PyFerret confirmation for Help->Exit in graphics window

Reported by karl smith on 10 Dec 2012 19:52 UTC
Add a confirmation dialog to Help->Exit command, explaining that this should only be used when pyferret has crashed or somehow shutdown without closing the window.  (Exiting a window that pyferret thinks is still viable will cause issues - crashes most likely - in pyferret.)
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2008

Modified by andrew.wittenberg on 12 Dec 2012 00:21 UTC

Modified by karl.smith on 17 May 2016 20:53 UTC

Modified by karl.smith on 17 May 2016 20:54 UTC

Comment by karl.smith on 28 Jul 2016 19:01 UTC
On the Mac the Help menu is overridden by the OS, so the Help->Exit button is not present.  So the confirmation dialog box need to come up whenever the graphics window display is exiting, not just as part of the callback chain for the Help->Exit button.

Comment by karl.smith on 28 Jul 2016 23:06 UTC
Added a dialog that is displayed on unexpected close events (ones not generated from the Ferret engine).  This dialog asks whether to terminate or hide the display window and provides an explanation.  The default button is to hide the window.  There is also the cancel option that will close the dialog without anything happening to the display window.

Comment by andrew.wittenberg on 1 Aug 2016 16:19 UTC
"Hide" doesn't seem to work -- the window disappears, but does not reopen when written to.  E.g.
 	NOAA/PMEL TMAP
 	PyFERRET v7.01 (beta/optim)
 	Linux 2.6.32-642.1.1.el6.x86_64 - 07/29/16
 	 1-Aug-16 12:09

yes? use coads_climatology
yes? shade/l=1 sst

On plot window: Help -> Exit -> Hide
yes? shade/l=1 sst

Here PyFerret hangs indefinitely.  Ctrl-C doesn't even work -- have to Ctrl-z and kill the PyFerret process.  (This is the same thing that happens if we press "Terminate" rather than "Hide".)
By the way, there's a typo in the dialog: "it will be show[n] again".

Comment by karl.smith on 8 Aug 2016 21:24 UTC
Updated so the timer checking for new commands is not closed until the viewer actually exits.  Instead of hiding the window, it is only minimized so the user can see that the window is still around if it has not been terminated, and can restore to the normal window (as opposed to minimized or maximized) using the mouse.  Drawing to the window (or rather the "show" that PyFerret issues after drawing) will restore to the normal window when the window is either hidden (which should no longer happen) or minimized.
Old behaviour (prior to all this) was that a hidden window would be shown as a normal window after drawing, but a minimized window would remain minimized.  (If you minimized it, it would stay out of your way; furthermore, actual drawing to the display was not done for a minimized window)  But the user has no way of seeing that a hidden window is actually around, so this was not very user-friendly.
Added ticket #2464 to deal with restoring a minimized window to normal window on update, if that is something we want to do.


fix(datatable-body): avoid multiple calculations and update properly on changes

This starts to improve the issues caused by the many setters and getters, while it does not fully solve some of the OnPush issues I encountered, it at least helps with some them.

@chintankavathia It seems due to the bottomSummaryRowsStyles = computed(() the cache is prematurely accessed.

@chintankavathia It seems due to the bottomSummaryRowsStyles = computed(() the cache is prematurely accessed.

Just made it wait for it

@chintankavathia Before I go ahead here, can you check if it conflicts with something?


[Feature Request] Allow "Relic" Trait to be added to more items

As it stands, the Relic trait can't be given to armor or shields, as far as I've read there is no actual limit that exists that would prevent relics to be armor or shields. I understand relics aren't a high priority at the moment, but it would be nice to have this functionality.

I took a look, and it seems that nothing says that relics gain the relic trait, and instead is something we inferred from paizo creating relic seeds with the relic trait. I think that's a good enough reason to include it, but someone else might disagree.
https://2e.aonprd.com/Traits.aspx?ID=494


Disable log event parsing vmlifecycle tests for JENKINs

The vmlifecycle test that parses the virt-handler's pod logs fails fairly consistently in JENKINs ci, but passes consistently for all of us locally.
We've spent quite a bit of time investigating this and still don't have a grasp on why this is occurring. The virt-handler pod's logs don't get updated when streaming them via k8s... but this only happens for our JENKINs test runs.
I've created issue #422 to track the log flushing problem.
This is currently impacting our ability to rely on the CI environment's results. In this PR I suggest we disable the single test case leading to all the false negatives when the functional tests are being run by jenkins.

The code itself looks good, so I'll give it a thumbs up--but would like others to weigh in since we're disabling a test here.

retest this please

looks good to me too. Should significantly reduce the count of failed test runs.

retest this please

ok, two times #424 in a row.


[SearchAnchor] A RenderFlex overflowed by 25 pixels on the right.

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
In SearchAnchor viewTrailing:  if you add more then 1 item in the list it will overflow
viewTrailing: [
            IconButton(
              onPressed: onClickSearch,
              icon: const Icon(
                Icons.search_outlined,
              ),
            ),
            IconButton(
              onPressed: () {
                searchController?.clear();
              },
              icon: const Icon(Icons.clear),
            ),
          ],

Expected results
It should not overflow
Actual results
A RenderFlex overflowed by 25 pixels on the right. is showing when using searchController.openView() for the 2nd time , on the first time it show not show this error
Code sample
Code sample
part of common;

class MainAppScaffoldSliver extends StatelessWidget {
  final List<Widget> slivers;
  final Widget? bottomNavigationBar;
  final ScrollController? controller;
  final SearchController? searchController;
  final VoidCallback? onClickLeading;
  final VoidCallback? onClickSearch;
  final VoidCallback? onClickCart;
  final Widget searachSuggestion;

  const MainAppScaffoldSliver({
    Key? key,
    required this.slivers,
    this.onClickLeading,
    this.onClickSearch,
    this.onClickCart,
    this.controller,
    this.bottomNavigationBar,
    this.searchController,
    this.searachSuggestion = const SizedBox.shrink(),
  }) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
      title: Theme.of(context).brightness == Brightness.dark
        ? Assets.images.logo.logo.svg(
          colorFilter: const ColorFilter.mode(Colors.white, BlendMode.srcIn),
        )
        : Assets.images.logo.logo.svg(),
      centerTitle: true,
      actions: [
        SearchAnchor(
          searchController: searchController,
          viewHintText: 'Search...',
          viewTrailing: [
            IconButton(
              onPressed: onClickSearch,
              icon: const Icon(
                Icons.search_outlined,
              ),
            ),
            IconButton(
              onPressed: () {
                searchController?.clear();
              },
              icon: const Icon(Icons.clear),
            ),
          ],
          builder: (context,searchController) {
            return IconButton(
              onPressed: () => searchController.openView(),
              icon: const Icon(Icons.search_outlined),
            );
          },
          suggestionsBuilder: (context,searchController) {
            return [
              searachSuggestion
            ];
          },
        ),

        IconButton(
          onPressed: onClickCart,
          icon: const Icon(Icons.shopping_bag_outlined),
        ),

      ],
    ),
      body: SafeArea(
        child: CustomScrollView(
          physics: const ClampingScrollPhysics(),
          controller: controller,
          slivers: slivers,
        ),
      ),
      drawer: const MainAppDrawer(),
      bottomNavigationBar: bottomNavigationBar,
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
════════ Exception caught by rendering library ═════════════════════════════════
The following assertion was thrown during layout:
A RenderFlex overflowed by 25 pixels on the right.

The relevant error-causing widget was
Scaffold
dashboard_screen.dart:13
You can inspect this widget using the 'Inspect Widget' button in the VS Code notification.
The overflowing RenderFlex has an orientation of Axis.horizontal.
The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and black striped pattern. This is usually caused by the contents being too big for the RenderFlex.

Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the RenderFlex to fit within the available space instead of being sized to their natural size.
This is considered an error condition because it indicates that there is content that cannot be seen. If the content is legitimately bigger than the available space, consider clipping it with a ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex, like a ListView.

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel stable, 3.10.6, on macOS 13.4.1 22F770820d darwin-arm64, locale en-TH)
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/3.0.3/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Volumes/External/Users/richard/fvm/versions/3.10.6. Consider adding /Volumes/External/Users/richard/fvm/versions/3.10.6/bin to the front of your path.
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.2)
[✓] VS Code (version 1.80.2)
[✓] Connected device (3 available)
    ! Error: Richard’s iPhone is busy: Fetching debug symbols for Richard’s iPhone. Xcode will continue when Richard’s iPhone is finished. (code -10)
[✓] Network resources

! Doctor found issues in 1 category.

Hi @rddewan. Thanks for filing this issue. I am unable to reproduce this issue:
Code Sample Used

import 'package:flutter/material.dart';

void main() => runApp(const SearchAnchorTestApp());

class SearchAnchorTestApp extends StatelessWidget {
  const SearchAnchorTestApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: MainAppScaffoldSliver(),
    );
  }
}

class MainAppScaffoldSliver extends StatefulWidget {
  const MainAppScaffoldSliver({
    Key? key,
  }) : super(key: key);

  @override
  State<MainAppScaffoldSliver> createState() => _MainAppScaffoldSliverState();
}

