I use
io.selendroid
selendroid-standalone
0.16.0

io.selendroid
selendroid-client
0.16.0

I am experiencing the same issue on android 6.0
Emulator is restarted after that.
I am experiencing the same issue

10-06 19:47:44.569  1318  1341 I ActivityManager: Force stopping io.selendroid.testapp appid=10053 user=-1: uninstall pkg
10-06 19:47:44.569  1318  1341 I ActivityManager: Killing 2366:io.selendroid.testapp/u0a53 (adj 0): stop io.selendroid.testapp
10-06 19:47:44.595  1318  1361 I art     : Starting a blocking GC Explicit
10-06 19:47:44.607  1318  1361 I art     : Explicit concurrent mark sweep GC freed 11495(931KB) AllocSpace objects, 8(192KB) LOS objects, 33% free, 6MB/10MB, paused 157us total 11.122ms
10-06 19:47:44.609  1318  1341 W ActivityManager: Crash of app io.selendroid.testapp running instrumentation ComponentInfo{io.selendroid.server_1/io.selendroid.server.ServerInstrumentation}
10-06 19:47:44.609  1318  1341 I ActivityManager: Force stopping io.selendroid.testapp appid=-1 user=0: finished inst
--------- beginning of crash
10-06 19:47:44.609  1318  1341 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
10-06 19:47:44.609  1318  1341 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method 'void android.app.IUiAutomationConnection.shutdown()' on a null object reference
10-06 19:47:44.609  1318  1341 E AndroidRuntime: 	at com.android.server.am.ActivityManagerService$MainHandler.handleMessage(ActivityManagerService.java:2026)
10-06 19:47:44.609  1318  1341 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
10-06 19:47:44.609  1318  1341 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:148)
10-06 19:47:44.609  1318  1341 E AndroidRuntime: 	at android.os.HandlerThread.run(HandlerThread.java:61)
10-06 19:47:44.609  1318  1341 E AndroidRuntime: 	at com.android.server.ServiceThread.run(ServiceThread.java:46)
10-06 19:47:44.610  1318  1488 W ActivityManager: Spurious death for ProcessRecord{edab98d 0:io.selendroid.testapp/u0a53}, curProc for 2366: null
10-06 19:47:44.611  1504  1504 W RecentsTaskLoader: Missing ActivityInfo for ComponentInfo{io.selendroid.testapp/io.selendroid.testapp.HomeScreenActivity} u=0
10-06 19:47:44.619  1318  1341 I Process : Sending signal. PID: 1318 SIG: 9
10-06 19:47:44.651   992   992 I ServiceManager: service 'telecom' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'launcherapps' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'media_projection' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'imms' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'wifi' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'wifiscanner' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'rttmanager' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'connectivity' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'servicediscovery' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'updatelock' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'notification' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'devicestoragemonitor' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'location' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'country_detector' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'search' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'netpolicy' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'wifip2p' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'dropbox' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'wallpaper' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'audio' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'network_management' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'textservices' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'network_score' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'netstats' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'DockObserver' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'midi' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'serial' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'jobscheduler' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'backup' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'appwidget' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'voiceinteraction' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'diskstats' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'samplingprofiler' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'commontime_management' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'dreams' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'assetatlas' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'graphicsstats' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'print' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'restrictions' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'media_session' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'media_router' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'trust' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'fingerprint' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'procstats' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'meminfo' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'gfxinfo' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'dbinfo' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'cpuinfo' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'permission' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'processinfo' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'sensorservice' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'battery' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'usagestats' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'webviewupdate' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'scheduling_policy' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'telephony.registry' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'media.camera.proxy' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'account' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'content' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'vibrator' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'consumer_ir' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'alarm' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'window' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'input' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'package' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'user' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'activity' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'input_method' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'accessibility' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'mount' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'uimode' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'lock_settings' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'deviceidle' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'device_policy' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'statusbar' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'clipboard' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'batterystats' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'appops' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'power' died
10-06 19:47:44.651   992   992 I ServiceManager: service 'display' died
10-06 19:47:44.651  1005  1005 W AudioFlinger: power manager service died !!!
10-06 19:47:44.651  1012  1012 D fingerprintd: binder died
10-06 19:47:44.651  1012  1012 V fingerprintd: nativeCloseHal()
10-06 19:47:44.653  1772  1928 E WifiManager: Channel connection lost
10-06 19:47:44.653  1504  1656 E WifiManager: Channel connection lost
10-06 19:47:44.654   993   993 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x7f867cfc3c00
10-06 19:47:44.654   993   993 D SurfaceFlinger: Screen type=0 is already mode=2
10-06 19:47:44.655  1006  1006 E installd: eof
10-06 19:47:44.655  1006  1006 E installd: failed to read command
10-06 19:47:44.655  1006  1006 I installd: closing connection
10-06 19:47:44.655   991   991 I lowmemorykiller: ActivityManager disconnected
10-06 19:47:44.655   991   991 I lowmemorykiller: Closing Activity Manager data connection
10-06 19:47:44.659  2415  2447 D Documents: Update found 5 roots in 259ms
10-06 19:47:44.697   993  1073 E SurfaceFlinger: ro.sf.lcd_density must be defined as a build property


DRILL-5237: add test coverage

Add test coverage for a case when flatten operator returns empty batch for the first time.
@rchallapalli Can you please review?
http://<IP_ADDRESS>:8080/job/Framework-Regression/896/console

I see that the query passed in your functional run but is the below even syntactically correct?
"where t1.a .a1 like 'a1'"

@rchallapalli good catch. It actually works as is but I made the change. Below is the test run after the change.
http://<IP_ADDRESS>:8080/job/Framework-Regression/897/console

LGTM +1


Support custom schemas

Currently running into issues with --ast not generating a valid schema:
pushing r8.im/cuuupid/redacted: PUT https://r8.im/v2/cuuupid/redacted/manifests/latest: UNKNOWN: The model's OpenAPI schema is invalid

It would be nice if I could pass in a JSON schema directly :)

Included in #33


container/commit: Auto-clean /var/tmp, /tmp, /run

The original command here was just scoped to /var, but we also
don't want content in /run.  Extend the tooling to handle that
and the other two temporary directories.
Also, let's be a bit nicer here and auto-clean empty directories
in /var.
I was testing out the
https://github.com/coreos/coreos-layering-examples/blob/main/tailscale/Dockerfile
example and today we have this:
drwxr-xr-x root/root         0 2022-09-13 18:53 run/
drwxr-xr-x root/root         0 2022-09-13 18:51 run/rpm-ostree/
drwxr-xr-x root/root         0 2022-09-13 18:53 run/rpm-ostree/lock/
drwxr-xr-x root/root         0 2022-09-13 18:51 run/systemd/
drwxr-xr-x root/root         0 2022-09-13 18:51 run/systemd/resolve/
-rwx------ root/root         0 2022-09-13 18:51 run/systemd/resolve/stub-resolv.conf
...
drwxr-xr-x root/root         0 2022-09-13 18:53 var/
drwxr-xr-x root/root         0 2022-09-13 18:53 var/cache/
drwx------ root/root         0 2022-09-13 18:53 var/cache/ldconfig/
-rw------- root/root     22000 2022-09-13 18:53 var/cache/ldconfig/aux-cache
drwxr-xr-x root/root         0 2022-09-08 23:10 var/cache/tailscale/
drwxr-xr-x root/root         0 2022-09-13 18:53 var/tmp/

In this set, we can auto-clean the leftover locking directories
rpm-ostree (erroneously) leaves in /run.
I am tempted to auto-cleanup the stub-resolv.conf thing and the
ldconfig/aux-cache.

This pairs with https://github.com/ostreedev/ostree-rs-ext/pull/366

I do like the empty directories /var autocleaning, it's a clear UX improvement. It assumes there is something re-creating those on boot (e.g. tmpfiles.d fragment or the software itself), but I think that's fine. And we can always implement auto-translation to tmpfiles.d here in the future if we want.
I'm less convinced about inspecting /run. IMHO it makes sense to leave that one alone (i.e. ignore any content landing there), basically treating it similarly to /tmp as an ephemeral hierarchy.

I'm less convinced about inspecting /run. IMHO it makes sense to leave that one alone (i.e. ignore any content landing there), basically treating it similarly to /tmp as an ephemeral hierarchy.

Good feedback!  Fixed.  For example, we no longer warn about anything in /var/tmp but just silently clean it, which definitely seems friendlier to me.

Tangentially related, cc https://github.com/containers/buildah/issues/4242 for a podman bug we may also want to work around in this code.

Got the new CI green :tada:


Remove blueprint_id before applying attributes

For historical reason some old dialogs may have blueprint_id which no longer exist. The fix is a safety check in case someone needs to import a dialog yaml file from an earlier exporting.

@miq-bot add_label technical debt
@miq-bot assign @gmcculloug

@eclarizio I originally thought a spec test is not necessary because it is not normal logic. By adding "blueprint_id" => "456" to the dialog hash makes it appear to be a desired attribute.
Anyway I now added this attribute to the test data. But we cannot validate the result because it is no longer a valid field for Dialog class.


