Re-introduce aws-sdk-rust as rusoto S3 replacement

refer #2837
Need to test against staging or similar env to check ImdsCredentialsProvider because all the tests uses EnvironmentVariableCredentialsProvider and that works fine.
Sorry @SomeoneToIgnore for the revert
Thanks!

No worries, everybody makes mistakes, I was wrong for not checking good enough about IAM even though had a branch with exactly same changes and had even looked it through.
And, staging is created for breaking, good that we've noticed it, thank you for quick fixes and the code.
LGTM changes, I will merge it later, most probably on Monday to not to interfere with the ongoing release.

Thanks @SomeoneToIgnore!
I will continue the original task when we confirm that there is no more errors and also the combination of stream and content_length gets supported in aws sdk (they put in their backlog).


ResolveDilatedConv bug fix

Missing scenario to detect dilated Conv is added.
Ref: #22146

@alanchiao : Gentle reminder!

Hello. Does this fix resolve as well the issue with conversion of models created with keras-TCN to TFLite? If yes, that would be great. Best regards.

@alanchiao : Gentle reminder!

Can one of the admins verify this patch?

@alanchiao Can you please take a look on this PR? Thanks!

@ANSHUMAN87 Can you please check reviewer comments and keep us posted. Thanks!

generate_examples_lib

@jdduke : I am trying to run the generate_examples_lib, but it throws so many compilation error in my workspace. Can you please help me how to run this in my local. May be i am doing some mistake.
NOTE: I am running on latest code.
TIA!


Question: I have a potentially long running operation as part of my extension's installation. Where is the best place to do it?

I have a long running operation (searching if a certain npm-package is globally installed, if not, installing it globally) that I need to do as a part of installing my VSCode extension.
I'm seeking information about what's the best place to do it?
Initially, I had it in extension activation (with checks to bail early if package is present) and it worked okay. The flipside is that the very first time the user installs the extension, it won't work until the long running operation completes.
So, I'm moving it as a script to be executed during "preinstall" or "postinstall" step.
    "scripts": {
        "preinstall": "node ./install.js"
    },

Now, when I Install my extension (from a packaged vsix), I am observing that the npm-package isn't being installed. So, I'm curious if "scripts:{ }" is the right way to go about this? [To be sure, the same script succeeds, if invoked separately from a command prompt.]
I can provide the script i'm using, if required.
Thanks.

Ah.. I just realized that "preinstall" is picked up by npm and is executed when i do an "npm install" before packing a vsix. But that would install the dependency on my machine. Is there a way for me to direct VSCode to do that on the user's box while installing the extension? I'm only seeing a "Vscode.prepublish" which I don't think would help my case.
So, I wonder what's the right way to go about this?

Doesn't adding to dependencies in your package.json help?

In my case, I would like the dependency to be installed in the global location. Is that what it does? I vaguely recall trying that unsuccessfully..

just verified: adding it to dependencies brings it to the node_modules folder of my extension. I need it to be installed in npm's global node_modules folder.

Our current recommendation is to do it in activation, like you had before. One suggestion is to indicate to the user that the extension needs to perform some one-time startup tasks, via the status bar or notification messages.
We don't support installation-time tasks.

At the same time... why do you need the dependency specifically installed globally?

I'm building a starter kit for something, which along some features like "project scaffolding, snippets, some completionlist help" etc. The project scaffolding is on top of yeoman and is effectively a npm package.
Installing my extension, should install that package to the global folder because:

vscode-yo looks for generators in the global npm location.
the generator should also be callable from command line with yo syntax, which also needs the package to be installed globally.

effectively, the issue is, the package my extension brings along isn't really used by my extension, but just brings in some stuff which may be used independently, later on, outside of my extension, either from VSCode itself or from command line.
for the first time though, this could actually take several minutes, to bring down dependencies via the network. So, doing this operation on activation doesn't result in a great end user experience. While I'll go with that route for now, I think this makes a case for adding support for "installation-time tasks". I'll open a new feature-request it seems agreeable.
/cc: @waderyan

