RangeSlider onChangeEnd method called twice when used in a showModalBottomSheet

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

Create a widget to render RangeSlider widget.
Then show this widget inside modalBottomSheet using the showModalBottomSheet method.
Now check the onChangeEnd callback of the RangeSlider widget. When the widget is used inside a sheet then the onChangeEnd gets called twice.

Expected results
The onChangeEnd method is called only once.
Actual results
The onChangeEnd method is called twice.

Once just after beginning the dragging.
After the actual end of the dragging.

Code sample
Code sample

import 'package:flutter/material.dart';

/// Flutter code sample for [RangeSlider].

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

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

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(title: const Text('RangeSlider Sample')),
        body: const MyButton(),
      ),
    );
  }
}

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

  @override
  Widget build(BuildContext context) {
    return Center(
      child: Column(
        mainAxisAlignment: MainAxisAlignment.spaceAround,
        children: [
          const RangeSliderExample(),
          ElevatedButton(
              onPressed: () {
                showModalBottomSheet(
                  context: context,
                  builder: (ctx) {
                    return const RangeSliderExample();
                  },
                );
              },
              child: const Text('Show range slider in bottom sheet')),
        ],
      ),
    );
  }
}

class RangeSliderExample extends StatefulWidget {
  const RangeSliderExample({super.key});

  @override
  State<RangeSliderExample> createState() => _RangeSliderExampleState();
}

class _RangeSliderExampleState extends State<RangeSliderExample> {
  RangeValues _currentRangeValues = const RangeValues(40, 80);

  @override
  Widget build(BuildContext context) {
    return RangeSlider(
      values: _currentRangeValues,
      max: 100,
      labels: RangeLabels(
        _currentRangeValues.start.round().toString(),
        _currentRangeValues.end.round().toString(),
      ),
      onChanged: (RangeValues values) {
        setState(() {
          _currentRangeValues = values;
        });
      },
      onChangeEnd: (RangeValues values) {
        debugPrint('On Change end value: $values');
        setState(() {
          _currentRangeValues = values;
        });
      },
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/96193041/39d89fde-15b0-40ee-93af-af7f1c5b3179

Logs
Logs
flutter: On Change end value: RangeValues(31.500871268866575, 80.0)
flutter: On Change end value: RangeValues(31.500871268866575, 65.79406498614406)

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.7.12, on macOS 13.4 22F66 darwin-arm64, locale en-DE)
    • Flutter version 3.7.12 on channel stable at /users/abc/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (7 weeks ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1

Checking Android licenses is taking an unexpectedly long time...[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /users/abc/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • ANDROID_HOME = /users/abc/Library/Android/sdk
    • Java binary at: /users/abc/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9971841/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 /users/abc/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.10121639/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)

[✓] Android Studio (version 2022.2)
    • Android Studio at /users/abc/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9971841/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)

[✓] IntelliJ IDEA Community Edition (version 2023.1.1)
    • IntelliJ at /users/abc/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/231.8770.65/IntelliJ IDEA CE.app
    • 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

[✓] IntelliJ IDEA Community Edition (version 2023.1.2)
    • IntelliJ at /users/abc/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/231.9011.34/IntelliJ IDEA CE.app
    • 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

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 12 (API 32) (emulator)
    • iPhone 14 Pro Max (mobile)  • CA6B67AE-6E76-41BA-8E57-68963373CD70 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 13.4 22F66 darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 113.0.5672.126

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Thanks for the detailed report and identifying possible root-cause. I see the same behavior on latest versions.
Also, the behavior seems to be specific to showModalBottomSheet only, as I tried with AlertDialog and onChangeEnd() is triggered only once.

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.10.3, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.10.3 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f92f44110e (4 days ago), 2023-06-01 18:17:33 -0500
    • Engine revision 2a3401c9bb
    • Dart version 3.0.3
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.12.0-2.0.pre.20, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.12.0-2.0.pre.20 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1bd1b5014c (4 hours ago), 2023-06-07 18:16:30 -0700
    • Engine revision a5f7d5d75f
    • Dart version 3.1.0 (build 3.1.0-171.0.dev)
    • DevTools version 2.24.0
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

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

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

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

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

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

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Hi @bahag-chandrana thank you for this report!
It looks like this is the same issue as we had with the regular Slider here https://github.com/flutter/flutter/issues/28115
The fix is the same, so I just submitted a PR :-)

A little bit of debugging shows that the _handleTapCancel method in range_slider.dart is being called which intermittently ends the interaction and triggers the _endInteraction method and thereby triggering onChangeEnd.

Yeah, this you are right this is the origin of the bug and it needs to be removed.

@nt4f04uNd Thank you so much for the fix 😃 . Do you know if this will be rolled out to 3.7.12 or only be available in 3.10.x stable.

@nt4f04uNd Thank you so much for the fix 😃 . Do you know if this will be rolled out to 3.7.12 or only be available in 3.10.x stable.

https://github.com/flutter/flutter/wiki/Where's-my-commit%3F#finding-the-versions-that-contain-framework-commit-x
commit: https://github.com/flutter/flutter/commit/ad8c9978174ce6c08b22994bfd6d318beb025d91
I will neither avaible on 3.7.12 nor 3.10.x unless there is a CP.

@nt4f04uNd Thank you so much for the fix 😃 . Do you know if this will be rolled out to 3.7.12 or only be available in 3.10.x stable.

@maRci002 is right - this will only make its way into the next beta version


Add an "--ignore-unsendable-files" flag

This is a work-in-progress attempt to fix #112 by:

Making unreadable file errors more human-friendly;
Adding an --ignore-unsendable-files flag that ignores such errors.

Examples
Here's what it looks like if we send a directory called breakage with a broken symlink called blap in it:
$ wormhole send breakage
Building zipfile..
ERROR:  A file you wanted to send couldn't be read, maybe because it's
not a file, or because it's a symlink that points to something that
doesn't exist.  To ignore this kind of error, you can run wormhole
with the --ignore-unsendable-files flag.

blap: No such file or directory

And here's what happens when we use the new flag:
$ wormhole send breakage --ignore-unsendable-files
Building zipfile..
blap: No such file or directory (ignoring error)
Sending directory (22 Bytes compressed) named 'breakage'
On the other computer, please run: wormhole receive
Wormhole code is: 7-maritime-trojan

To do

[x] Add test to ensure UnsendableFileError is raised when --ignore-unsendable-files is not passed.
[x] Add test to ensure UnsendableFileError is not raised when --ignore-unsendable-files is passed.

Ok, if travis/appveyor is happy with this, I think it's ready to go!

Looks like the windows error message is different:
https://ci.appveyor.com/project/warner/magic-wormhole/build/1.0.733/job/y79ne9b5iiiyd74p#L464
I guess the test should assert that the error string is one of the two possible values.

Oh shoot!  Ok, I think I fixed it, but I did so by making the test only test against the part of the string that doesn't include the actual OS error string--while testing for two would make things work across English versions of Linux and the version of Windows that appveyor uses, I believe it would fail on other locales and possibly other versions of OS's. Hope that's ok!

Looks good.. landing (in rebased form) momentarily.


Oracle Timestamp dataType can't be se serialized

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
java.lang.RuntimeException: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: No serializer found for class java.io.ByteArrayInputStream and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationFeature.FAIL_ON_EMPTY_BEANS) (through reference chain: io.seata.rm.datasource.undo.BranchUndoLog["sqlUndoLogs"]->java.util.ArrayList[0]->io.seata.rm.datasource.undo.SQLUndoLog["afterImage"]->io.seata.rm.datasource.sql.struct.TableRecords["rows"]->java.util.ArrayList[0]->io.seata.rm.datasource.sql.struct.Row["fields"]->java.util.ArrayList[2]->io.seata.rm.datasource.sql.struct.Field["value"]->oracle.sql.TIMESTAMP["stream"])
at io.seata.rm.datasource.undo.parser.JacksonUndoLogParser.encode(JacksonUndoLogParser.java:128)
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :
OS :
Others:

refer: #2047


local html file with javascript gives blank screen app

Summary Description
Converting newt-web.html and other files downloaded from stellafane website gives me blank screen app.
Tried replacing local path "newt-web.html" to full path like "file:///Users//path/newt-web.html" throws the following error
/usr/local/lib/node_modules/nativefier/lib/options/normalizeUrl.js:25
        throw 'Your Url: "' + normalized + '" is invalid!';
        ^

Directly converting the website link http://stellafane.org/tm/newt-web/newt-web.html makes a responsive app through.
Is there a different method for converting local html files to app?
Steps to Reproduce Issue
Download all the files given in the link http://stellafane.org/tm/newt-web/newt-web.html namely
newt-web.html
newt-web.css
newt-web.js
newt-save.php
newt-calc.js
newt-file.js
newt-info.js
telescope.ico
newt-specs.js
newt-trace.js
newt-draw.js
newt-help-ap.html
newt-help-scope.html
newt-help-ver.html
newt-help-gpl.html
Put them all in a folder
Move into the folder in a terminal and try
nativefier newt-web.html
Also tried
nativefier -p osx -a x64 -m -f -n Newt --maximize -i /Users/path-to-icon/icon.icns newt-web.html --ignore-certificate --insecure
which gave blank screen apps
When tried with various options such as these
nativefier -p osx -a x64 -m -f -n Newt --maximize -i /Users/path-to-icon/icon.icns /path/newt-web.html --ignore-certificate --insecure
nativefier -p osx -a x64 -m -f -n Newt --maximize -i /Users/path-to-icon/icon.icns file:///path/newt-web.html --ignore-certificate --insecure
and
nativefier -p osx -a x64 -m -f -n Newt --maximize -i /Users/path-to-icon/icon.icns "file:///path/newt-web.html" --ignore-certificate --insecure
It throws an error
/usr/local/lib/node_modules/nativefier/lib/options/normalizeUrl.js:25         throw 'Your Url: "' + normalized + '" is invalid!';         ^
Specifications

Version of Nativefier (run $ nativefier --version): v7.1.0
Version of Node.js (run $ node --version): v7.9.0
OS: Mac OS X Sierra 10.12.4
Architecture x64

Hi @rohinkumar, thanks for the feedback! No, currently there's no way to nativefy local files. Closing this duplicate of https://github.com/jiahaog/nativefier/issues/45, feel free to subscribe to it.


release v0.4.0

style: add emojis for changelogs too
chore(release): reliabot v0.4.0

This is wrong in many ways


Bug in file CronExpression.java

Hello!
Function findNextWhiteSpace always returns the last position of given string.
File server/src/main/java/com/orientechnologies/orient/server/schedule/CronExpression.java, line 949
Expression (s.charAt(i) != ' ' || s.charAt(i) != '\t') is always true.

if s.charAt(i) is space -> expression s.charAt(i) != '\t' is true -> (s.charAt(i) != ' ' || s.charAt(i) != '\t') is true
if s.charAt(i) is tabulation -> expression s.charAt(i) != ' ' is true -> (s.charAt(i) != ' ' || s.charAt(i) != '\t') is true
if s.charAt(i) is other symbol -> expression s.charAt(i) != ' ' is true -> (s.charAt(i) != ' ' || s.charAt(i) != '\t') is true

Example - https://ideone.com/wol0jb
This possible defect found by AppChecker

That class is old and not present after v2.0


Shl/Shr should throw UB on too large shift

The LLVM docs for shl say

If op2 is (statically or dynamically) equal to or larger than the number of bits in op1, this instruction returns a poison value.

However, the CTFE/Miri implementation of shl/shr currently just truncates the shift amount. In rustc-generated MIR this can never happen since there always is a check being emitted, but we should still make sure to implement all UB checks for this operation correctly -- and the simd_shl intrinsic also exposes direct access to this operation, making it possible to trigger this UB. (I plan to add tests for this.)
I just hope we didn't miss any other MIR operations which compile ti LLVM arithmetic operations that can produce poison/undef/UB... (we do check for div-by-zero, of course). Cc @rust-lang/wg-llvm

To my knowledge Div, Rem and the two shifts are the only MIR-native operations that have validity invariants. We also have unchecked methods for various operations, including those same shifts which expose these invariants to the users.

In rustc-generated MIR this can never happen since there always is a check being emitted

It can with -Zforce-overflow=checks=no. The shift amounts need to be truncated in that case: https://github.com/rust-lang/rust/blob/22c2d9ddbf356bcdb718e88ca6ee3665e1e42690/src/test/ui/mir/mir_overflow_off.rs#L2

We also have unchecked methods for various operations, including those same shifts which expose these invariants to the users.

Miri currently implements those by executing the MIR operation and then raising UB if an overflow is indicated.
For div and rem, AFAIK the unchecked intrinsics have a different validity invariant than the MIR-native operations: unchecked_div also makes overflow UB, such as in int_min / -1.

It can with -Zforce-overflow=checks=no. The shift amounts need to be truncated in that case

I assume truncation is happening as explicit MIR operation then (like the div-by-zero checks) -- or do the codegen backends implicitly insert truncation?

I assume truncation is happening as explicit MIR operation then (like the div-by-zero checks) -- or do the codegen backends implicitly insert truncation?

It is implicitly added.
pub fn foo(shift_amount: u8) -> bool {
    if 1 << shift_amount != 2_u8 {
        return false;
    }
    if 2 >> shift_amount != 1_u8 {
        return false;
    }
    true
}

gives the following MIR with -Zforce-overflow-checks=no:
fn foo(_1: u8) -> bool {
    debug shift_amount => _1;            // in scope 0 at /app/example.rs:1:12: 1:24
    let mut _0: bool;                    // return place in scope 0 at /app/example.rs:1:33: 1:37
    let mut _2: u8;                      // in scope 0 at /app/example.rs:2:8: 2:25
    let mut _3: u8;                      // in scope 0 at /app/example.rs:2:13: 2:25
    let mut _4: u8;                      // in scope 0 at /app/example.rs:5:8: 5:25
    let mut _5: u8;                      // in scope 0 at /app/example.rs:5:13: 5:25

    bb0: {
        _3 = _1;                         // scope 0 at /app/example.rs:2:13: 2:25
        _2 = Shl(const 1_u8, move _3);   // scope 0 at /app/example.rs:2:8: 2:25
        switchInt(move _2) -> [2_u8: bb2, otherwise: bb1]; // scope 0 at /app/example.rs:2:8: 2:33
    }

    bb1: {
        _0 = const false;                // scope 0 at /app/example.rs:3:16: 3:21
        goto -> bb5;                     // scope 0 at no-location
    }

    bb2: {
        _5 = _1;                         // scope 0 at /app/example.rs:5:13: 5:25
        _4 = Shr(const 2_u8, move _5);   // scope 0 at /app/example.rs:5:8: 5:25
        switchInt(move _4) -> [1_u8: bb4, otherwise: bb3]; // scope 0 at /app/example.rs:5:8: 5:33
    }

    bb3: {
        _0 = const false;                // scope 0 at /app/example.rs:6:16: 6:21
        goto -> bb5;                     // scope 0 at no-location
    }

    bb4: {
        _0 = const true;                 // scope 0 at /app/example.rs:8:5: 8:9
        goto -> bb5;                     // scope 0 at /app/example.rs:9:2: 9:2
    }

    bb5: {
        return;                          // scope 0 at /app/example.rs:9:2: 9:2
    }
}

The reason I know about this test in the first place is because it used to fail with cg_clif due to incorrectly implementing this truncating behavior.

So from that it seems like Miri is doing the right thing already -- but I can't find the code in the LLVM backend that does this truncation. Here it looks like it is just constructing a single Shl for the MIR binop.

The masking is done in cg_ssa: https://github.com/rust-lang/rust/blob/a3b9405ae7bb6ab4e8103b414e75c44598a10fd2/compiler/rustc_codegen_ssa/src/common.rs#L131-L158

Ah, there it is, thanks! I will add a comment in the Miri/CTFE code explaining this.
I assume the simd shift intrinsics directly use the underlying LLVM operation though, and thus do not implicitly truncate and do require a UB check here... so our SIMD operations are inconsistent with our MIR operations. :/

Indeed. It directly exposes the LLVM operation.
#![feature(platform_intrinsics, repr_simd)]

extern "platform-intrinsic" {
    fn simd_shl<T>(a: T, amount: T) -> T;
}

#[repr(simd)]
#[derive(Copy, Clone)]
pub struct u8x8([u8; 8]);

pub fn foo(a: u8x8) -> u8x8 {
    unsafe {
        simd_shl(a, a)
    }
}

define void @_ZN7example3foo17he8b5d79f940e09f4E(<8 x i8>* noalias nocapture sret(<8 x i8>) dereferenceable(8) %0, <8 x i8>* noalias nocapture dereferenceable(8) %a) unnamed_addr #0 !dbg !6 {
  %_2 = load <8 x i8>, <8 x i8>* %a, align 8, !dbg !10
  %_3 = load <8 x i8>, <8 x i8>* %a, align 8, !dbg !11
  %1 = shl <8 x i8> %_2, %_3, !dbg !12
  store <8 x i8> %1, <8 x i8>* %0, align 8, !dbg !12
  br label %bb1, !dbg !12

bb1:                                              ; preds = %start
  ret void, !dbg !13
}

Okay, that is good to know. Cc @workingjubilee this might be interesting to know for the SIMD folks, though I am not sure if you want to change anything here -- the SIMD shift intrinsics are not consistent with the MIR shift primitives. This will require extra care in a Miri implementation of those intrinsics, and could also be potentially confusing for other codegen backends.
AFAIK shifts are the only MIR primitive that does not directly correspond to an LLVM primitive, so I hope this is the only SIMD vs MIR inconsistency.

Since all backends need to do the truncation, how about we make it explicit in MIR and stop doing it in the backends?

So basically, we'd make too large shifts UB in the MIR -- seems fine to me, if someone wants to push through that change.

In Cranelift ishl/ushr/sshr are specified as masking themself. (Cranelift tries to avoid UB as much as possible.) Adding the masking at MIR level would result in two maskings for cg_clif.

OK then let's proceed with masking in the backends

That could also be handled by an optimization in cranelift though.
No strong opinion here, but it would be nice to make the MIR binops and intrinsics consistent (and that seems to be true for any backend that plans to implement simd_shl/shr).

No strong opinion here, but it would be nice to make the MIR binops and SIMD intrinsics consistent

I agree.

I was talking about making the 'primitive operations' that Miri/codegen see consistent -- so we have two options:

Make the SIMD intrinsic also well-defined for too large shifts. This would require a vectored version of the truncation that the LLVM backend currently performs -- not sure if that is a good idea, though maybe given that there already is a bounds check before the intrinsic is invoked, this will not be usable in high-throughput SIMD code anyway?
Make the MIR binop UB for too large shifts. This would require MIR building to explicitly perform truncation, leading to redundant truncation in cranelift -- not sure how good the cranelift optimizer is at removing the double-truncation.

To be honest, I regard all the compilers, including LLVM, as a bit silly here, because the assembly instructions in question tend to have a simple semantic of "if the arg is too big, then just set or clear all bits according to the existing semantics". This would be roughly equivalent to
fn $shift_op(self, rhs: U) -> T {
    let shift = cmp::max(mem::size_of<T> * 8 -1), rhs as _);
    $shift_impl(self, shift)
}

With the vectorized version simply doing that on a per-lane basis.
This may not actually be true on all machines LLVM targets, of course, so maybe LLVM shouldn't change that, but I have looked at several copies of this instruction on several different modern architectures, and just like Rust's other operators compile to, and matches the semantics of, a "just lower it to add reg0, reg1, reg2, don't worry too hard about optimizing it in isel", I don't quite see why Rust's shl, ashr, and lshr don't do the same.

Ah, so there's encodings for both that and a formally saturating shift (so 1 << BITS will set all, I think) for Neon, but x86 does masking for the scalar shift, but on PowerPC the vector shifts also mask, now that I actually look. I see, I see, that would make things more vexing to lower without UB or something indeed.

Anyways, now that I have finished being distracted by assembly manuals:

Make the SIMD intrinsic also well-defined for too large shifts. This would require a vectored version of the truncation that the LLVM backend currently performs -- not sure if that is a good idea, though maybe given that there already is a bounds check before the intrinsic is invoked, this will not be usable in high-throughput SIMD code anyway?

As far as the fact that there is a bounds check in the existing version of our implementation, I would not assume that this is considered a desirable feature by us. We have a few bounds checks in our current implementation simply because we did not yet find another route, because we are still at some edges negotiating our semantics, and because we do not want users to find interesting ways to discover UB while we hammer out such details.
For most operators, we have been implementing assuming an "always wrapping" semantic: No overflow checks. This also mirrors the behavior of most intrinsics users may be familiar with. So, in a way, that's a vote "for" Cranelift's interpretation, but at the same time it's not clear what we would most like do for the shift operators due to the varying machine behavior.

For most operators, we have been implementing assuming an "always wrapping" semantic: No overflow checks. This also mirrors the behavior of most intrinsics users may be familiar with. So, in a way, that's a vote "for" Cranelift's interpretation, but at the same time it's not clear what we would most like do for the shift operators due to the varying machine behavior.

Also, machine behavior does not matter all that much when what we are concerned with is generating LLVM IR.

simd_and is pretty efficient tho' on most arches, so it's not like I am going to lose sleep.

So you are saying, changing the LLVM backend to lower the simd_shl intrinsic into an LLVM SIMD and for masking followed by shl for the actual shift would be reasonable (and then you could remove the panic from the core::simd wrapper)?
That would also work well from a consistency perspective -- and it might be better for core::arch's shl to be panic-free, since presumably its arithmetic operations are also panic-free (except for division and rem, of course).

Also, machine behavior does not matter all that much when what we are concerned with is generating LLVM IR.

Well yes, but when at least one of the (virtual) machine implementers is in the conversation, discussing the implementation felt relevant, so I decided to embarrass myself by misremembering exactly how many architectures implement vector shl/shr with an inherently mostly-unwrapped mechanism. :^)

So you are saying, changing the LLVM backend to lower the simd_shl intrinsic into an LLVM SIMD and for masking followed by shl for the actual shift would be reasonable (and then you could remove the panic from the core::simd wrapper)?

Prooobably. I am not sure if using an appropriate and mask would have consensus, but at the moment I think it's on the table as an option, especially if @bjorn3 thinks that would help Cranelift in lowering. I will bring it up, as I was considering revising the wrapper to use simd_and (and thereby drop the panic) anyways.
At the moment, std::arch links directly against the "architecture intrinsics" for AVX512.

I opened https://github.com/rust-lang/rust/issues/91237 for discussing the inconsistency -- this is no longer just a Miri issue.


Maint 1.2

Thanks, corrected one translation with bad syntax, squashed together and merged as c99feee5f5f7a633b9f188d3d053027e2fc66645.


issues with llama_index dependency

Describe the bug
llama_index is imported in multiple places without any exception handling, but it is not added to the requirements. I appreciate the idea of avoiding bloated requirements, but we should probably add a user-friendly error message. You actually have done this in some places with the unstructured library.
Ragas version: 0.0.20
Python version: 3.10.12
Code to Reproduce
from langchain.document_loaders import DirectoryLoader
from ragas.testset import TestsetGenerator

loader = DirectoryLoader("./data", glob="*.txt")
documents = loader.load()

testsetgenerator = TestsetGenerator.from_default()
test_size = 10
testset = testsetgenerator.generate(documents, test_size=test_size)

Error trace
Traceback (most recent call last):
  File "/home/jafar/projects/rag-evaluate/src/generate_testset.py", line 2, in <module>
    from ragas.testset import TestsetGenerator
  File "/home/jafar/projects/rag-evaluate/env/lib/python3.10/site-packages/ragas/testset/__init__.py", line 1, in <module>
    from ragas.testset.testset_generator import TestsetGenerator
  File "/home/jafar/projects/rag-evaluate/env/lib/python3.10/site-packages/ragas/testset/testset_generator.py", line 16, in <module>
    from llama_index.node_parser.simple import SimpleNodeParser
ModuleNotFoundError: No module named 'llama_index.node_parser.simple'

Expected behavior
The following line should be printed:
ValueError: llama_index package not found, please install it with `pip install llama_index`

Additional context
There is also another issue regarding llama_index versions. I believe that's also relevant to the discussion, so I will create a new issue and attach here.

Now that the PR has been merged, I guess we can close this.


Update cats-retry to 1.1.1

Updates com.github.cb372:cats-retry from 1.1.0 to 1.1.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.cb372", artifactId = "cats-retry" } ]

labels: library-update, semver-patch

Codecov Report

Merging #55 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   93.22%   93.22%
=======================================
  Files           1        1
  Lines          59       59
=======================================
  Hits           55       55
  Misses          4        4

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 d4e34c8...6629d84. Read the comment docs.


Guard against missing formatters

Fixes #122

Mind adding changelog and merging?

Mind adding changelog and merging?

Sure!


PDI_value_parse during plug-in initilization can't be done

In GitLab by @Roussel-C on Feb 9, 2017, 16:51
When parsing a const char*  into a PDI_value_t with PDI_value_parse during the initization of a plug-in results in future failure  if the string contains reference to metadata or operator.
The value returned is not valid and future conversion from type PDI_value_t to int or str are failing.
The bug appears when parsing in the init function of plug-in utilities and converting PDI_value_t to int/str inside the event function of the plug-in.

In GitLab by @Roussel-C on Feb 14, 2017, 16:22
closed

In GitLab by @Roussel-C on Feb 14, 2017, 16:22
Ok... The error is not there anymore. Although I don't why it was not working in the first place. So I have updated Utilities plug-in in a way that was previously not working but that is working now.

In GitLab by @Roussel-C on Feb 13, 2017, 19:49
I will make an example in a new branch I think this will be the quickest.


"abort() was called at PC 0x400df2e9 on core 0" on M5 while adding it to iOS home app

abort() was called at PC 0x400df2e9 on core 0
0x400df2e9: chip::SessionHolder::Get() const at /Users/apple/connectedhomeip/src/lib/support/CodeUtils.h:489
(inlined by) chip::Optional<chip::ReferenceCountedHandlechip::Transport::Session >::Value() const & at /Users/apple/connectedhomeip/src/lib/core/Optional.h:171
(inlined by) chip::SessionHolder::Get() const at /Users/apple/connectedhomeip/src/transport/SessionHolder.h:54
Backtrace:0x40081e26:0x3ffe85400x400923a9:0x3ffe8560 0x40098ac6:0x3ffe8580 0x400df2e9:0x3ffe85f0 0x4012da31:0x3ffe8610 0x400dbfb3:0x3ffe8640 0x400dc545:0x3ffe8660 0x400dc619:0x3ffe8790 0x400dc675:0x3ffe87d0 0x40137e41:0x3ffe87f0 0x40137e51:0x3ffe8810 0x4013b216:0x3ffe8830 0x4013b4ee:0x3ffe8850 0x4013b515:0x3ffe88c0 0x40095631:0x3ffe88e0
0x40081e26: panic_abort at /Users/apple/tools/esp-idf/components/esp_system/panic.c:402
0x400923a9: esp_system_abort at /Users/apple/tools/esp-idf/components/esp_system/esp_system.c:121
0x40098ac6: abort at /Users/apple/tools/esp-idf/components/newlib/abort.c:46
the full log is attached her
M5_Panic.log
e

@shah-kartik What SHA was used here?  Knowing that is pretty important in terms of diagnosing the problem...  Clearly we are trying to report a ReadHandler whose underlying secure session has gone away, but the reasons secure sessions can go away have changed over time, so this may or may not still be an issue on tip, and the fix needed may be different depending on the situation.

Duplicate of #19472


ZetaClientd Uses unencrypted Validator Key

Zetaclientd is using an unencrypted validator key to sign transactions. This key should be encrypted or stored on a remote system.  Forcing operators to use an encrypted key is a big security issue and brand damage.
From https://docs.cosmos.network/v0.46/run-node/keyring.html#the-test-backend
Test Backend
Provided for testing purposes only. The test backend is not recommended for use in production environments.

Related to #359

Closing as it seems no longer relevant with the current state of the project. Feel free to reopen it.


Merge 2.x into Master

This will merge 2.x into Master, paving the cowpaths for a rolled release.
 Greens! @dlmanning @Keats Can we get this merged in so we can get this out the door today? I'd love to release this on the same day (within a few hours?) of the 3.0 release

I'm going to write an article about the new stuff in gulp-sass 2 / libsass, hopefully done by tonight.
Caught me a bit off guard, didn't expect node-sass to be released that fast!
congrats @xzyfer

Thanks all, y'all rock!

Wahoo!
Sounds good @Keats!
@dlmanning Can we get this rolled out? Or do we now have the ability to roll those?

@snugug Give me a couple hours and I'll publish the release. I'll also add you and @keats as contributors on npm. Thanks for the great work!

I look forward to checking my email in the morning :)

@snugug Give me a couple hours and I'll publish the release. I'll also add you and @keats as contributors on npm. Thanks for the great work!

Sounds good, thanks and thanks!

Published. Sorry about the delay; it was a busy day. @Snugug, I've added you as a contributor on npm. @Keats, if you tell me your npm username I'll do the same for you.

I don't have a npm user and to be honest, can't be arsed to create one right now.
No worries about the contributor thingy

Here's the article https://blog.wearewizards.io/gulp-sass-v2-released
Let me know if i made mistakes


Version 1.0

This issue tracks the process of the version 1.0

[x] Relationships #33.
[ ] Languages for entities #6.
[ ] Clean up the code more, so its easier for people to contribute.
[ ] Merge all repositories into this one.
[ ] Change current permission system to roles.
[ ] New api for entities #76.
[ ] Remove the default publication for entities #73.
[ ] Create a new website.
[ ] Write tests #77.

Previews versions will not be compatible with the new one, but I will create a upgrade guide.
I will create a new branch so people who want to help can.
Maybe I will add more.
I want to hear you comments

If we do it organically it will give everyone a chance to adapt to it without one single breaking release. As the new features come out, I will personally keep re-factoring my apps. I knew this would happen when I adopted meteor. I will say merging the repos should come first

This one might be a bit out of scope, but I'd love to see the bootstrap dependency removed from the admin. I might be interested in contributing to that actually because I loathe bootstrap. And maybe just clean up the default admin to be more modern looking.

Speaking of cleaning up the default admin I would love to see Inspinia Admin panel used with orion.  I simply like the look and field and it is clean and modern.

I have already purchased a subscription to inspinia admin so I get the latest updates and versions.  We could use that here.

I think the list is good.
I wouldn't worry so much about the front end technology for admin. Look at Django, it went with something very simple for a long time until people created their own skins on various technologies, and you're now able to choose and use whatever you prefer.

Clean up the code more, so its easier for people to contribute.

Also a small starting guide how to contribute.

@iamkevingreen I will focus on making orion as separated as posible to bootstrap, but the default theme will still be in it.
You can create a custom theme!

@rwatts3 I don't think the license of inpinia admin would allow this

I changed the issue to a pull request #81


SoTA Results w/ ResNeSt (Updating)

Using this issue to keep track of the state-of-the-art achieved using ResNeSt models:
Instance Segmentation

Method
Backbone
bbox
mask

Cascade R-CNN
ResNeSt-101 (ours)
48.30
41.56

ResNeSt-200 (tricks ours)
50.54
44.21

ResNeSt-200 (tricks+ms ours)
52.47
46.25

ResNeSt-200DCN (tricks+ms ours)
53.30*
47.10*

All of results are reported on COCO-2017 validation dataset. The values with * demonstrate the mutli-scale testing performance on the test-dev2019.
Panoptic Segmentation

Panoptic Segmentation

Backbone
bbox
mask
PQ

ResNeSt-200
51.00
43.68
47.90

Link to the model
Semantic Segmentation:

ADE20K

Method
Backbone
pixAcc%
mIoU%

Deeplab-V3
ResNeSt-101 (ours)
82.07
46.91

ResNeSt-200 (ours)
82.45
48.36

ResNeSt-269 (ours)
82.62
47.60

Link to the model
Pascal Context

Method
Backbone
pixAcc%
mIoU%

Deeplab-V3
ResNeSt-101 (ours)
81.91
56.49

ResNeSt-200 (ours)
82.50
58.37

ResNeSt-269 (ours)
83.06
58.92

Link to the model

Is pre-training trick necessary to train PASCAL Context to soTA level?


Remove Eureka pod if it is only used for validation and not UI

Eureka is useful as a form/screen builder, but we might not be using it for that anymore, and it'll be good to replace it with our own code if we are only using it for rule/validation.
After #3613  is merged

Eureka is currently used in 8 files.

File name
UI
Validation

EnterPasswordViewController.swift
√
√

EthereumAddressRule.swift

√

PrivateKeyRule.swift

√

MnemonicLengthRule.swift

√

MnemonicInWordListRule.swift

√

FormAppearance.swift
√

FloatLabelCell.swift
√

FloatLabelTextField.swift
√

However, these all files appear to be related/supporting EnterPasswordViewController.swift which is only used in two instances in EnterPasswordCoordinator.

Yes, and that seems like a very simple screen, so if you can remove it quite easily, go ahead.

i have implementation for this issue

Remember to negotiate and reassign yourselves

So happy. @oa-s @eviltofu:
$ gd 08e8a7306999c069cec79e0f08336b0908c83e65^ 08e8a7306999c069cec79e0f08336b0908c83e65 | ag "\-import " | sort | uniq

-import Eureka


Roadmap to v0.0.2 release

Description
We want to fix the redis hosting and scale up paper database.
Generally, we want to achieve:

redis hosting with agent / progress / envlog / progress database
scale up the collection of paper DB with tons of new arxived paper data and evaluation

Database Hosting:

[x] #430
[x] #429

Scaling up data collection:

[x] #166

Additional Information
No response

move the real redis support to v0.0.3.


Help Needed with Library Dependencies

Description:
Encountered issues with missing information while working on a project. Errors indicate the absence of essential dependencies, particularly related to modals and responsive font sizing.
Errors:

react-native-modal could not be found within the project or in these directories:
node_modules/toastify-react-native/node_modules
node_modules
react-native-responsive-fontsize could not be found within the project or in these directories:
node_modules/toastify-react-native/node_modules
node_modules

Fix:
I manually added the missing dependencies to make it work. Can we update the docs with clear install steps for these if these dependencies are needed in our project?
Info:

Library Version: 3.1.2
React Native Version: 0.69.2

same here


Failed to fetch http://azure.archive.ubuntu.com/ubuntu/ packages

Description
Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/universe/n/node-core-util-is/node-core-util-is_1.0.2-1_all.deb  503  Service Unavailable [IP: <IP_ADDRESS> 80]
trying to access the package mirror it looks something like:

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[X] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
 Image: ubuntu-20.04
  Version: 20230507.1
  Included Software: https://github.com/actions/runner-images/blob/ubuntu20/20230507.1/images/linux/Ubuntu2004-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu20%2F20230507.1

Is it regression?
yes
Expected behavior
packages can be downloaded
Actual behavior
packages could be installed
Repro steps
In a step run:

sudo apt-get update
install some packages sudo apt-get install build-essential libgtk-3-dev libwebkit2gtk-4.0-dev npm pkg-config libfuse-dev upx -y

now it seems it works

Hello @blankdots,
I have successfully completed commands from repro steps on ubuntu-20.04 runner, and since you confirmed as well, closing the issue.


feat: Export OnUrlUpdateFunction type for Vitest v2

Add docs for both v1 & v2, using Fumadocs's code tab directives.
Closes #706.

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

npm package (@latest dist-tag)
GitHub release


always link libm to libast.so and libast_pal.so

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

What's the next step to get this merged?

Let me merge #18 first.

Rebased my branch.

@conda-forge-admin, please rerender


chore: switch to yarn

/CC @AlCalzone

Pull Request Test Coverage Report for Build 814024463

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 17.732%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

config/index.js
0
2
0.0%

Totals

Change from base Build 813912845:
0.0%

Covered Lines:
2031

Relevant Lines:
11749

💛  - Coveralls


Responsive text utilities are missing the !important rule (v4)

When doing something like
I'm always aligned to the left
 the text-left helper class takes precedence, because the responsive utility classes are missing the !important rule (or should be removed from the base classes):
.text-left           { text-align: left !important; }
.text-right          { text-align: right !important; }
.text-center         { text-align: center !important; }
.text-justify        { text-align: justify !important; }
.text-nowrap         { white-space: nowrap !important; }
.text-truncate       { @include text-truncate; }

// Responsive alignment

@each $breakpoint in map-keys($grid-breakpoints) {
  @include media-breakpoint-up($breakpoint) {
    .text-#{$breakpoint}-left   { text-align: left; }
    .text-#{$breakpoint}-right  { text-align: right; }
    .text-#{$breakpoint}-center { text-align: center; }
  }
}

Fixed by #18314.

Responsive text-md-right works

^ since #18314
But

Responsive text-md-justify does not exist

Is there a reason responsive justify classes appear to have been left out?


Frontend UI agnostic abstraction

Is it possible to abstract the frontend so it can either be implemented by React or native JavaScript UI, or even a W3C WebComponent based solution. As Angular is alien to me, seems to be going out of fashion and an extra set of NPM dependencies that I would rather not have.
Otherwise, good work and very useful though !

@AaronNGray Thanks. Happy to know that this package is useful to you!
Framework agnostic web component based implementation seems interesting. But

Angular is not going out of fashion and is in active development and with cool features being added every release and an ever expanding ecosystem.
May i know what is the use case you are trying to solve? Do you want to integrate or use the UI non Nodejs backend?
Do you want any new feature added to the current UI?

