FormInput check

Hello,
I've a weird behaviour with switch FormInput;
<FormInput
value={item.isVisible()}
onChange={(e)=>this.onChange('visible', e)}
className={clsInput} type="switch">

=> react told me "main.min.js:6847 Warning: Failed form propType: You provided a checked prop to a form field without an onChange handler. This will render a read-only field. If the field should be mutable use defaultChecked. Otherwise, set either onChange or readOnly.
printWarning @ main.min.js:6847"
It seems that the onChange is not being used by the component.

Ok, after further test, i made a mistake : value doesnt work on a checkbox, i have to use checked property instead.
But there is still a bug (close to #81 ).

{'Afficher'}
this.onChangeVisible(e)}
							className={clsInput} type="switch">

{'Afficher'}

this.onChangeVisible(e)}
								className={clsInput} type="checkbox" />

The second code doesnt work to check the box, the first one with native elements work.


Api.test.ts does not seem to test anything

When I run npm run test I get output like this in the console:
 PASS  test/routing/Api.test.ts
  ● Console

    console.log
      expect(received).toEqual(expected) // deep equality

      - Expected  - 1
      + Received  + 1

      @@ -3,10 +3,10 @@
            0,
            0,
            0,
            0,
          ],
      -   "elevation": false,
      +   "elevation": undefined,
          "import_date": "some_date",
          "profiles": Array [],
          "version": "some_version",
        }

      at src/api/Api.ts:58:33

However, the tests still pass, so it seems like some expectations are not matched, but the test does not fail.
Also when I add a line like throw 'something is wrong in compareRequestBodyAndResolve the tests still do not fail

