Proposal: speed advisories

I'm a "podspeeder." I listen to most podcasts at 2.5× with the silence-truncating feature enabled. I adjust this on a per-podcast basis when necessary. For example, I listen to comedy without silence-truncation and at slower speeds.
But I run into a problem where a podcast I can normally consume just fine at my preferred speeds has sections that I can't understand unless they're slowed down to normal. Such spots are usually from accents, poor audio quality, music I need to hear (not bumpers), or other complicated audio (like crosstalk or not-background-enough music).
Thus, I wonder if it might help to allow podcasters to add a speed advisory to their podcasts and chapters. Then, the playback apps would have an optional toggle to honor these speed advisories. When such an app reaches that chapter (or other indicator), it temporarily slows down the playback.
I think relative terms would be best, like "slower." We could advise that such sections be played at 50% of the difference between 1.0× and the current playback speed. This, a "slower" on my 2.5× would result in a temporary drop to 1.75×.
While there could be a case for "slowest" to drop down to 1.0× or maybe 25% of the difference, I don't think there would be much (if any) need for a "faster" option, even though I've heard some unbelievably slow-talkers in some podcast voicemails.
I know Adam is adamantly against playback speed changes, but it's here to stay and a lot of listeners find it easier and often more enjoyable to consume content faster. So I think it might be worth considering making this experience a little better for listeners.
I think this would be most logical to include inside chapters, since we can already have hidden chapters.
One important challenge to this is potential abuse by podcasters trying to force people to listen to the whole show at slower speeds, or slowing down ads. But this is why I think it should be an advisory and apps should allow such advisories to be honored or ignored app-wide or podcast-specific.
I think "speedAdvisory": "slower" would be the ideal JSON option.

I like this a lot.  A chapter label for “ad” is probably appropriate as well.  Even if it never gets used it seems good to have for a complete spec.
Most apps will have pre-set speed options. I wonder if “slower” could just mean “temporarily drop down one notch unless it’s already at 1.0”. I can see this being useful for intro and outro music where the music sounds screwy at fast speed.

I, too, really like the sound of this. I like it being relative too, but perhaps there's a case for explicitly recommending default speed too? I.e. for a music segment it feels like I want default speed or my regular speed, but something inbetween won't give me much of anything.
Then again, perhaps it's better to just leave it up to the app to define what exactly slower means.

Main reason I would like this is playing music-parts at original 1.0x speed. Not even sure if that needs an advisory [?], my podcast player would just need to know the chapter/part is type "music".
In my podcast player I would say: play at 1.0x speed for chapters tagged "music". Not yet sure how to handle accents. Maybe parts would be tagged "clip" and I would set 1.5x speed for all clips?

I like that idea, @AbelLykens! Instead of a speed advisory, it could be a chapter type and apps could have preset speed changes for chapter types, or maybe some kind of "speed for" tag.
For example, my player could default to 2.5× for everything, but play all "music" chapters play at 1.0×, all "heavy accent" chapters play at 1.75×, and such.
We need to be careful with anything that could allow an app to automatically skip or speed through ads. Podcasters would hate that and I think it would draw too much negative controversy and thus inspire developers to not even bother supporting a tag or feature that could be used to hurt podcasters.

From a client end-user perspective I would not like the creator to determine the speeds I listen my podcasts at. What is 'complicated audio' or 'heavy accent' is highly subjective.
For me the only valid use-case is the identification of music-fragments (including intro/outro). I would therefore (as proposed above) go for a content type identification (e.g. 'music', 'intro', 'outro', 'clip', etc) rather than any indication of suggested speeds (e.g. 'slower') or subjective classification (e.g. 'heavy accent').

From a client end-user perspective I would not like the creator to determine the speeds I listen my podcasts at. What is 'complicated audio' or 'heavy accent' is highly subjective.
For me the only valid use-case is the identification of music-fragments (including intro/outro). I would therefore (as proposed above) go for a content type identification (e.g. 'music', 'intro', 'outro', 'clip', etc) rather than any indication of suggested speeds (e.g. 'slower') or subjective classification (e.g. 'heavy accent').

From a client end-user perspective I would not like the creator to determine the speeds I listen my podcasts at. What is 'complicated audio' or 'heavy accent' is highly subjective.

The point is for this to be an advisory and the consumer could tell their app to ignore speed advisories.

The point is for this to be an advisory and the consumer could tell their app to ignore speed advisories.

Agreed. The question is whether we (the podcaster) advices

which speeds the user should follow (tags indicating the speeds), or
which segments benefit from a different speeds (tags indicating the segment types), or
a combination of both.

I think the having at least the segment types will be easier for the client/end-user to handle. Because it is so subjective, I might want to follow the advisory regarding the music segment, but ignore the advisory on the heavy accent segment. If the tag only provides the speeds (without the segment types) that'll be impossible to achieve.
A combination of both would probably be most interesting.

Would this be the appropriate issue to support setting the playback speed?

Circling back to this proposal now that transcripts are becoming more widespread, I would suggest that we can actually infer speed changes from transcript timestamps. The rate of speech in a chapter or a segment can easily be measured in words per minute (wpm) by dividing the number of words spoken by the duration of the span in question.
Pros:

Doesn't require a new tag or attribute, so it helps to keep the tag bloating under control
Works with JSON, SRT and VTT transcripts (basically, any transcript format that has start/end timestamps)
Would provide a more objective measure of the actual rate of speech than if we let the podcast author subjectively assign a speed themselves, since what feels slow to one person may feel fast to another person
Apps could translate the wpm into the proposed "slower" / "normal" / "faster" types of categories if they wanted to, but could do one better by automatically adjusting the audio precisely to your desired wpm. E.g. If I can cope with listening at 300wpm, but this segment is 150wpm, it can automatically 2x the speed. If another segment is 200wpm, it can 1.5x the speed. This could also be a point of app differentiation in the market.

Cons:

Depends on having transcripts (although the proposed approach depends on having chapters anyway, and maybe it's good to have another incentive to actually provide transcripts for all the new possibilities they open)
Depends on the app implementing it (although so does the proposed approach)
Still requires manual control if you could normally cope with 300wpm except for a particular science podcast with lots of condensed jargon (although I think manual control should be an option in every alternative)

Note to implementers: wpm is often calculated in practice by counting the number of characters, and dividing that by the average number of characters in a word (in English, that's 5 characters per word on average). This is a bit more robust against sentences that by chance happen to have lots of big long words in it, and it makes the calculation more straightforward for some other languages that don't use spaces for word separation.

wpm is often calculated in practice by counting the number of characters, and dividing that by the average number of characters in a word

If it helps - for English, three words a second is a pretty good approximation. Most radio ad copywriters will write 90 words for a 30-second ad. Source: I was a radio ad copywriter for over eight years.
I'm really liking this as an idea, btw. It, of course, depends on transcripts.

"The rate of speech in a chapter or a segment can easily be measured in words per minute (wpm) by dividing the number of words spoken by the duration of the span in question."
That's an interesting idea, but I'm not sure it really serves the purpose. My goal is not to advise a speed based on how fast someone is talking, but based on the content.
Consider, for example (but I'm not recommending this), a non-regular participant with a thick "accent" (to the ear of the listener) might be very difficult to understand at 2×, but the normal host can be understood fine at 2×. So the transcript of the two speakers might have the same number of words per minute, but the understandability is significantly different.
More practically, though, consider the words per minute of music, which is usually much lower than speaking. Transcript-based speed advisories might then recommend speeding up the music, when I'm suggesting the podcaster should be able to advice slowing down the playback during times to focus on the music.
I understand that even the whole concept of podspeeding angers some people. However, people do it anyway (and some people can actually comprehend and retain the content better when they listen faster). So my desire in this proposal is a way to ensure their preferred experience doesn't break when music becomes a temporary focus during a portion of an episode.


Adds solar model

This is the enhanced API version of https://huggingface.co/upstage/SOLAR-10.7B-Instruct-v1.0, based on https://arxiv.org/abs/2312.15166. Developers can get their API key from https://console.upstage.ai/. 😊 Let us know if you need more information.
https://developers.upstage.ai/product-guides/solar

Thanks for your integration. I will test it with your new feature soon.


[firebase_auth] [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: NoSuchMethodError: The method '[]' was called on null.

I am continuously getting these error messages in all my firebase projects.
import 'package:flutter/material.dart';
import 'package:firebase_auth/firebase_auth.dart';

void main() => runApp(MyApp());

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

class MyHomePage extends StatelessWidget {
  String email;
  String password;
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Firebase Retest'),
      ),
      body: Column(
        children: <Widget>[
          TextField(
            onChanged: (value) {
              email = value;
            },
          ),
          TextField(
            onChanged: (value) {
              password = value;
            },
          ),
          RaisedButton(
            child: Text('Sign Up'),
            onPressed: () {
              FirebaseAuth.instance
                  .createUserWithEmailAndPassword(
                      email: email, password: password)
                  .then((result) {
                print(result.user.email);
              });
            },
          ),
        ],
      ),
    );
  }
}

dependencies :
firebase_auth: ^0.15.5+2
I/BiChannelGoogleApi(12641): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzaq@1e23187
D/FirebaseAuth(12641): Notifying id token listeners about user ( lFNdsGC2ITVoKNIChfd3McZ0buA2 ).
D/FirebaseAuth(12641): Notifying auth state listeners about user ( lFNdsGC2ITVoKNIChfd3McZ0buA2 ).
E/flutter (12641): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: NoSuchMethodError: The method '[]' was called on null.

Someone please help me i got stuck.
Yesterday it was working but i don't know why it's not working today
flutter doctor -v
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Mac OS X 10.15.2 19C57,
    locale en-IN)
    • Flutter version 1.12.13+hotfix.8 at /Users/aftab/Desktop/flutter
    • Framework revision 0b8abb4724 (7 weeks ago), 2020-02-11 11:44:36 -0800
    • Engine revision e1e6ced81d
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/aftab/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3, Build version 11C29
    • CocoaPods version 1.9.1

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

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

