text:
[scd] Add NotSupported option and coalesce Rejected + ConflictWithFlight

Currently, the scd interface for requesting USS flight planning operations has a "capabilities" endpoint that allows a USS to indicate what capabilities it supports, and then uss_qualifier chooses to skip test components that need unsupported capabilities.  This is somewhat awkward as all variations of all optional capabilities for all tests involving this interface would need to be added to the capabilities result data structure to support this paradigm.
Instead, this PR adds a "NotSupported" option when a requested flight interaction is not supported.  With that possibility, uss_qualifier can simply stop a test scenario if one of the participants is discovered to be unable to support a required action given the full details of that action.  This opens up the number of USS behaviors that can be supported -- for instance, if a USS can support high-priority operations, but only when they originate from specific users, the old/current paradigm does not support that behavior, but the new paradigm would.
This is a backwards-compatible change because a new enum option is added so all previous responses will still validate.  After this behavior is incorporated/supported by uss_qualifier and USSs, the capabilities endpoint can be entirely removed from this API.
As a second change, the ConflictWithFlight option is marked as deprecated as the distinction between Rejected and ConflictWithFlight is not particularly useful, and it does lead to some difficulties (e.g., if a request both contains invalid data and conflicts with another flight, which result should be returned?).  The tests should be constructed to evoke all rejection reasons of interest separately, so having the USS attempt to indicate the "root cause" of a rejection is not necessary.  It will become increasingly important to avoid attempting to differentiate rejection reasons as this API is used for flight planning interactions beyond U-space.
API changes have large, long-lasting impacts, so please provide robust feedback where appropriate :)

NotSupported option
That's a nice idea. Since I started working on the test scenarios, I found the capabilities checks a bit awkward to use correctly. The only downside would be that maybe this change will make the test implementation a bit more complex? Or maybe not, I'm not sure. But in any case this looks like a good change to me, and even with added complexity, it would be worth it :+1:

This is a backwards-compatible change because a new enum option is added so all previous responses will still validate. After this behavior is incorporated/supported by uss_qualifier and USSs, the capabilities endpoint can be entirely removed from this API.

Here I would agree with @barroco : it would be quite a bit easier to assume non-backward compatible changes are acceptable. But then, I don't really have the view of what is the current status of the different USSs implementations and what impact this would have on them.
Coalesce Rejected + ConflictWithFlight
I think that one issue this change could create is that the real reason for rejecting a flight might be hidden and thus induce potentially wrong test results. E.g. an error in configuration of the USS or in the test data used leads to somehow all flight injections being rejected due to incorrect flight auth data, yet we were trying to test for a conflict?
I guess that's probably why initially those two options were created.
This might prove complicated or even impossible, but what would you think of adding some codified reason for the rejection? E.g. with "result": "Rejected", there could be another field ``"rejection_reasons": ["flight_auth", "priority_conflict", ...]`.
While it would certainly be hard to exhaustively enumerate all reasons at first, adding additional possible values can be done while being backward-compatible.

The only downside would be that maybe this change will make the test implementation a bit more complex? Or maybe not, I'm not sure.

I think the change will make things different (some added complexity in some areas, some reduced complexity in others), and on net I think it will actually reduce complexity.  Trying to synchronize "things I need to decide about during the execution of a test" with "USS-announced capabilities" seemed to be difficult, and this basically just eliminates that.

it would be quite a bit easier to assume non-backward compatible changes are acceptable. But then, I don't really have the view of what is the current status of the different USSs implementations and what impact this would have on them.

Agreed, I think we are free to make breaking changes since we are at 0.x.x.  But, some USSs have actually implemented this version of the API, so I think it would be nice to bundle as many breaking changes as practical into a big batch and make them all at once to avoid breaking USSs' existing implementations.  Basically, pretend as if we're already at 1.x.x when practical, and it seemed practical in this case.

I think that one issue this change could create is that the real reason for rejecting a flight might be hidden and thus induce potentially wrong test results. E.g. an error in configuration of the USS or in the test data used leads to somehow all flight injections being rejected due to incorrect flight auth data, yet we were trying to test for a conflict? I guess that's probably why initially those two options were created.
This might prove complicated or even impossible, but what would you think of adding some codified reason for the rejection? E.g. with "result": "Rejected", there could be another field ``"rejection_reasons": ["flight_auth", "priority_conflict", ...]`. While it would certainly be hard to exhaustively enumerate all reasons at first, adding additional possible values can be done while being backward-compatible.

The tricky thing is that a USS should not be required to enumerate all reasons a user flight intent was not granted.  If my implementation verifies flight auth information before checking anything with regard to F3548-21, then I would reject the user flight intent without knowing whether a conflict existed or not.  So, if there was both invalid flight auth data and a conflict, I would report just the invalid flight auth data as the sole rejection reason.  Similarly, if my implementation checked F3548-21 first before validating flight auth information, I would report just the conflict as the sole rejection reason.  Requiring USSs to comprehensively report all reasons for rejection would require them to do something substantially different in their test interface than they would be required to do with their normal users since there is no requirement to tell normal users the comprehensive set of reasons for rejection.  Since we want to avoid imposition of as many additional requirements as possible, we would want to avoid this if possible.  And, we should be able to avoid this if we structure our test data well: we can always tease out whether a rejection is due to X by making everything valid except for X.  If/when we provide a user flight intent with both X and Y invalid, I don't think we should care whether the USS rejected it because of X, because of Y, or because of X and Y.  Therefore, I don't think the rejection reason matters -- just that it was rejected for some reason that wasn't 1) a system error (Failed) or 2) the USS doesn't support comprehension or execution of that (potentially) valid request (NotSupported).

authors: BenjaminPelletier mickmis


text:
vite build ends up with "[intlify] Not found '...' key in '...' locale messages."

Setting up vite with vite-plugin-vue-i18n according to the documentation followed by
npm run dev and navigating to localhost:<port> Will always display "message" and the console tells me
[intlify] Not found 'message' key in 'ja' locale messages.
[intlify] Fall back to translate 'message' key with 'en' locale.
[intlify] Not found 'message' key in 'en' locale messages.

Both in a "full-scale" application and the minimal example below.
Expected behavior
Localized message string.
Reproduction
package.json
{
  "name": "my-project",
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "serve": "vite preview"
  },
  "dependencies": {
    "@heroicons/vue": "^1.0.6",
    "@tailwindcss/forms": "^0.5.2",
    "tailwindcss": "^3.0.24",
    "vue": "^3.2.37",
    "vue-i18n": "^9.1.10"
  },
  "devDependencies": {
    "@intlify/vite-plugin-vue-i18n": "^5.0.0",
    "@vitejs/plugin-vue": "^3.0.0",
    "@vue/cli-service": "^5.0.8",
    "@vue/compiler-sfc": "^3.2.37",
    "autoprefixer": "^10.4.7",
    "postcss": "^8.4.14",
    "vite": "3.0.0",
    "vue-router": "^4.1.2"
  }
}

vite.config.js
import { fileURLToPath, URL } from 'url'
const { defineConfig } = require('vite')
import vue from '@vitejs/plugin-vue'
import vueI18n from '@intlify/vite-plugin-vue-i18n'

export default defineConfig({
  plugins: [
      vue(),
      vueI18n({
        // if you want to use Vue I18n Legacy API, you need to set `compositionOnly: false`
        // compositionOnly: false,
        // include: path.resolve(__dirname, './path/to/src/locales/**')
      })
  ],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('./src', import.meta.url))
    }
  },
})

index.js
import './index.css'
import { createApp } from 'vue'
import { createI18n } from 'vue-i18n'
import App from './App.vue'

const messages = {
    en: {
        message: {
            hello: 'hello world'
        }
    },
    ja: {
        message: {
            hello: 'こんにちは、世界'
        }
    }
}

const i18n = createI18n({
    globalInjection: true,
    locale: 'ja',
    fallbackLocale: 'en',
    messages,
})

const app = createApp(App);
app.use(i18n).mount('#app');

App.vue

<template>

{{ $t('message') }}

</template>

Issue Package
vite-plugin-vue-i18n
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04 LTS 22.04 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
    Memory: 11.71 GB / 14.86 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 18.6.0 - /usr/bin/node
    npm: 8.14.0 - /usr/bin/npm
  Browsers:
    Chromium: 103.0.5060.53
    Firefox: 102.0.1
  npmPackages:
    @intlify/vite-plugin-vue-i18n: ^5.0.0 => 5.0.0
    vite: 3.0.0 => 3.0.0
    vue: ^3.2.37 => 3.2.37
    vue-i18n: ^9.1.10 => 9.1.10

Screenshot
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the README
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.

Fixed it (partially):
The example here https://vue-i18n.intlify.dev/guide/#html is erroneous. It has to be
const messages = {
    en: {
        hello: 'hello world'
    },
    ja: {
        hello: 'こんにちは、世界'
    },
    de: {
        hello: 'hi!'
    },
}

/*
doesn't work

const messages = {
    en: {
        message: {
            hello: 'hello world'
        }
    },
    ja: {
        message: {
            hello: 'こんにちは、世界'
        }
    },
    de: {
        message: {
            hello: 'hi!'
        }
    }
}
*/

const i18n = createI18n({
    globalInjection: true,
    locale: 'ja',
    fallbackLocale: 'en',
    legacy: false,
    messages
})

I haven't tried mixing global and custom blocks, but using only custom blocks is ok  for me.
https://github.com/intlify/bundle-tools/issues/120#issuecomment-1257126108

What if I don't have messages beforehand and get them from API?

source: gharchive/issue

authors: UI-Mario Vectrex folmert

repo: intlify/bundle-tools

license: MIT

license_type: permissive

license_source: github-api


text:
Use bound functions for callbacks

Using anonymous functions in props will cause the child to always re-render since the function is redefined every render. By using a bound function the reference to the function is always the same, avoiding useless re-render.

Thanks for the PR, and taking the time to write it up. Bound methods only avoid a render if the child component implements shouldComponentUpdate which the host (DOM) elements don't so it's not actually saving any work. In this case it's probably better to avoid the etc code and indirection all things being equal :)

source: gharchive/pull-request