To fix the error we just need to add elevation: true to the first test in Api.test.ts:
Promise.resolve(
                JSON.stringify({
                    elevation: false,

but the underlying problem that the error is not thrown is that the methods infoWithDispatch and routeWithDispatch consume the error via the Promise.catch.
In case of routeWithDispatch we could check for the sent RouteRequestFailed action in the test.
In case of infoWithDispatch we would need to sent a similar action. But probably there is a better solution to test this async stuff.

I created a draft PR. The problem was that the api is inherently async. The callback of the api call would trigger the receive method in the test method.
Dispatcher.register({
            receive(action: Action) {
                expect(action instanceof InfoReceived).toBeTruthy()
                expect((action as InfoReceived).result).toEqual(expected)
            },
        })

The equality test would fail but the api has a catch clause
infoWithDispatch() {
        this.info()
            .then(result => Dispatcher.dispatch(new InfoReceived(result)))
            .catch(e => console.log(e.message))
    }

This catch clause would then handle the error caused by the failed expect().toEqual() and simply print a message. The test would then finish sucessfully.

Now, I've changed things so that

The Api.infoWithDispatch dispatches an ErrorAction when the catch clause gets called
The test now has a more elaborate receive method i.e.

Dispatcher.register({
            receive(action: Action) {
                if (action instanceof InfoReceived) {
                    expect(action.result).toEqual(expected)
                } else if (action instanceof ErrorAction) {
                    fail(action.message)
                } else {
                    fail('unexpected action')
                }
            },
        })

This way the test is explicitly failed if an ErrorAction is received. Even the error message of the failed comparison is printed. because the ErrorAction wraps the error message.

Additionaly the test needs to be async and the call to the tested method needs to be awaited like this to prevent the test to finish before the actions generated by the async api call are generated:

await new ApiImpl().infoWithDispatch()

I honestly don't know why one can await this method, since it doesn't return a promise but void 🤷but it works 🤷♀
Is this the solution we want or does anybody have a better idea how to solve this. It feels a little complicated to me.

Is this the solution we want or does anybody have a better idea how to solve this? It feels a little complicated to me.

This is a reasonable approach IMO. Other solutions could be to

avoid calling the catch clause for the test or
provide an optional error callback which we call in infoWithDispatch if an error happens

I honestly don't know why one can await this method, since it doesn't return a promise but void but it works

When I tried this the await did not work actually. I had to add some extra code to make sure my expectations run after the async code in infoWithDispatch had finished, see here: https://github.com/graphhopper/graphhopper-maps/pull/101#discussion_r648879466

A bit off-topic but we should probably also add the test directory (and maybe webpack config?) to the format script in package.json?

fixed with https://github.com/graphhopper/graphhopper-maps/pull/101


Multiple issues while starting speech recognition

(Delete all the statements that don't apply.)
My system is <Alpine linux 3.18>.
My Python version is 3.11
My Pip version is 23.1.2
My SpeechRecognition library version is 3.10.0. (You can check this by running python -c "import speech_recognition as sr;print(sr.__version__)".)
My PyAudio library version is 0.2.13  / I don't have PyAudio installed. (You can check this by running python -c "import pyaudio as p;print(p.__version__)".)
My microphones are: (You can check this by running python -c "import speech_recognition as sr;print(sr.Microphone.list_microphone_names())".)
output.
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
['HDA Intel PCH: CX20585 Analog (hw:0,0)', 'HDA Intel PCH: HDMI 0 (hw:0,3)', 'sysdefault', 'front', 'surround40', 'surround51', 'surround71', 'hdmi', 'default', 'dmix']
My working microphones are: (You can check this by running python -c "import speech_recognition as sr;print(sr.Microphone.list_working_microphones())".)
output.
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1520
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2821
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1520
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2821
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1520
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2821
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1520
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2821
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1520
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2821
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1520
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2821
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1520
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2821
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1520
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2821
{}
I installed PocketSphinx from . Not using sphinx
Overall output,
python main.py
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
A moment of silence, please...
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Set minimum energy threshold to<PHONE_NUMBER>9718016
Say something!
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

`import speech_recognition as sr
def speechrecognition():
r=sr.Recognizer()
with sr.Microphone() as source:
print('Listening.....')
r.pause_threshold=1
audio=r.listen(source,0,0)
 try:
      print('Recognizing.....')
      query=r.recognize_google(audio,language='eng-in')
      return query.lower()

 except:
      return ''

speechrecognition()`
I use this code but getting error, kindly help me to resolve this error:
Traceback (most recent call last):
File "f:\Project AI\chk.py", line 17, in
speechrecognition()
File "f:\Project AI\chk.py", line 5, in speechrecognition
with sr.Microphone() as source:
^^^^^^^^^^^^^^^
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python312\Lib\site-packages\speech_recognition_init_.py", line 80, in init
self.pyaudio_module = self.get_pyaudio()
^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python312\Lib\site-packages\speech_recognition_init_.py", line 111, in get_pyaudio
from distutils.version import LooseVersion
ModuleNotFoundError: No module named 'distutils'

i tried with,
python -c "import speech_recognition as sr;def speechrecognition(): r=sr.Rec
ognizer() with sr.Microphone() as source: print('Listening.....') r.pause_thresh
old=1 audio=r.listen(source,0,0)
no success.

Try SpeechRecognition 3.11.0 or later, distutils removed version


Files for: ZEN22, ZEN32, ZEN54, ZEN71, ZEN72, ZEN73, ZEN74, ZEN76, ZEN77

Hi Felix @kaechele, may i ask you to review the request? Thank you

Hi Felix @kaechele, may i ask you to review the request? Thank you

I could, but I'm not sure what weight it would carry, as I'm not directly affiliated with the project. I, for example, couldn't merge any changes.

Hi @AlCalzone may i ask you to review the request? Thank you


jhead: list known vulnerabilities

Motivation for this change
Jhead is having a few insecurities, label these.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 107627 1

2 packages marked as broken and skipped:
- image_optim
- jhead


Default DataProtectionProvider

I am working on an application built on MVC 5, .Net 4.5, Identity 2.2.1 using Visual Studio 2017.
Assume that I have started with a fresh application and not altered the default Startup.Auth neither have changed any configuration for ApplicationUserManager.DataproctectionProvider. When I debug the application, in ApplicationUserManager.Create the default value of options.DataProtectionProvider is Microsoft.Owin.Host.SystemWeb.DataProtection.MachineKeyDataProtectionProvider.
But the articles I have been following since beginning says that by default it will pick DpapiDataProtectionProvider. What I am missing here?
Since my app will be going on Azure I am really concerned if should I explicitly implement my own MachineKeyDataProtectionProvider?
P.S - I hate to raise it as an issue, please direct me to the right forum for asking queries

This is not an identity issue or a .NET Core issue.  The articles you're reading are for Data Protection in ASP.NET Core, which does try autodetection. As you're not using ASP.NET Core you don't get this feature and what you see in debug is correct, it uses a machine key from web.config. Azure Web Apps set this to a consistent value so you don't have to, so it'll just work.


[BUG] Please re-open https://github.com/nx-dotnet/nx-dotnet/issues/797 or fix permanently

Current Behavior
Version 2.1.2 meant to fix an issue that's still happening
https://github.com/nx-dotnet/nx-dotnet/issues/797
Please reopen this issue
Expected Behavior
Expect to have the error in the bug fixed but problem still persists.  Instructions are both provided at the bottom https://github.com/nx-dotnet/nx-dotnet/issues/797 and also on this commit  https://github.com/nx-dotnet/nx-dotnet/pull/802
Github Repo
No response
Steps to Reproduce

Please see the screenshots at the bottom of this page:
https://github.com/nx-dotnet/nx-dotnet/issues/797
Nx Report
Please see the screenshot at the bottom of this ticket:
https://github.com/nx-dotnet/nx-dotnet/issues/797

nx.json
not applicable - screenshot at the bottom of the ticket should be sufficient
https://github.com/nx-dotnet/nx-dotnet/issues/797

Failure Logs
No response
Additional Information
No response

Are you passing --fix to the command? I don't see it in your screenshots

thanks for the response @AgentEnder  - good question
so basically when following the instructions out of the box on this page, the project.json that gets made just reads as follows (this is with 2.1.2 release btw):

and when you run the lint task you get that error that we are discussing in these threads - so in my screenshot above I had patched the Object.assign() and just remove the line you had added in that commit -- However that's not a viable fix, so what I ended up doing so that every member on the team can work on the project was made my project.json that was made out of the box to look like this for now - besides this fix false below, I didn't do anything else compared to out of the box behaviour in that tutorial above

So that's expected behavior then. By default the linter will report misformatted code, and fail. To fix it you should run once with --fix and commit the results, or format your files with dotnet format manually.

i see - ok so I think we can mark it closed then - we add the "fix" : true" to options in project.json after seeding any new project

I wouldn't recommend specifying fix true in project.json, as you wouldn't catch misformatted code on CI that way


types: service discovery

Adding type definition for mage.core.serviceDiscovery and
all the related types (Service and ServiceNode)

This is currently failing because security vulnerabilities in dependencies are considered fatal. That should be resolved once https://github.com/couchbase/couchnode/pull/76 is merged and released.

LGTM 👍


Add Semantic Scholar social integration

This PR addresses issue #313 according to the suggestion by @alshedivat
In my tests with my local build, the icon got pulled automatically from the Semantic Scholar site.

In this case, http://www.semanticscholar.org/author/NUMERIC_CODE redirects to http://www.semanticscholar.org/author/AUTHOR_NAME/NUMERIC_CODE.

I added semantic scholar also to metadata.html
About the author name and numeric code: I thought about adding a hint, but it works with just the id as well and redirects to the author page.


Better auto indent tab char and size setting and link to improved tiny-process-library

Tested on OS X, MSYS2, Debian stable/testing and Ubuntu 14. Ready for merge.

@zalox After we have agreed upon the screenshot issues, I think this branch is a good release candidate for v1.0.0!
@oyvang Would be nice if you could test this as well:)

Ok this PR is ready for merge. Tested on OS X, Debian stable/testing, MSYS2 and Ubuntu 14.
@zalox Proposing that we release master as v1.0.0 after merge!:)

I just now saw this: https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-jucipp-git !
Our first distributed package, congrats all:)
We should create a pull request on this package when we have the v1.0.0 release ready.

Minor fix to autocompletion error coming soon, only affects OS X in rare conditions as far as I know.

Ohh nice! @oyvang @tedjk You should get in on this. I love it!
I'm reviewing the merge now.


TSLint does not run for entire directory on Windows

Hi,
trying once more as my previous report has been closed without resolution.
I have a directory structure like:
./checkout/src/random_dir/.ts
./checkout/test/random_dir/.ts
I'm trying to run tslint on Windows with './checkout_TEST/{,**/}*.ts' as an argument (and other combinations), but unless I specifically run it for test dir, it always seems to pick up only .ts files in src directory. It totally ignores test.
When I do tslint './checkout/**/*.ts' it again finds everything in the src directory (recursively), but nothing in test folder at all.
When I do tslint './checkout/test/**/*.ts', it find issues in test directory but nothing at all in src directory.
I have also tried tslint './checkout/**/**/*.ts' - which again finds only issues in src directory but not in test.
No other configuration is changed between the runs.
The exact command being executed from a powershell script is:
tslint './checkout_TEST/**/**/*.ts' --format json --config ./tslint.json --out TsLint_out_TEST_1.0.22779.json
I have also tried specifying the name of the file last:
tslint --format json --config ./tslint.json --out TsLint_out_TEST_1.0.22779.json './checkout_TEST/**/**/*.ts'
Anyone has any pointers?
Thanks!

👏 @evusik, sorry for the delay! I'm on Windows and can't reproduce your issue. Closing this for housekeeping, but if this is still an issue, please do comment here and @ me!


Upgrade cockroachdb image tag to v20.1.0

Hi folks,
While doing some integration testing + flyway, I found that the image tag for cockroachdb in testcontainers is 19.1.1  because I faced https://github.com/cockroachdb/cockroach/issues/28751 😅
I think it would be great if the latest stable release is used here which is v20.1.0 released on May 12th.

With #2839 we're intending to deprecate the default constructor for all modules and start encouraging all users to specify a version explicitly. This is primarily to avoid the risk of us breaking users' builds by changing the docker image unexpectedly.
As such, I'll close this PR, as I'd expect that we will leave default image tags where they are until they eventually get removed altogether.


What does file_filter refer to in tx.config?

Hi, great work with txgh!
I have a question:
I'm trying to set up txgh for this github repo:
https://github.com/timothyylim/h5p-greeting-card
and this transfiex project:
https://www.transifex.com/joubel/h5p-greeting-card/
Let's say I just have a single resource that I need translated called en.json. Does this tx.config make sense:
[main]
host = https://www.transifex.com
lang_map =

# Create one such section per resource
[h5p-greeting-card.ensjon]
file_filter = language/<lang>.json
source_file = language/en.json
source_lang = en
type = json

And do I place this tx.config in my txgh directory or in my github repo?
Any help would be very much appreciated.

@timothyylim it's important that you setup locales that match what you are using in your project (ie fr, nb, nn).  Txgh will try to automatically substitute whatever locale it gets back from Transifex.  In some cases this is not desirable (you setup a different locale than what is used by your app).  In these case you'll want to use the "lang_map" field to override that default.
A more detailed description of this file format can be found here: https://docs.transifex.com/client/client-configuration

Great, thank you.


chore: move v23 docs/plus from cdk8s repo

Summary
This PR moves the v23 docs from cdk8s to cdk8s-plus.
This is basically a manual backport of

https://github.com/cdk8s-team/cdk8s-plus/pull/1224

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1249

Questions ?
Please refer to the Backport tool documentation


203 opp history

Work towards this feature is now here instead: https://github.com/button-inc/digital_marketplace/pull/140


Video stutters after changing the audio/video track

Describe the bug
I have a video with multiple audio/video/subtitles tracks.
When I call the method setActiveTracks, the player starts to stutter.
Code:
import 'package:flutter/material.dart';
import 'package:fvp/mdk.dart';
import 'package:logging/logging.dart';

void main() {
  Logger.root.level = Level.ALL;
  Logger.root.onRecord.listen((record) {
    print('${record.loggerName}: ${record.message}');
  });
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: VideoPlayerScreen(),
      ),
    );
  }
}

class VideoPlayerScreen extends StatefulWidget {
  VideoPlayerScreen();

  @override
  _VideoPlayerScreenState createState() => _VideoPlayerScreenState();
}

class _VideoPlayerScreenState extends State<VideoPlayerScreen> {
  late final player = Player();
  double ratio = 16 / 9;

  void setAudioTrackByIndex(int index) {
    int trackLength = player.mediaInfo.audio?.length ?? 0;
    if (trackLength == 0) return;

    List<int> tracks = List<int>.generate(trackLength, (index) => 0); //[0,0,0]
    tracks[index] = 1; //[0,1,0]
    player.setActiveTracks(MediaType.audio, tracks);
  }

  void setVideoTrackByIndex(int index) {
    int trackLength = player.mediaInfo.video?.length ?? 0;
    if (trackLength == 0) return ;

    List<int> tracks = List<int>.generate(trackLength, (index) => 0);
    tracks[index] = 1;
    player.setActiveTracks(MediaType.video, tracks);
  }