What will happen to users that don't have Node installed and install your extension?
It seems to me your extension should describe some Prerequisites it its README, so users know what to install beforehand. Additionally, in a situation that Node exists but the global modules are not installed, it should offer the user the optional service of installing them.

What will happen to users that don't have Node installed and install your extension?

isn't this all the more reason to provide install time hooks, so that extension writers can check prerequisites and bail early if prerequisites are not satisfied?

in a situation that Node exists but the global modules are not installed, it should offer the user the optional service of installing them.

Could you please expand a bit more on what is the recommended way to accomplish this? this is what I'm trying to accomplish and thought it would be nice to do so at the time the extension is being installed?
Also, please let me know if I should open a new issue, as we seem to be discussing on a thread that's marked as "closed".

Let me rephrase: If users don't have Node installed, your extension couldn't install the global modules it needs at all.
For users that have Node installed: your extension, upon detecting that the global modules it needs are not available, when asked to perform any functionality (running a command, for example), it can propose to the user "Hey do you want to install this and that globally? Press Yes", proceed to install the dependencies and then performs the functionality it was asked to perform.


[5.5.x] Add priority classes to dns, gravity and tiller apps

Description

This PR sets high priority classes for Tiller deployment, gravity-site daemonset and coredns daemonset.
Type of change

New feature (non-breaking change which adds functionality)

Linked tickets and other PRs

Parially fixes https://github.com/gravitational/gravity/issues/1611 for 5.5

Requires rigging #78

TODOs
Implementation

Testing done

Install cluster with changes from this PR.
Create example nginx deployment.

kubectl apply -f https://k8s.io/examples/application/deployment.yaml

Set resource limits for nginx deployment.

kubectl set resources deployment nginx-deployment --limits=cpu=400m,memory=512Mi

Scale up nginx deployment to reach resources limits for nodes

kubectl scale deployment nginx-deployment --replicas=40

Check that some pods are in Pending state.

kubectl get pod -o wide | grep -i pending
nginx-deployment-76c987f6c4-464ft   0/1     Pending       0          31s     <none>         <none>         <none>           <none>
nginx-deployment-76c987f6c4-4wx6c   0/1     Pending       0          31s     <none>         <none>         <none>           <none>
nginx-deployment-76c987f6c4-8dhj9   0/1     Pending       0          31s     <none>         <none>         <none>           <none>
nginx-deployment-76c987f6c4-929c2   0/1     Pending       0          16s     <none>         <none>         <none>           <none>

Delete one of the coredns pods and check it is rescheduled again.

kubectl --namespace=kube-system delete pod coredns-fns46
pod "coredns-fns46" deleted

kubectl get pod -o wide --all-namespaces| grep cored
kube-system   coredns-9n9kn                         1/1     Running     0          11s     <IP_ADDRESS>   sergei-dev-2   <none>           <none>
kube-system   coredns-lgm8n                         1/1     Running     0          46m     <IP_ADDRESS>    sergei-dev-1   <none>           <none>
kube-system   coredns-v8vns                         1/1     Running     0          46m     <IP_ADDRESS>    <IP_ADDRESS>    <none>           <none>

Repeate the same step 6 for tiller and gravity-site pods.

Additional information

@UnderGreen I'm curious about the behavior when the node is already "full" and one of our critical pods needs to be scheduled on it. Will Kubernetes evict one of the other pods in this case?


Regards on Modeling Rewards Signaling

