TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95775

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104537

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104538


Please invite me to the community

Name
Hassan Momanyi
Additional Context
I am looking forward to joining the Community to collaborate on upcoming projects and improve my learning curve

Invitation sent to join the GitHub Organization. Welcome to Infraform 🎉Please check your mail to accept the invitation sent by GitHub! 🤖About usInfraform is an open source solution for serverless platforms, it is designed for developing solutions and enhancing creators to create their infrastructure 💻 Great to have you in our community ✨ Looking forward to your valuable contributions! 🤓 You can also check our community ✨ Github ✨ LinkedIn 💜 You can also share our community with other folks who want to learn about development, DevOps, tech, and contribute together and with us 👉💜👈


Hello, can you release a usable package for the latest version of the code? When I pull it up, it's still 1.3.4

Hello, can you release a usable package for the latest version of the code? When I pull it up, it's still 1.3.4

You're right, mybad


Adding additional benchmarks

Linear cross entropy
Quantum volume
Unbiased coin flipping (random-number generator)
QED-C benchmarks (Github link)

QAOA benchmark on Xanadu's Borealis

Borealis is a boson sampler. Has anyone run QAOA on it before?


<Points style="fill" (...) /> doesn't fill 👉 only draws borders

Description
When using <Points /> with the style="fill" option, it only draws the borders (both on iOS & web), while it works as intended when using <Path style="fill" (...) />:

Here's the code for those triangles:
// Draw a triangle
const triangleJsx = <Points
  points={[
    vec(x1, y1), // upper left point
    vec(x1, y2), // upper right point
    vec(x2, y3), // down center point
    vec(x1, y1), // BACK to first point (upper left point)
  ]}
  mode="polygon"
  style="fill"
  color={ '#1877AD' }
/>;

Not sure the style="fill" was ever implemented for Points?
Version
0.1.218
Steps to reproduce
Use the <Points /> component with the style="fill" option.
Snack, code example, screenshot, or link to a repository
Also reproduced using the star Point example from the doc. See in this snack:

Merci @wcandillon ;)

Merci @wcandillon ;)

Does it work for you ? Not for me with the latest release


Update results on Librispeech data set.

@whiteshirt0429

Done in https://github.com/mobvoi/wenet/pull/65

Done in https://github.com/mobvoi/wenet/pull/65


Add command line interface to common task e.g. pipeline operation and ax tm processing

It really time consuming to have to alter the code to process certain tm or change the output location or IDB version etc.
Add a CLI for common task e.g.
stix-pipline --tm-dir /adsf/adf/asdf --fit-dir /adfadf/adfadsf/ --filter 21/6/20

I think this can close, do you agree @nicHoch


Image Loading Problem in Release Version (results in pink container areas)

Internal: b/176078297
I'm facing a really strange problem, and really don't know how to fix this. It seems, that on some devices image assets are not properly loaded and a pink (fuchsia?, magenta?) colored area is shown instead. All types of images are affected (Network loaded images, images shown as Container decoration, and also Asset Images).
I'm not able to reproduce this on my devices, neither as debug, nor as release, neither on iOS nor on Android. The clients device with this problem is a iPhone 12 Pro, iOS: 14.2.1.
Does anybody have seen something like this or can give me a hint about what could cause this?

Hi @hm122
Can you please provide your flutter doctor -v and a minimal complete reproducible code sample of the screen you shared above?
Thank you

Hi @pedromassangocode , thank you for your fast reply. Following the flutter doctor -v output:
flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-AT)
    • Flutter version 1.22.4 at /Users/hannes/Applications/flutter
    • Framework revision 1aafb3a8b9 (10 days ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/hannes/Library/Android/sdk
    • Platform android-30, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

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

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 50.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

I can not reproduce the issue with my devices, even with my clients device it only happens sometimes. Right now, I can not reproduce it anymore. My feeling is that this is kind of a timing issue. My client told me that when he is browsing through the app after a few seconds some images start to appear correctly. But then, if he closes the app and reopens it, everything seems to be working alright.
I'm using the following code to load images:
Container(
  margin: EdgeInsets.fromLTRB(0, 0, margin, 0),
  decoration: BoxDecoration(
    boxShadow: [
      BoxShadow(
        color: Color.fromARGB(45, 0, 0, 0),
        offset: new Offset(2, 8),
        blurRadius: 15.0,
      )
    ],
  ),
  child: Image.asset('assets/images/foobar.png'),
);

Container(
  decoration: BoxDecoration(
    image: DecorationImage(
      image: AssetImage('assets/images/foobar.png'),
      alignment: Alignment.topCenter,
      fit: BoxFit.fitWidth,
    ),
    boxShadow: [
      BoxShadow(
        color: Color.fromARGB(45, 0, 0, 0),
        offset: new Offset(2, 8),
        blurRadius: 15.0,
      )
    ],
),

I got one more screenshot from my client, when the problem was discovered first:

You can see here, that the tile on the right has successfully loaded an image, while the other tiles do have the pink area. One more thing I would like the add, I have never used this pink color anywhere in the whole app.

it is also happening with us.
Only iOS 10 AFAIK and in my iOS 10 is not happening.
Assets and Internet image:

This problem occurs in out project , too. After user switch the app to background for a long time and then switch it back , the Image widget will turn to pink block.

I have the same problem too.Who knows what caused this

I have the same problem too.Who knows what caused this

I have the same problem too，flutter version: 1.12.13-hotfix.9

I have the same problem too，flutter version: 1.12.13-hotfix.9

Same problem, flutter 1.22.4, iPhone. Unable to reproduce on my devices

Same issue on one of my clients device..
Device - iphone 12 mini

For anyone facing this issue please try to provide a minimal reproducible code sample and the steps to reproduce the issue as well so that we can verify the issue and looking for fix.
Thank you

Looks like a serious regression. Trying to find an assignee for this ASAP.

I suspect this is may be because of a missing texture.  The shader is using a sampler with an unbound texture.  Pink is often used for that error.
One way to validate that this is a renderer problem, and not an image file problem, would be to render a layout that depends on the size of the image.  If we get a pink image still and the widget is the correct size that would point to this being a renderer only issue.

I tried as an experiment to bind nil for the textures to see if it draws magenta:
--- a/src/gpu/mtl/GrMtlPipelineState.mm
+++ b/src/gpu/mtl/GrMtlPipelineState.mm
@@ -123,8 +123,14 @@ void GrMtlPipelineState::bindUniforms(id<MTLRenderCommandEncoder> renderCmdEncod
 void GrMtlPipelineState::bindTextures(id<MTLRenderCommandEncoder> renderCmdEncoder) {
     SkASSERT(fNumSamplers == fSamplerBindings.count());
     for (int index = 0; index < fNumSamplers; ++index) {
-        [renderCmdEncoder setFragmentTexture: fSamplerBindings[index].fTexture
-                                     atIndex: index];
+        static int i = 0;
+        if (i++ % 2 == 0) {
+            [renderCmdEncoder setFragmentTexture: nil
+                                         atIndex: index];
+        } else {
+            [renderCmdEncoder setFragmentTexture: fSamplerBindings[index].fTexture
+                                         atIndex: index];
+        }
         [renderCmdEncoder setFragmentSamplerState: fSamplerBindings[index].fSampler->mtlSampler()
                                           atIndex: index];
     }

It rendered clear, not magenta.  It could be some other error in the shader, too.  It's hard to google but someone on the skia team suspected the magenta is coming from Metal to represent some error and not Skia.  The console log might provide clues if Metal is printing out an error.

About blondie63/pic4flutter#23, below the screenshot on iPhone 12 pro Max & iOS 14.4
Flutter (Channel stable, 1.22.6, on macOS 11.2.1 20D74 darwin-x64, locale it-IT)

Here is a proposed fix https://github.com/flutter/engine/pull/24503, can someone that can reproduce the bug please try it out since we don't have reproduction code.

https://github.com/flutter/engine/pull/24503 has now landed, which should make it easier for people to verify it they can reproduce it.

Flutter 2.0.0 fix it ?

The PR I made that I hope fixes the issue isn't in 2.0, it is currently on 2.1.0-10.0.pre and master.  If we get feedback that the PR fixed the issue I can propose it for a hotfix.  If you have reproduction code we are still looking for it, I'm unable to reproduce the issue.  I think it may have to do with how much time your app is occupying on the main thread when it's launched.  You can also try out the fix if you have the ability to reproduce the problem.

i am glad to see your efforts. Actually , the code to reproduce the issue is very simple. https://github.com/flutter/flutter/issues/71074#issuecomment-732170040
the previous comments has already given you a sample , and actually , i find that , even you only use a single Image.asset, the problem will occur in special circumstance .The points to reproduce the problem is not how complicated the code is , but the following steps you do .
1, Do not try to reproduce this problem in debug mode or in any simulator, it happened when a released flutter app was installed in an actual device.
2, Now all the issues occurs on the iPhone 12 , so use an actual iPhone 12 to reproduce and verify it.
3, Remember to switch the app to the background for a time long enough maybe 12-20 hours .
4, Switch the app back to the screen and make sure the app is resumed instead of restarted as the app maybe closed by the system. If the app was restarted , wait for another 12 hours. The issue will not occur when the app is restarted.
5, If you are patient enough to complete the above four steps , then you are very probably to see the Image widgets turned to be pink block.
In my research , this issue maybe caused by the iPhone12 GC mechanism. In iPhone12 ,it allows app to stay a long time in the background , so the app can keep its state without being closed by the system. But the cached bytes and the GPU resources that used to render the Image has been released. So the page and layout can keep fine, but Image turns to be pink block (Is it the placeholder by Flutter engine on iPhone12? ).
I hope these information can help you. Best wishes.

@plank-george with your reproduce steps,  whether https://github.com/flutter/engine/pull/24503 fix the problem?

@gaaclarke: Are you able to reproduce the problem post the patch with @plank-george s instructions?

I hooked up firebase messaging and was unable to reproduce the problem when launching the app either from being backgrounded or a fresh launch (as per the steps specified in the internal bug):
import 'package:flutter/material.dart';
import 'package:firebase_messaging/firebase_messaging.dart';
import 'package:firebase_core/firebase_core.dart';

Future<void> main() async {
  runApp(MyApp());

  await Firebase.initializeApp();
  NotificationSettings settings =
      await FirebaseMessaging.instance.requestPermission(
    alert: true,
    announcement: false,
    badge: true,
    carPlay: false,
    criticalAlert: false,
    provisional: false,
    sound: true,
  );
  print(settings.authorizationStatus);
  print(await FirebaseMessaging.instance.getToken());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);
  final String title;

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

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Container(
        margin: EdgeInsets.fromLTRB(0, 0, 5, 0),
        decoration: BoxDecoration(
          boxShadow: [
            BoxShadow(
              color: Color.fromARGB(45, 0, 0, 0),
              offset: new Offset(2, 8),
              blurRadius: 15.0,
            )
          ],
        ),
        child: Image.asset('assets/1.png'),
      ),
    );
  }
}

It may be that the 20hr backgrounding is required to reproduce the bug and that the notifications was a red herring.  I tried it on 2.0 and on the master channel.

I've tried master channel with example app and steps provided by @pawlowskim in this comment. it didn't fix the issue.
using iPhone 7 with iOS 14.4

Thanks @onikiri2007, I was able to reproduce that bug with those steps.  I suspect they are the same issue, just my device doesn't happen to draw them as magenta.

@gaaclarke
based on our testing - iPhone 12 draws them as magenta, iPhone 11 does not draw them at all/transparent

Re-requesting cp since it's a P2.

Is this on stable right now?

I also still got the same issue on the latest Flutter Version.
Happened on iPhone 11. Image below:

The latest stable release doesn't have the fix yet: https://github.com/flutter/flutter/commit/4266d629c26213ac5cd3f51c875f84e408d33a14

shouldn't be closed/fixed until released on stable branch.

@tryadelion closing issues when they are fixed on master has always been the policy of the team.  You can track the PR's progress with the link I provided above: https://github.com/flutter/flutter/commit/4266d629c26213ac5cd3f51c875f84e408d33a14  I don't have a good idea about when it will land on stable.  You can ask on the discord channel hackers-releases.

@gaaclarke thanks - and sorry, I wasn't trying to sound so imperative, & not trying to say it isn't the policy - just that the flow of the issue is lost once the PR is merged, and in the case of issues that have no workaround at all and affect production devices, like here, we've been answering to customer support for weeks in a not-so-fancy-for-them Indiana Jones way...

And the good news is it's been rolled into the latest stable (2.2.0) with 4266d62 . Please let us know if the issue still exist.

Has everyone solved this problem? I still encounter it.


Add text to speech for events

Having to read all the text from a computer screen is tireing. Optional TTS could really improve the scenarios, even with a robot voice. IMO this issue should have no prio yet, but is a very nice to have.
I fiddled around with System.Speech.
while (true)
{
	using (var synthesizer = new SpeechSynthesizer())
	{
		// show installed voices
		foreach (var v in synthesizer.GetInstalledVoices().Select(v => v.VoiceInfo))
		{
			Console.WriteLine("Name:{0}, Description:{1}, Gender:{2}, Age:{3}",
				v.Name, v.Description, v.Gender, v.Age);
		}

		// select audio device
		synthesizer.SetOutputToDefaultAudioDevice();

		// build and speak a prompt
		var builder = new PromptBuilder();
		builder.AppendText("Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn!");
		synthesizer.Speak(builder);
	}
}

The API seem to be also available on Mono.
http://www.go-mono.com/status/status.aspx?reference=4.0&profile=4.5&assembly=System.Speech

Awww, but that's one of my favorite things to do! And I like to make different voices for each character that speaks.

Entirely optional ;)

