Bottom Sheet component compatibility/custom native wrapper(long-term feature)

Hey @kirillzyusko !
I was exploring potential improvements for react-native-keyboard-controller and discovered that the package doesn't currently support the popular BottomSheet component(without any additional tricks).
Initially, I thought integrating with the BottomSheet package would be easier than it actually turned out to be. The library has its own pre-built component, BottomSheetInput, and offers additional options for modifying keyboard behavior.
The main challenge I faced was achieving a smooth transition for the BottomSheet between active and inactive keyboard states. Since the library manages the keyboard state based on the BottomSheet's react-native-reanimated state, it requires significant JavaScript boilerplate to make it work with react-native-keyboard-controller. I checked the input behavior to determine whether it was focused or not, and then simply adjusted the snapPoints state, which produced the desired effect.
On the other hand, after implementing a custom BottomSheet solution, I observed improved results:
https://github.com/kirillzyusko/react-native-keyboard-controller/assets/115457344/b8c8a974-35d9-44f6-8151-d03b5e63cc1a
Pasting quick implementation:
import React, { useCallback, useImperativeHandle } from "react";
import { Dimensions, StyleSheet } from "react-native";
import { Gesture, GestureDetector } from "react-native-gesture-handler";
import Animated, {
  Extrapolation,
  FadeIn,
  FadeOut,
  Layout,
  interpolate,
  runOnJS,
  useAnimatedStyle,
  useSharedValue,
  withSpring,
} from "react-native-reanimated";

import { Backdrop } from "./Backdrop";

import type { StyleProp, ViewStyle } from "react-native";

const { height: SCREEN_HEIGHT } = Dimensions.get("window");

type BottomSheetProps = {
  children?: React.ReactNode;
  maxHeight?: number;
  style?: StyleProp<ViewStyle>;
  onClose?: () => void;
};

export type BottomSheetRef = {
  open: () => void;
  isActive: () => boolean;
  close: () => void;
};

export const BottomSheet = React.forwardRef<BottomSheetRef, BottomSheetProps>(
  ({ children, style, maxHeight = SCREEN_HEIGHT, onClose }, ref) => {
    const translateY = useSharedValue(maxHeight);

    const MAX_TRANSLATE_Y = -maxHeight;

    const active = useSharedValue(false);

    const scrollTo = useCallback((destination: number) => {
      "worklet";
      active.value = destination !== maxHeight;

      translateY.value = withSpring(destination, {
        mass: 0.4,
      });
    }, []);

    const close = useCallback(() => {
      "worklet";
      return scrollTo(maxHeight);
    }, [maxHeight, scrollTo]);

    useImperativeHandle(
      ref,
      () => ({
        open: () => {
          "worklet";
          scrollTo(0);
        },
        close,
        isActive: () => {
          return active.value;
        },
      }),
      [close, scrollTo, active.value],
    );

    const context = useSharedValue({ y: 0 });

    const gesture = Gesture.Pan()
      .onStart(() => {
        context.value = { y: translateY.value };
      })
      .onUpdate((event) => {
        if (event.translationY > -50) {
          translateY.value = event.translationY + context.value.y;
        }
      })
      .onEnd((event) => {
        if (event.translationY > 100) {
          if (onClose) {
            runOnJS(onClose)();
          } else close();
        } else {
          scrollTo(context.value.y);
        }
      });

    const animatedContainerStyle = useAnimatedStyle(() => {
      const borderRadius = interpolate(
        translateY.value,
        [MAX_TRANSLATE_Y + 50, MAX_TRANSLATE_Y],
        [25, 5],
        Extrapolation.CLAMP,
      );

      return {
        borderRadius,
        transform: [{ translateY: translateY.value }],
      };
    });

    return (
      <>
        <Backdrop onTap={onClose ?? close} isActive={active} />
        <GestureDetector gesture={gesture}>
          <Animated.View
            style={[styles.bottomSheetContainer, animatedContainerStyle, style]}
          >
            <Animated.View layout={Layout} entering={FadeIn} exiting={FadeOut}>
              {children}
            </Animated.View>
          </Animated.View>
        </GestureDetector>
      </>
    );
  },
);

const styles = StyleSheet.create({
  bottomSheetContainer: {
    backgroundColor: "#FFF",
    width: "95%",
    position: "absolute",
    bottom: 30,
  }
});

import React from "react";
import { StyleSheet } from "react-native";
import Animated, {
  useAnimatedProps,
  useAnimatedStyle,
  withTiming,
} from "react-native-reanimated";

import type { ViewProps } from "react-native";
import type { AnimatedProps, SharedValue } from "react-native-reanimated";

type BackdropProps = {
  onTap: () => void;
  isActive: SharedValue<boolean>;
};

export const Backdrop: React.FC<BackdropProps> = React.memo(
  ({ isActive, onTap }) => {
    const animatedBackdropStyle = useAnimatedStyle(() => {
      return {
        opacity: withTiming(isActive.value ? 1 : 0),
      };
    }, []);

    const backdropProps = useAnimatedProps<AnimatedProps<ViewProps>>(() => {
      return {
        pointerEvents: isActive.value ? "auto" : "none",
      };
    }, []);

    return (
      <Animated.View
        onTouchStart={onTap}
        animatedProps={backdropProps}
        style={[
          {
            ...StyleSheet.absoluteFillObject,
            backgroundColor: "rgba(0,0,0,0.2)",
          },
          animatedBackdropStyle,
        ]}
      />
    );
  },
);

import React, { useCallback, useRef } from "react";
import { Button, StyleSheet, TextInput, View } from "react-native";
import {
  KeyboardAwareScrollView,
  KeyboardController,
} from "react-native-keyboard-controller";

import { BottomSheet } from "./BottomSheet";

import type { BottomSheetRef } from "./BottomSheet";

const styles = StyleSheet.create({
  container: {
    flex: 1,
    backgroundColor: "white",
    alignItems: "center",
    justifyContent: "center",
  },
  bottomSheetContainer: {
    backgroundColor: "#FFF",
    flex: 1,
    padding: 25,
  },
  input: {
    height: 50,
    width: "90%",
    borderWidth: 2,
    borderColor: "#3C3C3C",
    borderRadius: 8,
    alignSelf: "center",
    marginTop: 16,
  },
});

function BottomSheetScreen() {
  const ref = useRef<BottomSheetRef>(null);

  const close = useCallback(() => {
    ref.current?.close();

    KeyboardController.dismiss();
  }, []);

  const open = useCallback(() => {
    ref.current?.open();
  }, []);

  return (
    <View style={styles.container}>
      <Button title="Open BottomSheet" onPress={open} />

      <BottomSheet
        ref={ref}
        style={styles.bottomSheetContainer}
        onClose={close}
      >
        <KeyboardAwareScrollView showsVerticalScrollIndicator={false}>
          {new Array(5).fill(0).map((_, i) => (
            <TextInput
              key={i}
              placeholder={`TextInput#${i}`}
              keyboardType={i % 2 === 0 ? "numeric" : "default"}
              style={styles.input}
            />
          ))}
        </KeyboardAwareScrollView>
      </BottomSheet>
    </View>
  );
}