Reward Signals is one of the common reasons why RL(and at the same time, Game Theory) works well; it guides RL agents to move toward the ideal goal. Needless to say in Multi-Agent RL(MARL) problems as well.
Synthesizer vs Verifier
Note that our SynthRL is based on CEGIS(especially OGIS). We formulate the OGIS in RL problem. Thus, the problem involves the interaction between two agents: Syntherisizer and Verifier.
Synthesizer may want to synthesizer well, satisfying test case constraints. However, NOT JUST WELL. It must synthesize non-ambiguous program well. How could we guide the synthesizer to do so? One obvious way is by leveraging the Verifier's reward signal(to us, it is state value of Verifier). In a way that Verifier may have a less potential reward(i.e, Verifier won't produce semantically equivalent program well), the more possibility that Synthesizer will produce a non-ambiguous program, and therefore become close to the desired ideal, generalized, program.
Ablation Study
Reward signaling will be the most unique feature of our SynthRL, distinguishing from other program synthesis researches. However, empirical ablation study should be operated answer:
RQ. RL based synthesis with Reward signaling from verifier vs without signaling

Merely replacing SMT solver (in synthesizing) is not enough unique research.
We will be replacing the SMT solver for a synthesizer. Instead of solving some logical formula to find the desired program, we compose a (learned) agent, and the agent will synthesizer the program according to learned policy.
This is not enough. We may want to synthesize better. To do so may be leveraging signals from the verifier.


front camera mirrored

When I close my left eye for example, it is detected as the right eye. When i turn right, is detected as turn head left. I'm using the front camera. Any idea?

Try this https://www.youtube.com/watch?v=mv4c2uTxR4U&list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i&index=74


Two text inputs sharing same content

Unfortunately, i cant use more than one text input at once. There are two instances but they share the content...
See code:
import pygame_textinput
import pygame
pygame.init()

# Create TextInput-object
textinput = pygame_textinput.TextInputVisualizer()
textinput2 = pygame_textinput.TextInputVisualizer()

screen = pygame.display.set_mode((1000, 200))
clock = pygame.time.Clock()
switch = False

while True:
    screen.fill((225, 225, 225))

    events = pygame.event.get()
    for event in events:
        if event.type == pygame.QUIT:
            exit()

    if [ev for ev in events if ev.type == pygame.KEYDOWN and ev.key == pygame.K_RETURN]:
        switch = not switch
    # Feed it with events every frame
    if switch:
        textinput.update(events)
    else:
        textinput2.update(events)
    # Blit its surface onto the screen
    screen.blit(textinput.surface, (10, 10))

    screen.blit(textinput2.surface, (10, 30))
    pygame.display.update()
    clock.tick(30)

Hey, thanks for pointing this out! :) Should be fixed now, including in pypi. Upgrade with
python3 -m pip install pygame_textinput --upgrade

Tell me if you find more bugs!


Expensive test fixes

Please have a look at the individual commit messages for the details.

This change is

Reviewed 1 of 1 files at r1, 1 of 1 files at r2, 1 of 1 files at r3, 1 of 1 files at r4, 7 of 7 files at r5.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

analyzer/src/funTest/kotlin/gradle/BaseGradleSpec.kt, line 80 at r4 (raw file):

                if (matches.isNotEmpty()) {
                    sourceGradleProjectFiles.add(matches.first())
                }

What about something like:
val sourceGradleProjectFiles = downloadedDir.walkTopDown()
    .filter { it.isDirectory }
    .map { Gradle.matchersForDefinitionFiles.mapNotNull... }
    .filter { it.isNotEmpty() }
    .map { it.first }

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

analyzer/src/funTest/kotlin/gradle/BaseGradleSpec.kt, line 80 at r4 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
What about something like:
val sourceGradleProjectFiles = downloadedDir.walkTopDown()
    .filter { it.isDirectory }
    .map { Gradle.matchersForDefinitionFiles.mapNotNull... }
    .filter { it.isNotEmpty() }
    .map { it.first }

For now, I deliberately made this look like the corresponding code at https://github.com/heremaps/oss-review-toolkit/blob/master/analyzer/src/main/kotlin/Main.kt#L194. I agree both code locations deserve an improvement, but I'd like to do that at a later time.

Comments from Reviewable


Azure built-in roles restricted - Code: InvalidRegistrationDefinitionCreateRequest