Yeah, the only problem that I have with text to speech is how dry it comes out sounding. I guess you can just imagine Stephen Hawking narrating your story!

https://www.youtube.com/watch?v=5bueZoYhUlg&t=58s
The problem is, there are many TTS services and engines available. Most of them sound very similar – quite good but uncanny. The best ones are only available via cloud based services you need to pay for, like the Google Speech API, the Bing Spech API from MS Azure or Amazon Polly. The most promising today is Google Wavenet, but that isn't available to the public yet. The best poor man approach to this would be to just utilize a good offline speech engine, that is available on the specific plattform. I doubt, that there is one, that is available on all plattforms in all required languages. For Windows, there is System.Speech, that performs quite ok.

That is a reasonable suggestion, perhaps this isn't a Valkyrie thing after all then?  If I support different audio based on language it can be up to the scenario author.

Hi guys!
I spent a couple of days and integrated Google TTS.
API key with enabled Cloud TTS required, it would be better to create new for only Valkyrie.
Limitations for WaveNet are: 1 million chars per month for free.
Supported voices: https://cloud.google.com/text-to-speech/docs/voices
The commit is here: https://github.com/antroids/valkyrie/commit/4c81fca4801ab19370b7c2940464f7bbe9b2ec93#diff-a5790b06f63b7c1646f0de34b44fc108377a02fb07aa60b83aaff44deed06398
Feel free to use this code.


[BUG]

Describe the bug
This library can't be used with angular 16.
To Reproduce
Steps to reproduce the behavior:

Create a new angular 16 app
install this library with npm i @frontegg/angular
add FronteggAppModule to appModule
serve application
see error

Expected behavior
Expected to work with the latest versions of angular.

Hi there @danPwiz !
Our frontegg/angular SDK doesn't support yet Angular 16. Please email us at<EMAIL_ADDRESS>and we will add you to the notifications list for the release of a new SDK version that will support Angular 16. Otherwise, please monitor our documentation guides that also mention the supported versions.

@danPwiz We added support for angular 16, now available on the latest


Prevent exception if transport is already null when Connection.prototype._terminate() is called twice

Using node 0.10, when Connection.prototype._terminate() is called, this._transport.end() calls socket.end() which generates an event that leads to _terminate() being called again synchronously (meaning the first call to _terminate() is still waiting for this._transport.end() to return while the second call nullifies the _transport object.
Once the second call is finished, the first call continues and throws an exception when trying to call this._transport.terminate().
This PR should prevent that from happening :)

This change is

@pierreca thanks for the fix, lgtm


When a columnName contains other columnName, one of the two column is decrypt fail

Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
4.0.0-RC3
Which project did you use? Sharding-JDBC or Sharding-Proxy?
Sharding-JDBC
Expected behavior
When a columnName contains other columnName, all the two column is decrypt correct
Actual behavior
When a columnName contains other columnName, one of the two column is decrypt fail
Reason analyze (If you can)
When the column to decrypt,i guess use the string.contains to find the column
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
you can config like this. the bug is always occured.
encrypt:
encryptors:
encryptor_aes:
type: AES
props:
aes.key.value: eyHXCWAoB69&
tables:
sharding_test:
columns:
title:
cipherColumn: title
encryptor: encryptor_aes
a_title:
cipherColumn: a_title
encryptor: encryptor_aes
Example codes for reproduce this issue (such as a github link).

@terrymanu Please assign the bug to me for fixing the case @Keanhua mentioned above.

@SteNicholas Assigned.

@Keanhua Could you please add my wechat 834031959 to give the exception detail?

can not reshow


mypy  Cannot find implementation or library stub for module named "pandas" after installing it

I use venv in combination with python 3.9
I installed it via pip with the activated venv environment.

Hi! Could you please provide logs and the commands you ran to install. Environment definitions would be welcome too. We need more information in order to reproduce your problem. Thanks!

I ran into this as well, but resolved it. My issue was that while I installed pandas-stubs in the activated venv environment, I had installed mypy with sudo apt install mypy (probably from some tutorial when I was starting with mypy), so mypy wasn't seeing the pandas stubs. You should be able to see if your mypy is the correct one with which mypy, and it should be in the same venv folder that's activated (.../venv/bin/mypy).

pandas-stubs has moved to another repository and will now be managed alongside pandas itself: https://github.com/pandas-dev/pandas-stubs
Closing.


add option to continue building on failure when using --recipe-dir

I haven't figured out how to add the option to the CLI, any guidance is appreciated.

Also, can you make sure that the program still exists with an exit code if one of the ouputs failed to build?

Do you still need help with the CLI? Looks like you already managed to make it work?

Yes it seems to work, thank you, i used the wrong command from the CLI myself, so I was confused.

Also, can you make sure that the program still exists with an exit code if one of the ouputs failed to build?

This would be for a singular recipe right? I believe the latest commit includes that as well.


Custom Grid does not have the LocalTextPrefix Key

I have created my own grid but I cannot override the name that is being displayed. What am I missing?

You have miss to change DisplayName in your Row (and InstanceName) and you forgot to read the manual

You already did that

I did that also

See if your LocalTextPrefix in Row constructor is correct (ex "Default.ApprovedSummary")

