IE browser does not work with canopy 1.0.3

i have Canopy 1.0.3 installed but my IE 11 does not work, when i run it does not open and no error, Does canopy 1.0.3 support IE 11, Could you please let me know which webdriver i need to install for IE 11

Issue resolved so closing this, installed latest iewebdriver.exe


Add ability to pass a login hint in the url

We need a way to pass a username in the initial url that should be used on the sign in page.
This would allow for linking to an application where we already know the username (i.e. because we are switching from an existing application).
Ideally this would trigger the sign in flow as if the user typed in their own user name so that if GetCredentialType tries to redirect that this would happen immediately, to handle SSO scenarios.

Added in 38547f918668c7758cf2a7898a426274dec3f0c7


Memory alignment issues in Table Services

The CFE code has some problem areas for CPUs that have strict memory alignment requirements (e.g. SPARC).  Casting from a type with smaller requirements to a type with larger requirements generates a compile time warning and may induce a runtime exception if the memory actually is not aligned.
The following errors exist in the TBL subsystem:
{{{
/cfe/fsw/cfe-core/src/tbl/cfe_tbl_internal.c: In function 'CFE_TBL_RemoveAccessLink':
/cfe/fsw/cfe-core/src/tbl/cfe_tbl_internal.c:480:70: warning: cast increases required alignment of target type [-Wcast-align]
Status = CFE_ES_PutPoolBuf(CFE_TBL_TaskData.Buf.PoolHdl, (uint32 *)RegRecPtr->Buffers[0].BufferPtr);
^
/cfe/fsw/cfe-core/src/tbl/cfe_tbl_internal.c:492:74: warning: cast increases required alignment of target type [-Wcast-align]
Status = CFE_ES_PutPoolBuf(CFE_TBL_TaskData.Buf.PoolHdl, (uint32 *)RegRecPtr->Buffers[1].BufferPtr);
^
}}}
NOTE: This is related to PSP ticket [cfs_psp:41]

Imported from trac issue 283.  Created by jphickey on 2019-04-25T09:54:18, last modified: 2019-08-14T14:10:17

Targeting 7.0 to allow major tlm packet updates. Errors don't show up in 32bit build for MCP750 with CCSDS Version 2 set so not critical to 6.8.

This is already fixed in issue #437, via commit 4607e4ee

Fixed by #479


Index Creation KO: mark existing column as not present.

Stargate version: 2.0.1
(Introduced in V2, this test is working in V1)
Behaviour:
Given an existing table videos, in a keyspace java with column title.

The call is successful and return. I confirm this column exists in the table.
{
  "data": {
    "name": "title",
    "typeDefinition": "text",
    "static": false
  }
}

When trying to create an index on that column...

The following message is returned
{
  "description": "Column 'title' not found in table.",
  "code": 404,
  "grpcStatus": null,
  "internalTxId": null
}

The Table definition is the following:
CREATE TABLE java.videos (
    genre text,
    year int,
    title text,
    formats frozen<map<text, text>>,
    tuples frozen<tuple<text, text, text>>,
    upload timestamp,
    frames list<int>,
    tags set<text>,
    PRIMARY KEY (genre, year, title)
) WITH CLUSTERING ORDER BY (year ASC, title ASC)

Or as Json
{
  "data": {
    "name": "videos",
    "keyspace": "java",
    "columnDefinitions": [
      {
        "name": "genre",
        "typeDefinition": "text",
        "static": false
      },
      {
        "name": "year",
        "typeDefinition": "int",
        "static": false
      },
      {
        "name": "title",
        "typeDefinition": "text",
        "static": false
      },
      {
        "name": "formats",
        "typeDefinition": "frozen<map<text, text>>",
        "static": false
      },
      {
        "name": "frames",
        "typeDefinition": "list<int>",
        "static": false
      },
      {
        "name": "tags",
        "typeDefinition": "set<text>",
        "static": false
      },
      {
        "name": "tuples",
        "typeDefinition": "tuple<text, text, text>",
        "static": false
      },
      {
        "name": "upload",
        "typeDefinition": "timestamp",
        "static": false
      }
    ],
    "primaryKey": {
      "partitionKey": [
        "genre"
      ],
      "clusteringKey": [
        "year",
        "title"
      ]
    },
    "tableOptions": {
      "defaultTimeToLive": 0,
      "clusteringExpression": [
        {
          "name": "year",
          "order": "ASC"
        },
        {
          "name": "title",
          "order": "ASC"
        }
      ]
    }
  }
}

Hm, was there no test for this before or? Seems strange that some things are not working now and are OK in v1.

We do have tests for Index creation so it is not immediately clear why this would fail.
I will try to reproduce with an IT when I get to this one (there are couple of REST bugs to go through).

Ok, it looks like I can reproduce this issue with an Integration test -- will try to see how this is different from existing Index creation IT that passes.

Interesting. This is because title is part of primary key; check for column existence is looking at list of non-key columns (assuming probably that the list contains all columns).
Good catch; earlier tests was using non-key column and did not hit this problem.

PR ready for review.


In "New Spark Job" flow user cannot provide other fields declared in livy batch REST API

Is your feature request related to a problem? Please describe.
For batch Spark job submission flow, we can only provide the main file and class, and referencing jars or py files. There is no way to specify, for example driverMemory, executorMemory and other Spark configurations.
Describe the solution or feature you'd like
Please provide a list of parameters in addition to “Main Class” and “Arguments” declared in “POST /batches” REST API:
driverMemory	Amount of memory to use for the driver process	string
driverCores	Number of cores to use for the driver process	int
executorMemory	Amount of memory to use per executor process	string
executorCores	Number of cores to use for each executor	int
numExecutors	Number of executors to launch for this session	int
queue	The name of the YARN queue to which submitted	string
conf	Spark configuration properties	Map of key=val
Describe alternatives you've considered
No alternatives.

Done


Running without Webpack

I am having a problem with importing HighCharts/HighStock without webpack.
I am importing HighStock like this
import ReactHighstock from 'react-highcharts/bundle/ReactHighstock.src';

and then using it like this (amongst other ways)
ReactHighstock.Highcharts.setOptions(theme);

This works correctly when bundled with webpack.
When ran without it, via mocha, everything still works except the shown import, which does now equal some webpack object.
I really need to run my tests directly without first running through webpack. How can I do that?

Try require maybe instead of import?

Oh, I forgot to mention it but I also tried require and it seems it worked exactly as 'import', no difference whatsoever.
It took me some time to figure it out, but it is definitely very weird. No other component in a big project exhibited such behavior.

I've added you on hangouts, ping me when you have a sec, and we can debug it together.
As a guess try using non-bundled version.


Removing validate_number from Ecto lib docs.

As the function no longer exists (for now).
I've added in an example for validate_inclusion instead so that the :age related comment in the prose below still makes sense.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


Flutter Web SVG is rendering in Chrome fine, but not Firefox

Steps to Reproduce

Create a Flutter template app
Swap the contents of the Center widget with:

Image.network(
"data:image/svg+xml;base64,PHN2ZyByb2xlPSJpbWciIHZpZXdCb3g9IjAgMCAyNCAyNCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj48dGl0bGU+QWJzdHJhY3QgaWNvbjwvdGl0bGU+PHBhdGggZD0iTTEyIDBjOS42MDEgMCAxMiAyLjM5OSAxMiAxMiAwIDkuNjAxLTIuMzk5IDEyLTEyIDEyLTkuNjAxIDAtMTItMi4zOTktMTItMTJDMCAyLjM5OSAyLjM5OSAwIDEyIDB6bS0xLjk2OSAxOC41NjRjMi41MjQuMDAzIDQuNjA0LTIuMDcgNC42MDktNC41OTUgMC0yLjUyMS0yLjA3NC00LjU5NS00LjU5NS00LjU5NVM1LjQ1IDExLjQ0OSA1LjQ1IDEzLjk2OWMwIDIuNTE2IDIuMDY1IDQuNTg4IDQuNTgxIDQuNTk1em04LjM0NC0uMTg5VjUuNjI1SDUuNjI1djIuMjQ3aDEwLjQ5OHYxMC41MDNoMi4yNTJ6bS04LjM0NC02Ljc0OGEyLjM0MyAyLjM0MyAwIDExLS4wMDIgNC42ODYgMi4zNDMgMi4zNDMgMCAwMS4wMDItNC42ODZ6Ii8+PC9zdmc+",
height: 70,
width: 70,
)

Full repo of the problem can be found here:
https://github.com/jpeiffer/flutter_firefox_svg_issue
Note: although other platforms exist in that repo, this bug only is about the WEB platform.
Expected results:
SVG renders in all browsers
Actual results:
SVG renders fine in Chrome, but not Firefox

Flutter Doctor
[✓] Flutter (Channel dev, 1.23.0-4.0.pre, on Mac OS X 10.15.6 19G2021 x86_64, locale en-US)
    • Flutter version 1.23.0-4.0.pre at /Users/jpeiffer/flutter
    • Framework revision 83dd176777 (8 hours ago), 2020-09-22 12:04:44 -0700
    • Engine revision 2abe69c608
    • Dart version 2.10.0 (build 2.10.0-136.0.dev)

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/jpeiffer/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/jpeiffer/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0, Build version 12A7209
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.49.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.14.1

[✓] Connected device (5 available)
    • sdk gphone x86 arm (mobile) • emulator-5554                        • android-x86    • Android 11 (API 30) (emulator)
    • iPhone 11 Pro Max (mobile)  • 8457B0C6-D39C-41CC-8ADE-0EB6AA5DC60B • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)
    • macOS (desktop)             • macos                                • darwin-x64     • Mac OS X 10.15.6 19G2021 x86_64
    • Web Server (web)            • web-server                           • web-javascript • Flutter Tools
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 85.0.4183.121

</details>

Hi @jpeiffer,
Since you are trying to use an svg image, you might need to use flutter_svg plugin. Please see this issue and related comments.
Also, while using that plugin, if you face any issues, you may need to open said issue in that plugin's repo.
Thanks.

@darshankawar This issue is unrelated to flutter_svg as flutter_svg does not support web. Let's not go around in circles again like we did on https://github.com/flutter/flutter/issues/63828

