Android permission error but uses-permission is in manifest

The manifest file is:

<application
but i get ...
Running Gradle task 'assembleDebug'...
E/flutter (17922): [ERROR:flutter/lib/ui/ui_dart_state.cc(177)] Unhandled Exception: PlatformException(error, Sending SMS message: uid 10153 does not have android.permission.SEND_SMS., null, java.lang.SecurityException: Sending SMS message: uid 10153 does not have android.permission.SEND_SMS.
E/flutter (17922): 	at android.os.Parcel.readException(Parcel.java:1620)
E/flutter (17922): 	at android.os.Parcel.readException(Parcel.java:1573)
E/flutter (17922): 	at com.android.internal.telephony.ISms$Stub$Proxy.sendTextForSubscriber(ISms.java:1577)
E/flutter (17922): 	at android.telephony.SmsManager.sendTextMessageInternal(SmsManager.java:380)
E/flutter (17922): 	at android.telephony.SmsManager.sendTextMessage(SmsManager.java:333)
E/flutter (17922): 	at com.roketstorm.smsker.SmskerPlugin.onMethodCall(SmskerPlugin.kt:48)
E/flutter (17922): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:233)
E/flutter (17922): 	at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:85)
E/flutter (17922): 	at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:738)
E/flutter (17922): 	at android.os.MessageQueue.nativePollOnce(Native Method)
E/flutter (17922): 	at android.os.MessageQueue.next(MessageQueue.java:323)
E/flutter (17922): 	at android.os.Looper.loop(Looper.java:143)
E/flutter (17922): 	at android.app.ActivityThread.main(ActivityThread.java:7231)
E/flutter (17922): 	at java.lang.reflect.Method.invoke(Native Method)
E/flutter (17922): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
E/flutter (17922): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
E/flutter (17922): )
E/flutter (17922): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:582:7)
E/flutter (17922): #1      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:162:18)
E/flutter (17922):
E/flutter (17922): #2      Smsker.sendSms (package:smsker/smsker.dart:16:30)
E/flutter (17922):
E/flutter (17922): #3      _MyAppState._sendMessage (package:feelsafe_dev/main.dart:20:5)
E/flutter (17922):
E/flutter (17922):
E/flutter (17922): [ERROR:flutter/lib/ui/ui_dart_state.cc(177)] Unhandled Exception: PlatformException(error, Sending SMS message: uid 10153 does not have android.permission.SEND_SMS., null, java.lang.SecurityException: Sending SMS message: uid 10153 does not have android.permission.SEND_SMS.
E/flutter (17922): 	at android.os.Parcel.readException(Parcel.java:1620)
E/flutter (17922): 	at android.os.Parcel.readException(Parcel.java:1573)
E/flutter (17922): 	at com.android.internal.telephony.ISms$Stub$Proxy.sendTextForSubscriber(ISms.java:1577)
E/flutter (17922): 	at android.telephony.SmsManager.sendTextMessageInternal(SmsManager.java:380)
E/flutter (17922): 	at android.telephony.SmsManager.sendTextMessage(SmsManager.java:333)
E/flutter (17922): 	at com.roketstorm.smsker.SmskerPlugin.onMethodCall(SmskerPlugin.kt:48)
E/flutter (17922): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:233)
E/flutter (17922): 	at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:85)
E/flutter (17922): 	at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:738)
E/flutter (17922): 	at android.os.MessageQueue.nativePollOnce(Native Method)
E/flutter (17922): 	at android.os.MessageQueue.next(MessageQueue.java:323)
E/flutter (17922): 	at android.os.Looper.loop(Looper.java:143)
E/flutter (17922): 	at android.app.ActivityThread.main(ActivityThread.java:7231)
E/flutter (17922): 	at java.lang.reflect.Method.invoke(Native Method)
E/flutter (17922): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
E/flutter (17922): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
E/flutter (17922): )
E/flutter (17922): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:582:7)
E/flutter (17922): #1      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:162:18)
E/flutter (17922):
E/flutter (17922): #2      Smsker.sendSms (package:smsker/smsker.dart:16:30)
E/flutter (17922):
E/flutter (17922): #3      _MyAppState._sendMessage (package:feelsafe_dev/main.dart:20:5)
E/flutter (17922):
E/flutter (17922):
√ Built build\app\outputs\flutter-apk\app-debug.apk.
Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:62636/EZmL0jhuojc=/

Can you provide your manifest file please?

At first i had the user-permission tag above application tag and it did not work, after i putted it below  it worked. But shouldn't i put it above??

    <!-- Don't delete the meta-data below.
         This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
    <meta-data
        android:name="flutterEmbedding"
        android:value="2" />
</application>

<uses-permission android:name="android.permission.SEND_SMS" />
<uses-permission android:name="android.permission.INTERNET" />

This is just some metadata, it should ignore order of tags. Glad, it works!

Same again

<uses-permission android:name="android.permission.SEND_SMS" />
<uses-permission android:name="android.permission.INTERNET" />

<!-- io.flutter.app.FlutterApplication is an android.app.Application that
     calls FlutterMain.startInitialization(this); in its onCreate method.
     In most cases you can leave this as-is, but you if you want to provide
     additional functionality it is fine to subclass or reimplement
     FlutterApplication and put your custom class here. -->
<application
    android:name="io.flutter.app.FlutterApplication"
    android:label="feelsafe"
    android:icon="@mipmap/ic_launcher">
    <activity
        android:name=".MainActivity"
        android:launchMode="singleTop"
        android:theme="@style/LaunchTheme"
        android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
        android:hardwareAccelerated="true"
        android:windowSoftInputMode="adjustResize">
        <!-- Specifies an Android theme to apply to this Activity as soon as
             the Android process has started. This theme is visible to the user
             while the Flutter UI initializes. After that, this theme continues
             to determine the Window background behind the Flutter UI. -->
        <meta-data
          android:name="io.flutter.embedding.android.NormalTheme"
          android:resource="@style/NormalTheme"
          />
        <!-- Displays an Android View that continues showing the launch screen
             Drawable until Flutter paints its first frame, then this splash
             screen fades out. A splash screen is useful to avoid any visual
             gap between the end of Android's launch screen and the painting of
             Flutter's first frame. -->
        <meta-data
          android:name="io.flutter.embedding.android.SplashScreenDrawable"
          android:resource="@drawable/launch_background"
          />
        <intent-filter>
            <action android:name="android.intent.action.MAIN"/>
            <category android:name="android.intent.category.LAUNCHER"/>
        </intent-filter>
    </activity>
    <!-- Don't delete the meta-data below.
         This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
    <meta-data
        android:name="flutterEmbedding"
        android:value="2" />
</application>

Try to play with minSdkVersion or targetSdkVersion. One of them should be below 23

Yes i found this wordaround as well,
Should i download sdk 22 in android studio settings as well?

Somewhere says that you should ask for permission at runtime

I managed to make it work using another package, https://pub.dev/packages/permission_handler.
Are you going to emplement the function with dart, or maybe i can create a pull request?
What is your opinion??

I'll implement in the next version. Thanks!


[stable/nginx] add simple nginx chart

Add an nginx chart for hosting simple static content
Signed-off-by: Joe Julian<EMAIL_ADDRESS>What this PR does / why we need it:
There are no simple small charts for adding static web sites to a cluster. This adds one.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

I documented them in the values file and referenced that documentation in the readme

I would be in favor of adding this to helm hub rather than directly to stable (or at a minimum add to incubator first).
There are lots of use cases for nginx, and this makes getting a generic chart right pretty tough. I think having the chance to iterate without the baggage of maintaining stability for a bit would be valuable.

@joejulian have you published it somewhere? What is your current solution to serve static site?


Implemented modeling_simple_baseline pipeline for median rating calculations by genre

A new Kedro pipeline named modeling_simple_baseline has been created.
Functions for training the model on genre-based data and predicting ratings have been set up.
The pipeline is registered and configured within our project's structure.

Hey,  I'm not seeing the changes in here. I think maybe they weren't added in the last commit


Does not work within a ScrollView

Environment
Set up a project and copy the snippet available below.
Description
PagerView component does not work when inside of a ScrollView.
Code Snippet
import React from 'react';
import { ScrollView, StyleSheet, View, Text } from 'react-native';
import PagerView from 'react-native-pager-view';

const MyPager = () => {
  return (
    <ScrollView>
      <PagerView style={styles.pagerView} initialPage={0}>
        <View key="1">
          <Text>First page</Text>
        </View>
        <View key="2">
          <Text>Second page</Text>
        </View>
      </PagerView>
    </ScrollView>
  );
};

const styles = StyleSheet.create({
  pagerView: {
    flex: 1,
  },
});

export default MyPager;

@diegowendel diegowende
Fala Diego :).
This helped me to make it work.
https://github.com/callstack/react-native-pager-view/issues/722

Thanks @marceloch2! Got it working with a version change as well 👍

Obrigado! Consegui que funcionasse com uma mudança de versão também 👍

what you version ?

Hi @plugato Mine is "react-native-pager-view": "7.0.0-rc.0". Hope that's helps.

@marceloch2 @diegowendel When I update to 7.0.0-rc.1, I get the following error:
error: node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts: /Users/pcferreira/Projects/knapp/SupervisorConsole/node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts: Native commands must be exported with the name 'Commands'

Do you know what could be wrong on my setup? I'm using RN v0.73.3

@marceloch2 @diegowendel When I update to 7.0.0-rc.1, I get the following error:
error: node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts: /Users/pcferreira/Projects/knapp/SupervisorConsole/node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts: Native commands must be exported with the name 'Commands'

Do you know what could be wrong on my setup? I'm using RN v0.73.3

+1

Could you please check this example https://github.com/callstack/react-native-pager-view/blob/master/example/src/ScrollablePagerViewExample.tsx , if does not work as well?

