Carousel with two or less items glitchy

Description
When you have two or less carousel-items, sliding looks glitchy.
It looks like there's no item on the right side of the active carousel-item. This causes it to look very glitchy as soon as the active class switches to the next or previous carousel-item.
Repro Steps
I've created a codepen http://codepen.io/anon/pen/oZeXLr with two items (and uncommented third item).
Slide to the left a bit and you'll notice the missing item, enable the third uncommented item and it works as expected.
Screenshots / Codepen
When sliding to the left you can see there's no item on the right side of the current item.

Duplicate of https://github.com/Dogfalo/materialize/issues/4679


API Gateway assigned same role as Lambda

Issue
When the developer is providing a specific role and setting manage roles to false, Zappa takes the role provided in the role name argument and assigns it to both the Lambda and the Api Gateway.  This is problematic.

ApiGateway now has access to everything your application code does, when it only needs access to invoke your lambda.  It's unclear if these elevated privileges could be used to malicious ends.

The role now needs a trust relationship that allows Api Gateway to assume the role.  If this trust relationship doesn't exist, zappa deploy appears to work, but your actual lambda never gets executed.

The documentation doesn't make clear that the role will be used for both Api Gateway and the Lambda function.

Errors as experienced by the user:
The user sees an "internal server error" message when trying to access the api.  Zappa tail fails, because since the lambda never gets invoked, their is no log to tail.
When attempting to test the ApiGateway through the web console, the following error is found:
in the gui for api-gateway when I run a test:
Execution log for request test-request
Thu Nov 17 14:40:49 UTC 2016 : Starting execution for request: test-invoke-request
Thu Nov 17 14:40:49 UTC 2016 : HTTP Method: GET, Resource Path: /portal/
Thu Nov 17 14:40:49 UTC 2016 : Method request path: {proxy=portal/}
Thu Nov 17 14:40:49 UTC 2016 : Method request query string: {}
Thu Nov 17 14:40:49 UTC 2016 : Method request headers: {}
Thu Nov 17 14:40:49 UTC 2016 : Method request body before transformations: null
Thu Nov 17 14:40:49 UTC 2016 : Execution failed due to configuration error: API Gateway does not have permission to assume the provided role
Thu Nov 17 14:40:49 UTC 2016 : Method completed with status: 500
Suggested Change

Update the documentation to indicate the same role is used for both
Provide a separate setting for the ApiGateway role to use
Check the role on deploy and warn if ApiGateway and Lambda aren't explicitly allowed to assume into the role.  Otherwise you get what looks like a successful deployment with a failing application.

Thanks for raising this, this is an excellent issue. Permissions/Roles/Policies overall need a thorough overview, on the whole, we've operated in the fashion of being permissive out of the box for developers and individuals, but providing the ability to bring your own policies if operating in a corporate/controlled environment.
Your suggestions look good to me, did you come up with what the best ApiGateway specific role to use looks like?

Yes, I was able to work with Amazon to track that down.  Basically I need a Role with a attached policy like AWSLambdaRole:
{
    "Version": "2012-10-17",
    "Statement": [{
        "Effect": "Allow",
        "Action": [
            "lambda:InvokeFunction"
        ],
        "Resource": ["*"]
    }]
}

As you can see, this role allows the ApiGateway to invoke any lambda.  Optimally, this would only allow ApiGateway to execute the Zappa Lambda.
The second pice is that the role needs to have a trust relationship with ApiGateway such that ApiGateway can assume into the role
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
        "Service": "apigateway.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

I installed the Role as described and then used boto to switch the role that ApiGateway runs as (since its not editable in the Web Console) and everything is working pretty well.

For anyone who also has this problem, the following Python will switch your credentials. The syntax was a little unexpected.  Create your new role first, as described above, and then run the following in a python session.
import boto3
client = boto3.client('apigateway')
client.update_integration(
    restApiId=api_id,
    resourceId=resource_id,
    httpMethod='ANY',
    patchOperations=[
        {'op':'replace',
         'from': oldRoleArn,
         'value': newRoleArn,
         'path': '/credentials'}]
)

i am facing this issue of internal server error after successful Zappa deployment of a simple flask application. I am using a role_name for lambda function creation in zappa settings.  Could you please help me with this issue?

@milan322 What do you get when you test the application through the web console?

@atif1996  hey sorry for the delayed reply. I made it work. I just needed to change the policy settings.
as "Principal": {
"Service": "apigateway.amazonaws.com"
},
"Action": "sts:AssumeRole"
Thanks for the response.

I think I can help managing roles. I am thinking we need to separate deployment from execution altogether. I think Terraform will be a better fit for deploying over Cloudformation. We have a mess with pip packages that are not even related to execution uploading into Lambda, like trophosphere (used to generation of cloud formation templates).
I think I can help with this but will need some support to understand how it currently works.


cursor.push Causes Erroneous Triggering of cursor.select(i) Update Event

Why does the following situation occur?
var Baobab = require('baobab'),
    tree = new Baobab({array: [0]});

var arrayCursor = tree.select('array'),
    arrayIndex0Cursor = arrayCursor.select(0);

arrayIndex0Cursor.on('update', function(e) {
    if (e.data.data === e.data.previousData) {
        console.log('The data at tree.array[0] did not change, so why is this event firing?');
    }
});

arrayCursor.push(1);

If I wanted to know the array had been mutated, I would have used arrayCursor.on('update', ...).

Hello @mjhasbach. Are you working with v1 or v2? I shall investigate the issue. It might comes from a wrong handle over falsey values.

The issue occurs with both 1.1.2 and 2.0.0-dev13.

Ok, I've found the problem. That's because I assume that the push operation applies to the array as a whole rather than its last index. This makes the cursors on the array's elements fire also. Need to fix this.

It would also be cool to be able to create a cursor that maintains its reference to an array element after its position in the array changes. That would clean up my code in several different places. If you agree, I can open a separate ticket if you want.
Current:
var Baobab = require('baobab'),
    tree = new Baobab({array: ['bacon']}),
    arrayCursor = tree.select('array'),
    baconCursor = arrayCursor.select(0);

console.log(baconCursor.get()); // bacon

arrayCursor.unshift('eggs');

tree.commit();

console.log(baconCursor.get()); // eggs

Desired:
var Baobab = require('baobab'),
    tree = new Baobab({array: ['bacon']}),
    arrayCursor = tree.select('array'),
    baconCursor = arrayCursor.select(0);

console.log(baconCursor.get()); // bacon

arrayCursor.unshift('eggs');

tree.commit();

console.log(baconCursor.get()); // bacon

Actually, you can already do something of the kind by using a function or a descriptor object in the cursor's path:
// For instance
var Baobab = require('baobab'),
    tree = new Baobab({array: ['bacon']}),
    arrayCursor = tree.select('array'),
    baconCursor = arrayCursor.select(function(e) { return e === 'bacon'; });

Whoops, I overlooked that feature when reading the documentation. Thanks for the tip!

No problem @mjhasbach. Hope it will simplify some operations for you :-).

The push operation should now not trigger the update of sibling cursors within an array.


Fix a typo from architect to architecture in README.md

Why are the changes needed?
Fixes a typo in README.md from architect to architecture. This is a simple typo fix.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Simple typo fix, and I checked it manually via the web browser.

Thanks @HyukjinKwon, merged to master.

Thank you @pan3793!


refactor Refactor TableStatsMeta

Proposed changes

Add a abstraction for column stats status which is required so furthur optimization and feature development
Enable analyze test in p0 that disabled unexpectedly before

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


GitOps for SEA deployment

Describe the issue
We wish to automate some of the SEA deployment automation
Which Sprint Goal is this issue related to?

Note: 'Milestone' is a ZenHub term that we use synonymously with 'Sprint'.

The 'Milestone' description (created in ZenHub) should clearly list Sprint Goals. This section should indicate which 'goal' this issue is related to.
Additional context

getting config.json in the right form is a manual exercise

Definition of done

Aim to be idempotent
Have it run the destroy step first (prompt for destroy/confirm please!)

Not relevant anymore


Add contribution & vuln reporting guidelines

Clippy errors seem to be false-positive — when I remove references as suggested, it doesn't compile anymore


multiple Visium sections in one adata object does not work with sc.pl.spatial(img_key=None)

Does scanpy==1.5.1 support multiple sections in one adata object? If I concatenate several anndata object I can't plot even with sc.pl.spatial(img_key=None).
Try concatenating 3 mouse brain adata object and plotting:
adata = adata1.concatenate([obj2, obj3], index_unique=None)
sc.pl.spatial(adata[adata.obs["sample"]==adata.obs["sample"].unique()[0], :],
              color=["Rorb", "Vip"], img_key=None,
              vmin=0, cmap='magma',
              gene_symbols='SYMBOL')

This is the error I get:
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
<ipython-input-9-8c84185773ec> in <module>
      6               color=["Rorb", "Vip"], img_key=None,
      7               vmin=0, cmap='magma', #vmax=3.8,
----> 8               gene_symbols='SYMBOL'
      9              )

/nfs/team283/vk7/software/miniconda3farm5/envs/cellpymc/lib/python3.7/site-packages/scanpy/plotting/_tools/scatterplots.py in spatial(adata, img_key, library_id, crop_coord, alpha_img, bw, size, **kwargs)
    765     """
    766     if library_id is _empty:
--> 767         library_id = next((i for i in adata.uns['spatial'].keys()))
    768     else:
    769         if library_id not in adata.uns['spatial'].keys():

KeyError: 'spatial'

Versions:
scanpy==1.5.1 anndata==0.7.1 umap==0.3.10 numpy==1.17.3 scipy==1.4.1 pandas==0.25.3 scikit-learn==0.22.1 statsmodels==0.10.2 python-igraph==0.7.1 louvain==0.6.1 leidenalg==0.7.0

Much of the spatial data is stored in uns, which does not get combined by default.
There is an example of concatenating visium datasets in the tutorial and more information on concatenating .uns in the latest anndata docs.

Nice, thanks for pointing me to that tutorial! Still would be good if plotting worked without uns.

I get an error trying to merge multiples slides using the code in the tutorial. Is it possible to install the scanpy version the tutorial is using?
adata = adata.concatenate(
    list(slides.values()),
    batch_key="sample",
    uns_merge="unique",
    batch_categories=list(sample_data['sample_name'].values),
    index_unique=None
)

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-4-fe8a54a66c17> in <module>
     40     uns_merge="unique",
     41     batch_categories=list(sample_data['sample_name'].values),
---> 42     index_unique=None
     43 )
     44

TypeError: concatenate() got an unexpected keyword argument 'uns_merge'

I think you'll want to update your version of anndata for that.

Nice, anndata==0.7.3 works. Thanks!

No problem!


volatility: 2.6 -> 2.6.1

Motivation for this change
Bump volatility 2.6 to 2.6.1. Main reason for this: more win10 profiles.
We now need to fetch from GitHub because 2.6.1 is not published on downloads.volatilityfoundation.org.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

cc @bosu

Result of nixpkgs-review pr 100776 run on x86_64-linux 1

1 package built:

volatility

Result of nixpkgs-review pr 100776 run on x86_64-darwin 1

1 package built:

volatility

Result of nixpkgs-review pr 100776 run on x86_64-darwin 1

1 package built:

volatility

Result of nixpkgs-review pr 100776 run on x86_64-linux 1

1 package built:

volatility


why did:web is called permission and did:ion as permissionless?

Can you provide more details about your question?
I know the terms "permissioned" and "permissionless" in the context of blockchains, i.e. can anyone run a node on a blockchain, or do you have to get "approved" to run a node. But probably these terms are applied in other contexts as well.

who give the approval to run a node ?
what approval mean here?

In this url they have mentioned as permissioned and permissionless
https://learn.microsoft.com/en-us/azure/active-directory/verifiable-credentials/decentralized-identifier-overview

@Muthurajj can we close this? I think this is a question about the DID method itself, rather than about this specific implementation here. Maybe the following repo is a better place for this issue: https://github.com/w3c-ccg/did-method-web


⚠ Bofrost.lu has degraded performance

In 83be2fd, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2359 ms

Resolved: Bofrost.lu performance has improved in caa0851 after 6 minutes.


something seems wrong

Challenge http://www.freecodecamp.com/challenges/waypoint-manipulate-arrays-with-unshift has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

the ourArray example is incorrect
the last paragraph of the instructions should say 'start' and not 'end'  shift/unshift vs pop/push

my code should pass...?

The ouArray example unshifts and array into an array. The aim of a challenge is to unshift the string Paul into myArray as the description says. Hope this calrifies but please check these kinds of issues in help or the main chat before making them into github issues. Thanks for reporting this!

You're shifting an array that contains the string "Paul". You should be shifting JUST the string "Paul"


Plugin warning starting SDK configured with exporter-collector-grpc

What version of OpenTelemetry are you using?
0.16.0
What version of Node are you using?
v12.20.1
Please provide the code you used to setup the OpenTelemetry SDK
const { NodeSDK } = require('@opentelemetry/sdk-node');
const { CollectorTraceExporter } = require('@opentelemetry/exporter-collector-grpc');

const sdk = new NodeSDK({
    traceExporter: new CollectorTraceExporter(),
});
sdk.start().then(() => {
    console.log('SDK configured');
});

What did you do?
Ran the snippet above
What did you expect to see?
Expected the SDK to be setup with no issues.  stdout should read
SDK configured

What did you see instead?
There was a warning from the plugin loader in stdout
Some modules (grpc) were already required when their respective plugin was loaded, some plugins might not work. Make sure the SDK is setup before you require in other modules.
SDK configured

Additional context
I'm not sure how big a problem this is but think it should be possible to configure GRPC without warnings.  Exporting traces via GRPC all seems to work as expected.
If I configure the HTTP exporter instead (i.e. const { CollectorTraceExporter } = require('@opentelemetry/exporter-collector) or disable the GRPC plugin (as below), there's no such warning.
    plugins: {
        grpc: { enabled: false, path: '@opentelemetry/plugin-grpc' },
    },

The core of the issue here is that the grpc exporter depends on grpc. If the dependency is loaded before the instrumentation then the instrumentation can fail. One option would be to use the newer @opentelemetry/instrumentation-grpc instead which would allow you to enable the instrumentation before the SDK.
Otherwise you may need to use the sdk components directly rather than using the NodeSDK package so you can control the load order.
const { NodeTracerProvider } = require('@opentelemetry/node');
const { GrpcInstrumentation } = require('@opentelemetry/instrumentation-grpc');

const provider = new NodeTracerProvider({
  // be sure to disable old plugin
  plugins: {
    grpc: { enabled: false, path: '@opentelemetry/plugin-groc' }
  },
});

const grpcInstrumentation = new GrpcInstrumentation({
  // see https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-instrumentation-grpc/README.md for available configuration
});
grpcInstrumentation.enable();

provider.addSpanProcessor(new SimpleSpanProcessor(new ConsoleSpanExporter()));
provider.register();

Oops forgot to provide the NodeSDK example. Try this:
const { GrpcInstrumentation } = require('@opentelemetry/instrumentation-grpc');

const grpcInstrumentation = new GrpcInstrumentation({
  // see https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-instrumentation-grpc/README.md for available configuration
});
grpcInstrumentation.enable();

const { NodeSDK } = require('@opentelemetry/sdk-node');
const { CollectorTraceExporter } = require('@opentelemetry/exporter-collector-grpc');

const sdk = new NodeSDK({
    traceExporter: new CollectorTraceExporter(),
});
sdk.start().then(() => {
    console.log('SDK configured');
});

Thanks for the quick response.  That all makes sense and the example works well for me.


fix URL in setup.py

Description:

Related issue (if applicable): fixes #
Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] Tests have been added/updated. No exclusions in .coveragerc permitted.
[ ] README.MD updated (if necessary)

Thank you!


Part3 rma update

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

MPI/mpi-one-sided-communications-functions.md
:white_check_mark:Succeeded
View

MPI/mpi-win-flush-all-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-flush-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-flush-local-all-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-flush-local-function.md
:white_check_mark:Succeeded
View

MPI/toc.yml
:white_check_mark:Succeeded
View

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


Add doc page for protecting a list endpoint

Description
Some version of this question pops up pretty regularly on Discord. It'd be good to have documentation that we can point users to, and this could potentially be something that users discover before getting to where they ask the question.
Changes
Add the docs
Review
Lemme know what you think

Thanks!