This issue came up because flutter_svg doesn't support Web.  I created the websafe_svg plugin that uses Flutter's native browser SVG support when on the Web platform, and falls back to the awesome flutter_svg plugin otherwise.
I was informed of this issue via my plugin, and some of the users of it pointed out that it happens with just vanilla Flutter Web absent my plugin, so I offered to try to open an issue to see if it could be fixed.
Although the core issue doesn't appear to be my plugin, I have left the issue open there.  Some users have identified some potential causes that might be helpful to your research and hopefully to a resolution:
https://github.com/peiffer-innovations/websafe_svg/issues/7

Issue replicable on latest beta.

flutter doctor -v
[✓] Flutter (Channel beta, 1.22.0-12.1.pre, on Mac OS X 10.15.4 19E2269, locale
    en-IN)
    • Flutter version 1.22.0-12.1.pre at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 8b3760638a (8 days ago), 2020-09-15 17:47:13 -0700
    • Engine revision 4654fc6cf6
    • Dart version 2.10.0 (build 2.10.0-110.3.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.49.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (2 available)
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome
      85.0.4183.102

• No issues found!

/cc @ferhatb @dnfield

FWIW, flutter_svg does work if you use CanvasKit. Or, at least, a lot of it works :)
Does FireFox support SVGs in data uris?

It does.  All browsers (at least all the major / well known ones) support Data URIs for any time of image; SVG included.  We've used that capability in other products to embed the SVG data in API calls for things like icons on cards.

Any news about this? Shows well on Chrome desktop for me but not on Chrome mobile...


fides GET /api/v1/system endpoint pagination

Is your feature request related to a specific problem?
We need pagination for the system endpoint in Fides in order to complete the pagination task outlined originally in this issue.
Describe the solution you'd like
BE change for pagination to fides GET /api/v1/system endpoint
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

This would need to be implemented for all of the GET /api/v1/{resource_model} endpoints because of the programmatic implementation:
https://github.com/ethyca/fides/blob/11f24e745f90d74da0a6f0cae5ff4b3fb733c534/src/fides/api/ctl/routes/crud.py#L35
@ThomasLaPiana @NevilleS This represents a breaking change, even if it's a small one. Any objections to this work?

Considering that these endpoints are not designed to be user-facing, and are supposed to be used only by the CLI to persist data, I'm ok with this but think this warrants a minor version bump
The CLI logic that parses responses from the server will also need an update, so this is a 5 to me from a points standpoint.


undefined method `-' for nil:NilClass

I am trying to use Bosh Scaler, but I get a recurrent error.
The error is very similar for all the different platforms and versions, in particular:

CF v205 on top of openstack: Error raised while syncing rules for {"name"=>"cf", "releases"=>[{"name"=>"cf", "version"=>"205+dev.1"}], "stemcells"=>[{"name"=>"bosh-openstack-kvm-ubuntu-trusty-go_agent", "version"=>"2889"}]}: undefined method `-' for nil:NilClass
CF v205 on bosh-lite: Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"205"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
CF v207 on bosh-lite: Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass

I am not able to run Bosh Scaler with ruby >=2.x and as a consequence I used ruby 1.9.3p551. I also checkout an old commit before the update to the new ruby version, but the error is the same.

Cloud you paste the full logs? I guess maybe something is not compatible with the latest bosh.