authors: MatthewHerbst jquense

repo: intljusticemission/react-big-calendar

license: mit

license_source: bigquery


text:
Support for color blinds

This PR supports better readibility for color blinds.

Codecov Report

Merging #10 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   82.14%   82.14%
=======================================
  Files           2        2
  Lines          28       28
=======================================
  Hits           23       23
  Misses          5        5

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fea8968...61a4e02. Read the comment docs.

authors: codecov-io leopetter


text:
SuperPoint

hi, how can I use the SuperPoint model on ubuntu 22.04 with GPU?
i tried by installing libtorch-dev, but got the error that Caffe2 didn't find libc10

On another project, we used docker to simplify the installation of libtorch.

ah alright, thanks for you quick advice:)

authors: matlabbe philipsgithub

repo: introlab/find-object


text:
npm audit fixes

removing vulnerabilities as suggested by 'npm audit' and updated packages.json

@abisalehalliprasan @rajeshgupta723 can you push a version with this change to NPM? <3

@abisalehalliprasan @rajeshgupta723 can you push a version with this change to NPM? ❤

Thank you @mveytsman, will do soon. Appreciate your patience.

repo: intuit/oauth-jsclient


text:
global: document metadata refactor

removed  one level nesting of _computed, and moved eitems on the root
eitems with total number of eitems and hits with the actual eitems
has_eitems removed from circulation and filters and aggregations point to eitems.total
has_items removed from circulation filters and aggregations point to items.total
items circulation_status property renamed to circulation in alignment with document
closes #324

@equadon I have rebased, but could you please check if everything is right? I could not load the react app correctly, I didn't have the time to check if it is on my machine or there is any other issue. Thanks!

authors: ntarocco topless

repo: inveniosoftware/invenio-app-ils


text:
tests: addition of test cases for API

Signed-off-by: Jiri Kuncar jiri.kuncar@cern.ch

@lnielsen len(deposit)>6 :disappointed: I have changed the pid_type to "dep", but I wonder if we should allow longer names in PIDStore.

Coverage increased (+29.8%) to 83.391% when pulling bd5a7946dd18c2984d4232f9f4c0a6c17aba382a on jirikuncar:api-improvements into f8726d5675f4bf3c6286aec1b67fffa53e8ec365 on inveniosoftware:master.

Coverage increased (+29.8%) to 83.391% when pulling 02496b781d511644b25467a3c4f31e06e76a1d7d on jirikuncar:api-improvements into f8726d5675f4bf3c6286aec1b67fffa53e8ec365 on inveniosoftware:master.

authors: coveralls jirikuncar

repo: inveniosoftware/invenio-deposit


text:
🛑 Keycloak Competence Center is down