If your row is reusing an already existing table (i.e. there's another row with same [dbo].sometable), that happens... Probably you should customize the Report Grid based on the original table row.... it that is the issue case.
Best Regards

set this.title in constructor

or override getInitialTitle


Added a Step to override Service Account details in Wrangler Connection Page.

Please squash commits.

Commits squashed.


Improve Sub-Organizations Users Page to Clearly Indicate Shared Users from Parent Organization.

Describe the issue:
The Sub-Organization Users page fails to accurately reflect that the admin user is shared from the parent organization and managed by it.

Expected behavior:
It's better to have at least a managed-by label to improve the user experience there.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

will be improving to add a label indicating that this user is from a parent org


Japanese translation for Pepper&Carrot ep6

First Japanese Translation

@gurugurusp Thank you for the contribution! Can you please also submit those subtitles as community contribution to YouTube video? - https://www.youtube.com/watch?v=cTb1_w8hvqY

Hi, I added the translation to youtube video as well(using a different user name there, though)

Approved now. Thank you!


ORP - C Client - Error reported when SYNC packet received

Added decoding of SYNC packet to C client example
Resolves: BROOKLYN-3489
Signed-off-by: imorrison<EMAIL_ADDRESS>Testing:
imorrison@carmd-ed-11193:~/ws/imorrisonca/octave-orp/clients/c$ ./bin/orp -d /dev/ttyUSB3 -b 115200
ORP Serial Client - "h" for help, "q" to exit
using device: /dev/ttyUSB3, Baud: 115200
Protocol codec initialized

orp >
Received: 'Y13031T1607992228.000000', (28 bytes)
        Type     : 13 (Synchronization, sync)
        Data type: -1
        Sequence : 12337
        Timestamp:<PHONE_NUMBER>.000000

orp > r synack
Sending: '~y1205~', (8 bytes)
        Type     : 14 (Synchronization, sync-ack)
        Data type: 0
        Sequence : 2

Accidentally pushed more changes than intended.  Will close this PR and issue another


max_level doc improvements

see: https://github.com/rust-lang-nursery/log/issues/134

Or maybe https://github.com/rust-lang-nursery/log/issues/125 I'm not sure anymore. Anyway, it improves max_level docs!

@dtolnay Thanks!
You wrote:

The MaxLevel could also be linked but we can follow up separately.

Ok, I can do this! The documentation says:

The maximum log level is set by the MaxLevel token passed to loggers.

Should it refer to set_logger? or MaxLevelFilter set method?


Update the url in version.json file to get Dropdown menu should take you to the equivalent vXXX page feature.

Update the url in script in the for {cname}/dev/ and {cname}/release/{version}/ from {cname}/release/{version} to get use of the feature  Dropdown menu should take you to the equivalent vXXX page posted in the issue https://github.com/ansys/ansys-sphinx-theme/issues/175  posted by @RobPasMue in ansys-sphinx-theme. See https://github.com/ansys/ansys-sphinx-theme/blob/gh-pages/release/versions.json for the format and https://sphinxdocs.ansys.com/dev/getting_started/index.html to explore the feature.
i am not sure, this should fix manually for all those repos in which the multidoc feature has been already implemented. Pinging @jorgepiloto for insights.

I think this feature is automatically inherited once we upgrade to the latest pydata-sphinx-theme. Do you know if this is the expected behavior, @RobPasMue? If so, we only need to care about upgrading our ansys-sphinx-theme and the logic in PyData will take care of the rest.

I can confirm that by upgrading to pydata-sphinx-theme, this will be the default behaviour. No need to modify anything in our side.
PyData Sphinx theme JSON file: https://github.com/pydata/pydata-sphinx-theme/blob/main/docs/_static/switcher.json

After a private discussion this got much clear.


Reference NuGets instead of Xamarin Component Store components

The Xamarin Component restore operation requires a Xamarin account. Since it is no longer required to have a Xamarin account to build Xamarin apps, the component restore operation can fail because the endpoint expects a Xamarin account. Many Xamarin newcomers will not have Xamarin accounts because of its inclusion in Visual Studio and Xamarin Studio.
This goes unnoticed by someone developing with a Xamarin account, but will be a major point of frustration for those running the app for the first time with Community editions of Visual Studio or Xamarin Studio, and with no Xamarin account logged into the IDE.
It would be a good idea to switch all component references to comparable NuGets, as nuget.org does not require authorization to restore packages.

Thanks for your feedback!
We will evaluate the cost/time to update the apps due to not all the same components/versions are available in nuget so the change could be not so easy.

One of those newcomers who don't have Xamarin accounts here:
I need this done. There's no reason to require the account only on this specific case. And there do seem to be components out there worth using from what I can tell, starting, for example, with Android Support Design Library.


CI for every commit

Right now, I believe, the CI runs only for tags and publishing. It would be also great to cover PRs and commits with clippy / tests on CI as well.

Added clippy-check and tests workflow run on PRs as well.

Wouldn't it publish the crate when someone creates a PR?

Fixed. Now two different workflows are in place

build_test_publish.yml: As the name implies it build, test and publish the crate on newly tagged release.

on_pr.yml: Runs when a PR is created and does all the above mentioned actions except publishing the crate to crates.io, instead it --dry-run the publishing flow to check whether everything is configured properly for the publishing or not.


[PE-D][Tester B] App allows patients' phone numbers to have more than 8 digits.

Description:
When inputting a phone number of a patient to add that has more than 8 digits and all other fields are valid, the application allows the patient to be added, despite the UG stating that phone numbers must be exactly 8 digits.
Steps to Reproduce:

Input "add-patient n/testPatient2 ic/T1111110S g/F p/111111111 ec/11111111<EMAIL_ADDRESS>a/NUS c/CS b/A+ t/HIGH"
Press enter

Expected Behaviour:
Expected to get an error message stating that the description for the phone number that I input is invalid and that the phone number should contain exactly 8 digits according to your UG.
Actual Behavior:
The command result shows that the doctor has been successfully added.
Screenshots/Attachments:

Severity/Priority:
High as this does not agree with your UG.
Suggested Fix/Workaround (if any):
Perhaps the parser for the phone number field has an error in it.

Labels: severity.High type.FeatureFlaw
original: markgcera/ped#4

same issue brought up in issue #168


SSD single node training using "train.py" is much slower than using "train_multi.py"

hello, we found that using train.py for single node training is much slower than using train_multi.py.
It seems that it takes a long time in running chainer.iterators.MultiprocessIterator in train.py. Did you see similar issue on your site?
Be notice, even we use train_multi.py, only one node was used.

How did you investigate the duration of chainer.iterators.MultiprocessIterator? Perhaps, changing n_processes has some effect.

can we close this issue?


fix: revert regressions

Turns out, filters aren't available in v3.3 master yet, only in v3.4 dev.
This PR reverts some of the v4 updates, as the deprecated payloads are not longer deprecated as of recent commits.

Pull Request Test Coverage Report for Build 693325418

40 of 50 (80.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.09%) to 75.363%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/core/Player.ts
18
28
64.29%

Files with Coverage Reduction
New Missed Lines
%

src/core/Player.ts
2
37.5%

Totals

Change from base Build 693139076:
-0.09%

Covered Lines:
1500

Relevant Lines:
1992

💛  - Coveralls


Server maintenance mode

Scenario/Intent
OneView 5.2 introduced ability to put servers in Maintenance mode to stop server alerts going to Activities and SCMB.
One of the customers is asking for ability to set the maintenance mode through Ansible playbooks. Request to add this support in the Ansible library and update the examples.
Environment Details

Module Version: [Version of the Oneview-Ansible module for which you are encountering the issue]
**Ansible Version: 2.10.2
**OneView Appliance Version: 5.4
**OneView Client API Version: 2000
**Python Version: 3.6.8
**python-hpOneView SDK Version: 4.8.0
**Platform: CentOS 7.8

Steps to Reproduce
NA
Expected Result
Change server state from Maintenance mode Disable to Enable
Actual Result
Could not find a way to set maintenance mode using the present Ansible-OneView library.

@avgovind Hi Govind, we are looking into this, ill update you once we have this updated in our library.

Thank you very much for adding this enhancement request. I am going to try soon and close this issue.

I got the code from pull request and tried using the following playbook on OneView 5.4 (it failed with API version 1200 and works only when I set to 2000):
- hosts: localhost
  tasks:
  - name: Enable Server Maintenance Mode
    oneview_server_hardware:
      hostname: 10.x.y.z
      username: administrator
      password: password
      api_version: 2000
      state: enable_maintenance_mode
      data:
          name : 'ILOMXQ91002T3.v1000.cce01.presales.hpecorp.net'
    delegate_to: localhost

Can you please merge to main branch so that the customer can access the changes?


Why AzureOpenAITextEmbeddingGenerator class does not have option for ManualTokenCredential?[Question]

Context / Scenario
For Azure OpenAI API calls we are using Token Credential authentication approach. For Text Generation API , it is supported but for embedding API , we get error : Azure OpenAI auth type 'ManualTokenCredential' not available
Question
AzureOpenAITextGenerator class supports ManualTokenCredential for authentication. AzureOpenAITextEmbeddingGenerator allows only Managed identity or API Key. Is it not there for a reason why ManualTokenCredential  is not included? Thanks

Fixed in #295

Thank you for prompt handling of the request!!


3rdIterationLastDetails

Last details: change of some classes names
(AccelerationCard is now Accelaration, for example).
Also we deleted a message of creating a Player that was not longer useful (it's been decreasing the coverage).

Pull Request Test Coverage Report for Build 54

38 of 38 (100.0%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.7%) to 100.0%

Totals

Change from base Build 51:
1.7%

Covered Lines:
576

Relevant Lines:
576

💛  - Coveralls


Use custom type for Optional

We have a lot of code like this:
some_var: Optional[str] = None

Why we can't do it like this:
String = Optional[str]

sove_var: String = None

@sobolevn What do you think?

Nope, that's a bad idea. Optional[str] is very clear type. What is String? Mutable sequence of bytes? Immutable str? Union[str, bytes, unicode]?

@sobolevn Agree, looks not really good.


Improve app delete and env delete experience

Currently when outside of the project repo, it fails to get the project when trying to delete an environment or application. If in the project repo, app delete requires a flag specifying the application name before deleting. And env delete prompts user to input the env name. Would be better to select env name from a list when env delete and app delete.

If outside of a project repo, it prompts user to select a project, then prompts to select an application/env to delete.

If in a project repo, shows an application/env list to select to delete.

app delete must happen inside of a workspace to ensure we can delete the application manifest file.

We've been creating a smaller issues to tackle these usability bugs, resolving this one.
I believe we also added listing the environments in env delete


Cargo Fails to Cross-Compile due to Linker Errors

Build Platform

CPU Architecture: amd64
OS: Debian 10 (latest stable release)
Libraries:

glibc 2.28 (64-bit and 32-bit versions)
openssl 1.1.1d (only the 64-bit version)

Rust toolchain: Installed using rustup on the stable release channel (version 1.53.0)

Target Platform

CPU Architecture: i586
OS: Gentoo Linux
Libraries:

glibc 2.33
openssl 1.1.1k

Problem

When cross-compiling cargo for a different architecture, ld is looking for shared libraries under the wrong directory. On Debian, or at least my computer's instance of Debian, 64-bit libraries are stored under /usr/lib/x86_64-linux-gnu/, and 32-bit libraries are stored under /usr/lib32/. ld SHOULD be looking under /usr/lib32 for the libraries, but it instead looks for them under /usr/lib. Since very few libraries are actually stored under that directory, ld doesn't find any libraries matching what it looks for. Since I have not been able to find a way to pass flags to the rust compiler when a project uses build scripts in cargo and is being cross-compiled (#4423 describes this), I cannot cross-compile cargo itself. The ld error is
/usr/bin/ld: cannot find /lib/libc.so.6 inside /
/usr/bin/ld: cannot find /usr/lib/libc_nonshared.a inside /
collect2: error: ld returned 1 exit status
When I compile programs of my own, ld has never looked under the wrong directory, even for 32-bit cross-compilations. So this is definitely abnormal behavior for ld! I suspect that the issue is related to the order in which search directories are specified relative  to the order in which object files are linked, and has something to do with the fact that the extra search directories are listed after the object files are in the command, but that is only a suspicion.
Steps

Install Debian 10 on a 64-bit computer and make sure that glibc libraries are under /usr/lib/x86_64-linux-gnu/ and /usr/lib32/, but not under /usr/lib.
Install the rust toolchain using rustup and on the stable channel.
Clone the cargo repository.
Install the necessary tools for building cargo.
Obtain 32-bit openssl libraries
Execute: export OPENSSL_INCLUDE_DIR=/usr/include/x86_64-linux-gnu/; export OPENSSL_LIB_DIR=/path/to/32-bit/openssl
Run cargo build --release --target i586-unknown-linux-gnu

Extra Details that May Help in Finding a Solution
Compiler command (reformatted for readability with some unimportant and potentially security-compromising parts cut out):
cc -m32 -Wl,--eh-frame-hdr -Wl,-znoexecstack -Wl,--as-needed
-L ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/i586-unknown-linux-gnu/lib
~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/deps/cargo-db1abd5de703817f.cargo.7ncu5749-cgu.0.rcgu.o ... ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/deps/cargo-db1abd5de703817f.cargo.7ncu5749-cgu.9.rcgu.o -o ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/deps/cargo-db1abd5de703817f
~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/deps/cargo-db1abd5de703817f.26a1xlub64lpy80q.rcgu.o
-Wl,--gc-sections -pie -Wl,-zrelro -Wl,-znow -Wl,-O1 -nodefaultlibs
-L ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/deps
-L ~/i586CargoBuildDirectory/cargo/target/release/deps
-L ~/OLPC_GentooBuildDirectory/usr/lib/
-L ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/build/curl-sys-a0ec76bf26bdc4bb/out/build
-L ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/build/libnghttp2-sys-9cdfe4d47dadf3f9/out/i/lib
-L ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/build/libz-sys-b1490d697be50d36/out/lib
-L ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/build/libz-sys-b1490d697be50d36/out/lib
-L ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/build/libgit2-sys-6c249fec5f967830/out/build
-L ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/build/libssh2-sys-85f84cabb45c3e86/out/build
-L ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/i586-unknown-linux-gnu/lib
-Wl,-Bstatic
~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/deps/libgit2_curl-97c6d87432c9c66a.rlib ... ~/i586CargoBuildDirectory/cargo/target/i586-unknown-linux-gnu/release/deps/libanyhow-ab02cafa6b675c7e.rlib
-Wl,--start-group
~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/i586-unknown-linux-gnu/lib/libstd-2427bf187ccc6a16.rlib ... ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/i586-unknown-linux-gnu/lib/libcore-960d1b81d1028491.rlib
-Wl,--end-group
~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/i586-unknown-linux-gnu/lib/libcompiler_builtins-448d7dae8e89c1de.rlib
-Wl,-Bdynamic -lssl -lcrypto -lgcc_s -lutil -lrt -lpthread -lm -ldl -lc
The full output and verbose output from the compiler (with potentially security-compromising parts cut out):
Compiler Output
Verbose Compiler Output
From extra testing I've tried to do myself, the only way I was able to get ld to output an error similar to the one it did here was to type
gcc -c main.c
ld -melf_i386 main.o /lib/x86_64-linux-gnu/libc.so
and then ld outputs
ld: skipping incompatible //lib/x86_64-linux-gnu/libc.so.6 when searching for /lib/x86_64-linux-gnu/libc.so.6
ld: cannot find /lib/x86_64-linux-gnu/libc.so.6 inside /
ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libc_nonshared.a when searching for /usr/lib/x86_64-linux-gnu/libc_nonshared.a
ld: cannot find /usr/lib/x86_64-linux-gnu/libc_nonshared.a inside /
ld: skipping incompatible //lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 when searching for /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
ld: cannot find /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 inside /
main.c:
int main(){
    return 0;
}
But I couldn't get the gcc frontend to produce the errors that ld did. I couldn't even get ld to produce those same errors if I added the -m32 flag when compiling with gcc! Another odd thing occurring is that I get the same error if I copy and paste the command that Cargo runs, but if I use the same options and link to the same libraries but just with main.o instead, it doesn't produce any errors. I have no idea what is going on here, although after looking at this issue in a different repository and after following some links to this result, it appears that it might be fixable by adding the option to the gcc compiler --sysroot=/path/to/sysroot. In fact, when I did add this compiler option, the linking process didn't return any errors. Even though I think I know how to fix this passing options to the rust compiler, I'm pretty sure from what I've read that due to the fact that build scripts are used and due to #4423, there is no way to pass the flags to the rust compiler, which can than pass the flags to gcc. Regardless of whether or not it can easily be fixed, though, something much deeper that is a lot more confusing than this is happening, since gcc is being passed flags that should be telling it to search in the correct directories anyways (-L ~/OLPC_GentooBuildDirectory/usr/lib/). Also, I have tried symbolically linking the correct files into /lib (/lib itself is just a symbolic link of /usr/lib), but when I did, ld said that there were to many files open when running a linker script, most likely meaning that it didn't recognize the format of the symbolically linked library.
Notes
Since this is my first issue I've written, if I am doing anything wrong or missing something, I would like to know so that I can improve on it for next time.

I’ve found a solution. The solution is to create a file in the build directory .cargo/config that has the contents:
[build]
rustflags = “-C link-arg=—sysroot=/path/to/gcc/sysroot
I might make a pull request in the future to fix this, but this is such a rare issue that I doubt anyone else will come across it.


intl_utils 1.6.1 depends on petitparser >=1.1.3 <3.0.0

Please upgrade to petitparser 3+, because I have dependencies conflict with other packages.
For example: flutter_svg
It is especially important for beta, dev, and master channels.

Hi @slavap
Could you try with global installation of intl_utils instead of via dev_dependencies, as a temporary solution till update is released?
For instance, activate it globally and then run the generator:
flutter pub global activate intl_utils 1.6.1
flutter pub global run intl_utils:generate

That way it should not create a conflict around petitparser version.

this is now becoming a blocker as flutter 1.2.0 is released and the library is incompatible with meta.

Hi @guness,
Thanks for reporting that the Flutter 1.20.0 (stable channel) is now released.
We will update petitparser dependency in one of the upcoming releases as flutter_test does not depend anymore on it.
Could you give us more details regarding incompatibility with meta package?

Hey sorry, I think I have misread the error logs (still getting used to it). I was confused because it mentioned flutter_test at a line and intl_utils on previous log.
this is the error I am getting:

Because every version of flutter_test from sdk depends on meta 1.1.8 and appoint depends on meta ^1.2.0, flutter_test from sdk is forbidden.
So, because appoint depends on flutter_test any from sdk, version solving failed.

and this was the previous error before I edit some versions:

Because every version of intl_utils depends on petitparser >=1.1.3 <3.0.0 and xml >=3.7.0 depends on petitparser ^3.0.0, intl_utils is incompatible with xml >=3.7.0.
And because flutter_svg 0.18.0 depends on xml ^4.1.0 and no versions of flutter_svg match >0.18.0 <0.19.0, intl_utils is incompatible with flutter_svg ^0.18.0.
So, because appoint depends on both flutter_svg ^0.18.0 and intl_utils ^1.6.2, version solving failed.
R

Hi @guness,
No problem.
Thanks for the logs, it will help us to better understand potential issues.

New version 1.6.3 supports petitparser ^3.0.0.

Because every version of flutter_test from sdk depends on petitparser 2.4.0 and intl_utils >=1.7.0 depends on petitparser ^3.1.0, flutter_test from sdk is incompatible with intl_utils >=1.7.0.
So, because markets_owner depends on both intl_utils 1.8.0 and flutter_test any from sdk, version solving failed.
pub get failed (1; So, because markets_owner depends on both intl_utils 1.8.0 and flutter_test any from sdk, version solving failed.)
getig this error please help

Hi @rauttech,
According to the message, you should be able to solve this issue by upgrading the flutter to the >=1.20.0 version or by downgrading the intl_utils package to the 1.6.2.
Hope it helps!

i tried both above solution but not working
now i get below logs
The current Flutter SDK version is 1.20.0.
Because markets depends on google_maps_flutter >=1.0.0 which requires Flutter SDK version >=1.22.0 <2.0.0, version solving failed.
pub get failed (1; Because markets depends on google_maps_flutter >=1.0.0 which requires Flutter SDK version >=1.22.0 <2.0.0, version solving failed.)

Hi @rauttech,

Because markets depends on google_maps_flutter >=1.0.0 which requires Flutter SDK version >=1.22.0 <2.0.0, version solving failed.
pub get failed (1; Because markets depends on google_maps_flutter >=1.0.0 which requires Flutter SDK version >=1.22.0 <2.0.0, version solving failed.)

Because google_map_location_picker >=3.3.1 depends on intl >=0.16.0 <=0.16.
1 and every version of flutter_localizations from sdk depends on intl 0.17.
0-nullsafety.2, google_map_location_picker >=3.3.1 is incompatible with flu
tter_localizations from sdk.

Maybe I'm missing something, but in the latest error messages, I don't see anything related to the intl_utils package. 😕
Also, I noticed that you are using intl_utils as a dependency and that you have the flutter_intl config within your pubspec.yaml file (enabled "Flutter Intl" IDE plugin).
Out of curiosity, for what you are using the intl_utils package in your flutter project?
Note that enabled "Flutter Intl" IDE plugin will install globally intl_utils package for you and use it.


PSR2 cleanup

quick cleanup

Current coverage is 13.58%

Merging #45 into master will not affect coverage as of 0cdab98

@@            master     #45   diff @@
======================================
  Files            2       2
  Stmts           81      81
  Branches         0       0
  Methods         12      12
======================================
  Hit             11      11
  Partial          0       0
  Missed          70      70

Review entire Coverage Diff as of 0cdab98

Powered by Codecov. Updated on successful CI builds.


Allow insecure hosts

I'm trying to use chromeless on my machine (macOS Sierra) to test my local webapp.
The issue is that the test gets stuck at the "Your connection is not private" Chrome page.
I know there is the Chrome flag --allow-running-insecure-content you can pass when executing the Chrome binary, but it would be great if I could keep the ability to open Chrome for my scripts instead of having to open it beforehand.
So I was wondering if there was a way of passing arbitrary Chrome flags to the Chromeless constructor?
Thank you

Hi @stassinari — Thank you for sharing your use-case. I'm going to close this issue as a duplicate of #184 which is being addressed by PR #192. In other words—we should see this feature released in v1.3. 😄


Table stuck in NEW table state on certain importTable scenario

Describe the bug
A table gets stuck in the NEW state when the scenario below happens. See comments in the code.
Versions (OS, Maven, Java, and others, as appropriate):

Affected version(s) of this project: 2.1.3-SNAPSHOT and 3.1.0-SNAPSHOT

To Reproduce
Run the test added this branch: [DomGarguilo:accumulo:newTableStateBug] (https://github.com/DomGarguilo/accumulo/tree/newTableStateBug). This was branched from 3.1.0-SNAPHOT but the changes can also be applied to 2.1.
Pasted here in case the branch ever gets deleted. This test case was added to ImportExportIT:
@Test
  public void testBug() throws Exception {
    try (AccumuloClient client = Accumulo.newClient().from(getClientProps()).build()) {

      String[] tableNames = getUniqueNames(3);
      String srcTable = tableNames[0], destTable1 = tableNames[1], destTable2 = tableNames[2];
      client.tableOperations().create(srcTable);

      try (BatchWriter bw = client.createBatchWriter(srcTable)) {
        for (int row = 0; row < 1000; row++) {
          Mutation m = new Mutation("row_" + String.format("%010d", row));
          for (int col = 0; col < 100; col++) {
            m.put(Integer.toString(col), "", Integer.toString(col * 2));
          }
          bw.addMutation(m);
        }
      }

      final Path testDir = new Path("/tmp/manysplitsTableExport");
      final Path tableExportDir = new Path(testDir, srcTable);
      final Path copyDir = new Path(testDir, "_tmp");
      FileSystem fs = cluster.getFileSystem();
      fs.delete(testDir, true); // remove the dir if it exists from a previous run
      fs.mkdirs(tableExportDir);
      fs.mkdirs(copyDir);

      log.info("Exporting table data to {}", tableExportDir);
      client.tableOperations().offline(srcTable);
      client.tableOperations().exportTable(srcTable, tableExportDir.toString());
      // copy files
      try (FSDataInputStream fsDataInputStream = fs.open(new Path(tableExportDir, "distcp.txt"));
          InputStreamReader inputStreamReader = new InputStreamReader(fsDataInputStream, UTF_8);
          BufferedReader reader = new BufferedReader(inputStreamReader)) {
        String file;
        while ((file = reader.readLine()) != null) {
          Path src = new Path(file);
          Path dest = new Path(copyDir, src.getName());
          FileUtil.copy(fs, src, fs, dest, false, true, cluster.getServerContext().getHadoopConf());
        }
      }

      // create the table before trying to import to it
      client.tableOperations().create(destTable1);

      ImportConfiguration importConfig =
          ImportConfiguration.builder().setKeepOffline(true).setKeepMappings(true).build();

      // since the table already exists we expect this to be thrown
      assertThrows(TableExistsException.class, () -> client.tableOperations()
          .importTable(destTable1, Set.of(copyDir.toString()), importConfig));

      client.tableOperations().importTable(destTable2, Set.of(copyDir.toString()), importConfig);

      Map<String,String> tableIdMap = getServerContext().tableOperations().tableIdMap();
      TableId tid = TableId.of(tableIdMap.get(destTable2));
      var context = getServerContext();

      // for some reason when we try to import to a table that already exists and then use that same
      // dir to import to another table (that doesn't yet exist) the new table is created but does
      // not leave the NEW table state.
      Wait.waitFor(() -> context.getTableState(tid) != TableState.NEW, SECONDS.toMillis(30),
          SECONDS.toMillis(1), "Table stuck in NEW table state");

    }
  }

Expected behavior
A table should not get stuck in NEW table state

Bit of an update on this. It looks like the bug (as far as I can tell this is not the expected behavior) is not caused by the scenario that I outline above. It looks like setKeepOffline(true) in the ImportConfiguration builder does not create the new table in an offline state as it is supposed to but rather the new table gets created and is stuck in the NEW table state. This can be demonstrated by adding the following line to ImportExportIT.testExportImportOffline() which uses setKeepOffline(true) when importing to a new table:
// wait for the new table created by importTable to leave the NEW table state
Wait.waitFor(() -> getServerContext().getTableState(TableId.of(tableId)) != TableState.NEW, SECONDS.toMillis(30),
         SECONDS.toMillis(1), "Table stuck in NEW table state");

Adding that after this part of the IT will cause an exception:
https://github.com/apache/accumulo/blob/67fd967415612ab0770b422a5b24430655275946/test/src/main/java/org/apache/accumulo/test/ImportExportIT.java#L285-L291


fix: test pnpm

Jira Ticket ID:

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Feature (non-breaking change which adds functionality)
[ ] Code style update
[ ] Refactor (refactoring or adding test which isn't a fix or add a feature)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[ ] No

Did you test your solution?

[ ] I lightly tested it in one browser
[ ] I deeply tested it in several browsers
[ ] I wrote tests around it (unit tests, integration tests, E2E tests)

Problem Description

Solution Description

Side Effects, Risks, Impact

[ ] N/A

Aditional comments:

[AUTOMATED] Latest version has been pushed to preview.
Preview deployed at https://preview-1fb925c.dev.nextjs-boilerplate.jam3.cloud.jam3.net

[AUTOMATED] Latest version has been pushed to preview.
Preview deployed at https://preview-fd6a414.dev.nextjs-boilerplate.jam3.cloud.jam3.net

[AUTOMATED] Latest version has been pushed to preview.
Preview deployed at https://preview-35be339.dev.nextjs-boilerplate.jam3.cloud.jam3.net


Add Continuous Delivery

Do you want to request a feature or report a bug?
Feature
What did you expect to see?
Currently there's no continuous delivery. In other words this means we have to manually deploy our build outputs produced in #56. We don't want to do manual stuff as we're programmers so why not automate it?
Blocked by

Blocked by #56

Expectations
The CD should be able to do:

[ ] Deploy build outputs

[ ] Windows
[ ] Linux
[ ] OSx

[ ] Create a new tag on GitHub
[ ] Run nightly deploy

This will gives us a place to download artifacts from per version and a place to download the nightly build from.

I think for this, publishing a docker image (under latest/nightly tags) would satisfy the requirements.

I have implemented a pipeline which runs all tests and publishes in docker image only when all have passed. You can see it working in my fork.
Most of work for it is in PR #108

I'd like to follow NuGet Package Explorer's setup:

Use Nerdbank.GitVersioning to generate a version
Publish BaGet as Azure DevOps artifacts
With human approval, use github-tools-vsts's Create or Modify GitHub Release task to release the artifacts to GitHub
With human approval, publish a Docker image

I've added Continuous Delivery to BaGet. You can:

Download BaGet as a GitHub release: https://github.com/loic-sharma/BaGet/releases
Install BaGet's components using NuGet: BaGet.Core and BaGet.Azure

I'll add support for Docker images in the future.

Closing this issue as BaGet has continuous delivery. Please let me know if you have any other suggestions!


Retain backwards compatibility for clinical significance and RCV identifiers

Please see my email for details.

Thank you @tskir, good idea to make it schema backwards compatible. I will tag it as 1.7.1


Plugin was not found in any of the following sources

Hi I`m trying to run HelloFx project. I tried to create it manually or ran github project but get the same error. Could you help me ?
Error: Plugin [id: 'org.openjfx.javafxplugin', version: '0.0.7'] was not found in any of the following sources:
github project was from: https://github.com/openjfx/samples/tree/master/HelloFX/Gradle
details on screeshort: https://yadi.sk/i/FAOsg6xESOqcmA

What happens if you try from a terminal? On the root of the project run:
gradlew clean build run
If that works, the problem could be related to IntelliJ.
Else, check your internet settings (firewall, proxy, ...).
You could try also this instead:
buildscript {
    repositories {
        maven {
            url "https://plugins.gradle.org/m2/"
        }
    }
    dependencies {
        classpath 'org.openjfx:javafx-plugin:0.0.7'
    }
}
apply plugin: 'org.openjfx.javafxplugin'

The both ways did not help much, you may look at results on the screens folowing by the links. I`ll try google may be found something
https://yadi.sk/i/oCHLSz-L4f5lLQ
https://yadi.sk/i/fg7ai8vlkcR_xQ

Gradle plugin is published here: https://plugins.gradle.org/m2/, can you access that link from a regular browser?
Can you try any other gradle plugin?
(Maven plugin goes to Maven Central)

Yes, I have accsess that link from a regular browser
I tried different plugin It didnt work out either I guess its some network issue

eventually I managed to run projects, the issue was antivirus settings for network


Update SDG topics

Looks good!
Are there any additions or deletions to goals/targets/indicators?
https://github.com/datacommonsorg/website/blob/99c256749f5f7b3339477734ae6ebb738a93e0a5/tools/nl/embeddings/input/sdg/sheets_svs.csv

UN mentioned we should only expect variable changes, and the goal/topic/indicator hierarchy will stay the same

would it make sense to check in the changes to core_topics.py too?


fix: mixed content blocked for http and https

Otherwise you would see this in console of a browser:
Mixed Content: The page at 'https://localhost/qrcode/dynamic_qrcodes.php' was loaded over HTTPS, but requested an insecure stylesheet 'http://code.ionicframework.com/ionicons/2.0.1/css/ionicons.min.css'. This request has been blocked; the content must be served over HTTPS.
Thx.

Thank you


Added script that checks links in a file.

All the links in src/data.js are hardcoded. This introduces the
possiblity of them breaking without anyone noticing. To be able
to automate the checking of all links this script is introduced.
The only parameter this script takes is a file path. The file is then
read and parsed for all occurences of http/https links. Those
links are then checked if they return an http status of 2** if not
the failing links are printed to the command line with their
returned status code.

Hm, I can't reproduce the error. Could you give me the version of your requests library?
I could filter the status code errors to 4** only and also display what the error means. Do you think that this is sufficient to prevent confusion with non tech savvy users?

python3-urllib3                      1.25.8-2
python3-openssl                      19.0.0-1build1
I guess this is an error generated from the openSSL settings - I will dig deeper into it.

 Unfortunately this didn't fix the problem of @cpetig. As of now I was not able to reproduce the error. Until we get more cases of this error it will be regarded as unimportant.


Uuid -> Leafref at Notifications

All *Notification::objectIdRef attributes will become _objectIdRef attributes generated from shared associations to LTP class in UML. This applies on all notifications.
All *notification::object-id-ref leaf will become leafref to LTP.
Only object-deletion-notification::object-id-ref : leafref will be "require-instance false;"

Didn't manage to model require-instance: true -> all 4 _objectIdRef attributes became require-instance:false.
Corrected in UML and YANG (e.g. MacInterface_1.0.0-tsp.200123.1415+yang.4).

Didn't manage to model require-instance: true -> all 4 _objectIdRef attributes became require-instance:false.
Corrected in UML and YANG (e.g. MacInterface_1.0.0-tsp.200123.1415+yang.4).


Multiregion

Hello, is installation available in two or more data centers using multiregion as in CockroachDB?
If yes, could you provide documentation?
Thanks!

Hi @Paramoshka, typically YDB is deployed in 3 datacenters or availability zones. See mirror-3-dc in https://ydb.tech/en/docs/cluster/topology
However, having these datacenters not far from each other is recommended to avoid too high transaction latencies. For example, different countries in Europe would be working fine, but a cluster spanning across continents likely won't.
If you really need your data to be present in distant regions, there's a newer feature of async replication between YDB clusters. Afaik it is not quite documented yet, but you can get some idea of what it is about from these slides: https://squidex.jugru.team/api/assets/srm/acbeabc7-56f1-4234-9e97-0e66c33be4ce/hydra-2022-fomichev-nizametdinov-1-.pdf

Hi @Paramoshka, typically YDB is deployed in 3 datacenters or availability zones. See mirror-3-dc in https://ydb.tech/en/docs/cluster/topology
However, having these datacenters not far from each other is recommended to avoid too high transaction latencies. For example, different countries in Europe would be working fine, but a cluster spanning across continents likely won't.
If you really need your data to be present in distant regions, there's a newer feature of async replication between YDB clusters. Afaik it is not quite documented yet, but you can get some idea of what it is about from these slides: https://squidex.jugru.team/api/assets/srm/acbeabc7-56f1-4234-9e97-0e66c33be4ce/hydra-2022-fomichev-nizametdinov-1-.pdf

Hi @Paramoshka, typically YDB is deployed in 3 datacenters or availability zones. See mirror-3-dc in https://ydb.tech/en/docs/cluster/topology
However, having these datacenters not far from each other is recommended to avoid too high transaction latencies. For example, different countries in Europe would be working fine, but a cluster spanning across continents likely won't.
If you really need your data to be present in distant regions, there's a newer feature of async replication between YDB clusters. Afaik it is not quite documented yet, but you can get some idea of what it is about from these slides: https://squidex.jugru.team/api/assets/srm/acbeabc7-56f1-4234-9e97-0e66c33be4ce/hydra-2022-fomichev-nizametdinov-1-.pdf

Thanks.
I see a configuration for 3 Availability Zones
https://github.com/ydb-platform/ydb/blob/main/ydb/deploy/yaml_config_examples/mirror-3dc-3-nodes.yaml, if at the moment there are only two data centers at a short distance, what configuration would you recommended, and how to enable asynchronous mode?

@Paramoshka if you're setting up a new production YDB cluster that has a requirement to seamlessly operate even if a datacenter goes down, right now I'd recommend to look into finding the third datacenter. If there's no such requirement and surviving a server rack failure is sufficient (if we're talking about a non-cloud environment), you could just set up a block-4-2 topology in a single datacenter.
I double-checked and, unfortunately, we don't have any ready-to-use guidance on how to set up this async replication feature yet as it hasn't been fully released. Stay tuned!

@Paramoshka if you're setting up a new production YDB cluster that has a requirement to seamlessly operate even if a datacenter goes down, right now I'd recommend to look into finding the third datacenter. If there's no such requirement and surviving a server rack failure is sufficient (if we're talking about a non-cloud environment), you could just set up a block-4-2 topology in a single datacenter.
I double-checked and, unfortunately, we don't have any ready-to-use guidance on how to set up this async replication feature yet as it hasn't been fully released. Stay tuned!

Thank you, is it possible to use this config for production? One node with three disks.
https://github.com/ydb-platform/ydb/blob/main/ydb/deploy/yaml_config_examples/mirror-3dc-3-nodes.yaml


notification: add Go CDK pubsub support

Add the gocdk_pub_sub package, which supports the Go Cloud Development
Kit pubsub API.
Link in all current providers.
Update the notification scaffold.

Nice!  failed and exited with 1 during .
Your build has been stopped.
'''

Not sure whether it is complicated. Can this gocloud.dev/pubsub be moved to github.com?

FYI: the build log
https://travis-ci.org/chrislusf/seaweedfs/builds/508889375

Can this gocloud.dev/pubsub be moved/cloned to github?
Seems this is not new: https://github.com/googleapis/google-cloud-go/issues/820

I'm working on this; it is a problem with go-import redirects for the gocloud.dev import paths.

Tests are passing now.

Thanks a lot!
Is there any way to avoid this in the future? These go import redirects seem fragile.

Is there any way to avoid this in the future? These go import redirects seem fragile.

We're automating our process so this won't happen again.
More generally, the Go ecosystem will soon have proxies, which will pretty much end availability issues.  Run go help goproxy in Go 1.12.

@jba SeaweedFS use the notification to replicate files across systems. The current PR implemented SendMessage(). We need another one to ReceiveMessage(), similar to https://github.com/chrislusf/seaweedfs/blob/master/weed/replication/sub/notification_google_pub_sub.go#L94
Could you please also help here? Thanks!

Sure, I'll try to get to it this week.


Fixing error parsing for tslint v5

Tested to work against tslint 3.15.0, 4.1.0, and 5.1.0.

Please consider this fix for the parsing error: 0bfac455.
As for --type-check, changes to the defaults are only accepted if they fix catastrophic problems (such as security hazards).  You can achieve the same effect by setting syntastic_typescript_tslint_args from an autocmd.

@lcd047 Wow, quick turnaround, thanks!  0bfac45 works great.
I took your suggestion and pulled the type check logic out into a separate autocmd-triggered function.  In case anyone finds this trying to enable type-checking, the gist is here:
https://gist.github.com/KurtPreston/e3b385a97ab0cea549c6b89eac8efa58
Only issue is I'm currently grabbing the tslint version via a system call, but I'd like to pull it from syntastic instead (in case it's using a different tslint).  Any help as to what command to run to get the tslint version number from syntastic would be appreciated.

I took your suggestion and pulled the type check logic out into a separate autocmd-triggered function.

Err, what I had in mind is more along the lines of:
if !exists('b:syntastic_typescript_tslint_args')
    if !exists(s:type_check)
        let s:type_check =
            \ syntastic#util#versionIsAtLeast(syntastic#util#parseVersion(systemlist('tslint --version')[0]), [5]) ?
            \ '--type-check' : ''
    endif
    let b:syntastic_typescript_tslint_args = s:type_check
    if globpath(&runtimepath, 'autoload/tsuquyomi.vim', 1) !=# ''
        let b:syntastic_typescript_tslint_args .=
            \ ' -p ' . syntastic#util#shescape(tsuquyomi#tsClient#tsProjectInfo(@%, 0)['configFileName'])
    endif
endif

Put this in a file ~/.vim/after/ftplugin/typescript.vim (or equivalent).

Only issue is I'm currently grabbing the tslint version via a system call, but I'd like to pull it from syntastic instead (in case it's using a different tslint).

Well for one you'd use syntastic#util#system() instead of system(), in case syntastic uses a different shell. :smile: Beyond that, you'd have to reconstruct it from the makeprgBuild() variables.  Syntastic itself doesn't expose that kind of details.
Perhaps an introspection mechanism for checkers could be useful, but that's unlikely to happen any time soon.


The best to way to handle twitter's search error?

data = scrap(words = 'fosun pharma', start_date="2020-01-08", max_date="2020-12-31",interval=1,
      headless=False, proxy="socks5://<IP_ADDRESS>:7891")

I'm using this code to query tweets about fosun pharma during the year 2020.
The operation works amazingly but when things get to some threshold, like after a consistent query of 120 days, Twitter will refuse to offer the result and shows a search error.

I split my query into a group of a period of 4 months to make things down. I'm wondering is there any better choice to handle such a situation, recovering from twitter's query error.

Try again with resume=True works fine.


MaxP.update() – bins used by not defined

In https://github.com/pysal/mapclassify/commit/85057955b6828725224231019c791df5b15b678f I commented out the update method for MaxP due to linting failure, and then tests were passing without it. The linting was failing because bins is used but never passed in or defined within. I am wondering if this is a bug introduced through copy-paste  of another classifier's update method, for example UserDefined?

We can remove the update method for MaxP. Doing so will have it use the inherited update method which will simply reclassify the extended array. I think the listing error was due to an errant cut and paste.


Adapter API to parse ignore files to warn of suggested ignores

Describe the problem
Different adapters require different ignore settings.
The current proposed soln that is in use today is for all adapter output to be under .svelte-kit/<somedir> though this may change in future per adapter.
The proposed solution would provide adapter authors with an alternative.
Describe the proposed solution
Use gitignore-parser to let Adapters to loudly warn users. From this exchange:

Should we expect to see gitignore-parser provided via the Adapter API in the near future?

jthegedus https://github.com/sveltejs/kit/pull/2055#issuecomment-890661100

Yes, I think we should — we could have an API like utils.warn_if_unignored([opts.output])

Rich-Harris https://github.com/sveltejs/kit/pull/2055#issuecomment-890666505

Alternatives considered
Writing this in my documentation
Importance
would make my life easier
Additional Information
raising the issues:

#1832
#1581

initial proposition:

#1924

revert of initial proposition

#2055

https://kit.svelte.dev/docs#writing-an-adapter says:

If possible, we recommend putting the adapter output under the build/ directory with any intermediate output placed under '.svelte-kit/' + adapterName.

Unfortunately it hasn't always been possible. We had to move some of the Netlify output to be under .netlify

kit.svelte.dev/docs#writing-an-adapter says:

If possible, we recommend putting the adapter output under the build/ directory with any intermediate output placed under '.svelte-kit/' + adapterName.

Unfortunately it hasn't always been possible. We had to move some of the Netlify output to be under .netlify

Yes, this cannot always be achieved. If the adapter reads the platform config (netlify.toml, firebase.json etc) to determine where to put the final build output, then a way to warn about ignoring is required.
A key point to highlight, and that I think is missed in a lot of the Kit > PlatformX conversations, is the idea that Kit is the only App & owner of all APIs hosted on PlatformX. For instance, a single Firebase project can house many Android, iOS, Web apps and APIs all from the same firebase.json config, which is why the Firebase Adapter cannot simply put everything in build/ nor that build/ is even at the root of the Firebase project. But also, does not mean the user wants to commit the final build output wherever it lives.


Connection fails "operation in process" to a peripheral device without pairing

I don't know it that's the right issue, but my peripheral device accepts connections without pairing, and complains if you actually want to pair.
I can connect to the device using bluetoothctl and everything works as expected, but when I try to connect with the code from the example (where only the name has been changed), it does not work. It tries to connect (it blocks) then it panics with an "operation in process" error message.
What could be the next steps to debug the issue?
I'm thinking it might be related to pairing as I also tried to connect with blurz and it works with that crate when I just connect - without pairing - to the device. Looking at your code on connect it does not look like you are trying to pair though...

I've got the same issue here. Using connect XX:XX:XX:XX:XX:XX with bluetoothctl works just fine, but using the connect() method after having found the device results in a long wait and ends in either the "EINPROGRESS: Operation in progress", or sometimes "ECONNREFUSED: Connection refused" errors.
Would love to help debug this further if the author(s) could show me in the right direction.

On connect I'm getting the following rumble debug output:
[2019-06-08T19:18:17Z DEBUG rumble::bluez::adapter::peripheral] created socket 5 to communicate with device
[2019-06-08T19:18:17Z DEBUG rumble::bluez::adapter::peripheral] bound to socket 5
[2019-06-08T19:18:17Z DEBUG rumble::bluez::adapter::peripheral] configured socket 5
[2019-06-08T19:18:17Z DEBUG rumble::bluez::adapter] got message HCICommand { command: LESetScanParameters, data: [0, 96, 0, 48, 0, 0, 1] }
[2019-06-08T19:18:17Z DEBUG rumble::bluez::adapter] got message HCICommandComplete(LESetScanParameters)
[2019-06-08T19:18:17Z DEBUG rumble::bluez::adapter] got message LEScanEnableCommand { enable: true, filter_duplicates: true }
[2019-06-08T19:18:17Z DEBUG rumble::bluez::adapter] got message HCICommandComplete(LESetScanEnabled { enabled: false })
[2019-06-08T19:19:00Z DEBUG rumble::bluez::util] got error EINPROGRESS: Operation now in progress
[2019-06-08T19:19:00Z DEBUG rumble::bluez::adapter::peripheral] Failed to connect (EINPROGRESS: Operation now in progress), closing socket 5

I'm therefore guessing that this happens in the setup_connection method of bluez/adapter/peripheral.rs. The error seems to be coming from bluez itself, which I find very strange. However, I'm in no means a BLE expert and haven't used bluez before, so that's all info I can provide.

I'm interested in using this crate, but this happens to me whenever I talk to any BLE device. As in, I have not yet successfully connected to anything, even using the example code. There seems to be a serious bug in the way it's managing BlueZ's connection state. (The error it's reporting is the one BlueZ produces when you make two simultaneous connection requests, for what it's worth.)

Cannot connect to any device as well. Also experiencing permissions errors unless I run as root, not sure if anyone else has run into that?

Experiencing the exact same here, including having to run as root (I believe that is due to permissions on the bluetooth central adapter)

@SamuelWAnderson45 the permission error can be fixed temporarily by running 'sudo setcap 'cap_net_raw,cap_net_admin+eip' /path/to/your/compiled/binary

@Josh-Thompson already tried that. Didn't make a difference.


Added Japanese translation

Hello!

This looks perfect - thank you very much! I apologize for the slow response, we will include this translation in the next release.


Handle manifest request from Matrix Service retry loop

@hannes-ucsc wrote:  It just occurred to me that we should ask the Data Browser team to handle the manifest request retry loop client side. That way we wouldn't waste server side resources and could potentially offer better UI feedback (display "The matrix hand-off manifest is being prepared …" and then "The Matrix is being prepared …"). This would be the same as what you do for the Terra hand-off today.
@MillenniumFalconMechanic : This sounds like a fairly straight-forward modification to the current front-end functionality.

Deprecated in favor of #647.


Add exactly_one function

Adds a small function I found uses for personally.  Can't be added to the core library because in the error case it allocates a vec and stores data in it.

Relevant: https://github.com/rust-lang/rust/pull/55355.

I'd prefer this in Centril's version. And now we know, std doesn't want this method, so we can take it.

(Feel free to copy the contents from my PR if you want)

@bluss Why do we prefer returning nothing in the case of there being more than 1?  Since both versions consume the iterator it seems to me we're just needlessly hiding valuable debugging info.

If we simply don't like memory allocation for the error vec then I suppose we could make this take &mut instead and change the Err type to instead be (Self::Item, Self::Item).

In all the cases where I needed this I didn't want to get the remaining elements so the allocation shouldn't be pushed on folks imo; If you want to give back the iterator you can do: -> Result<Self::Item, (Self::Item, Self)> and then you can use rest in Err(x, rest) to get the remaining bits if you need that.

We can return an iterator or similar, we already have one for iterator + one item in itertools, PutBack, so that s a nice one to put in the error case

@bluss I've rewritten this to use an iterator in the error case.

Oh right, we need to put back two elements. Either use putbackn or a custom iterator in that case, I don't mind the latter

I think this turned out nicely. :)

@bluss how's this?

putbackn uses a vec internally which puts us back at the original problem, so I went for a custom iterator.

@bluss Just pinging you in case this got lost.  Based on your github history it seems the past few days have been very busy for you.

@bluss Believe this is ready to merge now.

Sorry, we need to add at test for this iterator before it merges. Then I agree it's ready. Can be a simple quickcheck test.

@bluss is the doc comment test not sufficient?

@Xaeroxe I realize I had thought about tests before and accepted the doctests, so I'm sorry that I didn't remember that. I shouldn't change my mind.
But in principle, no, features should have tests. Preferably quickcheck tests! They are very good at finding bugs. I feel strongly that testing documentation is often misunderstood — we test documentation to make sure that the examples we give actually work. We should make understandable examples, and they are there for documentation, not testing.

So since it's annoying to change one's mind, I'll merge since I had already decided some point prior to just let it slide.

bors r+
Thank you!

@bluss well I mean you made a really good case and I agree with you, so I'm happy to add the unit tests if you want.

@Xaeroxe ok, that can be a new PR if you want to

Wheels of bors are already turning

@bluss I've opened #324 , thanks!


Optimized the process by using flutter_lints.

Hi amazing developer,
Since flutter_lints is not applied to this library, I added flutter_lints to the dependencies to optimize the process. I don't think I have made any destructive changes, but please check to be sure and merge if everything is fine.
Thank you.

Will do so, thanks


Various QML fixes

I fixed a bunch of papercuts:

new cover page that follows Sailfish styling
refactored the settings page to follow Sailfish styling
added a new setting to disable fun facts while loading (I personally find them distracting, but I kept the new setting enabled by default, of course)
removed qsTr() from app name in notifications, it's not translated in any current translations anyway
added a dimmed background while loading to work around the glaring white screen that would otherwise show before the view is loaded
disabled the pulley menu in the channels list to work around #42

Screenshots:

Thanks @ichthyosaurus ! Looking through the changes and testing them now


chore: bdd-spring-1586298247 to 0.0.1

chore: Promote bdd-spring-1586298247 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


ERROR: only a single Aspire project is supported at this time

Type of issue
Other (describe below)
Description
Attempting to follow the documentation after installing the starter kit and running azd init, there is an error that only a single project is supported.
Additionally, the documentation said nothing about needing powershell 7.4 installed but in my case I had to update from 7.2 to 7.4 or the azd command was not found.

Page URL
https://learn.microsoft.com/en-us/dotnet/aspire/deployment/azure/aca-deployment?tabs=visual-studio%2Cinstall-az-windows%2Cpowershell
Content source URL
https://github.com/dotnet/docs-aspire/blob/main/docs/deployment/azure/aca-deployment.md
Document Version Independent Id
1362fc62-686d-2b3f-c139-7725fc8dca5f
Article author
@IEvangelist

This is by design to my knowledge. A single solution can only have a single AppHost project. Let's double check with @DamianEdwards though before closing this.


Updater overwrites user PRs

The check to not overwrite PRs with contributions from other users (introduced by #50) seems broken, see https://github.com/getsentry/sentry-react-native/actions/runs/4674147763/jobs/8278069442#step:5:34
Run $mainBranch = $(git remote show origin | Select-String "HEAD branch: (.*)").Matches[0].Groups[1].Value
baseBranch=main
prBranch=deps/scripts/update-javascript.sh
Looking for commits on git@github.com:getsentry/sentry-react-native.git branch 'deps/scripts/update-javascript.sh' that were made by someone else than<EMAIL_ADDRESS>hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: ambiguous argument 'origin/main..origin/deps/scripts/update-javascript.sh': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: ambiguous argument 'origin/main..origin/deps/scripts/update-javascript.sh': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Removing /tmp/b8c487ed-c3f2-4a[43](https://github.com/getsentry/sentry-react-native/actions/runs/4674147763/jobs/8278069442#step:5:44)-b7d8-16ddc[49](https://github.com/getsentry/sentry-react-native/actions/runs/4674147763/jobs/8278069442#step:5:50)7c0f8
changed=false

cc @krystofwoldrich


Position control problems with typhoon_h480 model in gazebo sitl

The bug
Since Firmware Commit https://github.com/PX4/Firmware/commit/43e3fc707de823faa19b16091e5ee4a900e3c446 the typhoon_h480 model does not exhibit good position control in gazebo simulation with mavros. Still the case as at https://github.com/PX4/Firmware/commit/b0176dc88aecd22363f771bfe62dafa57a6a194a. The error message Critical navigation failure! Check sensor calibration is logged in conjunction with the problem.
From release v1.9.0 to the commit prior to the reported issue (4a4d323) seem to work fine.
To Reproduce
Steps to reproduce the behavior:

Load commit version and ensure a totally clean build/initialisation (problem may not manifest unless all these steps are followed):

cd <FIRMWARE LOCATION>
git checkout <COMMIT UNDER TEST>
make clean
git submodule update
rm ~/.ros/eeprom/parameters
make px4_sitl_default gazebo_typhoon_h480

roslaunch model roslaunch px4 mavros_posix_sitl.launch vehicle:=typhoon_h480
Arm / transition to offboard mode
Send position target

Expected behavior
Stable position control behaviour (from commit 4a4d323):
https://logs.px4.io/plot_app?log=6c788665-95f7-4b2b-a963-9ad58911024c
Log Files and Screenshots
Unstable position control behaviour:
https://logs.px4.io/plot_app?log=894c8553-18b1-4fc1-ad4a-d1587485637e
Additional context

Iris model still seems to work OK in this regard
Have also observed Preflight Fail: Compass #0 uncalibrated but possibly due to not clearing parameter files between different build levels.
when using commander takeoff in gazebo via the pxh> shell the vehicle seems stable.

Issue still present as far as I can see - would be great to see the reason this has been closed?

You have probably been misled by the referenced Weekly Digest.
This issue is still open

So it is - silly me!

@jannsta1 Do you still have this issue? I can fly the H520 in SITL with the current master

@Jaeyoung-Lim - nice chatting with you at the dev summit :) and thanks for looking into this. I last checked with the master 5 days ago and still saw the issue - won't have access to my workstation until Monday so will try then and report back. Just to check though - is there a H520 model in the sitl_gazebo repo as well as the H480? Its also worth mentioning that its important to do the clean build steps (step 1 from the initial bug report) to ensure that everything has been rebuilt with desired git checkout.

@Jaeyoung-Lim - update as promised - I am still seeing the issue on latest master. Couple of other notes:

It is still possible to fly the vehicle - just that following takeoff the z position control is very poor and the
warning messages reported in the bug report are present.
x & y position control seem to work as normal
The z position control stabilises eventually, but a new z position setpoint causes high oscillations again (I am using barometer for height control)

Finally - looking at the changes made on the commit when I started seeing this (listed above), there were many changes made to the sitl sensor IDs - I just didn't notice anything that would explain why this would effect the typhoon model and not the iris models.

@jannsta1 I will look into this as soon as possible. Currently I am overloaded with other stuff not related to SITL, so won't be able to look at it this week

I have tested this and it can fly without any problems. @jannsta1 Please reopen if the problem persists


Incorrect (CancellationException) thrown during I/O operation

It seems very rare, but it is possible that CancellationException is thrown from an I/O operation if the connection is lost at a specific time during the operation (during the request phase):
https://github.com/JuulLabs/kable/blob/ed0e4f59b5c2bd3bd8b4a5fa37e49cc5f002cd2f/core/src/androidMain/kotlin/Connection.kt#L55-L57
If dispatcher is shutdown (due to connection loss) before the above is called, then a CancellationException may be thrown.
Snippet of the exception thrown is as follows:
2021-11-22 15:47:17.486 29287-29936/com.<redacted> D/Kable/Peripheral: <redacted> write
    service: <redacted>
    characteristic: <redacted>
    writeType: WithoutResponse
    data: <redacted>
2021-11-22 15:47:17.492 29287-29936/com.<redacted> W/MessageQueue: Handler (android.os.Handler) {78f626c} sending message to a Handler on a dead thread
    java.lang.IllegalStateException: Handler (android.os.Handler) {78f626c} sending message to a Handler on a dead thread
        at android.os.MessageQueue.enqueueMessage(MessageQueue.java:560)
        at android.os.Handler.enqueueMessage(Handler.java:778)
        at android.os.Handler.sendMessageAtTime(Handler.java:727)
        at android.os.Handler.sendMessageDelayed(Handler.java:697)
        at android.os.Handler.post(Handler.java:427)
        at kotlinx.coroutines.android.HandlerContext.dispatch(HandlerDispatcher.kt:139)
        at kotlinx.coroutines.internal.DispatchedContinuationKt.resumeCancellableWith(DispatchedContinuation.kt:322)
        at kotlinx.coroutines.intrinsics.CancellableKt.startCoroutineCancellable(Cancellable.kt:30)
        at kotlinx.coroutines.intrinsics.CancellableKt.startCoroutineCancellable$default(Cancellable.kt:25)
        at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:170)
        at kotlinx.coroutines.BuildersKt.withContext(Unknown Source:1)
        at com.juul.kable.AndroidPeripheral.write(Peripheral.kt:651)
        <redacted<
        at kotlinx.coroutines.flow.SubscribedFlowCollector.onSubscription(Share.kt:410)
        at kotlinx.coroutines.flow.SharedFlowImpl.collect(SharedFlow.kt:341)
        at kotlinx.coroutines.flow.ReadonlySharedFlow.collect(Unknown Source:2)
        at kotlinx.coroutines.flow.SubscribedSharedFlow.collect(Share.kt:400)
        <redacted>
        at kotlinx.coroutines.flow.SafeFlow.collectSafely(Builders.kt:61)
        at kotlinx.coroutines.flow.AbstractFlow.collect(Flow.kt:212)
        at kotlinx.coroutines.flow.FlowKt__ReduceKt.first(Reduce.kt:222)
        at kotlinx.coroutines.flow.FlowKt.first(Unknown Source:1)
        <redacted>
2021-11-22 15:47:17.492 29287-29936/com.<redacted> W/MessageQueue:     at com.<redacted>$4.invoke(Unknown Source:4)
        at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturnIgnoreTimeout(Undispatched.kt:100)
        at kotlinx.coroutines.TimeoutKt.setupTimeout(Timeout.kt:148)
        at kotlinx.coroutines.TimeoutKt.withTimeoutOrNull(Timeout.kt:104)
        <redacted>
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>: Stopped <redacted>
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>: java.util.concurrent.CancellationException: The task was rejected, the handler underlying the dispatcher 'Handler (android.os.Handler) {78f626c}' was closed
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.android.HandlerContext.cancelOnRejection(HandlerDispatcher.kt:164)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.android.HandlerContext.dispatch(HandlerDispatcher.kt:140)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.internal.DispatchedContinuationKt.resumeCancellableWith(DispatchedContinuation.kt:322)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.intrinsics.CancellableKt.startCoroutineCancellable(Cancellable.kt:30)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.intrinsics.CancellableKt.startCoroutineCancellable$default(Cancellable.kt:25)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:170)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.BuildersKt.withContext(Unknown Source:1)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at com.juul.kable.AndroidPeripheral.write(Peripheral.kt:651)
<redacted>
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.flow.SubscribedFlowCollector.onSubscription(Share.kt:410)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.flow.SharedFlowImpl.collect(SharedFlow.kt:341)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.flow.ReadonlySharedFlow.collect(Unknown Source:2)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.flow.SubscribedSharedFlow.collect(Share.kt:400)
<redacted>
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.flow.SafeFlow.collectSafely(Builders.kt:61)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.flow.AbstractFlow.collect(Flow.kt:212)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.flow.FlowKt__ReduceKt.first(Reduce.kt:222)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.flow.FlowKt.first(Unknown Source:1)
<redacted>
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturnIgnoreTimeout(Undispatched.kt:100)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.TimeoutKt.setupTimeout(Timeout.kt:148)
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.TimeoutKt.withTimeoutOrNull(Timeout.kt:104)
<redacted>
2021-11-22 15:47:17.499 29287-29936/com.<redacted> I/<redacted>:     at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
2021-11-22 15:47:17.500 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
2021-11-22 15:47:17.500 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
2021-11-22 15:47:17.500 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
2021-11-22 15:47:17.500 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
2021-11-22 15:47:17.500 29287-29936/com.<redacted> I/<redacted>:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

With #197, CancellationException may still be thrown, but only in instances where the Peripheral has been disposed (i.e. parent Coroutine has been cancelled).
So, this is resolved, as CancellationException should no longer be thrown as the result of a connection drop (only Peripheral disposal).

To add additional details on what was causing the issue: the underlying thread/handler were being shutdown and subsequent I/O that tried to use the thread/dispatcher would be hit with a CancellationException (from the shut down thread/handler) and it was allowed to propagate.
The resolution (in #197) was to keep the underlying thread/handler alive (until Peripheral is disposed). This means that we no longer hit the CancellationExceptions because the threads/handlers are not shutdown between connections (so we are not longer susceptible to the potential race conditions.
The CancellationExceptions may still be thrown because if a Peripheral is disposed then subsequent I/O could still hit the previous behavior. But in that situation, cancelling callers would make sense, as the Peripheral is no longer usable.


08/22/2018 18:27 : Create Pull Request for branch master -> prTesting1_2018082218

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Prep grpc client generation

Preparation for the gRPC Client Generation.
This PR tries to align operations which are necessary to support a flawless gRPC Client Code generation as well as the integration required into a custom app.

Adding a LogcatLoggingStrategy so that Android Apps can log messages
Add a VehicleApplication which provides access to the middleware
Add a VehicleApp (which implements) VehicleApplication, which is used inside the VehicleAppService to access VehicleApplication functionality
Update kuksa.val.v2 protocol to the latest version
Add a Main Pipeline
Align Proto Files used

LGTM  for an initial setup.
Only thing I found:

Java compatibility with the newest Android Studio Ladybug creates issues because Ladybug uses Java 21 now instead of 17 bundled within.