Test(windows-2022, msvc, _, _) of ci.yml didn't successfully use msvc as the compiler

log of Test(windows-2022, msvc, _, _):
-- The CXX compiler identification is Clang 17.0.6 with GNU-like command-line
-- The C compiler identification is Clang 17.0.6 with GNU-like command-line

I couldn't track down which commit introduced this issue because the logs have been outdated.

Upvote & Fund
@aminya is using Polar.sh so you can upvote and help fund this issue. The funding is received once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog!

@aminya I have just tested the current main with the example cpp_vcpkg_project project on windows 10 with
 MSBuild-Version 17.11.2+c078802d4 für .NET Framework
 Microsoft Visual Studio Professional 2022 (64-bit) - Current Version 17.11.2
It have tested the Workflow presets:

"windows-msvc-debug"
"windows-msvc-release"

I dit not generate a VS solution with cmake, I just opended the project directory from VS2022!
But I had to change some values, first, than in works for me:
MINGW64 ~/Workspace/cmake/project_options/examples/cpp_vcpkg_project (main)
$ git diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 93f08e6..02adf7f 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -1,4 +1,4 @@
-cmake_minimum_required(VERSION 3.21...3.28)
+cmake_minimum_required(VERSION 3.25...3.30)

 # set a default CXX standard for the tools and targets that do not specify them.
 # If commented, the latest supported standard for your compiler is automatically set.
@@ -14,13 +14,14 @@ endif()

 # Add project_options from https://github.com/aminya/project_options
 # Change the version in the following URL to update the package (watch the releases of the repository for future updates)