In 112b139, Keycloak Competence Center (https://keycloak.ch) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Keycloak Competence Center is back up in ac2fcaa after 5 minutes.

repo: inventage/upptime


text:
Stock status has no tracking history

It would be nice to track when a stock item is destroyed and add a note (much like how a location transfer is tracked at the moment).
This is part of a broader issue (#1056) where one might wish to track any changes to a stock item. @eeintech
and @SchrodingersGat mention django-simple-history as a potential solution.

@SchrodingersGat the package(django-simple-history) itself is great but I have had problems when people restore data. Used as a fancy log it worked fine.
Some stuff to consider:

values in unique fields might be taken again - creating conflicts
if you have a lot of signals in your model restores might start a lot of tasks - in one case that led to data-continuity problems in a multi-user environment, which are hard to debug if your dataflows were not designed to be rolled back in the first place
foreign keys might have changed too, that can lead to very strange problems and tends to be hard to figure out afterwards

All very reasonable points. A good is example is if stock was moved from a location which has now been deleted - there's no way to "undo" that in a single action!
Maybe this is a case of "asking the wrong question". What I am looking to do is refactor the current "stock history" implementation to solve a number of outstanding issues:

Stock "status" changes are not tracked - https://github.com/inventree/InvenTree/issues/1303
Stock history items are not properly translated (you know this one)
Stock history items are not "hyperlinked" - e.g. if you change location, I'd like to be able to click on that location (if that location still exists)

I think that the django-simple-history solution is a fine one here, but maybe it is overkill. Hooking into the signals might also be overbearing, we could potentially extend the current functionality of stock-tracking table to include location foreign keys, and status information...

I mean if you do not plan to restore anything I do not see a problem, then it might be a great + fast solution.
Stock history items would be translated now 👼. How one would implement that with an automatically generated record/table I would have to check. But passing through custom change-messages will be necessary anyway because the defaults do not mean anything to users.

this feature was implemented in #1572
do not @ me in closed issues

I can't get to know from request Stock Item History how to get it working. Could you navigate me how to get into location where overview is? Should I enable any setting to see it? My account is Admin and Superuser, but didn't see.
Sorry for mentioning. I used it because old discusion...

I founded page in Admin->Stock->Stock->Stock item trackings

Is it what you refered? Is there any frontend interface?

@MrShippeR I believe that what you are asking for is already implemented - literally in the screenshot that you shared above. If you think that it is not sufficient, please open a new issue for that.

authors: MrShippeR SchrodingersGat jnewlands matmair

repo: inventree/InvenTree


text:
关于3.0以上版本在net8环境下进入调试后无法查看方法内任何变量对象的问题

Rougamo非常不错！简直太符合我的胃口了，简单明了，功能强大。感谢作者的心血投入。
这几天在做各种测试，目前发现一个问题，全网找来找去，还好找到这里了。
刚刚看了你的3.0版的文章，里面说2.0版本不支持步入调试，3.0以后支持了。
但这和我碰到的问题差别有点大。
我碰到的问题是：在4.0版本下，代码可以正常进入事务，但在具体的方法内部，所有的对象、变量的值均无法查看，调试仍然可以一步一步往下走，但如果各个对象的状态、值看不到，那这个调试就毫无意义。
经过一个版本一个版本测试，发现：3.0以下的版本，可以正常调试，可以看到方法内部所有对象变量的值；但3.0以上，任何版本都不行。
我目前使用的是net8版本。或许我应该试试比如net6或者其他版本？
或者是我某个地方做得不对？但我上述测试均是在最简化条件下测试的结果。
还请赐教，谢谢！
我已提供了最简化的测试代码项目，可直接运行调试，地址如下：
https://gitee.com/hchxxzx/rougamotest

感谢反馈，我研究下，这个问题可能没那么快能解决

已修复，发布了预发版本 4.0.1-preview-1725141430 ，你可以先试试，周一会发布正式版

OK！我马上试试。

可以了！太棒了！谢谢！

authors: hchxxzx inversionhourglass

repo: inversionhourglass/Rougamo


text:
add commonjs module file

Hi, I've just added a file to make it work on npm, if you could push this to https://www.npmjs.com/package/angular-toasty that'd be great, thanks.
Also great work with the plugin, really neat and simple.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Ehesp:x: warrendodsworthYou have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant warrendodsworth

repo: invertase/angular-toasty


text:
.remove() fail to delete items when index < 0

Version: 1.4.0
Though it's not referenced on document, but nagative index seem to be supported according to:
https://github.com/invertase/denque/blob/2a4fb0bc1bef9d84c4b6f2d460c140a776f03ae5/index.js#L215
Minimum steps to reproduce:
q = new Denque()
q.push(1) // 1
q.push(2) // 2
q.push(3) // 3
q.remove(-2,2) // [ 2, 3 ]

q.length // 3

Forgot to reply here sorry, this is fixed and published to npm under version 1.4.1 now. Thanks.

authors: Salakar lrills

repo: invertase/denque


text:
request:  Envied package support for flutter web builds

Is there an existing feature request for this?

[X] I have searched the existing issues.

Description
As a developer I want to use envied package to generate environment variables on build time for my flutter web projects.
Reasoning
I have backend urls and other config values which are different in local and prod and I want to use environment variables to configure them.
Additional context and comments
No response

Did some debugging and the issue was with our gitignore matching code.

authors: codekeyz kaziwaseef

repo: invertase/globe


text:
spec_cli pulls in breaking changes from riverpod

Package spec_cli is failing due to breaking changes from riverpod 2.0.0. This seems to be causing Flame engine's github workflows to fail.
Here is a log: https://github.com/flame-engine/flame/actions/runs/3163297130/jobs/5150721652

I have the same issue.

Logs
NilsMBP13M13:ios nils$ dart pub global activate spec_cli
+ _fe_analyzer_shared 49.0.0.4s)
+ analyzer 5.1.0
+ ansi_styles 0.3.2+1
+ args 2.3.1
+ async 2.9.0
+ boolean_selector 2.1.0
+ charcode 1.3.1
+ cli_util 0.3.5
+ collection 1.16.0
+ conventional_commit 0.4.3+1 (0.5.0 available)
+ convert 3.0.2
+ coverage 1.6.1
+ crypto 3.0.2
+ dart_test_adapter 0.2.0
+ duration 3.0.12
+ file 6.1.4
+ freezed_annotation 1.1.0 (2.1.0 available)
+ frontend_server_client 3.0.0
+ glob 2.1.0
+ graphs 2.1.0
+ http 0.13.5
+ http_multi_server 3.2.1
+ http_parser 4.0.1
+ io 1.0.3
+ js 0.6.4
+ json_annotation 4.7.0
+ logging 1.0.2
+ matcher 0.12.12
+ melos 1.5.2 (2.7.1 available)
+ meta 1.8.0
+ mime 1.0.2
+ mustache_template 2.0.0
+ node_preamble 2.0.1
+ package_config 2.1.0
+ path 1.8.2
+ platform 3.1.0
+ pool 1.5.1
+ pub_semver 2.1.1
+ pubspec 2.3.0
+ quiver 3.1.0
+ riverpod 2.0.0
+ shelf 1.4.0
+ shelf_packages_handler 3.0.1
+ shelf_static 1.1.1
+ shelf_web_socket 1.0.2
+ source_map_stack_trace 2.1.0
+ source_maps 0.10.10
+ source_span 1.9.1
+ spec_cli 0.1.2+2
+ stack_trace 1.10.0
+ state_notifier 0.7.2+1
+ stream_channel 2.1.1
+ string_scanner 1.1.1
+ term_glyph 1.2.1
+ test 1.21.6
+ test_api 0.4.14
+ test_core 0.4.18
+ typed_data 1.3.1
+ uri 1.0.0
+ vm_service 9.4.0
+ watcher 1.0.1
+ web_socket_channel 2.2.0
+ webkit_inspection_protocol 1.2.0
+ yaml 3.1.1
Building package executables... (1.4s)
Failed to build spec_cli:main:
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:148:31: Error: The argument type 'AlwaysAliveRefreshable<StateController<RegExp?>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'RegExp' is from 'dart:core'.
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
    ref.read($testNameFilters.notifier).state = options.testNameFilters.isEmpty
                              ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:153:31: Error: The argument type 'AlwaysAliveRefreshable<StateController<List<String>>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'List' is from 'dart:core'.
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
    ref.read($filePathFilters.notifier).state = options.fileFilters
                              ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:157:27: Error: The argument type 'AlwaysAliveRefreshable<StateController<bool>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
    ref.read($isWatchMode.notifier).state = options.watch;
                          ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:158:25: Error: The argument type 'AlwaysAliveRefreshable<StateController<DateTime>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'DateTime' is from 'dart:core'.
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
    ref.read($startTime.notifier).state = DateTime.now();
                        ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:177:57: Error: The argument type 'AlwaysAliveRefreshable<StateController<List<FailedTestLocation>>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'List' is from 'dart:core'.
 - 'FailedTestLocation' is from 'package:spec_cli/src/dart_test.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
            data: (value) => ref.read(_$lastFailedTests.notifier).state = value,
                                                        ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:178:55: Error: The argument type 'AlwaysAliveRefreshable<StateController<List<FailedTestLocation>>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'List' is from 'dart:core'.
 - 'FailedTestLocation' is from 'package:spec_cli/src/dart_test.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
            loading: () => ref.read(_$lastFailedTests.notifier).state = [],
                                                      ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:180:53: Warning: Operand of null-aware operation '!' has type 'StackTrace' which excludes null.
 - 'StackTrace' is from 'dart:core'.
              Zone.current.handleUncaughtError(err, stack!);
                                                    ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:209:53: Warning: Operand of null-aware operation '!' has type 'StackTrace' which excludes null.
 - 'StackTrace' is from 'dart:core'.
              Zone.current.handleUncaughtError(err, stack!);
                                                    ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:231:30: Error: The getter 'future' isn't defined for the class 'AutoDisposeProvider<AsyncValue<int>>'.
 - 'AutoDisposeProvider' is from 'package:riverpod/src/provider.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/provider.dart').
 - 'AsyncValue' is from 'package:riverpod/src/common.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/common.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'future'.
        ref.listen($exitCode.future, (previous, current) {});
                             ^^^^^^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:234:41: Error: The getter 'future' isn't defined for the class 'AutoDisposeProvider<AsyncValue<int>>'.
 - 'AutoDisposeProvider' is from 'package:riverpod/src/provider.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/provider.dart').
 - 'AsyncValue' is from 'package:riverpod/src/common.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/common.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'future'.
        return await ref.read($exitCode.future);
                                        ^^^^^^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:254:43: Error: The argument type 'Refreshable<StateController<bool>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'Refreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($isEditingTestNameFilter.notifier).state = false;
                                          ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:255:35: Error: The argument type 'AlwaysAliveRefreshable<StateController<RegExp?>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'RegExp' is from 'dart:core'.
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($testNameFilters.notifier).state =
                                  ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:263:43: Error: The argument type 'Refreshable<StateController<bool>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'Refreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($isEditingTestNameFilter.notifier).state = false;
                                          ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:267:44: Error: The argument type 'Refreshable<StateController<String>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'Refreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($editingTestNameTextField.notifier).update((state) {
                                           ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:272:44: Error: The argument type 'Refreshable<StateController<String>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'Refreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($editingTestNameTextField.notifier).state +=
                                           ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:283:29: Error: The argument type 'AlwaysAliveRefreshable<StateController<bool>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($didPressQ.notifier).state = true;
                            ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:288:34: Error: The argument type 'Refreshable<StateController<bool>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'Refreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($showWatchUsage.notifier).state = true;
                                 ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:293:45: Error: The argument type 'AlwaysAliveRefreshable<StateController<bool>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($isRunningOnlyFailingTests.notifier).update((state) => !state);
                                            ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:299:44: Error: The argument type 'Refreshable<StateController<String>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'Refreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($editingTestNameTextField.notifier).state =
                                           ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:301:43: Error: The argument type 'Refreshable<StateController<bool>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'Refreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
        ref.read($isEditingTestNameFilter.notifier).state = true;
                                          ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:312:28: Error: The argument type 'AlwaysAliveRefreshable<TestEventsNotifier>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'TestEventsNotifier' is from 'package:spec_cli/src/dart_test.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
          ref.read($events.notifier).stop();
                           ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:324:23: Error: The argument type 'AlwaysAliveRefreshable<StateController<DateTime>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'DateTime' is from 'dart:core'.
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
  ref.read($startTime.notifier).state = DateTime.now();
                      ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/command_runner.dart:325:41: Error: The argument type 'AlwaysAliveRefreshable<StateController<List<FailedTestLocation>?>>' can't be assigned to the parameter type 'ProviderBase<dynamic>'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'StateController' is from 'package:riverpod/src/state_controller.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/state_controller.dart').
 - 'List' is from 'dart:core'.
 - 'FailedTestLocation' is from 'package:spec_cli/src/dart_test.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart').
 - 'ProviderBase' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
  ref.read($failedTestLocationToExecute.notifier).state =
                                        ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart:31:23: Error: A value of type 'AlwaysAliveRefreshable<Future<List<_Package>>>' can't be assigned to a variable of type 'ProviderOrFamily'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'Future' is from 'dart:async'.
 - 'List' is from 'dart:core'.
 - '_Package' is from 'package:spec_cli/src/dart_test.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart').
 - 'ProviderOrFamily' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
    $filteredPackages.future,
                      ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart:224:31: Error: A value of type 'AlwaysAliveRefreshable<Future<List<_Package>>>' can't be assigned to a variable of type 'ProviderOrFamily'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'Future' is from 'dart:async'.
 - 'List' is from 'dart:core'.
 - '_Package' is from 'package:spec_cli/src/dart_test.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart').
 - 'ProviderOrFamily' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
  dependencies: [$allPackages.future, $filePathFilters],
                              ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/rendering.dart:405:27: Error: A value of type 'AlwaysAliveRefreshable<TestEventsNotifier>' can't be assigned to a variable of type 'ProviderOrFamily'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'TestEventsNotifier' is from 'package:spec_cli/src/dart_test.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart').
 - 'ProviderOrFamily' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
}, dependencies: [$events.notifier]);
                          ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/rendering.dart:412:27: Error: A value of type 'AlwaysAliveRefreshable<TestEventsNotifier>' can't be assigned to a variable of type 'ProviderOrFamily'.
 - 'AlwaysAliveRefreshable' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
 - 'TestEventsNotifier' is from 'package:spec_cli/src/dart_test.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/dart_test.dart').
 - 'ProviderOrFamily' is from 'package:riverpod/src/framework.dart' ('../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/framework.dart').
}, dependencies: [$events.notifier]);
                          ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/provider_utils.dart:17:22: Error: Too few positional arguments: 2 required, 1 given.
    return AsyncError(e.error, stackTrace: e.stackTrace);
                     ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/common.dart:372:9: Context: Found this candidate, but the arguments don't match.
  const AsyncError(Object error, StackTrace stackTrace)
        ^^^^^^^^^^
../../../../../../.pub-cache/hosted/pub.dartlang.org/spec_cli-0.1.2+2/lib/src/provider_utils.dart:21:25: Error: Too few positional arguments: 2 required, 1 given.
    return AsyncError<T>(err, stackTrace: stack);
                        ^
../../../../../../.pub-cache/hosted/pub.dartlang.org/riverpod-2.0.0/lib/src/common.dart:372:9: Context: Found this candidate, but the arguments don't match.
  const AsyncError(Object error, StackTrace stackTrace)
        ^^^^^^^^^^

Dart SDK version: 2.18.2 (stable) (Tue Sep 27 13:24:11 2022 +0200) on "macos_arm64"

I opened a PR to fix this: https://github.com/invertase/spec/pull/30

Running dart pub global activate spec_cli still fails because it uses v0.1.2+2:
dart pub global activate spec_cli
+ _fe_analyzer_shared 49.0.0.3s)
+ analyzer 5.1.0
+ ansi_styles 0.3.2+1
+ args 2.3.1
+ async 2.9.0
+ boolean_selector 2.1.0
+ charcode 1.3.1
+ cli_util 0.3.5
+ collection 1.16.0
+ conventional_commit 0.4.3+1 (0.5.0 available)
+ convert 3.0.2
+ coverage 1.6.1
+ crypto 3.0.2
+ dart_test_adapter 0.2.0
+ duration 3.0.12
+ file 6.1.4
+ freezed_annotation 1.1.0 (2.1.0 available)
+ frontend_server_client 3.0.0
+ glob 2.1.0
+ graphs 2.1.0
+ http 0.13.5
+ http_multi_server 3.2.1
+ http_parser 4.0.1
+ io 1.0.3
+ js 0.6.4
+ json_annotation 4.7.0
+ logging 1.0.2
+ matcher 0.12.12
+ melos 1.5.2 (2.7.1 available)
+ meta 1.8.0
+ mime 1.0.2
+ mustache_template 2.0.0
+ node_preamble 2.0.1
+ package_config 2.1.0
+ path 1.8.2
+ platform 3.1.0
+ pool 1.5.1
+ pub_semver 2.1.1
+ pubspec 2.3.0
+ quiver 3.1.0
+ riverpod 2.0.2
+ shelf 1.4.0
+ shelf_packages_handler 3.0.1
+ shelf_static 1.1.1
+ shelf_web_socket 1.0.2
+ source_map_stack_trace 2.1.0
+ source_maps 0.10.10
+ source_span 1.9.1
+ spec_cli 0.1.2+2 (0.1.3 available)
+ stack_trace 1.10.0
+ state_notifier 0.7.2+1
+ stream_channel 2.1.1
+ string_scanner 1.1.1
+ term_glyph 1.2.1
+ test 1.21.6
+ test_api 0.4.14
+ test_core 0.4.18
+ typed_data 1.3.1
+ uri 1.0.0
+ vm_service 9.4.0
+ watcher 1.0.1
+ web_socket_channel 2.2.0
+ webkit_inspection_protocol 1.2.0
+ yaml 3.1.1