[!] Connected device
    ! No devices available

flutter run --verbose
[  +35 ms] executing: [/Users/aftab/Desktop/flutter/] git -c
log.showSignature=false log -n 1 --pretty=format:%H
[  +44 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
--pretty=format:%H
[   +1 ms] 0b8abb4724aa590dd0f429683339b1e045a1594d
[   +1 ms] executing: [/Users/aftab/Desktop/flutter/] git describe --match
v*.*.* --first-parent --long --tags
[  +12 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long
--tags
[        ] v1.12.13+hotfix.8-0-g0b8abb472
[  +10 ms] executing: [/Users/aftab/Desktop/flutter/] git rev-parse --abbrev-ref
--symbolic @{u}
[   +7 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/Users/aftab/Desktop/flutter/] git ls-remote --get-url
origin
[   +7 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +68 ms] executing: [/Users/aftab/Desktop/flutter/] git rev-parse --abbrev-ref
HEAD
[   +8 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[   +7 ms] executing: sw_vers -productName
[  +18 ms] Exit code 0 from: sw_vers -productName
[        ] Mac OS X
[        ] executing: sw_vers -productVersion
[  +22 ms] Exit code 0 from: sw_vers -productVersion
[        ] 10.15.2
[        ] executing: sw_vers -buildVersion
[  +19 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 19C57
[  +38 ms] executing: /usr/bin/xcode-select --print-path
[  +10 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[        ] /Applications/Xcode.app/Contents/Developer
[   +1 ms] executing: /usr/bin/xcodebuild -version
[ +142 ms] Exit code 0 from: /usr/bin/xcodebuild -version
[   +2 ms] Xcode 11.3
           Build version 11C29
[  +71 ms] executing: /Users/aftab/Library/Android/sdk/platform-tools/adb
devices -l
[   +8 ms] Exit code 0 from: /Users/aftab/Library/Android/sdk/platform-tools/adb
devices -l
[        ] List of devices attached
[  +17 ms] executing:
/Users/aftab/Desktop/flutter/bin/cache/artifacts/libimobiledevice/idevice_id -h
[  +68 ms] /usr/bin/xcrun simctl list --json devices
[ +137 ms] No supported devices connected.
[  +13 ms] "flutter run" took 589ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.validateCommand
(package:flutter_tools/src/commands/run.dart:289:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand
(package:flutter_tools/src/runner/flutter_command.dart:590:11)
#3      FlutterCommand.run.<anonymous closure>
(package:flutter_tools/src/runner/flutter_command.dart:515:33)
<asynchronous suspension>
#4      AppContext.run.<anonymous closure>
(package:flutter_tools/src/base/context.dart:146:29)
#5      _rootRun (dart:async/zone.dart:1126:13)
#6      _CustomZone.run (dart:async/zone.dart:1023:19)
#7      _runZoned (dart:async/zone.dart:1518:10)
#8      runZoned (dart:async/zone.dart:1465:12)
#9      AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#10     FlutterCommand.run
(package:flutter_tools/src/runner/flutter_command.dart:505:20)
#11     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#12     FlutterCommandRunner.runCommand.<anonymous closure>
(package:flutter_tools/src/runner/flutter_command_runner.dart:413:21)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure>
(package:flutter_tools/src/base/context.dart:146:29)
#14     _rootRun (dart:async/zone.dart:1126:13)
#15     _CustomZone.run (dart:async/zone.dart:1023:19)
#16     _runZoned (dart:async/zone.dart:1518:10)
#17     runZoned (dart:async/zone.dart:1465:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#19     FlutterCommandRunner.runCommand
(package:flutter_tools/src/runner/flutter_command_runner.dart:364:19)
#20     CommandRunner.run.<anonymous closure>
(package:args/command_runner.dart:112:25)
#21     new Future.sync (dart:async/future.dart:224:31)
#22     CommandRunner.run (package:args/command_runner.dart:112:14)
#23     FlutterCommandRunner.run
(package:flutter_tools/src/runner/flutter_command_runner.dart:250:18)
#24     run.<anonymous closure>.<anonymous closure>
(package:flutter_tools/runner.dart:63:22)
#25     _rootRun (dart:async/zone.dart:1126:13)
#26     _CustomZone.run (dart:async/zone.dart:1023:19)
#27     _runZoned (dart:async/zone.dart:1518:10)
#28     runZoned (dart:async/zone.dart:1502:12)
#29     run.<anonymous closure> (package:flutter_tools/runner.dart:61:18)
<asynchronous suspension>
#30     AppContext.run.<anonymous closure>
(package:flutter_tools/src/base/context.dart:146:29)
#31     _rootRun (dart:async/zone.dart:1126:13)
#32     _CustomZone.run (dart:async/zone.dart:1023:19)
#33     _runZoned (dart:async/zone.dart:1518:10)
#34     runZoned (dart:async/zone.dart:1465:12)
#35     AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#36     runInContext (package:flutter_tools/src/context_runner.dart:64:24)
#37     run (package:flutter_tools/runner.dart:50:10)
#38     main (package:flutter_tools/executable.dart:65:9)
#39     main
(file:///Users/aftab/Desktop/flutter/packages/flutter_tools/bin/flutter_tools.da
rt:8:3)
#40     _startIsolate.<anonymous closure>
(dart:isolate-patch/isolate_patch.dart:305:32)
#41     _RawReceivePortImpl._handleMessage
(dart:isolate-patch/isolate_patch.dart:174:12)

Someone please help me

Hi @saffer4u
You are not properly assigning your textfield values to your variable
Convert your stateless class to stateful and setState for each variable
Code Sample
import 'package:flutter/material.dart';
import 'package:firebase_auth/firebase_auth.dart';

void main() => runApp(MyApp());

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

class MyHomePage extends StatefulWidget {
  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  String email;

  String password;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Firebase Retest'),
      ),
      body: Column(
        children: <Widget>[
          TextField(
            onChanged: (value) {
              setState(() {
                email = value;
              });
            },
          ),
          TextField(
            onChanged: (value) {
              setState(() {
                password = value;
              });
            },
          ),
          RaisedButton(
            child: Text('Sign Up'),
            onPressed: () {
              FirebaseAuth.instance
                  .createUserWithEmailAndPassword(
                      email: email, password: password)
                  .then((result) {
                print(result.user.email);
              });
            },
          ),
        ],
      ),
    );
  }
}

I/BiChannelGoogleApi(25380): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzaq@b469f11
D/FirebaseAuth(25380): Notifying id token listeners about user ( wNHQvQbPu7amwkpdQsU77deXXkC2 ).
D/FirebaseAuth(25380): Notifying auth state listeners about user ( wNHQvQbPu7amwkpdQsU77deXXkC2 ).

Make sure you've  Email and Password auth enable in your firebase console too
Closing, as this isn't an issue with firebase_auth itself,
if you disagree please write in the comments and I will reopen it
Thank you

Hii  TahaTesser
I did the same as you told me, and my email and password auth is also enabled in firebase console,
but i'm still getting this error.
import 'package:flutter/material.dart';
import 'package:firebase_auth/firebase_auth.dart';

void main() => runApp(MyApp());

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

class MyHomePage extends StatefulWidget {
  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  String email;

  String password;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Firebase Retest'),
      ),
      body: Column(
        children: <Widget>[
          TextField(
            onChanged: (value) {
              setState(() {
                email = value;
              });
            },
          ),
          TextField(
            onChanged: (value) {
              setState(() {
                password = value;
              });
            },
          ),
          RaisedButton(
            child: Text('Sign Up'),
            onPressed: () {
              FirebaseAuth.instance
                  .createUserWithEmailAndPassword(
                      email: email, password: password)
                  .then((result) {
                print(result.user.email);
              });
            },
          ),
        ],
      ),
    );
  }
}

Everything was working fine two days before, but now this error is not going away it's happening in all my firebase auth projects.
I/BiChannelGoogleApi(16913): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzaq@2b926a
D/FirebaseAuth(16913): Notifying id token listeners about user ( 0urI4ivkTwV75PHCNfhREkxKEPX2 ).
D/FirebaseAuth(16913): Notifying auth state listeners about user ( 0urI4ivkTwV75PHCNfhREkxKEPX2 ).
E/flutter (16913): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: NoSuchMethodError: The method '[]' was called on null.

Any update on this?
I just updated to firebase_auth: ^0.15.3 and having exactly the same issue now.
@saffer4u did you fix it?

Some debugging shows that it first occurs with firebase_auth 0.12.0. The version right before was fine.

Same problem here

Could everyone who still has this problem please file a new issue with the exact description of what happens, logs and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Every single dev branch since November 2023 (efe601a) get detected and auto deleted by Windows Security

I have noticed from the last 2-3 months that every single build from the dev branch gets flagged as a dangerous file. It starts from the Chrome downloads and even after brute force downloading it from the browser, it will most definitely get flagged by Windows Security at some random time (most likely when am away from the PC or left the Miner unattended).
Even if I exclude the application in Windows Security exclusion, it still somehow ends up deleting it at random times. This doesn't used to happen as prevalent like now since the given build number. And this is why I am still running the older dev builds despite me wanting to try the latest ones. Any solutions to this?

Hello o/
Build version doesn't really matter, it's the AV signatures being updated that changes the detection status instead.

Any solutions to this?

Yes - use a better / smarter antivirus engine. ESET, Kaspersky, BitDefender, AVG, etc. Otherwise, you'll have to keep dealing with Windows Security being too stupid to understand what a packaged Python interpreter executable is, and how to deal with it. If the ignore/exclusion list isn't enough, then I can't really help you. "Fixing" this would require switching the entire project to use a different packaging method, other than PyInstaller. If you'd still have no luck, you can always run the whole application from source, or build an executable yourself - some instructions for that can be found here: https://github.com/DevilXD/TwitchDropsMiner/wiki/Setting-up-the-environment,-building-and-running
This is also a duplicate of #384, #335, #333, #315, #284, #270, #249, #217, #209 and #13. Another one to the collection :+1:


feat: add separate page just for the prompt, no data

fix EOT-11

I think we need to do a deep design review for this, lots of decisions. Should this be its own tab? If so how do we design the tabs if we're going to have more than 2 tabs later on? Should it instead be a popup modal? I think the prompt should be on the left maybe? maybe worth talking about sync first.


An incorrect foreign_key variable for the belongs_to attribute should trigger the same compile time check that occurs when an incorrect foreign_key is determined by diesel.

Setup
Rust: rustc 1.62.1 (e092d0b6b 2022-07-16)
Diesel: 1.4.1
Database: mysql
Operating System Ubuntu 20.04.4
Problem Description
The  belonging_to attribute will cause a compile error (error: proc-macro derive panicked) if it cannot find the expected default value. However, it will not perform the same check if the user specifies an incorrect foreign_key value.
What are you trying to accomplish?
Expand error checking to look at what the user provided and throw an error if it is not valid.
What is the expected output?
A "error: proc-macro derive panicked" should be displayed if an incorrect foreign_key is supplied. And the nice message on how to fix it "help: message: No field with column name foo_fiz_id".
What is the actual output?
No output. No error is thrown.
Are you seeing any additional errors?
No.
Steps to reproduce
Follow the steps at https://docs.rs/diesel/latest/diesel/associations/index.html . But specify an incorrect foreign_key for the belongs_to attribute.
Checklist

[x ] I have already looked over the issue tracker  and the disussion forum  for similar possible closed issues.

[x ] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)

[ x] This issue can be reproduced without requiring a third party crate

Please provide a complete minimal example. (To be clear this issue does not match the code in your example in the gitter channel because it does use a valid column name there, as id exists on your table.)

Yes, I see that now. I guess I should not have opened this just before calling it a night. :)


:book: Add development notes for debugging stations

This adds notes on how to use entanglement and edgevpn to create debugging stations for development
cc @jimmykarily

Nice! Very useful!


Rule fix: RequireBlankSpecial

*BLANK refers to a single space in RPGLE, not an empty string.

Updated to extension 0.20.0, (happens in prior versions also), single character blanks in strings for SQL statement strings are highlighted.   It might also happen with QCMDEXC command strings but I dont have an example of that appearing.

Other examples where the rules should not mark code.

@m-tyler solely screenshots are absolutely not helpful. Please just paste the content as well. Thanks!
0.20.0 was a big change under the hood so I was expecting new issues too.

Screen shots were just to visualize the results.
The blank issue happens in the prior version at least, maybe in older ones as well.  I was planning on putting in an issue of my own then I saw this sitting.
A source file I hope helps show where the rule causes me troubles.  If I happen to use the Format Document (Shift+Alt+F) command to auto fix linter items, it fixes these then most of the marked lines will end up being incorrect.
ISSUE_132_RPGLE.RPGLE.txt

Fix incoming this weekend!


"Mirșid" , "Firminiș" , "Moigrad-Porolissum" , "Popeni" are listed in the drop-down menu

Description:
The villages are listed in the drop-down menu alongside its corresponding county and city, according to the law
Preconditions:  the  website is up and runing. After every step delete the text you typed from the search bar.

Step 1
Write in the search bar "Mirșid"

Expected results
The location appears in the drop-down menu as "Sat Mirșid, SĂLAJ (Mirșid)"

Step 2
Write in the search bar "Firminiș"

Expected results
The location appears in the drop-down menu as "Sat Firminiș, SĂLAJ (Mirșid)"

Step 3
Write in the search bar "Moigrad-Porolissum"

Expected results
The location appears in the drop-down menu as "Sat Moigrad-Porolissum, SĂLAJ (Mirșid)"

Step 4
Write in the search bar "Popeni"

Expected results
The location appears in the drop-down menu as "Sat Popeni, SĂLAJ (Mirșid)"


Cant install

https://media.discordapp.net/attachments/548374067133022220/600946544749051907/unknown.png
Full Error:
Name: Discord For Word
From: https://office.terminal.ink/DiscordForWord.vsto
************** Exception Text **************
System.Security.SecurityException: Customized functionality in this application will not work because the certificate used to sign the deployment manifest for Discord For Word or its location is not trusted. Contact your administrator for further assistance.
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInTrustEvaluator.VerifyTrustPromptKeyInternal(ClickOnceTrustPromptKeyValue promptKeyValue, DeploymentSignatureInformation signatureInformation, String productName, TrustStatus status)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInTrustEvaluator.VerifyTrustUsingPromptKey(Uri manifest, DeploymentSignatureInformation signatureInformation, String productName, TrustStatus status)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.ProcessSHA2Manifest(ActivationContext context, DeploymentSignatureInformation signatureInformation, PermissionSet permissionsRequested, Uri manifest, ManifestSignatureInformationCollection signatures, AddInInstallationStatus installState, TrustStatus sha256TrustStatus, X509Certificate2 sha256PublisherCert)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.VerifySecurity(ActivationContext context, Uri manifest, AddInInstallationStatus installState)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
The Zone of the assembly that failed was:
MyComputer
I've added that link to my "Internet Properties" and I've checked it out.

my bad, when I typed "ink", I misread and typed "link"

Everybody makes mistakes - hope you like the program!


--logging option should be case insensitive

Description
teku --logging debug should work to set the log level to debug, but it has to be teku --logging DEBUG.  We should match case insensitively.

the option is still case insensitive, but the debug command is confusing the processing of the command line.
to fix, we will:

rename the debug subcommand to debug-tools

also noticed that the error level was not present in the log levels, so i'll have a look at that too.


After reading the latest chapter, the unread display on the bookshelf has not been updated

Steps to reproduce
Return to the bookshelf after reading
Expected behavior
The unread count on the bookshelf is displayed normally
Actual behavior
The unread display on the shelf is the state before reading
Crash logs
No response
Tachiyomi version
TachiyomiSY Dev Build 471
Android version
Android 12
Device
miui13
Other details
The unread display of the bookshelf has not been updated. You need to switch to another page and then switch back to the bookshelf to display it normally
TachiyomiSY 1.8.4 Stable version is normal
Acknowledgements

[X] This is a TachiyomiSY specific issue that does not happen in Tachiyomi Preview.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to version 1.8.4.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Known main Tachi issue


[WIP][SPARK-24005][CORE] Remove usage of Scala’s parallel collection

What changes were proposed in this pull request?
In the PR, I propose to replace usage of Scala parallel collections on executors side by new methods parmap(). The methods use futures to transform a sequential collection by applying a lambda function to each element in parallel. The result of parmap is another regular (sequential) collection.
How was this patch tested?
I am still testing the changes.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #93754 has started for PR 21913 at commit 506fa93.

Test build #93754 has finished for PR 21913 at commit 506fa93.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93754/
Test FAILed.

Test build #93755 has started for PR 21913 at commit 515d393.

Test build #93755 has finished for PR 21913 at commit 515d393.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93755/
Test FAILed.

Test build #93756 has started for PR 21913 at commit e3df464.

Test build #93756 has finished for PR 21913 at commit e3df464.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93756/
Test FAILed.

Test build #93780 has started for PR 21913 at commit 3601550.

Test build #93780 has finished for PR 21913 at commit 3601550.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93780/
Test PASSed.

cc @zsxwing

What problem does this solve?

What problem does this solve?

@srowen readParquetFootersInParallel is called in executors. When a task is cancelled, it will still keeping run. If it reads lots of files, it will take pretty long and occupy the task slow. This change is basically to make it interruptible.
@MaxGekk Maybe add the following test to ThreadUtilsSuite. It shows what this PR is fixing.
  test("parmap should be interruptible") {
    val t = new Thread() {
      setDaemon(true)

      override def run() {
        try {
          // "par" is uninterruptible. The following will keep running even if the thread is
          // interrupted. We should prefer to use "ThreadUtils.parmap".
          //
          // (1 to 10).par.flatMap { i =>
          //   Thread.sleep(100000)
          //   1 to i
          // }
          //
          ThreadUtils.parmap(1 to 10, "test", 2) { i =>
            Thread.sleep(100000)
            1 to i
          }.flatten
        } catch {
          case _: InterruptedException => // excepted
        }
      }
    }
    t.start()
    eventually(timeout(10.seconds)) {
      assert(t.isAlive)
    }
    t.interrupt()
    eventually(timeout(10.seconds)) {
      assert(!t.isAlive)
    }
  }

OK, got it. Yes that's worth mentioning in the doc too.
I'll have to go read up to get why this works differently, but obviously accept that it does.
There are other instances of .par, like in UnionRDD and in ddl.scala. Same treatment?

Yeah, let's also fix other instances.

Test build #94134 has started for PR 21913 at commit 6a5f2ae.

Test build #94134 has finished for PR 21913 at commit 6a5f2ae.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/94134/
Test FAILed.

Test build #94242 has started for PR 21913 at commit cf48d8d.

jenkins, retest this, please

Test build #94246 has started for PR 21913 at commit cf48d8d.

Test build #94246 has finished for PR 21913 at commit cf48d8d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/94246/
Test FAILed.

Test build #94248 has started for PR 21913 at commit 610154c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/94248/
Test PASSed.

LGTM, merging to master!


Is it possible to use POST method with data-remote

Is it possible to override the GET request when performing AJAX remote validation queries rather than the default GET?

Nope, sorry. This will be possible once I add support for async custom validators using promises, but I can't tell you when that's gonna come. I haven't had much time lately to work on the plugin, so it could be awhile. Your best bet in the meantime is to fork the project.

Many thanks for the fast response - any pointers to the code that currently handles the AJAX call?

On 11 Jul 2017, at 22:39, Cina Saffary<EMAIL_ADDRESS>wrote:
Nope, sorry. This will be possible once I add support for async custom validators using promises, but I can't tell you when that's gonna come. I haven't had much time lately to work on the plugin, so it could be awhile. Your best bet in the meantime is to fork the project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/1000hz/bootstrap-validator/issues/567#issuecomment-314580088, or mute the thread https://github.com/notifications/unsubscribe-auth/AarpDP7mhG-X881evBfrkRXUX0-VjAEoks5sM-t4gaJpZM4OU2AO.

Yup, you just need to change this method to $.post
https://github.com/1000hz/bootstrap-validator/blob/master/js/validator.js#L218

Thank you Cina - very much appreciated and good luck with the next release.
Simon.

On 11 Jul 2017, at 22:43, Cina Saffary<EMAIL_ADDRESS>wrote:
Yup, you just need to change this method to $.post
https://github.com/1000hz/bootstrap-validator/blob/master/js/validator.js#L218 https://github.com/1000hz/bootstrap-validator/blob/master/js/validator.js#L218
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/1000hz/bootstrap-validator/issues/567#issuecomment-314581029, or mute the thread https://github.com/notifications/unsubscribe-auth/AarpDPeAZd-EhyR5ooqubtZNAeHzEBM2ks5sM-x2gaJpZM4OU2AO.


POK-manager.sh emtpies itself

I run my ARK servers on a PC in my local network but my public IP is changing every day and my internet connection is dropped for a few minutes when it gets renewed. To restart the ARK servers after this I wrote a script which checks every 5 minutes the status of POK-manager.sh -status. When it find the line "Server not found under the current IP" it will stop the ARK instance and then start it again. The issue is, that the file POK-manager.sh is empty (0Bytes) after this.
My guess is that POK-manager.sh wants to update itself somewhere in the process. In the functions check_for_POK_updates() and update_manager_and_instances() you just check if wget or curl is available and if so it will run the command wget -q -O "$temp_file" "$script_url". But when you run this command without internet connection or against a wrong URL it will create an empty /tmp/POK-manager.sh file which later in the process will replace the real POK-manager.sh file.
Can you please add a check to replace the file only when for example the MD5 checksum is verified or if thats too much then maybe a check if the file has at least a certain size or grep something from the file to verify it is not empty?

Thanks for the feedback i added a fix for it hopefully it helps out with the issue

Thanks. Checking if the file is at least 1KB should prevent it. I guess it should also be in the function update_manager_and_instances() .
And just for information. With the MD5 Checksum I meant to check the checksum of the downloaded file against a checksum file on the server like for example Linux updates do this. But I think this is not necessary and more work as you have to change the checksum file on the server after each update. The cmp command to check the local file against the downloaded was good as it was. But the MD5 comparison is also good.

Thanks again for the valuable feedback! I’ve updated the update_manager_and_instances() function to include the 1KB file size check, just like we did in the check_for_POK_updates() function.
I’ve also kept the use of the cmp command to compare the current script with the downloaded version, which should keep things simple and effective.
As I’m still learning, your input is helping me a lot to improve the script.


[KIECLOUD-714] - Remove behave tests from rhpam|bamoe-kogito-builder …

…image
Thank you for submitting this pull request
JIRA: (please edit the JIRA link if it exists)
link
referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)

referenced pull request 1
referenced pull request 2
referenced pull request 2
etc.

How to retest a PR or trigger a specific build:

* a pull request please add comment: Jenkins retest this

r runtime-jvm and runtime-native images ?

Didn't we agree on the meeting last week to only remove from the builder as in the other images the behave tests was taking around 1 minute to complete?

well I though, as we are running behave tests on QE side, that there is no need on build side to run them. I would prefer to: either run for all or run for none.

that works too.

@radtriste update, please take a look.


Since we don't change parameter vec after the call, make vec constant.

Constant reference plays a light-weight call-by-value semantic.

We should accept this once CI clears.
@mbartling What's the flow to have CI on this thing?

First off @lubatang can you change the PR target to utensor:develop. Master is only updated on release. Once you make this change, then CI should run automatically.

I found develop branch has already some changed. I will close this PR and create another clear one.


Fix for the issue filter_post_data_parameters not working with aiohttp #398

A test_replace_post_data_parameters_with_body_type_as_dict is added under /vcrpy/tests/unit/test_filters.py

I implemented a fix for this before noticing this PR. However I don't think the implementation here is correct -- I believe it would not work appropriately when filter_post_data_parameters or remove_post_data_parameters delegates to it, nor it behaves as the API docs say with regards to replacements possibly being callables: https://vcrpy.readthedocs.io/en/latest/advanced.html#advanced-use-of-filter-headers-filter-query-parameters-and-filter-post-data-parameters
My version of the fix in #582 should behave appropriately with regards to these issues, and has some more unit test to showcase it.


Fix IE11 split

Turns out polyfilling isn't as straight forward as we thought. Basically the "this" wasn't passed through to our polyfill so we were just calling Array.prototype.slice which would return an empty array every time.
Going back to the original approach of manually checking for Uint8Array.

Can we confirm that this will work before waiting for SauceLabs to fail?

Agreed. It looks like the daily tests that caught this only take 17 minutes. @natemcmaster spoke to @mikaelm12 and me about a way to use Azure Pipelines run these tests on PR that opt into it. We should look into that.
#5114

I made sure this passes.

/AzurePipelines run AspNetCore-SignalR-Daily-Tests

AspNetCore-SignalR-Daily-Tests is only available in the internal-only CI. You'll need to create a public version

Yeah, I was a bit confused on that. So his comment just re ran the regular valication  I'm guessing then?

/AzurePipelines run AspNetCore-pr-validation-temp

/AzurePipelines run AspNetCore-pr-validation-temp


Add more notification types to listen to and reload accounts on

@keybase/react-hackers

@keybase/react-hackers bump

Thanks @buoyad.  @patrickxb, any reason to reload payment details on receiving a requestStatusNotification?

Nope.


Correct config usage

Hey there 👋.
Thanks for putting this together.
I noticed a couple issues when running the tool and have updated accordingly.
Changes:

Adds GITHUB_APP_TOKEN for encrypting Dependabot secret.
Use GITHUB_PRIVATE_KEY for signing JWT token.
Use DEPENDABOT_ORG configuration when finding the GitHub organisation install. (This was hard-coded)
Removes unused DEPENDABOT_OWNER configuration option

Release artifacts are available here: https://github.com/TierMobility/codeartifact-dependabot-sync/releases/tag/v0.2.0


'Category' tags for TsGroup must be array

Pynapple ignores/does not raise issue when passed a list instead of an array for tsgroup tags

I can't reproduce this error. If I do
import pynapple as nap
import numpy as np
group =   {
            0: nap.Ts(t=np.arange(10)),
            1: nap.Ts(t=np.arange(20)),
            2: nap.Ts(t=np.arange(30))
           }
tsgroup = nap.TsGroup(group, a  = [0, 1, 2])

tsgroup.set_info(b=[3,4,5])

I get
  Index    rate    a    b
-------  ------  ---  ---
      0    0.34    0    3
      1    0.69    1    4
      2    1.03    2    5

Can you paste the error you got more in details?

thanks closing this


/admin-ui 404's for Data Flow server in 1.2.0.BUILD-SNAPSHOT

Try /dashboard?

@mstine: we moved away from the admin term a while back; please see the docs here.


Add metadata provider

Adds definitions for the NFTMetadataProvider.
Currently blocked.

Two mentionable points:

I think it would be nice to create a solidity contract defining an "umbrella" interface for metadata stuff. We are currently abusing the fact, that the metadata of all contracts for which metadata is requested, implements the ERC721IMetadata interface. Any opinions?

I fixed a typo in our naming and I am certain it will break stuff in other repositories.


Unhandled exception when extracting checkum on ESP32

I have been using some variant of TinyGPS++, both works well but your parser seems to work @10Mhz
(for really low power) using the esp32 platform.
Minor snag: esp32 doesn't include this (for atoi/atof or something)
#include <stdlib.h>

However, the more pressing issue is that every now and then I get
0x400d3507: nmea::util::extractChecksum(char const*) at /Users/xxx/Documents/Arduino/libraries/107-Arduino-NMEA-Parser/src/nmea/util/checksum.cpp line 94
0x400d352d: nmea::util::isChecksumOk(char const*) at /Users/xxx/Documents/Arduino/libraries/107-Arduino-NMEA-Parser/src/nmea/util/checksum.cpp line 49
0x400d2f97: ArduinoNmeaParser::encode(char) at /Users/xxx/Documents/Arduino/libraries/107-Arduino-NMEA-Parser/src/ArduinoNmeaParser.cpp line 73

I haven't looked that much at the code yet, but was hoping you would have a quick idea what it might be ?
Thanks!
(the above from the below, after installing this https://github.com/me-no-dev/EspExceptionDecoder)
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

I can confirm that this library doesn't compile for esp32.
one solution would be to add
#include <stdlib_noniso.h>
to GxRMC.h and GxGGA.h
However I don't know if supporting esp32 is intended.
But I wasn't able to reproduce your error. I will have to do more testing.

hi.
I can confirm that this library doesn't compile for esp32.
one solution would be to add
#include <stdlib_noniso.h>
to GxRMC.h and GxGGA.h
However I don't know if supporting esp32 is intended.
But I wasn't able to reproduce your error. I will have to do more testing.

Hi @jhjulkun :wave: :coffee:
One possible cause could be that you receiving some NMEA messages which do not contain the delimiter char * used for marking the checksum. Try changing extractChecksum like this:
uint8_t extractChecksum(char const * const nmea_str)
{
  char checksum_str[3] = {0};
  /* Find the start of the checksum message */
  char const * start_checksum = strchr(nmea_str, '*');
-  /* Extract checksum. */
-  strncpy(checksum_str, start_checksum + 1, 2);
-  /* Convert to integer. */
-  return strtol(checksum_str, nullptr, 16);
+  if (start_checksum)
+  {
+    /* Extract checksum. */
+    strncpy(checksum_str, start_checksum + 1, 2);
+    /* Convert to integer. */
+    return strtol(checksum_str, nullptr, 16);
+  }
+  else
+    return 0;
}

Hi @jhjulkun :wave: :coffee:
One possible cause could be that you receiving some NMEA messages which do not contain the delimiter char * used for marking the checksum. Try changing extractChecksum like this:
uint8_t extractChecksum(char const * const nmea_str)
{
  char checksum_str[3] = {0};
  /* Find the start of the checksum message */
  char const * start_checksum = strchr(nmea_str, '*');
-  /* Extract checksum. */
-  strncpy(checksum_str, start_checksum + 1, 2);
-  /* Convert to integer. */
-  return strtol(checksum_str, nullptr, 16);
+  if (start_checksum)
+  {
+    /* Extract checksum. */
+    strncpy(checksum_str, start_checksum + 1, 2);
+    /* Convert to integer. */
+    return strtol(checksum_str, nullptr, 16);
+  }
+  else
+    return 0;
}

Thanks! Yes, since code didn't check for NULL, its a likely candidate (but I always thought there was a * in NMEA?).
Anyway, running updated code now, but like stated it happened infrequently, and when it did it was right after waking esp32/gps from sleep (ublox neo6 device). I'll keep you posted if it crashes again.

Thanks! Yes, since code didn't check for NULL, its a likely candidate (but I always thought there was a * in NMEA?).
Anyway, running updated code now, but like stated it happened infrequently, and when it did it was right after waking esp32/gps from sleep (ublox neo6 device). I'll keep you posted if it crashes again.

It may also happen due to a buffer overrun earlier in the code although I've not found any problematic code. It would help if you could add a Serial.println(checksum_str); in case of a checksum error so we can take a look at the buffer content. (That would be really helpful :wink:)

It may also happen due to a buffer overrun earlier in the code although I've not found any problematic code. It would help if you could add a Serial.println(checksum_str); in case of a checksum error so we can take a look at the buffer content. (That would be really helpful :wink:)

Interesting, made the changes below to isChecksumOk(), and some of the strings look truncated (some could be explained by the fact that both the esp32&gps wakes from sleep/powercycle), but two of them at a glance look like real strings.
checksum fail for '$GPGGA,080444.00,50.7,M,38.5,M,,6A
'
checksum fail for ',1.10,28.1,M,38.5,M,,66
'
checksum fail for '$GPGSV,3,1,11,02,320,,16,21,040,297E
'
checksum fail for '$GPGSV,3,3,11,26,04,017,,29,08,323,0,A,A6F
'
bool isChecksumOk(char const * const nmea_str)
{
bool ok = calcChecksum(nmea_str) == extractChecksum(nmea_str);
if (!ok) {
Serial.print("checksum fail for '");
Serial.print(nmea_str);
Serial.println("'");
}
return (ok);
}

Interesting, made the changes below to isChecksumOk(), and some of the strings look truncated (some could be explained by the fact that both the esp32&gps wakes from sleep/powercycle), but two of them at a glance look like real strings.
checksum fail for '$GPGGA,080444.00,50.7,M,38.5,M,,6A
'
checksum fail for ',1.10,28.1,M,38.5,M,,66
'
checksum fail for '$GPGSV,3,1,11,02,320,,16,21,040,297E
'
checksum fail for '$GPGSV,3,3,11,26,04,017,,29,08,323,0,A,A6F
'
bool isChecksumOk(char const * const nmea_str)
{
bool ok = calcChecksum(nmea_str) == extractChecksum(nmea_str);
if (!ok) {
Serial.print("checksum fail for '");
Serial.print(nmea_str);
Serial.println("'");
}
return (ok);
}

Hi :wave:
This is interesting already but not precisely what we are looking for. The checksum can also fail for other reasons. Maybe you've got baud rate issues and your UART is decoding some of those bytes wrong (it could be given your low CPU frequency). Better change the code this way:
Hi @jhjulkun :wave: :coffee:
One possible cause could be that you receiving some NMEA messages which do not contain the delimiter char * used for marking the checksum. Try changing extractChecksum like this:
uint8_t extractChecksum(char const * const nmea_str)
{
  char checksum_str[3] = {0};
  /* Find the start of the checksum message */
  char const * start_checksum = strchr(nmea_str, '*');
-  /* Extract checksum. */
-  strncpy(checksum_str, start_checksum + 1, 2);
-  /* Convert to integer. */
-  return strtol(checksum_str, nullptr, 16);
+  if (start_checksum)
+  {
+    /* Extract checksum. */
+    strncpy(checksum_str, start_checksum + 1, 2);
+    /* Convert to integer. */
+    return strtol(checksum_str, nullptr, 16);
+  }
+  else
+  {
+    Serial.print("checksum fail for '");
+    Serial.print(checksum_str);
+    Serial.println("'");
+    return 0;
+  }
}

Hi :wave:
This is interesting already but not precisely what we are looking for. The checksum can also fail for other reasons. Maybe you've got baud rate issues and your UART is decoding some of those bytes wrong (it could be given your low CPU frequency). Better change the code this way:
Hi @jhjulkun :wave: :coffee:
One possible cause could be that you receiving some NMEA messages which do not contain the delimiter char * used for marking the checksum. Try changing extractChecksum like this:
uint8_t extractChecksum(char const * const nmea_str)
{
  char checksum_str[3] = {0};
  /* Find the start of the checksum message */
  char const * start_checksum = strchr(nmea_str, '*');
-  /* Extract checksum. */
-  strncpy(checksum_str, start_checksum + 1, 2);
-  /* Convert to integer. */
-  return strtol(checksum_str, nullptr, 16);
+  if (start_checksum)
+  {
+    /* Extract checksum. */
+    strncpy(checksum_str, start_checksum + 1, 2);
+    /* Convert to integer. */
+    return strtol(checksum_str, nullptr, 16);
+  }
+  else
+  {
+    Serial.print("checksum fail for '");
+    Serial.print(checksum_str);
+    Serial.println("'");
+    return 0;
+  }
}

Have been running the above changes for a bit, but it has not printed anything yet (it only crashed a couple times yesterday).
Its not the cpu frequency btw, I already tried that, and the esp32 has HW uarts (but not sure how big a buffer they have).
I'll keep you posted once it prints something.
But got curious about the Viper quadcopter project, looks cool!
Are you guys planning on selling kits at some point ? How much works so far ?

Have been running the above changes for a bit, but it has not printed anything yet (it only crashed a couple times yesterday).
Its not the cpu frequency btw, I already tried that, and the esp32 has HW uarts (but not sure how big a buffer they have).
I'll keep you posted once it prints something.
But got curious about the Viper quadcopter project, looks cool!
Are you guys planning on selling kits at some point ? How much works so far ?

Ok, just happened:
checksum fail for ''

Ok, just happened:
checksum fail for ''

That's interesting, I'll give it some thought. With regards to the Viper MAV project ... it might be sold as a kit some point or you just assemble all the parts yourself. If you're interested I'd encourage you to take a look every now and then here.

That's interesting, I'll give it some thought. With regards to the Viper MAV project ... it might be sold as a kit some point or you just assemble all the parts yourself. If you're interested I'd encourage you to take a look every now and then here.

Maybe you can augment another function for me:

Maybe you can augment another function for me:

I think I found the source. The culprit seems to be that the parser is out of sync with you going into low-power mode and powering up again. Please try the code in #33 and let me know if it fixes your problem.

I think I found the source. The culprit seems to be that the parser is out of sync with you going into low-power mode and powering up again. Please try the code in #33 and let me know if it fixes your problem.

Thanks, trying it now (will run over night), and will let you know if it still happens.
Btw, I never got the above debug message to happen at same time as there was checksum error.

Thanks, trying it now (will run over night), and will let you know if it still happens.
Btw, I never got the above debug message to happen at same time as there was checksum error.

You still get a couple of checksum fails for empty strings, in conjunction with the isChecksumOk test.
Overall 41 blank checksum (which w/o the fix would have caused a crash),
935 corrupted NMEA messages, with a total of 7497576 parsed characters.
Since I do power up/down the GPS corrupted nmea strings is very likely, but since the parser doesn't crash anymore so I would call this fixed (and yes, it still seems to parse out the data).
checksum fail for '' parser_buf.buf = '$GPGLL,56 ' parser_buf.elems_in_buf = 12 checksum fail for '' parser_buf.buf = '$GPRMC,2F ' parser_buf.elems_in_buf = 12

You still get a couple of checksum fails for empty strings, in conjunction with the isChecksumOk test.
Overall 41 blank checksum (which w/o the fix would have caused a crash),
935 corrupted NMEA messages, with a total of 7497576 parsed characters.
Since I do power up/down the GPS corrupted nmea strings is very likely, but since the parser doesn't crash anymore so I would call this fixed (and yes, it still seems to parse out the data).
checksum fail for '' parser_buf.buf = '$GPGLL,56 ' parser_buf.elems_in_buf = 12 checksum fail for '' parser_buf.buf = '$GPRMC,2F ' parser_buf.elems_in_buf = 12

Thank you for the test but that's not satisfying enough. I think I've nailed the issue now. I https://github.com/107-systems/107-Arduino-NMEA-Parser/pull/33/commits/edafe97d7ac33203c4d81386f0d9a7b6249766db I've added a test to produce the memory violationa and in https://github.com/107-systems/107-Arduino-NMEA-Parser/pull/33/commits/51732341958bca7e35b5e47df40249eabb33cf95 I've fixed the offender. I'd be most obliged if you could run another test.

Thank you for the test but that's not satisfying enough. I think I've nailed the issue now. I https://github.com/107-systems/107-Arduino-NMEA-Parser/pull/33/commits/edafe97d7ac33203c4d81386f0d9a7b6249766db I've added a test to produce the memory violationa and in https://github.com/107-systems/107-Arduino-NMEA-Parser/pull/33/commits/51732341958bca7e35b5e47df40249eabb33cf95 I've fixed the offender. I'd be most obliged if you could run another test.

No problems.

No problems.

So 384 failed cksum, 22 blank cksums, 3474630 characters, and no crashes.
(sorry, a little less data, but needed the computer on the porch for other things too)
As long as it doesn't crash, and parser works @10Mhz on the esp32 I'm happy (and yes parser works, took device out for walk, it tracked nicely)
checksum fail for '' parser_buff = '$GPGGA,103350.00, ' _parser_buf.elems_in_buf = 20 checksum fail for '' parser_buff = '$GPGSV,4,1,13,05,36 ' _parser_buf.elems_in_buf = 22

So 384 failed cksum, 22 blank cksums, 3474630 characters, and no crashes.
(sorry, a little less data, but needed the computer on the porch for other things too)
As long as it doesn't crash, and parser works @10Mhz on the esp32 I'm happy (and yes parser works, took device out for walk, it tracked nicely)
checksum fail for '' parser_buff = '$GPGGA,103350.00, ' _parser_buf.elems_in_buf = 20 checksum fail for '' parser_buff = '$GPGSV,4,1,13,05,36 ' _parser_buf.elems_in_buf = 22

Fantastic, I'm gonna merge than. Thanks for the test!

Fantastic, I'm gonna merge than. Thanks for the test!


Update dapi protocol contract addresses

the dAPI contract addresses have been redeploy here. This PR is to update them in the documentation

clsoing because @wkande will push using a script


Fix inherited includes for object libraries

Should fix #232 and #235

@white238  Looks like pthread stuff is biting us on windows? Any idea why thats popping up now?
@mclarsen also got bit by pthread linking, I think post @corbett5's recent changes.  Matt can you confirm what version you where using so we can unravel the mystery?
Could it be that recent changes fixed in one place and broke in others?

[  9%] Linking CUDA executable ../../../tests/blt_cuda_runtime_smoke nvcc fatal   : Unknown option 'pthread'
commit 800ef02c5d173db3725c62f7e68d312afc52e7b7
Author: Benjamin Curtice Corbett<EMAIL_ADDRESS>Date:   Mon Mar 4 12:12:44 2019 -0800
Forward gtest_disable_pthreads to gtest.

@mclarsen do you have set(gtest_disable_pthreads ON CACHE BOOL "") in your host config?

@corbett5 that might be the key.
Q: was the pthreads fix needed for you in the case when you were linking with NVCC?

The pthreads issue is orthogonal to the object library and no I did not have that set. Is there a reason pthreads shouldn't always be off for gtest?

@cyrush the axom blueos nvcc host config had set(gtest_disable_pthreads ON CACHE BOOL ""). This was enough to build everything and run tests which didn't depend on pthreads. However tests which used gtest features that used pthreads (TEST_P for example) would fail at runtime.  800ef02 fixed that.
@mclarsen I would try adding that flag and see what happens.

@mclarsen -- I am pretty sure the gtest death tests use threads. They are disabled by default though and have to be explicitly enabled. I am not sure what other gtest features use threads.
I am not sure why you are seeing this issue now, but I don't think that @corbett5's change should be affecting you or object libraries, since it only adds a compiler define when the gtest_disable_pthreads option is added.  (Said differently, his change will not affect you if you have not set this option).
The better question is why @corbett5's change was needed when things previously worked on blue_os with nvcc (although @corbett5, please correct me if I'm wrong).  Perhaps there was a change to the system that required this?
Links:

Death tests: https://github.com/google/googletest/blob/master/googletest/docs/advanced.md#death-tests
BLT support for death tests: https://github.com/LLNL/blt/blob/master/thirdparty_builtin/CMakeLists.txt#L22-L31
@corbett5's PR: https://github.com/LLNL/blt/pull/233/files

@kennyweiss we didn't have a blue_os nvcc build in axom, I encountered the issue that led to #233 while creating that build. And the issue I was having wasn't with death tests, it was with the parameterized tests TEST_P which uses at least a pthreads mutex.

I tested this on the now more complicated test on both 3.9.2 (old target libraries) and 3.13.4 (new ones)

I just tried this and I am now getting a CMake error:
Object library target "vtkm_compiled_filters" may not link to anything.
Doing some googling,  Object libraries cannot be linked from the CMake 3.9 documentation. I think the ability to link object files was added in 3.12.

Specifically i am adding an object library:
blt_add_library(   NAME vtkm_compiled_filters   SOURCES ${vtkm_filters_sources}   HEADERS ${vtkm_filters_headers}   DEPENDS_ON ${vtkm_filters_deps}   OBJECT TRUE   )
where vtkm_filter_deps has an external library registered with BLT. It hits the target_link_libraries command on line 185 of BLTPrivateMacros.cmake  with the error:
Object library target "vtkm_compiled_filters" may not link to anything.

@mclarsen given the vtkm deps are bonafide imported cmake targets, for now can you check if you see if this works if you pass their proper names to blt_add_library, instead of using the name you created in blt_register_library?  I think that may work and it would also point out what we need to test next to get BLT full working.

This is definitely the case where I am surprised this passed my tests... try adding “arg_OBJECT OR “ to the beginning of the if check on line 173 of BLTPrivateMacros.cmake.

If i use the vtkm_cont target directly, it also fails. If I remove the vtkm dependency all together, it fails trying to link cuda in, all in with the same error message.

@white238 Adding that allowed cmake to complete the configure, but cmake still seems not to propagate the dependencies. On the compile line, the headers are not being included, and with the cuda dependency, the object is being compiled with gcc instead of nvcc.
If you have any time this week, I would be happy to sit down with you.

FYI: We worked through our issues and tested with ascent - i think this is ready to merge.


Release schedule?

What's the release schedule for this project? Fixes have been piling for a month. It'd be nice to start benefitting from them...

Completely our bad - we've been lagging behind as our team has worked on a bunch of big projects (like the site). We just made our big 1.2.0 release, and we plan to move to a 2 week cadence with absolutely nothing waiting longer than a month. We apologize for the pretty extreme delay in this release!

:+1:


custom field type and wrong decorator signature rule

Fixes #5

Codecov Report

Merging #9 into main will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #9   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           17        17
  Lines          307       311    +4
  Branches        94        97    +3
=========================================
+ Hits           307       311    +4

Impacted Files
Coverage Δ

src/rules/wrong-decorator-signature.ts
100.00% <100.00%> (ø)

src/util/typeGraphQLUtil.ts
100.00% <100.00%> (ø)

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 cfff12f...3228572. Read the comment docs.

Would be great if the rule would also document the default mappings that are enabled by default.

And also whether defining custom mapping for a type that overlaps with default mappings will replace or just extend default one.

Would be great if the rule would also document the default mappings that are enabled by default.

Added the default mappings to the docs!

And also whether defining custom mapping for a type that overlaps with default mappings will replace or just extend the default one.

That is a good point, I have added and documented an optional flag that allows you to do either.


Add section on Auth0

Removed small section mentioning that auth0 uses base64 encoded secrets. It doesn't anymore.

Great, thank you! Will cleanup and merge later on :)

@thibaultcha Let me know your style guide and I can improve it. I don't mind translating it to curl if that's the default.

Translated to curl would be great! Thanks

Done.

Manually merged with a few edits, thank you!


add path for client_secrets.json in sample_tools.py

I add path for client_secrets.json in sample_tools.py, because we have some accounts then we need to prepare some client_secrets.json.
To use the same script with several json files, I made each directory and set env files in the directories.

This PR is stale, and needs attention.  @t-Asai, do you want to follow up on comments, or should we close this?

Closing this as the original author @t-Asai has not responded. Please feel free to re-open.


All async queries do not work as expected.

All async queries do not work as expected. I must refactor the async query api to do polling. Please only use the current* commands and do your own client-side polling strategy for now.

I will fix it with the next release


GCalCli won't install on Ubuntu 20

Here is what I got installing from package:

Here is what I got installing manually:
~/gcalcli$ python setup.py install
File "setup.py", line 15
print('Warning: No long description generated.', file=sys.stderr)
^
SyntaxError: invalid syntax
Any idea how to fix this?

You are running it through Python2, Python3 is required.
If you're still getting probably after using Python3, try installing it through pipx
https://pipxproject.github.io/pipx/


AlternateReport's message link missing the server's ID

Hey, whenever I try reporting someone's message and the Trust & Safety form opens, the message link seems to never work. I got used to it and I always came back and copied the message link with another plugin and proceeded without any issues, but I've got tired lol.
The message link that goes to my clipboard whenever I open the form does not contain the ID of the said server (if the message is from a server, obviously). The image below describes it perfectly.

NOTE¹: The first link is the one that goes to my clipboard when I'm reporting someone while the second one is the message link, which was manually copied.
NOTE²: They're from the same message

huh i guess they changed it


Format Date

Docs:
https://shoelace.style/components/format-date
Source:
https://github.com/shoelace-style/shoelace/tree/next/src/components/format-date
Description
Properties
Dependencies

Outside of completeness, I don't know if there is a great reason to create this as a component


Inconsistent results with Redis OM .NET vs CLI query / Node OM

Finding inconsistencies between the .NET OM package, Node OM package and regular Redis CLI / Redis Insight. The following query:
FT.SEARCH products "@VendorId:{6b11fdc8\\-d5f1\\-477a\\-997f\\-ebc2c1460fdb}" LIMIT 0 10 SORTBY Name DESC
fails to execute in RedisOM .NET, but succeeds in RedisOM Node and in the CLI.
Here's the specific code which throws an exception:
var query = new RedisQuery("products")
{
    SortBy = new RedisSortBy
    {
        Direction = sortDirection == "ASC" ? SortDirection.Ascending : SortDirection.Descending,
        Field = sortField
    },
    Limit = new SearchLimit
    {
        Offset = skip,
        Number = take
    }
};

string queryText = "\"@VendorId:{" + vendorId.ToString().Replace("-", "\\\\-") + "}\"";
if (vendorId.HasValue) query.QueryText = queryText;
if (fields?. Length > 0) query.Return = new ReturnFields(fields.ToList());

var result = await _redis.Connection.SearchAsync<Terminal>(query);

The error I'm getting is this:
Syntax error at offset 1 near VendorId Failed on FT.SEARCH terminals "@VendorId:{6b11fdc8\\-d5f1\\-477a\\-997f\\-ebc2c1460fdb}" LIMIT 0 10 SORTBY Name DESC
The index is built with VendorId as a tag:
[Indexed][Required] public Guid VendorId { get; set; }

Required tag is from System.ComponentModel.DataAnnotations, but that's not relevant.
When I copy the above query and toss it into RedisInsight's Workbench, it works just fine. Also Node's OM package runs the query successfully.
Using Redis.OM 0.4.1. RediSearch 20603 in the cloud.

I cloned this repository and added it as a project to my solution just so I could debug what is going on. Here is some more information:
The exception is thrown exactly at this line:
https://github.com/redis/redis-om-dotnet/blob/main/src/Redis.OM/RedisObjectHandler.cs#L60
The hash dictionary that comes in has only the names of the fields as keys, it does not have a '$', so it throws an exception.

Thanks for the explanation. I did see the difference in response while debugging. I'd like to use the Select statement to build the query, but I'm letting users define which fields they want to see. That Select needs to be built dynamically, hence the Search<T> being brought in instead. Could you recommend a way to accomplish the aforementioned scenario using RedisOM? Search<T> and SearchAsync<T> require a type to be passed in.

@paulers if you change: https://github.com/redis/redis-om-dotnet/blob/main/src/Redis.OM/RedisObjectHandler.cs#L58
from
if (attr != null && attr.StorageType == StorageType.Json)

to
if (attr != null && attr.StorageType == StorageType.Json && hash.ContainsKey("$"))

does that fix the issue for you?

It does indeed. I found that Guid types are not deserialized correctly though. I updated line 407 in the SendToJson method and it's working correctly now:
if (type == typeof(string) || type == typeof(Guid) || type == typeof(GeoLoc) || type == typeof(DateTime) || type == typeof(DateTime?) || type == typeof(DateTimeOffset))

This does fix all the issues I had above for now. Thanks for the assist! Not sure if you want me to close this, or whether you wanna use this issue to track these updates?


Update some test dependencies.

While trying to fix a failing test I tried updating capybara. It failed to update, but in the process several other dependencies were updated. In general it seems good to get these updated. However the update XPath broke our usage XPath:HTML.  I fixed that by using find_button instead.
Capybara cannot be updated because of our usage of Rails 3.2. Capybara itself doesn't care, but cucumber-rails does. Cucumber-rails locks us into the current version of capybara. And we can't update cucumber-rails because the next version of cucumber-rails requires rails 4 or higher.

@knowuh this might be looking at and trying to merge.

I'm closing this because we can update this more easily later now that we've started on the work to upgrade Rails.


JSON error

Under Ubuntu 18 I'm now getting the following error whatever the command (everything work since today):
line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Same under Windows 7.

Might be related to #426
Please be sure to have Twint updated and retry

Now it's working again without updating

@EmanueleCozzo initially it was not working because the server was offline. I highly suggest you to update so that when the website will be offline again, Twint will automatically pick an UA from a given list

I'm going to close this issue since a solution has been found.
For any question I kindly ask you to post it in #426 to avoid duplicates


3d imaging

Is there a way to pull out 3d data instead of buffers.  What i really need is point cloud data instead of regular pixel values. Does harvester really support that or any other genTL producer.
If anyone has an idea please guide me to informative resources

@suhanshaikh33 Hi, Harvester can work with the GenTL Producers that support 3D. Which camera do you have? Regards, Kazunari.

Hello @kazunarikudo, I am trying for the point cloud information as well. Could you point me to the right way to acquire 3D point cloud information. I am having a Roboception rc_visard 65 sensor.


How many FuelManager.instance per context?

This may be a wrong place, but just curious whether FuelManager.instance could handle multiple base urls?
The issue is
I want to use this lib to handle multiple http requests to different base urls, like Fuel.post(url) asynchronously in coroutines. Is this thread/coroutine safe and efficient? Will coroutines share the same FuelManager?

Don't use the global .instance. Instead, create a new FuelManager().

Got you, thanks @SleeplessByte


DOC: Typo in see also s/SmoothUni/SmoothBi/g

From the original commit that introduce that; this seem to be the what
was meant.

Thanks, LGTM

Thanks, LGTM

Hmm, this resulted a bunch of "CI failed" emails. These do not seem related: they originate in test_hausdorff and seem to originate somewhere in numpy (a fresh numpy 1.20 release?)
        np         = <module 'numpy' from '/home/runner/.local/lib/python3.9/site-packages/numpy/__init__.py'>
mtrand.pyx:4478: in numpy.random.mtrand.RandomState.shuffle
    ???
E   UserWarning: `x` isn't a recognized object; `shuffle` is not guaranteed to behave correctly. E.g., non-numpy array/tensor objects with view semantics may contain duplicates after shuffling.

 These do not seem related: they originate in test_hausdorff and seem to originate somewhere in numpy (a fresh numpy 1.20 release?)
        np         = <module 'numpy' from '/home/runner/.local/lib/python3.9/site-packages/numpy/__init__.py'>
mtrand.pyx:4478: in numpy.random.mtrand.RandomState.shuffle
    ???
E   UserWarning: `x` isn't a recognized object; `shuffle` is not guaranteed to behave correctly. E.g., non-numpy array/tensor objects with view semantics may contain duplicates after shuffling.


Eboard error messages cause unhandled exceptions in JSON parsing.

As reported by @christomaszewski.

I think this exception is being generated here:
https://github.com/platypusllc/server/blob/feature/failsafe/src/com/platypus/android/server/Controller.java#L294

Nope, actually that part is fine, what is happening is that the error message is received and propagated to the onCommand() handler, which fails to interpret it.
https://github.com/platypusllc/server/blob/feature/failsafe/src/com/platypus/android/server/VehicleServerImpl.java#L402
This fails because "args" is not a JSON object, it is a string.  The solution is that we should check if the response from the server is an error in Controller, and raise an exception which can be handled if this is the case.

Should be resolved by #37.


Remove fio thread mode check

The daemon works when fio is using threads or processes, get rid of the assumption of fio using threads in the fio engine code.

Addressed in https://github.com/OpenMPDK/FlexAlloc/pull/29

#29 has been merged. closing this. Thx @vincentkfu


All poppers are broken in fullscreen mode when zIndex is modified via muiTablePaperProps

material-react-table version
v2.5.0
react & react-dom versions
v18.2.0
Describe the bug and the steps to reproduce it
When specifying a custom zIndex inside muiTablePaperProps, poppers (such as show/hide columns menu, filter menus in popover filtering mode, etc.) are not rendered correctly when in fullscreen table mode. They get rendered under the fullscreen table, and in their initial non-fullscreen location.
Minimal, Reproducible Example - (Optional, but Recommended)
https://codesandbox.io/p/devbox/nice-kalam-3pcwyg
Screenshots or Videos (Optional)
https://github.com/KevinVandy/material-react-table/assets/93911989/319d572c-c159-456a-87cf-dd6593d1535c
Do you intend to try to help solve this bug with your own PR?
No, because I do not have time to dig into it
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

How big is your custom zIndex? Larger than 200?

Yes, I had to set it to 1201 since this is the only option that goes above my website toolbar. I am using MUI AppBar component with a Toolbar and a Sidebar too, so I guess that 1200 is the default zIndex of AppBar. I tried tweaking the zIndex of the MUI navigation components but it breaks their behaviour.


Query timeout overwrite

Currently, the query option time doesn't overwrite correctly.
We should have:
user-config override should always be considered as the total time (maybe minus planning time, i will explain later)
with this in mind, all the current timeout configuration during query should also be considered as total time
all stages have a fixed timeout at an absolutely ts value = sys.currentTimeNano() + desiredTimeoutNano
if any stage hits this timeout, they will all agree to terminate.
See details in: https://github.com/apache/pinot/pull/9571#issuecomment-1278094979

Is this for multi-stage (v2) engine or also apply to v1? I believe v1 has the correct behavior.

This is for multi-stage only. Let me update the issue title


How can I query a record or a list of records with exact matching property values?

