Paginated Reports not showing correclty

Paginated Reports bookmark on "Filters" tab is  showing actual PBI Reports not the Paginated Reports.
Also, the same issue under "Display Names and IDs" tab.

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

ID: 3451b495-3af0-170e-a93c-d7360bf6b8cd
Version Independent ID: 5e964973-a536-b049-9eb9-5120be3f75e8
Content: Monitor Power BI Premium capacities in your organization - Power BI
Content Source: powerbi-docs/service-admin-premium-monitor-capacity.md
Service: powerbi
GitHub Login: @mgblythe
Microsoft Alias: mblythe

Hi @saiyash05 - so this is an issue you're seeing in the app (i.e. not the docs)?

@mgblythe : Yes, this is an issue I am seeing in the app.

Adding @swgupt to comment on this

Closing b/c this a product support issue. saiyash05 -- if you have any further issues with the app, please get support by going to https://support.powerbi.com.


Migrate to the latest FHIR SDK Artifacts

Describe the Issue
We need to (publish &) migrate to the latest code changes on the FHIR SDK for the following modules:

Engine
SDC
Knowledger

[x] Publish the artifacts

[x] Migrate FHIR Core

Batch Purging of resources

Loading workerContext using the Knowledge manager

Fix for incorrect ordering of members within Group resource

Temp sync upload workaround for main

Additionally fixes this issue : #582  - Clicking on Manual sync shows two toaster messages for Sync complete, immediately after clicking and after the sync completes


Update OpenAI script to cover all Cognitive Services accounts

This change updates the OpenAI specific script to update all Cognitive Services accounts to disable local auth.

I intentionally targeted OpenAI accounts as I only use this kind, but it makes to target all of them 😄


Scroll restoration doc: example not working as expected

Version
4.0.0
In the docs about scroll restoration, the part which explains how to scroll to top on a route change:
Use this component:
class ScrollToTop extends Component {
  componentDidUpdate(prevProps) {
    console.log(this.props); // no location prop
    if (this.props.location !== prevProps.location) {
      // never triggered
      window.scrollTo(0, 0);
    }
  }

  render() {
    return this.props.children;
  }
}

And incorporate it at the root of the Router like this (Router = BrowserRouter in my case):
const RenderRoutes = () => (
    <Router>
      <ScrollToTop>
        <Switch>
          <Route path="/app" render={props => <UserRoutes {...props} />} />
          <Route path="/admin" render={props => <AdminRoutes {...props} />} />
          <Route path="/" render={props => <PublicRoutes {...props} />} />
        </Switch>
      </ScrollToTop>
    </Router>
);

However this currently does not work, as the component <ScrollToTop /> does not have access to the location prop, and only has children when I log it. From my understanding, you get access to these router props only through <Route /> components, which would explain why this does not work, or am I missing something?

Are you exporting the component using withRouter? Like this: export default withRouter(ScrollToTop). If not, that may be the problem.

That was it, my bad! Didn't know that function existed.
Would it make sense if I made a tiny PR that adds one of these to make it even more friendly?:
At the top:
import { withRouter } from 'react-router'

Or add an extra line in the text:
"Make sure to export the component with withRouter to give it access to the router's props"

I'm not in position to answer that, but it seems like reasonable to me.

Hi, can I continue ask something about the window.scrollTo(0, 0) doesn't work.
Actually my project has desktop and mobile version, desktop works, but mobile doesn't work. The ScrollToTop component is on top of the both, I really don't know why it doesn't work on mobile.

Hey everybody!
I just created this to solve the scroll to top problem https://github.com/bluframe/react-router-scroll-top
Please please go super easy on me
This is my first ever open source component, and I hope I am following best practices but there are probably a lot of things I missed - I hope I did it right!
Suggestions, improvements, PRs all welcome!
It's just a shorthand for exactly what the official react-router documentation suggests, and I linked to the documentation on README.md
For me it's really useful on the projects I'm building - I don't have to create a ScrollToTop component every time
Is this useful for you guys as well?


RPC Redundancy/Failover Configuration

Is your feature request related to a problem? Please describe.
Current RPC providers can have downtime, temporary connectivity issues, or rate limits that make clients transactions fail. Over the past year we have observed several windows of RPC failure, which could have been mitigated if near-api-js had configurations for multiple RPC providers.
Describe the solution you'd like
Similar to issues #703 and #717, the core JSON RPC provider should be refactored to not only have retries, but allow for retries against multiple Providers. The default provider list can configure both near foundation and openshards RPC services. Provider list can be a single node string for backward compatibility OR an array of node strings.
Up for discussion but needed: Create a failover threshold of retries for each provider, and a threshold for provider failures before defaulting to a different priority.
Configuration Example:
RPC_MAINNET_PROVIDERS="https://rpc.mainnet.near.org,[https://mainnet-rpc.openshards.io](https://mainnet-rpc.openshards.io)"

RPC_GUILDNET_PROVIDERS="https://guildnet-rpc.openshards.io,[https://rpc.guildnet.near.org](https://rpc.guildnet.near.org)"

NOTE: Because near-api-js is used in many dapps and repos, this functionality is very key toward providing the easiest way to allow clients to decentralize their RPC access. This is critical for community attacks against public resources.
Describe alternatives you've considered
Users must create multiple instances of the Near module with different providers configured and detect TXN failures. Not idea at all.
Additional context
There is an ongoing effort to create a decentralized RPC for mainnet & guildnet using many of the openshards.io nodes with a redundant load-balancer.

I believe our strategy for the decentralization of RPC Servers is a bit different, but some of these ideas can be implemented. On near-api-js level we can provide support for multiple servers and fallback logic, but it will add an additional level of complexity and source of petensioal bugs.
@frol @MaximusHaximus , any thoughts?

Similar suggestion from @artob: https://github.com/near/near-api-js/issues/735

@volovyk-s What is on your mind in terms of a different strategy? I feel near-api-js is the right abstraction layer to deal with the pool of RPC servers to enable true decentralization.

@frol there are two separate problems. The first one is a stability of a single RPC Server. The second one is the ability to switch to another server when the first one is down (decentralization). As far as I know, our current strategy was to work on stability first (API Keys). For the second one, I agree, usage of multiple RPC Servers with fallbacks on a clientside is the best option. But we will need to design it carefully, simple fallback on each call can be slow. And we will need to support API Keys for each such server.  I will prioritize this issue.

@volovyk-s Ah, well, those are indeed two completely different efforts, but they came somewhat together, and we need both solutions: (1) extended RPC connection configuration, (2) failover configuration. This issue is about the second point.

@volovyk-s Ah, well, those are indeed two completely different efforts, but they came somewhat together, and we need both solutions: (1) extended RPC connection configuration, (2) failover configuration. This issue is about the second point.

(and @volovyk-s)
I apologize on the side discussion on decentralization here... It was just to mention the addition context and reasons.
The goal of this issue is to add support for multiple RPC configurations, allowing retries against a prioritized list of RPC nodes. This at least mitigates single RPC provider failures/outages.
The decentralization should be handled by a very different setup than SDK. :)

@frol @volovyk-s any movement on this? Another downtime/major latency issue on mainnet, with many apps unusable because of the dependency of a single RPC provider.

Seems like the ideal solution here will be the creation of FailoverJsonRpcProvider, which will make several simultaneous calls to all provided RPC URLs and return the result if, let's say, 50+% returns the same value. Or the first successful result if we want it to be snappy.
The problem here is the increased load on RPC Servers, something that we are trying to avoid.
Also, the code of near-api-js is heavily coupled and relies on JsonRpcProvider instead of Provider interface. Usage of the new Provider will lead to a ton of breaking changes.
@MaximusHaximus I think we should move the provider to a separate library in the future. People should be able to create their own implementations and use them in near-api-js-x.
In our case, we will need to refactor the existing JsonRpcProvider. And probably these calls and checks will be sequential. It will increase response time when the main RPC Server is down.

Enable configuring multiple RPC nodes also helps to resolve the feature request of switching RPC URLs in NEAR wallet: https://github.com/near/near-wallet-roadmap/issues/36, if wallet could set fallback RPC URLs by default.

@volovyk-s
I tried to add a new property node_urls. Tried polling different Connections and found that none of the Connection functions could return the status of the node. The status() function still request retry 12 times rather than return a wrong status.
Perhaps we can  exponentialDifferentConnectionsBackoff function instead of the exponentialBackoff function to achieve multiple nodes. Does not change the exponentialBackoff function name. Change the parameters passed and the implementation.

Another idea is. Before executing sendJsonRpc, we poll through the list of all rpc's. Find a connectable rpc and default it to be reliable. This avoids exponentialBackoff  to nodes that can never connect.

@frol @volovyk-s Yet another downtime/major latency issues on primarily on testnet, because of the dependency of a single RPC provider.

Dear Team,
We have a library named fallback-falooda which helps us get the reliable node in the list of nodes in our cosmos environment. We are also using it in our node selector in our near specific use cases.
I have made a few changes in the code to make it work with fallback falooda. here -
https://github.com/near/near-api-js/compare/master...leapsamvel:near-api-js:master
We can, either

Take the approach of using fallback falooda in the library or
Provide a getter method param and allow the user to provide the URL dynamic when the RPC call is made.

Could you let me know, and I will raise the PR accordingly with the test cases and documentation?
TIA.

Resolved by #1334


Example usage of "linear C_L model"

Description of Proposed Feature
An example of  how to call the linear C_L model in the neuralfoil.get_aero_ functions
Alternatives I Have Considered
Searched for it in the readme and aerosandbox neuralfoil examples but could not find it
Additional Context
In addition to its neural network models, NeuralFoil also has a bonus "Linear  model" that predicts lift coefficient
as a purely-affine function of angle of attack. This model is well-suited for linear lifting-line or blade-element-method analyses, where the  linearity can be used to solve the resulting system of equations "in one shot" as a linear solve, rather than a less-numerically-robust iterative nonlinear solve.

Hi @pareal !
This module is not directly accessible through the usual entry points (e.g., asb.Airfoil.get_aero_from_neuralfoil(), nf.get_aero_from_airfoil(), etc.).
However it is directly accessible here in the NeuralFoil source:
Link to repo
Currently, this goes unimported in the main NeuralFoil __init__.py, but you could import it as:
import aerosandbox as asb
from neuralfoil import CL_linear_regression as model

print(
    model.get_CL(
        airfoil=asb.Airfoil("naca0012"),
        alpha=3,
        Re=1e6,
    )
)

Thank you. I'll just put a simple comparison between neuralfoil and cl model, might be useful to someone
(works from jupyter notebook cell):
import aerosandbox as asb
import aerosandbox.numpy as np
import matplotlib.pyplot as plt
import aerosandbox.tools.pretty_plots as p
from neuralfoil import CL_linear_regression as model
airfoil = asb.Airfoil("n0012") #symmetrical airfoil
airfoil = asb.Airfoil("s1210") #cambered airfoil
alpha = np.linspace(-10, 10, 181)
Re=2e6
Ma=0.3
aero=airfoil.get_aero_from_neuralfoil(
alpha=alpha,
Re=Re,
mach=Ma,
model_size="xxxlarge",
)
cl_model= model.get_CL(
airfoil=airfoil,
alpha=alpha,
Re=Re,
)
fig, ax = plt.subplots()
ax.plot(alpha,aero["CL"])
ax.plot(alpha,cl_model)


Package request: fde-tools

Project description
powerful toolkit for FDE settings
Metadata

homepage URL: https://github.com/openSUSE/fde-tools
source URL: https://github.com/openSUSE/fde-tools
license: gpl2+ (?)
platforms: linux

Add a :+1: reaction to issues you find important.

Here is a start that build, noit sure what to do with it tho
{
  stdenv,
  fetchFromGitHub,
  libfido2,
  json_c,
  cryptsetup,
  gitMinimal
}:

stdenv.mkDerivation (finalAttrs: {
  name = "fde-tools";
  version = "0.7.2";

  src = fetchFromGitHub {
    owner = "openSUSE";
    repo = "fde-tools";
    rev = "refs/tags/${finalAttrs.version}";
    hash = "sha256-WPstx6f9fzBJIBg8CIpP3zl9tzCJ564A82PsPlUtdv8=";
  };

  postPatch = ''
    # man page generator dont work at all
    substituteInPlace Makefile \
      --replace-fail "SUBDIRS := man bash-completion" "SUBDIRS := bash-completion"
  '';

  makeFlags = [
    "DESTDIR=${placeholder "out"}"
  ];

  nativeBuildInputs = [
    libfido2
    json_c
    cryptsetup
    gitMinimal
  ];

  lib = {
    description = "Tools for controlling full disk encryption";
  };
})