PS: I used angular as i am not familiar with any other framework as much and plain js is way too much work 😁

Closing as no reply or activity.


Plugin load error

nvim --version: 0.5.0
nvim-lsp version(commit hash): b77a24f6b6bdf32d621f37c733f399f33a7eab0d
:checkhealth result:

function health#check[21]..health#nvim_lsp#check, line 2
    Vim(lua):E5108: Error executing lua ...me/.config/nvim/plugged/nvim-lsp/lua/nvim_lsp/health.lua:3: loop or previous error loading module 'nvim_lsp/configs'

Every time I open NeoVim:
Error detected while processing /Users/nomasprime/.config/nvim/init.vim:
line  309:
E5108: Error executing lua ...rime/.config/nvim/plugged/nvim-lsp/lua/nvim_lsp/util.lua:13: attempt to call field 'empty_dict' (a nil value)
Error detected while processing /Users/nomasprime/.config/nvim/plugged/nvim-lsp/plugin/nvim_lsp.vim:
line   14:
E5108: Error executing lua [string ":lua"]:7: loop or previous error loading module 'nvim_lsp'

Config:
Plug 'neovim/nvim-lsp'

lua << END
  require'nvim_lsp'.solargraph.setup{}
END

Even installing the plugin with Plug I get:
Error detected while processing /Users/nomasprime/.config/nvim/plugged/nvim-lsp/plugin/nvim_lsp.vim:
line   14:
E5108: Error executing lua [string ":lua"]:7: loop or previous error loading module 'nvim_lsp'

FFS! Hours wasted because Homebrew wasn't actually updating NeoVim to the latest commit.
Anyway, working now.

I am getting this error on mac os I have nvim 0.6.1 can anyone please help?

Same here. MacOS + nvim 0.6.1.

You should reproduce with the minimal config.

I fixed it, somehow. The thing was that at first I organized files to lua folders and probably something in this way of loading .lua files was wrong. I put everything into one single file (vim options + plugins loading) and suddenly no error was shown upon startup. So I started to divide these into separate files again and everything was ok.
I might load something before some dependency and that might cause the issue. Fixed on my end.


[FLINK-14230][task] Change the endInput call of the downstream operator to after the upstream operator closes

What is the purpose of the change
This pull request fixes the error of propagating endInput on the chain immediately after the input of the head operator is finished, and reverts the changes of PR#9298 and PR#9221.
Correctly, endInput of the downstream operator should be invoked only after closing the upstream operator.
Brief change log

Changes the endInput call of the downstream operator to after the upstream operator closes
Removes the BoundedOneInput implementation of AsyncWaitOperator and ContinuousFileReaderOperator

Verifying this change
This change modified some existing tests to verify the following:

SourceStreamTask: When the downstream operator on the chain executes the logic of endInput, it should have received all the records that the upstream operator outputs before and within close.
OneInputStreamTask: When the downstream operator on the chain executes the logic of endInput, it should have received all the records that the upstream operator outputs before and within close.
TwoInputStreamTask: When the downstream operator on the chain executes the logic of endInput, it should have received all the records that the upstream operator outputs before and within close.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Can you help me review this PR? Thanks. @pnowojski

If this PR is reverting #9221, perhaps it should revert this line too? https://github.com/apache/flink/pull/9221/files#diff-4ad14817e962f9d344a4f6004846c28eR202
It doesn't seem like there's any reason that the file reader should have to close its own output instead of letting the runtime take care of it.

Thank you for the review. I think you are right. But the call to X was not introduced by Y, you can see the line (). Maybe we can add a hotfix commit in this PR to remove this line, or we should create another PR to do this. What's your opinion?

Thank you for the review @bremac .

It doesn't seem like there's any reason that the file reader should have to close its own output instead of letting the runtime take care of it.

I think you are right. But the call to output.close() in close() was not introduced by PR#9221, you can check the L219 line. @bremac
Maybe we can add a hotfix commit in this PR to remove that line, or we should create another PR to do this. What's your opinion? @pnowojski

You're right. My apologies @sunhaibotb . Probably better not to remove that line in this PR then.

Thank you for the review @zhijiangW . I have updated the code of this PR.

I've addressed the lastest comments and added a detailed description to the commit messages. Thanks @zhijiangW.


Whether to consider supporting pv power generation in mountainous scenarios? The mountainous terrain can be an irregular triangular network or elevation point data.

Whether to consider supporting pv power generation in mountainous scenarios?
The mountainous terrain can be an irregular triangular network(TIN) or elevation point data.

Here is an example of modeling the effect of far-away mountains blocking the sun as it approaches the horizon: https://pvlib-python.readthedocs.io/en/stable/gallery/shading/plot_simple_irradiance_adjustment_for_horizon_shading.html
The effect of different module orientations due to terrain variation within the array could be modeled with pvlib, but the effect of row-to-row shading within the array cannot.
Supporting terrain meshes or DEMs might be outside the scope of pvlib, but it could be a separate project that interoperates with pvlib.  But it's not a small undertaking, and someone would have to have the time and motivation to do it.

@kandersolar do you think that this would warrant a function in pvlib?

this would warrant a function in pvlib?

What would the function do?


Allow opting out of caching

Seems a little inefficient to be checking the cache if we know that we aren't using it. So I provided a way to opt out completely using "no-store".

Thanks!


Login with google, token is null.

When I login with Google+
the token is always null
using version 1.2.1

Same Here. Getting token null while other values are fine

The last version has the token information now.


Use redis-py has error

I used pip install -r requirements.txt to install python packages, the default redis-py is 3.0.1.
when i start python redis_monitor.py, some error happened
2019-01-31 13:17:39.020112
Traceback (most recent call last):
  File "redis_monitor.py", line 88, in run
    self.LogInfo(redis_info, current_time, self.last)
  File "redis_monitor.py", line 185, in LogInfo
    expired, evicted, hit_rate, commands, used_memory, peak_memory)
  File "/usr/local/redis-monitor/src/dataprovider/redisprovider.py", line 33, in save_keys_Info
    self.conn.zadd(server +':'+ rediskey, score, data)
  File "/usr/lib/python2.7/site-packages/redis/client.py", line 2263, in zadd
    for pair in iteritems(mapping):
  File "/usr/lib/python2.7/site-packages/redis/_compat.py", line 94, in iteritems
    return x.iteritems()
AttributeError: 'int' object has no attribute 'iteritems'

then I found redis-py 3.xx had some changes https://github.com/andymccurdy/redis-py#mset-msetnx-and-zadd
def mset(self, mapping):
def msetnx(self, mapping):
def zadd(self, name, mapping, nx=False, xx=False, ch=False, incr=False):

so, we need do some compatible or prompt user to install redis-py 2.x version?

you can try one of the following

fix requirements.txt with special version  redis-py 2.x
replace  zadd(key, field, val) -> zadd(key, {field:val}) in redisprovider.py

PR welcome

pip install -r requirements.txt
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Looking in indexes: http://mirrors.cloud.aliyuncs.com/pypi/simple/
Collecting python-dateutil
Downloading http://mirrors.cloud.aliyuncs.com/pypi/packages/d4/70/d60450c3dd48ef87586924207ae8907090de0b306af2bce5d134d78615cb/python_dateutil-2.8.1-py2.py3-none-any.whl (227 kB)
|████████████████████████████████| 227 kB 21.6 MB/s
Collecting redis
Downloading http://mirrors.cloud.aliyuncs.com/pypi/packages/f0/05/1fc7feedc19c123e7a95cfc9e7892eb6cdd2e5df4e9e8af6384349c1cc3d/redis-3.4.1-py2.py3-none-any.whl (71 kB)
|████████████████████████████████| 71 kB 42.2 MB/s
Collecting tornado
Downloading http://mirrors.cloud.aliyuncs.com/pypi/packages/e6/78/6e7b5af12c12bdf38ca9bfe863fcaf53dc10430a312d0324e76c1e5ca426/tornado-5.1.1.tar.gz (516 kB)
|████████████████████████████████| 516 kB 32.5 MB/s
ERROR: Command errored out with exit status 1:
command: /usr/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-zaKVA7/tornado/setup.py'"'"'; file='"'"'/tmp/pip-install-zaKVA7/tornado/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-install-zaKVA7/tornado/pip-egg-info
cwd: /tmp/pip-install-zaKVA7/tornado/
Complete output (17 lines):
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-zaKVA7/tornado/setup.py", line 195, in
**kwargs
File "/usr/lib64/python2.7/distutils/core.py", line 112, in setup
_setup_distribution = dist = klass(attrs)
File "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 269, in init
_Distribution.init(self,attrs)
File "/usr/lib64/python2.7/distutils/dist.py", line 287, in init
self.finalize_options()
File "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 302, in finalize_options
ep.load()(self, ep.name, value)
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 2341, in load
return self.resolve()
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 2351, in resolve
raise ImportError(str(exc))
ImportError: 'module' object has no attribute 'check_specifier'
----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.


react native compile fail in macOS Sierra 10.12

Hey there and thank you for using React Native!
React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.
Do the checklist before filing an issue:

[ ] Is this something you can debug and fix? Send a pull request! Bug fixes and documentation fixes are welcome.
[ ] Have a usage question? Ask your question on StackOverflow. We use StackOverflow for usage question and GitHub for bugs.
[ ] Have an idea for a feature? Post the feature request on Product Pains. It has a voting system to surface the important issues. GitHub issues should only be used for bugs.

None of the above, create a bug report
Make sure to add all the information needed to understand the bug so that someone can help. If the info is missing we'll add the 'Needs more information' label and close the issue until there is enough information.

[ ] Provide a minimal code snippet / rnplay example that reproduces the bug.
[ ] Provide screenshots where appropriate
[ ] What's the version of React Native you're using?
[ ] Does this occur on iOS, Android or both?
[ ] Are you using Mac, Linux or Windows?

when i open my old project compile it and I got fail in RCTWebSocket after that:
/Users/HuminiOS/Desktop/workproject/jpush-react-plugin/node_modules/react-native/Libraries/WebSocket/RCTSRWebSocket.m:459:3: Ignoring return value of function declared with warn_unused_result attribute
/Users/HuminiOS/Desktop/workproject/jpush-react-plugin/node_modules/react-native/Libraries/WebSocket/RCTSRWebSocket.m:1301:5: Ignoring return value of function declared with warn_unused_result attribute

fixed on RN33
or follow this comment - https://github.com/facebook/react-native/issues/8584#issuecomment-236366222

@facebook-github-bot label Icebox

@facebook-github-bot close

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/react-native-compile-fail-in-macos-sierra-1012
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.


YOUR URL to   keyboard-shortcuts   = 404

This page cannot be reached
http://jsbin.com/help/keyboard-shortcuts

Yeah, it's an intermittent fault. Keep refreshing.

Thanks. I worked my way around this intermittent fault  (missing search
bar)  by clicking into the html area . At least that brings up the
browsers own search-bar.  If inside the code-area that comes up neither.
I actually hoped for a jsbin-internat search feature. Shortkeys seem
non-responsive though.  You can leave this ticket closed. Thanks again!

Stefan Brück * Krausestrasse 22  * 22305 Hamburg * 0170/ 38 37 0 17
Am 28.05.2015 19:59 schrieb Remy Sharp:

Yeah, it's an intermittent fault. Keep refreshing.
--
Reply to this email directly or view it on GitHub [1].

Links:
[1] https://github.com/jsbin/jsbin/issues/2392#issuecomment-106532716


feat(cleanUp): add clean up function

Readd the PR #246

[!Note]
We can't use the onunload function because Obsidian doesn't trigger it on close or reload.

I added the clean-up when using the other function (onClick file-menu).
I also edited the removeFolderIcon:

Don't need to save the data with inheritance if the root folder is deleted! Because, well, all file in it will be also deleted/the path will be moved :')
Also remove the inheritance icon from pack if it wasn't used too! Before, only the iconName was checked and it's lead an error for inheritance if they are no icon. I also added a check for that.

Don't think it's needed anymore as inheritance doesn't exists.
Also, discussion on the forum about updating bookmarks.json leads me to think it's not a good idea to clean this file, as Obsidian can't know if a file is really deleted or just wainting for sync, at the moment.
Maybe in the future, we can get a function that know if sync is terminated and allow to clean the files.

Don't think it's needed anymore as inheritance doesn't exists. Also, discussion on the forum about updating bookmarks.json leads me to think it's not a good idea to clean this file, as Obsidian can't know if a file is really deleted or just wainting for sync, at the moment.
Maybe in the future, we can get a function that know if sync is terminated and allow to clean the files.

Agree, thanks for the effort though!


Back out "Back out "[velox][PR] Support multiple HDFS endpoints""

Summary:
This is a re-submission of the PR #4552 by @PHILO-HE that ended up being reverted while importing to Meta's repo. Please refer to the original PR for more context.
Original commit changeset: 79e168d342bc
Original Phabricator Diff: D45678607
Differential Revision: D45747383

@pedroerp, you mentioned the API change here breaks the internal build. Do I need to do some change to avoid the issue?

@pedroerp, you mentioned the API change here breaks the internal build. Do I need to do some change to avoid the issue?

No worries, it was just one callsite I had to change. All good.


Run from Fragment

Description of the problem:
Hi there
At first I called this from my fragment and it worked perfectly:
IntentIntegrator.forSupportFragment(this).initiateScan();
Now I want to customize it like:
   IntentIntegrator integrator = new IntentIntegrator(getActivity());
    integrator.setDesiredBarcodeFormats(IntentIntegrator.ALL_CODE_TYPES);
    integrator.setPrompt("Scan Barcode");
    integrator.setCameraId(0);
    integrator.setBeepEnabled(false);
    integrator.setBarcodeImageEnabled(false);
    integrator.initiateScan();

How can I configure the integrator and then call it from my fragment instead of activity?
Thank you very much
Which library version are you using? E.g. 3.2.0.
Which phone/tablet are you using, and which Android version does it run? (e.g. Samsung Galaxy S5,
Android 5.0)
Does the same happen on other devices or an emulator?
Can you reproduce the issue in the sample project included with the library? If not, can you
provide your own sample project or sample code that produces this error?
In the case of an error do you have a stack trace or adb logs?

Just start with IntentIntegrator integrator = IntentIntegrator.forSupportFragment(this), then continue with the configuration as you had it.

can see：https://blog.csdn.net/ggy2l/article/details/78656635?locationNum=9&fps=1


Unicode not displaying in most fonts

Suddenly today Atom doesn't seem capable of displaying unicode in most fonts. I've tried a bunch of font families (droid, consolata, inconsolata, monospace, courier, sans-serif, arial, impact, ubuntu, ubuntu mono, etc) and the apparently only one who works is sans:

But in monospace:

And I don't have any problem of seeing unicode in other applications, just Atom.
Might help:

lucas ~> apm -v
apm  0.157.0
npm  2.5.1
node 0.10.35
python 2.7.6
git 1.9.1
lucas ~> uname -a
Linux magno-Z97-D3H 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Closing as a duplicate of #6214, please subscribe there for updates.


Release v1.2.0

[x] Create a branch for the release. release-v1.2.0
[x] Update the dependencies. The dependabot PR backlog is not comprehensive and doesn't include transitive dependencies, and merging them one at a time tends to break things, so the best way to do this is manually with npm. Done in #281
[x] Do a test build of the NPM package on your local machine so you know if something is going off the rails before the automated build action on GitHub. Done as part of #281
[x] Bump the "version" number in package.json and reinstall the dependencies so the correct version number is in package-lock.json. Done in commit 637e1dea2b8cabdd5820e5f91fa9a9512749ef8a
[x] Open a PR that merges the release branch into main. See #282
[x] Merge the release PR after it passes testing and review.
[x] Tag a corresponding release on GitHub. This will trigger an automated NPM package build on GitHub. If the package build succeeds it will be automatically published to NPM.

v1.2.0 successfully released!


Docker pull is failing on a fresh Ubuntu 14.04 on aws with

Output of docker version:
(paste your output here)

Output of docker info:
(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):

Sorry pushed enter and created issue. Apologies.


Python improvements in utils/80+-check

What's in this pull request?

The original version had an off-by-one error in the line number
(assuming you use the GitHub model of starting lines at 1).  Fix this
error, and move to using enumerate() instead of tracking the
count variable ourselves.
Add a comment about the exit codes to the help message.
Increase clarity in variable/argument names.

Resolved bug number: (SR-)
This isn’t resolving any bugs in the Swift bug tracker (or at least, not intentionally so).

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please Python lint

@alexwlchan Thanks!  Could you take a look at lint issues?

@gribozavr Lint issues should be fixed.

@swift-ci Please Python lint


Privileges not removed after timeout

I use version 1.5.3 (installed with autopkg), on macos 12.5, and deployed several settings with JAMF(authentification, reason, and timeout)
the timeout isn't working, after the delay, I'm still being admin, verified with Privileges --status

@moobyfr how did you invoke the timeout? (just making sure you know that the timeout only applies if you right-click and select "toggle privileges"...)

Please see the Privileges FAQ, as this topic is covered:
By default, is there a time limit on the admin rights granted by Privileges?
No. Admin rights are granted until some process (like running Privileges again) takes them away.
Can I set Privileges to give me administrator rights for a defined amount of time?
Yes. You can use the Toggle Privileges option on the dock icon to get admin rights for a set amount of time (the default amount is 20 minutes.)

For more information, please see this blog post:
https://derflounder.wordpress.com/2022/07/22/privileges-app-and-time-limited-admin

i have the same issue, installed previous version, but still the same. also macOS 12.5

As rtrouton's comment, removal of access is not part of the program. The blog entry is much better than the FAQ, I'll propose a FAQ update on this point, but I'm in vacation for the time being

yes but it is also strange without a config profile. The color of the icon is not changing as expected. but sure, I will check the blog.

I have come across `install_privileges_checker.zsh by @kandji-inc which is available here.
Deployed as-is, it makes use of DockToggleTimeout to enforce a switch back to Standard privileges after a set period of time. My experience is that it can simply be run as a script, following installation of Privileges.app.

@peterlewis this script is more efficient than the Kandji one, because instead of running a script every 30 seconds, the LaunchDaemon actually monitors for changes to the admins file and only runs the script when there's a change: https://github.com/eth-its/autopkg-mac-recipes-yaml/blob/main/Scripts_for_Installers/Privileges-postinstall.sh

@grahampugh Nice! Thanks for that, Graham, I like it! :) Only in the testing stages at the moment, so can easily change course, but what I do like about the script by @kandji-inc is the ability to use the timeout from the Configuration Profile as it makes trivial changing the value when/where it is required to do so.

I believe that if the ToggleTimeout is set that should be the default behavior whether you hit toggle or run the app. or at least have the option to configure it that way. I always want the admin rights to expire and never want a user to blanket to have them. I rather than have to use the app more often or request permanent admin rights.


ENH: Theme variables

Added theme variables as specified in https://github.com/QuantEcon/sphinxcontrib-jupyter/pull/233

[ ] merge once sphinxcontrib-jupyter=0.4.1 is released on PyPI.

juyter_template_coverage_file_path

@mmcky I think the reason we made this was to make the conf file minimal and shift as much build specific variables to command line as we can. But we can reiterate on this.

yeah I think that is the right call. Thanks @AakashGfude


RHBPMS-4618 - Human task subject not returned in REST API response

jenkins retest this

jenkins retest this


Train 153

https://github.com/dcos/dcos/pull/1246
https://github.com/dcos/dcos/pull/1437
https://github.com/dcos/dcos/pull/1442

@mesosphere-mergebot bump-ee

@lingmann @spahl This is ready to :ship:


JsonProperty.MemberConverter and JsonProperty.Converter documentation

I can't find any explanation of the difference between JsonProperty.MemberConverter and JsonProperty.Converter and when to set which. Could the documentation be elaborated?

It seems MemberConverter is just used in InternalReader for overriding propertyContract behavior. So it does not seem to be overly useful.
I haven't found a reference to where JsonProperty.Converter is being used. maybe it is a user accessible pass through variable for a parent type Converter to use.
Example:
So say in a JsonContract, the properties of this parent type X have converter Y, and my (X) converter is Z.
In converter Z you would presumably be able to get to the state of the JsonProperties of parent type X and be able to read that their converter is Y.
I find the relation between these contracts and converters really unintuitive and sometimes inhibitive to get the behavior I like. But it's what it is.

MemberConverter is now obsolete https://github.com/JamesNK/Newtonsoft.Json/commit/bbbddf0031fdced348b08d2435eb2d4698f50ef3


Support loading setting from clickhouse config file and improve logging

(you don't have to strictly follow this form)

Use case

A clear and concise description of what is the intended usage scenario is.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

https://github.com/Kyligence/ClickHouse/pull/118  close it


Pin blockly to version 8.0.0

I think something changed about the internals of blockly, and I was getting errors about selectedOption_ not existing from the line let type = block.inputList[0]?.fieldRow?.[3]?.selectedOption_[0];.
I went back to a version about the time this repo was last updated.

@bradjc Thanks for figuring this out! Are there any other bugs you noticed? I haven't been actively testing this over time with new versions of Blockly, so I'm happy to pin it to the working version for now.

That's the only one I encountered.


Kernel Error:: Node count exceeded maximum nodes per window

Observed this error on my stderr while running racon-gpu, not sure if related to #45? It's raised by the code here.

This limit seems to be a predefined constant. I guess the size of the graph we have is just a bit big! I could increase this threshold myself, but don't know what the ramifications of that might be.

Ah, I see this is actually an error that you've also referenced in #46!

Having tested #46, it seems the conditions are related.

@SamStudio8 forgot to mention that the fix for this was merged to master for both ClaraGenomicsAnalysis and racon. Can we close this issue if it works for you?

Yes I think we can close this!


[ROCKETMQ-106] Add flow control on topic level

https://issues.apache.org/jira/browse/ROCKETMQ-106

Great point, could you please add some unit tests?

Coverage increased (+0.05%) to 31.566% when pulling 112e36cece57dea4c6f64eec8b2d5dbb46385bee on Jaskey:ROCKETMQ-106-topic-flow-control into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

Coverage increased (+0.05%) to 31.566% when pulling 112e36cece57dea4c6f64eec8b2d5dbb46385bee on Jaskey:ROCKETMQ-106-topic-flow-control into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

Coverage increased (+0.05%) to 31.566% when pulling 112e36cece57dea4c6f64eec8b2d5dbb46385bee on Jaskey:ROCKETMQ-106-topic-flow-control into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

LGTM, but please add some unit tests at your convenience.
Please @vongosling @lizhanhui help review.

@zhouxinyu
unit test has been added.
@vongosling @lizhanhui  please help review the pr, thanks!

Not everyone needs this feature, I suggest to set this feature as disabled on default. Enable it only when application user manually set pullThresholdForTopic >= pullThresholdForQueue.

Coverage increased (+0.5%) to 32.021% when pulling 70de21da93b01f81680c1b8c420cc0dc111cf319 on Jaskey:ROCKETMQ-106-topic-flow-control into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

Coverage increased (+0.5%) to 32.021% when pulling 70de21da93b01f81680c1b8c420cc0dc111cf319 on Jaskey:ROCKETMQ-106-topic-flow-control into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

Coverage increased (+0.5%) to 32.021% when pulling 70de21da93b01f81680c1b8c420cc0dc111cf319 on Jaskey:ROCKETMQ-106-topic-flow-control into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

@lizhanhui
If we really need that. We can set the defaultValue to Long.MAX_VALUE.
But I think as long as we set a apporiate value, flow control should be needed to protect local heap memory.

@zhouxinyu @lizhanhui
what about i new a config call flowControlTreadholds and a boolean config flowControlForTopic =false(default).
If they set flowControlForTopic  = true, then control on topic, or remains the same logic.
But we need to deprecated the old config pullThresholdForQueue

Hi, @Jaskey

what about we provide a new a config call flowControlTreadholds and a boolean config flowControlForTopic (false by default).

I think this is a good idea.

But we need to deprecated the old config pullThresholdForQueue since the naming is specified already only for queue

Can we maintain semantics of the original config and name this specific config something like flowControlThresholdByTopic?

@lizhanhui

Can we maintain semantics of the original config and name this specific config something like flowControlThresholdByTopic?

This already done in my current pr.
What I suggest is one of the following:

Separate two config in two config field , pullThresholdForQueue  and pullThresholdForTopic, they both take effect.
2.Separate two config in a boolean config, by default , it is control on queue level.

Introduce one more boolean config and a topic level config is not clean enough since user must under stand the inner logic and we will find it hard to not easy to make them understood.

What I intend to deliver is that it's always good to have simple API, but it would be miserably unexpected to change semantics of a configuration quietly. Further, it's best not to introduce overhead for the features application developers may not need. This is why I suggest to introduce a boolean switch to short circuit it on default at the very beginning.

@lizhanhui for your second point, we just disable the topic level flow control by default will do the trick.
 pullThresholdForTopic  = Integer.MAX_VALUE;

max value will be considered as disable, so no need to introduce a redundant config, which makes api harder to understand.

Coverage decreased (-0.03%) to 31.492% when pulling 1d84be8b2807bb0274b5fd02db9d813c5c364f87 on Jaskey:ROCKETMQ-106-topic-flow-control into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

Coverage decreased (-0.03%) to 31.492% when pulling 1d84be8b2807bb0274b5fd02db9d813c5c364f87 on Jaskey:ROCKETMQ-106-topic-flow-control into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

All right. +1 now.

@vongosling @zhouxinyu @shroman what's your advice guys?

@vongosling @shroman any idea on this PR?

@dongeforever @lizhanhui @zhouxinyu
Some users in the QQ group has been asked for this feature, would you please help review and merge this pr?

+1 LGTM

+1, @dongeforever we'd merge this PR after conflicts are resolved as we have collected enough positive votes.

@Jaskey Hi, I want to merge this PR, could you plz help us resolve the conflicts?

yukon<EMAIL_ADDRESS>周一22:16写道：

@Jaskey https://github.com/jaskey Hi, I want to merge this PR, could
you plz help us resolve the conflicts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-rocketmq/pull/66#issuecomment-317436313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIhjY7HDDchyxHnC_z93aFE3hzZp7u-Tks5sRKctgaJpZM4MDzt8
.

That's sure ,my pleasure.tell me the branch

@Jaskey I found that user may be confused about how to set the right value for both pullThresholdForQueue and pullThresholdForTopic, Queue is a interval concept actually, user only knows Topic and have no idea about queue nums in most cases. So how about only open pullThresholdForTopic for client and calculate
pullThresholdForQueue value by queue nums dynamically?

@zhouxinyu  I totally agree with you! While the old design exposes the pullThresholdForQueue  for user to get and set, what about we deprecated the setter and we remove them in the next release?  @lizhanhui @shroman @vongosling what's your advice

Coverage decreased (-0.1%) to 38.978% when pulling 9aa5b3bae1e53ab6bb42e0787f6541de14b2f65b on Jaskey:ROCKETMQ-106-topic-flow-control into d4149207e27ed3516f1f06407b55986790b806ae on apache:master.

Coverage decreased (-0.1%) to 38.978% when pulling 9aa5b3bae1e53ab6bb42e0787f6541de14b2f65b on Jaskey:ROCKETMQ-106-topic-flow-control into d4149207e27ed3516f1f06407b55986790b806ae on apache:master.

Coverage decreased (-0.1%) to 38.978% when pulling 9aa5b3bae1e53ab6bb42e0787f6541de14b2f65b on Jaskey:ROCKETMQ-106-topic-flow-control into d4149207e27ed3516f1f06407b55986790b806ae on apache:master.

@Jaskey Another PR 171 submitted by @zhouxinyu does the same thing, and it considers both msgSize and msgCount, which may make it a better solution.


Provide Load and Resource Allocation Mapping

The load to resource information is important for below events:

The related resource assignment is based on resource assigned to the corresponding parent load. For example, a ferry is assigned to a particular berth. The corresponding berth gate should be assigned to the related passengers.
The next activity resource assignment is based on existing resource assigned.
Without that information provided by RCQsContext, the sophisticated simulation model could NOT be built.

The issue was addressed in new release in master branch


'getActivePinia()" was called but there was no active Pinia' is back

Environment

Operating System: Linux
Node Version:     v18.20.2
Nuxt Version:     3.10.3
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules, piniaPersistedstate, watch
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://gitlab.com/javier-sedano/ufe5
However, I have applied the workaround defined in https://github.com/nuxt/nuxt/issues/22943#issuecomment-1702506306 so in order to reproduce it again, comment out some lines:
The architecture is a bit complex (it is a microfrontend poc) so use:
yarn install
yarn initAll
edit app-core/node_modules/javier-sedano-ufe5-store-library-pinia/src/stores/total.store.ts and comment out the workaround from lines 7-8.
yarn dev
browse localhost:4100
WARNING: upon reload, it does not fail anymore, it only fails in the first load after a fresh start.
Describe the bug
The console complains with:
Looks like the bug was detected in Nuxt 3.7.0 and fixed in 3.7.something. It has appeared again, I think. I have verified that it works with Nuxt 3.10.2 and fails with Nuxt 3.10.3 (edit app-core/package.json to check this).
Additional context
MateuszStawski says in https://github.com/nuxt/nuxt/issues/22943#issuecomment-2119360501 that it fails for him as well.
Logs
No response

@jsedanoj Have you tried upgrading to the latest version of Nuxt 3 (3.11.2)? If the error continues, you can raise a hand, else you can close this issue

✋
Yes. Actually, I detected it in 3.11.2, but I downgraded until I found the version that caused the problem. The repo in the report is using 3.11.2, indeed.

@jsedanoj  I recall that from Pinia's documentation regarding something like context.
Check this issue: https://github.com/vuejs/pinia/discussions/971

Would you be able to provide a minimal reproduction? 🙏

@jsedanoj I recall from Pinia's documentation something regarding something like context. Check this issue: vuejs/pinia#971

Well... it MAY be something like this... but it is working with Nuxt 10.0.2 and fails with 10.0.3 and above, so my initial suspect was Nuxt. One of the microfrontends of the POC use Nuxt 3.7.4 and it works there, as well... so initially, I do not think we should suspect Pinia (unless the change from 10.0.2 to 10.0.3 makes a bug in Pinia afloat).

Would you be able to provide a minimal reproduction? 🙏

I have it reproduced in the repo linked in the report... but I guess it is a bit complex. So sure, I can try to simplify it, allow me some days.

Sorry, but I cannot simplify the error. When I create a simple Nuxt project, it works.
What can offer is helping anybody to clone and run my example (described in the report). It is dockerized, so running it on top or Rancher Desktop is fairly easy. Can we appoint a meeting?
I have double checked again, and it fails systematically with Nuxt 3.11.2 and 3.10.3; but works with 3.10.2.

This is unlikely to be an issue with Nuxt (probably related to either pinia or your project). I'm closing it as the reproduction isn't minimal enough to narrow it down. If you can reproduce more minimally, let me know and I'll happily dive in 🙏


Feature: please add a "status" field to response object which confirms to PEP 0333

According to this:
https://www.python.org/dev/peps/pep-0333/#the-start-response-callable
The response object must contain a status field with string values such as "200 OK" or "403 Forbidden" and so forth.  If one is developing a Python WSGI compliant API then any framework used (such as falcon) is going to require a status field is set correctly.
I am deploying a python app behind WSGI (falcon) and I use the requests module to perform requests on behalf of the API consumer (it's a special use case to sign requests going to Amazon Elasticsearch using signature 4 that I did not want to try to write in JavaScript) and as a result I have to take the response object from requests and take values contained within to construct a WSGI compliant response.
Currently I have to concatenate the status_code and reason fields from the requests response object to in order to construct a PEP 0333 complaint response status.  A field added to the requests response object would save this extra step.
This is a "nice to have", not a serious priority.

Thanks for this request @eric-tucker!
Unfortunately, Requests is in feature-freeze for the foreseeable future, which means that we're generally not implementing new features unless they represent a really compelling loss of function. Given that all the information you require is present, and that a helper function to build this information is exactly one line long, I'm afraid I don't think this feature is a priority for us at this time.
Sorry we can't be more help!

I understand, but can you elaborate on why you're in a "feature-freeze"?
Is the product no longer actively developed?

Well, our documentation talks about this a little bit, but allow me to elaborate.
Requests is not a project that aims to have every feature that a user can imagine. From our perspective, tools like curl are better suited to that. The reason we don't want to add lots of features is because each feature added complicates the API, and our API is sacred to us. It is the foundation on which Requests is built, and our overwhelming primary concern.
Requests is still actively developed: we will fix bugs as soon as they're reported, and add any glaring feature omissions if they're pointed out to us. But, fundamentally, we believe that Requests already covers 80% of what people need from it.
Generally speaking, then, we start at a -1 on any feature request. If the feature is both simple to implement outside of requests (like this one), required by relatively few users (also like this one), and has few-or-no pitfalls for unsuspecting users (also like this one), then our overwhelming inclination is to leave that feature out. Features represent an ongoing maintenance burden to the maintainers and a complexity cost to users, who need to navigate a maze of documentation of features they don't care about to find the few that they do. That's just not how we do things here.
For perspective, our feature freeze has been in place since v1.0.0 was released. Clearly, that has not stopped development of Requests. Don't worry, we're still here still supporting new Python versions and fixing bugs. We're just not willing to become libcurl for Python.

OK.
As long as I can be guaranteed that this:
response.status = str(return_result.status_code) + " " + return_result.reason

will always give me a PEP 0333 compliant status then I'm fine with things as they are.
Thanks!

That will remain true as long as HTTP/2 is unsupported by Requests.
However, in HTTP/2 there are no reason phrases. If we ever support HTTP/2, then .reason may return the empty string. Just a warning.


Figure out clipping during stitching

Experiencing some strange results when trying to run generate point matches while taking advantage of clipHeight and clipWidth. There are rather noticeable gaps in which tiles are able to find correspondences e.g.

Total mystery at this point.

The issue was that I was changing the attribute of the same instance (firstCanvasPosition of sift_options). Fix was to create new instances.


Agents complaining about context deadline exceeded

Greetings,
I am running k8s 1.9 / romana 2.0.2 (recently upgraded from 2.0.1 as an attempt to fix this issue).
Every romana-agent instance has the following entries in its logs:
Failed to update ipsets, can't apply Romana policies, context deadline exceeded
This is coupled with an inability to setup romana VIPs.
It appears containers still receive IPs appropriately though.

Hi @ebauman can you describe more completely when this happened? When you installed? When you tried to create a Romana VIP? Or add a Network Policy?

Sure thing, sorry for the lack of detail.
This morning I attempted to deploy a service to my new k8s cluster.
I had previously installed k8s 1.9 / romana 2.0.1 a few weeks ago. At that time I did some simple testing with an nginx pod and service and was able to assign a VIP from the subnet that my hosts were on.
Today when I attempted to deploy this service, the service did not receive a VIP from romana.
That's when I dug into the logs on the agent containers and saw the aforementioned entries.

@ebauman can you please paste the annotation use for romanaVIP here?

apiVersion: v1
kind: Service
metadata:
  name: vault
  annotations:
    romanavip: '{"auto": false, "ip": "<IP_ADDRESS>"}'

@ebauman send an email to<EMAIL_ADDRESS>and we can take this to slack, if you want.

Will do! I'll follow-up shortly. Thanks @chrismarino


Demo.html works, but data.json doesn't seem to work

Hi BodyMovin,
I can see my bodymovin work here:
http://rarecutcreative.com/body/demo.html
But if I try and play my data.json file, it doesn't seem to work (see here)
http://codepen.io/celli/pen/aBJgoq
Am I using the correct  .js code to get the JSON file to work ? or is there something wrong with my JSON file ? I've tried some many different options, but none seem to work.

Hi, you're having Cross Origins issues.
You need to setup your server to accept requests from codepen.io domain.
check the chrome console and you will see the error.
here is a link explainig the issue and how to solve it.
http://stackoverflow.com/questions/20035101/no-access-control-allow-origin-header-is-present-on-the-requested-resource

Hi bodymovin, You are absolutely right, thanks! That is solved, but I have another strange problem. You see this doesn't seem to hold the color information http://codepen.io/celli/pen/aBJgoq but the html demo export does here: http://rarecutcreative.com/body/demo.html
What do you think the problem is ?

Your animation is version 4.4.24 and the player is version 4.1.3
the player should always be the same or older than the animation

ahh, perfect. That solves it ! Thanks, Awesome tool !


Tests fail without "." in @INC

Later version of Perl remove "." from @INC which causes a bunch of the tests (t/20_Serializer/20_xs_encode_decode.t) to fail to find files they expect to find.

This was fixed in 519f8917641c2f968460af1c033afb26300d9aae


make no_std a feature

currently no_std is enforced in each crate which makes it hard to debug things

no_std requirement can be removed using the following command
rg '#!\[no_std\]' -l | xargs -i sed -i  's|#!\[no_std\]||' {}

I agree it's a bit annoying to not have easy access to things like dbg!, although the workarounds don't seem too bad in my opinion - temporarily removing no_std, or using panic! or something like tracing::event!.
I see a couple downsides to conditional use of no_std,

If we unconditionally import things like alloc::vec, we get an unused important warning in builds with std; see this issue which mentions some workarounds.
We'd probably want to test both builds in CI, doubling CI costs, or the one we don't test might get broken now and then (it was an issue in PLonky2).

So I think my preference would be avoiding conditional use of no_std for now, although this could change - i.e. (1) might go away if a nice standard solution develops, while (2) might happen anyway if we end up needing conditional std in order to implement certain optional features in the future.