-set(PROJECT_OPTIONS_VERSION "v0.36.4")
-FetchContent_Declare(
-  _project_options
-  URL https://github.com/aminya/project_options/archive/refs/tags/${PROJECT_OPTIONS_VERSION}.zip)
-
-FetchContent_MakeAvailable(_project_options)
-include(${_project_options_SOURCE_DIR}/Index.cmake)
+## set(PROJECT_OPTIONS_VERSION "v0.36.4")
+## FetchContent_Declare(
+##   _project_options
+##   URL https://github.com/aminya/project_options/archive/refs/tags/${PROJECT_OPTIONS_VERSION}.zip)
+##
+## FetchContent_MakeAvailable(_project_options)
+## include(${_project_options_SOURCE_DIR}/Index.cmake)
+include(../../Index.cmake)

 # Define the features of the project
 include("./Features.cmake")
@@ -84,8 +85,8 @@ project_options(
   PREFIX
   "my"
   ENABLE_CACHE
-  ${ENABLE_CPPCHECK}
-  ${ENABLE_CLANG_TIDY}
+  # ${ENABLE_CPPCHECK}
+  # ${ENABLE_CLANG_TIDY}
   ${ENABLE_VS_ANALYSIS}
   # ENABLE_CONAN
   # ENABLE_INTERPROCEDURAL_OPTIMIZATION
diff --git a/cmake/presets/CMakeUnixPresets.json b/cmake/presets/CMakeUnixPresets.json
index 25551d0..dd57396 100644
--- a/cmake/presets/CMakeUnixPresets.json
+++ b/cmake/presets/CMakeUnixPresets.json
@@ -2,7 +2,7 @@
   "version": 6,
   "cmakeMinimumRequired": {
     "major": 3,
-    "minor": 27,
+    "minor": 25,
     "patch": 0
   },
   "include": [
diff --git a/cmake/presets/CMakeWindowsPresets.json b/cmake/presets/CMakeWindowsPresets.json
index 3e63a17..f40eebf 100644
--- a/cmake/presets/CMakeWindowsPresets.json
+++ b/cmake/presets/CMakeWindowsPresets.json
@@ -27,10 +27,12 @@
         "value": "host=x64",
         "strategy": "external"
       },
-      "cacheVariables": {
-        "ENABLE_CPPCHECK_DEFAULT": false,
-        "ENABLE_CLANG_TIDY_DEFAULT": false
-      }
+        "cacheVariables": {
+            "CMAKE_VS_VERSION_RANGE": "[17.0,)",
+            "CMAKE_HOST_SYSTEM_PROCESSOR": "AMD64",
+            "ENABLE_CPPCHECK_DEFAULT": false,
+            "ENABLE_CLANG_TIDY_DEFAULT": false
+        }
     },
     {
       "name": "windows-msvc-debug",

MINGW64 ~/Workspace/cmake/project_options/examples/cpp_vcpkg_project (main)
$

It seems that Ninja prefers Clang over MSVC. This can be fixed in setup-cpp by setting CXX/CC to cl


Fail all unknown properties at once

Flyway fails-fast if it comes across an unknown configuration property. However, if there are multiple unknown properties in a config file, Flyway currently fails on the first one it finds; once that is corrected then, and only then, will it fail on the subsequent one. It would be better to list all unknown properties in the failure message, so that they can be remedied in a single iteration.

Fixed in 6.1.4


[mp] Add new tips and tricks

Description
Update tips & tricks page to contain videos from past two weeks.

@thomaschung408 could you take a look here? looks like this fell through the cracks


livox MID-70

Hi,
I'm trying to do this package with LIVOX MID-70 steady state LiDAR, is it available?

Hi,
I'm trying to do this package with LIVOX MID-70 steady state LiDAR, is it available?

yes, I have tried. but relocalize service is not work

hi，
how you change the file to fit other lidar?
thanks


feat: update to fastify 4

In this PR:

Updated fastify's major

Checklist:

[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

[x] Have you lint your code with pnpm lint locally prior to submission?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your core changes, as applicable?
[x] Have you successfully ran build with pnpm build of your changes locally?
[x] Have you successfully ran tests with pnpm test of your changes locally?

I believe this will solve #6.
Still need to check it later at work, since we are having this issue in our cache server.
@fox1t

Good catch. Since we are not introducing breaking changes, this should be safe.

Could you address the only comment that remains and resolve the conflicts?

Could you address the only comment that remains and resolve the conflicts?

Done 😊

Would love to see this merged! 🎉

This is a minor bump @matteovivona

@danielmitrov I am not sure about the "This branch has conflicts that must be resolved" message. Can you look into it so we can merge and publish this PR?

Ok, it is about the package.json and pnpm-lock.

Yeah, sure. Fixed the conflicts!

@matteovivona can you approve this PR so I can merge it? Or do you want @fox1t to approve it?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


sort-jobs-by-dru function can be made lazy

Consider using something like:
(defn sorted-merge
  "Accepts a seq-able datastructure `colls` where each item is seq-able.
   Each seq-able in `colls` is assumed to be sorted based on `key-fn`
   Returns a lazy seq containing the sorted items of `colls`

   Initial code from: http://blog.malcolmsparks.com/?p=42"
  ([key-fn ^java.util.Comparator comp-fn colls]
   (letfn [(next-item [[_ colls]]
             (if (nil? colls)
               [:end nil] ; Allow nil items in colls
               (let [[[yield & remaining] & other-colls]
                     (sort-by (comp key-fn first) comp-fn colls)]
                 [yield (if remaining (cons remaining other-colls) other-colls)])))]
     (->> colls
       (vector :begin) ; next-item input is [item colls], need initial item
       (iterate next-item)
       (drop 1) ; Don't care about :begin
       (map first)
       (take-while (partial not= :end)))))
  ([key-fn colls]
   (sorted-merge key-fn compare colls))
  ([colls]
   (sorted-merge identity compare colls)))

To sort between users

It is now lazy since #132


Use javax.ws.rs version 2

Use javax.ws.rs-api instead of jsr311-api.

why?

I'm just testing this out for Flemstrom. It conflicts with barge deps unless you use the newer library.


collectd.org is down

says "refuse to connect".
go get collectd.org hence does not work.

same problem +1

Ouch, sorry about that! Hardware upgrade went a little haywire, I'm working on getting the site back up ASAP —@flocto
12:06 AM - 19 Jul 2018

Is there any chance you remove the import comments (// import "collectd.org/api" ) that force the vanity URL? It would be nice to simply import github.com/collectd/go-collectd

Florian, can you please fix WIKI ?
https://collectd.org/wiki/ is down, server responding with 403 Forbidden.

New issue created specially for WIKI's inaccessibility : https://github.com/collectd/collectd/issues/2868
So, close this. )


Optimize shared texture creations

Fix #98733
This PR removes an unnecessary copy of Texture::slice_trackers, as it is always cleared afterward.
Build: scons platform=linuxbsd optimize=speed_trace debug_symbols=yes
Profiler: Tracy
Test project: see MRP in  #98733
Results with master branch:

Results with this PR:

I think slice_trackers should be turned into a pointer instead and allocate it on demand only if a shared texture is created. The HashMap currently occupies 48 bytes per texture and largely goes unused in the vast majority of cases. Then when the copy is made, the simple solution is to just set it to a nullptr. That way there'll be no cost from copying the contents as is and we get a reduced memory footprint overall, for the small extra cost of an indirection.
I'm not a big fan of the proposed solution as it adds another function to maintain and keep track of when the copy is made.

I agree and I am not a big fan of my solution too : ) I am going to rework my PR with your solution, it's a nice idea.


HW v2.1

[x] update I2S Pins on Feather (see Table: https://github.com/BlueAndi/esp-rgb-led-matrix/blob/Development/doc/boards/pixelix/v2.0/ELECTRONIC.md)
[x] add One Wire (see #40)
[x] add 3V3 and GND to I2S, I2C & One-Wire interface pins in a molex connector

@gabryelreyes @nischneider Can we close this?


Update conflict pipeline and test

Filtering out problematic unit in ACLED data and flagging in the log for consistency.  I also realized the yaml wasn't producing results I was expecting so refactored to make all three resources appear in the database.  However, they are all linked to the same resource because the results only contain one resource per dataset (I've added a todo to address this).
cc @mcarans @turnerm

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

18 of 19 (94.74%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 92.9%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/hapi/pipelines/database/conflict_event.py
18
19
94.74%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
1086

Relevant Lines:
1169

💛  - Coveralls

@b-j-mills I see 3 resources in the dataset: https://data.humdata.org/dataset/afghanistan-acled-conflict-data and the YAML refers to all 3. Do you mean that 2 use the wrong resource id in the HAPI data? If so, do you think this is something that requires changes in HDX Python Scraper?

Yes, all rows in the HAPI data point to only one resource id instead of using all three (per country) - I think it will require changes in HDX Python Scraper!  I don't want to break every other pipeline, but this seems mandatory.  Maybe it could return a list of resources and a list of corresponding results instead of one resource and all results in one dictionary?


Page::Session::Set Doesn't work when using hot reloading.

Description
When running application with hot loader, many strange issues happening: Page::Session::Set doesn't work (simply doesn't  registers key), issues with Page::Go. When running application normally it works very good.
Code example to reproduce the issue:
def register(error_message):
    username_str = username.value
    email_str = email.value
    password_str = password.value

    if len(username_str) <= 5:
        error_message.value = 'Username should be at least 5 characters.'

        pg.page.update()

        return

    if not match(r'^[_a-z0-9-]+(\.[_a-z0-9-]+)*@[a-z0-9-]+(\.[a-z0-9-]+)*(\.[a-z]{2,4})$', email_str):
        error_message.value = 'Invalid Email.'

        pg.page.update()

        return

    if len(password_str) <= 8:
        error_message.value = 'Password should be at least 8 characters.'

        pg.page.update()

        return

    username_busy = False
    email_busy = False

    for user in db.get_value('users'):
        if user.username == username_str: username_busy = True
        if user.email == email_str: email_busy = True

    if username_busy and email_busy:
        error_message.value = 'Username and Email is already busy.'

        pg.page.update()

        return

    elif username_busy:
        error_message.value = 'Username is already busy.'

        pg.page.update()

        return

    elif email_busy:
        error_message.value = 'Email is already busy.'

        pg.page.update()

        return

    user = UserModel(username_str, email_str, password_str, [])

    db.get_value('users').append(user)

    db.commit()

    pg.page.session.set('user', username_str) # Here issue happens.

    pg.navigator.navigate('/', pg.page) # And here.

Describe the results you received:
user key wasn't registered, and page hasn't changed.
Describe the results you expected:
I expected it to register user key and change page to /.
Additional information you deem important (e.g. issue happens only occasionally):
This issues happening only in hot reload mode.
Flet version (pip show flet):
0.10.3

Operating system:
Windows 10

Hot reload:

No hot reload:

UPDATE: After committing to the database, the file is updated, so the application is restarted, so these two lines won't be executed:
pg.page.session.set('user', username_str)

pg.navigator.navigate('/', pg.page)

Maybe it's possible to fix it via ignoring database directory?

#2105 - This pull request attempts to fix this issue, but when a small change is made in the code, the application updates and all `page.session' keys are deleted.

So we need to use some external storage for session? I guess it could be just a json file somewhere in user's documents directory?

Fixed in https://github.com/flet-dev/flet/pull/2105


storage: split client into files

Signed-off-by: Boris Glimcher<EMAIL_ADDRESS>

Maybe this is only for testing purposes and is fine, but should the client have direct access to middle/backend?

Perhaps we should add a linter for golang.

Maybe this is only for testing purposes and is fine, but should the client have direct access to middle/backend?

this is just testing APIs


Form resets while typing

Using 2.4.0 (so it's not #13 ?)
While typing my master passwords, sometimes the form resets and I cannot type more than 3 or 4 characters before the password field is emptied.

Thanks for the report! Can you work out, which sites cause the problem?

I'll keep an eye out, I don't remember. I'm almost certain it happened on sites where it also sometimes didn't happen.

It just happened to me on reddit. It seemed to work fine and I copy/pasted the password, but realized I must have typed one char wrong, tried to type it again, and it was impossible to type more than 6 chars before it would reset.

It's happening to me everywhere.

I think it's related to which tabs you have open, not only the tab you are currently have focused, so I'll have to investigate further.


Add Signature, Sign, and Verify

The main design consideration was how to get objects to describe their default set of fields to sign, and to fetch ~arbitrary values for verifying, because Signature includes the list of signed fields. The rest pretty much flows from that.
Signatures can be attached to command steps (to begin with) and cover just the command itself. The core piece (throwing fields and values at a hash) is the same between Sign and Verify, so I implemented both.
I made the algorithm interface big enough to handle both symmetric and asymmetric schemes, but have only implemented HMAC-SHA256 here.

testing

Ah, I knew I was forgetting something here.


Non-player entities teleport incorrectly with End portal

Information

Server version:  git-Paper-266 (MC: 1.17.1) (Git: 0d19cd7)

Full output of /mv version -p: https://j.mp/3u0kFaJ

Server log: https://gist.github.com/JamesRagnarok/8a786bfadc4ef73e674c26a53d846d17

Help request
Problem
With Multiverse activate, non-player entities such as items and mobs can't land on obsidian platform in the End while going through the End portal. Instead, they seems spawn at 0, 63, 0, right on the Exit portal, and immediately teleport back into overworld. Moreover, when items and mobs leave the End through Exit portal, they do not show up at the world spawn of the overworld (I had my overworld spawn moved to 800 blocks away), but somewhere near 0, 63, 0. These are not vanilla behaviors and somehow do not affect players.
What I have tried
Disable Multiverse would fix this problem. I had the respawnWorld property set before (otherwise players cannot leave the End), but removing respawnWorld didn't help.
Screenshots

@JamesRagnarok I can shed a bit of light on your issues.
As far as non player entities entering the end at 0,0 you need to set your spawn location (MVSpawnLocation) for your end worlds to the air block above the center of the obsidian platforms, thus making it like vanilla.
I typically take the server down and just edit the worlds.yml file.
Or you can use /mvsetspawn <your_world> x y z yaw pitch.
In my case: /mvsetspawn FoxDen1_the_end 100.5 49.0 0.5 0.0 0.0
I'm having the same issue where non player entities (items, mobs, armor stands) that go into the exit end portal in the main end world always arrive in the main world near 0, 0. What I expect to happen is for those entities to arrive at the main world spawn location (-8325, 11132) that is set in the Multiverse worlds.yml file just as players do.
I'm suspect that Multiverse-NetherPortals (4.2.1) has something to do with this issue since if I remove it, everything works as expected. We use MVNP for a resource world with it's own nether. I've tested this with Multiverse-Core 4.2.2, 4.3.0 as well, also tried linking the 2 worlds to and from the end and that did not fix the issue.
Any help would be greatly appreciated.
Startup log: https://paste.lucko.me/2wmkCoCCw7
Multiverse-Core Debug Info: https://j.mp/3w6446y

Recently I ran into this issue as well. I tried to transport a shulker from the end to the overworld, but every time it suffocated in the bedrock at y=0. Interesting enough it did not spawn the shulker at x=0 and z=0, but instead at the original world spawn location (and at y=0).
I managed to solve this by loading spawn with a second player account. This way the area was loaded and upon transporting a shulker or item, it got placed at the actual spawn location as it was set with /mvsetspawn.
I hope this will be fixed properly at some point, but at least this is a workaround.

@FleXCrash Are you using Multiverse-NetherPortals?

I am indeed. Version 4.2.1 to be precise

So is this issue somehow related to spawn chunks loading? I thought keepspawninmemory: true by default should work.

We have our world spawn in memory. I've even set our world spawn at 0,0 and non player entities still arrive at a random location around it, so no difference. I've also tested using other players. I can have only Multiverse-Core and Multiverse-NetherPortals loaded and the problem exists. If I remove MVNP, everything works fine except for our mining world nether portals, so we're kind of stuck using it.

So is this issue somehow related to spawn chunks loading? I thought keepspawninmemory: true by default should work.

That is a very good point I forgot to mention.
Now I think about it, it was slightly different even. Indeed as has been said here, the items never end up as where I set /mvsetspawn. The items will always go to the original world spawn location.
Having the area loaded by a player only makes sure that the items are spawned at the correct y level. If nobody is loading it, then the items are spawned at y=0
Its been some time ago since we brought shulkers over from the end :p

Thought that this might be useful or at least interesting. I tossed a wool block in each of the 8 corners of the exit and portal. Then placed an armor stand against each of the 4 faces of the pillar. This is were that came out centered around the yellow block at 0,0. Which is outside of our world border but increased for this testing. I marked the wool items with torches.

.

This problem can still be reproduced nowadays.


Windows server running with pm2 error！anxious！

Version
v1.0.0
Reproduction link
https://github.com/nuxt/nuxt.js
Steps to reproduce
I am using PM2 to deploy my nuxt service on a windows server but I get an error and I am using a Linux server without error
pm2 start npm --name "demo3" -- run start
What is expected ?

What is actually happening?

Additional comments?
I don't know how to start nuxt on the server, but using linux server without problems and using windows server has a problem, we have been using windows which makes our business no way to run

This bug report is available on Nuxt.js community (#c6896)

It'd help if you could provide the whole stack trace/error message.

Because this bug report seems to be inactive for quite some time, I'll close it now. If you feel like it deserves some attention because it's not fixed, feel free to ping me and I'll reopen it.


fix - Google IDP doesn't work when created with ROSA CLI

Signed-off-by: Tzvika Avni<EMAIL_ADDRESS>SDA-6472
@zgalor @oriAdler @pvasant PTAL

/ok-to-test

@ciaranRoche can you ok-to-test again?

/ok-to-test

/ok-to-test

/ok-to-test

Hi, Guys.
Just wondering the current status for this fix.
Thanks.

@zvikorn anything missing for this to be merged?

@zgalor nope. Just lgtm

/lgtm

/lgtm

/assign @zgalor

/approved


Feature/tri 510

Reimplemented relationship object

Please ignore Sonar Code Analysis coverage failure as its false-pasitive (wrong configuration of jacoco?)
There are tests for AssetAdministrationShellDescriptor class

"Is there somethng you can do about these HIGH warnings and KICS checks? I don't see how these are an issue." - I think for KICS we will have another task, to fix all of that.


[MISC] Add subdirectories for results

Documentation preview available at https://docs.seqan.de/preview/seqan/hibf_benchmarks/38


Update repo location

Since you're publishing a fork on npm, you've created a new package 😄, so it would be good to help folks find the source that has your patches.

Fair point @dprothero. Was a rushed decision over a tight timeline at a previous role. I should just delete this repo and unpublish the package.

Thanks for the PR though

Not my finest hour. But thanks for the PR.


How to add characters?

Please explain what you mean.

My assumption is that he's looking for a glfwDrawText(char* string, int x, int y) function. If that is the case then no, GLFW does not have anything like that. It's for context creation and context-related IO.

@chaosink If you mean text input then see the character callback.


Use code example without type hints

Thanks again! :)

You are welcome. I hope it doesn't annoy you.

@smorokin If fixing errors would annoy me I should quit programming 😄
(yeah I know you mean several PRs but if anything I am grateful, not annoyed - that's the whole point of open source - together we can build something better than each of us alone).
Thanks!


VM/VMSS to support v2 Version of Azure Metadata Security Protocol

Preconditions
Need to release Python SDK support 2024-07-01
Related command
Please see v1 https://github.com/Azure/azure-cli/issues/27729 , this v2 involves deleting a parameter (proxy-agent-mode) from the v1 version and add a couple new
az vm create [--enable-proxy-agent {false, true}] [--wireServer-mode {Audit, Enforce, Disabled}] [--wireServer-InVMAccessControlProfileReferenceId "" ] [--imds-mode {Audit, Enforce, Disabled}] [--imds-InVMAccessControlProfileReferenceId "" ] [--keyIncarnationId integer]
az vm update
az vmss create
az vmss update
Resource Provider
Microsoft.Compute
Description of Feature or Work Requested
PM doc: https://microsoft.sharepoint.com/:w:/r/teams/CPlat-PM/_layouts/15/Doc.aspx?sourcedoc={DD02825F-7D23-4C67-B21C-6352733A8858}&file=Wire-Server Endpoint Security PM Spec.docx&action=default&mobileredirect=true&share=IQFfggLdI31nTLIcY1JzOohYAV82cMdRnCluKCTcaCyt91E
User can opt-in the Azure metadata security protocol for their VM by specifying the newly introduced VM or VMSS property, thus their VM can be protected from SSRF and Scorpin heart attack to IMDS and WireServer endpoints.
Need to support for vm create, vm update, vmss create, vmss update.
Minimum API Version Required
2024-03-01
Swagger PR link / SDK link
https://github.com/Azure/azure-rest-api-specs/pull/29402
Request Example
VM: https://github.com/Azure/azure-rest-api-specs/blob/c9d9a0180149e72541752672790ed642a439adfa/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2023-09-01/examples/virtualMachineExamples/VirtualMachine_Create_WithProxyAgentSettings.json
VMSS: https://github.com/Azure/azure-rest-api-specs/blob/c9d9a0180149e72541752672790ed642a439adfa/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2023-09-01/examples/virtualMachineScaleSetExamples/VirtualMachineScaleSet_Create_WithProxyAgentSettings.json
Target Date
08-06-2024
PM Contact
<EMAIL_ADDRESS>Engineer Contact
<EMAIL_ADDRESS>Additional context
No response

Thank you for opening this issue, we will look into it.

@hmyan90 I want to confirm with you whether this feature is related to security?

User can opt-in the Azure metadata security protocol for their VM by specifying the newly introduced VM or VMSS property, thus their VM can be protected from SSRF and Scorpin heart attack to IMDS and WireServer endpoints.

Target Date
08-06-2024

@hmyan90 This new feature seems to be related to security, right? If so, we will schedule it for the next sprint

yes, this is a very high priority security feature. We will need to get it into July release. Please reach out to PM<EMAIL_ADDRESS>for the priority clarify if needed. thanks.

Hi @hmyan90, could you please help generate python sdk in Swagger PR https://github.com/Azure/azure-rest-api-specs/pull/29402 so that we can use it for development and testing.


Split Razor Components topic

Fixes #16904
This PR was reconstituted due to a build error, but the error is occurring across MS. We can proceed with review/discussion on it.
Internal Review (links to the Components topic; navigate the remaining from the sidebar TOC)

Seems to have split rather cleanly. I was able to turn the Components BOOK! into a much shorter, focused topic with split out topics for ...

Data binding
Event handling :point_left: I did update the branch from "events" to "event handling" as we discussed on the other PR.
Templated components
Integrate components (into RP/MVC apps)
Globalization and localization
Advanced scenarios (Just one right now, Manual RenderTreeBuilder logic. We can add more as needed going forward.)

Examine the ordering in the toc.yml file at the end of the diff to see if this sequence makes sense reading these top-to-bottom, as many devs consume node topics in that sequence.
The new Integrate components topic is especially good here given that it combines app-level concerns that were covered in the Hosting model config topic with the component-level concerns from the Components topic.

@scottaddie I'm stuck ... this branch is breaking the build somehow without a useful error message. Do you have any i-dears?

Run script failed with no detailed information. Please retry building your content again. If the issue still happens, open a ticket in https://SiteHelp and include the error report for our team to troubleshoot

There are very few content updates ... just a few nits.

@scottaddie Resolved feedback. Thanks.
Will await @Rick-Anderson  to take a look, especially :eye: the topic ...

Titles
UIDs
URLs (filenames)
Sequence in the Blazor TOC node

@scottaddie  is more familiar, I'll let him sign off.

Fair enough .... just want to get (especially) the UIDs and filenames right since those get frozen.

FYI ... DR is too busy 🏃 to look right now, but he'll remark later for updates if required. I'm going to go ahead and merge after your, Scott, final signoff.
This afternoon and tomorrow morning, there will be a smaller split effort made for the JS Interop topic. It will be a lot easier to build and review than this 👹 monster. :smile:

@guardrex I'm taking another look right now. Hang tight.


Test cases

test to check if each of threads/processes can restart

check precedence order of states of Pipeline, States and Tasks


chore: release main

:robot: I have created a release beep boop
accesskit: 0.8.1
0.8.1 (2023-06-16)
⚠ BREAKING CHANGES

Move thread synchronization into platform adapters; drop parking_lot (#212)
Make Node opaque and optimize it for size (#205)

Features

Add C bindings (#230) (7f7f4c7)

Bug Fixes

Set appropriate representations on all public types that will be exposed via FFI (54e82f6)

Documentation

Fix outdated documentation for TreeUpdate (#182) (dd658c7)

Code Refactoring

Make Node opaque and optimize it for size (#205) (4811152)
Move thread synchronization into platform adapters; drop parking_lot (#212) (5df52e5)

accesskit_c: 0.4.0
0.4.0 (2023-06-16)
⚠ BREAKING CHANGES

Remove objc and Core Foundation types from C bindings public API (#243)
Improve C bindings package directory structure (#239)

Features

Add C bindings (#230) (7f7f4c7)
Add CMake support to C bindings (d7fd986)

Bug Fixes

Improve C bindings package directory structure (#239) (44c27e7)
Remove objc and Core Foundation types from C bindings public API (#243) (3ae1c11)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit bumped from 0.11.0 to 0.8.1
accesskit_windows bumped from 0.14.0 to 0.15.0
accesskit_macos bumped from 0.7.0 to 0.8.0
accesskit_unix bumped from 0.5.0 to 0.6.0

accesskit_consumer: 0.16.0
0.16.0 (2023-06-16)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)
Move thread synchronization into platform adapters; drop parking_lot (#212)
Make Node opaque and optimize it for size (#205)

Features

Automatically get button and link labels from descendants (#184) (ec5c38e)
Basic Unix platform adapter (#198) (1cea32e)
Text support on macOS (#191) (3a35dbe)

Bug Fixes

Force a semver-breaking version bump in downstream crates (#234) (773389b)
Make Node::filtered_parent recursive as it was meant to be (#203) (d2faef5)
More reliable handling of the edge case for wrapped lines (#192) (c626d2c)

Code Refactoring

Make Node opaque and optimize it for size (#205) (4811152)
Move thread synchronization into platform adapters; drop parking_lot (#212) (5df52e5)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit bumped from 0.11.0 to 0.8.1

accesskit_macos: 0.8.0
0.8.0 (2023-06-16)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)
Move thread synchronization into platform adapters; drop parking_lot (#212)
Make Node opaque and optimize it for size (#205)
Move lazy initialization from the core platform adapter to the caller (#179)

Features

Live regions on macOS (#196) (47d8d9f)
Text support on macOS (#191) (3a35dbe)

Bug Fixes

Correctly apply the DPI scale factor to coordinates (#185) (d263938)
Don't expose the window title in our root element on macOS (#187) (9739b74)
Expose static text as the value rather than the title on macOS (#186) (e3720c8)
Expose which accessibility selectors are actually allowed for a particular node (#181) (c4cbb23)
Fix macOS leaks (e8537fc)
Fix problems related to the root node (#231) (7228494)
Force a semver-breaking version bump in downstream crates (#234) (773389b)
Handle views with flipped coordinates (#174) (d14484c)
Make VoiceOver move through nodes in logical order (#176) (f060be4)
More reliable handling of the edge case for wrapped lines (#192) (c626d2c)
Pin objc2 dependency to 0.3.0-beta.3 (#201) (0adfed1)
Re-export types from objc2 (#172) (1ac67ad)

Code Refactoring

Make Node opaque and optimize it for size (#205) (4811152)
Move lazy initialization from the core platform adapter to the caller (#179) (f35c941)
Move thread synchronization into platform adapters; drop parking_lot (#212) (5df52e5)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit bumped from 0.11.0 to 0.8.1
accesskit_consumer bumped from 0.15.0 to 0.16.0

accesskit_unix: 0.6.0
0.6.0 (2023-06-16)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)
Move thread synchronization into platform adapters; drop parking_lot (#212)
Make Node opaque and optimize it for size (#205)

Features

Add features for async runtimes on Unix (#248) (b56b4ea)
Basic Unix platform adapter (#198) (1cea32e)

Bug Fixes

Force a semver-breaking version bump in downstream crates (#234) (773389b)
Update atspi dependency (#217) (93f2dc9)

Code Refactoring

Make Node opaque and optimize it for size (#205) (4811152)
Move thread synchronization into platform adapters; drop parking_lot (#212) (5df52e5)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit bumped from 0.11.0 to 0.8.1
accesskit_consumer bumped from 0.15.0 to 0.16.0

accesskit_windows: 0.15.0
0.15.0 (2023-06-16)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)
Move thread synchronization into platform adapters; drop parking_lot (#212)
Make Node opaque and optimize it for size (#205)
Update winit to 0.28 (#207)
Move lazy initialization from the core platform adapter to the caller (#179)

Bug Fixes

Correct broken UIA method implementation that was incompatible with Windows 11 ATs (#193) (3c527c7)
Fix Windows 32-bit build errors (#223) (41f28b6)
Force a semver-breaking version bump in downstream crates (#234) (773389b)
More reliable handling of the edge case for wrapped lines (#192) (c626d2c)
Provide fallback property implementations for the window root (#194) (f3d30b9)
Update windows-rs to 0.44 (#220) (a6b0a12)

Miscellaneous Chores

Update winit to 0.28 (#207) (3ff0cf5)

Code Refactoring

Make Node opaque and optimize it for size (#205) (4811152)
Move lazy initialization from the core platform adapter to the caller (#179) (f35c941)
Move thread synchronization into platform adapters; drop parking_lot (#212) (5df52e5)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit bumped from 0.11.0 to 0.8.1
accesskit_consumer bumped from 0.15.0 to 0.16.0

accesskit_winit: 0.15.0
0.15.0 (2023-06-16)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)
Move thread synchronization into platform adapters; drop parking_lot (#212)
Make Node opaque and optimize it for size (#205)
Update winit to 0.28 (#207)
Move lazy initialization from the core platform adapter to the caller (#179)

Features

Add features for async runtimes on Unix (#248) (b56b4ea)
Basic Unix platform adapter (#198) (1cea32e)
Feature-gate the Unix adapter in accesskit_winit (#214) (be95807)

Bug Fixes

Don't force winit's X11 and Wayland features to be enabled (#209) (a3ed357)
Force a semver-breaking version bump in downstream crates (#234) (773389b)
Reduce the winit version requirement to match egui (#170) (1d27482)

Miscellaneous Chores

Update winit to 0.28 (#207) (3ff0cf5)

Code Refactoring

Make Node opaque and optimize it for size (#205) (4811152)
Move lazy initialization from the core platform adapter to the caller (#179) (f35c941)
Move thread synchronization into platform adapters; drop parking_lot (#212) (5df52e5)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit bumped from 0.11.0 to 0.8.1
accesskit_windows bumped from 0.14.0 to 0.15.0
accesskit_macos bumped from 0.7.0 to 0.8.0
accesskit_unix bumped from 0.5.0 to 0.6.0

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/DataTriny/accesskit/releases/tag/accesskit-v0.8.1 :sunflower:

:robot: Release is at https://github.com/DataTriny/accesskit/releases/tag/accesskit_consumer-v0.16.0 :sunflower:

:robot: Release is at https://github.com/DataTriny/accesskit/releases/tag/accesskit_macos-v0.8.0 :sunflower:

:robot: Release is at https://github.com/DataTriny/accesskit/releases/tag/accesskit_unix-v0.6.0 :sunflower:

:robot: Release is at https://github.com/DataTriny/accesskit/releases/tag/accesskit_windows-v0.15.0 :sunflower:

:robot: Release is at https://github.com/DataTriny/accesskit/releases/tag/accesskit_winit-v0.15.0 :sunflower:

:robot: Release is at https://github.com/DataTriny/accesskit/releases/tag/accesskit_c-v0.4.0 :sunflower:


[SmartReact] Support gif emojis

smart reaction still dosnt support gif emojies

Hi, this should be resolved with 6160ad4.


Export graph: include extension in filename

When we export a graph it would be nice if the suggested filename would include the extension.
Example: download.png
Also, instead if 'download' it would be great if the filename could be based on the graph title.

Shipped in 0.4-alpha.


powertoys Run garbled code

Microsoft PowerToys version
0.75.1
Installation method
Scoop
Running as admin
None
Area(s) with issue?
PowerToys Run
Steps to reproduce

Candidate item, the character to be matched is garbled. If that character is typed out, the garbled character will disappear.
✔ Expected Behavior
No garbled characters
❌ Actual Behavior
Display garbled characters
Other Software
none

/bugreport

Hello, I generated a bug report according to your suggestion, but I did not find the corresponding report file on the desktop.


Update to System.js 0.18.x

Alpha35 is a showstopper here.

Fixed by https://github.com/mgechev/angular2-seed/commit/e5a418d872b0b939da6887a7c5bc4ff2833d2bfb


[WIP] add inspect screen. closes #385

this currently doesn't work really because of some dom diffing problems

@juliangruber When I edit the name of a dat and click "Save", it navigates to the detail view (and does not save)

@Kriesse this should be fixed now :)

@juliangruber What are the reasons for the failing tests? Otherwise, looks merge-ready to me!

only one part of the CI setup failed, and it can't be rerun for some reason. Merging!


Postgresql connect issue with DB from Azure

What version of UAA are you running?
74.27.0
How are you deploying the UAA?
I am deploying the UAA

using a bosh release I downloaded from bosh.io

What did you do?
Updated from 74.26.0 to 74.27.0. The postgres DB provisioned from Azure rejected connection from uaa.
We manually checked the postgresql version in uaa.war to analyze that as reason.
In 74.26.0 the version 42.2.12 is used , in 74.27.0 42.2.16 is used.
If we switch back tio 74.26.0 we have the issue with #1347 and even more we found that
in version 74.26.0 there are libraries
"spring-beans" % "5.2.6.RELEASE"
"spring-context" % "5.2.6.RELEASE"
"spring-core" % "5.2.6.RELEASE"
which re-opens the issue https://tanzu.vmware.com/security/cve-2020-5421
What did you expect to see? What goal are you trying to achieve with the UAA?
Expect uaa with
"spring-beans" % "5.2.9.RELEASE"
"spring-context" % "5.2.9.RELEASE"
"spring-core" % "5.2.9.RELEASE"
and
https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.18
Because:
We manually patched the uaa and with postgresql driver 42.2.18 the Azure issue is fixed,
because of gssEncMode setting is fixed
What did you see instead?
Connect postgresql DB and a successful uaa startup

I looked into the spring version mismatch after we spoke yesterday. Because of the way the project is setup, the springBootVersion property determines the version of spring-framework-bom, not the springVersion property. springVersion is vestigial.
In v74.26.0 the springBootVersion is 2.3.0.RELEASE. The spring framework dependencies are then determined by spring-boot-dependencies, which will bring in spring framework 5.2.6.
In v74.27.0 I see that springBootVersion is 2.3.4.RELEASE which will result in the inclusion of spring framework 5.2.9.
I agree this is confusing; the dependencies file should not express springVersion if it is overridden by springBootVersion. I have put a story into the backlog to address the problem: https://www.pivotaltracker.com/story/show/175451332
Hopefully that provides some clarity.
That said, it sounds like the main issue here is that you're having trouble connecting to an Azure postgresql instance. This github issue covers the topic pretty thoroughly. From what I can tell this is a problem with Azure. That github issue reports Azure is providing a fix, but it isn't timely.
I see that you've included a PR to pin the postgres JDBC library ahead to the latest version. As discussed previously, we'd like to avoid pinning versions of transitive dependencies if possible, allowing them to be managed by the spring BOMs. I see that the postgres JDBC team recommends adding gssEncMode=disable to the provided database url. Have you tried this solution as a work around until Azure sorts itself out?

I created this issue because of following conflict

If we use the latest uaa bosh release we are free of known CVEs but we cannot run it in Azure.
If we use the version prio to the lastest , then we see various CVEs, e.g. postgres but also spring framework.

I see that issue inside jdbc driver and this is packed with uaa.war so I dont see it as Azure issue.
We proofed that with version 42.2.18 the issue, which was obviously introduced with 42.2.15 , is fixed.
So what I ask you is, to provide a uaa release with postgresql 42.2.18, either via spring boot update (which might come later) or with an extra dep. update, and for safing your time i created the PR.
I asked our Ops colleges to set the database url with this arbitrary setting, but they dont know, therefore , if you mean that is possible, please provide details on that.
What we have is
url: jdbc:postgresql://XXXXXX.database.azure.com:5432/uaadb?sslmode=verify-ca&sslfactory=org.postgresql.ssl.DefaultJavaSSLFactory
So  if I look into
https://github.com/cloudfoundry/uaa-release/blob/develop/jobs/uaa/templates/config/uaa.yml.erb#L258-L269
then we may can set uaadb with "uaadb?gssEncMode=disable", but then we could probably get
url: jdbc:postgresql://XXXXXX.database.azure.com:5432/uaadb?gssEncMode=disable?sslmode=verify-ca&sslfactory=org.postgresql.ssl.DefaultJavaSSLFactory
Further recommendations?
Thanks

I see. Yes, uaa-release would have to be extended to accept extra db connection parameters.  I think that might be more durable solution, as it gives some flexibility to work with the different cloud SQL providers.
I could imagine the uaa job spec being extended something like this:
  uaadb.connectionProperties:
    gssEncMode: disable
    someOtherProperty: someValue

Essentially a map of vendor specific connection properties. That map of values would then be appended to the connection url.
Thoughts?

So I agree on a vendor specific property map
Maybe you add this to YAML and the existing class
https://github.com/cloudfoundry/uaa/blob/develop/server/src/main/java/org/cloudfoundry/identity/uaa/db/DatabaseUrlModifier.java, e.g. already adds the timeout for connect
Extending the bean
https://github.com/cloudfoundry/uaa/blob/develop/server/src/main/resources/spring/data-source.xml#L11-L15
would allow the setting in yml files or a system property/env.
Because:
if bosh is going to be retired with k8s, this enhancement could still be used.
The issue (we have) could be solve if spring publish its new release and it looks like they do it today, e.g. https://github.com/spring-projects/spring-boot/releases ... so if this 2.3.x version is out can we get then a new uaa-release with the update ?

Would you like to create PRs for this functionality?

yes I can do


Upload antrea-aks.yml manifest automatically to release assets

Manifest is generated by prepare-assets.sh but was not uploaded.

/skip-all


chore(main): release 0.4.1

:robot: I have created a release beep boop
0.4.1 (2023-12-19)
Bug Fixes

add parameter use_cached to BlackholeGraph._get_blackhole_plasmids(), solving the slowdown introduced in releases v0.3.3 and v0.3.4 (fc7685e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/leoisl/plasnet/releases/tag/v0.4.1 :sunflower:


Image does not appear when sharing

@jvandemo
I have added image tag to have a certain image appear when sharing to Facebook
<meta name="og:image" content="assets/images/background.jpg" />. This works well when I share the homepage but whenever I share any other page, no image appears. The title and the description appear correctly but no image appears. Not the even the home page one.
Here's what I am doing when trying to update the image:
<update-meta name="og:image" content="{{property.property.images[0].image_path}}"></update-meta>
Any idea how can I debug this issue further?

Resolved in #5. Absolute path needed to be specified.


Cannot expose ambassador app, node had condition DiskPression

Hi,
I deployed CDK on AWS using the bundle. All well. I deployed then kubeflow on top of it and I ran into some issues with the script (see my other bug) and I've worked around them manually. Now, when I try to expose the ambassador app to access the kubeflow dashboard, the first ambassador-auth unit goes into this error: The node was low on resource: ephemeral-storage. Container ambassador was using 93222, which exceeds its request of 0., and all the other ambassador-auth units go into error with the error message Pod The node had condition: [DiskPressure].. It also looks like because of this error, juju tried to scale out and spawned 8 more units of the ambassador-auth, and they all ended up in the same state. The machines used for this are used only for this test, nothing else runs on them.
How can I resolve this issue? I am unable to deploy fully kubeflow at the moment.
My CDK status

juju kubeflow model status

kubectl status

Something weird too that I do not know if it is due to kubeflow or juju..probably juju. But I tried to scale down the number of units for ambassador-auth and it did the opposite.
$ juju scale-application ambassador-auth 2
ambassador-auth scaled to 2 units

gave that result... I have 17 units in error now o.o

I followed the workaround in the other issue I opened, and everything deployed fine this time. This bug was probably an aftermath of the other issues I faced. Thank you!


add pytorch API and controller

Add PyTorch API and controller into all-in-one branch.
Tested with create and delete pytorch job.
/cc @Jeffwan

@zw0610 Are there any changes from the source?

... Seems bot now detects the Github approval and converts it to a /approve label. I use Github approve and this PR was merged immediately which is not intended.

@zw0610 Are there any changes from the source?

For the API part, little. For the controller part, a lot. As we are adopting the reconciler mode, the pytorch-operator controller changes the code from setting up the controller to reconciling a pytorch job. Although we are using the reconcile method from kubeflow/common, I double checked the existing pytorch operator code and found the reconciliation part looks almost the same, despite from the service generation and Pod env setting.

part of https://github.com/kubeflow/common/issues/138


Stage

There are some failed builds here from Netlify, but I'm not sure how to fix them right now. I'm going to merge this PR, make sure everything works locally, then try to deploy to Netlify again. 🤞


README: fix typo

Thanks. But there's at least one more instance of the same mistake, could you correct that too

sure, fixed

thanks


Hive Keychain can overflow too much while using Brave

When Brave has a predetermined zoom over 100% the Brave browser respects this for extensions and renders larger than the popup window allows.  There is overflow requiring scrollbars which are sometimes disabled.
Mitigation:  Set predetermined Zoom to normal (100%).  I would like another mitigation if possible apart from using some other browser.

Which version of Keychain are you using?
Which screens can't you use properly for the lack of scrollbars?


No suggestions or auto-import with pass lib

Environment data

Language Server version: 2021.5.3-pre.1
OS and version: macOS 11
Python version (& distribution if applicable, e.g. Anaconda): Python 3.9.5 from Homebrew

Expected behaviour
I have added passlib to my project and expected, that an auto import is offered for it or some of its contents. This doesn't work. But an auto import is suggested for attrs which is installed as a dependency of passlib. I created a small video showcasing the issue.
https://user-images.githubusercontent.com/758/118319307-ddbe6c00-b4fa-11eb-80ec-600cbf17607c.mp4
As passlib is a quite common Python library, I think it is worth to research this particular problem.
Actual behaviour
I would expect to get passlib offered as an auto import too.

The same problem with requests in python 3.8.9 after python -m pip install requests

Also, none of the commented lines are recognized by the auto-import, I'm sure that these classes and functions are in the configured Python environment.

If your venv isn't in the workspace, then this may be #923; otherwise, ensure you have indexing enabled with "python.analysis.indexing": true or by using the insiders build.

If your venv isn't in the workspace, then this may be #923; otherwise, ensure you have indexing enabled with "python.analysis.indexing": true or by using the insiders build.

I tried to install this option, it is now enabled. I still can't get hints without importing this package in advance.

To analyze the problem in more detail, I created an empty project, deployed the Python 3.6.2 environment, installed django and requests in it

The text of the log when entering the Restart Language Server command
[Info  - 00:29:38] Pylance language server 2021.8.3 (pyright fa4194fd) starting
[Info  - 00:29:38] Server root directory: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist
[Info  - 00:29:38] No configuration file found.
[Info  - 00:29:38] No pyproject.toml file found.
[Info  - 00:29:38] Setting pythonPath for service "test-vs": "d:\Projects\Python\test-vs\env\Scripts\python.exe"
[Warn  - 00:29:38] stubPath d:\Projects\Python\test-vs\typings is not a valid directory.
[Info  - 00:29:38] Assuming Python version 3.9
[Info  - 00:29:38] Assuming Python platform Windows
Search paths for d:\Projects\Python\test-vs
  c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib
  d:\Projects\Python\test-vs
  d:\Projects\Python\test-vs\env36\Lib\site-packages
  d:\Projects\Python\test-vs\typings
  c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stubs\...
  c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs
  c:\Python39\DLLs
  c:\Python39\Lib
  c:\Python39
  d:\Projects\Python\test-vs\env
  d:\Projects\Python\test-vs\env\Lib\site-packages
[Info  - 00:29:39] Searching for source files
[Info  - 00:29:39] Auto-excluding d:\Projects\Python\test-vs\env
[Info  - 00:29:39] Auto-excluding d:\Projects\Python\test-vs\env36
[Info  - 00:29:39] Found 1 source file
[FG] parsing: d:\Projects\Python\test-vs\main.py (17ms)
[FG] parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 2ms] (75ms)
[FG] binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\builtins.pyi (35ms)
[FG] binding: d:\Projects\Python\test-vs\main.py (0ms)
[Info  - 00:29:39] Background analysis(1) root directory: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist
[Info  - 00:29:39] Background analysis(1) started
Background analysis message: setConfigOptions
Background analysis message: setImportResolver
Background analysis message: ensurePartialStubPackages
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: setFileOpened
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[Info  - 00:29:39] Indexer background runner(2) root directory: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist
[Info  - 00:29:39] Indexing(2) started
[IDX(2)] index libraries d:\Projects\Python\test-vs ...
[IDX(2)]   read stdlib indices (90ms)
Background analysis message: analyze
[BG(1)] analyzing: d:\Projects\Python\test-vs\main.py ...
[BG(1)]   parsing: d:\Projects\Python\test-vs\main.py (15ms)
[BG(1)]   parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 3ms] (78ms)
[BG(1)]   binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\builtins.pyi (32ms)
[BG(1)]   binding: d:\Projects\Python\test-vs\main.py (0ms)
[BG(1)]   checking: d:\Projects\Python\test-vs\main.py ...
[BG(1)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\typing.pyi [fs read 2ms] (34ms)
[BG(1)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\typing.pyi (11ms)
[BG(1)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi [fs read 1ms] (8ms)
[BG(1)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi (1ms)
[BG(1)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 1ms] (2ms)
[BG(1)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\typing_extensions.pyi (2ms)
[IDX(2)]   scan packages [found 48 modules over 1 exec env] (249ms)
[BG(1)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\contrib\auth\views.pyi [fs read 0ms] (15ms)
[BG(1)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\contrib\auth\views.pyi (2ms)
[IDX(2)]   index execution environment d:\Projects\Python\test-vs ...
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\asgiref\__init__.py [fs read 1ms] (19ms)
[BG(1)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\views\generic\base.pyi [fs read 0ms] (7ms)
[BG(1)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\views\generic\base.pyi (1ms)
[BG(1)]   checking: d:\Projects\Python\test-vs\main.py (108ms)
[BG(1)] analyzing: d:\Projects\Python\test-vs\main.py (236ms)
Background analysis message: resumeAnalysis
[BG(1)] indexing: d:\Projects\Python\test-vs\main.py [found 0] (0ms)
Indexing Done: d:\Projects\Python\test-vs\main.py
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 2ms] (57ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\builtins.pyi (9ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\asgiref\__init__.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\asgiref\__init__.py [found 1] (0ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\charset_normalizer\__init__.py [fs read 2ms] (7ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\charset_normalizer\__init__.py (1ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env36\Lib\site-packages\charset_normalizer\__init__.py [found 1] (0ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\apps\__init__.pyi [fs read 0ms] (1ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\apps\__init__.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\apps\__init__.pyi ...
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\apps\config.pyi [fs read 0ms] (4ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\apps\config.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\apps\registry.pyi [fs read 0ms] (1ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\apps\registry.pyi (1ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\apps\__init__.pyi [found 4] (7ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\conf\__init__.pyi [fs read 2ms] (4ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\conf\__init__.pyi (1ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\conf\__init__.pyi [found 8] (0ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\contrib\__init__.pyi [fs read 0ms] (0ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\contrib\__init__.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\contrib\__init__.pyi [found 0] (0ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\core\__init__.pyi [fs read 0ms] (0ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\core\__init__.pyi (1ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\core\__init__.pyi [found 0] (0ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\db\__init__.pyi [fs read 0ms] (1ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\db\__init__.pyi (1ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\db\__init__.pyi ...
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\db\utils.pyi [fs read 0ms] (7ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\db\utils.pyi (1ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\db\__init__.pyi [found 19] (8ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\dispatch\__init__.pyi [fs read 0ms] (1ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\dispatch\__init__.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\dispatch\__init__.pyi ...
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\dispatch\dispatcher.pyi [fs read 1ms] (1ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\dispatch\dispatcher.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\dispatch\__init__.pyi [found 2] (2ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\__init__.pyi [fs read 0ms] (10ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\__init__.pyi (1ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\__init__.pyi ...
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\core\exceptions.pyi [fs read 0ms] (3ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\core\exceptions.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\boundfield.pyi [fs read 0ms] (6ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\boundfield.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\fields.pyi [fs read 0ms] (5ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\fields.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\forms.pyi [fs read 1ms] (3ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\forms.pyi (1ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\formsets.pyi [fs read 0ms] (2ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\formsets.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\models.pyi [fs read 1ms] (15ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\models.pyi (1ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\widgets.pyi [fs read 0ms] (2ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\widgets.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\forms\__init__.pyi [found 85] (40ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\__init__.pyi [fs read 0ms] (1ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\__init__.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\__init__.pyi ...
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\cookie.pyi [fs read 0ms] (1ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\cookie.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\request.pyi [fs read 0ms] (9ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\request.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\response.pyi [fs read 0ms] (7ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\response.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\http\__init__.pyi [found 24] (18ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\middleware\__init__.pyi [fs read 1ms] (1ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\middleware\__init__.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\middleware\__init__.pyi [found 0] (0ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\shortcuts.pyi [fs read 0ms] (3ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\shortcuts.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\shortcuts.pyi [found 10] (1ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\template\__init__.pyi [fs read 0ms] (0ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\template\__init__.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\template\__init__.pyi ...

[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\test\client.pyi [fs read 0ms] (2ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\test\client.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\test\testcases.pyi [fs read 0ms] (3ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\test\testcases.pyi (0ms)
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\test\utils.pyi [fs read 0ms] (5ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\test\utils.pyi (1ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\test\__init__.pyi [found 18] (12ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\urls\__init__.pyi [fs read 0ms] (1ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\urls\__init__.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\urls\__init__.pyi ...

[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\views\generic\base.pyi [fs read 0ms] (2ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\views\generic\base.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\views\__init__.pyi [found 1] (3ms)
[IDX(2)]     parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\__init__.pyi [fs read 0ms] (0ms)
[IDX(2)]     binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\__init__.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\__init__.pyi ...
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\utils\version.pyi [fs read 0ms] (1ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\utils\version.pyi (0ms)
[IDX(2)]     indexing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\bundled\stubs\django\__init__.pyi [found 4] (1ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\idna\__init__.py [fs read 0ms] (1ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\idna\__init__.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env36\Lib\site-packages\idna\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\idna\core.py [fs read 0ms] (9ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\idna\core.py (1ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\idna\intranges.py [fs read 0ms] (1ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\idna\intranges.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env36\Lib\site-packages\idna\__init__.py [found 23] (11ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\pip\__init__.py [fs read 0ms] (0ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\pip\__init__.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\pip\__init__.py [found 2] (0ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\pkg_resources\__init__.py [fs read 0ms] (35ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\pkg_resources\__init__.py (4ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\pkg_resources\__init__.py ...
[IDX(2)]       parsing: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\pkgutil.pyi [fs read 0ms] (5ms)
[IDX(2)]       binding: c:\Users\alx\.vscode\extensions\ms-python.vscode-pylance-2021.8.3\dist\typeshed-fallback\stdlib\pkgutil.pyi (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\pkg_resources\__init__.py [found 71] (7ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\pytz\__init__.py [fs read 0ms] (17ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\pytz\__init__.py (3ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\pytz\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\pytz\exceptions.py [fs read 0ms] (0ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\pytz\exceptions.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\pytz\tzinfo.py [fs read 1ms] (4ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\pytz\tzinfo.py (1ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\pytz\__init__.py [found 14] (5ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\setuptools\__init__.py [fs read 0ms] (5ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\setuptools\__init__.py (1ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\setuptools\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\setuptools\_deprecation_warning.py [fs read 0ms] (0ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\setuptools\_deprecation_warning.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\setuptools\extension.py [fs read 0ms] (2ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\setuptools\extension.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\setuptools\dist.py [fs read 0ms] (26ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\setuptools\dist.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\setuptools\depends.py [fs read 1ms] (3ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\setuptools\depends.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\setuptools\__init__.py [found 8] (32ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\sqlparse\__init__.py [fs read 0ms] (1ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\sqlparse\__init__.py (1ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\sqlparse\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\sqlparse\__init__.py [fs read 0ms] (0ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\sqlparse\__init__.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\sqlparse\__init__.py [found 6] (0ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\__init__.py [fs read 0ms] (1ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\__init__.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\connectionpool.py [fs read 0ms] (3ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\connectionpool.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\filepost.py [fs read 1ms] (1ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\filepost.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\poolmanager.py [fs read 0ms] (2ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\poolmanager.py (1ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\response.py [fs read 0ms] (4ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\response.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\util\request.py [fs read 0ms] (1ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\util\request.py (1ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\util\retry.py [fs read 0ms] (1ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\util\retry.py (1ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\util\timeout.py [fs read 0ms] (0ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\util\timeout.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\util\url.py [fs read 1ms] (3ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\util\url.py (1ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env36\Lib\site-packages\urllib3\__init__.py [found 14] (20ms)
[IDX(2)]     parsing: c:\Python39\Lib\xml\__init__.py [fs read 0ms] (0ms)
[IDX(2)]     binding: c:\Python39\Lib\xml\__init__.py (0ms)
[IDX(2)]     indexing: c:\Python39\Lib\xml\__init__.py [found 0] (0ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\astroid\__init__.py [fs read 0ms] (12ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\astroid\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\astroid\exceptions.py [fs read 0ms] (5ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\astroid\exceptions.py (1ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\astroid\__init__.py (7ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\astroid\__init__.py [found 0] (0ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\__init__.py [fs read 0ms] (1ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\__init__.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\_version.py [fs read 0ms] (0ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\_version.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\api.py [fs read 0ms] (12ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\api.py (1ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\place.py [fs read 0ms] (3ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\place.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\settings.py [fs read 0ms] (7ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\settings.py (1ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\isort\__init__.py [found 17] (25ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\lazy_object_proxy\__init__.py [fs read 0ms] (3ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\lazy_object_proxy\__init__.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\lazy_object_proxy\__init__.py [found 0] (0ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\platformdirs\__init__.py [fs read 0ms] (3ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\platformdirs\__init__.py (1ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\platformdirs\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\platformdirs\api.py [fs read 0ms] (1ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\platformdirs\api.py (0ms)
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\platformdirs\version.py [fs read 0ms] (0ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\platformdirs\version.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\platformdirs\__init__.py [found 22] (1ms)
[IDX(2)]     parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\pylint\__init__.py [fs read 0ms] (1ms)
[IDX(2)]     binding: d:\Projects\Python\test-vs\env\Lib\site-packages\pylint\__init__.py (1ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\pylint\__init__.py ...
[IDX(2)]       parsing: d:\Projects\Python\test-vs\env\Lib\site-packages\pylint\__pkginfo__.py [fs read 0ms] (0ms)
[IDX(2)]       binding: d:\Projects\Python\test-vs\env\Lib\site-packages\pylint\__pkginfo__.py (0ms)
[IDX(2)]     indexing: d:\Projects\Python\test-vs\env\Lib\site-packages\pylint\__init__.py [found 3] (0ms)
[IDX(2)]   index execution environment d:\Projects\Python\test-vs [found 8328 in 445 files] (444ms)
[IDX(2)] index libraries d:\Projects\Python\test-vs [found 8328 in 1 exec envs] (784ms)
[Info  - 00:29:40] Indexer done(2). indexed 445 files

When entering the entry point into the module, it offers import, then there is no further.

Now, "python.analysis.indexing" became a real option. Set "python.analysis.indexing": true to enable indexing which will improve auto-import experience.
Also, new hidden option "python.analysis.packageIndexDepths" is added which can be used as below to control how much get indexed.

"python.analysis.packageIndexDepths": [['sklearn', 2],['matplotlib', 2]],

by default, only the first level module of third party libraries will be indexed, but now, you can use ["package name", module levels to be scanned] to control that.
if you put "" (empty string) to package name, then it will affect all packages.
for your example, ["django", 10] or ["passlib", 10] will make up to 10 level sub modules to be picked up.
...
that being said, to reduce amount of items in the completion, we do not suggest empty module such as __ init __.py with no content in it. so django.contrib still won't be suggested. but LoginView will be.
thank you
fix will be in the next release 2022.1.2

This issue has been fixed in version 2022.1.3, which we've just released. You can find the changelog here:  CHANGELOG.md


cargo fmt does not do anything in tokio repo

I found this problem locally and wondered how tokio was checking formatting in CI.
As you can see they are calling rustfmt directly:
https://github.com/tokio-rs/tokio/blob/master/ci/azure-rustfmt.yml#L17
This comment links to a cargo issue:
https://github.com/rust-lang/cargo/issues/7732
However, this cargo issue is closed and it's not clear how it's related.

I can't really speak to the tokio nor cargo aspects, so you'd have to check in those respective repos for more details.
cargo fmt is a wrapper around the rustfmt binary to make it easier to run rustfmt across entire projects/workspaces. cargo fmt leverages the cargo_metadata crate which at a high level executes the cargo metadata --format-version 1 ... commands and deserializes the results. cargo fmt then uses the contents of that cargo metadata to structure and issue the corresponding rustfmt commands.
If, for whatever reason, the cargo metadata cannot be determined within the tokio workspace then that would be problematic for cargo fmt.
You could try running cargo fmt with the --verbose flag to get additional output, including the rustfmt commands it would issue. However, I don't get the sense the tokio challenges are related to rustfmt, though please let us know if there does turn out to be an issue on the rustfmt side.

I see this in the https://github.com/rust-analyzer/rust-analyzer/ repository.
$ cargo fmt --verbose                                                                                 ✔
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_arena/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_assists/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_cfg/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_db/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_flycheck/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_fmt/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_hir/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_hir_def/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_hir_expand/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_hir_ty/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_ide/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_ide_db/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_mbe/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_parser/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_proc_macro/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_proc_macro_srv/src/lib.rs"
[bin (2018)] "~/Projects/rust-analyzer/crates/ra_proc_macro_srv/src/main.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_prof/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_project_model/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_syntax/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_text_edit/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/ra_tt/src/lib.rs"
[custom-build (2018)] "~/Projects/rust-analyzer/crates/rust-analyzer/build.rs"
[bin (2018)] "~/Projects/rust-analyzer/crates/rust-analyzer/src/bin/main.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/rust-analyzer/src/lib.rs"
[test (2018)] "~/Projects/rust-analyzer/crates/rust-analyzer/tests/heavy_tests/main.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/stdx/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/crates/test_utils/src/lib.rs"
[lib (2018)] "~/Projects/rust-analyzer/xtask/src/lib.rs"
[bin (2018)] "~/Projects/rust-analyzer/xtask/src/main.rs"
[test (2018)] "~/Projects/rust-analyzer/xtask/tests/tidy-tests/main.rs"

It looks like cargo fmt only finds files called lib.rs and main.rs.

It looks like cargo fmt only finds files called lib.rs, main.rs and build.rs. Seen on both nightly and stable.

That is by design. cargo fmt will pass the main entry point file for each target for each package within the workspace, and rustfmt then formats those recursively.

Outside of the linked issue, tokio uses macros to define modules, which rustfmt cannot recognize (https://github.com/tokio-rs/tokio/blob/67c4cc03919a58076c139f0930f28c3c41dad1e5/tokio/src/lib.rs#L326-L348).
I don't think that just adding support for modules defined inside macro calls fixes the issue in tokio crate, though we should add it anyway.

Somewhat related to #4034 since it's another case where we don't perform module resolution because of macros.


ESP8285 - ESP-M3

Hello has anyone chorus rf with ESP8285 - ESP-M3??? Which FW did you flash in the wifi? An which program for flash did you use ?

Mine ESP8285 wifi adapter came with FW without web interface.
I flashed with FW from here:
https://www.esp8266.com/viewtopic.php?f=5&t=7124
Flash Download Tool: https://www.espressif.com/en/support/download/other-tools
There is no Serial Split Timeout option in this firmware version, but it works good for me.
I couldn't find FW version that comes with adapter from Banggood :)

Hi, this version of wifi adapter is better than DT-06 Wireless WiFi?
Thanks


Removing the outdated video.

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @bcblackmer,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX