text:
Numeral System

Scripture App Builder allows the end user to select the numeral system to use for displaying numbers at the book collection level. This setting is at Books > {Book Collection} > Styles > Numeral System

The configuration is at:
      <numeral-system value="Default"/>

It can also exist at the book level:

The available numeral systems are:
from source/common/app-lib-common/src/main/java/org/sil/app/lib/common/utils/NumeralSystem.java in the app-builders repo:
public enum NumeralSystem {

    DEFAULT 	("Default"), // 0 1 2 3 4 5 6 7 8 9
    BENGALI 	("Bengali"),
    DEVANAGARI  ("Devanagari"),
    EASTERN_ARABIC  ("Arabic"),
    GUJARARTI  	("Gujararti"),
    GURMUKHI  	("Gurmukhi"),
    KANNADA  	("Kannada"),
    KHMER  		("Khmer"),
    LAO  		("Lao"),
    LIMBU  		("Limbu"),
    MALAYALAM  	("Malayalam"),
    MONGOLIAN  	("Mongolian"),
    MYANMAR  	("Myanmar"),
    NKO  		("N'Ko"),
    ORIYA  		("Oriya"),
    PERSIAN  	("Persian"),
    TAMIL  		("Tamil"),
    TELUGU 		("Telugu"),
    THAI  		("Thai"),
    TIBETAN  	("Tibetan");

Here is the java code from source/common/app-lib-common/src/main/java/org/sil/app/lib/common/utils/NumeralUtils.java in the app-builders repo:
    private static char[] getReplacementsForNumeralsType(NumeralSystem type) {

        // Numerals in different scripts
        // http://www.fileformat.info/info/unicode/category/Nd/list.htm

        //                       0          1         2         3         4         5         6        7          8         9
        char[] arabic  	   = {'\u0660', '\u0661', '\u0662', '\u0663', '\u0664', '\u0665', '\u0666', '\u0667', '\u0668', '\u0669'};
        char[] persian 	   = {'\u06F0', '\u06F1', '\u06F2', '\u06F3', '\u06F4', '\u06F5', '\u06F6', '\u06F7', '\u06F8', '\u06F9'};
        char[] nko   	   = {'\u07C0', '\u07C1', '\u07C2', '\u07C3', '\u07C4', '\u07C5', '\u07C6', '\u07C7', '\u07C8', '\u07C9'};
        char[] thai    	   = {'\u0E50', '\u0E51', '\u0E52', '\u0E53', '\u0E54', '\u0E55', '\u0E56', '\u0E57', '\u0E58', '\u0E59'};
        char[] gujararti   = {'\u0AE6', '\u0AE7', '\u0AE8', '\u0AE9', '\u0AEA', '\u0AEB', '\u0AEC', '\u0AED', '\u0AEE', '\u0AEF'};
        char[] devanagari  = {'\u0966', '\u0967', '\u0968', '\u0969', '\u096A', '\u096B', '\u096C', '\u096D', '\u096E', '\u096F'};
        char[] bengali     = {'\u09E6', '\u09E7', '\u09E8', '\u09E9', '\u09EA', '\u09EB', '\u09EC', '\u09ED', '\u09EE', '\u09EF'};
        char[] gurmukhi    = {'\u0A66', '\u0A67', '\u0A68', '\u0A69', '\u0A6A', '\u0A6B', '\u0A6C', '\u0A6D', '\u0A6E', '\u0A6F'};
        char[] oriya       = {'\u0B66', '\u0B67', '\u0B68', '\u0B69', '\u0B6A', '\u0B6B', '\u0B6C', '\u0B6D', '\u0B6E', '\u0B6F'};
        char[] tamil       = {'\u0BE6', '\u0BE7', '\u0BE8', '\u0BE9', '\u0BEA', '\u0BEB', '\u0BEC', '\u0BED', '\u0BEE', '\u0BEF'};
        char[] telugu      = {'\u0C66', '\u0C67', '\u0C68', '\u0C69', '\u0C6A', '\u0C6B', '\u0C6C', '\u0C6D', '\u0C6E', '\u0C6F'};
        char[] kannada     = {'\u0CE6', '\u0CE7', '\u0CE8', '\u0CE9', '\u0CEA', '\u0CEB', '\u0CEC', '\u0CED', '\u0CEE', '\u0CEF'};
        char[] malayalam   = {'\u0D66', '\u0D67', '\u0D68', '\u0D69', '\u0D6A', '\u0D6B', '\u0D6C', '\u0D6D', '\u0D6E', '\u0D6F'};
        char[] lao    	   = {'\u0ED0', '\u0ED1', '\u0ED2', '\u0ED3', '\u0ED4', '\u0ED5', '\u0ED6', '\u0ED7', '\u0ED8', '\u0ED9'};
        char[] tibetan	   = {'\u0F20', '\u0F21', '\u0F22', '\u0F23', '\u0F24', '\u0F25', '\u0F26', '\u0F27', '\u0F28', '\u0F29'};
        char[] khmer	   = {'\u17E0', '\u17E1', '\u17E2', '\u17E3', '\u17E4', '\u17E5', '\u17E6', '\u17E7', '\u17E8', '\u17E9'};
        char[] myanmar     = {'\u1040', '\u1041', '\u1042', '\u1043', '\u1044', '\u1045', '\u1046', '\u1047', '\u1048', '\u1049'};
        char[] mongolian   = {'\u1810', '\u1811', '\u1812', '\u1813', '\u1814', '\u1815', '\u1816', '\u1817', '\u1818', '\u1819'};
        char[] limbu       = {'\u1946', '\u1947', '\u1948', '\u1949', '\u194A', '\u194B', '\u194C', '\u194D', '\u194E', '\u194F'};

        char[] result = null;

        switch(type) {
            case BENGALI :			result = bengali; 	break;
            case DEVANAGARI :		result = devanagari; break;
            case EASTERN_ARABIC :	result = arabic; 	break;
            case GUJARARTI :		result = gujararti; break;
            case GURMUKHI :			result = gurmukhi; 	break;
            case KANNADA :			result = kannada;	break;
            case KHMER :			result = khmer;		break;
            case LAO :				result = lao;		break;
            case LIMBU :			result = limbu;		break;
            case MALAYALAM :		result = malayalam;	break;
            case MONGOLIAN :		result = mongolian;	break;
            case MYANMAR :			result = myanmar;	break;
            case NKO :				result = nko;	    break;
            case ORIYA :			result = oriya;		break;
            case PERSIAN :			result = persian;	break;
            case TAMIL :			result = tamil;		break;
            case TELUGU :			result = telugu;	break;
            case THAI :				result = thai;		break;
            case TIBETAN :			result = tibetan;	break;

            default :
                break;
        }

        return result;
    }

Here is an example of it being used:

repo: sillsdev/appbuilder-pwa


text:
Fix GetTasksForQueueAsync

Speed up NmtQueue test with parallel corpora
#513

This change is

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 56.95%. Comparing base (e2f1f25) to head (5d57c9f).

Files with missing lines
Patch %
Lines

...c/Serval.Machine.Shared/Services/ClearMLService.cs
0.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #534      +/-   ##
==========================================
- Coverage   56.95%   56.95%   -0.01%
==========================================
  Files         299      299
  Lines       15734    15735       +1
  Branches     2173     2173
==========================================
  Hits         8962     8962
- Misses       6122     6123       +1
  Partials      650      650

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

src/Serval/test/Serval.E2ETests/ServalApiTests.cs line 218 at r1 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
Please use an explict type if the type is specified elsewhere on the line.

Done.

source: gharchive/pull-request

repo: sillsdev/serval

license: MIT

license_type: permissive

license_source: github-api


text:
Batch action button styling

The batch action go button styling is a bit off.
SS 3.5.3
Multisite

Single Site

Turns out this is another module interfering, as it loads full bootstrap CSS into the CMS!!

source: gharchive/issue

license_source: bigquery


text:
FIX Use create syntax for CMSMemberLoginForm remember me form

see #5681 - port to CMSMemberLoginForm
PS: Why is this not in the admin module or cms?

thanks

repo: silverstripe/silverstripe-framework


text:
Remove moot version property from bower.json

Per bower/bower.json-spec@a325da3

:+1: for merge. Also need remove https://github.com/silviomoreto/bootstrap-select/blob/d565eabc633336789d15106b6b63eba111046d12/Gruntfile.js#L180.

repo: silviomoreto/bootstrap-select

license: mit


text:
[bug report]已有值的情况下输入，须重新输入

因为如果一个输入操作是建立在已有值的情况下，这时候输入会从头输入，并且这个组件内的value并没有对外提供set方法，无法修改实际值
[建议]1.提供主动调用清除功能的api
2.提供一个option，可以设置初始值
另外，因为有需求用数字键盘输入金额，因此不能以0开头；本应该是很好实现的需求，例如输入00123，输入完后格式化实际值为123，但是因为不能控制内部value的值，再次点开数字键盘输入，会从之前的00123开始输入

刚刚发现value是可以改的
const keyboard = new DigitalKeyboard()
keyboard.value 的值可以修改，因此以上的问题可以解决

嗯 后续我加个defaultValue API

authors: simbawus yujiaaoyujia

repo: simbawus/digital-keyboard


text:
DriftIsolate.shutdownAll is keeping isolate form exiting

Describe the bug
DriftIsolate.shutdownAll is leaking a ReceivePort, keeping the isolate from exiting when the event loop is empty.
The following program never exits:
import 'dart:io';
import 'dart:isolate';

import 'package:drift/drift.dart';
import 'package:drift/isolate.dart';
import 'package:drift/native.dart';
import 'package:path/path.dart' as p;

Future<void> main() async {
  final tmpDir = await Directory.systemTemp.createTemp();
  final path = p.join(tmpDir.path, 'db.sqlite');

  DriftIsolate? driftIsolate;

  final receivePort = ReceivePort();
  await Isolate.spawn(
    _startBackground,
    _IsolateStartRequest(receivePort.sendPort, path),
  );
  driftIsolate = await receivePort.first as DriftIsolate;

  await driftIsolate.shutdownAll();
}

void _startBackground(_IsolateStartRequest request) {
  final executor = NativeDatabase(File(request.targetPath));
  final driftIsolate = DriftIsolate.inCurrent(
    () => DatabaseConnection.fromExecutor(executor),
    killIsolateWhenDone: true,
  );
  request.sendDriftIsolate.send(driftIsolate);
}

class _IsolateStartRequest {
  final SendPort sendDriftIsolate;
  final String targetPath;

  _IsolateStartRequest(this.sendDriftIsolate, this.targetPath);
}

I think the problem is that a channel is created in _open and never close.
https://github.com/simolus3/drift/blob/7b5c33593748c60831f1f3101a8581ff13b7b50e/drift/lib/isolate.dart#L99-L101

Good catch, thanks! Fixed this in c0ec36eaaa28c1206b26b4be27b1d8d70dd59fdb.


text:
The getter 'definingUnit' was called on null (moor_generator:moor_generator)

When I run flutter packages pub run build_runner build the following error assocaited to the moor_generator:moor_generator occurs and results in a infinity loop where the action never completes:
> flutter packages pub run build_runner build
[INFO] Generating build script...
...
[SEVERE] moor_generator:moor_generator on lib/data/{MY_DAO_FILE}.dart:
NoSuchMethodError: The getter 'definingUnit' was called on null.
Receiver: null
Tried calling: definingUnit
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:51:5)
#1      LinkedElementFactory.isLibraryUri (package:analyzer/src/summary2/linked_element_factory.dart:133:28)
#2      LibraryContext.isLibraryUri (package:analyzer/src/dart/analysis/library_context.dart:97:27)
#3      LibraryAnalyzer._isLibrarySource (package:analyzer/src/dart/analysis/library_analyzer.dart:522:25)
#4      LibraryAnalyzer._resolveDirectives (package:analyzer/src/dart/analysis/library_analyzer.dart:562:36)
#5      LibraryAnalyzer.analyzeSync (package:analyzer/src/dart/analysis/library_analyzer.dart:136:5)
#6      LibraryAnalyzer.analyze (package:analyzer/src/dart/analysis/library_analyzer.dart:107:12)
#7      AnalysisDriver._computeAnalysisResult2.<anonymous closure> (package:analyzer/src/dart/analysis/driver.dart:1317:63)
#8      PerformanceLog.run (package:analyzer/src/dart/analysis/performance_logger.dart:32:15)
#9      AnalysisDriver._computeAnalysisResult2 (package:analyzer/src/dart/analysis/driver.dart:1294:20)
#10     AnalysisDriver._computeAnalysisResult.<anonymous closure> (package:analyzer/src/dart/analysis/driver.dart:1247:14)
#11     _rootRun (dart:async/zone.dart:1190:13)
#12     _CustomZone.run (dart:async/zone.dart:1093:19)
#13     _runZoned (dart:async/zone.dart:1630:10)
#14     runZoned (dart:async/zone.dart:1550:10)
#15     NullSafetyUnderstandingFlag.enableNullSafetyTypes (package:analyzer/dart/element/null_safety_understanding_flag.dart:42:12)
#16     AnalysisDriver._computeAnalysisResult (package:analyzer/src/dart/analysis/driver.dart:1246:40)
#17     AnalysisDriver._computeErrors (package:analyzer/src/dart/analysis/driver.dart:1372:41)
#18     AnalysisDriver.performWork (package:analyzer/src/dart/analysis/driver.dart:979:20)
#19     AnalysisDriverScheduler._run (package:analyzer/src/dart/analysis/driver.dart:2013:24)
<asynchronous suspension>
#20     AnalysisDriverScheduler.start (package:analyzer/src/dart/analysis/driver.dart:1936:5)
#21     analysisDriver (package:build_resolvers/src/analysis_driver.dart:62:13)
#22     AnalyzerResolvers._ensureInitialized.<anonymous closure> (package:build_resolvers/src/resolver.dart:306:26)
<asynchronous suspension>
#23     AnalyzerResolvers._ensureInitialized.<anonymous closure> (package:build_resolvers/src/resolver.dart)
#24     AnalyzerResolvers._ensureInitialized (package:build_resolvers/src/resolver.dart:309:6)
#25     AnalyzerResolvers.get (package:build_resolvers/src/resolver.dart:314:11)
#26     PerformanceTrackingResolvers.get.<anonymous closure> (package:build_runner_core/src/performance_tracking/performance_tracking_resolvers.dart:19:58)
#27     _NoOpBuilderActionTracker.trackStage (package:build_runner_core/src/generate/performance_tracker.dart:302:15)
#28     PerformanceTrackingResolvers.get (package:build_runner_core/src/performance_tracking/performance_tracking_resolvers.dart:19:16)
#29     BuildStepImpl.resolver (package:build/src/builder/build_step_impl.dart:74:54)
#30     _Builder.build (package:source_gen/src/builder.dart:72:32)
#31     MoorSharedPartBuilder.build (package:moor_generator/src/backends/build/moor_builder.dart:89:18)
<asynchronous suspension>
#32     runBuilder.buildForInput (package:build/src/generate/run_builder.dart:55:21)
#33     MappedListIterable.elementAt (dart:_internal/iterable.dart:417:31)
#34     ListIterator.moveNext (dart:_internal/iterable.dart:343:26)
#35     Future.wait (dart:async/future.dart:406:26)
#36     runBuilder.<anonymous closure> (package:build/src/generate/run_builder.dart:61:36)
#37     _rootRun (dart:async/zone.dart:1190:13)
#38     _CustomZone.run (dart:async/zone.dart:1093:19)
#39     _runZoned (dart:async/zone.dart:1630:10)
#40     runZonedGuarded (dart:async/zone.dart:1618:12)
#41     runZoned (dart:async/zone.dart:1547:12)
#42     scopeLogAsync (package:build/src/builder/logging.dart:26:3)
#43     runBuilder (package:build/src/generate/run_builder.dart:61:9)
#44     _SingleBuild._runForInput.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:485:19)
#45     _NoOpBuilderActionTracker.trackStage (package:build_runner_core/src/generate/performance_tracker.dart:302:15)
#46     _SingleBuild._runForInput.<anonymous closure>.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:483:23)
<asynchronous suspension>
#47     _SingleBuild._runForInput.<anonymous closure>.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart)
#48     NoOpTimeTracker.track (package:timing/src/timing.dart:222:44)
#49     _SingleBuild._runForInput.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:440:22)
#50     Pool.withResource (package:pool/pool.dart:127:28)
<asynchronous suspension>
#51     _SingleBuild._runForInput (package:build_runner_core/src/generate/build_impl.dart:436:17)
#52     _SingleBuild._runBuilder.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:374:38)
#53     MappedIterator.moveNext (dart:_internal/iterable.dart:392:20)
#54     Future.wait (dart:async/future.dart:406:26)
#55     _SingleBuild._runBuilder (package:build_runner_core/src/generate/build_impl.dart:373:36)
#56     _SingleBuild._runPhases.<anonymous closure>.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:319:20)
#57     _rootRunUnary (dart:async/zone.dart:1198:47)
#58     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#59     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#60     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#61     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#62     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#63     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
#64     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
#65     _SingleBuild._matchingPrimaryInputs (package:build_runner_core/src/generate/build_impl.dart)
#66     _rootRunUnary (dart:async/zone.dart:1198:47)
#67     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#68     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#69     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#70     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#71     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#72     Future.wait.<anonymous closure> (dart:async/future.dart:414:23)
#73     _rootRunUnary (dart:async/zone.dart:1198:47)
#74     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#75     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#76     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#77     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#78     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#79     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:567:7)
#80     _rootRun (dart:async/zone.dart:1190:13)
#81     _CustomZone.run (dart:async/zone.dart:1093:19)
#82     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#83     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
#84     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#85     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#86     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#87     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)
-- After that the code just get stuck in a loop and need to terminate the job:
[INFO] 33.4s elapsed, 2/15 actions completed.
...
[INFO]  1m 58s elapsed, 2/15 actions completed.

Temporary Fix:
This squence resolve the issue temporarily until it unexpectedly reverts back to not working as above when I have called flutter packages pub run build_runner build an seemingly random amount of times.
> flutter clean
> flutter pub get
> flutter packages pub run build_runner build --delete-conflicting-outputs
// Output: Going through each action one by one as expected until it gets completed with confirmation message:
[INFO] Succeeded after 14.4s with 12 outputs (56 actions)

pubspec.yaml
environment:
  sdk: ">=2.7.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  moor: ^3.4.0
  sqlite3_flutter_libs: ^0.2.0
  path_provider:
  path:
  meta: ^1.1.6
  cupertino_icons: ^1.0.0

dev_dependencies:
  moor_flutter: ^3.1.0
  flutter_test:
    sdk: flutter
  moor_generator: ^3.4.0
  build_runner:
  test: ^1.15.4

flutter:
  uses-material-design: true

Thanks for the report. This looks like a bug in the analyzer package to me, but it's hard to say without seeing the code it fails for. Can you share code that reproduces this?

Yes, found from another thread the solution and it was indeed a analyzer package issue. By reverting to version 0.40.5 solved this issue.
dependencies:
  analyzer: 0.40.5


text:
🛑 Lyson NZ is down

In 2e400fa, Lyson NZ (https://$LZ_SITE1/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Lyson NZ is back up in 61a29e7 after 26 minutes.


text:
🛑 Lyson Au is down

In 41ffb06, Lyson Au (https://$LA_SITE1/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Lyson Au is back up in dfe2b0b after 5 minutes.


text:
Fix Babel version detection

this obviously referred to the addon itself and this only worked before because ember-test-selectors itself does not depend on ember-cli-babel. Using this.parent instead will check the ember-cli-babel version of the parent (either addon or app) which is the correct behavior, even for using it as a nested addon.
Resolves #130
/cc @rwjblue

@marcoow we do have test cases for Babel 5, but as I said since ember-test-selectors is itself not depending on ember-cli-babel we would have gotten the correct version anyway. Writing a test for a situation where that is not the case is unfortunately unreasonably complex.

Released as v0.3.6

repo: simplabs/ember-test-selectors


text:
Disable "require-await" rule

I don't think this rule makes sense anymore. Even if all a function does is return the result of another async function it should be allowed to mark the function as async to clearly communicate that this function is supposed to be async.
@marcoow @pangratz @jessica-jordan opinions?

As far as I understand, async functions may, but don't need to contain anawait expression specificationwise, so I'd agree that the rule can be omitted to better highlight any asynchronous operations regardless of the existence of await in their function bodies.

Yeah, seems fine to disable this.

authors: Turbo87 jessica-jordan marcoow

repo: simplabs/eslint-config-simplabs


text:
依然登录验证失败

版本号
v2.5.0
附加版本
协议Android pad
问题描述
无法登陆
复现方式
完成登录验证后报错
相关日志
Exception in thread "main" java.lang.reflect.InvocationTargetException
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:568)
        at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
        at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
Caused by: java.lang.reflect.InvocationTargetException
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:568)
        at love.forte.common.ioc.MethodDependPass.invoke(DependPass.kt:76)
        at love.forte.common.ioc.DependCenter.init(DependCenter.kt:108)
        at love.forte.simbot.core.SimbotApp.initDependCenter(SimbotApp.kt:436)
        at love.forte.simbot.core.SimbotApp.run$core(SimbotApp.kt:281)
        at love.forte.simbot.core.SimbotApp$Run.run(SimbotApp.kt:510)
        at love.forte.simbot.core.SimbotApp$Run.run$default(SimbotApp.kt:474)
        at love.forte.simbot.core.SimbotApp$Run.run(SimbotApp.kt)
        at love.forte.simbot.core.SimbotApp.run(SimbotApp.kt)
        at love.simbot.example.SimbotExampleApplication.main(SimbotExampleApplication.java:21)
        ... 8 more
Caused by: java.lang.IllegalStateException: Can't overwrite cause with a null
        at java.base/java.lang.Throwable.initCause(Throwable.java:463)
        at love.forte.simbot.component.mirai.configuration.MiraiBotVerifier.verity(MiraiBotVerifier.kt:115)
        at love.forte.simbot.component.mirai.configuration.MiraiBotManager.registerBot(MiraiBotManager.kt:103)
        at love.forte.simbot.core.configuration.CoreBotRegistrar.registerBots(CoreBotRegistrar.kt:65)
        ... 21 more
Caused by: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(766979001), code=45, title=禁止登录, message=您好，您当前使用的版本过低，前往QQ官网im.qq.com下载新版QQ。, errorInfo=)
        at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:309)
        at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33)
        at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:749)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

其他补充
No response

已尝试过,仍然不行,日志同上

尝试：

清理缓存、重新编译后再次尝试
尝试更换其他账号
更新到 v2.5.1
更换使用 v3.x

已测试v2.5.1,报错

那就尝试使用其他方式

尝试了其他账号,可以了

authors: Enderman-Teleporting ForteScarlet


text:
Edit the Exception message

https://github.com/simplygoodsoftware/pyrusapi-python/blob/251ca7dbe158246b67d31248cadb57001a1cab38/pyrus/client.py#L208
Need to edit form_register_request to task_comment_request into the exception message

Hello! Thank you for your contribution to improving the library. These changes were released in version 2.27.0

authors: alyonka-boyarskih dkuptsov

repo: simplygoodsoftware/pyrusapi-python


text:
Functional cryptocurrencies list

URL: https://github.com/somlor/awesome-functional-cryptocurrencies
I've just started this list of cryptocurrency projects using functional programming languages. I believe it will grow over time. Please accept PR if you think it may be of some value. Thanks!

It's a cool idea, but…

I believe it will grow over time.

I don't believe so, sorry. I've merged way too many unfinished lists that were never worked on again. That's why lists needs be comprehensive before being added. Try again later on when you have a more complete list.

authors: sindresorhus somlor

repo: sindresorhus/awesome


text:
Setting do-not-disturb off does not reflect dnd mode being off in the menubar

Using newly installed instance of 10.14 (Mojave) with do-not-disturb-cli v0.2.0 installed, do-not disturb off after previously setting do-not-disturb on does not seem to update the menubar icon to reflect that dnd mode is now off. I'm not sure if it actually is still on or not. It may just be that the icon isn't updating properly. Will work on verifying that.
At any rate, just wanted to file this issue in the event that others are experiencing this.

Just a suggestion, I would think this happens because the app is sandboxed. If the app is not sandboxed it should work.

authors: megalithic mellson

repo: sindresorhus/do-not-disturb


text:
Can't use this with typescript/node16?

import escapeStringRegexp from 'escape-string-regexp';
Typescript compiles this down to
const escape_string_regexp_1 = require("escape-string-regexp");
which causes Node to throw
[ERROR] uncaughtException: require() of ES Module node_modules\escape-string-regexp\index.js from dist\backend\classes\UiClient.js not supported.
Instead change the require of index.js in dist\backend\classes\UiClient.js to a dynamic import() which is available in all CommonJS modules.

I don't have this issue with any other module; how can I work around this?

same issue here, node 14 + typescript

https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c

Unfortunately, await import(…) doesn't work either with Typescript (it compiles it to a require, even when targeting es2020).
And given that very few other node modules are compatible with ES6, this basically means that you cannot use this module with node + typescript.
Fortunately this module basically consists of just one line of code so I copied it into my project - problem solved.

There's no essential difference between v4 and v5, except of the fact that v4 is not ESM. Downgrading the package to v4 should resolve the issue for now.

authors: TomMettam brioapp olchyk98 sindresorhus

repo: sindresorhus/escape-string-regexp


text:
Error truncating #:~:text= URL

For example #:~:text= URLs :
https://github.com/sindresorhus/refined-github/issues/3686#gh-csc-3:~:text=register%20for%20the%20(free)%20developer%20account

or
https://github.com/sindresorhus/refined-github/issues/3686#:~:text=register%20for%20the%20(free)%20developer%20account

✔ Expected correct behavior:  see  image 🖼
❌ Current error behavior (live demo) : 👇
https://github.com/sindresorhus/refined-github/issues/3686#gh-csc-3:~:text=register for the (free) developer account
https://github.com/sindresorhus/refined-github/issues/3686#:~:text=register for the (free) developer account
The beginning of :~:text=....... will be truncated, so the original anchor function of the API link is lost.

About :~:text=....... API (Chrome⁸¹ᐩ ):

Link to Text Fragment
https://chrome.google.com/webstore/detail/pbcodcjpfjdpcineamnnmbkkmkdpajjg

//Bookmarklet
javascript:if(target=prompt("⚓", location.href+'#:~:text=' +window.getSelection())) {window.open(target);}

📖 Documentation :
https://developer.chrome.com/blog/new-in-chrome-80
https://github.com/WICG/scroll-to-text-fragment
https://wicg.github.io/scroll-to-text-fragment/
https://web.dev/text-fragments/#text-fragments

Thanks for the detailed report, but it's unrelated to Refined GitHub

authors: dnknn fregante

repo: sindresorhus/refined-github


text:
Add caseInsensitive option

This PR adds a caseInsensitive option, which defaults to false and therefore is not a breaking change.
Also, the replacement function now receives the matched substring as a first parameter, instead of the needle, which is not a breaking change for anyone not using the caseInsensitive option, and makes much more sense for anyone using caseInsensitive: true.

Thanks :)

authors: papb sindresorhus

repo: sindresorhus/replace-string


text:
Add support for Flow

It seems that XO does not support Flow.
babel-eslint could be used as the default parser and an optional option flow could be added for configuration.
eslint-plugin-flowtype could be used

Would love to see
{
	"flow": true
}

babel-eslint is intentionally not the default parsers. It used to be, but I removed it as it was super buggy and caused lots of problems. You can easily set it as the parser yourself. I don't want an option for everything. If I add a flow option, people will want a typescript option, and then the floodgates are open.
https://github.com/sindresorhus/xo#parser

I can keep this open so I remember to add a tip about it to the readme: https://github.com/sindresorhus/xo#tips

@sindresorhus, since you don't want to support Typescript, it would be a good idea to support flow for
static-type checking

That would be a good idea to add eslint-plugin-flowtype rules.
I would propose to:

Create a new eslint-config-xo-flow shareable config with the eslint-plugin-flowtype plugins, some rules and the parser set to babel-eslint
Update the XO documentation to indicate that using flow require to add eslint-config-xo-flow to the extends  option

What do you think @sindresorhus ?

Why not add a "flow": true option to #326 and just have all of this working out of the box?
My favorite thing about XO is that I can npm install --save-dev xo and everything just works. Having to think about/deal with installing another config and another plugin and another parser is not very friendly when it can all be bundled as a config option.

Create a new eslint-config-xo-flow shareable config with the eslint-plugin-flowtype plugins, some rules and the parser set to babel-eslint

Sure, I can do that.

I wish we could make it just work, like @jorgegonzalez said. The problem is that I don't really want to depend on babel-eslint as it depends on babel which is a very heavy dependency...
I wonder if we could make a package like xo-flow, which would come with eslint-plugin-flowtype, eslint-babel, and when installed it tells XO to use Flow-mode.

@sindresorhus @pvdlg Can I start work on an eslint-config-xo-flow?

We could also add an xo --init=flow option, which triggers an install of an eslint-config-xo-flow, so that way it's not a direct dependency for XO. Similarly for TypeScript.

Can I start work on an eslint-config-xo-flow

I made https://github.com/xojs/eslint-config-xo-flow. Was easier for me to make the initial version, as I'm very opinionated the rules, than to comment on everything afterward. I'm happy to consider changes to it though.

We could also add an xo --init=flow option, which triggers an install of an eslint-config-xo-flow, so that way it's not a direct dependency of XO. Similarly for TypeScript.

Yup, that's a good idea. I plan to remove --init from XO itself and make it a standalone CLI. It's already a standalone module. Same changes as done here: https://github.com/avajs/create-ava/commit/f833b27fb8cc0ae5d9a318e0490e16bb6e51b850 Help welcome for that. Then it would be: npm init ava --flow.

I wonder if we could make a package like xo-flow, which would come with eslint-plugin-flowtype, eslint-babel, and when installed it tells XO to use Flow-mode.

@pvdlg What do you think of this idea? That would reduce the step of adding TS/Flow to only one command: npm i xo-typescript or npm i xo-flow.

I don't think it's great idea to have multiple packages. That would basically replace an option by different package.
We should handle Flow and Typescript the same way we handle React, by creating a shareable config: https://github.com/xojs/eslint-config-xo-react#use-with-xo. We can make it more explicit in the README that in order to use React. Flow or Typescript you need to add the proper extend.
React is far more popular than Flow or Typescript so I'm sure there is a lot of folks using XO to lint React apps and so far having to add "extends": "xo-react" in the XO config doesn't seems to be in issue.

@pvdlg The problem is that it's not just about adding "extends": "xo-typescript". They also need to install: eslint-config-xo-typescript typescript-eslint-parser eslint-plugin-typescript

That's exactly the same situation for React, per the eslint-config-xo-react doc:

$ npm install --save-dev eslint-config-xo-react eslint-plugin-react

You could change the listed peer dependencies in eslint-config-xo-flow/typescript to dependencies. Then add something similar xo --init=flow and xo --init=typescript which will trigger the following:
execa('npm', ['install', '--save-dev', 'eslint-config-xo-typescript']);

Thus prevents the configs and their large dependencies from being direct dependencies of XO
The user won't need to install anything other than XO
You won't have to worry about separate xo-flow and xo-typescript packages
Something similar could be done for React

Oh shareable configs can't have dependencies ...
The packages can all still be installed programmatically.

The packages can all still be installed programmatically.

I don't think that's a good idea. Too surprising.

Now that we have https://github.com/xojs/eslint-config-xo-flow can this issue be closed?

authors: clemtrek jorgegonzalez pvdlg sindresorhus

repo: sindresorhus/xo


text:
chore(deps): update lscr.io/linuxserver/sabnzbd docker tag to v3.7.1 (dev)

This PR contains the following updates:

Package
Update
Change

lscr.io/linuxserver/sabnzbd
patch
3.7.0 -> 3.7.1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (3.7.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

repo: singhmanavjot/infrastructure


text:
Add gossip part in ABL and Unity

ABL part:

Add Action Gossip
Add a new WME - CalDistanceWME
Add a self-defined structure ArrayHolder
Modify GameAgent

Unity part:

Add a position tracker that keeps updating NPC's position in NPC movement script
Add locations in BasePlayer class

Todo: PositionTrackers only tracks NPC that has been recruited, but the system are supposed to track every NPC. We need to create an NPC manager that tracks all NPCs that use WanderNPCAI.cs

LGTM :) thanks fuhsin!

repo: singlab/oops-all-bards


text:
.shape attribute of arrays created with from_h5ad generates error

Create an scgroup with from_h5ad, open a component array (eg, obs) and inspect its shape parameter -- generates an error.
Test case: run the following from the apis/python directory and you will get an error on the line that prints the shape parameter.
Output:
$ python temp/test1.py
0.14.1
/home/bruce/projects/TileDB-SingleCell/venv/lib/python3.9/site-packages/anndata/compat/__init__.py:232: FutureWarning: Moving element from .uns['neighbors']['distances'] to .obsp['distances'].

This is where adjacency matrices should go now.
  warn(
/home/bruce/projects/TileDB-SingleCell/venv/lib/python3.9/site-packages/anndata/compat/__init__.py:232: FutureWarning: Moving element from .uns['neighbors']['connectivities'] to .obsp['connectivities'].

This is where adjacency matrices should go now.
  warn(
Traceback (most recent call last):
  File "/home/bruce/projects/TileDB-SingleCell/apis/python/temp/test1.py", line 16, in <module>
    sys.exit(main())
  File "/home/bruce/projects/TileDB-SingleCell/apis/python/temp/test1.py", line 12, in main
    print(obs.shape)
  File "tiledb/libtiledb.pyx", line 3607, in tiledb.libtiledb.Array.shape.__get__
  File "tiledb/libtiledb.pyx", line 3014, in tiledb.libtiledb.ArraySchema.shape.__get__
  File "tiledb/libtiledb.pyx", line 2329, in tiledb.libtiledb.Domain.shape.__get__
  File "tiledb/libtiledb.pyx", line 2188, in genexpr
  File "tiledb/libtiledb.pyx", line 2188, in genexpr
  File "tiledb/libtiledb.pyx", line 2056, in tiledb.libtiledb.Dim.shape.__get__
  File "tiledb/libtiledb.pyx", line 2041, in tiledb.libtiledb.Dim._shape
AttributeError: 'NoneType' object has no attribute 'item'

Test case:
import sys
import tiledb
import tiledbsc

def main():
    print(tiledb.__version__)
    sc = tiledbsc.SCGroup("./temp/test1", verbose=False)
    sc.from_h5ad("./anndata/pbmc3k_processed.h5ad")

    obs = tiledb.open("./temp/test1/obs")
    print(obs.shape)

if __name__ == "__main__":
    sys.exit(main())

The sparse matrices in the group all have exceptions on A.shape; the dense ones do not:
#!/usr/bin/env python

import tiledb
import tiledbsc

#g = tiledbsc.SCGroup("test")
#g.from_h5ad("/Users/johnkerl/scdata/anndata/pbmc-small.h5ad")

for x in ['X/data', 'obs', 'var', 'obsm/X_pca', 'varm/PCs', 'obsp/distances']:
    with tiledb.open('./test/' + x) as A:
        print()
        print(A.uri)
        #print(A.schema)
        try:
            print(A.shape)
        except:
            print('exc')

#./test/X/data         sparse=True,
#./test/obs            sparse=True,
#./test/var            sparse=True,
#./test/obsm/X_pca     sparse=False,
#./test/varm/PCs       sparse=False,
#./test/obsp/distances sparse=False,

#./test/X/data         exc
#./test/obs            exc
#./test/var            exc
#./test/obsm/X_pca     (80, 19)
#./test/varm/PCs       (20, 19)
#./test/obsp/distances (80, 80)

I'll check on what the expected behavior is for .shape on a sparse array (throwing an exception doesn't feel right).

I checked with the team and this is a bug in TileDB-Py:

Sparse array with int dims has a .shape
Sparse array with float or string dims does not

With float dims, .shape correctly does TypeError: shape valid only for integer domains
With string dims, we get the less-helpful error message reported here

TileDB-Py PR: https://github.com/TileDB-Inc/TileDB-Py/pull/1055

The true ask here is handled in #125.

authors: bkmartinjr johnkerl

repo: single-cell-data/TileDB-SingleCell


text:
Bugfix/remove scib

Removing scIB as a core dependency since we no longer use it for scran normalization. Note to @LuckyMD and @danielStrobl that if you're using scIB for the batch normalization task, you will have to add it as a dependency in either openproblems-python-extras, openproblems-r-extras, or a new Docker image. Note also that scIB's use of scanpy<1.5 breaks openproblems dependency on scanpy >= 1.6.

Yes, thx. We're aware of the dependency issue. We'll set up a docker image per method I think and then make sure the graphs are stored in obsp as well as uns to ensure any further use of the anndata object is fine no matter the scanpy version. We'll have to figure out how to run metrics that are dependent on scib without a scib general update...

Maybe it's just time to do a full update of scib and then test the results are consistent

authors: LuckyMD scottgigante


text:
Vacuum reports etcdserver: too many operations in txn request

2022-04-24T10:13:47.666572Z  WARN risingwave_meta::hummock::vacuum: Vacuum tracked data error internal error: meta internal error: grpc request error: status: InvalidArgument, message: "etcdserver: too many operations in txn request", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }

happening in https://github.com/singularity-data/risingwave/issues/2092

Manually revisited recent magically failed cases, all of them contains this warning. Not sure if a successful run will also contain such info.

But I guess recent failure might be caused by this issue...

Looks like etcd by default limits the ops in one transaction to be 128. (https://etcd.netlify.app/docs/v3.4/op-guide/configuration/#--max-txn-ops)
cc @zwang28. vacumm itself should not affect correctness but I guess "etcdserver: too many operations in txn request" may also happen in other operations, which can cause correctness problem. Do we have the full log?

Do we have the full log?
risedev-logs-4.zip

Looks like etcd by default limits the ops in one transaction to be 128. (https://etcd.netlify.app/docs/v3.4/op-guide/configuration/#--max-txn-ops)
cc @zwang28. vacumm itself should not affect correctness but I guess "etcdserver: too many operations in txn request" may also happen in other operations, which can cause correctness problem. Do we have the full log?

I think vacuum is not related to these magically failed cases (but surely should handle the etcdserver limit).
@skyzh Have the magically failed cases happened for 1-node with etcd meta / in-mem meta?

We do not have 1-node e2e / in-mem meta on CI...

Is it possible that vacuum failed -> version not updated in etcd -> SSTs lost, so that the queries only show a partial result or a state in the past?

2022-04-24T10:13:47.666572Z  WARN risingwave_meta::hummock::vacuum: Vacuum tracked data error internal error: meta internal error: grpc request error: status: InvalidArgument, message: "etcdserver: too many operations in txn request", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }

I don't think so. The call site removes stale version if succeeds, which should not affect the result from latest version.
Let's sync more info offline first.

Looked at the last three compaction task reported in meta node. The last compaction task reports empty SSTs in level 1, which should not be the case.
2022-04-24T10:13:39.151836Z  INFO risingwave_meta::hummock::hummock_manager: Reported compact task. Compaction task id: 4, target level: 1
Compaction watermark: 33559977820
Compaction # splits: 2
Compaction task status: true
Compaction SSTables structure:
Level 0: Some(Level { level_type: Overlapping, table_infos: [SstableInfo { id: 289, key_range: None }, SstableInfo { id: 366, key_range: None }, SstableInfo { id: 369, key_range: None }, SstableInfo { id: 351, key_range: None }, SstableInfo { id: 338, key_range: None }, SstableInfo { id: 306, key_range: None }, SstableInfo { id: 316, key_range: None }, SstableInfo { id: 309, key_range: None }, SstableInfo { id: 332, key_range: None }, SstableInfo { id: 324, key_range: None }, SstableInfo { id: 277, key_range: None }, SstableInfo { id: 270, key_range: None }, SstableInfo { id: 261, key_range: None }, SstableInfo { id: 259, key_range: None }, SstableInfo { id: 249, key_range: None }, SstableInfo { id: 245, key_range: None }, SstableInfo { id: 242, key_range: None }, SstableInfo { id: 233, key_range: None }, SstableInfo { id: 230, key_range: None }, SstableInfo { id: 224, key_range: None }, SstableInfo { id: 214, key_range: None }, SstableInfo { id: 209, key_range: None }, SstableInfo { id: 206, key_range: None }, SstableInfo { id: 200, key_range: None }, SstableInfo { id: 191, key_range: None }, SstableInfo { id: 183, key_range: None }, SstableInfo { id: 269, key_range: None }, SstableInfo { id: 264, key_range: None }, SstableInfo { id: 254, key_range: None }, SstableInfo { id: 247, key_range: None }, SstableInfo { id: 240, key_range: None }, SstableInfo { id: 235, key_range: None }, SstableInfo { id: 222, key_range: None }, SstableInfo { id: 217, key_range: None }, SstableInfo { id: 211, key_range: None }, SstableInfo { id: 201, key_range: None }, SstableInfo { id: 197, key_range: None }, SstableInfo { id: 192, key_range: None }, SstableInfo { id: 273, key_range: None }, SstableInfo { id: 257, key_range: None }, SstableInfo { id: 227, key_range: None }, SstableInfo { id: 187, key_range: None }, SstableInfo { id: 276, key_range: None }, SstableInfo { id: 267, key_range: None }, SstableInfo { id: 266, key_range: None }, SstableInfo { id: 256, key_range: None }, SstableInfo { id: 251, key_range: None }, SstableInfo { id: 243, key_range: None }, SstableInfo { id: 238, key_range: None }, SstableInfo { id: 231, key_range: None }, SstableInfo { id: 226, key_range: None }, SstableInfo { id: 219, key_range: None }, SstableInfo { id: 215, key_range: None }, SstableInfo { id: 208, key_range: None }, SstableInfo { id: 203, key_range: None }, SstableInfo { id: 196, key_range: None }, SstableInfo { id: 190, key_range: None }, SstableInfo { id: 186, key_range: None }, SstableInfo { id: 279, key_range: None }, SstableInfo { id: 285, key_range: None }, SstableInfo { id: 284, key_range: None }, SstableInfo { id: 282, key_range: None }, SstableInfo { id: 286, key_range: None }, SstableInfo { id: 395, key_range: None }, SstableInfo { id: 379, key_range: None }, SstableInfo { id: 390, key_range: None }, SstableInfo { id: 394, key_range: None }, SstableInfo { id: 388, key_range: None }, SstableInfo { id: 384, key_range: None }, SstableInfo { id: 392, key_range: None }, SstableInfo { id: 385, key_range: None }, SstableInfo { id: 382, key_range: None }, SstableInfo { id: 373, key_range: None }, SstableInfo { id: 377, key_range: None }, SstableInfo { id: 375, key_range: None }, SstableInfo { id: 179, key_range: None }, SstableInfo { id: 182, key_range: None }, SstableInfo { id: 178, key_range: None }, SstableInfo { id: 175, key_range: None }, SstableInfo { id: 172, key_range: None }, SstableInfo { id: 171, key_range: None }, SstableInfo { id: 174, key_range: None }, SstableInfo { id: 173, key_range: None }, SstableInfo { id: 176, key_range: None }, SstableInfo { id: 181, key_range: None }, SstableInfo { id: 177, key_range: None }, SstableInfo { id: 180, key_range: None }, SstableInfo { id: 148, key_range: None }, SstableInfo { id: 147, key_range: None }, SstableInfo { id: 146, key_range: None }, SstableInfo { id: 150, key_range: None }, SstableInfo { id: 151, key_range: None }, SstableInfo { id: 149, key_range: None }, SstableInfo { id: 170, key_range: None }, SstableInfo { id: 165, key_range: None }, SstableInfo { id: 169, key_range: None }, SstableInfo { id: 166, key_range: None }, SstableInfo { id: 167, key_range: None }, SstableInfo { id: 168, key_range: None }, SstableInfo { id: 152, key_range: None }, SstableInfo { id: 153, key_range: None }, SstableInfo { id: 155, key_range: None }, SstableInfo { id: 156, key_range: None }, SstableInfo { id: 154, key_range: None }, SstableInfo { id: 160, key_range: None }, SstableInfo { id: 162, key_range: None }, SstableInfo { id: 163, key_range: None }, SstableInfo { id: 158, key_range: None }, SstableInfo { id: 159, key_range: None }, SstableInfo { id: 161, key_range: None }, SstableInfo { id: 278, key_range: None }, SstableInfo { id: 271, key_range: None }, SstableInfo { id: 262, key_range: None }, SstableInfo { id: 258, key_range: None }, SstableInfo { id: 250, key_range: None }, SstableInfo { id: 246, key_range: None }, SstableInfo { id: 239, key_range: None }, SstableInfo { id: 232, key_range: None }, SstableInfo { id: 228, key_range: None }, SstableInfo { id: 223, key_range: None }, SstableInfo { id: 213, key_range: None }, SstableInfo { id: 210, key_range: None }, SstableInfo { id: 205, key_range: None }, SstableInfo { id: 199, key_range: None }, SstableInfo { id: 193, key_range: None }, SstableInfo { id: 184, key_range: None }, SstableInfo { id: 272, key_range: None }, SstableInfo { id: 263, key_range: None }, SstableInfo { id: 253, key_range: None }, SstableInfo { id: 248, key_range: None }, SstableInfo { id: 241, key_range: None }, SstableInfo { id: 234, key_range: None }, SstableInfo { id: 221, key_range: None }, SstableInfo { id: 218, key_range: None }, SstableInfo { id: 212, key_range: None }, SstableInfo { id: 202, key_range: None }, SstableInfo { id: 198, key_range: None }, SstableInfo { id: 194, key_range: None }, SstableInfo { id: 275, key_range: None }, SstableInfo { id: 268, key_range: None }, SstableInfo { id: 265, key_range: None }, SstableInfo { id: 255, key_range: None }, SstableInfo { id: 252, key_range: None }, SstableInfo { id: 244, key_range: None }, SstableInfo { id: 237, key_range: None }, SstableInfo { id: 236, key_range: None }, SstableInfo { id: 225, key_range: None }, SstableInfo { id: 220, key_range: None }, SstableInfo { id: 216, key_range: None }, SstableInfo { id: 207, key_range: None }, SstableInfo { id: 204, key_range: None }, SstableInfo { id: 195, key_range: None }, SstableInfo { id: 189, key_range: None }, SstableInfo { id: 185, key_range: None }, SstableInfo { id: 274, key_range: None }, SstableInfo { id: 260, key_range: None }, SstableInfo { id: 229, key_range: None }, SstableInfo { id: 188, key_range: None }, SstableInfo { id: 290, key_range: None }, SstableInfo { id: 287, key_range: None }, SstableInfo { id: 280, key_range: None }, SstableInfo { id: 283, key_range: None }, SstableInfo { id: 281, key_range: None }, SstableInfo { id: 288, key_range: None }, SstableInfo { id: 337, key_range: None }, SstableInfo { id: 349, key_range: None }, SstableInfo { id: 365, key_range: None }, SstableInfo { id: 296, key_range: None }, SstableInfo { id: 304, key_range: None }, SstableInfo { id: 308, key_range: None }, SstableInfo { id: 317, key_range: None }, SstableInfo { id: 321, key_range: None }, SstableInfo { id: 328, key_range: None }, SstableInfo { id: 333, key_range: None }, SstableInfo { id: 340, key_range: None }, SstableInfo { id: 346, key_range: None }, SstableInfo { id: 352, key_range: None }, SstableInfo { id: 355, key_range: None }, SstableInfo { id: 361, key_range: None }, SstableInfo { id: 372, key_range: None }, SstableInfo { id: 315, key_range: None }, SstableInfo { id: 322, key_range: None }, SstableInfo { id: 327, key_range: None }, SstableInfo { id: 334, key_range: None }, SstableInfo { id: 339, key_range: None }, SstableInfo { id: 345, key_range: None }, SstableInfo { id: 350, key_range: None }, SstableInfo { id: 356, key_range: None }, SstableInfo { id: 362, key_range: None }, SstableInfo { id: 371, key_range: None }, SstableInfo { id: 303, key_range: None }, SstableInfo { id: 307, key_range: None }, SstableInfo { id: 295, key_range: None }, SstableInfo { id: 300, key_range: None }, SstableInfo { id: 302, key_range: None }, SstableInfo { id: 311, key_range: None }, SstableInfo { id: 318, key_range: None }, SstableInfo { id: 320, key_range: None }, SstableInfo { id: 330, key_range: None }, SstableInfo { id: 336, key_range: None }, SstableInfo { id: 342, key_range: None }, SstableInfo { id: 348, key_range: None }, SstableInfo { id: 353, key_range: None }, SstableInfo { id: 357, key_range: None }, SstableInfo { id: 363, key_range: None }, SstableInfo { id: 367, key_range: None }, SstableInfo { id: 313, key_range: None }, SstableInfo { id: 319, key_range: None }, SstableInfo { id: 329, key_range: None }, SstableInfo { id: 335, key_range: None }, SstableInfo { id: 341, key_range: None }, SstableInfo { id: 347, key_range: None }, SstableInfo { id: 354, key_range: None }, SstableInfo { id: 358, key_range: None }, SstableInfo { id: 364, key_range: None }, SstableInfo { id: 368, key_range: None }, SstableInfo { id: 301, key_range: None }, SstableInfo { id: 312, key_range: None }, SstableInfo { id: 298, key_range: None }, SstableInfo { id: 297, key_range: None }, SstableInfo { id: 314, key_range: None }, SstableInfo { id: 323, key_range: None }, SstableInfo { id: 326, key_range: None }, SstableInfo { id: 331, key_range: None }, SstableInfo { id: 344, key_range: None }, SstableInfo { id: 359, key_range: None }, SstableInfo { id: 370, key_range: None }, SstableInfo { id: 305, key_range: None }, SstableInfo { id: 310, key_range: None }, SstableInfo { id: 325, key_range: None }, SstableInfo { id: 343, key_range: None }, SstableInfo { id: 360, key_range: None }, SstableInfo { id: 299, key_range: None }, SstableInfo { id: 291, key_range: None }, SstableInfo { id: 293, key_range: None }, SstableInfo { id: 294, key_range: None }, SstableInfo { id: 292, key_range: None }, SstableInfo { id: 396, key_range: None }, SstableInfo { id: 391, key_range: None }, SstableInfo { id: 393, key_range: None }, SstableInfo { id: 380, key_range: None }, SstableInfo { id: 387, key_range: None }, SstableInfo { id: 383, key_range: None }, SstableInfo { id: 389, key_range: None }, SstableInfo { id: 374, key_range: None }, SstableInfo { id: 378, key_range: None }, SstableInfo { id: 381, key_range: None }, SstableInfo { id: 386, key_range: None }, SstableInfo { id: 376, key_range: None }] })
Level 1: Some(Level { level_type: Nonoverlapping, table_infos: [SstableInfo { id: 145, key_range: None }, SstableInfo { id: 164, key_range: None }] })
Compaction task output: [SstableInfo { id: 409, key_range: Some(KeyRange { left: [101, 0, 0, 0, 83, 0, 0, 1, 114, 0, 0, 255, 255, 255, 248, 47, 171, 90, 66], right: [116, 0, 0, 1, 24, 1, 128, 0, 0, 3, 0, 0, 0, 5, 128, 0, 0, 16, 255, 255, 255, 248, 47, 170, 244, 89], inf: false }) }, SstableInfo { id: 410, key_range: Some(KeyRange { left: [116, 0, 0, 1, 24, 1, 128, 0, 0, 3, 0, 0, 0, 6, 127, 255, 255, 255, 255, 255, 255, 248, 47, 170, 244, 89], right: [116, 0, 0, 1, 214, 1, 128, 0, 0, 0, 0, 0, 12, 39, 128, 0, 0, 0, 0, 0, 12, 39, 255, 255, 255, 248, 47, 170, 202, 35], inf: false }) }]

2022-04-24T10:13:48.241369Z  INFO risingwave_meta::hummock::hummock_manager: Reported compact task. Compaction task id: 5, target level: 1
Compaction watermark: 33559977820
Compaction # splits: 1
Compaction task status: true
Compaction SSTables structure:
Level 0: Some(Level { level_type: Overlapping, table_infos: [SstableInfo { id: 537, key_range: None }, SstableInfo { id: 536, key_range: None }, SstableInfo { id: 533, key_range: None }, SstableInfo { id: 531, key_range: None }, SstableInfo { id: 529, key_range: None }, SstableInfo { id: 528, key_range: None }, SstableInfo { id: 526, key_range: None }, SstableInfo { id: 523, key_range: None }, SstableInfo { id: 522, key_range: None }, SstableInfo { id: 520, key_range: None }, SstableInfo { id: 517, key_range: None }, SstableInfo { id: 516, key_range: None }, SstableInfo { id: 513, key_range: None }, SstableInfo { id: 512, key_range: None }, SstableInfo { id: 510, key_range: None }, SstableInfo { id: 508, key_range: None }, SstableInfo { id: 505, key_range: None }, SstableInfo { id: 503, key_range: None }, SstableInfo { id: 501, key_range: None }, SstableInfo { id: 500, key_range: None }, SstableInfo { id: 498, key_range: None }, SstableInfo { id: 495, key_range: None }, SstableInfo { id: 494, key_range: None }, SstableInfo { id: 491, key_range: None }, SstableInfo { id: 489, key_range: None }, SstableInfo { id: 488, key_range: None }, SstableInfo { id: 486, key_range: None }, SstableInfo { id: 483, key_range: None }] })
Level 1: Some(Level { level_type: Nonoverlapping, table_infos: [SstableInfo { id: 409, key_range: None }] })
Compaction task output: [SstableInfo { id: 563, key_range: Some(KeyRange { left: [101, 0, 0, 0, 83, 0, 0, 1, 114, 0, 0, 255, 255, 255, 248, 47, 171, 90, 66], right: [116, 0, 0, 1, 24, 1, 128, 0, 0, 3, 0, 0, 0, 5, 128, 0, 0, 16, 255, 255, 255, 248, 47, 170, 244, 89], inf: false }) }]

2022-04-24T10:13:57.171767Z  INFO risingwave_meta::hummock::hummock_manager: Reported compact task. Compaction task id: 6, target level: 1
Compaction watermark: 33559977820
Compaction # splits: 1
Compaction task status: true
Compaction SSTables structure:
Level 0: Some(Level { level_type: Overlapping, table_infos: [SstableInfo { id: 694, key_range: None }] })
Level 1: Some(Level { level_type: Nonoverlapping, table_infos: [] })
Compaction task output: [SstableInfo { id: 695, key_range: Some(KeyRange { left: [116, 0, 0, 3, 212, 1, 128, 0, 0, 5, 128, 0, 0, 3, 0, 0, 0, 4, 255, 255, 255, 248, 47, 170, 124, 156], right: [116, 0, 0, 3, 214, 1, 128, 0, 0, 198, 128, 0, 0, 3, 0, 0, 0, 197, 255, 255, 255, 248, 47, 170, 124, 156], inf: false }) }]

nit: can we change KeyRange to print human readable strings? 🤪

Looked at the last three compaction task reported in meta node. The last compaction task reports empty SSTs in level 1, which should not be the case.

No, the Level refers to input level, see compact_task_to_string

Reported compact task

Oh I see. I misunderstood.

There is a bug in apply_compact_result: ordering of SSTs is not maintained when adding new SSTs into level1 after compaction. get implementation relies on the ordering to search for SSTs. Will submit a PR to fix it.

There is a bug in apply_compact_result: ordering of SSTs is not maintained when adding new SSTs into level1 after compaction. get implementation relies on the ordering to search for SSTs. Will submit a PR to fix it.

#2122 will fix this isse.

repo: singularity-data/risingwave


text:
feat(pgwire): introduce simple extended query mode

What's changed and what's your intention?

This is PR about the simple extended query mode.
The detail of this design and its restriction is in the #2924.
It supports the concept of "prepared statement" and "portal" in the pgwire semantically. To support generic parameters, its implementation is based on the regular expression replace. It didn't use any parse or infer technology and that's why this feature is limited.

Something may need to be modified

[ ] Error handle: For the specific behavior of the client driver(tokio_postgres), I use unwrap() as an error handler for some behavior because I think it will always be correct when the client driver is tokio_postgres. (Such as "named_portals.get(&portal_name).unwrap()", I can sure the portal_name always will be valid when the client driver is tokio_postgres) I add the comment ("// NOTE: error handle need to modify later;") in these places.
[ ] "cstr_to_str" occur in pg_extended.rs and pg_protocal.rs, I think it's maybe the code redundancy. Should we place it in another place such as "lib.rs"?

Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)
ref: #2924.

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

authors: CLAassistant ZENOTME


text:
Feature webview

Loads either Web resource or local resource contained in Bundle of application. Fixes #17

To be reviewed @sinnerschrader-mobile/ios


text:
[Version 7.1.0] Typescript compilation error

Hello,

FakeTimers version : 7.1.0
Environment : Windows,  node:erbium-alpine
Other libraries you are using:

Typescript 3.9.9
@sinonjs/common@1.7.0

What did you expect to happen?
To be able to compile with tsc
What actually happens
When i try to compile the project with fake-timers, i got a compilation error :
node_modules/@sinonjs/fake-timers/types/fake-timers-src.d.ts:11:28 - error TS2304: Cannot find name 'queueMicrotask'.
       queueMicrotask: typeof queueMicrotask;

Hi, this is correct, as this project has no such API.
Feel free to submit a feature request for this: spec.
P.S. You will have a much higher chance of seeing that feature request filled if you just do it yourself :)

Hi, I never got a reply to this, but it turns out I was wrong. I just searched the code and found it present  - just undocumented (only in JSDoc). See for instance discussion in #233.
The problem is somehow related to the typescript definitions we generated, so you might have better luck installing sinonjs/fake-timers@6 and using the DT @types. We just decided to drop them and leave this to DT the community again for v8 ...
So there is two problems here:

When the feature was added, no docs were added.
The definitions are missing.

The DT types have exposed them in their types: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/sinonjs__fake-timers/index.d.ts#L281
Given that we will not be fixing our own types, I will keep this closed, but open a new feature for improved docs.

repo: sinonjs/fake-timers


text:
fromStream and asyncPipeline

I am picking up this 2 from https://github.com/bustle/streaming-iterables
fromStream is a compatibility layer to add a async-iterable interface where there is a stream.
pipeline is a syntactic sugar for using compose. It is more intuitive and readable.

fromStream is a compatibility layer to add a async-iterable interface where there is a stream.

Well, I needed this months ago, I didn't know where to find it, so I had to created by myself (same function name BTW), now that you also decide to add it to iter-tools, this would cause a lot of duplication.

pipeline is a syntactic sugar for using compose. It is more intuitive and readable.

Totally agree.

@KSXGitHub still pondering if I want to add fromStream here, or in some other package. Maybe iter-tools-node-compat or something like that ? Did you have yours somewhere ?
Also writestream looks like a good idea in the same package https://github.com/bustle/streaming-iterables#writetostream

Did you have yours somewhere ?

Yes, it is called iterate-evented-stream

authors: KSXGitHub sithmel

repo: sithmel/iter-tools


text:
[docker image: graylog/graylog:4.0] Error importing content pack

Hello,
I'm using docker  with image: graylog/graylog:4.0 and HTTP Monitor Input Plugin. And when I go to System-> Content Packs -> Upload, I'm getting this error:
Error importing content pack, please ensure it is a valid JSON file. Check your Graylog logs for more information.Null id at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 333, column: 1] (through reference chain: org.graylog2.contentpacks.model.AutoValue_LegacyContentPack$Builder["id"])

Did you had any luck on this?
Same error on latest version of Graylog.


text:
Missing Documentation for gprm Dependency

Thank you for providing this excellent code repository. I noticed that the code heavily relies on a package named gprm (e.g., imports such as gprm.PointDistributionOnSphere and utilities from gprm.utils), but I couldn't find any information about this library in the repository or online.
Could you please provide:

A description of gprm, its purpose, and how it integrates with the current repository.
Installation instructions for gprm (e.g., whether it is an internal module, available via PyPI, or needs to be built separately).
Any additional documentation or references for gprm usage.

This information would be very helpful for replicating your work and understanding the code.
Thank you for your time and assistance!
Best regards,
Walter

Hi Walter,
gprm is an abbreviation for GPlatesReconstructionModel, which is a set of python tools to make working with GPlates-format plate tectonic reconstructions easier.
You can find the code, additional dependencies, and installation instructions here:
https://github.com/siwill22/GPlatesReconstructionModel
Hope that helps,
Simon

Hi Simon,
Thank you for your detailed response and for sharing the link to the repository. I’ll take a closer look and reach out if I have any further questions.
Best regards,
Walter


text:
ImportError: No module named cmdline

I have successfully installed version 1.16.0 but when I try to run "twitter" from my linux terminal it says like this: http://s17.postimg.org/wim9qyqnz/angel_beats_bg5.jpg
I had no error in version 1.15.0

These three look like duplicates: #67 #162 #281.

Yep. Dupe of #67,

authors: hillz1 hugovk sixohsix

repo: sixohsix/twitter


text:
Bird Error

same error

Same

authors: akashasmaul cr00tt hiepeng

repo: sizifart/SeedCoinBot


text:
feat: update peerDependencies to support React 19

Update package.json to include React 19 in peerDependencies for both react and react-dom.

Thank you for the PR! I haven't tested mui-tiptap with React 19 myself. We're you able to confirm that it worked for you?

yes i have tested it didnt saw any negative effects.

authors: KLXYinc sjdemartini

repo: sjdemartini/mui-tiptap


text:
Subdomains links are treated as external links

When crawling a page with links pointing to the same domain but with different subdomain, they are considered as external links and are excluded and not crawled. The only option is to enable IsExternalPageCrawlingEnabled, but it could be dangerous in some scenarios.

This example demonstrates how to use the a delegate that can customize what is considered internal to the root domain. Let me know if that works for you.

authors: marcmarsinach sjdirect

repo: sjdirect/abot


text:
lug: remove ubuntu-cd

Signed-off-by: Alex Chi iskyzh@gmail.com

@skyzh 你好，我是 sjtug/mirror-requests#267 的作者。
今日我在贵站寻找 Ubuntu 的镜像文件，发现 "ubuntu-cd" 目录再次被重定向到了 "https://repo.huaweicloud.com/ubuntu-cdimage//" 。在 #267 ，我写道：

...
但 "https://repo.huaweicloud.com/ubuntu-cdimage//" 似乎不包含 amd64 架构的 Ubuntu Server 的镜像文件（如 ubuntu-21.10-live-server-amd64.iso ）。要找到这样的镜像文件，需要去 "https://repo.huaweicloud.com/ubuntu-releases/" 。

经过分析，其实我想表达的是：
"https://mirror.sjtu.edu.cn/ubuntu-cd/" 没有指向 "https://repo.huaweicloud.com/ubuntu-releases/" ，让该重定向看起来是错误的； "https://mirror.sjtu.edu.cn/ubuntu-cdimage/" 与 "https://repo.huaweicloud.com/ubuntu-cdimage//" 的内容一致，让那个重定向看起来没有道理（本可以指向站内资源，但却指向了华为云）。
因此我期望：

...
"/ubuntu-cd/" 重定向到 "https://repo.huaweicloud.com/ubuntu-releases/" 。

当然，如果现在这样的重定向是有意为之，就请忽略我的请求吧。
谢谢，打扰了。

感谢你的反馈！我们将尽快将重定向改到 ubuntu-release.
ubuntu-cd 近期又有大量流量的下载，为了避免影响其他镜像的正常服务，我们进行了下线处理，并重定向到了其他镜像站。这里我们期望原来镜像站提供的数据和重定向后的一致。

repo: sjtug/mirror-docker-unified


text:
jspm install fails

Error is different than issue #10
jspm install npm:skatejs-web-components

Looking up npm:skatejs-web-components
     Updating registry cache...

warn Error on locate for github:webcomponents/custom-elements/archive/fc022e8.tar.gz
     GitHub packages must be of the form owner/repo.

warn Error on locate for github:webcomponents/shadycss/archive/19a46c9.tar.gz
     GitHub packages must be of the form owner/repo.

warn Error on locate for github:webcomponents/shadydom/archive/c162774.tar.gz
     GitHub packages must be of the form owner/repo.

warn Error locating github:webcomponents/custom-elements/archive/fc022e8.tar.gz.

err  Error locating github:webcomponents/custom-elements/archive/fc022e8.tar.gz.

warn Installation changes not saved.

tarball depdendencies not supported in jspm

I'm not sure this is easy until releases are pushed for each of the pfills. A workaround would be to load https://unpkg.com/skatejs-web-components using a  tag.

That's what I ended up doing, thanks.
On Dec 7, 2016 10:30 PM, "Trey Shugart" notifications@github.com wrote:

I'm not sure this is easy until releases are pushed for each of the
pfills. A workaround would be to load https://unpkg.com/skatejs-web-
components using a  tag.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/skatejs/web-components/issues/31#issuecomment-265644011,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHyNUGcpIrNNy_NAB1WsiHmFvLjzD0wSks5rF3nvgaJpZM4LHYHy
.

Cool, I'll close this for now.

authors: rhythnic treshugart

repo: skatejs/web-components


text:
Fix non-interactive population of x86-lookup-index

Calling x86-lookup non-interactively (such as from a custom x86-lookup-browse-pdf-function handler) fails to populate x86-lookup-cache before the browser process is launched. Consequently, a nil page parameter is passed to the browse-pdf handler. This commit fixes that.
Observed using Alhadis/.emacs.d@dcf7abc.

Thanks! I obviously hadn't considered this execution path.

authors: Alhadis skeeto

license: unlicense


text:
FR: show folders hierarchy

In a big monorepo list of workspaces might be pretty long. It will be useful to allow switch between flat list and hierarchy view.

I have started work on this issue and hope to have it in the next release

Sorry, I hope to be finished with this issue soon as it holding up releasing the next version. The tree view has been started and I hope to finish soon

I have a working version. I release a version soon to the marketplace. I started using @vscode/webview-ui-toolkit for various UI elements, but unfortunately it does not havea tree widget (there is a pr requesting this), so I needed to build the tree from scratch.

As you can see there are some spacing issues, wil try and fix those

See v1.4.0 Search depth has been increased 20 25 in v1.4.0

authors: sketchbuch yrtimiD

repo: sketchbuch/vsc-workspace-sidebar


text:
Database migration

そろそろマイグレーションほしい

非常にわかるけど茨の道な気がしている

repo: sketchglass/respass


text:
Drawing RTL Text needs to apply character shaping

Displaying right-to-left text looks wrong, because character shaping is not applied. Compare the text output of MS Word with that of the demo application.

Tested with version 6.00 Beta 2.

Cause you're not using the same font .

@Lasibian Seems that @randydom is right. Are you using the same font family? Do you have more info?

@randydom got it right. It was because of the different font.
At the moment I still can't use skia with RTL text, because I need the glyph positions of the shaped text. I haven't found a way to get these from the ISkTextBlob.

At the moment I still can't use skia with RTL text, because I need the glyph positions of the shaped text. I haven't found a way to get these from the ISkTextBlob.

Are you using FMX or VCL? For FMX, I recomend you to use the TSkTextLayout from unit FMX.Skia.Canvas.

@viniciusfbb I'm using VCL.

@Lasibian The most complete and ideal text manipulation/rendering class (including multiple styles) is the SkParagraph class. There are some examples in our demo and in FMX's own TSkTextLayout (which also uses SkParagraph behind it) to render and manipulate texts, including get the glyph positions.
I will close this issue now because what was reported was not exactly a bug, but feel free to continue the conversation.

authors: Lasibian randydom viniciusfbb


text:
[Feature request] Adjusting fade steps

