Is there a logout function?

Just wondering how to logout once get authed?
Thanks!

As far as I'm aware there is no real logout function for basic authentication. You could try the following option I found on Stackoverflow, but keep in mind the "Basic Auth" is just that, basic authentication ;)
https://stackoverflow.com/a/492926


Create issue templates

Adding issue templates will help the project keep everything organized.
There should at least be one for bug reports to help users submit complete and meaningful bugs.

Don't have access rights to the settings anymore so @knsv will have to take care of this one.

Thx, I added the templates for the project.


Align docstrings with method params

Describe the bug
A clear goal for this package is to be well documented, currently however, there are method parameters missing from documention.
To Reproduce

Read the docs, looking at the explanations and what the methods actually take

Expected behaviour
All method params are documented
Enviroment(please complete the following information):

OS: N/A
Pacakge Version: Latest

I think this is up to date now, but will keep in mind


flutter_localizations & intl dependencies issue during restoration

I have a problem with flutter_localizations + intl during restoration packages for the same flutter environment on different machines:
pub get on dev1 machine:
> fvm flutter pub get

Resolving dependencies...
Because no versions of flutter_date_pickers match >0.4.2 <0.5.0 and flutter_date_pickers 0.4.2 depends on flutter_localizations from sdk, flutter_date_pickers ^0.4.2 requires flutter_localizations from sdk.
And because every version of flutter_localizations from sdk depends on intl 0.18.1, flutter_date_pickers ^0.4.2 requires intl 0.18.1.
So, because my_test_app depends on both intl 0.18.0 and flutter_date_pickers ^0.4.2, version solving failed.

App pubspec.yml
environment:
   sdk: '>=3.0.0 <4.0.0'

dependencies:
  flutter:
    sdk: flutter
  ...
  intl: ^0.18.0
  collection: ^1.17.0
  flutter_date_pickers: ^0.4.2
  ...

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_lints: ^2.0.0

Flutter doctor from dev1
> fvm flutter doctor -v

[✓] Flutter (Channel stable, 3.10.5, on macOS 13.2.1 22D68 darwin-arm64, locale en)
    • Flutter version 3.10.5 on channel stable at /Users/dev/fvm/versions/3.10.5
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 796c8ef792 (8 weeks ago), 2023-06-13 15:51:02 -0700
    • Engine revision 45f6e00911
    • Dart version 3.0.5
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/dev/Library/Developer/android-sdk-macosx
    • Platform android-33, build-tools 32.0.0
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment Microsoft-40648 (build <IP_ADDRESS>+1-LTS)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.12.0

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

[!] 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/macos#android-setup for detailed instructions).

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 13 (API 33) (emulator)
    • iPhone 14 (mobile)          • CF79B28C-B1D8-4260-B422-6B7D053FCAE9 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-2 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 115.0.5790.170

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

But it works for dev2
But it works correctly on the second machine with the same app pubspec.yml and flutter version:
Flutter doctor from dev2
> fvm flutter doctor -v

[✓] Flutter (Channel stable, 3.10.5, on macOS 13.4.1 22F82 darwin-x64, locale en)
    • Flutter version 3.10.5 on channel stable at /Users/dev2/fvm/versions/3.10.5
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 796c8ef792 (8 weeks ago), 2023-06-13 15:51:02 -0700
    • Engine revision 45f6e00911
    • Dart version 3.0.5
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/dev2/Library/Developer/android-sdk-macosx
    • Platform android-33, build-tools 33.0.0
    • ANDROID_HOME = /Users/dev2/Library/Developer/android-sdk-macosx
    • Java binary at: /Users/dev2/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/223.8836.35.2231.10406996/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

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

[✓] Android Studio (version 2022.3)
    • Android Studio at /Users/dev2/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/223.8836.35.2231.10406996/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.4.1 22F82 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 115.0.5790.170

[✓] Network resources
    • All expected network resources are available.

• No issues found!

After some investigation, I see that pubspec.lock regenerates for each machine to use intl 0.18.0 or 0.18.1.
Attached fvm flutter pub deps -v output from both machines:
dev1_deps.txt
dev2_deps.txt
--
Looks similar to #102637 but works depending on pubspec.lock generation.

@wcoder
Thanks for the report. I added the said dependencies but didn't get the reported error.
/Users/dhs/Documents/Fluttersdk/flutter/bin/flutter --no-color pub get
Resolving dependencies...
  material_color_utilities 0.5.0 (0.8.0 available)
Got dependencies!
Process finished with exit code 0

It also maybe due to the package flutter_date_pickers you are using which could be using lesser version of intl, as I see a similar issue in that repo to upgrade the dependency version: https://github.com/MariaMelnik/flutter_date_pickers/issues/109

@darshankawar

I added the said dependencies but didn't get the reported error.

It appears that the issue lies in the restoration of the pubspec.lock. You can review the pub dependency logs provided above for further information.

It also maybe due to the package flutter_date_pickers you are using which could be using lesser version of intl

flutter_date_pickers package is using range:
https://github.com/MariaMelnik/flutter_date_pickers/blob/c69f1fb4b4dbebb03ef654515009c9c0fb86aa96/pubspec.yaml#L13
then dart deps resolve decides what to use, as I understand it.

Thanks for the update. I am unable to replicate the reported behavior, but based on the report and findings related to pubspec.lock, keeping the issue open for team's attention.

@wcoder Looking at the logs it seems like one machine is arm64 and the other x86_64, is that right?
Can you include the two /Users/.../.pub-cache/log/pub_log.txt files for the two machines after running this on each one?
This is probably a pub issue (maybe the heuristic is sensitive to the architecture?), in which case we would probably recommend filing the issue on https://github.com/dart-lang/pub/issues/new/choose.

Looking at the diff:
dev_pub_log.diff.txt
...it seems that for some reason pub thinks dev1's flutter_test depends on test_api 0.6.0 while dev2's depends on test_api 0.5.1. There are other differences too.
I see from the flutter doctor output above that both checkouts think they're on the same version of Flutter, but it sure seems like maybe something has gone wrong here and one is on a slightly older version. Can you try running git diff and git status in both developers' flutter directories? Is one locally modified in some way?

You were absolutely right! Thanks!
The issue was solved by resetting changes in used ~/fvm/versions/3.10.5 the reason for the changes is unknown.
dev1:
> git status

On branch stable
Your branch and 'origin/stable' have diverged,
and have 31 and 1365 different commits each, respectively.
  (use "git pull" to merge the remote branch into yours)

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   dev/automated_tests/pubspec.yaml
        modified:   dev/benchmarks/complex_layout/pubspec.yaml
        modified:   dev/benchmarks/macrobenchmarks/pubspec.yaml
        modified:   dev/benchmarks/microbenchmarks/pubspec.yaml
        modified:   dev/benchmarks/multiple_flutters/module/pubspec.yaml
        modified:   dev/benchmarks/platform_channels_benchmarks/pubspec.yaml
        modified:   dev/benchmarks/platform_views_layout/pubspec.yaml
        modified:   dev/benchmarks/platform_views_layout_hybrid_composition/pubspec.yaml
        modified:   dev/benchmarks/test_apps/stocks/pubspec.yaml
        modified:   dev/bots/pubspec.yaml
        modified:   dev/conductor/core/pubspec.yaml
        modified:   dev/customer_testing/pubspec.yaml
        modified:   dev/devicelab/pubspec.yaml
        modified:   dev/forbidden_from_release_tests/pubspec.yaml
        modified:   dev/integration_tests/abstract_method_smoke_test/pubspec.yaml
        modified:   dev/integration_tests/android_embedding_v2_smoke_test/pubspec.yaml
        modified:   dev/integration_tests/android_semantics_testing/pubspec.yaml
        modified:   dev/integration_tests/android_views/pubspec.yaml
        modified:   dev/integration_tests/channels/pubspec.yaml
        modified:   dev/integration_tests/deferred_components_test/pubspec.yaml
        modified:   dev/integration_tests/external_ui/pubspec.yaml
        modified:   dev/integration_tests/flavors/pubspec.yaml
        modified:   dev/integration_tests/flutter_gallery/pubspec.yaml
        modified:   dev/integration_tests/gradle_deprecated_settings/pubspec.yaml
        modified:   dev/integration_tests/hybrid_android_views/pubspec.yaml
        modified:   dev/integration_tests/ios_add2app_life_cycle/flutterapp/pubspec.yaml
        modified:   dev/integration_tests/ios_app_with_extensions/pubspec.yaml
        modified:   dev/integration_tests/ios_platform_view_tests/pubspec.yaml
        modified:   dev/integration_tests/non_nullable/pubspec.yaml
        modified:   dev/integration_tests/platform_interaction/pubspec.yaml
        modified:   dev/integration_tests/release_smoke_test/pubspec.yaml
        modified:   dev/integration_tests/spell_check/pubspec.yaml
        modified:   dev/integration_tests/ui/pubspec.yaml
        modified:   dev/integration_tests/web/pubspec.yaml
        modified:   dev/integration_tests/web_compile_tests/pubspec.yaml
        modified:   dev/integration_tests/web_e2e_tests/pubspec.yaml
        modified:   dev/integration_tests/wide_gamut_test/pubspec.yaml
        modified:   dev/integration_tests/windows_startup_test/pubspec.yaml
        modified:   dev/manual_tests/pubspec.yaml
        modified:   dev/tools/gen_defaults/pubspec.yaml
        modified:   dev/tools/gen_keycodes/pubspec.yaml
        modified:   dev/tools/pubspec.yaml
        modified:   dev/tools/vitool/pubspec.yaml
        modified:   dev/tracing_tests/pubspec.yaml
        modified:   examples/api/pubspec.yaml
        modified:   examples/flutter_view/pubspec.yaml
        modified:   examples/hello_world/pubspec.yaml
        modified:   examples/image_list/pubspec.yaml
        modified:   examples/layers/pubspec.yaml
        modified:   examples/platform_channel/pubspec.yaml
        modified:   examples/platform_channel_swift/pubspec.yaml
        modified:   examples/platform_view/pubspec.yaml
        modified:   examples/splash/pubspec.yaml
        modified:   packages/flutter/lib/src/widgets/framework.dart
        modified:   packages/flutter/pubspec.yaml
        modified:   packages/flutter/test_private/pubspec.yaml
        modified:   packages/flutter/test_private/test/pubspec.yaml
        modified:   packages/flutter_driver/pubspec.yaml
        modified:   packages/flutter_goldens/pubspec.yaml
        modified:   packages/flutter_goldens_client/pubspec.yaml
        modified:   packages/flutter_localizations/pubspec.yaml
        modified:   packages/flutter_test/pubspec.yaml
        modified:   packages/flutter_tools/pubspec.yaml
        modified:   packages/flutter_web_plugins/pubspec.yaml
        modified:   packages/fuchsia_remote_debug_protocol/pubspec.yaml
        modified:   packages/integration_test/example/pubspec.yaml
        modified:   packages/integration_test/integration_test_macos/pubspec.yaml
        modified:   packages/integration_test/pubspec.yaml