Could you please check this example https://github.com/callstack/react-native-pager-view/blob/master/example/src/ScrollablePagerViewExample.tsx , if does not work as well?

I tried it and couldn't get it to work in an iOS. I must say that I copied the example into a custom playground with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>since I didn't want to clone the whole repo (I have very limited storage😖). I also simplified it a little bit.
I got the following errors:
1: When using the useLegacy prop I got this error: requireNativeComponent: "LEGACY_RNCViewPager was not found in the UIManager."
2: When removing the useLegacy prop, the example renders but the ScrollView won't scroll when touching the PagerView (see video)
https://github.com/callstack/react-native-pager-view/assets/74896585/e624d52b-9b1e-44c4-8899-328288fb07fc

@marceloch2 @diegowendel When I update to 7.0.0-rc.1, I get the following error:
error: node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts: /Users/pcferreira/Projects/knapp/SupervisorConsole/node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts: Native commands must be exported with the name 'Commands'

Do you know what could be wrong on my setup? I'm using RN v0.73.3

Got the same issue. Solved by manually patching the export names:
diff --git a/node_modules/react-native-pager-view/src/LEGACY_PagerViewNativeComponent/LEGACY_PagerViewNativeComponent.ts b/node_modules/react-native-pager-view/src/LEGACY_PagerViewNativeComponent/LEGACY_PagerViewNativeComponent.ts
index 4770da9..326fe5f 100644
--- a/node_modules/react-native-pager-view/src/LEGACY_PagerViewNativeComponent/LEGACY_PagerViewNativeComponent.ts
+++ b/node_modules/react-native-pager-view/src/LEGACY_PagerViewNativeComponent/LEGACY_PagerViewNativeComponent.ts
@@ -67,7 +67,7 @@ interface NativeCommands {
   ) => void;
 }

-export const LEGACY_PagerViewNativeCommands: NativeCommands =
+export const Commands: NativeCommands =
   codegenNativeCommands<NativeCommands>({
     supportedCommands: [
       'setPage',
diff --git a/node_modules/react-native-pager-view/src/PagerView.tsx b/node_modules/react-native-pager-view/src/PagerView.tsx
index d2bfec5..5e44bcc 100644
--- a/node_modules/react-native-pager-view/src/PagerView.tsx
+++ b/node_modules/react-native-pager-view/src/PagerView.tsx
@@ -9,7 +9,7 @@ import {
 } from './utils';

 import PagerViewNativeComponent, {
-  PagerViewNativeCommands,
+  Commands as PagerViewNativeCommands,
   OnPageScrollEventData,
   OnPageScrollStateChangedEventData,
   OnPageSelectedEventData,
@@ -17,7 +17,7 @@ import PagerViewNativeComponent, {
 } from './PagerViewNativeComponent/PagerViewNativeComponent';

 import LEGACY_PagerViewNativeComponent, {
-  LEGACY_PagerViewNativeCommands,
+  Commands as LEGACY_PagerViewNativeCommands,
 } from './LEGACY_PagerViewNativeComponent/LEGACY_PagerViewNativeComponent';

 /**
diff --git a/node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts b/node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts
index 9017e53..7d520b0 100644
--- a/node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts
+++ b/node_modules/react-native-pager-view/src/PagerViewNativeComponent/PagerViewNativeComponent.ts
@@ -56,7 +56,7 @@ export interface NativeCommands {
   ) => void;
 }

-export const PagerViewNativeCommands: NativeCommands =
+export const Commands: NativeCommands =
   codegenNativeCommands<NativeCommands>({
     supportedCommands: [
       'setPage',

@leethree
Thank you for providing a fix for that. Would you mind making a PR 🙏

@troZee sure! here it is: https://github.com/callstack/react-native-pager-view/pull/818

Thank you @leethree so much ❤ Once pipeline pass, I will merge it

Could you please check this example https://github.com/callstack/react-native-pager-view/blob/master/example/src/ScrollablePagerViewExample.tsx , if does not work as well?

I tried it and couldn't get it to work in an iOS. I must say that I copied the example into a custom playground with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>since I didn't want to clone the whole repo (I have very limited storage😖). I also simplified it a little bit.
I got the following errors:
1: When using the useLegacy prop I got this error: requireNativeComponent: "LEGACY_RNCViewPager was not found in the UIManager."
2: When removing the useLegacy prop, the example renders but the ScrollView won't scroll when touching the PagerView (see video)
Screen.Recording.2024-04-04.at.12.11.23.mov

Did you solve this? I'm facing it too.

@Kamill90

@Kamill90 will take a look at it in his free time 💪

Yep

Could you please check this example https://github.com/callstack/react-native-pager-view/blob/master/example/src/ScrollablePagerViewExample.tsx , if does not work as well?

I tried it and couldn't get it to work in an iOS. I must say that I copied the example into a custom playground with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>since I didn't want to clone the whole repo (I have very limited storage😖). I also simplified it a little bit.
I got the following errors:
1: When using the useLegacy prop I got this error: requireNativeComponent: "LEGACY_RNCViewPager was not found in the UIManager."
2: When removing the useLegacy prop, the example renders but the ScrollView won't scroll when touching the PagerView (see video)
Screen.Recording.2024-04-04.at.12.11.23.mov

@AgustinMJ I'm still seeing the same invariant violation as of 6.3.1. Did you end up patching?

The scrolling issue persists in the latest Expo SDK 51 while running the app via Expo Go.

The issue still continuous on SDK51 running on Expo Go for IOS (for Android works perfect), but, I notice something strage. If you scroll from up above the Pager component, and before the scrolls stops you swipe again over the Pager Component, it will work so the vertical scroll works.

Running 7.0.0-rc.2 with the above patch by @leethree  applied seemed to fix both issues for me:

not being able to scroll when touch interaction lands anywhere inside pager
pager not being able to handle dynamically sized views and instead has a height of 0

I know the patch was included for 6.3.1 but it would be good to at least get a new rc with the patch applied

@troZee sure! here it is: #818

I'm not getting this fix in 7.0.0-rc2 @troZee , reverted back to 7.0.0.rc0 it works as expected

As a follow up, even though running 7.0.0-rc.2 + provided patch fixed the two bugs I mentioned, it also introduced a bug, any pressables inside the scrollview were not able to be interacted with. So I ended up having to not use this at all and redesign my screens.

I experienced this issue after upgrading from Expo 50 to 51 and can confirm that 7.0.0-rc.2 with the patch provided by @leethree fixed it.

In my case I tried with 6.5.0 on SDK 51 but it didn't even render the pager view. When I upgraded to 7.0.0-rc.2 it failed because of the wrong export names, I applied @leethree patch, now it renders correctly but the vertical scroll only works if I tap on a part of the scroll view that is not the pager view (in my case I have a header and the pager view inside a scroll view, tapping on the header and starting the scroll works).
Taps inside the pager view content work and the horizontal scroll works too, but vertical scroll doesn't.

Closing as per: https://github.com/callstack/react-native-pager-view/releases/tag/v6.6.0
Please create separated issue for 6.6.0 version.


Removing Overlay does not remove balloon if active

I have an overlay that is there, if I select an item so the balloon appears and the Overlay gets removed the balloon stays drawn and does not get removed.  Is this possible to do?
Also is it possible to select an overlay programatically and display a balloon?

I second this issue.

Any news on this?

For now you can test focus and explicitly hide the balloon before removing an overlay:
if (itemizedOverlay.getFocus() != null) {
    itemizedOverlay.hideBalloon();
}
mapOverlays.remove(itemizedOverlay);
mapView.invalidate();

Not ideal, but I'm not sure what if any callbacks I get upon removal/clear of an overlay to do this automatically.

That's great.
On 22 February 2012 16:23, Jeff Gilfelt <
<EMAIL_ADDRESS>
wrote:

For now you can test focus and explicitly hide the balloon before removing
an overlay:
if (itemizedOverlay.getFocus() != null) {
itemizedOverlay.hideBalloon();
}
mapOverlays.remove(itemizedOverlay);
mapView.invalidate();
Not ideal, but I'm not sure what if any callbacks I get upon removal/clear
of an overlay to do this automatically.

Reply to this email directly or view it on GitHub:
https://github.com/jgilfelt/android-mapviewballoons/issues/8#issuecomment-4107424

--
Cameron Cooke
Developer
Tel: 01273 625959
Web: www.brightec.co.uk
Twitter: www.twitter.com/brightec


'Configure puma' task fails as directory in {{ puma_config_path }} does not exist

The directories don't seem to be created yet.

@fonglh Had a similar issue with unicorn when provisioning on remote sites. In my setup I have two sets of config files, a site.yml for Vagrant and and remote-site.yml for production/staging. The main difference is the remote-site.yml includes the deploy role, inserted just before webserver (see example below). This at least ensures that the directories webserver needs are created, but does require a code deploy during the provision process. And it surfaces other issues.
I don't know Ansible very well, so this is all feels a bit hacky to me.
- hosts: application
  handlers:
    - include: roles/delayed_job/handlers/main.yml
  roles:
    - base
    - { role: ruby, tags: ruby }
    - vim
    - deploy
    - webserver


DOC, MAINT: consolidate links; move install doc files into folder

This PR does some housekeeping tasks for the documentation, that I think will lead to easier-to-maintain docs in the long run:

move the installation and configuration pages into a subfolder doc/install (and rename some of them)
consolidate all the various *links.inc into a single file
add a link to the main tutorials page to the topbar
add contributing to the TOC tree on the installation overview page, and fix the title adornments in contributing to match the rest of the docs.

Future intended steps (separate PR) include:

removing anything in doc/links.inc that is only referenced in one place, and putting the link directly in the referencing file instead (easier to maintain, IMO)
overhaul documentation landing page (cf. #5937 and #5944)
moving files out of doc/tutorials and deleting that folder (name is confusing given that tutorials/ and doc/auto_tutorials already exist)
cleanup of doc/manual
possibly unify all literature references into a single file? (allegedly rST citations are global so we wouldn't even need to .. include:: the bibilography file)

@drammock please share the links to rendered doc pages when you have them

Pushed a commit to move overview.rst to index.rst, feel free to revert if you disagree

Thx @larsoner. I'll merge once CIs are green

Thanks @drammock


Add @widgetFactory annotation

This PR adds the @widgetFactory annotation, which allows developers to mark extension methods as widget factories for the purpose of widget creation tracking.
Instrumentation of widget factories has been implemented in the Dart SDK (https://github.com/dart-lang/sdk/issues/50067).
Related issues:

https://github.com/flutter/flutter/issues/112468
https://github.com/flutter/devtools/issues/4772

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

cc @kenzieschmoll @jacob314

Could you resolve the merge conflict? Thanks!

@jacob314 Can you approve this one as well?

@goderbauer The "Google testing"  check seems stuck. Is there anything I should do?

Can you rebase this with the latest master? That should get the check unstuck.

Can you rebase this with the latest master? That should get the check unstuck.

Hm, looks like that didn't help. 🤔


Execution aborted due to an unexpected error

When in a pipeline https://codeocean.allenneuraldynamics.org/capsule/9120588/tree I am getting the error below, which makes debugging very difficult. Is there a way to provide information on where this error is occurring?

@camilolaiton Adding you to the issue

@nal10 just wanted to confirm that you were able to see the logs in Cloudwatch and this is closed, correct?
We are working on Pipeline process monitoring as part of an upcoming version which will allow you to see more information regarding ongoing Pipeline subprocesses to aid in investigation of such issues and have a Feature Request for this functionality here where we will keep everyone updated on development: https://github.com/AllenNeuralDynamics/aind-code-ocean-info/issues/25


HOSTEDCP-829: add KAS egress network policy [release-4.12]

fixed conflict with out of order merge wrt main on https://github.com/openshift/hypershift/pull/2195

/lgtm

/close
We don't backport hypershift-operator changes.   Only HO from main is supporte.d


What is correct way to start ASP.NET core application, when SQL connection fails

I have a ASP.NEt core 2.1 server that is started on-demand. So when someone enters to the web page. My SQL server is in the other location than the web server and there is cases when the SQL server is not up and runnig. So I would need to gracefully start the web server without the SQL server. But so that it of course tries to connect to the SQL server first.
This was working somehow in the ASP.NET Core 1.1, but now with 2.1 I'm getting the exception InvalidOperationException: No database provider has been configured for this DbContext.
I'm using dynamic connection string and I have a function that either returns the connection string, of some other info (like if failure is detected already before.) Code example and same question in the stackoverflow as well:
https://stackoverflow.com/questions/56656167/what-is-correct-way-to-start-asp-net-core-application-when-sql-connection-fails

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a47bf610-692d-9d40-d85f-aec1e2a87a07
Version Independent ID: 3c94634a-4b17-bc13-7436-0c61aea03ab6
Content: Configuring a DbContext - EF Core
Content Source: entity-framework/core/miscellaneous/configuring-dbcontext.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @rowanmiller
Microsoft Alias: divega

@hokpe Can you please post a small, runnable project/solution or complete code listing that demonstrates the behavior you are seeing?

Hi ajcvickers. Thank you for your interest. Today I tried to make such an example. And I added one by one all my used features to the example project generated by the visual studio. And finally I had all the possible parts in it. And it was still working. Then I returned to my actual project and tested the same thing there. And it is working as well. I have updated the .NET core SDK and .NET core runtimes for other reasons, but I didn't test is this working now. So only conclusion is that those updates has fixed this as well.


YARN-1790

https://issues.apache.org/jira/browse/YARN-1790
Render application type in webpage

Can one of the admins verify this patch?


What files does list list for a non-live archive?

Does the list stream end after it's listed all files in the archive? Or does it end after it's listed all files in the local copy? I think it does the second thing, but I was expecting it to do the first one. What do you guys think of updating the behavior of list in this case? If not, a clarification in the README would be cool.

Does the list stream end after it's listed all files in the archive?

If you pass option {live: true} the list stream does not end/callback.

does it end after it's listed all files in the local copy

It should list all the files in the source metadata, regardless of what is in local copy. I tried a test for this but it was passing. How can I reproduce this?

All right, here's what I'm looking at. I would expect archive.list to just hang in this case, because the metadata hasn't been replicated. Instead, it calls the callback. On my machine, this example prints out: null [].
var crypto = require('crypto')
var memdb = require('memdb')

var hyperdrive = require('.')

var drive = hyperdrive(memdb())
var archive2 = drive.createArchive({key: crypto.randomBytes(32), live: false})
archive2.list(console.log)

Ya that does sound like a bug but still can't reproduce it. I have this test but it is passing. Is this what you are doing?
tape('replicates list', function (t) {
  var drive = hyperdrive(memdb())
  var driveClone = hyperdrive(memdb())

  var archive = drive.createArchive({
    live: false,
    file: function (name) {
      return raf(path.join(__dirname, name))
    }
  })

  archive.append('misc.js')
  archive.append('replicates.js')

  archive.finalize(function (err) {
    t.error(err, 'no error')

    var clone = driveClone.createArchive(archive.key, {live: false})

    clone.list(function (err, entries) {
      t.error(err)
      t.same(entries.length, 2, 'has two entries') // PASSES
      t.end()
    })

    var stream = archive.replicate()
    var streamClone = clone.replicate()

    stream.pipe(streamClone).pipe(stream)
  })
})

Ha, I see what's going on now. I thought that I could pass key into drive.createArchive as a property of opts, but that is not allowed! Thanks for taking a look at this!

Oh, yep! I missed that in your code too =)


support Kubernetes 1.20

What
Update task(s) for Kubernetes 1.20.
How

change default API version to storage.k8s.io/v1 for CSIDriver
update kind for test
update runtimes

Checklist

[ ] Finish implementation of the issue
[ ] Test all functions
[ ] Have enough logs to trace activities
[ ] Notify developers of necessary actions

update supporting Kubernetes for 1.18 - 1.20

API version to storage.k8s.io/v1 for CSIDriver
Confirm the implementations below:

For CSI drivers, kubelet no longer creates the target_path for NodePublishVolume in accordance with the CSI spec. Kubelet also no longer checks if staging and target paths are mounts or corrupted. CSI drivers need to be idempotent and do any necessary mount verification. (#88759, @andyzhangx) [SIG Storage]

update controller-runtime to v0.8.2

Check breaking change and High-Impact in change log 0.7.0 - 0.8.2. And apply it.

update other libraries in go.mod

go-logr/logr does not update by hand, because it is dependent for controller-runtime

maintain the build script
updating CSI spec is skipped. It is already the latest version.
updating CSI sidecars are skipped. It is already the latest version.


data: HameedKareem

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Here are the problems I face while working on Biodrop :

I thought I was working on the forked repo before committing the JSON file.
I also think I was working on the data directory, but to my surprise, the code is not there.
I have since replicated this on the forked repo and also made a pull request. I haven't been replied or notified.

I thought I was working on the forked repo before committing the JSON file.
I also think I was working on the data directory, but to my surprise, the code is not there.

We have good documentation with steps to follow to do this, plus a video there also if you prefer. Here is the link https://www.biodrop.io/docs/quickstart-json

I have since replicated this on the forked repo and also made a pull request. I haven't been replied or notified.

Not sure what you mean @maxton4life , the community are trying to help on your pull request here, I can see the conversation above

Looks Good!

@rizahmeds please do not approve a PR without checking it first as this causes extra notifications for maintainers and confusion to the author.  As mentioned above this one needs to be moved to the data folder and the file name needs changing - it is not ready to be merged.

Please how do I move this file to the data folder? Do I need to clone my branch locally? Therefore moving the file into the folder 📂.

Please how do I move this file to the data folder? Do I need to clone my branch locally? Therefore moving the file into the folder 📂.

@maxton4life  Here are steps that you can follow to move your file inside of data folder.
Step 1 : Go to the file changed section from this PR  and click on Edit File. This will redirect you to your forked repo.

Now you are in your forked repo go the input field Hammed.json
go to the begginnig and type data/  this will put you file into the data folder and don't forget to changed the username to your github username.

At last after all the changes have been made you can commit don't create a new Pull Request instaed directly commit to this branch.

Please change the filename to your github username instead of data/Hameed.json  it should be data/maxton4life.json to get your profile merged.
We have mentioned this in our quick start guide https://www.biodrop.io/docs/quickstart-json (in section 7 ).

Okay.
I am on it.


Support for integrating user feedback into Console dot.

Support for integrating user feedback into Console dot.

Console PR: https://github.com/RedHatInsights/insights-chrome/pull/2523

Console is planning on waiting until V5 for this integration


Fix SparkSessionFactory to not fail when using Spark master local[*]

This prevents the factory to fail if using local[*]

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aromanenko-dev (tiny bugfix)


drivers: clock: rcar: Rework structure & filetree

This PR is reworking file tree for clocks definitions for renesas rcar SoCs.
Goals of these commits are:

to deploy a clean clocks definitions file tree as close as linux one as possible.
to use same clock names as linux ones for unification purpose.
to deploy a file tree and rework the drive so that it will be easier to add new SoCs later.

Summary of changes:

dt-bindings: rework renesas clocks dt-bindings

regroup renesas related dt-bindings in a folder
rename renesas rcar common dt-binding to match linux name
add soc specific dt-binding matching linux names
soc dt-bindings are defining clocks matching linux names

dts: use new clocks names

move clocks definitions in SoC layer for each core clock entry

soc: move some part of clock driver into SoC specific files

clock_rcar header defines prototypes for all vendor boards (renesas)
clock soc header defines common values for a whole family (gen3)
clock_r8a.. source is implementing soc specific methods and registers

driver: use new clocks names

call for SoC defined methods
driver will not grow exponentially with number of SoCs to support
most of the new changes should now be in SoC files

Signed-off-by: Aymeric Aillet<EMAIL_ADDRESS>

Thanks Aymeric, this is already in a good shape and will make easier to introduce future SoC series.

Just resolved a conflict after merge of #43056.

@julien-massot @nordic-krch  could you please take a look?

New version deploying a driver per soc in /driver folder is available in #44418.
The version from this PR is therefore obsolete.


Add sprig functions to secret template

What this PR does / why we need it:
This can be useful if you are familiar with Helm template like below.
- type: OCI
  address: docker.pkg.dev
  username: _json_key_base64
  password: {{ .encryptedSecrets.serviceAccount | b64enc }}

Does this PR introduce a user-facing change?:

NONE

/cla sign


Importing files containing YAML Anchors

Describe the Bug
When I attempt to import a file containing a YAML Anchor into a file containing the YAML Alias of said anchor, I get:
invalid stack config file 'orgs/<REDACTED>/anchor-test-resolve.yaml' yaml: unknown anchor 'enabled' referenced
Expected Behavior
I would expect the import to occur first, the anchor to be found, and the alias to resolve it.
It works when I copy the contents of the anchor file into the file containing the alias, so I wonder if this has to do with the validation occurring before the import.
Steps to Reproduce
anchor-test.yaml
anchors:
  enabled: &enabled true

anchor-test-resolve.yaml
import:
  - orgs/<REDACTED>/_defaults
  - orgs/<REDACTED>/anchor-test

components:
  terraform:
    anchor-test-resolve:
      metadata:
        component: <REDACTED>
        inherits:
          - base-<REDACTED>-defaults
          - <REDACTED>-default-template-rule
      vars:
        rule_tree:
          rules:
            children:
              Redirector:
                behaviors:
                  - <REDACTED>:
                      options:
                        enabled: *enabled

Screenshots
No response
Environment
Linux
Atmos 1.32.4
Additional Context
The reason why we are wanting to do this is because we want to manage the values of the anchors by a different team via CODEOWNERS, whereas the aliases are set into a specific ordered list in a file maintained by our internal team.

The scope of YAML anchors is tied to the file boundary. This is consistent with every YAML parser out there. I don't believe this is something we can solve easily while relying on the mainstream YAML parsers.

The reason why we are wanting to do this is because we want to manage the values of the anchors by a different team via CODEOWNERS, whereas the aliases are set into a specific ordered list in a file maintained by our internal team.

Have you you looked into the following:

https://atmos.tools/core-concepts/components/validation which is far more powerful than what you can achieve with CODEOWNERS alone. Then make your policies governed by CODEWONERS.
https://atmos.tools/core-concepts/stacks/imports#go-templates-in-imports parameters can be passed to stacks on import, which can help you achieve some of the DRYness you are seeking

Thanks Erik.
We're definitely using OPA.
Regarding the Go templates...
We need to enforce what specific fields can be set by the non-privileged team, which can include values for a particular object key that is in a list of objects.
If the non-privileged team is providing the context with an import, we would need a way to ensure the specific import is specified in the file they are allowed to manage.
I thought it would be easier to simply import their file and then use the things from their file where we need them.  However, I can appreciate that a) for yaml anchors, you need to parse the yaml, thus this isn't possible (I was thinking you'd resolve the imports first, but it makes sense you are parsing the yaml before importing), and b) Go templates might work if we can enforce that their file imports our file.
So, if I put the context in an import block for the non-privileged team to use, can I write an OPA policy that indicates which file must be imported for that specific context?
If so, I still think it would be easier to maintain if I didn't have to write policy and could govern it by the order of imports, but at least it might solve the use case.
Thanks,
Tom

@hypnotisttom we've introduced support for Sprig functions (some time ago) in go templates. So you should be able to do something like this.
anchors:
  enabled: &enabled true

Then where you need to use it, include it as content that gets injected before processing of the file as YAML, similar as to how Helm works, et al.
{{ .Files.Get "files/configMap.yaml" }}
import:
  - orgs/<REDACTED>/_defaults
  - orgs/<REDACTED>/anchor-test

components:
  terraform:
    anchor-test-resolve:
      metadata:
        component: <REDACTED>
        inherits:
          - base-<REDACTED>-defaults
          - <REDACTED>-default-template-rule
      vars:
        rule_tree:
          rules:
            children:
              Redirector:
                behaviors:
                  - <REDACTED>:
                      options:
                        enabled: *enabled

I haven't tested this, and if for some reason the .Files.Get is not exposed, please open a separate issue to address that. Also, we suggest against using too much Go templating. It's really intended to be used as an escape hatch.
Beyond this, we don't have plans to implement some hack specifically addressing cross-file YAML anchors.


feat(selection-list): support for ngModel

Adds support for NgModel to the selection-list.

Fixes #6896
Note: Based on top of #7334

No longer blocked but needs a rebase.

Running into some meatadata extractor issue with NG_VALUE_ACCESSOR, not sure exactly what's up yet

@josephperrott @jelbourn Renamed the  change event to selectionChange.
Also re-added the selectionChang event on the list option to avoid breaking changes. I marked that one as deprecated because we should encourage people to use the event on the list element instead.
Please have another look.

Setting back to merge-ready.
@tinayuangao if this fails on presubmit, can you help @DevVersion resolve any issues so that this can land for RC3?

is there any update for the documentation planed?


Default policy generated for S3 putObject missing PutObjectAcl for unauthenticated requests

If I take a simple project like:
https://github.com/Schweigi/thumbnail-service
And deploy, access via CURL will always yield "PutObject operation: Access Denied"
$ curl -X POST -H "Content-Type: application/json" -d '{
"width": 64,
    "height": 64,
"data": "'"$( base64 -i network_alt.png )"'"
}' "https://blablawahwah.execute-api.us-east-1.amazonaws.com/dev/"
{"stackTrace": [["/var/task/chalice/app.py", 258, "__call__", "response = view_function(*function_args)"], ["/var/task/app.py", 50, "index", "ContentType='image/{}'.format(format),"], ["/var/task/botocore/client.py", 251, "_api_call", "return self._make_api_call(operation_name, kwargs)"], ["/var/task/botocore/client.py", 537, "_make_api_call", "raise ClientError(parsed_response, operation_name)"]], "errorType": "ClientError", "errorMessage": "An error occurred (AccessDenied) when calling the PutObject operation: Access Denied"}(venv) $ vi ~/.aws/config

If I run "chalice gen-policy", I get:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Action": [
        "s3:PutObject"
      ],
      "Resource": [
        "*"
      ],
      "Effect": "Allow",
      "Sid": "somegreatuididididididid"
    }
  ]
}

If I check my policy associated with this role, it has PutObject and cloudwatch policies.  This is not sufficient to access the S3 bucket (newly created, no additional bucket policies set).
I am getting my head around this, but if I understand correctly, this "should" work as is, if I were authenticating my client request?  And that it should NOT work unless we add PutObjectAcl?  Please clarify.  Should the policy generated include PutObjectAcl?  It should save some head scratching.

I'm running into apparently the same issue, but on another project.
Can we not PUT an object to an S3 bucket if we just have the PutObject permission?

I am running into weird behavior with this as well.
If I manually edit the created policy in AWS and put resource in explicitly (ie "arn:aws:s3:::") it sometimes works, but not always.
Has anyone solved this or have any ideas?

This isn't supported by our analyzer just yet.  This will be difficult to implement because we assume that client method calls correspond to an IAM action, but in this case we actually need to look at the arguments provided to s3.put_object to see if you're setting the ACL of the object.
Your best option would be to manually manage the policies yourself:
# In .chalice/config.json
{
  "autogen_policy": false
}

And then create a .chalice/police-dev.json file that has the necessary permissions.
Marking this as a feature request to the analyzer.  It would be really useful to support this.

I've come across the same issue there's 2 ways around it,
I moved the update ACL into its own call eg:
S3.put_object_acl(ACL='public-read', Bucket=S3_BUCKET, Key=filename)
Which caused chalice to add the appropriate permission to the policy
But I guess this increases the run time of the lambda function
You could just edit the policy manually and add the permission yourself.
OR MAYBE? create a dummy function thats not exposed by the API gateway with the S3.put_object_acl call which will cause chalice to create the right policy but in your main execution do it in the put_object Hacky in the code but possibly the nicest way of running it


Need to guess if what I see is a collapsed markdown cell

Testing #141222
Same as https://github.com/microsoft/vscode/issues/141222#issuecomment-1021172492.
Other than by background color there is no way to quickly identify a collapsed markdown cell:

You mean if it's markdown vs code?

We could

Show a single line of rendered markdown

The first line might not be useful to show rendered - it could be a comment, a table header, etc. We could parse it enough to show the first non-comment line

Add some label or icon like the markdown codicon


HARP-12687: User Images are removed from cache when theme is changed

remove images from cache only if not used in any other MapView

Signed-off-by: stefan.dachwitz<EMAIL_ADDRESS>Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

Looks good to me, but as I understand the ticket, but does it solve the issue? Or maybe there is a follow up planned?
Wouldn´t the MapView.userImageCache and the MapView.imageCache register Images referencing the same MapView, and therefore if MapView.imageCache is cleared it would still clear the userImageCache, as described in the ticket?

That's right. This change does not solve the issue.

That is right, my bad. I caught hung up in fixing the issue when removing shared images (which still happens when the theme is changed).

Reworked the PR to use a proper interface for owners.

retest this please


Cannot add integration

Hi all,
i'm a newbye and i try to use this integration.. The problem that i found is that i cannot add integration in my HA (Home Assistant Core 2023.1.7), when i try to add the integration  i receive an error popup "Impossible to load config flow:”Invalid handler specified"
Any suggestion about where could be the problem?  ..Maybe the release of HA?
Thank in advance  you for your attention.

Hello @domoZAM,
meross_lan used to be 'very' beckward compatible with older HA cores but latest changes (and especially the migration to python 3.11) in core led to abandon this 'policy' and support only very recent HA cores
I'm sorry I didn't update the requirement check in HACS configuration so that it now still states its compatibility with HA core 2023.1
As I've said, due to these continual changes I'm a bit lost at the moment about which versions are compatible but I'm almost sure latest releases only works on HA cores after 2023.7
If you 'need' to install it on core 2023.1 you're left with using a rather old meross_lan implementation (you could try with the first 'Cloudy' release....)


Backend: Implement auth for hardware routes

https://ahaw021.medium.com/mutual-tls-mtls-with-fastapi-and-uvicorn-3b9e91bdf5a6

mTLS will likely be non-feasible the way the hardware location optimization is going.


Support custom fragments in alarm creation

Is your feature request related to a problem? Please describe.

When creating an alarm via a json payload, custom fragments are ignored and not included when creating the Cumulocity IoT Alarm.
Describe the solution you'd like

Alarm creation via a json payload should include any custom fragments provided when creating the Cumulocity IoT Alarm.
Example
The following command publishes a CRITICAL alarm of type myCustomAlarmType to thin-edge.io. It also includes a custom fragment called someOtherCustomFragment which includes extra information about the alarm.
tedge mqtt pub tedge/alarms/critical/myCustomAlarmType/child_device_example '{ "text": "Some test alarm", "someOtherCustomFragment": {"nested":{"value": "extra info"}} }'

The above command should produce an alarm in Cumulocity IoT which the custom fragment someOtherCustomFragment is also present (the source fragment was left out for demonstrative purposes only).
{
    "severity": "critical",
    "someOtherCustomFragment": {
        "nested": {
            "value": "extra info"
        }
    },
    "text": "Some test alarm",
    "time": "2023-01-17T09:42:28.804Z",
    "type": "myCustomAlarmType"
}

Event creation via json already supports custom fragments, so adding custom fragment support to alarm creation would provide a more consistent interface for users.
Describe alternatives you've considered

No other solution was considered.
Additional context

Note: If the alarm existing for the same type is already ACTIVE or ACKNOWLEDGED then the custom fragment information will be ignored by Cumulocity IoT, and only the count fragment will be incremented by 1. The custom fragment information is only accepted by Cumulocity IoT if the alarm is "new".

The issue here is the alarm message that is sent as a JSON message to the tedge-mapper is converted into a smartrest message and forwarded to the c8y cloud. While converting it into the Smartrest message it filters out the custom fragments. This is the reason why the custom fragment for the alarm does not work.
For example:
// Send an alarm message with custom fragments as below

tedge mqtt pub tedge/alarms/critical/temp_high '{ "text": "Some test alarm", "someOtherCustomFragment": {"nested":{"value": "extra info"}} }' -q 2 -r

// Sent to cloud as smartrest message
[c8y/s/us] 301,temp_high,"Some test alarm",2023-01-24T13:31:13.99172905Z

Since the Smart rest does not support the custom fragments, the incoming alarm message must be converted to a C8y JSON message and forwarded to the c8y.

Sending the below alarm message with custom fragments as below.
tedge mqtt pub 'c8y/alarm/alarms/create' '{
   "severity": "critical",
   "someOtherCustomFragment": {
       "nested": {
           "value": "extra info"
       }
   },
   "text": "Some test alarm",
   "time": "2023-01-17T09:42:28.804Z",
   "type": "myCustomAlarmType"
}' -q 2 -r

Note: The c8y UI does not render these messages properly. So, these alarm messages are not visible on UI. One can get the alarm messages using the REST apis or using the cli framework https://goc8ycli.netlify.app/ by querying c8y alarms list --device childops_test | jq


Add S3 bucket for G7 draft documents

Documents for draft services will go into a separate bucket that is not
visible to the outside world. After submissions close we will virus
scan them before migrating only the successfull ones into the live
docuemnts S3 bucket.

Does this also need changes for the environment variables that were added/removed?

Good call! I'll do that now.


fix initial put function may not have host.json

host.json is created by runtime.  During initial put of function, it may not exist.  As a result, no trigger is synched.   Change to use env instead.

:shipit:

Merged


 fit date grid with togglable year browser

Sunday is not showing now when year scroller is toggled visible on narrow mobile screens. Needs a UI design.

Moved to https://github.com/vaadin/vaadin-date-picker/issues/99


error: static assertion failed

Hey,
the following error appears several times with TC_USE_DOUBLE=1 on installing mpm.
error: static assertion failed: GridState<2> size must be POT
static_assert(bit::is_power_of_two((int)sizeof(GridState<2>)),
CPU info:
Model:               60
Model name:          Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz

any comment on this topic?

Hi, is there a specific reason why you want double-precision mpm? I think it is double precision for MPM is out-of-maintenance for a while and may not be fixed easily.

For simulations with high stiffness and consequently small time steps (in the order of -6), there are particles moving slightly during the simulation, though they should not! In other words, a pattern of rectangular tiles is forming in the non-disturb region. I guess it might be related to the single precision compilation as this effect disappear if lower stiffness is adopted.

do you think this topic will be fixed in the future?

Resolving grid structure to be POT is easy but @yuanming-hu, could you please address the other sources of the errors when using the double-precision option? It would be really important to use that as @forfor112 mentioned.


fix typo at bottom of settings page

Simple typo in the footer on the settings page
Relevant issue number(s) if applicable
Did you run npm run lint from the viewer or parliament directory (whichever you are making changes to) and correct any errors
Yep
Did you Ensure that all tests still pass by navigating to the tests directory and running ./tests.pl --viewer
Yep
License
I confirm that this contribution is made under an Apache 2.0 license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

thanks


TAPify; use setEncoding

Not sure if you're still maintaining this. Is there an alternative I should be trying?
Regarding the actual pull, the tests pass on Node 0.6.9. Two notes on that:

I replaced client.flush() calls with an async loop on the client.write() callback.
test_one_line_ending_in_nl.js didn't have a client.end() call, I'm not sure if that was intended.

The other part to this pull is a small patch to use the Node facility setEncoding for decoding streams, rather than data.toString on chunks of data.

Version 0.1.4 is out, thanks for the great contribution!


KAFKA-4422 / KAFKA-8700 / KAFKA-5566: Wait for state to transit to RUNNING upon start

I looked into the logs of the above tickets, and I think for a couple fo them it is due to the fact that the threads takes time to restore, or just stabilize the rebalance since there are multi-threads. Adding the hook to wait for state to transit to RUNNING upon starting.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@cpettitt-confluent @mjsax for reviews.

Cherry-picked to 2.4.


⚠ LPDM Handbook (hosted on Divio) has degraded performance

In fdb6d46, LPDM Handbook (hosted on Divio) (https://repohubdev.tk) experienced degraded performance:

HTTP code: 500
Response time: 5169 ms

Resolved: LPDM Handbook (hosted on Divio) performance has improved in f002ee5.


Add methods "width" (estimate as an interval) and "is_atomic"

width is interesting when the width of an interval inters computations (e.g. ∫ₐᵇ ... = width([a,b]) ∫₀¹ ...).
is_atomic helps, say, when we a trying to split an interval for refinement.

I find these functions interesting/useful too. But I don't have any plans to add new operations that are not present in IEEE Std 1788 at the moment.
BTW, I have another implementation of is_atomic, which is simpler but maybe less performant than yours ;-)

I encourage you to add “recipes” page to the documentation for sharing codes that others may find useful.


fix(tabs): Tab widget now supports custom padding (Fixes issue #502))

The tab widget now contains the values padding_left/padding_right and the function padding() that sets those values.
Should fix issue #502.

Cool. I didn't realize that the spacing before the tabs was coming from padding left / right. My mental model without having looked at the code was that the spaces "belonged to the divider. This solution is better than the ones on the Issue.
A question though, what if we made the padding accept  &str instead of just a number?
A follow up to this might be to make padding accept Line to make the divider / padding able to be styled easily.
Imagine:
🭊🭁Tab 1🭌🬿 🭊🭁Tab 2🭌🬿

But with the background of the label part the same color as the tab padding parts.
(copied from the discord feedback so that it's recorded for posterity)

Hey, would you mind setting up commit signing?
https://github.com/ratatui-org/ratatui/blob/main/CONTRIBUTING.md#sign-your-commits

I did, I think something went wrong as it says the email does not match the signature.

Github mangles your email address to<EMAIL_ADDRESS>is that setup as being valid for signing?

Thanks for fixing up the commit signing - Github still complains that it can't merge them as it needs all the commits to be signed. Can you please squash the commits into a single signed commit and force push the single commit as an update to your branch?

Just merged this - thanks again for the PR :)


WIP: Disable ES output for Fluentd when cluster is a Calico Cloud management cluster

Description

Add logic to handle disabling ES output for Fluentd when cluster is a Calico Cloud management cluster.

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.


⚠ SpeakUpForHope.org has degraded performance

In 7ee8ecb, SpeakUpForHope.org (https://www.speakupforhope.org) experienced degraded performance:

HTTP code: 200
Response time: 10210 ms

Resolved: SpeakUpForHope.org performance has improved in ef2bc23 after 10 minutes.


Suggestion for GU audio: example for simple beep or implement bell via print \a

I am wanting to implement a simple beep through the Galactic Unicorn audio but the audio subsystem is very complex to understand for this kind of basic requirement so an example in the documentation or some simpler code in the examples directory would be really useful.
Even better would be implementation of the print \a bell character!

You're right, it's awfully complex and could probably stand a channel reserved for some basic utility effects. Though hooking print() in MicroPython would probably be quite tricky.
In the mean time here's how to configure a channel to use as a basic beeper in MicroPython:
import time
from cosmic import CosmicUnicorn

cu = CosmicUnicorn()

# New beeper on channel 1
beeper = cu.synth_channel(1)

# Configure the beeper waveform and envelope
beeper.configure(
    waveforms=beeper.SINE + beeper.SQUARE,
    attack=0.05,
    decay=0.5,
    sustain=0,
    release=0,
    volume=1.0
)

# Configure the beeper frequency
beeper.frequency(440)

# Start the synth engine running
cu.play_synth()

# Beep lots
while True:
    beeper.trigger_attack()
    time.sleep(1.0)

Once configured you can call trigger_attack() where you need in order to make it beep.
SQUARE + SINE is mellow-ish, a pure SQUARE will be a little more shouty.


remove get_counts

DON'T MERGE YET.
This change will go out after we merge #71 and release v0.3.0 to CRAN. #69 added a deprecation warning on the get_counts function that will ship to CRAN with the next release. This PR, which will be the first on the way to 0.4.0 (or maybe 1.0.0???), removes get_counts from the package. Unfortunately this didn't allow us to clean up the dependencies at all but it will simplify the package and make the philosophy of uptasticsearch clearer.
There are no tests in the diff because we never had any, which is fun.

#71 is merged and 0.3.0 is (out on CRAN!)[https://cran.r-project.org/web/packages/uptasticsearch/index.html]
gonna merge this up as soon as travis builds

very very excited to merge this one and simplify the package. This is the first step on our path from 0.3.0 to 1.0.0!


Master to Live

Docs Build status updates of commit 829fd99:
:clock10: Pending: waiting for processors (28 builds ahead of you)
:warning: Docs Build is busy, currently there are 28 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 829fd99:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

exchange/docs-conceptual/connect-to-exchange-online-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Connect-ExchangeOnline.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Connect-IPPSSession.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXOCasMailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXOMailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXORecipient.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-EXORecipientPermission.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-MyAnalyticsFeatureConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/sharepoint-ps/sharepoint-online/Unlock-SPOSensitivityLabelEncryptedFile.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Remove-SPClaimTypeMapping.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Remove-SPTrustedRootAuthority.md
:white_check_mark:Succeeded
View (sharepoint-ps)

skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

Line 0, Column 0: [Warning-microsoft-graph-api-failed]

Call to Microsoft Graph API failed: Code: generalException
Message: An error occurred sending the request.
 Try closing and reopening the PR. If you get this Error again, file an issue.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


bgp_graceful_restart_test.go

Hi,
source/destination address has to be either prefix/32 or  CIDR/mask has to be provided while configuring acl.
1.) a2.SourceAddress = ygot.String(ateDst.IPv4CIDR())  ==> script is sending "<IP_ADDRESS>/30" , it does not work. WE need to send either
<IP_ADDRESS>/30   or <IP_ADDRESS>/32 (exact prefix)
2.) We need to update it to configure network instance type.
Thanks,
Prabha

Thank you Prabha, this seems reasonable.  Would you like to submit a PR to directly update the test?

Sure Darren. I will submit a PR.
Thanks,
Prabha


question about Python support

First thanks for the awesome project.
Question about Python support in
https://github.com/QuantConnect/Lean/tree/master/Algorithm.Python#python-autocomplete-imports
In this sentence

Copy and paste the imports found here to the top of your project file to enable autocomplete.

What is the "your project file" ? Could you please give an example?
Is it Lean/Algorithm.Python/BasicTemplateFrameworkAlgorithm.py in the standard testing case?

Hey, we think this is old and will update it today; you should only need:
from AlgorithmImports import *
at the top of all your files.

Thanks for your help @jaredbroad !


Remove bootstrap-sass

And the need for apps to pull in import<EMAIL_ADDRESS>Create new classes instead that should be bundled into the quickstarts.css.

@jschuler, do you know how soon this will be resolved?  It is blocking https://github.com/openshift/console/pull/9532, and we intend to delivery that with 4.9 (for which code freeze is in 6 weeks).
cc:  @sg00dwin @spadgett


Godoc for List operation is potentially misleaiding

func (Client) List
func (client Client) List(filter string, top *int32) (result ResourceListResult, err error)
List get all of the resources under a subscription.

filter is the filter to apply on the operation. top is query parameters. If null is passed returns all resource groups.

I don't think it really turns all resource groups. I think this only returns the first page as the server sends it. (I'm assume that in OData the server can set a maximum page size that forces the client to page.)
Is my assumption true?
If so, should we update the docs, or should we update the List() call so that it automatically pages if you pass nil for the top *int32 parameter?

@colemickens This might be because we have to implement the OData support.

I don't think it really turns all resource groups. I think this only returns the first page as the server sends it. (I'm assume that in OData the server can set a maximum page size that forces the client to page.)
Is my assumption true?

Your assumption is true. It returns to you a ResourceListResult of which the definition looks like this:
// ResourceListResult is list of resource groups.
type ResourceListResult struct {
	autorest.Response `json:"-"`
	Value             *[]GenericResource `json:"value,omitempty"`
	NextLink          *string            `json:"nextLink,omitempty"`
}

Above code from arm/resources/resources/models.go
If NextLink is not nil then there are additional values that still need to be iterated over.
That said, I believe the whole Azure SDK for Go team would agree that this is not as intuitive as it could be. What would you think of a future Azure SDK release where list results were returned as readonly channels? We could update go-autorest to take care of paging the responses for folks and because we'd be using channels, the threading required to make it happen could be completely opaque to the user.
Thoughts?

What would you think of a future Azure SDK release where list results were returned as readonly channels? We could update go-autorest to take care of paging the responses for folks and because we'd be using channels, the threading required to make it happen could be completely opaque to the user.

Hm. I guess if it was optional, maybe. A GetAll set of functions that do the paging would be fine. The channel would be an optimization on that for really huge results lists, I suppose. Interesting idea!

Alright, we've talked a little about what we could do to improve the results of List operations in general. At the end of the day, it basically means refactoring/rewriting the ms-pageable extension. At the moment, that would go on the backlog. (Though, personally, that's something that I would love to knock out as a hack-a-thon project or something.)
In terms of the original question, which is that documentation like this is sorta misleading. It neglects to mention that while it does "return" all, it does so in chunks and requires multiple network hits. Even worse, at the moment, it requires surrounding code in a loop. However, it's not wrong, just sorta scummy and speaking logically instead of practically. I hate to say this, but if we're just talking about improving the docs, we should create more targeted documentation issues that bother us. For now, I'm going to close this issue. Please open it back up if you disagree with my evaluation of the situation.

Hm, not sure what all was discussed, but I can leave the docs bugs be for now - the API signature makes it pretty obvious that there is paging the user needs to handle.
But... I still think it'd be pretty easy to generate a a real GetAll function that implements the same loop that every single consumer of the SDK is probably writing today as it were.
Will you keep an Issue open for that? :) Or do you want me to file it against AutoRest maybe since it would be a change in the C#/razor?

That is totally legit! I'll open one up against the AutoRest repository and see what I can do about it. :)


[Bug]: Nifti File writer does not save sitkImage directions

Hi all,
I'm trying to write a simple script to sample a volume and save the resulting samples as NIFTI files in the same coordinate space as the original volume. In the process of doing this, I discovered that sitk.WriteImage() does not save the direction meta data to the NIFTI file.
I believe this is a bug and have a minimal example to reproduce the behavior.
import SimpleITK as sitk
import numpy as np

if __name__ == '__main__':
    theta = np.deg2rad(20)
    img = sitk.GridSource(size=(64, 64), outputPixelType=sitk.sitkUInt16)
    euler2d_transform = sitk.Euler2DTransform()
    euler2d_transform.SetAngle(theta)
    img = sitk.Resample(img, euler2d_transform)
    img.SetDirection(
        np.multiply(np.reshape(img.GetDirection(), (2, 2)),
                    np.reshape(euler2d_transform.GetMatrix(), (2, 2))).flatten())
    img.SetOrigin(euler2d_transform.TransformPoint(img.GetOrigin()))
    sitk.WriteImage(img, 'test.nii.gz')
    img1 = sitk.ReadImage('test.nii.gz')
    assert img == img1

This sample returns the following error:
RuntimeError: Exception thrown in SimpleITK Equal: /Users/runner/work/1/sitk-build/ITK-prefix/include/ITK-5.2/itkImageToImageFilter.hxx:220:
ITK ERROR: BinaryFunctorImageFilter(0x7f88acc9c650): Inputs do not occupy the same physical space!
InputImage Direction: 9.3969262e-01 0.0000000e+00
0.0000000e+00 9.3969262e-01
, InputImage_1 Direction: 1.0000000e+00 0.0000000e+00
0.0000000e+00 1.0000000e+00

	Tolerance: 1.0000000e-06

Happy to discuss if I am mistaken.
Best,
Walter

Your matrix is not orthonormal, and contains scaling.
You are using the element-size multiplicationnp.multiply not matrix multiplication np.matmul.

Wow, thanks for pointing that out! If SimpleITK had warned it was discarding a non-orthonormal direction matrix on saving, I would have found this sooner.

Please consider reporting the request for a warning to ITK:
https://github.com/InsightSoftwareConsortium/ITK/issues


StorageVolUpload corrupts image

I try to upload a Ubuntu image to libvirt via StorageVolUpload. If I upload the image from a file it does work but if I upload it from a http stream the image gets corrupted.
Strangely it does work from http stream as well if I use a big buffered reader in between.
Does anyone have an idea whats going on here?
Here are the steps to reproduce the behaviour:

download the image

curl -O https://cloud-images.ubuntu.com/minimal/releases/disco/release-20190605/ubuntu-19.04-minimal-cloudimg-amd64.img

download test code main.txt

curl -o main.go https://github.com/digitalocean/go-libvirt/files/3311212/main.txt

run test

go run main.go

compare downloaded files in /var/lib/libvirt/images (or where ever your default pool stores the files)

sha256sum /var/lib/libvirt/images/image_from_*

The actual size of that image file (https://cloud-images.ubuntu.com/minimal/releases/disco/release-20190605/ubuntu-19.04-minimal-cloudimg-amd64.img) is 155MB, so for your test that uses a large buffered reader, the image will fit completely in the reader's buffer. I suspect that's a clue. Can you try this test without using the progress bar's ProxyReader? I'm wondering if that code has a bug that causes it to report that the transfer is complete, when it actually isn't.

@trapgate thank you for your answer. That was also my first guess, but the ProxyReader does not cause the problem. The same problem appears without progress bar.
To check if StorageVolUpload consumes all data from the reader I used the CountReader in my example. The number of bytes read from the http stream and from the file are the same. However, in the end the image from http has a smaller size in /var/lib/libvirt/images.
-rw------- 1 root root 162529280 20. Jun 21:38 /var/lib/libvirt/images/image_from_file
-rw------- 1 root root 162512896 20. Jun 21:39 /var/lib/libvirt/images/image_from_http

To me it looks that something is not properly flushed in the end.

@dsbrng25b do you run Flush method and check error from it and from Close method?

@vtolstov I used defer resp.Body.Close() for the http stream.  Now I moved the resp.Body.Close() before the ConnectClose and checked for errors but it does not return an error.
Which Flush method do you mean? As far as I understand a Flush or Close method is not required because the StorageVolUpload accepts an io.Reader. So to my understanding StorageVolUpload should Read until io.EOF.

I found the problem. The sendStream function does not return remaining bytes on io.EOF (see #83).


404 generic handler

Added a base 404 handler. You can now add 404 handling by creating a 404.html file in your root of templates.
Also, began working on better error handling by removing map_sql_error for all diesel calls. It is now done through a from<diesel::result::error> impl on CustomHttpError.
Added some documentation in the README.md for this too.
Closes #14

Started #13.


Add ActivityFeed to record activity feed events

Codecov Report

Merging #683 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #683   +/-   ##
=======================================
  Coverage   87.97%   87.97%
=======================================
  Files         193      193
  Lines        7716     7716
=======================================
  Hits         6788     6788
  Misses        928      928

I still don't fully understand why all the additions don't show up in the test coverage. @beaugunderson can you help me out to see what's going on?

looks like something changed in the codecov config? i'll see if it's an easy fix

Thanks! 👍

also i'm no longer an org owner so one of you should visit codecov and go through the upgrade flow:

i don't see an issue with the yaml so it may just be an issue of this repo being on the legacy service and not knowing how to handle pull requests anymore... @gedankenstuecke upgrade and see if that fixes it :)

Ok, I ran the update and added OpenHumans/open-humans to their list. I can't see any changes so far on their end though.


🐛 [Bug report]: Handling the error on Emojipedia play

Descrcibe the bug?
Whenever the api is not able to fetch the emojis data the page is breaking.

Steps to reproduce the bug?

Clone reactplay locally
Set the env variables
And then when you run the app using npm start, the page of emojiPedia breaks
To run it in your local set api key with your own access_key from https://emoji-api.com/ in your .env file
But while you try to push it for a preview in vercel the page breaks again

Expected behavior
There should be an error handling message and a button which would navigate you back to Reactplay if the api breaks.
Desktop (Please provide your system information)
Desktop: Windows
Browser: Chrome, firefox
Mobile (Please provide your device information)
No response
Screenshot / Screenshare
No response
Relevant log output
No response
Code of Conduct

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

@atapas Can you please assign me to this task


Teleport to spawn on join not working as expected

Hi there! I'm having some troubles configuring this plugin to do what I expect. I'm running a 3 server network. All 3 servers running paper, the "hub" server is the one running this plugin. I'm using Velocity as the proxy for the network.
Here's a relevant snippet of the config file:
# teleport the player to spawn on join
teleport-on-join:
  enabled: true
  # teleport the player ONLY on first join
  only-first-join: false

What I expect to happen: Whenever the player joins the hub, the player is teleported to spawn.
What is actually happening: The player maintains their last position.
I've already restarted the server and such. The /spawn set and /spawn commands are working as intended.
Let me know if there's anything else I'm supposed to do to achieve my goal, or if that goal is something this plugin even aims to solve. Thank you for your time and work on this plugin!

Hi, sorry to hear that the plugin is not working as expected. Your goal is actually one of the use cases I created the plugin for.
I've just tested it on Paper 1.21.1 (build 132) and 1.21.3 (build 77) behind Velocity 3.4.0 (build 452) and it works as expected on my end.
Could you please try if this solves the problem:
If you are using the world-list, make sure it does not accidentally prevent this feature from working.
All features have bypass permissions (spawn.bypass.join-teleport, spawn.bypass.world-list are relevant in your case) which are currently given to op's by default. You can negate this permission by setting it to false with a permission plugin.
If this is not the case and even non op players are not teleported, please check if another plugin is forcing them to their last position. You can also test if this happens with most/all other plugins disabled.
Please let me know if any of these steps have solved the problem or if you need further assistance.

Thank you for your help & for testing it out for me! I got it working properly, it turned out to be a combination of two things. I had removed some of the options I knew I'd never use from the config file to keep it slim, which seemed to cause the plugin to behave improperly sometimes (I noticed it throwing tracebacks in the console eventually). The other part is I didn't realize that op privileges where overriding it. I was so focused on trying to get the basic function of the plugin working before thinking about permissions that I never looked at that section of the docs (sorry! I should have considered that).


Fix bugs where internship list reset after edit and mark command

closes #129
closes #155

Codecov Report

Merging #160 (7372151) into master (8973a51) will increase coverage by 0.17%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #160      +/-   ##
============================================
+ Coverage     70.77%   70.95%   +0.17%
- Complexity      484      486       +2
============================================
  Files            79       79
  Lines          1598     1601       +3
  Branches        169      169
============================================
+ Hits           1131     1136       +5
+ Misses          413      412       -1
+ Partials         54       53       -1

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

...java/seedu/address/logic/commands/EditCommand.java
96.47% <100.00%> (ø)

...java/seedu/address/logic/commands/MarkCommand.java
90.90% <100.00%> (+6.06%)
:arrow_up:

...rc/main/java/seedu/address/model/ModelManager.java
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


FIX: sam parser empty case

Not sure the best way to handle this.  Right now it returns a nested empty list.
Specific suggestions are welcome.  I couldn't figure out how to return an empty iterator.

tests failed

Coverage decreased (-0.08%) to 85.656% when pulling 4d551c7129e5897e5f81f8513d0544637d9e6221 on mortonjt:bf into 976ff939bdbccc27ac1e642cdaab85d274f419b4 on biocore:master.


Support of Separate linked Write and Read targets

Many thanks for developing this GUI!
Since js.controller 3.x, an Alias can have separate targets for write and read objects. This is currently not implemented in any GUI and must be created manually using Admin in the Raw settings for the Alias object.
It would be very nice if it also was supported by the Alias Manager.
Reference - Alias Documentation (in German, it's missing in the English version): https://www.iobroker.net/#de/documentation/dev/aliases.md
Example from manually created Alias with separate Targets:
{   "from": "system.adapter.admin.0",   "user": "system.user.admin",   "ts":<PHONE_NUMBER>319,   "common": {     "name": "currentstate",     "role": "state",     "type": "boolean",     "desc": "Manually created",     "read": true,     "write": true,     "def": false,     "alias": {       "id": {           "read": "knx.0.VVS_och_VA.Ventilation.Köksfläkt_Status_Värde",           "write": "knx.0.VVS_och_VA.Ventilation.Köksfläkt_Värde"       },       "read": "val > 40",       "write": "val ? 80 : 40"     }   },   "native": {},   "acl": {     "object": 1636,     "owner": "system.user.admin",     "ownerGroup": "system.group.administrator",     "state": 1636   },   "_id": "alias.0.uuid-533453-334345.fan.currentstate",   "type": "state" }

Solved with 0.1.0


feat(assert): Add assert_data_eq!

This leaves us room to evaluate #223
Fixes #226
Cherry pick 2a1a25f (#296)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

12 of 12 (100.0%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.04%) to 51.873%

Files with Coverage Reduction
New Missed Lines
%

crates/snapbox/src/lib.rs
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
1343

Relevant Lines:
2589

💛  - Coveralls


Modifying index.html

Modifying index.html file to enhance the UI

Change looks good. New UI looks more user-friendly.


[BUG] The split index's shards cannot be assigned because of the source index's index.blocks.read_only setting

Describe the bug
When executing Split API , if we set the index.blocks.read_only setting of the source index to true, then the Split API responds slowly and finally return an action_request_validation_exception with 400 status code, but the new splitted index is created and only part of the new shards are STARTED, so the new split index's health is red. By checking the log, it shows that the unassigned shards cannot be recovered because the new split index has a read_only block:
Caused by: org.opensearch.cluster.block.ClusterBlockException: index [index111] blocked by: [FORBIDDEN/5/index read-only (api)]
I think it means that the new spit index's settings are copied from the source index, so the index.blocks.read_only setting of the new spit index is true. After changing the setting to false  and executing POST _cluster/reroute?retry_failed=true to retry recovering the unassigned shards, the new spit index's health then became green.
So, should we add more validations for Split & Shrink & Clone API ? Maybe we can throw an action_request_validation_exception with 400 when the source index's index.blocks.read_only or index.blocks.metadata setting was set to true.
Besides, why only parts of new spit index's shards are assigned and in STARTED status? That's really confused and there might be some other underlying problems.
To Reproduce
Steps to reproduce the behavior:

Update the source index's index.blocks.read_only setting to true

PUT opensearch_dashboards_sample_data_ecommerce/_settings
{
  "index.blocks.read_only":true
}

Executing the Split API

POST opensearch_dashboards_sample_data_ecommerce/_split/index111
{
  "settings":{
    "index.number_of_shards":6,
    "index.number_of_replicas":0
  }
}

the response is:
{
  "error" : {
    "root_cause" : [
      {
        "type" : "action_request_validation_exception",
        "reason" : "Validation Failed: 1: index.number_of_shards is required for split operations;"
      }
    ],
    "type" : "action_request_validation_exception",
    "reason" : "Validation Failed: 1: index.number_of_shards is required for split operations;"
  },
  "status" : 400
}

Check the new split index

GET _cat/shards/index111
GET index111/_recovery
GET _cluster/health/index111

we can see that only parts of the new shards are STARTED and the new index's health is red.
Expected behavior
Add more validations for Split & Shrink & Clone API to avoid the above situation.
Host/Environment (please complete the following information):

OS: macOS
Version: 12.5.1
The opensearch version is 2.3.

@nandi-github Could you look into this?

From the code I found that there is a block check, but it's useless because the new split index has not been created yet:
https://github.com/opensearch-project/OpenSearch/blob/31bcda613083707db16d6673454386cef6e24f11/server/src/main/java/org/opensearch/action/admin/indices/shrink/TransportResizeAction.java.
So maybe we should check the MATADATA_WRITE block when creating the new split index, like this:
https://github.com/opensearch-project/OpenSearch/blob/31bcda613083707db16d6673454386cef6e24f11/server/src/main/java/org/opensearch/cluster/metadata/MetadataCreateIndexService.java#L1314.
I think we can throw an illegalArgumentException if the new split index has a METADATA_WRITE block because it will prevent the new shards from being allocated , there are two situations the new split index may have a METADATA_WRITE block:

User sets index setting index.blocks.read_only or index.blocks.metadata to true explicitly in the API's request body parameter settings.
The source index's setting index.blocks.read_only is true, and user does not set index setting index.blocks.read_only to false explicitly in the API's request body(if user does so, the setting in the request body will overwrite the setting copied from the source index).
For another situation, if the source index's setting index.blocks.metadata is true, a cluster_block_exception will be thrown early in getting source index's stats, so the new split index will not have a METADATA_WRITE block.

@nandi-github may I know your opinion about this?


Maintain Styling format from existing file

I have an excel file which its content contains some styles, such as merged cell, bolded text, aligned cell.
I read the file using XLSX.readFile and get sheetname by
 const guideSheetName = templateWorkbook.SheetNames[0]
 const guideWorkSheet = templateWorkbook.Sheets[guideSheetName]

then I created new Workbook and append the sheet to this workbook
XLSX.utils.book_append_sheet(newExcel, guideWorkSheet, 'Sheet1')
but when i saved the file, styling format gone. I just have unformatted worksheet. there are no styles, such as merged cell, bolded tex, aligned cell as well as previous excel file
Ho can I maintain the formating style from previous workbook to new workbook?

This is currently in the purview of our Pro builds, see https://sheetjs.com/pro for more info


Invite JScott-JMC to CDCgov GitHub Organization

What type of help do you need?

[ ] Question
[ ] New Repo
[ ] Delete Repo
[X ] User Membership (please make sure new members are familiar with the CDC open practices and set up their profile with name and org info to help people collaborate with them)
[ ] Other

Please describe how you'd like us to help.
Please invite @JScott-JMC to the CDCgov GitHub organization. Their CDC e-mail is<EMAIL_ADDRESS>

Invitation sent to JScott-JMC. They will have to accept the invitation within 7 days.


System.Reflection.ReflectionTypeLoadException Method does not have an implementation

Duplicate of #709. I recieve a very similar message when upgrading my project to 2.2
Unable to load one or more of the requested types.Method 'BuildModel' in type 'XXXDbContextModelSnapshot' from assembly 'MyProject' does not have an implementation.

Eventually I was able to find out that the NSwag.MSBuild package uses Microsoft.EntityFrameworkCore version 2.2.4, whereas my project directly referenced 2.2.6.
Fortunately I am able to use 2.2.4 but if I did want to use 2.2.6 which fixes a potential memory leak, what can I do?

Why does NSwag.MSBuild have a dep to ef core??

I don't think it is supposed to as it only seems to be an issue with 2.2. I thought it would be something to do with the Microsoft.AspNetCore.App metapackage but that isn't referenced anywhere so I have no idea where they are coming from.

How are you calling nswag.msbuild? With project or assembly parameter?

As part of my build, in the csproj:
  <Target Name="NSwag" AfterTargets="Build">
    <Copy SourceFiles="@(ReferencePath)" DestinationFolder="$(OutDir)References" />
    <Exec Command="$(NSwagExe_Core22) run nswag.json /variables:Configuration=$(Configuration),OutDir=$(OutDir),AssemblyName=$(AssemblyName)" />
    <RemoveDir Directories="$(OutDir)References" />
  </Target>

nswag.json
{
  "runtime": "NetCore22",
  "defaultVariables": null,
  "documentGenerator": {
    "aspNetCoreToOpenApi": {
      "project": "",
      "msBuildProjectExtensionsPath": null,
      "configuration": null,
      "runtime": null,
      "targetFramework": null,
      "noBuild": true,
      "verbose": true,
      "workingDirectory": null,
      "requireParametersWithoutDefault": false,
      "apiGroupNames": null,
      "defaultPropertyNameHandling": "Default",
      "defaultReferenceTypeNullHandling": "Null",
      "defaultDictionaryValueReferenceTypeNullHandling": "NotNull",
      "defaultResponseReferenceTypeNullHandling": "Null",
      "defaultEnumHandling": "Integer",
      "flattenInheritanceHierarchy": false,
      "generateKnownTypes": true,
      "generateEnumMappingDescription": false,
      "generateXmlObjects": false,
      "generateAbstractProperties": false,
      "generateAbstractSchemas": true,
      "ignoreObsoleteProperties": false,
      "allowReferencesWithProperties": false,
      "excludedTypeNames": [],
      "serviceHost": null,
      "serviceBasePath": null,
      "serviceSchemes": [],
      "infoTitle": "My Title",
      "infoDescription": null,
      "infoVersion": "1.0.0",
      "documentTemplate": null,
      "documentProcessorTypes": [],
      "operationProcessorTypes": [],
      "typeNameGeneratorType": null,
      "schemaNameGeneratorType": null,
      "contractResolverType": null,
      "serializerSettingsType": null,
      "useDocumentProvider": true,
      "documentName": "v1",
      "aspNetCoreEnvironment": null,
      "createWebHostBuilderMethod": null,
      "startupType": null,
      "allowNullableBodyParameters": true,
      "output": null,
      "outputType": "OpenApi3",
      "assemblyPaths": [
        "$(OutDir)$(AssemblyName).dll"
      ],
      "assemblyConfig": null,
      "referencePaths": [],
      "useNuGetCache": false
    }
  },
  "codeGenerators": {
    "openApiToTypeScriptClient": {
       // ...snip
    }
  }
}


2431 hotfix missing logical files

@pkdash @aphelionz @martinseul Brute-force to fixing missing logical files creates missing generic logical files as needed.
This is not finished but is provided for reference for others who might be working on the problem.

The game plan is to use ResourceFile.get_or_create_logical_file in any place that ResourceFile.logical_file fails to work due to a missing logical file. This includes templates.
Behavior of get_or_create_logical_file is identical to behavior of ./hsctl managepy fix_missing_logical_files.

Need to merge into 1.14RC instead.

Build finished.


Simple Wordcount

As Kettle developer I want to use Spoon’s drag and drop interface to create a simple word count.
See also here for the Apache Beam reference.

Added documentation on how to run

Exciting times! Thanks a lot!

Experimental so let me know what breaks. Over the weekend I'll try to implement #3 so you can also run on GCP Dataflow.

Tried to run mvn clean install and got this error:
[dsteiner@dellxps kettle-beam-core]$ mvn clean install
[INFO] Scanning for projects...
Downloading from eclipse-maven-repo: https://mvnrepository.com/org/pentaho/pentaho-ce-jar-parent-pom/8.1-SNAPSHOT/maven-metadata.xml
Downloading from eclipse-maven-repo: https://mvnrepository.com/org/pentaho/pentaho-ce-jar-parent-pom/8.1-SNAPSHOT/pentaho-ce-jar-parent-pom-8.1-SNAPSHOT.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for kettle-beam:kettle-beam-core:0.0.4-SNAPSHOT: Could not find artifact org.pentaho:pentaho-ce-jar-parent-pom:pom:8.1-SNAPSHOT in eclipse-maven-repo (https://mvnrepository.com) and 'parent.relativePath' points at wrong local POM @ line 5, column 11
 @

Did you install the Pentaho settings.xml for maven?  in ~/.m2
https://github.com/pentaho/maven-parent-poms/tree/master/maven-support-files

Ok, thanks, this helped.


Tasks list as result for completionOfAllTasks api.

We had a nil  result from completionOfAllTasks for the all time. It will be very helpful to have tasks list in next "bolt".
We can found the same idea on the Facebook's Parse.Promise and PromiseKit as well.
P.S. New functionality test have been added and CLA have been signed.

@nlutsenko-fb can we close this PR now #76 was merged?

Agreed.
Closing as superseded by #76


Accessibility: Elements must only use allowed ARIA attributes

Describe the Bug
While scanning my application using the aXe DevTools Accessibility plugin, it made me aware of the following bug:

aria-label attribute cannot be used on a g with no valid role attribute.

This was triggered specifically because I made the edges non-focusable, which removed the "role="button" attribute.
At minimum, being able to specify a role would be useful (or allowing us to spread generic HTML properties onto an edge/node.). Setting a role by default when edgesFocusable={false} is set could also be useful.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
This can be reproduced on any ReactFlow example by setting edgesFocusabe={false} and running the aXe DevTools plugin.
Expected behavior
The error should not appear.
Screenshots or Videos

Platform

OS: macOS
Browser: Chrome v115.0.5790.114
Version<EMAIL_ADDRESS>
Additional context
No response

That's a good catch. Thanks! Would role="img" work in this case?

fixed in v11.8.0