nomt backend: use bitbox DB for pages

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#242  👈
#241
#240
#239
#238
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gabriele-0201 and the rest of your teammates on  Graphite

Merge activity

Aug 12, 4:06 PM EDT: @rphmeier started a stack merge that includes this pull request via Graphite.


IBDesignable build fails when making a UIView of class Gauge

I am just trying to get a "Hello World" with GaugeKit.  Creating a CocoaPod by following guide at (https://developerslogblog.wordpress.com/2017/05/14/swiff-3-reusable-components-using-xib-files-and-the-interface-builder/)
When I add a UIView to my storyboard (or .xib) that is IBDesignable I get "build failed."

When adding to the storyboard and attempting to build I see a #selector issue: "Argument of '#selector' refers to instance method 'updateProgress' that is not exposed to Objective-C"

Running Xcode 9.2, Swift 3.x.  My project commit that holds this error: (https://github.com/jfosterdavis/ZMUtilityAppFramework/commit/f059d2bfc6cb9533140325313a037a6ec3959554)

fixed too :+1:


Running app locally PUT/POST APIs come as 404

Hi @johnpapa/@yooakim,
Thanks for the sample work for Static Web App files.
I'm using it both for honing my skills on Angular as well as working the Static Web App functions.
Running the app locally... all GET HTTP verbs work fine, but PUT/POST returns 404.
not sure, I am missing something in the routing setup. I ran it per instruction though.
Thank you for  help,
Mohammad

The authorization in this app restricts modifications to those with the role you designate. By default, I made these not allowed. You could remove those in the routes.json. For more details, see  Docs


Localizational mistakes on the Home page for unregistered user

Steps to reproduce:

Go to the https://ita-social-projects.github.io/GreenCityClient/#/welcome
Pay attention to the mistakes, shown in the attachments

Expected Result:
All content, titles and buttons should be appropriately translated in the chosen language
Actual Result:
'localization1' file - 'Введіть ваш email' is not translated into Eng
'localization2' file - Content in 'Eco-advices' block is not translated into Eng and Рус
'localization3' file -  'Введіть ваш email' is not translated into Рус. A grammar mistake in the phrase 'интересные новости' and there is a mistake in the word 'чтобы'
Environment: Chrome Версія 80.0.3987.122 (Розробка) (64-розрядна версія) Windows7 Ultima

![localization3]

#352

Not fixed in full
'localization1' and 'localization3' files - fixed
'localization2' file - Content in 'Eco-advices' block is not translated into Eng and Рус - not fixed.
Windows 10 x64, Mozilla Firefox 76.0 (64-bit)

Eco-advises changed to Tips & Tricks and still not added, grammar mistakes and translations fixed

'localization2' file - Content in 'Eco-advices' block is not translated into Eng and Рус


Feature Request - Offset timing of chained tweens

It would be awesome to be able to offset the timing of chained tweens, for example, tween2 starts 0.3 seconds before tween1 ends.

Thank you for taking the time to open this issue. However, official support for Phaser 2 has now ended as we focus on preparing Phaser 3 for beta release. In a bid to keep the project tidy, and avoid confusion, we are closing all v2 related issues.
This does not mean your issue won't be looked-at. In November 2016 the Phaser CE (Community Edition) project began. The aim of Phaser CE was to allow the community to continue v2 development. Since then it has gained significant traction, with many updates and releases.
If you are still interested in having your issue investigated we strongly recommend testing the latest Phaser CE release. And only if the problem persists, opening an issue on the Phaser CE repo.


[bug] download wix failed

Describe the bug
when i run cargo tauri build and downloading wix,throw a network error.it seems that connetion failed,but when i use curl,it  works.
ternimal report
cargo tauri build
     Running beforeBuildCommand `pnpm build`

><EMAIL_ADDRESS>build D:\CodeRepository\__React__STACK\Electron\tauri-app
> vue-tsc --noEmit && vite build

    Finished release [optimized] target(s) in 0.48s
        Info Verifying wix package
 Downloading https://github.com/wixtoolset/wix3/releases/download/wix3112rtm/wix311-binaries.zip
       Error failed to bundle project: `https://github.com/wixtoolset/wix3/releases/download/wix3112rtm/wix311-binaries.zip: Connection Failed: Connect error: 由于连接方在一段时间后没有正确答复
或连接的主机没有反应，连接尝试失败。 (os error 10060)`

Reproduction
No response
Expected behavior
No response
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 120.0.2210.144
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.74.0 (79e9716c9 2023-11-13)
    ✔ cargo: 1.74.0 (ecb9851af 2023-10-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.16.0
    - pnpm: 8.6.11
    - yarn: 1.22.21
    - npm: 9.7.2

[-] Packages
    - tauri-build [RUST]: 1.5.1
    - tao [RUST]: 0.16.6
    - tauri-cli [RUST]: 1.5.7
    - @tauri-apps/api [NPM]: 1.4.0 (outdated, latest: 1.5.3)
    - @tauri-apps/cli [NPM]: 1.5.7 (outdated, latest: 1.5.9)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite

Stack trace
No response
Additional context
No response

Looks like a duplicate of https://github.com/tauri-apps/tauri/issues/7338. There are english and chinese comments so i hope there's something helpful for you too. Basically it should be issues with proxies.


Minor issues on VnV plan

[ ] Section 2 The external link to Abbreviations and Acronyms did not work for me. please check the hyperlink.
[ ] Section 4 should be a roadmap to the following subsections. You have written external data for the 4.7 section which is a software validation plan. Maybe I'm wrong but I think it is a little ambiguous.
[ ] The caption of Table 1: "Table of Teammates and Their Roles". I think only the first letter should be capitalized: Table of teammates and their roles.
[ ] section 4.4 I'm not sure someone outside the university knows about Rubric. Considering that you couldn't find a link for that maybe it is better to not mention it?

The external link assumes that you have the SRS in the filepath ../SRS/SRS.pdf (like is in the repo). If you try that, it should work, but if not, I included a reference to the SRS by each of these external links in the case of a hyperlink not working.
I'll look into the rest of the issues when I have the chance!

The fourth point was handled by 7aa2d25cb (added links to the Avenue rubric).


[Enhancement] Remove conv_cfg argument in dcgan

Since conv_cfg cannot make any difference easily, we just remove this argument for clear and simple usage.

Codecov Report

Merging #75 (423e87a) into master (c7d36e5) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #75      +/-   ##
==========================================
- Coverage   75.80%   75.75%   -0.06%
==========================================
  Files         117      117
  Lines        7718     7718
  Branches     1423     1423
==========================================
- Hits         5851     5847       -4
- Misses       1494     1496       +2
- Partials      373      375       +2

Flag
Coverage Δ

unittests
75.75% <ø> (-0.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...els/architectures/dcgan/generator_discriminator.py
93.68% <ø> (ø)

...chitectures/stylegan/generator_discriminator_v1.py
88.70% <0.00%> (-1.13%)
:arrow_down:

mmgen/models/architectures/stylegan/mspie.py
90.59% <0.00%> (-1.00%)
:arrow_down:

...chitectures/stylegan/generator_discriminator_v2.py
86.66% <0.00%> (ø)

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 c7d36e5...423e87a. Read the comment docs.


Player Track confused by Duty Recorder

When viewing a Duty Recorder recording (recorded via A Realm Recorded but I suspect this applies to standard duty recordings too), it will still recognize each player as who they are, but think that their name was changed to their job, for example Gunbreaker, and it will show name/world change notifications to that effect. It will also error when trying to add those players to the visibility plugin with the error Whitelist: 'PlayerTrack' is not a valid world name..

This is a weird one, thanks for reporting!


input组件文档中参数错误

What problem does this feature solve?
文档里写的是#addonAfter  实际是 #addOnAfter。
What does the proposed API look like?
文档和例子保持一致

will be fixed in next version.

please use version 0.7.0 now.


Unable to connect to Chrome debug port: 37095

I installed Flutter and VS Code in the following way:
$ sudo snap install --classic code
$ sudo snap install --classic flutter
$ tail -n 1 ~/.bashrc
export CHROME_EXECUTABLE="/usr/bin/chromium"

$ flutter doctor -v
[✓] Flutter (Channel stable, 2.2.1, on Linux, locale en_AU.UTF-8)
    • Flutter version 2.2.1 at /home/debian/snap/flutter/common/flutter
    • Framework revision 02c026b03c (4 months ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/chromium

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Chromium 90.0.4430.212 built on Debian 11.0, running on Debian 11.0

! Doctor found issues in 2 categories.

I can start the Flutter app in terminal.

However, under VS code I get Unable to connect to Chrome debug port: 37095

What did I miss?

Hi @mictadlo
I can't reproduce it on the latest Flutter stable channel.
Can you please upgrade to the latest  stable and try again
Execute the following commands to upgrade
flutter channel stable
flutter upgrade --force
flutter doctor -v
Also, make sure your Flutter VS Code is up to date

Hi @TahaTesser ,
I execucted all the commands but the  problem still remained.
$ flutter channel stable
Switching to flutter channel 'stable'...
git: From https://github.com/flutter/flutter
git:  + 02c026b03c...4cc385b4b8 stable                  -> origin/stable  (forced update)
git:  + b22742018b...400608f101 beta                    -> origin/beta  (forced update)
git:  + f9c825981c...f2903d3da5 dev                     -> origin/dev  (forced update)
git:  * [new branch]            dnfield-patch-1         -> origin/dnfield-patch-1
git:  + 42c3e45fb7...1e436a4460 experimental_skshaper   -> origin/experimental_skshaper  (forced update)
git:    02c026b03c..07d2f6f4b1  flutter-2.2-candidate.10 -> origin/flutter-2.2-candidate.10
git:  * [new branch]            flutter-2.3-candidate.19 -> origin/flutter-2.3-candidate.19
git:  * [new branch]            flutter-2.3-candidate.20 -> origin/flutter-2.3-candidate.20
git:  * [new branch]            flutter-2.3-candidate.21 -> origin/flutter-2.3-candidate.21
git:  * [new branch]            flutter-2.3-candidate.22 -> origin/flutter-2.3-candidate.22
git:  * [new branch]            flutter-2.3-candidate.23 -> origin/flutter-2.3-candidate.23
git:  * [new branch]            flutter-2.3-candidate.24 -> origin/flutter-2.3-candidate.24
git:  * [new branch]            flutter-2.3-candidate.25 -> origin/flutter-2.3-candidate.25
git:  * [new branch]            flutter-2.3-candidate.26 -> origin/flutter-2.3-candidate.26
git:  * [new branch]            flutter-2.3-candidate.27 -> origin/flutter-2.3-candidate.27
git:  * [new branch]            flutter-2.3-candidate.28 -> origin/flutter-2.3-candidate.28
git:  * [new branch]            flutter-2.4-candidate.0 -> origin/flutter-2.4-candidate.0
git:  * [new branch]            flutter-2.4-candidate.1 -> origin/flutter-2.4-candidate.1
git:  * [new branch]            flutter-2.4-candidate.2 -> origin/flutter-2.4-candidate.2
git:  * [new branch]            flutter-2.4-candidate.3 -> origin/flutter-2.4-candidate.3
git:  * [new branch]            flutter-2.4-candidate.4 -> origin/flutter-2.4-candidate.4
git:  * [new branch]            flutter-2.4-candidate.5 -> origin/flutter-2.4-candidate.5
git:  * [new branch]            flutter-2.4-candidate.6 -> origin/flutter-2.4-candidate.6
git:  * [new branch]            flutter-2.4-candidate.7 -> origin/flutter-2.4-candidate.7
git:  * [new branch]            flutter-2.4-candidate.8 -> origin/flutter-2.4-candidate.8
git:  * [new branch]            flutter-2.5-candidate.0 -> origin/flutter-2.5-candidate.0
git:  * [new branch]            flutter-2.5-candidate.1 -> origin/flutter-2.5-candidate.1
git:  * [new branch]            flutter-2.5-candidate.2 -> origin/flutter-2.5-candidate.2
git:  * [new branch]            flutter-2.5-candidate.3 -> origin/flutter-2.5-candidate.3
git:  * [new branch]            flutter-2.5-candidate.4 -> origin/flutter-2.5-candidate.4
git:  * [new branch]            flutter-2.5-candidate.5 -> origin/flutter-2.5-candidate.5
git:  * [new branch]            flutter-2.5-candidate.6 -> origin/flutter-2.5-candidate.6
git:  * [new branch]            flutter-2.5-candidate.7 -> origin/flutter-2.5-candidate.7
git:  * [new branch]            flutter-2.5-candidate.8 -> origin/flutter-2.5-candidate.8
git:  * [new branch]            flutter-2.5-candidate.9 -> origin/flutter-2.5-candidate.9
git:  * [new branch]            flutter-2.6-candidate.0 -> origin/flutter-2.6-candidate.0
git:  * [new branch]            flutter-2.6-candidate.1 -> origin/flutter-2.6-candidate.1
git:  * [new branch]            flutter-2.6-candidate.10 -> origin/flutter-2.6-candidate.10
git:  * [new branch]            flutter-2.6-candidate.2 -> origin/flutter-2.6-candidate.2
git:  * [new branch]            flutter-2.6-candidate.3 -> origin/flutter-2.6-candidate.3
git:  * [new branch]            flutter-2.6-candidate.4 -> origin/flutter-2.6-candidate.4
git:  * [new branch]            flutter-2.6-candidate.5 -> origin/flutter-2.6-candidate.5
git:  * [new branch]            flutter-2.6-candidate.6 -> origin/flutter-2.6-candidate.6
git:  * [new branch]            flutter-2.6-candidate.7 -> origin/flutter-2.6-candidate.7
git:  * [new branch]            flutter-2.6-candidate.8 -> origin/flutter-2.6-candidate.8
git:  * [new branch]            flutter-2.6-candidate.9 -> origin/flutter-2.6-candidate.9
git:    58ac7b85d9..a8a27635a1  master                  -> origin/master
git:  * [new branch]            pull-87493              -> origin/pull-87493
git:  * [new branch]            revert-81813-ExpansionPanelList_elevation -> origin/revert-81813-ExpansionPanelList_elevation
git:  * [new branch]            revert-82570-patch-1    -> origin/revert-82570-patch-1
git:  * [new branch]            revert-84342-flutter-engine-flutter-autoroll-a31192cf-636b-427f-821f-ace70b4be488-1623321347 -> origin/revert-84342-flutter-engine-flutter-autoroll-a31192cf-636b-427f-821f-ace70b4be488-1623321347
git:  * [new branch]            revert-86171-revert-83924-textTheme -> origin/revert-86171-revert-83924-textTheme
git:  * [new branch]            revert-86198-deprecate_appbar_backwards_compatibility_flag -> origin/revert-86198-deprecate_appbar_backwards_compatibility_flag
git:  * [new branch]            revert-89885-scrollVelocity -> origin/revert-89885-scrollVelocity
git:  * [new branch]            revert-skia-to-82d4c12d -> origin/revert-skia-to-82d4c12d
git:  * [new branch]            test                    -> origin/test
git:  * [new branch]            test2                   -> origin/test2
git:  * [new branch]            timsneath-accent-deprecations -> origin/timsneath-accent-deprecations
git:  * [new branch]            zanderso-patch-1        -> origin/zanderso-patch-1
git:  * [new tag]               2.3.0-16.0.pre          -> 2.3.0-16.0.pre
git:  * [new tag]               2.3.0-24.1.pre          -> 2.3.0-24.1.pre
git:  * [new tag]               2.4.0-0.0.pre           -> 2.4.0-0.0.pre
git:  * [new tag]               2.4.0-4.0.pre           -> 2.4.0-4.0.pre
git:  * [new tag]               2.4.0-4.2.pre           -> 2.4.0-4.2.pre
git:  * [new tag]               2.5.0                   -> 2.5.0
git:  * [new tag]               2.5.0-1.0.pre           -> 2.5.0-1.0.pre
git:  * [new tag]               2.5.0-5.0.pre           -> 2.5.0-5.0.pre
git:  * [new tag]               2.5.0-5.1.pre           -> 2.5.0-5.1.pre
git:  * [new tag]               2.5.0-5.2.pre           -> 2.5.0-5.2.pre
git:  * [new tag]               2.5.0-5.3.pre           -> 2.5.0-5.3.pre
git:  * [new tag]               2.5.0-6.0.pre           -> 2.5.0-6.0.pre
git:  * [new tag]               2.6.0-0.0.pre           -> 2.6.0-0.0.pre
git:  * [new tag]               2.6.0-5.1.pre           -> 2.6.0-5.1.pre
git:  * [new tag]               2.6.0-5.2.pre           -> 2.6.0-5.2.pre
git:  * [new tag]               2.2.2                   -> 2.2.2
git:  * [new tag]               2.2.3                   -> 2.2.3
git:  * [new tag]               2.3.0-24.0.pre          -> 2.3.0-24.0.pre
git:  * [new tag]               2.4.0-4.1.pre           -> 2.4.0-4.1.pre
git:  * [new tag]               2.6.0-5.0.pre           -> 2.6.0-5.0.pre
git: Already on 'stable'
git: Your branch and 'origin/stable' have diverged,
git: and have 13 and 1846 different commits each, respectively.
git:   (use "git pull" to merge the remote branch into yours)
Successfully switched to flutter channel 'stable'.
To ensure that you're on the latest build from this channel, run 'flutter upgrade'
(base) debian@appdev:/mnt/OneTB/projects/flutter/testapp$ flutter upgrade --force
Upgrading Flutter to 2.5.0 from 2.2.1 in /home/debian/snap/flutter/common/flutter...
Downloading Dart SDK from Flutter engine f0826da7ef2d301eb8f4ead91aaf026aa2b52881...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0  221M    0  6971    0     0   8846      0  7:17:20 --:--:--  7:17:20  8835
  4  221M    4 10.2M    0     0  5044k      0  0:00:44  0:00:02  0:00:42 5044k
 14  221M   14 32.2M    0     0  10.6M      0  0:00:20  0:00:03  0:00:17 10.6M
 28  221M   28 64.1M    0     0  16.0M      0  0:00:13  0:00:03  0:00:10 16.0M
 43  221M   43 96.0M    0     0  19.5M      0  0:00:11  0:00:04  0:00:07 19.5M
 47  221M   47  104M    0     0  17.7M      0  0:00:12  0:00:05  0:00:07 20.5M
 68  221M   68  152M    0     0  21.7M      0  0:00:10  0:00:07  0:00:03 28.9M
 83  221M   83  184M    0     0  23.7M      0  0:00:09  0:00:07  0:00:02 32.1M
100  221M  100  221M    0     0  27.0M      0  0:00:08  0:00:08 --:--:-- 37.4M
Building flutter tool...

Upgrading engine...
Downloading android-arm-profile/linux-x64 tools...               1,522ms
Downloading android-arm-release/linux-x64 tools...               1,030ms
Downloading android-arm64-profile/linux-x64 tools...             1,015ms
Downloading android-arm64-release/linux-x64 tools...               359ms
Downloading android-x64-profile/linux-x64 tools...                 882ms
Downloading android-x64-release/linux-x64 tools...                 839ms
Downloading android-x86 tools...                                 1,576ms
Downloading android-x64 tools...                                 2,247ms
Downloading android-arm tools...                                 1,278ms
Downloading android-arm-profile tools...                           538ms
Downloading android-arm-release tools...                           412ms
Downloading android-arm64 tools...                                 820ms
Downloading android-arm64-profile tools...                         568ms
Downloading android-arm64-release tools...                         492ms
Downloading android-x64-profile tools...                           564ms
Downloading android-x64-release tools...                           467ms
Downloading android-x86-jit-release tools...                       631ms
Downloading Web SDK...                                           2,843ms
Downloading package sky_engine...                                  321ms
Downloading flutter_patched_sdk tools...                           457ms
Downloading flutter_patched_sdk_product tools...                   424ms
Downloading linux-x64 tools...                                   2,146ms
Downloading linux-x64/font-subset tools...                         309ms

Flutter 2.5.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 4cc385b4b8 (9 days ago) • 2021-09-07 23:01:49 -0700
Engine • revision f0826da7ef
Tools • Dart 2.14.0

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.5.0, on Debian GNU/Linux 11 (bullseye) 5.10.0-8-amd64, locale en_AU.UTF-8)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] VS Code
[✓] Connected device (1 available)

! Doctor found issues in 2 categories.

$ flutter doctor -v
[✓] Flutter (Channel stable, 2.5.0, on Debian GNU/Linux 11 (bullseye) 5.10.0-8-amd64, locale en_AU.UTF-8)
    • Flutter version 2.5.0 at /home/debian/snap/flutter/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4cc385b4b8 (9 days ago), 2021-09-07 23:01:49 -0700
    • Engine revision f0826da7ef
    • Dart version 2.14.0

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/chromium

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] VS Code
    • VS Code at /snap/code/current
    • Flutter extension version 3.26.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Chromium 90.0.4430.212 built on Debian 11.0, running on Debian 11.0

! Doctor found issues in 2 categories.

What did I miss?

P.S. I use Flutter v3.26.0 for VS code.

HI @mictadlo
This might a bug with just VS Code. Do you mind giving Android Studio plugin try? Also from CLI, flutter run -d chrome?
Thank you

Hi @TahaTesser,
It works with flutter run -d chrome and I opened an issue on VS Code https://github.com/microsoft/vscode/issues/133428

Hi @mictadlo
Thanks for reporting it at Dart Code
Given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you

Could we please open it again because on the Dart - Code it looks like it was solved?

I responded at https://github.com/Dart-Code/Dart-Code/issues/3568#issuecomment-922752858, although I don't think it's a Dart-Code issue - I think it might either be a proxy issue or Snap-related. There's an open issue that seems similar here:
https://github.com/flutter/flutter/issues/73743
There are comments there suggesting mixing Snap and non-Snap installs of VS Code/Flutter/Chromium might cause issues, eg. this comment says using Snap for all works, and this comment says using non-Snap for all works.
I'm not familiar enough with Snap to understand why mixing Snap/non-Snap apps may have issues, but it's worth trying to see if that resolves the problem.

@mictadlo
To be sure, can you please try manual installation and remove the snap installation
snap remove --purge flutter
rm -rf ~/snap/flutter

It works now after I did:
sudo apt remove chromium
sudo snap install --classic chromium
$ tail -n 1 ~/.bashrc
export CHROME_EXECUTABLE="/snap/bin/chromium"

(base) debian@appdev:/mnt/OneTB/projects/flutter/testapp$ echo $HTTP_PROXY

(base) debian@appdev:/mnt/OneTB/projects/flutter/testapp$ echo $NO_PROXY

(base) debian@appdev:/mnt/OneTB/projects/flutter/testapp$

Now is Flutter, VS Code and Chromium from Snap. Is it better to have everything from Snap or from deb?
Thank you in advance,
Michal

Glad to hear!

Is it better to have everything from Snap or from deb?

I don't know enough about Snap to know the answer to this, but I think as long as you're consistent and things seem to be working, there's probably not much difference.


[FEAT] Custom Error Page 404

I will design an Error Page for calls or redirecting to pages which do not exist.
Hello!
I am Viraj Chandra, a proud contributor at GSSoC '23. I would like to the contribute to this project by designing an Error Page for calls or redirecting to pages which do not exist.
Things I will be doing as of now:

[ ]  Designing the error page 404

@rohansx  Please Assign me this.

@virajchandra51 go ahead

@virajchandra51 go ahead

Can you please assign me this issue under GSSOC'23 . Will make it quickly.

If viraj fails to complete the task within 5 days then only @parthpathakpp1 I can assign you the task. Meanwhile you can check other issues or you can create other issues

This part is done


Add notes for --runInBand in the CLI.md and Troubleshooting.md

Summary
Add new information to jest documentation for run in band. Potential for issue #15216
@bregenspan, does this seem like an appropriate update to the documentation?

@BonsaixPanda based on discussion in https://github.com/jestjs/jest/issues/15216#issuecomment-2289642057 , this looks to definitely be a bug, so correct resolution is releasing the fix (which it appears is already in the latest source, just not released yet).


"self" not being passed as arg, so stripping other args

I kept getting the same cache results returned until I made the following change:
    if "result_to_cache" in kwargs:
        kwargs = {k: v for k, v in kwargs.items() if k != "result_to_cache"}
    elif ignore_self:
        if args[0] == "self":
            args = args[1:]

It seems like self wasn't getting passed as an arg to _get_cache_key, so it was stripping the other relevant args, meaning the hash was based off of "", making the first cache hit return no matter what.
Python version: 3.8.16

@joel-aws this is fixed in the final release (v0.4.0). Because the functionality is now supported directly in cachier I've deprecated this wrapper as it's no longer beneficial. Cachier should be used directly from now on.


[3.0]Add mesh rule route

The branch of 0.2.0 is master-0.2.0. If your PR is to solve the problem of 0.2.0, please submit the PR to it.
Please do not create a Pull Request without creating an issue first.
What is the purpose of the change
Support dubbo 3.0 mesh rule route.
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist.
[ ] Run `mvn clean compile --batch-mode -DskipTests=false -Dcheckstyle.skip=false -Drat.skip=false -Dmaven.javadoc.skip=true to make sure basic checks pass.

Codecov Report

Merging #789 (de02071) into develop-for-dubbo-3.x (021c3f5) will decrease coverage by 0.41%.
The diff coverage is 12.15%.

@@                     Coverage Diff                     @@
##             develop-for-dubbo-3.x     #789      +/-   ##
===========================================================
- Coverage                    20.36%   19.94%   -0.42%
- Complexity                     331      359      +28
===========================================================
  Files                           97      129      +32
  Lines                         3885     4287     +402
  Branches                       616      668      +52
===========================================================
+ Hits                           791      855      +64
- Misses                        3018     3355     +337
- Partials                        76       77       +1

Flag
Coverage Δ

unit
19.94% <12.15%> (-0.42%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

.../org/apache/dubbo/admin/common/util/Constants.java
0.00% <ø> (ø)

.../apache/dubbo/admin/model/store/mesh/BaseRule.java
0.00% <0.00%> (ø)

...bbo/admin/model/store/mesh/VsDestinationGroup.java
0.00% <0.00%> (ø)

...store/mesh/destination/ConnectionPoolSettings.java
0.00% <0.00%> (ø)

.../model/store/mesh/destination/DestinationRule.java
0.00% <0.00%> (ø)

...el/store/mesh/destination/DestinationRuleSpec.java
0.00% <0.00%> (ø)

...bbo/admin/model/store/mesh/destination/Subset.java
0.00% <0.00%> (ø)

...dmin/model/store/mesh/destination/TCPSettings.java
0.00% <0.00%> (ø)

...min/model/store/mesh/destination/TcpKeepalive.java
0.00% <0.00%> (ø)

...in/model/store/mesh/destination/TrafficPolicy.java
0.00% <0.00%> (ø)

... and 58 more

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 021c3f5...de02071. Read the comment docs.


3 same slots never match

How to i programmatically match 3 same slots ?

This is the code that checks for a winning combination of 3 emoji in the Slot machine:
        if (dataArray[0][emoji0] == dataArray[1][emoji1]
         && dataArray[1][emoji1] == dataArray[2][emoji2]) {
            labelResult.text = K.win
            winSound.play()
        } else {
            labelResult.text = K.lose
        }

The if-statement is checking that the first and second emojis are equal and then checking that the second and third emojis are also equal.


buildFHSUserEnvBubblewrap: add etcdFiles argument

Description of changes
This commit fix a bug using buildFHSUserEnvBubblewrap during nix build.
In the build sandbox, only passwd group hosts exist in /etcd folder but bubblewrap tries to --ro-bind-try multiple files in the default list.
Most of them would not cause problem except ssl/certs.
readlink would return an error so --ro-bind-try $(${coreutils}/bin/readlink -f /etc/ssl/certs) /etc/ssl/certs became --ro-bind-try /etc/ssl/certs instead of --ro-bind-try /etc/ssl/certs /etc/ssl/certs. The missing argument would break all the binds afterwards.
We could fix the issue by giving a default return for readlink but I think moving the etcd file list to an argument could cover more use cases.

Bind only limited files during build process
Bind /etc/{kubernetes,cni} for kubelet running in FHS
Bind more custom configuration files when user is using nix as a package manager in other linux distros.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Closing this as stale


Is this behaviour intended?

When testfixtures is imported unittest.mock is accessible without having to explicitly import unittest.mock:
import unittest
import sys

import testfixtures

class Test(unittest.TestCase):
    @unittest.mock.patch('sys.version_info', (2,7,0))
    def test_version(self):
        assert(sys.version_info < (3,0,0))

This should be throwing a AttributeError: module 'unittest' has no attribute 'mock' but importing testfixtures blocks this.
Also, up to testfixtures==3.0.2, the above test fails as expected.

I'm not sure why this would be, but what would you like to have happen?

I'm not sure why this would be, but what would you like to have happen?

unittest.mock shouldn't be in the global namespace because of testfixtures without it being imported explicitly.
Here's an example of how this is potentially bad: https://github.com/coala/coala-bears/issues/2862

unittest.mock isn't in the global namespace. unittest.mock is a module in the unittest package. Once a module has been imported anywhere in the python interpreter, it is available as an attribute of its containing package:
>>> import unittest
>>> unittest.mock
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'unittest' has no attribute 'mock'
>>> def a_function():
...     import unittest.mock
...
>>> a_function()
>>> unittest.mock
<module 'unittest.mock' from '.../unittest/mock.py'>

I tried to follow coala/coala-bears#2862 but, honestly, this looks like a lot of conjecture based around a lack of understanding around python. I don't know what coalaBearTest.py and the coalaBearTest class are supposed to represent, but the names alone suggest a lack of familiarity with Python.
Now, importing testfixtures will import unittest.mock and the mock backport, if it's available, as part of providing comparison for Mock objects. I'd be surprised if any code should fail because a module that is present is imported. This certainly isn't "funky", and I doubt pytest is doing any "magic" in this area.
Just to check you're aware: unittest.mock does not exist in Python 2, it only exists in Python 3. If your code needs to use mock on both Python 2 and 3, then you'll need to conditionally rely on the mock backport, which will require different import statements.


Importing circuits from bellman

Hello from the Filecoin team!
We would like to be able to use this library to ship a pure go version of filecoin that does not need to depend on bellman. We have existing circuits defined in bellman, but i'm not sure what the best way to go about using gnark to verify their outputs is.

Hello 👋
Probably need a bit more context on that one; if you switch to gnark do you intend to use bellman in the network, in another implementation? If not (ie you don’t need full interopability), then the short answer is likely to rewrite the circuits in gnark, we have a new release coming soon which should make that straightforward unless you need very fancy crypto primitives in your circuits. That would also offer the advantage to have the circuit code in pure Go, which we aim to be compatible with other proof systems than Groth16.
Now for the longer answer, the flow for both library is similar:

frontend (circuit code)  -> R1CS
setup (R1CS)  -> proving key, verifying key
prove (R1CS, proving key, witness)  -> proof
verify (verifying key, proof, public part of the witness) -> ok / nok.

The hard part of the interopability is the R1CS. There is no guarantees that gnark and bellman will express the circuit code into the same set of rank 1 constraints. Most importantly, solving this rank 1 constraint system (which happens during proof generation, to generate “circuit wire values” from the witness), is done in a very different way, that’s library-specific.
Verifying bellman-generated proof with gnark should be possible without too much trouble, as it does not depend on the R1CS (but is not currently implemented)

Yeah, the idea is that (at least at first) we would keep using bellman on the proving side (in the miner software) and verify proofs on the 'full node' side of things. So, verifying a proof made in bellman with gnark.
Beyond that, given your increased proving perf over bellman, I would eventually like to be able to generate the proofs in go, but thats going to be a lot more work because all the surrounding calling code is also in rust.

Noted, created #30 , likely not going to be implemented in the coming weeks but will ping you when we do :-) .

Much appreciated! Thanks!


Restrict logging of errors with verbosity level

Allow control errors logging with PDFJS.verbosity level

Can't we simplify this a lot by keeping a similar structure as https://github.com/mozilla/pdf.js/blob/fa0f09bcf02581689e80e612c28536787f37c7d3/src/shared/util.js#L196 ? I see no need for another fuction and the bindings...

@timvandermeij
In my opinion this code looks much more elegant
// Fatal errors.
function err(fn) {
  if (PDFJS.verbosity >= PDFJS.VERBOSITY_LEVELS.errors) {
    fn();
  }
}

// Fatal errors that should trigger the fallback UI and halt execution by
// throwing an exception.
function error(msg) {
  // If multiple arguments were passed, pass them all to the log function.
  if (arguments.length > 1) {
    var logArguments = ['Error:'];
    logArguments.push.apply(logArguments, arguments);
    err(console.log.apply.bind(console.log, console, logArguments));
    // Join the arguments into a single string for the lines below.
    msg = [].join.call(arguments, ' ');
  } else {
    err(console.log.bind(console, 'Error: ' + msg));
  }
  err(console.log.bind(console, backtrace()));
  UnsupportedManager.notify(UNSUPPORTED_FEATURES.unknown);
  throw new Error(msg);
}

than this one
// Fatal errors that should trigger the fallback UI and halt execution by
// throwing an exception.
function error(msg) {
  // If multiple arguments were passed, pass them all to the log function.
  if (arguments.length > 1) {
    var logArguments = ['Error:'];
    logArguments.push.apply(logArguments, arguments);
    if (PDFJS.verbosity >= PDFJS.VERBOSITY_LEVELS.errors) {
      console.log.apply(console, logArguments);
    }
    // Join the arguments into a single string for the lines below.
    msg = [].join.call(arguments, ' ');
  } else {
    if (PDFJS.verbosity >= PDFJS.VERBOSITY_LEVELS.errors) {
      console.log('Error: ' + msg);
    }
  }
  if (PDFJS.verbosity >= PDFJS.VERBOSITY_LEVELS.errors) {
    console.log(backtrace());
  }
  UnsupportedManager.notify(UNSUPPORTED_FEATURES.unknown);
  throw new Error(msg);
}

Please, let me now, which you prefer.

Please, let me now, which you prefer.

Neither solution above look good. Can you review calls of error() function and make it as a single argument function (similar to info/warn)? If multiple arguments are used, make it something like error(formatString("test", 1)) and add an utility function formatString.
Currently, the patch contains err() which is not really useful by itself.

Can you review calls of error() function and make it as a single argument function (similar to info/warn)?

A very quick look through the code-base seem to indicate that no caller of error passes in more than one argument, but a thorough review is obviously necessary.
A fair number of callers actually pre-concatenate strings themselves, before calling error, so I fully support the idea of changing error to only accept a single argument.

@yurydelendik , @timvandermeij , @Snuffleupagus Reviewed code and found no caller with multiple arguments. Changed code to simple
// Fatal errors that should trigger the fallback UI and halt execution by
// throwing an exception.
function error(msg) {
  if (PDFJS.verbosity >= PDFJS.VERBOSITY_LEVELS.errors) {
    console.log(msg);
    console.log(backtrace());
  }
  UnsupportedManager.notify(UNSUPPORTED_FEATURES.unknown);
  throw new Error(msg);
}

multiple console logs for separate lines. Or can be done with "\n".

@andrewdacenko Please squash the commits into one, see: https://github.com/mozilla/pdf.js/wiki/Squashing-Commits.

@Snuffleupagus Done.
@timvandermeij , @yurydelendik thanks for your attention )

/botio test

/botio-windows test

Thanks for the patch!


np.polyfit() error in EarthRef JupyterHub environment

The MPMS notebooks that use np.polyfit() are running fine locally for me, but are causing this issue on the EarthRef JupyterHub (perhaps needs an updated environment?).
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/opt/tljh/user/lib/python3.6/site-packages/ipywidgets/widgets/interaction.py in observer(change)
     77         with out:
     78             clear_output(wait=True)
---> 79             f(**kwargs)
     80             show_inline_matplotlib_plots()
     81     for k,w in controls.items():

~/rockmag/PmagPy-RockmagPy-notebooks-2144031/rockmag.py in <lambda>(background_temp_range, excluded_temp_range, poly_deg)
    543             background_temp_range[0], background_temp_range[1],
    544             excluded_temp_range[0], excluded_temp_range[1],
--> 545             poly_deg
    546         ), {
    547             'background_temp_range': background_temp_range_slider,

~/rockmag/PmagPy-RockmagPy-notebooks-2144031/rockmag.py in verwey_estimate(temps, mags, t_range_background_min, t_range_background_max, excluded_t_min, excluded_t_max, poly_deg, plot_zero_crossing, plot_title)
    396     dM_dT_filtered = dM_dT_df['dM_dT'][temps_dM_dT_filtered_indices]
    397
--> 398     poly_background_fit = np.polyfit(temps_dM_dT_filtered, dM_dT_filtered, poly_deg)
    399     dM_dT_filtered_polyfit = np.poly1d(poly_background_fit)(temps_dM_dT_filtered)
    400

/opt/tljh/user/lib/python3.6/site-packages/numpy/lib/polynomial.py in polyfit(x, y, deg, rcond, full, w, cov)

Ah, ok, I'll take a look - the JupyterHub packages are definitely getting out of date!

@Swanson-Hysell, I tried the notebooks on JupyterHub and couldn't reproduce the error above (I got a few other errors, but not that TypeError). Does running this as part of the rmag setup change the results in the MPMS notebooks?
pip install --user --upgrade numpy

Even with numpy upgraded:

I am still getting this issue associated with np.polyfit():

@Swanson-Hysell, I added a Python 3.10 option as a kernel on JupyterHub and that seems to fix the numpy issue using the latest version of MPMS_goethite_fit.ipynb:

@rminnett I am giving this a try. The first issue I bump into when using the Python 3.10 kernel is that pandas isn't available as a package. Now I can pip install it, but that seems non-ideal as it makes sense to have the standard scientific python packages available.

It seems to work at the moment:

Do you still get the error? Are there any other packages missing?

I am still getting errors in this 3.10 environment. When I import pandas it gives this error:
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
Cell In[1], line 1
----> 1 import rockmag as rmag
      2 import pmagpy.ipmag as ipmag
      3 import pmagpy.contribution_builder as cb

File ~/rockmag/PmagPy-RockmagPy-notebooks-acc3fc0/rockmag.py:1
----> 1 import pandas as pd
      2 import numpy as np
      3 import matplotlib.pyplot as plt

File /opt/tljh/user/envs/Python-3.10/lib/python3.10/site-packages/pandas/__init__.py:19
     16         _missing_dependencies.append(f"{_dependency}: {_e}")
     18 if _missing_dependencies:  # pragma: no cover
---> 19     raise ImportError(
     20         "Unable to import required dependencies:\n" + "\n".join(_missing_dependencies)
     21     )
     22 del _hard_dependencies, _dependency, _missing_dependencies
     24 try:
     25     # numpy compat

ImportError: Unable to import required dependencies:
numpy: No module named 'numpy'
pytz: No module named 'pytz'

Ok, I think it's better now after installing these packages in the 3.10 shared environment instead of just for the user:

numpy
pytz
matplotlib
pillow
pyparsing
cycler
kiwisolver
plotly
ipywidgets
future
scipy
@Swanson-Hysell are you able to run the latest version of the MPMS_goethite_fit.ipynb notebook now?

Documenting issues with current JupyterHub 3.10 kernel:

Anisotropy_plot_AMS.ipynb : no issues
high_T_susceptibility.ipynb : no issues
MPMS_goethite_fit.ipynb : ipywidget sliders do not appear, these missing sliders provide important interactive functionality
MPMS_plot_dc.ipynb : any attempt to use plotly throws the error ModuleNotFoundError: No module named 'tenacity'
MPMS_verwey_fit.ipynb : ipywidget sliders do not appear, these missing sliders provide important interactive functionality

The sliders and plotly appear to be working on 3.10 now:

The np.polyfit() error and the plotly import error have been resolved. The ipywidget slider issue documented in issue #26 remains.


Calorie Tracker Isuue no. 244

Title and Issue number

Title :
Issue No. :  244
Code Stack :  Tracker.jsx (JS)
Close #<issue_no>

Video (mandatory)

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md if its a new page/tech stack
[x] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?

[x] I'm a GSSOC-EXT contributor
[ ] I'm a HACKTOBERFEST contributor

@justhappyuknow Fit it, Try to keep it somewhere instead of Hompage. Or create a page and link it in a footer.

 @justhappyuknow Fit it, Try to keep it somewhere instead of Hompage. Or create a page and link it in a footer.

You will have to use the API key which I have removed from the codebase for fetching the data, and yes will link it in footer

 @justhappyuknow Fit it, Try to keep it somewhere instead of Hompage. Or create a page and link it in a footer.

You will have to use the API key which I have removed from the codebase for fetching the data, and yes will link it in footer

From where you have got that API Key?

@justhappyuknow Create in it in a new page and link it to the footer

 @justhappyuknow Fit it, Try to keep it somewhere instead of Hompage. Or create a page and link it in a footer.

You will have to use the API key which I have removed from the codebase for fetching the data, and yes will link it in footer

From where you have got that API Key?

calorieninjas.com


chore: bdd-sbhg-import-1587014669 to 0.0.1

chore: Promote bdd-sbhg-import-1587014669 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Check for Duplicate Requirements in <IP_ADDRESS>.d and A.6.2.d as basis for duplicate warning message.

Check for Duplicate Requirements in <IP_ADDRESS>.d and A.6.2.d as basis for duplicate warning message.

Vehicle Composite of DM5:
A/C system refrigerant     not supported,     complete
Boost pressure control sys     supported, not complete
Catalyst                   not supported,     complete
Cold start aid system      not supported,     complete
Comprehensive component        supported,     complete
Diesel Particulate Filter      supported, not complete
EGR/VVT system                 supported, not complete
Evaporative system         not supported,     complete
Exhaust Gas Sensor             supported, not complete
Exhaust Gas Sensor heater      supported, not complete
Fuel System                    supported, not complete
Heated catalyst            not supported,     complete
Misfire                        supported, not complete
NMHC converting catalyst   not supported,     complete
NOx catalyst/adsorber          supported, not complete
Secondary air system       not supported,     complete
FAIL: <IP_ADDRESS>.a (A6.2.c) - Composite vehicle readiness for NMHC converting catalyst did not meet the criteria of Table A4
WARN: <IP_ADDRESS>.a (A6.2.d) - Fuel System is supported by more than one OBD ECU
WARN: <IP_ADDRESS>.a (A6.2.d) - Misfire is supported by more than one OBD ECU
WARN: <IP_ADDRESS>.a (A6.3.a) - Non-OBD ECU Instrument Cluster #1 (23) responded
WARN: <IP_ADDRESS>.a (A6.3.a) - Non-OBD ECU Passenger-Operator Climate Control #1 (25) responded
FAIL: <IP_ADDRESS>.b - OBD ECU Engine #1 (0) reported active DTC count not = 0
FAIL: <IP_ADDRESS>.b - OBD ECU Management Computer #1 (39) reported active DTC count not = 0
WARN: <IP_ADDRESS>.d - Required monitor Fuel System is supported by more than one OBD ECU
WARN: <IP_ADDRESS>.d - Required monitor Misfire is supported by more than one OBD ECU

6.1.13	DM5: Diagnostic Readiness 1: Monitor Readiness
<IP_ADDRESS>	Actions
a.	Global DM5 [send Request (PG 59904) for PG 65230 (SPs 1218-1223)].
b.	Display monitor readiness composite value in log for OBD ECU replies only.
<IP_ADDRESS>	Fail/Warn Criteria
a.	Fail/warn per Section A.6, Criteria for Readiness 1 Evaluation.
b.	Fail if no OBD ECU reports DTC counts of 0 for both active and previously active faults.
c.	Fail if no OBD ECU provides DM5 with readiness bits showing monitor support.
d.	Warn if any individual required monitor, except Continuous Component Monitoring (CCM) is supported by more than one OBD ECU.
<IP_ADDRESS>	Actions2
a.	DS DM5 to each OBD ECU.
<IP_ADDRESS>	Fail Criteria
a.	Fail if any difference compared to data received during global request.
b.	Fail if NACK not received from OBD ECUs that did not respond to global query.

A.6	CRITERIA FOR READINESS 1 EVALUATION
Section A.6 describes criteria for evaluation of readiness bits in SPs 1221, 1222, and 1223 (bytes 4-8) of the DM5 message (PG 65320). Parallel construction can be applied to SPs 3303, 3304 and 3305 (bytes 4-8) in the DM26 message (PG 59904) which share the same assignments of monitors to bits, except for the monitor inhibit status in DM26, but operates on a smaller time scale.

The response from each responding device shall be evaluated separately using a through d below:
a.	Fail if no response from an OBD ECU (ECUs that indicate 13h, 14h, 22h, or 23h for OBD compliance).
b.	Fail if any response does not report supported and complete for comprehensive components support and status (SP 1221, byte 4, bit 3 = 1 and bit 7 = 0), except when all the bits in SPs 1221, 1222, and 1223 are sent as 0 as defined in SAE J1939-73 paragraph 5.7.5.
c.	Fail if any response does not report 0 = ‘complete/not supported’ for the status bit for every unsupported monitors (i.e., any of the support bits in SP 1221, byte 4 bits 1-3, 1222 byte 5 bits 1-8, or 1222 byte 6 bits 1-5 that report 0 also report 0 in the corresponding status bit in SP 1221 and 1223).
d.	Fail if any response does not report 0 for reserved bits (SP 1221 byte 4 bits 4 and 8, SP 1222 byte 6 bits 6-8, and SP1223 byte 8 bits 6-8).
All responses received from all responding OBD devices shall be combined with appropriate ‘AND/OR’ logic to create a composite vehicle readiness response: (Do not use responses from non-OBD devices to create a composite vehicle readiness response.)
a.	If one or more responses indicates 1 = supported in the support bit for a monitor,
i.	Then the composite vehicle readiness shall indicate 1 = supported for that support bit/monitor,
ii.	Else it shall indicate 0 = unsupported for that support bit/monitor;
b.	If one or more responses indicates the status bit for a supported monitor is 1 = not complete,
i.	Then the composite vehicle readiness shall indicate 1 = not complete for that status bit/monitor,
ii.	Else it shall indicate 0 = complete for that status bit/monitor).
c.	Fail if composite vehicle readiness does not meet any of the criteria in Table A4.
d.	Warn if any individual required monitor, except Continuous Component Monitoring (CCM) is supported by more than one OBD ECU.
All responses received from non-OBD ECU shall be evaluated using the criteria below:
a.	Warn if any response from non-OBD ECU received.
b.	Warn if all the monitor status and support bits in any reply from a non-OBD ECU are not all binary zeros or all binary ones.
SP 1222, bit 7 (Exhaust Sensor Heater Monitor Support) may appear as a 0 with a warning message, instead of a requiring a failure message in 2013 MY engines. Future engine model years (c. 2016) shall unbundle all heater monitoring support and support both bits 7 and 6. When SP 1222, bit 7 is provided as a 0 (not supported) after the 2013 engine model year, SP 1223, bit 7 (Exhaust Sensor Heater Monitor Status) shall be provided as 0 (complete).
Specific implementations may require the immediate setting of the misfire monitor status bit to zero (complete). Refer to 13 CCR 1971.1 for such conditions. Observation of a zero (complete) for a misfire monitor status bit after fault codes have been cleared shall be marked with a warning message.

Yes, there is a duplicate.

Strike 2.d in A.6.

Documented in artifact (strikeout font), bundled with #1171

#1171 has brl tag


Migrate to mkdocs

Demonstrate how mkdocs-jupyter plugin can be used to execute and render Jupyter Notebooks in a similar way to MyST.
Output: https://metalearners--81.org.readthedocs.build/en/81/
TODO:

[x] Fix enumeration in background.md
[ ] Docstrings can / should be adapted to mkdocs style
[ ] Jupyter notebooks should be adapted to mkdocs style (remove cell tags), additionally, discuss whether jupyter notebooks should be built once and checked into git for fast serving of docs (better DX than slow optuna notebook).
[x] ~Wait for https://github.com/mkdocstrings/python/issues/194~ => moved to griffe extension: https://github.com/mkdocstrings/griffe-inherited-docstrings (now works with version 1.1.1) TBD: maybe not include in template!
[ ] Look into ruff pydocstyle (replacement to pre-commit-hook docformatter)

One issue I discovered with math blocks (= math formulae that are not rendered inline).
For some reason KaTeX is only able to render math blocks if there is no indentation before them which is annoying when dealing with enumerated lists:
Math works, enumeration doesn't (1. and 1.):

Enumeration works, math doesn't:

I haven't looked into MathJax yet. Other solutions could be to use unordered lists or use headings instead:

Thanks for looking into this @thomasmarwitz !
Is it possible that the subscripts no longer need escaping?
See

from this PR compared to

from https://metalearners.readthedocs.io/en/latest/background.html#x-learner

@kklein Thanks for pointing that out, looks like I completely missed this. You are right, you don't need to escape subscript anymore.

Aside from the math and enumeration topic mentioned above, what do you see as hurdles and next steps?
Might it make sense to test whether our readthedocs setup works fine with mkdocs?

An alternative to readthedocs could be github pages in combination with https://github.com/jimporter/mike

Sounds interesting! Can we have branch-specific deployments with GitHub-pages? Given our somewhat heavy use of formulas, we rely a lot on rendered docs in PRs.

I don't know whether branch based deployments can be accomplished out of the box with mike and gh-pages, that would be interesting to keep an eye on.
I just tried out to host the mkdocs documentation with readthedocs and that worked: https://metalearners--81.org.readthedocs.build/en/81/

But perhaps this is even desired behavior? In the sense that if you change the implementation, you should also adapt the docstring?

I can totally see that one might want to ask that question. In our case we mostly described the 'contract' of a given method/function in the docstrings, i.e. what a user may provide as input and what they can expect as an output. We don't usually say much about the 'how's.
At times, changing the implementation does not change this contract.
E.g. one might think of the folllowing:
class Shape:
    contour: list[Point]
    def surface_area(self):
        """Return the surface area in square meters."""
        return numerical_integration(self.contour)

class Rectange(Shape)
    def surface_area(self):
        return distance(self.cotour[2], self.contour[0]) * distance(self.contour[3], self.contour[1])

Can we have branch-specific deployments with GitHub-pages? Given our somewhat heavy use of formulas, we rely a lot on rendered docs in PRs.

I don't think so, so in this case readthedocs might be more fitting.

Thanks for your work @thomasmarwitz ! A couple of observations on the rendered docs:

We have quite a few diagrams with a transparent background and black or dark grey font color. Given the dark background of the mkdocs theme, these are not so easily legible, e.g. https://metalearners--81.org.readthedocs.build/en/81/motivation/#accessing-base-models.

Some of the math isn't rendered as intended, see e.g. the X-Learner paragraph, the R-Learner paragraph or the DR-Learner paragraph.

For some reason 'Covariates' in the glossary is treated surprisingly, see here.

Some cross-references aren't displayed as intended yet, see e.g. the second bullet in the example on using a first MetaLearner

The examples no longer show the output of the code cells, e.g. here.

The Table of Content of this Linear Regression paragraph has three colon-subparagraphs which I don't see in the content.

Some cross-references aren't picked up, see e.g. the first usage of {term} and {ref} in the known propensity example .

Some notes aren't picked up properly, see e.g. the {note} reference in this paragraph.

RST Urls from docstring aren't rendered as intended, see e.g. the arxiv links in the docs of the DR-Learner class.

I can't find the parameter and return value type hints in the API docs, e.g. in the evaluate method docs.

@kklein Thanks for examining the current progress so carefully. I checked each point to see whether there is some way of solving it. I haven't implemented everything as changing all URLs, adjusting all docstrings etc. takes some time.

We have quite a few diagrams with a transparent background and black or dark grey font color. Given the dark background of the mkdocs theme, these are not so easily legible, e.g. metalearners--81.org.readthedocs.build/en/81/motivation#accessing-base-models.

We can disable the dark and auto-mode as a temporary work-around. The site will then be always displayed in light mode.
A solution can be the neat conditional rendering of images depending on light/dark mode, this would require a dark-mode friendly version of the images, though.

Some of the math isn't rendered as intended, see e.g. the X-Learner paragraph, the R-Learner paragraph or the DR-Learner paragraph.

Thanks for pointing that out. As it turned out, prettier adjusted the tabwidth in markdown, that's why the version on github was always broken. I found a way to override the tabwidth for markdown with 4.

For some reason 'Covariates' in the glossary is treated surprisingly, see here.

Fixed, typo in heading.

Some cross-references aren't displayed as intended yet, see e.g. the second bullet in the example on using a first MetaLearner.

I have to replace all sphinx-like references with mkdocs / normal links. Just not there yet.

The examples no longer show the output of the code cells, e.g. here.

I think, this point needs some discussion.
During development, I turned off the execute option during docs build as the building of the optuna notebook (through mkdocs) takes >20 min on my mac (even by excluding optuna, the remaning notebooks need 5 min to be all converted). This leads to all notebooks being used in their current state, some may have no output, but some have e.g. optuna.
When building the documentation in CI, we could execute all notebooks beforehand to ensure everything is up to date and then build the documentation. Executing all notebooks everytime, makes the mkdocs serve rather inconvenient as I expect high iteration speeds from such a live server.
WDYT? (also @pavelzw as you are a huge fan of the serve option)

The Table of Content of this Linear Regression paragraph has three colon-subparagraphs which I don't see in the content.

Appears to be a bug, as a work-around we can remove Headings using "``"  to wrap code-like elements. If we use that feature frequently, I can open an issue.

Some cross-references aren't picked up, see e.g. the first usage of {term} and {ref} in the known propensity example .

This is also sphinx-specific terminology that I haven't replaced completely with the mkdocs equivalent.

Some notes aren't picked up properly, see e.g. the {note} reference in this paragraph.

Mkdocs has nice admonition rendering: https://squidfunk.github.io/mkdocs-material/reference/admonitions/#+type:note. In jupyter notebooks, the syntactic sugar to render those admonitions is not (sadly) not available. A solution I found is to refer to the "compiled" html elements directly e.g.

Note

The fact that we have a fixed propensity score for all observations is not true for this dataset, we just use it for illustrational purposes.

Again, this is not really pretty. If we find ourselves using that a lot, we can also think about opening an issue to support the more concise markdown syntax.

RST Urls from docstring aren't rendered as intended, see e.g. the arxiv links in the docs of the DR-Learner class.

This is also sphinx-specific terminology that I haven't replaced completely with the mkdocs equivalent.

I can't find the parameter and return value type hints in the API docs, e.g. in the evaluate method docs.

I found a setting to render the type hints:

If we add black as a dependency in the docs feature, we get a formatted signature (that looks much better imo):

For a table like display (there are also other display options) like this:

The function needs a numpy, google or sphinx docstring: https://mkdocstrings.github.io/python/usage/configuration/docstrings/#docstring_style. There is a tendency that google docstrings has more features coming.
The nice thing here is that we don't need this google style or whatever everywhere. One can sprinkle that in if e.g. a param needs some explanation as in the screenshot. In all other cases, the param names and types seem pretty solid.

I'm afraid this is taking so long - that's mainly because migration all sphinx specific syntax to mkdocs (even in docstrings or jupyter notebooks) takes some time and I can only spend a certain amount of time per week on this.
@kklein I'll ping you here explicitly once I've migrated all docstrings and jupyter notebooks.

I think, this point needs some discussion.

I totally second your take that the runtime caused by the execution of the notebooks upon building of the docs is a pain.
At the same time, I think that the output of the cells creates a lot of value for a reader of the docs.
If we can find a solution which provides the outputs while reducing the amount of time used for docs-building that'd be great.
To give you some context: We didn't start off by using jupyter notebooks at all for these code examples. Rather, we executed the corresponding code blocks by hand and mode the code blocks as well as the outputs into rst. This approach clearly has the downside of

there being no alerting mechanism if code doesn't run (anymore)
there being a lot of development overhead

If we add black as a dependency in the docs feature, we get a formatted signature (that looks much better imo):

Looks great; I think adding black as a docs dependency is not problem at all. :)

If we can find a solution which provides the outputs while reducing the amount of time used for docs-building that'd be great.

@kklein I talked w/ @pavelzw about how we could address this. I agree that having outputs is very valuable to the reader.
Our idea is:

Have an additional check here that checks whether the execution count for each cell of the jupyter notebooks is not null, i.e. the notebook has been executed and, fail if we encounter an unexecuted cell. Thus, it becomes the task of the person changing something in the jupyter notebook or adding a new one to execute it at least once.
In the docs build, we can just copy over the output of all already executed cells.

@thomasmarwitz sgtm :)


chore(protocol): Compressor Implementations

Description
Re-works compression to use compression writers that allows for streaming compression.

📚 $\text{Stack Overview}$
Pulls submitted in this stack:

#305 👈
#299
main

This comment was automatically generated by st.

This needs to be restacked ontop of https://github.com/alloy-rs/op-alloy/pull/335 once it's merged in trunk. Should make it much clearer where the issue lies to the reviewer


Re-Design - Brand

Perf/brand
TL;DR

Added new brandcard design
Updated Nav
Adjusted Sponsor card
Deleted sponsor cards from landing page
Updated loaders

Details
TODO:

[ ] codn implementation

Checklist / Reminders:

[ ] Documentation is created / adapted
[ ] Cypress Tests

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


Errors with Strawberry Generated Schema including JSON Scalar

Describe the bug
When using genqlient with a schema that is generated from Strawberry that includes strawberry.scalars import JSON and includes a stanza
"""
The `JSON` scalar type represents JSON values as specified by [ECMA-404](http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf).
"""
scalar JSON @specifiedBy(url: "http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf")

in the schema file, an attempt to use a field with this scalar in a query results in the error during go generate:
me@MAC mydir % go generate
/mydir/graphql/schema.graphql:93: unknown scalar JSON: please add it to "bindings" in genqlient.yaml
Example: https://github.com/Khan/genqlient/blob/main/example/genqlient.yaml#L12
exit status 1
generate.go:1: running "go": exit status 1

However, adding
bindings:
  JSON:
    type: string

to the genqlient.yaml file only produces the following error when attempting to execute a query accessing this JSON containing field:
2024/02/08 15:52:29 ERROR error while retrieving Interfaces device=<snip> port="" !BADKEY="json: cannot unmarshal object into Go struct field DevicesDevicesDeviceSchema.data.devices.state of type string"
2024/02/08 15:52:29 ERROR failed to get <snip> devices: %e !BADKEY="json: cannot unmarshal object into Go struct field DevicesDevicesDeviceSchema.data.devices.state of type string"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x10065ec20]

To Reproduce
Provided above, using Golang version 1.21.7 and genqlient github.com/Khan/genqlient v0.6.0
% go version
go version go1.21.7 darwin/arm64
Expected behavior
I would expect the JSON field to be stored in a string.
genqlient version
v0.6.0
Additional context
There are no errors occurring on the Strawberry GraphQL server (providing a 200 response to client)

You probably want to bind to encoding/json.RawMessage, which is the Go convention for "leave this part of the JSON as JSON"; string has to map to a JSON string. If that doesn't work, I think you'll need to post a more complete repro (e.g. a full schema + config + sample server response) so we can see what's going on! (And if it does, documentation PRs to make this clearer are very welcome!)


metrics: remove duplicate grafana panel

Signed-off-by: nolouch<EMAIL_ADDRESS>
What problem does this PR solve?
fix the duplicate panel
What is changed and how it works?
change to keys.
Check List
Tests

Manual test (add detailed scripts or steps below)

Release note

No release note

/rebuid

/merge

/merge

Codecov Report

Merging #2465 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2465      +/-   ##
==========================================
+ Coverage   77.01%   77.03%   +0.01%
==========================================
  Files         205      205
  Lines       21948    21948
==========================================
+ Hits        16903    16907       +4
- Misses       3755     3759       +4
+ Partials     1290     1282       -8

Impacted Files
Coverage Δ

pkg/metricutil/metricutil.go
72.22% <0.00%> (-13.89%)
:arrow_down:

server/tso/tso.go
77.37% <0.00%> (-8.76%)
:arrow_down:

pkg/dashboard/adapter/manager.go
81.65% <0.00%> (-2.76%)
:arrow_down:

pkg/mock/mockhbstream/mockhbstream.go
89.23% <0.00%> (-1.54%)
:arrow_down:

server/schedule/operator_controller.go
80.84% <0.00%> (-0.17%)
:arrow_down:

server/server.go
77.53% <0.00%> (ø)

pkg/etcdutil/etcdutil.go
84.05% <0.00%> (ø)

server/grpc_service.go
58.36% <0.00%> (+0.38%)
:arrow_up:

server/handler.go
51.61% <0.00%> (+0.43%)
:arrow_up:

server/cluster/cluster.go
80.72% <0.00%> (+0.44%)
:arrow_up:

... and 5 more

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 8b43704...45e2b61. Read the comment docs.


Typo on modules/subnet/outputs.tf

On line 7 there is a ] that produces the error

Error: Argument or block definition required
On modules/subnet/outputs.tf line 7: An argument or block definition is
required here.

I suppose it will be fixed in a future...


Issue with az resource tag -i

Incremental parameter does not work
"az: error: unrecognized arguments: -i"

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

ID: e76a8ad2-efd8-9e8a-9b2b-eebeb1e9d1d4
Version Independent ID: 280b7ea9-eb6c-9601-464b-09bf8e0cff5d
Content: az resource
Content Source: src/azure-cli/azure/cli/command_modules/resource/_help.py
Service: azure-resource-manager
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

add to S170

@jrachwalski Hello, -i is work fine on my side, may I ask which version of CLI did you use?

azure-cli                         2.0.77 *
command-modules-nspkg              2.0.3
core                              2.0.77 *
nspkg                              3.0.4
telemetry                          1.0.4

My Az cli was an old version, due to my brew being out of date
brew update && brew upgrade azure-cli
updated the cli to 2.5, and I can now use the --is-incremental option.
You can close this issue,
Thanks.


Refactor for checking

test

test

Changes needed before this PR will get approved

[ ] Move SASS styles from Assets folder into styles folder. Follow our usual pattern. Also it doesn't make sense since I noticed just now you're putting it into Assets folder directly. What about other assets like svgs, images, and vids if you're gonna put it in Assets folder? You should also put this into mind
[ ] Rename Elements folder into Shared folder to let developers know the component can be reused. We don't need to elaborate this is an Element since it's already sitting inside component folder
[ ] Move BookmarkStoreButton component into its component. This isn't being reused by other components
[ ] Please make use of prettier. You have spacings that are inconsistent

@hnbmunoz Perfect! Let's merge this.


Problem with injecting .NET IOptions

I'm registering IOptions<DataAccess> this way:
services.Configure<DataAccess>(configuration.GetSection(nameof(DataAccess)));

After that I'm getting exception:
System.ArgumentException: 'Open generic service type 'Microsoft.Extensions.Options.IOptions`1[TOptions]' requires registering an open generic implementation type. (Parameter 'descriptors')'

I saw that u tried to apply fix in related issue: https://github.com/enisn/DotNurseInjector/issues/6. However, it still doesn't work.

Hi @stpdeveloping
Can you try the version v2.4.0 ?
I'm configured my entity like that:

And, injected by attribute:

Also, there is already a test for that situation and it passes
https://github.com/enisn/DotNurseInjector/blob/master/tests/DotNurse.Injector.Tests/ResolvingTests.cs#L43


(feat) disable event propagation

Need way for optional prevent event broadcasting.
Something like:
iohook.on('keyup', (event) => {
  event.preventDefault();
});

Or equal method

Is this possible? I've been looking for modules that has this, but found none so far.
I want to make an app to control another computer's keyboard/mouse, just like Synergy. Simulating keys/mouse on the "client" computer is not a problem, only problem is that the host key/mouse should be prevented.

Need to review this feature in https://github.com/kwhat/libuiohook repository. iohook use this lib for hooking. I will be very happy if somebody make pull-request with this feature.
At this moment I have no time for research and implement it. Sorry...

Hi there!
I have worked to an implementation of this feature because I need it for enable/disable the propagation of mouse click events in my project.
@WilixLead it is not possible to implement this feature inside the callback because the event is already propagated at this moment but I have extended the API with two new methods.
 /**
 * Disable mouse click propagation.
 * The click event are captured and the event emitted but not propagated to the window.
 */
disableClickPropagation() {
   NodeHookAddon.grabMouseClick(true);
}

 /**
  * Enable mouse click propagation (option by default).
 * The click event are emitted and propagated.
 */
enableClickPropagation() {
  NodeHookAddon.grabMouseClick(false);
}`

Propagation is enabled by default.
It's work fine in windows and linux (it is hard to do it in x11 but is done :). I have no tested in Mac OS but I am really confident about the solution.
I am open to discuss for extend this feature to other events like key pressed but I have no time for do'it.
I hope this helps!

Hey @eboukamza ! That's great ! It would be awesome to be able to use this feature to key events. I'll update your PR soon. Thanks !

@eboukamza  It's amazing!
Is there someone implementing the same feature for keyboard propagation?

I updated codes to be able to enable/disable keyboard events. Please, refer to #102.

Any news on this?

I got something like this working. It's not enough to put into master (only works on Windows) but parallels how disableClickPropogation works:
https://github.com/theicfire/iohook/commit/f2e1e14c079e175cc97f314dfcf2203cc1467508

@theicfire Great work, but when disabling keyboard keypress event won't work, and is just the one needed to extract the real character typed.


gui elements behave unexpectedly with begin/end scissor mode

If a gui element is not drawn due to BeginScissorMode, it can still be interacted with.

I'm afraid it's up to the user to manage that behaviour. That's a limitation of immediate-mode...


Folders with '.' in names are not being resolved correctly

When running ctix create and a folder named foo.bar is encountered, the corresponding index.ts file is trying to import the module with import * from "foo" .

@Vulthil  Hi, Thank you for your reporting.
Would you create reproducable repo?

Updated initial issue with a reproduction repository

@Vulthil Thank you! I check your repository 👍

@Vulthil Thank you for your feedback, It was fixed 1.8.1


initial implementation

Summary by CodeRabbit

New Features

Added support for managing train departure and cancellation information via Redis queues and database updates.
Introduced new API endpoints for handling train departure and cancellation data.

Enhancements

Improved server error handling and graceful shutdown processes.
Added configuration management for environment settings.

Database

Updated database schema to include detailed cancellation information.
Added methods for inserting and retrieving train cancellation data.

Testing

Updated test cases to cover new cancellation data insertion and retrieval functionalities.

Dependencies

Added new dependencies for Redis, national rail client, and more.

@coderabbitai can you generate a read me for this project?


Change status bar color

Suggestion / Feature Request
Change color of the status bar to match the app's theme

please assign me the task

Sure @rishabhknowss , good luck 😄

Hey @ken1000minus7 can u assign me this task?

Sure @PratikFagadiya good luck !


Add onclick to README's callback list

Can you please re-submit against the develop branch?

Ok, done #374


add tool for check openvz mirrors with clair to contrib

Add from https://github.com/FastVPSEestiOu/check_openvz_mirror_with_clair to /contrib as told in
Issue https://github.com/coreos/clair/issues/8

Added copyright headers.

This will need a LICENSE file in this directory if you want to put it under GPLv2. Any chance you would put it under Apache for consistency with the rest of the repo? Your call, either way is fine with me.

I set Apache  license for consistency with rest of the repo.

Great, thanks!

Thanks for your contribution!


Remove EOL options as we can just rely on calling next_line

I think we decided we didn't need this, right?

oh, yeah, we should talk about this!
I actually didn't get it working with the alternative implementation, where we just call xparse and handle INVALID_DELIMITER. I meant to investigate further.
So we're still relying on this little workaround for now


keepalive.. per backend?

tl;dr: (how do I correctly add keepalive_timeout to my backend..)
Everything is working, 6 hosts working as configured.
Looking to make the 'unifi' controller app more responsive..
I see in nginx.conf
http{
..
keepalive_timeout 90s;
..
but in
/data/nginx/proxy_host/
[1-6].conf I do not see keepalive_timeout set in each backend..
In the nginx docs keepalive has no default but keepalive_timeout has 60s default.. but it's in the context of upstream
so I create /data/custom/server_proxy.conf and added:
keepalive 2;
keepalive_timeout 90s;
and restarted the app..
am I missing something?
Or is something missing..

Where is server_proxy.conf defined to be used?
Thank you in advance..

missed including this..
tcpdump -v -i eno1.69 -n -q dst host <IP_ADDRESS> -A

.bP...?)..GET /speedtest.js HTTP/1.1
Host: files.tech.domain.internal
X-Forwarded-Scheme: http
X-Forwarded-Proto: http
X-Forwarded-For: <IP_ADDRESS>
X-Real-IP: <IP_ADDRESS>
Connection: close
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Sec-GPC: 1
Referer: http://files.tech.domain.internal/
Priority: u=2


Custom shuffle/loop intents end audio playback

I have tried to implement custom shuffle and loop intents for my action that has audio content. The platform does not seem to support this.
The ideal behavior would be like this:
> "OK Google, tell 'my cool action' to play music"
< "Playing music..."
> "OK Google, turn loop on"
< "Turning loop on"
Music continues playing

Instead, this is what happens:
> "OK Google, tell 'my cool action' to play music"
< "Playing music..."
> "OK Google, turn loop on"
< "Turning loop on"
Music stops

Even worse, after the latter scenario, since the session with my action is over, restarting the audio ("OK Google, play") will only play through the current track and my fulfillment endpoint will not get a request to play the next song. The custom shuffle and loop intents will also not be invoked. Instead, the built-in intents for shuffle and loop are invoked.
The reason this is happening is because we have two options when sending a speech response:

Await a user response and keep the mic open
End the session and turn the mic off.

Option 1) Awaiting a user response doesn't make any sense in this scenario because there is nothing for the user to respond with after they just asked for loop/shuffle to be turned on/off. This continues to prompt them 3 times until Google gives up and closes the session.
Option 2) Ending the session makes more sense but it also ends the currently playing audio track.
Is there any plan to support something like this? Or is there any usable workaround for this?

It should be noted that turning loop and shuffle features on and off is natively supported by Alexa, which is why we're sort of monkey-patching it into our Google intents to try to keep feature parity.


Is it necessary to filter the hi-c reads before the mapping pipeline using ArimaGenomics ？

Hi,
Is it necessary to filter the hi-c reads before the mapping pipeline using ArimaGenomics ？ @skoren @ghuryejay @pb-jchin @cschin

The arima pipeline will perform filtering for you so you can just run the mapping pipeline followed by salsa.


chore: main back to alpha

:tada: This PR is included in version 1.19.1-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.19.2-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add RangeCheck0 custom gate

Expose the the RangeCheck0 gate to snarky
Re #12624

ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


Fixes #248

Fixes #248

Duplicate of https://github.com/inProgress-team/react-native-meteor/pull/249

Why was this closed? I don't see any other duplicates

Sorry wrong number, duplicate of #247.


Bug/792 no login request from other account

:tada: This PR is included in version 0.13.0-development.9 :tada:
The release is available on:

npm package (@development dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Graceful Proxy shutdown

I have a scenario in which the user kills the client application from the task manager, at this point the proxy does not turn off as the client application is not active. Is there a way in which I can gracefully switch off the proxy when the client application is killed through the task manager?
Note: Proxy is active when the client application is running, When user kills the client application the access to internet is lost until the proxy switch in the settings is switched off manually by the user.

You need another program which monitors the proxy, since if you kill an application, it can't do anything:)

Thanks @honfika  for the answer. I'll create new Windows Service to shutdown the proxy.


add the hyperlink in my wish-list

issue #110 is solved
the hyper link is added in my wishlist in cart.

@aashkaaaaaa there was some merge conflict , i rectified it it's ready to merge, congratulation for your first contribution


Nuget Package

Hi! This is awesome what you're doing here. I was thinking about maybe using your MeshIO.FBX in my AssetRipper project. Would you be willing to publish a nuget package for it?

Hi @ds5678,
thanks for the suggestion, I'll look to release the first version of this library in NugetPackage.
The project is in an early stage, but if you start using it and you find any bug, error or an idea to add as a feature don doubt to open an issue.

Hi Dom, do you have Discord? There's a link to my server on AssetRipper repository page. If you're willing, I would like to pass some thoughts back and forth.

Hi @ds5678,
I've publish the first version of the Package, notice that is an alpha version and there is only the fbx library.

@DomCR Do you have an opinion on these changes?


Remove explicit box-sizing for input[type="search"]

This normalizes the CSS to what the suggested default browser CSS should be, which is now implemented in IE11, Edge, Blink, WebKit and Gecko (for the latter, see https://www.w3.org/Bugs/Public/show_bug.cgi?id=28784)
References https://github.com/twbs/bootstrap/issues/17379
Closes https://github.com/necolas/normalize.css/issues/471

(btw happy to squash / rebase this PR ... just didn't want to jump the gun here in case the decision to just nuke the box-sizing wasn't final)

Rebased this to just remove the box-sizing CSS and test, as discussed.

/cc @necolas for review?

Thanks. Applied as fe567632afcf8afcf17925ab2a507ed87504cce8


Changes to error_thrower

New Code
Change Log

I found errors that are in the wrong section, and i updated them. there were a few tracemalloc errors, fixed with awaits and async

This wouldn't be too bad


Disable playground plugin script in bootstrap

This script changes the list of plugins on bootstrap into a committed file, which causes differences when building. This is annoying for local dev, but also fails CI because I made it error on file diffs like that.
The fixes could be:

gitignore the file; builds are less deterministic
Stop updating it

I'm going to opt for the latter for now. There do not seem to be new plugins being created these days. We can manually rerun the script later or figure something better out.

Then again, builds are already non-deterministic thanks to the releases. Maybe I do just gitignore it.

Eh, let's just do this for now to unblock other changes.


Flow integration outside of the Box

Does the Flow Renderer integrate trajectories outside of a given Box?
I believe it does so with Streamlines.  I'm not sure about Pathlines.
If we do integrate outside of the Box region, performance would be greatly improved by constraining it to the relevant data.

@shaomeng - Is this the case, and is it worth limiting integration to the Renderer Region (Box) for performance?

Hi @sgpearse , the flow line code currently does not check the box, if I remember correctly.
I wonder how often a user selects a smaller box in flow line integration? I feel that it's not a very common use case.


apply resistance before target mods

The following demonstrates that resistance is applied before target modifiers (13% magic damage taken from Ebon plaguebringer and 30% disease damage taken from crypt fever)
https://classic.warcraftlogs.com/reports/BXzqP3mx1ZvbRGcF/#source=1&view=events&fight=1
The first fight I have EP on the target which gives 13% magic damage and 30% disease damage taken.
You can see all resist values properly give 10% or 20% resisted with the following formulae:
# disease
resist / (resist + dmg/1.3/1.13)

# not disease
resist / (resist + dmg/1.13)

For example:
Sailz Blood Plague Highlord's Nemesis Trainer Tick 148 (R: 25)
25/(25+148/1.3/1.13) = 19.88% which is within rounding error of 20%

Sailz Death Coil Highlord's Nemesis Trainer 1108 (R: 109)
109/(109+1108/1.13) = 10%

Now in the second fight I do not have EP / CF so no target modifiers and we can see all resist values properly give 10% or 20% resisted with the following:
resist / (resist + dmg)

For example:
Sailz Blood Plague Highlord's Nemesis Trainer Tick 83 (R: 9)
9/(9+83) = 9.78% within rounding error of 10%

Sailz Death Coil Highlord's Nemesis Trainer 461 (R: 115)
115/(115+461) = 19.96% within rounding error of 20%

LGTM. It would be helpful to also log the equivalent of "rawDamage", to better verify against combat logs, but one step at a time ;)


Deploy to a staging hub during our CI/CD

Description
Our hub deployment infrastructure currently does not do any "testing deploys" as a part of our PR workflow. This means that unpredictable things can happen when we make new changes to main on our pilot hubs. We should add in some testing that mimics what will happen when our hubs are actually deployed or updated as a part of our CI/CD.
Value / benefit
There are a few benefits that this would have:

We will know more about what will happen when a PR is merged (e.g. unexpected YAML validation errors)
We will feel more confident in making changes to our pilot-hubs infrastructure, because we know the steps have been followed as a part of our tests
This will likely lead to more errors caught earlier on, and thus more stable infrastructure in general.

Implementation details
We discussed pieces to this, here were a few ideas:

Keep a staging cluster that is constantly running. We use this cluster as part of our testing infrastructure. A PR will create a new hub and deploy changes to this cluster, and run some kind of test suite as well.
Keep a staging hub that is constantly running on one of our clusters. We use this hub to deploy changes each time they're made, and run tests on it.

See this comment from yuvi from a previous conversation around this.
Tasks to complete

[ ] Decide whether we want to deploy a "new staging hub" for each PR, or whether to deploy to a pre-existing one
[ ] Confirm that there's not a generally better way of doing this
[ ] Decide next steps and implement

Updates
No response

Keep a staging hub that is constantly running on one of our clusters. We use this hub to deploy changes each time they're made, and run tests on it.

Since we are always deploying staging to our different clusters, why not pushing stuff to all the stagings (in each of our clusters) when we submit a PR?
In that way we test in all the different cluster we own (from different cloud providers) and we do not spend money in a dedicated stating cluster (that I think it is actually needed but since lower infra change less frequently, we may not need to have that one always up, right?).

Since we are always deploying staging to our different clusters, why not pushing stuff to all the stagings (in each of our clusters) when we submit a PR?

This is how I envisaged implementing this

my inbox gets filled with notifications

Jaja... btw, I am totally OK with the test-this-pr approach, that is how envisaged your envision 😉 .

that is how envisaged your envision

Tbf, my dream workflow is to have bots working on my behalf so I can really be on a beach somewhere

I could not resist the temptation 😜

We do this now!


Tab switching does not work when opening atom with files/tabs already opened

Reproduction (on Windows atom v0.176.0):

Given a project (folder) opened in atom
Open at least two files of this project
Close atom and restart it (you should see previously opened files/tabs again)
Now try ctrl + tab

Popup shows up
But no switching happens

Conclusion: only newly opened files/tabs within a atom session will switch.

I cannot confirm this with atom 1.0.3 (linux, 64bit).
Closed & restarted atom with 4 "restored" tabs - tab-switching works.
Maybe update to a newer atom?


Add animation APIs for starting/looping/stopping

Right now we just have "startAnimation" but these would all be very helpful

we have new animation api


Check for inherited attrs in initializeAttrs

When an element extends another element, none of its inherited attrs become defined. This PR updates initializeAttrs to traverse the instances prototype chain to gather property names with the @attr decorator from parent elements.
@controller
class KindaCoolElement extends HTMLElement {
  @attr foo = ''
}

// foo will be available on instances of `VeryCoolElement` and 'data-foo'
// will be in `VeryCoolElement`’s `observedAttributes`
@controller
class VeryCoolElement extends KindaCoolElement {}

VeryCoolElement.observedAttributes // ['data-foo']

const veryCool = document.createElement('very-cool')
document.body.appendChild(veryCool)

veryCool.foo === '' // true
veryCool.foo = 'bar'
veryCool.getAttribute('data-foo') // 'bar'

Anything we can do to move this along?

This looks good to me ✨

Thanks so much! Anything I can do to help get this merged?

This looks good to me ✨

Thanks so much! Anything I can do to help get this merged?

I just forgot to merge and publish 😄


[ConstraintSystem] Detect and diagnose extraneous return(s) in result build body

This is (hopefully) the last source of "failed to produce a diagnostic" related to result builder
where having a return would just assume that body is a regular closure just to fail a bit later.
Instead of doing that (in diagnostic mode) let's mark body with explicit returns as invalid and
carry on solving to diagnose it if it was possible to reach a solution, this would also mean
that situations where nested result builders have return statements are going to be correctly
diagnosed.
Resolves: rdar://problem/66709164

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test Windows platform

@swift-ci please smoke test Windows platform

@swift-ci please smoke test

@swift-ci please smoke test Linux platform

@swift-ci please smoke test Linux platform

@swift-ci please smoke test Linux platform


Uncaught MongoError, bedrock-mongodb@6, mongo client 2.x

     Uncaught MongoError: connection 5 to localhost:27017 closed
      at Function.MongoError.create (node_modules/mongodb-core/lib/error.js:29:11)
      at Socket.<anonymous> (node_modules/mongodb-core/lib/connection/connection.js:214:22)
      at TCP._handle.close (net.js:597:12)

This sort of error pops up on rare occasion on when looping on TestCloud.  It would be good to investigate this error and see if we can fail/recover more gracefully.

do we know if connection 5 means the fifth connection attempt or 1 of 5 concurrent connections? Perhaps localhost only allows a set number of concurrent connections?

I'm closing as won't fix -- as a part of a very old version. We shouldn't put any effort toward this unless it comes up again with the new version.


Connecting more servers

Hello,
I currently use Simple DNSCrypt and currently use the pre-defined resolvers but like to use a couple from https://servers.opennic.org/ I don't see anywhere to add IPs or DNSCrypt keys to connect to those servers.

But they do support secure connections with the use of DNSCrypt. How would I add a resolver to either dnscrypt-proxy service (https://github.com/jedisct1/dnscrypt-proxy/wiki/Installation-Windows) or SimpleDNSCrypt?
One of the networks:
Provider Address: X.XX.X.XX:5353
Provider Name: 2.dnscrypt-cert
DNSCrypt Key:
And if you see here: https://servers.opennic.org/ you can see they support DNSCrypt connections by the orange flag.

If the list is incomplete, the list has to be updated :)
What servers are missing?

So it's not possible for users to add/connect to servers manually then using DNSCrypt?
There are too many servers to list.

You can use [static] block to add your servers.

You can add new servers, and this is in the documentation, but all the OpenNIC servers should be in the list. If they aren't, it would be better to report which ones are missing so they can be added.

I can report about them.
Currently opennic-onic and opennic-tumabox (+ opennic-tumabox-ipv6) not listed at servers.opennic.org.
Unlisted servers:
https://servers.opennic.org/edit.php?srv=ns3.vic.au.dns.opennic.glue

sdns://AQYAAAAAAAAADzEwMy4yMzYuMTYyLjExOSCsA3mel5peBSzSovzwdgGi5qkfpWXYHfBxtBp7n8dliCkyLmRuc2NyeXB0LWNlcnQubnMwMy5tZWwudXNlcnNwYWNlLmNvbS5hdQ

But here not provided port. Full with port 443 here

sdns://AQYAAAAAAAAAEzEwMy4yMzYuMTYyLjExOTo0NDMgrAN5npeaXgUs0qL88HYBouapH6Vl2B3wcbQae5_HZYgpMi5kbnNjcnlwdC1jZXJ0Lm5zMDMubWVsLnVzZXJzcGFjZS5jb20uYXU

IPv6 (port 5353):

sdns://AQYAAAAAAAAAJ1syNDA0Ojk0MDA6MzowOjIxNjozZWZmOmZlZTA6N2Y2OV06NTM1MyCsA3mel5peBSzSovzwdgGi5qkfpWXYHfBxtBp7n8dliCkyLmRuc2NyeXB0LWNlcnQubnMwMy5tZWwudXNlcnNwYWNlLmNvbS5hdQ

https://servers.opennic.org/edit.php?srv=ns16.de.dns.opennic.glue
IPv4:

sdns://AQYAAAAAAAAAEjUuMTg5LjE3MC4xOTY6NTM1MyBUNSxVQDuC7pPEB_3CNESXDZpW7yK_z_nskJzNMiQyaygyLmRuc2NyeXB0LWNlcnQubnMxNi5kZS5kbnMub3Blbm5pYy5nbHVl

IPv6:

sdns://AQYAAAAAAAAAIFsyYTAyOmMyMDc6MjAwODoyNTIwOjUzOjoxXTo1MzUzIFQ1LFVAO4Luk8QH_cI0RJcNmlbvIr_P-eyQnM0yJDJrKDIuZG5zY3J5cHQtY2VydC5uczE2LmRlLmRucy5vcGVubmljLmdsdWU

https://servers.opennic.org/edit.php?srv=ns8.fr.dns.opennic.glue
IPv4:

sdns://AQYAAAAAAAAAETE1MS44MC4yMjIuNzk6NDQzIO4Y9lZnORlvodxu39dnm6mFruwTRnlmovbEga4Fyw3TIDIuZG5zY3J5cHQtY2VydC5vcGVubmljLmkycGQueHl6

IPv6:

sdns://AQYAAAAAAAAAG1syMDAxOjQ3MDoxZjE1OmI4MDo6NTNdOjQ0MyDuGPZWZzkZb6Hcbt_XZ5upha7sE0Z5ZqL2xIGuBcsN0yAyLmRuc2NyeXB0LWNlcnQub3Blbm5pYy5pMnBkLnh5eg