export default BottomSheetScreen;

Finally, it seems to me that the idea of creation own native iOS/Android Bottomsheet wrapper might be a more suitable solution in this scenario, rather than attempting to modify the behavior of an existing JavaScript library.
However, it seems that this approach is not the primary goal of the current library. Perhaps creating a new package would be a better course of action.
I would value your input on this issue, as deciding on this feature involves extensive consideration of its pros and cons. I've shared all the considerations and ideas that have been on my mind for the past three weeks 🙂

Thank you @VladyslavMartynov10 and sorry for late response 😅
I think the integration is problematic because bottom-sheet is using own pre-defined keyboard movement interpolations, right? What happens if you disable keyboard handling from BottomSheet? Would it be possible then just to translate a bottom sheet by translateY using useReanimatedKeyboardAnimation, for example?
I think replication of BottomSheet is a pretty complex stuff and definetly I wouldn't like to have such components inside this library 😅 3rd party package sounds more reasonable for me 👍
But in ideal case both libraries should work together well, so first of all I'd like to understand which problems did you have trying to integrate bottom sheet and this library? Would you mind to describe it as precisely as possible?

Hey! No worries, I'm almost available at any time.
I agree that replicating a bottom-sheet is a challenging task, especially if we aim for a native implementation.
My interest in exploring potential integration originates from my personal experiments. It's important to note that currently, all third-party libraries are using React Native implementation, and we lack a native implementation alternative. Additionally, I've been particularly impressed with the NativeSheet implementation for iOS. This implementation excels, offering excellent functionality with minimal boilerplate required, especially when using the SwiftUI framework.
In my situation, I attempted to integrate a KeyboardToolBar component (which I presented to you for KeyboardToolbar feature) with gorhom/bottomsheet to achieve smooth transitions between focused inputs. From this starting point, I'm considering three options:

Disable the react-native-keyboard-controller module and use a pre-built component from gorhom/bottomsheet. This was my initial solution, but it presents some issues due to unsynchronized keyboard height.

Implement my own solution using react-native-reanimated, which is straightforward but doesn't address all potential scenarios. While it's a great option for experimentation, it requires a significant amount of code.

Utilize the react-native-keyboard-controller module to monitor the focus/unfocus state of inputs and adjust the translateY of BottomSheet accordingly.

Overall, I believe we should develop a practical example for others who might encounter this issue in the future. Also, thank you for the suggested idea. I need to review it further, as it seems to me that a custom interpolation approach should work.
Perhaps in the near future, we might be able to develop something akin to a native solution, although I'm aware that this would require considerable effort and thorough investigation.

@VladyslavMartynov10 I followed a guide that I wrote in https://github.com/kirillzyusko/react-native-keyboard-controller/pull/445 and it looks like it works pretty well:
https://github.com/kirillzyusko/react-native-keyboard-controller/assets/22820318/e929c103-6c44-4cec-b1e2-484fc8f770e2
Can I close this issue and merge this PR?

@VladyslavMartynov10 the issue got automatically closed because I merged PR. If you think that the issue is still present - let me know and I'll be happy to re-open this issue 😊


[BUG] Thingiverse connection broken

Describe the bug
After making the connection to thingiverse, I can see my likes and designs in the thingiverse area. However, this list is not updating as I am making any updates on the thingiverse website, no matter how often I refresh or sign out and sign in again from Depot. The only way to re-populate that list with additional objects is to revoke app access from Depot through the thingiverse website and re-establishing the connection from scratch. Furthermore, downloads are not working, but stuck at 0% indefinitely.
To Reproduce
Steps to reproduce the behavior:

Go to 'Thingiverse'
Click on anything
Try to download
See error

Expected behavior
Update the list of items automatically or at least when hitting "Refresh" in the thingiverse options screen.
Screenshots

Mac (please complete the following information):

OS: [Monterey]
Version [12.0.1]

Additional context

Thanks for the bug report and screenshot!  I'll take a look at this and see what's going on, and ask for further input possibly too.

I'm having difficulty reproducing this.. any way you can run the app and then get logs from Console.app ?  If that is too tricky, let me know and perhaps I can put some details together.

	Hi Eric, unfortunately I am now travelling and will not return to my desk until New Year‘s - will get onto it as soon as I am back! Sorry for the delay and enjoy the holidays!

Von: Eric Anderson @.***>Gesendet: Samstag, Dezember 18, 2021 1:57 PMAn: getdepot/depotCc: langerdennis; AuthorBetreff: Re: [getdepot/depot] [BUG] Thingiverse connection broken (Issue #15)
I'm having difficulty reproducing this.. any way you can run the app and then get logs from Console.app ?  If that is too tricky, let me know and perhaps I can put some details together.
—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

No worries, have a great holiday!  Thanks!

Hi,
I have now opened Depot, started to capture logs, hit the "Refresh" button in the thingiverse section of preferences and captured the output of processes "Depot" and "runningboard" - let me know if you are looking for other logs. I only find "200" responses on the Depot tasks...
thingiverse.log
I have made another observation though. When I signed out of Thingiverse from within Depot and tried to log in again, I am getting the screenshotted error message. Once I remove the connection to the Depot app in my thingiverse account, I can create a new initial connection from Depot and my "likes" and "designs" are populated properly. Therefore the initial connection seems to always work correctly, but additional refreshes don't. It has worked once though - a design I have liked yesterday appeared in Depot sometime today. Could it be that it just takes time to refresh and only forced sync is not working? If so, at what interval should I expect new likes on thingiverse to appear in the Depot app?

Thanks for the log and extra effort!
I believe this is a Thingiverse issue, unfortunately.  They appear to have a limit on the number of users that can use an app (that uses their API) until they approve it, which has been in the approval status for many months.  This is not documented anywhere, so this was unknown to me until these errors started popping up.
I have tried to contact Thingiverse several times, with ZERO response.  I have also tried Twitter, and contacting the parent company.  Please file a bug with them to help bring this to the top of their queue, otherwise I am not sure how to resolve it without violating their terms.

Thank you for following up! The answer makes sense, too bad thingiverse is working that way. I appreciate your effort though and cross my fingers the app will get approved at some point. I will just periodically re-establish the connection then as a workaround. I will close the bug and consider raising the issue at thingiverse!

Just as a quick update: Seems to be working now, no idea if the app was approved or some other magic happened... but seeing my likes populated very fast now!


Build fails with CONFIG_SHELL_VT100_COMMANDS=n

Zephyr apps do not build with CONFIG_SHELL_VT100_COMMANDS=n.
To Reproduce
Steps to reproduce the behavior:

echo CONFIG_SHELL_VT100_COMMANDS=n >> samples/subsys/shell/fs/prj.conf
west build -b nrf52840dk_nrf52840 samples/subsys/shell/fs
See error:

zephyr/subsys/shell/shell_cmds.c:446:26: error: 'cmd_clear' undeclared here (not in a function); did you mean 'cmd_select'?
        SHELL_HELP_CLEAR, cmd_clear, 1, 0);

Expected behavior
It should build.
Impact
Annoyance. In our case we can filter the vt100 codes elsewhere.
Environment (please complete the following information):

OS: Debian bullseye
Toolchain: arm-none-eabi- cross-compiler
Commit 963d05bd525766701cbce44d0aaa63f57e26ae9b

I will fix it shortly. Thank you for finding


Adopt a modern build/packaging toolchain

Once we pick the frontend framework we're going to use, we'll need to put together a toolchain that works for us.  Schalk and I are already moving in the direction of using jest and prettier, but if we adopt React, we'll need to add Babel to the mix. And we'll probably want a packager like webpack or parcel.
We could stay small and use this new toolchain just for pages of the website that use the new frontend framework. Or we could go big and try to convert all of Kuma to use it. John probably already has issues filed about moving us off of Django pipeline, so there may be some overlap there.
User story
As a Kuma developer I need a modern toolchain to accompany my frontend framework to handle transpilation and asset packaging.
Acceptance critera

[ ] tools selected
[ ] selection decisions are documented and communicated
[ ] prototype code using the toolchain exists (probably not deployed, though)

Looks like there is a consensus on Webpack, and implementation will be next sprint. Please update the estimate and confidence as needed.

It appears to me that a runner like gulp , npm scripts, or a Makefile is still needed with Webpack. Is a runner still needed? If so, is there a consensus on the runner?

We won't need anything more than npm scripts. You can see an example of these here:
https://github.com/schalkneethling/mdn-feature-banner-component/blob/master/package.json#L7

I do not believe there is a lot for me to do on this, this coming sprint. I am therefore time boxing it to 1 point. Let me know if I am missing something.

This one seems like it could have been completed this sprint, but it's unclear if the acceptance criteria are met:

Tools selected - What tool selections remain?
Selection decisions are documented and communicated - Is this issue enough, or is there another channel to update?
Prototype code using the toolchain exists: We're shipping webpack, Babel, and Jest, but there may be additional tool selections.

Tools selected

I reckon this is essentially Webpack?

Selection decisions are documented and communicated - Is this issue enough, or is there another channel to update?

We did not discuss this but perhaps we need to open an ADR based on this issue and have that go through the process?

Prototype code using the toolchain exists: We're shipping webpack, Babel, and Jest, but there may be additional tool selections.

I reckon this is what we will be using for the foreseeable future.

We discussed this on other issues and in meetings. My summary is that the tool selection is an implementation detail of the other decisions (React, Flow, Emotion), and don't necessarily rise to the level of an ADR. I think this issue can be enough for now.


Add flags to leaderboard API responses

Would it be possible to add player's flag icon strings to the leaderboard responses?
https://server4.beyondallreason.info/teiserver/api/public/leaderboard/Team

Yes, this should be both very possible and very easy.

@L-e-x-o-n might be interested

What should be the response when the player's flag is not known for whichever reason? Should the country key not be present at all or should it have some default value?

The response to no known flag is typically ??


Eliminate duplication of actions in execution of ci workflow

https://blog.fleetdm.com/4-tips-for-github-actions-usability-2-debugging-4c0c920adfde


AMD Support

Support for AMD GPUs on Akash Network. There may not be any significant work necessary but first step is to test with an AMD GPU(s). This is very important because AMD is working on the MI 250 chipset which is expected to be a serious contender to Nvidia A100 and H100 chips. Here is a blog from MosaicML benchmarking and comparing its performance with Nvidia's chips: https://www.mosaicml.com/blog/amd-mi250
It seems like the initial work is validating whether the kubernetes device plugin for AMD can work for us (the way the Nvidia one has) https://github.com/RadeonOpenCompute/k8s-device-plugin#deployment
Is this something that a community person can help with?

Updates:

provider 0.4.9-rc0 doesn't seem to register the AMD MI 210; despite MI 210 working in a K8s Pod. Details https://github.com/ovrclk/engineering/issues/810#issuecomment-1864190645

provider version 0.4.9-rc0 (both provider & client): AMD GPU MI210 deployment works!
provider: issue with the aggregated GPU count when mixed GPU Vendors (e.g. NVIDIA & AMD) are present on the same worker node (kubectl describe node <node-name> should only report 'nvidia.com/gpuORamd.com/gpuK8s node attribute, otherwise it will only and always see a single GPU or no GPU / Limbo [flapping between0/1 gpu count]; and you cannot easily remove K8s node attributes such as 'nvidia.com/gpu, amd.com/gpu  as they get stuck in etcd [K8s DB] - the only way is to reinstantiate the node.)

Next steps:

[ ] akash-provider: address the akash-provider issue with the wrong GPU count when mixed GPU Vendors on a node are present;
[ ] security/helm-chart: see whether we can deploy that amd-gpu-helm/amd-gpu helm-chart in its own namespace instead of kube-system for better security;
[ ] security/helm-chart: make sure one cannot request more AMD GPU than he should.. refs. HIP_VISIBLE_DEVICES
/ ROCR_VISIBLE_DEVICES (similarly to how it was possible with NVIDIA GPU via NVIDIA_VISIBLE_DEVICES=all env variable, which was addressed here )
[ ] docs: document AMD GPU Akash Provider enablement (preliminary test version of the doc Docs: How to enable AMD GPU support in Akash Provider is in the private repo atm)

[x] security/helm-chart: see whether we can deploy that amd-gpu-helm/amd-gpu helm-chart in its own namespace instead of kube-system for better security;

This is possible - requires --create-namespace --namespace amd-device-plugin --set namespace=amd-device-plugin flags to be specified as follows:
helm install --create-namespace --namespace amd-device-plugin --set namespace=amd-device-plugin my-amd-gpu amd-gpu-helm/amd-gpu --version 0.10.0

Verification:
root@node1:~# helm install --create-namespace --namespace amd-device-plugin --set namespace=amd-device-plugin my-amd-gpu amd-gpu-helm/amd-gpu --version 0.10.0
NAME: my-amd-gpu
LAST DEPLOYED: Mon Jan  8 12:38:25 2024
NAMESPACE: amd-device-plugin
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
amd-gpu-device-plugin-daemonset deployed in namespace 'amd-device-plugin'

pushed the doc https://github.com/akash-network/docs/pull/299
now available at https://docs.akash.network/other-resources/experimental/amd-gpu-support
I'll go through it once more once I get the access to the AMD GPU box.


Missing reporting currency in documentation

When you look at the scrap of fixed assets documentation, you elegantly avoid the issue with reporting currency, which is now a huge issue in fixed assets. ALL features that remove the fixed asset, split, scrap, sale etc. need to not only zero out the accounting currency, but also the reporting currency. Please include in your documentation the reporting currency for the balances of fixed assets.

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

