[!] Google Api Error: publishingDailySaveQuotaExceeded: Daily save quota exceeded.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I am getting below error while updating apk to alpha on playtore
[!] Google Api Error: publishingDailySaveQuotaExceeded: Daily save quota exceeded.
And i haven't updated the app today, so i am not sure why i am getting this error, as this is my first attempt to update the app on alpha.
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

[INSERT OUTPUT HERE]
lane :flavor1 do
supply(
track: 'alpha',
skip_upload_metadata: 'true',
skip_upload_images: 'true',
skip_upload_screenshots: 'true',
package_name: 'com.flavor1.src',
apk_paths: ["/Users/Involvio/..."]
)
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
[INSERT OUTPUT HERE]

+1
I have the same error "[!] Google Api Error: publishingDailySaveQuotaExceeded: Daily save quota exceeded." after publishing just 5 apk (split by abi).

+1
Same issue. Started Yesterday. Still happens today.
UncaughtThrowError: [!] uncaught throw #<FastlaneCore::Interface::FastlaneError: Google Api Error: publishingDailySaveQuotaExceeded: Daily save quota exceeded.>
  Fastfile:416:in `throw'
  Fastfile:416:in `rescue in perform_android_build'
  Fastfile:389:in `perform_android_build'
  Fastfile:243:in `block in parsing_binding'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:192:in `try_switch_to_lane'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:147:in `trigger_action_by_name'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/fast_file.rb:146:in `method_missing'
  Fastfile:249:in `block in parsing_binding'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:45:in `chdir'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:45:in `execute'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/lane_manager.rb:52:in `cruise_lane'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/command_line_handler.rb:30:in `handle'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/commands_generator.rb:105:in `block (2 levels) in run'
  /Users/jenkins/.gem/ruby/2.2.3/gems/commander-4.4.3/lib/commander/command.rb:178:in `call'
  /Users/jenkins/.gem/ruby/2.2.3/gems/commander-4.4.3/lib/commander/command.rb:178:in `call'
  /Users/jenkins/.gem/ruby/2.2.3/gems/commander-4.4.3/lib/commander/command.rb:153:in `run'
  /Users/jenkins/.gem/ruby/2.2.3/gems/commander-4.4.3/lib/commander/runner.rb:446:in `run_active_command'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:38:in `run!'
  /Users/jenkins/.gem/ruby/2.2.3/gems/commander-4.4.3/lib/commander/delegates.rb:15:in `run!'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/commands_generator.rb:302:in `run'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/fastlane/lib/fastlane/cli_tools_distributor.rb:65:in `take_off'
  /Users/jenkins/.gem/ruby/2.2.3/gems/fastlane-2.19.3/bin/fastlane:15:in `<top (required)>'
  /Users/jenkins/.gem/ruby/2.2.3/bin/fastlane:23:in `load'
  /Users/jenkins/.gem/ruby/2.2.3/bin/fastlane:23:in `<top (required)>'

@mfurtak  probably related to: https://github.com/fastlane/fastlane/pull/8474?

Hi everyone 👋
This is a rate limiting error message from the Play API that is outside of the control of fastlane and supply, but we'd like to look into it further in case there's something we could be doing better. 👍  Please provide information about your fastlane environment by pasting the output of fastlane env here.
Thanks!

Also, it would be helpful to know how often you're calling supply per day, and how many APK variants you are publishing.

Hmm, that's very odd - doesn't seem obvious how #8474 would have caused the Play API to trigger rate limiting more aggressively. If anything, I'd think it would reduce the traffic from supply to Play.

@tmtrademarked My feeling is the same is yours, so I'm not too suspicious of that change yet 👍

doesn't seem to be connected, sorry i think i thought in the wrong direction 😢

No worries @hjanuschka - looking at the recent changes is always a good idea 👍

For what it's worth, I'm also getting this same error. Even though this is the first time I've tried uploading an alpha today and even though (near as I can tell) the Google Play API Manager shows no API usage at all.
I'm not sure if this helps at all, but if I pass a 'validate_only' flag it is fine (and validates okay). This only happens when I try uploading a build.
Has anyone figured out a cause for - or solution to - this?
+-------------------------+-------------------------------------------------+
|                         Summary for supply 2.23.0                         |
+-------------------------+-------------------------------------------------+
| track                   | alpha                                           |
| json_key                | app/src/main/assets/google_service_account.json |
| apk                     | app/build/outputs/apk/app-release-signed.apk    |
| package_name            | (package name goes here)                        |
| skip_upload_metadata    | 1                                               |
| skip_upload_images      | 1                                               |
| skip_upload_screenshots | 1                                               |
| rollout                 | 0.1                                             |
| metadata_path           | ./metadata                                      |
| skip_upload_apk         | false                                           |
| validate_only           | false                                           |
+-------------------------+-------------------------------------------------+

DEBUG [2017-03-30 10:10:39.70]: Fetching a new access token from Google...
INFO [2017-03-30 10:10:40.73]: Preparing to upload for language 'en-US'...
INFO [2017-03-30 10:10:41.03]: Preparing apk at path 'app/build/outputs/apk/app-release-signed.apk' for upload...
INFO [2017-03-30 10:10:46.26]: Updating track 'alpha'...
INFO [2017-03-30 10:10:46.99]: Uploading all changes to Google Play...
/Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/fastlane_core/lib/fastlane_core/ui/interface.rb:146:in `user_error!': [!] Google Api Error: publishingDailySaveQuotaExceeded: Daily save quota exceeded. (FastlaneCore::Interface::FastlaneError)
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/fastlane_core/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/supply/lib/supply/client.rb:362:in `rescue in call_google_api'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/supply/lib/supply/client.rb:360:in `call_google_api'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/supply/lib/supply/client.rb:113:in `commit_current_edit!'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/supply/lib/supply/uploader.rb:36:in `perform_upload'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/supply/lib/supply/commands_generator.rb:38:in `block (2 levels) in run'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.4/lib/commander/command.rb:178:in `call'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.4/lib/commander/command.rb:153:in `run'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.4/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:38:in `run!'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.4/lib/commander/delegates.rb:15:in `run!'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/supply/lib/supply/commands_generator.rb:59:in `run'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/supply/lib/supply/commands_generator.rb:12:in `start'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/fastlane/lib/fastlane/cli_tools_distributor.rb:51:in `take_off'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.23.0/bin/fastlane:20:in `<top (required)>'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/bin/fastlane:22:in `load'
	from /Users/xcodeserver/.rbenv/versions/2.4.0/bin/fastlane:22:in `'

✅ fastlane environment ✅

### Stack

| Key                         | Value                                       |
| --------------------------- | ------------------------------------------- |
| OS                          | 10.12.2                                     |
| Ruby                        | 2.4.0                                       |
| Bundler?                    | false                                       |
| Git                         | git version 2.10.1 (Apple Git-78)           |
| Installation Source         | ~/.rbenv/versions/2.4.0/bin/fastlane        |
| Host                        | Mac OS X 10.12.2 (16C68)                    |
| Ruby Lib Dir                | ~/.rbenv/versions/2.4.0/lib                 |
| OpenSSL Version             | OpenSSL 1.0.2k  26 Jan 2017                 |
| Is contained                | false                                       |
| Is homebrew                 | false                                       |
| Is installed via Fabric.app | false                                       |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/ |
| Xcode Version               | 8.2.1                                       |

### System Locale

| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_US.UTF-8 | ✅ |
| LC_ALL   | en_US.UTF-8 | ✅ |
| LANGUAGE | en_US.UTF-8 | ✅ |

### fastlane files:

**No Fastfile found**

**No Appfile found**

### fastlane gems

| Gem      | Version | Update-Status |
| -------- | ------- | ------------- |
| fastlane | 2.23.0  | ✅ Up-To-Date  |

### Loaded fastlane plugins:

**No plugins Loaded**

Loaded gems

| Gem                       | Version      |
| ------------------------- | ------------ |
| did_you_mean              | 1.1.0        |
| slack-notifier            | 1.5.1        |
| claide                    | 1.0.1        |
| colored                   | 1.2          |
| nanaimo                   | 0.2.3        |
| xcodeproj                 | 1.4.2        |
| rouge                     | 1.11.1       |
| xcpretty                  | 0.2.4        |
| terminal-notifier         | 1.7.1        |
| unicode-display_width     | 1.1.3        |
| terminal-table            | 1.7.3        |
| plist                     | 3.2.0        |
| public_suffix             | 2.0.5        |
| addressable               | 2.5.0        |
| multipart-post            | 2.0.0        |
| word_wrap                 | 1.0.0        |
| tty-screen                | 0.5.0        |
| babosa                    | 1.0.2        |
| highline                  | 1.7.8        |
| commander-fastlane        | 4.4.4        |
| excon                     | 0.54.0       |
| faraday                   | 0.11.0       |
| unf_ext                   | <IP_ADDRESS>      |
| unf                       | 0.1.4        |
| domain_name               | 0.5.20161129 |
| http-cookie               | 1.0.3        |
| faraday-cookie_jar        | 0.0.6        |
| fastimage                 | 2.0.1        |
| gh_inspector              | 1.0.3        |
| mini_magick               | 4.5.1        |
| multi_json                | 1.12.1       |
| multi_xml                 | 0.6.0        |
| rubyzip                   | 1.2.0        |
| security                  | 0.1.3        |
| xcpretty-travis-formatter | 0.0.4        |
| json                      | 1.8.6        |
| thread_safe               | 0.3.5        |
| tzinfo                    | 1.2.2        |
| minitest                  | 5.10.1       |
| activesupport             | <IP_ADDRESS>      |
| io-console                | 0.4.6        |
| openssl                   | 2.0.2        |
| faraday_middleware        | <IP_ADDRESS>     |
| bundler                   | 1.14.3       |

*generated on:* **2017-03-30**

BTW, when I set DEBUG = 1 and run the upload I get a number of 500 error responses on the 'commit' calls before it fails.


Prepare release 0.13.2 & run regression detector with the release candidate

What does this PR do?
Update 'outer' lading with support for experiments that don't have a generator.
Motivation
This allows apache_common_http_to_blackhole to function.
Related issues
#514

I'm going to split the prepare-release part of this out to a separate PR as soon as the RC binaries are published. That will allow us to hold 0.13.2 until the RC is tested in the trusted CI flow.


SVG image issue

Version 36.0.1985.143 on Mac
bigplay.svg - the center arrow of the rollover state does not display.

@mmcglynn Closing old issues. If you'd like to reopen this, let us know. Thanks!


I want to meet who developed it, I will try it may be oneday ❤

Checkboxes

[ ] Updated fsociety
[ ] Issue does not already exist
[ ] fsociety issue, not a tool issue

Expected Result

Actual Result

Please close if you have no issues.

🧏♂🧏♂🧏♂🧏♂🧏♂🧏♂🧏♂


Fix NULL id issue in performance records

Updated the schema to set id as INTEGER PRIMARY KEY AUTOINCREMENT.
Ensured proper ID generation for performance records.
Added tests for performance recorder.

#1


Add task to search repositories

id: myflow
namespace: company.myteam

tasks:
  - id: search
    type: io.kestra.plugin.github.repositories.Search
    token: your_github_token
    query: "tetris language:assembly"

We will fetch all the page
We will store the result as Ion file only

Done in https://github.com/kestra-io/plugin-github/pull/7


Document best practice and anti-patterns for development workflows (SQLite in dev, Postgres in prod)

Lots of people are used to working with SQLite in development and then switching to a "proper" DB like Postgres in production.
This is a workflow that's not straightforward to achieve with Prisma (mostly because the provider of a datasource can't be set dynamically). Further, it's actually considered not a good practice because:

Prisma schema capabilities (as well as the generated Prisma Client code) change depending on the provider (e.g. enum definitions are possible with Postgres but not SQLite; the goal of Prisma is to be able to expose the specific features of the underlying DB, and since SQLite doesn't natively support enums, Prisma does not allow their usage in the Prisma schema either)
there is a potential for a mismatch in behaviour when going from development to production that should rather be avoided

More context in this Slack convo:

Even more context here: https://github.com/prisma/prisma/issues/3834

Even more context here: https://github.com/prisma/prisma/issues/3834

another related convo: https://twitter.com/benediktms/status/1359844377091338245

Is there any progress/recipe on this? Having to spin up a "full" db for local dev. is a bit overkill for most use cases.

Thanks for bumping this one, @cupcakearmy; it does look like a good topic for the Docs team to take on. We will  pull it in and triage it soon.

If prisma devs ever consider supporting sqlite in dev, postgres in prod, in my opinion, this would be very helpful, and is achievable, Django devs did it and it works well:
https://docs.djangoproject.com/en/5.0/topics/migrations/


Client Even Better TOML LSP: connection to server is erroring. Cannot call write after a stream was destroyed

Keeps occurring constantly since I switched away from the bundled version (since the bundled version seems out of date).
Taplo Version
/home/tom/.cargo/bin/taplo -V
taplo 0.9.3

VS Code User Settings
    "evenBetterToml.taplo.bundled": false,
    "evenBetterToml.taplo.path": "/home/tom/.cargo/bin/taplo",

VS Code Info
Version: 1.97.0-insider
Commit: 89f808979a5151bd91324e65d4f7ab1b62896983
Date: 2024-12-20T05:04:19.167Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.8.0-51-generic

Extension Output
[Error - 2:54:26 PM] Server process exited with code 1.
[Error - 2:54:26 PM] Client Even Better TOML LSP: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 2:54:26 PM] Server initialization failed.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 2:54:26 PM] Even Better TOML LSP client: couldn't create connection to server.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Info  - 2:54:26 PM] Connection to server got closed. Server will restart.
true
ERROR operation failed error=the LSP is not part of this build, please consult the documentation about enabling the functionality
[Error - 2:54:27 PM] Server process exited with code 1.
[Error - 2:54:27 PM] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Info  - 2:54:27 PM] Connection to server got closed. Server will restart.
true
[Error - 2:54:27 PM] Even Better TOML LSP client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 2:54:27 PM] Server process exited with code 1.
[Error - 2:54:27 PM] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Info  - 2:54:27 PM] Connection to server got closed. Server will restart.
true
[Error - 2:54:27 PM] Even Better TOML LSP client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 2:54:27 PM] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 2:54:27 PM] Server process exited with code 1.
[Error - 2:54:27 PM] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Info  - 2:54:27 PM] Connection to server got closed. Server will restart.
true
[Error - 2:54:27 PM] Even Better TOML LSP client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 2:54:27 PM] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 2:54:27 PM] Server process exited with code 1.
[Error - 2:54:27 PM] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 2:54:27 PM] The Even Better TOML LSP server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
[Error - 2:54:27 PM] Even Better TOML LSP client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 2:54:27 PM] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097

ERROR operation failed error=the LSP is not part of this build, please consult the documentation about enabling the functionality
It seems you have installed taplo without LSP feature


Add a toggle function to comment all debugprint

I think it's useful to temporarily comment out these print statements because if it's just deletion, then if you want to see the print again, you'll have to regenerate it

@xzbdmw interesting idea, and - famous last words - I don't think too hard to implement. I'll take a look at it. Thanks!

@xzbdmw hi, this has been implemented now, please try out the latest version of NeoVim on the main branch. There is a command added by default called ToggleCommentDebugPrints which should do what you want.
You will need to have mini.nvim installed also (even if you don't use it) - the README shows how to make this a dependency.

Note that - hot off the press - mini.nvim is now no longer needed on NeoVim 0.10+ (nightly) since it supports comments inbuilt. Still needed for older NeoVim versions.


Fix: Add not allowed sign for archived workspace.

Notes: Browsers or OS will decide how the cursor should show. In MacOS, the default cursor is used for it. This is expected.
Details

Fix: Add not allowed sign for archived workspace.
Fixed Issues

$ https://github.com/Expensify/App/issues/24191
PROPOSAL: https://github.com/Expensify/App/issues/24191#issuecomment-1667253937
Tests

Open any Archived Room
Drag the attachment on The Archived Room
Verify that the mouse appears as not allowed sign.

[x] Verify that no errors appear in the JS console

Offline tests

Same as Tests.
QA Steps

Open any Archived Room
Drag the attachment on The Archived Room
Verify that the mouse appears as not allowed sign.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/16502320/e31a3ce7-c401-44f8-898b-721aaba58067
https://github.com/Expensify/App/assets/16502320/c8e51805-54c9-49e1-a829-4eb8a8e21fb5

Mobile Web - Chrome

chrome.webm

Mobile Web - Safari

safari.webm

Desktop

https://github.com/Expensify/App/assets/16502320/b40df25a-60cd-4d2e-bcc3-be1a164c149d

iOS

Not support

Android

Not support

@Santhosh-Sellavel PR is ready for review! Please have a look, ty 😄

little bump @Santhosh-Sellavel

Oh, I lost this one completely. Adding to the list

Sorry for the delay will try to get it done within 1 or 2 days!

@hungvu193
I'm getting this error method got renamed, can you fix this one please?

@hungvu193 I'm getting this error method got renamed, can you fix this one please?

it was changed to canUserPerformWriteAction in this https://github.com/Expensify/App/pull/29887.
Updated btw 😄

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

MacOS: Chrome / Safari & MacOS: Desktop
https://github.com/Expensify/App/assets/85645967/e4e2b200-a30f-4045-a759-faae912872f2

Android: Native
Unable to test this case

Android: mWeb Chrome
Unable to test this case

iOS: Native
Unable to test this case

iOS: mWeb Safari
Unable to test this case

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/nkuoch in version: 1.3.96-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.96-15 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/nkuoch in version: 1.3.98-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.98-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Allow types to be specified directly for relationships

What Changed & Why
The motivation for this PR is to allow for serializing polymorphic relationships.
A model with a relationship is defined like:
jsonApi.define('order', {
  name: '',
  payables: {
    jsonApi: 'hasMany',
    type: ????
  }
})

If payable has a polymorphic type, then the type cannot be specified during model definition.
This PR brings in support for serializing types that are not present in model definitions, and can instead be specified directly when a Devour request is being constructed.  See the tests and readme for an example.
In conjunction with https://github.com/twg/devour/pull/51 this library will have better support in general for polymorphic relationships.
Testing

[ ] npm test

Bug/Ticket Tracker
n/a
Documentation
n/a
People
@Emerson @billxinli @themarkappleby

@spiderbites  – 👍  Feel free to merge as needed, not using this library at the moment, so it's all yours to manage :-)

👌


Errors and warnings with noncompounded returns and sum() type functions

I recently ran into similar warnings/errors for noncompounded returns similar to #11 (see below). The fixes are fairly straightforward, I will submit a pull request.
/path/to/python/lib/python3.12/site-packages/numpy/core/fromnumeric.py:86: FutureWarning: The behavior of DataFrame.sum with axis=None is deprecated, in a future version this will reduce over both axes and return a scalar. To retain the old behavior, pass axis=0 (or do not pass axis)

  File "/path/to/python/lib/python3.12/site-packages/quantstats_lumi/_plotting/wrappers.py", line 555, in yearly_returns
    returns = returns.resample("YE").apply(_df.sum)
[...]
  File "/path/to/python/lib/python3.12/site-packages/pandas/core/frame.py", line 11657, in sum
    result = super().sum(axis, skipna, numeric_only, min_count, **kwargs)
             ^^^^^^^^^^^
TypeError: super(type, obj): obj must be an instance or subtype of type

/path/to/python/lib/python3.12/site-packages/quantstats_lumi/_plotting/core.py:426: FutureWarning: The provided callable <function sum at 0x7fb51bb2f2e0> is currently using DatetimeIndexResampler.sum. In a future version of pandas, the provided callable will be used directly. To keep current behavior pass the string "sum" instead.
  .apply(apply_fnc)
/path/to/python/lib/python3.12/site-packages/quantstats_lumi/_plotting/core.py:432: FutureWarning: The provided callable <function sum at 0x7fb51bb2f2e0> is currently using DatetimeIndexResampler.sum. In a future version of pandas, the provided callable will be used directly. To keep current behavior pass the string "sum" instead.
  returns.fillna(0).resample(resample).apply(apply_fnc).resample(resample).last()
/path/to/python/lib/python3.12/site-packages/quantstats_lumi/_plotting/core.py:1008: FutureWarning: The provided callable <function sum at 0x7fb51bb2f2e0> is currently using DatetimeIndexResampler.sum. In a future version of pandas, the provided callable will be used directly. To keep current behavior pass the string "sum" instead.
  port["Weekly"] = port["Daily"].resample("W-MON").apply(apply_fnc)
/path/to/python/lib/python3.12/site-packages/quantstats_lumi/_plotting/core.py:1011: FutureWarning: The provided callable <function sum at 0x7fb51bb2f2e0> is currently using DatetimeIndexResampler.sum. In a future version of pandas, the provided callable will be used directly. To keep current behavior pass the string "sum" instead.
  port["Monthly"] = port["Daily"].resample("ME").apply(apply_fnc)
/path/to/python/lib/python3.12/site-packages/quantstats_lumi/_plotting/core.py:1014: FutureWarning: The provided callable <function sum at 0x7fb51bb2f2e0> is currently using DatetimeIndexResampler.sum. In a future version of pandas, the provided callable will be used directly. To keep current behavior pass the string "sum" instead.
  port["Quarterly"] = port["Daily"].resample("QE").apply(apply_fnc)
/path/to/python/lib/python3.12/site-packages/quantstats_lumi/_plotting/core.py:1017: FutureWarning: The provided callable <function sum at 0x7fb51bb2f2e0> is currently using DatetimeIndexResampler.sum. In a future version of pandas, the provided callable will be used directly. To keep current behavior pass the string "sum" instead.
  port["Yearly"] = port["Daily"].resample("YE").apply(apply_fnc)

@grzesir I noticed that 0.1.11 was released today. Any chance you could take a look at #20 and see if it can be included in the next release?

Fixed by #20


Databricks Unity Catalog connector

to bring in metadata, including col-level lineage https://www.databricks.com/blog/2022/12/12/announcing-general-availability-data-lineage-unity-catalog.html?utm_source=bambu&utm_medium=social&utm_campaign=advocacy&blaid=3916832

I am currently evaluating Open Metadata for a larger customer/project that uses Databricks as a platform. We are using the Unity Catalog in the AWS Cloud and the metadata (type: metadata) is already being ingested successfully.
Unfortunately, the type profiler does not yet work as desired, because it terminates with the following error message:
ServerOperationError( databricks.sql.exc.ServerOperationError: Table or view not found: common.dim__addresses; line 3 pos 5
Is it possible that this is related to the new three-level namespace of Unity Catalog? Obviously here the catalog (is called prod) is not prefixed, but only common (schema) and dim__addresses (table).
[2023-03-23 12:07:48,372] {sqa_profiler_interface.py:429} INFO - Computing metrics with 1.0 threads.
[2023-03-23 12:07:48,372] {sqa_profiler_interface.py:383} DEBUG - Running profiler for dim__addresses on thread <Thread(ThreadPoolExecutor-0_0, started<PHONE_NUMBER>87360)>
[2023-03-23 12:07:48,372] {system.py:65} INFO - System metrics not support for databricks. Skipping processing.
[2023-03-23 12:07:48,374] {sqa_profiler_interface.py:383} DEBUG - Running profiler for dim__addresses on thread <Thread(ThreadPoolExecutor-0_0, started<PHONE_NUMBER>87360)>
[2023-03-23 12:07:48,967] {sqa_profiler_interface.py:177} DEBUG - Traceback (most recent call last):
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1802, in _execute_context
    self.dialect.do_execute(
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 719, in do_execute
    cursor.execute(statement, parameters)
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/client.py", line 241, in execute
    execute_response = self.thrift_backend.execute_command(
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/thrift_backend.py", line 629, in execute_command
    return self._handle_execute_response(resp, cursor)
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/thrift_backend.py", line 704, in _handle_execute_response
    final_operation_state = self._wait_until_command_done(
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/thrift_backend.py", line 582, in _wait_until_command_done
    self._check_command_not_in_error_or_closed_state(op_handle,
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/thrift_backend.py", line 359, in _check_command_not_in_error_or_closed_state
    raise ServerOperationError(
databricks.sql.exc.ServerOperationError: Table or view not found: common.dim__addresses; line 3 pos 5

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/airflow/.local/lib/python3.9/site-packages/metadata/interfaces/sqalchemy/sqa_profiler_interface.py", line 168, in _
    row = runner.select_first_from_sample(
  File "/home/airflow/.local/lib/python3.9/site-packages/metadata/orm_profiler/profiler/handle_partition.py", line 128, in handle_and_execute
    return func(_self, *args, **kwargs)
  File "/home/airflow/.local/lib/python3.9/site-packages/metadata/orm_profiler/profiler/runner.py", line 80, in select_first_from_sample
    return self._select_from_sample(*entities, **kwargs).first()
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 2810, in first
    return self.limit(1)._iter().first()
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 2894, in _iter
    result = self.session.execute(
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 1689, in execute
    result = conn._execute_20(statement, params or {}, execution_options)
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1614, in _execute_20
    return meth(self, args_10style, kwargs_10style, execution_options)
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/sql/elements.py", line 325, in _execute_on_connection
    return connection._execute_clauseelement(
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1481, in _execute_clauseelement
    ret = self._execute_context(
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1845, in _execute_context
    self._handle_dbapi_exception(
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 2026, in _handle_dbapi_exception
    util.raise_(
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 207, in raise_
    raise exception
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1802, in _execute_context
    self.dialect.do_execute(
  File "/home/airflow/.local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 719, in do_execute
    cursor.execute(statement, parameters)
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/client.py", line 241, in execute
    execute_response = self.thrift_backend.execute_command(
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/thrift_backend.py", line 629, in execute_command
    return self._handle_execute_response(resp, cursor)
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/thrift_backend.py", line 704, in _handle_execute_response
    final_operation_state = self._wait_until_command_done(
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/thrift_backend.py", line 582, in _wait_until_command_done
    self._check_command_not_in_error_or_closed_state(op_handle,
  File "/home/airflow/.local/lib/python3.9/site-packages/databricks/sql/thrift_backend.py", line 359, in _check_command_not_in_error_or_closed_state
    raise ServerOperationError(
sqlalchemy.exc.DatabaseError: (databricks.sql.exc.ServerOperationError) Table or view not found: common.dim__addresses; line 3 pos 5
[SQL: /* {"app": "OpenMetadata", "version": "<IP_ADDRESS>"} */
SELECT count(*) AS `rowCount`, %(param_1)s AS `columnCount`, %(param_2)s AS `columnNames`
FROM `common`.`dim__addresses`
 LIMIT %(param_3)s]
[parameters: {'param_1': 4, 'param_2': 'dim__addresses__sk,country,city,zip', 'param_3': 1}]
(Background on this error at: https://sqlalche.me/e/14/4xp6)

We can review the sdk and see if it brings more/better info than our current SQLAlchemy approach. It might be easier to get all the info from there


Micronaut cloud database guide base and Oracle Cloud

I left some TODOs that I'll get back to in a bit and there's still some rework needed

Here's a PDF of the guide: micronaut-cloud-database-oracle.pdf

I've added the PR to the project. Please, let's use the Github project.

WARNING: We cannot merge this until this PR is merged https://github.com/micronaut-projects/micronaut-guides/pull/685

@kroegerk can you proofread this guide? Thanks!


[FEATURE REQUEST] Upgrade Python from 3.7 to 3.10 and apply needed changes

Is your feature request related to a problem? Please describe.
Right now we are using for development and in devcontainer Python 3.7.
Describe the solution you'd like
We want to upgrade python for our development to version 3.9 and apply changes needed to the code.
Describe alternatives you've considered
None.
Additional context
None.

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Schema updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license
[ ] Backport tasks created / doesn't need to be backported

@asciible I think we should also update agent pool on Azure DevOps to use Python 3.10, not Python 3.7 for running unit tests and linters.
Files that probably needs to be updated:
https://github.com/epiphany-platform/azure-pipelines-agents/blob/main/docker-image/Dockerfile
https://github.com/epiphany-platform/azure-pipelines-agents/blob/main/docker-image/configure-tool-cache.sh
and then we have to re-deploy Azure pipelines agents.

#2947 created


Is there a way to run doctests?

I wondered, since there are docstrings with code samples, and even the doc/fake__sounddevice.py may be you guys considered already (so I do not need to fight the windmill) to run the doctests?  On my semi-blind attempt:
$> python -m nose --with-doctest sounddevice.py
FFFFF
======================================================================
FAIL: Doctest: sounddevice.AsioSettings.__init__
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.6/doctest.py", line 2199, in runTest
    raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for sounddevice.AsioSettings.__init__
  File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 2093, in __init__

----------------------------------------------------------------------
File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 2117, in sounddevice.AsioSettings.__init__
Failed example:
    sd.play(..., extra_settings=asio_out)
Exception raised:
    Traceback (most recent call last):
      File "/usr/lib/python3.6/doctest.py", line 1330, in __run
        compileflags, 1), test.globs)
      File "<doctest sounddevice.AsioSettings.__init__[2]>", line 1, in <module>
        sd.play(..., extra_settings=asio_out)
      File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 135, in play
        ctx.frames = ctx.check_data(data, mapping, kwargs.get('device'))
      File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 2306, in check_data
        dtype = _check_dtype(data.dtype)
      File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 2459, in _check_dtype
        raise TypeError('Unsupported data type: ' + repr(dtype))
    TypeError: Unsupported data type: 'object'
----------------------------------------------------------------------
File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 2122, in sounddevice.AsioSettings.__init__
Failed example:
    sd.play(...)
Exception raised:
    Traceback (most recent call last):
      File "/usr/lib/python3.6/doctest.py", line 1330, in __run
        compileflags, 1), test.globs)
      File "<doctest sounddevice.AsioSettings.__init__[4]>", line 1, in <module>
        sd.play(...)
      File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 135, in play
        ctx.frames = ctx.check_data(data, mapping, kwargs.get('device'))
      File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 2306, in check_data
        dtype = _check_dtype(data.dtype)
      File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 2459, in _check_dtype
        raise TypeError('Unsupported data type: ' + repr(dtype))
    TypeError: Unsupported data type: 'object'
----------------------------------------------------------------------
File "/home/yoh/deb/gits/python-sounddevice/sounddevice.py", line 2128, in sounddevice.AsioSettings.__init__
Failed example:
    sd.playrec(..., channels=1, ...)
Exception raised:
    Traceback (most recent call last):
      File "/usr/lib/python3.6/doctest.py", line 1330, in __run
        compileflags, 1), test.globs)
      File "<doctest sounddevice.AsioSettings.__init__[7]>", line 1
    SyntaxError: positional argument follows keyword argument

...

so already not sure if that is something to investigate to see if could be made "proper".
P.S. but may be it is just me+Friday -- can't even build documentation :-(
$> which python
/home/yoh/deb/gits/python-sounddevice/venvs/dev3/bin/python
(dev3) 1 11269.....................................:Fri 06 Apr 2018 07:21:37 PM EDT:.
(git)hopa:~deb/python-sounddevice[master]git
$> python /usr/share/sphinx/scripts/python3/sphinx-build -P doc build/doc
Running Sphinx v1.6.7
Exception occurred while building, starting debugger:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/cmdline.py", line 305, in main
    opts.warningiserror, opts.tags, opts.verbosity, opts.jobs)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 192, in __init__
    self.setup_extension(extension)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 456, in setup_extension
    self.registry.load_extension(self, extname)
  File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 196, in load_extension
    mod = __import__(extname, None, None, ['setup'])
  File "/usr/lib/python3/dist-packages/sphinx/builders/linkcheck.py", line 18, in <module>
    from requests.exceptions import HTTPError
  File "/usr/lib/python3/dist-packages/requests/__init__.py", line 84, in <module>
    from urllib3.contrib import pyopenssl
  File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", line 46, in <module>
    import OpenSSL.SSL
  File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in <module>
    from OpenSSL import crypto, SSL
  File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 12, in <module>
    from cryptography import x509
  File "/usr/lib/python3/dist-packages/cryptography/x509/__init__.py", line 8, in <module>
    from cryptography.x509.base import (
  File "/usr/lib/python3/dist-packages/cryptography/x509/base.py", line 16, in <module>
    from cryptography.x509.extensions import Extension, ExtensionType
  File "/usr/lib/python3/dist-packages/cryptography/x509/extensions.py", line 13, in <module>
    from asn1crypto.keys import PublicKeyInfo
  File "/usr/lib/python3/dist-packages/asn1crypto/keys.py", line 22, in <module>
    from ._elliptic_curve import (
  File "/usr/lib/python3/dist-packages/asn1crypto/_elliptic_curve.py", line 51, in <module>
    from ._int import inverse_mod
  File "/usr/lib/python3/dist-packages/asn1crypto/_int.py", line 56, in <module>
    from ._perf._big_num_ctypes import libcrypto
  File "/usr/lib/python3/dist-packages/asn1crypto/_perf/_big_num_ctypes.py", line 39, in <module>
    libcrypto = CDLL(libcrypto_path)
  File "/usr/lib/python3.6/ctypes/__init__.py", line 348, in __init__
    self._handle = _dlopen(self._name, mode)
TypeError: expected str, bytes or os.PathLike object, not NotImplementedType
> /usr/lib/python3.6/ctypes/__init__.py(348)__init__()
-> self._handle = _dlopen(self._name, mode)
(Pdb)

First of all: there are no tests. And that's bad. It would be really good if we could add some tests to the project. See also #14.
The code from the README and from the docstrings isn't meant to be used for doctests.
There are many omissions, e.g. the definitions of myarray, fs, ... and so on. I intentionally didn't define those to keep the code short and simple.
There are also some platform-specific code examples, which means they would have to be selectively or globally disabled when running tests.
The test failures you are showing above are very much expected. Note the ... which should be replaced by real code. Also, the ASIO stuff will only work if ASIO is available.
The file doc/fake__sounddevice.py is not meant for tests. It's for building the documentation without CFFI and the PortAudio library being installed. This way we can also build it on readthedocs.org.
To be able to do this, we mocked and monkey-patched a few things (only during the documentation build), including ctypes.util.find_library().
I think this is the cause for the second error you showed above.
For some reason some crypto-libraries are imported which seem to call ctypes.util.find_library() and since we have patched it to always return NotImplemented, the import fails.
I guess we should change our way of monkey-patching ctypes.util.find_library(), any ideas how we could do that?

Eh, I wish I had a good answer, but your project is new to me, and I never dealt with cffi before, and with ctypes only so briefly and awhile back. But I guess there is a need to provide the moved up library which would be returned by find_library and so it could be used by the tests - you could mock it's calls in turn to provide output your are expecting, so you could implement your code unit tests.
My reason for raising this issue is just to find some way to test correct code behavior (even if without testing integration with real hardware/library) across Debian/Ubuntu released while preparing the Debian package

Part of this issue (regarding find_library()) should be fixed in f41bbf2fbf0fdd0bc3ad1ee90204c690b32e22e9.
But there are still no automated tests ...


Can you support etcd?

Can you support etcd?

Etcd is slightly harder in the sense that it's very generic. It means that we need to define ourself how a service is registered in etcd.
Do you know if there is some kind of standard?
In addition, you can implement a custom service discovery for etcd using your own  opinionated way to register the services.

Using etcd directly is not a very secure practice. Read/write data to the kubernetes etcd store is root access to every cluster node. From what I see you to use the kubernetes etcd store should be done via the kubernetes API, creating a config-map or CRD but in that case yes, is there a standard?


Dev fix json bug

Coverage increased (+0.4%) to 91.247% when pulling 3df56f42cc095cbc9e647d22efce3f4bd1e64e23 on dev_fix_json_bug into 52799f645277f14f92549ca8a8963b1cf3b6bfba on json_bug.

Coverage increased (+0.4%) to 91.247% when pulling 555976ec33866838047be2bb323fa560f77af58e on dev_fix_json_bug into 52799f645277f14f92549ca8a8963b1cf3b6bfba on json_bug.

Coverage increased (+0.4%) to 91.247% when pulling 428c90255fba7f9e5ed5496c098cac2ca30651cd on dev_fix_json_bug into 52799f645277f14f92549ca8a8963b1cf3b6bfba on json_bug.

Coverage increased (+1.0%) to 91.817% when pulling 6a3855856881311320d008792273c0f0dbff7d17 on dev_fix_json_bug into 52799f645277f14f92549ca8a8963b1cf3b6bfba on json_bug.

Coverage decreased (-0.2%) to 90.614% when pulling da9a989b38fe7e9c8cb86e8861e13db2e5d9c792 on dev_fix_json_bug into 52799f645277f14f92549ca8a8963b1cf3b6bfba on json_bug.

Coverage increased (+1.0%) to 91.817% when pulling 5703dd10a01727c96e7d0861a2463bfcb3437051 on dev_fix_json_bug into 52799f645277f14f92549ca8a8963b1cf3b6bfba on json_bug.

Coverage increased (+1.0%) to 91.817% when pulling 8d8ae9ba83a6c31adb255ffe492979803961b62c on dev_fix_json_bug into 52799f645277f14f92549ca8a8963b1cf3b6bfba on json_bug.


Allow choosing "Goto Source (Def)" editor

Currently, it opens a TextEditorWindow (or notepad2, if on the path?). Allow this to be customized, so the user can choose, for example, VIM or Visual Studio.

@vancem I think I can provide a PR for this, but I'm unsure about where to place the setting for specifying the executable to use for the source files. Should it be under File => "Set Text Editor" (similar to "Set Symbol Path" and "Set Source Path")?

Today PerfView does have a configuration story (the AppData\Roaming\PerfView\UserConfig.xml file) but the UI for it is not really there.
But I also believe it is useful for some things to be controlled via Environment variable as well (we already do this with _NT_SYMBOL_PATH and _NT_SOURCE_PATH).    This allows people to configure PerfView with scripts.
Thus one simple way of dealing with this is to define an environment variable for it (e.g. PerfView_TextEditor) and simply document that.
In the end, we probably want a 'User Config' dialog that lets you set users preferences like this.    Indeed Clear User Config and 'Set Symbol Path' (and set Source Path' should be  under that.
However that is a bigger change.   I OK with simply hading a 'Set Text Editor' under the 'File' menu item as you suggest in the short term.

Hi,
I would like to contribute to this project. I believe this is a good issue to start with if nobody is actively working on it? Also, Could you point me to any documentation, build instructions, etc. to understand the code base, and start with this?
with regards to the issue, would it suffice to have a menu item?
Thanks in advance for the help.

No one is activity working on it.   The main GitHub page https://github.com/Microsoft/perfview has some getting started guidance.
The environment variable approach is the easiest because it does not require any change to the user interface (we will need to document it (update userGuide.htm)).
You should also consider if you wish to  tackle the large item of allowing update of user config (and this would be just one piece).

Hi everyone!
I'll work on this one.
VS Code isn't capable of compiling the source?

VS Code isn't capable of compiling the source?

I don't understand your question.   The issue is what editor if fetched when you do a 'Goto Source' command.   The source will be fetched one file at a time from a source server, and thus is not buildable by any tool in that form (it would only be one file).
It is certainly possible to set up your symbol path and source path so that it finds the source code in some local directory which you DID set up to be buildable.   However keep in mind that most tools (like VS, and VSCode), know how to edit a single file if launched one way, and open a whole solution if launched another (e.g. opening the *.sln).
This work item has modest goals, to allow users to choose their editor.  Making it set up so that it hops to a IDE set up to build the source woudl be nice, but probably needs some features from the IDE to make work.    Feel free to think about that, but that is really more than what was being requested here.

@vancem I think that @cirojr wants to use VS Code to compile this repo to work on this issue.

Exactly! Sorry if didn't make it clearer.
But VS Studio is a better tool to visualize the xaml files, I think.
I would like to make a little overview in the repo first.
Thanks anyway.

Ahh, I see.  I don't know the limits of VSCode, but PerfView does have both native and managed components, and is a moderately complex project.    There are probably blocking issues, but if anyone want to investigate I can give them information about the PerfView project.   (should be done as its own issue/pr)

Hi @vancem! I've did the changes in UI too, making a "User Config" menu item, with the three sub options. I reutilized the same SymbolPathDialog to save and retrieve a Text Editor path.
My doubt now is: I'll need to call the run command just with the editor path and the "sourcePathToOpen", without the "/g" parameter or the line number, because the editor configured may does not accept them. Am I right?
I'll search if there's any tests to this functionality, make a manual test here and send the PR.


Modified view-agency component & css for updated interface

Related Issue

Fixes #212
Checklist:

[x] I have read the contributor's guide.
[x] I linked an issue in the previous section
[x] I have commented on the linked issue
[x] I was assigned the linked issue (not required)
[x] I have tested the change to the best of my ability against the sandbox or a local build.

Optional items:

[ ] My change adds new text and requires a change to translations.
[ ] My change requires a change to the documentation.
[ ] I have submitted a PR to the documentation repo.
[ ] I was not able to test... (explain below, e.g. you did not have permissions to test a specific feature)
[ ] This change depends O-FISH Realm repository changes (explain below)

Optional: Add any explanations here
Modified view-agency component as well as css file to incorporate design requirements

Optional: Add any relevant screenshots here

Hi, it still won't build - you can see that on this PR page:

and if you click through to "Details" you can see:
./src/components/agencies/view-agency/view-agency.component.js
Line 257:41:  'agencyInfo' is not defined  no-undef

Hi @deveshchatuphale7 - Can you see the "checks" section of #326 ? I can't review the code until it builds and gets a green checkmark there. It looks like you fixed the first issue, but now there's another issue.

Thanks for informing. Hopefully my latest commit will fix the issue. But I am curious why I was not getting any issue while generating build locally

Hi there! The build on the website builds the current code with your changes. You probably did not do a "git pull" before your testing and PR submission, so you had older code - the files you didn't change. Github tests the current code plus your changes because there could be issues and it wants to find them first.

Hi! It built, but I'm not seeing the problem resolved.
I logged in as an Agency Administrator, then went to the Agencies page. Then clicked on my agency, and here's the page I got:

It still shows 0 officers, when there should at least be 1 officer (me!).
I did this against the sandbox; is that what you used?

Yes, Actually also for my login I got officers array with key officers under agencyAdditionalInfo object was empty. Hence dashboard is showing zero officers.

Did I miss any step here, could you point me in right direction ?

Ah! I see. You correctly printed out agencyAdditionalInfo.
The problem is that agencyAdditionalInfo object is wrong - how is it populated? is it looking in the wrong place for officers?
You might be able to find some clues by looking at src/components/agencies/agencies.component.js - I can see there's a function in there called getAgenciesWithOfficers, which is how that page gets a list of officers, which it then uses to display.

Congratulations! 🎉 🙌 🎆 ㊗
This PR is great and has been merged into the code. Thanks so much for contributing! If you'd like, you can request to work on another issue. We really appreciate your effort!
To claim your O-FISH badge, head on over to the MongoDB Community forums, login, and reply - making sure to link to this PR.

Congratulations! 🎉 🙌 🎆 ㊗
This PR is great and has been merged into the code. Thanks so much for contributing! If you'd like, you can request to work on another issue. We really appreciate your effort!
To claim your O-FISH badge, head on over to the MongoDB Community forums, login, and reply - making sure to link to this PR.

Sure!


Add Jimbodiah's Simple RSS patch from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of Jimbodiah, to add Jimbodiah's Simple RSS patch to CKAN.
Mod details:
name = /mod/1446/Jimbodiah%27s%20Simple%20RSS%20patch
author = Jimbodiah
abstract = Want to play RSS but not use RO or other extensive rescalers? This patch allows you to use stock parts in a bare RSS install and raises ISP/Thrust to make ships behave like in the real solar system.
license = MIT
Homepage = http://forum.kerbalspaceprogram.com/index.php?/topic/161996-13x-jimbodiahs-patch-laboratory/
description = A super simple patch to tune engine thrust and ISP so that you can use stock parts in a bare install of Real Solar System without needing Realism Overhaul or other complicated setups.
This does not re-scale your rockets to actual real-world size like RO does, but keeps all components as they are out of the box.
Please direct questions about this pull request to Jimbodiah.

RSS not available for kSP1.3


ecobee api changes, effective dec 1 2020

just got this e-mail, figured i would share here since the client will obviously need some changes to work with the new token format...
Upcoming API Changes Effective December 1, 2020
The following changes will go into effect on December 1, 2020. If you are unsure whether these changes will have an impact on your solution today, we encourage you to discuss it with your technology team, program manager, other stakeholders and ecobee partners.
Access/Refresh Token Format Changes
Starting from December 1, 2020, ecobee access tokens will no longer be returned as opaque 32-character strings. Access tokens will now be JWTs, which are considerably longer and uses a wider character set. Our JWTs follow the RFC7575 standard for JSON Web Signature tokens.
To ensure your application will continue to work, you will need to ensure that your application supports the following changes:                                                                                Access tokens will be up to 7KB in length, and includes upper/lower case alphanumeric characters, hyphens, underscores, and periods.
Refresh tokens can be of varying lengths and can contain non-alphanumeric characters.
Authorization Code Changes
The Redirect URI associated with your registered application should be a semi-colon separated list of absolute URLs that start with https://. We do not accept http:// protocol links.
PIN Authorization Changes
PINs will become 10 character alphanumeric strings.
This flow is only recommended in situations where a user is interacting with a device that cannot easily use a web-based login form; we recommend migrating to the Authorization Code strategy for a better user experience.

Thanks for the heads-up. The changes seem trivial but unless there's a test server to test this on I won't be able to push any code changes until it goes live and I'm able to test it.

There is supposed to be a way of getting access to a test server, but I am not having much success with this - regular support gave me a different email address to contact, but there has been no response to my message to that address. I have raised another ticket and will report back if/when I get a more useful response. Assuming that the keys are held as regular Python strings and that no assumptions are made about their contents, there should be no need to change anything.

I also emailed their support last week to get access to the test server but they haven't gotten back to me

I've just been notified that for those using PIN authentication, there is now an early access program available.  I've just been added to the program and will report back after some testing regarding the longer PIN codes and access tokens.

FWIW...After re-authorizing my app and testing under the early access program, the authentication process works fine with no further code changes (as stated previously, I'm using PIN authentication).  The service now returns a longer PIN code (9 digits in the form xxxx-xxxx) a much longer access token, and refresh and authorization tokens of varying lengths.

FWIW...After re-authorizing my app and testing under the early access program, the authentication process works fine with no further code changes (as stated previously, I'm using PIN authentication). The service now returns a longer PIN code (9 digits in the form xxxx-xxxx) a much longer access token, and refresh and authorization tokens of varying lengths.

Well, that's good to know!! I thought there might be some minor changes required specifically to pass the query parameter ecobee_type=jwt when requesting the access/refresh tokens but it seems the following will take care of everything
"After December 1, 2020, all access tokens returned will be JWTs, regardless of whether or not the ecobee_type param is specified. The format for refresh tokens will also be changing. Please see here for more information."

Yes, agreed re: the ecobee_type param.  Not sure precisely what the transition plan is regarding already authorized apps though, i.e, whether they will continue to work as per the old authorization mechanism or will require re-authorization to get the longer PIN and JWT tokens.  I had to "force" re-authorization for my test app in order to see the changes, otherwise I still received the "older" style PIN/tokens.  I also found it curious that though the migration strategy statement states the PINs will be 10-characters or longer, they actually are only 9.

I think if you don't re-authorize your app will continue to work using the old style tokens
This is the documentation regarding ecoeee_type
"Optional. Specify "jwt" to have the API return access tokens as JWTs. If not specified, the API will return opaque access tokens."
Interesting thing I just saw, is that the refresh key using JWT will never expire (i.e. You won't ever need to refresh it)
"Refresh tokens will also never expire (they used to have an expiry of 1 year). It is important that refresh tokens are treated like secrets and are kept safe and secure."

Congrats to fowlerk for getting access to the trial server. I am still waiting for a response from the relevant people!!
The refresh key not expiring is of extremely limited relevance to most applications since (AFAIK) the access key still only lasts an hour, and (again AFAIK) you still get a new refresh key when you renew the access key - or is it now the same refresh key that is returned?


Unable to add members

The installation has been successful. I am unable to add members to database.
Please help!

Kindly share more details to troubleshoot / reproduce.

hello I have also been facing the same issue

I am unable to add new members from the add members form
When I mark an enquiry as a member, it does not reflect on the members list

how can I resolve this?

We are pushing some updates in the next couple of days that will fix the issue.

okay, thank you


Handle pytest 5.4 deprecation to use Node.from_parent

Fixes #26
Depends on https://github.com/ropez/pytest-describe/pull/25

In order to release this, I believe pytest-describe will need to officially drop support for pytest<5.4, which will in turn require dropping support for python<3.5.

To use this patch in your Poetry project, add the following to pyproject.toml:
[tool.poetry.dev-dependencies]

pytest-describe = { git = "https://github.com/jacebrowning/pytest-describe", branch = "pytest-5.4-support" }

Thank you! Dropping support for Python 2 would be even harsher than what I did in #25 though.

I wasn't totally sure when Node.from_parent() was introduced, but its introduction sets the minimum pytest version unless we want to get clever by checking for the existence of the method.

Maybe "use from_parent() except AttributeError: old way" will work?

There would also need to be changes to DescribeBlock.__init__(). Given that this warning only shows up with pytest>=5.4, it seems acceptable to me that the fix would require pytest>=5.4.

Ok, looked into this a bit more. How about this:
Remove the __init__ method alltogether, and create the following from_parent method instead:
    @classmethod
    def from_parent(cls, parent, obj):
        name = obj.__name__
        try:
            from_parent_super = super(DescribeBlock, cls).from_parent
        except AttributeError:  # PyTest < 5.4
            self = cls(name, parent)
        else:
            self = from_parent_super(parent, name=name)
        self._name = getattr(obj, '_mangled_name', name)
        self.funcobj = obj
        return self

Then, in pytest_pycollect_makeitem just return DescribeBlock.from_parent(collector, obj).

Thanks for looking into the API a bit more!
Maybe we should let @ropez decide? If they have limited bandwidth, perhaps trying to support anything other than the latest version of pytest puts too much on their plate? Dropping support for legacy Python also simplifies the build matrix and allows us to drop the legacy super() syntax.

Even then, in order to test libraries that still need to support a broad range of Python versions, it would be nice to publish one last official release that supports that broad version range, and only then remove the Python 2 and older Pytest support, simplify the code for Python 3, and maybe release that as version 1.0 or so. We must not forget to adapt "install_requires" and the classifiers in setup.py when doing that.

This has now been solved in with the alternative fix in 453aa9045b265e313f356f1492d8991c02a6aea6 that also provides backward compatibility, so we can close this now.


Organizations page

The exact desired UI could not be implemented, but the organization members were fetched as features and integrated into the UI.


Add logic for only compressing certain content types

Interesting article about what does and doesn't make sense to gzip: https://www.fastly.com/blog/new-gzip-settings-and-deciding-what-compress
We need to add logic to look at the response's content type and only compress the ones that deflate well (all forms of text, mostly).
/cc @tannernelson thoughts?

That's interesting. As long as the middleware is applied late enough in the chain we should have content-type information in the headers to help make this decision.

Hmm, is there a middleware which sees the response but can't see the content type yet? I thought the routes always return a fully defined response. But yeah, we can always choose a sane default (to not gzip unless we know the content type and it's a well compressible one)

If the response has var json: JSON? set, but hasn't gone through the JSONMiddleware yet, then it would appear the response is empty. The JSONMiddleware is what serializes the JSON to the body and sets the appropriate headers, Content-Length, Content-Type etc. And there are other middlewares that work like this, so gzipping would need to be toward the end of the line.

Yeah, makes sense. I guess we'd just need to document how to add that
middleware. Works for me great, I'd like to see more people gzipping soon.
On Mon, Aug 22, 2016 at 6:06 PM Tanner<EMAIL_ADDRESS>wrote:

If the response has var json: JSON? set, but hasn't gone through the
JSONMiddleware yet, then it would appear the response is empty. The
JSONMiddleware is what serializes the JSON to the body and sets the
appropriate headers, Content-Length, Content-Type etc. And there are
other middlewares that work like this, so gzipping would need to be toward
the end of the line.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/czechboy0/gzip-vapor/issues/2#issuecomment-241463026,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACFL6bQu2lbW6naMHMn3gkmBmr40Pwfqks5qickjgaJpZM4Jp5TC
.


Add more detail for note status for history statistics page

Add more detail to the statistics page for note status.

LGTM. Thanks!


Datepicker display issue

I have a datepicker displayed like this:

Is this a known issue or....and how i can fix it?
Thanks guys.

Same here. This issue started just after the update to version 0.11.0

Hey, me too!!

I just opened #1512 as a proposed fix

+1

+1

This was fixed a long time ago :grin:


mpd: add paused format string

I've been using this locally for a while and finally decided to submit this upstream, now that the MPD module doesn't segfault anymore :wink:. Let me know if there are any changes I need to make.

Nice!
Can you also update the documentation and wiki 😄

What should I say for its default? In its current implementation, it uses the value of format if nothing is specified. Does this look right?
*format-paused*: ++
    typeof: string ++
    default: value of *format* ++
    Information displayed when a song is paused.

I've got docs updated locally and will push if you think this looks good. I'll also update the wiki after we get this merged :wink:

*format-paused*: ++
	typeof: string ++
	This format is used when a when a song is paused.

Something like this :)

Should be good to go. It breaks away from the standard "Information shown when ___", but I don't really think that's an issue.

Thanks :)
Can you update this wiki page?
https://github.com/Alexays/Waybar/wiki/Module:-MPD


Upgrade to Go 1.21

What this PR does / why we need it:
Upgrade to Go 1.21.0.
Which issue(s) this PR fixes:

Fixes #
What type of PR is this?

/kind chore
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

Machine Controller is now built using Go 1.21.0

Documentation:

NONE

@xrstf can you override the pull-machine-controller-e2e-vmware-cloud-director, we are hitting https://github.com/kubermatic/machine-controller/issues/1619

/override pull-machine-controller-e2e-vmware-cloud-director
/approve
/lgtm


🐛 [firestore-bigquery-export] backfilling less than 300k docs took days and cost ~$200 USD

[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs for a specific extension in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
To file a bug against the Firebase Extensions platform, or for an issue affecting multiple extensions, please reach out to
Firebase support directly.

[REQUIRED] Step 2: Describe your configuration

Extension name: firestore-bigquery-export
Extension version: 0.1.46
Configuration values (redact info where appropriate):
Cloud Functions location
redacted
BigQuery Dataset location
redacted
BigQuery Project ID
redacted
Database ID
(default)
Collection path
occasions
Enable Wildcard Column field with Parent Firestore Document IDs (Optional)
false
Dataset ID
firestore_raw_export
Table ID
occasions_v2
BigQuery SQL table Time Partitioning option type (Optional)
none
BigQuery Time Partitioning column name (Optional)
createdAt
Firestore Document field name for BigQuery SQL Time Partitioning field option (Optional)
createdAt
BigQuery SQL Time Partitioning table schema field(column) type (Optional)
TIMESTAMP
BigQuery SQL table clustering (Optional)
Parameter not set
Maximum number of synced documents per second (Optional)
100
Backup Collection Name (Optional)
Parameter not set
Transform function URL (Optional)
Parameter not set
Use new query syntax for snapshots
no
Exclude old data payloads (Optional)
no
Import existing Firestore documents into BigQuery?
yes
Existing Documents Collection (Optional)
occasions
Use Collection Group query (Optional)
no
Docs per backfill
200
Cloud KMS key name (Optional)
Parameter not set

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
We installed the suggestion and set the preference to import existing records. The firestore database we imported from had <250K records. While importing, we saw a massive spike in firestore reads up to 45 million per hour. Our typically read volume is <10K per hour. We incurred a cost of ~$200 just from running this import.
Expected result
Bigquery database is created with minimal impact on read volumes
Actual result
45 million firestore reads per hour. 120 million reads total in a few hours.

Linking to the same bug someone else reported: https://github.com/firebase/extensions/issues/2000

Hey looking into this now, do you have any relevant cloud function logs/errors?

I believe this issue is caused by us using offset to paginate, I am working on an alternative approach.

Yes, see attached for the logs.
firestore-export-logs.docx
When do you think you'll have a fix in?
Also, what's the process for requesting a credit?

Hi - is there any update on this? Any other recommendations for streaming
firestore data to bigquery?
On Tue, Mar 26, 2024 at 3:52 AM Jacob Cable @.***>
wrote:

I believe this issue is caused by us using offset to paginate, I am
working on an alternative approach.
—
Reply to this email directly, view it on GitHub
https://github.com/firebase/extensions/issues/2003#issuecomment-2020109360,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIRPP65GMCX3WTHGSAQ6VTY2FAOTAVCNFSM6AAAAABFICKA3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQGEYDSMZWGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

You can still use the extension for streaming, this issue only affects backfilling which we disabled for now. Another solution that can backfill your existing data is to use the import script, which you can run locally.
You can reach out to Firebase support on this link.

Hi, software engineer from Firebase here.
Just wanted to chime in on this issue, we have turned off backfill so if you use the latest version you won't run into the issue, and as Mais explained above, the import script is the temporary work around.
That being said we are actively working on reworking the backfill implementation such that offset isn't used. Will follow up when that is pushed out.


Add sync primitives

This is a follow up PR for https://github.com/rust-lang/miri/pull/1284 that adds support for the missing synchronization primitives.
Sorry for flooding with PRs, but my internship is coming to an end and I need to get things out.
Fixes https://github.com/rust-lang/miri/issues/1419

:umbrella: The latest upstream changes (presumably #1354) made this pull request unmergeable. Please resolve the merge conflicts.

@RalfJung Please let me know when I should rebase.

Please let me know when I should rebase.

Let's do this after we are done with the review -- being able to check just the diff of what you do is quite convenient.

Looking good, all nits resolved. :) Thanks a lot!
Please rebase, and squash the niting in the end to a few commits. (No need to have a beautiful history but 66 commits is a bit much.)

It seems that 200ms is a too small range for a timeout.

Looking great, thank you so much. :)
@bors r+

:pushpin: Commit 34ddd775e8352c4905b56f183421902cdda9d100 has been approved by RalfJung

:hourglass: Testing commit 34ddd775e8352c4905b56f183421902cdda9d100 with merge bfe030dea4e777c6861e0e9e3704fc0b952576ad...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing bfe030dea4e777c6861e0e9e3704fc0b952576ad to master...

 After you've merged all your changes @vakaras, any chance you could do a little write-up to demonstrate what now works in miri?

I plan to write a blog post once my thesis is finally submitted (~2 weeks), mentioning all the things that landed in the last 6 months or so (panics, file system access, cross-target-execution, concurrency... there's probably more and there are some minor but notable things I still plan to do before the post) but of course I'd happily link to a more detailed write-up about the concurrency parts.  After you've merged all your changes @vakaras, any chance you could do a little write-up to demonstrate what now works in miri?

Not earlier than in the next three weeks because I need to get Prusti working again as soon as possible.


[V8] Account menu: synchronize header conditions with footer conditions

At the moment, the conditions to display the account menu in the header_required element and in the footer_required element are very different.
That implies for example that we always add the core/account asset if there's a logged in user (in header_required), but we don't actually use it.
Let's always use the same conditions.

Wrong PR, I'll submit a new one


Issue with Azure Container Apps (ACA) Limitation on Opening Multiple Ports

Issue Description
According to the documentation here, it is mentioned that we can open additional TCP ports on Azure Container Apps (ACA), with a maximum of 5 additional ports per app. However, when attempting to open multiple ports per app, I encountered a limitation where only one port per app is allowed.
Is there any solution to implement a solution in ACA to deploy apps that require multiple ports?
Example Scenario:
Consider the following Docker command as an example:
docker run -p 90:90 -p 310:310 -p 456:456 <image_name>:<version>

if you're using the cli, you can create such app on ACA using
properties:
  environmentId: '{Your Env Id}'
  configuration:
    ingress:
      # set `external: true` if you want to be able to access these ports from _outside_ the environment.
      # setting it to `external: false` means this is only available to apps running _inside_ the environment.
      external: false
      targetPort: 90
      exposedPort: 90
      transport: tcp
      allowInsecure: false
      additionalPortMappings:
        # you can have up to 5 additional port mappings in here
        - external: false
          targetPort: 310
          exposedPort: 310
        - external: false
          targetPort: 456
          exposedPort: 456
  template:
    containers:
      - name: my-app
        image: <image_name>:<version>
    scale:
      minReplicas: 1
      maxReplicas: 1

Then create your app using
az containerapp create \
    --name <app-name>
    --resource-group <resource-group> \
    --yaml /path/to/app.yaml # file with above content.

Great, I will try. I thought is only implemented for ARM/Bicep with api-version=2023-05-02-preview.
If I create the ACA from portal the api is 2022 and I can not update it after.
I tried to patch the existing ACA using a json config with no luck.
Updating an existing container ACA to expose multiple ports failed.
I will try the method you provided to create an ACA with multiple ports and also update the existing one.
Using Bicep with the latest version was with success.
I will test via CLI too and circle back.
Thanks 😊


zk patch

Codecov Report

Merging #201 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #201      +/-   ##
==========================================
+ Coverage   98.57%   98.57%   +<.01%
==========================================
  Files          73       73
  Lines        2875     2876       +1
==========================================
+ Hits         2834     2835       +1
  Misses         41       41

Impacted Files
Coverage Δ

...nds/compiler/etherlime-compile/compilerSupplier.js
77.86% <ø> (ø)
:arrow_up:

cli-commands/commands.js
99.44% <100%> (ø)
:arrow_up:

cli-commands/init/init.js
100% <100%> (ø)
:arrow_up:

cli-commands/zk-proof/generate-call.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8aa3c99...2409b43. Read the comment docs.