  @override
  void initState() {
    super.initState();
    player.media = 'https://mirror.selfnet.de/CCC/congress/2019/h264-hd/36c3-11235-eng-deu-fra-36C3_Infrastructure_Review_hd.mp4';
    player.loop = -1;
    player.state = PlaybackState.playing;
    player.updateTexture();
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: ValueListenableBuilder<int?>(
            valueListenable: player.textureId,
            builder: (context, id, _) => id == null ? const SizedBox.shrink() : Texture(textureId: id),
          ),
        floatingActionButton: FloatingActionButton(
          onPressed: () {
            setAudioTrackByIndex(1);
          },
          child: Icon(
            Icons.transcribe_rounded,
          ),
        ),
      ),
    );
  }

  @override
  void dispose() {
    super.dispose();
    player.dispose();
  }
}

Log
These are the logs in the moment I try to change the audio track:
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 3584 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
D/om.example.tes(23768): PlayerBase::stop() from IPlayer
D/AudioTrack(23768): stop(43): called with 256 frames delivered
....

Same issue in HLS.

player dead while seeking on mdk.

player dead while seeking on mdk.

log

To select the second audio track, the tracks list is [1] instead of [0, 1, 0]
 player.setActiveTracks(MediaType.audio, [1]);

Right


[Repo] Remove stories from coverage report and raise threshold to 90%

In an effort to stabilize our components and make them more resilient to change we are removing the storybook snapshot test from our overall coverage threshold on each file. We will still run snapshots to help highlight where we are changing the output of the component but testing thresholds will now be dependent on unit and browser testing that explicitly test the functionality of each component.
This issue will be an overarching epic to track the process of doing this per component.
In order to complete the task for each component they should:

have the coverage threshold above 90% for all areas (statements, branches, functions, lines) when snapshots are turned off from coverage (found in the jest.config.js's collectCoverageFrom prop).

We may need to turn off coverage as we work each file but not commit that change to the config until all files are above the threshold.

Status without snapshot coverage and threshold being 90%
Indirect tests, i.e. from test files using components where the test target is a child at some level, does touch a lot of code which is good for the coverage, but it is tough to tell if the code they touch is really tested.

Jest: "global" coverage threshold for statements (90%) not met: 86.83%
Jest: "global" coverage threshold for branches (90%) not met: 80.56%
Jest: "global" coverage threshold for lines (90%) not met: 86.97%
Jest: "global" coverage threshold for functions (90%) not met: 84.93%

Helper and utility js files are note included in the list below:

Breadcrumb.jsx" coverage threshold for branches (90%) not met: 87.5%
Breadcrumb.jsx" coverage threshold for lines (90%) not met: 89.66%
ComposedModal.jsx" coverage threshold for branches (90%) not met: 82.05%
TableBody/RowActionsCell/RowActionsError.jsx" coverage threshold for branches (90%) not met: 62.5%
TableBody/RowActionsCell/RowActionsCell.jsx" coverage threshold for branches (90%) not met: 81.82%
TableBody/TableBodyRow/TableBodyRow.jsx" coverage threshold for statements (90%) not met: 84.06%
TableBody/TableBodyRow/TableBodyRow.jsx" coverage threshold for branches (90%) not met: 76.86%
TableBody/TableBodyRow/TableBodyRow.jsx" coverage threshold for lines (90%) not met: 83.33%
TableSaveViewModal/TableSaveViewForm.jsx" coverage threshold for functions (90%) not met: 83.33%
ListItem/ListTarget.jsx" coverage threshold for branches (90%) not met: 80%
ListItem/ListItemWrapper.jsx" coverage threshold for branches (90%) not met: 88.46%
ListItem/ListItem.jsx" coverage threshold for branches (90%) not met: 89.47%
ListItem/ListItem.jsx" coverage threshold for functions (90%) not met: 86.67%
List.jsx" coverage threshold for functions (90%) not met: 86.67%
TableManageViewsModal/TableManageViewsModal.jsx" coverage threshold for branches (90%) not met: 80%
TableSkeletonWithHeaders/TableSkeletonWithHeaders.jsx" coverage threshold for branches (90%) not met: 83.33%
index.jsx" coverage threshold for branches (90%) not met: 87.5%
FlyoutMenu.jsx" coverage threshold for branches (90%) not met: 83.33%
TableToolbar/TableToolbarAdvancedFilterFlyout.jsx" coverage threshold for branches (90%) not met: 89.55%
PageTitleBar.jsx" coverage threshold for statements (90%) not met: 82.22%
PageTitleBar.jsx" coverage threshold for branches (90%) not met: 83.95%
PageTitleBar.jsx" coverage threshold for lines (90%) not met: 81.82%
TileCatalog.jsx" coverage threshold for functions (90%) not met: 66.67%
StatefulTileCatalog.jsx" coverage threshold for branches (90%) not met: 83.33%
CatalogContent.jsx" coverage threshold for branches (90%) not met: 50%
ComposedStructuredList.jsx" coverage threshold for branches (90%) not met: 53.85%
ResourceList.jsx" coverage threshold for branches (90%) not met: 83.33%
HierarchyList/HierarchyList.jsx" coverage threshold for branches (90%) not met: 87.84%
HierarchyList/HierarchyList.jsx" coverage threshold for functions (90%) not met: 82.86%
CardRangePicker.jsx" coverage threshold for branches (90%) not met: 83.33%
Card.jsx" coverage threshold for branches (90%) not met: 81.25%
TimePickerSpinner.jsx" coverage threshold for branches (90%) not met: 80.77%
DateTimePicker.jsx" coverage threshold for branches (90%) not met: 79.05%
IconDropdown.jsx" coverage threshold for branches (90%) not met: 84.09%
IconDropdown.jsx" coverage threshold for functions (90%) not met: 87.5%
Hero.jsx" coverage threshold for statements (90%) not met: 66.67%
Hero.jsx" coverage threshold for branches (90%) not met: 0%
Hero.jsx" coverage threshold for lines (90%) not met: 66.67%
Hero.jsx" coverage threshold for functions (90%) not met: 0%
NavigationBar.jsx" coverage threshold for branches (90%) not met: 80%
NavigationBar.jsx" coverage threshold for functions (90%) not met: 75%
HeaderAction/HeaderAction.jsx" coverage threshold for branches (90%) not met: 86.67%
SideNav.jsx" coverage threshold for branches (90%) not met: 87.5%
SuiteHeaderAppSwitcher/SuiteHeaderAppSwitcher.jsx" coverage threshold for branches (90%) not met: 89.47%
SuiteHeaderAppSwitcher/SuiteHeaderAppSwitcher.jsx" coverage threshold for functions (90%) not met: 85.71%
SuiteHeader.jsx" coverage threshold for branches (90%) not met: 78.33%
SuiteHeader.jsx" coverage threshold for functions (90%) not met: 84%
DashboardHeader.jsx" coverage threshold for branches (90%) not met: 83.33%
ValueRenderer.jsx" coverage threshold for statements (90%) not met: 85.71%
ValueRenderer.jsx" coverage threshold for branches (90%) not met: 70%
ValueRenderer.jsx" coverage threshold for lines (90%) not met: 85.71%
Attribute.jsx" coverage threshold for statements (90%) not met: 58.82%
Attribute.jsx" coverage threshold for branches (90%) not met: 34.38%
Attribute.jsx" coverage threshold for lines (90%) not met: 58.82%
Attribute.jsx" coverage threshold for functions (90%) not met: 50%
ValueCard.jsx" coverage threshold for branches (90%) not met: 78.57%
editorUtils.jsx" coverage threshold for branches (90%) not met: 84.15%
HotspotContent.jsx" coverage threshold for functions (90%) not met: 88.89%
ImageUploader.jsx" coverage threshold for functions (90%) not met: 80%
tableCardUtils.jsx" coverage threshold for branches (90%) not met: 81.08%
TableCard.jsx" coverage threshold for branches (90%) not met: 72.66%
TableCard.jsx" coverage threshold for functions (90%) not met: 79.37%
ListCard.jsx" coverage threshold for branches (90%) not met: 86.67%
GaugeCard.jsx" coverage threshold for branches (90%) not met: 80.95%
DashboardEditorHeader/DashboardEditorHeader.jsx" coverage threshold for branches (90%) not met: 88.89%
DashboardEditorCardRenderer.jsx" coverage threshold for branches (90%) not met: 83.72%
DashboardEditorCardRenderer.jsx" coverage threshold for functions (90%) not met: 88.46%
CardCodeEditor.jsx" coverage threshold for functions (90%) not met: 88.89%
CardEditForm/CommonCardEditFormFields.jsx" coverage threshold for statements (90%) not met: 86.21%
CardEditForm/CommonCardEditFormFields.jsx" coverage threshold for lines (90%) not met: 85.71%
CardEditForm/CardEditFormItems/ThresholdsFormItem.jsx" coverage threshold for branches (90%) not met: 83.33%
CardEditForm/CardEditFormItems/DataSeriesFormItemModal.jsx" coverage threshold for statements (90%) not met: 85.71%
CardEditForm/CardEditFormItems/DataSeriesFormItemModal.jsx" coverage threshold for branches (90%) not met: 82.65%
CardEditForm/CardEditFormItems/DataSeriesFormItemModal.jsx" coverage threshold for lines (90%) not met: 85.71%
CardEditForm/CardEditFormItems/DataSeriesFormItemModal.jsx" coverage threshold for functions (90%) not met: 88.46%
CardEditForm/CardEditFormItems/ContentFormItemTitle.jsx" coverage threshold for branches (90%) not met: 83.33%
Dropdown.jsx" coverage threshold for branches (90%) not met: 87.5%
HotspotTextStyleTab/HotspotTextStyleTab.jsx" coverage threshold for branches (90%) not met: 83.33%
HotspotEditorDataSourceTab/HotspotEditorDataSourceTab.jsx" coverage threshold for branches (90%) not met: 87.5%
HotspotEditorModal.jsx" coverage threshold for branches (90%) not met: 82.98%
CardEditForm/CardEditFormItems/ImageCardFormItems/ImageCardFormContent.jsx" coverage threshold for branches (90%) not met: 83.33%
CardEditForm/CardEditFormItems/TableCardFormItems/TableCardFormContent.jsx" coverage threshold for branches (90%) not met: 86.67%
CardEditForm/CardEditFormContent.jsx" coverage threshold for branches (90%) not met: 88.46%
CardEditForm/CardEditFormContent.jsx" coverage threshold for functions (90%) not met: 80%
CardEditForm/CardEditFormItems/DataSeriesFormItems/DataSeriesFormSettings.jsx" coverage threshold for functions (90%) not met: 85.71%
CardEditForm/CardEditFormItems/BarChartCardFormItems/BarChartCardFormSettings.jsx" coverage threshold for functions (90%) not met: 80%
CardEditForm/CardEditFormItems/TableCardFormItems/TableCardFormSettings.jsx" coverage threshold for branches (90%) not met: 81.25%
CardEditForm/CardEditFormItems/TableCardFormItems/TableCardFormSettings.jsx" coverage threshold for functions (90%) not met: 88.24%
CardEditor.jsx" coverage threshold for branches (90%) not met: 80%
PieChartCard.jsx" coverage threshold for functions (90%) not met: 85%
PageWizardStep/PageWizardStep.jsx" coverage threshold for branches (90%) not met: 87.5%
StatefulPageWizard.jsx" coverage threshold for branches (90%) not met: 80.95%
SimpleList/SimpleList.jsx" coverage threshold for branches (90%) not met: 89.19%
SimpleList/SimpleList.jsx" coverage threshold for functions (90%) not met: 83.33%
AccordionItemDefer.jsx" coverage threshold for branches (90%) not met: 83.33%
ScrollingControls.jsx" coverage threshold for branches (90%) not met: 87.5%
TableHead/FilterHeaderRow/FilterHeaderRow.jsx" coverage threshold for statements (90%) not met: 87.3%
TableHead/FilterHeaderRow/FilterHeaderRow.jsx" coverage threshold for branches (90%) not met: 81.33%
TableHead/FilterHeaderRow/FilterHeaderRow.jsx" coverage threshold for lines (90%) not met: 87.1%
TableHead/FilterHeaderRow/FilterHeaderRow.jsx" coverage threshold for functions (90%) not met: 83.33%
TableHead/TableHead.jsx" coverage threshold for statements (90%) not met: 89.72%
TableHead/TableHead.jsx" coverage threshold for branches (90%) not met: 85%
TableHead/TableHead.jsx" coverage threshold for lines (90%) not met: 89.11%
TableHead/TableHead.jsx" coverage threshold for functions (90%) not met: 77.14%
TableMultiSortModal/TableMultiSortModal.jsx" coverage threshold for branches (90%) not met: 85.71%
ErrorTable/ErrorTable.jsx" coverage threshold for branches (90%) not met: 83.33%
Table.jsx" coverage threshold for statements (90%) not met: 89.8%
Table.jsx" coverage threshold for branches (90%) not met: 88.1%
Table.jsx" coverage threshold for functions (90%) not met: 82.35%
StatefulTable.jsx" coverage threshold for branches (90%) not met: 86%
GroupLogic.jsx" coverage threshold for functions (90%) not met: 85.71%
RuleBuilder.jsx" coverage threshold for branches (90%) not met: 83.78%
TableDetailWizard/TableDetailWizard.jsx" coverage threshold for branches (90%) not met: 85.71%
TimeSeriesCard/TimeSeriesCard.jsx" coverage threshold for functions (77%) not met: 71.88%

Closed by #2822


feat(text): add client sample code

Because

we want developers to be able to see the result without login into Instill Cloud

This commit

expose text component function
add the example section for golang client

Ported to https://github.com/instill-ai/pipeline-backend/pull/682


fix(useform): fix bug when set input value at funtion setRefValue

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Updated code samples to use .Target property for attaching pointing t…

…ips and moved non-point tips out of Button.
This change is coming through as a separate pull request as I am waiting on the corresponding update to the implementation. This keeps the shared documentation consistent with the publicly available version of the control.

At this line
What does it mean to require manual acknowledgement?  Is this picture supposed to have an "OK" button or some such?

@MikeHillberg, both samples above have an [X] in the top right corner whereas the light-dismiss tip does not. Does the follow edit read more clearly?
"A teaching tip can require the user to dismiss it via an "X" button in a top corner or a "Close" button at the bottom. However, a teaching tip may also be light-dismiss enabled in which case there is no dismiss button and the teaching tip will instead dismiss when a user scrolls or interacts with other elements of the application."

@MikeHillberg I have moved this discussion over to our main PR as this PR is just for the .Target update.


[network] Migrate network module to new wire protocol

As described in #2878, we want to migrate to a new network wire protocol that is message-oriented rather than stream-oriented.
This PR performs the migration to the new wire protocol messages. It is composed of 5 commits:

The first commit migrates RPC and DirectSend modules to use messages defined in #2878 and send those to the Peer actor. The Peer actor internally sends each message over a  substream opened just for the purpose of sending 1 message. The details of implementation of RPC and DirectSend are described in the Rustdocs of respective modules.
The second commit removes the auto-upgrade of transport to Yamux after a connection is established. The task of upgrading to yamux is moved to the Peer actor, which becomes the sole entity dealing with substreams.
The third commit removes stream-oriented communication entirely. The Peer actor no longer "upgrades" a socket to Yamux, and instead reads and writes messages to a socket directly.
The fourth commit removes some trait bounds on TSocket
The fifth commit gets rid of all yamux and multiplexing related code in the module[

Related PRs
#2878, #2879, #2928

This is breaking for validators, but not for clients, since clients currently do not use LibraNet?

@davidiw : Looking at the size of PR after I was done fixing the tests, I too wondered if it was possible to break it down into more digestible bits. Unfortunately, and as you guessed, that would require being in a very hacky middle-of-nowhere state to support both streams and message based APIs at the peer actor. My recommendation for review would be to only look at the final state of things rather than looking at before-after split, especially for RPC and DirectSend, since those have almost fully been re-written.

@bors-libra r=davidiw
I've tried to incorporate most suggestions that were applicable. In case I've missed anything, I'll cover them in a final pass after the migration is complete, which should anyway give us a better picture of what else we can clean up.

:pushpin: Commit 096146e has been approved by davidiw

:hourglass: Testing commit 096146e89df2a6797a9ad2c5be342f2717fe76b3 with merge c5730fdb4ea5df699f384326544474e558846578...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra r+

:pushpin: Commit 96db26f has been approved by davidiw

:hourglass: Testing commit 96db26f65fb93a20c8b6397998feb72c72727f8b with merge 789df28cb7803ef3e7909aa6e95f13577b299688...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra retry

:hourglass: Testing commit 96db26f65fb93a20c8b6397998feb72c72727f8b with merge 4a13ec7fd4c048a61e70cc11d42c358797e082a5...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra retry

:hourglass: Testing commit 96db26f65fb93a20c8b6397998feb72c72727f8b with merge 82b56f62876ee9792e16f6c74bfae8b06d1ecc82...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra retry

:hourglass: Testing commit 96db26f65fb93a20c8b6397998feb72c72727f8b with merge f55a11795ac57bc4d357e7123b853747f309a0b4...

:broken_heart: Test failed - checks-circle_commit_workflow

That latency number looks bad, compare that to my runs this morning: https://github.com/libra/libra/pull/3169
Perhaps we could look at a flamegraph or something similar to identify if we're doing something differently then before?

@davidiw I just discussed this with @ankushagarwal  as well. My run on the exact same commits from today morning had these results:
{
  "metrics": [
    {
      "experiment": "all up",
      "metric": "submitted_txn",
      "value": 223670.0
    },
    {
      "experiment": "all up",
      "metric": "expired_txn",
      "value": 0.0
    },
    {
      "experiment": "all up",
      "metric": "avg_txns_per_block",
      "value":<PHONE_NUMBER>101021
    },
    {
      "experiment": "all up",
      "metric": "avg_tps",
      "value":<PHONE_NUMBER>176896
    },
    {
      "experiment": "all up",
      "metric": "avg_latency",
      "value": 3021.1793012775943
    }
  ],
  "text": "all up : 929 TPS, 3021.2 ms latency, no expired txns"
}

Results on https://github.com/libra/libra/pull/3178, which was the last merged PR, also look similarly bad

@bors-libra retry

:hourglass: Testing commit 96db26f65fb93a20c8b6397998feb72c72727f8b with merge 5eceb42e6739faeecffda51777d8c0eb6a5d7fb8...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra retry

:hourglass: Testing commit 96db26f65fb93a20c8b6397998feb72c72727f8b with merge 96ccb4631fa5e0559d06f0ec881e3da18744ae19...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r=davidiw

:pushpin: Commit 4b263d8 has been approved by davidiw

:hourglass: Testing commit 4b263d8922b5961c940dcd6642d4fb803617ae67 with merge 5a234569b226bc1d1af7ec856bcd744c99ebd902...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: davidiw
Pushing 5a234569b226bc1d1af7ec856bcd744c99ebd902 to master...


Direct server crash when starting server (fabric)

Description
Just a lot of errors and a crashing server, don't really know what happens.
I tried running with the lastest build on the site (5.3.0) and on old version on modrinth (5.2.92). With each build I get the errors.
When removing luckperms the server runs smooth.
Server:
2gb - shared test server
openjdk version "1.8.0_262"
OpenJDK Runtime Environment (build 1.8.0_262-b10)
OpenJDK 64-Bit Server VM (build 25.262-b10, mixed mode)
:/home/container$ java -Xms128M -Xmx2048M -jar server.jar
[15:41:09] [main/INFO]: Loading for game Minecraft 1.16.5

Error:
https://mcpaste.io/71c41545486ea761
Mods installed:

It looks like there is a conflict between chunky pre gen and luckperms

Minecraft 1.16.5 usa jdk 11 se não me engano.

Same problem on java 11, chunky dev says its luckperms problem not his code

Closing as duplicate of #2880


OPNsense 23.7.5 breaks addon

I have been using this addon for a while now, it is great (thanks). But today I upgraded opnsense to 23.7.5 and it no longer works. Trying to reconfigure the addon in home assistant (2023.9.3) gives me this error:

There are otherwise no errors in home assistant. I have redownloaded the addon and recreated the api keys but that does not solved the problem.

Same error

I am also experiencing this problem.
The integration still shows sensors related to the router's condition/performance, but my device trackers all show "Unavailable" and I am unable to configure more.
I have these two errors in my logs and I do not recall them being present before.
2023-10-19 09:06:00.311 ERROR (SyncWorker_19) [custom_components.opnsense] failed to retrieve arp table err=TimeoutError('The read operation timed out'), type(err)=<class 'TimeoutError'>```

I am also experiencing this problem.
The integration still shows sensors related to the router's condition/performance, but my device trackers all show "Unavailable" and I am unable to configure more.
I have these two errors in my logs and I do not recall them being present before.
2023-10-19 09:06:00.311 ERROR (SyncWorker_19) [custom_components.opnsense] failed to retrieve arp table err=TimeoutError('The read operation timed out'), type(err)=<class 'TimeoutError'>```

OK. I figured out my issue, I do not think it is the same as the previous two posters. I had deleted my DNS servers from my OPNSense configuration during a previous router troubleshooting session...forgot about it...and fixed it.

Same for me, but while configuring it for the first time:
Source: custom_components/opnsense/config_flow.py:148
Unexpected err=TypeError("string indices must be integers, not 'str'"), type(err)=<class 'TypeError'>
OPNsense: 23.7.8
HA: 2023.11.2

@travisghansen are there any logs we could provide, or beta versions we could test?
My logs are the same as @stmpl
12:36:22 – (ERROR) OPNsense (custom integration)
Unexpected err=TypeError("string indices must be integers, not 'str'"), type(err)=<class 'TypeError'>
12:36:22 – (ERROR) OPNsense (custom integration)
Unexpected get_system_info error err=TypeError("string indices must be integers, not 'str'"), type(err)=<class 'TypeError'>

HA: 2023.11.1
OPNsense: 	OPNsense 23.7.9-amd64, FreeBSD 13.2-RELEASE-p5, OpenSSL 1.1.1w
Thank you for a great plugin!

Same Error with HA

integration shows Error:

Logfile:
2024-03-06 18:20:28.995 ERROR (SyncWorker_24) [custom_components.opnsense.pyopnsense] Unexpected get_system_info error err=TypeError("string indices must be integers, not 'str'"), type(err)=<class 'TypeError'> 2024-03-06 18:20:28.997 ERROR (MainThread) [custom_components.opnsense.config_flow] Unexpected err=TypeError("string indices must be integers, not 'str'"), type(err)=<class 'TypeError'>
Any idea, how to fix this?

Thanks for the patience getting back to you. All of these are when attempting to configure the integration initially? You cannot even get it to load initially?

Come to say it works for me in 24.1.3 of OPNsense with Home Asisstant 2024.3.1

@travisghansen correct, steps to repro are:

Add repo in HACS, install
Click on "Add Integration" on the integrations page
Enter host url, apio key, secret, and name.
Observe error "Unexpected Error" and the string indices must be integers, not 'str'" error in the logs.

OPNSense: OPNsense 24.1.4-amd64
Home Assistant: 2024.3.1
hass-opnsense: v0.1.21

Hmm ok. That's pretty strange. The setup phase has very little interaction with the api :(

How could I help debug? Are there any other logs that would be helpful, or is there some way to increase verbose output?

Are there any logs on the opnsense side that provide some better info about what the error might be?

This error originated from a custom integration.

Logger: custom_components.opnsense.config_flow
Source: custom_components/opnsense/config_flow.py:149
integration: OPNsense (documentation, issues)
First occurred: 20:13:13 (1 occurrences)
Last logged: 20:13:13

Unexpected err=TypeError("string indices must be integers, not 'str'"), type(err)=<class 'TypeError'>

FWIW, If I try to enable the "verify ssl" flag, I get a correct error that the cert is self signed, so the connection to the server seems to be going through:

@travisghansen I did some light digging, and traced this down to the client.get_system_info call. I can't really follow what you're doing with the pythonic php execution, but my guess is that the response at https://github.com/travisghansen/hass-opnsense/blob/main/custom_components/opnsense/pyopnsense/init.py#L268 is throwing the type error, perhaps coming from the json encode at https://github.com/travisghansen/hass-opnsense/blob/main/custom_components/opnsense/pyopnsense/init.py#L127
I can confirm that the address is getting dialed and the authentication is valid (tested via curl), so I'm guessing the object coming back from the php side of things isn't rendering into the dictionary the code expects.

Right, the question is why is that method failing? It's the most basic bits of code and should not be things that would be brittle :(
If you're comfortable doing some python dev you can clone this repo locally, setup a venv and manually use the xmlrpc client. Doing so would help us see the output better to determine what's blowing up.

Still a problem.

Latest HAOS/OPNsense, freshly generated api keys. It used to work before I updated OPNsense to ver. 24
Is there any update to this?

I just encountered the same issue after trying this plugin for the first time. I forked, added a stacktrace log, and found that there was an error being reported by my OPNSense about the os-homeassistant-maxit install failing due to a versioning issue.
These steps fixed the issue for me:

Update to OPNsense 24.1.8
SSH'ed back in to OPNsense and re-ran pkg install os-homeassistant-maxit

Please give v0.2.0 a try and open a new issue if this is still happening.

Hey @Snuffy2  it's still an issue on 0.2.0:


Uncaught InvalidCharacterError: Failed to execute 'add' on 'DOMTokenList': The token provided ('A...

[Enter steps to reproduce:]

...
...

Atom: 1.36.0 x64
Electron: 2.0.18
OS: Mac OS X 10.14.4
Thrown From: Atom Core
Stack Trace
Uncaught InvalidCharacterError: Failed to execute 'add' on 'DOMTokenList': The token provided ('Alice,
How') contains HTML space characters, which are not valid in tokens.
At /Applications/Atom.app/Contents/Resources/app/static/<embedded>:14

Error: Failed to execute 'add' on 'DOMTokenList': The token provided ('Alice,
How') contains HTML space characters, which are not valid in tokens.
    at SuggestionListElement.addClassToElement (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:1969704)
    at SuggestionListElement.renderItem (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:1970996)
    at SuggestionListElement.renderItems (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:1967361)
    at ViewRegistry.performDocumentUpdate (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:326703)

Commands
  3x -1:40.8.0 core:backspace (input.hidden-input)
     -1:35.3.0 core:save (input.hidden-input)
  2x -1:34.7.0 platformio-ide-terminal:toggle (input.hidden-input)
     -0:59.8.0 core:move-down (input.hidden-input)
  2x -0:59.6.0 atomic-emacs:next-line (input.hidden-input)
  2x -0:58.2.0 core:backspace (input.hidden-input)
     -0:55.8.0 editor:newline (input.hidden-input)
  2x -0:55 atomic-emacs:previous-line (input.hidden-input)
  3x -0:54.2.0 atomic-emacs:next-line (input.hidden-input)
  3x -0:53.5.0 core:backspace (input.hidden-input)
  2x -0:52.2.0 editor:newline (input.hidden-input)
     -0:46.9.0 core:move-up (input.hidden-input)
 13x -0:45.9.0 core:backspace (input.hidden-input)
 11x -0:39.7.0 atomic-emacs:previous-line (input.hidden-input)
 16x -0:39 atomic-emacs:next-line (input.hidden-input)
 31x -0:30.9.0 core:backspace (input.hidden-input)

Non-Core Packages
ariake-dark-syntax 0.1.3
atom-beautify 0.33.4
atom-hipster-ui 0.3.0
atom-material-syntax 1.0.8
atom-material-syntax-dark 1.0.0
atom-material-syntax-light 0.4.6
atom-material-ui 2.1.3
atom-runner 2.7.1
atomic-emacs 0.13.0
auto-encoding 0.7.2
autocomplete-paths 2.12.2
autocomplete-python 1.14.0
autocomplete-sql 0.5.0
autocomplete-xml 0.11.0
avengers-syntax 0.3.0
busy-signal 2.0.1
challenger-deep-syntax 0.17.0
color-picker 2.3.0
custom-xml-autocomplete 0.1.0
editor-background 1.2.41
ficus-dark-syntax 2.1.0
ficus-syntax 2.1.0
file-icons 2.1.31
git-plus 8.6.2
highlight-selected 0.16.0
hipster-syntax 0.0.3
intentions 1.1.5
isotope-light-ui 2.3.0
isotope-ui 2.8.5
japanese-menu 1.14.0
kite 0.154.0
linter 2.3.0
linter-autocomplete-jing 0.8.4
linter-clang 4.1.2
linter-flake8 2.4.0
linter-gcc 0.7.1
linter-javac 1.10.0
linter-python 3.1.2
linter-python-pep8 0.2.0
linter-ui-default 1.7.1
monokai 0.24.0
monokai-neo-syntax 1.3.2
ninja-atom-syntax 0.1.2
ninja-ui-syntax 0.1.4
pear-dark-syntax 1.0.9
pear-syntax 0.1.8
pigments 0.40.2
platformio-ide-terminal 2.9.1
project-manager 3.3.7
pumpkin-swamp-dark-syntax 0.4.0
pumpkin-syntax 0.1.0
python-indent 1.1.7
slime 2.4.0
split-diff 1.6.0
Sublime-Style-Column-Selection 1.7.5
tag 0.5.0
terminal-tab 0.5.7
xml-common-schemata 0.0.3
zenburn 3.1.0
zenburn-theme 1.3.0

Thanks for the report! I'm guessing this isn't reproducible in safe mode (atom --safe)?
I think this is likely a duplicate of #16164 - based on that issue and #16305, my guess would be that autocomplete-python might be causing the error?
If you can reproduce in safe mode however, please let us know.

It appears that this is being caused by the autocomplete-python package, not Atom itself. It may be that there is still a bug in Atom. If so, we'll need the maintainer of the package that is causing the problem to help track that down. You should file this issue on their repository so they can either fix the problem or tell us where the problem is coming from. The Atom FAQ has information on how to contact the maintainers of any Atom community package or theme.


Docs

fix docs links to the documentation
adding badges to increase curb appeal
after merge - I will create 1.2.1 release.

I know there's no code changes, but probably still makes sense to update _version.py and CHANGELOG.txt to reflect changes and be consistent with PyPI version?

I know there's no code changes, but probably still makes sense to update _version.py and CHANGELOG.txt to reflect changes and be consistent with PyPI version?

CHANGELOG.txt and _version.py both updated.


Issue @27 Index Based Source operator

Adding class for text field.
Updating test data with one more field
IndexBasedSourceOperator.
Test cases for index based source operator.

It shows "All checks have failed."  Please fix it first before other people can review it.

@chenlica @sandeepreddy602  @prakul Please review.
I have added one more field type "TextField" , as the StringField does not support tokenization.

I left one comment. Overall, it looks good to me. Let's wait for @chenlica  and @JavierJia comments before merging.

@kishore-narendran to do a review (as an exercise).

@akshaybetala .. Please include the issue number (Issue #27) in commit messages.

please review it now.

Since there's no open PR from our team, I made the changes and pushed the file in this branch as it's used by your team also. Hope it's okay. :)

I have changed 2 test cases to use the helper function. I can update the remaining test case, when the other helper function is implemented.
Can I go ahead and merge this request?

I suggested adding high-level comments to the class.  Please take care of it if you can.
You can do the merge.  After @rajesh9625 added another helper function for the test cases, you can do another PR to modify your test cases.

Added helper function "containsAllResults" that takes two sets of results, one is expectedResults and the other is exactResults. Checking if "expectedResults is a subset of exactResults" and vice versa. This works for all the tests implemented so far. Will have to change this once spans are introduced.


Change broken user guide link to quick start

The link to the user guide under "Getting Started" in the README.md now 404s, so I've replaced it with a link to the quick start which looks like the closest replacement.
Whilst at it, add syntax highlighting to a code block in the README.md which was missing it.

@srstevenson thanks for the PR! lgtm


Update dep for test-infra

Update the test-infra dependency using dep update

/uncc vaikas-google

/cc adrcunha

/approve
/lgtm
Please note that you need OWNERS approval to get this PR merged.


Skip scipy.sparse.linalg.eighs tests for CUDA 9.2

In the cupy daily combination tests, the recent PR #4138 makes use of a call that returns nan arrays in CUDA 9.2
With the provided t.npy.zip, cusolver syevd fails in CUDA 9.2
import cupy
a = cupy.load('t.npy')
cupy.linalg.eigh(a)  # nans

We will skip these tests since there is no easy way to fix this in our side, as this is an older cusolver internal problem.
@anaruse any thoughts about this? thanks!

We need to document this behavior. @toslunar, @kmaehashi
Should we add a note or warning in the cupy.linalg.eigh docstring?

Could you run the following to check if cuSOLVER reports an error?
import cupy, cupyx
a = cupy.load('t.npy')
with cupyx.errstate(linalg='raise'):
    cupy.linalg.eigh(a)  # nans

No error is reported 😢

So the failure is occurring here? Perhaps there is a bug in CUDA 9.2's cuSOLVER.
https://github.com/cupy/cupy/blob/786c303540fbcd81ff11667ac23ede67cad104c9/cupyx/scipy/sparse/linalg/_eigen.py#L134-L150
One workaround is to use numpy.linalg.eigh here instead of cupy.linalg.eigh. This would require data transfer between CPU and GPU, but since the matrix size processed here is very small, there would be little or no performance loss.

The bug is indeed in cuSOLVER, let me discuss with the team the possible solution :).
Thanls!

@emcastillo , Could you try https://github.com/cupy/cupy/pull/4231 on CUDA 9.2?

Error was fixed in #4231, closing this


Configuration not becoming available after power cycle of monitor

After a power cycle of the monitor, the sensors come up again automatically but configuration not:

Page Reload not fixes it.
Quick Reload not fixes it.
Only restart of Home Assistant fixes it:

The polling interval for the configuration is 5 minutes and after every change we do (even though it's a local device, I don't think we change config that often that we should poll it a lot). I think if you wait a few more minutes it should work again.
Let me know if you think differently

I think 5min is too long and if it does not create too much load I would go for at least 1min.


importance_df provided the order but not aboslute_mean_shap value

https://github.com/TorkamaniLab/zoish/blob/537d1e403e6c0cfc85bbfa1e7cb1aa7336bb15de/zoish/feature_selectors/shap_selectors.py#L755
importance_df provided the sorted feature index (same content of other attribute) but not aboslute_mean_shap value or feature names

Now it has requested information, check examples


targetScope doesn't appear to support arrays

Bicep version
Bicep CLI version 0.3.255 (589f0375df)
Describe the bug
Declaring the target scope using an array not supported as per the bicep spec
Azure Policy Documentation "Azure Policy Definition deployments target either subscription or management group scopes."
To Reproduce
Add the following to a Bicep file containing a Policy Definition:
targetScope = [
  'managementGroup'
  'subscription'
]

VS Code Warning

Expected a value of type "'managementGroup' | 'resourceGroup' | 'subscription' | 'tenant'" but the provided value is of type "array".bicep(BCP033)

Additional context
Add any other context about the problem here.

Closing as dup of #788, but we should try to take care of this sooner rather than later cc @majastrz / @shenglol FYI


WIP: Kiciek/make startup easy

This will solve simple tasks I need to do before starting real changes.

On first startup there were errors waiting to greet me. I am going to fix them

[ ] Cannot read property 'map' of undefined
[ ] Callback error updating toughness_0.value, save_0.value, invuln_0.value, fnp_0.value, wounds_0.value
[ ] Callback error updating toughness_2.value, save_2.value, invuln_2.value, fnp_2.value, wounds_2.value
[ ] Callback error updating toughness_1.value, save_1.value, invuln_1.value, fnp_1.value, wounds_1.value
[ ] Callback error updating page_content.children
[ ] Callback error updating page_content.children

There is still a lot more unused imports in other files. At first, I was deleting them to find out what are minimal requirements, but as they do not introduce any new requirements you may want to remove commits deleting unused imports while merging.

I have only masked errors - wrong requests are still coming.


Preliminary PowerSet Support

Closes #493
This is truly ready for review and testing. I'm positive that the code can be optimized and cleaned up, so feel free to provide suggestions!
Goals:

Populate and save the trays with initial power/powersets.
Gracefully handle clicking on powers (since they will still do nothing)
Save Inspirations and Boosts to "inventory"
Send Starting Inspirations to new characters
Gracefully handle clicking on inspirations (since they will still do nothing)

Additions/modifications proposed in this pull request:

Fixed removeFriend() issue #493
I lose sight of scope and spend hours working on a framework for Powers ;)
Added logPowers logging category
Serialize trays to database
Serialize Owned Powers to database
Serialize Inspirations to database
Finished naming Windows in WindowIDX enum
New Methods for Character class: addPowerSet() addStartingInspirations() getInherentPowers() getPowerFromBuildInfo() sendEnhancements() sendInspirations() sendOwnedPowers()
Refactored SendCharBuildInfo()
Set default target to self
Added pointer vectors for m_queued_powers and m_recharging_powers to Entity class
Added moveInspiration() to Powers.cpp -- NOTE: this appears buggy, the client doesn't acknowledge the move?
Added structs for CharacterPower, CharacterPowerSet, CharacterInspiration, CharacterPowerEnhancement
Added getPowerCatByName() getPowerSetByName() getPowerByName() getPowers() getPower() sendClientState() showMapXferList() sendFloatingInfo() methods to DataHelpers
ClientStates enum
Rewrote storePowerInfoUpdate()
Added FloatingInfo class  for "Mission Complete!" and "Level Up!" type notifications
Added FloatingInfoStyles enum
Added MapXferList, and MapXferListClose framework
Added ActivatePower and ActivatePowerAtLocation framework
Added SendStance framework -- NOTE: crashes client if uncommented?
Added SetClientState event
Added MoveInspiration event
Added m_all_powers to global MapServerData
Added initial starting powersets to array
Added starting Inspirations
Added Temporary_Powers to the initial powers list (this powerset must exist, even if empty!)
Added Inherent Powers to initial powers list
Fixed tray switching
Click on Door, thing happens ;)
Click on Power, thing happens ;)
Click on Inspiration, thing happens ;)
Add Enhancements, Move Enhancements, Attach to Powers, Combine Enhancements with combine chances
ChangeTitle window now works! Try it out with /title
RecvSelectedTitles class
Added DialogButton event
Added MoveEnhancement event
Added SetEnhancement event
Added CombineEnhancement event
Added TrashEnhancement event
Added LevelUp event
Added RecvNewPower event
Added CombineEnhanceResponse event
Added /mapmenu /clientstate /title /setcustomtitles /setspecialtitle /addpower /addinsp /addboost /levelup slash commands

Recommended methods for testing:

Toggle on logPowers, either from settings.cfg or via /log Powers
Use /addpowerset /addpower /addinsp or /addboost to add various "powers"
Click on everything. Try to break stuff. See what happens.
Use /mapmenu and /title and /levelup
NOTE: leveling up is not feature complete in that your MaxAttribs are not updated properly

As of Jul 25th:

As of Jul 27th:

As of Aug 2nd:

Just 2 minor things:

Need to push Inherent in for Brawl. I don't remember the Powerset index off the top of my head. 27 maybe?

I propose renaming Boost to Enhancement or a shorter version like Enhance. I think that helps clarity, since all the UI, etc refers to them that way.

Good feedback. I was thinking about Brawl too. Will have to deduce it's idx from the bin files.
boosts are what enhancements appear to be called in the client code. I like enhancements better too, though it's long. Especially since boost is such a popular library, and the client doesn't refer to them as such anywhere else.
Maybe we call them 'hancies'... Nah just kidding 🤣

This is ready for vigorous review and testing. There's a lot here, so I'll update the PR summary with a list of features.

This is excellent work. Good job!!

Seemingly random, but I'm getting BasePower not found messages when logging in with characters.
It's not consistent, sometimes it's new chars, sometimes old, and only happens about 30-40% of the time?
Maybe I'm passing an uninitialized variable somewhere?

I suspect that the way I'm storing inspirations is wrong. Modifying that vector at all causes subsequent logins to crash the client.
Maybe store as std::vector< std::vector< CharacterInspiration >> m_inspirations instead? Then I can store the col x row array between sessions?
Would make accessing specific inspirations for use and move more simple: m_inspirations[cool][row]

https://paragonwiki.com/wiki/Inspirations
and
https://paragonwiki.com/wiki/The_Players'_Guide_to_the_Cities/User_Interface/Inspirations_Window

And a reminder to myself to implement this:
At any time, if there is an empty slot under another inspiration, that inspiration (and any above it) will slide down one slot in the window.

TravisCI hates me =(
Not sure why this is kicking out errors. Log has nothing of value. Will try to restart the build and see if it's just a fluke.

Further digging seems to show that powerset[0] must be Temporary_Powers (idx 27.0) to line up with client side.
This explains why the client returns pset as +1

To Test:
Test if /bind properly serializes to the database. Plus I don't think && works for adding multiple commands in one send. Not sure how to implement that.
Test location targeting for powers like Teleport


Fix pallet_assets no_std compilation

Could you port this to polkadot-v0.9.19 as well? thanks

Hmm, it is included in the bin/node/runtime. So, it should already be compiled as part of the CI in wasm. Not sure why it didn't failed there :thinking:
What compiler version are you using?

@bkchr we are using: nightly-2021-11-07, somehow I cannot compile into wasm yet due to missing vec import, wierd

I found the problem. I bet with you that you have the std feature of sp-std somewhere in your project enabled. Please check this.

Not sure if it's caused by compiler though, it's also reporting some others:

let me check thanks

@bkchr you are awesome! fixed now

I am running into the same issue in v0.9.26
I have tried wit the sp-std/std flag enabled and disabled.
Suggestions?

@anantasty it can also be any other crate that propagates std feature to sp-std. You can use cargo tree to find out which crate enables the std feature.

Thanks @bkchr


[audiofile] Add new port

Describe the pull request

What does your PR fix?
Add new port: https://github.com/adamstark/AudioFile

Which triplets are supported/not supported? Have you updated the CI baseline?
Header only. All triplets should be supported. No.

Does your PR follow the maintainer guide?
Yes.

/azp run

/azp run

/azp run


fix(raw): exclude yaml from raw plugin

🔗 Linked issue

https://github.com/nuxt-modules/i18n/issues/2835
Related https://github.com/unjs/nitro/pull/2229
Related https://github.com/unjs/nitro/pull/2239

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Nuxt I18n is running into issues specifically with yaml files since nitro 2.9.2+, I think because we're trying to parse and transform the file ourselves but it's already been handled as a raw file?
Let me know if this is not the correct way to resolve this or if there is a way for us to exclude specific files from being handled, I'm following this PR https://github.com/unjs/nitro/pull/2239 as an example (it looks like it added checks for yaml as well anyway).

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Would you please make a minimal reproduction with nitro that works before 2.9 and broken with 2.9.2? 🙏🏼

Sorry, I should have included a reproduction in the first place, I know how annoying it can be without (was a bit drained).
Here is the reproduction: https://github.com/BobbieGoede/nuxt-i18n-yaml-nitro-raw
Interesting to note, this issue only happens when using the server side translation feature, which adds a server/nitro plugin as well as plugins to transform yaml and json5 files (see relevant code), there are no issues using json5 files as seen in the reproduction.
Using nitro 2.9.1

Install and run using pnpm i && pnpm run dev
Open page and observe behaviour is as expected
(optional) Build project using pnpm run build

Observe transformed yaml locale file at .output/server/chunks/build/ja-[hash].mjs

Using nitro >2.9.2

Remove pnpm.overrides from package.json and install and run again using pnpm i && pnpm run dev
Terminal will throw error [worker reload] [worker init] _import_meta_url_ is not defined, page stuck on Nuxt loading splash logging 503 status
(optional) Build project using pnpm run build

Observe transformed yaml locale file at .output/server/chunks/raw/ja.mjs

Just adding on that this seems to be throwing an error in my projects as well. They use the rollup yaml plugin to process the yaml files into JS objects, but after nitro 2.9.2, there's an error on dev startup saying no such file or directory. There's probably a way for me to make sure the raw plugin doesn't take over that may resolve the issue, but I assume this PR will do that too.


Producers and Consumers should accept Topics as arguments

Closes #336

Closing this PR for now, more info here


Pass Current Directory And Allow Expansion of Paths

Modify the tool to pass the working directory and add a function to help expand this out.

We will simply pass this as the first argument and strip it out


Document the default values of the ADDJOB command options

Hello, not merging that because I think the current defaults are odd... The first step is to fix those opening an issue to chat. The for the other PRs as well!


cmake build fails on Ubuntu bionic ppc64le

cmake version 3.10.2 aborts the build:
CMake Error at src/training/CMakeLists.txt:4 (cmake_policy):
  Policy "CMP0074" is not known to this version of CMake.

Can this policy be set conditionally only for newer versions of cmake?
After removing the policy line, the build sets wrong linker options for Curl (caused by commit c4ad9b7bbf1a390872402cf52cc52e9e9f4901e2):
CMake Error at CMakeLists.txt:812 (add_executable):
  Target "tesseract" links to target "CURL::libcurl" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
[...]

After fixing that locally, building tesseract works, but the training tools give linker errors:
[ 90%] Linking CXX executable ../../bin/text2image
cd /home/ubuntu/src/github/tesseract-ocr/tesseract/build/src/training && /usr/bin/cmake -E cmake_link_script CMakeFiles/text2image.dir/link.txt --verbose=1
/usr/bin/clang++-10  -O3 -DNDEBUG -Wno-unused-command-line-argument   CMakeFiles/text2image.dir/text2image.cpp.o CMakeFiles/text2image.dir/degradeimage.cpp.o  -o ../../bin/text2image libpango_training.a libunicharset_training.a libcommon_training.a ../../libtesseract.a -lpthread /usr/lib/powerpc64le-linux-gnu/libarchive.so /usr/lib/powerpc64le-linux-gnu/libcurl.so -llept
/usr/bin/ld: libpango_training.a(ligature_table.cpp.o): undefined reference to symbol '_ZN6icu_608ByteSink5FlushEv'
//usr/lib/powerpc64le-linux-gnu/libicuuc.so.60: error adding symbols: DSO missing from command line
clang: error: linker command failed with exit code 1 (use -v to see invocation)
src/training/CMakeFiles/text2image.dir/build.make:126: recipe for target 'bin/text2image' failed
make[2]: *** [bin/text2image] Error 1
make[2]: Leaving directory '/home/ubuntu/src/github/tesseract-ocr/tesseract/build'
CMakeFiles/Makefile2:228: recipe for target 'src/training/CMakeFiles/text2image.dir/all' failed
make[1]: *** [src/training/CMakeFiles/text2image.dir/all] Error 2
make[1]: Leaving directory '/home/ubuntu/src/github/tesseract-ocr/tesseract/build'
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

That looks like the linker does not get called with all necessary libraries.

Commit e1764e1bc837bd3005f06318bcfaeaddf53c0476 fixes the problem with clang policy CMP0074.

Commit e1764e1bc837bd3005f06318bcfaeaddf53c0476 fixes the problem with clang policy CMP0074.

The linker errors are also caused by the cmake version: <XXX>_LINK_LIBRARIES variables which are currently used in the training build are only supported since cmake 3.12.

cmake version 3.10.2 aborts the build

We should bump minimum cmake version then.

version 3.10.2 was released 4 years ago. The current version is 3.22.1. Any chance they would include a newer version?

Ubuntu bionic is version 18.4. According action there is no problem with building training tools.
Can you check if all necessary libraries are installed and OK? Maybe reinstall icu libs?

We should bump minimum cmake version then.

Ubuntu bionic comes with clang 3.10.2 and is supported until 2023. So I'd wait with dropping that version.

Can you check if all necessary libraries are installed and OK? Maybe reinstall icu libs?

Replacing <XXX>_LINK_LIBRARIES (which is not supported by clang 3.10.2) fixes the build, so it does not look like a problem of missing libraries.

Ubuntu bionic comes with clang 3.10.2
I assume you mean cmake 3.10.2. Right?

I did not get this. Why build on Ubuntu 18.04.6 works (x86?), but on the ppc64le not (icu)? I expect there is the same version of cmake (and other packages).

Thanks, yes, it should be cmake, not clang. I fixed my comment now. And cmake on Ubuntu bionic x86* should have the same problem, so either there is a newer cmake version (where from?) or it does not use the problematic lines.

GitHub actions for Ubuntu always use the latest cmake version (not the one which is provided by Ubuntu). Therefore those CI actions don't have a problem.

This issue was fixed by pull request #3705.

What about requiring 3.10 as the minimum CMake version instead of 3.7?

That would be possible, but is it necessary? Do we already or do we want to use features which work with 3.10, but not with 3.7?

Do we already or do we want to use features which work with 3.10, but not with 3.7?

I don't know.
Did you tested 5.01 with 3.7? If you did not, how do you know we don't use a CMake feature that is not supported in CMake 3.7?

Debian stretch has 3.7. I now did a test there, and cmake failed.
CMakeLists.txt uses TREE (supported since 3.8) and check_ipo_supported (supported since 3.9). So the cmake build already requires 3.9, and we should indeed update the documented requirement.
For Debian stretch there is a newer version in stretch-backports, and Ubuntu bionic already has 3.10. Therefore requiring 3.10 would be fine for me, too.

See pull request #3724.


feat(client): add detailed resuming message when upload got interrupted

Use logger.error to add detailed message about draft number for
resuming upload actions in gas.upload_dataset() and
dataset_client.upload_segment().

Pull Request Test Coverage Report for Build 834910483

8 of 30 (26.67%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 80.255%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tensorbay/client/gas.py
3
13
23.08%

tensorbay/client/dataset.py
3
15
20.0%

Totals

Change from base Build 834900971:
-0.2%

Covered Lines:
4272

Relevant Lines:
5323

💛  - Coveralls