Hi Skipadu,
Thanks for sharing this interesting plugin with the Obsidian community.
It would be nice if there is an option to set the fade steps to reproduce something similar to what you have shown to us (https://github.com/skipadu/obsidian-ghost-fade-focus/blob/main/images/focus.png).
Also, it would be easier to use if we can have a quick option to set auto opacity level.
E.g, I can set 10 fade steps, then set the highest and lower opacity, and the program would automatically make opacity spread out equally in 10 lines.
Best,
Jake

Thanks for the feature request!
The screenshot shows the default fade settings. It might be confusing because that has lots of texts on one line (see line numbers) as the plugin is line based.
I try to look that automatical fade spread in later updates.

authors: jakemkc skipadu

repo: skipadu/obsidian-ghost-fade-focus


text:
Improve unit tests

The test coverage is pretty low at the moment. This needs to be improved.

Known limitation:

--filter flag is ignored in exportTranslationKeys
--filter flag cannot be set for generateSchema

https://github.com/skolmer/i18n-tag-schema/tree/next


text:
Update identityserver4 and automapper versions

Upgrades IdentityServer4 from 2.4.0 -> 2.5.0 and AutoMapper from 8.0.0 -> 8.1.1 to satisfy dependency of https://www.nuget.org/packages/IdentityServer4.EntityFramework.Storage/.
Resolves breaking change introduced by AutoMapper between 8.0 and 8.1
https://github.com/AutoMapper/AutoMapper/issues/3117
Fixes issues https://github.com/skoruba/IdentityServer4.Admin/issues/283, https://github.com/skoruba/IdentityServer4.Admin/issues/314
All tests pass and I manually verified that the /Configuration/Clients endpoint functions once again.

Thanks, I will try it. 👍🏼

I will update it asap, currently I am on vacation.
Thanks

I will update it asap, currently I am on vacation.
Thanks

No worries. Enjoy your vacation :)

authors: LobsterBandit StasPerekrestov skoruba


text:
Not availble Reason in QueuePauseAction

Reason is not avaible in QueuePauseAction.

Please feel free to add it and submit a PR

authors: fernandorossato skrusty

repo: skrusty/AsterNET


text:
[ENH] grid and random tuning

The package should include a grid and random tuning utility that can make use of predict_proba and probabilistic metrics already refactored.
This should hopefully be a minor adaptation exercise using the abstractions in sktime.

Closed by #37

repo: sktime/skpro


text:
Update README.md

Settings for ALS3 for a basic AIOC interface to an inexpensive HT

Thanks for the update! I will get back to this PR in the coming weeks

authors: chevybowtie skuep

repo: skuep/AIOC


text:
allows to force scroll view for #187

To accommodate your reluctancy to remove entirely the ViewPagerAndroid, and based on @crozzfire's PR, I've added a property to force ScrollView

Please try version from master. Feedback would be welcome. Hope there won't be bugs.

Thanks, that is indeed working. What pushed you to decide to remove completely the AndroidViewPager in the end?
Also, do you plan on releasing that version?

I looked throw docs and didn't find the reason to keep it. I wan't do get any feedback before releasing.

authors: skv-headless walidvb


text:
Version 4.3.9.33 on PyPI