Hello,
I have been working on implementing Azure Lighthouse to our organization. The built-in roles are great for allowing me to define the actions and permissions allowed for users in a defined security group.
https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles
However, I seem to run into issues such as:
The role definition 'e5e2a7ff-d759-4cd2-bb51-3152d37e2eb1' is not allowed for registration definition '00000000-0000-0000-0000-000000000000' [redacted] because of restricted actions. (Code: InvalidRegistrationDefinitionCreateRequest)
The 'e5e2a7ff-d759-4cd2-bb51-3152d37e2eb1' role is the Storage Account Backup Contributor
Is there a way to find what roles are restricted from being delegated?
What would be the workaround? Creating a custom role?

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

ID: 99581afb-7950-6daa-7227-055d04446b7e
Version Independent ID: f1a5bf89-9e54-aede-3a9a-70788a95927b
Content: Azure built-in roles - Azure RBAC
Content Source: articles/role-based-access-control/built-in-roles.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@dchcom
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation


Fix to make nested transaction receive userParams from outer transaction

User params are passed from knex to the first transaction, but not from the first transaction to the next nested transaction. This PR fixes that.

coverage: 92.795% (-0.002%) from 92.797% when pulling 41d03d12958808424c5bfffd52e85e0757c86200 on ryanrobertsname:pr-fix-transaction-userParams into 5ececd35c9520dd2a006ee27721178dc465a8a8c on knex:master.


OCPBUGS-36230: Use a reconciled proxy config when generating nodepool userdata

What this PR does / why we need it:
The proxy configuration from the HostedCluster resource is not currently used when generating user data (an empty proxy config is used). This commit invokes the reconcile on the proxy config so that it's filled in with the values from the HostedCluster.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #OCPBUGS-36230
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.

The change was introduced here: https://github.com/openshift/hypershift/pull/3969
It didn't look intentional.

/jira refresh

/lgtm

/retest-required

/cherry-pick release-4.16

/hold cancel


Refactor type definitions using templates

This refactors type definitions using templates. Benefit of approach is that we can hide some specs of sub CRs from the top-level Ironic CR, and decrease size and complexity of the resource definition.
This also replaces defaulting in webhook. The problem with using webhook is that the copied default is baked in CR and users should update all fields when they update existing instances.

/retest
looks new crd definition is not picked up for some reason ...

/retest

/test ironic-operator-build-deploy-kuttl

/test ironic-operator-build-deploy-kuttl
github api ratelimit


[NEMO-128] Support Beam UnboundedSource

JIRA: NEMO-128: Support Beam UnboundedSource
Major changes:

Support Beam UnboundedSources

Minor changes to note:
Tests for the changes:
Other comments:
Closes #

@DifferentSC ping :)

@taegeonum @johnyangk Thanks a lot for your review and sorry for my slow response :). I have addressed your comments.


build: remove cc_wrapper

Signed-off-by: Mike Schore<EMAIL_ADDRESS>

we need to fix a definition. Let me take a look

superseded by #286


Added Translation (Portuguese-Portugal)

Don't know why it's failing. Can you see what's wrong?
thank you

I haven't touched this project for 2 years, I guess CI config needs to be updated to fix builds.
Your PR is not why build is broken.

Ok :)


[Core] Optimize typedefs.h functions

Optimized typedefs functions. Their performance improved 1.5 - 8 times.

Benchmark function I used
int arr[10000];
static void Bench(benchmark::State& state) {
  for (auto _ : state) {
	for(int i = 0; i < 10000; i++) {
		arr[i] = func(arr[i]);
	}

  }
}
BENCHMARK(Bench);

86x difference in performance is achieved for nearest_shift function.

For next/prev_pow2 it is 1.5 - 1.8.

What is arr initialized with? You're calling the method with the array but your code doesn't show how it's initialized
Also at least some of the implementations aren't correct, see the windows run, so would be good to ensure all work correctly before benchmarking it
Also would need benchmarking on all platforms where the code has changed, so we can tell it hasn't worsened

What is arr initialized with? You're calling the method with the array but your code doesn't show how it's initialized