How can I tell dart pub that it should use the new version? It also shows that there is a new version.

authors: nilsreichardt ufrshubham

repo: invertase/spec


text:
🛑 Bitwage API (Sandbox) is down

In d373eb6, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 75 ms

Resolved: Bitwage API (Sandbox) is back up in 5b23f0d after 18 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 86395be, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 322 ms

Resolved: Bitwage API (Sandbox) is back up in 4ee71fd after 44 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 1c04682, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 284 ms

Resolved: Bitwage API (Sandbox) is back up in ca6d8c7 after 37 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 5ed49be, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 103 ms

Resolved: Bitwage API (Sandbox) is back up in 254d96f after 30 minutes.


text:
Bump sonoff to 3.0.3

update confirmed by @GermanBluefox at 6.11.2023 by telegram

3.0.3 created 25.09.2023
1500 user
OK


text:
Easy definition of sanitized substitutions

This PR aims to address issue #264.

I think this PR is ready to merge. Here is an example of what it allows you to do:
layout = (hv.Image(np.random.rand(10,10),
         group=('Spectrum', 'Frequency spectrum'),
         label=('Glucose', '$C_6H_{12}O_6$'))
+ hv.Image(np.random.rand(10,10),
         group=('Spectrum', 'Frequency spectrum'),
         label=('Water', '$H_2O$')))

Now you can select the two parts of the layout conveniently with layout.Spectrum.Glucose or layout.Spectrum.Water while showing the chemical compound names in the title (before you had to use some awkward, auto-generated sanitized string).
To make this less awkward, you can do this using the new Aliases helper function:
al = hv.util.Aliases(Spectrum='Frequency spectrum',
                     Water='$H_2O$',
                     Glucose='$C_6H_{12}O_6$')

(hv.Image(np.random.rand(10,10), group=al.Spectrum,  label=al.Glucose)
+ hv.Image(np.random.rand(10,10), group=al.Spectrum, label=al.Water))

Lastly, the same principles apply setting dimension names using tuples:
im =hv.Image(np.random.rand(10,10),
             kdims=[('Lambda', '$\Lambda$'), ('Joules', 'Energy ($J$)')])

Which now makes methods such as select easier:
im.select(Lambda=(-0.2, 0.2), Joules=(-0.3, 0.3))

Of course you can use the Aliases helper here too!
After I add some tests, I think this is ready to merge and I definitely think it will help scientists (and anyone using LaTeX and special symbols really!) use HoloViews productively.

I've now added unit tests and one they pass, I think it is ready to merge (unless you have any comments!).
It is worth mentioning one limitation of this new system, the group/label/dimension name stays a string (the long string, not the short alias) which means your alias definitions won't be pickled together with the object.
Aliases are defined as dictionaries (the aliases parameter) on the three global functions: hv.util.label_sanitizer, hv.util.group_sanitizer, hv.util.dimension_sanitizer. Restoring your aliases comes down to restoring these dictionaries on these three objects appropriately.

Looks good, very happy to finally have a nice way to specify aliases. Since the tests are passing and I have no specific comments I'll go ahead and merge.

Excellent!  Looks great.

authors: jbednar jlstevens philippjfr

repo: ioam/holoviews


text:
[Bug]: Soundbar Q995GC - Error disconnecting - TypeError: Cannot read properties of null (reading 'socket')

What happened?
I implemented a new Soundbar Samsung Q995GC via Wifi into my network.
I wouldn't use it with iobroker for now but since the soundbar is available in the network my iobroker log is flooded with the follor messages every 5 seconds (see below):
Soundbar Q995GC - Error disconnecting - TypeError: Cannot read properties of null (reading 'socket')
I use chromecast with some other smartspeaker.
I'm not able to disable / ignore this soundbar.
Adapter Version
3.03
JS-Controller Version
4.0.24
Node JS Version
16.20.0
NPM Version
8.19.4
Operating System
Debian
Relevant log output
chromecast.0 | 2023-06-13 17:28:18.773 | info | Soundbar Q995GC - Connected client
chromecast.0 | 2023-06-13 17:28:18.700 | info | Soundbar Q995GC - client disconnected
chromecast.0 | 2023-06-13 17:28:18.699 | error | Soundbar Q995GC - Error disconnecting - TypeError: Cannot read properties of null (reading 'socket')
chromecast.0 | 2023-06-13 17:28:13.694 | info | Soundbar Q995GC - Connected client
chromecast.0 | 2023-06-13 17:28:13.621 | info | Soundbar Q995GC - client disconnected
chromecast.0 | 2023-06-13 17:28:13.620 | error | Soundbar Q995GC - Error disconnecting - TypeError: Cannot read properties of null (reading 'socket')
chromecast.0 | 2023-06-13 17:28:08.616 | info | Soundbar Q995GC - Connected client
chromecast.0 | 2023-06-13 17:28:08.542 | info | Soundbar Q995GC - client disconnected
chromecast.0 | 2023-06-13 17:28:08.541 | error | Soundbar Q995GC - Error disconnecting - TypeError: Cannot read properties of null (reading 'socket')
chromecast.0 | 2023-06-13 17:28:03.538 | info | Soundbar Q995GC - Connected client
chromecast.0 | 2023-06-13 17:28:03.463 | info | Soundbar Q995GC - client disconnected
chromecast.0 | 2023-06-13 17:28:03.462 | error | Soundbar Q995GC - Error disconnecting - TypeError: Cannot read properties of null (reading 'socket')
chromecast.0 | 2023-06-13 17:27:58.459 | info | Soundbar Q995GC - Connected client
chromecast.0 | 2023-06-13 17:27:58.383 | info | Soundbar Q995GC - client disconnected
chromecast.0 | 2023-06-13 17:27:58.383 | error | Soundbar Q995GC - Error disconnecting - TypeError: Cannot read properties of null (reading 'socket')
chromecast.0 | 2023-06-13 17:27:53.379 | info | Soundbar Q995GC - Connected client
chromecast.0 | 2023-06-13 17:27:53.305 | info | Soundbar Q995GC - client disconnected
chromecast.0 | 2023-06-13 17:27:53.305 | error | Soundbar Q995GC - Error disconnecting - TypeError: Cannot read properties of null (reading 'socket')

Anything else?
No response

Issue is still there.
Is it maybe possible to implement a flag to disable a device and prevent new queries from a plugin for that device?

Maybe you can put devices with badly behaved Chromecast implementation on their own subnet or VLAN?

authors: TeraX raintonr


text:
Colors.rgb2hsv is not a function

host.iobrokerPROD | 2024-08-14 19:18:46.212 | error | instance system.adapter.wifilight.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
-- | -- | -- | --
host.iobrokerPROD | 2024-08-14 19:18:46.212 | error | Caught by controller[0]: at processImmediate (node:internal/timers:483:21)
host.iobrokerPROD | 2024-08-14 19:18:46.212 | error | Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11200:62)
host.iobrokerPROD | 2024-08-14 19:18:46.212 | error | Caught by controller[0]: at Object.options.stateChange (/opt/iobroker/node_modules/iobroker.wifilight/lib/dontBeSoSoef.js:1113:21)
host.iobrokerPROD | 2024-08-14 19:18:46.212 | error | Caught by controller[0]: at Object.onStateChange (/opt/iobroker/node_modules/iobroker.wifilight/main.js:150:12)
host.iobrokerPROD | 2024-08-14 19:18:46.212 | error | Caught by controller[0]: at WifiLight.onStateChange (/opt/iobroker/node_modules/iobroker.wifilight/main.js:272:18)
host.iobrokerPROD | 2024-08-14 19:18:46.212 | error | Caught by controller[0]: at WifiLight.bri (/opt/iobroker/node_modules/iobroker.wifilight/main.js:751:24)
host.iobrokerPROD | 2024-08-14 19:18:46.212 | error | Caught by controller[0]: TypeError: Colors.rgb2hsv is not a function
wifilight.0 | 2024-08-14 19:18:45.971 | error | Colors.rgb2hsv is not a function
wifilight.0 | 2024-08-14 19:18:45.971 | error | TypeError: Colors.rgb2hsv is not a function at WifiLight.bri (/opt/iobroker/node_modules/iobroker.wifilight/main.js:751:24) at WifiLight.onStateChange (/opt/iobroker/node_modules/iobroker.wifilight/main.js:272:18) at Object.onStateChange (/opt/iobroker/node_modules/iobroker.wifilight/main.js:150:12) at Object.options.stateChange (/opt/iobroker/node_modules/iobroker.wifilight/lib/dontBeSoSoef.js:1113:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11200:62) at processImmediate (node:internal/timers:483:21)
wifilight.0 | 2024-08-14 19:18:45.971 | error | uncaught exception: Colors.rgb2hsv is not a function
host.iobrokerPROD | 2024-08-14 19:18:30.709 | error | instance system.adapter.wifilight.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobrokerPROD | 2024-08-14 19:18:30.709 | error | Caught by controller[0]: at processImmediate (node:internal/timers:483:21)
host.iobrokerPROD | 2024-08-14 19:18:30.709 | error | Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11200:62)
host.iobrokerPROD | 2024-08-14 19:18:30.709 | error | Caught by controller[0]: at Object.options.stateChange (/opt/iobroker/node_modules/iobroker.wifilight/lib/dontBeSoSoef.js:1113:21)
host.iobrokerPROD | 2024-08-14 19:18:30.709 | error | Caught by controller[0]: at Object.onStateChange (/opt/iobroker/node_modules/iobroker.wifilight/main.js:150:12)
host.iobrokerPROD | 2024-08-14 19:18:30.709 | error | Caught by controller[0]: at WifiLight.onStateChange (/opt/iobroker/node_modules/iobroker.wifilight/main.js:272:18)
host.iobrokerPROD | 2024-08-14 19:18:30.709 | error | Caught by controller[0]: at WifiLight.bri (/opt/iobroker/node_modules/iobroker.wifilight/main.js:751:24)
host.iobrokerPROD | 2024-08-14 19:18:30.709 | error | Caught by controller[0]: TypeError: Colors.rgb2hsv is not a function
wifilight.0 | 2024-08-14 19:18:30.475 | error | Colors.rgb2hsv is not a function
wifilight.0 | 2024-08-14 19:18:30.475 | error | TypeError: Colors.rgb2hsv is not a function at WifiLight.bri (/opt/iobroker/node_modules/iobroker.wifilight/main.js:751:24) at WifiLight.onStateChange (/opt/iobroker/node_modules/iobroker.wifilight/main.js:272:18) at Object.onStateChange (/opt/iobroker/node_modules/iobroker.wifilight/main.js:150:12) at Object.options.stateChange (/opt/iobroker/node_modules/iobroker.wifilight/lib/dontBeSoSoef.js:1113:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11200:62) at processImmediate (node:internal/timers:483:21)