ID: 2f6b6e90-0b9c-6c07-fdd5-35ade43a3b3c
Version Independent ID: 7f24d65a-2304-c9a2-96c1-1e1bc93a0f1e
Content: Dispose of a fixed asset as scrap - Finance | Dynamics 365
Content Source: articles/finance/fixed-assets/dispose-of-a-fixed-asset-as-scrap.md
Service: dynamics-365-finance
Product: ****
Technology: ****
GitHub Login: @moaamer
Microsoft Alias: moaamer

@IngaJensen, thank you for your feedback. This feedback has been passed onto the product group for consideration.


Bug: YAML Key Sort does not remove blank lines

Describe the Bug
When YAML Key Sort is active, and blank lines are present in the YAML, they are sorted to the end, not deleted as the documentation states.
How to Reproduce
Steps to reproduce the behavior:

Create some YAML frontmatter
Put blank lines in among the YAML lines
Lint
Sorting takes place according to your preferences, but the blank lines remain

Expected Behavior
Blank lines removed
Device

[ ] Desktop
[x] Mobile

Thanks for letting me know. I need to update the documentation to say it may remove empty lines. I believe it did so consistently at one point, but with the change to get things working on iOS and the fact hat we have rules to handle empty lines in the frontmatter leads me to the decision to just update the wording.


Sorry about the second PR, forgot to update the README

You really didn't have to do that, thanks so much! Saved me a very minor headache

You really didn't have to do that, thanks so much! Saved me a very minor headache

It's fine lol
MD is fun for me lol


Observers being called repeatedly when multiple property changes at the sametime.

observers: [ 'valueChanged(startDate,endDate)' ],

this.startDate = moment(start).format(DATE_FORMAT)
this.endDate = moment(end).format(DATE_FORMAT)
// then valueChanged will be called twice.

Is this is a bug ?
Any solution to resolve this problem ?

I get a solution by myself. see polymer-ext
Add a extension option asyncObservers to Polymer.

Hi @yutingzhao1991, this is the expected behaviour.
You are observing two attributes. Every time you do an assignation, it produces a change in the DOM element. So one of your attributes is changing and the handler is triggered.
You can avoid null values just adding some conditions to your code.
if (startDate !== undefined && endDate !== undefined) {
    // do stuff
}

Or you can use async and debounce function in your observer trying to condense your calls.
valueChanged: function(startDate, endDate) {
    this.async(this.debounce(this._valueChanged));
}

@adelarosab Thanks. I Got it. But in my practice it is a frequently-used situation. Is it has any possibility to add a official api to Polymer?

@yutingzhao1991 I'm not part of the Google Team. But I guess with MutationObserver as background, they'll keep the behaviour as simple as they can.
In fact, there is no way to assign/set several attributes in a DOM element at the same time.
I was thinking, and it could be a chance for you. You can use an async object.
properties: {
    [...]
    async: {
        observer: 'valueChanged'
        type: Object,
        value: {
            endDate: 'whatelse', // nesspreso
            startDate: 'whatever'
        }
    }
}

this.async = _.extend(this.async, {
    startDate: 'newDate',
    endDate: 'anotherDate'
});

I think with this example, you could group your attributes and make some meaningful observers.

@adelarosab is correct, the observer will be called for each argument. You can use debounce to wait for both values to update like in this JSBin: http://jsbin.com/kocegi/edit?html,console,output
I'm closing this issue, but feel free to open one about enhancing observers with your async use case.


Error compiling info example

In its current version, it does not compile due to:
info.f90:(.text+0x19e): undefined reference to `c_f_string_ptr_'

Thank you for reporting the issue, has been fixed.


Fix unittest and document

We should fix the unittest and document of alab management

I started on this on another branch actually, I will complete the test issues next week. Documentation will take some more time


[Builtins] Introduce 'RuntimeScheme'

This one introduces RuntimeScheme which is akin to TypeScheme except it doesn't
contain a bunch of irrelevant types stuff that we don't need during evaluation.
  RuntimeScheme doesn't look massively different from TypeScheme to an ignorant observer like me.


bibtex plugin ouput type support update

To continue the discussion https://github.com/larsgw/citation.js/issues/210, since proceedings-article is not a valid CSL-JSON type I would prefer if the fix was in https://github.com/citation-js/citation-js/blob/v0.5/packages/core/src/plugins/input/csl.js (a function to fix broken CSL-JSON that is used before all output including BibTeX). I can do this if you want, or provide instructions if you want to make the pull request.

To continue the discussion https://github.com/larsgw/citation.js/issues/210, since proceedings-article is not a valid CSL-JSON type I would prefer if the fix was in https://github.com/citation-js/citation-js/blob/v0.5/packages/core/src/plugins/input/csl.js (a function to fix broken CSL-JSON that is used before all output including BibTeX). I can do this if you want, or provide instructions if you want to make the pull request.

Normally, https://github.com/citation-js/citation-js/blob/v0.5/packages/plugin-doi/src/json.js and https://github.com/citation-js/citation-js/blob/v0.5/packages/plugin-doi/src/type.js fixes broken CSL-JSON such as the one you have, but those fixes are only applied if the input is a DOI. It would be better to move those fixes to the parseCsl function mentioned above as that also affects RIS and other output formats, and not just BibTeX.

Normally, https://github.com/citation-js/citation-js/blob/v0.5/packages/plugin-doi/src/json.js and https://github.com/citation-js/citation-js/blob/v0.5/packages/plugin-doi/src/type.js fixes broken CSL-JSON such as the one you have, but those fixes are only applied if the input is a DOI. It would be better to move those fixes to the parseCsl function mentioned above as that also affects RIS and other output formats, and not just BibTeX.

yes please go ahead and implement the fix.
This pull request is just a suggestion. I'd leave this to the experts.  :)

yes please go ahead and implement the fix.
This pull request is just a suggestion. I'd leave this to the experts.  :)


Configure Sentry integrations

Sentry recommended these integrations, based on our installed packages. They also recommended SQLAlchemy (https://docs.sentry.io/platforms/python/sqlalchemy/) -- I guess it's used by CCI? I wasn't sure if we wanted that, or also whether we want the ASGI integration (https://docs.sentry.io/platforms/python/asgi/)?

We don't want the SQLAlchemy integration, as we're not using SQLA anywhere.
The ASGI integration looks useful.

@wlonk Are you willing to add in the ASGI integration?

@jgerigmeyer yup.

@jgerigmeyer I'd love to merge or reject this; I don't know how to test it beyond the hand testing I did that looked OK, though. Do you have thoughts on how to validate that this is working as it should?

@wlonk I'm okay merging this. From the docs it still sounds like we should have another settings file with a sentry.init() call in it specifically for the worker process, but I'm not 100% clear on how that all works.

Generally, make sure that the call to init is loaded on worker startup, and not only in the module where your jobs are defined. Otherwise, the initialization happens too late and events might end up not being reported.

https://docs.sentry.io/platforms/python/rq/


Reinstate jacoco support in build.gradle after downgrade to JDK 8

Forgot to put jacoco code back into build.gradle.

Restored the jacoco entries in build.gradle.


Update writing of hdf5 data

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 88.195%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

atomisticparsers/gromacs/parser.py
0
4
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
6216

Relevant Lines:
7048

💛  - Coveralls


Add support for batched inference of images of same size

Allow user to pass in a list of np arrays to enhance method like this:
from basicsr.archs.rrdbnet_arch import RRDBNet
from realesrgan import RealESRGANer
from realesrgan.archs.srvgg_arch import SRVGGNetCompact

model = SRVGGNetCompact(num_in_ch=3, num_out_ch=3, num_feat=64, num_conv=32, upscale=4, act_type='prelu')  # https://github.com/xinntao/Real-ESRGAN/releases/download/v<IP_ADDRESS>/realesr-general-x4v3.pth
netscale = 4

upsampler = RealESRGANer(
    scale=netscale,
    model_path='realesr-general-x4v3.pth',
    model=model,
    half=True)

from PIL import Image
import numpy as np
img = Image.open('img1.jpg')
img2 = Image.open('img2.jpg')
img = np.asarray(img)
img2 = np.asarray(img2)
assert img.shape == img2.shape
scale = 4
output, _ = upsampler.enhance([img, img], outscale=scale)
print(output)

Note due to constraints of the model and its padding usage, only images of same height and width (shape) is supported. You can resize it to same before hand.
This can come useful in fast video inference where all frames are of same size.
Fixes https://github.com/xinntao/Real-ESRGAN/issues/634

I tried this batch inference, but after testing, it turned out to be slower than inferencing a single image. Is there something wrong? @aliencaocao

It could be cpu bound because the implementation is essentially a lot of for loops for np arrays. It is surely not as optimized as it could be.
This is more for the case where you have a very large batch size like 100+, then the time taken to launch GPU kernels will override the extra overhead by the for loops


Error: undefined method `undent' for #String:0x00007fd723263430