Oh. Made new benchmarks where I initialized rand values.
Made benchmarks on Windows, Linux and another Linux, but an old device from 2011. MSVC compiler was used on Windows.
It turns out that before next/prev_power_of_2 was 1.5 (Linux) - 3.5 (Windows) times faster. For everything else, my changes are better.
For next_power_of_2_64 1.5 times on all devices.
nearest_shift 10 times old linux, 5 times linux, 8 times Windows.
get_shift_from_power_of_2 (made random data that is a power of two) 7 times linux 10 times old, 7 times Windows.

Please provide the full benchmarking code to replicate

benchmark_typedefs.zip

If you get different results with uninitialised values (and we don't know what values they are, depends on compiler and you code) and with randomly initialised values, 10k test pattern may be not enough to measure before-after difference for different inputs for before-after.

Please provide the full benchmarking code to replicate

Edit: Oops, I made a mistake in the next_power_of_2_64 benchmark. Updated file: benchmark_typedefs.zip

Ran the provided code - I'm sure I might have done something wrong, but I got the following results:

If results are actually valid, standard deviation for next_power_of_2_64 and previous_power_of_2 is enormous, so tests might be invalid. If so, samples amount should actually be increased and the same input data should be used to test same before/after functions.

the same input data should be used to test same before/after functions

I don't think so, since these functions are independent of the data they are given.

the same input data should be used to test same before/after functions

I don't think so, since these functions are independent of the data they are given.

As I know, using different data for comparison tests is bad practice (because could be used to get fake results). Maybe it doesn't matter in this specific situation.
I think that functions are still dependent of input data, at least "before" functions with for loops and return inside loops. So you may get different iterations amount depending on input number.


[Bug]: png images no longer displayed as transparent

Describe the problem
As title says, in one of the last updates something changed and png images with transparent background no longer are displayed as transparent but with a black background instead. Is this a bug or am I missing something in the settings?
Device model
No response
Android version
Android 14
App version
1.19
Additional information
No response

Hi @morphinpink, thanks for reporting this issue. Nothing was changed recently regarding support for transparent PNGs, so I'm trying to understand what could be happening as I'm not able to reproduce the issue myself.
* Does it happen with any transparent PNG?

* Do you have the "data saver" setting enabled?

* Is the file extension `.png` or `.PNG`?

Thanks for the help!
Yes it happened with all transparent pngs, I've tried with several different files. They're all indeed png files.
I'm not sure about the data saver setting, is this option in the app settings or the settings of every individual widget?

@morphinpink ok, thanks for confirming. As for the data saver, you can find it in the settings tab of the app, the menu is called "Optimized Storage". Regardless if you have it enabled or not, could you try switching that preference and see if the issue still happens?

I found it! it was enabled and disabling it did fix it.  Thank you so much!

@morphinpink hooray! 🎉
I'm glad to hear that. It seems like there's something wrong with this option then, because it should work just the same when it is enabled. I'll have it fixed in the next update, thanks for bringing this to my attention!


[build] Remove testing feature and ensure correct builds

Libra used the 'testing' feature as well as overloaded dev-dependencies to
enable testing features of dependencies at test time. Unfortunately due to
Cargo's feature unification, this resulted in every build including test and
fuzzing code, including code that allowed private keys to be cloned.
This retains the testing and fuzzing support while removing the feature
unification problems. This is accomplished by never overloading features in
dev-dependencies, and instead passing wanted features on the command line at
testing time. It also avoids other cases of feature unification by using
default-members to control what gets built by default. Building all targets
simultaneously will always result in feature unification turning on things as
some of our targets are test only and cargo unifies features globally per
invocation of cargo build.
Because this increase the complexity of running unit tests, some of which need
extra flags now, a new extension to Cargo is added called xtask. Use cargo xtask test-unit or cargo xtask test-unit -p CRATE to unit test all crates
or an individual one. The test-unit command knows what flags each crate needs
for testing.

@bors-libra r=bmwill

:pushpin: Commit b6700ab has been approved by bmwill

:hourglass: Testing commit b6700abf9f443ce2cad0b01569968ab377839749 with merge d016e23a1d277f0aa7d0d65e45c0da3507884640...

@bors-libra p=1337

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r=bmwill p=1337

:pushpin: Commit f8c1d0a has been approved by bmwill

@bors-libra r=bmwill p=1337

:pushpin: Commit 9e8d3ce has been approved by bmwill

:hourglass: Testing commit 9e8d3ce6686a25d0765e2b1d98afaed094635334 with merge aa6fc6aef0dad31a6536f33a27178ebfc0137570...

@bors-libra r=bmwill p=1337

:pushpin: Commit b1d8844 has been approved by bmwill

:hourglass: Testing commit b1d88440d896242a1afc64c3dbc38d4c39f0e335 with merge 1d1cb4002980a129d51a38f36f0ee885d5fd8bb0...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: bmwill
Pushing 1d1cb4002980a129d51a38f36f0ee885d5fd8bb0 to master...


Fail to setup CloudFoundry on AWS region eu-central-1 with BOSH version 3232

We are currently trying to deploy CloudFoundry on AWS (region: eu-central-1) as per their instructions. At the point where we run the command bosh aws create we get the following error:
[ec2-user@ip-XXX-XXX-XXX-XXX cf]$ bosh aws create
Executing migration CreateKeyPairs
allocating 1 KeyPair(s)
Executing migration CreateVpc
creating internet gateway
creating security groups: open, bosh, bat, cf, web
creating subnets: bosh1, bosh_rds1, cf_elb1, cf_rds1, services_rds1, cf1, services1, bosh_rds2, cf_elb2, cf_rds2, services_rds2
  Making subnet bosh1 <IP_ADDRESS>/24:
  Making subnet bosh_rds1 <IP_ADDRESS>/24:
  Making subnet cf_elb1 <IP_ADDRESS>/24:
  Making subnet cf_rds1 <IP_ADDRESS>/24:
  Making subnet services_rds1 <IP_ADDRESS>/21:
  Making subnet cf1 <IP_ADDRESS>/20:
  Making subnet services1 <IP_ADDRESS>/20:
  Making subnet bosh_rds2 <IP_ADDRESS>/24:
  Making subnet cf_elb2 <IP_ADDRESS>/24:
  Making subnet cf_rds2 <IP_ADDRESS>/24:
  Making subnet services_rds2 <IP_ADDRESS>/21:
details in S3 receipt: aws_vpc_receipt and file: aws_vpc_receipt.yml

expected string value for option image_id.

The actual error, expected string value for option image_id., seems to come from the aws-sdk (aws-sdk-v1-1.60.2) ruby gem, in file lib/aws/core/option_grammar.rb and function apply_string_descriptor. Is this because of the region eu-central-1, or is the bosh_cli_plugin_aws broken, or is this something else?
We see that the file receipts/aws_vpc_receipt.yml is actually put in the s3 bucket and it has file contents. Also there is aws_migrations/migrations.yaml in the s3 bucket.
We (obviously) tried finding the cause of this error myself, then stumbled upon a Github issue stating that "bosh aws * commands have been deprecated few months ago. (written on Nov 2, 2015)", but is this the actual case, and what is the replacement to install Cloud Foundry on an AWS Environment then?
Relevant version information:
BOSH version: 1.3232.0
Ruby version: 2.0.0p648
Gemfile.lock: see attached Gemfile.lock.txt

cc @Amit-PivotalLabs

Hey @djvdorp
Not sure if you saw my response to your Slack question: https://cloudfoundry.slack.com/archives/general/p1465834173000016
The docs are in an intermediate state essentially waiting on new tooling, and the new tooling is in progress, but we can guide you in using the new tooling if you're willing to try it out.  It intentionally doesn't do everything the old "bosh aws bootstrap" tools did, for instance it doesn't create RDS instances (and assumes you'll deploy CF with the built-in postgres job, or manage RDS or some other external database yourself).  If you're interested in this guidance, let me know.