Versions:

Adapter version: 1.3.2
JS-Controller version: 5.0.19
Node version:  20.16.0
Operating system: debian

Ist mir heute auch aufgefallen..

me2

@GermanBluefox  any news ? the Adapter crashs, if the command object is set with r:0, g:0, b:0, on:true, transition:30
otherwise we have to roll back to version 1.2.1, this have the faulty states but don't crashs.. :(

I really do not understand, why function is not a function. without hardware is to hard to reproduce this error.

On other side, there are at least 3 people with hardware and no one could even look into adapter. Very sad

What should I do?

What should I do?

For now: just test the new version 1.3.3
For future, I am recording the video: "How to debug the ioBroker adapter to help the developer". It is possible with ease without any additional tools. Just chrome and CLI (shell)
https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27
cd /opt/iobroker
iob stop wifilight
node --inspect-brk=0.0.0.0 node_modules/iobroker.wifilight/main.js --debug

Add into chrome://inspect your raspberry pi

and then after 10-30 seconds the inspect will appear in the list:

after that set the breakpoint to line main.js:751 and generate the error
Show the developer scopes and in this particular case the value of rgb2hsv

When I start/restart the Instance all Devices set to On=true

When I start/restart the Instance all Devices set to On=true all devices, which are reachable.
When devices will power off for save energy and power will be turned on, then the device is not reachable further on. So I have to restart the instance. It should rescan after a time (10s)?

Sorry I could not understand you. May be "deutsch"?

Mich wundert das dort Colors.rgb2hsv steht ... der Direktimport würde and er Stelle an sich ne andere Meldung verursachen ... das ist mega komisch ... @mcuiobroker Wirklich sicher das die neue version korrekt installiert ist? Korrekter host bei multihost und so? Bitte mal volles Debug log posten bis zu dem Fehler

@mcuiobroker Please check the most recent verison 1.3.3

@GermanBluefox
Wenn ich die Instanz starte oder neu starte  werden alle erreichbaren Geräte eingeschaltet. Die Lichter gehen an. Die zugehörigen on-DPs werden auf true gesetzt -> on=true
Der obige Fehler kommt nicht mehr.
Um Energie zu sparen sind einige LED an einem Power-Switch, so dass sie nicht permanent Strom ziehen. Dort sind auch noch andere Geräte (keine wifilight) mit involviert.
Sind diese Geräte bei Instanzstart nicht an werden sie als reachable false erkannt -> ok
Schalte ich nun den Power-Switch wieder ein, so sind die Wifilight, die eben noch aus waren jetzt an.
Jetzt sollten die wifilight Geräte ja von iobroker erreichbar sein, sind sie aber nicht.
Damit ich sie über iobroker steuern kann, muss ich  die Instanz neu starten.  Sie werden nicht automatisch erkannt (erst nach restart der Instanz) und somit deren reachable auf true gesetzt.
Debug-Log kommt, wenn ich wieder die Möglichkeit habe. Zurzeit Mobil.

@Apollon77 Der obige Fehler wurde ja behoben mit 1.3.3. Es ist nur ein anderes Problem entstanden. Habe es einen Post höher beschrieben.
Zurzeit kann ich kein Log schicken.

Wenn ich die Instanz starte oder neu starte werden alle erreichbaren Geräte eingeschaltet. Die Lichter gehen an. Die zugehörigen on-DPs werden auf true gesetzt -> on=true

Ist dieser Fehler erst mit 1.3.x gekommen oder war der auch in 1.2.2 drin?

Um Energie zu sparen sind einige LED an einem Power-Switch, so dass sie nicht permanent Strom ziehen. Dort sind auch noch andere Geräte (keine wifilight) mit involviert. Sind diese Geräte bei Instanzstart nicht an werden sie als reachable false erkannt -> ok Schalte ich nun den Power-Switch wieder ein, so sind die Wifilight, die eben noch aus waren jetzt an. Jetzt sollten die wifilight Geräte ja von iobroker erreichbar sein, sind sie aber nicht.
Damit ich sie über iobroker steuern kann, muss ich die Instanz neu starten. Sie werden nicht automatisch erkannt (erst nach restart der Instanz) und somit deren reachable auf true gesetzt.
Ist das Gerät bei Instanzstart an und ich schalte es dann durch Power-Switch ab, so wird der reachable nicht geändert, er bleibt weiterhin auf true. Es findet also keine korrekte reachable-Prüfung statt?

Ist dieser Fehler erst mit 1.3.x gekommen oder war der auch in 1.2.2 drin?
Da der Adapter schlecht geschrieben ist (globale variablen, nicht mehr unterstütze Pakete) für mich sehr kompliziert ohne Hardware den Adapter zu pflegen.

Ist erst mit 1.3.3 gekommen.
Soll ich Dir die Hardware zuschicken? Hab aber nur eine Variante (MagicHome) Wifi LED Controller, kein MiLight.

Geräte suchen in der Instanz-Konfiguration -> Fehler

2024-09-03 19:25:24.132 - error: wifilight.0 (63730) uncaught exception: result.include is not a function
--
2024-09-03 19:25:24.133 - error: wifilight.0 (63730) TypeError: result.include is not a function
at Socket. (/opt/iobroker/node_modules/iobroker.wifilight/lib/discovery.js:31:20)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at UDP.onMessage (node:dgram:946:8)
2024-09-03 19:25:24.133 - error: wifilight.0 (63730) result.include is not a function
2024-09-03 19:25:24.137 - error: wifilight.0 (63730) uncaught exception: result.include is not a function
2024-09-03 19:25:24.137 - error: wifilight.0 (63730) TypeError: result.include is not a function
at Socket. (/opt/iobroker/node_modules/iobroker.wifilight/lib/discovery.js:31:20)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at UDP.onMessage (node:dgram:946:8)
2024-09-03 19:25:24.137 - error: wifilight.0 (63730) result.include is not a function
2024-09-03 19:25:24.138 - error: wifilight.0 (63730) uncaught exception: result.include is not a function
2024-09-03 19:25:24.138 - error: wifilight.0 (63730) TypeError: result.include is not a function
at Socket. (/opt/iobroker/node_modules/iobroker.wifilight/lib/discovery.js:31:20)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at UDP.onMessage (node:dgram:946:8)
2024-09-03 19:25:24.139 - error: wifilight.0 (63730) result.include is not a function
2024-09-03 19:25:24.139 - error: wifilight.0 (63730) uncaught exception: result.include is not a function
2024-09-03 19:25:24.139 - error: wifilight.0 (63730) TypeError: result.include is not a function
at Socket. (/opt/iobroker/node_modules/iobroker.wifilight/lib/discovery.js:31:20)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at UDP.onMessage (node:dgram:946:8)
2024-09-03 19:25:24.139 - error: wifilight.0 (63730) result.include is not a function
2024-09-03 19:25:24.141 - info: wifilight.0 (63730) terminating
2024-09-03 19:25:24.141 - warn: wifilight.0 (63730) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[0]: TypeError: result.include is not a function
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.wifilight/lib/discovery.js:31:20)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[0]: at Socket.emit (node:events:519:28)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[0]: at Socket.emit (node:domain:488:12)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[0]: at UDP.onMessage (node:dgram:946:8)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[1]: TypeError: result.include is not a function
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/iobroker.wifilight/lib/discovery.js:31:20)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[1]: at Socket.emit (node:events:519:28)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[1]: at Socket.emit (node:domain:488:12)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[1]: at UDP.onMessage (node:dgram:946:8)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[2]: TypeError: result.include is not a function
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[2]: at Socket. (/opt/iobroker/node_modules/iobroker.wifilight/lib/discovery.js:31:20)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[2]: at Socket.emit (node:events:519:28)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[2]: at Socket.emit (node:domain:488:12)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[2]: at UDP.onMessage (node:dgram:946:8)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[3]: TypeError: result.include is not a function
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[3]: at Socket. (/opt/iobroker/node_modules/iobroker.wifilight/lib/discovery.js:31:20)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[3]: at Socket.emit (node:events:519:28)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[3]: at Socket.emit (node:domain:488:12)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD Caught by controller[3]: at UDP.onMessage (node:dgram:946:8)
2024-09-03 19:25:24.436 - error: host.iobrokerPROD instance system.adapter.wifilight.0 terminated with code 1 (JS_CONTROLLER_STOPPED)

fixed in 1.3.5, well done!

Bleibt noch das Problem mit den "destroy" Clients. Einmal gelöschte Clients / IPs werden nach Einschalten (Power-Switch) nicht erfasst. -> Man muss die Instanz neu starten.

EDIT: Es werden die LEDs jetzt nicht mehr geschaltet.

Ich habe wirklich nichts diesbezüglich getan

bei mir funktioniert alles bestens, mit 1.3.5.
Sogar, wenn mit der App geschaltet wird, wird der Status von PowerON nach max 30sec aktualisiert, das gabs vorher ja nie.
Hier meine Devices (gibt ja verschiedene Hardware) mit den Ports:

Habe jetzt nochmal von 1.2.2 NPM-Update gemacht. Jetzt läuft es. Komisch.
Problem ist aber nachwievor, dass man die Instanz neu starten muss für die devices, die man stromlos geschaltet hatte und wieder einschaltet.
Und der ack wird anscheinend nicht immer gesetzt?

Ich habe wifilight ziemlich umgeschrieben.
Bitte v2.0.0 ausprobieren

Da kommt dann dies. Adapter bleibt rot

2024-09-05 15:19:01.920 - info: host.iobrokerPROD instance system.adapter.wifilight.0 started with pid 704570
--
2024-09-05 15:19:02.371 - info: wifilight.0 (704570) starting. Version 2.0.0 (non-npm: iobroker-community-adapters/ioBroker.wifilight) in /opt/iobroker/node_modules/iobroker.wifilight, node: v20.17.0, js-controller: 5.0.19
2024-09-05 15:19:02.487 - error: wifilight.0 (704570) uncaught exception: akt.cmd.eq is not a function
2024-09-05 15:19:02.487 - error: wifilight.0 (704570) TypeError: akt.cmd.eq is not a function
at WifiLight.exec (/opt/iobroker/node_modules/iobroker.wifilight/main.js:784:52)
at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.wifilight/main.js:791:55)
at listOnTimeout (node:internal/timers:581:17)
at processTimers (node:internal/timers:519:7)
2024-09-05 15:19:02.487 - error: wifilight.0 (704570) akt.cmd.eq is not a function
2024-09-05 15:19:02.493 - error: wifilight.0 (704570) uncaught exception: akt.cmd.eq is not a function
2024-09-05 15:19:02.493 - error: wifilight.0 (704570) TypeError: akt.cmd.eq is not a function
at WifiLight.exec (/opt/iobroker/node_modules/iobroker.wifilight/main.js:784:52)
at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.wifilight/main.js:791:55)
at listOnTimeout (node:internal/timers:581:17)
at processTimers (node:internal/timers:519:7)
2024-09-05 15:19:02.493 - error: wifilight.0 (704570) akt.cmd.eq is not a function
2024-09-05 15:19:02.494 - info: wifilight.0 (704570) terminating
2024-09-05 15:19:02.494 - warn: wifilight.0 (704570) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[0]: TypeError: akt.cmd.eq is not a function
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[0]: at WifiLight.exec (/opt/iobroker/node_modules/iobroker.wifilight/main.js:784:52)
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[0]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.wifilight/main.js:791:55)
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[0]: at listOnTimeout (node:internal/timers:581:17)
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[0]: at processTimers (node:internal/timers:519:7)
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[1]: TypeError: akt.cmd.eq is not a function
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[1]: at WifiLight.exec (/opt/iobroker/node_modules/iobroker.wifilight/main.js:784:52)
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[1]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.wifilight/main.js:791:55)
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[1]: at listOnTimeout (node:internal/timers:581:17)
2024-09-05 15:19:02.727 - error: host.iobrokerPROD Caught by controller[1]: at processTimers (node:internal/timers:519:7)
2024-09-05 15:19:02.727 - error: host.iobrokerPROD instance system.adapter.wifilight.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2024-09-05 15:19:02.727 - info: host.iobrokerPROD Restart adapter system.adapter.wifilight.0 because enabled
2024-09-05 15:19:32.762 - info: host.iobrokerPROD instance system.adapter.wifilight.0 started with pid 704703
2024-09-05 15:19:33.209 - info: wifilight.0 (704703) starting. Version 2.0.0 (non-npm: iobroker-community-adapters/ioBroker.wifilight) in /opt/iobroker/node_modules/iobroker.wifilight, node: v20.17.0, js-controller: 5.0.19
2024-09-05 15:19:33.354 - error: wifilight.0 (704703) uncaught exception: akt.cmd.eq is not a function
2024-09-05 15:19:33.354 - error: wifilight.0 (704703) TypeError: akt.cmd.eq is not a function
at WifiLight.exec (/opt/iobroker/node_modules/iobroker.wifilight/main.js:784:52)
at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.wifilight/main.js:791:55)
at listOnTimeout (node:internal/timers:581:17)
at processTimers (node:internal/timers:519:7)
2024-09-05 15:19:33.355 - error: wifilight.0 (704703) akt.cmd.eq is not a function
2024-09-05 15:19:33.360 - info: wifilight.0 (704703) terminating
2024-09-05 15:19:33.360 - warn: wifilight.0 (704703) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-09-05 15:19:33.558 - error: host.iobrokerPROD Caught by controller[0]: TypeError: akt.cmd.eq is not a function
2024-09-05 15:19:33.559 - error: host.iobrokerPROD Caught by controller[0]: at WifiLight.exec (/opt/iobroker/node_modules/iobroker.wifilight/main.js:784:52)
2024-09-05 15:19:33.559 - error: host.iobrokerPROD Caught by controller[0]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.wifilight/main.js:791:55)
2024-09-05 15:19:33.559 - error: host.iobrokerPROD Caught by controller[0]: at listOnTimeout (node:internal/timers:581:17)
2024-09-05 15:19:33.559 - error: host.iobrokerPROD Caught by controller[0]: at processTimers (node:internal/timers:519:7)
2024-09-05 15:19:33.559 - error: host.iobrokerPROD instance system.adapter.wifilight.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2024-09-05 15:19:33.559 - info: host.iobrokerPROD Restart adapter system.adapter.wifilight.0 because enabled

yes, with V2.0 the same errors: akt.cmd.eq is not a function - back to V1.3.5, everything is fine. (productive system)

Ich habe das gerät jetzt simuliert und konnte den Fehler reproduzieren.
Jetzt sollte laufen

Super, vielen Dank, mit 2.0.1 funktioniert jetzt alles. Beim starten des Adapters hatte ich 3 Devices als offline angezeigt bekommen, wobei davon nur wirklich eins offline war (lt. App). Ich habe die Pollzeit bei den anderen beiden Devices von 30 auf 60 erhoeht, den Adapter neu gestartet, jetzt werden alle (bis auf das eine, was wirklich offline ist) richtig angezeigt.
Habe soweit alle Funktionen getestet, keine Fehler mehr.
Vielen Vielen Vielen Dank !

Bei mir nicht, gleiches Verhalten, wie sonst auch. Ist die Instanz gestartet und einige Geräte sind stromlos, werden diese auch nach Minuten nicht erkannt, wenn man dort den Strom einschaltet.
Auch ein manueller Refresh funktioniert nicht.
Erst nach Restart von der Instanz sind die Geräte als reachable erkannt und können geschaltet werden.

@mcuiobroker
Da as Issue schin geschlossen wurde und eigentlich "Colors.rgb2hsv is not a function" betrifft, wär es ev. sinnvoll ein neues Issue mit deinem Problem anzulgen - incl der bei dir im Einsatz befindlichen Versionen und einem DEBUG Log. Alternativ kannst du natürlich auch warten ob sich @GermanBluefox hier nochmals dazu meldet.

Kann ich machen, aber ich hatte das Problem auch schon 3x hier erwähnt. Er kennt es.

Jep - deswegen hab ich auch geschrieben dass du auch gerne auf eine Reaktion von BF hier warten kannst. Wenn nix in den nächsten Tagen kommt, dann schlage ich eher ein neues Issue vor, da die geclosten später niemand mehr durchsieht. Hoff auch dein Problem wird rasch gefixed mit dem rewrite des Museums Adapter hat BF ja schon mal tolle Arbeit geleistet und das Ding wartbar gemacht. DANKE @GermanBluefox


text:
Scroll doesn't work on  angular material dialog

create a mdDialog ( angular material  dialog), and apply ng-scrollbar to it .
only default browser scroll will work

+1

+1

@iominh is there any update around this issue?

authors: No6things ayZagen rochejul sangramjagtap

repo: iominh/ng-scrollbars


text:
[v4]: Virtual scroll + infinite scroll not working