/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/json/common.rb:156:in parse' /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/json/common.rb:156:in parse'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/locker.rb:88:in brew_list_info' /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/locker.rb:42:in block in lock'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/locker.rb:34:in each' /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/locker.rb:34:in lock'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/installer.rb:56:in install' /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/commands/install.rb:10:in run'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/cmd/bundle.rb:78:in bundle' /usr/local/Homebrew/Library/Homebrew/brew.rb:110:in '

Remove undent from your `Brewfile.


Replace Peekable in PowerDistributor with Receivers

What's needed?
The PowerDistributor is the only place in the SDK where Peekables are used.  Peekable is a confusing interface and should be avoided.
Proposed solution
No response
Use cases
No response
Alternatives and workarounds
No response
Additional context
No response

Done here: https://github.com/frequenz-floss/frequenz-sdk-python/pull/800


Should suppor to add an icon in the SnackBarAction

Now only support a String .
why not use a widget?

Hm, I wonder why we require that the action be a SnackbarAction.


hashed password in the password-file

Hi!
Maybe I missed something in the docs, but is there an option not to use the plain-text file with the password for the repo that is passed with the -p key, but to have password's MD5 hash or else to have more secure scripts?

The  --password-command switch can help you here:
--password-command string: specify a shell command to obtain a password ( default: $RESTIC_PASSWORD_COMMAND)

Sure, thanks, I didn't though of that option! Case closed.

Awesome.. @osscombat , can you close the issue?

For the record: you could also do that with shell magic:
$ restic --password-file <(gpg --decrypt ~/restic-password.gpg) [...]

But --password-command also works :)


sendToken precision

The sendToken function only accepts 3 decimals.
Hive Engine tokens can have a precision of up to 8, though.

We'll fix this in the next update, good point!
@cedricguillas ^


Set next distribution date to be consistent for the viewer

App timezone set to Brisbane, which should fix this for all current users.


Publish docs on Microsoft Docs

Adds a new docfx.json at the src/docs level. This is where OPS is expecting to find docfx.json.
Removes the layout: page metadata from every .md file
Adds a global metadata key for layout: page in the docfx.json file located at the src level.

This is presumably the docfx.json file being used for the github.io site.

Merging this PR should -- and I want to emphasize should -- result in these same docs being hosted at both the github.io site (exactly as they are today) AND Microsoft Docs (staging site, not live site) at the following URL: https://review.docs.microsoft.com/en-us/dotnet/orleans/?branch=master
Please note that all these metadata warnings will need to be resolved before publishing to the live site.
preview link

Docs Build status updates of commit f035dcc:
:warning: Validation status: warnings

File
Status
Preview URL
Details

src/docs/benefits.md
:warning:Warning
View
Details

src/docs/deployment/azure_web_apps_with_azure_cloud_services.md
:warning:Warning
View
Details

src/docs/deployment/consul_deployment.md
:warning:Warning
View
Details

src/docs/deployment/docker_deployment.md
:warning:Warning
View
Details

src/docs/deployment/handling_failures.md
:warning:Warning
View
Details

src/docs/deployment/index.md
:warning:Warning
View
Details

src/docs/deployment/kubernetes.md
:warning:Warning
View
Details

src/docs/deployment/multi-cluster_support/GlobalSingleInstance.md
:warning:Warning
View
Details

src/docs/deployment/multi-cluster_support/GossipChannels.md
:warning:Warning
View
Details

src/docs/deployment/multi-cluster_support/MultiClusterConfiguration.md
:warning:Warning
View
Details

src/docs/deployment/multi-cluster_support/Overview.md
:warning:Warning
View
Details

src/docs/deployment/multi-cluster_support/SiloConfiguration.md
:warning:Warning
View
Details

src/docs/deployment/service_fabric.md
:warning:Warning
View
Details

src/docs/deployment/troubleshooting_azure_cloud_services_deployments.md
:warning:Warning
View
Details

src/docs/deployment/troubleshooting_deployments.md
:warning:Warning
View
Details

src/docs/grains/cancellation_tokens.md
:warning:Warning
View
Details

src/docs/grains/code_generation.md
:warning:Warning
View
Details

src/docs/grains/event_sourcing/event_sourcing_configuration.md
:warning:Warning
View
Details

src/docs/grains/event_sourcing/immediate_vs_delayed_confirmation.md
:warning:Warning
View
Details

src/docs/grains/event_sourcing/index.md
:warning:Warning
View
Details

src/docs/grains/event_sourcing/journaledgrain_basics.md
:warning:Warning
View
Details

src/docs/grains/event_sourcing/journaledgrain_diagnostics.md
:warning:Warning
View
Details

src/docs/grains/event_sourcing/log_consistency_providers.md
:warning:Warning
View
Details

src/docs/grains/event_sourcing/replicated_instances.md
:warning:Warning
View
Details

src/docs/grains/external_tasks_and_grains.md
:warning:Warning
View
Details

src/docs/grains/grain_identity.md
:warning:Warning
View
Details

src/docs/grains/grain_lifecycle.md
:warning:Warning
View
Details

src/docs/grains/grain_persistence/azure_storage.md
:warning:Warning
View
Details

src/docs/grains/grain_persistence/dynamodb_storage.md
:warning:Warning
View
Details

src/docs/grains/grain_persistence/index.md
:warning:Warning
View
Details

src/docs/grains/grain_persistence/relational_storage.md
:warning:Warning
View
Details

src/docs/grains/grain_placement.md
:warning:Warning
View
Details

src/docs/grains/grainservices.md
:warning:Warning
View
Details

src/docs/grains/index.md
:warning:Warning
View
Details

src/docs/grains/interceptors.md
:warning:Warning
View
Details

src/docs/grains/observers.md
:warning:Warning
View
Details

src/docs/grains/reentrancy.md
:warning:Warning
View
Details

src/docs/grains/request_context.md
:warning:Warning
View
Details

src/docs/grains/stateless_worker_grains.md
:warning:Warning
View
Details

src/docs/grains/timers_and_reminders.md
:warning:Warning
View
Details

src/docs/grains/transactions.md
:warning:Warning
View
Details

src/docs/host/client.md
:warning:Warning
View
Details

src/docs/host/configuration_guide/activation_garbage_collection.md
:warning:Warning
View
Details

src/docs/host/configuration_guide/client_configuration.md
:warning:Warning
View
Details

src/docs/host/configuration_guide/configuring_.NET_garbage_collection.md
:warning:Warning
View
Details

src/docs/host/configuration_guide/configuring_ADO.NET_providers.md
:warning:Warning
View
Details

src/docs/host/configuration_guide/index.md
:warning:Warning
View
Details

src/docs/host/configuration_guide/list_of_options_classes.md
:warning:Warning
View
Details

src/docs/host/configuration_guide/local_development_configuration.md
:warning:Warning
View
Details

src/docs/host/configuration_guide/serialization.md
:warning:Warning
View
Details

This comment lists only the first 50 files in the pull request.

src/docs/benefits.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/azure_web_apps_with_azure_cloud_services.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 7, Column 70: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-gb/services/app-service/web/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 9, Column 117: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-gb/services/virtual-network/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/consul_deployment.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 16, Column 7: [Warning-file-not-found] Invalid file link: '~/docs/implementation/cluster_management.md'.
Line 19, Column 140: [Warning-file-not-found] Invalid file link: '~/docs/implementation/cluster_management.md'.
Line 111, Column 109: [Warning-file-not-found] Invalid file link: '~/docs/implementation/cluster_management.md'.
Line 154, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 162, Column 123: [Warning-file-not-found] Invalid file link: '~/docs/implementation/cluster_management.md'.
Line 173, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/docker_deployment.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 80, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Implementing your Orleans Application') are not allowed. You can only have one top-level heading.
Line 86, Column 1: [Warning-alt-text-missing] Missing alternate text for image 'docker-orleans-solution.png'. Alt text is required for accessibility.
Line 311, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Dockerfile') are not allowed. You can only have one top-level heading.
Line 345, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'docker-compose') are not allowed. You can only have one top-level heading.
Line 396, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Put everything together') are not allowed. You can only have one top-level heading.
Line 507, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Docker Swarm') are not allowed. You can only have one top-level heading.
Line 515, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Google Kubernetes (K8s)') are not allowed. You can only have one top-level heading.
Line 519, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 '[Bonus topic] Debugging Orleans inside Containers') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/handling_failures.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 43, Column 51: [Warning-hard-coded-locale] Link 'https://msdn.microsoft.com/en-us/library/jj591569.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 58, Column 18: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/architecture/patterns/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 58, Column 18: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/azure/architecture/patterns/' will be broken in isolated environments. Replace with a relative link.

src/docs/deployment/index.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 78, Column 37: [Warning-file-not-found] Invalid file link: '~/docs/host/configuration_guide/index.md'.
Line 78, Column 127: [Warning-file-not-found] Invalid file link: '~/docs/implementation/cluster_management.md'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/kubernetes.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 20, Column 202: [Warning-file-not-found] Invalid file link: '~/docs/host/configuration_guide/server_configuration.md'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/multi-cluster_support/GlobalSingleInstance.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/multi-cluster_support/GossipChannels.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/multi-cluster_support/MultiClusterConfiguration.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/multi-cluster_support/Overview.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 29, Column 1: [Suggestion-sensitive-language-ma] Term 'master branch' is sensitive and should not be used in content or code. Usage: 'rs, and/or when it is written to storage frequently. Support for log-view grains is not part of the master branch yet. We have a prerelease including samples and a bit of documentation in the [geo-orleans branch]('

src/docs/deployment/multi-cluster_support/SiloConfiguration.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/service_fabric.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/troubleshooting_azure_cloud_services_deployments.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 8: [Warning-duplicate-titles] Title 'Troubleshooting Deployments' is duplicated in: 'deployment/troubleshooting_azure_cloud_services_deployments.md(2,8), deployment/troubleshooting_deployments.md(2,8)'. Titles must be unique within a docset.
Line 5, Column 1: [Warning-duplicate-h1s] H1 'Troubleshooting Deployments' is duplicated with other articles: 'deployment/troubleshooting_azure_cloud_services_deployments.md(5,1), deployment/troubleshooting_deployments.md(5,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/deployment/troubleshooting_deployments.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 8: [Warning-duplicate-titles] Title 'Troubleshooting Deployments' is duplicated in: 'deployment/troubleshooting_azure_cloud_services_deployments.md(2,8), deployment/troubleshooting_deployments.md(2,8)'. Titles must be unique within a docset.
Line 5, Column 1: [Warning-duplicate-h1s] H1 'Troubleshooting Deployments' is duplicated with other articles: 'deployment/troubleshooting_azure_cloud_services_deployments.md(5,1), deployment/troubleshooting_deployments.md(5,1)'. First level headings must be unique within a docset.
Line 76, Column 49: [Warning-file-not-found] Invalid file link: '~/docs/host/configuration_guide/index.md'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/cancellation_tokens.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/code_generation.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 38, Column 13: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.iloggerfactory' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 38, Column 13: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.iloggerfactory' will be broken in isolated environments. Replace with a relative link.

src/docs/grains/event_sourcing/event_sourcing_configuration.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/event_sourcing/immediate_vs_delayed_confirmation.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 25, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Delayed Confirmation') are not allowed. You can only have one top-level heading.
Line 48, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Concurrency Guarantees') are not allowed. You can only have one top-level heading.
Line 58, Column 61: [Warning-file-not-found] Invalid file link: '~/docs/grains/external_tasks_and_grains.md'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/event_sourcing/index.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/event_sourcing/journaledgrain_basics.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/event_sourcing/journaledgrain_diagnostics.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/event_sourcing/log_consistency_providers.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/event_sourcing/replicated_instances.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/external_tasks_and_grains.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 7, Column 173: [Warning-hard-coded-locale] Link 'https://msdn.microsoft.com/en-us/library/dd997402(v=vs.110).aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 412: [Warning-insecure-link] Link 'http://blogs.msdn.com/b/pfxteam/archive/2011/10/24/10229468.aspx' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 99, Column 182: [Warning-hard-coded-locale] Link 'https://msdn.microsoft.com/en-us/magazine/jj991977.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/grain_identity.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/grain_lifecycle.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 49: [Warning-file-not-found] Invalid file link: '~/docs/implementation/orleans_lifecycle.md'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/grain_persistence/azure_storage.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 17, Column 207: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/common/storage-scalability-targets#azure-table-storage-scale-targets' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 17, Column 207: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/azure/storage/common/storage-scalability-targets#azure-table-storage-scale-targets' will be broken in isolated environments. Replace with a relative link.

src/docs/grains/grain_persistence/dynamodb_storage.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/grain_persistence/index.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 1: [Warning-file-not-found] Invalid file link: '~/images/grain_state_1.png'.
Line 146, Column 213: [Warning-bookmark-not-found] Cannot find bookmark '#using-grainlttstategt-to-add-storage-to-a-grain' in 'grains/grain_persistence/index.md', did you mean '#using-graintstate-to-add-storage-to-a-grain'?
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/grain_persistence/relational_storage.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 59: [Warning-file-not-found] Invalid file link: '~/docs/host/configuration_guide/index.md'.
Line 13, Column 115: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/obtaining-a-dbproviderfactory' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 159: [Warning-file-not-found] Invalid file link: '~/docs/host/configuration_guide/adonet_configuration.md'.
Line 31, Column 10: [Warning-file-not-found] Invalid file link: '~/docs/host/configuration_guide/adonet_configuration.md'.
Line 46, Column 18: [Warning-file-not-found] Invalid file link: '~/docs/host/configuration_guide/adonet_configuration.md'.
Line 136, Column 154: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/ado-net-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 150, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/sql/relational-databases/polybase/get-started-with-polybase' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 150, Column 109: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/native-compilation-of-tables-and-stored-procedures' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 157, Column 124: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/sql/relational-databases/partitions/partitioned-tables-and-indexes' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 167, Column 90: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/sql/relational-databases/data-tier-applications/data-tier-applications' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 218, Column 27: [Warning-file-not-found] Invalid file link: '~/docs/host/configuration_guide/adonet_configuration.md'.
Line 223, Column 92: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/memory-optimized-tables' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 226, Column 75: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/sql/relational-databases/linked-servers/linked-servers-database-engine' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 228, Column 119: [Warning-hard-coded-locale] Link 'https://msdn.microsoft.com/en-us/library/jj851212.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 13, Column 115: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/obtaining-a-dbproviderfactory' will be broken in isolated environments. Replace with a relative link.
Line 136, Column 154: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/ado-net-overview' will be broken in isolated environments. Replace with a relative link.
Line 150, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/sql/relational-databases/polybase/get-started-with-polybase' will be broken in isolated environments. Replace with a relative link.
Line 150, Column 109: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/native-compilation-of-tables-and-stored-procedures' will be broken in isolated environments. Replace with a relative link.
Line 157, Column 124: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/sql/relational-databases/partitions/partitioned-tables-and-indexes' will be broken in isolated environments. Replace with a relative link.
Line 167, Column 90: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/sql/relational-databases/data-tier-applications/data-tier-applications' will be broken in isolated environments. Replace with a relative link.
Line 223, Column 92: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/memory-optimized-tables' will be broken in isolated environments. Replace with a relative link.
Line 226, Column 75: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/sql/relational-databases/linked-servers/linked-servers-database-engine' will be broken in isolated environments. Replace with a relative link.

src/docs/grains/grain_placement.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/grainservices.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/index.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 11, Column 41: [Warning-file-not-found] Invalid file link: '~/docs/tutorials_and_samples/tutorial_1.md'.
Line 11, Column 126: [Warning-file-not-found] Invalid file link: '~/docs/tutorials_and_samples/tutorial_1.md'.
Line 14, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Grain Interfaces and Classes') are not allowed. You can only have one top-level heading.
Line 68, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Returning Values from Grain Methods') are not allowed. You can only have one top-level heading.
Line 167, Column 43: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/csharp/async' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 167, Column 43: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/dotnet/csharp/async' will be broken in isolated environments. Replace with a relative link.

src/docs/grains/interceptors.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 22, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Incoming Call Filters') are not allowed. You can only have one top-level heading.
Line 215, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Outgoing Call Filters') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/observers.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 116, Column 68: [Warning-hard-coded-locale] Link 'https://msdn.microsoft.com/en-us/library/system.weakreference' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/reentrancy.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/request_context.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/stateless_worker_grains.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/timers_and_reminders.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Timers') are not allowed. You can only have one top-level heading.
Line 40, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Reminders') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/grains/transactions.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/host/client.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 21, Column 19: [Warning-file-not-found] Invalid file link: '~/docs/grains/stateless_worker_grains.md'.
Line 37, Column 22: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 37, Column 163: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 37, Column 332: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/actions' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 37, Column 427: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.hosting.ihostedservice' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51, Column 1: [Warning-alt-text-missing] Missing alternate text for image '~/images/frontend_cluster.png'. Alt text is required for accessibility.
Line 51, Column 1: [Warning-file-not-found] Invalid file link: '~/images/frontend_cluster.png'.
Line 99, Column 65: [Warning-file-not-found] Invalid file link: '~/docs/grains/index.md'.
Line 100, Column 100: [Warning-file-not-found] Invalid file link: '~/docs/grains/index.md'.
Line 110, Column 76: [Warning-file-not-found] Invalid file link: '~/docs/grains/index.md'.
Line 122, Column 1: [Warning-file-not-found] Invalid file link: '~/docs/grains/observers.md'.
Line 126, Column 87: [Warning-file-not-found] Invalid file link: '~/docs/streaming/index.md'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 37, Column 22: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 163: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 332: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/actions' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 427: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.hosting.ihostedservice' will be broken in isolated environments. Replace with a relative link.

src/docs/host/configuration_guide/activation_garbage_collection.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/host/configuration_guide/client_configuration.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 1: [Warning-h1-not-first] Markdown content is not allowed before H1 'Client Configuration'.
Line 11, Column 53: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 11, Column 53: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options' will be broken in isolated environments. Replace with a relative link.

src/docs/host/configuration_guide/configuring_.NET_garbage_collection.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/host/configuration_guide/configuring_ADO.NET_providers.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/host/configuration_guide/index.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 14, Column 38: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 21: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 14, Column 38: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options/' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 21: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options/' will be broken in isolated environments. Replace with a relative link.

src/docs/host/configuration_guide/list_of_options_classes.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/host/configuration_guide/local_development_configuration.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

src/docs/host/configuration_guide/serialization.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 18, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Generated Serializers') are not allowed. You can only have one top-level heading.
Line 30, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Serialization Providers') are not allowed. You can only have one top-level heading.
Line 66, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Writing Custom Serializers') are not allowed. You can only have one top-level heading.
Line 325, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Fallback Serialization') are not allowed. You can only have one top-level heading.
Line 329, Column 71: [Warning-hard-coded-locale] Link 'https://msdn.microsoft.com/en-us/library/system.runtime.serialization.formatters.binary.binaryformatter' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 354, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Exception Serialization') are not allowed. You can only have one top-level heading.
Line 356, Column 200: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/standard/serialization/custom-serialization' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 394, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Optimize Copying Using Immutable Types') are not allowed. You can only have one top-level heading.
Line 463, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Serialization Best Practices') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 356, Column 200: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/dotnet/standard/serialization/custom-serialization' will be broken in isolated environments. Replace with a relative link.

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@CamSoper so, do we need to just "try it out" and if it blows up the live site, revert again? If so, i want @ReubenBond to sign off, and then let's set a window of time for when we do it, test it, and revert/leave it together. I don't even mind a big block of time where we hackathon this thing.

We can build and test this locally by running dotnet build in the root or launching docfx build <path-to-docfx.json>
I'll try it now

We can build and test this locally by running dotnet build in the root or launching docfx build <path-to-docfx.json>

Well color me surprised.

Quite broken

Correct, that's my expectation. The higher level one (src) should be used to build the Github.io site. The one in src\docs is what's used for OPS.


Add Dark Mode theme toggle

It will be great if we can add a toggle to switch between dark and light mode in the template.
I am thinking of something along the line of this image, maybe around the top right corner.

That's sounds kinda challenging, but I would love to try this. Let me know if anybody wants to collaborate on this

@dtemir I would also like to try it out. Wanna collaborate?

Closed by #30


model defaults deep copy for array params

if model defaults have array or [] params, then new Model() for array will be error data.
example:
var Defaulted = Backbone.Model.extend({
  defaults: {
      array: []
  }
});
model = new Defaulted();
assert.equal(model.get('array').length, 0);
model.get('array').push("obj1");
model = new Defaulted();
assert.equal(model.get('array').length, 0);

last equal will fail, array.length is 1.

This is how prototypes in javascript work. Please do a search through the issues for some background.

Thanks so much, I will learn it. but how can i use array for model prototypes?

Turn defaults into a method, returning your defaults object.
On Thu, Apr 7, 2016, 21:13 luki2678511<EMAIL_ADDRESS>wrote:

Thanks so much, I will learn it. but how can i use array for model
prototypes?
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/jashkenas/backbone/pull/4009#issuecomment-207159290

--
Adam K (mobile)


[DO NOT MERGE UNTIL CHANGED TO MASTER] Add CircleCI to Master!

*Note: This version of circle.yml only works on the circleci branch for reviewing purposes.
Added circle.yml which tests all non AppEngine tests.
It tests for Ruby versions 2.3.1 and 2.2.5.
Last Run with CircleCI
https://circleci.com/gh/GoogleCloudPlatform/ruby-docs-samples/110

@remi please review this when you get a chance.

👍  LGTM
Feel free to update to master

Done!


Unintentional Consequences of TailwindMerge?

Version
@nuxt/ui: 2.8.0
nuxt: v3.7.1
Summary
With the latest version of nuxt ui, it seems to prioritise the base version of the UI over custom UI added to the component  - for example, on UCard, I've got a bunch of customisations but one example that was pretty obvious was body: { padding: 'px-0' } (doesn't seem to apply for me, favours the base style of "padding": "px-4 py-5 sm:p-6")
If this was the point of the update then feel free to close the ticket, but I think this might just be unintentional
Steps to reproduce
Add custom styling to the ui prop on UCard, for example padding on the body, watch results
What is Expected?
Custom styling on the component ui prop to be applied (and favoured over the base styles)
What is actually happening?
Custom styling is not applied unless an important flag is added e.g. body: { padding: '!px-0' }

This was indeed a breaking change of the https://github.com/nuxt/ui/releases/tag/v2.8.0 release, you can read more about this change in #509.
As we now use tailwind-merge, the classes are merged intelligently so you'd have to overwrite with sm:px-0 for example.
There is also an ongoing discussion about this change in #628 to apply the same logic in app.config.ts and introduce an option to disable this behaviour.

The only problem I can see with this is that there are a couple of instances that we just want to remove all classes from something in just one place e.g. there's one UCard where I want to set the ui to include something like ring: ''. But for all other cards I want to keep the original styling.
Tailwind-merge is pretty useful in a lot of places, but without globally turning off this feature, is there a better way to accomplish the desired results?

Using :ui="{ ring: '' }" should remove the ring from the UCard even with tailwind-merge.

Awesome, in that case I'll close this issue in favour of the potential configuration change ticket that you linked. Thanks.


Strider Production URL returns no results and an error.

Posted the query using url = 'https://strider.renci.org/1.1/query':
{
    "message": {
        "query_graph": {
            "nodes": {
                "n0": {
                    "categories": [
                        "biolink:ChemicalSubstance"
                    ],
                    "name": "Chemical Substance",
                    "ids": [
                        "CHEBI:24996"
                    ]
                },
                "n1": {
                    "categories": [
                        "biolink:ChemicalSubstance"
                    ],
                    "name": "Chemical Substance"
                }
            },
            "edges": {
                "e0": {
                    "subject": "n0",
                    "object": "n1"
                }
            }
        }
    },
    "log_level": "DEBUG"
}

The query returns no results.

And an error:

NB: The staging URL does return results.

@cbizon should I consider this complete as Production URL is stable now?

Yes, if the production strider is returning results

Confirmed. This returns with results in production.


Create pluggable authentication support

I want to use https://metacpan.org/release/Mojolicious-Plugin-Web-Auth to do oauth and oauth2 authentication.
@marcusramberg wants to use https://metacpan.org/release/Mojolicious-Plugin-OAuth2.
The reason I want to use Web::Auth is that it supports both oauth and oauth2. What do you think @marcusramberg?
I also want to make this an optional module.

I want to add support @jberger's https://metacpan.org/pod/Mojo::JWT module instead. I can be very nice for inviting people to chat, instead of using the invite code that is implemented today.

:+1: to that!  Mojo::JWT is super cool!
I can totally see it being perfect for invite codes, but how do you see it as an alternative to OAuth2?  My understanding is that you use OAuth2 to allow another, bigger, provider such as GitHub and Facebook to handle authentication.  It keeps the responsibility of passwords off of your system (yes?) and it centralizes credentials for users.  In this scenario, I just sign in to Convos with my Github account.  Easy!
With JWT...  what do you envision happening?

Closing this issue for now since the plugin is created. What need to be done later is to have the possibility to customise which elements that should be visible on the login/register page.
@s1037989: It's not really an alternative. I just don't fancy Oauth2 too much to bother to implement it. At least not for now.
Going to revisit it later, when I see how invitation links with JWT can mak the onboarding much smoother.

@jhthorsen any chance the situation regarding login via OpenID Connect / Oauth2 can be revisited?

I have a hard time seeing how that would work. Let's say if I you add support for Facebook, how would you limit who could register?

Maybe that would be the point? Open registration :)
But actually there are a lot of selfhosted services that offer OIDC server/provider functionality, such as Nextcloud and Gitea. Thus one could manage the users through those systems and allow people to also log into Convos that way.

@poVoq: Could you open a new issue with the description of how you picture this to work? I don't want to reopen this issue, since it has gotten very messy 😞