[ERROR] xrdp_mm_chansrv_connect: error in trans_connect chan

I am using Arch Linux with xrdp 0.9.19-2 and xorgxrdp-nvidia 0.2.18-1 on the server side
I am using an iPad with the MS RDP client (this client works perfectly fine with Windows and xrdp on Ubuntu)
When I try to log in through RDP using my credentials, the RDP client hangs for a moment before exiting the session.
I have attached log files that may be useful for diagnosing this issue.
xrdp.log
[20220426-19:47:38] [INFO ] address [<IP_ADDRESS>] port [3389] mode 1
[20220426-19:47:38] [INFO ] listening to port 3389 on <IP_ADDRESS>
[20220426-19:47:38] [INFO ] xrdp_listen_pp done
[20220426-19:47:40] [INFO ] starting xrdp with pid 1804
[20220426-19:47:40] [INFO ] address [<IP_ADDRESS>] port [3389] mode 1
[20220426-19:47:40] [INFO ] listening to port 3389 on <IP_ADDRESS>
[20220426-19:47:40] [INFO ] xrdp_listen_pp done
[20220426-19:47:45] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<IP_ADDRESS> port 49655
[20220426-19:47:45] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20220426-19:47:45] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20220426-19:47:45] [INFO ] Security protocol: configured [SSL|RDP], requested [SSL|HYBRID|HYBRID_EX|RDP], selected [SSL]
[20220426-19:47:45] [INFO ] Connected client computer name: Book
[20220426-19:47:45] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20220426-19:47:45] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20220426-19:47:45] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000409]
[20220426-19:47:45] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [us] options []
[20220426-19:47:45] [INFO ] TLS connection established from ::ffff:<IP_ADDRESS> port 49655: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
[20220426-19:47:45] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20220426-19:47:45] [INFO ] xrdp_process_offscreen_bmpcache: support level 0 cache size 0 MB cache entries 0
[20220426-19:47:45] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20220426-19:47:45] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20220426-19:47:45] [WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file
[20220426-19:47:45] [INFO ] connecting to sesman on <IP_ADDRESS>:3350
[20220426-19:47:45] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20220426-19:47:45] [INFO ] sesman connect ok
[20220426-19:47:45] [INFO ] sending login info to session manager. Please wait...
[20220426-19:47:45] [INFO ] xrdp_wm_log_msg: login successful for user luna on display 10
[20220426-19:47:45] [INFO ] login successful for user luna on display 10
[20220426-19:47:45] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20220426-19:47:45] [INFO ] started connecting
[20220426-19:47:45] [INFO ] lib_mod_connect: connecting via UNIX socket
[20220426-19:47:45] [INFO ] lib_mod_log_peer: xrdp_pid=1805 connected to X11rdp_pid=1808 X11rdp_uid=1000 X11rdp_gid=1000 client_ip=::ffff:<IP_ADDRESS> client_port=49655
[20220426-19:47:45] [INFO ] connected ok
[20220426-19:47:49] [WARN ] xrdp_mm_chansrv_connect: connect failed trying again...
[20220426-19:47:53] [WARN ] xrdp_mm_chansrv_connect: connect failed trying again...
[20220426-19:47:57] [WARN ] xrdp_mm_chansrv_connect: connect failed trying again...
[20220426-19:48:01] [WARN ] xrdp_mm_chansrv_connect: connect failed trying again...
[20220426-19:48:01] [ERROR] xrdp_mm_chansrv_connect: error in trans_connect chan

xrdp-sesman.log
[20220426-19:47:38] [INFO ] starting xrdp-sesman with pid 1802
[20220426-19:47:45] [INFO ] Socket 12: AF_INET6 connection received from ::1 port 33630
[20220426-19:47:45] [INFO ] Terminal Server Users group is disabled, allowing authentication
[20220426-19:47:45] [INFO ] ++ created session (access granted): username luna, ip ::ffff:<IP_ADDRESS>:49655 - socket: 12
[20220426-19:47:45] [INFO ] starting Xorg session...
[20220426-19:47:45] [INFO ] Starting session: session_pid 1806, display :10.0, width 1552, height 1084, bpp 24, client ip ::ffff:<IP_ADDRESS>:49655 - socket: 12, user name luna
[20220426-19:47:45] [INFO ] [session start] (display 10): calling auth_start_session from pid 1806
[20220426-19:47:45] [ERROR] sesman_data_in: scp_process_msg failed
[20220426-19:47:45] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[20220426-19:47:45] [INFO ] Starting X server on display 10: /usr/lib/Xorg :10 -auth .Xauthority -config xrdp/xorg_nvidia.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20220426-19:47:45] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20220426-19:47:45] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20220426-19:47:45] [INFO ] Session started successfully for user luna on display 10
[20220426-19:47:45] [INFO ] Starting the xrdp channel server for display 10
[20220426-19:47:45] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20220426-19:47:45] [INFO ] Session in progress on display 10, waiting until the window manager (pid 1807) exits to end the session
[20220426-19:47:45] [INFO ] Starting the default window manager on display 10: /etc/xrdp/startwm.sh
[20220426-19:47:45] [WARN ] Window manager (pid 1807, display 10) exited with non-zero exit code 127 and signal 0. This could indicate a window manager config problem
[20220426-19:47:45] [WARN ] Window manager (pid 1807, display 10) exited quickly (0 secs). This could indicate a window manager config problem
[20220426-19:47:45] [INFO ] Calling auth_stop_session and auth_end from pid 1806
[20220426-19:47:45] [INFO ] Terminating X server (pid 1808) on display 10
[20220426-19:47:45] [INFO ] Terminating the xrdp channel server (pid 1813) on display 10
[20220426-19:47:45] [INFO ] X server on display 10 (pid 1808) returned exit code 0 and signal number 0
[20220426-19:47:45] [INFO ] xrdp channel server for display 10 (pid 1813) exit code 0 and signal number 0
[20220426-19:47:45] [INFO ] cleanup_sockets:
[20220426-19:47:45] [INFO ] Process 1806 has exited
[20220426-19:47:45] [INFO ] ++ terminated session:  username luna, display :10.0, session_pid 1806, ip ::ffff:<IP_ADDRESS>:49655 - socket: 12

I'm guessing a bit here, but looking at the Manjaro startup files, this message could be caused by a session manager not being found, and xterm not being installed:-
[20220426-19:47:45] [WARN ] Window manager (pid 1807, display 10) exited with non-zero exit code 127 and signal 0. This could indicate a window manager config problem

A couple of questions for you, @Orange-Murker :-

What desktop are you trying to run?
What do you get for ls -l /etc/X11/xinit/xinitrc.d/?

I am trying to run GNOME
I get:
total 2
-rwxr-xr-x 1 root root 318 Apr  1 19:02 40-libcanberra-gtk-module.sh
-rwxr-xr-x 1 root root 538 Mar 17 22:40 50-systemd-user.sh
-rwxr-xr-x 1 root root 243 Jan 15 21:01 80xapp-gtk3-module.sh

This issue may be related to GNOME specifically.
The RDP session works as expected with KDE Plasma after resolving the Black Screen problem by removing --exit-with-session in ~/xinitrc as per the ArchWiki.

This is the first mention I've seen of ~/xinitrc.
A couple of questions for you:-

You do mean ~/.xinitrc don't you?
What's in yours
Can you provide a link to the Arch Wiki page you mention above? I know some Arch basics, but that's it. I can't find the information you mention.

Thanks.

First of all, sorry for the late reply.

1. You do mean `~/.xinitrc` don't you?

I did mean ~/.xinitrc, sorry for this

2. What's in yours

My ~/.xinitrc file looks like this:
#!/bin/bash
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

DEFAULT_SESSION=startplasma-x11

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then
    xrdb -merge "$userresources"
fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
    for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
        [ -x "$f" ] && . "$f"
    done
    unset f
fi

get_session(){
    local dbus_args=(--sh-syntax --exit-with-session)
    case $1 in
        awesome) dbus_args+=(awesome) ;;
        bspwm) dbus_args+=(bspwm-session) ;;
        budgie) dbus_args+=(budgie-desktop) ;;
        cinnamon) dbus_args+=(cinnamon-session) ;;
        deepin) dbus_args+=(startdde) ;;
        enlightenment) dbus_args+=(enlightenment_start) ;;
        fluxbox) dbus_args+=(startfluxbox) ;;
        gnome) dbus_args+=(gnome-session) ;;
        i3|i3wm) dbus_args+=(i3 --shmlog-size 0) ;;
        jwm) dbus_args+=(jwm) ;;
        kde) dbus_args+=(startplasma-x11) ;;
        lxde) dbus_args+=(startlxde) ;;
        lxqt) dbus_args+=(lxqt-session) ;;
        mate) dbus_args+=(mate-session) ;;
        xfce) dbus_args+=(xfce4-session) ;;
        openbox) dbus_args+=(openbox-session) ;;
        *) dbus_args+=($DEFAULT_SESSION) ;;
    esac

    echo "dbus-launch ${dbus_args[*]}"
}

exec $(get_session "$1")

3. Can you provide a link to the Arch Wiki page you mention above? I know some Arch basics, but that's it. I can't find the information you mention.

This is the Arch Wiki page: https://wiki.archlinux.org/title/Xrdp
You can find the fix I am referring to in Troubleshooting -> Black screen

I'm pretty sure Arch starts a dbus session itself with pam_systemd.so, so GNOME will certainly find the environment confusing when it tries to start, given the file above.
Let's stat by getting a log out of this. Can you add the following lines to the start of your ~/.xinitrc file, under the # Executed by startx  line:-
if [ -n "$XRDP_SESSION" ]; then
    exec >~/xinitrc.xrdp.log 2>&1
    env | sort
    set -x
fi

When you try to log in with XRDP this should now give you a file xinitrc.xrdp.log with some more useful information in it. If I've got those lines right, of course!

The specified file is not being created after I try to connect:
> cat ~/xinitrc.xrdp.log
cat: /home/user/xinitrc.xrdp.log: No such file or directory

Is /etc/xrdp/startwm.sh executable?
What happens when you run this command as user (make sure you don't leave the space out)? Do you get a log file then?
DISPLAY= /etc/xrdp/startwm.sh

same problem here....
but in my /etc/xrdp/startwm.sh i have :
`cat /etc/xrdp/startwm.sh
#!/bin/sh
xrdp X session start script (c) 2015, 2017, 2021 mirabilos
published under The MirOS Licence
Rely on /etc/pam.d/xrdp-sesman using pam_env to load both
/etc/environment and /etc/default/locale to initialise the
locale and the user environment properly.
if test -r /etc/profile; then
. /etc/profile
fi
test -x /etc/X11/Xsession && exec /etc/X11/Xsession
exec /bin/sh /etc/X11/Xsession`
And if i take a look to /etc/X11/Xsession i doesn't have it but i have Xsession.d at the same location...

@Ludo-code - this is an Arch issue I believe. Given it's stale, I'm going to close it.
rPI 4 incompatibilities with xrdp are well documented elsewhere. Try reading #2129 and #2160 for some background.
TLDR; Set up a different user from pi and use that for XRDP logins.


[skipruntime-ts] Take control over reducer instantiation to avoid capturing/side effects

It came up in conversation today that reducers ought to be instantiated under skipruntime control like mappers, to prevent accidental capture of mutable state or other side effects in reducers. (users may be particularly likely to capture state there, instead of implementing the purely-functional fold using the accumulator arguments) So, this PR does just that.
The main interesting bit is what to do about the two variable-sized parameter lists (i.e. params to the mapper constructor and the reducer constructor).  The obvious thing to do is to have mapReduce take two explicit arrays which default to empty
(mapper: new(...mapperParams)=>Mapper<...>, reducer: new(...reducerParams)=>Reducer<...>, mapperParams: MapperParams = [], reducerParams: ReducerParams = []) but that (rightly) doesn't typecheck, since it would allow to elide params even when MapperParams/ReducerParams are non-empty.  So, we can use overloads to only allow eliding those parameters when the respective constructors take no arguments. But, that's a bit clunky, and leads to the same problem in map/createLazyCollection if we also take array arguments there for consistency's sake.
Long-winded way of saying: I decided to just curry mapReduce so that it can splat out arguments to its mapper and reducer separately.  Seems a nice clean interface to me, but open to other suggestions!

Should we just have a reduce function rather than mapReduce?
In the longer-term we can optimize such sequences: map followed by reduce, slices followed by map, etc.

Should we just have a reduce function rather than mapReduce?

I have argued for that in the past as it makes for nicer user code.  But doing so directly comes with a real perf cost, materializing a lot more intermediate collections, so was rejected.  May be worth revisiting and doing some optimizations like you suggest for such sequences of operations!

Lots of offline conversation atm w/ Josh/Lucas/Daniel about adding an abstraction layer between the TS APIs and the actual skstore computation graph, some kind of builder-pattern operating over a graph IR.
No unanimous conclusions, but to summarize:
(1) fusing operations like this and separating our API design from implementation is a nice medium/long term thing to work on which would enable all kinds of cool things
(2) it's probably not worth the effort in the immediate term, there are lots of complexities particularly around dynamic changes to the graph and conditional operations in mappers
(3) we should probably just expose reduce now, position mapReduce as a special case with better perf, and not worry too much about the extra materializations


Check GnuPG signature of CoreOS image

Verify GnuPG signature of downloaded CoreOS image. systemd-nspawn/machinectl doesn't have a functionality of checking downloaded images by GPG signatures. We need to download the image and validate it by ourselves and then import it by machinectl.
Also introduce a command line option --image-gpg-verify for kube-spawn create. This option is set to true by default. Any user who wants to disable gpg verification can set this option to false: --image-gpg-verify=false.
This PR is based on https://github.com/kinvolk/kube-spawn/pull/131 by @nhlfr. First I rebased it on top of master, which needed a bit of work, as the project structure has changed a lot recently. After that I decided to simplify the openpgp logic. Please let me know if anything is wrong. A couple of test results looked good to me.
Supersedes https://github.com/kinvolk/kube-spawn/pull/131
Fixes https://github.com/kinvolk/kube-spawn/issues/107

But most importantly: like this, kube-spawn overwrites my $HOME/.gnupg with a new keyring, since it's run with sudo -E (i.e. $HOME points to /home/user).
So since I haven't looked at the code carefully before testing, this just wiped out my user's GPG keyring and setup and I need to recover it from backup :(

Whoa, sorry about that. :(  We need to be able to avoid this case.


module not found in landuse change script

This PR https://github.com/ACCESS-NRI/access-esm1.5-configs/pull/66 used a work-around to access the python conda environment that is running payu.
This doesn't work because it's not opening a shell, and so doesn't have the module infra loaded, and throws this error:
./scripts/update_landuse_driver.sh: line 4: module: command not found
Traceback (most recent call last):
  File "/g/data/vk83/apps/payu/1.1.5/lib/python3.10/site-packages/payu/fsops.py", line 320, in _run_script
    subprocess.check_call(shlex.split(script_cmd))
  File "/g/data/vk83/apps/payu/1.1.5/lib/python3.10/subprocess.py", line 364, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/g/data/vk83/apps/payu/1.1.5/lib/python3.10/subprocess.py", line 345, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/g/data/vk83/apps/payu/1.1.5/lib/python3.10/subprocess.py", line 966, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/g/data/vk83/apps/payu/1.1.5/lib/python3.10/subprocess.py", line 1842, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: './scripts/update_landuse_driver.sh'

One possible solution is to force the bash interpreter in the update landuse driver script to be a login shell.
If that doesn't work we can hard-code a path to a released python environment and flag to fix later.


Option to remove/toggle links (TMDb/Trankt/IMDb/YouTube), buttons, and version indicator

Would love to have the ootion to hide/remove/toggle these UI items. Primarily for use with Homepage dashboard as iFrame widget.

Please test :dev

Added in v1.5.1


fix a small bug

You call widget.onTap when it's null.
if (widget.onTap == null) {
  widget.onTap(snapshot.data[index]);
}

I think you want call it when it's NOT null.
widget.onTap?.call(snapshot.data[index]);

The fix will be live with release of Searchfield^0.3.2


The unbound root.min.hints is outdated

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
root.hints file (not sure why it is shipped with core) needs updating.

https://gitlab.isc.org/isc-projects/bind9/-/issues/4101
https://www.lacnic.net/6868/1/lacnic/lacnic-asigna-recursos-de-numeracion-al-servidor-raiz-de-usc_isi

Forgive me for refetching the file to check the validity of the submission... I've committed https://github.com/opnsense/core/commit/f1ae49b803a since the diff is smaller than what you have here and the upstream file checksum then matches


Discover language doesn't work properly

Description
When setting Discover Language to English, it still shows series & films from other languages
Version
1.3.0
Steps to Reproduce
Settings | General | Discover Language | English.
Screenshots

Logs
No response
Platform
desktop
Device
Any
Operating System
Any
Browser
Any
Additional Context
No response
Code of Conduct

[X] I agree to follow Overseerr's Code of Conduct

Checking in to see if this is getting any traction. Thanks.

Wb if you set discover country

It is already set as well

I too am seeing this.  With Discovery Language set to English I get search results for what looks like any language.
To qualify this a bit more:

When I first login, everything displayed on the "home screen" looks to be in English.
When selecting Movies or Series from the navigation bar on the left everything displayed on those screens also look to be in English.
When entering text into the search bar, the Search Results are not all English.  They seem to be in any language.

I am running Jellyseerr 1.5.0 on Docker CE (on OpenMediaVault 6).

That setting does exactly what it's said "discover language" as in change the language for the discover page not search. That's why

Thanks for the explanation. I obviously did not understand that there was a distinction between Discovery and Search.
Obvious next question.  How then do I filter on the language when doing a search?

Obvious next question. How then do I filter on the language when doing a search?

Filters on search is pretty limited as of now. In a way not there even because the only "filters" are like adding year Batman:2022 or imdb:xxxxx or tmdb:xxxxx

Ok.  Thanks for your help.


Allow using vesin in ASE calculator

The ASE calculator is annoying for very simple potentials (I'm playing with a Morse potential) because the NL becomes slow for dense systems.
EDIT: the speed-up is crazy
Contributor (creator of pull-request) checklist

[ ] Tests updated (for new features and bugfixes)?
[ ] Documentation updated (for new features)?
[ ] Issue referenced (for PRs that solve an issue)?

Reviewer checklist

[ ] CHANGELOG updated with public API or any other important changes?

📚 Download documentation preview for this pull-request

I added it to the docstring, but I didn't find a good place to add it to the ASE tutorial, simply because it doesn't use a NL :)

Good point for the tutorial 😄


Use global state context instead of drilling down props.

Before working on adding a hook for listening to and updating CODAP state, I thought it would be useful to also update the way we manage state so that we don't have to drill down props as much and can just create functions where they are needed.

Yes! Thank you for doing this. I was thinking the same thing when we started work on it.

Skipping this review since @eireland already reviewed it.


[FLINK-2784] Remove deprecated configuration keys and updated documentation

+1 looks good to merge!

I'll merge this one too.


JavaScript IntelliSense Problem

Windows 7 / VS Code 0.10.6
A simple JavaScript project folder with two files:
crt.js file is used as the source of intellisense function.
var foo = {};
foo.Version = '1.0';

var bar = {
  Version: '1.0';
}

main.js file use the variables defined in crt.js file:
foo.(no suggestion shows here)
bar.(shows Version as suggestion)

Can we have the foo show suggestions as bar?
Andrew

:+1:

As we now ship with project Salsa this should work


Fixed eventListeners not being removed

Hi,
I discovered a bug that occurred when you replace that animation data multiple times as well as switch between different sets of event listeners based on the animation.
On further investigation, I realised it was probably because events do not get deregistered before the animation object gets reassigned.
I refactored index.js to add two class methods registerEvent and deregisterEvent.
Then in the componentWillUpdate lifecycle method if the animation has changed It now deregisters events before destroying animation object and then creates new event listeners if applicable.
I also fleshed out your readme a bit regarding Props that the Lottie component can receive.
Let me know if you think I should do anything differently.
Cheers
J

Thanks for fixing this 👍

@chenqingspring
hey man,
changed from my fork to tag 2.3.0.
noticed it wasn't behaving as expected. noticed you made some more changes in 61fb09e. Not sure what undefined event listener issue you were trying to address. but the code doesn't work now.
let me know if you need some more help with this repo.

@jwfwessels  You're right, I made a bug after refactoring code.. I'll fixing it soon
Thanks for reminding me this!

@jwfwessels I released v0.2.4, can you help me check again?
And If you want give me a hand by adding a demo into storybook, that will be good :-)

Seems to be working again 🕺
Yeah, sure i'll add a storybook demo.

Awesome! Thanks :)


Agency Work

Statement of Need:
UGRC receives only partial legislative funding and, therefore, must actively pursue revenue-generating contract work to account for the annual budgetary shortfall for infrastructure, services and, most importantly, personnel costs. The advanced GIS and IT skills of UGRC staff are sometimes sought after by state agencies and other groups to provide business process-related technology solutions that cannot be fulfilled easily within their organization. This may include, but is not limited to, the creation of geospatial data and services; data extract, transform, and load (ETL) services; specialized GIS and spatial workflow tools and processes; computer vision services; and web map application development using both custom code and configurable GIS mapping platforms. UGRC must enter into contractual agreements with the requesting agency or organization to define deliverables, and for cost recovery for time spent on project work.
PI Benefit Hypthesis
lorem ipsum
PI Acceptance Criteria:
Continue with projects from the previous fiscal year, and acquire new revenue-generating work, to meet one quarter of the estimated annual UGRC budgetary need during each quarter.
Projects

UIC inventory
DEM flood risk mapping
OPCRH mapping
Enviro tech debt
WMRC
PLSS - monument review

this is represented by more specific objectives


On some special screen phones, there will be a transparent view at the top of webview_flutter

On some special screen phones, there will be a transparent view at the top of webview_flutter
Responding to click event point misalignment
This is the test video
test-vedio.zip
Rendering
1.Screenshot of the target phone

2.Photograph

Target phone parameters

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, v1.9.1+hotfix.6, on Microsoft Windows [Version 10.0.18362.418], locale zh-CN)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Android Studio (version 3.5)
[!] IntelliJ IDEA Ultimate Edition (version 2019.1)
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
[√] Connected device (1 available)

! Doctor found issues in 1 category.

this my code
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

class TestWebView extends StatelessWidget {
  static final String routeName = "TestWebView";

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      backgroundColor: Colors.red,
      appBar: AppBar(
        title: Text("test WebView"),
      ),
      body: Column(
        children: <Widget>[
          Container(
            child: Text("sss"),
            width: 100,
            color: Colors.white,
          ),
          Expanded(
              child: WebView(
            initialUrl: "https://www.baidu.com/",
            javascriptMode: JavascriptMode.unrestricted,
            navigationDelegate: (NavigationRequest navigation) {
              if (!navigation.url.startsWith("http")) {
                return NavigationDecision.prevent;
              }
              return NavigationDecision.navigate;
            },
          ))
        ],
      ),
    );
  }
}

This is caused because of how Xiaomi's pre-Android 9 phones handle the notch

I have the same problem in Xiaomi

The issue is not reproducible on the latest stable 2.2.3 and master 2.5.0-6.0.pre.29 with webview_flutter: ^2.0.10. This was tested on a POCO X3 NFC running Android 11.
@XHL-study @lvchenyang can you please confirm on the latest flutter versions if you are still experiencing this issue?
Thank you

flutter doctor -v
[✓] Flutter (Channel master, 2.5.0-6.0.pre.29, on macOS 11.5.1 20G80 darwin-arm, locale en-GH)
    • Flutter version 2.5.0-6.0.pre.29 at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6876c52b5b (8 hours ago), 2021-08-08 15:34:09 -0700
    • Engine revision c0e59bc7b6
    • Dart version 2.14.0 (build 2.14.0-383.0.dev)

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

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.2

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

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

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

[✓] Connected device (3 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android
      12 (API 31) (emulator)
    • iPhone 12 (mobile)          • F2592D43-5FE3-46BB-8A2B-A38BA468DCE9 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • Chrome (web)                • chrome                               • web-javascript • Google
      Chrome 92.0.4515.131

• No issues found!

[✓] Flutter (Channel stable, 2.2.3, on macOS 11.5.1 20G80 darwin-arm, locale en-GH)
    • Flutter version 2.2.3 at /Users/nexus/dev/sdks/flutter
    • Framework revision f4abaa0735 (5 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

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

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.2

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

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

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

[✓] Connected device (3 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android
      12 (API 31) (emulator)
    • iPhone 12 (mobile)          • F2592D43-5FE3-46BB-8A2B-A38BA468DCE9 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • Chrome (web)                • chrome                               • web-javascript • Google
      Chrome 92.0.4515.131

• No issues found!

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Project Rating

Looking at the warehouse interface shuold be posible to show some rating, maybe a stars based system.

+1 to this feature. The only current measure of any sort is the number of downloads which is pretty much meaningless. This would at least give us a mechanism to have some user-driven feedback.

I agree that it would be good to have some kind of public measure of popularity (particularly for search ordering - see #702), but I think we need to be very careful here.  We need to particularly think about the impact a poor rating might have on a package author.  Is the review fair and accurate?  What recourse do they have to respond?
Importantly, is a rating system going to dissuade newcomers from publishing their packages because of fear of public criticism?
My alternative idea is to mimic the star system provided by GitHub.  This would give each package some kind of popularity count, while also allowing package consumers to keep track of their favourite packages.  It also carries no 'negative' feedback mechanism, which is good for package authors :)

Good point about negative feedback. However, I'd argue that the number stars would be akin to download count and doesn't really provide any real benefit.
Thinking about this a little more, the problem with reviews is that they're subjective by nature, so accuracy will always be arguable. Perhaps rather than stars, we could have a well defined quality matrix that can be represented visually in a variety of ways. Simple items could be marked off, for example:
Does the project have:

Some form of CI setup (i.e. Travis-CI et al), although this one can be tricky for pull CI systems
Some form of static analysis
Unit tests

I'm not entirely sold on this yet, just thinking out loud really..

This could also be based on the fact that a bunch of other well-rated packages depends (via install_requires) on this particular package.

One thing to think about here is that in the past, PyPI did have a review and star rating system. Package authors got really upset about it and fought tooth and nail to get it removed (which it ultimately did get removed). That was before I was involved in the Python community at all, so I don't know specifics about why people were really against it.
I know that @jacobian was one of the vocal opponents to the system as it existed back then, I'm not entirely sure if the main problem with it was the implementation or the entire idea. He might be willing to come in here and talk a bit about it, but there was a fairly long thread on catalog-sig about it here. Talking to him briefly, he said:

my argument at the time -- which I still agree with -- is that ratings come down to a popularity contest, which is unfun

That's not to say "welp we tried it once, it's never going to happen again", just that if if we do it, we need to be very careful about how we do it so as not to encounter the same issues. We have to carefully balance features for people looking to use packages and features for people who are publishing packages, if we skew too far in either direction then we're likely to lose the other group of users, to the detriment of the ecosystem as a whole.

I'm still strongly against ratings/reviews, for the reasons I tried to articulate in that thread. Voting and popularity contests have no place in a neutral catalog.
To what I said in 2011, I'll add: the web in 2016 is, if anything, a far less "friendly" place than it was even five years ago. We've seen over and over again that system that allows commenting, rating, voting, and the like is rife for abuse. Yes, I'm talking about gmergte and the like. I beg of you: if Warehouse must contain some sort of voting, commenting, or other system, please consider the potential for abuse and consider flagging, moderation, anti-brigiading, and other defense mechanisms as pre-conditions to launch. For more on this line of thinking, please read Anil Dash's Against "Don't Read The Comments" -- which should be required reading for anyone building social features into websites these days.

Thinking further, I think the point I'm trying to make comes down to this:
There's nothing inherently "wrong" or "right" about commenting/voting/etc features. But slapping them onto a site without considering the social implications is wrong. If Warehouse is going to gain these features, please consider them and their ramifications very carefully.

I agree that having a user-driven rating system is likely something that wouldn't be well placed in Warehouse. What I do think would be valuable is some kind of a system such as django packages has, where a set of attributes are provided when browsing packages (I believe @ncoghlan had mentioned something akin to this some time ago as well). Things like commit history could be valuable during evaluation stages to help get a gauge on community activity. Other attributes such as existence of tests, automated builds, etc can help speak to level of effort around quality. These are all attributes that both are outside of the influence of the public (removing that "negative" feeling and popularity contest), but still speak to quality, which is something that's entirely missing from current PyPI.
@jacobian, @dstufft, @nlhkabu: Any objection to perhaps putting a list of attributes that we may want to highlight for a given project in an entirely automated fashion

(This rambles a lot, since better understanding this area is basically my day job, but it's also a huge field with more open questions than answers at this point in time. But my short answer is "Given PyPI's central role in the ecosystem, I think it's wrong to measure and report things beyond the core metrics that only PyPI can provide, without first validating that those measures are actually a useful predictor of pragmatic software quality")
Caveat: I'm heavily biased here, as I think upstream package repositories should act as neutral data sources for independent content curation efforts (e.g. by exposing download counts and links to version control systems and issue trackers, as PyPI does, and dependency counts, which PyPI doesn't do yet, but I hope will be able to do eventually as the Python packaging ecosystem's metadata management improves).
The main benefit of this approach specifically for the PyPI development team is that it makes it possible to run the repository with as light a hand as possible - community management is hard work, and time consuming enough when you're just wrangling tooling developers and trying to get basic security features right, let alone if you're actively trying to facilitate the formation of a full-blown direct-from-producer-to-consumer market system - any metric added that can be interpreted as a measure of "software quality" or "community quality" risks drawing the ire of developers of packages that score badly on that metric, and PyPI is unique in the ecosystem for owning the package publication experience (whereas it is relatively much easier for third parties to offer alternate download experiences, as with tools like peep and pipsi, or redistributors that use different formats, like Linux packaging, conda, PyPM, Canopy, etc). If a third party rates the contents of PyPI, then there's no software publisher/community publication platform conflict there - exposing your software to being both used and rated by others is a natural consequence of publishing it as open source. However, if PyPI rates it in some way (beyond reporting objective statistics like download rates), then that impacts the publisher/platform relationship in a way that third party rating systems don't.
The PyPI ToS thus aims to ensure that everyone running "pip install " is always legally entitled to download and deploy that component, but doesn't make any promises about whether or not that component is worth running (or even safe to run, as "pip install python-nation" illustrates).
The potential benefit for the broader Python ecosystem of PyPI staying out of the "software rating" game is that leaving these features out of the base platform facilitates the creation of a competitive market for content curation tools. The oldest of those are the Linux distros, albeit being rather out of favour with many developers due to the relatively high latency in delivering new feature releases to end users, together with cross-platform redistributors like ActiveState, Enthought and Continuum Analytics. In the enterprise sector, vendors like Black Duck offer advanced language independent content scanning capabilities, while newer providers like requires.io and versioneye.com offer more specifically security focused capabilities. DjangoPackages also stands out as an example of a subcommunity successfully coming together to address a shared interest in assessing packages within the context of a particular domain of development (Django-based web services) without reliance on a centralised vendor handling the bulk of the curation effort.
The main technical problem with attempting to highlight additional metrics through PyPI itself at this point in time is that beyond the basics ("using dependencies with known CVEs is a bad idea", "using dependencies with licenses that are incompatible with your project is a bad idea"), we, as an industry, still don't really know what good predictors are for "open source components that will save you more time than they cost you" - searching for open source software on the internet remains an art rather than a science.
There are a bunch of indicators we use, but other than actually going and reading documentation and reviews, most of them are actually measuring "if you choose poorly, at least you won't go down alone" factors like download rates and commit volumes and adoption by high profile individuals and organisations, rather than "is this component likely to be a good fit for my specific use case?".
So I think the way to go about this is precisely the way DjangoPackages went about it: find a community with a shared interest in content curation, and build a curation system aimed at meeting the needs of that community. If a particular approach to package assessment proves to generalise effectively (which, as it turned out, DjangoPackages didn't - attempts to create similar sites for other Python web frameworks fizzled out, even though the necessary work was done to separate the underlying comparison framework out from the site specific DjangoComparisons code), then it may make sense to propose it for standardisation upstream on PyPI itself. However, I think we're quite some way away from anyone having the evidence needed to back up pitching any particular measures as useful predictors.

It's late and I haven't fully read this. I just wanted to correct (or clarify) the PyPI ToS since its been a somewhat contentious point among some community members. It does nothing to ensure that someone is legally allowed to modify or eve use the software on PyPI. The only right it ensures is a right to distribute for PyPI and all users of PyPI. Determining if it's legal to use a particular project is an exercise left to the reader (though the common case is certainly OSS).
Sent from my iPhone

On Mar 7, 2016, at 12:59 AM, ncoghlan<EMAIL_ADDRESS>wrote:
The PyPI ToS thus aims to ensure that everyone running "pip install " is always legally entitled to download and deploy that component, but doesn't make any promises about whether or not that component is worth running (or even safe to run, as "pip install python-nation" illustrates).

Good catch - I'd forgotten that "run" wasn't listed as one of the requirements for upload. (I knew "modify" wasn't listed, as that's how the ToS avoids conflicting with the GPL and other copyleft licenses).

I really like the idea of @nlhkabu to use something similar to github, this way developers can show their preference for a particular library and there is no way that a library have bad karma or even a negative score, plus a good number of developers make use of github is a system that is familiar.

A list of dependant projects can be another usefull mesure, many of use make indirect use of librarles, for example many users can start and use the babel library but not start the pytz, showing the dependants of pytz can give credits to its developers

Thanks for the tremendously thoughtful response @ncoghlan.
One of my motivations behind wanting a feature like this is due to personal frustrations I've had during package evaluations, especially when doing so within a timebox when working on projects at work. Adding a mechanism to provide warehouse users with additional data around package quality and community activity seemed like big win to me.
That said, I think you're absolutely spot on with it being an art and not a science and until curation has been tried, tested, iterated on to a point where it's globally accepted by the Python community at large, it doesn't belong in warehouse (if even then based on your other points).
After reading and giving this a whole lot more thought, I think I've come to the conclusion (FWIW) that I'm -1 on this feature (quality matrix and Github star-like system alike). At least, until something has been proven out of band with warehouse at which point it likely be worthwhile to reevaluate (but not be a slam dunk).

I'm -1 on this feature (quality matrix and Github star-like system alike)

I agree.  As you mentioned, the GitHub star system is really not that different to download data, so I am happy to strike that idea off the list.
As for other community ratings, I agree wholeheartedly with @jacobian.  One of my design objectives is to make the site friendly and usable for all Python community members - it seems a rating system would only undermine this.
Something stood out from @ncoghlan's post:

any metric added that can be interpreted as a measure of "software quality" or "community quality" risks drawing the ire of developers of packages that score badly on that metric

We currently have badges (for version, dependencies, test coverage, test status) on each of the package pages - I wonder if these are also out of the scope of what PyPI should provide?  Comments on #786 would be appreciated.

I've been thinking about this all morning and talking it over with folks and I here is what I'm at right now.
I believe that a comment system requires a commitment to moderate and police the comments made on that. While you can provide tools to try and crowdsource that to some degree, at the end of the day, if we gain a comment system we're responsible for ensuring that the content of those comments contain the kind of content we want to see on PyPI. I have serious doubts to our ability to actually effectively moderate that, particularly given the handful of people with power to do that and what their schedules look like already in terms of time.
I also believe that a review system for a software project is a fundamentally harder thing to do than for your typical product on say, Amazon. There are only so many (legitimate) ways that you can use a bowl you bought from Amazon, and there are a fairly finite set of things you can judge it based on. However a project like Django, there is a much more diverse set of use cases and things you can judge it on. This makes it hard to even write a review for it (in fact, I can probably count on one hand the number of critiques for software I've read in my life that weren't seriously flawed in some way).
I believe that GitHub like star ratings are likely to provide little to no real information beyond that of download counts and will likely contribute to having people feel like publishing packages to PyPI comes with a built in popularity contest (moreso than is inherent in the nature of competing software projects). I think it's likely that it will provide even less information than we can currently get from download counts, because at the very least a download generally represents some action taken by someone (baring mirroring and fraud) whereas all a star really means is that you convinced someone to click a button on a website once. There's no real investment or statement that the star really means much, if anything.
As far as trying to provide some sort of automated comparison of quality for a project, I think it's hard to do that really. There are very few (if any) things that I can think of that we can determine automatically with a low enough false positive rate that really speaks in a meaningful way as to the "quality" of a project. That number gets even less so when you remove things which are otherwise self evident (e.g. things like "has a description", it's fairly obvious from a project detail page if it has a description already or not, a badge doesn't add much). That doesn't mean that I think it's impossible to do something like this, just that I think that it would be hard to find many things to include in this matrix.
I do agree with @ncoghlan that we should focus on providing data, particularly data that is difficult or impossible for someone other than PyPI to provide (although I disagree with the characterization of the data as objective- what data you choose to show in the UI and how you show it fundamentally is about choosing what story we want to show with the data, and is a subjective statement on what we think is important). Which I think segues nicely into a thing that I think we could do, which is provide functionality similar to GitHub "watchers", allow people to "watch" a project which would subscribe them to all of the notifications for new releases and such for that project, and then expose the number of watchers. This is a bit more meaningful than just stars, since there's some level of investment by the people doing the watching (they're asking to get notifications/emails/etc based on activity on the project) which keeps people from just watching tons of projects (else they end up getting "spammed" by notifications). It does still have a bit of a popularity contest feel to it, but I think it's similar in vein to the download counts.

Another nice thing about watchers (versus stars or download counts) is they are not just a measure of usage, but also a measure of investment and degree of import.

I admit when I was talking about data collected by PyPI being objective, I was thinking in terms of an API for other (opinionated) services to use to retrieve that data, rather than decisions on how to present the information in the default web UI.
In terms of "watching" projects, I'm less sure of the value beyond the existing download counts, since it's already possible to watch packages even on current PyPI by registering them with https://release-monitoring.org/ (Debian and openSUSE also have their own language independent techniques for upstream monitoring)
That said, those other techniques are generally polling based (and hence may take a while to notice new releases), while an asynchronous event stream from PyPI would allow new releases to be picked up almost immediately.

I think a possible problem with download counts as the sole metric is that it ignores a number of things:

It treats all dependencies of a project with the same importance, but I think that fails to account for the fact that your "main" dependency, like say Django, is likely to be something you care about more than a tertiary dependency, like say psycopg2 (for a Django web app).
The download counts can only represent usage that comes from "typical" dependence. This means that a project like, say packaging or versioneer are likely to be underrepresented since one of their primary methods of use is by bundling.
The download counts can only represent usage via PyPI, but it ignores usage through a redistributor. While it's not unusual for redistributors to offer their own metrics, having this as a separate metric goes back to the fact it's a bit different than pure download (or installed) counts, it would infer a stronger "dependence" than simply a download or install.

I was always planning on adding the feature of watching a package (partially tracked in #997 and #798) but I'm not sure if exposing the number of watchers a project has is a good idea or not (though I lean towards yes).

Yeah, a watchers feature is probably worthwhile - I came around to that point of view when I checked Anitya and noticed it works by way of daily polling for new versions.
As a possible separate option from watchers (and keeping in mind I'm talking about changes after the PyPI replacement milestone), it might be interesting to have the notion of "registered redistributors", where downstream redistributors can post back to PyPI to say "we redistribute this".
I'm not actually sure that's a good idea (mainly because we'd need some kind of review process to avoid link spam), but I can see potential benefits for both package maintainers (as they can see at a glance who is redistributing their software), and for redistributors (they get a discovery path from the upstream releases to their downstream counterparts).

Thinking about this lightly last night and heavily over coffee this morning, I'm pretty firmly -1 on the watchers feature and here's why:
Popularity contests aside, having this number in warehouse would (in my mind) come with the connotation that it's the official metric whereby users can determine the level of global investment by a project's development community and its users. In reality, the accuracy of watcher count in relation to actual community investment will vary wildly per project as, aside from user-driven input, there is no mechanism to determine what this should really look like with the myriad of methods a user can "watch" a project outside of PyPI. Due to the fact that communication mechanisms are determined by each individual project and are outside of the realm of control of PyPI, I don't believe that adding watcher count per project would really add any real value and would rather more often than not, be misleading.

@demianbrecht To play a bit of an advocate (though I'm still on the fence personally) how does this differ from download counts? The accuracy of that varies wildly from projects which are only available for download on PyPI, projects which are available on PyPI and on their own systems, and still other projects which are only available to download from their own systems. Then add in the pip download cache, the pip wheel cache, bandersnatch mirrors, and redistributors like Debian, Fedora, Anaconda, etc. I'm not sure that the value of exposing that number would be any more (or less) misleading than the current numbers we expose. Maybe that's an argument for removing download counts (although when we removed them briefly in 2013 when we first switched to Fastly people complained loudly), maybe it's an argument that one imperfect metric doesn't excuse another one (though I would argue that there are no perfect metrics, just flawed ones that require interpretation to be fully meaningful).

@dstufft heh you're absolutely right, and I'd be in favor of removing download counts as well. That said, I also remember the backlash of 2013, so I'm fine with them being grandfathered in. You're also right in that one imperfect metric doesn't excuse another.
To be clear: I'm not horribly opposed to the feature in of itself. What it really boils down to what is the vision for PyPI/Warehouse? Is it to be a repository, simply providing access and impartial facts about the projects that it hosts, or is it to also provide user-driven color commentary on the hosted projects and to provide Yet Another community resource? If it's the former, then I think that all extraneous, user-driven features should be nixed for warehouse. If it's the latter, then features like watcher count and such makes more sense.
Personally, I'd like to apply the Unix philosophy of doing one thing and doing it well: A repository. Other community-related features should be nixed from Warehouse and offloaded to other, external applications.
This isn't to say that there shouldn't be community tie-ins (a la Github webhooks and services) within PyPI. I think adding functionality around that would provide much richer user experience than attempting to rebuild wheels within PyPI, especially where the value it's adding may contradict the overall vision of what PyPI/Warehouse should be.
That all said, I'm brand spankin' new to working on PyPI/Warehouse development so I may be entirely off my face with all of this :)

@demianbrecht I think you have the right kinds of problems and perspectives in mind to try and balance :)
When it comes to PyPI & metrics, I think there are 3 key aspects to keep in mind:

Data collection (in many cases, only PyPI can do this, since it's the common publishing platform that seeds the rest of the Python package distribution ecosystem)
Data publication via an API for use by 3rd party review services (again, only PyPI can do this for cases where PyPI holds the raw data)
Data publication in the default web UI (here we have the option of deferring to 3rd party review services like djangopackages.com)

I think there are several areas where 1 & 2 will make sense, with PyPI acting as a clearing house for metrics just as it does for actual software distribution. I see that falling into three categories:

metrics about client behaviour (download counts, watcher counts - perhaps categorised in some way to improve data granularity, such as separating out download counts for known mirroring clients like bandersnatch, or attempting to report unique downloading IPs rather than raw download counts)
opt-in metrics supplied by publishers (such as the suggested test status and test coverage metrics)
analysis of the dependency graph between packages (this one can be handled by 3rd parties that mirror the whole of PyPI, so doing it in PyPI itself would be an efficiency measure that lowers the barriers to making use of the dependency graph details, rather than something that third parties inherently can't do on their own)

For the 3rd aspect, my own main interest would be in nudging users in the direction of a "risk management" approach to consuming open source software, and in that context, the merit of high download counts and high watcher counts is "If this was actively malicious, it wouldn't be so popular" (the open source equivalent of "nobody ever got fired for buying "), while the benefit of test status and test coverage information is that tested software with good test coverage is more likely to work as advertised.

FWIW, in the haskell community,  hackage allows you to vote for packages and stackage has disqus comments. Neither seem to be used much from what I've seen, although the haskell community is much smaller than the python one.

I am strongly for GitHub stars and number of downloads (ideally total and e.g. this week/month). As on now it is hard to distinguish between actively developed and wildly used packages and ones abandoned years ago. Right now when I search in PyPI it's like searching a dumpster, with rare pearls among dead packages.
Examples where it works:

https://packagecontrol.io/ (also: the front page, search-as-you type, and compact view)
https://atom.io/packages/

I would rather use already existing stats than trying to add new voting system. (Why add complexity?)

When it comes to finding useful Python software, searching on Google with "python" appended as an additional search term is generally going to give much better results than searching PyPI directly, and that's always going to be true regardless of what happens on the PyPI side of things (the general purpose search engines have inordinately more information sources to draw from when ordering results, and "incoming links to the project documentation or download page" is actually a pretty decent measure of adoption).
In terms of metrics reported by PyPI itself, there's zero chance of reporting a metric maintained by some other system (as with the reference to GitHub stars themselves, rather than a star-like system). The most we'll provide is a machine readable link to the relevant data source (such as a project's source code hosting service), wherever that may be, and even that would be dependent on project maintainers filling it out in their project metadata.

Right, a key problem with using GitHub stars is that not every project is on GitHub (although a lot of them are), and even if they were it seems like a bad idea to bake that assumption into PyPI when it's entirely within the realm of reasonable possibilities that in a few years time GitHub goes the way of SourceForge. Overall across everything we do here, we try to avoid tying ourselves to external systems in ways that can't be easily replaced. For instance, using the Fastly CDN? That's fine because we can switch to Cloudflare or Akamai or doing it ourselves without any impact on end users. Forcing everyone to log into the site using Github? That's bad because we can't swap it out without end users being affected.
I'm perfectly fine with measures of popularity, as long as they're meaningful measures. Number of stars is pure popularity contest without much meaning behind it, since all it really suggests is that you convinced someone to click a button- and I think people attempting to game that system. I think that the best measures of popularity inherently stem from taking some action that people can do for it's own purpose, and exposing the number of people who take that action.

@stared are you saying that downloads do not provide an idea of what's actively developed but GitHub stars do? Where in the screenshots that you showed do you see that something is actively developed? You have the number of installs and the rough ranking based on that. Then you have the number of stars with the number of ... commits? next to that. Is the number of commits to you an indication of maturity/activity/status of maintenance? If you want better intelligence about a package openhub.net has a great way of analyzing a project for you. Further, given that something exists that does this well, why does Warehouse/PyPI need to do this?

Nothing is forever. Yet, if the PyPI web interface want to have any use, as it is is not enough.
And there is a wild difference between using GitHub as supplementary source of data (even if for some, not all, projects) and making it core of it.

Number of stars is pure popularity contest without much meaning behind it

While I understand this sentiment, I couldn't disagree more. Try creating a not-even-working code and get more starts than competing projects. Of course sure, depending on subject absolute numbers may be different - for some specialized projects 50 stars may be a lot, whereas for other - 1000 stars may be some baseline.

meaningful measures

So, what is wrong with keeping:

number of downloads (as a function of time)
created and updated dates?

@stared Number of downloads is part of Warehouse (although not currently operational, you can see a mock up though: https://pypi.io/project/pip/#statistics). I don't think we expose specifically the created date of the project, though we expose the date that every single release was made, so you can get the first release date by just going to the first release. Currently the last release date is exposed at the top of each project page plus the already mentioned stream of every release.
Is there something you're looking for that isn't covered by that?

@stared GitHub Stars aren't a measure of "I used this, this worked, and I'm validating that it is still maintained." GitHub Stars have always been "This looks cool, let me save that for later".

@sigmavirus24 Still, I find it to be a great proxy. (Though, I personally star things I use and like.) The problem is not between 50 vs 200 starts. The problem is with weeding abandoned packages.
But again, "downloads" is better.
@dstufft Great! I know it from "the old PyPI website".
And using it in search would be really, really wonderful.
To be honest, other packages rarely mention the created that. I think it is a pity. When the past update is 3 month ago, there is a big difference if the firs update was also 3 months ago (then chances are it is neither mature nor under active development) or 4 years ago (likely that there is some separate dev branch, or that it is so mature that does not need frequent updates).
Personally (as a big fan of D3.js stuff) I would love to see se "barcode" with stripes, each for a release, with position related to the release date.

A little context on why I'm weighing in, and then my take.
Context: I'm the project manager for Warehouse, via the Mozilla Open Source Support Program grant, to replace the legacy PyPI site. The new site is about to hit beta and we'll be announcing that and asking folks to test it. Our developer roadmap focuses on the essential things we need to do to replace pypi.python.org within the next few months. Once that's done, we can work on longer-term features (such as new APIs). I'm also running a sprint at PyCon in May and happy to discuss this there.
And for basic and advanced PyPI download usage statistics, we now provide BigQuery support, although this is not discoverable through PyPI project detail pages and, for reasons mentioned above, perhaps should not be.
My assessment: In the past two years, Libraries.io has become a provider of PyPI statistics for projects, including GitHub stars and forks, dependency tracking, and other relevant factors. It's backed by Tidelift but it's open source. It has an API we could hook into. (See #3252 for some more thoughts on that.) @andrew is working on major improvements to their ranking metrics, and has further metrics work in their backlog.
Therefore, I think we should strongly consider referring users to libraries.io for project metrics and rankings, and submit future issues there to help them improve, rather than implement any project ratings primarily in PyPI. And then we can decide, based on what they have available, which of their stats to display on PyPI project detail pages.

@brainwane +1, I like the idea of using libraries.io as they're giving far more thought to meaningful metrics than I suppose anyone would ever want to put directly into pypi.

Lending PyPI's weight to Tidelift's efforts to come up with a language independent ranking approach that encourages and rewards good community behaviours seems like a good direction to me.

Sounds good for me, since the main idea to show more info about a library
was to give to posible new users more info about a library to decide to
include it in a project or not looks like library.io is a.good source for
those info.
--
Enviado desde mi móvil, disculpe la brevedad
William

People who want a watching/watchers feature: you can log in to libraries.io via GitLab, GitHub, or BitBucket to watch packages and get email notifications of new releases + an onsite newsfeed. It can also watch your repositories & notify you of changes in your dependencies, though it doesn't yet support some dependency manifests like tox.ini. Surfacing the number of people subscribed for a package is in their backlog.
I linked to this thread on distutils-sig and will leave this issue open for a few more days to let more people comment, but I'm leaning towards closing it and opening:

an issue to link to the libraries.io page for a project on each Warehouse project detail page
a PR to add an FAQ entry about project stats, linking to BigQuery guidance and libraries.io

Sorry for the delay, was mostly offline for the Bath Ruby conference last week. If there's anything else I can do to make it easier to get statistics out of Libraries.io for you to use them do let me know.
SourceRank 2.0 development is now underway in https://github.com/librariesio/libraries.io/pull/2056, would love to hear any feedback/thoughts on the details, especially how it works within the python ecosystem.
Would some kind of badge or embedable widget be a lightweight way of adding more info to each page?

Now that #3400 and #3434 are merged, I'd like to close this issue and thank everyone for participating in the discussion.
Thanks for the link and invitation, @andrew. Can you point to a demo or any screenshots? And is there an existing issue somewhere in the libraries.io set of repositories about badge-y things, or a repo where such discussion would be best?

@brainwane there aren't any badges/embeds in Libraries.io at the moment, I've opened an issue up on Libraries.io: https://github.com/librariesio/libraries.io/issues/2077


[Question] Why this package releases only beta version for the past three years?

Always was wondering, why StyleCop 1.2.0 wasn't released yet. If one won't look at the dates and just install latest stable version, they will miss out on a lot of rules and fixes.

We haven't had the time to do an audit of all C# 8 features against each of the available rules, followed by the stabilization period. And then in that time, C# 9 and 10 were released, with C# 11 coming.

So it will stay in beta for a foreseeable future? Especially since C# releases are now on annual basis?

Yes, that's correct

Please reconsider. The fact that some new language features are missing, does not imply that this package is unstable.
If I check NuGet I can clearly see that a lot of people are using the 'unstable' versions instead (for good reasons).

I just noticed this non-pre-release 'unstable' variant on nuget: https://www.nuget.org/packages/StyleCop.Analyzers.Unstable/ :-D


FeatureFormView - Attachment handling revisions

Related Apollo 684

This is ready for review once again

Still ready for review. Updated AttachmentFormElement.deleteAttachment(attachment) to AttachmentFormElement.delete(attachment).

Updated AttachmentFormElement.deleteAttachment(attachment) to AttachmentFormElement.delete(attachment).

Is that what the new generated code outputs?

Does the AttachmentImportMenu.init(element: AttachmentsFormElement, onAdd: ((FeatureAttachment) async throws -> Void)? = nil) method still need the onAdd argument to be async throws?
Same question for onDelete and onRename for the AttachmentPreview class?

Is that what the new generated code outputs?

It looks like taking the attachments property out of generation to make it not-cached actually caused that.. which I wouldn't have expected. Reverting for now.

I think AttachmentFormElement.delete(attachment) is actually better. See the Swift API doc here.


Header navigation component goes offset to the left

Hey guys, there is UI issue. Header navigation component goes offset to the left. I'm using same code from documentation.

How get error message? I don't select any file, on pressing button on header I don't get any error either.

can u share expo snack to reproduce ?


Rename TimeImpl to FakeTime and make it slightly more useful

cl/304931012

For bonus points, you can also remove TestTime in AndroidSqliteDatabaseRegistryTest.kt

Sadly that test relies on both real and fake time implementations... It's kinda tricky to update.


Can't login with Google account

Description
Trying to log in with my Google account gives me an error page. The URL of the login page is https://project-pantry.onrender.com/accounts/login/
How to Reproduce

Click the Login with Google account Button
Select your Google account
Click Continue

More Detail
I can't provide the screenshot because the error page shows the settings.

We have fixed the issue. Thank you for your report.


FAQ: Bastion connection supported? Says no. But yes it works.

On this page it says:
"Are cloud-hosted environments supported with Azure Bastion?
These environments haven't been tested, nor are they supported with Azure Bastion."
I use Azure Bastion exclusively to access all my cloud hosted environments. My access works every time.  Maybe this FAQ question could be revisited?

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

ID: fe3913a6-4daa-9973-6f0b-d7ae4c1007c2
Version Independent ID: f2cd311b-fcb8-cff4-57a3-47c3c52b19d6
Content: Deploy and access development environments - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/dev-tools/access-instances.md
Service: dynamics-365-cross-app
GitHub Login: @laneswenka
Microsoft Alias: laswenka

Reached out to PM for guidance.


Momentum scrolling not working on my iOS devices

Scroll doesn't work in the classic phone/tablet way on my iPhone or iPad with the Stackedit site. Is this a known issue?

Please try again with the v5 and open a new ticket if it's not fixed.


CREATE DOCUMENTATION TEMPLATE

Here are the points for Documentation Update template:
Is there an existing issue for this?
I have searched the existing issues (required)
Issue Description
Please provide a clear description of the documentation update you are suggesting. (required)
Suggested Change
Provide details of the proposed change to the documentation. (required)
Rationale
Why is this documentation update necessary or beneficial? (optional)
Urgency
How urgently do you believe this documentation update is needed?
High
Medium
Low (required)
Acknowledgements
I have read the Contributing Guidelines (required)
I'm a GSSOC'24-Extd contributor
I'm a Hacktoberfest contributor
I have starred the repository (required)
I am willing to work on this issue (optional)

@Git21221 assign me the task under GSSOC

@alo7lika why this is required?

@alo7lika and how are you gonna update it? readme or anything else?

@alo7lika and how are you gonna update it? readme or anything else?

Will use GitHub’s “Issue and Pull Request Templates” feature, which lets us set up multiple templates for issues and PRs specifically, helping to streamline contributions. This keeps everything organized, up-to-date, and easier to navigate, especially as more features get added to the project!

@alo7lika go ahead

@alo7lika go ahead

add labels GSSOC

@alo7lika doesn't matter in issue though, but I will add


add support to setuptests.js when running tests in webstorme

So WebStorm 2017.1.2 is out, so I added a configuration to run my tests.

Its seems to work (Thanks WebStorm devs !!) but there is still some problems:
This works:

But when I Moved global.a to setupTests.js it fails (console.log doesn't print on console as well)

It seems that setupTests isn't been run before each test, because all my test depends on setupTests.js, I can run any test.
notice that in terminal the same test is passes
also adding import '../../setupTests' in the test file will make it work in WebStorm also.
so the issue is that in WebStorm, setupTests.js does not run before each test.

@shai32 Did you include
"setupTestFrameworkScriptFile": "<rootDir>/src/setupTests.js", in your jest(in package.json). That should run setupTests before jest!
Let me know if it helps!

Yea, this will not be very smooth because WebStorm isn't aware of the configuration we're passing to Jest. So indeed your best option would be to (unfortunately) duplicate it in package.json as described by @anilreddykatta.

it works, thanks (should be added to docs)
but there is another problem.
this is the test:

this is the error

when running from terminal the test passes

@shai32 Please while running from webstorm add this to --env=jsdom to JEST options.
Let us know how it goes?

@anilreddykatta works!!!! :)

@shai32 Can you close if the issue is resolved?

Close - works when defining setupTestFrameworkScriptFile in package.json

This solution doesn't seem to work anymore without ejection:
`These options in your package.json Jest configuration are not currently supported by Create React App:
• setupFiles`


Problem with helpers using references being called from template (Blaze)

When a helper uses references as described in the Controls section of docs, this gets thrown:
Exception in template helper: TypeError: Cannot read property 'enabled' of undefined`

If I change the code so that the helper only gets called if I click a button (for example), it works fine.
Minimal reproduction:
<template name="parentTemplate">
  {{#if isEnabled}}
    ENABLED
  {{/if}}

  {{> childTemplate ref='childtemp' }}
</template>

<template name="childTemplate">
  <button {{b "toggle: enabled"}} type="button">toggle</button>
</template>

Template.parentTemplate.viewmodel({
  isEnabled() {
    return this.childtemp.enabled();
  }
});

Template.childTemplate.viewmodel({
  enabled: false
});

Now, if I exchange that {{#if isEnabled}} into a div <div {{b "if: isEnabled">... it works.
Tested with Meteor <IP_ADDRESS>.

There's no fix for it since the parent #if is invoked before the child is
created. You'd have to check for the existence of the reference or use the
if binding (which happens after the child is created).
On May 28, 2017 7:08 AM, "arggh"<EMAIL_ADDRESS>wrote:

When a helper uses references as described in the Controls section of docs
https://viewmodel.org/docs/misc#controls, this gets thrown:
Exception in template helper: TypeError: Cannot read property 'enabled' of undefined`
If I change the code so that the helper only gets called if I click a
button (for example), it works fine.
Minimal reproduction:

Template.parentTemplate.viewmodel({
isEnabled() {
return this.childtemp.enabled();
}
});
Template.childTemplate.viewmodel({
enabled: false
});
Now, if I exchange that {{#if isEnabled}} into a div <div {{b "if:
isEnabled">... it works.
Tested with Meteor <IP_ADDRESS>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/288, or mute the thread
https://github.com/notifications/unsubscribe-auth/AED31ky5BvBTNUVGbz3FA9TgSREw5Y92ks5r-XG8gaJpZM4NopH2
.

Thanks for the clarification 👍


Update Regions “2022-09-26-sylt”

Automatically generated by Netlify CMS

👷 Deploy Preview for gilded-sunburst-0982f4 processing.

Name
Link

🔨 Latest commit
5342f1d57e2b6ef31368fc61bd8b5a4ea70a9475

🔍 Latest deploy log
https://app.netlify.com/sites/gilded-sunburst-0982f4/deploys/6331b16924c44000085ab866


NIFI-8975 Integrate KerberosUserService into HBase processors/services

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

@exceptionfactory - Was wondering if you have any time to look at this since you reviewed the previous PR, no rush. The changes in the HBase client service should be very similar to those in AbstractHadoopProcessor.
The change set would have been smaller, but I wanted a way for the HBase processors to identify a Kerberos login issue separately from other errors, and this led me down the path of changing KerberosUser to throw a new RuntimeException, instead of LoginException, so this requires lots of small tweaks.

@exceptionfactory thanks for reviewing, committed your suggestions and added another commit for some logging tweaks.
For the provided dependencies, yes the general approach is that any service API from standard services should never be included in any NAR besides nifi-standard-services-api-nar, so the pom for nifi-nar-bundles marks them all as provided in a dependency management block to ensure other NARs don't accidentally include them...
https://github.com/apache/nifi/blob/main/nifi-nar-bundles/pom.xml#L179-L257
Then the nifi-standard-service-api-nar overrides the scopes to compile to actually include them:
https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-standard-services/nifi-standard-services-api-nar/pom.xml
So I was just removing redundant "provided" scopes.


can't join a node

When the playbook reaches the "Join to kubernetes cluster" task it fails with:
failed to check server version: Get https://<IP_ADDRESS>:6443/version: x509: certificate has expired or is not yet val│ 2345 root      20   0  111896   4248   3456 S   0.0  0.1   0:00.69 docker-proxy                    packet_write_wait
id
I am new to kubernetes so I am probably doing something wrong, any help would be appreciated!

My server time was off :)


Lift signal bit widths into type system when Rust achieves proper support for const generics

This has basically always been the plan, but is on hold until everything is stable. This will be very much a breaking change but I can imagine a lot of user code actually won't look much different due to type inference.
It looks like this is the tracking issue min_const_generics, which is the minimal feature subset that will be stabilized first, but it's not quite sufficient.

I believe this will also be required for this use case in order to be able to calculate bit widths for combined Signals - eg. a * b will produce a new Signal whose bit width is the sum of the bit widths of a and b respectively. This means the signature of mul will be something like fn mul<const N: u32, const M: u32>(a: &Signal<N>, b: &Signal<M>) -> Signal<N + M> which is not supported with only min_const_generics.

Is it possible to use https://docs.rs/typenum instead before the stablization of generic_const_exprs?


[20.03][Security] bluez: 5.52 -> 5.53 for CVE-2020-0556

See here for details:
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00352.html
(cherry picked from commit 8f8b6459e9f38bc21df4976265f96b4541b917ec)

@GrahamcOfBorg build bluez bluez-alsa bluezFull bluez-tools

please change the base branch to staging-20.03

Rebased backport onto staging and changed base branch.

@GrahamcOfBorg build bluez bluez-alsa bluezFull bluez-tools

In addition to the OfBorg CI tests passing, I have also rebuilt my NixOS 20.03 laptop with bluez 5.53 and verified that my bluetooth headset is still working as expected.


Automated cherry pick of #7998: optimized: create eip params

Cherry pick of #7998 on release/3.3.
#7998: optimized: create eip params

/lgtm
/approve


Y-Axis flickers if using non-compatibility renderer

Godot version
4.x
System information
Windows 11, Forward+ & Mobile, RTX 3080, version 528.49
Issue description
The default viewport of a 3D scene has the Y-axis perfectly aligned, which causes flickering when applying a yaw rotation. This flickering is minimized/removed when zooming a viewport all the way in or out, but is otherwise consistently popping in and out of view. Using compatibility mode will also remove flickering, though a min/max zoomed viewport appears to have less "jitter" on the Y-Axis when rotating
YouTube demonstration of the renderers and their different behaviors
Steps to reproduce

Open a new instance of a Godot 4.x project
Ensure the renderer is set to either Forward+ or Mobile
Enter a 3D scene & hold the middle-mouse button to yaw the camera

Minimal reproduction project
N/A

Duplicate of https://github.com/godotengine/godot/issues/37016. So closing to keep the issue tracked in one place.


Error: Your supplied key '' is either not a valid key, or came from a different server version (that is not compatible with this one). Please try fetching a new key.

Describe the bug
Error when  fetching data from slo datasource (data dynatrace_slo).
Error message:
Error: Your supplied key '' is either not a valid key, or came from a different server version (that is not compatible with this one). Please try fetching a new key.
To Reproduce
Steps to reproduce the behaviour:

Create a terraform code:

data "dynatrace_slo" "slos" {
name  = "yoursloname"
}
terraform init ; terraform plan
Expected behavior
It should return the SLO object data.
Screenshots

Desktop (please complete the following information):

OS: OS
Browser [None, CLI terraform]
Version:  terraform "~> 1.2" and dynatrace-oss/dynatrace"  "> 1.41.0"

Additional context
The behaviour is intermittent as print screen shows.

Hello @anspereira-mck, I'm having troubles reproducing the issue you're describing.
Based on the screenshot you've provided it looks like a subsequent terraform plan eventually succeeds, am I right?
Is the key mentioned in the error message identical to the id that's being used when the output states reading complete after 1s [id=....]?

Yes, the error was intermittent but now it seems to be solved.


Routes work when navigated to by  elements, but not when directly navigated to from the browser url bar

See sandbox for example:
--redacted--
When using the links, the page navigates fine. But when typing in the link directly from the navbar it shows a 404 error in the console and nothing comes up. What am I doing wrong? Thank you!

Snowpack issue, fixed by putting
routes: [{ match: "routes", src: ".*", dest: "/index.html" }],
in your snowpack.config.mjs


Validate it works with GitHub Actions v2 beta

I want to check that this action still works in the new beta that has the yaml syntax for workflows. If it doesn't work, I will look into updating it to make sure it does work by either maybe switching to the JS action style or adding an action.yml file

Confirmed it still works


Fix unknown authority error

I ran gocat in my eks environment as pod.
But I got the following error.
[ERROR]  Get "https://github.com/my-org/my-repo.git/info/refs?service=git-upload-pack": x509: certificate signed by unknown authority

I resolved this issue by copying the ca certificate from the build image.
please check the diff.
a03f85352a72cfac9f1d6909945d41d5f46c4f1c

The ci failure can be fixed by merging the #715 pull request.

@pirlodog1125
Thank you for your contribution.
To the maintainer.
After merging this pull request, I request you to release it with a new tag, v0.1.6, specified.
The reason is that I would like to specify a stable version to use.


How to unlink one of many targets from a source?

My app is reading data off of some hardware, which gets processed three or four times before showing up on a graph or in a datafile. I'm implementing this process using this Dataflow library (which is great, by the way).
The main dataflow network needs to persist throughout the app's lifetime. I also have a requirement that when the user clicks a button, the app should record the data that's flowing through until they click again, and then run some calculation on the recorded data. I'd like to implement this in my dataflow network class like so:
public void LinkToExample(ITargetBlock<double> tempTarget)
{
    this.ExampleBlockFromThePipeline.LinkTo(tempTarget);
}

My question is how to unlink this when I want to stop recording. The article above doesn't really answer the question. Can I just call Complete() on the temp target block? Will I run into a memory leak if I do that and a malicious user clicks the button repeatedly?

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

ID: 64ab5489-f298-dd0d-6812-68ed98365dc5
Version Independent ID: de509e9a-3c3d-a485-4a41-3cb9ef6ff2a9
Content: How to: Unlink Dataflow Blocks
Content Source: docs/standard/parallel-programming/how-to-unlink-dataflow-blocks.md
Product: dotnet
GitHub Login: @rpetrusha
Microsoft Alias: ronpet

The LinkTo method returns an IDisposable that, according to the referenced docs:

...upon calling Dispose, will unlink the source from the target.

@lettucemode worth a try?

Ah thanks, I missed that. I'll give it a shot.


I want to change px to pt

Hi !
i have fixed height div now i want to print that div but the issue is i want to change the font-size unit into Points in order to maintain font-size in print

+1
I am using this for the signature autograph in my html that is designed for print. I would also like to specify how much height I want the text to occupy.


[SPARK-47716][SQL] Avoid view name conflict in SQLQueryTestSuite semantic sort test case

What changes were proposed in this pull request?
In SQLQueryTestSuite, the test case "Test logic for determining whether a query is semantically sorted" can sometimes failure with an error
Cannot create table or view `main`.`default`.`t1` because it already exists.

if run concurrently with other sql test cases that also create tables with the same name.
Fix it by putting it in a schema with a unique name.
Why are the changes needed?
Fix flaky test issue
Does this PR introduce any user-facing change?
No
How was this patch tested?
Test itself
Was this patch authored or co-authored using generative AI tooling?
No

Hi, @jchen5 and all. How do you want to proceed this PR?
I guess https://github.com/apache/spark/pull/45855#discussion_r1550652914 is the latest direction. Could you update the PR in that direction?

Not related to this PR. It seems we should move the test case Test logic for determining whether a query is semantically sorted to other place.
SQLQueryTestSuite is used to generate and test golden files.

Hi @HyukjinKwon @dongjoon-hyun can you do a quick review of the updated PR?

Merged to master.


Values are not being re-render when default time is changed using time Picker option in the dashboard

Description
I have created a widget using the NRQL status widget option, one of the configurations of this widget is to polling data every 5 seconds and everything is working if the time picker of the dashboard I have attached the widget to, stay with the default option but as long as I change the time picker option to any other value, the data stop the updating process and if you check the network tab under the inspector you will see that the request is happening but the value is not being re-render in the UI.
Steps to Reproduce
Add Data option -> Look into App & Visualisations -> enable the app Status Widget Pack -> select the option NRQL status Widget -> create a query like SELECT count(*) FROM Transaction -> set some critical and warning thresholds -> set polling to 5 seconds -> save the widget into a dashboard -> open the dashboard and see that the widget is being updating with the values every second in the default option of the time picker -> change dashboard's time picker to 5 minutes -> widget stop the re-render process of the value.
Expected Behaviour
Change the dashboard's time picker without affecting the re-render process of the widget's value since the polling should keeps happening every 5 seconds
Relevant Logs / Console output
Your Environment

Browser name and version: Google Chrome Version 121.0.6167.139 (Official Build) (arm64)
Operating System and version: macOS Sonoma 14.3

This should be fixed in the latest release. Feel free to reopen if the issue persists.

Thank you I will let you know in case the issue persists, really appreciate your help 👍🏽


operator sysdig-shield-operator (v0.1.2)

New operator bundle
Name: sysdig-shield-operator
Version: v0.1.2
Certification project: 6721216c61823a8bc1399531

/pipeline restart operator-hosted-pipeline


wip: Add error when instantiating generic without type arguments

Motivation

Not sure that this is an approach I want to commit to, but I want to see how
many errors this generates.
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_QUa8gexgQdlz9e
→ https://go/builds/bui_QUa81JfF37vg93
→ https://go/builds/bui_QUa8E8YB3YHVuw

there's quite a few of these and it seems particularly punishing to require people to add these type arguments, because in the vast majority of them it's fair to assume that Sorbet should have been able to infer them.


serve() should fix relative URIs in CSS by default

As the URI-rewriting code in Version1 and Minify_CSS appears to be
reliable (and setting it up manually is a pain), this should be the
default behavior in Minify::serve().

Minifying CSS should "just work" out-of-the-box.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 31 Jul 2008 at 7:42

Done in R177.

Original comment by<EMAIL_ADDRESS>on 19 Aug 2008 at 12:23

Changed state: Verified

Original comment by<EMAIL_ADDRESS>on 31 Jul 2008 at 8:05

Added labels: Usability


cleaning up logic and test issues with ContainerProxy

Description

Repairing more issues with ContainerProxy. Logic for aborting queued concurrent activations now waits for those activations to be processed before stopping.
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[x] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[x] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[x] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

@markusthoemmes any concerns with this in current form?


Hardcoded 'yarn_analysis_template' found in the Cloudformation template

I found some hardcoded code in 'migration hadoop to emr tco simulator', not sure if this is intended.
Also, it looks like the permission for this 'yarn_analysis_template' is required in order to run Cloudformation successfully. Thanks !

Thank you for your comment. The account ID is the absolute path where QuickSight Analysis Template is located, and when you run CloudFormation file in the user account, the QuickSight Dashboard is automatically create from the template.


Adding Machine Learning Simplified by Andrew Wolf

After reading this book, you would understand everything that comes into the scope of Supervised ML, and would be able to not only understand nitty-gritty details of mathematics behind the scene, but also explain to anyone how things work on a high level.
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
The underlying goal of "Machine Learning Simplified" is to develop strong intuition for ML inside you. We would use simple intuitive examples to explain complex concepts, algorithms or methods, as well as democratize all mathematics behind machine learning.
Why is this valuable (or not)?
The Machine Learning Simplified is supplemented with a Jupyterbook that contains python implementations of concepts, algorithms, statistical methods and techniques explained in the book.
How do we know it's really free?
You can access this book on this page: https://themlsbook.com/read
For book lists, is it a book? For course lists, is it a course? etc.
It is a book.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Will change an order for it to be alphabetical


Add nistkat test

Depends on #25

add nistkat test
add script and meta file for checking nistkat
fix _fini undefined

[ ] Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)?  (If so, a version bump will be required from x.y.z to x.(y+1).0.)

Please rebase on top of main.


v0.1.26, failed when syncing to altitude 1214

Description
In ubuntu system, when I synced to 1214 altitude, it stopped syncing. This state has lasted for 24 hours

The problem seems to be solved. I deleted the spacefile file and restarted the synchronization, and then it succeeded.
It should be a fork or other problem during the synchronization process, it is recommended to optimize

Thanks for the bug report, @bananooo-zhang, I'm glad to hear the problem resolved itself!


Test support for e2e rpc tests

Describe the feature
currently geth have testBackend type where it hold some data for backend testing, Ref  : https://github.com/ethereum/go-ethereum/blob/0004c6b229b787281760b14fb9460ffd9c2496f1/eth/tracers/api_test.go#L54-L54
thinking of adding a new type called TestBackend with only provider data on it
and a trait of EthereumRPC  which would have transaction_by_hash, block_by_hash ... etc
then implement this trait for our type
Is it good approach ?
Additional context
No response

thinking of adding a new type called TestBackend with only provider data on it

yeah, this type should wrap:

Arc<TempDatabase>
Chainspec

similar to:
https://github.com/paradigmxyz/reth/blob/d9920ce6c4ac43bc1be41b944d4015c5329f3031/crates/stages/src/test_utils/test_db.rs#L34-L36
this will be a good starting point, then we need a bunch of helper functions to insert and get stuff

thinking of adding a new type called TestBackend with only provider data on it

yeah, this type should wrap:

Arc
Chainspec

similar to:
https://github.com/paradigmxyz/reth/blob/d9920ce6c4ac43bc1be41b944d4015c5329f3031/crates/stages/src/test_utils/test_db.rs#L34-L36
this will be a good starting point, then we need a bunch of helper functions to insert and get stuff

thnak you for your answer. This should be in which file please?

hey @mattsse any hint where this should be written please? :)

let's keep it in rpc-builder for now, we can eventually move it later

closing this because I'll convert this into a new larger tracking issue


feat: upgrade back button

:tada: This PR is included in version 0.85.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[3.2] Fix overflow and underflow checks for string conversion to int

3.2 version of PR #40009

Thanks!