Hello i'm wondering if there is any reason why 4.3.9.33 version is not on PyPI and 4.2.0.34 released the same day is ?
Expected behaviour
Version 4.3.9.33 is available at PyPI following the links mentionned in release (https://pypi.org/project/opencv-python/, https://pypi.org/project/opencv-python/, etc.)
Actual behaviour
Version 4.3.9.33 is not available
Steps to reproduce
Go to https://pypi.org/project/opencv-python/

Sorry, there was a copy-paste typo in the releases page. The correct version is 3.4.9: https://pypi.org/project/opencv-python/3.4.9.33/
Note that it will not show up as a first entry in PyPi since 3.4.9 is the older branch of OpenCV and will be inserted as a "older" release to the releases list according to semantic versioning practices: https://pypi.org/project/opencv-python/#history
The release numbering follows OpenCV versioning (the last sequential number is just a tag which points to some commit in this repository): https://github.com/opencv/opencv/releases

authors: killzoner skvark

repo: skvark/opencv-python


text:
Syntastic syntax checker in puppet giving error

Not sure if this is related to https://github.com/skwp/dotfiles/issues/590 in any way.
The last couple of days I've gotten a strange error message from Syntastic when running it on a puppet manifest.
syntastic: error: checker puppet/puppet: can't parse version string (abnormal termination?)

I created an issue over at scrooloose/syntastic and realized that I've had a problem in vim for quite a while that might be the cause of this.
Running the following in vim should report my puppet version:
:echo system('puppet --version 2>/dev/null')

It doesn't, it just returns:
Command terminated

The guy over at syntastic says it's either shell or vim related. And if I change my shell to /bin/sh, instead of zsh, it works.
He says:

Well, Command terminated is an unusual condition, and I have no idea what it actually means on your OS. Also, the environment variable SHELL is not supposed to take precedence over Vim's option shell. Both of these point to problems in your Vim.
Syntastic relies heavily on system() working properly, and should (re-)start working once your system() does. I'm not sure what else I could tell you. shrug

I'm not familiar enough with the internals of vim, and I know that you guys are not vim support - but you are more familiar with the combination OS X/zsh/vim and its plugins.
Any thoughts?

It might be rvm-related:
:echo system('puppet --version')
Command terminated
dyld: lazy symbol binding failed: Symbol not found: _rb_ary_new_from_values
  Referenced from: /Users/jonasb/.rvm/gems/ruby-2.1.1/gems/psych-2.0.6/lib/psych.bundle
  Expected in: flat namespace

dyld: Symbol not found: _rb_ary_new_from_values
  Referenced from: /Users/jonasb/.rvm/gems/ruby-2.1.1/gems/psych-2.0.6/lib/psych.bundle
  Expected in: flat namespace

Press ENTER or type command to continue

I'll investigate further.

Uninstalling the complaining gem, psych-2.0.6 did solve all problems. Both the command terminated and the abnormal termination

repo: skwp/dotfiles


text:
Add in the Japanese translations to the release branch.

Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Run the unit tests with gradlew app:connectedGmsDebugAndroidTest to make sure you didn't break anything (with an emulator running or phone connected)

[ ] If you have multiple commits please combine them into one commit by squashing them.

Note you may see the Cirrus CI system failing on your PR. It's pretty flaky right now so don't
be alarmed.

Seems likely.  Looks like it has Polish changes in here too.  Since I started this back in January I cannot remember for the life of me what it was for.

repo: sky-map-team/stardroid


text:
Cross-compile go binaries outside docker builds

Cross-compile Go binaries outside Docker containers. This speeds up Docker builds and therefore integration tests significantly.

ok to test

ok to test

ok to test

repo: sky-uk/kfp-operator


text:
[Feature Request] Shared 'popular' prompts + Library/Log + Export features.

There's a few chrome extensions that have some of these features. I'm trying to implement it w/ WebViews+Flutter but not really a mobile dev. This app is pretty sleek so would be cool to add these features.

Hey @patrickcurl, sorry for the delayed response. I think one of my great colleagues @Nash0x7E2 may have a similar solution to this. Any idea for this? 😄

Hey @patrickcurl, this blog post may be of interest to you https://getstream.io/blog/build-flutter-chrome-extension/

authors: Nash0x7E2 patrickcurl skydoves

repo: skydoves/chatgpt-android


text:
Error 403

when I test or submit the program, it returns error:ERROR: HTTP failed:403.
How could I figure it out?

try to login again and run test to see what will happen next

should get rid of this if auto login is enabled. see 3d6e91c

repo: skygragon/leetcode-cli


text:
Closing jadx main window only hides it

If you close the jadx main windows while decompilation is in progress the main windows is just hidden but the decompilation continues which occupies CPU and RAM.
This problem was introduced by PR #543 by changing the DefaultCloseOperation in MainWindow.java from WindowConstants.EXIT_ON_CLOSE to WindowConstants.DO_NOTHING_ON_CLOSE.
For some tests I changed it back to EXIT_ON_CLOSE and did not notice any problems - but I am not an expert of the new project system. @asashour Can you please check if going back to EXIT_ON_CLOSE would be possible without problems?

I would say, the root cause is that cancelBackgroundJobs() doesn't stop the decompilation.
However, there is no harm if we call System.exit() as in the proposed PR.

I have merged that PR, but it is a workaround and root cause must be fixed.
EXIT_ON_CLOSE must be used to close last window and method cancelBackgroundJobs() must be fixed because it is used in other cases like canceling decompilation and opening another file if previous still decompiling.

But EXIT_ON_CLOSE should not be used, because otherwise we will not ask the user to save the project before exiting.
I am definitely with fixing cancelBackgroundJobs()

@skylot According to this article on Stackoverflow.com EXIT_ON_CLOSE is equivalent to calling System.exit(0);

@jpstotz yeah, I already checked sources. But I don't like System.exit(0) in code. Anyway, it is acceptable.
Also, I thought that as soon as we closing window from callback it is possible to stop the propagation of closing event, but it is not true. So @asashour I am sorry for the incorrect statement :(
In result, I think System.exit(0) and DO_NOTHING_ON_CLOSE is ok.

authors: asashour jpstotz skylot

repo: skylot/jadx


text:
component const and non const are generating different ctype/family

Hello,
thanks a lot for sharing this lib!
I just started to use it, and there is a behavior which i found confusing, so i'm curious if it's expected.
here is what i did:
auto entity = registry_.create();
registry_.assign(entity, Position2D(100, 100));
and then in a process
registry_.view().each([](auto entity, auto const & pos){ ... });
From what i read in the doc, I was assuming that it would just access the position, read-only.
Instead the view is empty, because the constness actually generates a different family/ctype, which pool is empty.
Is there anything I'm doing/getting wrong?
thanks a lot in advance,
best regards,
Ju

Dealing with shared libraries?

@skypjack The ASSERT_TRUEs in the call to each aren’t reached in SingleComponentView, ConstNonConstAndAllInBetween because the view is empty. Those really should be static_asserts anyway.

no, all static.
On Sun, Feb 10, 2019 at 12:44 PM Michele Caini notifications@github.com
wrote:

Dealing with shared libraries?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/skypjack/entt/issues/182#issuecomment-462125375, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvaVmr9X5dPFI9M_lyKhoImbWb11IUmks5vMAYdgaJpZM4azAz0
.

@Kerndog73 do you mean this?

@skypjack Yes. Inside the lambda that is passed to each

I see, the same applies here. It seems I forgot a few assigns. :smile:

Ok, tests fixed. No bug detected btw.
@trashuj what you're doing looks a lot like what this test does and it seems to work as expected. In other terms:
entt::registry<> registry;
auto view = registry.view<const my_type>();

registry.assign<my_type>(registry.create());

cview.each([](auto, const auto &instance) {
    // ...
});

The test checks the size of the view (that is correctly returned as 1) and iterates components.
One thing I don't understand in your example is this:
registry_.view().each([](auto entity, auto const & pos){ ... });

Did you mean this instead?
registry_.view<const Position2D>().each([](auto entity, auto const & pos){ ... });

Otherwise, can you copy and paste the actual code, so that I can tell you what's wrong there? Thanks.

Also, I cannot understand why you're saying this:

component const and non const are generating different ctype/family

Almost all the tests would break if this was true. The only way that came to my mind for that is if you create a view as:
registry.view<const my_type &>();

Instead of:
registry.view<const my_type>();

I didn't test it, so I'm not even sure it would compile actually.

yes sorry, bad copy/paste.
I actually created a quick example, and it works fine...
I'm trying to figure out what's wrong in my actual code :(
but removing or adding const gets different results:
auto viewPosConst = registry_.view(); // size 0
auto viewPos = registry_.view(); // size 1
On Sun, Feb 10, 2019 at 1:36 PM Michele Caini notifications@github.com
wrote:

Also, I cannot understand why you're saying this:
component const and non const are generating different ctype/family
Almost all the tests would break if this was true. The only way that came
to my mind for that is if you create a view as:
registry.view<const my_type &>();
Instead of:
registry.view();
I didn't test it, so I'm not even sure it would compile actually.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/skypjack/entt/issues/182#issuecomment-462129116, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvaVtN2b6tVdw6NTUbeLLRYPHdl5Jq7ks5vMBJagaJpZM4azAz0
.

@skypjack That gives me an idea. What if you could do this:
reg.each([](A a, B b) {
  // ...
});

Use the signature of the lambda to construct a standard view and then call each on the view.
Really nothing more than syntax sugar but it's some sweet, sweet sugar don't you think? 😋

@trashuj

but removing or adding const gets different results:
auto viewPosConst = registry_.view<const Position2D>(); // size 0
auto viewPos = registry_.view<Position2D>(); // size 1

Can you provide a full example for this?
The test I linked does exactly the same (creates and entity with a component and creates two views, a non-const one and a const one: both have the same size, 1). The two lines above don't help and I don't manage to reproduce the problem, really.
@Kerndog73
You know you'll ask the same for groups, don't you? :smile:

@trashuj any news on this?
I tried a couple of things but I cannot reproduce the issue and thus I must consider it invalid if you don't come up with a reproducible example.
I'm sorry.

Hi all,
here are my findings so far.
I striped down my project to the minimum (find sources attached).
Here is what i print (in display.cpp)
size_t t = registry_.type();
size_t t2 = registry_.type();
printf("out %u %u\n", t, t2);
size_t tb = registry_.type();
size_t tb2 = registry_.type();
printf("out %u %u\n", tb, tb2);
I tested it on ubuntu/ninja/clang, it works fine (and returns 0 0, 1 1)
but on windows, using Windows10/visual studio 2017 (MSVC 19.16.27024.1), it
prints 0 3, 1 2
Now, couple of things to note.
clang seems to give the proper result (ie 0 and 1).
on windows though, I copy pasted the code above in different modules to see
the results, and the values change.
if i print from game.cpp, it gives me 2 2, 3 3 (and then display.cpp also
prints 2 2, 3 3).
if I comment out the code in game.cpp and print only from display like
above, I get 0 3, 1 2
Also, if I change the lib order in main properties > C++ > input, and link
game lib before the others (and rebuild), I also get 2 2, 3 3.
So I guess I have 2 issues here:

static init order makes a difference
msvc increments both const and non-const identifier in family.hpp, but
"may" end up with consistent results (ie eventually type<> returns the same
value for const and non const)

if any kind soul could give it a try and tell me what the output is, that
would be very helpful.
to build i'm using cmake 3.13.0

copy entt in ext folder
mkdir build
cd build
cmake ..

thanks a lot in advance!
On Mon, Feb 11, 2019 at 7:55 AM Michele Caini notifications@github.com
wrote:

@trashuj https://github.com/trashuj any news on this?
I tried a couple of things but I cannot reproduce the issue and thus I
must consider it invalid if you don't come up with a reproducible example.
I'm sorry.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/skypjack/entt/issues/182#issuecomment-462232741, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvaVtxlcf8CY6IPnRjWZbnBVoNbqvw7ks5vMRPmgaJpZM4azAz0
.

I know I've already asked this, but:

Also, if I change the lib order in main properties

Are you working with multiple libs? Shared ones or whatever? Can you give more details on this?
This is a know problem on Windows that doesn't guarantee inline variables are uniquely identified when linking to shared libraries.
This is also likely the next big step of EnTT, the full support for use with shared libraries on systems where shared libraries are just shitty things that work differently from all the other systems. :smile:
In other terms, support for use across boundaries with dlls. Nothing more, nothing less.

I use only static libs.
main is exe, linking with static libs engine, display and game.
On Mon, Feb 11, 2019 at 10:49 AM Michele Caini notifications@github.com
wrote:

I know I've already asked this, but:
Also, if I change the lib order in main properties
Are you working with multiple libs? Shared ones or whatever? Can you give
more details on this?
This is a know problem on Windows that doesn't guarantee inline variables
are uniquely identified when linking to shared libraries.
This is also likely the next big step of EnTT, the full support for use
with shared libraries on systems where shared libraries are just shitty
things that work differently from all the other systems. 😄
In other terms, support for use across boundaries with dlls. Nothing more,
nothing less.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/skypjack/entt/issues/182#issuecomment-462268741, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvaVmlfguuegsC3DXB4Ys8wcZmkJ9IPks5vMTy-gaJpZM4azAz0
.

Yeah, I reproduced your error with static (and shared) libraries on Windows.
This is a known problem that shows up only on Windows, something to face yet. There are several discussions around if you look at closed issues. :+1:

Can i get away with it by using only non const components for now, or
should i expect more trouble?
Next i'm gonna start using signals and events.
On Mon, Feb 11, 2019, 15:17 Michele Caini <notifications@github.com wrote:

Yeah, I reproduced your error
https://ci.appveyor.com/project/skypjack/entt with static (and shared)
libraries on Windows.
This is a known problem that shows up only on Windows, something to face
yet. There are several discussions around if you look at closed issues. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/skypjack/entt/issues/182#issuecomment-462342843, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvaVvsp2tLnmc_b7djP4g_szCogpINEks5vMXuTgaJpZM4azAz0
.

It's not a problem of const and non const, that's just how you observe it.
The fact is that inline variables aren't guaranteed to be unique across all TU on Windows (and only on Windows apparently) as the standard would mandate instead. Therefore unique identifiers are incorrectly reassigned across boundaries and only across boundaries.
We are discussing a solution these days on gitter (feel free to join us if you want to participate).
The idea is to assign a stable identifier based on compile-time strings, something like this:
struct my_type: shared<"foobar"_hs> { ... }

Of course, there will be a macro available to reduce the boilerplate and use the name of the class as an identifier.
This way, the registry has a direct and indirect access to a component and it can use the latter when you are on the wrong side of a boundary.
Unfortunately I cannot give you a deadline. EnTT is a free time project backed by patrons and donations that so far doesn't allow me to work full-time on it. I'm sorry.

Do you mind if I edit the title of your issue, so that to leave it open and use it to track progresses on this front?
Otherwise I can open another issue if you prefer.

Please go ahead!
Thanks a lot for sharing this lib again, i think it's promising!
On Mon, Feb 11, 2019, 23:26 Michele Caini <notifications@github.com wrote:

Do you mind if I edit the title of your issue, so that to leave it open
and use it to track progresses on this front?
Otherwise I can open another issue if you prefer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/skypjack/entt/issues/182#issuecomment-462520072, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvaVrFGjKfiS_XTXXRNeNesDzBTKt85ks5vMe4egaJpZM4azAz0
.

In the meantime, you can look at the closed issues. Someone already faced the problem and somehow solved it a while ago, but I don't remember how.
Also stay tuned, I'm actively working on it, so I don't think it will take much to have it up and running across boundaries. :+1:

@Kerndog73 it's time to make EnTT the greatest library on all platforms. Can I count you in for help and for a review? :-)

@skypjack Sure. I'll do what I can

This one?
https://github.com/skypjack/entt/issues/113
On Mon, Feb 11, 2019, 23:39 Michele Caini <notifications@github.com wrote:

In the meantime, you can look at the closed issues. Someone already faced
the problem and somehow solved it a while ago, but I don't remember how.
Also stay tuned, I'm actively working on it, so I don't think it will take
much to have it up and running across boundaries. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/skypjack/entt/issues/182#issuecomment-462523537, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvaVqK1ObV1h7-aEiHnxo95c8sAkIFbks5vMfEGgaJpZM4azAz0
.

Yeah, that's one of them. The issue popped out more than once in two years. :-)

I'll close this issue and open a new one dedicated to the problem. There are too many messages here already.

See #186 and feel free to participate. :+1:

authors: Kerndog73 skypjack trashuj

repo: skypjack/entt


text:
Feature/basic UI

Milestone #4 - Basic UI Implementation

In this feature branch, I added the basic-UI, and relationship, between the multiple classes as per the diagram into files and implemented the features for creating the books, rentals, students, and teachers. Details of the features that I have implemented in this branch are as follows:

Created different folders for different files.
Added the feature by using the association's concept.
Implemented the menu
Updated the files by replacing the variable name according to style guide.
Resolved the rubocop linter errors.
Created the app.rb and main.rb
Used the best practices for writing the code in Ruby.
Converted all the variables and method names in SnakeCase as per Ruby Styling Guide.

@MahmoudBakr23 Thank you very much


text:
Use datastore property name instead of hardcoding

Type of change (place an x in the [ ] that applies)

[ ] New sample
[ ] New feature
[ ] Bug fix
[ ] Documentation
[x] improvement

Requirements (place an x in each [ ] that applies)

[x] I’ve checked my submission against the Samples Checklist to ensure it complies with all standards
[x] I have ensured the changes I am contributing align with existing patterns and have tested and linted my code
[x] I've read and agree to the Code of Conduct

Thank you for the speedy review @e-zim!

repo: slack-samples/deno-announcement-bot


text:
I can't get 'event("reaction_added", {..})' to work

Description
Describe your issue here.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[X] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Hello, I'm trying to create a basic Typescript Bolt application, for that I started from the Template provided in the example folder.
The application listens on the following two methods :
app.message("hello", async ({ message, say }) => {
  if (message.subtype === undefined || message.subtype === "bot_message") {
    await say({
      blocs : [...],
      text : `Hey there <@${message.user}>!`,
    }) ;
  }
}) ;

and
app.event("reaction_added", async ({ event, context }) => {
  try {
    // The `event` object contains information about the reaction added
    const { user, reaction, item } = event;

    // Do something with the event data
    console.log(`User ${user} added reaction ${reaction} to item ${item}`);
  } catch (error) {
    console.error(error);
  }
});

When I type "hello" in the general channel of my slack, the method is well executed.
Problem : But when I add reactions I can never get into the hook "reaction_added" ?
Thanks in advance for your help
package version: ^3.3.0
node version: v16.17.0
OS version(s): Mac Ventura 13.0.1
What you expected to happen :
When I add an emoji on a message I expect the "reaction_added" hook code to be executed
Actual result:
Nothing happened, function is not triggered
Attachments:
I tried to add several permissions without success, do I miss something ?
display_information:
  name: MyApp
  description: MyDescription
  background_color: "#000000"
features:
  bot_user:
    display_name: Test
    always_online: true
oauth_config:
  scopes:
    user:
      - reactions:read
    bot:
      - channels:history
      - channels:join
      - channels:read
      - chat:write
      - commands
      - groups:read
      - groups:history
      - im:history
      - im:read
      - mpim:read
      - users:read
      - reactions:read
settings:
  event_subscriptions:
    user_events:
      - reaction_added
    bot_events:
      - message.groups
      - reaction_added
      - message.channels
      - message.im
  interactivity:
    is_enabled: true
  org_deploy_enabled: false
  socket_mode_enabled: true
  token_rotation_enabled: false

Hi @victorlrz, thanks for asking the question!
Your app manifest looks valid, and I made sure that a brand-new app with the settings works without any issues. Please double-check the following points:

your app's bot user must be a member of the channels where reactions can be added
if you added the reaction_added event subscription after the app's initial installation, your app needs to be installed again

I hope this helps.

Hi @seratch,
Thanks a lot for your feedback, I just reinstalled the App and it worked! 🙏

if you added the reaction_added event subscription after the app's initial installation, your app needs to be installed again

But according to slack's description, it seems we are not required to re-install app again if we already own scope in Bot Token Scopes, and the issue for me is that reaction_added seems not reliable, my app sometimes cannot receive such reaction events and we have to react several times

authors: evicxxt seratch victorlrz

repo: slackapi/bolt-js