sorry but how should i build this? im newbie


Organize theme files

Description
RFC
Proposed organization of theme files. Breaking up main theme file into more atomic pieces that include foundation styles and component styles, along with their variants.
To Test

This kind of touches every part of the app (ugh, sorry), so it will require looking around at all the pages
Everything should look mostly the same and nothing obviously broken

disabled edit button styling
Other than that, there are just smaller things that differ from val--buttons are a bit wider, x Close button in modals is positioned lower, card header text in this PR is bigger

+1
Also links remain in the unclicked styling on both this and dev so we are keeping functionality, but is that intentional?

disabled edit button styling
Other than that, there are just smaller things that differ from val--buttons are a bit wider, x Close button in modals is positioned lower, card header text in this PR is bigger

+1
Also links remain in the unclicked styling on both this and dev so we are keeping functionality, but is that intentional?

Garrett, I'm not sure I understand this question! Can you show me an example? It's possibly a regression, but I think I need an example to be sure.


Does MMDetection automatically create bounding boxes in an annotation file if they're missing?

I've recently migrated to instance segmentation, but want to recheck what the performance would be on an object detection dataset, does MMDetection have the functionality built in to construct the annotations in this format?

Hey, not sure if there is a default transform implemented, but you can easily add your own using
https://github.com/open-mmlab/mmdetection/blob/fe3f809a0a514189baf889aa358c498d51ee36cd/mmdet/structures/bbox/horizontal_boxes.py#L392
Which allow to create boxes from masks.


about the network

hello ,Great work! Will you open source the train code ?

I have a question during reading the paper. Did the R rings elements mean there is one network(encoder), and for each step, use the same network(encoder) compute(encode) R images, the use the R results compute Lsc.

The trick is in batching the data. yes the concept is similar like Siamese networks extended to rings. One can pass all the data through one encoder and slice the data according to their labels at the end of the encoder output to consider it for different rings and compute the loss.
Only the 100 shape related vectors are considered.

Releasing the training code is having some internal licensing issues due to its reliance in tensorflow flame which may take further time.


fix: fixed grpc++ linking problem

This change is

Dropping this. I'm going to fix a different way.


Local ./runall.sh - login not working for hsconfigure

Hi,
I am attempting to setup hsds locally, link it to an AWS S3 bucket I have created, and then use h5pyd to add content to my file and have it reflected in S3.
I have hsds running locally via $ ./runall.sh --no-docker and see the output of READY! use endpoint: http+unix://%2Ftmp%2Fhs%2Fsn_1.sock
(Note: I ran into some trouble doing this initial setup, while on master, so I switched to https://github.com/HDFGroup/hsds/commit/4d8418a8e9fc2369ceba91b545e4c6b4c78f9374 based on https://github.com/HDFGroup/hsds/issues/122, which enabled ./runall.sh --no-docker to succeed)
I am now following https://github.com/HDFGroup/hsds/blob/master/docs/post_install.md, and trying to run:
$ hsconfigure
$ hstouch -u admin -p admin /home/

However, hsconfigure (shown below) currently returns Unauthorized.
I have set some environment variables:
export BUCKET_NAME=XXXXX
export AWS_S3_GATEWAY=http://s3.amazonaws.com
export HSDS_ENDPOINT=http+unix://%2Ftmp%2Fhs%2Fsn_1.sock
export HS_USERNAME=admin
export HS_PASSWORD=admin

When I run $ hsconfigure, it fails at the end with Unauthorized (username/password or api key not valid)
$ hsconfigure
Enter new values or accept defaults in brackets with Enter.

Server endpoint [http+unix://%2Ftmp%2Fhs%2Fsn_1.sock]:
Username [admin]:
Password [admin]:
API Key [None]:
Testing connection...
Unauthorized (username/password or api key not valid)
Quit? (Y/N)

I have cp the basic admin/config/passwd.txt file, prior to running ./runall.sh --no-docker, and referenced https://github.com/HDFGroup/hsds/issues/53, but seems like a slightly different use case.
Any advice would be appreciated!  In addition, do you have any links/setup guides for running HSDS locally while connecting it to s3?
I have been referencing https://github.com/HDFGroup/hsds/blob/master/docs/docker_install_aws.md and piecing it together.
Appreciate all the documentation in general, thanks!

I suspect HSDS is not finding the password file.   When running in an Anaconda environment the server seems to pick up the password file using a relative path: "admin/config/passwd.txt".   But I guess you are not using conda, since you had problems prior to  switching to  the nodocker branch.
Try this - edit the runall.sh and change the line with export PASSWORD_FILE="admin/config/passwd.txt" to use an absolute path.  Let me know if that works.
Running locally while connecting to S3 should be no problem.  As long as you have AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_S3_GATEWAY set as environment variables, the server should use S3 rather than posix storage.

Hi @jreadey thanks for the quick reply.
Unfortunately, it's the same error.
I updated PASSWORD_FILE as well as CONFIG_DIR to be absolute paths.  I also updated runall.sh to print out the underlying hsds command that is being run (I'm including the whole console output for reference below):
./runall.sh --no-docker
--no_docker option specified - using directory: /tmp/hs for socket and log files
using password file: /Users/XXXX/YYYY/ZZZZ/hsds/admin/config/passwd.txt
AWS_S3_GATEWAY set, using AAAAA S3 Bucket (verify that this bucket exists)
no docker startup
Using S3 Gateway
COMMAND -----> hsds --bucket_name AAAAA --password_file /Users/XXXX/YYYY/ZZZZ/hsds/admin/config/passwd.txt --logfile hs.log  --socket_dir /tmp/hs --loglevel INFO --config_dir=/Users/XXXX/YYYY/ZZZZ/hsds/admin/config --count=4
set logging to: 20
INFO:root:using cmd_dir: /usr/local/bin
INFO:root:all processes ready!
INFO:root:Ready after: 0.00 s

READY! use endpoint: http+unix://%2Ftmp%2Fhs%2Fsn_1.sock

In the separate terminal, the hsconfigure is the same:
$ hsconfigure
Enter new values or accept defaults in brackets with Enter.

Server endpoint [http+unix://%2Ftmp%2Fhs%2Fsn_1.sock]:
Username [admin]:
Password [admin]:
API Key [None]:
Testing connection...
Unauthorized (username/password or api key not valid)
Quit? (Y/N)

Thanks

Ok - it was worth a try!
If you look at the server log file (/tmp/hs/hs.log), do you see a line like:
sn INFO> Loading password file:  /Users/XXXX/YYYY/ZZZZ/hsds/admin/config/passwd.txt
?

Yes I do
...
...
sn INFO> CORS add route: <ResourceRoute [PUT] <DynamicResource  /datasets/{id}/acls/{username}> -> <function PUT_ACL at 0x117220af0>
sn INFO> CORS add route: <ResourceRoute [GET] <DynamicResource  /datasets/{id}/acls> -> <function GET_ACLs at 0x117220a60>
sn INFO> Using metadata memory cache size of: 134217728
sn INFO> allow_noauth = True
sn INFO> initUserDB
sn INFO> Loading password file: /Users/XXXX/YYYY/ZZZZ/hsds/admin/config/passwd.txt
sn INFO> using password file: /Users/XXXX/YYYY/ZZZZ/hsds/admin/config/passwd.txt
sn INFO> added user: admin
sn INFO> added user: test_user1
sn INFO> added user: test_user2
sn INFO> user_db initialized: 3 users
sn INFO> initgroupDB
sn INFO> No groups file
sn INFO> group_db initialized: 0 groups
binding to socket: http+unix://%2Ftmp%2Fhs%2Fsn_1.sock
======== Running on http://unix:/tmp/hs/sn_1.sock: ========
(Press CTRL+C to quit)
dn1 INFO> s3sync nothing to update
dn2 INFO> s3sync nothing to update
dn3 INFO> s3sync nothing to update
dn4 INFO> s3sync nothing to update
dn1 INFO> s3syncCheck no objects to write, sleeping for 1
dn2 INFO> s3syncCheck no objects to write, sleeping for 1
dn3 INFO> s3syncCheck no objects to write, sleeping for 1
dn4 INFO> s3syncCheck no objects to write, sleeping for 1
dn1 INFO> s3sync nothing to update
dn2 INFO> s3sync nothing to update
...

Here is the contents of passwd.txt
# HSDS password file template
#
#
# This file contains a list of usernames/passwords that will be used to authenticate
# requests to HSDS.
# If using HTTP Basic Auth, copy file to "passwd.txt" in the same directory before deploying HSDS.
# Otherwise, if using Azure Active Directory or Kerberos, don't copy this file - usernames will be
# authenticated using those identity providers.
# For production use, replace the "test" password below with secret passwords and add
# and any new accounts desired.
admin:admin
test_user1:test
test_user2:test

What do you get when you run the following:
$ hsinfo -e http+unix://%2Ftmp%2Fhs%2Fsn_1.sock -u test_user1 -p test

?

$ hsinfo -e http+unix://%2Ftmp%2Fhs%2Fsn_1.sock -u test_user1 -p test
server name: Highly Scalable Data Service (HSDS)
server state: READY
endpoint: http+unix://%2Ftmp%2Fhs%2Fsn_1.sock
username: test_user1
password: ****
home: NO ACCESS
server version: 0.7.0beta
node count: 4
up: 11 min 11 sec
h5pyd version: 0.9.2

That's an improvement over unauthorized!  So looks like the password is getting loaded correctly.
Do you get the same result without the mod to runall.sh?
The NO ACCESS comes from the server looking for a folder  "/home/test_user1/" and not finding one.  You can set the folder up as described in steps 3 and 4 of https://github.com/HDFGroup/hsds/blob/master/docs/post_install.md.

Cool, same output for hsinfo after setting the paths back to relative in runall.sh! 👍

You can set the folder up as described in steps 3 and 4 of https://github.com/HDFGroup/hsds/blob/master/docs/post_install.md

Yeah the post_install was what led me to the issue with hsconfigure -- planning to complete those steps after resolving this.
Appreciate the help!

awesome - glad we got it sorted out!

@jreadey apologies for the confusion -- I still have the issue with hsconfigure
$ hsconfigure
Enter new values or accept defaults in brackets with Enter.

Server endpoint [http+unix://%2Ftmp%2Fhs%2Fsn_1.sock]:
Username [admin]:
Password [admin]:
API Key [None]:
Testing connection...
Unauthorized (username/password or api key not valid)
Quit? (Y/N)

Given that I have two terminals -- one running ./runall.sh --no-docker and the other testing hsconfigure, do I need to run anything additional in the second terminal to pick up any of the changes that we're making ./runall.sh --no-docker (I don't believe I have to, but thought I would confirm)?

No, the other terminal just needs to know the endpoint, username, and password.

Looks like hsconfigure was treating the input text "None" as a API_key rather than no api key.  I have a fix checked into the master branch of h5pyd if you want to try it out.

Changes are merged into master branch


*: refine flashback syntax by remove until timestamp statement.

What problem does this PR solve?
PR https://github.com/pingcap/parser/pull/611 add the flashback syntax. But it was hard to use with the until timestamp statement.
And currently, we can't support flashback to any timestamp, even in the GC safe time.
After think over and talk with PM, we decided to remove the until timestamp statement in the flashback syntax. Now the flashback syntax is like below:
FLASHBACK TABLE table_name [TO] [other_name]

What is changed and how it works?
Check List
Tests

Unit test

@AilinKid  Since this PR doesn't compatible, so it can't pass the integration test, it need merge with TiDB PR at the same time.

@AilinKid Since this PR doesn't compatible, so it can't pass the integration test, it need merge with TiDB PR at the same time.

Oh, got


Music Disabled.

When commanded to que music, it doesn't. It does though give the message on the profile saying "Music Disabled". How do i go about fixing this?

Music is disabled until further notice.
We don't have the resources to run it.

@SimonJKed if you host the bot yourself, you can run music commands.