Hi @Amit-PivotalLabs
I must apologize that I missed your response to my Slack question, which I will put here below for other people's reference which might be useful:
amitgupta [6:09 PM]
@djvdorp: the problem with those docs and tools is they can get out of date. We're working on some tooling that will be actively supported. For now you've got a few options

1. Still try to use the "bosh aws" tooling. Last time we tried those instructions they worked, with some small road bumps though
2. Those docs also outline a manual procedure you could try
3. The new tooling is still in experimental phase, but I can point you to it

I did not have the opportunity yet to discuss this with my colleagues who are working with me on deploying CloudFoundry on AWS, but today we have spent quite some time on getting option 1 to work. For tomorrow we were thinking about looking into option 2, but I would be very interested to learn more about option 3 since I highly prefer automation over manual work.
Could you point us towards information regarding this option, and guide us in using this new tooling to try out? Thank you for your time and effort so far, it is highly appreciated!

We'd like to remove the "bosh aws" from the documentation as soon as possible, so if you're willing to try option 3 the feedback would be very valuable for us, and should get us to a place where we can replace those docs with something that works sooner.
Option 3 is currently experimental and lives in the pivotal-cf-experimental org, but we'll be moving it over to the cloudfoundry-incubator org soon: https://github.com/pivotal-cf-experimental/bosh-bootloader.  If you open an issue there we can describe a workflow that should get you started with CF (later on, a polished set of docs will describe the workflow), though we're waiting on one feature from BOSH that's just around the corner, to support "BOSH 1.0" style manifests, since the existing tooling for generating CF manifests only supports the 1.0 style.