Contact Details
No response
What happened?
I want a situation where only the record or records with the exact property match are returned, instead of those with partial match. For instance, if a record has a property name "field1" and the property value for that that "field1" is "abcdef". If the input value is "abc", that record should not be returned. It should only be returned when the input value is exactly "abcdef".
What I did below does not work. Please how can I achieve this?
const api = new ApiClient()
  api
      .resourceAction({
        resourceId: 'User',
        actionName: 'search',
        query: email,
        params: {
          'filters.email': props.record.params.email
        }
      })
.then(...)

Bug prevalence
Every time
AdminJS dependencies version
"adminjs": "^7.0.5",
What browsers do you see the problem on?
No response
Relevant log output
No response
Relevant code that's giving you issues
No response

Hey! I had a similar issue and found the solution after lots of debugging.
api.resourceAction({
  resourceId: "User",
  actionName: "list",
  params: {
    "filters.email": props.record.params.email,
  },
});

That should do the trick.


Postback support

As far as I noticed there is postback message support in TODO, is it in progress?
If it's not started can I handle this, do you accept pull requests and what is contribution guidelines?

@strangeworks The contribution guidelines are pretty relaxed. And I accept any pull request :)
If you wish to handle that would be super cool!

Okay thanks, I will submit pr asap

@strangeworks Let me know if I can help you in any way :)

#6

@strangeworks fantastic!! I just merged the PR
I will update my bot with this feature...many thanks!

I will add new facebook payload support asap(quick_reply, geocoordinate payloads etc), in order to implement fully functional facebook messenger bot.

@strangeworks that would be great! 👍


Release 3.0.0

See #75

[x] Drop support for []byte when using RSA signing methods
[x] Support for custom Claim types
[x] Migrate ParseFromRequest to a subpackage.
[ ] Modify request parsing API to provide more flexibility.
[ ] Updated release notes and documentation

Hey @dgrijalva, I'd be interested in putting the time in to get this ready to be merged if you can let me know what needs to happen.

@dgrijalva do you still intend to work on this?

Yep. The main remaining thing is getting the oauth/http stuff out into a subpackage and cleaning it up.  I just haven't had time.

This is just about ready to land.  As soon as #137 has been looked at, we can complete the README updates and ship it.  Any remaining issues to be resolved?

Has the issue I mentioned here now been fixed? https://github.com/dgrijalva/jwt-go/pull/73
Thanks!

@StephanDollberg That thread is super long, but I believe we have addressed all the issues.  There are several example uses you can review to see usage.

Oh yeah sorry. It was the issue with https://github.com/dgrijalva/jwt-go/blob/release_3_0_0/token.go#L33 having to return a pointer to MapClaims.

That has been solved, though it's not super elegant. I ended up special casing it. I think it's ok, but we can watch it.
-dave

On Jun 7, 2016, at 11:23 AM, Stephan Dollberg<EMAIL_ADDRESS>wrote:
Oh yeah sorry. It was the issue with https://github.com/dgrijalva/jwt-go/blob/release_3_0_0/token.go#L33 having to return a pointer to MapClaims.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Anything I can do to help push 3.0 out?

There are no remaining issues for 3.0.0.  Shall we ship it (finally)?

The only thing that got left out is support for leeway.  The documentation says about it:

Implementers MAY provide for some small leeway, usually no more than a few minutes, to account for clock skew

I think we can add support for this by modifying Claims. See #131.  Does anyone want to make the case for this in 3.0?

Actually, the change proposed in #131 would enable things like iss validation, etc in the future.  Let me see how hard it would be...

See #139

Let's wait on #139.  Seems like there are several viable approaches.  If you need leeway support today, see #131 for an easy workaround.


Show data of table is persistent on every tab

Describe the bug
Show data of table is persistent on every tab
Severity (remove the excessive)

I have a workaround to keep working

Problem commit => https://github.com/SirRacoozy/DBison/commit/6fc316abbc8668dbc3686d5a6af20d74a814e0ee


IIS\Microsoft Web Deploy V3\msdeploy.exe

Running Deployment to Slot Task is showing success, but Deployment Center is never reporting it as Successful (this was working until 2/27/2020 2:52 PM GMT-6).  Deployment to production slot is working fine.
Command being Ran
2020-03-02T13:17:03.8343536Z [command]"C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -verb:sync -source:IisApp='D:\a\r1\a_Clinical Portal\Portal React App\ClientApp\build' -dest:iisApp='',ComputerName='https://****.scm.azurewebsites.net:443/msdeploy.axd?site=',UserName='*',Password='',AuthType='Basic' -enableRule:AppOffline -retryAttempts:6 -retryInterval:10000 -userAgent:VSTS_78eaf9f2-6424-4199-b742-0cd1436ae6df_Release__464_1766_10
Slot Deployment Was working until Thursday 2/27/2020

Production Slot works but no longer Slot deployment to Stage.

Azure App Service deploy:  Task version 4.*

Task YAML
steps:

task: AzureRmWebAppDeployment@4
displayName: 'Deploy ????? to App Service'
inputs:
azureSubscription: ?????????
WebAppName: '????-??-????'
deployToSlotOrASE: true
ResourceGroupName: ????QaEnv
SlotName: Stage
packageForLinux: '$(System.DefaultWorkingDirectory)/_Clinical Portal/Portal React App/ClientApp/build'
enableCustomDeployment: true
RemoveAdditionalFilesFlag: true
ExcludeFilesFromAppDataFlag: false

I believe this was an Error in my template.  Closing issue if issue persists will inform.


Interupted sound

Problem Description
Hi,
I am trying to run bt_music_sender.ino
with following setup:
ESP32-WROOM32
ESP-IDF 4.3.6
Visual studio + platformio
I hear the sinus sound but it is interupted in every lets say 100-200msec. It sounds like a morse code.
I have tried with example from ESP-IDF the noise as well and it also sound also interupted.
static int32_t bt_app_a2d_data_cb(uint8_t *data, int32_t len)
{
    if (data == NULL || len < 0) {
        return 0;
    }

    int16_t *p_buf = (int16_t *)data;
    for (int i = 0; i < (len >> 1); i++) {
        p_buf[i] = rand() % (1 << 16);
    }

    return len;
}

If I just build I run the example source code of ESP-IDF it sounds without any interuption
If I run your "bt_music_sender_write" there is no any interruption. It sound well.

So what I am wrong with the "bt_music_sender" example?
I have another question. If I run the ESP-IDF example sender my speaker stops the connection after 120sec.
I think heartbeat is running, what I miss?
Thx
Device Description
ESP32-WROOM32
ESP-IDF 4.3.6
Visual studio + platformio
Sketch
bt_music_sender

Other Steps to Reproduce
No response
Provide your Version of the EP32 Arduino Core (or the IDF Version)
ESP-IDF 4.3.6
I have checked existing issues, discussions and online documentation

[X] I confirm I have checked existing issues, discussions and online documentation

Same problem here. :/

As far as I understand you generate a buffer overflow and write past the valid data!


Move to cmake-qt for Building qrenderdoc

Description
Modern CMake provides the cmake-qt module. Currently renderdoc relies on an external invocation of qmake for compiling.
Using cmake-qt would simplify building qrenderdoc drastically since then the whole process around specifying where to find the qmake command would be removed. Also it simplifies passing flags to compile targets.
The only issue is, that this would require at least CMake version 3.0 to be somehow functional.
In case this is something that you are happy to see in the future I can try to look into it.

Environment

RenderDoc version: v1.21
Operating System: Linux Fedora 36
Graphics API: Vulkan

I don't want to make this change, no. The qt project file is used so that qrenderdoc can be built in qt creator standalone, and I don't want to maintain three parallel build systems (default VS solution, qt project, and cmake).
It might be a really small simplification but mostly would move complexity from one place to another, and inevitably with linux some distribution will need new special considerations and flags because the new system of building won't work for them, and those will have to be discovered and fixed. Since the current build works well and is tested I don't see a compelling reason to change it.


Disable e2e tests that are not expected to pass

With https://github.com/neurobagel/annotation_tool/pull/330 merged, we now get the app to run correctly up to the categorization page again. That means that our integration/e2e tests for all pages up to categorization can and are passing again. However, this information is currently hidden in the summary test results because the subsequent page integration tests (annotation and download) are still failing - as expected.
We should disable the integration tests for annotation and download pages as long as we expect them to fail, so that we can get useful summary test results during PR for the integration tests that are now expected to pass.
In other words: e2e test should now be green again and stay like that.

@jarmoza: do you want to do this one?

@surchs Yes, I'll take this one one. It will be part of the phase 2 refactor, and I will have a complementary issue at the end for re-enabling the e2e tests.

Closed by #343


Max call stack exceeded

v0.15.3
I don't have much more log context for this one.

closing, was fixed in 0a2b3a4


[Table] Phase 1 Test - Test against storage C++ SDK

@jongio @XiaoningLiu  C++ don't have table SDK, suggestion on how to do the test?

@v-xuto - Please track this in Azurite test work items.


[Question] adapter for optional types

Is it possible to create generic adapter for Optional<T> https://docs.oracle.com/javase/8/docs/api/java/util/Optional.html ?

Not at the moment. I've created a separate issues for this feature #23


case error for folder name "02_dpctl_Intro"

Check the folder name: AI-and-Analytics/Jupyter/Numba_DPPY_Essentials_training/02_dpctl_Intro
02_dpctl_Intro should be big case C, 02_dpCtl_Intro
Otherwise the link for "Module 2 - Introduction to dpCtl" from https://github.com/oneapi-src/oneAPI-samples/blob/master/AI-and-Analytics/Jupyter/Numba_DPPY_Essentials_training/Welcome.ipynb
which use lower case "c" doesn't work.
thanks.
-Yang

OneSmpl_Team1 working on this.

(OneSmpl_Team1)
@ywang30intel
This issue will not occur in the latest version. This issue can be closed now.