Bug Report
Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.
Ionic:

   ionic (Ionic CLI)          : 4.0.0 (/usr/local/lib/node_modules/ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.0
   @angular-devkit/core       : 0.7.0-rc.3
   @angular-devkit/schematics : 0.7.0-rc.3
   @angular/cli               : 6.0.8
   @ionic/ng-toolkit          : 1.0.0
   @ionic/schematics-angular  : 1.0.0

System:

   NodeJS : v10.6.0 (/usr/local/bin/node)
   npm    : 6.1.0
   OS     : macOS High Sierra

Describe the Bug
Trying to have an infinite scroll along with virtual scroll. After loading additional data, the virtual scrol is unable to scroll further and it stops with the initially loaded data. new data is not getting appended. Tried the same code without virtual scroll, it worked as expected.
Steps to Reproduce
Related Code
<ion-content padding>

  <ion-virtual-scroll [items]="data" approxItemHeight="320px">
    <ion-card *virtualItem="let item; let itemBounds = bounds;">
      <ion-card-header>
        <ion-card-title>{{ item }}</ion-card-title>
      </ion-card-header>
    </ion-card>
  </ion-virtual-scroll>

  <ion-infinite-scroll (ionInfinite)="doInfinite($event)">
    <ion-infinite-scroll-content></ion-infinite-scroll-content>
  </ion-infinite-scroll>

</ion-content>

Angular code
import { Component,ViewChild } from '@angular/core';
import {InfiniteScroll} from '@ionic/angular'

export class HomePage {
  @ViewChild(InfiniteScroll) infiniteScroll: InfiniteScroll;
   data = [];

  doInfinite(event) {
    console.log("loadData came");
    setTimeout(function() {
      let start = this.data.length;
      let end = this.data.length + 10 ;
      console.log("start: ",start,"end: ",end);
      for(let i=start;i<end;i++){
        this.data.push(i+1);
      }
      console.log('Done');
      event.target.complete();
    }.bind(this), 2000);
  }
}

Expected Behavior
expected scrolling with new appended items.
Additional Context
List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to fix, Stack Overflow links, forum links, screenshots, OS if applicable, etc.

It seems like VirtualScroll doesn't currently update the height of the virtual list when the data set is changed, hence no ability to scroll beyond the initial data set.  This is a virtual scroll specific problem and not related to infinite scroll or the combination.
To try it you can just create a simple array with enough items to fill more than the screen height, display it as a virtual scroll list and on a timer add new items to the end of the array.  You can't scroll past more than the height of the original items.

@manucorporat this is still present in Beta12

I've slightly modified above code and its working fine for me:

preloading data within the constructor
calling checkEnd() on IonVirtualScroll element after new data has been pushed

import { Component, ViewChild } from '@angular/core';
import { IonInfiniteScroll, IonVirtualScroll } from '@ionic/angular';

@Component({
  selector: 'app-home',
  template: `
    <ion-content padding>
      <ion-virtual-scroll [items]="data" approxItemHeight="320px">
        <ion-card *virtualItem="let item; let itemBounds = bounds;">
          <ion-card-header>
            <ion-card-title>{{ item }}</ion-card-title>
          </ion-card-header>
        </ion-card>
      </ion-virtual-scroll>

      <ion-infinite-scroll (ionInfinite)="doInfinite($event)">
        <ion-infinite-scroll-content></ion-infinite-scroll-content>
      </ion-infinite-scroll>
    </ion-content>
  `
})
export class HomePage {

  @ViewChild(IonInfiniteScroll) infiniteScroll: IonInfiniteScroll;
  @ViewChild(IonVirtualScroll) virtualScroll: IonVirtualScroll;
  data = [];

  constructor( ) {
    // prefill list with data
    this.doInfinite(null);
  }

  doInfinite(event) {
    console.log('loadData came');
    setTimeout(() => {
      const start = this.data.length;
      const end = this.data.length + 20;
      console.log('start: ', start, 'end: ', end);
      for (let i = start; i < end; i++) {
        this.data.push(i + 1);
      }
      console.log('Done', this.data);
      this.virtualScroll.checkEnd();
      this.infiniteScroll.complete();
    }, 2000);
  }
}

@felly your code should be the example text in the docs it works well.

Did something change?
I tried to use  this.virtualScroll.checkEnd(); but with no luck.
Fortunately there is no need for that.
I have this in my component:
`

<ion-virtual-scroll [items]="loadedPatients$ | async" approxItemHeight="40px">
<ion-item *virtualItem="let item">
{{ item.first_name }} {{ item.middle_name }} {{ item.last_name }}

  <ion-infinite-scroll threshold="100px" (ionInfinite)="loadData($event)">
    <ion-infinite-scroll-content
      loadingSpinner="bubbles"
      loadingText="Loading more data...">
    </ion-infinite-scroll-content>
  </ion-infinite-scroll>
</ion-card-content>

`
I am using the async pipe because the items are loaded from NgRx store like this:     this.loadedPatients$ = this.store.pipe(select(fromPatient.getAllPatients));
Data is loaded like this:
loadData(event) {     this.store.dispatch(PatientsActions.loadMorePatients({         sort: 'first_name.middle_name.last_name',         order: 'ASC',         limit: 100,         deleted: this.toShow,         filter: this.filterValue ? this.filterValue : null,         event: event,     }));   }
where 'event' is the infinite scroll event and I am passing it to the Effect so I can call .complete() there:
`loadMore$ = createEffect(() =>
this.actions$.pipe(
ofType(PatientsActions.loadMorePatients),
withLatestFrom(
this.store.select(fromPatient.getPagination),
this.store.select(fromPatient.getAllPatients)
),
exhaustMap(([action, pagination, patents]) => {
if (action.event) {
action.event.target.complete();
        if (patents.length === pagination.rowCount) {
            action.event.target.disabled = true;
        }
      }
      const options = {
        ...action,
        page: pagination.page + 1
      };
      return this.patientsService
          .fetchPatients({ ...options })
          .pipe(
              map((result) => PatientsActions.LoadMorePatientsSuccess({ patients: result.patients, pagination: result.pagination })),
              catchError((err) => of(PatientsActions.LoadPatientsFail({ err: err })))
          );
    })
)

);`
and that's basically it. It works as intended but when I try to pass the virtual scroll element and call this.virtualScroll.checkEnd(); in the effect (not with this.virtualSroll ofcouce) there are all kinds of errors...

If your have an async call back remove any timers and use this.virtualScroll.checkEnd() inside an async/await function.

authors: Kaai141 Ross-Rawlins faraazc felly ghenry22 sapabg

repo: ionic-team/ionic


text:
[ionic 4.0.2] list item icon direction on iOS mode in rtl is opposit

list item icon direction on iOS mode in RTL is opposite
look this:

Still an issue with beta.17. My current workaround is at template level because I didn't find a way to hack the CSS:
component
public detailIcon;

constructor() {
  this.detailIcon = document.dir === 'rtl' ? 'ios-arrow-back' : 'ios-arrow-foward';
}

template
<ion-list>
  <ion-item [detailIcon]="detailIcon">...</ion-item>
</ion-list>

authors: HalwestRasul abennouna


text:
[4.0.0-beta.7] [Toast] dismiss function doesn't pass data and role data to onDidDismiss

Bug Report
Ionic Info
Ionic:

   ionic (Ionic CLI)          : 4.1.1 (/home/linuxbrew/.linuxbrew/lib/node_modules/ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.7
   @angular-devkit/core       : 0.7.5
   @angular-devkit/schematics : 0.7.5
   @angular/cli               : 6.1.5
   @ionic/ng-toolkit          : 1.0.8
   @ionic/schematics-angular  : 1.0.6

System:

   NodeJS : v10.7.0 (/home/linuxbrew/.linuxbrew/Cellar/node/10.7.0/bin/node)
   npm    : 6.4.1
   OS     : Linux 4.17

Describe the Bug
When a Toast message gets dismissed the ondidDismiss() data and role properties are both undefined. But they're passed into it
Steps to Reproduce
Steps to reproduce the behavior:
Simply create a Toast message, present it and call the onDidDismiss() Method.
const toast = await this.toastCtrl.create({
  message: 'A new version is available',
  showCloseButton: true,
  position: 'bottom',
  closeButtonText: 'Update'
});

toast.present();

const dismiss = await toast.onDidDismiss();
console.log('Dismissed toast', dismiss);
if(dismiss.role === 'close') {
  console.log('Close button pressed!');
}

Related Code
Sample project can be found here: GitHub.
Important code is in home.ts
Expected Behavior
When the toast gets dismissed should at least the role parameter be set. E.g. when it gets dismissed automatically (duration) it can be set to 'automatic'. When closing via the close Button 'close'.
So we can perform some action based on whether the user clicked the button or not. E.g. reload the page to update the service worker.
Additional Context
I guess the issue can be fixed in the toast.tsx file
The dismiss has both arguments (data and role) but when it gets called none are passed. (Also the button doesn't pass anything)

I believe this is also affection onDidDismiss for both loading and modal components.  Related, is the fact that onDidDismiss should take a callback as a parameter in each case.  However, between beta5 and beta7, we see this for each:
'onDidDismiss': () => Promise<OverlayEventDetail<any>>;

where it used to be
'onDidDismiss': (callback?: ((detail: OverlayEventDetail<any>) => void) | undefined) => Promise<OverlayEventDetail<any>>;

The comment states that it should accept a callback.

@TheAppField I'm not sure, but maybe await toast.present(); instead of just toast.present();  works?

@russcarver
I guess you're right. I've already tried to implement a modal  to select one item and it seems like, there are also some events missing.
@doender
await toast.present(); is just waiting for showing the toast. Not dismissing.
Therefore it will immediately fire after the toast has shown up (not dismissed!)

@russcarver The following works:
const toast = await toastCtrl.create(...
toast.onDidDismiss().then(callback);

authors: TheAppField doender mhashmi russcarver


text:
Release 4.1.0

Release 4.1.0

application close button ??


text:
Kotlinx serialization support

A support library that contains bignum serializers. Needs to be separate as KotlinX Serialization doesn't support Linux ARM and MinGW x86 targets, and also JS legacy build errors out so it's not included in the library. This addresses #170 and #181.

Hey. Are there any docs for this? Should I use it like this?
@Serializable
class example() {
  val number: ByteArraySerializable = 0.toBigInteger()
}

This gives an error:
@Serializable
class example() {
  val number: BigInteger = 0.toBigInteger()
}

Serializer has not been found for type 'BigInteger'. To use context serializer as fallback, explicitly annotate type or property with @Contextual

authors: ionspin jQrgen

repo: ionspin/kotlin-multiplatform-bignum


text:
php warnings on about page

There are 16 php warnings on the about page:

resolved itself

authors: skanda-vasishta superjai

repo: ioos/sanctuarywatch


text:
[Bug]: All information icons open the same popup

Issue description
All information icons open the same popup describing messages instead of opening a popup describing the concept it is next to.
Expected behaviour
Open popup describing the concept it is next to. i.e. if it is next to address, then the popup should describe addresses.
Actual behaviour
All icons open popup about messages.
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
No response
Errors
No response
Duplicate declaration

[X] I have searched the issues tracker for this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Duplicate of #124

authors: laumair nicole-obrien

repo: iotaledger/explorer


text:
network disconnected

Issue description
When I open the Firefly wallet, I receive directly an error message "Netzwerk nicht verbunden" (it is in german), and I see that the network is disconnected.
Firefly version
1.3.0
OS details
Windows 10 Pro
Can the issue be reliably reproduced?
Yes
Steps to reproduce the issue
1.Start the Software
2.
3.
...
Expected behaviour
Solve this issue, I need help
Actual behaviour
Solve this issue, I need help
Errors
Firefly v1.3.0
Sprache: de
Währung: EUR
Node-Auswahl: Manuell
Plattform: win32
Plattformversion: 10.0.19044
Plattform-Architektur: x64
CPU-Anzahl: 16
Gesamtspeicher: 16304.8 MB
Freier Speicher: 9900.7 MB

This is not a bug with firefly, the network is currently not issues new milestones. Please follow official IOTA channels to be notified when this issue is resolved. https://twitter.com/iota/status/1476126255506501632?s=20

authors: DerKranke nicole-obrien

repo: iotaledger/firefly


text:
[Task]: Add QR code popup

Task description
Add viewable QR code when clicking on the icon inside the Network Card
Requirements
TBD
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Blocked, because we're missing the designs.


text:
[Bug report]: whitescreen when deleting profile

Platform
Desktop
Version
1.7.1
Description
Firefly whitescreen after deleting one profile.
I have more than one profile. dont know if this happens if the deleted profile was the only profile in firefly.
I am not sure about the staking part right know.
Expected behaviour
no whitescreen
Actual behaviour
whitescreen
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
log in profile and delete it
Operating System
Windows
Diagnostics
No response
Developer Profile
No
Profile Type
Software (Stronghold)
Staking
None
Crash Status
White screen
Error Messages
No response
Error Logs
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey @sl00k, we have recently launched the new Firefly IOTA (latest version is v2.0.2 at the moment of writing this). Do you mind giving it a try and letting us know if this issue still happens? :smile:
Thank you :v:

I did a simple test
create new profile and delete it.
seems to be fixed


text:
INativeToken rename

Description
Had to stay the same name in develop for compatibility, should be renamed in 2.0.

Closed by https://github.com/iotaledger/iota-sdk/pull/1967

repo: iotaledger/iota-sdk


text:
Add IRC27 and IRC30 metadata utilities

Description of change
This PR adds two kinds of NFT Immutable Metadata schemas. These can be created and used directly as a MetadataFeature in the immutable features of an NFT.
Links to any relevant issues
Closes #504
Type of change
Choose a type of change, and delete any options that are not relevant.

Enhancement (a non-breaking change which adds functionality)

How the change has been tested
I added tests for serialization, and used the metadata in a separate NFT test. However, there is an issue with that test. The input selection returns an Err(InsufficientAmount { found: 302000, required: 490500 }) when it should return UnfulfillableRequirement.

The test probably fails because the new metadata is smaller and then there is not enough amount for a remainder output and the amount requirement is just checked before. I would just revert the changes in this test.
Would be nice to have the examples make use of the new types, for example in  https://github.com/iotaledger/iota-sdk/blob/develop/sdk/examples/how_tos/native_tokens/create.rs#L68 and https://github.com/iotaledger/iota-sdk/blob/a3260a4ed7073167b20376077b2b90ecefa5b4e9/sdk/examples/how_tos/nfts/mint_nft.rs#L66

Created #1169 and #1170 to add bindings

authors: Alexandcoats Thoralf-M


text:
Update Milestone Merkle Validation to Chrysalis Pt.2

Rendered
Example Go implementation in wollac/iota-crypto-demo:

Merkle tree computation of message IDs: pkg/merkle/pt2/merkle.go
Example: examples/merkle/pt2

@charlesthompson3 since we are touching those RFCs anyway, it would be great if you could also give it a quick read

@charlesthompson3 since we are touching those RFCs anyway, it would be great if you could also give it a quick read

repo: iotaledger/protocol-rfcs


text:
nmh's work for week 2020-04-20

[x] refresh stats area  https://github.com/iotexproject/iotex-explorer/issues/1274
[ ]  https://github.com/iotexproject/iotex-explorer/issues/1239
[x] https://github.com/iotexproject/iotex-explorer/issues/1291
[x]  https://github.com/iotexproject/iotex-explorer/issues/878
[x] https://github.com/iotexproject/iotex-explorer/issues/1292

#1239 Still waiting for the answer to where can I read that reward pool balance?

closed for https://github.com/iotexproject/iotex-explorer/issues/1297

repo: iotexproject/iotex-explorer


text:
Unable to unlock desktop wallet with mnemonic phrase

Installed ioTex desktop wallet on 10 year old laptop.  Although I created a password and saved mnemonic phrase, foolishly did not save Keystore File or Private Key.  Transferred ioTex crypto to wallet for the purpose of staking.  Exited from wallet.  Attempted to unlock wallet the next day using mnemonic phrase but no response.  I installed wallet on 2013 laptop and am able to unlock wallet with mnemonic phrase successfully.  Is there any hope I can unlock the first wallet?

No response so I closed the issue


text:
🛑 备用KMS激活服务器 01 is down

In db49923, 备用KMS激活服务器 01 (s01.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 83924e5 after 1 minute.

repo: iougemini/ikms-uptime


text:
🛑 备用KMS激活服务器 01 is down

In a4cb581, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 15d9edc after 24 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In 5e5eb74, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 23143af after 21 minutes.


text:
elf: improve tests

Try to test all the elf functionality.

Thanks!

authors: iaguis schu

repo: iovisor/gobpf


text:
2019-04-01T09:46:39.098Z error: Error: 36:68: execution error: “System Events”遇到一个错误：不能获得“login item "IPFS Desktop"”。 (-1728)

2019-04-01T09:46:39.098Z error: Error: 36:68: execution error: “System Events”遇到一个错误：不能获得“login item "IPFS Desktop"”。 (-1728)
macOS report this error. and can't use ipfs in the cmd.

@poseidonplan please ignore the error.
IPFS will be available on cmd on the next version ;)

authors: hacdias poseidonplan

repo: ipfs-shipyard/ipfs-desktop


text:
[gui error report] SyntaxError: C:\Users\razak.ipfs\config: Unexpected end of JSON input

👉 This error occurs when opening IPFS desktop tool
Specifications

OS: win32
IPFS Desktop Version: 0.20.1
Electron Version: 17.1.0
Chrome Version: 98.0.4758.102

Error
SyntaxError: C:\Users\razak\.ipfs\config: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at Object.readFileSync (G:\IPFS Desktop\resources\app.asar\node_modules\jsonfile\index.js:52:17)
    at readConfigFile (G:\IPFS Desktop\resources\app.asar\src\daemon\config.js:29:13)
    at checkPorts (G:\IPFS Desktop\resources\app.asar\src\daemon\config.js:223:18)
    at module.exports (G:\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:152:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async startIpfs (G:\IPFS Desktop\resources\app.asar\src\daemon\index.js:46:17)
    at async module.exports (G:\IPFS Desktop\resources\app.asar\src\daemon\index.js:114:3)
    at async run (G:\IPFS Desktop\resources\app.asar\src\index.js:83:5)

Continued in https://github.com/ipfs/ipfs-desktop/issues/2050

authors: lidel razakyermal

repo: ipfs/ipfs-desktop


text:
[gui error report] Error: Command failed: powershell.exe -NoProfile -NonInteractive -InputF

👉 Please describe what you were doing when this error happened.
Specifications

OS: win32 10.0.19045
IPFS Desktop Version: 0.31.0
Electron Version: 19.1.9
Chrome Version: 102.0.5005.167

Error
Error: Command failed: powershell.exe -NoProfile -NonInteractive -InputFormat None -Command Get-AuthenticodeSignature -LiteralPath 'C:\Users\jesus\AppData\Local\ipfs-desktop-updater\pending\temp-IPFS-Desktop-Setup-0.32.0.exe' | ConvertTo-Json -Compress | ForEach-Object { [Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($_)) }

    at ChildProcess.exithandler (node:child_process:408:12)
    at ChildProcess.emit (node:events:526:28)
    at maybeClose (node:internal/child_process:1092:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5)

See workaround in https://github.com/ipfs/ipfs-desktop/issues/2335#issuecomment-2161827010

authors: Churrique lidel


text:
Move Kelani's research outputs to this repo

Move Kelani's research outputs to the large volumes directory in this repo (along with any research plans and other process documentation).

Done.
Summary: https://github.com/ipfs/user-research/blob/master/large-volumes/Discovery_Jan-Jun_2018/IPFS-UX_large-volumes_2018-06-26.md
Folder: https://github.com/ipfs/user-research/tree/master/large-volumes/Discovery_Jan-Jun_2018

repo: ipfs/user-research


text:
IS_NUM name conflict with mysql++

In file included from amordad.cpp:46:0:
../common/crow_all.h:2898:0: warning: "IS_NUM"
redefined [enabled by default]
#define IS_NUM(c)           ((c) >= '0' && (c) <=
^
In file included from /usr/include/mysql++/common.h:189:0,
from /usr/include/mysql++/connection.h:38,
from /usr/include/mysql++/mysql++.h:56,
from ../common/EngineDB.hpp:26,
from amordad.cpp:45:
/usr/include/mysql/mysql.h:90:0: note: this is
the location of the previous definition
#define IS_NUM(t) (((t) <= MYSQL_TYPE_INT24 && (t
^

Hmm, we've introduced this issue, because http_parser_merged.h actually undefs this macro but because we further merge into a single .h it become redundant. The obvious but dirty solution would be to just rename the IS_NUM macro, but that's less than ideal, especially considering http_parser is actually lifted from a different project. Does anyone have any ideas?

repo: ipkn/crow


text:
🛑 CounterApi (brochure) is down

In f1fc93a, CounterApi (brochure) (https://counterapi.com/) was down:

HTTP code: 403
Response time: 130 ms

Resolved: CounterApi (brochure) is back up in d81a47c.

repo: iplanwebsites/up


text:
Unblock: Discovery Channel

Channel ID (required)
DiscoveryChannel.fi
Reason (required)
Other
Notes
For some reason the channel is blocked. Please unblock it.

The channel was blocked after an appeal from the rights holder: https://github.com/iptv-org/iptv/issues/1831

authors: freearhey jeirasmus

repo: iptv-org/database

license: Unlicense


text:
https://iptv-org.github.io/epg/guides/us.xml is not populating with info just started to day

Guide
https://iptv-org.github.io/epg/guides/us.xml
Description
I have multiple devices from Firestick 4k max. Mecool km1. Bluestacks running Tivimate. 4.6.1 paid for sub. and only the channels I assigned to the github epg has no information.  other channels from the IPTV services have info  I use Github to fill in the  channels that have missing info from github.  It had  info until a recent epg pull now the those same channels have no info. no error getting to URL but it seems  the UR is doing the same as the old TVTV url was doing. Anyone else?

At the moment both guides are working fine.
https://iptv-org.github.io/epg/guides/us.xml

https://iptv-org.github.io/epg/guides/tr.xml

yes it is working now but yesterday it wasn't for a bit.

authors: freearhey lilchina

repo: iptv-org/epg