dev2:
> git status

On branch stable
Your branch is behind 'origin/stable' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)

nothing to commit, working tree clean

Oh weird, I wonder if maybe dev1 ran flutter update-packages --force-upgrade'. That's a command we use during development to roll forward our dependencies but isn't something we expect people to run normally, which would cause all the pubspec.yaml` files to get updated.
Maybe we should prevent that command from running on master/main/beta/stable ? cc @christopherfujino

Oh weird, I wonder if maybe dev1 ran flutter update-packages --force-upgrade'. That's a command we use during development to roll forward our dependencies but isn't something we expect people to run normally, which would cause all the pubspec.yaml` files to get updated.
Maybe we should prevent that command from running on master/main/beta/stable ? cc @christopherfujino

My idea for this was, now that we have a bot running this on a CRON, detect from that command if the user has a terminal attached, and if so put a warning that you probably shouldn't be running this command

It looks like the root cause of this was developers mistakenly running the maintainer-only sub-command flutter update-packages --force-upgrade. I am going to close this issue as resolved, and will track making sure this doesn't happen again in https://github.com/flutter/flutter/issues/132800


poll on FolderBranch in SubMan for empty TLF

When user goes into an empty TLF in GUI and upload something, it doesn't show any changes because the subscription manager can't register for changes with an empty FolderBranch. This PR fixes that by polling on trying to get FolderBranch for the TLF at a 1s interval while subscription is active, and make the subscription actually happen and send a notification as soon as it gets a FolderBranch.

CI passed before rebase. Merging


chore(main): release sandworm 1.2.0

:robot: I have created a release beep boop
1.2.0 (2022-09-23)
Features

allow init call from sandworm-mocha module (a63bcd1)
retry sending events to inspector (584eb69)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-js/releases/tag/sandworm-v1.2.0 :sunflower:


Need playbook level "ignore_errors: true"

https://github.com/apigee/henchman/blob/master/henchman/test/plan/invalid/invalidIncludeFormatAtVarsLevel.yaml
Currently the ignore_errors: true is at the task level.
Need support at the plan level, just like sudo: true.
name: "Cleanup Edge Installations"
sudo: true
ignore_errors: true

hosts:
  - central_cassandra
  - zk
tasks:
  - name: Stop Zookeeper if running
    shell: cmd="/opt/cassandra stop" loglevel=debug

  - name: Stop Zookeeper if running
    shell: cmd="/opt/zookeeper stop" loglevel=debug

If ignore_errors: true is specified at plan level.  Should ignore_errors: false override the plan level declaration?

The aim of a plan is to make sure that we have content in there that should fail if things don't work. Its understandable that one or two tasks can fail but having a complete override doesn't completely make sense. Thoughts?

@baskaran-md can we close this one since we opened the other one ?

Sometimes the cleanup tasks are not idempotent. So it might require ignore errors throughout the plan.
Which is the alt ticket?


A compatible .NET SDK was not found - 6.0.302

Project structures.
We are using Dotnet 6 App and using Kudu Build for the deployment, Our app is targets to build on 6.0.302 SDK(global.json) which was working fine till 1 week before on kudu. But now this SDK has been removed from azure kudu and not available anymore. The only available versions are below
remote: 1.1.14 [C:\Program Files (x86)\dotnet\sdk]
remote: 2.1.526 [C:\Program Files (x86)\dotnet\sdk]
remote: 2.2.109 [C:\Program Files (x86)\dotnet\sdk]
remote: 3.1.118 [C:\Program Files (x86)\dotnet\sdk]
remote: 3.1.422 [C:\Program Files (x86)\dotnet\sdk]
remote: 3.1.423 [C:\Program Files (x86)\dotnet\sdk]
remote: 5.0.406 [C:\Program Files (x86)\dotnet\sdk]
remote: 5.0.408 [C:\Program Files (x86)\dotnet\sdk]
remote: 6.0.400 [C:\Program Files (x86)\dotnet\sdk]
remote: 6.0.401 [C:\Program Files (x86)\dotnet\sdk]

The log/error given by the failure.
A compatible .NET SDK was not found.
Requested SDK version: 6.0.302
remote: global.json file: C:\home\site\repository\Web\global.json

remote: 1.1.14 [C:\Program Files (x86)\dotnet\sdk]
remote: 2.1.526 [C:\Program Files (x86)\dotnet\sdk]
remote: 2.2.109 [C:\Program Files (x86)\dotnet\sdk]
remote: 3.1.118 [C:\Program Files (x86)\dotnet\sdk]
remote: 3.1.422 [C:\Program Files (x86)\dotnet\sdk]
remote: 3.1.423 [C:\Program Files (x86)\dotnet\sdk]
remote: 5.0.406 [C:\Program Files (x86)\dotnet\sdk]
remote: 5.0.408 [C:\Program Files (x86)\dotnet\sdk]
remote: 6.0.400 [C:\Program Files (x86)\dotnet\sdk]
remote: 6.0.401 [C:\Program Files (x86)\dotnet\sdk]

Debug your Azure website remotely.

it is recommanded that you share your Web App name, directly or indirectly
we can take a look at what's going on.

Sub: aec......fb3
Site: grc..inter...01
Question:

Is there a way we can install a specific version of dotnet SDK ? If it's removed ?
We don't know why this particular version go removed. Is there any documentation on which dotnet SDK will be supported for long term ?

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


feat: Add create-fedimint-app

Inspired by the create-vite script.
This pull request introduces the create-fedimint-app script, updates dependencies, and adds new templates and tests. The most important changes include the addition of the new script, updates to package dependencies, and the inclusion of new templates and tests for the create-fedimint-app package.
New Script and Templates:

Added create-fedimint-app script to quickly get started with the fedimint-web-sdk. (.changeset/big-lies-wonder.md, packages/create-fedimint-app/index.js, packages/create-fedimint-app/package.json) [1] [2] [3]
Added README for create-fedimint-app with instructions on scaffolding a Vite project. (packages/create-fedimint-app/README.md)
Added Vite + React + TypeScript starter template files. (packages/create-fedimint-app/template-vite-react-ts/README.md, packages/create-fedimint-app/template-vite-react-ts/_gitignore, packages/create-fedimint-app/template-vite-react-ts/index.html, packages/create-fedimint-app/template-vite-react-ts/package.json) [1] [2] [3] [4]

Dependency Updates:

Updated @fedimint/core-web dependency in examples/vite-core/package.json from canary to ^0.0.10. (examples/vite-core/package.json)
Added new dependencies and scripts to the main package.json. (package.json) [1] [2] [3]

Tests:

Added tests for the create-fedimint-app CLI, including prompts and scaffolding checks. (packages/create-fedimint-app/__tests__/cli.test.ts)

Build Configuration:

Added build configuration for the create-fedimint-app package using unbuild. (packages/create-fedimint-app/build.config.ts)

@SocketSecurity ignore<EMAIL_ADDRESS>


F-spot crashes on import Fotos with too many files open