@djvdorp, I think you have been able to get CloudFoundry deployed now with some help from bbl, so I'm going to close this. Feel free to reopen if that's not the case, or start a new issue for other problems.


Fail to download train and validation splits

Thank you for your excellent work !
l want to download train and validation splits list, but l can't access dropbox (https://www.dropbox.com/s/fyz9fec72v7gbxj/list.tar.gz). anyone can help me
l also need ucf-101 train and validation splits list and expect to your help

It seems working for me.


Could Parcel have the @parcel/@parceljs/@parcel-bundler scopes on npm?

Hi, I contribute to https://parceljs.org
We noticed that the @parcel/, @parceljs/, and @parcel-bundler/ npm scopes/usernames are taken by members of the Webpack team.
I sent a message the other day to the team member (@rynclark) who owns @parcel/ requesting it for ourselves and they refused and then blocked me and other Parcel team members.
Squatting on names like this isn't okay. It's not how we should behave in the open source ecosystem. I didn't expect this kind of hostility from the Webpack team.
Could we please fix this?

/cc @webpack/core-team @contributor-team
Looks like shame, sorry

https://www.npmjs.com/settings/parcel/members
https://www.npmjs.com/settings/parceljs/members
https://www.npmjs.com/settings/parcel-bundler/members
Someone with admin access add thejameskyle and/or devongovett and everything will be 200 OK.

I would like to apologize for some members of webpack team. It is not possible to learn about what is happening in the minds of some people. I hope for an early solution of the problem.

I second @evilebottnawi, as part of the webpack documentation team, hope this gets fixed soon.

I'm locking this issue as we don't know, nor can we presume to the know the reasoning or motivation behind the conflict. Posting an issue instead of going through a myriad of other available channels to resolve this seems an awful lot like trying to shame the project into action. You could have chosen a better path, and your issue isn't going to do much to lessen the silly polarization and side-taking between the two projects.
We'll address this internally, find out why it happened, what transpired during the requests, and go from there. I'd also like to note that if an individual chooses to act on their own, even if they've contributed to the project in the past, it does not constitute policy of the rest of contributors, past or present, nor of the actual core or contrib teams.
cc: @TheLarkInn

We do not own this package. I have already spoken with @devongovette about this. We can do our best at the very least and just as we have in the same way in the past, will not make any exceptions and help if we can.