class _MainAppScaffoldSliverState extends State<MainAppScaffoldSliver> {
  SearchController searchController = SearchController();
  ScrollController scrollController = ScrollController();
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Theme.of(context).brightness == Brightness.dark
            ? const Icon(
                Icons.umbrella,
                color: Colors.white,
              )
            : const Icon(Icons.umbrella),
        centerTitle: true,
        actions: [
          SearchAnchor(
            searchController: searchController,
            viewHintText: 'Search...',
            viewTrailing: [
              IconButton(
                onPressed: () {},
                icon: const Icon(
                  Icons.search_outlined,
                ),
              ),
              IconButton(
                onPressed: () {
                  searchController.clear();
                },
                icon: const Icon(Icons.clear),
              ),
            ],
            builder: (context, searchController) {
              return IconButton(
                onPressed: () => searchController.openView(),
                icon: const Icon(Icons.search_outlined),
              );
            },
            suggestionsBuilder: (context, searchController) {
              return [];
            },
          ),
          IconButton(
            onPressed: () {},
            icon: const Icon(Icons.shopping_bag_outlined),
          ),
        ],
      ),
      body: SafeArea(
        child: CustomScrollView(
          physics: const ClampingScrollPhysics(),
          controller: scrollController,
          slivers: [],
        ),
      ),
    );
  }
}

Also, from the logs:

Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the RenderFlex to fit within the available space instead of being sized to their natural size.
This is considered an error condition because it indicates that there is content that cannot be seen. If the content is legitimately bigger than the available space, consider clipping it with a ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex, like a ListView.

Kindly try applying this to fit into your use case. If neither works, kindly provide a minimal complete reproducible code sample that doesn’t include 3rd party plugins or complex production code that provides more information on this issue.
Thank you!
flutter doctor -v

[✓] Flutter (Channel stable, 3.10.6, on macOS 13.0 22A380 darwin-arm64, locale
    en-NG)
    • Flutter version 3.10.6 on channel stable at
      /Users/damilolaalimi/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (4 weeks ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b802.4-9586694)
    • 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.2)
    • Android Studio at /Applications/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.6b802.4-9586694)

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        •
      android-arm64  • Android 14 (API 34) (emulator)
    • iPhone 14 (mobile)          • 1A122DE2-0CAB-4C3E-A395-691BF27D626F • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)             • macos                                •
      darwin-arm64   • macOS 13.0 22A380 darwin-arm64
    • Chrome (web)                • chrome                               •
      web-javascript • Google Chrome 115.0.5790.170

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

• No issues found!

[✓] Flutter (Channel master, 3.13.0-19.0.pre.78, on macOS 13.0 22A380 darwin-arm64, locale en-NG)
    • Flutter version 3.13.0-19.0.pre.78 on channel master at /Users/damilolaalimi/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 436df69a46 (4 hours ago), 2023-08-08 01:58:16 -0400
    • Engine revision 146c4c9487
    • Dart version 3.2.0 (build 3.2.0-42.0.dev)
    • DevTools version 2.26.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • 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.2)
    • Android Studio at /Applications/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.6b802.4-9586694)

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 14 (API 34) (emulator)
    • iPhone 14 (mobile)          • 1A122DE2-0CAB-4C3E-A395-691BF27D626F • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 13.0 22A380 darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 115.0.5790.170

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

• No issues found!


Cleaned up adapter

Updated code to use async/await
Fixed status codes returned by processActivity().
Added ability to pass ConversationParamters to createConversation().

How about we make this separate PRs?

consistent application of async/await

alignment with C# adapter methods

http returns 200

Pull Request Test Coverage Report for Build 1901

87 of 118 (73.73%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 73.135%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder/src/botFrameworkAdapter.ts
87
118
73.73%

Totals

Change from base Build 1891:
-0.1%

Covered Lines:
2292

Relevant Lines:
3032

💛  - Coveralls


[very wip, doesn't work] add pinecone vector store

this is a very WIP attempt at adding a pinecone vector store.
it doesn't work at the moment, still need to do the following:

figure out how to cast pinecone index to the appropriate type "VectorOperationsApi"?
figure out how to write get_default_tokenizer
to implement nodeToMetadataDict and metadataDictToNode, we need to implement proper serdes for node <-> dict. ideally keep as same exact format as what's passed in the python version
figure out how to implement delete
test the entire thing

@jerryjliu @yisding hey guys, is this still happening? I was looking into building a vector store integration with lancedb and I came across this PR. It seems like this'll make changes to other modules outside of vectorStore. So should I take a stab at the implementation or wait for this one to get in? (It seems like latter to me)

@AyushExel Yes, if you're interested in making a PR for lancedb it'd be appreciated! This PR is from rather early in the dev cycle, so a lot has changed since then. I'm going to close this for now as it's a bit misleading as to what would be needed to implement a vector DB integration at this point.

Hi @AyushExel
Here’s a test script we are using for Pinecone
import fs from "fs/promises";
import {
  Document,
  VectorStoreIndex,
  storageContextFromDefaults,
} from "llamaindex";
import { PineconeVectorStore } from "llamaindex-pinecone";

async function main() {
  // Load essay from abramov.txt in Node
  const essay = await fs.readFile(
    "node_modules/llamaindex/examples/abramov.txt",
    "utf-8"
  );

  // Create Document object with essay
  const document = new Document({ text: essay });

  const vectorStore = new PineconeVectorStore({ indexName: "test" });
  const storageContext = await storageContextFromDefaults({ vectorStore });

  // Split text and create embeddings. Store them in a VectorStoreIndex
  const index = await VectorStoreIndex.fromDocuments([document], {
    storageContext,
  });

  // Query the index
  const queryEngine = index.asQueryEngine();
  const response = await queryEngine.query(
    "What did the author do in college?"
  );

  // Output response
  console.log(response.toString());
}

main().catch(console.error);

@yisding okay thanks.
I have one question about the vectorStore interface though. The operations to read, write & query would most likely be async right? Is there any specific reason to not make them async? I was able to get it working on making the return type a Promise, but most of my work is still pretty hacky. I'll clean it up and make a draft PR maybe?

 That was an oversight on our part. Thankfully @tyre also noticed and fixed it in https://github.com/run-llama/LlamaIndexTS/pull/54

@AyushExel I've been working on a PineconeVectorStore this week that might be what you're looking for. Check it out and let me know if you run into any issues/questions/feature requests:
https://github.com/tyre/llamaindex-pinecone

@tyre is your package meant to be working? I just tried now and I'm getting type errors
Type 'PineconeVectorStore' is not assignable to type 'VectorStore'.
  The types returned by 'query(...)' are incompatible between these types.

package.json
"@pinecone-database/pinecone": "^0.1.6",
"llamaindex": "^0.0.17",
"llamaindex-pinecone": "^0.1.0"

First of all, thanks for the work! 🎉
For whoever will be reading this thread, you might want to have a look at this repository instead: https://github.com/yisding/llamaindex-pinecone.
It's a fork from https://github.com/tyre/llamaindex-pinecone).


Ongoing minor issue list

Minor issues which are not relevant enough to be in their own issue should be reported here by commenting on this issue.
As minor things are resolved, comments will be hidden.
Fixes will be implemented periodically, typically before a new release is created.

DualConstructableType in the test source set of hartshorn-di is missing the license header

SpongeGradle should be updated to 2.0.0 to keep API8 support active. As of 2.0.0 the metadata model for Sponge plugins changed, making it so the current setup with SG 1.1.1 generates a incorrect plugin metadata file, causing Hartshorn to not load on Sponge platforms

Parameter names are not kept when running in a test environment. This causes @Parameter injection (from hartshorn-commands) to fail when injecting argument values, resulting in null values being passed instead.
Sidenote, should this have early validation? A warning would be nice..

MethodContext#invoke yields the entire exception when one is encountered. While this is expected, it would be better to unwrap the InvocationTargetException and return the cause instead.

Exceptions caught by the default CommandExecutor are captured but not handled by the MethodCommandExecutorContext.
See https://github.com/GuusLieben/Hartshorn/blob/abc70109d6748b254c4a62703106a46c46c837a1/hartshorn-commands/src/main/java/org/dockbox/hartshorn/commands/context/MethodCommandExecutorContext.java#L129

ServiceMethodModifier uses direct access to JavassistProxyUtil while this can be replaced with context.environment().application().
https://github.com/GuusLieben/Hartshorn/blob/b4ddf36046837859561e8ee79bdb05e057916411/hartshorn-core/src/main/java/org/dockbox/hartshorn/core/services/ServiceMethodModifier.java#L26

CommandServiceScanner contains duplicate method validation at:
https://github.com/GuusLieben/Hartshorn/blob/b520b76bed0e063079ee3b2f351edeebc8bf6264/hartshorn-commands/src/main/java/org/dockbox/hartshorn/commands/service/CommandServiceScanner.java#L42

Archiving in favor of dedicated issues.


python37Packages.mac_alias: 2.1.1 -> 2.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.mac_alias is: "Generate or read binary Alias and Bookmark records from Python code"
meta.homepage for python37Packages.mac_alias is: "https://github.com/al45tair/mac_alias"
meta.changelog for python37Packages.mac_alias is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.2.0 with grep in /nix/store/3f4jxhzvl7m0llk39k27l4r3ngp5xda2-python3.7-mac_alias-2.2.0

directory tree listing: https://gist.github.com/026b900b7e7fda6f610a9e2d8f824f76

du listing: https://gist.github.com/4a4af6203c73871aa2e5a8b804392f5b

Rebuild report (if merged into master) (click to expand)

12 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python37Packages.mac_alias
python38Packages.mac_alias
python39Packages.mac_alias

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3f4jxhzvl7m0llk39k27l4r3ngp5xda2-python3.7-mac_alias-2.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python37Packages.mac_alias https://github.com/r-ryantm/nixpkgs/archive/6b0b154c6f9276b56e8e9a9939c7ebf49a7be7d0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3f4jxhzvl7m0llk39k27l4r3ngp5xda2-python3.7-mac_alias-2.2.0
ls -la /nix/store/3f4jxhzvl7m0llk39k27l4r3ngp5xda2-python3.7-mac_alias-2.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

3 packages built:

python37Packages.mac_alias
python38Packages.mac_alias
python39Packages.mac_alias

Maintainer pings
cc @siriobalmelli for testing.

LGTM, ok on Darwin as well:
https://github.com/NixOS/nixpkgs/pull/106518

3 packages built:
python37Packages.mac_alias python38Packages.mac_alias python39Packages.mac_alias


No outgoing messages from testserver?

Today i'm testing with the testserver but i'm experiencing lot of delays in messages that I requested to be send. My last message isn't even send. It keeps the status 'Waiting for treatment'. Is this an issue with the testserver?

Update: after 1h my last message was also send. Is there an explanation for this delay? This makes it hard to do testing.

Hello
Sorry for this issue
We made some performance test on the server and we changed the timing of sending messages from Every minutes to Every hour.
It will be restored tomorrow morning

It is still slow today....

It's solved now


Document more methods from HFFileSystem

See https://github.com/huggingface/huggingface_hub/issues/2100 cc @severo

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Yep, just noticed that :confused: I hoped it would work. Then we'll have explicitly document them. The thing is that those methods are inherited from fsspec, now HF specific (still agree with you they should be better documented)

yes, but I think it's important to document which part of the fsspec methods we implement.

Although some specific implementations may not offer all features (e.g., http is read-only), generally all normal operations, such as ls, rm, should be expected to work (see the full list: fsspec.spec.AbstractFileSystem).

from https://filesystem-spec.readthedocs.io/en/latest/usage.html?highlight=s3#use-a-file-system

Closing this PR has it doesn't lead anywhere. We should open a proper one to document those methods (so I'm definitely keeping https://github.com/huggingface/huggingface_hub/issues/2100 open).


fix: Clicking multiple times on same freight not working

Fix: Clicking multiple times on same freight not working
Having components defined inside another components is not the best practice especially without useMemo or something similar since it is quite easy to trigger a lot of re-renders.
In this instance it was triggering loop somehow (not sure 100% what it was causing, my tip is that tooltip) which ends up in:

Since there is no really good reason to have it (FreightContentItem) defined inside another component I extracted it as separate component which fixes the issue.
You can replicate the issue by clicking on highlighted area multiple times:

Note that after first click it will open details of Freight, after second click it will close it and on third click it will do nothing (it should open details again but it does not)... This happens only if you keep mouse in highlighted area. If you go up and down (git / docker) then it kind of works....
With this commit you can click as many times you want on the same spot and it will keep opening and closing those details without hitting:
Warning: Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn't have a dependency array, or one of the dependencies changes on every render.

@Marvin9 done.
One suggestion would be to create one command which, would verify everything including linter so we can run it locally without knowing which parts needs to be checked since Github checks do not fail automatically.

@Marvin9 done.
One suggestion would be to create one command which, would verify everything including linter so we can run it locally without knowing which parts needs to be checked since Github checks do not fail automatically.

Sure thing. There is already a make command make format but agree that should be in doc if not already


feat: Add SQS option to SNS event

Issue #, if available:
https://github.com/awslabs/serverless-application-model/issues/854
This pull request will resolve #854 partially.
I implemented simple boolean SqsSubscription option to SNSEvent at first.
Description of changes:
Added SQS option(SqsSubscription) to SNS event.
Description of how you validated changes:

make pr
verified transformed template in the steps written in DEVELOPMENT_GUIDE
confirmed that SAM template below could be deployed successfully.

AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31

Resources:
  TweetTopic:
    Type: AWS::SNS::Topic
  WorkerFunction:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: worker_lambda/
      Handler: app.lambda_handler
      Timeout: 10
      Runtime: python3.7
      Events:
        MessageTopic:
          Type: SNS
          Properties:
            Topic: !Ref TweetTopic
            SqsSubscription: true

Checklist:

[x] Write/update tests
[x] make pr passes
[x] Update documentation
[x] Verify transformed template deploys and application functions as expected
[-] Add/update example to examples/2016-10-31

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1065 into develop will increase coverage by 0.03%.
The diff coverage is 97.91%.

@@             Coverage Diff             @@
##           develop    #1065      +/-   ##
===========================================
+ Coverage    94.81%   94.84%   +0.03%
===========================================
  Files           69       70       +1
  Lines         3276     3318      +42
  Branches       639      642       +3
===========================================
+ Hits          3106     3147      +41
  Misses          89       89
- Partials        81       82       +1

Impacted Files
Coverage Δ

samtranslator/model/eventsources/push.py
89.5% <100%> (+0.89%)
:arrow_up:

samtranslator/model/sqs.py
93.33% <93.33%> (ø)

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 5090228...8ec4b96. Read the comment docs.

@53ningen Thank you for contributing this very important feature! Can you please add an example of how to use this in the examples folder? This is a great example of how to do it.

I added an example of how to use new SqsSubscription option.
Ready for review again.


Change error for generating signed URL

Change message when calling generate_signed_url on Blob if credentials with insufficient parameters are used.
See: #1964
The tests should actually be failing here. I'm still looking into why they aren't.

Looks like you are being hosed by a new pylint opinion.

Yeah, separate PR #1967

@daspecster Does tox -e cover pass for you?

Nope! I don't get it...it doesn't appear to use my _GoogleCredentials mock?

I'm kind of thinking that the tests weren't acting as expected so I've been trying to dig into that more.

Bingo! Ok @tseaver LMKWYT.

LGTM pending Travis.


Flaky test: MaxRequestBufferSizeTests.LargeUpload

This has failed 50% of the time for me on recent local builds, always with the same actual result.
[xUnit.net 00:00:44.2552397]     LargeUpload(maxRequestBufferSize: 5242880, connectionAdapter: True, expectPause: True) [FAIL]
[xUnit.net 00:00:44.2588137]       Assert.InRange() Failure
[xUnit.net 00:00:44.2591272]       Range:  (5238785 - 20971519)
[xUnit.net 00:00:44.2592656]       Actual: 20971520
[xUnit.net 00:00:44.2619018]       Stack Trace:
[xUnit.net 00:00:44.2652259]         D:\github\AspNet\KestrelHttpServer\test\Kestrel.FunctionalTests\MaxRequestBufferSizeTests.cs(160,0): at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.MaxRequestBufferSizeTests.<LargeUpload>d__6.MoveNext()
[xUnit.net 00:00:44.2657057]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:44.2658986]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:44.2660844]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:44.2682372]       Output:
[xUnit.net 00:00:44.2684638]         | Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.0 POST http:///  20971520
Failed   LargeUpload(maxRequestBufferSize: 5242880, connectionAdapter: True, expectPause: True)
Error Message:
 Assert.InRange() Failure
Range:  (5238785 - 20971519)
Actual: 20971520
Stack Trace:
   at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.MaxRequestBufferSizeTests.<LargeUpload>d__6.MoveNext() in D:\github\AspNet\KestrelHttpServer\test\Kestrel.FunctionalTests\MaxRequestBufferSizeTests.cs:line 160

You can see the history of this test failure here.

Another failure, but a different error this time:
System.IO.IOException : Unable to read data from the transport connection: Invalid argument.
---- System.Net.Sockets.SocketException : Invalid argument
   at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.MaxRequestBufferSizeTests.<>c__DisplayClass6_2.<<LargeUpload>b__0>d.MoveNext() in /_/test/Kestrel.FunctionalTests/MaxRequestBufferSizeTests.cs:line 120
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.MaxRequestBufferSizeTests.LargeUpload(Nullable`1 maxRequestBufferSize, Boolean connectionAdapter, Boolean expectPause) in /_/test/Kestrel.FunctionalTests/MaxRequestBufferSizeTests.cs:line 163
--- End of stack trace from previous location where exception was thrown ---
----- Inner Stack Trace -----

------- Stdout: -------
| [2018-04-10T13:17:35] Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.0 POST http:///  20971520
| [2018-04-10T13:17:39] Microsoft.AspNetCore.Server.Kestrel Error: Connection id "0HLCUSLM70C7C", Request id "0HLCUSLM70C7C:00000001": An unhandled exception was thrown by the application.
|    at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpRequestStream.ValidateState(CancellationToken cancellationToken) in /_/src/Kestrel.Core/Internal/Http/HttpRequestStream.cs:line 216
|    at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpRequestStream.ReadAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken) in /_/src/Kestrel.Core/Internal/Http/HttpRequestStream.cs:line 110
|    at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.MaxRequestBufferSizeTests.<>c__DisplayClass8_0.<<StartWebHost>b__3>d.MoveNext() in /_/test/Kestrel.FunctionalTests/MaxRequestBufferSizeTests.cs:line 298
| --- End of stack trace from previous location where exception was thrown ---
|    at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application) in /_/src/Kestrel.Core/Internal/Http/HttpProtocol.cs:line 536
| [2018-04-10T13:17:39] Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request finished in 3976.3743ms 0

No, I should have some time to look at tests tomorrow.

The history for this test is pretty messy. I count 8 failures for the various overloads.
http://aspnetci/viewLog.html?buildId=446050&buildTypeId=XPlat_Windows_Win10Universe&tab=testsInfo
3 are part of mass failures and can be dismissed as agent issues
http://aspnetci/viewLog.html?buildId=424325&tab=buildResultsDiv&buildTypeId=XPlat_Mac_MacUniverseCoreCLR#testNameId6816592842570504506
http://aspnetci/viewLog.html?buildId=424325&tab=buildResultsDiv&buildTypeId=XPlat_Mac_MacUniverseCoreCLR#testNameId-9108478846534902949
http://aspnetci/viewLog.html?buildId=443056&tab=buildResultsDiv&buildTypeId=Lite_KestrelStressTest#testNameId-9108478846534902949
There's 2 reports of the original issue I posted above
http://aspnetci/viewLog.html?buildId=443290&tab=buildResultsDiv&buildTypeId=XPlat_Windows_Win10Universe#testNameId6816592842570504506
http://aspnetci/viewLog.html?buildId=444798&tab=buildResultsDiv&buildTypeId=XPlat_Windows_Win10Universe#testNameId2969803565931579806
2 invalid arguments
http://aspnetci/viewLog.html?buildId=407883&tab=buildResultsDiv&buildTypeId=XPlat_Linux_UbuntuUniverseCoreCLR#testNameId2969803565931579806
http://aspnetci/viewLog.html?buildId=444611&tab=buildResultsDiv&buildTypeId=XPlat_Linux_UbuntuUniverseCoreCLR#testNameId2969803565931579806
And 1 bind failure
http://aspnetci/viewLog.html?buildId=422166&tab=buildResultsDiv&buildTypeId=XPlat_Linux_UbuntuUniverseCoreCLR#testNameId2969803565931579806

RE the InRange failure, it does not appear to be TFM specific, and it reproduces both on Sockets and Libuv, though more readily on Sockets. Only the connectionAdapter: True variation fails with the above error.
connectionAdapter: True has failed once with an OutOfMemoryException.

Re: System.IO.IOException : Unable to read data from the transport connection: Invalid argument.
Invalid argument is now likely to be reported as OperationAborted https://github.com/dotnet/corefx/pull/29091

Mitigation for the original issue has been checked into dev for 2.2. If we see it again in 2.1 we can consider backporting it. If we see any more reports of the other errors we can open a separate issue.

Nevermind, it's still failing.

This fails most frequently on our Win10 build, on which it has failed 4 times today.

@Tratcher did you look into this one yet?

I wasn't able to get a consistent repro so I moved on to tests with more failures. I'll revisit it when I get that far down the list.

Just failed on my dev machine, same error as the first post in this issue:
  [xUnit.net 00:00:17.1104598]     LargeUpload(maxRequestBufferSize: 5242880, connectionAdapter: True, expectPause: True) [FAIL]
  Failed   LargeUpload(maxRequestBufferSize: 5242880, connectionAdapter: True, expectPause: True)
RUNDOTNET : error Message:  [C:\Users\mharder\.dotnet\buildtools\korebuild\2.2.0-preview1-17051\KoreBuild.proj]
   Assert.InRange() Failure
  Range:  (5238785 - 20971519)
  Actual: 20971520
  Stack Trace:
     at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.MaxRequestBufferSizeTests.LargeUpload(Nullable`1 maxRequestBufferSize, Boolean connectionAdapter, Boolean expectPause) in D:\Git\KestrelHttpServer\test\Kestrel.FunctionalTests\MaxRequestBufferSizeTests.cs:line 149
  --- End of stack trace from previous location where exception was thrown ---

It's possible the client and/or server buffers on Win10 have been increased, so we may need to change the test parameters:
https://github.com/aspnet/KestrelHttpServer/blob/de98f8c962aec15dd94e98520f471a2880e3aeb9/test/Kestrel.FunctionalTests/MaxRequestBufferSizeTests.cs#L49-L52
https://github.com/aspnet/KestrelHttpServer/blob/de98f8c962aec15dd94e98520f471a2880e3aeb9/test/Kestrel.FunctionalTests/MaxRequestBufferSizeTests.cs#L222-L225
Specifically, we may need to increase the data sent from 20MB to something larger until the test is reliable on all platforms.

I can take this issue since I wrote these tests.

I've been running the LargeUpload tests in a loop on my dev machine:
for /l %n in () do dotnet test --no-build -f netcoreapp2.2 --filter "DisplayName~LargeUpload"

The following test (and only this specific test) fails about 25-30% of the time:
LargeUpload(maxRequestBufferSize: 5242880, connectionAdapter: True, expectPause: True)

It may be noteworthy that connectionAdapter: true, and the variant with connectionAdapter: false never fails.
I also tried running only the two tests with maxRequestBufferSize: 5242880 in a loop:
for /l %n in () do dotnet test --no-build -f netcoreapp2.2 --filter "DisplayName~LargeUpload & DisplayName~5242880

However, when running this subset I was unable to repro any failures.

I was also able to reproduce this in a Win10 Hyper-V VM on my dev machine, but it seems to fail less often (say 10% in VM and 30% on physical).

New occurance: https://ci3.dot.net/job/aspnet_KestrelHttpServer/job/dev/job/linux-Configuration_Release_prtest/307/
15:41:29   [xUnit.net 00:00:14.0401462]     LargeUpload(maxRequestBufferSize: 26, connectionAdapter: False, expectPause: True) [FAIL]
15:41:29   Failed   LargeUpload(maxRequestBufferSize: 26, connectionAdapter: False, expectPause: True)
15:41:29 RUNDOTNET : error Message:  [/home/dotnet-bot/.dotnet/buildtools/korebuild/2.2.0-preview1-17060/KoreBuild.proj]
15:41:29    Assert.Contains() Failure
15:41:29   Not found: bytesRead: 41943040
15:41:29   In value:
15:41:29   Stack Trace:
15:41:29      at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.MaxRequestBufferSizeTests.LargeUpload(Nullable`1 maxRequestBufferSize, Boolean connectionAdapter, Boolean expectPause)
15:41:29   --- End of stack trace from previous location where exception was thrown ---
15:42:50   Results File: /mnt/j/workspace/aspnet_KestrelHttpServer/dev/linux-Configuration_Release_prtest/artifacts/logs/UnitTests-netcoreapp2.2-307.trx
15:42:50


Option to delete your account

If the user has resources for which they are the sole owner do not allow them to delete the account.  Instead give a message that they first need to delete these resources or transfer them to another user.
If the user does not have any resources for which they are the sole owner warn them that deleting is irreversible and that they will lose access to any content that they have access to in the system.  Have a check box that they need to click to acknowledge this.  Then allow them to delete the account.

We decided to leave the resources in HydroShare, but notify the user so when the account is being deactivated.
@horsburgh, should we implement this checkbox that the user must check before deactivating the account?

Given that we are not actually deleting the account, but rather just disabling it, I'm assuming that the disabled user account will remain the owner of any resources they leave behind. I don't think we actually need the check box. The confirmation message we already have tells the user that if they disable their account without first deleting their resources, the resources will still be available. So, we may still want to examine this process in the future, but I think it's OK for now.

Can be tested at https://park.hydroshare.org

Implemented with revamp of profile page. Please confirm and close.

I just tested this on www. You can now deactivate your account, but per our current policy I don't think the account is actually deleted. Closing for now.


Fix step variables

Codecov Report

Merging #1351 (e51fcee) into master (b85165c) will decrease coverage by 9.80%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1351      +/-   ##
==========================================
- Coverage   58.70%   48.89%   -9.81%
==========================================
  Files          81       47      -34
  Lines        9873     6532    -3341
==========================================
- Hits         5796     3194    -2602
+ Misses       3803     3061     -742
- Partials      274      277       +3

Flag
Coverage Δ

unittests
48.89% <ø> (-9.81%)
:arrow_down:

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

Impacted Files
Coverage Δ

hrp/step_request.go
48.80% <0.00%> (-0.38%)
:arrow_down:

hrp/internal/builtin/utils.go
0.00% <0.00%> (ø)

httprunner/step_request.py

httprunner/step_sql_request.py

httprunner/step_thrift_request.py

httprunner/make_test.py

httprunner/make.py

httprunner/utils.py

httprunner/response.py

httprunner/__main__.py

... and 27 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 64f3b53...e51fcee. Read the comment docs.


Using input and single choice at the same time

I tried to add two inputs or using an input with single choice dialog at the same time but it shows just one of them, so i tried custom view but the problem is  I could not get custom view and do some stuffs like setting typeface and etc before making dialog, what's the best way for this?

That's all possible with the custom view, see the sample project.


Update Apacdex, Quantumdex, Valueimpression docs

As mentioned in PR https://github.com/prebid/prebid-server/pull/2097, we currently support bidding via PBS.
This PR updates documentation regarding the Apacdex adapter and its alias (Quantumdex, Valueimpression) to update this to the documentation page.

Hello @muuki88,
My PR was merged and released in PBS 0.188.0.
Please help me merge this document.
Thank you.

Sure @thuyhq . Can you post again the link to the PR. I can't find it 😄


memory leak for python2

demo code:

import os
import psutil
import ahocorasick
def build_automaton():
automation = ahocorasick.Automaton()
for i in range(2000000):
automation.exists(str(i))
def show_used_memory():
print('memory used: {} M'.format(psutil.Process(os.getpid()).memory_info().rss / (1024. ** 2)))
if name == 'main':
build_automaton()
show_used_memory()
build_automaton()
show_used_memory()

build_automaton()
show_used_memory()

for python2, result:
memory used: 162.6875 M
memory used: 255.78125 M
memory used:<PHONE_NUMBER> M
for python3, result:
memory used: 10.23046875 M
memory used: 10.26171875 M
memory used: 10.26171875 M
thanks!

Thank you for the report.

any plans to fix this?

i have the same problem.

@eddy-avanan Not at that moment, but I'll try to look at this issue. It seems to be a regression, as we already had similar problem and it was solved.

Any updates on memory leak issue for python 2?

@galanamanj could you try to run the tests listed in the release-checklist.txt file on your Python 2 installation? In particular the valgrind tests.
Actual help to track (and fix) these would be mucho welcomed!

I am closing for lack of activity. Please reopen if you feel strongly about it, though Python 2 really fell out of fashion these days ;)


Sed task

Maybe have a file that needs to be changed so that all instances of something have to be edited so that a chest will open that will allow you to continue?

Good idea for implementing sed/awk.
It was already decoded that sed and awk tasks will be added.
Originally posted by @wolandark in https://github.com/wolandark/bash-dungeon/issues/3#issuecomment-2212528504


Update build process and instructions

Now that #37 and #38 have merged, this PR adjust things to reflect the new reality.
This commit is giant, but a lot of what it is doing is moving things around. The biggest move is to get rid of the IPDK_Container directory, and instead move everything up to the build directory. From there, I modified the README.md to reference both README_DOCKER.md and README_NATIVE.md for the two types of installation methods.
In addition, I moved the vagrant directory to vagrant-native, and created a parallel vagrant-container directory. I updated the instructions on using both.
Finally, I brought both environments up and tested them through the demo pings between VMs, and they both work just fine.
Worth noting that the container build to demo process is about 50% faster in my tests running inside Vagrant VMs on my 2020 Macbook Pro. I'll explore this next.

@stolsma Would love to get your eyeballs on this one if possible. Thanks!

@mestery I like the removal of the IPDK_Container directory and the new structure + addition of the vagrant for container use!! Maybe it's good to have a build/doc directory for all the markdown and text files describing all kind of specifics?? That will declutter the build dir even more.
I can't check all the vagrant stuff as I don't have that installed (but you have 😄) I will try if the container stuff still works... Will come back to that later today!

@mestery It's amazing!!! I ran the docker workflow from start to end on a clean system and it just works!! 😄
Have added only one proposed change, a question about working on a bare metal machine/vm (without vagrant) and a comment for you to look at so for me there is no real blocker. LGTM if you are ready for it...


Did anyone have this stop working today?

Hi guys - I've been using this great connector for a while, and noticed that it stopped working for me this morning.  Anyone have the same issue? Thanks.

Resolved.  Likely a mistake I made. Thanks!

Glad to be of help! ;)

David -
Thanks so much for the code!  I think what actually happened is Garmin Connect went down for a bit; I just happened to be testing something else at that time, and after fretting for about 20 minutes, I came back, and it worked again.  Weird.
Thanks again,
Brian

On Dec 29, 2020, at 3:41 PM, David Wilcock<EMAIL_ADDRESS>wrote:
Glad to be of help! ;)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/dawguk/php-garmin-connect/issues/46#issuecomment-752277423, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJNXSZ4FPDVZQUP6XG3QBLDSXJSLXANCNFSM4VNW5FZQ.


Clarification on SQL Ledger storage

Please clarify if SQL Ledger is supported on any WORM storage or just Azure and if so, how the database needs to be created. Do only data files reside on WORM storage and logs on standard storage?
Thanks
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c2c95399-0656-08b2-6daf-bea16906ff5b
Version Independent ID: c2c95399-0656-08b2-6daf-bea16906ff5b
Content: Configure a ledger database - SQL Server
Content Source: docs/relational-databases/security/ledger/ledger-how-to-configure-ledger-database.md
Service: sql-database
Sub-service: security
GitHub Login: @VanMSFT
Microsoft Alias: vanto

Hi @DougBernhardtData - This is discussed here: https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-overview?view=sql-server-ver16#how-it-works

https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-overview?view=sql-server-ver16#how-it-works is a high level explanation.  There is no detailed explanation on exactly how to do it. The following excerpt which is the only mention of on-premises WORM simply contains a link to a wikipedia article " on-premises Write Once Read Many (WORM) storage devices"

Thanks for the feedback, @DougBernhardtData.
@Pietervanhove - Pieter, do you mind reviewing this and see if we can add some clarity into our docs, or comment on the feedback.
#assign:Pietervanhove

Hi @DougBernhardtData
The WORM device can be used to store the database digest files.  In Azure SQL DB you can choose between Azure Storage or Azure Confidential Ledger for automatic digest storage. In SQL Server, we currently only support Azure Storage for automatic digest storage. If you want to use a local WORM device to store the database digests, you will have to generate the digests manually. I wrote a blog post about it a few months ago. See https://techcommunity.microsoft.com/t5/sql-server-blog/ledger-automatic-digest-upload-for-sql-server-without-azure/ba-p/3630992
A database that contains a ledger table should be created on normal storage.
Regards
Pieter

Hi @DougBernhardtData , thanks for contacting Microsoft! It seems your question was addressed so I'm going to close out this Git Issue but please feel free to comment should you need anything further.
Thanks again for reaching out and I hope you have a wonderful rest of your day!
Masha from the SQL Docs team
#please-close


Area for Improvement: Support advanced debugger capabilities in IDEs

The ability to step through logic and inspect program state is critical to many developer’s debugging workflows. Overall, the Dart debugger provides all the essential functionality needed by most developers to debug their application (e.g, pausing and resuming execution, stepping through code, inspecting state, etc.). However, when compared to the debuggers available in Android Studio and XCode, the debugger provided by Dart tooling is missing some advanced but useful functionality.
While some of the features provided by other tooling can likely be considered situational (e.g., contextual and dependent breakpoints), others could be useful to the average Dart developer. Some advanced features that could be useful include:

Suspend all threads / single threads on breakpoint: when debugging issues across multiple isolates, particularly those that involve message passing, stopping the world on when some breakpoint is hit (in particular, an unhandled exception), can make it easier to debug state across the entire process.
Support for filtering out handled / unhandled exception types: if developers are interested in tracking all exceptions thrown within their project, even if they’re handled, but don’t care about exceptions thrown and caught in other libraries (e.g., dart:core or some third party package), they should be able to filter out exceptions by type or origin library while break on all exceptions mode is enabled.
Break every N hits: gives developers the ability to inspect state after some specified number of hits where pausing on each hit would be too frequent.
Remove breakpoint once hit: a developer only cares about pausing on the first hit of a breakpoint to start stepping through a particular issue further along in the code.
Evaluate condition and log: rather than sprinkling print statements throughout their code that need to be removed after debugging, debug logging can be done through log points that execute based on the result of an expression evaluation. When debugging is completed, the log points can simply be removed without any modifications to project code.

Given the nature of these advanced features, most of them could likely be implemented in either DDS or the Dart debug adapter protocol (DAP) implementation. The remaining features would need to be explicitly added to the VM service protocol specification and would need to be implemented in both the Dart VM and DWDS.

Which of these features do you envision having to be implemented in the Dart VM?

It depends. Most, if not all, could probably be implemented in DDS but I've marked it as a VM service issue for now until we know for sure. Feel free to change the labels if you think there's a better set to use.

Another item on the list is supporting hybrid debugging where we can step in and out across language boundaries (e.g. you step into FFI call - you land in C++ code, or even step into JNIGEN code and land in the Java code).


Python Language Server Logging Information Not Written To Output

@mobiusklein commented on Thu Apr 04 2019
Environment data

VS Code version: 1.32
Extension version: 2019.3.6352
OS and version: Windows 10 Pro 1809
Python version (& distribution if applicable, e.g. Anaconda): Anaconda Python 2.7/3.68
Type of virtual environment used: conda

Expected behaviour
When the Python Language Server starts up or begins an analysis, if the log level is set to Trace, incremental progress information will be displayed as it analyzes files in the Output tab in the terminal panel.
When vscode-python lints a file, it will indicate that it ran the linter in the Output tab in the terminal panel.
Actual behaviour
No content is written to the Output tab.
Steps to Reproduce

Open a file with the extension .py with vscode
Wait for extension to active, monitoring both the status bar and the Output tab

Not sure what is expected. By default tracing is not produced because it slows down analysis quite a bit (~20%).

When the log level is configured to be Trace, I thought that would enable the trace messages. Is there another configuration I need to modify to get that information?

If you set "python.analysis.logLevel": "Trace", then you should be getting lots of stuff into the output panel.

The "python.analysis.logLevel" key is set to "Trace", and still the output is empty.

You are in the Output panel with Python selected in the dropdown at the right, correct?

i.e.:

Apparently not, thank you. I was seeing it in what I thought was the default tab for some period of time. I do see the tracing statements, and the linting banner, though no linting output is shown below the banner nor problems published, even when there are undefined top level symbols.
I'll try to find an explanation for that separately, so this can be closed.

But I'm still seeing this on VS Code 1.63.2
the test:
def test_foo(self):
    LOGGER.critical('critical')
    LOGGER.error('error')
    LOGGER.warning('warning')
    LOGGER.info('info')
    LOGGER.debug('debug')
    LOGGER.fatal('fatal')

and the setting:
"python.analysis.logLevel": "Trace",

and the output:

???


FIX: tags are missing in slack command status

related to this topic https://meta.discourse.org/t/discourse-status-slack-command-does-not-show-tags/60651?u=vinothkannans

Also tests please 😁

@tgxworld changes are done. Now it can be merged.

@tgxworld changes are done now

Now it's fixed. Should I squash my commits here too?

@vinothkannans Yup you almost always want to squash your commits. "update" commits should really just be part of the main commit :)

@tgxworld it is now squashed :+1:

Cool I'll test it out tml before merging.

@tgxworld I added two more commits which related to https://meta.discourse.org/t/discourse-status-should-only-show-the-status-for-the-current-channel/60892
If you are OK with these commits then I will squash it.

Merged in https://github.com/discourse/discourse-slack-official/commit/1a32095d756d214ea465e0f890014a2049c04091.
Thank you @vinothkannans


Add rude implementation of buddy system allocator

The CI seems like not being triggered by pull requests. Can you fix this by changing
https://github.com/imtsuki/xv7/blob/fbb700c0769bf12b34c6ef793df92bee6e03c241/.github/workflows/rust.yml#L3
to
  on: [push, pull_request]


SENSORS

Hi.
i'm trying to add
sensors: ^0.8.4+2 on dependencies:
but i got this error.
[proyecto_crumbs] flutter pub get
Resolving dependencies...
Git error. Command: git clone --mirror git://github.com/fluttercommunity/sensors.git C:\Users\David\AppData\Local\Pub\Cache\git\cache\sensors-167e421677789dfea279f6c88fc48349cb69039c
stdout:
stderr: Cloning into bare repository 'C:\Users\David\AppData\Local\Pub\Cache\git\cache\sensors-167e421677789dfea279f6c88fc48349cb69039c'...
remote: Repository not found.
fatal: repository 'https://github.com/fluttercommunity/sensors.git/' not found
exit code: 128
exit code 69
where can i found this library?
thanks

@DavidVyhmeister
sensor plugin is deprecated you can use sensors_plus
if you have any issue with the latter please open an issue in the plus_plugins

@DavidVyhmeister Please try adding sensors_plus as suggested above. I also would recommend you file a new issue on plus_plugins if you have a specific issue with these plugins.
Since this doesn't look like a Flutter framework issue, I will close the issue from here. If you still have this issue when adding any other packages, please write in the comments and I will reopen this for further investigation. Thank you!


Non-Root container false positive

Description
We are recently getting non-root-container alerts
Name: backup-internal

ApiVersion: batch/v1
Kind: CronJob
Name: backup-internal
Namespace:

Severity | Name | Docs | Assisted Remediation
-- | -- | -- | --
Medium | Non-root containers | C-0013 | spec.jobTemplate.spec.template.spec.containers[0].securityContext.runAsGroup=1000

Name: backup-internal
ApiVersion: batch/v1

Kind: CronJob

Name: backup-internal

Namespace:

Severity	Name	Docs	Assisted Remediation
Medium	Non-root containers	[C-0013](https://hub.armosec.io/docs/c-0013)
spec.jobTemplate.spec.template.spec.containers[0].securityContext.runAsGroup=1000

While it is true, that we don't set runAsGroup in the container's security context, we set runAsNonRoot in the pod's security context.
Documentation states:
Remediation
If your application does not need root privileges, make sure to define the runAsUser or runAsGroup under the PodSecurityContext or container securityContext and use user ID 1000 or higher, or make sure that runAsNonRoot is true.
In my understanding we should meet the criteria in the last sentence.
Do I mis-understand the documentation? Or is this a false-positive and probably a bug?
Environment
OS: Alpine Linux (Container environment)
Version: 3.18
Steps To Reproduce

This is one of the incriminated manifests

apiVersion: batch/v1
kind: CronJob
metadata:
  name: backup-internal
  annotations:

  labels:
    app.kubernetes.io/name: db-rv-tool
    helm.sh/chart: db-rv-tool-0.2.0
    app.kubernetes.io/instance: rv-tool
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/version: "master"
    alerts.n4.de/workload: high-cpu
spec:
  schedule: 45 */12 * * *
  timeZone: Europe/Berlin
  concurrencyPolicy: Forbid
  jobTemplate:
    spec:
      ttlSecondsAfterFinished: 86400
      template:
        metadata:
          name: backup-internal
          annotations:
            checksum/config: b5b96799c8c23ba72612c8ae14f0bdaee919a664a6bcf53d95bd145d0d7c1a6b
            checksum/secret: 87d02c00a9a573b759075f2c5751db236f8815641b1152ecacb03a30959a5831
            kubectl.kubernetes.io/default-container: db-rv-tool

          labels:
            app.kubernetes.io/name: db-rv-tool
            helm.sh/chart: db-rv-tool-0.2.0
            app.kubernetes.io/instance: rv-tool
            app.kubernetes.io/managed-by: Helm
            app.kubernetes.io/version: "master"
            networkpolicies.n4.de/access-from-ingress: deny
            networkpolicies.n4.de/access-from-prometheus: deny
            networkpolicies.n4.de/access-from-own-namespace: deny

            networkpolicies.n4.de/access-to-own-namespace: allow
            networkpolicies.n4.de/access-to-prometheus-pushgateway: allow
            networkpolicies.n4.de/access-to-world: allow
            alerts.n4.de/workload: high-cpu
        spec:
          imagePullSecrets:
          - name: n4r-rv-tool-pullsecret
          securityContext:
            runAsNonRoot: true
          containers:
          - name: backup-internal
            image: registry.n4group.eu/team-elster/helper/postgres-v15-backup:v0.15.1
            imagePullPolicy: Always
            command:
            - "backupandrestore"
            - "-b"
            - "-e"
            - "PUSH"
            securityContext:
              allowPrivilegeEscalation: false
              capabilities:
                drop:
                - all
              privileged: false
              readOnlyRootFilesystem: true
            resources:
              requests:
                cpu: "250m"
                ephemeral-storage: "256Mi"
                memory: "256M"
              limits:
                cpu: "750m"
                ephemeral-storage: "256Mi"
                memory: "1Gi"
            volumeMounts:
            - mountPath: /tmp
              name: n4-tmp
            - mountPath: /home/bnr
              name: home-bnr
            envFrom:
            - secretRef:
                name: n4c-db-rv-tool-backup-postgres-internal
            startupProbe:
              exec:
                command:
                - cat
                - /tmp/backupandrestore.pid
              failureThreshold: 5
              periodSeconds: 3
            livenessProbe:
              exec:
                command:
                - cat
                - /tmp/backupandrestore.pid
              initialDelaySeconds: 15
              periodSeconds: 3
              failureThreshold: 3
            readinessProbe:
              exec:
                command:
                - cat
                - /tmp/backupandrestore.pid
              initialDelaySeconds: 15
              periodSeconds: 3
          volumes:
          - emptyDir: {}
            name: n4-tmp
          - emptyDir: {}
            name: home-bnr
          restartPolicy: Never
          priorityClassName: n4-medium-plus

Expected behavior
Non-root containers should not be incriminated. If setting runAsGroup is expected, the documentation seems misleading, at least to me.
Actual Behavior
We get a false-positive for C-0013

Thank you for reporting this.
@YiscahLevySilas1 can you please take a look?

@YiscahLevySilas1 I think that change whould make it clear what needs to be done to prevent the finding. Thank you! :smiley:

Great - thanks for reporting, I'll update the remediation


Add greyworld AWB mode

Adds the greyworld AWB mode for the Pi Noir cameras

Hey, just to let you know I've merged a copy of this PR into a picamera fork we're using for some projects, found at https://github.com/labthings/picamerax/pull/2
Thanks!


Nested Compositors have mouse movement problems within 3D Games

Steps:

run a nested compositor (I tested Cage and labwc)
run a 3d game within them (I tested Portal and Minecraft)
Try to move your camera

Expected:
Movement works normally
What actually happens:
https://user-images.githubusercontent.com/76440879/212472187-bebcfc95-002a-4b69-9ed4-47ec815c63e0.mp4

Why did I get the idea to do this:
I thought this would help me deal with full-screen games better, since the I can just screencapture the nested compositor instead of the game itself.

Running gamescope within a nested compositor yielded me this result.
https://user-images.githubusercontent.com/76440879/212472892-27c7775f-6d2e-4c79-9aca-21cc2a413738.mp4
There is far too much mouse sensitivity.
(test.sh just makes a white terminal to increase contrast with my mouse cursor)

I'm pretty sure this is a problem with the micro compositor itself, not Hyprland. At least in my experience mouse sensitivity issues also occurs when using Gamescope in other Wayland environments.

jfc why

this is a wlroots issue iirc, generally you're not supposed to do this anyways


Version for Unreal 5.3

Hi! The Plugin will be updated to UE 5.3?? Thanks!

Hi @chisio23,
It is on the roadmap, but I cannot give you an estimate of when will it happen.

Would also like it for 5.2.1!

Hi @chisio23,
It is on the roadmap, but I cannot give you an estimate of when will it happen.

Hi Is the current version works with 5.0? I added it as plugin and it does not show any icon on my window like the demo video does. So I do not know how to open the easysynth window.

I hope we will be able to make new releases for UE 5.2 and 5.3 at some point, but there is still no expected date.
The most recent version is compatible with 5.1, while the previous release is compatible with 5.0 (https://github.com/ydrive/EasySynth/releases/tag/v2.0.0).
Nothing comes to my mind as to why the icon would not appear.

Hi, releases for all major 5.x UE versions are now available on the UE marketplace and in the dedicated Github releases.


great app god must bless

hope to add recovery version in the future!

Hi, @benjaminhsu20021009! Can you please clarify what you mean by a "recovery version"?

@benjaminhsu20021009 Just wanted to check in if you could please provide more detail about what you are looking for in this functionality.

sorry for being too late to reply, the "recovery version" I mean is a version of bible just like ESV or AMP

@benjaminhsu20021009 YouVersion Suggest already supports multiple versions/translations, if that's what you're wondering. You can use the yvset version command to change your preferred version/translation.


Capacity Default Setting

"Capacity Default: The dataset inherits the setting from the Premium capacity. The capacity default is controlled by the Power BI Premium capacity administrator."
Where am I able to change the default?  I can't find it in the admin center for our Premium capacity.

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

ID: c13962e5-2d39-a6cd-274c-2317477acc22
Version Independent ID: 099fe9f8-0c2b-b359-b761-251587a0ab76
Content: Query caching in Power BI Premium - Power BI
Content Source: powerbi-docs/power-bi-query-caching.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

On the blog it says: this setting will be added in the near future.
https://powerbi.microsoft.com/en-us/blog/announcing-query-caching-in-power-bi-premium/

Thanks for your comment, @apfenech. This issue has been assigned to the doc author for review.

Hi, @apfenech and thanks for your comment, @NickyvVr -- I'm checking to see if you should be seeing it now. If not, I'll delete it.
thanks!

Hi, @apfenech and @NickyvVr -- I've deleted it for now.
Thanks!

Has this feature still not been added to the admin center?


Unable to download (any?) theme

Describe the problem and steps to reproduce it:
(Please include as many details as possible.)
I went to the add-ons site via 1) the web site and 2) the extensions tab in thunderbird. I was looking for a dark theme (to match the new MacOS dark theme :).
But I tried multiple (also non-dark) themes, and all brought me to a 404 not found page when i clicked on the '+ add to Thunderbird' button.
What happened?
I got a 'We're sorry, but we can't find what you're looking for' page, instead of the plugin/theme being downloaded.
What did you expect to happen?
That the plugin/theme would be loaded.
Anything else we should know?
(Please include a link to the page, screenshots and any relevant files.)
Not sure what other details could be of help, other than:
OS: MacOS High Sierra
Thunderbird Version: 52.9.1 (64-bit)
Browser: Chrome 69

Most themes cannot be downloaded, they must be installed within Thunderbird. See: https://support.mozilla.org/en-US/kb/install-themes-change-look-thunderbird
Note that this requires Thunderbird 60, which can be downloaded from https://www.thunderbird.net -- there are a number of problems with TB52 and the addons site at this point.


Validate email address is entered for passwords#create

Currently there is no error message when someone tries to reset the password and enters no email address. The passwords controller even tries to find a user without an email address.
Wouldn't the default case be that you'd want an error message to appear if no email address is entered?

This is a bit harder to address than I would like due to the fact that many of the forms do not have backing models which to call validate on. I could write those easily but that'd be a breaking change for people who have generated the views.
We could do validations in the controllers based on params, but I don't really love that solution. One stop-gap would be to add HTML5 validations to forms. I'll likely kick the tires on this.

Yeah I think introducing a model and validations would be overkill. But logically, looking at the controller, I would expect a check that params[:password][:email] is present before this line:
https://github.com/thoughtbot/clearance/blob/781e9a9fd99bad27b45fa10e1c3b019b8caa31a5/app/controllers/clearance/passwords_controller.rb#L66


fix: Add TeamForCapella flags for stable xmi:ids

In the default configuration, xmi:ids are not stable. This leads to a huge diff in Git in each commit.
With the added flags, the CDO IDs are used as xmi:id.

I've tested the changes against a large model. It took 39.107 seconds without the new flags and 39.428 seconds with the new flags. The small increase in time is probably negligible and can be attributed to measurement accuracy.


Add pbm configs

Summary
backups to s3 require options from the user. This PR implements the config changed action
Context
Backups for Charmed MongoDB make use of PBM. PBM requires configurations in s3 such as: storage.s3.region storage.s3.bucket, storage.s3.prefix, storage.s3.credentials.access-key-id, storage.s3.credentials.secret-access-key, storage.s3.serverSideEncryption.kmsKeyID.
Manual test
Manually tested by listing config options with percona-backup-mongodb config --list to verify that juju config mongodb  option="value" was effective
Future PRs
As mentioned this is the first PR of several to get the backup action up and running. The rest are:

Implement the backup action
Add unit tests
Integration tests

Closing this PR because it doesn't match the agreed upon implementation which is:
juju deploy s3-integrator
juju run-action s3-integrator/leader sync-s3-credentials \
    access-key=<your_key> \
    secret-key=<your_secret_key>
juju config s3-integrator \
    bucket=s3-bucket-name \
    path-prefix=some-dir \
    access-key=login \
    secret-key=password
juju relate s3-integrator mysql
juju run-action --wait mysql-k8s/0 create-backup
juju run-action --wait mysql-k8s/0 list-backups
juju run-action --wait mysql-k8s/0 restore backup-id=<%Y-%m-%d-%H-%M>


PPA does not contain packages for Ubuntu 14.04 LTS Trusty Tahr

This results in errors when running apt-get update, e.g.
W: Failed to fetch http://ppa.launchpad.net/cartodb/base/ubuntu/dists/trusty/main/binary-amd64/Packages  404  Not Found
W: Failed to fetch http://ppa.launchpad.net/cartodb/base/ubuntu/dists/trusty/main/binary-i386/Packages  404  Not Found
and so on.

If you go to http://ppa.launchpad.net/cartodb/base/ubuntu/dists/ , you will see that the only distribution supported are Ubuntu LTS Precise (12.04) and Lucid (10.04) , so NOT Trusty (14.04)

We don't officially support anything other than Precise (12.04) yet. It might work if you change the config at /etc/apt/sources.list.d/... to point to "precise" instead of "trusty", it might work but we don't warantee it will (as we only test and run on Precise for now).


The function was called unexpectedly when its name is the same as the component name

Version
3.2.27
Reproduction link
sfc.vuejs.org/
Steps to reproduce
open the reproduction link and see devtools console
What is expected?
hello wont be called
What is actually happening?
hello has be called

And the template ref's value is wrong too

how to use a template ref properly is documented here.
https://v3.vuejs.org/guide/composition-api-template-refs.html#template-refs

This is expected
You can resolve this by not using conflicting names for an imported component and local function .
<hello ref="helloRef" />

to
<Hello ref="helloRef" />

is a possible fix  for your use case.

This is expected You can resolve this by not using conflicting names for an imported component and local function .
<hello ref="helloRef" />

to
<Hello ref="helloRef" />

is a possible fix for your use case.

It's works, thanks.


adds servertime to countdown timer, fixes #114

Karma is failing, not sure what is causing it as there is no stack trace. Works perfect in browser.

The first version of this plugin (v1.0) used this approach, but in the end accumulating the milliseconds has a lot of disadvantages so it was change in version 2.x. There is an Issue where you can found more detailed explanation.


MA-606: add "no data" icon for vitals

https://konghq.atlassian.net/browse/MA-606
Summary
Added a new dashed line KIcon (grabbed it from Figma).
Vue 3
Did you create a corresponding PR to add this change to the beta branch? (required)

[ ] Yes, here is a link to the PR: [link to beta branch PR]
[ ] No, I did not create a PR for the beta branch and I have added the port to beta branch tag to this PR.
[ ] No, because [type your reasons]

PR Checklist

[ ] Does not introduce dependencies
[ ] Functional: all changes do not break existing APIs and if so, bump major version.
[ ] Tests pass: check the output of yarn test packages/
[ ] Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
[ ] Framework style: abides by the essential rules in Vue's style guide
[ ] Cleanliness: does not have formatting issues, unused code (e.g., console.logs), or leftover comments
[ ] Docs: includes a technically accurate README, uses JSDOC where appropriate

 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.

@kaiarrowood have a look please.  Icon should be centered now, and have the correct fill color.
https://deploy-preview-644--kongponents.netlify.app/components/icon.html


chore: add maxveldink to org

Requirement for https://github.com/open-feature/community/pull/333
@maxveldink please :+1: this PR if you're OK to be a member!

@staceypotter @DavidPHirsch can we add @maxveldink to the currently open GC vote? He's been a contributor for a good long while, but for some reason we missed his addition to the org until now.


Documentation for existing functions and constructors

Added a few docstrings to the existing functions in the repository, including Population, Impact, Food and land modules.
This does not include documentation to the utils module which will be removed soon.

Set this as a draft, as I'm being cautious of multiple PR potentially making changes to the same files, and the conflicting each other.


Automatic detection failed in sct_label_vertebrae

Description
Automatic detection of vertabrae failed using the file sub-1000032.T1w_seg.nii.gz with sct_label_vertebrae. The data is from Ukbiobank. Right now, the gradient distortion correction isn't applied on these images, but the segmentation of the spinal cord worked for the T1w image.
Here is the segmentation of the T1w image:

Steps to Reproduce
DATA:
sub-1000032_T1w.nii.gz
sub-1000032_T1w_seg.nii.gz

Install SCT v5.0.0

Run

sct_label_vertebrae -i sub-1000032_T1w.nii.gz -s sub-1000032_T1w_seg.nii.gz -c t1

Expected behavior:
That the automatic vertebrae labeling would work and create  sub-100032_labeled.nii.gz
Actual behavior:

@sandrinebedard it failed because there is nothing to detect 😉 .
The algorithm is supposed to find C2-C3 disc, which is not visible in your image.
as discussed you need to use the distorted (raw, uncropped) image


Mx Linux debian 10----WidevineCDM download error.

Hello developers.
System in use: MX linux debian
KOdi matrix 19
When I try to start some live content, I am asked to install widevine CDM, I click ok, but nothing happens, and I get the error you see in the screenshot.
How can I solve?

Thanks

I need a full debug log to investigate your problem. Please read https://kodi.wiki/view/Log_file/Easy

Thanks , mediaminister!
https://paste.kodi.tv/lirayugake.kodi
wish you did well!

I have a fix for your problem, can you test the following test package?
script.module.inputstreamhelper-0.5.2+matrix.1-prev-dd63bce.zip

Should I install as a normal zip file addon?

I have updated, not solved

Yes, install as a normal zip file addon. I'll test more to make sure it works.

Please test this new test package. Install add-on as zip
script.module.inputstreamhelper-0.5.2+matrix.1-prev-b2727ab.zip

Great, this worked.
Only now it asks me if I want to update widevine, but it never stops updating, and when I start Kodi, I get two errors:

remote server communication failed;
error tubed api.

I'm waiting for your news, thanks :-)

I guess this will work:
script.module.inputstreamhelper-0.5.2+matrix.1-prev-4941c2f.zip

Excuse me. The two errors were caused by multiple instances of kodi running in the backgroud.
This latest script doesn't work.
Failed to play :-(

Some channels ask to update widevine: do I do this?

You can try or provide more info, a screenshot or debug log so I can investigate.

Some channels, not all.
If you need the log let me know.
Thank you

@Rick654
So is this problem completely solved for you also for LA7 plugin ?
https://github.com/luivit/plugin.video.rivedila7/issues/56


Handle CoreCLR events

This adds support for enabling the CoreCLR ETW provider and tracking events related to
JIT compilation, GC, and others if the --coreclr argument is used. There is also
a --coreclr-allocs, which will emit an event for every GC allocation (which is a lot).
(The allocation tracking doesn't emit the type name yet, just a type handle, but names
are coming.)
CoreCLR events are only currently useful if Samply launches the app; there's future work
coming to enable the CoreCLR "rundown" provider that provides all the necessary info
at the start of capture for existing processes. (Similar to the DCStart events; it's just
not enabled by default because it's very expensive, as it has to dump info about all JIT
methods already compiled etc.)

CoreCLR events are only currently useful if Samply launches the app;

Or when using samply record -a if the app starts after profiling starts, I assume.


[New Port Request]

Library name: Simd
Library description: The Simd Library is a free open source image processing and machine learning library, designed for C and C++ programmers. It provides many useful high performance algorithms for image processing such as: pixel format conversion, image scaling and filtration, extraction of statistic information from images, motion detection, object detection (HAAR and LBP classifier cascades) and classification, neural network.
Source repository URL: https://github.com/ermig1979/Simd
Anything else that is useful to know when adding (such as optional features the library may have that should be included): Builds pretty easily, info in repo's readme.

DLL builds on windows for both x86 and x64 in Debug/Release without any problems as is from source, just pull and build. Different projects for building are located in this directory: https://github.com/ermig1979/Simd/tree/master/prj.
Static windows build require you to change project's output type to Static Library and uncomment #define SIMD_STATIC in simd/src/Simd/SimdConfig.h. After that build as good as dll for all types (x86, x64; Debug/Release).
For linux libs cmake can be used (https://github.com/ermig1979/Simd/tree/master/prj/cmake), instructions are in readme (https://github.com/ermig1979/Simd/blob/master/README.md). Though library builds for linux, I didn't test if it actually works.

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now, consider making a pull request instead.


GET /api/v1/posts/ schema is incorrect

{
  "page_size": 50,
  "page_number": 1,
  "page_results_count": 31,
  "total_results_count": 31,
  "posts": [
    {
      "id": "44d51254-c7c0-5643-adb5-6e488b7defd9",
      "feed_id": "bf07ffa3-4099-5fbc-90c7-681f850744d3",
      "datetime_added": "2024-12-05T14:24:14Z",
      "datetime_updated": "2024-12-05T14:24:18Z",
      "title": "monday evening post",
      "description": "removed",
      "pubdate": "2024-12-02T19:09:00Z",
      "author": "Throwawy",
      "is_full_text": true,
      "content_type": "text/html; charset=utf-8",
      "added_manually": false,
      "categories": []
    },

Response missing profile_id and link
schema (below) should not have markdown_file
{
  "page_size": 50,
  "page_number": 3,
  "page_results_count": 50,
  "total_results_count": 3,
  "posts": [
    {
      "profile_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "datetime_added": "2024-12-06T06:33:18.140Z",
      "datetime_updated": "2024-12-06T06:33:18.140Z",
      "title": "string",
      "description": "string",
      "link": "string",
      "pubdate": "2024-12-06T06:33:18.140Z",
      "author": "string",
      "categories": [
        "string"
      ],
      "is_full_text": false,
      "content_type": "plain/text",
      "added_manually": false,
      "feed_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "markdown_file": "string"
    }
  ]
}

this looks like a sync issue, the post has been processed on h4f but it hadnt been added to obstracts so it doesn't have a profile_id yet.
And I don't think it's possible for a response to be missing link, I can't reproduce this.


Nix: add XWayland hidpi option

Describe your PR, what does it fix/add?
Adds hidpiXWayland flag and the required logic to get it working.
Based on https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/733
The flag will be enabled by default, as I haven't had any issues with it in the past few days.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Users will have to adjust their config files accordingly, possibly having to add
exec-once=xprop -root -f _XWAYLAND_GLOBAL_OUTPUT_SCALE 32c -set _XWAYLAND_GLOBAL_OUTPUT_SCALE 2

in order for XWL to scale. This will make XWL programs look as if they were unscaled. To fix this, users have to export different environment variables to make the specific toolkits render at the proper scaling. For example
export GDK_SCALE=2
export XCURSOR_SIZE=32

The GDK_SCALE variable won't conflict with wayland-native GTK programs.
Is it ready for merging, or does it need work?
I'm still not sure whether we should go with this approach, or rather having a separate package.
@viperML @Misterio77 @nix guys for reviews

I would add another job to the CI action to build this

And also move the patching into its own wlroots.nix file

@viperML I updated the HM module as well. Do you think I should also add a mkRenamedModule entry? Essentially it's xwayland -> xwayland.enable.

Sure. I don't even think anyone would use that option to disable xwayland

Done. Mergeable?

Yes merge


[HTML5] Refactor event handlers, drop most emscripten html5 dependencies.

In this PR:

Refactor input events to use our own JS library.
Refactor input JS library into its own file.

In an effort to be less dependent on emscripten libraries, this PR drops most of the emscripten_* function usage in favour of internal JS implementations. This gives us more control over input processing, there's more work that could be done on this (e.g. resuming the AudioContext directly from JS), but this PR is growing already quite big, so I'd rather do that in a separate one.
With this, the only emscripten functions left used from C++ are the app lifecycle functions (set/cancel main loop, exit) and webgl related functions (context creation, buffer swapping, GLES compatibility).

Hey, just dropping in to say that this overlaps with my recent PR https://github.com/godotengine/godot/pull/52809 as it adds a new callback handler.
So if one goes through we'll have to update the other one.
I don't have a PR for the 3.x branch yet but the same thing goes for that too.

Thanks!


[Feature request] Lerna structure support - define directories for labelling

Quick suggestion, given some of the approaches for monorepo libraries, is to nest package folders inside of subdirectories instead of in the root.
If there was an array we could parse into the action configuration to tell the API where to look for changes would be very useful.
eg. Given Lerna structure
- packages
-- module1
-- module2
- package.json

My PR currently is labelled packages
Request
Given structure:
- packages
-- module1
-- module2
- package.json

Configure GH action
action "Label PR Monorepos" {
  uses =<EMAIL_ADDRESS>  secrets = ["GITHUB_TOKEN"]
  dir = ["/packages", "/src"] // Leave empty for default directory "root"
}

Outcome: PR's label per subdirectory instead

👋 thanks for the suggestion.  Looking into it.

@clifford-lc per your suggestion

dir = ["/packages", "/src"] // Leave empty for default directory "root"

Are you thinking it would be helpful to configure multiple directories that contain modules?  Just wanted to double check and not assume.

Are you thinking it would be helpful to configure multiple directories that contain modules? Just wanted to double check and not assume.

Correct, I think it would be useful to define the directory/directories that contain the module folders to loop through.

https://github.com/lerna/lerna#what-does-a-lerna-repo-look-like
In my use case, the lerna.json file defines 2 directory locations to semantically split module folders, in JSON it looks a little like this:

"packages": [
    "packages/*",
    "services/*"
]

I would expect that if I were to define the following config for the GH action, it would find the folders within these directories instead of sniffing the root directory:
dir = ["/packages", "/services"]

I'm not sure if the label would have to change, perhaps eg. Repo: Foo and Repo: Bar from respective /packages/foo and /services/bar is still fine. Otherwise Repo: packages/foo as a label could make sense, but if someone were to define deeper subdirectories, maybe some other issues may arise Repo: really/deep/subdirectory/for/the/insane/package

@clifford-lc check out the PR w/ a proposed implementation - feedback appreciated 👏

@adamzolyak It looks good to me, it hits the lerna monorepo style 👍
I wonder if BASE_ENV definitions does/should support paths like path/to/package|module-folder? Something for later perhaps.

Released https://github.com/marketplace/actions/monorepo-pr-repo-labeler?version=1.1.1.  Thanks for the help @clifford-lc 👏👏👏!


Great project! you need to upload this project on NPM.js

Why don't you let the world use this great project?
I was finding fine project sth like this for a whole day!

Thank you for loving this tool so much. I'm still trying to find some time to improve it. Any comments or ideas are welcome.


APNS bundleId is deprecated, use topic instead

Hello
I have a problem your plugin, Before that everything ok but when I reinstall package via command line npm install. I have get a error
 0|parse-se | node-pre-gyp WARN parse-server-push-adapter APNS bundleId is deprecated, use topic instead
0|parse-se | node-pre-gyp WARN parse-server-push-adapter APNS bundleId is deprecated, use topic instead
0|parse-se | node-pre-gyp WARN parse-server-push-adapter APNS bundleId is deprecated, use topic instead
0|parse-se | node-pre-gyp WARN parse-server-push-adapter APNS bundleId is deprecated, use topic instead

Note that it work for Android and IOS before that. For now it only work Android, by the way I use current version
parse-server-push-adapter": "2.0.0-alpha.1",

This is intentional.
Please see discussion on https://github.com/parse-community/parse-server/issues/3987


Wrong closure capture in folded cycle.

Steps To Reproduce
https://deck.net/a2d9df1ab9da9e244785d985e6187fe3
public class Program
{
    public static int[] data = new int[]{ 1, 2, 3};
    public static List<Action> actions = new List<Action>();

    public static void Main()
    {
       	foreach	(var i2 in data)
        foreach	(var i in data)
            actions.Add(()=> Console.WriteLine(i));

        foreach (var action in actions)
            action();
    }
}

Expected Result
1
2
3
1
2
3
1
2
3

Actual Result
3
3
3
3
3
3
3
3
3

Hi @VoronFX – Thanks for reporting this issue, and for the excellent sample demonstrating how to reproduce. We will investigate right away and fix.

No problem! I've discovered it while preparing a speech about Bridge.NET awesomeness for upcoming .NET Developers Meetup in Tokyo. =)

Cool! You should post an announcement for the Tokyo meetup in the fourms.
I would like to know more, and please feel free to contact me directly<EMAIL_ADDRESS>if you require any assistance.

This issue has been fixed and will be included in the upcoming Bridge 16.3.1 release.