With the latest master I get this strange error when I try to import fotos to the collection. Any idea what it is or how I can fix that?
Unhandled Exception:
GLib.GException: Error opening directory '/home/david/Fotos/2015/05/22': Too many open files
at GLib.FileAdapter.EnumerateChildren (System.String attributes, GLib.FileQueryInfoFlags flags, GLib.Cancellable cancellable) [0x0005c] in :0
at FSpot.FileSystem.GLibDirectory+c__Iterator0.MoveNext () [0x00056] in <9bee6194a6af48d6861d2a29e12d996e>:0
at System.Collections.Generic.List1[T]..ctor (System.Collections.Generic.IEnumerable1[T] collection) [0x0008b] in :0
at System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable1[T] source) [0x00011] in <2392cff65f724abaaed9de072f62bc4a>:0    at FSpot.FileSystem.SortedFileEnumerator..ctor (System.Collections.Generic.IEnumerable1[T] baseEnumerable, FSpot.FileSystem.IFileSystem fileSystem) [0x00014] in <9bee6194a6af48d6861d2a29e12d996e>:0
at FSpot.FileSystem.RecursiveFileEnumerator+c__Iterator0.MoveNext () [0x00130] in <9bee6194a6af48d6861d2a29e12d996e>:0
at FSpot.FileSystem.RecursiveFileEnumerator+c__Iterator0.MoveNext () [0x001d7] in <9bee6194a6af48d6861d2a29e12d996e>:0
at FSpot.FileSystem.RecursiveFileEnumerator+c__Iterator0.MoveNext () [0x001d7] in <9bee6194a6af48d6861d2a29e12d996e>:0
at FSpot.FileSystem.RecursiveFileEnumerator+c__Iterator0.MoveNext () [0x001d7] in <9bee6194a6af48d6861d2a29e12d996e>:0
at FSpot.Import.FileImportSource.NextImageFileOrNull (System.Collections.Generic.IEnumerator1[T] enumerator) [0x00002] in <c94d77e20e1a4170bce58831069af460>:0    at FSpot.Import.FileImportSource+<ScanPhotoDirectory>c__Iterator0.MoveNext () [0x0009c] in <c94d77e20e1a4170bce58831069af460>:0    at FSpot.Import.ImportDialogController.DoScan (FSpot.Import.IImportSource source, System.Boolean recurse, System.Boolean merge, System.Threading.CancellationToken token) [0x00059] in <01535742dcaa401d922c7f20a6ac3d9c>:0    at FSpot.Import.ImportDialogController+<StartScan>c__AnonStorey1.<>m__0 () [0x00032] in <01535742dcaa401d922c7f20a6ac3d9c>:0    at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <f712f98eb8e445c8918edaf595bbe465>:0    at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <f712f98eb8e445c8918edaf595bbe465>:0    at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <f712f98eb8e445c8918edaf595bbe465>:0    at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <f712f98eb8e445c8918edaf595bbe465>:0    at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <f712f98eb8e445c8918edaf595bbe465>:0  [ERROR] FATAL UNHANDLED EXCEPTION: GLib.GException: Error opening directory '/home/david/Fotos/2015/05/22': Too many open files   at GLib.FileAdapter.EnumerateChildren (System.String attributes, GLib.FileQueryInfoFlags flags, GLib.Cancellable cancellable) [0x0005c] in <e52eb98dbf2b47958c1d4f57b170767d>:0    at FSpot.FileSystem.GLibDirectory+<Enumerate>c__Iterator0.MoveNext () [0x00056] in <9bee6194a6af48d6861d2a29e12d996e>:0    at System.Collections.Generic.List1[T]..ctor (System.Collections.Generic.IEnumerable1[T] collection) [0x0008b] in <f712f98eb8e445c8918edaf595bbe465>:0    at System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable1[T] source) [0x00011] in <2392cff65f724abaaed9de072f62bc4a>:0
at FSpot.FileSystem.SortedFileEnumerator..ctor (System.Collections.Generic.IEnumerable1[T] baseEnumerable, FSpot.FileSystem.IFileSystem fileSystem) [0x00014] in <9bee6194a6af48d6861d2a29e12d996e>:0    at FSpot.FileSystem.RecursiveFileEnumerator+<ScanForFiles>c__Iterator0.MoveNext () [0x00130] in <9bee6194a6af48d6861d2a29e12d996e>:0    at FSpot.FileSystem.RecursiveFileEnumerator+<ScanForFiles>c__Iterator0.MoveNext () [0x001d7] in <9bee6194a6af48d6861d2a29e12d996e>:0    at FSpot.FileSystem.RecursiveFileEnumerator+<ScanForFiles>c__Iterator0.MoveNext () [0x001d7] in <9bee6194a6af48d6861d2a29e12d996e>:0    at FSpot.FileSystem.RecursiveFileEnumerator+<ScanForFiles>c__Iterator0.MoveNext () [0x001d7] in <9bee6194a6af48d6861d2a29e12d996e>:0    at FSpot.Import.FileImportSource.NextImageFileOrNull (System.Collections.Generic.IEnumerator1[T] enumerator) [0x00002] in :0
at FSpot.Import.FileImportSource+c__Iterator0.MoveNext () [0x0009c] in :0
at FSpot.Import.ImportDialogController.DoScan (FSpot.Import.IImportSource source, System.Boolean recurse, System.Boolean merge, System.Threading.CancellationToken token) [0x00059] in <01535742dcaa401d922c7f20a6ac3d9c>:0
at FSpot.Import.ImportDialogController+c__AnonStorey1.<>m__0 () [0x00032] in <01535742dcaa401d922c7f20a6ac3d9c>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in :0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in :0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in :0

@dkoeb can you take a look at this?

That's quite likely a bug I introduced with the latest pull request :-(
@codingdave if you need a working build for now, go back to e1265e2c5c133461ce18f3997b896d0a014b5c8f
I'll try to fix it within the next days.

@codingdave I just did a quick test with a quite large list of files (tens of thousands) but could not reproduce the exception. Could you share some more details on your environment? (e.g, number of files in the folder you tried to import, file types)

@dkoeb sure.
git describe
0.8.0-644-ga6b4d190
uname -a
Linux UX32VD 4.8.0-40-generic #43-Ubuntu SMP Thu Feb 23 16:01:19 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
find ~/Fotos/ -type f -iname "*.JPG" -exec ls {} ; | wc -l
17757
find ~/Fotos/ -type f -not -iname "*.JPG" -exec ls {} ; | wc -l
3
find ~/Fotos/ -type d  | wc -l
1504
The is reproducible with every try on my side. What else can I provide?

I reverted to the revision mentioned above. It also crashes. Interestingly it seems that f-spot also has trouble with my exif data and at some point starts to create xmp files for all following jpgs. Maybe this is related?
david@UX32VD:~/w/f-spot.git|stable⚡*?
➤ ~/unstable/f-spot/bin/f-spot
[Info  20:38:29.379] Initializing Mono.Addins
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
(f-spot:23877): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
** (f-spot:23877): WARNING **: Invalid borders specified for theme pixmap:
/usr/share/themes/Breeze/gtk-2.0/../assets/line-h.png,
borders don't fit within the image
[Warn  20:38:36.026] Metadata of file file:///home/david/Fotos/2004/01/01/STA60133.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:36.546] Metadata of file file:///home/david/Fotos/2004/01/03/STA60356.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:38.122] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0127.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:38.644] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0126.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:39.160] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0125.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:39.676] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0124.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:40.199] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0123.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:40.717] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0122.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:41.236] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0121.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:41.754] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0120.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:42.266] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0119.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:42.778] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0118.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:43.290] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0117.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:43.803] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0116.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:44.320] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0115.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:44.838] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0113.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:45.351] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0112.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:45.879] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0111.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:46.392] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0109.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:46.904] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0108.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:47.418] Metadata of file file:///home/david/Fotos/2007/09/26/DSC_0107.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  20:38:47.740] Caught an exception - Hyena.Data.Sqlite.SqliteException: Sqlite error 14: unable to open database file (SQL: INSERT INTO rolls (time) VALUES<PHONE_NUMBER>)) (in `Hyena.Data.Sqlite')
at Hyena.Data.Sqlite.Connection.CheckError (System.Int32 errorCode, System.String sql) [0x00042] in :0
at Hyena.Data.Sqlite.Connection.Execute (System.String sql) [0x00021] in :0
at Hyena.Data.Sqlite.HyenaSqliteCommand.Execute (Hyena.Data.Sqlite.HyenaSqliteConnection hconnection, Hyena.Data.Sqlite.Connection connection) [0x000a8] in :0
Unhandled Exception:
Hyena.Data.Sqlite.SqliteException: Sqlite error 14: unable to open database file (SQL: INSERT INTO rolls (time) VALUES<PHONE_NUMBER>))
at Hyena.Data.Sqlite.HyenaSqliteCommand.WaitForResult (Hyena.Data.Sqlite.HyenaSqliteConnection conn) [0x00049] in :0
at Hyena.Data.Sqlite.HyenaSqliteConnection.Execute (Hyena.Data.Sqlite.HyenaSqliteCommand command) [0x0000e] in :0
at FSpot.Database.RollStore.Create (System.DateTime time_in_utc) [0x00027] in <36ec76427fb34676bb6062e735cd2151>:0
at FSpot.Database.RollStore.Create () [0x00007] in <36ec76427fb34676bb6062e735cd2151>:0
at FSpot.Import.ImportController.DoImport (FSpot.Database.IDb db, FSpot.Core.IBrowsableCollection photos, System.Collections.Generic.IList1[T] tagsToAttach, System.Boolean duplicateDetect, System.Boolean copyFiles, System.Boolean removeOriginals, System.Action2[T1,T2] reportProgress, System.Threading.CancellationToken token) [0x00047] in <0bae3e55f1fe4a58babeb31bb9c1aa48>:0
at FSpot.Import.ImportDialogController.DoImport (System.Threading.CancellationToken token) [0x0005e] in <4736f7bb28f0409f81cfbe58844a260e>:0
at FSpot.Import.ImportDialogController.m__0 () [0x0000c] in <4736f7bb28f0409f81cfbe58844a260e>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in :0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in :0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: Hyena.Data.Sqlite.SqliteException: Sqlite error 14: unable to open database file (SQL: INSERT INTO rolls (time) VALUES<PHONE_NUMBER>))
at Hyena.Data.Sqlite.HyenaSqliteCommand.WaitForResult (Hyena.Data.Sqlite.HyenaSqliteConnection conn) [0x00049] in :0
at Hyena.Data.Sqlite.HyenaSqliteConnection.Execute (Hyena.Data.Sqlite.HyenaSqliteCommand command) [0x0000e] in :0
at FSpot.Database.RollStore.Create (System.DateTime time_in_utc) [0x00027] in <36ec76427fb34676bb6062e735cd2151>:0
at FSpot.Database.RollStore.Create () [0x00007] in <36ec76427fb34676bb6062e735cd2151>:0
at FSpot.Import.ImportController.DoImport (FSpot.Database.IDb db, FSpot.Core.IBrowsableCollection photos, System.Collections.Generic.IList1[T] tagsToAttach, System.Boolean duplicateDetect, System.Boolean copyFiles, System.Boolean removeOriginals, System.Action2[T1,T2] reportProgress, System.Threading.CancellationToken token) [0x00047] in <0bae3e55f1fe4a58babeb31bb9c1aa48>:0
at FSpot.Import.ImportDialogController.DoImport (System.Threading.CancellationToken token) [0x0005e] in <4736f7bb28f0409f81cfbe58844a260e>:0
at FSpot.Import.ImportDialogController.m__0 () [0x0000c] in <4736f7bb28f0409f81cfbe58844a260e>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in :0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in :0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in :0

well, this now is a different issue, an SQLite one. This also happened for all my tries (2 of 2).

btw, the trouble with the exif info is also with the latest revision

It's the number of folder, not the number of files that causes this issue.
@codingdave please, let me know if #82 fixes the issue on your system and I will merge it to master.
Your second observation is not related. Would you mind opening a separate issue?

@dkoeb thanks for the fix. This really was the reason. I was able to import all my files without f-spot crashing:
david@UX32VD:~/w/f-spot.git|users/dkoeb/issue-81⚡*?
➤ ~/unstable/f-spot/bin/f-spot
[Info  23:40:46.399] Initializing Mono.Addins
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
(f-spot:20939): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
** (f-spot:20939): WARNING **: Invalid borders specified for theme pixmap:
/usr/share/themes/Breeze/gtk-2.0/../assets/line-h.png,
borders don't fit within the image
[Warn  23:40:52.598] Metadata of file file:///home/david/Fotos/2003/10/31/03-11-08_Freitag_20.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
[Warn  23:40:53.124] Metadata of file file:///home/david/Fotos/2004/01/01/STA60158.JPG may be corrupt, refusing to write to it, falling back to XMP sidecar.
...
hundreds of xmp issues of the same kind (I'll file a new case about it)
...
(f-spot:20939): Gdk-WARNING **: losing last reference to undestroyed window
[Info  00:03:38.243] Exiting...
(f-spot:20939): GLib-CRITICAL **: Source ID 73138 was not found when attempting to remove it
(f-spot:20939): GLib-CRITICAL **: Source ID 61772 was not found when attempting to remove it
(f-spot:20939): GLib-CRITICAL **: Source ID 52458 was not found when attempting to remove it
(f-spot:20939): GLib-CRITICAL *: Source ID 66891 was not found when attempting to remove it
david@UX32VD:~/w/f-spot.git|users/dkoeb/issue-81⚡?

please merge to master ;-)

merged e83d49c5795145f878afedd75ab2de4ec929c4dc


[TINY] Simplify "Included Types" code sample

Remove the unneeded Fluent API calls to get a type included in the
model.
Fixes aspnet/EntityFramework/5855

:shipit:


Vertical scrollbar always shown

I would like to know if there is a possibility to have an always shown vertical scrollbar on the Scintilla control, and if it is, how?
I tried to do it on my own, but I've failed. After cloning the repository and trying to discover how the current scroll controls works, I gave up, sorry!
Thank you for any hint!

I am not 100% certain, but I don't think Scintilla has the ability to keep the vertical scrollbar visible when it's not needed. If I'm not wrong, you'd have to hack the native version of the component to change this behaviour.

I believe this is correct. You can control whether the vertical scroll is displayed when necessary but not whether it is displayed all the time. I seem to remember looking into hacking this and it was a nightmare.

You could hide the scrollbar in ScintillaNet and then add a separate scrollbar control next to the ScintillaNet control and link the using events. I did something similar when I started writing a custom scrollbar that could show indicators on it like the one in VS.
https://docs.microsoft.com/en-us/dotnet/framework/winforms/controls/hscrollbar-and-vscrollbar-controls-overview-windows-forms


how to run a custom express server with typescript and nextjs?

{
  // package.json
  "name": "with-typescript",
  "version": "1.0.0",
  "scripts": {
    "dev": "concurrently \"tsc --watch\" && node server.js"
  },
  "dependencies": {
    "express": "^4.15.4",
    "express-logging": "^1.1.1",
    "logops": "^2.1.0",
    "next": "latest",
    "react": "^15.5.4",
    "react-dom": "^15.5.4"
  },
  "devDependencies": {
    "@types/node": "^8.0.20",
    "@types/react": "^15.0.1",
    "babel-plugin-root-import": "^5.1.0",
    "babel-preset-es2015": "^6.24.1",
    "babel-register": "^6.24.1",
    "concurrently": "^3.1.0",
    "typescript": "^2.1.5"
  }
}

// server.ts
import express from 'express';
import next from 'next';

const dev = process.env.NODE_ENV !== 'production';
const port = process.env.PORT || 3000;
const app = next({ dev });
const handle = app.getRequestHandler();

app.prepare()
  .then(() => {
    const server = express();

    server.get('*', (req, res) => {
      return handle(req, res);
    });

    server.listen(port, (err) => {
      if (err) throw err;
      console.log(`> Ready on http://localhost:${port}`);
    });
  });

If I run npm run dev nothing really happens.
If I instead run change the script to "dev": "node server.js"
I get an error TypeError: next_1.default is not a function
Since server.ts is being converted to server.js it gives me this line where this error is:
const app = next_1.default({ dev }); from const app = next({ dev });
So question is, how can I run custom express server using typescript?

It's because default ESM import transpiles to require.default so use CommonJS.
If you want to use ESM, try import * as next from 'next' or import * from 'next' (0% guarantee, I don't know how TypeScript will handle this.)

this seems to work.
What I can't get to work is the script to run both tsc and node
"dev": "concurrently \"tsc --watch\" && node server.babel.js -p $PORT",
It just runs the first part before &&

that's not how concurrently works, it doesn't split off tsc somewhere else. what you'll need to do is:
concurrently \"tsc --watch\" node server.babel.js -p $PORT

@retrixe I tried that but gave me error, I got it working like this though:
"dev": "concurrently \"tsc --watch\" \"node server.babel.js -p $PORT\"",
Thank you!

no problem, i was about to edit my comment. seems like concurrently only takes one word commands if you wish to remove the quotes.

here is a example for using next.js width koa2 & typescript:  https://github.com/lvlinhaohan2010/next-koa2-typescript-starter

Anybody have any tips on getting the custom server going in light of the latest next 5 release?

Don't use older TypeScript + Next.js boilerplates.
Continue running the custom server like you used to, you can use nodemon with ts-node to run it and with Next.js 5, use @zeit/next-typescript along with your custom server in combination with @zeit/next-css or whatever you happen to require.
And get rid of concurrently. Just start the custom server and next-typescript or your custom ts-loader configuration in next.config.js will keep you good to go.

That works great @retrixe ! Thank you so much!

@retrixe Would you be willing to submit a PR to add a custom-server-typescript example like was mentioned in #3694? I'm using nodemon to execute ts-node --project tsconfig.server.json server.ts (using ES import and need to use commonjs module option), but something is killing the server after a short period of time. I'm clearly missing something and would be interested in seeing your solution.

I also ran into more odd issues and strange behavior telling me I have some setup wrong @corydeppen . I would be willing to buy @retrixe a beer or coffee if I had a working example for inspiration :)

@zachariahtimothy @corydeppen see #3838 :smile:

Set "esModuleInterop": true will fix TypeError: next_1.default is not a function.


c++/cli mqttClientHandleMessageReceived callbacks

Describe your question
Correct way to add mqttClient callbacks for mqttClientHandleMessageReceived,MqttClientConnectedEventArgs in c++/cli
Which project is your question related to?

Client

Current State Of Project
I created a c++/cli project in the hopes of still using native c++ libraries and also using c# + windows forms to make a quick GUI
I have compiled MqttNet and linked the dll's with my project, everything compiles and my application works
I need to add Mqtt functionality so I chose this library(MqttNet)
Below is the reccomend way of creating a delegate
client.ApplicationMessageReceivedHandler = new MqttApplicationMessageReceivedHandlerDelegate(e => OnAppMessage(e));
but c++/cli does not feature the => operator
below I have tried some of my own attempts to bind the functions but with no luck
//private: void ConnectedHandler(System::Object^ sender, EventArgs^ e)
private: void ConnectedHandler(MQTTnet::Client::Connecting::MqttClientConnectedEventArgs^ connectedArgs)
{
	//connected functionality goes here
}