I, [2015-05-15T12:03:04.297189 #8676]  INFO -- : Starting...
I, [2015-05-15T12:03:04.297463 #8676]  INFO -- : Starting BOSH Scaler...
E, [2015-05-15T12:03:04.923022 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
I, [2015-05-15T12:03:04.982213 #8676]  INFO -- : BOSH Scaler is running
I, [2015-05-15T12:03:04.982534 #8676]  INFO -- : Starting BoshNatsCollector...
I, [2015-05-15T12:03:05.551795 #8676]  INFO -- : BoshNatsCollector is running
I, [2015-05-15T12:03:05.551912 #8676]  INFO -- : Starting CfVarzTsdbCollector...
I, [2015-05-15T12:03:05.552723 #8676]  INFO -- : NATS connected to mbus://nats:nats@<IP_ADDRESS>:4222
E, [2015-05-15T12:04:05.571712 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:05:06.222797 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:06:06.858284 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:07:07.479111 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:08:08.140354 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:09:08.798762 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:10:09.436299 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:11:10.063476 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:12:10.716418 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass
E, [2015-05-15T12:13:11.405511 #8676] ERROR -- : Error raised while syncing rules for {"name"=>"cf-warden", "releases"=>[{"name"=>"cf", "version"=>"207"}], "stemcells"=>[{"name"=>"bosh-warden-boshlite-ubuntu-trusty-go_agent", "version"=>"389"}], "cloud_config"=>"none"}: undefined method `-' for nil:NilClass

Hope this is useful.
Thank you.

Can I do anything to debug this problem?
Thank you,

Sorry for the delay to reply. Could you paste your deployment manifest?

The one deployed on top of Openstack.
I hope I can help you in find a possible solution.
Thank you very much.
compilation:
  cloud_properties:
    instance_type: m1.xsmall
  network: cf1
  reuse_compilation_vms: true
  workers: 6
director_uuid: 9e88299f-d714-4573-8c06-f2dcea0d451a
jobs:
- default_networks:
  - name: cf1
    static_ips: null
  instances: 1
  name: ha_proxy_z1
  networks:
  - name: floating
    static_ips:
    - <IP_ADDRESS>
  - default:
    - gateway
    - dns
    name: cf1
    static_ips:
    - <IP_ADDRESS>
  properties:
    ha_proxy:
      disable_http: false
      ssl_ciphers: null
      ssl_pem: '-----BEGIN CERTIFICATE-----

        -----END CERTIFICATE-----

        -----BEGIN PRIVATE KEY-----

        -----END PRIVATE KEY-----

'
    metron_agent:
      zone: z1
    networks:
      apps: cf1
    router:
      servers:
        z1:
        - <IP_ADDRESS>
        z2: []
  resource_pool: router_z1
  templates:
  - name: haproxy
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: nats_z1
  networks:
  - name: cf1
    static_ips:
    - <IP_ADDRESS>
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: nats
    release: cf
  - name: nats_stream_forwarder
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: nats_z2
  networks:
  - name: cf2
    static_ips: []
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: medium_z2
  templates:
  - name: nats
    release: cf
  - name: nats_stream_forwarder
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: consul_z1
  networks:
  - name: cf1
    static_ips: []
  persistent_disk: 1024
  properties:
    consul:
      agent:
        mode: server
        servers:
          lan: []
    metron_agent:
      zone: z1
  resource_pool: medium_z1
  templates:
  - name: consul_agent
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update:
    max_in_flight: 1
    serial: true
- instances: 0
  name: consul_z2
  networks:
  - name: cf2
    static_ips: []
  persistent_disk: 1024
  properties:
    consul:
      agent:
        mode: server
        servers:
          lan: []
    metron_agent:
      zone: z2
  resource_pool: medium_z2
  templates:
  - name: consul_agent
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update:
    max_in_flight: 1
    serial: true
- instances: 1
  name: etcd_z1
  networks:
  - name: cf1
    static_ips:
    - <IP_ADDRESS>
  persistent_disk: 10024
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: etcd
    release: cf
  - name: etcd_metrics_server
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: etcd_z2
  networks:
  - name: cf2
    static_ips: []
  persistent_disk: 10024
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: medium_z2
  templates:
  - name: etcd
    release: cf
  - name: etcd_metrics_server
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: stats_z1
  networks:
  - name: cf1
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: small_z1
  templates:
  - name: collector
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: nfs_z1
  networks:
  - name: cf1
    static_ips:
    - <IP_ADDRESS>
  persistent_disk: 10024
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: debian_nfs_server
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: postgres_z1
  networks:
  - name: cf1
    static_ips:
    - <IP_ADDRESS>
  persistent_disk: 4096
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: postgres
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: uaa_z1
  networks:
  - name: cf1
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: uaa
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: uaa_z2
  networks:
  - name: cf2
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: medium_z2
  templates:
  - name: uaa
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: login_z1
  networks:
  - name: cf1
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: login
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: login_z2
  networks:
  - name: cf2
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: medium_z2
  templates:
  - name: login
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: api_z1
  networks:
  - name: cf1
  persistent_disk: 0
  properties:
    consul:
      agent:
        servers:
          lan: []
        services:
        - cloud_controller_ng
    metron_agent:
      zone: z1
    networks:
      apps: cf1
    nfs_server:
      address: <IP_ADDRESS>
      allow_from_entries:
      - <IP_ADDRESS>/16
      - <IP_ADDRESS>/16
      share: null
  resource_pool: large_z1
  templates:
  - name: cloud_controller_ng
    release: cf
  - name: metron_agent
    release: cf
  - name: nfs_mounter
    release: cf
  - name: ca_truster
    release: cf
  - name: consul_agent
    release: cf
  update: {}
- instances: 0
  name: api_z2
  networks:
  - name: cf2
  persistent_disk: 0
  properties:
    consul:
      agent:
        servers:
          lan: []
        services:
        - cloud_controller_ng
    metron_agent:
      zone: z2
    networks:
      apps: cf2
    nfs_server:
      address: <IP_ADDRESS>
      allow_from_entries:
      - <IP_ADDRESS>/16
      - <IP_ADDRESS>/16
      share: null
  resource_pool: large_z2
  templates:
  - name: cloud_controller_ng
    release: cf
  - name: metron_agent
    release: cf
  - name: nfs_mounter
    release: cf
  - name: ca_truster
    release: cf
  - name: consul_agent
    release: cf
  update: {}
- instances: 1
  name: clock_global
  networks:
  - name: cf1
  persistent_disk: 0
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: cloud_controller_clock
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: api_worker_z1
  networks:
  - name: cf1
  persistent_disk: 0
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
    nfs_server:
      address: <IP_ADDRESS>
      allow_from_entries:
      - <IP_ADDRESS>/16
      - <IP_ADDRESS>/16
      share: null
  resource_pool: small_z1
  templates:
  - name: cloud_controller_worker
    release: cf
  - name: metron_agent
    release: cf
  - name: nfs_mounter
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: api_worker_z2
  networks:
  - name: cf2
  persistent_disk: 0
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
    nfs_server:
      address: <IP_ADDRESS>
      allow_from_entries:
      - <IP_ADDRESS>/16
      - <IP_ADDRESS>/16
      share: null
  resource_pool: small_z2
  templates:
  - name: cloud_controller_worker
    release: cf
  - name: metron_agent
    release: cf
  - name: nfs_mounter
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 1
  name: hm9000_z1
  networks:
  - name: cf1
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: hm9000
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: hm9000_z2
  networks:
  - name: cf2
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: medium_z2
  templates:
  - name: hm9000
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 2
  name: runner_z1
  networks:
  - name: cf1
    static_ips: null
  properties:
    dea_next:
      zone: z1
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: runner_z1
  templates:
  - name: dea_next
    release: cf
  - name: dea_logging_agent
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update:
    max_in_flight: 1
- instances: 0
  name: runner_z2
  networks:
  - name: cf2
    static_ips: null
  properties:
    dea_next:
      zone: z2
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: runner_z2
  templates:
  - name: dea_next
    release: cf
  - name: dea_logging_agent
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update:
    max_in_flight: 1
- instances: 1
  name: loggregator_z1
  networks:
  - name: cf1
  properties:
    doppler:
      zone: z1
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: doppler
    release: cf
  - name: syslog_drain_binder
    release: cf
  - name: metron_agent
    release: cf
  update: {}
- instances: 0
  name: loggregator_z2
  networks:
  - name: cf2
  properties:
    doppler:
      zone: z2
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: medium_z2
  templates:
  - name: doppler
    release: cf
  - name: syslog_drain_binder
    release: cf
  - name: metron_agent
    release: cf
  update: {}
- instances: 1
  name: loggregator_trafficcontroller_z1
  networks:
  - name: cf1
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
    traffic_controller:
      zone: z1
  resource_pool: small_z1
  templates:
  - name: loggregator_trafficcontroller
    release: cf
  - name: metron_agent
    release: cf
  update: {}
- instances: 0
  name: loggregator_trafficcontroller_z2
  networks:
  - name: cf2
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
    traffic_controller:
      zone: z2
  resource_pool: small_z2
  templates:
  - name: loggregator_trafficcontroller
    release: cf
  - name: metron_agent
    release: cf
  update: {}
- instances: 1
  name: router_z1
  networks:
  - name: cf1
    static_ips:
    - <IP_ADDRESS>
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: router_z1
  templates:
  - name: gorouter
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: router_z2
  networks:
  - name: cf2
    static_ips: []
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: router_z2
  templates:
  - name: gorouter
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: routing_api_z1
  networks:
  - name: cf1
    static_ips: []
  properties:
    metron_agent:
      zone: z1
    networks:
      apps: cf1
  resource_pool: medium_z1
  templates:
  - name: routing-api
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  name: routing_api_z2
  networks:
  - name: cf2
    static_ips: []
  properties:
    metron_agent:
      zone: z2
    networks:
      apps: cf2
  resource_pool: medium_z2
  templates:
  - name: routing-api
    release: cf
  - name: metron_agent
    release: cf
  - name: ca_truster
    release: cf
  update: {}
- instances: 0
  lifecycle: errand
  name: acceptance_tests
  networks:
  - name: cf1
  resource_pool: small_errand
  templates:
  - name: acceptance-tests
    release: cf
  - name: ca_truster
    release: cf
- instances: 0
  lifecycle: errand
  name: smoke_tests
  networks:
  - name: cf1
  properties:
    networks:
      apps: cf1
  resource_pool: small_errand
  templates:
  - name: smoke-tests
    release: cf
  - name: ca_truster
    release: cf
meta:
  default_env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  environment: null
  releases:
  - name: cf
    version: latest
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
name: cf
networks:
- name: cf1
  subnets:
  - cloud_properties:
      net_id: d04bf948-753d-4b4a-bf90-6809a2b0f4ab
    gateway: <IP_ADDRESS>
    range: <IP_ADDRESS>/16
    static:
    - <IP_ADDRESS> - <IP_ADDRESS>
    reserved: [<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>]
  type: manual
- name: cf2
  subnets:
  - cloud_properties:
      net_id: d04bf948-753d-4b4a-bf90-6809a2b0f4ab
    gateway: <IP_ADDRESS>
    range: <IP_ADDRESS>/16
    static:
    - <IP_ADDRESS> - <IP_ADDRESS>
  type: manual
- cloud_properties:
    net_id: 10d9e92914244b79bf29f6fd7b0fe05e
  name: floating
  type: vip
properties:
  acceptance_tests: null
  app_domains:
  - <IP_ADDRESS>.xip.io
  ca_truster:
    certificates: []
  cc:
    allowed_cors_domains: []
    app_events:
      cutoff_age_in_days: 31
    app_usage_events:
      cutoff_age_in_days: 31
    audit_events:
      cutoff_age_in_days: 31
    billing_event_writing_enabled: true
    broker_client_default_async_poll_interval_seconds: 60
    broker_client_max_async_poll_attempts: 25
    broker_client_timeout_seconds: 70
    buildpacks:
      buildpack_directory_key: cloudfoundry
      cdn: null
      fog_connection: null
    bulk_api_password: cloudfoundry
    client_max_body_size: 1536M
    db_encryption_key: cloudfoundry
    db_logging_level: debug2
    default_app_disk_in_mb: 1024
    default_app_memory: 1024
    default_buildpacks:
    - name: java_buildpack
      package: buildpack_java
    - name: ruby_buildpack
      package: buildpack_ruby
    - name: nodejs_buildpack
      package: buildpack_nodejs
    - name: go_buildpack
      package: buildpack_go
    - name: python_buildpack
      package: buildpack_python
    - name: php_buildpack
      package: buildpack_php
    default_health_check_timeout: 60
    default_quota_definition: default
    default_running_security_groups:
    - public_networks
    - dns
    default_staging_security_groups:
    - public_networks
    - dns
    default_to_diego_backend: false
    development_mode: false
    diego_docker: false
    directories: null
    disable_custom_buildpacks: false
    droplets:
      cdn: null
      droplet_directory_key: cloudfoundry
      fog_connection: null
    external_host: api
    external_protocol: http
    install_buildpacks:
    - name: java_buildpack
      package: buildpack_java
    - name: ruby_buildpack
      package: buildpack_ruby
    - name: nodejs_buildpack
      package: buildpack_nodejs
    - name: go_buildpack
      package: buildpack_go
    - name: python_buildpack
      package: buildpack_python
    - name: php_buildpack
      package: buildpack_php
    internal_api_password: cloudfoundry
    internal_api_user: internal_user
    jobs:
      app_bits_packer:
        timeout_in_seconds: null
      app_events_cleanup:
        timeout_in_seconds: null
      app_usage_events_cleanup:
        timeout_in_seconds: null
      blobstore_delete:
        timeout_in_seconds: null
      blobstore_upload:
        timeout_in_seconds: null
      droplet_deletion:
        timeout_in_seconds: null
      droplet_upload:
        timeout_in_seconds: null
      generic:
        number_of_workers: null
      global:
        timeout_in_seconds: 14400
      model_deletion:
        timeout_in_seconds: null
    logging_level: debug2
    maximum_app_disk_in_mb: 2048
    maximum_health_check_timeout: 180
    min_cli_version: null
    min_recommended_cli_version: null
    newrelic:
      capture_params: false
      developer_mode: false
      environment_name: null
      license_key: null
      monitor_mode: false
      transaction_tracer:
        enabled: true
        record_sql: obfuscated
    packages:
      app_package_directory_key: <IP_ADDRESS>.xip.io-cc-packages
      cdn: null
      fog_connection: null
      max_package_size:<PHONE_NUMBER>
    quota_definitions:
      default:
        memory_limit: 10240
        non_basic_services_allowed: true
        total_routes: 1000
        total_services: 100
    resource_pool:
      cdn: null
      fog_connection: null
      resource_directory_key: <IP_ADDRESS>.xip.io-cc-resources
    security_group_definitions:
    - name: public_networks
      rules:
      - destination: <IP_ADDRESS>-<IP_ADDRESS>
        protocol: all
      - destination: <IP_ADDRESS>-<IP_ADDRESS>
        protocol: all
      - destination: <IP_ADDRESS>-<IP_ADDRESS>
        protocol: all
      - destination: <IP_ADDRESS>-<IP_ADDRESS>
        protocol: all
      - destination: <IP_ADDRESS>-<IP_ADDRESS>
        protocol: all
    - name: dns
      rules:
      - destination: <IP_ADDRESS>/0
        ports: "53"
        protocol: tcp
      - destination: <IP_ADDRESS>/0
        ports: "53"
        protocol: udp
    srv_api_uri: https://api.<IP_ADDRESS>.xip.io
    stacks: null
    staging_upload_password: cloudfoundry
    staging_upload_user: upload
    system_buildpacks:
    - name: java_buildpack
      package: buildpack_java
    - name: ruby_buildpack
      package: buildpack_ruby
    - name: nodejs_buildpack
      package: buildpack_nodejs
    - name: go_buildpack
      package: buildpack_go
    - name: python_buildpack
      package: buildpack_python
    - name: php_buildpack
      package: buildpack_php
    thresholds:
      api:
        alert_if_above_mb: null
        restart_if_above_mb: null
        restart_if_consistently_above_mb: null
      worker:
        alert_if_above_mb: null
        restart_if_above_mb: null
        restart_if_consistently_above_mb: null
    user_buildpacks: []
    users_can_select_backend: true
  ccdb:
    address: <IP_ADDRESS>
    databases:
    - name: ccdb
      tag: cc
    db_scheme: postgres
    port: 5524
    roles:
    - name: ccadmin
      password: cloudfoundry
      tag: admin
  collector:
    use_tsdb: true
    deployment_name: cf
  opentsdb:
    address: <IP_ADDRESS>
    port: 4567
  databases:
    address: <IP_ADDRESS>
    databases:
    - citext: true
      name: ccdb
      tag: cc
    - citext: true
      name: uaadb
      tag: uaa
    db_scheme: postgres
    port: 5524
    roles:
    - name: ccadmin
      password: cloudfoundry
      tag: admin
    - name: uaaadmin
      password: cloudfoundry
      tag: admin
  dea_next:
    advertise_interval_in_seconds: 5
    allow_host_access: null
    allow_networks: null
    default_health_check_timeout: 60
    deny_networks: null
    directory_server_protocol: https
    disk_mb: 16384
    disk_overcommit_factor: 2
    evacuation_bail_out_time_in_seconds: 600
    heartbeat_interval_in_seconds: 10
    instance_disk_inode_limit: 200000
    kernel_network_tuning_enabled: true
    logging_level: debug
    memory_mb: 4096
    memory_overcommit_factor: 3
    rlimit_core: 0
    staging_disk_inode_limit: 200000
    staging_disk_limit_mb: 4096
    staging_memory_limit_mb: 1024
  description: Cloud Foundry sponsored by Pivotal
  disk_quota_enabled: true
  domain: <IP_ADDRESS>.xip.io
  doppler:
    blacklisted_syslog_ranges: null
    debug: false
    maxRetainedLogMessages: 100
  doppler_endpoint:
    shared_secret: cloudfoundry
  dropsonde:
    enabled: true
  etcd:
    machines:
    - <IP_ADDRESS>
  etcd_metrics_server:
    nats:
      machines:
      - <IP_ADDRESS>
      password: cloudfoundry
      username: nats
  hm9000:
    url: https://hm9<IP_ADDRESS>.191.xip.io
  logger_endpoint:
    port: 4443
  loggregator:
    blacklisted_syslog_ranges: null
    debug: false
    maxRetainedLogMessages: 100
  loggregator_endpoint:
    shared_secret: cloudfoundry
  login:
    analytics:
      code: null
      domain: null
    asset_base_url: null
    brand: oss
    catalina_opts: -Xmx768m -XX:MaxPermSize=256m
    enabled: true
    invitations_enabled: null
    links:
      home: http://console.<IP_ADDRESS>.xip.io
      network: null
      passwd: http://console.<IP_ADDRESS>.xip.io/password_resets/new
      signup: http://console.<IP_ADDRESS>.xip.io/register
      signup-network: null
    messages: null
    notifications:
      url: null
    protocol: http
    restricted_ips_regex: 10\.\d{1,3}\.\d{1,3}\.\d{1,3}|192\.168\.\d{1,3}\.\d{1,3}|169\.254\.\d{1,3}\.\d{1,3}|127\.\d{1,3}\.\d{1,3}\.\d{1,3}|172\.1[6-9]{1}\.\d{1,3}\.\d{1,3}|172\.2[0-9]{1}\.\d{1,3}\.\d{1,3}|172\.3[0-1]{1}\.\d{1,3}\.\d{1,3}
    saml: null
    self_service_links_enabled: null
    signups_enabled: null
    smtp:
      host: null
      password: null
      port: null
      user: null
    spring_profiles: null
    tiles: null
    uaa_base: null
    uaa_certificate: null
    url: null
  metron_endpoint:
    shared_secret: cloudfoundry
  nats:
    address: <IP_ADDRESS>
    debug: false
    machines:
    - <IP_ADDRESS>
    monitor_port: 0
    password: cloudfoundry
    port: 4222
    prof_port: 0
    trace: false
    user: nats
  nfs_server:
    address: <IP_ADDRESS>
    allow_from_entries:
    - <IP_ADDRESS>/16
    - <IP_ADDRESS>/16
    share: null
  request_timeout_in_seconds: 900
  router:
    cipher_suites: TLS_RSA_WITH_RC4_128_SHA:TLS_RSA_WITH_AES_128_CBC_SHA
    enable_ssl: true
    requested_route_registration_interval_in_seconds: 20
    secure_cookies: true
    ssl_cert: '-----BEGIN CERTIFICATE-----

      -----END CERTIFICATE-----

'
    ssl_key: '-----BEGIN RSA PRIVATE KEY-----

      -----END RSA PRIVATE KEY-----

'
    status:
      password: cloudfoundry
      user: router
  smoke_tests: null
  ssl:
    skip_cert_verify: true
  support_address: http://support.cloudfoundry.com
  syslog_daemon_config: null
  system_domain: <IP_ADDRESS>.xip.io
  system_domain_organization: null
  uaa:
    admin:
      client_secret: admin_secret
    authentication:
      policy:
        countFailuresWithinSeconds: null
        lockoutAfterFailures: null
        lockoutPeriodSeconds: null
    batch:
      password: cloudfoundry
      username: batch
    catalina_opts: -Xmx768m -XX:MaxPermSize=256m
    cc:
      client_secret: cloudfoundry
    clients:
      app-direct:
        secret: cloudfoundry
      cloud_controller_username_lookup:
        authorities: scim.userids
        authorized-grant-types: client_credentials
        secret: cloudfoundry
      developer_console:
        secret: cloudfoundry
      doppler:
        authorities: uaa.resource
        override: true
        secret: cloudfoundry
      login:
        authorities: oauth.login,scim.write,clients.read,notifications.write,critical_notifications.write,emails.write,scim.userids,password.write
        authorized-grant-types: authorization_code,client_credentials,refresh_token
        override: true
        redirect-uri: https://login.<IP_ADDRESS>.xip.io
        scope: openid,oauth.approvals
        secret: cloudfoundry
      notifications:
        authorities: cloud_controller.admin,scim.read
        authorized-grant-types: client_credentials
        secret: cloudfoundry
    issuer: https://uaa.<IP_ADDRESS>.xip.io
    jwt:
      signing_key: '-----BEGIN RSA PRIVATE KEY-----

        -----END RSA PRIVATE KEY-----

'
      verification_key: '-----BEGIN PUBLIC KEY-----

        -----END PUBLIC KEY-----

'
    ldap: null
    login: null
    no_ssl: false
    restricted_ips_regex: 10\.\d{1,3}\.\d{1,3}\.\d{1,3}|192\.168\.\d{1,3}\.\d{1,3}|169\.254\.\d{1,3}\.\d{1,3}|127\.\d{1,3}\.\d{1,3}\.\d{1,3}|172\.1[6-9]{1}\.\d{1,3}\.\d{1,3}|172\.2[0-9]{1}\.\d{1,3}\.\d{1,3}|172\.3[0-1]{1}\.\d{1,3}\.\d{1,3}
    scim:
      external_groups: null
      userids_enabled: true
      users:
      - admin|cloudfoundry|scim.write,scim.read,openid,cloud_controller.admin,doppler.firehose
    spring_profiles: null
    url: https://uaa.<IP_ADDRESS>.xip.io
    user: null
  uaadb:
    address: <IP_ADDRESS>
    databases:
    - name: uaadb
      tag: uaa
    db_scheme: postgresql
    port: 5524
    roles:
    - name: uaaadmin
      password: cloudfoundry
      tag: admin
releases:
- name: cf
  version: 205+dev.1
resource_pools:
- cloud_properties:
    instance_type: m1.x2small
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: small_z1
  network: cf1
  size: 3
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.x2small
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: small_z2
  network: cf2
  size: 0
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xsmall
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: medium_z1
  network: cf1
  size: 9
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xsmall
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: medium_z2
  network: cf2
  size: 0
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xmedium
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: large_z1
  network: cf1
  size: 1
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xmedium
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: large_z2
  network: cf2
  size: 0
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xmediumrunner
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: runner_z1
  network: cf1
  size: 2
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xmediumrunner
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: runner_z2
  network: cf2
  size: 0
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xsmall
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: router_z1
  network: cf1
  size: 2
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xsmall
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: router_z2
  network: cf2
  size: 0
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.x2small
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: small_errand
  network: cf1
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
- cloud_properties:
    instance_type: m1.xmedium
  env:
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
  name: xlarge_errand
  network: cf1
  stemcell:
    name: bosh-openstack-kvm-ubuntu-trusty-go_agent
    version: 2889
update:
  canaries: 1
  canary_watch_time: 30000-600000
  max_in_flight: 1
  serial: true
  update_watch_time: 5000-600000
scale:
  jobs:
  - name: runner_z1
    cooldown: 300
    out:
      limit: 3
      conditions:
        - class: CfVarzAverage              # Cloud Foundry Metrics
          varz_job: DEA                     # varz job name
          varz_key: available_memory_ratio  # varz key name
          smaller_than: 20
          duration: 300
    in:
      limit: 1
      conditions:
        - class: CfVarzAverage
          varz_job: DEA
          varz_key: available_memory_ratio
          larger_than: 50
          duration: 300

Could you try to add size: 0 to these resource pools in your manifest?

small_errand
xlarge_errand

Thanks, it fix the errors and BOSH Scaler is correctly started. It seems that I am having some other configuration problems: BOSH Scaler does not scale in/out. I tried both with Openstack and Bosh Lite.
In particular I configured BOSH Scaler with these rule:
  jobs:
  - name: runner_z1
    cooldown: 300
    out:
      limit: 3
      conditions:
        - class: CfVarzAverage              # Cloud Foundry Metrics
          varz_job: DEA                     # varz job name
          varz_key: available_memory_ratio  # varz key name
          smaller_than: 20
          duration: 300
    in:
      limit: 1
      conditions:
        - class: CfVarzAverage
          varz_job: DEA
          varz_key: available_memory_ratio
          larger_than: 40
          duration: 300

and bosh vms --vitals displays about runners:
+------------------------------------+---------+---------------+--------------+-----------------------+------+------+------+---------------+-------------+------------+------------+------------+
| Job/index                          | State   | Resource Pool | IPs          |         Load          | CPU  | CPU  | CPU  | Memory Usage  | Swap Usage  | System     | Ephemeral  | Persistent |
|                                    |         |               |              | (avg01, avg05, avg15) | User | Sys  | Wait |               |             | Disk Usage | Disk Usage | Disk Usage |
+------------------------------------+---------+---------------+--------------+-----------------------+------+------+------+---------------+-------------+------------+------------
| runner_z1/0                        | running | runner_z1     | <IP_ADDRESS>     | 0.78, 0.84, 0.92      | 1.0% | 1.1% | 4.0% | 27% (1022.8M) | 0% (852.0K) | 46%        | 44%        | n/a        |
| runner_z1/1                        | running | runner_z1     | <IP_ADDRESS>     | 0.00, 0.01, 0.05      | 0.1% | 0.0% | 0.2% | 13% (505.0M)  | 0% (64.0K)  | 46%        | 40%        | n/a        |

The available memory should be larger than 40 and if I have understood well I expect that Bosh Scaler will scale in the runner (it will delete runner_z1/1)
The BOSH Scaler log is:
I, [2015-05-21T07:28:45.578165 #26128]  INFO -- : BoshNatsCollector is running
I, [2015-05-21T07:28:45.579310 #26128]  INFO -- : Starting CfVarzTsdbCollector...
I, [2015-05-21T07:28:45.590902 #26128]  INFO -- : NATS connected to mbus://nats:cloudfoundry@<IP_ADDRESS>:4222
I, [2015-05-21T08:30:29.131711 #26326]  INFO -- : Starting...
I, [2015-05-21T08:30:29.198474 #26326]  INFO -- : Starting BOSH Scaler...
I, [2015-05-21T08:30:33.827888 #26326]  INFO -- : BOSH Scaler is running
I, [2015-05-21T08:30:33.828571 #26326]  INFO -- : Starting BoshNatsCollector...
I, [2015-05-21T08:30:34.606640 #26326]  INFO -- : BoshNatsCollector is running
I, [2015-05-21T08:30:34.607826 #26326]  INFO -- : Starting CfVarzTsdbCollector...
I, [2015-05-21T08:30:34.613217 #26326]  INFO -- : NATS connected to mbus://nats:cloudfoundry@<IP_ADDRESS>:4222

Is it possible to see if BOSH Scaler is collecting information from NATS and CfVarz?

Change the logging level to debu. It should output detailed log.
https://github.com/nttlabs/bosh-scaler/blob/master/config/sample.yml#L33

Could you please paste a manifest that you know it is working with Bosh Scaler?

Oops, it's debug, not debu. Actually, the manifest in the README should works.

Make sure that the IP address of your bosh scaler is <IP_ADDRESS> as specified in your manifest.

Yes, the ip address is right and also "debug" option is correctly configured. The log shows that Bosh Scaler is able to receive information from the collector, but not from nats. In particular it is able to connect to nats, but does not collect anything.
In my opinion is a CF configuration problem. Maybe a BOSH/CF manifest that is correctly configured to work with Bosh Scaler could help me in debugging the problem.
Do you have a CF manifest that works with Bosh Scaler?
Thank you

Hmm, I have exactly the same issue - undefined method `-' for nil:NilClass...
I have add 'size: 0' to my cf manifest but error still exists.
After some debug I have found that the problem is in loading manifest.
file: "lib/scaler/listeners/bosh_scaler.rb"
exception thrown by line 69: deployment = Scaler::Deployment.load_yaml(manifest)
But I have no idea why... I have checked 'manifest' variable and it's correct.
It seems like problem is in YAML.load() function...
I am using ruby 1.9.3p551.
I will be grateful for any help or clue.


Deliver does not support 13 inch ipad screen resolution: 2064x2752

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I see the App Store now asks for 13 inch ipad screenshots. I used a iPad Pro M4 with resolution 2064x2752 (which is indicated in appstore connect as valid). However, I do get a error in Fastlane, that the resolution is not supported.
Error: ./fastlane/screenshots-lite/th/13 inch-04-FOO.png - Invalid screen size (Actual size is 2064x2752. See the specifications to fix https://help.apple.com/app-store-connect/#/devd274dd925)

The linked website states that this resolution is valid. So I guess it needs to be added to Fastlane.

Command executed

upload_to_app_store(app_identifier: "bundle.foo, skip_binary_upload: true, skip_metadata: true, overwrite_screenshots:true, screenshots_path: './fastlane/screenshots-foo', ignore_language_directory_validation: true)

Complete output when running fastlane, including the stack trace and command used

[00:23:40]: ------------------------------
[00:23:40]: --- Step: default_platform ---
[00:23:40]: ------------------------------
[00:23:40]: Driving the lane 'ios upload_screenshots_foo' 🚀
[00:23:40]: ---------------------------------
[00:23:40]: --- Step: upload_to_app_store ---
[00:23:40]: ---------------------------------
[00:23:40]: Successfully loaded 'fastlane/Deliverfile' 📄
[00:23:40]: No values defined in './fastlane/Deliverfile'
[00:23:40]: Login to App Store Connect (email@email)
[00:23:42]: Login successful
+--------------------------------------------------------------------+
|                      deliver 2.220.0 Summary                       |
+--------------------------------------+-----------------------------+
| app_identifier                       | bundle.id     |
| skip_binary_upload                   | true                        |
| skip_metadata                        | true                        |
| overwrite_screenshots                | true                        |
| screenshots_path                     | ./fastlane/screenshots-foo |
| ignore_language_directory_validation | true                        |
| metadata_path                        | ./fastlane/metadata         |
| username                             |          |
| platform                             | ios                         |
| edit_live                            | false                       |
| use_live_version                     | false                       |
| skip_screenshots                     | false                       |
| skip_app_version_update              | false                       |
| force                                | false                       |
| screenshot_processing_timeout        | 3600                        |
| sync_screenshots                     | false                       |
| submit_for_review                    | false                       |
| verify_only                          | false                       |
| reject_if_possible                   | false                       |
| version_check_wait_retry_limit       | 7                           |
| phased_release                       | false                       |
| reset_ratings                        | false                       |
| team_id                              |                      |
| dev_portal_team_id                   |                  |
| run_precheck_before_submit           | true                        |
| precheck_default_rule_level          | warn                        |
| precheck_include_in_app_purchases    | true                        |
+--------------------------------------+-----------------------------+
[00:23:43]: 🚫 Invalid screenshots were detected! Here are the reasons:
[00:23:43]: 🚫 Error: ./fastlane/screenshots-foo/zh-Hans/13 inch-01_foo.png - Invalid screen size (Actual size is 2064x2752. See the specifications to fix https://help.apple.com/app-store-connect/#/devd274dd925)
[00:23:43]: 🚫 Error: ./fastlane/screenshots-foo/zh-Hans/13 inch-02_foo.png - Invalid screen size (Actual size is 2064x2752. See the specifications to fix https://help.apple.com/app-store-connect/#/devd274dd925)
[..]

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
14.5

Ruby
2.7.8

Bundler?
true

Git
git version 2.39.3 (Apple Git-146)

Installation Source
~/.rvm/gems/ruby-2.7.8/bin/fastlane

Host
macOS 14.5 (23F79)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.7.8/lib

OpenSSL Version
OpenSSL 1.1.1w  11 Sep 2023

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
15.4

Swift Version
5.10

System Locale

Variable
Value

LANG
nl_NL.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  desc "Update metadata lite"
  lane :update_metadata_lite do
    upload_to_app_store(metadata_path: "fastlane/metadata-lite",app_identifier:"nl.umito.ios.minipiano",  skip_binary_upload: true, skip_metadata: false, skip_screenshots:true)
  end
end

platform :ios do
  desc "Update metadata pro"
  lane :update_metadata_pro do
    upload_to_app_store(metadata_path: "fastlane/metadata-pro",app_identifier: "nl.umito.ios.minipiano.pro", skip_binary_upload: true, skip_metadata: false, skip_screenshots:true)
  end
end

platform :ios do
  desc "Generate new localized screenshots"
  lane :screenshots do
    snapshot(app_identifier: "nl.umito.ios.minipiano")
    # system("sips --rotate 90 screenshots/*/*.png")
#    upload_to_app_store(skip_binary_upload: true, skip_metadata: true)
  end
end

platform :ios do
  desc "Upload screenshots"
  lane :upload_screenshots_lite do

    upload_to_app_store(app_identifier: "nl.umito.ios.minipiano", skip_binary_upload: true, skip_metadata: true, overwrite_screenshots:true, screenshots_path: './fastlane/screenshots-lite', ignore_language_directory_validation: true)
  end
end

`./fastlane/Appfile`
<EMAIL_ADDRESS># Your Apple email address

itc_team_id("525444") # App Store Connect Team ID
team_id("V69H5Z8LUZ") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.220.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.4.0

executable-hooks
1.7.1

bundler-unload
1.0.2

rubygems-bundler
1.4.5

bundler
2.3.13

rake
13.2.1

base64
0.2.0

nkf
0.2.0

rexml
3.2.6

CFPropertyList
3.0.7

public_suffix
5.0.5

addressable
2.8.6

artifactory
3.0.17

atomos
0.1.3

aws-eventstream
1.3.0

aws-partitions
1.929.0

aws-sigv4
1.8.0

jmespath
1.6.2

aws-sdk-core
3.196.1

aws-sdk-kms
1.81.0

aws-sdk-s3
1.151.0

babosa
1.0.4

claide
1.1.0

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.5

domain_name
0.6.20240107

dotenv
2.8.1

emoji_regex
3.2.3

excon
0.110.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.4.1

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.3

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.3.1

gh_inspector
1.1.3

jwt
2.8.1

multi_json
1.15.0

os
1.1.4

signet
0.19.0

googleauth
1.8.1

httpclient
2.8.3

mini_mime
1.1.5

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

google-apis-core
0.11.3

google-apis-androidpublisher_v3
0.54.0

google-apis-playcustomapp_v1
0.13.0

google-cloud-env
1.6.0

google-apis-iamcredentials_v1
0.17.0

google-apis-storage_v1
0.31.0

google-cloud-errors
1.4.0

google-cloud-core
1.7.0

google-cloud-storage
1.47.0

json
2.7.2

mini_magick
4.12.0

naturally
2.2.1

optparse
0.5.0

plist
3.7.1

rubyzip
2.3.2

security
0.1.5

simctl
1.6.10

terminal-notifier
2.0.0

unicode-display_width
2.5.0

terminal-table
3.0.2

tty-screen
0.8.2

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.24.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2024-05-16

I did got to work around it a bit by adding iPad Pro (12.9-inch) (3rd generation) screenshots, that seem also to fall under that category of 13 inch ones. But still the supported resolutions need a update I guess.

same here

Same here. Unable to upload 12.9-inch screenshots. The 12.9-inch screenshots are uploaded to the latest 13-inch iPad incorrectly.

A quick dirty fix: https://github.com/fastlane/fastlane/compare/master...gongzhang:fastlane:master
The most confusing part is that every IOS_IPAD_PRO_12_9 in the code actually refers to the latest 13-inch iPad Pro, while every IOS_IPAD_PRO in the code actually refers to the older 12.9-inch iPad Pro.
Please let me know if I was wrong.

When will this bug be availble in official fastlane release?


[2/n] [FlexiRaft] Implementation of flexible vote counter

The diff extends the VoteCounter to include the more generic FlexiRaft proposal for leader elections. A few more restrictions need to be put in place but they would be done in separate commits.
https://fb.workplace.com/groups/2221310364783502/permalink/2494430674138135/

Please remove the workplace link from the description. This is an open source repo.


Deprecate control plane self-hosted etcd

Feature Request
Problem
Self-hosted etcd is still marked as experimental by bootkube, and the actual pivot between the on host etcd and self-hosted etcd a significant chunk of the startup time for bootkube clusters (~20%). Anecdotally, I've also seen self-hosted clusters fail, which was part of the inspiration for the bootkube recover sub-command.
Desired Behavior
Support on-host etcd clusters. Possibly either by provisioning separate machines, or having the etcd instances living on the masters. Etcd instances on the master nodes has an attractive aspect of reduced overhead, but might not be optimal due to masters living in an auto-scaling group.
Tradeoffs
Etcd doesn't behave well in an auto-scaling group.[1] This might be alleviated by talking to the cloud provider or not supporting expanding the number of masters, but is worth investigation on its own. Bootstrapping needs a concrete, cross cloud solution, and re-balancing must survive reboots and adding new members after the initial cluster is formed.
A large chunk of this feature is determining how best to bootstrap and manage the etcd cluster.
[1] https://crewjam.com/etcd-aws/

I'd like to do some initial exploration, so please feel free to assign me for now.

The self-hosted etcd problems are outlined in FAQ https://typhoon.psdn.io/faq/#self-hosted-etcd The plan is to revert back to etcd on controllers (not an instance group), which is how we were doing it before self-hosted etcd came along.

I've dropped self-hosted etcd as an option on bare-metal and will begin removing it from cloud clusters. In the mean time, I've had one AWS (alpha) cluster crash related to self-hosted etcd.
https://github.com/coreos/etcd-operator/issues/731
https://github.com/kubernetes/kubernetes/issues/40973

Digital Ocean now uses on-host (i.e. on-controller) etcd. #32

AWS now uses on-host etcd. #53
All platforms now use on-host etcd across controllers. Self-hosted etcd is no longer used. Clusters should be more stable, reliable, and bootstrap times are much nicer (< 6min).


Updating the kong enterprise documentation

Adding content to support deployment of AIO on Kind so that developers can try this on local environments if they want to have a play.
Summary
I have added documentation to support deployment of Kong Ingress controller with Kong enterprise on Kind.
Reason
I believe it will help developer try our Kong enterprise locally on their machine with Kind. Not every one will have access to cloud infrastructure to try KIC and Kong enterprise. This hopefuly will give them the opportunity to try the product locally and get an understanding of the components.
Testing
Follow the steps indicated with ### For kind heading.

@Kong/team-k8s could you please take a look at this doc submission?

@rajeevkong thanks for this submission. 🤜 🤛
As indeed documenting Kind specifics might be useful for developers, I'd only point out that we should make sure that's stated clearly somewhere it is not an officially supported way of deployment.
Also, I think we might consider having a separate article for that (similar to Kong Ingress on Minikube) as the content regarding Kind isn't really specific only to the enterprise deployment, right? It could contain a full set of instructions for setting up the Kind cluster and so on in a linear fashion instead of conditional sections like in the currently modified article. WDYT?

Hey @Grzegorz Burzyński @.***> ,
I think the suggestion for a separate article makes a lot of sense and I
think it's the right approach. Please let me know if there is anything you
need from me.
Regards
Rajeev
On Fri, Jan 13, 2023 at 4:53 PM Grzegorz Burzyński @.***>
wrote:

@rajeevkong https://github.com/rajeevkong thanks for this submission. 🤜
🤛
As indeed documenting Kind specifics might be useful for developers, I'd
only point out that we should make sure that's stated clearly somewhere it
is not an officially supported way of deployment.
Also, I think we might consider having a separate article for that
(similar to Kong Ingress on Minikube
https://docs.konghq.com/kubernetes-ingress-controller/latest/deployment/minikube/)
as the content regarding Kind isn't really specific only to the enterprise
deployment, right? It could contain a full set of instructions for setting
up the Kind cluster and so on in a linear fashion instead of conditional
sections like in the currently modified article. WDYT?
—
Reply to this email directly, view it on GitHub
https://github.com/Kong/docs.konghq.com/pull/5030#issuecomment-1381708573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A26ZL4OOVSM25DXF5GLV74TWSE3JPANCNFSM6AAAAAATYWDMFY
.
You are receiving this because you were mentioned.Message ID: <Kong/docs.
@.***>

--
Regards
https://konghq.com/ Rajeev Ramani (he/him)
APIs | Mesh | Microservices @ Kong http://konghq.com/

@rajeevkong adapting content into a separate KIND-focused article, a la the GKE-specific deployment guide would work. Would you be up for writing a guide that covers deploying to KIND environment?
Something that starts linking to the general KIND environment setup guide and then proceeds with instructions to install a basic Kong deployment atop that local cluster should work as a good starting point--from there you can add the various KIND node patches to set up the network environment and then deploy Kong (some of what you have in the PR already, minus the non-KIND branches).

Sounds good to me @Travis Raines @.***>. Happy to contribute
in any way. Could you help me understand the process for submitting a new
page and I am more than happy to put the doc together.
Just a note / suggestion that on this page
https://docs.konghq.com/gateway/3.1.x/install/kubernetes/helm-quickstart/
the kind install is provided as a tab. This was the reason for my
suggestion. Maybe we can make the pages more consistent and similar in the
layout and menus.
Regards
Rajeev
On Sat, Jan 14, 2023 at 1:12 AM Travis Raines @.***>
wrote:

@rajeevkong https://github.com/rajeevkong adapting content into a
separate KIND-focused article, a la the GKE-specific deployment guide
https://docs.konghq.com/kubernetes-ingress-controller/latest/deployment/gke/
would work. Would you be up for writing a guide that covers deploying to
KIND environment?
Something that starts linking to the general KIND environment setup guide
https://kind.sigs.k8s.io/docs/user/quick-start/ and then proceeds with
instructions to install a basic Kong deployment atop that local cluster
should work as a good starting point--from there you can add the various
KIND node patches to set up the network environment and then deploy Kong
(some of what you have in the PR already, minus the non-KIND branches).
—
Reply to this email directly, view it on GitHub
https://github.com/Kong/docs.konghq.com/pull/5030#issuecomment-1382313659,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A26ZL4NGNC6FPRKBLR7J2OLWSGV4FANCNFSM6AAAAAATYWDMFY
.
You are receiving this because you were mentioned.Message ID: <Kong/docs.
@.***>

--
Regards
https://konghq.com/ Rajeev Ramani (he/him)
APIs | Mesh | Microservices @ Kong http://konghq.com/

@rajeevkong to add a new page you'd add a new file similar to one of the existing documents under https://github.com/Kong/docs.konghq.com/tree/main/app/_src/kubernetes-ingress-controller/deployment
And then add a TOC entry for it under https://github.com/Kong/docs.konghq.com/blob/main/app/_data/docs_nav_kic_2.8.x.yml#L42-L63
@lena-larionova did ya'll have any thoughts @rajeevkong's organization question? We do have tabbed guides in some places but I think we'd probably add a new page here given that there are docs for various other platforms.

@rajeevkong @rainest I think having a separate doc sounds like a good plan. Mainly because of this:

Also, I think we might consider having a separate article for that (similar to Kong Ingress on Minikube) as the content regarding Kind isn't really specific only to the enterprise deployment

That way this new content isn't buried in the Enterprise topic and is easier to track down.
You make a good point about the consistency of our install/setup topics - we know this is a painpoint, and we have plans to fix that up in the future.

Hey folks,
I am on leave but will try and get the documentation sorted by next week.
On Tue, 24 Jan 2023 at 12:37 am, lena-larionova @.***>
wrote:

@rajeevkong https://github.com/rajeevkong @rainest
https://github.com/rainest I think having a separate doc sounds like a
good plan. Mainly because of this:
Also, I think we might consider having a separate article for that
(similar to Kong Ingress on Minikube
https://docs.konghq.com/kubernetes-ingress-controller/latest/deployment/minikube/)
as the content regarding Kind isn't really specific only to the enterprise
deployment
That way this new content isn't buried in the Enterprise topic and is
easier to track down.
You make a good point about the consistency of our install/setup topics -
we know this is a painpoint, and we have plans to fix that up in the future.
—
Reply to this email directly, view it on GitHub
https://github.com/Kong/docs.konghq.com/pull/5030#issuecomment-1400838013,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A26ZL4M37SIFAN6KAXIRJNTWT3JGXANCNFSM6AAAAAATYWDMFY
.
You are receiving this because you were mentioned.Message ID: <Kong/docs.
@.***>

--
Regards
https://konghq.com/ Rajeev Ramani (he/him)
APIs | Mesh | Microservices @ Kong http://konghq.com/

Hey Diana,
My apologies for the delay, I have submitted a new pull request with the
documentation in a new page. Let me know if its ok.
Regards
On Thu, Mar 30, 2023 at 4:07 AM Diana @.***> wrote:

@rajeevkong https://github.com/rajeevkong Hi! Just checking in to see
if you've had time to work on the documentation for this. Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/Kong/docs.konghq.com/pull/5030#issuecomment-1488985371,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A26ZL4IU3XULEINK745ZRZ3W6RT6XANCNFSM6AAAAAATYWDMFY
.
You are receiving this because you were mentioned.Message ID: <Kong/docs.
@.***>

--
Regards
https://konghq.com/ Rajeev Ramani (he/him)
APIs | Mesh | Microservices @ Kong http://konghq.com/
+61 431588242
https://konghq.com/events/labyrinth-foundations-intro-to-end-to-end-connectivity

No worries @rajeevkong ! Thanks for making those updates :)

Thanks Diana, I made a small correction and pushed the change..
On Fri, Mar 31, 2023 at 12:23 AM Diana @.***> wrote:

No worries @rajeevkong https://github.com/rajeevkong ! Thanks for
making those updates :)
—
Reply to this email directly, view it on GitHub
https://github.com/Kong/docs.konghq.com/pull/5030#issuecomment-1490297777,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A26ZL4PVDR5HUEZHO4I5Z7LW6WCLPANCNFSM6AAAAAATYWDMFY
.
You are receiving this because you were mentioned.Message ID: <Kong/docs.
@.***>

--
Regards
https://konghq.com/ Rajeev Ramani (he/him)
APIs | Mesh | Microservices @ Kong http://konghq.com/
+61 431588242
https://konghq.com/events/labyrinth-foundations-intro-to-end-to-end-connectivity

Closing in favour of https://github.com/Kong/docs.konghq.com/pull/5365


slice username & domain from email address

This code snippet would help the user to slice the username and domain from an email address.

Hi, maintainers of 30-seconds-of-python!
Please have a look into this PR. :)
Thanks,
thevirtualbuddy

Hi @Trinityyi ,
Could you please review this PR?


fix bundle conf

Fix the custom conf overrided by an empty array.

Rejecting. This avoid parse all the config even if it is valid. I will explain you in the other issue.

@shakaran I doubt that the $container->getExtensionConfig($this->getAlias()); parse anything.
Check the function content :
    public function getExtensionConfig($name)
    {
        if (!isset($this->extensionConfigs[$name])) {
            $this->extensionConfigs[$name] = array();
        }

        return $this->extensionConfigs[$name];
    }


"Compile and Display JS" command for Sublime Text 2

Added the equivalent of the Textmate "Compile and Display JS" for Sublime Text 2.

Those are all Textmate commands. They shouldn't be expected to run in Sublime Text 2, as far as I understand.


[BACKLOG-15953] Adding getRowFrom/putRowTo to RowHandler

http://jira.pentaho.com/browse/BACKLOG-15953

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/step/BaseStep.java
  engine/src/org/pentaho/di/trans/step/RowHandler.java
  engine/src/org/pentaho/di/trans/step/messages/messages_en_US.properties
  engine/test-src/org/pentaho/di/trans/step/BaseStepTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.trans.step.BaseStep

Complexity Change:  + .23%
Instruction Change:  + .11%
Line Change:  + .08%
Method Change:  + .39%

org.pentaho.di.trans.step.BaseStep.DefaultRowHandler

Complexity Change:  + 8.33%
Instruction Change:  + 12.15%
Line Change:  + 11.11%
Method Change:  + 8.33%

org.pentaho.di.trans.step.RowHandler

Complexity New Coverage: 100.00%
Instruction New Coverage: 100.00%
Line New Coverage: 100.00%
Method New Coverage: 100.00%

org.pentaho.di.trans.step.StepMeta

Branch Change:  + .68%
Complexity Change:  + .58%
Instruction Change:  + .19%
Line Change:  + .26%

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change:  + .04%

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -.09%:small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change:  + .11%

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change:  + .31%
Instruction Change:  + .06%
Line Change: -.23%:small_red_triangle_down:
Method Change: -1.02%:small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2.08%:small_red_triangle_down:
Complexity Change: -2.11%:small_red_triangle_down:
Instruction Change: -.28%:small_red_triangle_down:
Line Change: -.74%:small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change:  + .05%

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change:  + .06%

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change:  + .18%

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.33%:small_red_triangle_down:
Complexity Change: -1.85%:small_red_triangle_down:
Instruction Change: -.28%:small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -.18%:small_red_triangle_down:

org.pentaho.di.trans.Trans

Branch Change:  + .10%
Complexity Change:  + .14%
Instruction Change:  + .09%
Line Change:  + .11%

@hudak


UPNP broadcasts on non-LAN interface

OPNsense 22.7.4
OPNsense have 2 interfaces - LAN (hn1) and WAN (hn0).
WAN interface is of type PPPoE (pppoe0).
UPNP plugin is installed.
UPNP External Interface is set to WAN.
UPNP Interfaces is set to LAN.
tcpdump -i hn0 -n port 1900
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on hn0, link-type EN10MB (Ethernet), capture size 262144 bytes
23:01:44.080662 IP <IP_ADDRESS>.33861 > <IP_ADDRESS>.1900: UDP, length 446
23:01:44.080849 IP <IP_ADDRESS>.33861 > <IP_ADDRESS>.1900: UDP, length 455
23:01:44.081003 IP <IP_ADDRESS>.33861 > <IP_ADDRESS>.1900: UDP, length 518
23:01:44.081514 IP <IP_ADDRESS>.57158 > <IP_ADDRESS>.1900: UDP, length 510
...
<IP_ADDRESS> is the LAN (hn0) interface IP address. Tried using other LAN addresses and the source of the captured traffic changes accordingly.
hn0 interface is not assigned at all and is not supposed to send anything except PPPoE packets.
UPNP plugin is currently broadcasting your LAN interface address on the WAN interface.
It has not been tested if UPNP will act and how if a response is received on hn0 interface.

I can't replicate this on 22.7.4


Are Kit Versions used?

https://github.com/genesis-community/cf-genesis-kit/blob/master/kit.yml#L3
That shows the cf-genesis-kit to be at v0.0.1, but released versions are up to 0.2.4.

I do not think it is used any where, all the rest of kits do not specicify kit version in kit.yml.
It is nice to have kit version somewhere and being used


Bug: Text was duplicating it for all users

Bug is fixed by setting it to random example: sdufs.txt

deleted the repo my fault


cog example (fixed code and RESTORED FILES)

Summary

Checklist

[ ] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[x] This PR is not a code change (e.g. documentation, README, ...)

3 prs

im sorry first timer 🤷🏻♂🤷🏻♂😂😭

Can you make explanation not suck I suppose?

😭😭😭 do i have to make a whole paragraph of this ???


Docs fix spelling issues

Hello
I fixed several minor spelling issues.
Glad I could help
Br, Elias.

This account @nnsW3  looks like farming airdrops through spellcheck PRs

@metachris  I am trying to help with the knowledge that I have. I am passionate about this space but I can't make more meaningful contribution than this for the moment....


[TimePicker] fix issue where clock does not render in timepicker nested in dialog

This PR fixes #1398
Having a TimePicker component in a Dialog component currently renders like this:

This PR resolves this issue so that it now renders like this:

Is adding <!doctype html> in your index solving this issue?
However, I'm wondering why we have this height: '100%'.

@oliviertassinari yes, that works too! but it does seem like removing height: '100%' works with or without <!doctype html>

Looks like all the root style is useless.
Could you be more aggressive and remove the first <div> that is rendered with all the dead code that comes with it?

@ryannyunn Thanks for raising this issue. It's continued here https://github.com/callemall/material-ui/pull/3591.


Add option to enable default websocket deployment info.

This would be helpful if using undertow to serve a vaadin application with atmosphere.
So in the server definition you could say:
           DeploymentInfo servletBuilder = deployment()
              .setClassLoader(Main.class.getClassLoader())
              .setContextPath(MYAPP)
              .setDeploymentName("vaadin.war")
              .setResourceManager(new FileResourceManager(new File("src/main/webapp"), 1024))
              .enableDefaultWebsocket(true)
              .addServlets(
                servlet("MyUIServlet", MyUI.MyUIServlet.class)
                  .setAsyncSupported(true)
                  .addMapping("/*"));

instead of this adding boilerplate like so:
            DeploymentInfo servletBuilder = deployment()
              .setClassLoader(Main.class.getClassLoader())
              .setContextPath(MYAPP)
              .setDeploymentName("vaadin.war")
              .setResourceManager(new FileResourceManager(new File("src/main/webapp"), 1024))
              .addServlets(
                servlet("MyUIServlet", MyUI.MyUIServlet.class)
                  .setAsyncSupported(true)
                  .addMapping("/*"));

            WebSocketDeploymentInfo webSocketDeploymentInfo = new WebSocketDeploymentInfo();
            servletBuilder.addServletContextAttribute(WebSocketDeploymentInfo.ATTRIBUTE_NAME, webSocketDeploymentInfo);

Can one of the admins verify this patch?

This would need to use some kind of service loader based approach to make this work as websockets depends on Servlet and not the other way around. Given that the boilderplate is only a single line (no need to assign it to a variable first ) I don't think this this woth it.


Expose getInitialCropFromCroppedArea[Percentages|Pixels] functions

When working with the cropper, it is helpful to be able to align the media with a specific edge of the crop box. Forwarding these two functions to the user would allow one to simply derive the intended croppedAreaPercentages or croppedAreaPixels and pass them on to their respective methods to get the required crop and zoom values. I didn't want to use the initialCroppedAreaPixels/Percentages because it is currently only called when the assets are loaded and would require unloading/reloading the assets.
Working example on CodeSandbox: https://codesandbox.io/s/react-easy-crop-forked-3v0hi3
Definitely open to suggestions if passing the mediaSize and cropSize values up to the parent is frowned-upon.

Not sure why the extra commits are showing as those should have already been merged. I think it has to do with how I merged upstream changes.

Thanks for this PR!
This is definitely intended for advanced usage but I think this is a valid use case with little changes on the API.
Could you please add the 2 new props to the Readme with maybe a mention to your codesandbox example?

@ValentinH Absolutely. I will push an update shortly.

@ValentinH I believe this should be ready to merge. Let me know if you need anything else from me.


Multi-threading flash access is not supported by flash_write_protection_set()

The problem
When two or more threads writes to flash device it is possible that flash protection will be enabled by one of threads despite another thread(s) still needs it disabled.
Impact
flash_write() or flash_erase() operation might fail unexpectedly while flash device is written or erased from multiple thread. This will be race condition.
Solution
Remember that below code is allowed:
flash_write_protection_set(flash_dev, false);
flash_erase(flash_dev, page_offset, page_size);

flash_write_protection_set(flash_dev, false);
flash_write(flash_dev, offset, data, sizeof(data));

flash_write_protection_set(flash_dev, true); // enable is recommended

Count flash protection disable/enable operation (with thread instance awareness, a thread might only increase/decrease counter by one).
Re-enable protection only once is zero.

cc @anangl @carlescufi

cc @anangl @carlescufi

@nvlsianpu I think that stream_flash has similar problem on higher level.

@nvlsianpu Your proposed solution would not work for flash chip that automatically enables write protection after write or erase command.
I have a custom board with such a flash chip and I'm impacted by this bug. The only solution I found so far is to hack the driver so that the lock is acquired by flash_write_protection_set(flash_dev, false); and released by flash_erase or flash_write. flash_write_protection_set(flash_dev, true); is a no-op for such flash.

IMHO the only proper way to address this problem is to change the flash API. Removing the flash_write_protection_set function and changing flash_erase and flash_write so that they acquire the lock, disable the write protection do the erase/write operation, enable the write-protection and finally release the lock.

@armandciejak

@nvlsianpu Your proposed solution would not work for flash chip that automatically enables write protection after write or erase command.

I think you understand me bad. I put the code sample in the description (same here https://docs.zephyrproject.org/latest/reference/peripherals/flash.html#c.flash_write_protection_set) - this code sample reflect usage with the automatic flash protection your mentioned, that why ther are dedicated flash disable calls before each write/erase operations. Solution I suggested will work for this case as well.
API change you mentioned is also possible solution worth to be considered.

@nvlsianpu, the thread awareness seems unnecessary complex. Maybe it is better to make flash_write_protection_set a nop and to include this in flash_write and flash_erase.

@Laczen Agree, that will be much simpler but requires modification in each driver. I would go this way. Probably need to first present this on the API meeting.


Release Google.Cloud.Batch.V1Alpha version 1.0.0-alpha30

Changes in this release:
New features

Add block_project_ssh_keys field to the v1alpha job API to block project level ssh keys access to Batch created VMs (commit 3a1b85f)
Remove visibility restriction of cancel job api, allow in v1alpha (commit 3a1b85f)
Update Go Datastore import path (commit 3a1b85f)
Update Go Bigtable import path (commit 3a1b85f)

Documentation improvements

Refine usage scope for field task_execution and task_state in status_events (commit 3a1b85f)
Add instructions on how to configure cross-project pubsub publisher (commit 5e272cf)
Document default disk type: pd-standard for non boot disk, pd-balanced for boot disk (commit 5e272cf)
Update list of volume.mount_options field (commit 5e272cf)
Update GCS description of volume.mount_options field (commit 5e272cf)
Update links in the description of volume.mount_options field (commit 5e272cf)

Created release for Google.Cloud.Batch.V1Alpha-1.0.0-alpha30


Help? - CSS Conflicts with jquery css Used for Collapsible Blocks

[x] This is a question about using the theme.

Hello,
First of all, I'm using your theme for my small personal/professional blog and it's great! thanks so much for sharing your good work. Now, please excuse me in advance if this is more of an issue of my education on web development than an issue with the theme. Either way, help or good references would be greatly appreciated.
My problem is in this post specifically: http://danieljumper.com/used_car_pricing_trends_1/. I used jquery for collapsible code blocks as implimented in this example. It seems that using this style sheet:

<link rel="stylesheet" href="https://code.jquery.com/mobile/1.4.5/jquery.mobile-1.4.5.min.css">

Is necessary for the proper collapsing block behavior, but it conflicts with aspects of the page style. For example, Font size and link colors are different and the background color on the page header (and other places) is white instead of slightly off-white.
I tried to investigate how to handle CSS conflicts, but i'm not very educated on the issue. The way I implimented the collapsing feature is by including the  <link rel="stylesheet" in the post .md file itself. I tried instead, including the .css file in the compiled webpage code attempting to order it after the rest of the stylesheets to give other styles precedent. But giving other stylesheets priority ruins the collapsing block behavior (they show up as expanded on page load and don't collapse). I tried to grep the stylesheet contents to find where the collapse specific tags are implimented and just use that part of the stylesheet but I was unsuccessful in finding the proper section.
I'd love to keep using this collapsing box feature, but i hate how it's mildly ruining the page style. Do you have any suggestions or fixes for me here?
Thanks!

You had the right idea trying to change the source order of the jQuery mobile CSS file, it definitely is overriding some of the theme's styles like  text color and the background due to the cascade.
To do it right I think you'll have to add just the styles for the accordion and stay away from anything that might impact the theme globally. But if you're not all that familiar with CSS that can be tricky.
Maybe try a simpler accordion. There's a fairly well supported "checkbox" accordion you can hack together that doesn't require any sort of JavaScript. It's purely CSS.
I use a version of it on my personal site to do a collapsible "Table of Content" (example: https://mademistakes.com/articles/using-jekyll-2016/)
There's several examples with code on Codepen.io if you want to try that method instead.
http://codepen.io/search/pens?q=accordion css&limit=all&order=popularity&depth=everything&show_forks=false

Hi Michael. Thanks for the help (and especially such a quick reply!).
I appreciate the references - I'll do some reading there. I'll have to refresh my memory because it was a little while ago that I first did this, but a constraint I had was that I wanted to use markdown for code syntax highlighting INSIDE the pull down box. So I had html in the post .md file, but then wanted markdown inside that html. I think the solution I found at the end of the day was to use
 content
 inside the accordion html chunk. And I think this should be compatible with most CSS implementations you referenced?
One last thing, can I impose on you again to get a kick in the right direction for implementing CSS accordian? Is the right order of affairs to add a new css file to ./sass/<accordian css (scss?) file> and then add an @import  "<accordian css(scss?) file>"; line to ./assets/css/main.scss? On a separate note, I'm learning about but not greatly familiar with SASS. Can I get by with just renaming .css files to .scss in ./sass/? I think that's what I did when attempting to include the jQuery mobile CSS.
Thanks again and sorry for the basic level questions! You're very kind to help.

Yes you'll likely need to wrap HTML

 in your Markdown file if Kramdown doesn't parse it correctly. It usually has trouble with indented HTML because it treats it like a blockquote or code block. Usually takes some trial and error to get that all sorted.
And yes that's the correct way to approach getting the accordion (or any other CSS modules you add) into the main stylesheet. Just add it as _whatever.scss to the _sass folder then @import it in /assets/css/main.scss.
It's perfectly fine to just change a .css file to .scss without making any other changes. That's one of the benefits of using SCSS over SASS. It's just standard CSS... where you can add all the extra stuff like variables, mixins, etc.

Excellent, sounds good. Once I get everything fixed and working properly on my end I'll leave a final update for posterity and close the issue. Thanks a ton!

Closing this issue as it appears to be addressed. If not feel free to re-open.


Interact with multiple rocks at the same time

luarocks install luasocket luafilesystem moonscript lapis

luarocks upgrade luasocket luafilesystem moonscript lapis

luarocks remove luasocket luafilesystem moonscript lapis

The above would be very handy additions, allowing you to queue up a bunch of packages at once instead of needing to install them one at a time.
Example: A project I have has several dependencies and I would like to be able to tell people to simply copy/paste a line to install them all.
https://github.com/karai17/lapis-chan#other-stuff

This is not the first time we get this feature request. Unfortunately, this can't be added without breaking compatibility, because the second argument after the rock name is interpreted as being the version number.

What about comma delimiting?
On Jun 22, 2016 03:41, "Hisham Muhammad"<EMAIL_ADDRESS>wrote:

This is not the first time we get this feature request. Unfortunately,
this can't be added without breaking compatibility, because the second
argument after the rock name is interpreted as being the version number.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keplerproject/luarocks/issues/573#issuecomment-227656933,
or mute the thread
https://github.com/notifications/unsubscribe/AAkB_D4G_7R8DU2oF9zYYMogQm29Aa0Rks5qONkEgaJpZM4I7Z8S
.

It seems to me that the correct solution for your problem would be for you to write a rockspec for your project and specify your dependencies in it. Also, it would allow you to specify supported version ranges for your dependencies, which is missing from the instructions. (How do you know an incompatible version of any of these modules won't be released tomorrow, breaking your current build instructions?)

Problem is my project relies on more than just a few Lua modules, as noted
in my readme. Seems like only a half-measure to write a rockspec. Not to
mention my project wouldn't exactly run if it were installed via LuaRocks,
it needs to be installed in a web serving directory, or at leas tin a
directory that you can modify (config files, among others).
LuaRocks is supposed to be a package manager, and thus is should probably
take on some of these standard features that other package managers have.
Perhaps instead of having a second argument for version, a worthwhile
breaking change could be to append versions to the package name:
luarocks install moonscript installs the latest version
luarocks install moonscript-1.3.0-1 installs the version desired

Landon Manning
<EMAIL_ADDRESS>On 22 June 2016 at 14:27, Hisham Muhammad<EMAIL_ADDRESS>wrote:

It seems to me that the correct solution for your problem would be for you
to write a rockspec for your project and specify your dependencies in it.
Also, it would allow you to specify supported version ranges for your
dependencies, which is missing from the instructions. (How do you know an
incompatible version of any of these modules won't be released tomorrow,
breaking your current build instructions?)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keplerproject/luarocks/issues/573#issuecomment-227816916,
or mute the thread
https://github.com/notifications/unsubscribe/AAkB_MuHO6d7qKvjsqyUrzwcDmOUd2Htks5qOXBqgaJpZM4I7Z8S
.

LuaRocks is supposed to be a package manager

Nice.

@karai17 if your project has to be installed in a complicated way it's better to use something like a requirement file, which can be simulated using an empty rockspec, see #266.

@hishamhm am I wrong in this?
@mpeterv I'll look into this.