[ceph-users] Re: erasure coded pool PG stuck inconsistent on ceph Pacific 15.2.13

[Wesley Dillingham]

That response is typically indicative of a pg whose OSD sets has changed
since it was last scrubbed (typically from a disk failing).

Are you sure its actually getting scrubbed when you issue the scrub? For
example you can issue: "ceph pg  query"  and look for
"last_deep_scrub_stamp" which will tell you when it was last deep scrubbed.

Further, in sufficiently recent versions of Ceph (introduced in
14.2.something iirc) setting the flag "nodeep-scrub" will cause all in
flight deep-scrubs to stop immediately. You may have a scheduling issue
where you deep-scrub or repairs arent getting scheduled.

Set the nodeep-scrub flag: "ceph osd set nodeep-scrub" and wait for all
current deep-scrubs to complete then try and manually re-issue the deep
scrub "ceph pg deep-scrub " at this point your scrub should start
near immediately and "rados
list-inconsistent-obj 6.180 --format=json-pretty" should return with
something of value.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Thu, Nov 18, 2021 at 2:38 PM J-P Methot 
wrote:

> Hi,
>
> We currently have a PG stuck in an inconsistent state on an erasure
> coded pool. The pool's K and M values are 33 and 3.  The command rados
> list-inconsistent-obj 6.180 --format=json-pretty results in the
> following error:
>
> No scrub information available for pg 6.180 error 2: (2) No such file or
> directory
>
> Forcing a deep scrub of the pg does not fix this. Doing a ceph pg repair
> 6.180 doesn't seem to do anything. Is there a known bug explaining this
> behavior? I am attaching informations regarding the PG in question.
>
> --
> Jean-Philippe Méthot
> Senior Openstack system administrator
> Administrateur système Openstack sénior
> PlanetHoster inc.
>
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[issue45824] CSV module document does not include how to append files

[Wesley Altham]

Wesley Altham  added the comment:

I now see other things on it but I think the doc should have it as well

--

___
Python tracker 
<https://bugs.python.org/issue45824>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue45824] CSV module document does not include how to append files

[Wesley Altham]

New submission from Wesley Altham :

easy- The CSV module does not include how to append a file which is using 'a' 
and not 'w' or 'r'. There might be more to appending but it is not documented 
for me to know, I saw a stackoverflow post about it when I looked and I tried 
it and worked. I hope whoever knows the CSV module could document append at all.

--
messages: 406438
nosy: wesrl
priority: normal
severity: normal
status: open
title: CSV module document does not include how to append files
type: enhancement
versions: Python 3.10

___
Python tracker 
<https://bugs.python.org/issue45824>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Upload Click Conversions using Manager account

[Wesley van Opdorp]

Hello,

I'm having some trouble trying to upload click conversions using the api.

The error I'm receiving is:
*This customer does not have an import conversion action that matches the 
conversion action provided*

Let me provide me some context as how we've come to receive this error.

Our account structure:

   - Manager
  - Sub Manager
 - Account 1
 - Account 2
  
Some notes:

   - We use the *Manager* accounts id as *customerId.*
   - The import from clicks conversion action is configured under the 
   *Manager.*
   - For testing purposes we've generated a *gclid* from a campaign that 
   does not use cross account actions.

*Authentication and client setup*
The $loginCustomerId corresponds with the Manager id formatted to int.
---
$oAuth2Credential = (new 
\Google\Ads\GoogleAds\Lib\OAuth2TokenBuilder())->from($configuration)->build();
$googleAdsClient = (new GoogleAdsClientBuilder())
  ->withOAuth2Credential($oAuth2Credential)
  ->withDeveloperToken($developerToken)
  ->withLoginCustomerId($loginCustomerId)
  ->build()
;

*Retrieving the action through the api*
Because of the error I made an attempt to fetch the action through the api 
to make sure that we're using the correct customerId and actionId.
---


*$action = 
$googleAdsClient->getConversionActionServiceClient()->getConversionAction(ResourceNames::forConversionAction($loginCustomerId,
 
$actionId));echo $action->getOwnerCustomer(); // Same as 
$loginCustomerIdecho $action->getId(); // Same as $actionId*

*Uploading click conversion*
The following snippet attempts to upload the conversion. The 
$loginCustomerId and $actionId haven't changed from the snippets above.

*---*







*$clickConversion = new ClickConversion([ 'gclid' => 'Generated gclid 
from Account 1', 'conversion_action' => 
ResourceNames::forConversionAction($loginCustomerId, $actionId), 
'conversion_value' => 0.01, 'conversion_date_time' => (new 
\DateTime())->format('Y-m-d H:i:sP'), 'currency_code' => 'EUR',]);*

*$uploadClient = 
$googleAdsClient->getConversionUploadServiceClient();$response = 
$uploadClient->uploadClickConversions($loginCustomerId, [$clickConversion], 
true);*

The documentation 

 
has a lot of criteria that must be in place for this in order to work and 
I've been trying to make sense of them all. I'm just going to duplicate 
them here, and write down my comments.

   - The ConversionActionType is UPLOAD_CLICKS 
   

   .
  - $action->getType() returns 7 === UPLOAD_CLICKS.
   - The status 
   

 of 
   the ConversionAction is ENABLED.
  - It's enabled in the UI dashboard.
   - The ConversionAction exists in the effective conversion account of the 
   click's Google Ads account.
  - This one has me doubting - the click comes from a account that does 
  not have cross-account conversions enabled, but is still using it's own 
  conversion goals pulled from Google Analytics.
   - At the *time of the click*, conversion tracking was enabled in the 
effective 
   conversion account 
   

 of 
   the click's Google Ads account.
  - I'm not sure what this means - help?
   - Starting with v8 of the Google Ads API, the customer_id of the 
   UploadClickConversionsRequest 
   

 must 
   be the customer ID of the owner_customer of each click conversion's 
   conversion_action 
   

   .
  - The action's owner is the same as our $loginCustomerId.
   
I'm having the idea that the account from which the click originated needs 
to have cross account tracking configured for this to work properly? Could 
someone please confirm this that this is a problem?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 

Bug#964934: cookiecutter: Upgrade to version 1.7.x

[Wesley Schwengle]

Hello Vincent,

On 7/13/20 1:08 AM, Vincent Bernat wrote:

  ❦ 12 juillet 2020 16:14 -04, Wesley Schwengle:


In December 2019 version 1.7.0 was released and in April 2020 1.7.1 and
1.7.2 were released. It adds a very useful feature:

   https://cookiecutter.readthedocs.io/en/1.7.2/advanced/directories.html

I would like to make use of this. Could you bump the version the debian
unstable branch?


I am missing a recent enough version of python3-recommonmark due to bug
#955180.


It seems that bug has been resolved. Could you perhaps see if the 
version bump is now possible?


Many thanks!
Wesley

--
Wesley Schwengle
E: wes...@schwengle.net

[Mpi-forum] December MPI Forum Meeting Registration Posted / Call For Topics

[Wesley Bland via mpi-forum]

Hi all,

The registration page for the December 2021 meeting from December 6 - 9, 2021 
is now posted. Please register here:

https://forms.gle/FYUSaHSqaL1uwEEv8 

If you have topics for votes, plenaries, readings, etc., please announce them 
to this mailing list ASAP. The deadline for those announcements is November 
22nd, which is the week of Thanksgiving in the US so many folks may be on 
vacation that week.

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

[google-appengine] App Engine PHP developers… the Google Cloud team needs you!

[wesley chun]

Six weeks ago, the Google Cloud serverless team released many of the
original App Engine APIs/bundled services
<https://cloud.google.com/blog/products/serverless/support-for-app-engine-services-in-second-generation-runtimes>
for most of the second-generation runtimes (Python 3, Java 11, Go 1.12+),
and PHP 7 is next! To ensure product readiness for customer workloads,
we're seeking App Engine app developers ready to upgrade their apps to PHP
7. Here is a chart illustrating the available services (Datastore,
Memcache, Task Queues, URLfetch, Mail, Users):


Please sign-up at this form <https://forms.gle/5r4RH2kKUnWJ5EDt5> to
request access to the private preview program. After registering, we will
grant access to the private preview, its documentation, and the
announcements mailing list. For more information, see this thread
<https://reddit.com/o9wr72> in the App Engine Subreddit.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA7do5GqLRr6K9e6%3DgieByBT%3DeRj%2BxyfkfTDkjmJMz2BvA%40mail.gmail.com.

[Gimp-user] I'm a bit surprised you've never included weather effects.

[Wesley Colvin via gimp-user-list]

It’s surprising because I can find basic effects under ‘Edit & Create’ and then 
‘Add 3D Effects’ when that’s under a basic edit image program in the picture 
itself.  Do you have any plans to update GIMP to include any weather effects?

Sent from Mail for Windows

___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

[google-appengine] Re: Use of Pandas in GAE

[Wesley C (Google)]

This topic came up recently again in Reddit <http://reddit.com/pxqw75>. I 
answered there as well as this similar Q on SO 
<https://stackoverflow.com/a/69820884/305689>. The bottom line is that this 
shouldn't be an issue after 2018 when the 2nd-gen App Engine service 
launched. You don't have to use GAE flexible, and if you think you do, try 
Cloud Run 1st.

Cheers,
--Wesley

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software 
Architect & Engineer
Developer Advocate at Google 
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at 
night: Core Python <http://amzn.com/dp/0132269937>


On Wednesday, February 15, 2017 at 3:10:19 PM UTC-8 pay...@google.com wrote:

> Hey Juan,
>
> In the App Engine Standard Environment 
> <https://cloud.google.com/appengine/docs/about-the-standard-environment>, 
> the docs explain that code and libraries must be pure python 
> <https://cloud.google.com/appengine/docs/python/runtime#Python_Pure_Python>
> :
>
> All code for the Python runtime environment must be pure Python, and not 
> include any C extensions or other code that must be compiled. 
>
>
> However, for the Flexible Environment 
> <https://cloud.google.com/appengine/docs/flexible/>, you can use C 
> modules, certainly, along with any code that would run on a linux machine. 
> The code runs inside a Docker container, but it's not quite the same as 
> deploying on a Compute Engine instance and is more like programming for App 
> Engine. 
>
> You should check out the quickstart for a Flexible Environment python app 
> <https://cloud.google.com/appengine/docs/flexible/python/quickstart> and 
> then see about reading my last comment which showed a Dockerfile which 
> would allow you to install libraries on the python instance container image.
>
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Wednesday, February 15, 2017 at 8:10:48 AM UTC-5, Juan Antonio 
> Fernández Sánchez wrote:
>>
>> Hi Nick, 
>>
>> Thank you for your answer. The problem is that I would like to run these 
>> libraries in a service inside a normal GAE app, not in a container in
>> Compute Engine. 
>>
>> Thanks!
>>
>> El lunes, 13 de febrero de 2017, 20:12:12 (UTC+1), Nick (Cloud Platform 
>> Support) escribió:
>>>
>>> Hey Juan,
>>>
>>> It could be because in installing the C -based python modules locally, 
>>> pip is compiling C code for your system's architecture, which wouldn't 
>>> translate to the deployed machine. If this is the case, see if the 
>>> following works as a solution:
>>>
>>> You can write a Dockerfile for your Custom Runtime app that will install 
>>> the requirements when the container image is built, that way it'll use the 
>>> architecture of the container that will actually run the app. Here's an 
>>> example Dockerfile from our python custom runtime github repository 
>>> <https://github.com/GoogleCloudPlatform/python-runtime>:
>>>
>>> FROM gcr.io/google-appengine/python
>>>
>>> # Create a virtualenv for dependencies. This isolates these packages from
>>> # system-level packages.
>>> RUN virtualenv /env
>>>
>>> # Setting these environment variables are the same as running
>>> # source /env/bin/activate.
>>> ENV VIRTUAL_ENV /env
>>> ENV PATH /env/bin:$PATH
>>>
>>> # Copy the application's requirements.txt and run pip to install all
>>> # dependencies into the virtualenv.*ADD requirements.txt 
>>> /app/requirements.txt
>>> RUN pip install -r /app/requirements.txt*
>>>
>>> # Add the application source code.
>>> ADD . /app
>>>
>>> # Run a WSGI server to serve the application. gunicorn must be declared as
>>> # a dependency in requirements.txt.
>>> CMD gunicorn -b :$PORT main:app
>>>
>>> You can see the lines which install dependencies in bold.
>>>
>>> Let me know how that works out for you! We could see about getting this 
>>> caveat for custom runtime deployment and dependencies with c-based python 
>>> modules documented if that turns out to be the case.
>>>
>>> In order for me to be able to test and reproduce what you've seen in 
>>> future, could you also attach the requirements.txt to your reply?
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support
>>&

[google-appengine] Updates from the Google App Engine team (Fall 2021)

[wesley chun]

   or software development workflows or wish to avoid some of the constraints
   from App Engine or Cloud Functions, consider Cloud Run <http://cloud.run>
   .


Both Cloud Functions and Cloud Run have similar execution profiles, are
pay-per-use, deploy quickly, and autoscale as needed, just like what you're
used to from App Engine. Providing a more complete serverless product suite
that meets all your use cases and workloads is one of the goals of the Google
Cloud serverless <http://cloud.google.com/serverless> team.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA5wxyv%3DKKtg3Ea4d3eV3y29pPvPx6sKR8Z%3DQ%3D9DfWROgg%40mail.gmail.com.

Re: [google-appengine] Re: local development server (dev_appserver.py) not running in http://localhost:8080/

[wesley chun]

A 500 generally indicates an issue w/the application code. Can you paste
your entrypoint code here as well as any other log entries that may be
useful so people can help debug? (Less relevant: any reason for not using
Python 3?)

On Mon, Nov 1, 2021 at 3:05 AM Supratik Nag  wrote:

> Hi,
>
> I didnt install those packages in first place. Now those are installed.
> But still same thing. Firefox shows a blank page and chrome the below
> messages:
> *This page isn’t working*
>
> *localhost is currently unable to handle this request.*
> *HTTP ERROR 500*
>
> (.venvp2) snag@mx-Xfce ~> pip list
> DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020.
> Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0
> will drop support for Python 2.7 in January 2021. More details about Python
> 2 support in pip can be found at
> https://pip.pypa.io/en/latest/development/release-process/#python-2-support
> pip 21.0 will remove support for this functionality.
> PackageVersion
> -- ---
> Jinja2 2.11.3
> MarkupSafe 1.1.1
> pip20.3.4
> setuptools 44.1.1
> webapp22.5.2
> wheel  0.37.0
> (.venvp2) snag@mx-Xfce ~>
>
> Thaks.
> On Saturday, 30 October 2021 at 01:05:40 UTC+5:30 NoCommandLine wrote:
>
>>
>> Your link has a Dependencies section which lists Jinja2 and Webapp2. Did
>> you install those dependencies?
>>
>> *Note:* The Dependencies also mentions "Twitter Bootstrap" but there is
>> a folder for it which means you don't have to download it
>>
>>
>>
>>  * .* NoCommandLine *..*
>>  https://nocommandline.com
>>
>> *A GUI for Google App Engine*
>>
>> On Friday, October 29, 2021 at 4:57:37 AM UTC-5 sna...@gmail.com wrote:
>>
>>> Hello,
>>>
>>> I have followed the instructions mentioned in the below page:
>>>
>>> https://cloud.google.com/appengine/docs/standard/python/getting-started/creating-guestbook
>>>
>>> Local configuration:
>>>
>>>- Debian (10) Linux
>>>- Python 2.7.16
>>>- Google Cloud SDK 362.0.0
>>>-
>>>- cat /etc/hosts
>>>   - 127.0.0.1 localhost
>>>   - 127.0.0.1   mx-Xfce
>>>
>>> I have tried 2 running the app in 2 different ways:
>>>
>>>1. From inside Python2.7 virtualenv: *sudo
>>>/opt/google-cloud-sdk/bin/dev_appserver.py ./app.yaml*
>>>2. From inside gc sdk bin directory: *python dev_appserver.py
>>>/home//appengine-guestbook-python/app.yaml*
>>>
>>> I get below messages in terminal:
>>> INFO 2021-10-28 21:21:28,722 devappserver2.py:316] Skipping SDK
>>> update check.
>>> INFO 2021-10-28 21:21:28,832 :383] Starting API server at:
>>> http://localhost:37783
>>> INFO 2021-10-28 21:21:28,900 dispatcher.py:281] Starting module
>>> "default" running at: http://localhost:8080
>>> INFO 2021-10-28 21:21:28,900 admin_server.py:150] Starting admin
>>> server at: http://localhost:8000
>>> INFO 2021-10-28 21:21:30,910 instance.py:294] Instance PID: 2803
>>>
>>> admin server http://localhost:8000 runs fine but default
>>> http://localhost:8080 does not:
>>> http://localhost:8080 says:
>>> *This page isn’t working*
>>>
>>> *localhost is currently unable to handle this request.*
>>> *HTTP ERROR 500*
>>>
>>> Please help to understand me what am I doing wrong here.
>>>
>>> Thanks,
>>> Supratik
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/55a7a7c4-a73d-459c-9496-763317399884n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/55a7a7c4-a73d-459c-9496-763317399884n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google Cloud by day; at night...
Python training & consulting : http://CyberwebConsulting.com
"Core Python" books : http://CorePython.com
Python blog: http://wescpy.blogspot.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA4_%3DFr4yex%2BXP6gS5sHGaGNjZ9v3WmJHQK%3DbaqU3psVWA%40mail.gmail.com.

[Bug 1947977] [NEW] 'ubuntu-minimal' could not be located during release upgrade

[Wesley Tokoi]

Public bug reported:

The release upgrade from 20.04 to 21.04 kept failing because some
foreign packages were installed. After I attempted removing the said
packages - using the "Software & Updates" GUI tool, the upgrade failed
because "the essential package 'ubuntu-minimal' could not be located on
the system".

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.36
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
Date: Thu Oct 21 11:42:14 2021
InstallationDate: Installed on 2020-06-23 (484 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2021-10-21 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2021-10-21 11:41:48.737310
 Log time: 2021-10-21 11:41:53.536546
 Log time: 2021-10-21 11:42:14.033802
 Log time: 2021-10-21 11:42:15.661275
mtime.conffile..etc.update-manager.release-upgrades: 2021-10-21T10:31:39.609905

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947977

Title:
  'ubuntu-minimal' could not be located during release upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1947977/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Mpi-forum] MPI Virtual Meeting Wednesday October 20th

[Wesley Bland via mpi-forum]

The GitHub wiki seems to have an incorrect link for some reason (trying to 
resolve it). In the meantime, here’s a link to the right place:

https://github.com/mpi-forum/mpi-standard/wiki/virtual-forum-meeting-information
 


Thanks,
Wes

> On Oct 19, 2021, at 6:07 PM, Martin Schulz via mpi-forum 
>  wrote:
> 
> Hi all,
> 
> After some break, we will have a virtual meeting tomorrow/Wednesday again - 
> at the usual time, which is 10am Central Time. The zoom link is, as usual on 
> the forum website.
> 
> We have the following main agenda item (by Howard):
> Issue 511: https://github.com/mpi-forum/mpi-issues/issues/511
> Pull request 629: https://github.com/mpi-forum/mpi-standard/pull/629
> Topic: MPI_Comm_create_from_group and friend - need clarification of 
> errhandler argument
> 
> If there are any other items to add, please let me know.
> 
> Thanks!
> 
> Martin
> 
> 
> -- 
> Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems
> Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching
> Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ)
> Email: schu...@in.tum.de
> 
> 
> 
> 
> ___
> mpi-forum mailing list
> mpi-forum@lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: [racket-dev] Building Racket 8.2 on Termux/Android

[wesley bitomski]

Thanks! The Termux docs did mention that dlopen was "different":

> Symbol visibility when opening shared libraries using dlopen() works
differently. On a normal linker, when an executable linking against a
shared library libA dlopen():s another shared library libB, the symbols of
libA are exposed to libB without libB needing to link against libA
explicitly. This does not work with the Android linker, which can break
plug-in systems where the main executable dlopen():s a plug-in which does
not explicitly link against some shared libraries already linked to by the
executable. See the relevant NDK issue
<https://github.com/android-ndk/ndk/issues/201> for more information.

I have no qualms about digging around in the sources. I was sort of hoping
I'd have to do that.

Anyway, removing the noted vesdigital code just caused a failure in
ffi/unsafe, specifically in the body of get-ffi-obj*. I'll start messing
around with linker flags tomorrow.


On Tue, Oct 19, 2021, 19:37 Matthew Flatt  wrote:

> At Tue, 19 Oct 2021 16:25:33 -0700 (PDT), Wesley Bitomski wrote:
> > ffi-lib: could not load foreign library
> >   path: [all opened]
> >   system error: unknown error
>
> The "[all opened]" here means that
>
>  (define libmz (ffi-lib #f))
>
> failed in "racket/collects/openssl/mzssl.rkt".
>
> That line, plus
>
>  (define-ffi-definer define-mzscheme libmz)
>
> are leftovers that can just be removed, and I'll get rid of them.
>
> If deleting those lines is not an option for some reason, or in case
> you run into the same problem somewhere else: I think the cause of the
> underlying error is a `dlopen` call with `NULL` as its first argument.
> Unless that's just disallowed on Android, you might be able to work
> around the problem with a linker flag like `-rdynamic`.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/CAF-8S4FN5WCiwJNueWVHijzS-JQ7ZqxwyycnUvoJJhxW65iNbg%40mail.gmail.com.

[racket-dev] Building Racket 8.2 on Termux/Android

[Wesley Bitomski]

OK. I'm pretty deep in this rabbithole, but forgive me if I'm skipping some 
details.

I've spent a good portion of yesterday, and a unreasonable chunk of today, 
trying to build Racket for aarch64 on Android using Termux for the build 
environment (yes, I'm building this on the target (a phone), so no 
cross-compilation shenanigans). Recently, I've been able to reliably 
produce a working `racket` binary, but `raco` fails to build on account of 
`ffi-lib` not being able to find where the system libraries are (this is 
what I think is happening).

So, question: how to I point out where the system libs live in such that 
ffi-lib can find them?

Steps to reproduce:
0. download source bundle with prebuilt packages 
(downloads.racket-lang.org).
1. run configure from tarball root: `src/configure --enable-csonly 
--enable-sysroot=$PREFIX --prefix=$PREFIX --exec-prefix=$PREFIX`
2. `make` -- works flawlessly
3. `make install` -- errors:
make[4]: Entering directory 
'/data/data/com.termux/files/home/racket-8.2/cs/c'
/data/data/com.termux/files/usr/bin/racket -Z ../../../../../build/config 
-X "/data/data/com.termux/files/usr/share/racket/collects" -G 
"/data/data/com.termux/files/usr/etc/racket"  -Z 
../../../../../build/config  -N "raco" -l- setup 
--no-user   
  

ffi-lib: could not load foreign library
  path: [all opened] 
  system error: unknown error
  
context...: 
 
body of 
"/data/data/com.termux/files/usr/share/racket/collects/openssl/mzssl.rkt"   

body of 
"/data/data/com.termux/files/usr/share/racket/collects/setup/main.rkt"
4. Hypothesis: ffi-lib can't find libssl, located in $PREFIX/lib. `raco` 
needs this to securely communicate with package catalogs.
5. Result: no `raco`, but `racket` works just fine.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/f6f931d9-d67b-494b-ace0-c8692358c691n%40googlegroups.com.

[libreoffice-documentation] New Documentation Contributor Introduction

[Wesley Lewis]

Hello All,

Here is a quick email about my experience and interests as they relate to 
contributing to this project. I am increasingly a fan of open-source products 
and subsequently excited to finally contribute to one.

I come from a technical background, having been the sole IT employee at a small 
company in the healthcare field and a remote support agent of automated package 
management equipment. I have since transitioned to a project management role 
and am attempting to break into the technical writing field. My primary 
experience with technical writing in these roles has been the creation of user 
guides. My editing experience includes completing QC audits of my own 
documentation as well as being a (sometimes) welcome thorn in the side of my 
girlfriend and her siblings as they write various documents in pursuit of 
higher education.

As far as how I would like to contribute to this project, I intend to get 
started with editing documentation. I am afraid I would not yet call myself a 
proficient user of LibreOffice or the tools used to upkeep its documentation, 
but as that changes, I will complete reviewing and writings tasks.

Once again, looking forward to working with you all! In the spirit of those 
awkward corporate icebreakers, feel free to share what your favorite 
(non-Libre) open source project is.

Best Regards,

Wesley Lewis
-- 
To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Bug#996170: linux: FTBFS if bpftool detects clang-bpf-co-re

[Nathaniel Wesley Filardo]

Source: linux
Version: 5.10.70-1
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Attempting to build kernel packages using the machinery of
https://salsa.debian.org/kernel-team/linux.git on a host where the
"clang-bpf-co-re" test performed in the tools/bpf/bpftool directory passes will
fail, as the build will attempt to bootstrap the BTF vmlinux.h header
(confusingly, from the kernel in /boot/vmlinux-$(uname -r), as it can't find
anything else); for example:

> /dozer/scratch/nwf/tmp/linux/debian-kernel-linux/debian/build/build-tools/tools/bpf/bpftool/bpftool-bootstrap
>  btf dump file /boot/vmlinux-5.10.0-0.bpo.5-powerpc64le format c > 
> /dozer/scratch/nwf/tmp/linux/debian-kernel-linux/debian/build/build-tools/tools/bpf/bpftool/vmlinux.h
> Error: failed to load BTF from /boot/vmlinux-5.10.0-0.bpo.5-powerpc64le: No 
> such file or directory

The official builders do not pass this test (see, e.g.
https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64el=5.14.9-2=1633298169=0
where the logs say "clang-bpf-co-re: [ OFF ]"), so I believe the correct answer
on Debian systems is to disable the test (making it appear as if it fails)
regardless of the host environment.  The patch below does exactly that and
allows me to build the kernel packages.

Cheers,
--nwf;

--- a/tools/bpf/bpftool/Makefile2021-10-11 01:52:26.625003863 +0100
+++ b/tools/bpf/bpftool/Makefile2021-10-11 03:38:54.006277839 +0100
@@ -62,8 +62,7 @@
 LLVM_STRIP ?= llvm-strip
 
 FEATURE_USER = .bpftool
-FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap \
-   clang-bpf-co-re
+FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap
 FEATURE_DISPLAY = libbfd disassembler-four-args zlib libcap \
clang-bpf-co-re
 

Bug#996170: linux: FTBFS if bpftool detects clang-bpf-co-re

[Nathaniel Wesley Filardo]

Source: linux
Version: 5.10.70-1
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Attempting to build kernel packages using the machinery of
https://salsa.debian.org/kernel-team/linux.git on a host where the
"clang-bpf-co-re" test performed in the tools/bpf/bpftool directory passes will
fail, as the build will attempt to bootstrap the BTF vmlinux.h header
(confusingly, from the kernel in /boot/vmlinux-$(uname -r), as it can't find
anything else); for example:

> /dozer/scratch/nwf/tmp/linux/debian-kernel-linux/debian/build/build-tools/tools/bpf/bpftool/bpftool-bootstrap
>  btf dump file /boot/vmlinux-5.10.0-0.bpo.5-powerpc64le format c > 
> /dozer/scratch/nwf/tmp/linux/debian-kernel-linux/debian/build/build-tools/tools/bpf/bpftool/vmlinux.h
> Error: failed to load BTF from /boot/vmlinux-5.10.0-0.bpo.5-powerpc64le: No 
> such file or directory

The official builders do not pass this test (see, e.g.
https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64el=5.14.9-2=1633298169=0
where the logs say "clang-bpf-co-re: [ OFF ]"), so I believe the correct answer
on Debian systems is to disable the test (making it appear as if it fails)
regardless of the host environment.  The patch below does exactly that and
allows me to build the kernel packages.

Cheers,
--nwf;

--- a/tools/bpf/bpftool/Makefile2021-10-11 01:52:26.625003863 +0100
+++ b/tools/bpf/bpftool/Makefile2021-10-11 03:38:54.006277839 +0100
@@ -62,8 +62,7 @@
 LLVM_STRIP ?= llvm-strip
 
 FEATURE_USER = .bpftool
-FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap \
-   clang-bpf-co-re
+FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap
 FEATURE_DISPLAY = libbfd disassembler-four-args zlib libcap \
clang-bpf-co-re
 

Bug#996170: linux: FTBFS if bpftool detects clang-bpf-co-re

[Nathaniel Wesley Filardo]

Source: linux
Version: 5.10.70-1
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Attempting to build kernel packages using the machinery of
https://salsa.debian.org/kernel-team/linux.git on a host where the
"clang-bpf-co-re" test performed in the tools/bpf/bpftool directory passes will
fail, as the build will attempt to bootstrap the BTF vmlinux.h header
(confusingly, from the kernel in /boot/vmlinux-$(uname -r), as it can't find
anything else); for example:

> /dozer/scratch/nwf/tmp/linux/debian-kernel-linux/debian/build/build-tools/tools/bpf/bpftool/bpftool-bootstrap
>  btf dump file /boot/vmlinux-5.10.0-0.bpo.5-powerpc64le format c > 
> /dozer/scratch/nwf/tmp/linux/debian-kernel-linux/debian/build/build-tools/tools/bpf/bpftool/vmlinux.h
> Error: failed to load BTF from /boot/vmlinux-5.10.0-0.bpo.5-powerpc64le: No 
> such file or directory

The official builders do not pass this test (see, e.g.
https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64el=5.14.9-2=1633298169=0
where the logs say "clang-bpf-co-re: [ OFF ]"), so I believe the correct answer
on Debian systems is to disable the test (making it appear as if it fails)
regardless of the host environment.  The patch below does exactly that and
allows me to build the kernel packages.

Cheers,
--nwf;

--- a/tools/bpf/bpftool/Makefile2021-10-11 01:52:26.625003863 +0100
+++ b/tools/bpf/bpftool/Makefile2021-10-11 03:38:54.006277839 +0100
@@ -62,8 +62,7 @@
 LLVM_STRIP ?= llvm-strip
 
 FEATURE_USER = .bpftool
-FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap \
-   clang-bpf-co-re
+FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap
 FEATURE_DISPLAY = libbfd disassembler-four-args zlib libcap \
clang-bpf-co-re
 

Re: [google-appengine] Re: Flask deployment

[wesley chun]

I also 2nd the notion of searching on SO as this question has likely
already been asked by at least a dozen other developers. I'd tag
google-app-engine , google-cloud-sql and perhaps google-cloud-platform for
starters. I also suggest looking at this page in the App Engine docs
<https://cloud.google.com/sql/docs/mysql/connect-app-engine-standard> which
was made specifically for Cloud SQL usage, and in particular, if you're not
using a public IP, you need to setup Serverless VPC Access.

Cheers,
--Wesley

On Tue, Oct 5, 2021 at 8:37 AM NoCommandLine 
wrote:

> Hi,
>
> This type of question is better handled on Stackoverflow
> <https://stackoverflow.com/>. Just tag it with Google App Engine and any
> other relevant tags.
>
> *.* NoCommandLine *..*
>  https://nocommandline.com
>
> *A GUI for Google App Engine*
>
> On Sunday, August 29, 2021 at 1:13:41 PM UTC-7 samuel.t...@gmail.com
> wrote:
>
>> Hi everyone,
>>
>> I am creating a website using Flask. It is currently working on my local
>> server. Locally, my cloud SQL mysql database is connected to my project and
>> there is no problem. (I authorized my IP to get it to work). However, I am
>> getting a 500 internal server error when I deploy my app.
>>
>> Looking at the logs, I can see that I am getting errors connecting to the
>> database. I am probably not doing it correctly for production
>>
>> The logged error is the following :
>>
>> "Traceback (most recent call last): File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/flask/app.py",
>> line 2070, in wsgi_app response = self.full_dispatch_request() File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/flask/app.py",
>> line 1515, in full_dispatch_request rv = self.handle_user_exception(e) File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/flask/app.py",
>> line 1513, in full_dispatch_request rv = self.dispatch_request() File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/flask/app.py",
>> line 1499, in dispatch_request return
>> self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args) File
>> "/srv/main.py", line 181, in home for item in
>> Blog_Post.query.order_by(Blog_Post.id.desc()).limit(NUMBER_RESULTS): File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/orm/query.py",
>> line 2840, in __iter__ return self._iter().__iter__() File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/orm/query.py",
>> line 2847, in _iter result = self.session.execute( File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/orm/session.py",
>> line 1688, in execute conn = self._connection_for_bind(bind) File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/orm/session.py",
>> line 1529, in _connection_for_bind return
>> self._transaction._connection_for_bind( File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/orm/session.py",
>> line 747, in _connection_for_bind conn = bind.connect() File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/engine/base.py",
>> line 3166, in connect return self._connection_cls(self,
>> close_with_result=close_with_result) File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/engine/base.py",
>> line 96, in __init__ else engine.raw_connection() File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/engine/base.py",
>> line 3245, in raw_connection return
>> self._wrap_pool_connect(self.pool.connect, _connection) File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/engine/base.py",
>> line 3215, in _wrap_pool_connect
>> Connection._handle_dbapi_exception_noconnection( File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/engine/base.py",
>> line 2069, in _handle_dbapi_exception_noconnection util.raise_( File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/util/compat.py",
>> line 207, in raise_ raise exception File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/engine/base.py",
>> line 3212, in _wrap_pool_connect return fn() File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/pool/base.py",
>> line 307, in connect return _ConnectionFairy._checkout(self) File
>> "/layers/google.python.pip/pip/lib/python3.9/site-packages/sqlalchemy/pool/b

Re: [Interest] Qt 6 Universal binaries for Mac OS?

[Wesley Krasko]

So I just used the example multimedia project in Qt Creator and added the
same line, it fails the same way.
Before I go filing a bug report though, could this be because I'm running
Big Sur in a VM? (Parallels)
This is what I've been doing to compile and run the app without that line
just fine (using 6.2.0). I must because I can't yet upgrade my dev machine
until I know this works (Intel Macbook running Catalina, because with Big
Sur comes Xcode 12+, I must keep this machine as is so we can still compile
and release our app against 5.15.2)
If that is suspect I guess I could dual boot instead but I really didn't
want to do that because it would only be until we can validate we can build
these new universal binaries going forward, then I'd just upgrade my main
OS.

On Thu, Sep 30, 2021 at 1:44 PM Tor Arne Vestbø 
wrote:

> Hi,
>
> Please file a bug with a sample project that reproduces this issue, thanks!
>
> tor arne
>
> On 30 Sep 2021, at 20:28, Wesley Krasko  wrote:
>
> Thanks. So I added this to my pro file for macos:
>
> QMAKE_APPLE_DEVICE_ARCHS="x86_64 arm64"
>
>
> It looked like it was going to build fine and then I got 1 build error for my 
> app :(
>
>
> It says:
>
> cannot use 'c++-cpp-output' output with multiple -arch options
>
>
> I searched that and fine results for "output with multiple" other things, but 
> not -arch. Ideas?
>
>
> On Wed, Sep 22, 2021 at 1:44 PM Croitor Alexandru 
> wrote:
>
>> Hi,
>>
>> Seems like the doc snapshots haven't been indexed by search engines yet
>> (from my results at least).
>>
>> See https://doc-snapshots.qt.io/qt6-6.2/macos.html#architectures
>>
>> You can specify the relevant options in Creator's Project pane for either
>> build system.
>>
>> On Wed, Sep 22, 2021 at 10:38 PM Wesley Krasko 
>> wrote:
>>
>>> Hello all. We have been waiting for Qt 6.2 for universal binary support.
>>> I have 6.2 RC and have our app building and running fine in Creator (for
>>> Intel on an Intel machine, Big Sur, Xcode 12).
>>> Does anyone know how to then create the universal binaries? I have found
>>> documentation on building Qt for both architectures, but that's irrelevant
>>> as we use the pre-compiled Qt downloaded through the maintenance tool.
>>> Our current process has been to dev/build the app in Creator (we do not
>>> use Xcode, find Creator much easier and more user friendly). Once done, I
>>> copy the bundle somewhere, run macdeployqt on it, sign it, then
>>> notarize it. Of course there's some details in between but that's
>>> essentially it, I have a pkg to distribute.
>>> I'm not seeing in Creator now how to create a universal binary, or
>>> finding any docs.
>>> Thanks!
>>>
>>> --
>>> Wes Krasko
>>> www.worldwidewes.com
>>> www.kraskofamily.com
>>> "Stay away from negative people. They have a problem for every solution."
>>>
>>>
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> https://lists.qt-project.org/listinfo/interest
>>>
>>
>
> --
> Wes Krasko
> www.worldwidewes.com
> www.kraskofamily.com
> "Stay away from negative people. They have a problem for every solution."
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
>
>

-- 
Wes Krasko
www.worldwidewes.com
www.kraskofamily.com
"Stay away from negative people. They have a problem for every solution."
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 6 Universal binaries for Mac OS?

[Wesley Krasko]

Thanks. So I added this to my pro file for macos:

QMAKE_APPLE_DEVICE_ARCHS="x86_64 arm64"


It looked like it was going to build fine and then I got 1 build error
for my app :(


It says:

cannot use 'c++-cpp-output' output with multiple -arch options


I searched that and fine results for "output with multiple" other
things, but not -arch. Ideas?


On Wed, Sep 22, 2021 at 1:44 PM Croitor Alexandru 
wrote:

> Hi,
>
> Seems like the doc snapshots haven't been indexed by search engines yet
> (from my results at least).
>
> See https://doc-snapshots.qt.io/qt6-6.2/macos.html#architectures
>
> You can specify the relevant options in Creator's Project pane for either
> build system.
>
> On Wed, Sep 22, 2021 at 10:38 PM Wesley Krasko  wrote:
>
>> Hello all. We have been waiting for Qt 6.2 for universal binary support.
>> I have 6.2 RC and have our app building and running fine in Creator (for
>> Intel on an Intel machine, Big Sur, Xcode 12).
>> Does anyone know how to then create the universal binaries? I have found
>> documentation on building Qt for both architectures, but that's irrelevant
>> as we use the pre-compiled Qt downloaded through the maintenance tool.
>> Our current process has been to dev/build the app in Creator (we do not
>> use Xcode, find Creator much easier and more user friendly). Once done, I
>> copy the bundle somewhere, run macdeployqt on it, sign it, then
>> notarize it. Of course there's some details in between but that's
>> essentially it, I have a pkg to distribute.
>> I'm not seeing in Creator now how to create a universal binary, or
>> finding any docs.
>> Thanks!
>>
>> --
>> Wes Krasko
>> www.worldwidewes.com
>> www.kraskofamily.com
>> "Stay away from negative people. They have a problem for every solution."
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>>
>

-- 
Wes Krasko
www.worldwidewes.com
www.kraskofamily.com
"Stay away from negative people. They have a problem for every solution."
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [google-appengine] Google Translate API & Permissions

[wesley chun]

All, I'm happy to announce that I've finally published the blog post
<http://developers.googleblog.com/2021/09/exploring-serverless-with-nebulous-app.html?utm_source=blog_medium=partner_campaign=CDR_wes_aap-serverless_nebserv_sms_201028>
(Tweet
<http://twitter.com/googledevs/status/1442903087497183233?utm_source=twitter_medium=unpaidsoc_campaign=CDR_wes_aap-serverless_nebserv_sms_201028_content=->
& FB post
<http://facebook.com/967415219957038/posts/456979724079?utm_source=facebook_medium=unpaidsoc_campaign=CDR_wes_aap-serverless_nebserv_sms_201028_content=->
for sharing) I promised. Summarizing the 2 things that would've improved
Joshua's initial experience:

   1. Awareness of the *Google Cloud client libraries* (he used the Google
   APIs client libraries, lower-level and somewhat more challenging) — I'm
   working on a follow-up post explaining why we have two different types of
   client libraries and when you'd use one vs. the other.
   2. Awareness of *default service accounts* — these exist for all our
   serverless platforms and come pre-baked w/enough IAM permissions to get a
   prototype working; that gives you more time to research specific IAM
   roles/perms the app will need when you get closer to production.

The point is to make products that people can get started on without much
friction but also allow for more sophisticated usage as needed. I've also
provided Joshua's feedback directly to folks on our serverless platform
teams. Anyway, hope this helps and please let me know if you have any
questions; also reshare as desired to your developer social networks! (BTW,
thx for the kind words Eric!)

Cheers,
--Wesley

On Sat, May 8, 2021 at 6:09 AM Eric Hardy  wrote:

> Thank you Wesley.  I appreciate your efforts.  I want to spend more time
> site building than wrestling with a cloud platform.  I will follow the
> above mentioned links to nut this out.
>
> On Sat, May 8, 2021 at 9:20 AM wesley chun  wrote:
>
>> @Joshua: your inquiry inspired me to do some research into this issue
>> over the past few months resulting in the following:
>>
>> 1. *Use Cloud client libraries:* yep, your experience was not fun for
>> any developer looking to use a Cloud API (whether App Engine or a simple
>> cmd-line script). One solution is to avoid the Google APIs client library
>> <https://developers.google.com/api-client-library> and use the Google
>> Cloud client libraries
>> <http://cloud.google.com/apis/docs/cloud-client-libraries> instead, and
>> in your case just the one for Cloud Translation
>> (basic/v2
>> <https://cloud.google.com/translate/docs/reference/libraries/v2/python> or
>> advanced/v3
>> <https://cloud.google.com/translate/docs/reference/libraries/v3/python>).
>> (I'm also working on a blog post to outline the differences between these 
>> *platform
>> vs. product* client libraries, so stay tuned for that.) With the Cloud
>> Translation client library (which hides a lot of low-level details), your
>> code sample can be as simple as:
>>
>> from __future__ import print_function
>> import google.auth
>> from google.cloud import translate
>>
>> TRANSLATE = translate.TranslationServiceClient()
>> _, PROJECT_ID = google.auth.default()
>> PARENT = 'projects/{}'.format(PROJECT_ID)
>> TARGET_LANG = 'es'
>> TEXT = 'Hello world'
>> DATA = {
>> 'parent': PARENT,
>> 'contents': [TEXT],
>> 'target_language_code': TARGET_LANG,
>> }
>> try:# Python 3/advanced/v3
>> rsp = TRANSLATE.translate_text(request=DATA)
>> except TypeError:   # Python 2/basic/v2
>> rsp = TRANSLATE.translate_text(**DATA)
>> print(TEXT, '=', rsp.translations[0].translated_text)
>>
>> It works in Python 2 and 3 without any modification:
>>
>> $ python2 translate_demo2.py
>> Hello world = Hola Mundo
>> $ python3 translate_demo2.py
>> Hello world = Hola Mundo
>>
>> You should be able to just drop something like this right into your App
>> Engine code (plus the necessary stuff in app.yaml and requirements.txt).
>> App Engine comes with a default service account
>> <https://cloud.google.com/appengine/docs/standard/python/service-account>,
>> so you don't need to mess with all you did unless you need to (create a
>> separate service account and public/private key-pair) for other reasons. To
>> run this script *locally* (as I did above), you *do* need to do that
>> (create a service acct & keypair, download the JSON credentials file to
>> your local system, then point GOOGLE_APPLICATION_CREDENTIALS to it), but
>> not on App Engine (nor Cloud Functions nor Cloud Run) as *all 3* have
>> de

[Interest] Qt 6 Universal binaries for Mac OS?

[Wesley Krasko]

Hello all. We have been waiting for Qt 6.2 for universal binary support.
I have 6.2 RC and have our app building and running fine in Creator (for
Intel on an Intel machine, Big Sur, Xcode 12).
Does anyone know how to then create the universal binaries? I have found
documentation on building Qt for both architectures, but that's irrelevant
as we use the pre-compiled Qt downloaded through the maintenance tool.
Our current process has been to dev/build the app in Creator (we do not
use Xcode, find Creator much easier and more user friendly). Once done, I
copy the bundle somewhere, run macdeployqt on it, sign it, then
notarize it. Of course there's some details in between but that's
essentially it, I have a pkg to distribute.
I'm not seeing in Creator now how to create a universal binary, or finding
any docs.
Thanks!

-- 
Wes Krasko
www.worldwidewes.com
www.kraskofamily.com
"Stay away from negative people. They have a problem for every solution."
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[ovirt-users] Re: I'm in trouble....

[Wesley Stewart]

I appreciate the quick replies.  Yes very basic.  Single host/node with NFS
and local storage.

I will try to reinstall the host and import.  I haven't had to do this yet!

On Sat, Sep 18, 2021, 5:26 PM Jayme  wrote:

> It sounds like your setup is fairly basic. For quickness I’d personally
> just reinstall engine and import storage domains from nfs sever then import
> the vms. you can restore the hosted engine if you have a backup of it made
> by the proper hosted engine backup tool.
>
> On Sat, Sep 18, 2021 at 6:21 PM Wesley Stewart 
> wrote:
>
>> I believe I should have the dump from the initial engine-setup.  Can that
>> be used?
>>
>> Also, I'm only running about 8 vms and need to start over for 4.4.  Would
>> it be easier to just reinstall and import the disks?
>>
>>
>>
>> On Sat, Sep 18, 2021, 5:11 PM Jayme  wrote:
>>
>>> Do you have a backup of the hosted engine that you can restore? If your
>>> vms are on nfs mounts you should be able to readd the storage domain and
>>> import the vms
>>>
>>> On Sat, Sep 18, 2021 at 4:26 PM Wesley Stewart 
>>> wrote:
>>>
>>>> Luckily this is for a home lab and nothing critical is lost.  However I
>>>> was trying to change the subnet my host was on.  And I found out that you
>>>> cant do that.  So I reverted back but my hosted engine wasnt happy about my
>>>> NFS mounts.
>>>>
>>>> so I did a engine-cleanup and an engine-setup.  Went through the
>>>> prompts and thought nothing of it.  I logged back into ovirt, and
>>>> everything looks like it was a brand new install.  No VMs or anything.  I
>>>> believe I have a fairly recent backup somewhere... trying to track that
>>>> down, but it's not looking good.
>>>>
>>>> Currently running 4.3.10.  I have been planning out my 4.4 upgrade
>>>> anyways.  I would prefer to not start from scratch... but if I do it is not
>>>> the end of the world, will just take a lot more time.
>>>>
>>>> Looking for some guidance! Thank you.
>>>> ___
>>>> Users mailing list -- users@ovirt.org
>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BKJLN25CGI2U4LIO7HOEJQJVRE7CA3JN/
>>>>
>>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WZD3EEHZLBNVDSUD46J6CLOS4JSCTKMP/

[ovirt-users] Re: I'm in trouble....

[Wesley Stewart]

I believe I should have the dump from the initial engine-setup.  Can that
be used?

Also, I'm only running about 8 vms and need to start over for 4.4.  Would
it be easier to just reinstall and import the disks?



On Sat, Sep 18, 2021, 5:11 PM Jayme  wrote:

> Do you have a backup of the hosted engine that you can restore? If your
> vms are on nfs mounts you should be able to readd the storage domain and
> import the vms
>
> On Sat, Sep 18, 2021 at 4:26 PM Wesley Stewart 
> wrote:
>
>> Luckily this is for a home lab and nothing critical is lost.  However I
>> was trying to change the subnet my host was on.  And I found out that you
>> cant do that.  So I reverted back but my hosted engine wasnt happy about my
>> NFS mounts.
>>
>> so I did a engine-cleanup and an engine-setup.  Went through the prompts
>> and thought nothing of it.  I logged back into ovirt, and everything looks
>> like it was a brand new install.  No VMs or anything.  I believe I have a
>> fairly recent backup somewhere... trying to track that down, but it's not
>> looking good.
>>
>> Currently running 4.3.10.  I have been planning out my 4.4 upgrade
>> anyways.  I would prefer to not start from scratch... but if I do it is not
>> the end of the world, will just take a lot more time.
>>
>> Looking for some guidance! Thank you.
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BKJLN25CGI2U4LIO7HOEJQJVRE7CA3JN/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6XMRWXLBYQDHORTL7APQZ2CR4CXL333C/

[ovirt-users] I'm in trouble....

[Wesley Stewart]

Luckily this is for a home lab and nothing critical is lost.  However I was
trying to change the subnet my host was on.  And I found out that you
cant do that.  So I reverted back but my hosted engine wasnt happy about my
NFS mounts.

so I did a engine-cleanup and an engine-setup.  Went through the prompts
and thought nothing of it.  I logged back into ovirt, and everything looks
like it was a brand new install.  No VMs or anything.  I believe I have a
fairly recent backup somewhere... trying to track that down, but it's not
looking good.

Currently running 4.3.10.  I have been planning out my 4.4 upgrade
anyways.  I would prefer to not start from scratch... but if I do it is not
the end of the world, will just take a lot more time.

Looking for some guidance! Thank you.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BKJLN25CGI2U4LIO7HOEJQJVRE7CA3JN/

Re: [Interest] Qt 6.2.0 RC still missing basic QMediaPlayer calls?

[Wesley Krasko]

It works. I figured it out. The documentation for QMediaPlayer 6.2 is
incorrect. I think Qt just copied it from 5.15 and didn't update it. It
still shows using QMediaPlayer the old way when in fact stuff was
broken out into QAudioOutput, QVideoOutput, etc. So now, you must first get
the QAudioOutput of the QMediaPlayer and then you can do setVolume,
setMuted, etc. The docs need updating.
This is no longer how it works:
https://doc-snapshots.qt.io/qt6-6.2/qmediaplayer.html#details

On Sat, Sep 18, 2021 at 5:51 AM Alexander Dyagilev 
wrote:

> Hello,
>
> It seems you just did not install it. See Additional modules section in
> the online installer.
>
> Works fine for me.
> On 9/17/2021 1:45 AM, Wesley Krasko wrote:
>
> Hi. We have been closely monitoring Qt 6.2 releases as we will need to
> create unified builds of our apps ASAP.
> For the longest time the thing that stopped us from compiling has been
> QMediaPlayer missing basic functions. For example, setVolume and setMuted.
> I have been grabbing updates as they come out thinking at some point they
> wouldn't be, since the documentation for QMediaPlayer 6 still shows these
> function calls. This is concerning that they are still missing in the RC.
> Can anyone shed some light on this?
> I also get "no type named 'State'" errors but I see that has just changed
> to another name so that's no big deal. But, it is also missing volume()
>
> --
> Wes Krasko
> www.worldwidewes.com
> www.kraskofamily.com
> "Stay away from negative people. They have a problem for every solution."
>
>
> ___
> Interest mailing 
> listInterest@qt-project.orghttps://lists.qt-project.org/listinfo/interest
>
>

-- 
Wes Krasko
www.worldwidewes.com
www.kraskofamily.com
"Stay away from negative people. They have a problem for every solution."
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Qt 6.2.0 RC still missing basic QMediaPlayer calls?

[Wesley Krasko]

Hi. We have been closely monitoring Qt 6.2 releases as we will need to
create unified builds of our apps ASAP.
For the longest time the thing that stopped us from compiling has been
QMediaPlayer missing basic functions. For example, setVolume and setMuted.
I have been grabbing updates as they come out thinking at some point they
wouldn't be, since the documentation for QMediaPlayer 6 still shows these
function calls. This is concerning that they are still missing in the RC.
Can anyone shed some light on this?
I also get "no type named 'State'" errors but I see that has just changed
to another name so that's no big deal. But, it is also missing volume()

-- 
Wes Krasko
www.worldwidewes.com
www.kraskofamily.com
"Stay away from negative people. They have a problem for every solution."
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Mpi-forum] EuroMPI Starts Today, MPI-Forum starts Thursday, Joint Session on Wednesday

[Wesley Bland via mpi-forum]

I just want to remind people one last time to register for the MPI Forum that 
begins tomorrow (Thursday). There’s still a few more orgs that I’m expecting to 
attend, but haven’t heard from. Remember that you must have registered and 
attended the meeting before the first voting block, which is scheduled for 
Thursday at 12:30pm US Central. If you register and the join the meeting right 
at that moment, so please do so ASAP.

Logistical information is available on the website: 
https://www.mpi-forum.org/meetings/2021/09/logistics 


Thanks,
Wes

> On Sep 6, 2021, at 11:34 PM, Martin Schulz via mpi-forum 
>  wrote:
> 
> Hi all,
> 
> Just as a quick reminder, EuroMPI and the MPI Forum will be this week, with a 
> joint session between the two on Wednesday (more below). If you haven't 
> registered, yet, please do so at https://www.eurompi21.lrz.de/ - registration 
> is free!
> 
> 
> EuroMPI 2021 
> 
> 
> EuroMPI 2021 starts today with a keynote by Olga Pearce and several paper 
> presentations plus a poster/open discussion session. Tomorrow (Wednesday) we 
> will have two topical sessions on RMA and MPI Sessions where we will look 
> into the future of these two important concepts - more on this below. The 
> conference will run 9am to 1pm US CT each day.
> 
> 
> September MPI Forum
> === 
> 
> Starting Thursday we will transition into the MPI Forum starting on Thursday 
> with plenary discussions, mainly focusing on MPI 4.1 - the agenda is at 
> https://www.mpi-forum.org/meetings/2021/09/agenda. The forum will run 9am to 
> 1pm US CT each day.
> 
> 
> Joint Session on Wendesday
> ===
> 
> In the spirit of bringing EuroMPI closer to the activities of the MPI Forum, 
> we will use the second day of EuroMPI to discuss perspectives on two 
> important topics for MPI 5.0: RMA and Sessions - for each topic we will have 
> a separate session starting with a vision talk by Bill Gropp for RMA and Dan 
> Holmes for Session, followed by three paper presentations on these topics, 
> and then an interactive panel discussion. While officially part of EuroMPI, 
> this will also guide discussions in the forum - therefore, we also invite all 
> Forum participants to join us in this session (please register for the 
> conference to get the link - it is free!)
> 
> 
> Looking forward to seeing/hearing you all this week!
> 
> Best regards,
> 
> Martin
> 
> 
> 
> -- 
> Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems
> Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching
> Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ)
> Email: schu...@in.tum.de
> 
> 
> 
> 
> ___
> mpi-forum mailing list
> mpi-forum@lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: [Mpi-forum] MPI Virtual Meeting / EuroMPI / MPI-Forum September Meeting

[Wesley Bland via mpi-forum]

Hi all,

I want to remind everyone to register for next week’s meeting and/or 
conference. As of right now, we still don’t have enough orgs registered to meet 
quorum (need 25 IMOVE orgs and currently have 21). If you’re not sure if you 
registered, you can find the list of everyone I have here: 
https://www.mpi-forum.org/meetings/2021/09/attendance 
<https://www.mpi-forum.org/meetings/2021/09/attendance>.

Thanks,
Wes

> On Aug 24, 2021, at 4:37 PM, Martin Schulz via mpi-forum 
>  wrote:
> 
> Hi all,
> 
> Just a few reminders:
> 
> - We have our next MPI Forum Virtual Meeting tomorrow (Wednesday 8/25) at the 
> usual time of 10am US CT (link on github). The agenda is to continue 
> discussions on changes for MPI 4.1. In particular, Bill is planning to 
> discuss a few items from his editorial pass(es).
> 
> - EuroMPI registration is open and registration is free. As last year, the 
> conference is virtual.  I think we have an exciting program over the two 
> days, September 7th and 8th (from 9am US CT to 1pm US CT), which will also 
> bleed over to the MPI forum with RMA and Sessions discussions on Day 2. More 
> information on https://www.eurompi21.lrz.de/. Please help spread the word.
> 
> - The MPI-Forum on September 9th and 10th (also virtual, also 9am US CT to 
> 1pm US CT) is getting close and this Thursday is the two week deadline for 
> plenary announcements (readings, erratas, regular ballots). I already saw 
> some going around - if there are any others, please post them to the email 
> list. If there are any other items you would like to see on the agenda, 
> please let me know as well.
> 
> - We have a combined registration for both events (thanks to Wesley!), which 
> is at https://forms.gle/vJ32yJqNxe2DCUxC7 - if you plan on attending either 
> one, please register as soon as possible.
> 
> Thanks!
> 
> Martin
> 
> 
> -- 
> Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems
> Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching
> Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ)
> Email: schu...@in.tum.de
> 
> 
> 
> 
> 
> ___
> mpi-forum mailing list
> mpi-forum@lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

[Mpi-forum] September Meeting / EuroMPI Registration Now Open & Send Reading/Vote Announcements

[Wesley Bland via mpi-forum]

Hi all,

The registration link for the upcoming meeting is finally posted.

https://forms.gle/vJ32yJqNxe2DCUxC7 

This link is used for both the MPI Forum and the EuroMPI conference (if you’d 
like to attend either/both). Please go ahead and register.

If you have any reading/voting announcements for the meeting, please send those 
to the list as well. Because the meeting will only take place on Thursday and 
Friday, the announcements are due this Thursday.

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: [Emc-users] Missing Features in LCNC for FFF/FDM Printers

[Sven Wesley]

Den mån 26 juli 2021 kl 01:35 skrev :

> There are addins now that post process gcode to convert line segments to
> G2/G3.
>
>
Yes! ArcWelder is extremely good at this! Can be used as a console app or
as a plugin directly in OctoPrint if you fancy that. I use it all the time
and not only will you get smaller files, the printer operates so much
smoother and at a faster pace.
Highly recommended!
https://github.com/FormerLurker/ArcWelderLib
https://github.com/FormerLurker/ArcWelderPlugin

Regards,
Sven

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Mpi-forum] Reading announcement for issue 511

[Wesley Bland via mpi-forum]

Just to clarify, this is marked as an errata reading. So it will be a reading 
and a vote. Is that correct?

Thanks,
Wes

> On Aug 17, 2021, at 3:40 PM, Pritchard Jr., Howard via mpi-forum 
>  wrote:
> 
> Hello All,
>  
> For the upcoming September MPI forum, I’d like to announce a reading for a 
> proposed change for the MPI 4.1 standard to clarify the error handler 
> argument to MPI_Comm_create_from_group and MPI_Intercomm_create_from_groups.
>  
> See issue
> https://github.com/mpi-forum/mpi-issues/issues/511 
> 
>  
> and associated pull request
>  
> https://github.com/mpi-forum/mpi-standard/pull/610 
> 
>  
> Thanks,
>  
> Howard
> 
> —
>  
> 
> Howard Pritchard
> Research Scientist
> HPC-ENV
>  
> Los Alamos National Laboratory
> howa...@lanl.gov 
>  
>   
>  
> 
>  
>  
>  
> ___
> mpi-forum mailing list
> mpi-forum@lists.mpi-forum.org 
> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum 
> 
___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

[ceph-users] Re: ceph osd continously fails

[Wesley Dillingham]

Can you send the results of "ceph daemon osd.0 status" and maybe do that
for a couple of osd ids ? You may need to target ones which are currently
running.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Wed, Aug 11, 2021 at 9:51 AM Amudhan P  wrote:

> Hi,
>
> Below are the logs in one of the failed OSD.
>
> Aug 11 16:55:48 bash[27152]: debug-20> 2021-08-11T11:25:47.433+
> 7fbf3b819700  3 osd.12 6697 handle_osd_map epochs [6696,6697], i have 6697,
> src has [
> Aug 11 16:55:48 bash[27152]: debug-19> 2021-08-11T11:25:47.433+
> 7fbf32006700  5 osd.12 pg_epoch: 6697 pg[2.14b( v 6312'183564
> (4460'174466,6312'18356
> Aug 11 16:55:48 bash[27152]: debug-18> 2021-08-11T11:25:47.433+
> 7fbf32006700  5 osd.12 pg_epoch: 6697 pg[2.14b( v 6312'183564
> (4460'174466,6312'18356
> Aug 11 16:55:48 bash[27152]: debug-17> 2021-08-11T11:25:47.433+
> 7fbf32006700  5 osd.12 pg_epoch: 6697 pg[2.14b( v 6312'183564
> (4460'174466,6312'18356
> Aug 11 16:55:48 bash[27152]: debug-16> 2021-08-11T11:25:47.433+
> 7fbf32006700  5 osd.12 pg_epoch: 6697 pg[2.14b( v 6312'183564
> (4460'174466,6312'18356
> Aug 11 16:55:48 bash[27152]: debug-15> 2021-08-11T11:25:47.441+
> 7fbf3b819700  3 osd.12 6697 handle_osd_map epochs [6696,6697], i have 6697,
> src has [
> Aug 11 16:55:48 bash[27152]: debug-14> 2021-08-11T11:25:47.561+
> 7fbf3a817700  2 osd.12 6697 ms_handle_refused con 0x563b53a3cc00 session
> 0x563b51aecb
> Aug 11 16:55:48 bash[27152]: debug-13> 2021-08-11T11:25:47.561+
> 7fbf3a817700 10 monclient: _send_mon_message to mon.strg-node2 at v2:
> 10.0.103.2:3300/
> Aug 11 16:55:48 bash[27152]: debug-12> 2021-08-11T11:25:47.565+
> 7fbf3b819700  2 osd.12 6697 ms_handle_refused con 0x563b66226000 session 0
> Aug 11 16:55:48 bash[27152]: debug-11> 2021-08-11T11:25:47.581+
> 7fbf3b819700  2 osd.12 6697 ms_handle_refused con 0x563b66227c00 session 0
> Aug 11 16:55:48 bash[27152]: debug-10> 2021-08-11T11:25:47.581+
> 7fbf4e0ae700 10 monclient: get_auth_request con 0x563b53a4f400 auth_method
> 0
> Aug 11 16:55:48 bash[27152]: debug -9> 2021-08-11T11:25:47.581+
> 7fbf39815700  2 osd.12 6697 ms_handle_refused con 0x563b53a3c800 session
> 0x563b679120
> Aug 11 16:55:48 bash[27152]: debug -8> 2021-08-11T11:25:47.581+
> 7fbf39815700 10 monclient: _send_mon_message to mon.strg-node2 at v2:
> 10.0.103.2:3300/
> Aug 11 16:55:48 bash[27152]: debug -7> 2021-08-11T11:25:47.581+
> 7fbf4f0b0700 10 monclient: get_auth_request con 0x563b6331d000 auth_method
> 0
> Aug 11 16:55:48 bash[27152]: debug -6> 2021-08-11T11:25:47.581+
> 7fbf4e8af700 10 monclient: get_auth_request con 0x563b53a4f000 auth_method
> 0
> Aug 11 16:55:48 bash[27152]: debug -5> 2021-08-11T11:25:47.717+
> 7fbf4f0b0700 10 monclient: get_auth_request con 0x563b66226c00 auth_method
> 0
> Aug 11 16:55:48 bash[27152]: debug -4> 2021-08-11T11:25:47.789+
> 7fbf43623700  5 prioritycache tune_memory target: 1073741824 mapped:
> 388874240 unmap
> Aug 11 16:55:48 bash[27152]: debug -3> 2021-08-11T11:25:47.925+
> 7fbf32807700 -1
> /home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_
> Aug 11 16:55:48 bash[27152]:
>
> /home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos8/DIST/centos8/MACHINE_SIZ
> Aug 11 16:55:48 bash[27152]:  ceph version 15.2.7
> (88e41c6c49beb18add4fdb6b4326ca466d931db8) octopus (stable)
> Aug 11 16:55:48 bash[27152]:  1: (ceph::__ceph_assert_fail(char const*,
> char const*, int, char const*)+0x158) [0x563b46835dbe]
> Aug 11 16:55:48 bash[27152]:  2: (()+0x504fd8) [0x563b46835fd8]
> Aug 11 16:55:48 bash[27152]:  3: (OSD::do_recovery(PG*, unsigned int,
> unsigned long, ThreadPool::TPHandle&)+0x5f5) [0x563b46918c25]
> Aug 11 16:55:48 bash[27152]:  4:
> (ceph::osd::scheduler::PGRecovery::run(OSD*, OSDShard*,
> boost::intrusive_ptr&, ThreadPool::TPHandle&)+0x1d) [0x563b46b74
> Aug 11 16:55:48 bash[27152]:  5: (OSD::ShardedOpWQ::_process(unsigned int,
> ceph::heartbeat_handle_d*)+0x12ef) [0x563b469364df]
> Aug 11 16:55:48 bash[27152]:  6:
> (ShardedThreadPool::shardedthreadpool_worker(unsigned int)+0x5c4)
> [0x563b46f6f224]
> Aug 11 16:55:48 bash[27152]:  7:
> (ShardedThreadPool::WorkThreadSharded::entry()+0x14) [0x563b46f71e84]
> Aug 11 16:55:48 bash[27152]:  8: (()+0x82de) [0x7fbf528952de]
> Aug 11 16:55:48 bash[27152]:  9: (clone()+0x43) [0x7fbf515cce83]
> Aug 11 16:55:48 bash[27152]: debug -2> 2021-08-11T11:25:47.929+
> 7fbf32807700 -1 *** Caught signal (Aborted) **
> Aug 11 16:55:48 bash[27152]:  in thread 7fbf32807700 thread_name:tp_osd_tp
> Aug 11 16:55:48 bash[27152]:  ceph version 15.2.7
> (88e41c6c49beb18add4fdb6b4326ca466d931db8) octopus (stable)
> Aug 11 16:55:48 bash[27152]:  1: (()+0x12dd0) [0x7fbf5289fdd0]
> Aug 11 16:55:48 bash[27152]:  2: (gsignal()+0x10f) [0x7fbf5150870f]
> Aug 11 16:55:48 

Re: [casper] Red Pitaya STEMlab 125-14-Z7020

[Wesley New]

Hi Mutsuo,

There was a small team that added support for the first 2 red pitaya boards
to be used as cheap tutorial hardware for evaluation of the CASPER tools.
The nature of CASPER is one of open-source and collaboration.
Unfortunately many of us won't have the time to focus on making a port for
the latest Red Pitaya, but we would certainly be able to point you in the
right direction and assist with any questions you have with regards to
adding support for the latest Red Pitaya board.

AT first glance, it looks like the FPGA is just the Zynq 7020 SOC rather
than the 7010. This will mean that the STEMlab 125-14 will work for the
STEMlab 125-14-Z7020 with a simple change to the target fpga. As for adding
sata sync support, you would need to examine how that is implemented and
possibly create a yellow block or include it into the board support
package.

Hope this helps and points you in the right direction.

Regards

Wes

On Sat, Jul 31, 2021 at 12:15 PM IRspec Ogura  wrote:

> Dear Sirs,
>
> We are developing an InGaAs SWIR camera and hoping to use SOC-FPGA for
> related real-time processing
> in a user frendly manner.
>
> I wonder who prepared the elaborate tutorial for Casper project.
>
> It will be very nice to get the Casper module for STEMlab 125-14-Z7020 and
> its line by line tutorial.
> STEMlab 125-14-Z7020 is a Red Pitaya’s new board and it has Sata interface
> for synchronization.
> It will save labor and cost to use plural of simple boards rather than
> make one board more complicated and restrict them to the specific
> applications.
>
> I appreciate any information about Casper and Red pitaya.
>
>
> https://www.redpitaya.com/p76/stemlab-125-14-z7020
>
> https://casper-toolflow.readthedocs.io/projects/tutorials/en/latest/tutorials/redpitaya/red_pitaya_setup.html
>
> Sincerely,
>
> Mutsuo Ogura, Dr. Eng.
> IRspec Corp.
> Takezono 2-6-2,
> Tsukuba, Ibaraki 305-0032
> E-mail: og...@irspec.com
> Tel:+81-29-859-6910 Mobile:090-4452-2627
> Fax: 050-6861-1411
> http://www.irspec.com/E%20top.html
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/20210731191524.88CC.33551042%40irspec.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAE2vkmXwW5PyMO8e4YYFQCp4abua0bSTLSs7C3JP4t2UixRuAA%40mail.gmail.com.

RE:[cayugabirds-l] eBird Question

[Wesley M. Hochachka]

I believe that the reason is that so far the eBird reviewers for that region 
have not confirmed any of the sightings reported in eBird.  The eBird outputs 
--- at least the maps --- will only directly display these flagged rarities 
after they have been given a status of "confirmed" by regional reviewers.

However, you can see the checklists with flagged species, if you can guess at 
another species that is also present on the same checklist, display all of the 
checklists with this "surrogate" species, and then by trial and error check all 
of the these checklists containing reports of the surrogate until you find one 
with the flagged species on it.  For example, by searching for all recent 
checklists from the general area with Mallards, I found this checklists with a 
Common Shelduck photo: https://ebird.org/wi/checklist/S92590436

Wesley





-Original Message-
From: bounce-125804771-3494...@list.cornell.edu 
 On Behalf Of Carl J. Steckler
Sent: Sunday, August 1, 2021 12:40 PM
To: CAYUGABIRDS-L 
Subject: [cayugabirds-l] eBird Question

For several days I have been getting eBird alerts about a Common Shelduck in 
Lake Winnebago  near Fond Du Lac WI. However when I search for this species on 
eBird it doesn't show.

Does anyone know why this is?

Carl


--

Cayugabirds-L List Info:
http://www.NortheastBirding.com/CayugabirdsWELCOME
http://www.NortheastBirding.com/CayugabirdsRULES
http://www.NortheastBirding.com/CayugabirdsSubscribeConfigurationLeave.htm

ARCHIVES:
1) http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html
2) http://www.surfbirds.com/birdingmail/Group/Cayugabirds
3) http://birdingonthe.net/mailinglists/CAYU.html

Please submit your observations to eBird:
http://ebird.org/content/ebird/

--

--

Cayugabirds-L List Info:
http://www.NortheastBirding.com/CayugabirdsWELCOME
http://www.NortheastBirding.com/CayugabirdsRULES
http://www.NortheastBirding.com/CayugabirdsSubscribeConfigurationLeave.htm

ARCHIVES:
1) http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html
2) http://www.surfbirds.com/birdingmail/Group/Cayugabirds
3) http://birdingonthe.net/mailinglists/CAYU.html

Please submit your observations to eBird:
http://ebird.org/content/ebird/

--

[OPSAWG] Tsvart last call review of draft-ietf-opsawg-vpn-common-09

[Wesley Eddy via Datatracker]

Reviewer: Wesley Eddy
Review result: Ready with Issues

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-...@ietf.org if you reply to or forward this review.

This document basically looks good to me, though I have a small number of
comments:

(1) I think this comment impacts only the narrative and not the YANG model
itself.  The list of possible underlay-transport values seems to be a mixture
of expected types of encapsulations, but then a couple of things at the end
that are signaling and not encapsulations per-se.  The last 2 entries in the
list on page 6 are what seem out of place to me - RSVP and BGP.  I don't think
it's quite correct to refer to these two as the underlay-transport.

(2) This is a YANG model question, that I'm unsure of.  I want to make sure
that in the match-type when match-flow is used that a combination of L3 and L4
attributes can be used.  It appears like either L3 or L4 can be indicated,
mutually exclusive, but I don't quite understand how it would then be possible
to properly represent the combination of IP, transport protocol, and ports that
identify a flow.  It seems like a list of criteria from both L3 and L4
components is what's needed to express a flow, rather than a choice of L3 or L4.


___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Re: [google-appengine] Re: Where is the APIs & auth menu?

[wesley chun]

This thread isn't directly related to App Engine unless you're using Google
APIs from a GAE app, but if you find yourself needing to access the API
manager often, a shortcut link to go there directly is
console.developers.google.com ... once there, you'll get access to its 3
main pages:

   1. *Dashboard* -- your project's API usage, traffic, enabled APIs list
   2. *Library* -- where to search for and en-/disable APIs, and
   3. *Credentials* -- where you can create API keys, OAuth client IDs, or
   service acct credentials

--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google Cloud by day; at night...
Python training & consulting : http://CyberwebConsulting.com
<http://cyberwebconsulting.com/>
"Core Python" books : http://CorePython.com <http://corepython.com/>
Python blog: http://wescpy.blogspot.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA6VXWHbGcrsL_%3DF-ixBOfPt-F4jFzcqEeqoH2m1YoOSpw%40mail.gmail.com.

[ceph-users] Re: bug ceph auth

[Wesley Dillingham]

Do you get the same error if you just do "ceph auth get
client.bootstrap-osd" i.e. does client.bootstrap exist as a user?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Wed, Jul 14, 2021 at 1:56 PM Wesley Dillingham 
wrote:

> is /var/lib/ceph/bootstrap-osd/ in existence and writeable?
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Wed, Jul 14, 2021 at 8:35 AM Marc  wrote:
>
>>
>>
>>
>> [@t01 ~]# ceph auth get client.bootstrap-osd -o
>> ​/var/lib/ceph/bootstrap-osd/ceph.keyring
>> Traceback (most recent call last):
>>   File "/usr/bin/ceph", line 1272, in 
>> retval = main()
>>   File "/usr/bin/ceph", line 1120, in main
>> print('Can\'t open output file {0}:
>> {1}'.format(parsed_args.output_file, e), file=sys.stderr)
>>   File "/usr/lib64/python2.7/codecs.py", line 351, in write
>> data, consumed = self.encode(object, self.errors)
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 23:
>> ordinal not in range(128)
>>
>>
>>
>> ___
>> ceph-users mailing list -- ceph-users@ceph.io
>> To unsubscribe send an email to ceph-users-le...@ceph.io
>>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: bug ceph auth

[Wesley Dillingham]

is /var/lib/ceph/bootstrap-osd/ in existence and writeable?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Wed, Jul 14, 2021 at 8:35 AM Marc  wrote:

>
>
>
> [@t01 ~]# ceph auth get client.bootstrap-osd -o
> ​/var/lib/ceph/bootstrap-osd/ceph.keyring
> Traceback (most recent call last):
>   File "/usr/bin/ceph", line 1272, in 
> retval = main()
>   File "/usr/bin/ceph", line 1120, in main
> print('Can\'t open output file {0}:
> {1}'.format(parsed_args.output_file, e), file=sys.stderr)
>   File "/usr/lib64/python2.7/codecs.py", line 351, in write
> data, consumed = self.encode(object, self.errors)
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 23:
> ordinal not in range(128)
>
>
>
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Re: [cayugabirds-l] Mystery bird virus

[Wesley M. Hochachka]

Hi,

   I work at the Lab of O, and I suppose that I could be labelled a "disease 
ecologist", but I want to make clear that I'm not speaking for the Lab of 
Ornithology here.

   Anyway, in terms of spread in NYS, I've heard informally that whatever this 
disease is, it's seems to have started to appear in the area around Ithaca.

   In my opinion there's no way that any human action is going to stop the 
spread of the disease, if it's caused by a pathogen (e.g., bacteria, virus, 
protozoa).  I cannot think of a single wildlife disease (and extremely few 
human diseased, i.e. just smallpox) that has been stopped.  Spread might be 
slowed, but that's about it.
   Given that we don't know the cause of the disease, even slowing spread seems 
unlikely to me.  There are not clearly obvious recommendations for actions that 
would be certain to have a positive effect.  Taking down feeders might help, if 
the disease is caused by a directly transmitted pathogen.  However, if it's 
really true that mostly young birds are coming down with the disease, they 
might not be the most likely to be attending bird feeders...of course it might 
just be that younger birds are more likely to be noticed.  If the disease is 
caused by a vector-transmitted pathogen (mosquito-transmitted, for example) 
then actions like taking down bird feeders likely would have extremely minimal 
effects, at best.
   Only if the disease is somehow caused by a human-made toxin could there be a 
chance for really effective action, I'm guessing.

   Having written all of the above, whatever recommendations I've seen couldn't 
hurt, and so they seem reasonable from that perspective.

   We'll have to wait a few months to see if we can detect any effect of the 
populations of some bird species, looking at data from eBird or Project 
FeederWatch, but that's something that should probably be done this fall.  I 
know that wouldn't help the situation, but right now there's no clear 
information about the impact of the disease on bird populations.  Individual 
birds are definitely dying, but the magnitude of the effect on populations as a 
whole is unknown, as far as I know.

Wesley




From: bounce-125761038-3494...@list.cornell.edu 
 on behalf of Thomas Yaglowski 

Sent: Saturday, July 10, 2021 09:29
To: CAYUGABIRDS-L 
Subject: [cayugabirds-l] Mystery bird virus

I've been seeing quite a bit about the mystery bird virus that is killing many 
birds. My understanding is that it originated down South and is spreading 
rapidly to the northeast. A friend has relayed that it is now in Chautauqua 
county and the Hudson Valley region.

What is everyone's opinion on how to help stop the spread? Are you already 
taking down feeders and sanitizing them? Any advice and suggestions from the 
experts at the Lab of Ornithology would be greatly appreciated.

Regards,
Tom
--
Cayugabirds-L List Info:
Welcome and Basics<http://www.northeastbirding.com/CayugabirdsWELCOME>
Rules and Information<http://www.northeastbirding.com/CayugabirdsRULES>
Subscribe, Configuration and 
Leave<http://www.northeastbirding.com/CayugabirdsSubscribeConfigurationLeave.htm>
Archives:
The Mail 
Archive<http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html>
Surfbirds<http://www.surfbirds.com/birdingmail/Group/Cayugabirds>
BirdingOnThe.Net<http://birdingonthe.net/mailinglists/CAYU.html>
Please submit your observations to eBird<http://ebird.org/content/ebird/>!
--

--

Cayugabirds-L List Info:
http://www.NortheastBirding.com/CayugabirdsWELCOME
http://www.NortheastBirding.com/CayugabirdsRULES
http://www.NortheastBirding.com/CayugabirdsSubscribeConfigurationLeave.htm

ARCHIVES:
1) http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html
2) http://www.surfbirds.com/birdingmail/Group/Cayugabirds
3) http://birdingonthe.net/mailinglists/CAYU.html

Please submit your observations to eBird:
http://ebird.org/content/ebird/

--

[PATCH v2] Documentation: PCI: pci-error-recovery: swap sequence between MMIO Enabled and Link Reset

[Wesley Sheng]

Reset_link() callback function (named with reset_subordinates()
in pcie_do_recovery() function) was called before mmio_enabled(),
so exchange the sequence between step 2 MMIO Enabled and step 3
Link Reset accordingly.

Signed-off-by: Wesley Sheng 
---
 Documentation/PCI/pci-error-recovery.rst | 25 
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/Documentation/PCI/pci-error-recovery.rst 
b/Documentation/PCI/pci-error-recovery.rst
index 187f43a03200..0e2f3f77bf0a 100644
--- a/Documentation/PCI/pci-error-recovery.rst
+++ b/Documentation/PCI/pci-error-recovery.rst
@@ -157,7 +157,7 @@ drivers.
 If all drivers on the segment/slot return PCI_ERS_RESULT_CAN_RECOVER,
 then the platform should re-enable IOs on the slot (or do nothing in
 particular, if the platform doesn't isolate slots), and recovery
-proceeds to STEP 2 (MMIO Enable).
+proceeds to STEP 3 (MMIO Enable).
 
 If any driver requested a slot reset (by returning PCI_ERS_RESULT_NEED_RESET),
 then recovery proceeds to STEP 4 (Slot Reset).
@@ -184,7 +184,14 @@ is STEP 6 (Permanent Failure).
and prints an error to syslog.  A reboot is then required to
get the device working again.
 
-STEP 2: MMIO Enabled
+STEP 2: Link Reset
+--
+The platform resets the link.  This is a PCI-Express specific step
+and is done whenever a fatal error has been detected that can be
+"solved" by resetting the link.
+
+
+STEP 3: MMIO Enabled
 
 The platform re-enables MMIO to the device (but typically not the
 DMA), and then calls the mmio_enabled() callback on all affected
@@ -197,8 +204,8 @@ information, if any, and eventually do things like trigger 
a device local
 reset or some such, but not restart operations. This callback is made if
 all drivers on a segment agree that they can try to recover and if no automatic
 link reset was performed by the HW. If the platform can't just re-enable IOs
-without a slot reset or a link reset, it will not call this callback, and
-instead will have gone directly to STEP 3 (Link Reset) or STEP 4 (Slot Reset)
+without a slot reset, it will not call this callback, and
+instead will have gone directly to STEP 4 (Slot Reset)
 
 .. note::
 
@@ -210,7 +217,7 @@ instead will have gone directly to STEP 3 (Link Reset) or 
STEP 4 (Slot Reset)
such an error might cause IOs to be re-blocked for the whole
segment, and thus invalidate the recovery that other devices
on the same segment might have done, forcing the whole segment
-   into one of the next states, that is, link reset or slot reset.
+   into the next states, that is, slot reset.
 
 The driver should return one of the following result codes:
   - PCI_ERS_RESULT_RECOVERED
@@ -233,17 +240,11 @@ The driver should return one of the following result 
codes:
 
 The next step taken depends on the results returned by the drivers.
 If all drivers returned PCI_ERS_RESULT_RECOVERED, then the platform
-proceeds to either STEP3 (Link Reset) or to STEP 5 (Resume Operations).
+proceeds to STEP 5 (Resume Operations).
 
 If any driver returned PCI_ERS_RESULT_NEED_RESET, then the platform
 proceeds to STEP 4 (Slot Reset)
 
-STEP 3: Link Reset
---
-The platform resets the link.  This is a PCI-Express specific step
-and is done whenever a fatal error has been detected that can be
-"solved" by resetting the link.
-
 STEP 4: Slot Reset
 --
 
-- 
2.25.1

Re: [PATCH] Documentation: PCI: pci-error-recovery: rearrange the general sequence

[Wesley Sheng]

On Thu, Jul 01, 2021 at 05:22:31PM -0500, Bjorn Helgaas wrote:
> Please make the subject a little more specific.  "rearrange the
> general sequence" doesn't say anything about what was affected.
> 
> On Fri, Jun 18, 2021 at 02:04:46PM +0800, Wesley Sheng wrote:
> > Reset_link() callback function was called before mmio_enabled() in
> > pcie_do_recovery() function actually, so rearrange the general
> > sequence betwen step 2 and step 3 accordingly.
> 
> s/betwen/between/
> 
> Not sure "general" adds anything in this sentence.  "Step 2 and step
> 3" are not meaningful here in the commit log.  It needs to spell out
> what those steps are so the log makes sense by itself.
> 
> "reset_link" does not appear in pcie_do_recovery().  I'm guessing
> you're referring to the "reset_subordinates" function pointer?
>
Yes, you are right.
pcieaer-howto.rst has a section named with "Provide callbacks",
the callback supplied to pcie_do_recovery() was referred to 
reset_link.
 
> > Signed-off-by: Wesley Sheng 
> 
> I didn't quite understand your response to Oliver, so I'll wait for
> your corrections and his ack before proceeding.
>
OK.
I thought step 2 MMIO Enabled and step 3 link reset should swap sequence.

> > ---
> >  Documentation/PCI/pci-error-recovery.rst | 23 ---
> >  1 file changed, 12 insertions(+), 11 deletions(-)
> > 
> > diff --git a/Documentation/PCI/pci-error-recovery.rst 
> > b/Documentation/PCI/pci-error-recovery.rst
> > index 187f43a03200..ac6a8729ef28 100644
> > --- a/Documentation/PCI/pci-error-recovery.rst
> > +++ b/Documentation/PCI/pci-error-recovery.rst
> > @@ -184,7 +184,14 @@ is STEP 6 (Permanent Failure).
> > and prints an error to syslog.  A reboot is then required to
> > get the device working again.
> >  
> > -STEP 2: MMIO Enabled
> > +STEP 2: Link Reset
> > +--
> > +The platform resets the link.  This is a PCI-Express specific step
> > +and is done whenever a fatal error has been detected that can be
> > +"solved" by resetting the link.
> > +
> > +
> > +STEP 3: MMIO Enabled
> >  
> >  The platform re-enables MMIO to the device (but typically not the
> >  DMA), and then calls the mmio_enabled() callback on all affected
> > @@ -197,8 +204,8 @@ information, if any, and eventually do things like 
> > trigger a device local
> >  reset or some such, but not restart operations. This callback is made if
> >  all drivers on a segment agree that they can try to recover and if no 
> > automatic
> >  link reset was performed by the HW. If the platform can't just re-enable 
> > IOs
> > -without a slot reset or a link reset, it will not call this callback, and
> > -instead will have gone directly to STEP 3 (Link Reset) or STEP 4 (Slot 
> > Reset)
> > +without a slot reset, it will not call this callback, and
> > +instead will have gone directly or STEP 4 (Slot Reset)
> 
> s/or/to/  ?
> 
> >  .. note::
> >  
> > @@ -210,7 +217,7 @@ instead will have gone directly to STEP 3 (Link Reset) 
> > or STEP 4 (Slot Reset)
> > such an error might cause IOs to be re-blocked for the whole
> > segment, and thus invalidate the recovery that other devices
> > on the same segment might have done, forcing the whole segment
> > -   into one of the next states, that is, link reset or slot reset.
> > +   into next states, that is, slot reset.
> 
> s/into next states/into the next state/ ?
> 
> >  The driver should return one of the following result codes:
> >- PCI_ERS_RESULT_RECOVERED
> > @@ -233,17 +240,11 @@ The driver should return one of the following result 
> > codes:
> >  
> >  The next step taken depends on the results returned by the drivers.
> >  If all drivers returned PCI_ERS_RESULT_RECOVERED, then the platform
> > -proceeds to either STEP3 (Link Reset) or to STEP 5 (Resume Operations).
> > +proceeds to STEP 5 (Resume Operations).
> >  
> >  If any driver returned PCI_ERS_RESULT_NEED_RESET, then the platform
> >  proceeds to STEP 4 (Slot Reset)
> >  
> > -STEP 3: Link Reset
> > ---
> > -The platform resets the link.  This is a PCI-Express specific step
> > -and is done whenever a fatal error has been detected that can be
> > -"solved" by resetting the link.
> > -
> >  STEP 4: Slot Reset
> >  --
> >  
> > -- 
> > 2.25.1
> > 

Re: [PATCH] Documentation: PCI: pci-error-recovery: rearrange the general sequence

[Wesley Sheng]

On Fri, Jun 18, 2021 at 05:21:32PM +1000, Oliver O'Halloran wrote:
> On Fri, Jun 18, 2021 at 4:05 PM Wesley Sheng  wrote:
> >
> > Reset_link() callback function was called before mmio_enabled() in
> > pcie_do_recovery() function actually, so rearrange the general
> > sequence betwen step 2 and step 3 accordingly.
> 
> I don't think this is true in all cases. If pcie_do_recovery() is
> called with state==pci_channel_io_normal (i.e. non-fatal AER) the link
> won't be reset. EEH (ppc PCI error recovery thing) also uses
> .mmio_enabled() as described.

Yes, in case of non-fatal AER, reset_link() callback (aer_root_reset() for 
AER and dpc_reset_link() for DPC) will not be invoked. And if 
.error_detected() return PCI_ERS_RESULT_CAN_RECOVER, .mmio_enabled() be
called followed.

But if pcie_do_recovery() is called with state == pci_channel_io_frozen,
reset_link() callback is called after .error_detected() but before
.mmio_enabled(). So I thought Step 2: MMIO Enabled and Step 3: Link Reset
should rearrange their sequence.

Bug#990279: linux-image-5.10.0-7-powerpc64le: Upgrade to 5.10.0-7-powerpc64le from 5.10.0-0.bpo.5-powerpc64le breaks amdgpu

[Nathaniel Wesley Filardo]

Package: src:linux
Version: 5.10.40-1
Severity: normal
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Upgrading from 5.10.0-0.bpo.5-powerpc64le=5.10.24-1~bpo10+1 to
5.10.0-7-powerpc64le=5.10.40-1 has broken my X server's ability to use GL, and
has, indeed, lead to markedly poor performance even in things like rxvt.
Quoting /var/log/Xorg.0.log:

[19.084] (II) LoadModule: "glx"
[19.087] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[19.102] (II) Module glx: vendor="X.Org Foundation"
[19.143] (II) Loading sub module "glamoregl"
[19.143] (II) LoadModule: "glamoregl"
[19.143] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[19.159] (II) Module glamoregl: vendor="X.Org Foundation"
[19.573] (II) modeset(0): glamor X acceleration enabled on AMD Radeon (TM) 
Pro WX 7100 Graphics (POLARIS10, DRM 3.40.0, 5.10.0-7-powerpc64le, LLVM 11.0.1)
[19.573] (II) modeset(0): glamor initialized
[19.647] (II) Initializing extension GLX
[19.656] (II) AIGLX: Loaded and initialized radeonsi
[19.656] (II) GLX: Initialized DRI2 GL provider for screen 0
[20.985] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[21.018] (WW) glamor: Failed to allocate 48x48 FBO due to GL_OUT_OF_MEMORY.
[21.018] (WW) glamor: Expect reduced performance.

Things work just fine with the same machine on the old kernel, so I'm holding
back for now, but this isn't a great long-term solution.  This is a Talos II
workstation, making it a little niche and therefore unsurprising that
regressions have crept in, but it'd be nice to get them resolved.  Any
suggestions, advice, requests for further information,  are all appreciated.
I can rebuild kernels and bisect if pointed at the right git repository and
tags, if that'd be a useful thing.

FWIW, the same thing happened, I believe, with 5.10.0-6-powerpc64le, previously,
but I no longer have it installed to check again.

Thanks much in advance,
--nwf;

-- Package-specific info:
** Version:
Linux version 5.10.0-7-powerpc64le (debian-kernel@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 
SMP Debian 5.10.40-1 (2021-05-28)

** Command line:
root=ZFS=rpool/ROOT/debian ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[5.306593] [drm] amdgpu kernel modesetting enabled.
[5.309579] amdgpu 0030:01:00.0: vgaarb: deactivate vga console
[5.309753] amdgpu 0030:01:00.0: enabling device (0140 -> 0142)
[5.309767] amdgpu 0030:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature 
not supported
[5.644486] amdgpu 0030:01:00.0: amdgpu: Fetched VBIOS from ROM BAR
[5.644492] amdgpu: ATOM BIOS: 113-C9540101-103
[5.647802] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_mc.bin
[5.647819] amdgpu 0030:01:00.0: BAR 2: releasing [mem 
0x620001000-0x62000101f 64bit pref]
[5.647822] amdgpu 0030:01:00.0: BAR 0: releasing [mem 
0x62000-0x62fff 64bit pref]
[5.647869] amdgpu 0030:01:00.0: BAR 0: assigned [mem 
0x62000-0x62001 64bit pref]
[5.647879] amdgpu 0030:01:00.0: BAR 2: assigned [mem 
0x62002-0x62002001f 64bit pref]
[5.647913] amdgpu 0030:01:00.0: amdgpu: VRAM: 8192M 0x00F4 - 
0x00F5 (8192M used)
[5.647916] amdgpu 0030:01:00.0: amdgpu: GART: 256M 0x00FF - 
0x00FF0FFF
[5.648123] [drm] amdgpu: 8192M of VRAM memory ready
[5.648128] [drm] amdgpu: 8192M of GTT memory ready.
[5.649983] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_pfp_2.bin
[5.650921] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_me_2.bin
[5.651856] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_ce_2.bin
[5.652822] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_rlc.bin
[5.654748] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_mec_2.bin
[5.657197] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_mec2_2.bin
[5.659428] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_sdma.bin
[5.661056] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_sdma1.bin
[5.661159] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
[5.663358] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_uvd.bin
[5.666276] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_vce.bin
[5.668251] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_smc.bin
[5.727666] snd_hda_intel 0030:01:00.1: bound 0030:01:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])
[5.946750] amdgpu 0030:01:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, 
active_cu_number 36
[6.091370] amdgpu 

Bug#990279: linux-image-5.10.0-7-powerpc64le: Upgrade to 5.10.0-7-powerpc64le from 5.10.0-0.bpo.5-powerpc64le breaks amdgpu

[Nathaniel Wesley Filardo]

Package: src:linux
Version: 5.10.40-1
Severity: normal
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Upgrading from 5.10.0-0.bpo.5-powerpc64le=5.10.24-1~bpo10+1 to
5.10.0-7-powerpc64le=5.10.40-1 has broken my X server's ability to use GL, and
has, indeed, lead to markedly poor performance even in things like rxvt.
Quoting /var/log/Xorg.0.log:

[19.084] (II) LoadModule: "glx"
[19.087] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[19.102] (II) Module glx: vendor="X.Org Foundation"
[19.143] (II) Loading sub module "glamoregl"
[19.143] (II) LoadModule: "glamoregl"
[19.143] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[19.159] (II) Module glamoregl: vendor="X.Org Foundation"
[19.573] (II) modeset(0): glamor X acceleration enabled on AMD Radeon (TM) 
Pro WX 7100 Graphics (POLARIS10, DRM 3.40.0, 5.10.0-7-powerpc64le, LLVM 11.0.1)
[19.573] (II) modeset(0): glamor initialized
[19.647] (II) Initializing extension GLX
[19.656] (II) AIGLX: Loaded and initialized radeonsi
[19.656] (II) GLX: Initialized DRI2 GL provider for screen 0
[20.985] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[21.018] (WW) glamor: Failed to allocate 48x48 FBO due to GL_OUT_OF_MEMORY.
[21.018] (WW) glamor: Expect reduced performance.

Things work just fine with the same machine on the old kernel, so I'm holding
back for now, but this isn't a great long-term solution.  This is a Talos II
workstation, making it a little niche and therefore unsurprising that
regressions have crept in, but it'd be nice to get them resolved.  Any
suggestions, advice, requests for further information,  are all appreciated.
I can rebuild kernels and bisect if pointed at the right git repository and
tags, if that'd be a useful thing.

FWIW, the same thing happened, I believe, with 5.10.0-6-powerpc64le, previously,
but I no longer have it installed to check again.

Thanks much in advance,
--nwf;

-- Package-specific info:
** Version:
Linux version 5.10.0-7-powerpc64le (debian-ker...@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 
SMP Debian 5.10.40-1 (2021-05-28)

** Command line:
root=ZFS=rpool/ROOT/debian ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[5.306593] [drm] amdgpu kernel modesetting enabled.
[5.309579] amdgpu 0030:01:00.0: vgaarb: deactivate vga console
[5.309753] amdgpu 0030:01:00.0: enabling device (0140 -> 0142)
[5.309767] amdgpu 0030:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature 
not supported
[5.644486] amdgpu 0030:01:00.0: amdgpu: Fetched VBIOS from ROM BAR
[5.644492] amdgpu: ATOM BIOS: 113-C9540101-103
[5.647802] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_mc.bin
[5.647819] amdgpu 0030:01:00.0: BAR 2: releasing [mem 
0x620001000-0x62000101f 64bit pref]
[5.647822] amdgpu 0030:01:00.0: BAR 0: releasing [mem 
0x62000-0x62fff 64bit pref]
[5.647869] amdgpu 0030:01:00.0: BAR 0: assigned [mem 
0x62000-0x62001 64bit pref]
[5.647879] amdgpu 0030:01:00.0: BAR 2: assigned [mem 
0x62002-0x62002001f 64bit pref]
[5.647913] amdgpu 0030:01:00.0: amdgpu: VRAM: 8192M 0x00F4 - 
0x00F5 (8192M used)
[5.647916] amdgpu 0030:01:00.0: amdgpu: GART: 256M 0x00FF - 
0x00FF0FFF
[5.648123] [drm] amdgpu: 8192M of VRAM memory ready
[5.648128] [drm] amdgpu: 8192M of GTT memory ready.
[5.649983] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_pfp_2.bin
[5.650921] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_me_2.bin
[5.651856] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_ce_2.bin
[5.652822] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_rlc.bin
[5.654748] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_mec_2.bin
[5.657197] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_mec2_2.bin
[5.659428] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_sdma.bin
[5.661056] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_sdma1.bin
[5.661159] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
[5.663358] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_uvd.bin
[5.666276] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_vce.bin
[5.668251] amdgpu 0030:01:00.0: firmware: direct-loading firmware 
amdgpu/polaris10_smc.bin
[5.727666] snd_hda_intel 0030:01:00.1: bound 0030:01:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])
[5.946750] amdgpu 0030:01:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, 
active_cu_number 36
[6.091370] amdgpu 

[PATCH] nvme: Remove the redundant aqa value setting

[Wesley Sheng]

From: Wesley Sheng 

AQA (Admin Queue Attributes) register is a dword size with
lower word of ASQS, and higher word of ACQS.

The code set the variable aqa twice, but it is redundant.

Signed-off-by: Wesley Sheng 
---
 drivers/nvme/nvme.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/nvme/nvme.c b/drivers/nvme/nvme.c
index fc64d93ab8..a062234163 100644
--- a/drivers/nvme/nvme.c
+++ b/drivers/nvme/nvme.c
@@ -379,7 +379,6 @@ static int nvme_configure_admin_queue(struct nvme_dev *dev)
 
aqa = nvmeq->q_depth - 1;
aqa |= aqa << 16;
-   aqa |= aqa << 16;
 
dev->page_size = 1 << page_shift;
 
-- 
2.25.1

[PATCH] nvme: Correct the prps per page calculation method

[Wesley Sheng]

From: Wesley Sheng 

Each prp is 8 bytes, calculate the number of prps
per page should just divide page size by 8
there is no need to minus 1

Signed-off-by: Wesley Sheng 
---
 drivers/nvme/nvme.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/nvme/nvme.c b/drivers/nvme/nvme.c
index fc64d93ab8..622bb378c0 100644
--- a/drivers/nvme/nvme.c
+++ b/drivers/nvme/nvme.c
@@ -79,7 +79,7 @@ static int nvme_setup_prps(struct nvme_dev *dev, u64 *prp2,
u64 *prp_pool;
int length = total_len;
int i, nprps;
-   u32 prps_per_page = (page_size >> 3) - 1;
+   u32 prps_per_page = page_size >> 3;
u32 num_pages;
 
length -= (page_size - offset);
-- 
2.25.1

[PATCH] Documentation: PCI: pci-error-recovery: rearrange the general sequence

[Wesley Sheng]

Reset_link() callback function was called before mmio_enabled() in
pcie_do_recovery() function actually, so rearrange the general
sequence betwen step 2 and step 3 accordingly.

Signed-off-by: Wesley Sheng 
---
 Documentation/PCI/pci-error-recovery.rst | 23 ---
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/Documentation/PCI/pci-error-recovery.rst 
b/Documentation/PCI/pci-error-recovery.rst
index 187f43a03200..ac6a8729ef28 100644
--- a/Documentation/PCI/pci-error-recovery.rst
+++ b/Documentation/PCI/pci-error-recovery.rst
@@ -184,7 +184,14 @@ is STEP 6 (Permanent Failure).
and prints an error to syslog.  A reboot is then required to
get the device working again.
 
-STEP 2: MMIO Enabled
+STEP 2: Link Reset
+--
+The platform resets the link.  This is a PCI-Express specific step
+and is done whenever a fatal error has been detected that can be
+"solved" by resetting the link.
+
+
+STEP 3: MMIO Enabled
 
 The platform re-enables MMIO to the device (but typically not the
 DMA), and then calls the mmio_enabled() callback on all affected
@@ -197,8 +204,8 @@ information, if any, and eventually do things like trigger 
a device local
 reset or some such, but not restart operations. This callback is made if
 all drivers on a segment agree that they can try to recover and if no automatic
 link reset was performed by the HW. If the platform can't just re-enable IOs
-without a slot reset or a link reset, it will not call this callback, and
-instead will have gone directly to STEP 3 (Link Reset) or STEP 4 (Slot Reset)
+without a slot reset, it will not call this callback, and
+instead will have gone directly or STEP 4 (Slot Reset)
 
 .. note::
 
@@ -210,7 +217,7 @@ instead will have gone directly to STEP 3 (Link Reset) or 
STEP 4 (Slot Reset)
such an error might cause IOs to be re-blocked for the whole
segment, and thus invalidate the recovery that other devices
on the same segment might have done, forcing the whole segment
-   into one of the next states, that is, link reset or slot reset.
+   into next states, that is, slot reset.
 
 The driver should return one of the following result codes:
   - PCI_ERS_RESULT_RECOVERED
@@ -233,17 +240,11 @@ The driver should return one of the following result 
codes:
 
 The next step taken depends on the results returned by the drivers.
 If all drivers returned PCI_ERS_RESULT_RECOVERED, then the platform
-proceeds to either STEP3 (Link Reset) or to STEP 5 (Resume Operations).
+proceeds to STEP 5 (Resume Operations).
 
 If any driver returned PCI_ERS_RESULT_NEED_RESET, then the platform
 proceeds to STEP 4 (Slot Reset)
 
-STEP 3: Link Reset
---
-The platform resets the link.  This is a PCI-Express specific step
-and is done whenever a fatal error has been detected that can be
-"solved" by resetting the link.
-
 STEP 4: Slot Reset
 --
 
-- 
2.25.1

[PATCH] nvme: Remove the redundant aqa value setting

[Wesley Sheng]

From: wesleywesley 

AQA (Admin Queue Attributes) register is a dword size with
lower word of ASQS, and higher word of ACQS.

The code set the variable aqa twice, but it is redundant.

Signed-off-by: wesleywesley 
---
 drivers/nvme/nvme.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/nvme/nvme.c b/drivers/nvme/nvme.c
index fc64d93ab8..a062234163 100644
--- a/drivers/nvme/nvme.c
+++ b/drivers/nvme/nvme.c
@@ -379,7 +379,6 @@ static int nvme_configure_admin_queue(struct nvme_dev *dev)
 
aqa = nvmeq->q_depth - 1;
aqa |= aqa << 16;
-   aqa |= aqa << 16;
 
dev->page_size = 1 << page_shift;
 
-- 
2.25.1

[PATCH] nvme: Correct the prps per page calculation method

[Wesley Sheng]

From: wesleywesley 

Each prp is 8 bytes, calculate the number of prps
per page should just divide page size by 8
there is no need to minus 1

Signed-off-by: wesleywesley 
---
 drivers/nvme/nvme.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/nvme/nvme.c b/drivers/nvme/nvme.c
index fc64d93ab8..622bb378c0 100644
--- a/drivers/nvme/nvme.c
+++ b/drivers/nvme/nvme.c
@@ -79,7 +79,7 @@ static int nvme_setup_prps(struct nvme_dev *dev, u64 *prp2,
u64 *prp_pool;
int length = total_len;
int i, nprps;
-   u32 prps_per_page = (page_size >> 3) - 1;
+   u32 prps_per_page = page_size >> 3;
u32 num_pages;
 
length -= (page_size - offset);
-- 
2.25.1

[Mpi-forum] Moving the June 9 Voting Block

[Wesley Bland via mpi-forum]

Hi all,

As discussed today at the end of the call, we’ll be moving the voting block 
during tomorrow's (June 9th) call up to an earlier time since we finished most 
of our discussions today. The voting block will now be at 9:30 AM US Central. 
That is 30 minutes after the meeting is scheduled to call. The agenda website 
is now updated to reflect the change.

https://www.mpi-forum.org/meetings/2021/06/agenda 
 

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

[google-appengine] App Engine legacy bundled services private preview

[wesley chun]

To Java 8, Python 2, and Go 1.11 (or earlier) App Engine users:

In order to help with modernizing your apps to newer language releases, the
App Engine team is broadening the participation in our private preview of
the legacy bundled services. Previously, users have had to migrate from
bundled services like App Engine Datastore, Memcache, Task Queues, etc., to
their standalone, unbundled equivalent, i.e., Cloud Datastore, Cloud
Memorystore, Cloud Tasks, etc., before upgrading to the second generation
App Engine Java 11, Python 3, PHP 7, and Go 1.12 (and newer) runtimes.

Now by accessing these private preview features, you can do the vice versa:
upgrade to the modern language runtimes, then migrate to the new standalone
services on your own time. The legacy services we are making available are
meant to aid you as a migration tool. Be aware that new features and
product innovations will only take place in the newer standalone services,
so we do recommend upgrading when possible. Here is what's currently
available in the private preview (with more on the way soon):

Feature

Java 11

Python 3

Go 1.12+

Datastore
✔ ✔ ✔

Memcache
✔ ✔ ✔

Blobstore
✔
✔

Task Queues
✔
✔

URLfetch
✔ ✔ ✔

Mail
✔

Users
✔
✔

Images
✔


If you would like to register for the private preview, please fill out this
registration form
<https://docs.google.com/forms/d/e/1FAIpQLSd1hFLA2UFSYwIMxm9ZI3pwigORZBgjJRH0qrnhtE7nvhhRCQ/viewform>
. Registering will get you in the queue to access the private preview, its
documentation, and the announcements mailing list.
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google Cloud by day; at night...
Python training & consulting : http://CyberwebConsulting.com
"Core Python" books : http://CorePython.com
Python blog: http://wescpy.blogspot.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA5b_ryFHPAvCTkSHy7BUaxRqe-RhN%2BvmB1RSX5SoJy-Gw%40mail.gmail.com.

[Mpi-forum] Zoom Information Posted

[Wesley Bland via mpi-forum]

Hi all,

For anyone who was trying to get ready before the meeting by getting set up 
with the Zoom call, I apologize that we didn’t have the information posted it. 
It’s now posted at the bottom of the wiki page here:

https://github.com/mpi-forum/mpi-standard/wiki/Virtual-Forum-Meeting-Information
 


Make sure you scroll to the section that says “June 2021 Meeting” instead of 
the weekly calls at the top. I’m in the call now so if you go into a room and 
don’t see the pre-roll slides, you’re in the wrong place. If you’re having 
issues, feel free to email me back or send me a message on the MPI Forum Slack.

We’ll be starting in about 30 minutes. See you there!

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

[rdo-users] download-logs.sh feature for zuul logs

[Wesley Hayutin]

Greetings,

RFE to rdo projects zuul and others... would be to deploy the feature that
includes the option to download logs from the log server. Example is here
[1]

Thanks all!

[1]
https://6d6df89134025ef5b0e9-648722ac87374da2f576895eac8df5a8.ssl.cf5.rackcdn.com/794592/4/check/tripleo-ci-centos-8-standalone/7e2d1d6/download-logs.sh
___
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscr...@lists.rdoproject.org

[PATCH] Documentation PCI: Fix typo in pci-error-recovery.rst

[Wesley Sheng]

Replace "It" with "If", since it is a conditional statement.

Signed-off-by: Wesley Sheng 
---
 Documentation/PCI/pci-error-recovery.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/PCI/pci-error-recovery.rst 
b/Documentation/PCI/pci-error-recovery.rst
index 84ceebb08cac..187f43a03200 100644
--- a/Documentation/PCI/pci-error-recovery.rst
+++ b/Documentation/PCI/pci-error-recovery.rst
@@ -295,7 +295,7 @@ and let the driver restart normal I/O processing.
 A driver can still return a critical failure for this function if
 it can't get the device operational after reset.  If the platform
 previously tried a soft reset, it might now try a hard reset (power
-cycle) and then call slot_reset() again.  It the device still can't
+cycle) and then call slot_reset() again.  If the device still can't
 be recovered, there is nothing more that can be done;  the platform
 will typically report a "permanent failure" in such a case.  The
 device will be considered "dead" in this case.
-- 
2.25.1

Re: [google-appengine] Re: I can´t delete my Google Cloud account I used App Engine "for free"

[wesley chun]

Also for all future students who are finding this thread online, please try
to AVOID the Free Trial if you can. As a student, it's best if you work
with your professors and teachers to get completely free credits without
giving Google your credit card information. Send your educators to
cloud.google.com/edu and select "Faculty resources" where they can request
GCP ("teaching") credits as well as ("training") credits for Qwiklabs
codelab tutorials <http://google.qwiklabs.com> for students in their
courses. Students, you should never have to send an email message like this!

On Sat, May 29, 2021 at 3:15 PM 'babdelrahman' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Hello,
>
> I understand that you created a free trial account with GCP to do an
> assignment and that you can't delete the account.
>
> Kindly check document [1] on information about the GCP Free Tier.
>
> For the future, you can set budget alerts in order to not exceed a certain
> threshold [2].
>
> Since your only project is shut down, you will not be charged more.
>
> For information on how to delete your billing account, please check
> document [3].
>
> Can you elaborate more on the billing support that you are inquiring about?
>
>
> [1] https://cloud.google.com/free/docs/gcp-free-tier
> [2] https://cloud.google.com/billing/docs/how-to/budgets
> [3] https://cloud.google.com/billing/docs/how-to/manage-billing-account
> On Saturday, May 29, 2021 at 9:03:39 AM UTC-4 jdmval...@gmail.com wrote:
>
>> Hi everyone I create an account on Google Cloud because was an assignment
>> of my subject of Web Programming, so know that I send my homework, I can´t
>> delete the account
>> I´m on the free trial but I saw the charges in my credit card.
>> Tre project on App Engine I enabled and deleted with success I think, the
>> send an email
>> "our project supple-synapse-315102 has been shut down"
>> I can´t be able to have the support on Cloud Billing Support because I
>> need a project to request help
>> appears this  *To view this page, select a project.*
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/6f0efd37-9749-4c67-92d4-f50e7e772169n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/6f0efd37-9749-4c67-92d4-f50e7e772169n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google Cloud by day; at night...
Python training & consulting : http://CyberwebConsulting.com
"Core Python" books : http://CorePython.com
Python blog: http://wescpy.blogspot.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA7B3jy3%3DWXQkpt3TZFx1maRq9J3WRzutC3ozhVyez%3DX8g%40mail.gmail.com.

Re: [Mpi-forum] June 2021 Voting Announcements and RC Document

[Wesley Bland via mpi-forum]

Hi all,

Tony just asked a good question off list about how to do the diff from 
December, but I think others will find this useful so I wanted to put it on the 
list:

It’s up to each person, but if I were doing it (which I guess I am ), I would 
start with the diff and see if it needs to be summarized beyond that. Here’s a 
link to the online version of the diff:

https://github.com/mpi-forum/mpi-standard/compare/mpi-4.0-rc-dec-2020...mpi-4.0-rc-june-2021
 
<https://github.com/mpi-forum/mpi-standard/compare/mpi-4.0-rc-dec-2020...mpi-4.0-rc-june-2021>

You can click on “60 changed files” at the top of the diff and pick just the 
file you want from there.

You can also get the same thing on the command line by fetching all of the 
remote tags and doing the comparison there (example with just the I/O chapter):

$ git fetch —all —tags
$ git diff mpi-4.0-rc-dec-2020  mpi-4.0-rc-june-2021 chap-io/io.tex

Thanks,
Wes

> On May 24, 2021, at 11:30 AM, Wesley Bland  wrote:
> 
> Hi all,
> 
> This is a bit of a long one with all of the announcements for the upcoming 
> meeting, so stick with me:
> 
> The RC document for the June meeting is now available on the website. You can 
> find it here: https://www.mpi-forum.org/docs/mpi-4.0/mpi40-rc-jun-21.pdf 
> <https://www.mpi-forum.org/docs/mpi-4.0/mpi40-rc-jun-21.pdf>
> 
> I’ve also posted all of the plenaries and votes for this meeting that come 
> from the ratification process. I’ll read each of these in the same way we did 
> the last meeting to move things along more quickly. Today also closes the 
> nomination period for officers. We’ll vote for those in the upcoming meeting.
> 
> Reminder to Chapter Chairs: As we’ve discussed previously, we’ll do a recap 
> of the changes that have happened to each chapter since December 2020. Please 
> have a slide or two ready to go over those changes..
> 
> You can find all of that on the agenda page: 
> https://www.mpi-forum.org/meetings/2021/06/agenda 
> <https://www.mpi-forum.org/meetings/2021/06/agenda>
> 
> Here’s that list:
> Procedure
> 
> Vote to delay MPI 4.0 for unresolved issues
> Vote to ratify MPI 4.0
> Elect MPI Forum Chair
> Elect MPI Forum Secretary
> Elect MPI Forum Treasurer
> Elect MPI Forum Document Editor
> No "No Votes"
> 
> #488 <https://github.com/mpi-forum/mpi-issues/issues/488>: Issue W 
> 'backward/semantic changes' - PR434 + PR445 + PR544 applied to RC-4-June
> #489 <https://github.com/mpi-forum/mpi-issues/issues/489>: Incomplete listing 
> of communicator duplication functions
> #501 <https://github.com/mpi-forum/mpi-issues/issues/501>: Add xref in 4.0 
> ChangeLog for LargeCount
> Errata Votes
> 
> #456 <https://github.com/mpi-forum/mpi-issues/issues/456>: Fix list of 
> functions that are callable at any time
> #500 <https://github.com/mpi-forum/mpi-issues/issues/500>: Fix LIS for MPI_T 
> events functions
> #495 <https://github.com/mpi-forum/mpi-issues/issues/495>: Remove LIS Changes 
> in I/O Chapter
> #458 <https://github.com/mpi-forum/mpi-issues/issues/458>: Issue A 'applang' 
> - PR444 + PR528 applied to RC-4-June
> #459 <https://github.com/mpi-forum/mpi-issues/issues/459>: Issue B 
> 'change-log' - PR434(change-log part) + PR529 applied to RC-4-June
> #460 <https://github.com/mpi-forum/mpi-issues/issues/460>: Issue C 'bindings' 
> - PR434(bindings part) + PR530 applied to RC-4-June
> #461 <https://github.com/mpi-forum/mpi-issues/issues/461>: Issue D 'contexts' 
> - PR484 + PR533 applied to RC-4-June
> #462 <https://github.com/mpi-forum/mpi-issues/issues/462>: Issue E 'dynamics' 
> - the first change of PR258 applied to RC-4-June
> #463 <https://github.com/mpi-forum/mpi-issues/issues/463>: Issue F 'terms' - 
> the second change of PR258 + PR534 applied to RC-4-June
> #464 <https://github.com/mpi-forum/mpi-issues/issues/464>: Issue G 
> 'datatypes' - PR531 applied to RC-4-June
> #465 <https://github.com/mpi-forum/mpi-issues/issues/465>: Issue H 'coll' - 
> PR532 applied to RC-4-June
> #435 <https://github.com/mpi-forum/mpi-issues/issues/435>: Issue I - Is 
> definition of local Session_init + collective Session_finalize pair broken?
> #491 <https://github.com/mpi-forum/mpi-issues/issues/491>: Issue L - Progress 
> references in General Index - for RC-4-June
> #453 <https://github.com/mpi-forum/mpi-issues/issues/453>: Clarifications of 
> PR#423 uses wrong language
> #433 <https://github.com/mpi-forum/mpi-issues/issues/433>: Handling of extra 
> state in dropped event handler for MPI_T
> #444 <https://github.com/mpi-forum/mpi-issues/issues/444>: Fix undefined 
> behaviour of MPI_Info_get_string caused by binding to MPI_Info_set
&

[Mpi-forum] June 2021 Voting Announcements and RC Document

[Wesley Bland via mpi-forum]

Hi all,

This is a bit of a long one with all of the announcements for the upcoming 
meeting, so stick with me:

The RC document for the June meeting is now available on the website. You can 
find it here: https://www.mpi-forum.org/docs/mpi-4.0/mpi40-rc-jun-21.pdf 


I’ve also posted all of the plenaries and votes for this meeting that come from 
the ratification process. I’ll read each of these in the same way we did the 
last meeting to move things along more quickly. Today also closes the 
nomination period for officers. We’ll vote for those in the upcoming meeting.

Reminder to Chapter Chairs: As we’ve discussed previously, we’ll do a recap of 
the changes that have happened to each chapter since December 2020. Please have 
a slide or two ready to go over those changes..

You can find all of that on the agenda page: 
https://www.mpi-forum.org/meetings/2021/06/agenda 


Here’s that list:
Procedure

Vote to delay MPI 4.0 for unresolved issues
Vote to ratify MPI 4.0
Elect MPI Forum Chair
Elect MPI Forum Secretary
Elect MPI Forum Treasurer
Elect MPI Forum Document Editor
No "No Votes"

#488 : Issue W 
'backward/semantic changes' - PR434 + PR445 + PR544 applied to RC-4-June
#489 : Incomplete listing 
of communicator duplication functions
#501 : Add xref in 4.0 
ChangeLog for LargeCount
Errata Votes

#456 : Fix list of 
functions that are callable at any time
#500 : Fix LIS for MPI_T 
events functions
#495 : Remove LIS Changes 
in I/O Chapter
#458 : Issue A 'applang' - 
PR444 + PR528 applied to RC-4-June
#459 : Issue B 'change-log' 
- PR434(change-log part) + PR529 applied to RC-4-June
#460 : Issue C 'bindings' - 
PR434(bindings part) + PR530 applied to RC-4-June
#461 : Issue D 'contexts' - 
PR484 + PR533 applied to RC-4-June
#462 : Issue E 'dynamics' - 
the first change of PR258 applied to RC-4-June
#463 : Issue F 'terms' - 
the second change of PR258 + PR534 applied to RC-4-June
#464 : Issue G 'datatypes' 
- PR531 applied to RC-4-June
#465 : Issue H 'coll' - 
PR532 applied to RC-4-June
#435 : Issue I - Is 
definition of local Session_init + collective Session_finalize pair broken?
#491 : Issue L - Progress 
references in General Index - for RC-4-June
#453 : Clarifications of 
PR#423 uses wrong language
#433 : Handling of extra 
state in dropped event handler for MPI_T
#444 : Fix undefined 
behaviour of MPI_Info_get_string caused by binding to MPI_Info_set
#424 : Sessions: need to 
update sections of standard describing initial error handler
#437 : LIS inout and 
C IN fix for Partitioned Communication
#446 : Fix to the 
Partitioned Communication Chapter for the 
rank/process/group/file/win/communicator nomenclature
#438 : Handling of enum 
argument on MPI_T_event_get_info
#454 : Add progress of 
partitioned communication sentence

In addition, I’d like to announce the 1st vote for issue #283: Add 
MPI_Delete_error_class, MPI_Delete_error_code, MPI_Delete_error_string 
 (PR #166 
). That’s on the agenda 
page as well.

If you have any other plenaries/votes to announce, please do so today. Martin 
will be updating the agenda later to include everything for the meeting. Note 
that we’ll need to have a voting block every day in order to accommodate our 
voting rules for a Final Ratification Meeting

Thanks,
Wes

___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: how to output yara rule file information in C language

[Wesley Shields]

metas is a pointer to a YR_META structure 
(https://github.com/VirusTotal/yara/blob/master/libyara/include/yara/types.h#L225).
 You can see how yara handles it when printing metadata about a rule here: 
https://github.com/VirusTotal/yara/blob/master/cli/yara.c#L1004

-- WXS

> On May 22, 2021, at 4:51 AM, 95 Daoge  wrote:
> 
> exampe:
> rule test_file
> {
>   meta:
>   author = "test"
>   description = "test mete display"
>   date = "20210522"
>   condition:
>   true
> }
> 
> use 
> yr_rule_metas_foreach(p, metas){
> printf("the message is :%s\n",metas->identifier);
> }
> i can only output :author descri and date but i want output 
> author = "test"
> description = "test mete display"
> date = "20210522"
> 
> is this possible?
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "YARA" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to yara-project+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/yara-project/000550e7-b234-45af-981f-0ab94464b4f8n%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"YARA" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to yara-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/yara-project/AE4AD0BF-0223-48B8-AB72-5B0842956865%40atarininja.org.

[Mpi-forum] June 2021 Registration Reminder

[Wesley Bland via mpi-forum]

Hi all,

I just want to remind folks to register for the June meeting. If you were 
looking at the logistics page before now, the link there was wrong. I’ve fixed 
that now. Please register here:

https://forms.gle/QNQ4LNZsktXai8uHA 

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: [OMPI devel] C style rules / reformatting

[Wesley Bland via devel]

Hey folks,

As a datapoint, in MPICH, we use GNU indent 
 for this.

Script to format code (either one file or the entire code tree) - 
https://github.com/pmodels/mpich/blob/main/maint/code-cleanup.bash 

Pre-commit hook that doubles as a CI checker - 
https://github.com/pmodels/mpich/blob/3e6c3ae11df33d6c02a025aaa5b145bd262d1c32/maint/hooks/pre-commit#L52-L94
 

 

There are (as always) a few gotchas, but overall it works pretty well. The main 
annoyance we discovered was that at least between version 2.2.11 and 2.2.12, 
there were changes made that changed the output formatting with the same set of 
input arguments, which is obviously a problem if people use different versions. 
So we lock in version 2.2.11. Unfortunately, that version is not the easiest to 
find and by default didn’t work on Mac OS IIRC (patch to fix Homebrew formula 
here ). You 
might be better served by moving on to the most recent version, but you 
probably want to pick a version and stick with it until you verify that it 
won’t cause problems otherwise. Maybe we should figure out a way to have 
multiple versions live alongside each other so people that work on both 
projects could have both versions. The project doesn’t seem to be particularly 
active so this probably isn’t a problem that will come up often.

We picked K formatting as a starting point and then customized a few things 

 based on our tastes. There are relatively sane defaults and a few different 
“sets” of defaults depending on what you prefer.

Let me know if you have any questions. I’d be happy to provide any pointers.

Thanks,
Wes

> On May 17, 2021, at 2:59 PM, Jeff Squyres (jsquyres) via devel 
>  wrote:
> 
> FYI: It was decided last week that we will abandon the current effort to 
> reformat master / v5.0.x according to style rules.
> 
> SHORT VERSION
> 
> We have already reformatted opal/ and tests/.  But the two PRs for 
> reformatting ompi/ brought up a whole bunch of issues that do not seem 
> resolvable via clang-format.  As such, we're just walking away: we're not 
> going to revert the reformatting that was done to opal/ and tests/ on master 
> and v5.0.x, but we're just going to close the ompi/ reformatting PRs without 
> merging.
> 
> Many thanks to Nathan who invested a lot of time in this; I'm sorry it didn't 
> fully work out.  :-(
> 
> MORE DETAIL
> 
> It turns out that clang-format actually parses the C code into internal 
> language primitives and then re-renders the code according to all the style 
> choices that you configure.  Meaning: you have to make decisions about every 
> single style choice (e.g., whether to put "&&" at the beginning or end of the 
> line, when expressions span multiple lines).
> 
> This is absolutely not what we want to do.  
> https://github.com/open-mpi/ompi/wiki/CodingStyle is intentionally very 
> "light touch": it only specifies a bare minimum of style rules -- the small 
> number of things that we could all agree on.  Everything outside of those 
> rules is not regulated.
> 
> Clang-format simply doesn't work that way: you have to make a decision for 
> every single style choice.
> 
> So we'll close https://github.com/open-mpi/ompi/pull/8816 and 
> https://github.com/open-mpi/ompi/pull/8923 without merging them.
> 
> If someone would like to find a better tool that can:
> 
> a) re-format the ompi/ and oshmem/ trees according to our "light touch" rules
> b) fail a CI test when a PR introduces a delta that results in code breaking 
> the "light touch" rules
> 
> Then great: let's have that conversation.  But clang-format is not going to 
> work for us, unfortunately.  :-(
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> 
> 
> 

Re: [google-appengine] Re: Where can your run "legacy" Google App Engine (Java) applications?

[wesley chun]

Howdy folks, yes, Ludo is correct. This is a new program we introduced into
private alpha recently, so if you're a Python 2, Java 6-8, or Go 1.6-1.11
user, this is the time to prototype an upgrade to Python 3, Java 11, and Go
1.12+. Keep in mind that not *all* previously built-in services will be
available and that new features/innovation will only happen w/the
standalone products like Cloud Datastore, Cloud Memorystore, Cloud Tasks,
etc. As I mentioned in my previous email, we're committed to supporting
legacy runtimes
<https://cloud.google.com/appengine/docs/standard/long-term-support> while
means App Engine is staying where it is, however those original bundled
services are just going to stay as-is, so we're encouraging folks to
migrate to "the new stuff."

The good news is that with the migration resources
<https://twitter.com/wescpy/status/1378050414449319937?utm_source=twitter_medium=unpaidsoc_campaign=CDR_wes_aap-serverless_modernizegae_codelabsannounce_201031_content=->we're
building can help you move off the bundled services to those standalone
services, and you can continue to use App Engine whether you're staying on
the 1st gen or modernizing/upgrading to 2nd gen. Alternatively, you can
break up large apps to run as a set of microservices on Cloud Functions
<http://cloud.google.com/functions>, or if you want to containerize your
app but still run serverlessly, you've now got Cloud Run
<http://cloud.google.com/run>. Back in the old days, App Engine and the
bundled services didn't give users many options, but with a more open App
Engine today and other serverless products, developers have way more
options than before!

On Wed, May 5, 2021 at 5:33 AM Linus Larsen  wrote:

> Wow, this is really great news I think.
>
> I was under the impression that Google was phasing out the "legacy"
> platform, so this is not the case?
>
> A big relief for all of us sitting with a bunch of Java 8 services were
> porting to second gen services is not really an option.
>
> / Linus
>
>
>
>
>
> tisdag 4 maj 2021 kl. 23:40:39 UTC+2 skrev ludovic.c...@gmail.com:
>
>>
>> Hi,
>> Ludo (from the Java App Engine team here).
>> Good news: as of today, we are providing to select customers a private
>> preview access to a new Java11 GAE runtime with many of the App Engine APIs
>> (com.google.appengine.api.*) support for easy GAE application upgrade from
>> Java8.
>> This new Java11 runtime is an extension of the previous Java11 runtime
>> <https://cloud.google.com/appengine/docs/standard/java11> (which did not
>> support the 'legacy' API), and it is based on Jetty 9.4 Web server and
>> existing well know Java Web Apps, configured with appengine-web.xml (not
>> app.yaml) under a WEB-INF/ web app directory, and same existing tooling
>> (Maven, Gradle).
>> It would be great if existing Java8 GAE customers could try this private
>> preview on a new version of their app (and obviously do not use it to
>> server production traffic yet), and give us feedback!
>>
>> Some of the major bundled GAE services the Private Preview now include:
>>
>>- - Memcache
>>- - Datastore / Objectify with GAE Datastore
>>- - URLfetch
>>- - Blobstore
>>- - Images
>>- - Task Queues
>>- - Users
>>- - Mail
>>
>>
>> If you would like to register for the Private Preview, please fill out
>> the Registration Form
>> <https://docs.google.com/forms/d/e/1FAIpQLSd1hFLA2UFSYwIMxm9ZI3pwigORZBgjJRH0qrnhtE7nvhhRCQ/viewform>
>> .
>> Registering will get you access to the Private Preview documentation,
>> which includes the full API docs for the runtime.
>>
>> Thanks for trying it now and helping us fine tuning it so we can make it
>> public soon!
>> Ludo
>>
>> On Thursday, April 29, 2021 at 5:56:51 PM UTC-7 Wesley C (Google) wrote:
>>
>>> At this time, you can run those applications with the "bundled services"
>>> on our Java 8 App Engine runtime
>>> <https://cloud.google.com/appengine/docs/standard/java>. That's the
>>> latest version w/the bundled services available. The other one is Java
>>> 11 but *without* bundled services
>>> <https://cloud.google.com/appengine/docs/standard/java11>. Also see the 
>>> documentation
>>> page highlighting the differences b/w both 1st and 2nd generation runtimes
>>> <https://cloud.google.com/appengine/docs/standard/runtimes>.
>>>
>>> While we're committed to supporting legacy runtimes
>>> <https://cloud.google.com/appengine/docs/standard/long-term-support>,
>>> we've also got guides to help developers m

Re: [google-appengine] Google Translate API & Permissions

[wesley chun]

@Joshua: your inquiry inspired me to do some research into this issue over
the past few months resulting in the following:

1. *Use Cloud client libraries:* yep, your experience was not fun for any
developer looking to use a Cloud API (whether App Engine or a simple
cmd-line script). One solution is to avoid the Google APIs client library
<https://developers.google.com/api-client-library> and use the Google Cloud
client libraries <http://cloud.google.com/apis/docs/cloud-client-libraries>
instead, and in your case just the one for Cloud Translation
(basic/v2
<https://cloud.google.com/translate/docs/reference/libraries/v2/python> or
advanced/v3
<https://cloud.google.com/translate/docs/reference/libraries/v3/python>).
(I'm also working on a blog post to outline the differences between
these *platform
vs. product* client libraries, so stay tuned for that.) With the Cloud
Translation client library (which hides a lot of low-level details), your
code sample can be as simple as:

from __future__ import print_function
import google.auth
from google.cloud import translate

TRANSLATE = translate.TranslationServiceClient()
_, PROJECT_ID = google.auth.default()
PARENT = 'projects/{}'.format(PROJECT_ID)
TARGET_LANG = 'es'
TEXT = 'Hello world'
DATA = {
'parent': PARENT,
'contents': [TEXT],
'target_language_code': TARGET_LANG,
}
try:# Python 3/advanced/v3
rsp = TRANSLATE.translate_text(request=DATA)
except TypeError:   # Python 2/basic/v2
rsp = TRANSLATE.translate_text(**DATA)
print(TEXT, '=', rsp.translations[0].translated_text)

It works in Python 2 and 3 without any modification:

$ python2 translate_demo2.py
Hello world = Hola Mundo
$ python3 translate_demo2.py
Hello world = Hola Mundo

You should be able to just drop something like this right into your App
Engine code (plus the necessary stuff in app.yaml and requirements.txt).
App Engine comes with a default service account
<https://cloud.google.com/appengine/docs/standard/python/service-account>,
so you don't need to mess with all you did unless you need to (create a
separate service account and public/private key-pair) for other reasons. To
run this script *locally* (as I did above), you *do* need to do that
(create a service acct & keypair, download the JSON credentials file to
your local system, then point GOOGLE_APPLICATION_CREDENTIALS to it), but
not on App Engine (nor Cloud Functions nor Cloud Run) as *all 3* have
default service accounts.

2. *Sample app:* I created a simple Python 2 GAE app that uses that Cloud
Translation code to get an idea of what you went through and discovered it
wasn't that bad if the product client library is used. Then I wanted to see
how challenging it would be to port it to Python 3 (since you got to at
some point) as well as running it locally. Then I thought, "Why not try to
throw the app into a Docker container for Cloud Run?" *Bottom-line*: today
I pushed to GitHub this "nebulous" sample app
<https://github.com/googlecodelabs/cloud-nebulous-serverless-python> that
can be deployed (at least) 8 different ways w/just minor config changes.
Eh, I'll write up a blog post on this one too when I get a chance.

I know the challenges weren't fun to deal with, but I hope these can help
you and other developers!
--Wesley

On Mon, Dec 7, 2020 at 10:10 AM Joshua Smith 
wrote:

> This problem is more systemic than that. The documentation lacks a
> step-by-step how-to. I understand that there are a lot of options, but I'm
> pretty sure my use case is very common:
>
> 1. I have a google app engine app
> 2. I want to call the translation API from that app
>
> I figured out how to do that from the translation API docs, but I lacked
> permission.
>
> I could not find any step by step instructions for giving permission. I
> found this:
>
> https://cloud.google.com/translate/docs/setup
>
> which pointed me to this:
>
> https://cloud.google.com/iam/docs/understanding-roles
>
> at which point a normal human is going to be ready to give up. Look at
> that second page! It's an endless stream of gobledegook.
>
> After getting the pointer from Amit that I need to add the role to IAM, I
> went to IAM & Admin in my console, and selected "roles". Spoiler alert:
> this is not where you do this.
>
> Amit mentioned "service accounts" so I went looking for that. I chose the
> "Service Accounts" section. I see my service account, and it has a "..."
> Actions menu. None of those actions are about adding roles.
>
> I click on the link for my service account, and see there's a tab for
> "permissions". Doesn't seem to be anywhere I can give it permissions there.
>
> Honestly, I've just given up again. I know that by fumbling around in the
> console I eventually ended up on a page where it wanted me to type an ema

Re: [plonegov-br] Categorização de Tags

[Wesley Lopes]

Olá Carolina!

Qual versão do IDG você está utilizando?  Aqui pra mim aparece na versão
2.1.1.

Wesley

Em sex., 30 de abr. de 2021 às 12:13, Carolina Machay <
carolina.mac...@gmail.com> escreveu:

> Bom dia.
> Verifiquei que o campo para inserção de novas tags não é exibido na Guia
> Categorização das Notícias. Alguém saberia, por gentileza, em que parte do
> Plone pode ser feita a correção dos campos do modo Edição?
>
> Muito obrigada.
> --
> Comunidade Plone no Governo
> Site: http://www.softwarelivre.gov.br/plone
> Wiki: http://colab.interlegis.leg.br/wiki/PloneGovBr
> Histórico:
> http://colab.interlegis.leg.br/search/?type=thread=latest=plonegov-br
> Lista: https://listas.interlegis.gov.br/mailman/listinfo/plonegov-br
-- 
Comunidade Plone no Governo
Site: http://www.softwarelivre.gov.br/plone
Wiki: http://colab.interlegis.leg.br/wiki/PloneGovBr
Histórico: 
http://colab.interlegis.leg.br/search/?type=thread=latest=plonegov-br
Lista: https://listas.interlegis.gov.br/mailman/listinfo/plonegov-br

Re: [plonegov-br] collective.prettydate, como forçar a instalação?

[Wesley Lopes]

Alexandre,

tente usar as versões do zc.buildout/setuptools que estão no master:

https://github.com/plonegovbr/portal.buildout/blob/7c35da28a94ff9002dcb0ae31b531965960a869f/buildout.d/versions.cfg#L180-L181

Em sáb., 1 de mai. de 2021 às 10:29, Alexandre Chagas <
alexandre@gmail.com> escreveu:

> Olá Marco,
>
> Como instalo o plone separadamente para depois instalar o IDG, nao
> encontrei o arquivo default.cfg, havia tentado instalar seguindo os passos
> indicado num post anterior, utilizando virtualenv, etc. mas sem sucesso e
> acabei voltando para  instalar manualmente.
>
> o index = https://pypi estava correto, havia adicionado não só no
> buildout.cfg, mas o mesmo já se encontrava no base.cfg por padrão.
>
> Cheguei a conclusão que deverei tentar resolver o problema (que ainda
> persiste) com SSL.
>
> No entanto, consegui instalar o portal adicionando complemento por
> complemento no eggs. Está rodando!
> Mas terei que voltar e estudar como resolver a questão do SSL, embora
> procurei algumas dicas no github e outros, não obtive êxito.
>
> Por hora, o portal está no ar e aparentemente sem problemas.
> encontrado uma solução simples para o SSL, colocarei aqui para ficar
> registrado.
>
> Grato pela ajuda!
> []s
>
>
> Em sáb., 1 de mai. de 2021 às 01:56, Marco Antonio de Albuquerque Silva <
> marco.albuquer...@ifal.edu.br> escreveu:
>
>> Boa noite, Alexandre.
>>
>> Parece ser o caso do buildout estar com o index definido de forma errada.
>>
>> https://www.buildout.org/en/latest/reference.html
>>
>> Se não tiver um index customizado, tenta forçar explicitamente, no
>> arquivo buildout/default.cfg:
>>
>> [buildout]
>> index = https://pypi.python.org/simple/
>>
>> Atenciosamente,
>>
>> Em sex., 30 de abr. de 2021 às 17:33, Alexandre Chagas <
>> alexandre@gmail.com> escreveu:
>>
>>> Boa tarde pessoal,
>>> Como faço para forçar a instalação do collective.prettydate?
>>>
>>> https://github.com/collective/collective.prettydate
>>> https://github.com/collective/collective.prettydate.git
>>>
>>> Estou instalando o IDG 2.1.1 da seguinte forma:
>>> 1-instalo o plone 4.3.19
>>> 2-atualizo o versions.cfg (
>>> https://raw.githubusercontent.com/plonegovbr/portalpadrao.release/master/2.1.1/versions.cfg
>>> )
>>> 3-altero o buildout.cfg (eggs = brasil.gov.portal)
>>> ... e executo o buildout (sempre instalei assim, questão de preferência
>>> )
>>>
>>> abaixo o erro, grato ;)
>>>
>>> <>
>>> Getting required 'collective.prettydate==1.2.2'
>>> We have no distributions for collective.prettydate that satisfies
>>> 'collective.prettydate==1.2.2'.
>>> Download error on http://download.zope.org/ppix/: [SSL:
>>> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661) -- Some
>>> packages may not be found!
>>> Download error on http://download.zope.org/distribution/: [SSL:
>>> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661) -- Some
>>> packages may not be found!
>>> Couldn't find index page for 'collective.prettydate' (maybe misspelled?)
>>> Getting distribution for 'collective.prettydate==1.2.2'.
>>> Couldn't find index page for 'collective.prettydate' (maybe misspelled?)
>>> While:
>>>   Installing client1.
>>>   Getting distribution for 'collective.prettydate==1.2.2'.
>>> Error: Couldn't find a distribution for 'collective.prettydate==1.2.2'.
>>> << >>
>>>
>>> Apesar de acusar erro de certificado, não acredito ser o problema,
>>> porque aconteceu com outros pacotes e seguiram instalando.
>>>
>>> Grato.
>>>
>>> --
>>> *Alexandre Chagas*
>>>
>>> Analista de Experiência do Usuário - UX/UI Designer
>>> Ilustração e Animação Web 2D, 3D | Plone | Wordpress
>>> [image: https://www.linkedin.com/in/alexandre-chagas-44089497]
>>> 
>>> (61) 98301-0009
>>> --
>>> Comunidade Plone no Governo
>>> Site: http://www.softwarelivre.gov.br/plone
>>> Wiki: http://colab.interlegis.leg.br/wiki/PloneGovBr
>>> Histórico:
>>> http://colab.interlegis.leg.br/search/?type=thread=latest=plonegov-br
>>> Lista: https://listas.interlegis.gov.br/mailman/listinfo/plonegov-br
>>
>>
>>
>> --
>> Marco Antonio de Albuquerque Silva
>> Analista de Tecnologia da Informação - CORE/DTI/IFAL
>> --
>> Comunidade Plone no Governo
>> Site: http://www.softwarelivre.gov.br/plone
>> Wiki: http://colab.interlegis.leg.br/wiki/PloneGovBr
>> Histórico:
>> http://colab.interlegis.leg.br/search/?type=thread=latest=plonegov-br
>> Lista: https://listas.interlegis.gov.br/mailman/listinfo/plonegov-br
>
>
>
> --
> *Alexandre Chagas*
>
> Analista de Experiência do Usuário - UX/UI Designer
> Ilustração e Animação Web 2D, 3D | Plone | Wordpress
> [image: https://www.linkedin.com/in/alexandre-chagas-44089497]
> 
> (61) 98301-0009
> --
> Comunidade Plone no Governo
> Site: http://www.softwarelivre.gov.br/plone
> Wiki: http://colab.interlegis.leg.br/wiki/PloneGovBr
> Histórico:
> 

Re: [google-appengine] Re: Where can your run "legacy" Google App Engine (Java) applications?

[wesley chun]

At this time, you can run those applications with the "bundled services" on
our Java 8 App Engine runtime
<https://cloud.google.com/appengine/docs/standard/java>. That's the latest
version w/the bundled services available. The other one is Java 11 but
*without* bundled services
<https://cloud.google.com/appengine/docs/standard/java11>. Also see
the documentation
page highlighting the differences b/w both 1st and 2nd generation runtimes
<https://cloud.google.com/appengine/docs/standard/runtimes>.

While we're committed to supporting legacy runtimes
<https://cloud.google.com/appengine/docs/standard/long-term-support>, we've
also got guides to help developers move off bundled services so they can
upgrade to Java 11
<https://cloud.google.com/appengine/docs/standard/java11/java-differences>.
We're planning additional resources to help users upgrade their apps, so
stay tuned for those. The first bunch for Python launched recently
<https://twitter.com/wescpy/status/1378050414449319937?utm_source=twitter_medium=unpaidsoc_campaign=CDR_wes_aap-serverless_modernizegae_codelabsannounce_201031_content=->,
and we're planning equivalent resources for Java after all the Python ones
are done.

Cheers,
--Wesley

On Thu, Apr 29, 2021 at 3:21 PM 'cyberquarks' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Hi, our app is built on Google App Engine (Java) version 1.9.40 where all
> components are "integrated" into the runtime, the Datastore, the Task Queue
> etc.
>
> On Friday, April 30, 2021 at 1:53:21 AM UTC+8 Elliott (Cloud Platform
> Support) wrote:
>
>>
>> Hello,
>>
>> I understand that you would like to run a legacy Java App Engine
>> application on the infrastructure that exists currently in Google Cloud
>> Platform without modifying the existing project.
>>
>> I was able to find a document
>> <https://cloud.google.com/appengine/docs/standard/long-term-support>,
>> which describes the legacy 8 version of Java still supported. What version
>> of Java are you using? Are you using Google App Standard or Google App Flex?
>>
>> I’m thinking that depending on your answer, you may choose to use
>> Containers in Google Cloud Run <https://cloud.google.com/run> to create
>> your environment but you indicated that you do not wish to modify your
>> project.
>>
>> So to provide more options, I would ask you to give detail about your
>> project.
>>
>>
>>
>> On Thursday, April 29, 2021 at 10:14:18 AM UTC-4 qqua...@protonmail.com
>> wrote:
>>
>>> Where can you run GAE application built with "integrated" Datastore?
>>> Meaning, those application that were build prior to Google platform making
>>> the Datastore a separate service from the "core" GAE service. That is
>>> without modifying the project.
>>>
>>> Can the current Google App Engine run "legacy" applications?
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/eeeaee50-0677-4f9d-9b54-a3206409e6fcn%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/eeeaee50-0677-4f9d-9b54-a3206409e6fcn%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google Cloud by day; at night...
Python training & consulting : http://CyberwebConsulting.com
"Core Python" books : http://CorePython.com
Python blog: http://wescpy.blogspot.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA4-%3DTvzcK%2BDVfnX5cWhTzKnsEEhxb58CHVtnA5vPL11Hw%40mail.gmail.com.

[rdo-dev] FYI.. docker.io rate limiting

[Wesley Hayutin]

Greetings,

Most of the tripleo ci jobs at
https://ci.centos.org/view/rdo/view/promotion-pipeline/
are now failing due to docker.io rate limits.  This may impact how often
the various releases promote.

0/
___
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev

To unsubscribe: dev-unsubscr...@lists.rdoproject.org

Re: [google-appengine] Re: GAE Microservices

[wesley chun]

Hi Mukesh, in addition to my colleague Andrew's recommendations, I'll add
the following:

   1. You inquired about microservices. We have a Python 2 *App Engine
   microservices architecture*
   
<https://cloud.google.com/appengine/docs/standard/python/microservices-on-app-engine>
document
   that should be interesting to you.
   2. You could probably replicate a similar architecture on Python 3,
   however Python 3 on App Engine slightly different (no bundled services) so
   we didn't publish a similar page for 3.x. Another reason is that such an
   architecture on Python 3 may be better suited for its sister product, Google
   *Cloud Functions*
   <https://cloud.google.com/functions/docs/concepts/python-runtime>. What
   you call "modules" can be implemented as individual functions.
   3. If you're going to store data in Firebase, you might as well use
*Firebase
   Auth <https://firebase.google.com/docs/auth>* to authenticate your
   users. Learn about that and other auth options on App Engine from this
   page
   
<https://cloud.google.com/appengine/docs/standard/python3/authenticating-users>
   in the docs. (It's very likely the same technique can be used w/Cloud
   Functions as well).
   4. Heads-up there's a "new" product that combines the Firebase RTDB
   <http://firebase.google.com/products/realtime-database> + Google
   Cloud's NoSQL Cloud Datastore <http://cloud.google.com/datastore>
called *Cloud
   Firestore* <http://cloud.google.com/firestore> that launched in 2017
   <https://firebase.googleblog.com/2017/10/introducing-cloud-firestore.html>
   as the next-gen successor to both. If you're considering one of them,
   here's the page in the docs helping you decide b/w Firebase & Firestore
   <https://firebase.google.com/docs/database/rtdb-vs-firestore>.

Good luck and let us know how it goes!
--Wesley

On Sun, Apr 25, 2021 at 6:09 AM mukesh raj dass 
wrote:

> Hi
>
> Appreciate the feedback.
>
> I am using Standard environment in Python 3.7.  I need to create a URL for
> services that can only be access from inside the application after login
> authentication.  The
> services will be modules that will available.  It cannot be accessed from
> outside the application.  Do i restrict access via app.yaml only to allow
> access from within the application into a module which will be a "service"
> .  How best to do it ?
>
> Mukesh Raj
>
>
> On Friday, 23 April 2021 at 18:24:40 UTC+10 anco...@google.com wrote:
>
>> Which documentation are you following? Are you thinking of using GAE Flex
>> or GAE Standard?
>>
>> I have added a couple of links that you might find interesting that
>> details how requests are routed in GAE. Please note, this is for Python but
>> the concept is the same for other languages.
>>
>>-
>>
>>How Requests are Routed
>>
>> <https://cloud.google.com/appengine/docs/standard/python3/how-requests-are-routed>
>>-
>>
>>Communicating Between Your Services
>>
>> <https://cloud.google.com/appengine/docs/standard/python3/communicating-between-services>
>>-
>>
>>Serverless network endpoint groups overview
>>
>> <https://cloud.google.com/load-balancing/docs/negs/serverless-neg-concepts>
>>
>>
>> On Monday, April 12, 2021 at 11:54:36 AM UTC+2 optimum...@gmail.com
>> wrote:
>>
>>> Hi
>>>
>>> I am trying to develop an GAE with multiple modules each having distinct
>>> codes talking to Firebase.  A client might need an app with only 2 modules
>>> and other might need 5 modules...i was hoping to load them as services or
>>> microservices...problem is how to connect them together ?
>>>
>>> It is like going to an accounting system and having a GL, Job Costing,
>>> Project costing as a separate module.  In the main entry point  (services:
>>> default) there will be a button to go to each services or modules  From
>>> what i understand in the documentation...each services (previously modules)
>>> cannot access to each of them unless via REST.
>>>
>>> Any bright ideas how to do it in GAE using Firebase ?
>>>
>>> Appreciate the input.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/b7a45753-f14a-41ab-adb1-34f0daa4c12en%40googlegroups.com
> <https://groups.google.c

[PATCH] usb: gadget: Fix double free of device descriptor pointers

[Wesley Cheng]

From: Hemant Kumar 

Upon driver unbind usb_free_all_descriptors() function frees all
speed descriptor pointers without setting them to NULL. In case
gadget speed changes (i.e from super speed plus to super speed)
after driver unbind only upto super speed descriptor pointers get
populated. Super speed plus desc still holds the stale (already
freed) pointer. Fix this issue by setting all descriptor pointers
to NULL after freeing them in usb_free_all_descriptors().

Signed-off-by: Hemant Kumar 
Signed-off-by: Wesley Cheng 
---
 drivers/usb/gadget/config.c | 4 
 1 file changed, 4 insertions(+)

diff --git a/drivers/usb/gadget/config.c b/drivers/usb/gadget/config.c
index 2d11535..8bb2577 100644
--- a/drivers/usb/gadget/config.c
+++ b/drivers/usb/gadget/config.c
@@ -194,9 +194,13 @@ EXPORT_SYMBOL_GPL(usb_assign_descriptors);
 void usb_free_all_descriptors(struct usb_function *f)
 {
usb_free_descriptors(f->fs_descriptors);
+   f->fs_descriptors = NULL;
usb_free_descriptors(f->hs_descriptors);
+   f->hs_descriptors = NULL;
usb_free_descriptors(f->ss_descriptors);
+   f->ss_descriptors = NULL;
usb_free_descriptors(f->ssp_descriptors);
+   f->ssp_descriptors = NULL;
 }
 EXPORT_SYMBOL_GPL(usb_free_all_descriptors);
 
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH] usb: dwc3: gadget: Avoid canceling current request for queuing error

[Wesley Cheng]

On 4/15/2021 12:28 PM, Thinh Nguyen wrote:
> Thinh Nguyen wrote:
>> Wesley Cheng wrote:
>>>
>>>
>>> On 4/14/2021 11:26 PM, Felipe Balbi wrote:
>>>> Wesley Cheng  writes:
>>>>
>>>>> If an error is received when issuing a start or update transfer
>>>>> command, the error handler will stop all active requests (including
>>>>> the current USB request), and call dwc3_gadget_giveback() to notify
>>>>> function drivers of the requests which have been stopped.  Avoid
>>>>> having to cancel the current request which is trying to be queued, as
>>>>> the function driver will handle the EP queue error accordingly.
>>>>> Simply unmap the request as it was done before, and allow previously
>>>>> started transfers to be cleaned up.
>>>>>
>>>>> Signed-off-by: Wesley Cheng 
>>>>> ---
>>>>>  drivers/usb/dwc3/gadget.c | 5 +
>>>>>  1 file changed, 5 insertions(+)
>>>>>
>>>>> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
>>>>> index e1b04c97..4200775 100644
>>>>> --- a/drivers/usb/dwc3/gadget.c
>>>>> +++ b/drivers/usb/dwc3/gadget.c
>>>>> @@ -1399,6 +1399,11 @@ static int __dwc3_gadget_kick_transfer(struct 
>>>>> dwc3_ep *dep)
>>>>>   if (ret == -EAGAIN)
>>>>>   return ret;
>>>>>  
>>>>> + /* Avoid canceling current request, as it has not been started 
>>>>> */
>>>>> + if (req->trb)
>>>>> + memset(req->trb, 0, sizeof(struct dwc3_trb));
>>>>
>>>> we don't need a full memset. I think ensuring HWO bit is zero is enough.
>>>>
>>> Hi Felipe,
>>>
>>> Thanks for the input/review, will make this change to just clear the HWO.
>>>
>>
>> Make sure to increment the dequeue pointer also. I think you can use
>> dwc3_gadget_ep_skip_trbs().
>>
> 
> Nevermind. There maybe a problem with using dwc3_gadget_ep_skip_trbs().
> 
> Thinh
> 
Hi Thinh,

Thank you for your input.  In this case (if kick transfer fails w/ an
error), would we still need to mess with the enqueue/dequeue pointers?
Not sure if my assumption is correct, but the TRB wouldn't have been
started, so we can use the same (failed) TRB for future requests, right?

I think one thing I will need to update is to loop through num_trbs and
clear all HWO bits if the above is not needed.

Thanks
Wesley Cheng

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: Wi-fi imbutido não encontra nenhuma rede

[Wesley Davi]

Acho bem válido tentar a solução que o Ricardo apresentou.

#apt-cache search realtek
Verifica qual vai atender sua placa e instala, lembrando do non-free no
sources.


Em sáb., 17 de abr. de 2021 às 18:36, riesdra  escreveu:

> Se tiver acesso a internet pelo cabo instale o pacote firmware-realtek
> * Precisa do non-free no sources.
>
> Talvez isto resolva.
>
> --
>
>
>
> *Ricardo Libanio*
>
>  On Sáb, 17 abr 2021 16:33:46 -0300 *
> leonardodearaujoaugu...@gmail.com  *
> wrote 
>
> Estou com dificuldades para fazer com que a minha placa Realtek
> 8188CE (imbutida, notebook Positivo C14CR21 (não tenho informação sobre o
> modelo específico de notebook, mas segue a ficha pelo hw-probe.
> https://linux-hardware.org/?probe=2829ea9d87))
>
> Resultado de inxi -n:
>
> cynthia@cy:~$ inxi -n
>
> Network:
>
>   Device-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce
>
>   IF: wlp1s0 state: down mac: 9a:53:9b:7a:84:35
>
>   Device-2: JMicron JMC250 PCI Express Gigabit Ethernet driver: jme
>
>   IF: enp2s0f5 state: down mac: 80:ee:73:79:ec:99
>
>   IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac:
> ae:27:3e:fe:26:72
>
>
> Ao erro: em tese a placa é reconhecida e aparentemente funciona, mas não
> localiza nenhum SSID. Tentei conectar diretamente à rede existente, sem
> sucesso.
>
> O driver que o sistema utiliza é o rtl8192ce. Encontrei também um driver
> alternativo no github, pra nenhum efeito. Tentei utilizar o ndiswrapper
> para tentar carregar um driver windows (sei que a placa funciona, ela é
> funcional no windows 10) e igualmente não obtive sucesso.
>
> Alguém com experiência nesse dispositivo poderia auxiliar? Posso prover
> logs se necessário.
>
> Obrigado!
>
>
>

-- 
Att., Wesley Davi da Silva

Re: [PATCH] usb: dwc3: gadget: Avoid canceling current request for queuing error

[Wesley Cheng]

On 4/14/2021 11:26 PM, Felipe Balbi wrote:
> Wesley Cheng  writes:
> 
>> If an error is received when issuing a start or update transfer
>> command, the error handler will stop all active requests (including
>> the current USB request), and call dwc3_gadget_giveback() to notify
>> function drivers of the requests which have been stopped.  Avoid
>> having to cancel the current request which is trying to be queued, as
>> the function driver will handle the EP queue error accordingly.
>> Simply unmap the request as it was done before, and allow previously
>> started transfers to be cleaned up.
>>
>> Signed-off-by: Wesley Cheng 
>> ---
>>  drivers/usb/dwc3/gadget.c | 5 +
>>  1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
>> index e1b04c97..4200775 100644
>> --- a/drivers/usb/dwc3/gadget.c
>> +++ b/drivers/usb/dwc3/gadget.c
>> @@ -1399,6 +1399,11 @@ static int __dwc3_gadget_kick_transfer(struct dwc3_ep 
>> *dep)
>>  if (ret == -EAGAIN)
>>  return ret;
>>  
>> +/* Avoid canceling current request, as it has not been started 
>> */
>> +if (req->trb)
>> +memset(req->trb, 0, sizeof(struct dwc3_trb));
> 
> we don't need a full memset. I think ensuring HWO bit is zero is enough.
> 
Hi Felipe,

Thanks for the input/review, will make this change to just clear the HWO.

Thanks
Wesley Cheng

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

[PATCH] usb: dwc3: gadget: Avoid canceling current request for queuing error

[Wesley Cheng]

If an error is received when issuing a start or update transfer
command, the error handler will stop all active requests (including
the current USB request), and call dwc3_gadget_giveback() to notify
function drivers of the requests which have been stopped.  Avoid
having to cancel the current request which is trying to be queued, as
the function driver will handle the EP queue error accordingly.
Simply unmap the request as it was done before, and allow previously
started transfers to be cleaned up.

Signed-off-by: Wesley Cheng 
---
 drivers/usb/dwc3/gadget.c | 5 +
 1 file changed, 5 insertions(+)

diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index e1b04c97..4200775 100644
--- a/drivers/usb/dwc3/gadget.c
+++ b/drivers/usb/dwc3/gadget.c
@@ -1399,6 +1399,11 @@ static int __dwc3_gadget_kick_transfer(struct dwc3_ep 
*dep)
if (ret == -EAGAIN)
return ret;
 
+   /* Avoid canceling current request, as it has not been started 
*/
+   if (req->trb)
+   memset(req->trb, 0, sizeof(struct dwc3_trb));
+   dwc3_gadget_del_and_unmap_request(dep, req, ret);
+
dwc3_stop_active_transfer(dep, true, true);
 
list_for_each_entry_safe(req, tmp, >started_list, list)
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

[google-appengine] More migration resources

[wesley chun]

Greetings long-time App Engine developers,

If you're running on Python 2, Java 6-8, Go 1.6-1.11, and PHP 5, we'd like
to encourage you to consider upgrading to Python 3, Java 11, Go 1.12+, and
PHP 7. The issue facing many of you is that moving to the next-gen App
Engine platform involves two significant changes, so we understand why
there has been some hesitancy:

   1. Upgrading to a newer language version
   2. Moving from bundled to unbundled/best-of-breed services

While Google can't help with the former, we *can* do something about the
latter. Last month, my colleague announced
<https://groups.google.com/g/google-appengine/c/6Ws9IXl_QmM/m/3ZvsIozbAAAJ> a
community-driven repo of migration samples
<https://github.com/GoogleCloudPlatform/appengine-python2-3-migration>. A
few weeks ago, I introduced a series of codelab tutorials
<https://twitter.com/wescpy/status/1378050414449319937?utm_source=twitter_medium=unpaidsoc_campaign=CDR_wes_aap-serverless_modernizegae_codelabsannounce_201031_content=->
to give users hands-on experience migrating unbundled services, starting
with Python as those developers have even greater challenges due to Python
3 not being backwards-compatible to Python 2. There is also content for
those interested in containerizing their App Engine apps (for Cloud Run).

These are just a few steps we're taking to help existing users modernize
their apps. Stay tuned for additional resources coming soon from the App
Engine team.

Best regards,
--Wesley
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google Cloud by day; at night...
Python training & consulting : http://CyberwebConsulting.com
"Core Python" books : http://CorePython.com
Python blog: http://wescpy.blogspot.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA50wfHow%3D6ZuD-yC2v4z7t_ydFnQDknppN04N6SumEtKA%40mail.gmail.com.

[Mpi-forum] Registration Open for June 2021 MPI Forum Meeting

[Wesley Bland via mpi-forum]

Hi all,

The registration page for the June meeting is now open. You can find the 
details on the logistics page 
. As usual for our 
virtual meetings, registration is free, but required. The link directly to the 
registration form is here:

https://forms.gle/ACFkW6oGy1bgT7pD9 

Registrations after the first voting block begins (usually scheduled for 
12:00pm US Central on June 7, 2021) will not count toward voting eligibility 
for this meeting. If you have questions, please let me know.

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: [PATCH] Revert "usb: dwc3: gadget: Prevent EP queuing while stopping transfers"

[Wesley Cheng]

On 4/1/2021 4:55 AM, Martin Kepplinger wrote:
> This reverts commit 9de47c3737e0c0207beb03615b320cabe495.
> 
> Signed-off-by: Martin Kepplinger 
> ---
> 
> I more or less blindly report:
> commit 9de47c ("usb: dwc3: gadget: Prevent EP queuing while stopping
> transfers") results in the below error every time I connect the type-c
> connector to the dwc3, configured with serial and ethernet gadgets.
> 
> fyi, I apply the following to dwc3 on this port:
> dr_mode = "otg";
> snps,dis_u3_susphy_quirk;   
> hnp-disable;
> srp-disable;
> adp-disable;
> usb-role-switch;
> 
> v5.12-rc5 does not have this error so I'm not sure whether it's
> more appropriate to add something to dwc3 than reverting. I hope usb
> people to know better and maybe even see the problem.
> 
> thanks,
>martin
> 
Hi Martin,

This has been fixed with the below:
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-linus=5aef629704ad4d983ecf5c8a25840f16e45b6d59

Can you pull that in and give it a try?

Thanks
Wesley Cheng

> 
> 
> 
> [   51.148220] [ cut here ]
> [   51.148241] dwc3 3810.usb: No resource for ep2in
> [   51.148376] WARNING: CPU: 0 PID: 299 at drivers/usb/dwc3/gadget.c:360 
> dwc3_send_gadget_ep_cmd+0x570/0x740 [dwc3]
> [   51.148431] Modules linked in: aes_ce_ccm rfcomm algif_hash algif_skcipher 
> af_alg bnep qmi_wwan cdc_wdm usbnet mii option usb_wwan usbserial caam_jr 
> caamhash_desc caamalg_desc crypto_engine mousedev redpine_sdio redpine_91x 
> bluetooth uas usb_storage mac80211 st_lsm6dsx_spi aes_ce_blk crypto_simd 
> crct10dif_ce cfg80211 ghash_ce sha2_ce sha1_ce bq25890_charger s5k3l6xx 
> snd_soc_wm8962 hi846 vcnl4000 leds_lm3560 edt_ft5x06 ofpart 
> industrialio_triggered_buffer tps6598x st_lsm6dsx_i2c st_lsm6dsx kfifo_buf 
> gnss_mtk typec mxc_mipi_csi2_yav gnss_serial mx6s_capture gnss 
> videobuf2_dma_contig videobuf2_memops spi_nor v4l2_fwnode videobuf2_v4l2 
> videobuf2_common snd_soc_gtm601 snd_soc_simple_card videodev mtd 
> snd_soc_simple_card_utils mc snd_soc_fsl_sai imx_pcm_dma caam error 
> snvs_pwrkey imx_sdma virt_dma snd_soc_core imx2_wdt snd_pcm_dmaengine snd_pcm 
> watchdog snd_timer snd soundcore pwm_vibra rfkill_hks rfkill ledtrig_timer 
> usb_f_acm u_serial usb_f_rndis g_multi usb_f_mass_storage u_ether
> [   51.148759]  libcomposite ledtrig_pattern fuse ip_tables x_tables ipv6 
> xhci_plat_hcd xhci_hcd usbcore dwc3 cdns_mhdp_imx ulpi cdns_mhdp_drmcore 
> udc_core imx_dcss roles usb_common phy_fsl_imx8mq_usb clk_bd718x7
> [   51.148837] CPU: 0 PID: 299 Comm: irq/64-dwc3 Not tainted 
> 5.11.11-librem5-00334-ge4c4ff3624e9 #218
> [   51.148848] Hardware name: Purism Librem 5r4 (DT)
> [   51.148854] pstate: 6085 (nZCv daIf -PAN -UAO -TCO BTYPE=--)
> [   51.148863] pc : dwc3_send_gadget_ep_cmd+0x570/0x740 [dwc3]
> [   51.148894] lr : dwc3_send_gadget_ep_cmd+0x570/0x740 [dwc3]
> [   51.148924] sp : 800011cb3ac0
> [   51.148929] x29: 800011cb3ac0 x28: 032a7b00 
> [   51.148942] x27: 0327da00 x26:  
> [   51.148954] x25: ffea x24: 0006 
> [   51.148967] x23: bee1c080 x22: 800011cb3b7c 
> [   51.148979] x21: 0406 x20: bf17 
> [   51.148992] x19: 0001 x18:  
> [   51.149004] x17:  x16:  
> [   51.149016] x15:  x14: 8000114512c0 
> [   51.149028] x13: 1698 x12: 0040 
> [   51.149040] x11: 80001151a6f8 x10: e000 
> [   51.149052] x9 : 8000100b2b7c x8 : 80001146a6f8 
> [   51.149065] x7 : 80001151a6f8 x6 :  
> [   51.149077] x5 : bf939948 x4 :  
> [   51.149089] x3 : 0027 x2 :  
> [   51.149101] x1 :  x0 : 049ae040 
> [   51.149114] Call trace:
> [   51.149120]  dwc3_send_gadget_ep_cmd+0x570/0x740 [dwc3]
> [   51.149150]  __dwc3_gadget_ep_enable+0x288/0x4fc [dwc3]
> [   51.149179]  dwc3_gadget_ep_enable+0x6c/0x15c [dwc3]
> [   51.149209]  usb_ep_enable+0x48/0x110 [udc_core]
> [   51.149251]  rndis_set_alt+0x138/0x1c0 [usb_f_rndis]
> [   51.149276]  composite_setup+0x674/0x194c [libcomposite]
> [   51.149314]  dwc3_ep0_interrupt+0x9c4/0xb9c [dwc3]
> [   51.149344]  dwc3_thread_interrupt+0x8bc/0xe74 [dwc3]
> [   51.149374]  irq_thread_fn+0x38/0xb0
> [   51.1

Re: [OPSAWG] Tsvart last call review of draft-ietf-opsawg-vpn-common-06

[Wesley Eddy]

Your response all sounds good to me, thanks.

On 4/1/2021 3:14 AM, mohamed.boucad...@orange.com wrote:

Hi Wes,

Thank you for the review.

Please see inline.

...


___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

[OPSAWG] Tsvart last call review of draft-ietf-opsawg-vpn-common-06

[Wesley Eddy via Datatracker]

Reviewer: Wesley Eddy
Review result: Almost Ready

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-...@ietf.org if you reply to or forward this review.

(1) I noticed in the "qos-classification-policy" there is "l4" support either
TCP or UDP.  It isn't clear if other transport protocols are purposefully not
included.  Should this also support SCTP and/or DCCP, or other transport
protocol numbers in general?  Are the QUIC aspects that might be matched
contained within the UDP fields supported?

(2) Is the allowable MTU another aspect of VPN services that should be able to
be expressed?

(3) ICMP isn't mentioned as an identity type, and I wondered if this should be.



___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Re: [PATCH v3 2/2] usb: dwc3: Fix DRD mode change sequence following programming guide

[Wesley Cheng]

On 3/29/2021 6:19 PM, Thinh Nguyen wrote:
> Wesley Cheng wrote:
>>
>>
>> On 3/6/2021 3:39 PM, Thinh Nguyen wrote:
>>> Wesley Cheng wrote:
>>>>
>>>> On 1/7/2021 5:51 PM, John Stultz wrote:
>>>>> In reviewing the previous patch, Thinh Nguyen pointed out that
>>>>> the DRD mode change sequence should be like the following when
>>>>> switching from host -> device according to the programming guide
>>>>> (for all DRD IPs):
>>>>> 1. Reset controller with GCTL.CoreSoftReset
>>>>> 2. Set GCTL.PrtCapDir(device)
>>>>> 3. Soft reset with DCTL.CSftRst
>>>>> 4. Then follow up with the initializing registers sequence
>>>>>
>>>>> The current code does:
>>>>> a. Soft reset with DCTL.CSftRst on driver probe
>>>>> b. Reset controller with GCTL.CoreSoftReset (added in previous
>>>>>patch)
>>>>> c. Set GCTL.PrtCapDir(device)
>>>>> d. < missing DCTL.CSftRst >
>>>>> e. Then follow up with initializing registers sequence
>>>>>
>>>>> So this patch adds the DCTL.CSftRst soft reset that was currently
>>>>> missing from the dwc3 mode switching.
>>>>>
>>>>> Cc: Felipe Balbi 
>>>>> Cc: Tejas Joglekar 
>>>>> Cc: Yang Fei 
>>>>> Cc: YongQin Liu 
>>>>> Cc: Andrzej Pietrasiewicz 
>>>>> Cc: Thinh Nguyen 
>>>>> Cc: Jun Li 
>>>>> Cc: Mauro Carvalho Chehab 
>>>>> Cc: Greg Kroah-Hartman 
>>>>> Cc: linux-...@vger.kernel.org
>>>>> Signed-off-by: John Stultz 
>>>>> ---
>>>>> Feedback would be appreciated. I'm a little worried I should be
>>>>> conditionalizing the DCTL.CSftRst on DRD mode controllers, but
>>>>> I'm really not sure what the right thing to do is for non-DRD
>>>>> mode controllers.
>>>>> ---
>>>>>  drivers/usb/dwc3/core.c | 3 +++
>>>>>  1 file changed, 3 insertions(+)
>>>>>
>>>>> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
>>>>> index b6a6b90eb2d5..71f8b07ecb99 100644
>>>>> --- a/drivers/usb/dwc3/core.c
>>>>> +++ b/drivers/usb/dwc3/core.c
>>>>> @@ -40,6 +40,8 @@
>>>>>  
>>>>>  #define DWC3_DEFAULT_AUTOSUSPEND_DELAY   5000 /* ms */
>>>>>  
>>>>> +static int dwc3_core_soft_reset(struct dwc3 *dwc);
>>>>> +
>>>>>  /**
>>>>>   * dwc3_get_dr_mode - Validates and sets dr_mode
>>>>>   * @dwc: pointer to our context structure
>>>>> @@ -177,6 +179,7 @@ static void __dwc3_set_mode(struct work_struct *work)
>>>>>  
>>>>>   dwc3_set_prtcap(dwc, dwc->desired_dr_role);
>>>>>  
>>>>> + dwc3_core_soft_reset(dwc);
>>>> Hi John/Thinh/Felipe,
>>>>
>>>> I actually added this change into my local branch, because we were
>>>> seeing an issue when switching from host mode --> peripheral mode.  What
>>>> was happening was that the RXFIFO register did not update back to the
>>>> expected value for peripheral mode by the time
>>>> dwc3_gadget_init_out_endpoint() was executed.  With the logic to
>>>> calculate the EP max packet limit based on RXFIFO reg, this caused all
>>>> EPs to be set with an EP max limit of 0.
>>>>
>>>> With this change, it seemed to help with the above issue.  However, can
>>>> we consider moving the core soft reset outside the spinlock?  At least
>>>> with our PHY init routines, we have some msleep() calls for waiting for
>>>> the PHYs to be ready, which will end up as a sleeping while atomic bug.
>>>> (not sure if PHY init is required to be called in atomic context)
>>>>
>>>> Thanks
>>>> Wesley Cheng
>>>
>>> Hi Wesley,
>>>
>>> Thanks for letting us know the issue you're having also.
>>>
>>> Yes, you need to wait a certain amount of time to synchronize with the
>>> PHY (at least 50ms for dwc_usb32 and dwc_usb31 v1.80a and above, and
>>> less for older versions). When removing the spinlock to use msleep(),
>>> just make sure that there's no race issue. BTW, how long does your setup
>>> need to msleep()?
>>>
>> Hi Thinh,
>>
>> Sorry for the late response.  My mist

Re: [Mpi-forum] Process towards MPI 4.0 / Final Steps

[Wesley Bland via mpi-forum]

This was removed from 4.0 because it was not considered an “emergency fix”. 
That’s not to say that it’s not worthwhile and we can’t or shouldn’t do it for 
4.1, just that we’re going to remove all changes from the list that are not 
required so we can make sure to finish 4.0 in June.

This can still be read in June and voted in to 4.1 in the usual time frame 
after that (1st in September, 2nd in December).

Am I misunderstanding that there’s something breaking by not having this in 4.0?

Thanks,
Wes

> On Mar 30, 2021, at 4:03 AM, Rolf Rabenseifner via mpi-forum 
>  wrote:
> 
> Dear Martin, Wesley, Bill and all,
> 
>> Please let us know if you have any questions or concerns - we will also 
>> address
>> this in the meeting next week.
> 
> I detected that also Issue (K=) 468 was moved to MPI-4.1.
> 
> I updated the issues's abstract with a summary of the discussion
> (which was partially within the Parrived progress discussion)
> at the Feb. 2021 meeting.
> 
> Adding a 4th such test routine (after MPI_Test, Request_get_status, Win_test, 
> Parrived),
> it gets significantly more evident if for only one routine, 
> Request_get_status, 
> there is no such written progress guarantee in the standard.
> 
> Therefore, we did this analysis and reading of adding at the Feb. meeting 
> for voting it into the standard in June.
> 
> There is no reason to break this result from the Feb. 2021 meeting.
> 
> Therefore, I put https://github.com/mpi-forum/mpi-issues/issues/468
> back to the triage.
> 
> @Martin please put it for tomorrow on the agenda.
> 
> Best regards
> Rolf
> 
> 
> - Original Message -
>> From: "Main MPI Forum mailing list" 
>> To: "Main MPI Forum mailing list" 
>> Cc: "Martin Schulz" 
>> Sent: Wednesday, March 24, 2021 7:55:11 PM
>> Subject: [Mpi-forum] Process towards MPI 4.0 / Final Steps
> 
>> Hi all,
>> 
>> For those of you who had to miss the virtual MPI Forum meeting today, we had 
>> a
>> discussion on the updated process towards MPI 4.0 and how to handle the final
>> tickets.
>> 
>> The recording is at (with the right time-marker to this discussion):
>> https://youtu.be/h9MO-BmbfdQ?t=2125
>> 
>> The slides are at:
>> https://github.com/mpi-forum/mpi-forum.github.io/raw/master/slides/2021/03/2021-03-24-rcm-frm-procedures.pptx
>> 
>> The quick summary is that we will limit the tickets that are still considered
>> for MPI 4.0 to only emergency fixes that avoid breaking the standard and that
>> are directly related to new items/procedures/concepts/text added specifically
>> for MPI 4.0. Otherwise we fear (and we are seeing this already) that we may 
>> get
>> clogged up with more and more changes that will not get the needed vetting 
>> and
>> - equally important - that we run the risk of some issues not being accepted
>> during the vote, which means the FRM is not the final document, which is
>> problematic.
>> 
>> Wesley will be going through the board and classifying all issues based on 
>> that
>> (see also slide 11) and then move tickets that do not meet the criteria to 
>> MPI
>> 4.1 (changes that are already in, will stay , though). For this, we agreed to
>> temporarily assume the role of a release manager that will advance tickets 
>> once
>> they are ready (and that includes sufficient reviews by the CCs) and meet the
>> criteria.
>> 
>> Note, though, this does not mean that the items tagged as 4.1 are postponed
>> indefinitely - the plan is to start working on them right after MPI 4.0, if
>> time permits, already in the June meeting. We should strive for getting a
>> cleaned-up MPI 4.1 out the door soon, preferably before we add (m)any new
>> items, but that part we will also discuss in the June meeting.
>> 
>> Please let us know if you have any questions or concerns - we will also 
>> address
>> this in the meeting next week.
>> 
>> Thanks!
>> 
>> Martin
>> (also in the name of Bill and Wesley)
>> 
>> 
>> 
>> --
>> Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems
>> Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching
>> Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ)
>> Email: schu...@in.tum.de
>> 
>> 
>> 
>> 
>> ___
>> mpi-forum mailing list
>> mpi-forum@lists.mpi-forum.org
>> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum
> 
> -- 
> Dr. Rolf Rabenseifner . . . . . . . . . .. email r

Re: [PATCH v3 1/2] usb: dwc3: Trigger a GCTL soft reset when switching modes in DRD

[Wesley Cheng]

On 3/29/2021 3:20 PM, John Stultz wrote:
> On Mon, Mar 29, 2021 at 3:15 PM Wesley Cheng  wrote:
>>
>>
>>
>> On 3/19/2021 4:09 PM, Thinh Nguyen wrote:
>>> Wesley Cheng wrote:
>>>>
>>>>
>>>> On 3/8/2021 10:33 PM, Wesley Cheng wrote:
>>>>>
>>>>>
>>>>> On 3/8/2021 7:05 PM, Thinh Nguyen wrote:
>>>>>> Wesley Cheng wrote:
>>>>>>>
>>>>>>> On 3/6/2021 3:41 PM, Thinh Nguyen wrote:
>>>>>>>> Wesley Cheng wrote:
>>>>>>>>> On 1/8/2021 4:44 PM, Thinh Nguyen wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> John Stultz wrote:
>>>>>>>>>>> On Fri, Jan 8, 2021 at 4:26 AM Felipe Balbi  
>>>>>>>>>>> wrote:
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> John Stultz  writes:
>>>>>>>>>>>>> From: Yu Chen 
>>>>>>>>>>>>>
>>>>>>>>>>>>> Just resending this, as discussion died out a bit and I'm not
>>>>>>>>>>>>> sure how to make further progress. See here for debug data that
>>>>>>>>>>>>> was requested last time around:
>>>>>>>>>>>>>   
>>>>>>>>>>>>> https://urldefense.com/v3/__https://lore.kernel.org/lkml/calaqxlxdnaufjkx0an9xwwtfwvjmwigppy2aqsnj56yvnbu...@mail.gmail.com/__;!!A4F2R9G_pg!LNzuprAeg-O80SgolYkIkW4-ne-M-yLWCDUY9MygAIrQC398Z6gRJ9wnsnlqd3w$
>>>>>>>>>>>>>
>>>>>>>>>>>>> With the current dwc3 code on the HiKey960 we often see the
>>>>>>>>>>>>> COREIDLE flag get stuck off in __dwc3_gadget_start(), which
>>>>>>>>>>>>> seems to prevent the reset irq and causes the USB gadget to
>>>>>>>>>>>>> fail to initialize.
>>>>>>>>>>>>>
>>>>>>>>>>>>> We had seen occasional initialization failures with older
>>>>>>>>>>>>> kernels but with recent 5.x era kernels it seemed to be becoming
>>>>>>>>>>>>> much more common, so I dug back through some older trees and
>>>>>>>>>>>>> realized I dropped this quirk from Yu Chen during upstreaming
>>>>>>>>>>>>> as I couldn't provide a proper rational for it and it didn't
>>>>>>>>>>>>> seem to be necessary. I now realize I was wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>> After resubmitting the quirk, Thinh Nguyen pointed out that it
>>>>>>>>>>>>> shouldn't be a quirk at all and it is actually mentioned in the
>>>>>>>>>>>>> programming guide that it should be done when switching modes
>>>>>>>>>>>>> in DRD.
>>>>>>>>>>>>>
>>>>>>>>>>>>> So, to avoid these !COREIDLE lockups seen on HiKey960, this
>>>>>>>>>>>>> patch issues GCTL soft reset when switching modes if the
>>>>>>>>>>>>> controller is in DRD mode.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cc: Felipe Balbi 
>>>>>>>>>>>>> Cc: Tejas Joglekar 
>>>>>>>>>>>>> Cc: Yang Fei 
>>>>>>>>>>>>> Cc: YongQin Liu 
>>>>>>>>>>>>> Cc: Andrzej Pietrasiewicz 
>>>>>>>>>>>>> Cc: Thinh Nguyen 
>>>>>>>>>>>>> Cc: Jun Li 
>>>>>>>>>>>>> Cc: Mauro Carvalho Chehab 
>>>>>>>>>>>>> Cc: Greg Kroah-Hartman 
>>>>>>>>>>>>> Cc: linux-...@vger.kernel.org
>>>>>>>>>>>>> Signed-off-by: Yu Chen 
>>>>>>>>>>>>> Signed-off-by: John Stultz 
>>>>>>>>>>>>> ---
>>>>>>>>>>>>> v2:
>>>>>&g

Re: [PATCH v3 2/2] usb: dwc3: Fix DRD mode change sequence following programming guide

[Wesley Cheng]

On 3/6/2021 3:39 PM, Thinh Nguyen wrote:
> Wesley Cheng wrote:
>>
>> On 1/7/2021 5:51 PM, John Stultz wrote:
>>> In reviewing the previous patch, Thinh Nguyen pointed out that
>>> the DRD mode change sequence should be like the following when
>>> switching from host -> device according to the programming guide
>>> (for all DRD IPs):
>>> 1. Reset controller with GCTL.CoreSoftReset
>>> 2. Set GCTL.PrtCapDir(device)
>>> 3. Soft reset with DCTL.CSftRst
>>> 4. Then follow up with the initializing registers sequence
>>>
>>> The current code does:
>>> a. Soft reset with DCTL.CSftRst on driver probe
>>> b. Reset controller with GCTL.CoreSoftReset (added in previous
>>>patch)
>>> c. Set GCTL.PrtCapDir(device)
>>> d. < missing DCTL.CSftRst >
>>> e. Then follow up with initializing registers sequence
>>>
>>> So this patch adds the DCTL.CSftRst soft reset that was currently
>>> missing from the dwc3 mode switching.
>>>
>>> Cc: Felipe Balbi 
>>> Cc: Tejas Joglekar 
>>> Cc: Yang Fei 
>>> Cc: YongQin Liu 
>>> Cc: Andrzej Pietrasiewicz 
>>> Cc: Thinh Nguyen 
>>> Cc: Jun Li 
>>> Cc: Mauro Carvalho Chehab 
>>> Cc: Greg Kroah-Hartman 
>>> Cc: linux-...@vger.kernel.org
>>> Signed-off-by: John Stultz 
>>> ---
>>> Feedback would be appreciated. I'm a little worried I should be
>>> conditionalizing the DCTL.CSftRst on DRD mode controllers, but
>>> I'm really not sure what the right thing to do is for non-DRD
>>> mode controllers.
>>> ---
>>>  drivers/usb/dwc3/core.c | 3 +++
>>>  1 file changed, 3 insertions(+)
>>>
>>> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
>>> index b6a6b90eb2d5..71f8b07ecb99 100644
>>> --- a/drivers/usb/dwc3/core.c
>>> +++ b/drivers/usb/dwc3/core.c
>>> @@ -40,6 +40,8 @@
>>>  
>>>  #define DWC3_DEFAULT_AUTOSUSPEND_DELAY 5000 /* ms */
>>>  
>>> +static int dwc3_core_soft_reset(struct dwc3 *dwc);
>>> +
>>>  /**
>>>   * dwc3_get_dr_mode - Validates and sets dr_mode
>>>   * @dwc: pointer to our context structure
>>> @@ -177,6 +179,7 @@ static void __dwc3_set_mode(struct work_struct *work)
>>>  
>>> dwc3_set_prtcap(dwc, dwc->desired_dr_role);
>>>  
>>> +   dwc3_core_soft_reset(dwc);
>> Hi John/Thinh/Felipe,
>>
>> I actually added this change into my local branch, because we were
>> seeing an issue when switching from host mode --> peripheral mode.  What
>> was happening was that the RXFIFO register did not update back to the
>> expected value for peripheral mode by the time
>> dwc3_gadget_init_out_endpoint() was executed.  With the logic to
>> calculate the EP max packet limit based on RXFIFO reg, this caused all
>> EPs to be set with an EP max limit of 0.
>>
>> With this change, it seemed to help with the above issue.  However, can
>> we consider moving the core soft reset outside the spinlock?  At least
>> with our PHY init routines, we have some msleep() calls for waiting for
>> the PHYs to be ready, which will end up as a sleeping while atomic bug.
>> (not sure if PHY init is required to be called in atomic context)
>>
>> Thanks
>> Wesley Cheng
> 
> Hi Wesley,
> 
> Thanks for letting us know the issue you're having also.
> 
> Yes, you need to wait a certain amount of time to synchronize with the
> PHY (at least 50ms for dwc_usb32 and dwc_usb31 v1.80a and above, and
> less for older versions). When removing the spinlock to use msleep(),
> just make sure that there's no race issue. BTW, how long does your setup
> need to msleep()?
> 
Hi Thinh,

Sorry for the late response.  My mistake, its actually just a usleep()
for a less than 100uS (polling for a status bit change, so it will exit
early if possible).  For this change, can we just move the
dwc3_core_soft_reset() outside of the spinlock?

Thanks
Wesley Cheng

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH v3 1/2] usb: dwc3: Trigger a GCTL soft reset when switching modes in DRD

[Wesley Cheng]

On 3/19/2021 4:09 PM, Thinh Nguyen wrote:
> Wesley Cheng wrote:
>>
>>
>> On 3/8/2021 10:33 PM, Wesley Cheng wrote:
>>>
>>>
>>> On 3/8/2021 7:05 PM, Thinh Nguyen wrote:
>>>> Wesley Cheng wrote:
>>>>>
>>>>> On 3/6/2021 3:41 PM, Thinh Nguyen wrote:
>>>>>> Wesley Cheng wrote:
>>>>>>> On 1/8/2021 4:44 PM, Thinh Nguyen wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> John Stultz wrote:
>>>>>>>>> On Fri, Jan 8, 2021 at 4:26 AM Felipe Balbi  wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> John Stultz  writes:
>>>>>>>>>>> From: Yu Chen 
>>>>>>>>>>>
>>>>>>>>>>> Just resending this, as discussion died out a bit and I'm not
>>>>>>>>>>> sure how to make further progress. See here for debug data that
>>>>>>>>>>> was requested last time around:
>>>>>>>>>>>   
>>>>>>>>>>> https://urldefense.com/v3/__https://lore.kernel.org/lkml/calaqxlxdnaufjkx0an9xwwtfwvjmwigppy2aqsnj56yvnbu...@mail.gmail.com/__;!!A4F2R9G_pg!LNzuprAeg-O80SgolYkIkW4-ne-M-yLWCDUY9MygAIrQC398Z6gRJ9wnsnlqd3w$
>>>>>>>>>>>  
>>>>>>>>>>>
>>>>>>>>>>> With the current dwc3 code on the HiKey960 we often see the
>>>>>>>>>>> COREIDLE flag get stuck off in __dwc3_gadget_start(), which
>>>>>>>>>>> seems to prevent the reset irq and causes the USB gadget to
>>>>>>>>>>> fail to initialize.
>>>>>>>>>>>
>>>>>>>>>>> We had seen occasional initialization failures with older
>>>>>>>>>>> kernels but with recent 5.x era kernels it seemed to be becoming
>>>>>>>>>>> much more common, so I dug back through some older trees and
>>>>>>>>>>> realized I dropped this quirk from Yu Chen during upstreaming
>>>>>>>>>>> as I couldn't provide a proper rational for it and it didn't
>>>>>>>>>>> seem to be necessary. I now realize I was wrong.
>>>>>>>>>>>
>>>>>>>>>>> After resubmitting the quirk, Thinh Nguyen pointed out that it
>>>>>>>>>>> shouldn't be a quirk at all and it is actually mentioned in the
>>>>>>>>>>> programming guide that it should be done when switching modes
>>>>>>>>>>> in DRD.
>>>>>>>>>>>
>>>>>>>>>>> So, to avoid these !COREIDLE lockups seen on HiKey960, this
>>>>>>>>>>> patch issues GCTL soft reset when switching modes if the
>>>>>>>>>>> controller is in DRD mode.
>>>>>>>>>>>
>>>>>>>>>>> Cc: Felipe Balbi 
>>>>>>>>>>> Cc: Tejas Joglekar 
>>>>>>>>>>> Cc: Yang Fei 
>>>>>>>>>>> Cc: YongQin Liu 
>>>>>>>>>>> Cc: Andrzej Pietrasiewicz 
>>>>>>>>>>> Cc: Thinh Nguyen 
>>>>>>>>>>> Cc: Jun Li 
>>>>>>>>>>> Cc: Mauro Carvalho Chehab 
>>>>>>>>>>> Cc: Greg Kroah-Hartman 
>>>>>>>>>>> Cc: linux-...@vger.kernel.org
>>>>>>>>>>> Signed-off-by: Yu Chen 
>>>>>>>>>>> Signed-off-by: John Stultz 
>>>>>>>>>>> ---
>>>>>>>>>>> v2:
>>>>>>>>>>> * Rework to always call the GCTL soft reset in DRD mode,
>>>>>>>>>>>   rather then using a quirk as suggested by Thinh Nguyen
>>>>>>>>>>>
>>>>>>>>>>> v3:
>>>>>>>>>>> * Move GCTL soft reset under the spinlock as suggested by
>>>>>>>>>>>   Thinh Nguyen
>>>>>>>>>> Because this is such an invasive change, I would prefer that we get
>>>>>>>>>> Tested-By tags from a good fraction of 

Re: [google-appengine] Re: Need Assistance to select product

[wesley chun]

Some suggestions:

   1. *Python: *many options here: Flask, Django, Pyramid, Bottle, web.py
   2. *Website*: if you prefer to build your site managing (just) source
   code, App Engine <http://cloud.google.com/appengine> is the main reason
   why people are on this mailing list. If you have other dependencies
   (binaries, libraries in unsupported languages, e.g., C++, other OS code,
   etc.) requiring you to containerize your app, then Cloud Run
   <http://cloud.google.com/run> would be the way to go. In both cases, you
   wouldn't have to worry about servers. Containerizing also allows your app
   to be more portable. Both GAE & GCR support Python 2 & 3 (although 2.x
   support is now limited).
  - The above represent a more traditional web app architecture style.
  You can also roll something more contemporary, a la "JAM stack
  <http://google.com/search?q=jam+stack>"-style by writing
  loosely-coupled microservice functions hosted on Cloud Functions
  <http://cloud.google.com/functions>, endpoints easily reachable via
  HTTP or event-driven from web or mobile front-ends where your
app basically
  consists of a set of API calls.
   3. *Data*: Cloud Firestore
<https://firebase.google.com/docs/firestore> (NoSQL);
   RDBMS via Cloud SQL <http://cloud.google.com/sql> also available (MySQL,
   PostgreSQL, SQL Server) but Firestore IMO is a better option for web/mobile
   apps
   4. *APIs*: API Gateway <https://cloud.google.com/api-gateway>: allows
   you to manage API endpoints hosted on GCP serverless compute like App
   Engine, Cloud Run, or Cloud Functions
   5. *Team*: Cloud IAM gives you control to manage different team members
   & roles <https://cloud.google.com/iam/docs/understanding-roles> as
   related to your project

It would also be good to hear from someone in the community (here) that has
built something with these technologies. Finally one last thought regarding
the mobile part of the equation, consider Flutter <https://flutter.dev> for
developing the front-end as you can build native-looking iOS, Android, and
web apps with just one codebase.

Good luck!
--Wesley

On Mon, Mar 29, 2021 at 10:08 AM NoCommandLine 
wrote:

> Hi,
>
> I'm not sure what you mean by #4 but in general, I would say the 2
> simplest options would be Google App Engine (GAE) or Google Compute Engine
> (GCE).
>
> 1. I would start with GAE (standard environment unless you have some
> unique/complicated stuff) and then migrate to GCE if I need to later. I'm
> recommending GAE because you don't have to worry about scaling your
> infrastructure to meet your demands. You just write your code, deploy it
> and Google takes care of scaling up/down to meet changes in your traffic.
> Google also gives you free SSL and you can use your custom domain on GAE
> <https://cloud.google.com/appengine/docs/standard/python/mapping-custom-domains>
> .
>
> If you're using GAE, you have access to Cloud Datastore
> <https://cloud.google.com/datastore> to store your data
>
> 2. Development is done on your local machine and you deploy to GAE by
> either using the gcloud command line interface (gcloud CLI) or a 3rd party
> GUI (I have one - https://nocommandline.com). Since the code is local,
> you take care of versioning and/or sharing amongst different people anyway
> you like. If you want different people to be able to deploy, you can grant
> them access (deployment role
> <https://cloud.google.com/appengine/docs/standard/python/roles#predefined_roles>)
> to be able to deploy or make them co-owners of the product
>
>
> GAE (standard) will not work if you need any of - streaming,  instant
> messaging (like PubSub). For those, you'll need to use GCE or maybe GAE
> Flexible (you'll have to confirm the information about GAE Flexible)
>
> *.* *NoCommandLine* *..*
> *If you miss GAE Launcher*, try https://nocommandline.com
>
> On Thursday, March 25, 2021 at 4:44:40 AM UTC-7 Ooty Beauty wrote:
>
>> Hello,
>>
>> I'm very new to google cloud and confused as to which product should go
>> with. Below are my requirements, I believe you will be able to show me some
>> lights
>>
>> I WANT TO:
>>
>>1. Build a dynamic website with Python
>>2. Host the website on the cloud, I don't have the infrastructure on
>>my own.
>>3. Store the website data in the cloud
>>4. Develop API which will cater to both the website and Mobile App
>>5. Have access to code and probably share the development work among
>>different teams
>>
>> I ALREADY HAVE:
>>
>>1. Domain registered
>>
>> Thanks,
>> Pradeep
>>
> --
> You received this message because you are subscri

[Bug 1891205] Re: Julia crashes only on Ubuntu

[wesley]

I am the user with the bug reported here

https://github.com/JuliaLang/julia/issues/40222.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891205

Title:
  Julia crashes only on Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/julia/+bug/1891205/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

RE: [cayugabirds-l] Merlin reports

[Wesley M. Hochachka]

From my yard, it’s been seeming that most of the Merlin activity has been 
concentrated around the row of White Pine trees behind the dumpsters of the two 
apartment buildings on Tareyton, in the area that there was a crow nest 2 years 
ago (I think 2 years ago…).  When I’ve been watching a calling Merlin in 
flight, it’s path seems to almost invariably lead to circling around or maybe 
diving into those pines.

Wesley




From: bounce-125495218-3494...@list.cornell.edu 
 On Behalf Of anneb.cl...@gmail.com
Sent: Thursday, March 25, 2021 11:20 PM
To: Kenneth V. Rosenberg 
Cc: Karen ; CAYUGABIRDS-L 

Subject: Re: [cayugabirds-l] Merlin reports

Interesting. They have more 2020 crow nests to rent in the Birchwood area than 
near that sycamore. But it will be interesting to see if one pair is searching 
the whole area. The nest used last year was either a recently depredated 
American crow nest or a takeover, the reason for the crow nest failure.
Anne
Sent from my iPhone


On Mar 25, 2021, at 6:41 PM, Kenneth V. Rosenberg 
mailto:k...@cornell.edu>> wrote:
 Hi John

At least one Merlin has returned to the Northeast Ithaca  neighborhood. I say 
“at least” one because there is a male perching regularly on the large sycamore 
at the north end of Muriel St. (and calling in that area) and one seen 
regularly (by Brad) flying around and calling on Birchwood Dr.  I live about 
halfway between these areas on Tareyton and also see/hear one regularly flying 
over— so we don’t know if this represents 1 or 2 birds.

Interestingly there was a pair of Merlins (one noticeably larger) perched and 
calling in the Muriel sycamore on a warm day in February— so they may have been 
winteri g locally.

KEN
Sent from my iPhone


On Mar 25, 2021, at 6:18 PM, Karen 
mailto:confergoldw...@aol.com>> wrote:

I love Merlins and Merlin reports and people who send in Merlin reports[Heart 
Eyes]. I check them all out. . Thanks to such reports, I have observed an 
increasing number of incubated nests in Tompkins County as follows: 2 (2014), 6 
(2015), 6 (2016), 5 (2017), 3 (2018), 6 (2019), 9 (2020).  These include pairs 
in Trumansburg, Lansing, Dryden, Freeville, Etna, and Ithaca (plus hints of a 
pair in Groton). Local observers provided guidance to almost all of these. I 
have written one paper on this, and am trying to write a more complete paper 
including habitat choice. Interestingly, all nests have been in urban/suburban 
areas. None in forests nor edge of forest nor edge of lake.

Merlins start egg-laying in early May. Observations in late March are helpful 
by providing a hint about where they may finally nest. For instance, the pair 
observed by so many at Myer's Pint never nested there. Weeks after being seen 
at Myer's Point, there was a pair about 800 m east closer to the Catholic 
church.

I would love to have individuals provide me with their observations at 
confergoldw...@aol.com<mailto:confergoldw...@aol.com>

Thanks,

John
--
Cayugabirds-L List Info:
Welcome and Basics<http://www.northeastbirding.com/CayugabirdsWELCOME>
Rules and Information<http://www.northeastbirding.com/CayugabirdsRULES>
Subscribe, Configuration and 
Leave<http://www.northeastbirding.com/CayugabirdsSubscribeConfigurationLeave.htm>
Archives:
The Mail 
Archive<http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html>
Surfbirds<http://www.surfbirds.com/birdingmail/Group/Cayugabirds>
BirdingOnThe.Net<http://birdingonthe.net/mailinglists/CAYU.html>
Please submit your observations to eBird<http://ebird.org/content/ebird/>!
--
--
Cayugabirds-L List Info:
Welcome and Basics<http://www.northeastbirding.com/CayugabirdsWELCOME>
Rules and Information<http://www.northeastbirding.com/CayugabirdsRULES>
Subscribe, Configuration and 
Leave<http://www.northeastbirding.com/CayugabirdsSubscribeConfigurationLeave.htm>
Archives:
The Mail 
Archive<http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html>
Surfbirds<http://www.surfbirds.com/birdingmail/Group/Cayugabirds>
BirdingOnThe.Net<http://birdingonthe.net/mailinglists/CAYU.html>
Please submit your observations to eBird<http://ebird.org/content/ebird/>!
--
--
Cayugabirds-L List Info:
Welcome and Basics<http://www.northeastbirding.com/CayugabirdsWELCOME>
Rules and Information<http://www.northeastbirding.com/CayugabirdsRULES>
Subscribe, Configuration and 
Leave<http://www.northeastbirding.com/CayugabirdsSubscribeConfigurationLeave.htm>
Archives:
The Mail 
Archive<http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html>
Surfbirds<http://www.surfbirds.com/birdingmail/Group/Cayugabirds>
BirdingOnThe.Net<http://birdingonthe.net/mailinglists/CAYU.html>
Please submit your observations to eBird<http://ebird.org/content/ebird/>!
--

--

Cayugabirds-L List Info:
http://www.NortheastBirding.com/CayugabirdsWELCOME
http://www.NortheastBirding.com/Cay

[PATCH] usb: dwc3: gadget: Clear DEP flags after stop transfers in ep disable

[Wesley Cheng]

Ensure that dep->flags are cleared until after stop active transfers
is completed.  Otherwise, the ENDXFER command will not be executed
during ep disable.

Fixes: f09ddcfcb8c5 ("usb: dwc3: gadget: Prevent EP queuing while stopping 
transfers")
Reported-and-tested-by: Andy Shevchenko 
Tested-by: Marek Szyprowski 
Signed-off-by: Wesley Cheng 
---
 drivers/usb/dwc3/gadget.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index e1442fc..2c4d201 100644
--- a/drivers/usb/dwc3/gadget.c
+++ b/drivers/usb/dwc3/gadget.c
@@ -791,10 +791,6 @@ static int __dwc3_gadget_ep_disable(struct dwc3_ep *dep)
reg &= ~DWC3_DALEPENA_EP(dep->number);
dwc3_writel(dwc->regs, DWC3_DALEPENA, reg);
 
-   dep->stream_capable = false;
-   dep->type = 0;
-   dep->flags = 0;
-
/* Clear out the ep descriptors for non-ep0 */
if (dep->number > 1) {
dep->endpoint.comp_desc = NULL;
@@ -803,6 +799,10 @@ static int __dwc3_gadget_ep_disable(struct dwc3_ep *dep)
 
dwc3_remove_requests(dwc, dep);
 
+   dep->stream_capable = false;
+   dep->type = 0;
+   dep->flags = 0;
+
return 0;
 }
 
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH v3] usb: dwc3: gadget: Prevent EP queuing while stopping transfers

[Wesley Cheng]

On 3/23/2021 10:27 AM, Andy Shevchenko wrote:
> On Tue, Mar 23, 2021 at 1:19 AM Wesley Cheng  wrote:
>>
>> Hi Andy,
>>
>> On 3/22/2021 2:14 PM, Andy Shevchenko wrote:
>>> On Mon, Mar 22, 2021 at 10:06 PM Wesley Cheng  wrote:
>>>>
>>>> Hi Andy,
>>>>
>>>> On 3/22/2021 12:34 PM, Andy Shevchenko wrote:
>>>>> On Mon, Mar 22, 2021 at 8:49 PM Wesley Cheng  
>>>>> wrote:
>>>>>>
>>>>>> Hi Andy,
>>>>>>
>>>>>> On 3/22/2021 5:48 AM, Andy Shevchenko wrote:
>>>>>>> On Fri, Mar 12, 2021 at 2:01 AM Wesley Cheng  
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> In the situations where the DWC3 gadget stops active transfers, once
>>>>>>>> calling the dwc3_gadget_giveback(), there is a chance where a function
>>>>>>>> driver can queue a new USB request in between the time where the dwc3
>>>>>>>> lock has been released and re-aquired.  This occurs after we've already
>>>>>>>> issued an ENDXFER command.  When the stop active transfers continues
>>>>>>>> to remove USB requests from all dep lists, the newly added request will
>>>>>>>> also be removed, while controller still has an active TRB for it.
>>>>>>>> This can lead to the controller accessing an unmapped memory address.
>>>>>>>>
>>>>>>>> Fix this by ensuring parameters to prevent EP queuing are set before
>>>>>>>> calling the stop active transfers API.
>>>>>>>
>>>>>>>
>>>>>>> commit f09ddcfcb8c569675066337adac2ac205113471f
>>>>>>> Author: Wesley Cheng 
>>>>>>> Date:   Thu Mar 11 15:59:02 2021 -0800
>>>>>>>
>>>>>>>usb: dwc3: gadget: Prevent EP queuing while stopping transfers
>>>>>>>
>>>>>>> effectively broke my gadget setup.
>>>>>>>
>>>>>>> The output of the kernel (followed by non responsive state of USB 
>>>>>>> controller):
>>>>>>>
>>>>>>> [  195.228586] using random self ethernet address
>>>>>>> [  195.233104] using random host ethernet address
>>>>>>> [  195.245306] usb0: HOST MAC aa:bb:cc:dd:ee:f2
>>>>>>> [  195.249732] usb0: MAC aa:bb:cc:dd:ee:f1
>>>>>>> # [  195.773594] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
>>>>>>> [  195.780585] [ cut here ]
>>>>>>> [  195.785217] dwc3 dwc3.0.auto: No resource for ep2in
>>>>>>> [  195.790162] WARNING: CPU: 0 PID: 217 at
>>>>>>> drivers/usb/dwc3/gadget.c:360 dwc3_send_gadget_ep_cmd+0x4b9/0x670
>>>>>>> [  195.799760] Modules linked in: usb_f_eem u_ether libcomposite
>>>>>>> brcmfmac brcmutil mmc_block pwm_lpss_pci pwm_lps
>>>>>>> s snd_sof_pci_intel_tng snd_sof_pci snd_sof_acpi_intel_byt
>>>>>>> snd_sof_intel_ipc snd_sof_acpi snd_sof snd_sof_nocodec
>>>>>>> spi_pxa2xx_platform snd_sof_xtensa_dsp spi_pxa2xx_pci
>>>>>>> extcon_intel_mrfld intel_mrfld_adc sdhci_pci cqhci sdhci m
>>>>>>> mc_core intel_mrfld_pwrbtn intel_soc_pmic_mrfld hci_uart btbcm btintel
>>>>>>> [  195.835604] CPU: 0 PID: 217 Comm: irq/16-dwc3 Not tainted 
>>>>>>> 5.12.0-rc4+ #60
>>>>>>> [  195.842403] Hardware name: Intel Corporation Merrifield/BODEGA BAY,
>>>>>>> BIOS 542 2015.01.21:18.19.48
>>>>>>> [  195.851191] RIP: 0010:dwc3_send_gadget_ep_cmd+0x4b9/0x670
>>>>>>> [  195.856608] Code: cd 00 00 00 44 89 44 24 20 48 89 4c 24 18 e8 ee
>>>>>>> f7 e4 ff 48 8b 4c 24 18 4c 89 f2 48 c7 c7 b9
>>>>>>> ed 4f a0 48 89 c6 e8 ef 24 43 00 <0f> 0b 41 be ea ff ff ff 44 8b 44 24
>>>>>>> 20 e9 80 fc ff ff 41 83 fe 92
>>>>>>> [  195.875381] RSP: :a53c00373ba8 EFLAGS: 00010086
>>>>>>> [  195.880617] RAX:  RBX: 1387 RCX: 
>>>>>>> dfff
>>>>>>> [  195.887755] RDX: dfff RSI: ffea RDI: 
>>>>>>> 
>>>>>>> [  195.894893] RBP: 9ce8c8f2b028

Re: [PATCH v3] usb: dwc3: gadget: Prevent EP queuing while stopping transfers

[Wesley Cheng]

On 3/23/2021 10:27 AM, Andy Shevchenko wrote:
> On Tue, Mar 23, 2021 at 1:19 AM Wesley Cheng  wrote:
>>
>> Hi Andy,
>>
>> On 3/22/2021 2:14 PM, Andy Shevchenko wrote:
>>> On Mon, Mar 22, 2021 at 10:06 PM Wesley Cheng  wrote:
>>>>
>>>> Hi Andy,
>>>>
>>>> On 3/22/2021 12:34 PM, Andy Shevchenko wrote:
>>>>> On Mon, Mar 22, 2021 at 8:49 PM Wesley Cheng  
>>>>> wrote:
>>>>>>
>>>>>> Hi Andy,
>>>>>>
>>>>>> On 3/22/2021 5:48 AM, Andy Shevchenko wrote:
>>>>>>> On Fri, Mar 12, 2021 at 2:01 AM Wesley Cheng  
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> In the situations where the DWC3 gadget stops active transfers, once
>>>>>>>> calling the dwc3_gadget_giveback(), there is a chance where a function
>>>>>>>> driver can queue a new USB request in between the time where the dwc3
>>>>>>>> lock has been released and re-aquired.  This occurs after we've already
>>>>>>>> issued an ENDXFER command.  When the stop active transfers continues
>>>>>>>> to remove USB requests from all dep lists, the newly added request will
>>>>>>>> also be removed, while controller still has an active TRB for it.
>>>>>>>> This can lead to the controller accessing an unmapped memory address.
>>>>>>>>
>>>>>>>> Fix this by ensuring parameters to prevent EP queuing are set before
>>>>>>>> calling the stop active transfers API.
>>>>>>>
>>>>>>>
>>>>>>> commit f09ddcfcb8c569675066337adac2ac205113471f
>>>>>>> Author: Wesley Cheng 
>>>>>>> Date:   Thu Mar 11 15:59:02 2021 -0800
>>>>>>>
>>>>>>>usb: dwc3: gadget: Prevent EP queuing while stopping transfers
>>>>>>>
>>>>>>> effectively broke my gadget setup.
>>>>>>>
>>>>>>> The output of the kernel (followed by non responsive state of USB 
>>>>>>> controller):
>>>>>>>
>>>>>>> [  195.228586] using random self ethernet address
>>>>>>> [  195.233104] using random host ethernet address
>>>>>>> [  195.245306] usb0: HOST MAC aa:bb:cc:dd:ee:f2
>>>>>>> [  195.249732] usb0: MAC aa:bb:cc:dd:ee:f1
>>>>>>> # [  195.773594] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
>>>>>>> [  195.780585] [ cut here ]
>>>>>>> [  195.785217] dwc3 dwc3.0.auto: No resource for ep2in
>>>>>>> [  195.790162] WARNING: CPU: 0 PID: 217 at
>>>>>>> drivers/usb/dwc3/gadget.c:360 dwc3_send_gadget_ep_cmd+0x4b9/0x670
>>>>>>> [  195.799760] Modules linked in: usb_f_eem u_ether libcomposite
>>>>>>> brcmfmac brcmutil mmc_block pwm_lpss_pci pwm_lps
>>>>>>> s snd_sof_pci_intel_tng snd_sof_pci snd_sof_acpi_intel_byt
>>>>>>> snd_sof_intel_ipc snd_sof_acpi snd_sof snd_sof_nocodec
>>>>>>> spi_pxa2xx_platform snd_sof_xtensa_dsp spi_pxa2xx_pci
>>>>>>> extcon_intel_mrfld intel_mrfld_adc sdhci_pci cqhci sdhci m
>>>>>>> mc_core intel_mrfld_pwrbtn intel_soc_pmic_mrfld hci_uart btbcm btintel
>>>>>>> [  195.835604] CPU: 0 PID: 217 Comm: irq/16-dwc3 Not tainted 
>>>>>>> 5.12.0-rc4+ #60
>>>>>>> [  195.842403] Hardware name: Intel Corporation Merrifield/BODEGA BAY,
>>>>>>> BIOS 542 2015.01.21:18.19.48
>>>>>>> [  195.851191] RIP: 0010:dwc3_send_gadget_ep_cmd+0x4b9/0x670
>>>>>>> [  195.856608] Code: cd 00 00 00 44 89 44 24 20 48 89 4c 24 18 e8 ee
>>>>>>> f7 e4 ff 48 8b 4c 24 18 4c 89 f2 48 c7 c7 b9
>>>>>>> ed 4f a0 48 89 c6 e8 ef 24 43 00 <0f> 0b 41 be ea ff ff ff 44 8b 44 24
>>>>>>> 20 e9 80 fc ff ff 41 83 fe 92
>>>>>>> [  195.875381] RSP: :a53c00373ba8 EFLAGS: 00010086
>>>>>>> [  195.880617] RAX:  RBX: 1387 RCX: 
>>>>>>> dfff
>>>>>>> [  195.887755] RDX: dfff RSI: ffea RDI: 
>>>>>>> 
>>>>>>> [  195.894893] RBP: 9ce8c8f2b028

Re: [PATCH] usb: gadget: Stall OS descriptor request for unsupported functions

[Wesley Cheng]

On 3/22/2021 11:25 PM, Jack Pham wrote:
> Hi Wesley,
> 
> On Mon, Mar 22, 2021 at 06:50:17PM -0700, Wesley Cheng wrote:
>> From: Chandana Kishori Chiluveru 
>>
>> Hosts which request "OS descriptors" from gadgets do so during
>> the enumeration phase and before the configuration is set with
>> SET_CONFIGURATION. Composite driver supports OS descriptor
>> handling in composite_setup function. This requires to pass
>> signature field, vendor code, compatibleID and subCompatibleID
>> from user space.
>>
>> For USB compositions that contain functions which don't implement os
>> descriptors, Windows is sending vendor specific requests for os
>> descriptors and composite driver handling this request with invalid
>> data. With this invalid info host resetting the bus and never
>> selecting the configuration and leading enumeration issue.
>>
>> Fix this by bailing out from the OS descriptor setup request
>> handling if the functions does not have OS descriptors compatibleID.
>>
>> Signed-off-by: Chandana Kishori Chiluveru 
>> Signed-off-by: Wesley Cheng 
>> ---
>>  drivers/usb/gadget/composite.c | 6 ++
>>  1 file changed, 6 insertions(+)
>>
>> diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
>> index 72a9797..473edda6 100644
>> --- a/drivers/usb/gadget/composite.c
>> +++ b/drivers/usb/gadget/composite.c
>> @@ -1945,6 +1945,12 @@ composite_setup(struct usb_gadget *gadget, const 
>> struct usb_ctrlrequest *ctrl)
>>  buf[6] = w_index;
>>  /* Number of ext compat interfaces */
>>  count = count_ext_compat(os_desc_cfg);
>> +/*
>> + * Bailout if device does not
>> + * have ext_compat interfaces.
>> + */
>> +if (count == 0)
>> +break;
>>  buf[8] = count;
>>  count *= 24; /* 24 B/ext compat desc */
>>  count += 16; /* header */
> 
> Do we still need this fix? IIRC we had this change in our downstream
> kernel to fix the case when dynamically re-configuring ConfigFS, i.e.
> changing the composition of functions wherein none of the interfaces
> support OS Descriptors, so this causes count_ext_compat() to return
> 0 and results in the issue described in $SUBJECT.
> 
Hi Jack,

You're correct.  We can address this as well in the userspace perspective.

> But I think this is more of a problem of an improperly configured
> ConfigFS gadget. If userspace instead removes the config from the
> gadget's os_desc subdirectory that should cause cdev->os_desc_config to
> be set to NULL and hence composite_setup() should never enter this
> handling at all, right?

Sure, I'll go with fixing it in the userspace, since the support to
stall the OS desc is already present in the composite driver as you
mentioned.  Thanks for the input.

Thanks
Wesley Cheng

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

[PATCH] usb: gadget: Stall OS descriptor request for unsupported functions

[Wesley Cheng]

From: Chandana Kishori Chiluveru 

Hosts which request "OS descriptors" from gadgets do so during
the enumeration phase and before the configuration is set with
SET_CONFIGURATION. Composite driver supports OS descriptor
handling in composite_setup function. This requires to pass
signature field, vendor code, compatibleID and subCompatibleID
from user space.

For USB compositions that contain functions which don't implement os
descriptors, Windows is sending vendor specific requests for os
descriptors and composite driver handling this request with invalid
data. With this invalid info host resetting the bus and never
selecting the configuration and leading enumeration issue.

Fix this by bailing out from the OS descriptor setup request
handling if the functions does not have OS descriptors compatibleID.

Signed-off-by: Chandana Kishori Chiluveru 
Signed-off-by: Wesley Cheng 
---
 drivers/usb/gadget/composite.c | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
index 72a9797..473edda6 100644
--- a/drivers/usb/gadget/composite.c
+++ b/drivers/usb/gadget/composite.c
@@ -1945,6 +1945,12 @@ composite_setup(struct usb_gadget *gadget, const struct 
usb_ctrlrequest *ctrl)
buf[6] = w_index;
/* Number of ext compat interfaces */
count = count_ext_compat(os_desc_cfg);
+   /*
+* Bailout if device does not
+* have ext_compat interfaces.
+*/
+   if (count == 0)
+   break;
buf[8] = count;
count *= 24; /* 24 B/ext compat desc */
count += 16; /* header */
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH v3] usb: dwc3: gadget: Prevent EP queuing while stopping transfers

[Wesley Cheng]

Hi Andy,

On 3/22/2021 2:14 PM, Andy Shevchenko wrote:
> On Mon, Mar 22, 2021 at 10:06 PM Wesley Cheng  wrote:
>>
>> Hi Andy,
>>
>> On 3/22/2021 12:34 PM, Andy Shevchenko wrote:
>>> On Mon, Mar 22, 2021 at 8:49 PM Wesley Cheng  wrote:
>>>>
>>>> Hi Andy,
>>>>
>>>> On 3/22/2021 5:48 AM, Andy Shevchenko wrote:
>>>>> On Fri, Mar 12, 2021 at 2:01 AM Wesley Cheng  
>>>>> wrote:
>>>>>>
>>>>>> In the situations where the DWC3 gadget stops active transfers, once
>>>>>> calling the dwc3_gadget_giveback(), there is a chance where a function
>>>>>> driver can queue a new USB request in between the time where the dwc3
>>>>>> lock has been released and re-aquired.  This occurs after we've already
>>>>>> issued an ENDXFER command.  When the stop active transfers continues
>>>>>> to remove USB requests from all dep lists, the newly added request will
>>>>>> also be removed, while controller still has an active TRB for it.
>>>>>> This can lead to the controller accessing an unmapped memory address.
>>>>>>
>>>>>> Fix this by ensuring parameters to prevent EP queuing are set before
>>>>>> calling the stop active transfers API.
>>>>>
>>>>>
>>>>> commit f09ddcfcb8c569675066337adac2ac205113471f
>>>>> Author: Wesley Cheng 
>>>>> Date:   Thu Mar 11 15:59:02 2021 -0800
>>>>>
>>>>>usb: dwc3: gadget: Prevent EP queuing while stopping transfers
>>>>>
>>>>> effectively broke my gadget setup.
>>>>>
>>>>> The output of the kernel (followed by non responsive state of USB 
>>>>> controller):
>>>>>
>>>>> [  195.228586] using random self ethernet address
>>>>> [  195.233104] using random host ethernet address
>>>>> [  195.245306] usb0: HOST MAC aa:bb:cc:dd:ee:f2
>>>>> [  195.249732] usb0: MAC aa:bb:cc:dd:ee:f1
>>>>> # [  195.773594] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
>>>>> [  195.780585] [ cut here ]
>>>>> [  195.785217] dwc3 dwc3.0.auto: No resource for ep2in
>>>>> [  195.790162] WARNING: CPU: 0 PID: 217 at
>>>>> drivers/usb/dwc3/gadget.c:360 dwc3_send_gadget_ep_cmd+0x4b9/0x670
>>>>> [  195.799760] Modules linked in: usb_f_eem u_ether libcomposite
>>>>> brcmfmac brcmutil mmc_block pwm_lpss_pci pwm_lps
>>>>> s snd_sof_pci_intel_tng snd_sof_pci snd_sof_acpi_intel_byt
>>>>> snd_sof_intel_ipc snd_sof_acpi snd_sof snd_sof_nocodec
>>>>> spi_pxa2xx_platform snd_sof_xtensa_dsp spi_pxa2xx_pci
>>>>> extcon_intel_mrfld intel_mrfld_adc sdhci_pci cqhci sdhci m
>>>>> mc_core intel_mrfld_pwrbtn intel_soc_pmic_mrfld hci_uart btbcm btintel
>>>>> [  195.835604] CPU: 0 PID: 217 Comm: irq/16-dwc3 Not tainted 5.12.0-rc4+ 
>>>>> #60
>>>>> [  195.842403] Hardware name: Intel Corporation Merrifield/BODEGA BAY,
>>>>> BIOS 542 2015.01.21:18.19.48
>>>>> [  195.851191] RIP: 0010:dwc3_send_gadget_ep_cmd+0x4b9/0x670
>>>>> [  195.856608] Code: cd 00 00 00 44 89 44 24 20 48 89 4c 24 18 e8 ee
>>>>> f7 e4 ff 48 8b 4c 24 18 4c 89 f2 48 c7 c7 b9
>>>>> ed 4f a0 48 89 c6 e8 ef 24 43 00 <0f> 0b 41 be ea ff ff ff 44 8b 44 24
>>>>> 20 e9 80 fc ff ff 41 83 fe 92
>>>>> [  195.875381] RSP: :a53c00373ba8 EFLAGS: 00010086
>>>>> [  195.880617] RAX:  RBX: 1387 RCX: 
>>>>> dfff
>>>>> [  195.887755] RDX: dfff RSI: ffea RDI: 
>>>>> 
>>>>> [  195.894893] RBP: 9ce8c8f2b028 R08: a0732288 R09: 
>>>>> 9ffb
>>>>> [  195.902034] R10: e000 R11: 3fff R12: 
>>>>> 00041006
>>>>> [  195.909170] R13: a53c00373c24 R14: 9ce8c11dadb0 R15: 
>>>>> 9ce8c2861700
>>>>> [  195.916310] FS:  () GS:9ce8fe20()
>>>>> knlGS:
>>>>> [  195.924409] CS:  0010 DS:  ES:  CR0: 80050033
>>>>> [  195.930161] CR2: f7f694a0 CR3: 38e0c000 CR4: 
>>>>> 001006f0
>>>>> [  195.937300] Call Trace:
>>&g

Re: [PATCH v3] usb: dwc3: gadget: Prevent EP queuing while stopping transfers

[Wesley Cheng]

Hi Andy,

On 3/22/2021 12:34 PM, Andy Shevchenko wrote:
> On Mon, Mar 22, 2021 at 8:49 PM Wesley Cheng  wrote:
>>
>> Hi Andy,
>>
>> On 3/22/2021 5:48 AM, Andy Shevchenko wrote:
>>> On Fri, Mar 12, 2021 at 2:01 AM Wesley Cheng  wrote:
>>>>
>>>> In the situations where the DWC3 gadget stops active transfers, once
>>>> calling the dwc3_gadget_giveback(), there is a chance where a function
>>>> driver can queue a new USB request in between the time where the dwc3
>>>> lock has been released and re-aquired.  This occurs after we've already
>>>> issued an ENDXFER command.  When the stop active transfers continues
>>>> to remove USB requests from all dep lists, the newly added request will
>>>> also be removed, while controller still has an active TRB for it.
>>>> This can lead to the controller accessing an unmapped memory address.
>>>>
>>>> Fix this by ensuring parameters to prevent EP queuing are set before
>>>> calling the stop active transfers API.
>>>
>>>
>>> commit f09ddcfcb8c569675066337adac2ac205113471f
>>> Author: Wesley Cheng 
>>> Date:   Thu Mar 11 15:59:02 2021 -0800
>>>
>>>usb: dwc3: gadget: Prevent EP queuing while stopping transfers
>>>
>>> effectively broke my gadget setup.
>>>
>>> The output of the kernel (followed by non responsive state of USB 
>>> controller):
>>>
>>> [  195.228586] using random self ethernet address
>>> [  195.233104] using random host ethernet address
>>> [  195.245306] usb0: HOST MAC aa:bb:cc:dd:ee:f2
>>> [  195.249732] usb0: MAC aa:bb:cc:dd:ee:f1
>>> # [  195.773594] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
>>> [  195.780585] [ cut here ]
>>> [  195.785217] dwc3 dwc3.0.auto: No resource for ep2in
>>> [  195.790162] WARNING: CPU: 0 PID: 217 at
>>> drivers/usb/dwc3/gadget.c:360 dwc3_send_gadget_ep_cmd+0x4b9/0x670
>>> [  195.799760] Modules linked in: usb_f_eem u_ether libcomposite
>>> brcmfmac brcmutil mmc_block pwm_lpss_pci pwm_lps
>>> s snd_sof_pci_intel_tng snd_sof_pci snd_sof_acpi_intel_byt
>>> snd_sof_intel_ipc snd_sof_acpi snd_sof snd_sof_nocodec
>>> spi_pxa2xx_platform snd_sof_xtensa_dsp spi_pxa2xx_pci
>>> extcon_intel_mrfld intel_mrfld_adc sdhci_pci cqhci sdhci m
>>> mc_core intel_mrfld_pwrbtn intel_soc_pmic_mrfld hci_uart btbcm btintel
>>> [  195.835604] CPU: 0 PID: 217 Comm: irq/16-dwc3 Not tainted 5.12.0-rc4+ #60
>>> [  195.842403] Hardware name: Intel Corporation Merrifield/BODEGA BAY,
>>> BIOS 542 2015.01.21:18.19.48
>>> [  195.851191] RIP: 0010:dwc3_send_gadget_ep_cmd+0x4b9/0x670
>>> [  195.856608] Code: cd 00 00 00 44 89 44 24 20 48 89 4c 24 18 e8 ee
>>> f7 e4 ff 48 8b 4c 24 18 4c 89 f2 48 c7 c7 b9
>>> ed 4f a0 48 89 c6 e8 ef 24 43 00 <0f> 0b 41 be ea ff ff ff 44 8b 44 24
>>> 20 e9 80 fc ff ff 41 83 fe 92
>>> [  195.875381] RSP: :a53c00373ba8 EFLAGS: 00010086
>>> [  195.880617] RAX:  RBX: 1387 RCX: 
>>> dfff
>>> [  195.887755] RDX: dfff RSI: ffea RDI: 
>>> 
>>> [  195.894893] RBP: 9ce8c8f2b028 R08: a0732288 R09: 
>>> 9ffb
>>> [  195.902034] R10: e000 R11: 3fff R12: 
>>> 00041006
>>> [  195.909170] R13: a53c00373c24 R14: 9ce8c11dadb0 R15: 
>>> 9ce8c2861700
>>> [  195.916310] FS:  () GS:9ce8fe20()
>>> knlGS:
>>> [  195.924409] CS:  0010 DS:  ES:  CR0: 80050033
>>> [  195.930161] CR2: f7f694a0 CR3: 38e0c000 CR4: 
>>> 001006f0
>>> [  195.937300] Call Trace:
>>> [  195.939755]  __dwc3_gadget_ep_enable+0x2d4/0x4e0
>>> [  195.944393]  ? dwc3_remove_requests.constprop.0+0x86/0x170
>>
>> Odd that this change would affect the USB enablment path, as they were
>> focused on the pullup disable path.  Would you happen to have any
>> downstream changes on top of v5.12-rc4 we could review to see if they
>> are still required? (ie where is the dwc3_remove_requests() coming from
>> during ep enable)
> 
> You may check my branch [1] on GH. Basically you may be interested in
> the commit:
> 0f86df1294ee7523060cc16eafaf4898c693eab0 REVERTME: usb: dwc3: gadget:
> skip endpoints ep[18]{in,out}
> Otherwise it's a clean v5.12-rc4 with a revert and another USB PHY
> sus

Re: [PATCH v3] usb: dwc3: gadget: Prevent EP queuing while stopping transfers

[Wesley Cheng]

Hi Andy,

On 3/22/2021 5:48 AM, Andy Shevchenko wrote:
> On Fri, Mar 12, 2021 at 2:01 AM Wesley Cheng  wrote:
>>
>> In the situations where the DWC3 gadget stops active transfers, once
>> calling the dwc3_gadget_giveback(), there is a chance where a function
>> driver can queue a new USB request in between the time where the dwc3
>> lock has been released and re-aquired.  This occurs after we've already
>> issued an ENDXFER command.  When the stop active transfers continues
>> to remove USB requests from all dep lists, the newly added request will
>> also be removed, while controller still has an active TRB for it.
>> This can lead to the controller accessing an unmapped memory address.
>>
>> Fix this by ensuring parameters to prevent EP queuing are set before
>> calling the stop active transfers API.
> 
> 
> commit f09ddcfcb8c569675066337adac2ac205113471f
> Author: Wesley Cheng 
> Date:   Thu Mar 11 15:59:02 2021 -0800
> 
>usb: dwc3: gadget: Prevent EP queuing while stopping transfers
> 
> effectively broke my gadget setup.
> 
> The output of the kernel (followed by non responsive state of USB controller):
> 
> [  195.228586] using random self ethernet address
> [  195.233104] using random host ethernet address
> [  195.245306] usb0: HOST MAC aa:bb:cc:dd:ee:f2
> [  195.249732] usb0: MAC aa:bb:cc:dd:ee:f1
> # [  195.773594] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
> [  195.780585] [ cut here ]
> [  195.785217] dwc3 dwc3.0.auto: No resource for ep2in
> [  195.790162] WARNING: CPU: 0 PID: 217 at
> drivers/usb/dwc3/gadget.c:360 dwc3_send_gadget_ep_cmd+0x4b9/0x670
> [  195.799760] Modules linked in: usb_f_eem u_ether libcomposite
> brcmfmac brcmutil mmc_block pwm_lpss_pci pwm_lps
> s snd_sof_pci_intel_tng snd_sof_pci snd_sof_acpi_intel_byt
> snd_sof_intel_ipc snd_sof_acpi snd_sof snd_sof_nocodec
> spi_pxa2xx_platform snd_sof_xtensa_dsp spi_pxa2xx_pci
> extcon_intel_mrfld intel_mrfld_adc sdhci_pci cqhci sdhci m
> mc_core intel_mrfld_pwrbtn intel_soc_pmic_mrfld hci_uart btbcm btintel
> [  195.835604] CPU: 0 PID: 217 Comm: irq/16-dwc3 Not tainted 5.12.0-rc4+ #60
> [  195.842403] Hardware name: Intel Corporation Merrifield/BODEGA BAY,
> BIOS 542 2015.01.21:18.19.48
> [  195.851191] RIP: 0010:dwc3_send_gadget_ep_cmd+0x4b9/0x670
> [  195.856608] Code: cd 00 00 00 44 89 44 24 20 48 89 4c 24 18 e8 ee
> f7 e4 ff 48 8b 4c 24 18 4c 89 f2 48 c7 c7 b9
> ed 4f a0 48 89 c6 e8 ef 24 43 00 <0f> 0b 41 be ea ff ff ff 44 8b 44 24
> 20 e9 80 fc ff ff 41 83 fe 92
> [  195.875381] RSP: :a53c00373ba8 EFLAGS: 00010086
> [  195.880617] RAX:  RBX: 1387 RCX: 
> dfff
> [  195.887755] RDX: dfff RSI: ffea RDI: 
> 
> [  195.894893] RBP: 9ce8c8f2b028 R08: a0732288 R09: 
> 9ffb
> [  195.902034] R10: e000 R11: 3fff R12: 
> 00041006
> [  195.909170] R13: a53c00373c24 R14: 9ce8c11dadb0 R15: 
> 9ce8c2861700
> [  195.916310] FS:  () GS:9ce8fe20()
> knlGS:
> [  195.924409] CS:  0010 DS:  ES:  CR0: 80050033
> [  195.930161] CR2: f7f694a0 CR3: 38e0c000 CR4: 
> 001006f0
> [  195.937300] Call Trace:
> [  195.939755]  __dwc3_gadget_ep_enable+0x2d4/0x4e0
> [  195.944393]  ? dwc3_remove_requests.constprop.0+0x86/0x170

Odd that this change would affect the USB enablment path, as they were
focused on the pullup disable path.  Would you happen to have any
downstream changes on top of v5.12-rc4 we could review to see if they
are still required? (ie where is the dwc3_remove_requests() coming from
during ep enable)

> [  195.949897]  dwc3_gadget_ep_enable+0x5d/0x120
> [  195.954274]  usb_ep_enable+0x27/0x80
> [  195.957869]  gether_connect+0x32/0x1f0 [u_ether]
> [  195.962512]  eem_set_alt+0x6d/0x140 [usb_f_eem]
> [  195.967061]  composite_setup+0x224/0x1ba0 [libcomposite]
> [  195.972405]  ? debug_dma_unmap_page+0x79/0x80
> [  195.976782]  ? configfs_composite_setup+0x6b/0x90 [libcomposite]
> [  195.982811]  configfs_composite_setup+0x6b/0x90 [libcomposite]
> [  195.988668]  dwc3_ep0_interrupt+0x459/0xa50
> [  195.992869]  dwc3_thread_interrupt+0x8e2/0xee0
> [  195.997327]  ? __schedule+0x237/0x6d0
> [  196.001005]  ? disable_irq_nosync+0x10/0x10
> [  196.005200]  irq_thread_fn+0x1b/0x60
> [  196.008789]  irq_thread+0xd6/0x170
> [  196.012202]  ? irq_thread_check_affinity+0x70/0x70
> [  196.017004]  ? irq_forced_thread_fn+0x70/0x70
> [  196.021373]  kthread+0x116/0x130
> [  196.024617]  ? kthread_create_worker_on_cpu+0x60/0x60
> [  196.029680]  ret_from_fork+0x22/0x30
> [  1

Re: [dev] st: enlarge font

[Wesley Pannell]

Can we remove this email address from the list? This is rediculous.

‐‐‐ Original Message ‐‐‐

On Monday, March 22nd, 2021 at 12:59 AM,  
wrote:

> you'll also have to zoom webpages
>
> and emails in thunderbird
>
> in general the ppi / 96 = zoom %
>
> On 3/20/21 1:30 PM, Nuno Teixeira wrote:
>
> > Hello all,
> >
> > Recently I bought a new laptop that runs at:
> >
> > [ 144.414] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
> >
> > st font size is too small and I use Ctrl-Shift-Page Up 3 times to get
> >
> > desired font size.
> >
> > How do I tell st to use my desired font size instead of using
> >
> > Ctrl-Shift-Page Up?
> >
> > I will need a command to find font geometry and then start st with -g
> >
> > geometry, I think.
> >
> > Thanks,
> >
> > Nuno Teixeira

Re: [PATCH 2/2] usb: dwc3: gadget: Ignore EP queue requests during bus reset

[Wesley Cheng]

Hi Thinh,


On 3/19/2021 7:01 PM, Thinh Nguyen wrote:
> Wesley Cheng wrote:
>>
>>
>> On 3/19/2021 5:40 PM, Thinh Nguyen wrote:
>>> Hi,
>>>
>>> Wesley Cheng wrote:
>>>> The current dwc3_gadget_reset_interrupt() will stop any active
>>>> transfers, but only addresses blocking of EP queuing for while we are
>>>> coming from a disconnected scenario, i.e. after receiving the disconnect
>>>> event.  If the host decides to issue a bus reset on the device, the
>>>> connected parameter will still be set to true, allowing for EP queuing
>>>> to continue while we are disabling the functions.  To avoid this, set the
>>>> connected flag to false until the stop active transfers is complete.
>>>>
>>>> Signed-off-by: Wesley Cheng 
>>>> ---
>>>>  drivers/usb/dwc3/gadget.c | 9 +
>>>>  1 file changed, 9 insertions(+)
>>>>
>>>> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
>>>> index 6e14fdc..d5ed0f69 100644
>>>> --- a/drivers/usb/dwc3/gadget.c
>>>> +++ b/drivers/usb/dwc3/gadget.c
>>>> @@ -3327,6 +3327,15 @@ static void dwc3_gadget_reset_interrupt(struct dwc3 
>>>> *dwc)
>>>>u32 reg;
>>>>  
>>>>/*
>>>> +   * Ideally, dwc3_reset_gadget() would trigger the function
>>>> +   * drivers to stop any active transfers through ep disable.
>>>> +   * However, for functions which defer ep disable, such as mass
>>>> +   * storage, we will need to rely on the call to stop active
>>>> +   * transfers here, and avoid allowing of request queuing.
>>>> +   */
>>>> +  dwc->connected = false;
>>>> +
>>>> +  /*
>>>> * WORKAROUND: DWC3 revisions <1.88a have an issue which
>>>> * would cause a missing Disconnect Event if there's a
>>>> * pending Setup Packet in the FIFO.
>>>>
>>>
>>> This doesn't look right. Did you have rebase issue with your local
>>> change again?
>>>
>>> BR,
>>> Thinh
>>>
>> Hi Thinh,
>>
>> This was rebased on Greg's usb-linus branch, which has commit
>> f09ddcfcb8c5 ("usb: dwc3: gadget: Prevent EP queuing while stopping
>> transfers") merged.
> 
> Ah I see.
> 
>>
>> commit f09ddcfcb8c5  moved the dwc->connected = true to after we have
>> finished stop active transfers.  However, this change will also ensure
>> that the connected flag is set to false to ensure that when we call stop
>> active transfers, nothing can prepare TRBs.  (previous commit only
>> addresses the case where we get the reset interrupt when coming from a
>> disconnected state)
>>
> 
> That still doesn't address this issue.
> 
> Because:
> 1) We're still protected by the spin_lock_irq*(), so this change doesn't
> make any difference while handling an event.

Thank you for the feedback.  So it is true that we lock dwc->lock while
handling EP/device events, but what these changes are trying to address
is that during dwc3_stop_active_transfers() we will eventually call
dwc3_gadget_giveback() to call the complete() functions registered by
the function driver.  Before we call the complete() callbacks, we unlock
dwc->lock, so we are no longer protected, and if there was a pending ep
queue from a function driver, that would allow it to acquire the lock
and continue preparing the TRBs.

> 2) We don't enable the interrupt for END_TRANSFER command completion
> when doing dwc3_stop_active_transfers(), the
> DWC3_EP_END_TRANSFER_PENDING flag will not be set to prevent preparing
> new requests.
> 
Agreed.  That is the reason for adding the check to dwc->connected in
__dwc3_gadget_ep_queue()

if (!dep->endpoint.desc || !dwc->pullups_connected || !dwc->connected) {
dev_err(dwc->dev, "%s: can't queue to disabled endpoint\n",
dep->name);
return -ESHUTDOWN;

> We should do dwc->connected = true when we handle connection_done
> interrupt instead. The END_TRANSFER command should complete before this.
> 
So how this change will address the issue is:

1.  IRQ handler will acquire dwc->lock
2.  dwc3_gadget_reset_handler() sets dwc->connected = false
3.  Call to dwc3_stop_active_transfers()
---> dwc3_gadget_giveback() releases dwc->lock
4.  If there was a pending ep queue (waiting for dwc->lock) it can
continue here
5.  __dwc3_gadget_ep_queue() exits early due to dwc->connected = false
6.  dwc3_gadget_giveback() re-acquires dwc->lock and continues

Thanks
Wesley Cheng

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH 2/2] usb: dwc3: gadget: Ignore EP queue requests during bus reset

[Wesley Cheng]

On 3/19/2021 5:40 PM, Thinh Nguyen wrote:
> Hi,
> 
> Wesley Cheng wrote:
>> The current dwc3_gadget_reset_interrupt() will stop any active
>> transfers, but only addresses blocking of EP queuing for while we are
>> coming from a disconnected scenario, i.e. after receiving the disconnect
>> event.  If the host decides to issue a bus reset on the device, the
>> connected parameter will still be set to true, allowing for EP queuing
>> to continue while we are disabling the functions.  To avoid this, set the
>> connected flag to false until the stop active transfers is complete.
>>
>> Signed-off-by: Wesley Cheng 
>> ---
>>  drivers/usb/dwc3/gadget.c | 9 +
>>  1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
>> index 6e14fdc..d5ed0f69 100644
>> --- a/drivers/usb/dwc3/gadget.c
>> +++ b/drivers/usb/dwc3/gadget.c
>> @@ -3327,6 +3327,15 @@ static void dwc3_gadget_reset_interrupt(struct dwc3 
>> *dwc)
>>  u32 reg;
>>  
>>  /*
>> + * Ideally, dwc3_reset_gadget() would trigger the function
>> + * drivers to stop any active transfers through ep disable.
>> + * However, for functions which defer ep disable, such as mass
>> + * storage, we will need to rely on the call to stop active
>> + * transfers here, and avoid allowing of request queuing.
>> + */
>> +dwc->connected = false;
>> +
>> +/*
>>   * WORKAROUND: DWC3 revisions <1.88a have an issue which
>>   * would cause a missing Disconnect Event if there's a
>>   * pending Setup Packet in the FIFO.
>>
> 
> This doesn't look right. Did you have rebase issue with your local
> change again?
> 
> BR,
> Thinh
> 
Hi Thinh,

This was rebased on Greg's usb-linus branch, which has commit
f09ddcfcb8c5 ("usb: dwc3: gadget: Prevent EP queuing while stopping
transfers") merged.

commit f09ddcfcb8c5  moved the dwc->connected = true to after we have
finished stop active transfers.  However, this change will also ensure
that the connected flag is set to false to ensure that when we call stop
active transfers, nothing can prepare TRBs.  (previous commit only
addresses the case where we get the reset interrupt when coming from a
disconnected state)

Thanks
Wesley Cheng

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH v3 1/2] usb: dwc3: Trigger a GCTL soft reset when switching modes in DRD

[Wesley Cheng]

On 3/8/2021 10:33 PM, Wesley Cheng wrote:
> 
> 
> On 3/8/2021 7:05 PM, Thinh Nguyen wrote:
>> Wesley Cheng wrote:
>>>
>>> On 3/6/2021 3:41 PM, Thinh Nguyen wrote:
>>>> Wesley Cheng wrote:
>>>>> On 1/8/2021 4:44 PM, Thinh Nguyen wrote:
>>>>>> Hi,
>>>>>>
>>>>>> John Stultz wrote:
>>>>>>> On Fri, Jan 8, 2021 at 4:26 AM Felipe Balbi  wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> John Stultz  writes:
>>>>>>>>> From: Yu Chen 
>>>>>>>>>
>>>>>>>>> Just resending this, as discussion died out a bit and I'm not
>>>>>>>>> sure how to make further progress. See here for debug data that
>>>>>>>>> was requested last time around:
>>>>>>>>>   
>>>>>>>>> https://urldefense.com/v3/__https://lore.kernel.org/lkml/calaqxlxdnaufjkx0an9xwwtfwvjmwigppy2aqsnj56yvnbu...@mail.gmail.com/__;!!A4F2R9G_pg!LNzuprAeg-O80SgolYkIkW4-ne-M-yLWCDUY9MygAIrQC398Z6gRJ9wnsnlqd3w$
>>>>>>>>>  
>>>>>>>>>
>>>>>>>>> With the current dwc3 code on the HiKey960 we often see the
>>>>>>>>> COREIDLE flag get stuck off in __dwc3_gadget_start(), which
>>>>>>>>> seems to prevent the reset irq and causes the USB gadget to
>>>>>>>>> fail to initialize.
>>>>>>>>>
>>>>>>>>> We had seen occasional initialization failures with older
>>>>>>>>> kernels but with recent 5.x era kernels it seemed to be becoming
>>>>>>>>> much more common, so I dug back through some older trees and
>>>>>>>>> realized I dropped this quirk from Yu Chen during upstreaming
>>>>>>>>> as I couldn't provide a proper rational for it and it didn't
>>>>>>>>> seem to be necessary. I now realize I was wrong.
>>>>>>>>>
>>>>>>>>> After resubmitting the quirk, Thinh Nguyen pointed out that it
>>>>>>>>> shouldn't be a quirk at all and it is actually mentioned in the
>>>>>>>>> programming guide that it should be done when switching modes
>>>>>>>>> in DRD.
>>>>>>>>>
>>>>>>>>> So, to avoid these !COREIDLE lockups seen on HiKey960, this
>>>>>>>>> patch issues GCTL soft reset when switching modes if the
>>>>>>>>> controller is in DRD mode.
>>>>>>>>>
>>>>>>>>> Cc: Felipe Balbi 
>>>>>>>>> Cc: Tejas Joglekar 
>>>>>>>>> Cc: Yang Fei 
>>>>>>>>> Cc: YongQin Liu 
>>>>>>>>> Cc: Andrzej Pietrasiewicz 
>>>>>>>>> Cc: Thinh Nguyen 
>>>>>>>>> Cc: Jun Li 
>>>>>>>>> Cc: Mauro Carvalho Chehab 
>>>>>>>>> Cc: Greg Kroah-Hartman 
>>>>>>>>> Cc: linux-...@vger.kernel.org
>>>>>>>>> Signed-off-by: Yu Chen 
>>>>>>>>> Signed-off-by: John Stultz 
>>>>>>>>> ---
>>>>>>>>> v2:
>>>>>>>>> * Rework to always call the GCTL soft reset in DRD mode,
>>>>>>>>>   rather then using a quirk as suggested by Thinh Nguyen
>>>>>>>>>
>>>>>>>>> v3:
>>>>>>>>> * Move GCTL soft reset under the spinlock as suggested by
>>>>>>>>>   Thinh Nguyen
>>>>>>>> Because this is such an invasive change, I would prefer that we get
>>>>>>>> Tested-By tags from a good fraction of the users before applying these
>>>>>>>> two changes.
>>>>>>> I'm happy to reach out to folks to try to get that. Though I'm
>>>>>>> wondering if it would be better to put it behind a dts quirk flag, as
>>>>>>> originally proposed?
>>>>>>>
>>>>>>> https://urldefense.com/v3/__https://lore.kernel.org/lkml/20201021181803.79650-1-john.stu...@linaro.org/__;!!A4F2R9G_pg!LNzuprAeg-O80SgolYkIkW4-ne-M-yLWCDUY9MygAIrQC398Z6gRJ9wnRWITZfc$
>>>>>>>  
>>>>>>>
>