private: System::Void setupMqttClient()
{
	// Create a new MQTT client.
	auto factory = gcnew MqttFactory();
	this->mqttClient = factory->CreateMqttClient();
	String^ username = txtMqttUsername->Text;
	String^ password = txtMqttPassword->Text;
	auto clientOptions = gcnew MQTTnet::Client::Options::MqttClientOptionsBuilder();
	clientOptions->WithClientId("Client1");
	clientOptions->WithTcpServer("<IP_ADDRESS>", 1337);
	clientOptions->WithCredentials(username,password);
	auto options = clientOptions->Build();

mqttClient->ConnectedHandler = gcnew  MQTTnet::Client::Connecting::MqttClientConnectedHandlerDelegate(ConnectedHandler);
	mqttClient->ConnectedHandler = gcnew  MQTTnet::Client::Connecting::MqttClientConnectedHandlerDelegate(&ConnectedHandler);
	mqttClient->ConnectedHandler = gcnew  MQTTnet::Client::Connecting::MqttClientConnectedHandlerDelegate(this, &ConnectedHandler);
	mqttClient->ConnectedHandler = gcnew  MQTTnet::Client::Connecting::MqttClientConnectedHandlerDelegate(gcnew Action(this, MainForm::ConnectedHandler));

}

I hope someone may be able to point me in a better direction

https://en.cppreference.com/w/cpp/language/lambda

Your last attempt was really close. I think you can use the following:
mqttClient->ConnectedHandler = gcnew MQTTnet::Client::Connecting::MqttClientConnectedHandlerDelegate(
    gcnew Action<MQTTnet::Client::Connecting::MqttClientConnectedEventArgs^>(this, &ConnectedHandler));

I assume this is answered and not an issue of this library.


Update Hemi RPC URL

The RPC URL needs to be added to github variables, by setting

NEXT_PUBLIC_CUSTOM_RPC_URL_HEMI_SEPOLIA_PROD
NEXT_PUBLIC_CUSTOM_RPC_URL_HEMI_SEPOLIA_STAGING

Added to the repo's variables.

Reopening (it will be closed after merging #545)


add arbitrable contract title in the store provider

Pull Request Test Coverage Report for Build 441

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 69.856%

Totals

Change from base Build 437:
0.1%

Covered Lines:
591

Relevant Lines:
772

💛  - Coveralls


Added liveness and readiness checks to collector and query

The idea of this PR is to create a first version of the readiness and liveness checks. It can be improved in the future to expose the metrics from expvar, so that an orchestration service can auto scale based on the data reported by this.
Similarly, this would allow the server to keep booted even if the underlying data store is offline: while the main HTTP port might still accept incoming requests and put on a buffer, the health check endpoint might return a degraded state, so that admins could get notified if something is wrong.
Sample output for "ready and alive":
curl -v http://localhost:17686/
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 17686 (#0)
> GET / HTTP/1.1
> Host: localhost:17686
> User-Agent: curl/7.53.1
> Accept: */*
>
< HTTP/1.1 204 No Content
< Date: Thu, 20 Jul 2017 12:18:20 GMT
<
* Connection #0 to host localhost left intact

Sample output for "booted, but in trouble" (ie: not passing liveness check):
curl -v http://localhost:15268/
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 15268 (#0)
> GET / HTTP/1.1
> Host: localhost:15268
> User-Agent: curl/7.53.1
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Date: Thu, 20 Jul 2017 12:19:38 GMT
< Content-Length: 20
< Content-Type: text/plain; charset=utf-8
<
* Connection #0 to host localhost left intact
Server not available

Sample output for "booting" (ie: not passing readiness check):
curl -v http://localhost:15268/
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 15268 (#0)
> GET / HTTP/1.1
> Host: localhost:15268
> User-Agent: curl/7.53.1
> Accept: */*
>
< HTTP/1.1 503 Service Unavailable
< Date: Thu, 20 Jul 2017 12:20:12 GMT
< Content-Length: 20
< Content-Type: text/plain; charset=utf-8
<
* Connection #0 to host localhost left intact
Server not available

Coverage remained the same at 100.0% when pulling 95b5f4c708e9922f5c1c6edddeb78bd51360618b on jpkrohling:JPK-LivenessReadinessChecks into f53da8657d78fb1da169cb357526a37dc1b8ac27 on uber:master.

Looks like I need to do some better testing before sending PRs :)
/tmp/go-build859975043/github.com/uber/jaeger/cmd/standalone/_test/standalone.test flag redefined: health-check.http-port

Coverage remained the same at 100.0% when pulling b1445036b6a9418290903e15daf49cfab90728bb on jpkrohling:JPK-LivenessReadinessChecks into f328d3a266681eb330f089dedbe3c8faae76055d on uber:master.

Coverage remained the same at 100.0% when pulling b1445036b6a9418290903e15daf49cfab90728bb on jpkrohling:JPK-LivenessReadinessChecks into f328d3a266681eb330f089dedbe3c8faae76055d on uber:master.

@yurishkuro , is this feature something you'd consider merging? If so, which changes would be needed, other than having the health check server on its own source files?

Yes, it makes sense to merge. A few thoughts:

I would make it a separate shared component, somewhere in /pkg/health, and reuse in collector/agent/query
it should be a struct that can be created in main() and have methods to start serving and to change status
at Uber we usually handle SIGTERM by changing the health state to "unavailable" first, and then existing after a short delay. It allows health endpoint to be used in traffic controllers so that it will stop sending requests to the service, thus allowing it to drain/finish in flight requests before exiting

I just updated this PR to implement the first two points (except that I didn't do it for the agent).

at Uber we usually handle SIGTERM by changing the health state to "unavailable" first, and then existing after a short delay. It allows health endpoint to be used in traffic controllers so that it will stop sending requests to the service, thus allowing it to drain/finish in flight requests before exiting

I understand that you have your own main.go file, so, is this something we need to handle here? If so, I'm not quite sure I understand what has to be done: should I change the status when receiving a signal and let the code "sleep" for some time? From what I understand, that wouldn't help that much, as the HTTP server would already be down, no?

Coverage remained the same at 100.0% when pulling 54b4e970d2f9767a380002005fc3c0e61d9c5891 on jpkrohling:JPK-LivenessReadinessChecks into 43a18f4e73d97d0800f68e5b32001ad2702e06d9 on uber:master.

Coverage remained the same at 100.0% when pulling f28b8ab6a8eb06967edf298681bad0440e7809c4 on jpkrohling:JPK-LivenessReadinessChecks into 87b6a3b584f98dd13a5cdc85acd1193af993cf46 on uber:master.

PR updated to fix the merge conflicts. Once this is merged, I'll send a plan to refactor the bootstrap code, to be more testable and reusable.

Coverage remained the same at 100.0% when pulling 3636e5a3608b73fe021258ae552402b34da2a234 on jpkrohling:JPK-LivenessReadinessChecks into 7daccda31e93e05d9244ad038e8d0297ddd72cca on uber:master.

I just updated the PR with some tests. Although the tests would pass fine without the Close() method on the handler, I added it anyway, as I don't like the idea of just letting processes to linger on random ports, even if just during the tests :)

Coverage decreased (-0.1%) to 99.855% when pulling 599a4a2b3e7f397f02acc897f2679d71a9353415 on jpkrohling:JPK-LivenessReadinessChecks into 43ef964c095bb3c4f08a620f0b5171342be0435a on uber:master.

Coverage decreased (-0.1%) to 99.855% when pulling c4be25a6599cf542e2119494ee6f42ad6c286abb on jpkrohling:JPK-LivenessReadinessChecks into 43ef964c095bb3c4f08a620f0b5171342be0435a on uber:master.

Coverage decreased (-0.06%) to 99.936% when pulling 13dc29d6e1b1487677e9645dc6b905c4a23a17f2 on jpkrohling:JPK-LivenessReadinessChecks into 43ef964c095bb3c4f08a620f0b5171342be0435a on uber:master.

We need to investigate why 1.8 is so shower. Meanwhile I'd go with splitting the server and listener in the health server (it does not need to be exposed to main).

Coverage decreased (-0.03%) to 99.968% when pulling 67962aea9e3fb143fc5847488d3f2f6e21cba6e0 on jpkrohling:JPK-LivenessReadinessChecks into b3817054f6e9e276227b4914eac4a6c36772a8c1 on uber:master.

Coverage decreased (-0.03%) to 99.968% when pulling a61e53fe7e2e189d5a73e068cb91fd61be558814 on jpkrohling:JPK-LivenessReadinessChecks into b3817054f6e9e276227b4914eac4a6c36772a8c1 on uber:master.

Coverage decreased (-0.03%) to 99.968% when pulling 169da0733e898d961c716ff294ce34180385fe34 on jpkrohling:JPK-LivenessReadinessChecks into b3817054f6e9e276227b4914eac4a6c36772a8c1 on uber:master.

Coverage decreased (-0.03%) to 99.968%

It's because of one line that is reached only when http.Serve returns. I couldn't find a reasonable way to test it on 1.7.

I think if you stop/close the listener the Serve method exists with the error. You have similar code in the Agent, and its test has 100% coverage.

Coverage remained the same at 100.0% when pulling 5daf319a99f61c651ed6c9dec6c1f875fae73051 on jpkrohling:JPK-LivenessReadinessChecks into b3817054f6e9e276227b4914eac4a6c36772a8c1 on uber:master.


Add the crop-like setting to the test or val dateset pipeline

Add the crop-like setting to the test or val datasets pipeline
Motivation
Due to some reason, the images I used to build datasets involve interference on the broad edge of the image. I can crop the parts I wanted, but I don't want to save the parts image because of information loss,  otherwise training or test them directly.
But, I found when add crop operation to test_pipeline, the AP calculated to 0.0 always. And https://github.com/open-mmlab/mmdetection/issues/5340 issued same problem.
So, will you take care of it?

We do not support this operation now, If you want to crop while testing, you need write code in the test pipeline to support this.

Thanks, I try to write code, could you let me know which part or where can I locate the core.


Redux Challenge 10, introductory text might be unclear

The following section seems a bit unclear to me
The name you give to the keys will be used by Redux as the name for the associated piece of state.

What does this mean? And how is this used when a message is dispatched to the store?

@Pethaf it means that if you define a reducer with the name users, and then pass this to redux your state tree (an object) will have a key users in it, whose state is controlled by that users reducer. Feel free to submit a PR to clarify the language if you think we can explain it better!


Move runtime spec into submodule

This allows to add the image spec as parallel module later on.
Refers to https://github.com/containers/oci-spec-rs/issues/10

Codecov Report

Merging #11 (e5ce8c0) into main (88a9cb7) will decrease coverage by 0.76%.
The diff coverage is 25.23%.

@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
- Coverage   25.00%   24.23%   -0.77%
==========================================
  Files           5        6       +1
  Lines         556      590      +34
  Branches      315      320       +5
==========================================
+ Hits          139      143       +4
- Misses        158      172      +14
- Partials      259      275      +16


Add prompts for page title, subtitle, link, subtitle link to afqbrowser-assemble

Add add something to the documentation about how to change the page title

Resolved by #245 and #252.


0.4.21 compiler error with sdl2 2.0.8

go-sdl2 0.4.21 references SDL_SensorType in sdl/gamecontroller.go like so:
static SDL_bool SDL_GameControllerHasSensor(SDL_GameController *gamecontroller, SDL_SensorType type)
{
    return SDL_FALSE;
}
..other functions..

But since SDL_SensorType is not defined in sdl 2.0.8 this results in a compiler error.
../../.go/pkg/mod/github.com/veandco/go-sdl2@v0.4.21/sdl/gamecontroller.go:227:86: error: unknown type name 'SDL_SensorType'; did you mean 'SDL_EventType'?
 static float SDL_GameControllerGetSensorDataRate(SDL_GameController *gamecontroller, SDL_SensorType type)

A simple fix would be to typedef SDL_SensorType in gamecontroller.go if the version is not at least 2.0.14
typedef SDL_SensorType int;

Hi @kazzmir, thanks for reporting this issue! It should be fixed in v0.4.22 now.

works great!


Upgraded to Jint v3

Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[x] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] All new and existing tests passed

Description
As discussed in #84 this PR is to cover the upgrade of AngleSharp.Js to use Jint v3.
Changes made:

Upgraded Nuget package reference of Jint to v3.0.0.
Changed target framework of project to .NET Standard 2.0 and .NET Framework 4.6.2 to match the Jint v3 targets.
Updated Jint namespaces and class names (e.g. FunctionInstance > Function) to match the changes made in Jint v3.
Updated EngineInstance to remove the lexical and variable environments since those are no longer public in Jint v3. Instead there is now a global window object which also gets exposed on the global object (to ensure that things like window.location.href and location.href resolve to the same thing).
Replaced ConsoleInstance with a new Console class that ties it directly to the Window object (as per JS spec).
Removed obsolete classes that have been replaced by Jint equivalents (e.g. DomDelegateInstance > ClrFunction).
Checked that all existing unit tests are passing, and added a new ECMA test class. I've only added a single test in there to check that loading an ECMA script succeeds, but feel free to suggest any other tests required.

Also a shoutout to @lahma for providing some guidance and older test code that helped me figure out the global object changes. 👍

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Also another question - what about #87 ? Should we bring this in (the test and fix, if that still applies)?

I think #87 should be merged in devel first since it's been around for a while, and then I can rebase my branch on that one to ensure my changes work with that fix.

Merged into devel. Thanks for taking this and putting in the effort @tomvanenckevort !

We're note quite there yet.
I ran some extra tests locally yesterday and realised that the <script type="module"> tags currently don't work. So I need to have another look at that one.
But I guess we can handle that via another PR :)

Yes, I mean it's anyway just a first preview. I've assigned some / relevant issues to the v1 milestone.
I am not sure yet how much I can look into them tonight and on the weekend, but my goal would be to have a bit of focus now on AngleSharp.Js to have this as a 1.0.0. Thanks for your PR and motivating me to do so.
If you want to pick up / anyway have some of these issues handled then please comment on them. Otherwise I'll just pick up whatever is left.

Preview is out (https://www.nuget.org/packages/AngleSharp.Js/0.15.0-beta.16).
The version is still placed at 0.15 and I also noticed that some parts of the NuGet package definition (e.g., the README) are missing: I'll add those and push to devel.

Awesome work @tomvanenckevort ! I'll hopefully have some timesoon  too to check this out and investigate if there's something that Jint could improve too. Just have to get back from vacation first 😄

Preview is out (https://www.nuget.org/packages/AngleSharp.Js/1.0.0-beta.20); incl. latest target frameworks, correct reference to Jint and AngleSharp, README etc.
I think from the infrastructure POV we are done, now we "only" need to clear the outstanding issues and have it (draw the rest of the owl).


BUG: The statistics graph does not work

Maybe there was some temporary issue at hosting service provider end. Closing this issue


SVG to PNG in Safari/Chome IOS

Hi - The output svg of Raphael JS is different for Safari and Chrome mobile hence I face an issue when I export it as the converter from svg to png doesn't support this particular format. Is there are any work around?
For the Desktop Chrome I use the following libs/js syntax and it works fine.
`var innerSVG = canvasCollage.innerHTML;
    var fixedSVG = svgfix(innerSVG);
    canvg(data.canvasOutputId, fixedSVG, {
        renderCallback : function() {
            //to something
        }
    });`

*svgfix - http://nerdyjs.com/script/345449
*canvg - http://canvg.github.io/canvg/canvg.js
Any suggestion would be much appreciated. Thanks.

have you try to do "svg" to "canvas" to "png" work ???


Allow inbound 443 when using custom vnet + azure firewall

I think we need to allow the user to specify if they'd like to open up inbound internet access to their cluster/ingress point.

Closing this as the AZFW only controls egress traffic in the Custom Vnet config

Reopening because the AZFW is killing the traffic 🥼
Purely adding this made the voting app work

@khowling - fyi.


Getting Ruby 3.3.0 working

Had to:
uncomment redis gem
run bundle update
Then after running rails db:migrate there were changes to db/schema.rb that I don't fully understand.

coverage: 94.555%. remained the same
when pulling<PHONE_NUMBER>b618552c7b79d42fdb6eb2b5d20451 on njw-ruby-3.3.0
into 83b006124a153bcb3ce552ad9b9a9b5891b24cfd on main.

@mo-nathan -

I notice that your bundle update is updating turbo-rails here, which is brand new and a huge update, it likely has breaking changes. You'll need to lock it at version 1.5.x for now.
We don't use redis yet, and it does not seem to be a dependency of any other gem, either. I believe it should stay commented out.

@mo-nathan did you get everything working? should we close this PR?

Yeah, I think we're good here.  Thanks for the help!


setCookie middleware is not working with 2 or more cookies in deno deploy

What version of Hono are you using?
3.11.12
What runtime/platform is your app running on?
Deno
What steps can reproduce the bug?
Create a endpoint, use the setCookie middleware to set 2 cookies or more, deploy the project and make the request to the endpoint url.
my code:

The server response

As you can see, only the last cookie y set in response headers. I have checked if the token_name is added to the environment variables and is reading it correctly.
What is the expected behavior?
Two cookies in the response headers.
What do you see instead?
Only the last cookie is set.
Additional information
this is my deno.json file with the hono imports:

I'm using the helper, so I am importing setCookie middleware from<EMAIL_ADDRESS>

Hi @diecodev
I can't reproduce it. I can set two cookies with setCookie() in the cookie helper on Deno Deploy. Could share us minimal code to reproduce the bug?

hi @yusukebe
After bunch of local testing it seems like the compress() middleware is the cause of the problem, i let you a link to the reproduction link and code

@diecodev
Thank you very much! I'll see it later.


SignInManager.SignInAsync will skip PreSignInCheck

When I set "RequireConfirmedEmail = true" in SignInOptions, the SignInManager.SignInAsync will skip PreSignInCheck (ex. Check the Email confirmed).
The visual studio template Account/Register action will take the SignInAsync method.
So, When I register a new account, I will sign-in successful. Then, if I log out, I could't sign-in again.
So, I think that SignInAsync method should take the PreSignInCheck?

CanSignIn is the method that looks at the SignInOptions like RequireConfirmedEmail.  The two normal flows (PasswordSignIn/ExternalSignIn) ensure that CanSignIn is true before calling SignIn.  But if you are directly calling SignInAsync, you will need to check that the user can sign in first if desired.
We could tweak this a bit, by having an overload of SignInAsync that takes a bool checkCanSignIn to clear this up a bit.
Thoughts @divega @blowdart @rustd?

I don't think the parameter clarifies anything :(

Well atleast it puts it in the API so users can see. Without it they need to find the other API to call :)

Well the implementation change with the new overload would push the check into SignIn instead of Password/External, so we could have SignIn default to check the flag, and only if you explicitly disabled it would you get the existing behavior (so it'd be a slight breaking change)

ok, I got it.
But, there is still a problem about the project template in Visual Studio (2015 Update1) :
if I set RequireConfirmedEmail = true in SignInOptions,
When I register a new account, I will login success. Then, if I logout, I couldn't login again.

That is by design, you can't login if the email isn't confirmed.  You should make sure there's a flow to confirm the email before logging them in.


Feature : Addition of scroll back to top button

Description

I want to add scroll back to top button for this website.
This will improve website’s User Experience(UX) with an arrow, when a user start scrolling the page. The page smoothly scrolls back to top when the the button is clicked.

Screenshot

Please assign me to work for this feature under GSSOC '22.

@flyingsonu122 I'm almost done with the issue I will send PR regarding this tomorrow ASAP

Sorry for the delay @flyingsonu122  I was busy in SIH 22 and will complete it ASAP. I know it's too late to close this issue.


Add horizontal scroll bar

The Copilot Chat window does an excellent job of flowing text to match the available width of the chat window, except when it's displaying source code.  The source code frequently goes past the right edge of the chat window in order to maintain readable formatting (this is all good).
Would you mind adding a horizontal scroll bar to the chat window so that one can scroll left and right to see all the source code, without having to resize the chat window?

You should already be able to scroll the code block themselves. The scrollbar may not show until you scroll or you place your cursor at the bottom of the code block in chat

Opening an issue to see if we should also respect editor.scrollbar.horizontal here
The other option is to set "chat.editor.wordWrap": "on" which will wrap the contents of the code block to fit the available area

Sorry!  I didn't see the scrollbar appear, but now that I went back, tried it, and looked for it it's definitely there.
Thanks!


[language][prover] Extended syntax of specifications to allow vector …

…index
using v[i].  Added a test case.
We plan several more extensions soon to support vector specification.
There is also some code for subranges, although it doesn't generate an AST
yet (I'm having some misgivings about how I added it to the parser).
This is incomplete because boogie is not being generated.  For now, use
of this feature generates dummy boogie code.
I also moved aborts_if test from tests/translator_tests.rs to
prover_tests.rs because it was in the wrong file.

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

@bors-libra r=junkil-park

:pushpin: Commit 5f644fc has been approved by junkil-park

@bors-libra r+

:bulb: This pull request was already approved, no need to approve it again.

There's another pull request that is currently being tested, blocking this pull request: #2547

:pushpin: Commit 5f644fc has been approved by DavidLDill

:hourglass: Testing commit 5f644fcdb63c7cf879b15ac207bc109127208b34 with merge 223467986cca41f1156ee05b230ac04c12ef6e63...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: DavidLDill
Pushing 223467986cca41f1156ee05b230ac04c12ef6e63 to master...


New forest icon / outdoor store icon

Give the current tree icon used for outdoor to "forest" stuff, and make a new icon for outdoor gear.

Forest icon styling is looking good :)

done.


Add a setting for SDK download

Closes #1433

Add fileds for setting Codegen instance in Setting platform: collection and view
Change condition for button 'SDK Generator': Button is available if there is a setting for SDK generator
Change host from generator.swagger.io to the Codegen instance defined in Settings.

Please be aware that @jykae is restructuring the Documentation module folder to follow our recently added folder structure guidelines.
The relevant part is as follows:

/component_name

/client

/sub_component

sub_component.html
sub_component.js

/sub_component_2

sub_component_2.html
sub_component_2.js

This prevents sub-components from needing their own client folders, since they are under a shared client folder.

Ok, I will pull changes by @jykae for Documentation module

This PR looks good. There are a couple of cleanup and consistency improvements, noted above.

Also, consider linting this PR with ESLint. We have an open PR for ESLint configuration #1466, which you can use as a basis.

@marla-singer please resolve conflicts. We merged a refactoring branch that touched some of the documentation module files.

Thanks. We are trying to organize our code for consistency lately, so things are moving around as we are working.

When I try to save the Codegen setting, the form does not appear to submit. I click the button, but nothing happens. No error is visible in the console.

There appears to be a regression in the development branch.

When I tested this feature on my old localhost version, it worked correct.
But now I did  meteor reset and had this problem too. However another fields on this page don't work too.

It appears related to switching the Settings collection file to using export. I have a fix in progress.

See PR #1475

The fix may not be as simple as I originally thought. I will have to continue working on this tomorrow.


This is what I have so far for Sudoku

@Bluenix2 - when you go to review again, please make sure to take a look at line 257. It's commented out, so wanted to point it out just in case you miss it. I made a small comment there and would like some help with it. Thanks!


Multiple colored bars in Bar Chart

Is it possible to set different fill colors in one Bar Chart for each bar? I am not talking about Bar Groups, just a simple Bar chart

Should be possible. Let me check and come back to you. Sorry for the late reply!

Could you give me more info about your data format?
What are your X and Y values like?
At the moment the code looks like fill={colorScale(label(stack))} so the color is decided by the label.
That means if you change your data format that each has it's own label it would work out of the box.
That might be troublesome to do though, so maybe, we could add a simpler way.

I usually have 4 columns. The data is like this
{"Developer":4,"Admin":2,"Manager":0,"Other":3}
At the moment I render it like this:
barGraphData(results) {
		return Object.keys(results).map(function(choice) {
			return {
				label: choice,
				value: results[choice]
			};
		});
	},

<BarChart data={this.barGraphData(this.props.results)}
		title={this.props.currentQuestion.q}
		height={window.innerHeight * 0.6}
		width={window.innerWidth * 0.9}
								/>

So you already did what I wrote above right :)
Good, so basically what you would need is the color scale to react to x values instead of the label.
I will see to make a small patch to support this. I guess it's useful for a lot of people.

If you could combine it with something like this
d3.scaleCategory10()
or
d3.scaleCategory20()
that would be awesome.

The color scale you can pass yourself. The default one is one of those two. I will only adjust which key is used for the color.

I added a new property to the BarChart called colorByLabel. If you set it to false it will use the X values in the color scale which will give you the required effect.
<BarChart colorByLabel={false} />

I checked again, the default colors cale in use is Category20, which you noted above.
If you want you can use your own color scale by passing it.
<BarChart colorByLabel={false} colorScale={your d3 color scale} />

Hope this helps!

Thank you for your quick help. I tried to use it, but I get errors. Here is my bar chart code
var React = require('react');
var Display = require('./parts/Display');
var BarChart = require('react-d3').BarChart;
var Board = React.createClass({
	barGraphData(results) {
		return Object.keys(results).map(function(choice) {
			return {
				label: choice,
				value: results[choice]
			};
		});
	},
	render() {
		return (

				<Display if={this.props.status === 'connected' && this.props.currentQuestion}>
					<BarChart data={this.barGraphData(this.props.results)}
								colorByLabel={false}
							  title={this.props.currentQuestion.q}
							  height={window.innerHeight * 0.6}
							  width={window.innerWidth * 0.9}
								/>
				</Display>
				<Display if={this.props.status === 'connected' && !this.props.currentQuestion}>

Awaiting a Question...

				</Display>

		);
	}
});
module.exports = Board;

I get these errors:
Uncaught TypeError: Cannot read property 'values' of undefined
Uncaught TypeError: Cannot read property '_currentElement' of null
I might have some errors in my package.json. These are my dependencies:
"dependencies": {
    "babel-core": "^5.8.12",
    "babel-loader": "^5.3.2",
    "bootstrap": "^3.3.5",
    "express": "^4.13.1",
    "react": "^0.14.6",
    "react-d3": "^0.4.0",
    "react-d3-components": "^0.6.2",
    "react-dom": "^0.14.6",
    "react-router": "^0.13.3",
    "socket.io": "^1.3.6",
    "socket.io-client": "^1.3.6",
    "underscore": "^1.8.3",
    "webpack": "^1.10.5"
  }

Could you please help? A  full code example would be very nice
Your example page seems to be down, too.
http://codesuki.github.io/react-d3-components/example.html
Thanks again for the help.

Most likely a problem with your data format. I'll whip up a sample.

data = {
	label: "salaries",
	values: [{x: "Developer", y: 4},{x: "Admin", y:2},{x:"Manager", y:0},{x: "Other", y:3}]
};

ReactDOM.render(
<BarChart
	data={data}
	width={800}
	height={400}
	margin={{top: 10, bottom: 50, left: 50, right: 10}}
	colorByLabel={false}
/>,
document.getElementById('barchart'));

This uses the default fields, label, values, x,y.
values should be an array of objects.
You can provide custom getters in case you rename the fields like work instead of x or hours instead of y.
Then you would make functions like this
var myXAccessor = function(element) { return element.work };
var myYAccessor = function(element) { return element.hours };

and then pass them to the chart via
<BarChart
x={myXAccessor}
y={myYAccessor}
/>

Hope that helps. More about the accessors is in the readme.
Feel free to ask here though.

Your example page looks like this in my browser
http://codesuki.github.io/react-d3-components/example.html

I had to use
var BarChart = require('d3-components).BarChart;

Now it works very nicely.
Thanks

Oh yeah I didn't realize the import is wrong :)
Somehow your browser can't download the react libraries from Facebook when loading the example page. Did you block the fb.me URL or something? No idea sorry.
But glad it works now!


[TACHYON-905] cleanup imports for PinListSync

Can one of the admins verify this patch?

Jenkins, ok to test.

Jenkins, add to whitelist.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/4718/
Test PASSed.

Thanks!


Lightweight/EDS attached SAN validation

Title: Lightweight/EDS attached SAN validation
Description:
Currently, we create a cluster for a Kubernetes Service. Each Service consists of Pods, which are given distinct SPIFFE identities. Each pod represents an endpoint within the cluster.
While identities, in our model, are attached to endpoints, in Envoy they are bound to the transport_socket on the cluster (ie, at the Service level). Because of this, we aggregate all of the service accounts and provide a list to the cluster.
This introduces a mismatch. We want to just send a small EDS update just for one ClusterLoadAssignment when a pod scales up/down. However, we can't do that; instead we need to also trigger a CDS push, which is much more expensive.
It would be great to be able to either dynamically update the SAN matches or put them in the endpoint level (metadata?).
I considered auto_san_validation and/or override_auto_sni_header but they don't seem to fit quite as needed since they are HTTP only and we don't want users to override by header, we would want to override internally

What's the desired behavior when SAN negotiation fails? Should a cluster try another endpoint?

I think just failing is fine as it would if it failed at the cluster level.

We should be careful not to allow mutation of endpoint policy since changing an endpoint does not trigger any drain I believe. So that means both the policy and the attribute on the endpoint is expected to be permanent.

I think we can also use a custom cert validator with its own source of data as well, like https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/transport_sockets/tls/v3/tls_spiffe_validator_config.proto.


documentation does not match code : ng serve

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

OSX El Capitan
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.17
node: 4.5.0
os: darwin x64
Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

$ ng --help
The log given by the failure.

Normally this include a stack trace and some more information.

The help command gives this inconsistent information.
ng serve <options...>
--host (String) (Default: localhost) Listens on all interfaces by default
Either :
a) the default is "<IP_ADDRESS>", in which case "Listens on all interfaces by default" is correct; or
b) the default is "localhost", in which case "Listens on all interfaces by default" is incorrect.
Trial and error leads me to believe that the default is "localhost".
This caused me to spend debugging time, trying to understand why my "ng serve" docker container was not working.
Mention any other details that might be useful.

Thanks! We'll be in touch soon.

Would you be willing to submit a PR changing this?
This is the line from which ng help derives the description: https://github.com/angular/angular-cli/blob/master/packages/angular-cli/commands/serve.ts#L44


Examples: multiple ports

Fixes #2815

I came at this by considering how a user might convert our classic greeting app to use multiple routing names.
First choice: add @RoutingName to the PUT method for changing the greeting
Ideally, there would be the obvious change to config and then one line of change in the code: add @RoutingName("private") to the PUT method on the existing resource. The public port would be available to outside requests but not the private one so only internal users could change the greeting.
This will not even compile because the @RoutingName annotation is defined to apply only to types. Ideally, it would work on methods as well.
Second choice: add @RoutingName to the resource classes
The next best would be to create two resources, one for the public endpoints with @Path("/greet") and the second annotated with @RoutingName("private") @Path("/greet/greeting") for the private ones. That builds but does not work as desired; the app endpoints (/greet and /greet/greeting) seem available on both the default routing and the private one so it looks as if the @RoutingName on resources is ignored.
Last choice: split the existing resource and create two Application classes (as you've had to do)
So, are we really telling developers that to use this feature they need take the quick-start example (or their own app), create two Application classes so they can specify the @RoutingName("private") on one and then write their respective getClasses methods, and also divide the resource class into two different resource classes so each application can report its own resource?
Ugh.
Even with the first and second choices not possible, it would be good in our example to at least preserve the external API of the greeting app. I tried binding the "public" resource to the path /greet and the "private" one to /greet/greeting and that seems to work. Trying to PUT to the public port returns a 405 Method Not Allowed which makes sense.

@tjquinno I experimented with those first two options as well with the same results.

@barchetta It might be worth seeing if the @RoutingName processing could be changed so one of the first two approaches would work.


Develop

I've made the translations. I left proper nouns like "TacoTruck.Party (website name)" and "DevProgress" alone.  I also left the bangs (!) at the front of each line alone. I'm not familiar with i18n and Javascript, so I was unable to see the changes in my local site.
There could be some discussion about the translation for "taco truck". I say "camioneta de taco". My mom and dad say "taquero". I would say that's the person working inside the truck, but it could also be the taco truck itself. If you want Spanglish, "troca de taco" make sense, but someone is bound to complain.
If you want more changes, let me know.

Thanks for the translations! The exclamation points at the start of each line should be removed; they were just there to indicate something that should be translated but hadn't been yet.
Other than that, :+1:

There was some confusion on my fork-and-branch when I went to make the updates. (I thought I updated from the develop branch already? I thought I saved this commit already?). I did remove the bangs (!) at the beginning of each string in the end. If there are still issues or the pull request updates have disappeared, please let me know.

Looks good, thanks! :fireworks: By the way, if you change your preferred browser language to one of the Spanish options, the translations should appear.


[Feature] Fix linter type comparison

Is your feature request related to a problem? Please describe.
Currently linting fails with
bg_atlasgen/atlas_scripts/admba_3d_dev_mouse.py:221:8: E721 Do not compare types, use `isinstance()`
bg_atlasgen/metadata_utils.py:51:12: E721 Do not compare types, use `isinstance()`

Describe the solution you'd like
Linting passes.

This was fixed (by the bot!) in https://github.com/brainglobe/bg-atlasgen/pull/66


Upgrading leaves old files

Observed behavior:
Upgrading from v<IP_ADDRESS> to v<IP_ADDRESS> leaves old files behind.
Expected behavior:
Files that are no longer needed should be removed.
Steps to reproduce:

Run the v<IP_ADDRESS> installer and choose the location of the installed v<IP_ADDRESS> application.
Copy the application folder to another location.
Unistall v<IP_ADDRESS>.
Run the v<IP_ADDRESS> installer.
Compare the files from the backup location in step 2 to the new installation in step 4.

These are the files from the previous version that were not cleaned up:

\help\clipboard.htm
\help\customeditors.htm
\help\dragdrop.htm
\help\find.htm
\help\intellisense.htm
\help\keyboard.htm
\help\menus.htm
\help\options.htm
\help\overview.htm
\help\schemas.htm
\help\ui.htm
\help\updates.htm
\help\validation.htm
\runtimes\win-x64\native\WebView2Loader.x64.dll

System Information:
Windows 10 Enterprise v21H2
v<IP_ADDRESS> starting point was a portable installation

I'm not sure this is a scenario that my setup technology supports, see: https://wixtoolset.org/docs/wix3/
You did not uninstall v<IP_ADDRESS> right? So windows thinks you still have v<IP_ADDRESS> installed, and perhaps these help files belong to that install so that's why they were not removed?
But in general I don't want to support this kind of complexity during setup, the .msi standalone installer is provided as a convenience only for folks that cannot use the ClickOnce or winget installers and .msi is not a technology I want to become an expert in since everyone is moving to .msix, ClickOnce and winget and these newer install technologies solve this problem by always creating a new folder for the new version.


convert-aws-account-to-string

    reason: 'Upgrade "vacl7" failed: failed to create resource: AWSMachineTemplate.infrastructure.cluster.x-k8s.io
      "vacl7-bastion" is invalid: spec.template.spec.imageLookupOrg: Invalid value:
      "integer": spec.template.spec.imageLookupOrg in body must be of type string:
      "integer"'

just merging


VSTest@3 publish test results

In VSTest@3 when running the tests through, say, MSTest, I don't see any documentation on publishing the test results in the case of a success. It publishes when something fails, but I don't see how to publish the results unconditionally.

@AbhishekMarda Does this issue refer to any specific article?

Not particularly. The closest article would be this: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/vstest-v3?view=azure-pipelines

@AbhishekMarda It should publish results on every run. You can customize this by using the settings under "Reporting options". If this isn't working properly, please file an issue on the task here: https://github.com/microsoft/azure-pipelines-tasks/issues


Move Skottie and SceneGraph out of the core SkiaSharp.dll

Description of Change
No functional changes, just moving the types.
The reason for this is so that if anything happens to Scene Graph or Skottie, we don't have any issues. I am not 100% sure of the reason behind these modules and how they relate to Chromium.
Also, I do want to investigate in the future a way to compile skia and not have a single blob of bits and rather split this up into separate native binaries - if possible.
Bugs Fixed
None.
API Changes
None.

Behavioral Changes
None.

Required skia PR
None.

PR Checklist

[x] Has tests (if omitted, state reason in description)
[x] Rebased on top of main at time of PR
[x] Merged related skia PRs
[x] Changes adhere to coding standard
[x] Updated documentation

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp