Allow header doesn't work alone

I'm trying to run the following tests and the 1st one is successful, but the 2nd one will not pass unless I add .expect(405) either before or after the .expect('Allow') statement.
var app = require('../../server/app');
var request = require('supertest')(app);

      it("GET /designs/ returns 405", function(done) {
         request
            .get('/designs/')
            .expect('Allow', 'POST')
            .expect(405, done);
      });

      it("GET /designs/ retuns Allow header with POST", function(done) {
         request
            .get('/designs/')
            .expect('Allow', 'POST', done);
      });

Server Response:
$ curl -D - http://.....:8000/designs
HTTP/1.1 405 Method Not Allowed
X-Powered-By: Express
Allow: POST
Content-Type: text/html; charset=utf-8
Content-Length: 18
ETag: W/"12-4ACs7zIBKmUNjCQ9d8cwLA"
Date: Thu, 20 Aug 2015 01:45:28 GMT
Connection: keep-alive

Method Not Allowed

The 2nd text seems to pass if the response is of the following:
$ curl -D - http://.....:8000/designs
HTTP/1.1 200 OK
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Download-Options: noopen
X-XSS-Protection: 1; mode=block
Allow: POST
Content-Type: application/json; charset=utf-8
Content-Length: 2
ETag: W/"2-mZFLkyvTelC5g8XnyQrpOw"
Date: Tue, 25 Aug 2015 00:36:29 GMT
Connection: keep-alive

{}

This has to do with #224  and how non 2xx status codes are handled due to an underlying change in superagent 1.x.
@steven10172 your example passes because the status code returned is 200, not a 405.


Add description prop support for Ng-Zorro-Antd UI

Could we please add description prop support for NG-Zorro controls?
Similar to other UI components (such as Bootstrap as shown below):

It would quite helpful for NG-Zorro to support the 'description' prop, as it currently stands, it only accepts 'label' as shown here:

Ng-Zorro-Antd form controls support extra information via nzExtra:

and the code:

This issue has been fixed and released as part of v6.2.0 release.
Please let us know, in case you are still encountering a similar issue/problem.
Thank you!

you can also use this library：https://github.com/zzhimin/ngx-ng-zorro-formly


Tab Length setting is not respected

hi,
my "Tab Length" setting is set to 2 (the default), but 4 spaces are used in the source code.

I am having the same issue

Actually, this is not a bug but by design. The language-rust package sets editor settings that conform to the Rust style guide. If you really want different settings, you can override them in the package settings.
There's a discussion in #93 where we'll hopefully find out if most people like to keep this behavior or if we should change it.


adding tutorials back to docs until longer term fix

Description
Tutorial copy past was broken in CI, adding a temp fix
Type of change
Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
Existing test

@yifanwu I updated formatting of feature highlights (finger-ups) because Markdown titles (e.g., ##) are parsed as clickable sections by Sphinx.


Additional info on Classes/Triggers Overview tab

An additional column on the triggers overview tab would help if it flags which triggers have logic added (as we know logic should be within classes, not the trigger itself!)

On the apex classes overview tab - an additional column that flags if there are SOQL Queries/DML inside FOR Loops -> not sure if it's possible to go to this level of detail though?

The two requirements are very interesting but needs to analyse Apex code...
PMD should be better at this. Check ApexPMD at https://pmd.github.io/latest/pmd_apex_metrics_index.html
We could probably check some quick stuff like size of a trigger should not be for example more than 500 characters? if it is the case, we might suspect that there is logic in it....
What would be the threshold in terms of size for a trigger??

thanks @VinceFINET ! will check out  ApexPMD, is it similar to what CodeScan does?
re: We could probably check some quick stuff like size of a trigger should not be for example more than 500 characters? --> let me go through some of the triggers in my org (we have loads of triggers) and come back to you with an avg # on characters i see.

Any update @pritaunk ?

Should have this info by end of week, does it need to be character count or # lines do?
So far I am seeing triggers without logic can go up to roughly 20-25 lines (600-650 characters, without space) @VinceFINET

Just noticed one WITH logic that goes up to 7500 characters and 165 lines!!!!!!!
@VinceFINET

ok so adding a warning if triggers have more than 5000 characters


Update documentation for output modes

Here's the documentation for the output modes. It right now takes Bidsapp mode for granted, and introduces workflow mode as a way of directly calling the Snakemake CLI. It also teaches users to directly create or clone the app to the directory they want their results to go, and only mentions the -W flag at the end.
Need to make sure the file tree structures render correctly on Readthedocs. Does anyone know how to test that?
Will parts of the documentation (especially the tutorial) need to be updated to reflect new assumptions made in Snakebids app development (e.g. what kind of output to expect in Bidsapp mode)?

Is there a staging site for the readthedocs currently? One possible way is to enable some sort of preview via actions (similar to how netlify does the github pages for the lab site). It seems like readthedocs provides some way of doing this though I haven't looked too deep into this yet. https://docs.readthedocs.io/en/latest/pull-requests.html

Looks like something an admin of readthedocs needs to do, at any rate. @akhanf?

re: readthedocs, I've just now enabled building on pull requests too, but haven't used that feature before, not sure where things will end up.
If you make a readthedocs account and give me the username I can add you as maintainer, right now just myself and @tkkuehn are maintainers

So the documentation is very much not working. (https://snakebids--67.org.readthedocs.build/en/67/running_snakebids/overview.html#workflow-mode). Is someone more familiar with .rst able to comment on what may be incorrect? (@akhanf @tkkuehn @kaitj )?

So the documentation is very much not working.

The documentation at that link looks okay to me at a glance -- What's the issue?

Do you mean the "warning" box around everything (which seems expected if a
PR build) or something else?
On Mon, Nov 15, 2021 at 12:25 PM Tristan Kuehn @.***>
wrote:

So the documentation is very much not working.
The documentation at that link looks okay to me at a glance -- What's the
issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/akhanf/snakebids/pull/67#issuecomment-969138620, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXV2XOJR76OFLKD54L3PB3UME7A5ANCNFSM5HZKJM7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Ali R. Khan, PhD
Canada Research Chair in Computational Neuroimaging
Assistant Professor, Medical Biophysics
Scientist, Robarts Research Institute
Schulich School of Medicine & Dentistry, Western University
e. @.***
t.<PHONE_NUMBER> (x24280)
w. www.khanlab.ca

So it is working now... Either the last commit or time's magic touch, I've no idea.
Any last comments before I commit?


Add QGis

Add GIS awesome framework writhed in python

https://github.com/totpero/awesome-qgis
**[An awesome list that curates the best QGis frameworks, libraries, tools, plugins, tutorials, articles,resources and more. **
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

[x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
[x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
[x] You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
[x] You have read and understood the instructions for creating a list.
[x] This pull request has a title in the format Add Name of List. It should not contain the word Awesome.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

[x] Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

[x] Your entry should be added at the bottom of the appropriate category.
[x] The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

[x] No blockchain-related lists.
[x] The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

[x] Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
[x] Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
[x] The default branch should be named main, not master.
[x] Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

[x] It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
[x] The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

[x] The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

[x] Non-generated Markdown file in a GitHub repo.
[x] The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
[x] Not a duplicate. Please search for existing submissions.
[x] Only has awesome items. Awesome lists are curations of the best, not everything.
[x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
[x] Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to a maximum of half the width of the original image.
Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.

[x] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
[x] Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

[x] Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

[x] Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

[x] Has contribution guidelines.

The file should be named contributing.md. The casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

[x] All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
[x] Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

[x] Does not use hard-wrapping.
[x] Does not include a CI (e.g. GitHub Actions) badge.You can still use a CI for linting, but the badge has no value in the readme.
[x] Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Hi @totpero ,
Would you mind running the awesome-lint and checking the errors it provides?
I ran it and I'm getting:

✖   1:1  Missing or invalid Table of Contents  remark-lint:awesome-toc
✖   5:3  Invalid list item link URL            remark-lint:awesome-list-item

I suspect that the first error is because you're missing the heading "Contents" for your Table of Contents (it simply lists the links).
The latter errors are coming from the fact that the headings referrer in the links are not present in the README.
Eg, - [Utilities](#utilities) should link to some heading "Utilities", but it's nowhere to be found in the README.
In general, I found it quite helpful to have Table of Contents auto-generated in VSCode with extension "Markdown All in One" - perhaps try it out?

There is no content in this list.


[Relay/TOPI][OP] Add arange op in Relay and TOPI

Currently I put start, stop, step in Relay attributes since it is required to infer the output shape. Later if Relay supports unknown dimension like Any, we can move them into inputs of arange op instead of attributes.
This PR relies on https://github.com/dmlc/tvm/pull/2615.

@zhreshold

Hey @yzhliu, could you help review this PR?

Thanks all. This is merged.


Cannot Clone Private Repositories

I checked a couple of posts from older versions:-
https://github.com/drone/drone/issues/371
But it seems I cannot get the public key for drone itself. I checked the settings page of repo, but it doesn't contain a sshkey either.
I tried going inside docker container, and it seems, that there are ssh keys in the filesystem.
https://stackoverflow.com/questions/46525611/running-docker-interactive-shell
How to clone private repositories using drone public key?

Please create a thread at https://discourse.drone.io for usage support. We reserve the issue tracker for bug reports and feature requests only.


Fix "?" references in PDF files

Some PDF files such as https://us.metamath.org/downloads/finiteaxiom.pdf need to be compiled twice, in order for references to work.
Fix:
Duplicate the pdflatex call (this line) in build-website.sh.

could you submit this as a PR?

Sure, single line PR is ready. 😅

It still seems broken. Were the scripts ever used to rebuild the PDFs after this patch?


Mod Settings not displaying correctly

I don't know why it's doing this please help. I even tried using it while in a match but it was the same.

Same, let me know if you find a solution

The texture of reset button is missing. Download reset.vtf and reset.vmt from here if you want a cleaner look.


Environment ID is required

Trying to use the plugin, but get this error:
$ vagrant scp /home/vagrant/test.txt ./
.../.vagrant.d/gems/gems/vagrant-scp-0.4.2/lib/vagrant/scp/commands/scp.rb:19:in execute': undefined method empty?' for nil:NilClass (NoMethodError)
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/cli.rb:42:in execute' 	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:301:in cli'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant:174:in `'
Adding the environment ID worked, but I thought it was optional if there is only one.
Vagrant version is 1.7.4.

Hi Daryl,
I've decided to disable that behaviour because it was confusing to some users, as the direction in which the scp happens (from the Vagrant VM to the local host, or vice versa) is unspecified.
You should be able to run that command as:
vagrant scp :/home/vagrant/test.txt ./

Where the ':' indicate the remote host. This is equivalent to:
vagrant scp default:/home/vagrant/test.txt ./

Let me know if it works out for you, because it's a brand new feature, that was added yesterday.


getElementText working but elementClick not working

getElementText is working but elementClick is stuck forever
Logs -
} 2022-07-11T18:04:29.648Z INFO webdriver: COMMAND getElementText("<Screenshot[base64]>") 2022-07-11T18:04:29.649Z INFO webdriver: [GET] http://<IP_ADDRESS>:4723/session/bdc99cad-0752-4130-9ea8-e82ff8f3a7a1/element/eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiY291bnRlciIsImtleVZhbHVlVHlwZSI6IlN0cmluZyJ9/text 2022-07-11T18:04:29.964Z INFO webdriver: RESULT 0 2022-07-11T18:04:29.964Z INFO webdriver: COMMAND elementClick("eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiaW5jcmVtZW50QnV0dG9uIiwia2V5VmFsdWVUeXBlIjoiU3RyaW5nIn0") 2022-07-11T18:04:29.964Z INFO webdriver: [POST] http://<IP_ADDRESS>:4723/session/bdc99cad-0752-4130-9ea8-e82ff8f3a7a1/element/eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiaW5jcmVtZW50QnV0dG9uIiwia2V5VmFsdWVUeXBlIjoiU3RyaW5nIn0/click
Appium Logs
MacBook-Air-2:~ sahilkhurana$ appium WARN Appium Appium encountered 2 warnings while validating drivers found in manifest /Users/sahilkhurana/.appium/node_modules/.cache/appium/extensions.yaml WARN Appium Driver "flutter" has 1 potential problem:  WARN Appium   - Driver "flutter" (packageappium-flutter-driver) may be incompatible with the current version of Appium (v2.0.0-beta.40) due to an invalid or missing peer dependency on Appium. Please ask the developer of appium-flutter-driverto add a peer dependency<EMAIL_ADDRESS>[Appium] Welcome to Appium v2.0.0-beta.40 (REV 5b3d188b83f27ec31d97f3f3e6e49220e09b6985) [Appium] Attempting to load driver xcuitest... [debug] [Appium] Requiring driver at /Users/sahilkhurana/.appium/node_modules/appium-xcuitest-driver [Appium] Attempting to load driver uiautomator2... [debug] [Appium] Requiring driver at /Users/sahilkhurana/.appium/node_modules/appium-uiautomator2-driver [Appium] Attempting to load driver flutter... [debug] [Appium] Requiring driver at /Users/sahilkhurana/.appium/node_modules/appium-flutter-driver (node:7792) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit (Use node --trace-warnings ...` to show where the warning was created)
[Appium] Appium REST http interface listener started on <IP_ADDRESS>:4723
[Appium] Available drivers:
[Appium]   -<EMAIL_ADDRESS>(automationName 'XCUITest')
[Appium]   -<EMAIL_ADDRESS>(automationName 'UiAutomator2')
[Appium]   -<EMAIL_ADDRESS>(automationName 'Flutter')
[Appium] No plugins have been installed. Use the "appium plugin" command to install the one(s) you want to use.
[HTTP] --> POST /session
[HTTP] {"capabilities":{"alwaysMatch":{"appium:automationName":"Flutter","appium:platformName":"Android","appium:deviceName":"emulator-5554","appium:retryBackoffTime":5000,"appium:app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk"},"firstMatch":[{}]},"desiredCapabilities":{"appium:automationName":"Flutter","appium:platformName":"Android","appium:deviceName":"emulator-5554","appium:retryBackoffTime":5000,"appium:app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk"}}
[debug] [AppiumDriver@c272] Calling AppiumDriver.createSession() with args: [{"appium:automationName":"Flutter","appium:platformName":"Android","appium:deviceName":"emulator-5554","appium:retryBackoffTime":5000,"appium:app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk"},null,{"alwaysMatch":{"appium:automationName":"Flutter","appium:platformName":"Android","appium:deviceName":"emulator-5554","appium:retryBackoffTime":5000,"appium:app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk"},"firstMatch":[{}]}]
[debug] [AppiumDriver@c272] Event 'newSessionRequested' logged at<PHONE_NUMBER>812 (23:34:13 GMT+0530 (India Standard Time))
[BaseDriver] The capabilities ["platformName"] are standard capabilities and do not require "appium:" prefix
[Appium] Attempting to find matching driver for automationName 'Flutter' and platformName 'Android'
[Appium] The 'flutter' driver was installed and matched caps.
[Appium] Will require it at /Users/sahilkhurana/.appium/node_modules/appium-flutter-driver
[debug] [Appium] Requiring driver at /Users/sahilkhurana/.appium/node_modules/appium-flutter-driver
[AppiumDriver@c272] Appium v2.0.0-beta.40 creating new FlutterDriver (v1.4.0) session
[AppiumDriver@c272] Checking BaseDriver versions for Appium and FlutterDriver
[AppiumDriver@c272] Appium's BaseDriver version is 8.5.7
[AppiumDriver@c272] FlutterDriver's BaseDriver version is 8.5.7
[debug] [FlutterDriver@de4e] Creating session with W3C capabilities: {
[debug] [FlutterDriver@de4e]   "alwaysMatch": {
[debug] [FlutterDriver@de4e]     "appium:automationName": "Flutter",
[debug] [FlutterDriver@de4e]     "platformName": "Android",
[debug] [FlutterDriver@de4e]     "appium:deviceName": "emulator-5554",
[debug] [FlutterDriver@de4e]     "appium:retryBackoffTime": 5000,
[debug] [FlutterDriver@de4e]     "appium:app": "/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk"
[debug] [FlutterDriver@de4e]   },
[debug] [FlutterDriver@de4e]   "firstMatch": [
[debug] [FlutterDriver@de4e]     {}
[debug] [FlutterDriver@de4e]   ]
[debug] [FlutterDriver@de4e] }
[FlutterDriver@de4e] The following capabilities were provided, but are not recognized by Appium:
[FlutterDriver@de4e]   retryBackoffTime
[FlutterDriver@de4e]   app
[FlutterDriver@de4e (bdc99cad)] Session created with session id: bdc99cad-0752-4130-9ea8-e82ff8f3a7a1
[FlutterDriver] Starting an Android proxy session
[debug] [AndroidUiautomator2Driver@cee8] Creating session with W3C capabilities: {
[debug] [AndroidUiautomator2Driver@cee8]   "alwaysMatch": {
[debug] [AndroidUiautomator2Driver@cee8]     "appium:automationName": "Flutter",
[debug] [AndroidUiautomator2Driver@cee8]     "platformName": "Android",
[debug] [AndroidUiautomator2Driver@cee8]     "appium:deviceName": "emulator-5554",
[debug] [AndroidUiautomator2Driver@cee8]     "appium:retryBackoffTime": 5000,
[debug] [AndroidUiautomator2Driver@cee8]     "appium:app": "/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk"
[debug] [AndroidUiautomator2Driver@cee8]   },
[debug] [AndroidUiautomator2Driver@cee8]   "firstMatch": [
[debug] [AndroidUiautomator2Driver@cee8]     {}
[debug] [AndroidUiautomator2Driver@cee8]   ]
[debug] [AndroidUiautomator2Driver@cee8] }
[AndroidUiautomator2Driver@cee8] The following capabilities were provided, but are not recognized by Appium:
[AndroidUiautomator2Driver@cee8]   retryBackoffTime
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] Session created with session id: 97dc0b5c-f633-43e6-a91b-e618ea0bc6d7
[BaseDriver] Using local app '/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Checking whether app is actually present
[ADB] Found 3 'build-tools' folders under '/Users/sahilkhurana/Library/Android/sdk' (newest first):
[ADB]     /Users/sahilkhurana/Library/Android/sdk/build-tools/33.0.0
[ADB]     /Users/sahilkhurana/Library/Android/sdk/build-tools/30.0.3
[ADB]     /Users/sahilkhurana/Library/Android/sdk/build-tools/28.0.3
[ADB] Using 'adb' from '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 start-server'
[AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices
[debug] [ADB] Connected devices: [{"udid":"emulator-5554","state":"device"}]
[AndroidDriver] Using device: emulator-5554
[ADB] Using 'adb' from '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 start-server'
[debug] [ADB] Setting device id to emulator-5554
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell getprop ro.build.version.sdk'
[debug] [ADB] Current device property 'ro.build.version.sdk': 28
[ADB] Getting device platform version
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell getprop ro.build.version.release'
[debug] [ADB] Current device property 'ro.build.version.release': 9
[debug] [ADB] Device API level: 28
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] Relaxing hidden api policy
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell 'settings put global hidden_api_policy_pre_p_apps 1;settings put global hidden_api_policy_p_apps 1;settings put global hidden_api_policy 1''
[debug] [AndroidDriver] Parsing package and activity from app manifest
[ADB] Package name: 'co.test.dev'
[ADB] Main activity name: 'co.test.MainActivity'
[debug] [AndroidDriver] Parsed package and activity are: co.test.dev/co.test.MainActivity
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 wait-for-device'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell echo ping'
[debug] [AndroidDriver] Pushing settings apk to device...
[debug] [ADB] Getting install status for io.appium.settings
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package io.appium.settings'
[debug] [ADB] 'io.appium.settings' is installed
[debug] [ADB] Getting package info for 'io.appium.settings'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package io.appium.settings'
[debug] [ADB] The version name of the installed 'io.appium.settings' is greater or equal to the application version name ('4.1.1' >= '4.1.1')
[debug] [ADB] There is no need to install/upgrade '/Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/io.appium.settings/apks/settings_apk-debug.apk'
[debug] [ADB] Getting IDs of all 'io.appium.settings' processes
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell 'pgrep --help; echo $?''
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pgrep -f ([[:blank:]]|^)io.appium.settings([[:blank:]]|$)'
[debug] [AndroidDriver] io.appium.settings is already running. There is no need to reset its permissions.
[debug] [Logcat] Starting logs capture with command: /Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 logcat -v threadtime
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Forwarding UiAutomator2 Server port 6790 to local port 8203
[debug] [ADB] Forwarding system: 8203 to device: 6790
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 forward tcp:8203 tcp:6790'
[debug] [ADB] Getting install status for io.appium.uiautomator2.server
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package io.appium.uiautomator2.server'
[debug] [ADB] 'io.appium.uiautomator2.server' is installed
[debug] [ADB] Getting package info for 'io.appium.uiautomator2.server'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package io.appium.uiautomator2.server'
[debug] [ADB] The version name of the installed 'io.appium.uiautomator2.server' is greater or equal to the application version name ('5.6.2' >= '5.6.2')
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] io.appium.uiautomator2.server installation state: sameVersionInstalled
[debug] [ADB] Checking app cert for /Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v5.6.2.apk
[ADB] Using 'apksigner.jar' from '/Users/sahilkhurana/Library/Android/sdk/build-tools/33.0.0/lib/apksigner.jar'
[debug] [ADB] Starting apksigner: /Library/Java/JavaVirtualMachines/jdk-17.0.1.jdk/Contents/Home/bin/java -Xmx1024M -Xss1m -jar /Users/sahilkhurana/Library/Android/sdk/build-tools/33.0.0/lib/apksigner.jar verify --print-certs /Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v5.6.2.apk
[debug] [ADB] apksigner stdout: Signer #1 certificate DN<EMAIL_ADDRESS>CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[debug] [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[debug] [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[debug] [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[debug] [ADB]
[debug] [ADB] sha256 hash did match for 'appium-uiautomator2-server-v5.6.2.apk'
[ADB] '/Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v5.6.2.apk' is signed with the default certificate
[debug] [ADB] Getting install status for io.appium.uiautomator2.server.test
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package io.appium.uiautomator2.server.test'
[debug] [ADB] 'io.appium.uiautomator2.server.test' is installed
[debug] [ADB] Checking app cert for /Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk
[debug] [ADB] Starting apksigner: /Library/Java/JavaVirtualMachines/jdk-17.0.1.jdk/Contents/Home/bin/java -Xmx1024M -Xss1m -jar /Users/sahilkhurana/Library/Android/sdk/build-tools/33.0.0/lib/apksigner.jar verify --print-certs /Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk
[debug] [ADB] apksigner stdout: Signer #1 certificate DN<EMAIL_ADDRESS>CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[debug] [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[debug] [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[debug] [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[debug] [ADB]
[debug] [ADB] sha256 hash did match for 'appium-uiautomator2-server-debug-androidTest.apk'
[ADB] '/Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk' is signed with the default certificate
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] Server packages are not going to be (re)installed
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Waiting up to 30000ms for services to be available
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pm list instrumentation'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
[ADB] Adding packages ["io.appium.settings","io.appium.uiautomator2.server","io.appium.uiautomator2.server.test"] to Doze whitelist
[debug] [ADB] Got the following command chunks to execute: [["dumpsys","deviceidle","whitelist","+io.appium.settings",";","dumpsys","deviceidle","whitelist","+io.appium.uiautomator2.server",";","dumpsys","deviceidle","whitelist","+io.appium.uiautomator2.server.test",";"]]
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys deviceidle whitelist +io.appium.settings ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server.test ;'
[debug] [ADB] Checking app cert for /Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk
[debug] [ADB] Starting apksigner: /Library/Java/JavaVirtualMachines/jdk-17.0.1.jdk/Contents/Home/bin/java -Xmx1024M -Xss1m -jar /Users/sahilkhurana/Library/Android/sdk/build-tools/33.0.0/lib/apksigner.jar verify --print-certs /Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk
[debug] [ADB] apksigner stdout: Signer #1 certificate DN: C=US, O=Android, CN=Android Debug
[debug] [ADB] Signer #1 certificate SHA-256 digest: 45af6adf641e1063f0a5d4c4be1ded6884969a3a12580be4a46596e97491160b
[debug] [ADB] Signer #1 certificate SHA-1 digest: 500f7ebede27c3d98a990f3a9d00f3b319f76cd0
[debug] [ADB] Signer #1 certificate MD5 digest: 552063fdacae362a43f3b6ca88c67601
[debug] [ADB]
[ADB] '/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk' is signed with a non-default certificate
[debug] [ADB] Getting install status for co.test.dev
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package co.test.dev'
[debug] [ADB] 'co.test.dev' is not installed
[debug] [ADB] App '/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk' is not installed
[debug] [ADB] Installing '/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 help'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 features'
[ADB] The application at '/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk' will not be cached, because the device under test has confirmed the support of streamed installs
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 install /Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk'
[ADB] The installation of 'app-dev-debug.apk' took 3266ms
[debug] [ADB] Install command stdout: Performing Streamed Install
[debug] [ADB] Success
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Performing shallow cleanup of automation leftovers
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] No obsolete sessions have been detected (socket hang up)
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell am force-stop io.appium.uiautomator2.server.test'
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] Starting UIAutomator2 server 5.6.2
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] Using UIAutomator2 server from '/Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v5.6.2.apk' and test from '/Users/sahilkhurana/.appium/node_modules/appium-flutter-driver/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk'
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] Waiting up to 30000ms for UiAutomator2 to be online...
[debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","emulator-5554","shell","am","instrument","-w","-e","disableAnalytics",true,"io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Matched '/status' to command name 'getStatus'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Proxying [GET /status] to [GET http://<IP_ADDRESS>:8203/status] with no body
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] socket hang up
[debug] [Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Matched '/status' to command name 'getStatus'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Proxying [GET /status] to [GET http://<IP_ADDRESS>:8203/status] with no body
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] socket hang up
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Matched '/status' to command name 'getStatus'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Proxying [GET /status] to [GET http://<IP_ADDRESS>:8203/status] with no body
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Got response with status 200: {"sessionId":"None","value":{"message":"UiAutomator2 Server is ready to accept commands","ready":true}}
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] The initialization of the instrumentation process took 2078ms
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Matched '/session' to command name 'createSession'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Proxying [POST /session] to [POST http://<IP_ADDRESS>:8203/session] with body: {"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android","automationName":"Flutter","deviceName":"emulator-5554","retryBackoffTime":5000,"app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk"},"platformName":"Android","automationName":"Flutter","deviceName":"emulator-5554","retryBackoffTime":5000,"app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk","deviceUDID":"emulator-5554","appPackage":"co.test.dev"}],"alwaysMatch":{}}}
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Got response with status 200: {"sessionId":"a7f41f13-8b68-4580-825e-dc9b80ad3d1f","value":{"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android","automationName":"Flutter","deviceName":"emulator-5554","retryBackoffTime":5000,"app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk"},"platformName":"Android","automationName":"Flutter","deviceName":"emulator-5554","retryBackoffTime":5000,"app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk","deviceUDID":"emulator-5554","appPackage":"co.test.dev"}],"alwaysMatch":{}},"sessionId":"a7f41f13-8b68-4580-825e-dc9b80ad3d1f"}}
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] Determined the downstream protocol as 'W3C'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Proxying [GET /appium/device/info] to [GET http://<IP_ADDRESS>:8203/session/a7f41f13-8b68-4580-825e-dc9b80ad3d1f/appium/device/info] with no body
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Got response with status 200: {"sessionId":"a7f41f13-8b68-4580-825e-dc9b80ad3d1f","value":{"androidId":"de9a91982dcda64d","apiVersion":"28","bluetooth":null,"brand":"Android","carrierName":"Android","displayDensity":440,"locale":"en_US","manufacturer":"unknown","model":"Android SDK built for arm64","networks":[{"capabilities":{"SSID":null,"linkDownBandwidthKbps":102400,"linkUpstreamBandwidthKbps":51200,"networkCapabilities":"NET_CAPABILITY_MMS,NET_CAPABILITY_SUPL,NET_CAPABILITY_DUN,NET_CAPABILITY_FOTA,NET_CAPABILITY_IMS,NET_CAPABILITY_CBS,NET_CAPABILITY_IA,NET_CAPABILITY_INTERNET,NET_CAPABILITY_NOT_RESTRICTED,NET_CAPABILITY_TRUSTED,NET_CAPABILITY_NOT_VPN,NET_CAPABILITY_VALIDATED,NET_CAPABILITY_NOT_ROAMING,NET_CAPABILITY_NOT_CONGESTED,NET_CAPABILITY_NOT_SUSPENDED","signalStrength":-2147483648,"transportTypes":"TRANSPORT_CELLULAR"},"detailedState":"CONNECTED","extraInfo":"epc.tmobile.com","isAvailable":true,"isConnected":true,"isFailover":false,"isRoaming":false,"state":"CONNECTED","subtype":13,"subtypeName":"LTE","type":0,"typeName":"MO...
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window'
[AndroidDriver] Screen already unlocked, doing nothing
[AndroidUiautomator2Driver@cee8 (97dc0b5c)] Starting 'co.test.dev/co.test.MainActivity and waiting for 'co.test.dev/co.test.MainActivity'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell am start -W -n co.test.dev/co.test.MainActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000'
[debug] [ADB] Waiting up to 20000ms for activity matching pkg: 'co.test.dev' and activity: 'co.test.MainActivity' to be focused
[debug] [ADB] Possible activities, to be checked: 'co.test.MainActivity', 'co.test.dev.co.test.MainActivity'
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'co.test.dev' and fully qualified activity name : 'co.test.MainActivity'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Proxying [GET /appium/device/pixel_ratio] to [GET http://<IP_ADDRESS>:8203/session/a7f41f13-8b68-4580-825e-dc9b80ad3d1f/appium/device/pixel_ratio] with no body
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Got response with status 200: {"sessionId":"a7f41f13-8b68-4580-825e-dc9b80ad3d1f","value":2.75}
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Matched '/appium/device/system_bars' to command name 'getSystemBars'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Proxying [GET /appium/device/system_bars] to [GET http://<IP_ADDRESS>:8203/session/a7f41f13-8b68-4580-825e-dc9b80ad3d1f/appium/device/system_bars] with no body
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Got response with status 200: {"sessionId":"a7f41f13-8b68-4580-825e-dc9b80ad3d1f","value":{"statusBar":66}}
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Matched '/window/current/size' to command name 'getWindowSize'
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Proxying [GET /window/current/size] to [GET http://<IP_ADDRESS>:8203/session/a7f41f13-8b68-4580-825e-dc9b80ad3d1f/window/current/size] with no body
[debug] [AndroidUiautomator2Driver@cee8 (97dc0b5c)] Got response with status 200: {"sessionId":"a7f41f13-8b68-4580-825e-dc9b80ad3d1f","value":{"height":2208,"width":1080}}
[FlutterDriver] Attempt #1
[ADB] Found 3 'build-tools' folders under '/Users/sahilkhurana/Library/Android/sdk' (newest first):
[ADB]     /Users/sahilkhurana/Library/Android/sdk/build-tools/33.0.0
[ADB]     /Users/sahilkhurana/Library/Android/sdk/build-tools/30.0.3
[ADB]     /Users/sahilkhurana/Library/Android/sdk/build-tools/28.0.3
[ADB] Using 'adb' from '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb'
[debug] [ADB] Running '/Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -P 5037 start-server'
[AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices
[debug] [ADB] Connected devices: [{"udid":"emulator-5554","state":"device"}]
[AndroidDriver] Using device: emulator-5554
[debug] [FlutterDriver] /Users/sahilkhurana/Library/Android/sdk/platform-tools/adb -s emulator-5554 forward tcp:43370 tcp:43370
[FlutterDriver] Connecting to Dart Observatory: ws://<IP_ADDRESS>:43370/a8fw31bFM8o=/ws
[FlutterDriver] Connecting to ws://<IP_ADDRESS>:43370/a8fw31bFM8o=/ws
[FlutterDriver] Listing all isolates: [{"type":"@Isolate","id":"isolates/944174503757411","name":"main","number":"944174503757411","isSystemIsolate":false},{"type":"@Isolate","id":"isolates/2911695030448175","name":"main","number":"2911695030448175","isSystemIsolate":false}]
[AppiumDriver@c272] New FlutterDriver session created successfully, session bdc99cad-0752-4130-9ea8-e82ff8f3a7a1 added to master session list
[debug] [AppiumDriver@c272] Event 'newSessionStarted' logged at<PHONE_NUMBER>625 (23:34:29 GMT+0530 (India Standard Time))
[debug] [FlutterDriver@de4e (bdc99cad)] Cached the protocol value 'W3C' for the new session bdc99cad-0752-4130-9ea8-e82ff8f3a7a1
[debug] [FlutterDriver@de4e (bdc99cad)] Responding to client with driver.createSession() result: {"capabilities":{"subcommand":"server","address":"<IP_ADDRESS>","port":4723,"allowCors":false,"allowInsecure":[],"basePath":"","callbackPort":4723,"debugLogSpacing":false,"denyInsecure":[],"keepAliveTimeout":600,"localTimezone":false,"loglevel":"debug","logNoColors":false,"logTimestamp":false,"longStacktrace":false,"noPermsCheck":false,"relaxedSecurityEnabled":false,"sessionOverride":false,"strictCaps":false,"useDrivers":[],"usePlugins":[],"driver":{"xcuitest":{"wdaLocalPort":8100}},"tmpDir":"/var/folders/4q/_7sb1vcj0cxfyj9xg0m88jdm0000gn/T","platformName":"Android","automationName":"Flutter","deviceName":"emulator-5554","retryBackoffTime":5000,"app":"/Users/sahilkhurana/build/app/outputs/flutter-apk/app-dev-debug.apk","fastReset":true,"skipUninstall":true}}
[HTTP] <-- POST /session 200 15819 ms - 850
[HTTP]
[HTTP] --> GET /session/bdc99cad-0752-4130-9ea8-e82ff8f3a7a1/element/eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiY291bnRlciIsImtleVZhbHVlVHlwZSI6IlN0cmluZyJ9/text
[HTTP] {}
[debug] [FlutterDriver@de4e (bdc99cad)] Calling AppiumDriver.getText() with args: ["eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiY291bnRlciIsImtleVZhbHVlVHlwZSI6IlN0cmluZyJ9","bdc99cad-0752-4130-9ea8-e82ff8f3a7a1"]
[debug] [FlutterDriver] Executing Flutter driver command sahil 'getText'
[debug] [FlutterDriver] >>> {"command":"get_text","finderType":"ByValueKey","keyValueString":"counter","keyValueType":"String"}
[debug] [FlutterDriver] <<< {"isError":false,"response":{"text":"0"},"type":"_extensionType","method":"ext.flutter.driver"} | previous command get_text
[debug] [FlutterDriver@de4e (bdc99cad)] Responding to client with driver.getText() result: "0"
[HTTP] <-- GET /session/bdc99cad-0752-4130-9ea8-e82ff8f3a7a1/element/eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiY291bnRlciIsImtleVZhbHVlVHlwZSI6IlN0cmluZyJ9/text 200 310 ms - 13
[HTTP]
[HTTP] --> POST /session/bdc99cad-0752-4130-9ea8-e82ff8f3a7a1/element/eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiaW5jcmVtZW50QnV0dG9uIiwia2V5VmFsdWVUeXBlIjoiU3RyaW5nIn0/click
[HTTP] {}
[debug] [FlutterDriver@de4e (bdc99cad)] Calling AppiumDriver.click() with args: ["eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiaW5jcmVtZW50QnV0dG9uIiwia2V5VmFsdWVUeXBlIjoiU3RyaW5nIn0","bdc99cad-0752-4130-9ea8-e82ff8f3a7a1"]
[debug] [FlutterDriver] Executing Flutter driver command 'click'
[debug] [FlutterDriver] Sahil
[debug] [FlutterDriver] >>> {"command":"tap","finderType":"ByValueKey","keyValueString":"incrementButton","keyValueType":"String"}
a[HTTP] <-- POST /session/bdc99cad-0752-4130-9ea8-e82ff8f3a7a1/element/eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiaW5jcmVtZW50QnV0dG9uIiwia2V5VmFsdWVUeXBlIjoiU3RyaW5nIn0/click - - ms - -
[HTTP]
[HTTP] --> POST /session/bdc99cad-0752-4130-9ea8-e82ff8f3a7a1/element/eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiaW5jcmVtZW50QnV0dG9uIiwia2V5VmFsdWVUeXBlIjoiU3RyaW5nIn0/click
[HTTP] {}
[debug] [FlutterDriver@de4e (bdc99cad)] Calling AppiumDriver.click() with args: ["eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlU3RyaW5nIjoiaW5jcmVtZW50QnV0dG9uIiwia2V5VmFsdWVUeXBlIjoiU3RyaW5nIn0","bdc99cad-0752-4130-9ea8-e82ff8f3a7a1"]
[debug] [FlutterDriver] Executing Flutter driver command 'click'
`

Resolved

How was it resolved?

How was it resolved?

Using appium v2 fixed the issue


*: extend basic testing chain documentation

Save some time for developers who are not familiar with RPC server unit-test structure.

Something wrong with the commit.

Maybe a commit length check had dropped with the new Goland.

Maybe a commit length check had been dropped with the new Goland update.

I don’t use Goland, it’s vim, and it was due to a copy-past. Will fix.


Remove extra quotes for strings in metadata formatter

Commit Message: Remove extra quotes for strings in metadata formatter
Additional Description: string values in metadata are handled the same way objects are, which adds escaped quotes around  them. This change removes these extra quotes (with a runtime flag "unquote_log_string_values").
Risk Level: Low - will change logging behavior for string metadata values, but flag protected.
Testing: Unit tests.
Docs Changes: N/A
Release Notes: access_log: remove extra quotes on metadata string values. This behavior can be temporarily reverted by setting envoy.reloadable_features.unquote_log_string_values to false.
Platform Specific Features:
[Optional Runtime guard:] unquote_log_string_values runtime flag (defaults to new behavior)
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

/assignee htuch

/assign htuch

/assign yanavlasov

LGTM, the format complains about the ordering of the runtime keys in the array. Good to go after it is fixed.
/wait

LGTM, the format complains about the ordering of the runtime keys in the array. Good to go after it is fixed.
/wait

Done.

It looks like //test/integration:proxy_proto_integration_test uses access logging in tests and expects double quotes. I think we can just fix the test to use single quotes, since it is the new expectation.

We may need to wait for windows build to be fixed and merge main.

Windows build was fixed. Please merge main.

Windows build was fixed. Please merge main.

Done.


Support for custom lines

Hi! Is it possible to add a custom line to the trading view chart? I.e. for an order

Hmmm not sure, does not seem to be documented by the TradingView team

After scrolling through https://s3.tradingview.com/tv.js I don't think it's possible doing programmaticly

You could do it with this though -> https://github.com/tradingview/lightweight-charts


Update link for Threads of Destiny

Project name: Threads of Destiny
Project URL: https://wraithdrof.itch.io/threads-of-destiny

Why it's awesome
I made this project, and it's actually out on itch.io so I was just updating the link! I've gotten a couple of requests to view it as I turned off sharing on the WIP google doc.

Looks good, thanks!


Support for authenticated JDBC driver URIs

Authenticated JDBC Driver URI
Currently, we are unable to set JDBC_DRIVER_URI to a web server that requires authentication.  Authenticated JDBC Driver URI support will be very helpful for easily launching Pega web containers within unsecured networks and when driver downloads requires authentication.
Describe the solution you'd like
It would be great if the following variables where exposed so that JDBC_DRIVER_URI can reside on an authenticated server.

JDBC_DRIVER_URI_USERNAME
JDBC_DRIVER_URI_PASSWORD

Describe alternatives you've considered
It would be added complexity to construct our own image with the drivers baked-in, hence, the first choice would be support for authenticated JDBC driver URIs.

Another thing to note is that this capability used to exist before the images were fully moved over to github in this repo.  For example in 8.1.0
I feel like this was a feature that was not appropriately ported over

This will also block adoption of EPIC-59878 Ability to launch multiple Platform dockerized tomcats since many of our at-home developers use bin.pega.io for their downloads which is a secured artifactory

Interesting that this was somehow missed or wasn't moved over. Do we know the decision behind that? Wondering if there is something we may be missing here...

Actually, looking at various versions, I think by time 8.2 rolled out it was already gone, I don't remember the timings on when pega ready was created, so maybe it was gone before then.
Unfortunately the documentation in the platform repo readme remained stubbornly incorrect

Good times ;)

@cdancy Can we get an ETA on this enhancement, its actually pretty annoying especially with everyone working from home.  If we want to download the driver from the authenticated bin.pega.io artifactory for speed

Downloading drivers is not a real docker way of doing things. I recommend to create your own layer on top of the base image where you create your owns specific needs.
Downloading drivers means that functionality can change between runs.

To me that seems like an odd position to take for this specific image given that it exposes a JDBC_DRIVER_URI env var and documents it as how to provide the driver.
If what you are saying is true the base image should not expose a URI or document it, but isnead just come pre-packaged with a driver -or- simly not work at all until its extended

It's not that odd I think. This is the 'ready' image.
from the readme: "This ready Docker image represents one component of a full image you can use to run a Pega node. It is built on top of Tomcat but does not contain the Pega .war file (hence it is ready for the .war file...."
So its ready for war and jdbc?

This is fixed by #160


No tooltips for filtered fluids in 512k Fluid Storage Block

Issue description:
Similar to https://github.com/raoulvdberge/refinedstorage/issues/1209 but for Fluid Storage Block instead of Disk Drive in fluid mode.
What happens:
No tooltips for filtered fluids in 512k Fluid Storage Block

Fluid in screenshot is Biodiesel from IE, but I guess all fluids will be missing the tooltip...
What you expected to happen:
Tooltips  for filtered fluids in 512k Fluid Storage Block
Steps to reproduce:

Place a  512k Fluid Storage Block, add a fluid filter, hover over it. No tooltip.

...
Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: <IP_ADDRESS>7
Refined Storage:refinedstorage-1.2.25

Does this issue occur on a server? [yes/no]
Not tested.
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

This happens to every fluid slot. It's already fixed for every fluid slot.

I thought so but reported anyway just in case. Thank you.


SNI not set in client-hello when "test" is used as hostname

I can see the hostname set when using string other that test* in - SSL_set_tlsext_host_name(ssl, ). But, when I use SSL_set_tlsext_host_name(ssl, "test") the client hello doesn't contain a SNI extension and also results in a successful handshake. Where as my expectation is that "test" should have been sent in SNI extension and resulting in Handshake failure due to wrong hostname.( am using X509_VERIFY_PARAM_set_hostflags and X509_VERIFY_PARAM_set1_host) to force hostname checking.
code:-
void enable_hostname_verification(SSL *ssl, const char *domain)
{
        X509_VERIFY_PARAM *param = NULL;
        int ret = 0;

        param = SSL_get0_param(ssl);

        /* Enable automatic hostname checks */
        X509_VERIFY_PARAM_set_hostflags(param, X509_CHECK_FLAG_NO_PARTIAL_WILDCARDS);
        if (!X509_VERIFY_PARAM_set1_host(param, domain, sizeof(domain) - 1)) {
                // handle error
                return;
        }

        ret = SSL_set_tlsext_host_name(ssl, domain);
        if (ret != 1)
        {
            printf("### unable to set hostname to: %s ###", domain);
        } else {
            printf("### set SNI  to: %s ###", domain);
        }
        /* Enable peer verification, (with a non-null callback if desired) */
        SSL_set_verify(ssl, SSL_VERIFY_PEER, NULL);
}

Issue occurs when I call the above function as enable_hostname_verification(ss, "test").

Hmmm. I don't see this behaviour here. Using OpenSSL 3.0.1 if I use the "-servername" option to s_client then that causes s_client to call SSL_set_tlsext_host_name with the supplied parameter:
        if (servername != NULL && !SSL_set_tlsext_host_name(con, servername)) {
            BIO_printf(bio_err, "Unable to set TLS servername extension.\n");
            ERR_print_errors(bio_err);
            goto end;
        }

So:
$ openssl s_client -servername test -trace
CONNECTED(00000003)
Sent Record
Header:
  Version = TLS 1.0 (0x301)
  Content Type = Handshake (22)
  Length = 305
    ClientHello, Length=301
...sniip...
      extensions, length = 166
        extension_type=server_name(0), length=9
          0000 - 00 07 00 00 04 74 65 73-74                     .....test

Sorry, my bad. Am able to see the SNI set properly. However, I see  a successful handshake while sending "test" as a SNI even if the client receives a server-certificate with "comman-name" set to "TLS-Unit-test"

the client receives a server-certificate with "comman-name" set to "TLS-Unit-test"

The setting of SNI does not affect the host that the client checks in the certificate. This is set via X509_VERIFY_PARAM_set1_host and must be accompanied by a call to SSL_set_verify with SSL_VERIFY_PEER. In your sample code you do seem to set that. This line looks wrong:
         if (!X509_VERIFY_PARAM_set1_host(param, domain, sizeof(domain) - 1)) {

sizeof(domain) here will be the size of the ptr type, not the length of the string. But this probably doesn't explain the behaviour you are seeing.

Marking as inactive, to be closed at the end of the 3.4 dev cycle, barring further input


adding support for statistical facets

added support for terms_stats

Hi Peter, thanks!, great contribution, merged & pushed!

Hi Karmi, You are most welcome, thank you for the great gem saved me tons of time.


vimPlugins.lze: init at 0.1.1

I made this, and I almost completely deleted it because I was fully on board with lz-n again. However, I have been using it and lz-n simultaneosly and trying them out.
I wish to publish lze after all. I like it a lot.
It works completely differently from lz-n and has a different handler api, but has a similar plugin spec.
It has been rewritten significantly AGAIN since I last went to upload it.
It has a much more respectful readme this time around too, as now I have more legitimately good things to say about both options.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 339387 run on x86_64-linux 1

7 packages built:

lua51Packages.lze
luaPackages.lze (lua52Packages.lze)
lua53Packages.lze
lua54Packages.lze
luajitPackages.lze
vimPlugins.lze
vimPluginsUpdater

Ah, yeah ty. Still new here. Kinda thought that other people were supposed to be the ones to do stuff to make sure it worked on THEIR hardware. Some stuff still to learn about contributing :)

I also forgot about the --post option XD

Result of nixpkgs-review pr 339387 run on x86_64-linux 1

7 packages built:

lua51Packages.lze
luaPackages.lze (lua52Packages.lze)
lua53Packages.lze
lua54Packages.lze
luajitPackages.lze
vimPlugins.lze
vimPluginsUpdater

Ah, yeah ty. Still new here. Kinda thought that other people were supposed to be the ones to run it to make sure it worked on THEIR hardware. Some stuff still to learn about contributing :)

(Still new here as well) I suppose simple packages, that don't use any specific hardware (cuda, drivers, etc), don't need to be tested by external contributor as Nix is pure and if something works on one system, it will work everywhere

Yeah Id be pretty surprised if this didnt work anywhere that you could run nvim XD I dont even refer to any filepaths anywhere XD

I also forgot about the --post option XD My PAT doesnt have permissions to post :( Guess I have to change that

Btw, you don't have to use --post. For example, I am too lazy to configure my GitHub key, so I just do cat report.md in a shell created by nixpkgs-review

Thats fair. It was easy enough tho :)

Result of nixpkgs-review pr 339387 run on aarch64-darwin 1

7 packages built:

lua51Packages.lze
lua52Packages.lze
lua53Packages.lze
lua54Packages.lze
luajitPackages.lze
vimPlugins.lze
vimPluginsUpdater

Result of nixpkgs-review pr 339387 run on x86_64-darwin 1

7 packages built:

lua51Packages.lze
lua52Packages.lze
lua53Packages.lze
lua54Packages.lze
luajitPackages.lze
vimPlugins.lze
vimPluginsUpdater

Result of nixpkgs-review pr 339387 run on x86_64-linux 1

7 packages built:

lua51Packages.lze
lua52Packages.lze
lua53Packages.lze
lua54Packages.lze
luajitPackages.lze
vimPlugins.lze
vimPluginsUpdater

Result of nixpkgs-review pr 339387 run on aarch64-linux 1

7 packages built:

lua51Packages.lze
lua52Packages.lze
lua53Packages.lze
lua54Packages.lze
luajitPackages.lze
vimPlugins.lze
vimPluginsUpdater


[KEP] 0007-performance-test

status: provisional
Kubernetes Ingress Controller (KIC) Performance Testing

Summary
Motivation

Goals
Non-Goals

Proposal

User Stories

Story 1
Story 2

Summary
Motivation
Goals
Non Goals
Proposal

revert to draft since is just a holder for document the idea.

should we close this now that https://github.com/Kong/kubernetes-ingress-controller/pull/1488 exists? It seems like we're not going to write a KEP anymore, instead we have the tests and some follow up issues which will suffice?

should we close this now that #1488 exists? It seems like we're not going to write a KEP anymore, instead we have the tests and some follow up issues which will suffice?

We did discussion, documentation and scope on https://github.com/Kong/kubernetes-ingress-controller/issues/1197. https://github.com/Kong/kubernetes-ingress-controller/pull/1488 is follow up concrete implementation.

The actual KEP work is documented in #1197


extending readme

Hey @TGlide, really cool project!
I thought you might like a more detailed ReadMe - let me know if it's useful!
Created it with https://www.hello-cluster.com/

Thanks for this @goudete, I was thinking of adding this as well.
I will suggest most importantly adding the expected props the Editor component can accept similar to what novel.sh has: https://github.com/steven-tey/novel

I will also add that the installation guide isn't that important as everyone should know how to clone and install however since this is a library there will be a rare case that anyone is coming to the README to see how to setup the repo locally, except contributors. Instead I think people would want to see what they can do with the library (this was the first thing I looked for when I was looking for a svelte based notion editor.)
In that case I will suggest we follow the same approach as that of the original novel repo 👍


Feature request: API Port should scan installed nuget packages

It'd be nice if API Port could include in a report what nugget packages satisfy portability, eventually with an update if available.
e.g. I want to check portability to .NET Standard 2.0, so it'd scan installed nuget packages and check if all of them support .NET Standard 2.0.
Thanks!

Thanks for suggesting this feature! It would definitely be helpful to end users.

Is this now supposed to be working? Scott Hunter's .NET Conf 2017 Keynote demo (7:30) suggests it is as he installed a nuget package not built for .NET Standard 2.0 and then ran the portability analyser to verify that the project was compliant with .Net Standard 2.0.

Closing as API Port was deprecated in favor of binary analysis in .NET Upgrade Assistant.


502 errors

`
504 Gateway Time-out
awselb/2.0
`
8.00 AM EST
This follows Yesterdays issues  but the additional info seems to be "awselb/2.0"

Marking as closed as they seem to have dissipated...Second time in 2 days

Just to clarify: this exact issue happens when redirected to hydra.arduino.cc and the SSO is down, so it's not actually a forum issue (you can check this by trying to log in on the store or the homepage).
We are currently investigating on those (diminishing) random SSO outages, but currently they should be fixed by themselves in ~1-2 minutes.
Still, thank you for noticing us!


Vulnerability roundup 61: openjpeg-2.3.0: 1 advisory

search, files

[ ] CVE-2019-6988 (nixos-18.09, nixos-unstable)

Scanned versions: nixos-18.09: 8008d0bbc69; nixos-unstable: 2d6f84c1090. May contain false positives.

I'm not sure if the fix isn't already in nixpkgs. Please see #51100 and #49788 for discussion. Can someone verify that this is a false alert?

Linked issue https://github.com/uclouvain/openjpeg/issues/1178 was reopened, the original fix was insufficient. Unless they allocate a new CVE, I think this means this issue should stay open :/

closing in favor of https://github.com/NixOS/nixpkgs/issues/57180


wrong extend auth params variable

https://github.com/desmondmorris/node-twitter/commit/6833c8a61e92611b3aec671a61a229ba15d2985d
lib/twitter.js
line 64
consumer_secret: this.options.consumer_key,
should be actually
consumer_secret: this.options.consumer_secret,

Yeah!
This fix will avoid  "Could not authenticate you." error.
Thank you @JSReligion

Fixed!


Add alternative Array#sample sig when no arg0 is passed in

Motivation
When no argument is passed in, the result is just T.nilable(Elem), which simplifies not having to deal with the T.any
Test plan
See included automated tests.

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

This doesn't work, because multiple sigs for the same method in an rbi can't be added when there are keyword arguments


Convert private API functions to public utility functions

This would increase testability of each part.

Also group similar task into partial types. It will become a mess otherwise…


[Feature]: Display two curves in one graph?

Description
#!/usr/bin/env python
"""main."""
import wandb
from torch.utils.tensorboard.writer import SummaryWriter

model = image_models["mbt2018"](pretrained=True, quality=6)

log_dir = '/output/logs'

name = '5'
wandb.init(project="my-test-project-2", dir=log_dir, name=name, id=name,
           config={"learning_rate": 0.001, "epochs": 100, "batch_size": 128},
           sync_tensorboard=True)

writer = SummaryWriter(log_dir=log_dir)

writer.add_scalars('metrics/loss', {'train': 20, 'val': 100}, 0)
writer.add_scalars('metrics/loss', {'train': 10, 'val':  50}, 1)

# Optional
wandb.finish()

Can it display curves of same tag to one graph?
This is wandb:

This is tensorboard:

Suggested Solution
/
Alternatives
No response
Additional Context
No response

Hi @Freed-Wu,
Yup, this is already possible. You can read about it in our docs here : https://docs.wandb.ai/ref/app/features/panels/line-plot#compare-two-metrics-on-one-chart

Can it support tensorboard's add_scalars?

Hey @Freed-Wu,
Yes, add_scalar from tensorboard is supported.

I means Can it display multi curves in one graph like add_scalars.

That is how can wandb display similar result with tensorboard? https://github.com/wandb/wandb/issues/4449#issue-1436190950

Hey @Freed-Wu,
As I mentioned before, multiple curves are already supported. You will have to do some manual work to get these exactly the way you need them however. Here is a video to aid you with how to do this for any 2 plots:
https://user-images.githubusercontent.com/93002515/201744085-43405125-a054-41ff-886f-9793dfe4fb55.mov

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

Is it possible to do this automatically? Manually fiddling isn't ideal when many metrics are logged. It also liters workspace and requires deleting 'standalone', ungroupped graphs. It would be nice if logging a dict (with maybe additional flag group to not break things) would group things automatically as OP showed.

I agree that this should be done automatically, since it's impractical and error prone to do this for every single figure. Especially when dealing with more than two curves. Suggested solution: copy tensorboard's functionality.

I would also agree that it would be nice to do this automatically.


Feature Request - Column, not writeable - but readable

I would like to have a feature, so that a column in a database is read-only - it will never considered during writing, but it will always be considered during read operations.
Why ?
serial columns or data column, where the data is filled by the relational database.

I could do this by myself, but I need to define this behaviour and the rdbColumnMapping is the correct place for that. I already have written a subclass with additional column information - index creation stuff, nullable option and serial options - so it seems, that this class is a good candiate for getting bigger and bigger over time ...

I can look into that as I have time. So the column would be marked read-only in GCFP, not in Postgres itself correct? Attempting to write a column marked read-only would raise an exception.

Ok, consider a column id like
CREATE TABLE table_name(
id SERIAL,
name text,
);
You want to have the read the values, but you are not allowed to write that column.

You want to have the read the values, but you are not allowed to write that column.
Not writing the column would apply only to UPDATE operations right? INSERT and DELETE would still be allowed to add/remove rows when the table contains a read-only column?

I am thinking of implementing this feature by excluding columns marked read-only from update streams (#openUpdateCursorOn: tupleClass columnMapping: columnMap keyMapping: keyMap tableName: tableName). Would this meet your needs for this feature?

Add ability to mark GsPostgresColumnMapEntry objects as read-only. When this is done, updates will silently exclude any columns marked read-only. Inserts and deletes work as normal and are not affected. See class WidgetWithReadOnlyStrings and PostgresTestCase>>test_insertUpdateDeleteOnReadOnly for example usage.


Always show message when LSP exits early

Problem
Sorbet in LSP mode exits early for a handful of reasons. Here are some:
https://github.com/sorbet/sorbet/blob/75d798fc5cab54c595c321593d6fa95c0b1bf0a5/main/lsp/LSPConfiguration.cc#L20-L21
https://github.com/sorbet/sorbet/blob/75d798fc5cab54c595c321593d6fa95c0b1bf0a5/main/lsp/watchman/WatchmanProcess.cc#L95-L99
https://github.com/sorbet/sorbet/blob/75d798fc5cab54c595c321593d6fa95c0b1bf0a5/main/lsp/protocol.cc#L121-L123
In each of these cases, the Sorbet process exits with a non-zero exit code after logging something to the debug log file and to stdout.
In the case where Sorbet has been started by a language client (like VS Code or Vim), stdout is never shown to the user, and no mention of the debug log file is made (or even if it exists).
Proposed solution
We should use the LSP spec's window/showMessage notification to show an error message to the user if we ever exit early from LSP. Here is the spec:
→ window/showMessage
Three easy cases are the errors above. Those are probably the most important to fix, because those are the most likely to be encountered by people setting up Sorbet LSP for the first time.

Another option would be to use window/showMessageRequest, which would require a prompt from the user to say "Ok" or take some other action. I'm not sure the UI that most language clients use to implement either of these, so it might be worth playing around with both to see what the experience is.


Self hosted gateway | Intermediate certs are not added to CA store of container

Known issue that intermediate certs are not added to CA store of container this can can be mitigated here by installing it manually as per the below steps:

Convert individual .cer certificates in the certificate chain to PFX (blank password). This can be done using open ssl. Here is a sample command:
openssl pkcs12 -export -nokeys -in certificate.cer -out pkcs12.pfx

Add each of the PFX certs in the chain to APIM. This can be done from Azure Portal --> Certificates --> Certificates tab

Associate each of the certificates added in step 2 with self hosted gateway. This needs to be done using REST API. See https://docs.microsoft.com/en-us/rest/api/apimanagement/current-ga/gateway-certificate-authority/create-or-update . Note: isTrusted should be false for all intermediate certs and true for the root cert.

Assuming customer is using self-hosted gateway v2, use the following setting to enable CA certs in the Kubernetes deployment file:
certificates.local.ca.enabled: "true"

Deploy self-hosted gateway container and test.

Important Note: The permissions to directory “/.dotnet/corefx/cryptography/x509stores/root” is required.

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

ID: e318d1df-e46f-abf9-ec2a-f0d0d7685f03
Version Independent ID: 7c1791cb-6acd-46bc-0924-3dcb483b4c5a
Content: Configure a custom domain name for your self-hosted Azure API Management gateway
Content Source: articles/api-management/api-management-howto-configure-custom-domain-gateway.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

@FadyFT
Thanks for your feedback! We will investigate and update as appropriate.

@FadyFT - Thanks for providing the details. I've created a doc workitem for our backlog with details to address this in an upcoming doc sprint. According to our usual process, I'll now proceed to close this issue. Thanks!
#please-close


adding rofi completion

This is a simple copy of the dmenu block for rofi.
It will call rofi --dmenu to choose which entry to display

First time in go. Hope it helps

Yes. I saw the duplication too. I will merge this and then try to work on making it DRY. Ok?

ok, thanks for your help !

I'm not going to merge this as it it. We're currently thinking about making the approach more general, so it really doesn't matter if one uses dmenu or rofi, or whatever.


Building Raylib from the source produces errors

Issue description
compiling raylib from the master branch using the following command:
mingw32-make PLATFORM=PLATFORM_DESKTOP
produces these errors:
gcc -c rcore.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=c99 -O1 -Werror=implicit-function-declaration -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
gcc -c rshapes.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=c99 -O1 -Werror=implicit-function-declaration -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
gcc -c rtextures.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=c99 -O1 -Werror=implicit-function-declaration -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
gcc -c rtext.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=c99 -O1 -Werror=implicit-function-declaration -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
gcc -c utils.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=c99 -O1 -Werror=implicit-function-declaration -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
gcc  -c rglfw.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=c99 -O1 -Werror=implicit-function-declaration -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
In file included from rglfw.c:73:0:
external/glfw/src/win32_window.c: In function 'updateCursorImage':
external/glfw/src/win32_window.c:247:41: warning: passing argument 2 of 'LoadCursorW' from incompatible pointer type [-Wincompatible-pointer-types]
             SetCursor(LoadCursorW(NULL, IDC_ARROW));
                                         ^~~~~~~~~
In file included from c:\mingw\include\windows.h:48:0,
                 from external/glfw/src/win32_platform.h:68,
                 from external/glfw/src/platform.h:31,
                 from external/glfw/src/internal.h:331,
                 from external/glfw/src/init.c:30,
                 from rglfw.c:61:
c:\mingw\include\winuser.h:3999:27: note: expected 'LPCWSTR {aka const short unsigned int *}' but argument is of type 'CHAR * {aka char *}'
 WINUSERAPI HCURSOR WINAPI LoadCursorW (HINSTANCE, LPCWSTR);
                           ^~~~~~~~~~~
In file included from rglfw.c:73:0:
external/glfw/src/win32_window.c: In function 'createNativeWindow':
external/glfw/src/win32_window.c:1277:46: warning: passing argument 2 of 'LoadCursorW' from incompatible pointer type [-Wincompatible-pointer-types]
         wc.hCursor       = LoadCursorW(NULL, IDC_ARROW);
                                              ^~~~~~~~~
In file included from c:\mingw\include\windows.h:48:0,
                 from external/glfw/src/win32_platform.h:68,
                 from external/glfw/src/platform.h:31,
                 from external/glfw/src/internal.h:331,
                 from external/glfw/src/init.c:30,
                 from rglfw.c:61:
c:\mingw\include\winuser.h:3999:27: note: expected 'LPCWSTR {aka const short unsigned int *}' but argument is of type 'CHAR * {aka char *}'
 WINUSERAPI HCURSOR WINAPI LoadCursorW (HINSTANCE, LPCWSTR);
                           ^~~~~~~~~~~
In file included from rglfw.c:73:0:
external/glfw/src/win32_window.c:1291:35: warning: passing argument 2 of 'LoadImageW' from incompatible pointer type [-Wincompatible-pointer-types]
                                   IDI_APPLICATION, IMAGE_ICON,
                                   ^~~~~~~~~~~~~~~
In file included from c:\mingw\include\windows.h:48:0,
                 from external/glfw/src/win32_platform.h:68,
                 from external/glfw/src/platform.h:31,
                 from external/glfw/src/internal.h:331,
                 from external/glfw/src/init.c:30,
                 from rglfw.c:61:
c:\mingw\include\winuser.h:4011:26: note: expected 'LPCWSTR {aka const short unsigned int *}' but argument is of type 'CHAR * {aka char *}'
 WINUSERAPI HANDLE WINAPI LoadImageW (HINSTANCE, LPCWSTR, UINT, int, int, UINT);
                          ^~~~~~~~~~
gcc -c rmodels.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=c99 -O1 -Werror=implicit-function-declaration -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
In file included from rmodels.c:95:0:
external/m3d.h: In function 'm3d_load':
external/m3d.h:3769:53: warning: 'mi' may be used uninitialized in this function [-Wmaybe-uninitialized]
                         model->voxel[i].data[j++] = (M3D_VOXEL)mi;
                                                     ^~~~~~~~~~~~~
gcc -c raudio.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=c99 -O1 -Werror=implicit-function-declaration -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
In file included from c:\mingw\include\windows.h:48:0,
                 from raudio.c:136:
c:\mingw\include\winuser.h:3519:25: error: conflicting types for 'CloseWindow'
 WINUSERAPI BOOL  WINAPI CloseWindow (HWND);
                         ^~~~~~~~~~~
In file included from raudio.c:75:0:
raylib.h:959:12: note: previous declaration of 'CloseWindow' was here
 RLAPI void CloseWindow(void);                                     // Close window and unload OpenGL context
            ^~~~~~~~~~~
In file included from c:\mingw\include\windows.h:48:0,
                 from raudio.c:136:
c:\mingw\include\winuser.h:4280:23: error: conflicting types for 'ShowCursor'
 WINUSERAPI int WINAPI ShowCursor (BOOL);
                       ^~~~~~~~~~
In file included from raudio.c:75:0:
raylib.h:1008:12: note: previous declaration of 'ShowCursor' was here
 RLAPI void ShowCursor(void);                                      // Shows cursor
            ^~~~~~~~~~
Makefile:704: recipe for target 'raudio.o' failed
mingw32-make: *** [raudio.o] Error 1

Environment
Windows 10 LTSC , Intel Pentium G2020 , GNU Make 3.82.90 (Built for i686-pc-mingw32)

nvm


add production_telemetry to the API

Hi Daniel,
I liked your implementation for Enphase V4 API
However I wanted a different endpoint to be queried.
(/api/v4/systems/{system_id}/telemetry/production_micro )
I added that to your code. Maybe you or somebody else also has in interest in this.
Jacco

@jaccol Did you try running this endpoint on the free WATT plan? I kinda remember trying this but it giving me 401s.

@jaccol So I tried your python code and it worked. I must have something wrong in Postman. So I'll fix that, confirm that works so I can update the Postman library and merge this change.

I'm on the free plan and it works for me.
Looking at the different plans (https://developer-v4.enphase.com/developer-plans )
it should work, because this is 'site level production monitoring'. The more detailed version ('device level production monitoring') is apparently only for the KiloWATT plan.


Re-enable processor

Still in a state of
performance-service-processor-production-696888774c-pz2zj         0/1     CrashLoopBackOff   13 (117s ago)   43m

cc @tsunyoku


Allow other server

Allow other server type as Spigot or Purpur.
Technical details
Spigot
No pre-packaged JAR
Purpur
An API is available: https://api.purpurmc.org/v2/purpur
Endpoints:

to get all available version: https://api.purpurmc.org/v2/purpur
to get all available build: https://api.purpurmc.org/v2/purpur/:version
to get build details: https://api.purpurmc.org/v2/purpur/:version/:build
to download: https://api.purpurmc.org/v2/purpur/:version/:build/download

Sponge
Based on nexus
Glowstone
To check

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.


Cleanup deployments

Context
Cleanup mostly routes and oci image handling in deployments to reduce size of nix/cardano-services/deployments/default.nix and make it easier to read
Testing:
No deployments diff

Yes, replicas scale down was intentional, there is no need for us to have 3 replicas there


Noise improvement using Olstein-Uhlenberg processes

In order to generate better stochastic environments, we could develop noise generation using Olstein-Uhlenberg processes

These are some results applying Olstein-Uhlenberg processes. Red line describe drybulb in epw with noise and blue line the same but in original epw file:
sigma=1.0 mu=0.0 tau=0.001

sigma=5.0 mu=0.0 tau=0.01

sigma=10.0 mu=0.0 tau=0.1


Missing space

I'm assuming, that searchExistingType is always defined.
Fixes #1

Sorry I'm late here. Let's add a line to https://github.com/dblock/create-a-github-issue/blob/main/CHANGELOG.md even though this is trivial so it's easier to track what changed between releases?

It is indeed trivial, but of you insist :)

FYI this was released in v3.1.0.


add --uri-substitution option

rebased and updated

Ok tested with https://github.com/dart-lang/bazel/pull/35 on the codelab app, everything works!


Cmake Integrated the glog dynamic library built by bazel, and the operation crashes

When LOG (INFO) is called for printing each time, the log can be output normally, but the interface will crash after running. After LOG (INFO) is annotated, the crash will be eliminated；
storehouse：0x0000000000007080 in ?? ()

It is not clear what the problem is. Please provide an example that demonstrates the issue.

Closing due to lack of response.


fix: remove uses of panel_main() and panel_sidebar()

Fixes https://github.com/posit-dev/py-shiny/issues/1588

Thank you!


Updated CodemonListen.py and .gitignore

__pycache__ is resolved as well as removed import from isModified.

Thanks ! @yashshah14093


Remove clone via Dockerfile and copy from local

Solve issue #15

Changed docker-runner.sh to create docker-image/tmp/ folder and copy all chatbots and connecting_worlds to it.
Changed Dockerfile to copy docker-image/tmp/ into chatbot-conversations/
Changed install-chatbot.sh to build chatbots from local files

@neomatrix369 I've pushed changes to solve issue #15 .
I thought might be interesting to give option to not use local files, but changed my mind in the middle...
Please feel free to add comments over the implementation.

Good decision: removal of https://github.com/neomatrix369/chatbot-conversations/pull/23/commits/cbdb2bbdfa2ac11b2e03184f5b29804304d54dc9


Android camera records video with wrong orientation

What package does this bug report belong to?
camera
What target platforms are you seeing this bug on?
Android
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
  camera:
    dependency: "direct main"
    description:
      path: ".."
      relative: true
    source: path
    version: "0.11.0+2"
  camera_android_camerax:
    dependency: transitive
    description:
      name: camera_android_camerax
      sha256: "59a01443c280cf969449f4b72db9396e80e5a9e8f07a2500a042906a157ce894"
      url: "https://pub.dev"
    source: hosted
    version: "0.6.9+2"
  camera_avfoundation:
    dependency: transitive
    description:
      name: camera_avfoundation
      sha256: "7c28969a975a7eb2349bc2cb2dfe3ad218a33dba9968ecfb181ce08c87486655"
      url: "https://pub.dev"
    source: hosted
    version: "0.9.17+3"
  camera_platform_interface:
    dependency: transitive
    description:
      name: camera_platform_interface
      sha256: b3ede1f171532e0d83111fe0980b46d17f1aa9788a07a2fbed07366bbdbb9061
      url: "https://pub.dev"
    source: hosted
    version: "2.8.0"
  camera_web:
    dependency: "direct overridden"
    description:
      path: "../../camera_web"
      relative: true
    source: path
    version: "0.3.5"

Steps to reproduce

Run current camera plugin example app (tried Galaxy S20 and Emulator of Pixel 7 Pro API 35)
Select a camera
Take video
See video showing sideways in the thumbnail.

Reverting to camera_android_camerax 0.6.8+3 did not fix. I'm not sure at what point this stopped working.
Expected results
Video should be recorded as shown in the CameraPreview widget without any rotation flags for easy playback on any platform. Video shows correctly in preview widget.
Actual results
Video is recorded with a rotation of 90 degrees CCW (left). Analyzing the video file with ffprobe, it appears to have a metadata flag of displaymatrix set to rotation of -90.00 degrees.
Code sample
Code sample
[Paste your code here]

Screenshots or Videos

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.24.3, on Microsoft Windows [Version 10.0.22621.4169], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/to/windows-android-setup for more details.
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2019 16.10.0)
[√] Android Studio (version 2024.2)
[√] VS Code (version 1.94.0)
[√] Connected device (5 available)
[√] Network resources

! Doctor found issues in 1 category.

Hi @jt274
camera_android_camerax example is using video_player to play the output video and this is a known issue at https://github.com/flutter/flutter/issues/154696. Marking this as a duplicate of that issue, so please follow it for updates.

@huycozy I believe this is a separate issue. Yes, the video_player package is not properly rotating videos with displaymatrix rotation metadata flags. However, the camera package should be recording videos according to their original orientation, not a default orientation and adding a flag.
Current state

Put phone in portrait up mode and record video
Video records at 1920x1080 resolution (landscape left) with displaymatrix flag of -90 rotation
Video player on any platform must rotate video according to metadata flag (+90 rotation) to display properly. Players/platforms other than video_player may have the same rotation issue.

Expected state

Put phone in portrait mode and record video
Video records at 1080x1920 resolution (portrait up) with no displaymatrix flag.
Video plays back on all platforms with no required rotation by a video player.

Your steps above and sample code match what was reported at https://github.com/flutter/flutter/issues/154696 (see demo video at https://github.com/flutter/flutter/issues/154696#issue-2509236120). I also used camerax example to verify that issue.
To confirm this, can you try using video_player_android: 2.7.1 (without Impeller integration)?

What I'm saying is if I download the recorded video from the device, I can see that a video recorded in portrait mode was encoded in a landscape orientation with a metadata flag to tell the player to rotate the video back to portrait mode during playback. This will cause issues for players that do not properly interpret this flag (including video_player).
The proposed fix is to encode the portrait video in portrait (not landscape), without a rotation flag set. This would ensure proper playback on all platforms and players. The video would record in 1080 width x 1920 height, instead of 1920 width x 1080 height and a rotation flag.
I confirmed this flag and resolution by downloading the recorded file to a PC and analyzing it with ffprobe.

Your steps above and sample code match what was reported at #154696 (see demo video at #154696 (comment)). I also used camerax example to verify that issue.
To confirm this, can you try using video_player_android: 2.7.1 (without Impeller integration)? (see #154696 (comment))

I pinned video_player_android: 2.7.1 and can confirm:

The video is still recorded with the wrong orientation, and includes the displaymatrix rotation flag.
The video player now correctly plays the video by rotating it during playback.

So it fixes the PLAYBACK error, but not the RECORDING issue.

Thanks for your update.
I used ffprobe with the output video from camerax example here and see displaymatrix value is rotation of -90.00 degrees:
➜  Desktop ffprobe REC235196964642373781.mp4
ffprobe version 7.0.1 Copyright (c) 2007-2024 the FFmpeg developers
  built with Apple clang version 15.0.0 (clang-15<IP_ADDRESS>)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/7.0.1 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags='-Wl,-ld_classic' --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libaribb24 --enable-libbluray --enable-libdav1d --enable-libharfbuzz --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox --enable-audiotoolbox
  libavutil      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'REC235196964642373781.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2024-10-09T11:51:07.000000Z
    com.android.version: 14
  Duration: 00:00:04.39, start: 0.000000, bitrate: 6114 kb/s
  Stream #0:0[0x1](eng): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc, bt709, progressive), 720x480, 6108 kb/s, 29.86 fps, 30 tbr, 90k tbn (default)
      Metadata:
        creation_time   : 2024-10-09T11:51:07.000000Z
        handler_name    : VideoHandle
        vendor_id       : [0][0][0][0]
      Side data:
        displaymatrix: rotation of -90.00 degrees

However, when I play video on macOS (with VLC app), I see its orientation keeps portrait as expected:

camera_android_camerax example output video
https://github.com/user-attachments/assets/955fc6ce-1b57-434f-be10-7e1bb8d7a5c7

Marking this as a separate issue with the camera package to get others' perspectives. Current package version: camera_android_camerax: 0.6.10

From Android triage: Closing this as a duplicate of https://github.com/flutter/flutter/issues/154241 and https://github.com/flutter/flutter/issues/154696. Feel free to leave any repro reports under https://github.com/flutter/flutter/issues/154241 if camera_android_camerax: 0.6.10 did not fix your issue with the camera preview orientation (not the video playback)!


fix(staff-payload): updated entity to contain missing displayName

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: