Translate Filters in  ES DSL to Yaml

Hi member. I'm developing an visualization page to configure ES DSL of Yaml.
As I hava a lot of search in use in Yaml，and we are just familiar with Yaml，I want to let my users write, test and save their queries in Yaml, then I read their Yaml searches and parse the filter field in es-alert rule.yaml.
There is an question that how does ES DSL translates filters into Yaml?
Wishing your help and think u.
ES DSL：
{
  "title": "test",
  "type": "table",
  "params": {
    "perPage": 10,
    "showPartialRows": false,
    "showMeticsAtAllLevels": false,
    "sort": {
      "columnIndex": null,
      "direction": null
    },
    "showTotal": false,
    "totalFunc": "sum"
  },
  "aggs": [
    {
      "id": "1",
      "enabled": true,
      "type": "count",
      "schema": "metric",
      "params": {}
    },
    {
      "id": "2",
      "enabled": true,
      "type": "terms",
      "schema": "bucket",
      "params": {
        "field": "fields_logs.remote_addr.keyword",
        "otherBucket": false,
        "otherBucketLabel": "Other",
        "missingBucket": false,
        "missingBucketLabel": "Missing",
        "size": 10,
        "order": "desc",
        "orderBy": "1",
        "customLabel": "ip"
      }
    }
  ]
}

Is this the same question as #1794 ? If you're asking how to convert arbitrary queries into ElastAlert filters, you can't. ElastAlert only supports bool filters and single aggregations.


Release 0.31 preparation

Do they need to be updated? Would we need to update the script that changes the tag?

Good question. If one were to clone our release branch, build an image, save it to container cache and then run a demo yaml, the Pod wouldn't start due to ErrImagePull or similar.
In that sense, yes, I think those yamls should also be updated with the version number. On the other hand, the set-version script has been similar for a quite a long time and we haven't received any issues, so it's probably not a big thing. :)

Do they need to be updated?
Would we need to update the script that changes the tag?

These images are not published and they are not used in e2e tests either so the current config is expected.


Refactor all call functions

Refactors call, callCont, protectedCall, and protectedCallCont to accept a struct of arguments rather than parameters. This improves documentation at the call site.

Merged locally


Support contingency table historical backfill

At the moment, contingency tables are only available for 2021. We would like tables to also be available for 2020. To do so, we need to:

[x] Make sure mental health indicators aren't generated for pre-Wave 4 surveys
[ ] Report symptom, social distancing, and travel indicators
[ ] Add in avoiding contact with others
[ ] Report any other indicators the API reports for 2020
[x] Make sure that empty tables aren't reported

Make sure mental health indicators aren't generated for pre-Wave 4 surveys

Added nohh_cmnty_cli and others_masked. Did not add inperson_school_<full/parttime>

Add in avoiding contact with others

@capnrefsmmat which "avoiding contact" indicator/s were you thinking of?
The API reports the shopping, visit a restaurant, use public transit, work not-from-home, etc indicators based on C13, but those are already included in the contingency tables.
Item C11 (“In the past 24 hours, have you had direct contact with anyone who recently tested positive for COVID-19 (coronavirus)?”) is already reported in contingency tables, but not in the API.
Item C7 (“To what extent are you intentionally avoiding contact with other people?”) and replacement C7a (“how often did you intentionally avoid contact with other people?") were never used for any API indicators.

I think we could add C7/C7a just because it's interesting, but it looks like we have all the important contact items already.


Errors in docs on spacy.io label:docs

Section Navigating the Parse Tree does not include dep\dep_ - universal dependency label.
It would also be nice to have an overview for Token class like there is one for Span and all other classes.
Example in section Doc.ents. The last line has no meaning. It is always True.

Thanks! Fixed in the website source.


L+R and U+D are not mutually exclusive

Minor issue that affects some games like Battletoads. See http://forums.nesdev.com/viewtopic.php?t=711

Closed by 388b6e8


feat(nargo)!: Require package type be specified in Nargo.toml

Description

Problem*

Resolves #2073
Summary*

This adds the type field to the Nargo.toml file, which is required. We use this to determine what the default entry point file should be but it also opens up the ability to allow custom paths (as per #2076) because we'll know what package type is represented by the custom path.
As a matter of cleanup and separation of concerns, this also moves the CrateType into Nargo as PackageType and adds some helpful error messages if a project is configured incorrectly (such as a missing main function when running nargo check against a binary package). These changes enable us to add a contracts package type for #2075
Since we want to generate library and binary crates, this adds --lib and --bin to the nargo new and nargo init commands to generate an appropriate project.
Documentation

[x] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[x] I will request for and support Dev Rel's help in documenting this PR.

The required type field needs to be documented when we document the Nargo.toml file and we need to add the new flags for new and init commands.
Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

This has been rebased on https://github.com/noir-lang/noir/pull/2157 to show the usage of the trait.


Improve data caching with datetime objects

No need to convert a datetime string to a DateTime object until it is required to be returned as zval. For caching only datetime strings are needed.

Coverage increased (+0.001%) to 74.08% when pulling<PHONE_NUMBER>ac0bfd1a99dcea84969a4a24314de3 on yitam:dtCache into c0cf381d6c9643e3ae1b0f754ce1cb6e8750d3b0 on microsoft:dev.

Codecov Report

Merging #1008 into dev will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev    #1008      +/-   ##
==========================================
- Coverage   78.71%   78.67%   -0.05%
==========================================
  Files          25       25
  Lines        8133     8136       +3
==========================================
- Hits         6402     6401       -1
- Misses       1731     1735       +4

Impacted Files
Coverage Δ

...php-7.1.30-src/ext/pdo_sqlsrv/shared/core_sqlsrv.h
79.53% <0%> (-1%)
:arrow_down:

...php-7.1.30-src/ext/pdo_sqlsrv/shared/core_stmt.cpp
78.15% <0%> (-0.09%)
:arrow_down:

...x86/php-7.1.30-src/ext/sqlsrv/shared/core_stmt.cpp
84.46% <0%> (-0.04%)
:arrow_down:

...c14/x86/php-7.1.30-src/ext/pdo_sqlsrv/pdo_stmt.cpp
84.61% <0%> (-0.04%)
:arrow_down:

...x86/php-7.1.30-src/ext/sqlsrv/shared/core_sqlsrv.h
81.16% <0%> (ø)
:arrow_up:

...x86/php-7.1.30-src/ext/sqlsrv/shared/core_util.cpp
48.13% <0%> (+1.61%)
:arrow_up:

...php-7.1.30-src/ext/pdo_sqlsrv/shared/core_util.cpp
46.05% <0%> (+2.14%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c0cf381...8041345. Read the comment docs.


typo in readme requirements

Table in https://github.com/VLL-HD/FrEIA#dependencies says "Pythton", I assume it's a typo

Thank you kindly! I have just fixed it.


root/torch/install/share/lua/5.1/torch/Tensor.lua:466: Wrong size for view.

Hi Aaron,
Thanks for your sharing code, and I used some pictures to generate raw file and the error prompted as below:
stack traceback:         [C]: in function 'error'         /root/torch/install/share/lua/5.1/torch/Tensor.lua:466: in function 'view'         process.lua:26: in main chunk         [C]: in function 'dofile'         /root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:150: in main chunk         [C]: at 0x00405d50
Is any suggestion for this?
Kunyang

Is it a grayscale / single channel image?
If so, change line 24:
local img = image.load(opt.input .. '/' .. fname .. '.jpg')

to
local img = image.load(opt.input .. '/' .. fname .. '.jpg', 3)


FIX for #4092, allowing multiple parent has_many relations to the same child object

Addresses #4092 which affects 3.1 only.

If #4092 can’t be fixed with dot-notation, we’ll need a unit test that fails before this change to cover this issue :)

It can be fixed with dot-notation. Anyone else reading this and encountering the same problem, instead of:
<?php
class Contest extends DataObject {
    private static $has_many = [
        "GrandPrizeWinners" => "Person",
        "RunnersUp" => "Person",
    ];
}

class Person extends DataObject {
    private static $has_one = [
        "GrandPrize" => "Contest",
        "RunnerUp" => "Contest",
    ];
}

Do this instead:
<?php
class Contest extends DataObject {
    private static $has_many = [
        "GrandPrizeWinners" => "Person.GrandPrize",
        "RunnersUp" => "Person.RunnerUp",
    ];
}

class Person extends DataObject {
    private static $has_one = [
        "GrandPrize" => "Contest",
        "RunnerUp" => "Contest",
    ];
}

And make sure you perform a dev/build as well, otherwise it will not work until you do.

Thanks again @kinglozzer!


SPIKE - Data Watcher Database Content

Description
Short description of the issue you would like to solve.
Requirements

Requirement 1
Requirement 2

Nice to have or Goal Requirements

Nice to have 1
Nice to have 2

Additional notes
Any additional notes on the issue, if you have them.
Related tickets

#123

Follow up tickets
This spike is not considered complete until at least one follow up issue is created.

[ ] Placeholder ticket

**Below is the template for the response to this ticket. Add as many solutions as needed, but preferably include 2-5 for discussion. The response should be posted as a comment on this issue, or linked in a comment. **
Solution 1
Write an overview of the solution here.
Pros:

pro 1

Cons:

con 1

Additional notes:

note

Solution 2
Write an overview of the solution here.
Pros:

pro 1

Cons:

con 1

Additional notes:

note

Summary
Write up a summary of your findings, including your preferred solution.

Link to conversation thread that sparked this discussion: https://github.com/IMAP-Science-Operations-Center/sds-data-manager/pull/104#discussion_r1271465224

What is left to figure out: exactly what the information we need from the metadata table to determine if processing can proceed, and if we need some additional data tracking tools for internal or external use (eg an api which can return the status of processing, given an instrument, level, and timestamp)

For this SPIKE, I was hoping that we could decide what the database column will look like.

instrument
filename
data_level
version
status

But this might come together during implementation based on user stories and how data watcher is implemented.
So we can close this SPIKE.

Completed with #95, follow up #185


Pull Requests Merged and Versions

This project should have a new release because some PRs were merged which updated the README without releasing a new version.
For example the new .xcconfig workflow does not work with the current 0.11.7 release
Cheers

Would love a new release with the xcconfig changes. In the meantime you can install from git+https://github.com/maxkomarychev/react-native-config.git#xcconfig.


Use a buffer for incoming data for the plotter

This fixes #6. The problem was with how data was being processed in the plotter data callback. I think if multiple lines were present they weren't always processed and if partial lines were present they too were not processed.

Excellent! Once again, thank you for the contribution!

Released in 0.7.2.


Fix resetting of cursor-tools when closing the document (PR 17464 follow-up)

With the removal of the "secondarytoolbarreset" event in PR #17464 resetting of cursor-tools state accidentally broke.

/botio-linux preview


Missing NuGet package icon

The new version has an icon now: https://nuget.episerver.com/package/?id=Geta.404Handler


Falba PCB rev 13-01-2021: pad overlap question

I recently received my boards from Falbatech and noticed an issue with an overlap of a hotswap pad, a diode smd pad and the associated diode through hole.  It looks like it was scratched through the copper layer on the "left" side to try and correct the issue.  Has anyone that has built with this board had any issues?  I am doing through hole and not hot swap, so I am not overly concerned but wanted to validate.  Looking at the other post here with this board revision I can see the same scratch mark.  Attached are photos of both boards with the same scratch on the "left" as well as the flip side of the board with properly spaced pads on the "right" side of the board.
Thanks for a great design and offering the PCBs at a reasonable cost compared to a lot of other kits.

Hi,
with the premise that, as emerged from here, I've just learned about the existence of this particular board. It looks like there was a misfortunate placement of the pads that was later fixed by cutting the trace after the fact.
I think that, if you're not planning to use the hot swap socket, you should be good but I cannot be 100% sure.
To be extra sure you can grab the multimeter and make a few continuity checks using the schematic available here.

Okay, about this "scratches", I have exactly the same in same exact places but board is functioning properly. I have even checked for continuity and everything was alright. If you are planning installing LED's then you should read my post.

Thanks @mattdibi and @Spamm3r for the comments.  I haven't done the continuity check but will do that tonight and validate.  Good to hear its working fine for you Spamm3r.
Matt since I haven't done the install yet do you want me to take photos of the build process so you can add it to your documentation with this updated board?

I think that there is no need to update everything. the most important parts are that hot swap mod is supported and LEDs lanes are inverted. But decision is up to Matt.
@raymaclabs how long have you wait for your order?

@Spamm3r it didn't seem unusually long.  It was 4 days from order to shipping and then less than a week to arrive in the USA.

Oh really? I was waiting month or even more. I have ordered case, cables and pcb.

@mattdibi I may have problem with one key (pad is overlapped) (key is ]/} - I have default keymap). I have checked for continuity when I have pressed key and there is connection between pads. I have replaced diode and different positions but no success (you never know if falba changed something). So is there an way to simulate an key press by shorting some pads on pro micro? If traces are damaged I will just short wire connection to key.

Great! Thank for the informations. I'll wait for the documentation from Falbatech then.

I have no clue how long you will have to wait etc. Maybe if you will call him you will get more answers then me.

@Spamm3r is this the spot with the scratched pads or a different one?  I want to ensure i jump the same spot when soldering mine up also.  Thanks!

Yea with scratched pads. The funny thing is that on my one half everything is alright but on second one is not. I can guess that he did "disconnecting" of pads by hand and in my case he damaged trace.

I see what you're talking about, the trace for that last column that is close to those pads.

Did you guys buy these as B-Stock units for a lower price, or are they the standard option?

I bought these as the standard option from this link. https://falba.tech/product/ergodox-pcb-electrical-boards-set-of-2/

@raymaclabs But... those are Ergodox PCBs not Redox PCBs.

I have bought mine as normal PCB's. So dunno.

Sorry bad cut and paste on my end. It was the redox ones here. There is no
listing for a b-stock pcb of redox.
https://falba.tech/product/redox-pcb-electrical-boards-set-of-2/
On Sat, Feb 27, 2021 at 04:55 Spamm3r<EMAIL_ADDRESS>wrote:

I have bought mine as normal PCB's. So dunno.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mattdibi/redox-keyboard/issues/88#issuecomment-787046959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP43ODIQ7MBPPO4NRY52LATTBC6SPANCNFSM4YC3GJNQ
.


Release 0.1.7

Released https://mvnrepository.com/artifact/io.github.phymbert/spark-search_2.12/0.1.7


DBZ-5138 Retry failed metrics registration; allow starting without me…

…trics
https://issues.redhat.com/browse/DBZ-5138

Hi @jpechane overall this LGTM, I pushed a small commit to the PR to correctly track registration even when successful.  This should address the previous test failures and if the tests pass I'll merge.

@Naros Thanks a lot! I just followed with one more smallish change PR - https://github.com/debezium/debezium/pull/3506


Exporting data from the Table directly

Hi There, i have started to use nebula and in particular the sn-table...
does this have any features that would allow the customer to download the data from the table direct to excel?
im thinking a couple of options, whats in view (e.g 100 rows visible, all data up to a certain volume). do you happen to know if this is possible?
thanks

If you are using it inside Qlik Sense there is that option. If you are using it in a mashup that feature is not available. There are no current plans of implementing outside sense.


Fix Issue #471

fixes #471

Check if an instance actually exists in the cloud before trying to delete it
Terminate jenkins nodes immediately if the isntance failed to start in the cloud

Testing done
Currently testing on self hosted jenkins in our company. Will report back with results
If any automated tests need to be changed to test this behavior, I would appreciate some help
Submitter checklist

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[x] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Testing on our jenkins instance was successful. I consider this pull request ready. If you want me to add new tests, please provide some pointers on what to do

hi @Theoderich, yes adding some tests could be great.
I'll try to reproduce it and think about how we could test it.


getCarrierinfo

Is it possible to get carrier name, i understand due to the option of number porting the new provider may not be updated. I am ok with stale or incorrect data

At the moment, it doesn't appear to be the case at least that function call is not available. I suspect it could be done but the functionality of the Java script would need replicating.


Clicking in the pathways panel loses your place when you searched

Describe the bug
A clear and concise description of what the bug is.
If you made a search and then you just want to see something in the search, you click the pathway.    Where did it go?  It's gone.
To Reproduce
Steps to reproduce the behavior:

Go to enrichmentmap.org
Go to the demo
Type "signalling" in the search
Click on "integrin signalling pathway"
The search is gone.  The pathway is gone.  Where did everything go?

Expected behavior
The panel shouldn't jump around and reset randomly.
Screenshots
https://github.com/cytoscape/enrichment-map-webapp/assets/989043/8fc404c2-1e95-4334-b5c1-c5cffce1222b

looks good


New installer logs? - Feedback from user

Feedback from user:

So I answer YES and nothing else appears to happen.
So I peeked in Activity Monitor.  Sure enough after I press YES the process terminates.
Are there any logs so I can give you more actionable data?\
Thanks,
David

Stale - closing out.


Multiple instances per page

As highlighted in #402, remark will currently only work with one instance per page because there can only a single configuration object.
This makes sense for most use cases where comments are for a blog, but it prevents using Remark in other setups like online consultation where feedback on multiple areas might be needed.
Would multiple configuration objects be necessary? Or could a node/nodes value specify an array of target nodes and the embed script loop over them, sharing the rest of the config? The url value could then be a combination of the url with the node value appended.
Would this be helpful? Or is it too much of an edge case?

Same question was raised here also. Right now there is no solution (unless a horribly hacky one)
I think we should move away from declaring remark object (which also pollutes global namespace) to declarative approach, i.e connecting script which watch for element with some data-attrs, for example
<div
  data-is-remark-comments
  data-host="http://..."
  data-site-id="remark"
  data-post-url="https://..."
  data-theme="dark"
  ...
/>

I think this can be done as a non-breaking change (still support old init and retire it later)


typeguard update

This fixes #461

Annoying. @typechecked is broken.
But. It seems that if you add @typechecked to the class rather than __init__, mypy will not complain. I suspect it derives the type of Cons() using __init__ and some heuristics.

Annoying. @typechecked is broken.
But. It seems that if you add @typechecked to the class rather than __init__, mypy will not complain. I suspect it derives the type of Cons() using __init__ and some heuristics.

Yeah, it's broken.  Given that I guess that the class decorating approach is the way of least pain indeed...  Thanks!

For reference, make checks does not report any errors on my machine and tests on testing.psij.io seem to pass on this branch.

For reference, make checks does not report any errors on my machine and tests on testing.psij.io seem to pass on this branch.

Yeah, same here - tests pass fine locally, docs build all right, but github CI still complains...

For reference, make checks does not report any errors on my machine and tests on testing.psij.io seem to pass on this branch.

Yeah, same here - tests pass fine locally, docs build all right, but github CI still complains...

I think we can merge. If we run into issues building the docs after, we can address it then.

By the way, I approve of this PR :)

The failing tests are due to RP installing an older version of PSI/J as a dependency, which conflicts with the version being tested. While we should address the "circular" dependency (there is little sense to use PSI/J to submit to PSI/J via RP), this needs not happen now since RP is an optional install.


Question - ddcloud_address_list instructions for child_lists option not defined

Hi,
I have the other options working but was trying to use the optional child_lists feature.  I get the error:

ddcloud_address_list.production-list: child_lists: should be a list

So, I am unsure on the syntax in how to represent this option.  So, if you can update the documentation on the same that would be great.  BTW, the documentation refers to port_lists in the address_list readme file so you will want to update that also.  Thanks.

This is the same issue for the resource ddcloud_port_list.

The final note here is whether or not the ddcloud_firewall_list has updates to utilize the new resources ddcloud_address_list and ddcloud_port_list respectively.  Is this code written but not released or in flight?

No it should definitely work - I updated the docs before I went on leave. I'll have a look at this tomorrow.
On 26 Oct. 2016, at 7:04 am, wninobla <notifications<EMAIL_ADDRESS>wrote:
The final note here is whether or not the ddcloud_firewall_list has updates to utilize the new resources ddcloud_address_list and ddcloud_port_list respectively. Is this code written but not released or in flight?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-256159684, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezN1SQFwNVSNi7BVrLtUfC7d6DKzkks5q3mC6gaJpZM4KgXeN.
itevomcid

Should be enough to just put a list of comma-separated entries in square brackets.
Same syntax as depends_on.
On 26 Oct. 2016, at 7:04 am, wninobla <notifications<EMAIL_ADDRESS>wrote:
The final note here is whether or not the ddcloud_firewall_list has updates to utilize the new resources ddcloud_address_list and ddcloud_port_list respectively. Is this code written but not released or in flight?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-256159684, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezN1SQFwNVSNi7BVrLtUfC7d6DKzkks5q3mC6gaJpZM4KgXeN.
itevomcid

I see - yes address lists are supported for ddcloud_firewall_rule, but I didn't specify the property names for address lists in the documentation. I'll update the docs, but for reference here are the 4 properties relating to address / port lists (source / destination) on a firewall rule:

source_address_list
source_port_list
destination_address_list
destination_port_list

This should be fixed now, @wninobla. Can you take a look at let me know?

OK, this looks good now.  I will test the ID and see if the ddcloud_firewall_acl gets updated now.  What I didn't see or rather would like an example of is the list that you were talking about if I specify multiples for the ddcloud_address/port_list.  I can play around with it but if you can update the docs that specify that example or just send me one I can update my project to reflect the same.  Thanks in advance!
BTW, I talked with Hashicorp just now and looking to play with their Atlas/Terraform Enterprise shim.  Should be interesting to say the least. =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 2:32 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
This should be fixed now, @wninoblahttps://github.com/wninobla. Can you take a look at let me know?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257426718, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9vxIfCrfHw7bs4GDiFYO3kaWxw0_eks5q5l5SgaJpZM4KgXeN.
itevomcid

@wninobla does that suit?

Well yeah and no.  I was looking for a child_list example.  For instance:

I have (2) resources defined as ADDRLIST_01 and ADDRLIST_02 that I want to combine

I define a new resource as GROUP_01 to hold the items above as a single list

Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 2:53 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
@wninoblahttps://github.com/wninobla does that suit?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257432029, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v3I8Udj2uZmhI4u1dXUk-HW7jyZeks5q5mNEgaJpZM4KgXeN.
itevomcid

Oh, sorry I thought that was obvious. Obviously not now that I think about it. Sorry, my bad 😊

BTW, it fails also because it has as a required component the name and address fields...  So I can fill the name one but the address field doesn't necessarily make sense.  The IP_version I think got truncated in the doc so you'll want to readd that in there also.
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: William Ninobla (ITaaS)
Sent: Monday, October 31, 2016 2:55 PM
To: DimensionDataResearch/dd-cloud-compute-terraform; DimensionDataResearch/dd-cloud-compute-terraform
Cc: Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Well yeah and no.  I was looking for a child_list example.  For instance:

I have (2) resources defined as ADDRLIST_01 and ADDRLIST_02 that I want to combine

I define a new resource as GROUP_01 to hold the items above as a single list

Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 2:53 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
@wninoblahttps://github.com/wninobla does that suit?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257432029, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v3I8Udj2uZmhI4u1dXUk-HW7jyZeks5q5mNEgaJpZM4KgXeN.
itevomcid

No worries.  We often make the assumption including myself on what's intended.  That's why I am working through the instructions as it gives a fres view on it all.
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 2:57 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Oh, sorry I thought that was obvious. Obviously not now that I think about it. Sorry, my bad ??

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257433123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v14hrJyDsf54K6l2XNbc5nmjowbiks5q5mRggaJpZM4KgXeN.
itevomcid

Sorry when you say address is required, where do you mean? Can you provide an example? Looking in the code, address is marked as optional.

Oh, in the documentation. Sorry, yes, I'm stupid.

@wninobla ok - how about now? 🌵

It's OK.  I retried the syntax I used on Friday but for some reason it looks like its reading it now although when I run it I get this:
[root@192-168-104-251 test]# terraform apply
ddcloud_networkdomain.networkdomain: Refreshing state... (ID: 9c4033c9-3c2c-4ea0-bf20-52929c74140c)
ddcloud_address_list.utility-list: Refreshing state... (ID: 1c061f76-658a-4322-b606-dd6fa0a46104)
ddcloud_vlan.trust-vlan: Refreshing state... (ID: b2cfad36-061b-46dc-996b-0e490b05793e)
ddcloud_vlan.dmz-vlan: Refreshing state... (ID: d2473a60-75df-4b86-9d6f-cbd14783ea84)
ddcloud_address_list.trust-list: Refreshing state... (ID: d3a73729-d87f-4f6d-bf67-3d7b0c0bb52c)
ddcloud_address_list.dmz-list: Refreshing state... (ID: 01ec9196-7c1d-44f5-bc66-b80bb97f7190)
ddcloud_vlan.utility-vlan: Refreshing state... (ID: cd1e9af8-7062-466b-992e-e40a681f22c3)
ddcloud_port_list.http-alt-list: Refreshing state... (ID: d7de85ac-3f6a-4633-8198-e24fd67a9293)
ddcloud_port_list.http-list: Refreshing state... (ID: 274bad7f-9031-42c8-b349-2982a7b56182)
ddcloud_port_list.https-list: Refreshing state... (ID: e395809e-0232-406b-9a95-e3b8459559db)
ddcloud_server.webapp-server: Refreshing state... (ID: 6e1f29cf-08ad-4b62-b2b6-77b4802bf33a)
ddcloud_server.db-server: Refreshing state... (ID: b5f99711-8f46-4cec-b2c0-5361075f5f2b)
ddcloud_server_nic.webapp-server: Refreshing state... (ID: cfe129d0-6986-4e36-8723-16402925d322)
ddcloud_nat.nat: Refreshing state... (ID: 1bc62bd8-b06d-480e-b44f-c3196ff176a4)
ddcloud_server_anti_affinity.server_anti_affinity: Refreshing state... (ID: ae573a1d-1342-4946-9884-b31b6878596f)
ddcloud_vip_node.vip-node: Refreshing state... (ID: b27ebac9-8729-4c6a-a743-4f1ea8f2bdf5)
ddcloud_server_nic.db-server: Refreshing state... (ID: 3ceeed53-70b4-469b-9164-372ebaa7e06b)
ddcloud_firewall_rule.firewall-rule-001: Refreshing state... (ID: 5a8e6032-0e5b-4d1a-9608-9bc9a6c0dc6b)
ddcloud_vip_pool.vip-pool: Refreshing state... (ID: 78703344-ca07-4ba0-9c19-a2ba552163f6)
ddcloud_virtual_listener.virtual-listener: Refreshing state... (ID: 7a63c5f0-675f-4c89-bff6-d11c0d21f5ea)
ddcloud_vip_pool_member.pool_member: Refreshing state... (ID: 320e2f9f-e0e8-468f-855a-a40716d4d1c3)
ddcloud_firewall_rule.firewall-rule-002: Refreshing state... (ID: d84a355e-f73f-4593-a69d-0ece4a66072f)
ddcloud_address_list.prod-list: Creating...
child_lists.#: "" => "2"
child_lists.0: "" => "ddcloud_address_list.dmz-list"
child_lists.1: "" => "ddcloud_address_list.trust-list"
ip_version:    "" => "IPv4"
name:          "" => "PROD_Address_List"
networkdomain: "" => "9c4033c9-3c2c-4ea0-bf20-52929c74140c"
Error applying plan:
1 error(s) occurred:

ddcloud_address_list.prod-list: Request to create IP address list 'PROD_Address_List' failed with status code 400 (RESOURCE_NOT_FOUND): IP Address List ddcloud_address_list.dmz-list not found.

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
I'll now read ur docs and see what I'm doing wrong... =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 3:12 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Oh, in the documentation.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257436184, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v90zRwvElkKOt_3-SWg6g1r-N4lJks5q5mfbgaJpZM4KgXeN.
itevomcid

OK I updated my .tf file and it won't take as its expecting a comma or something:
resource "ddcloud_address_list" "prod-list" {
name                 = "PROD_Address_List"
ip_version           = "IPv4"
child_lists = [
"${ddcloud_address_list.dmz-list.id}"
"${ddcloud_address_list.trust-list.id}"
]
networkdomain        = "${ddcloud_networkdomain.networkdomain.id}"
depends_on           = ["ddcloud_networkdomain.networkdomain"]
}
Error is:
[root@192-168-104-251 test]# terraform plan
Error loading config: Error parsing /root/terraform/test/address_list.tf: At 58:2: error parsing list, expected comma or list end, got: STRING
[root@192-168-104-251 test]#
I'm not seeing the problem...  I know its simple but its not happy. =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: William Ninobla (ITaaS)
Sent: Monday, October 31, 2016 3:19 PM
To: DimensionDataResearch/dd-cloud-compute-terraform; DimensionDataResearch/dd-cloud-compute-terraform
Cc: Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
It's OK.  I retried the syntax I used on Friday but for some reason it looks like its reading it now although when I run it I get this:
[root@192-168-104-251 test]# terraform apply
ddcloud_networkdomain.networkdomain: Refreshing state... (ID: 9c4033c9-3c2c-4ea0-bf20-52929c74140c)
ddcloud_address_list.utility-list: Refreshing state... (ID: 1c061f76-658a-4322-b606-dd6fa0a46104)
ddcloud_vlan.trust-vlan: Refreshing state... (ID: b2cfad36-061b-46dc-996b-0e490b05793e)
ddcloud_vlan.dmz-vlan: Refreshing state... (ID: d2473a60-75df-4b86-9d6f-cbd14783ea84)
ddcloud_address_list.trust-list: Refreshing state... (ID: d3a73729-d87f-4f6d-bf67-3d7b0c0bb52c)
ddcloud_address_list.dmz-list: Refreshing state... (ID: 01ec9196-7c1d-44f5-bc66-b80bb97f7190)
ddcloud_vlan.utility-vlan: Refreshing state... (ID: cd1e9af8-7062-466b-992e-e40a681f22c3)
ddcloud_port_list.http-alt-list: Refreshing state... (ID: d7de85ac-3f6a-4633-8198-e24fd67a9293)
ddcloud_port_list.http-list: Refreshing state... (ID: 274bad7f-9031-42c8-b349-2982a7b56182)
ddcloud_port_list.https-list: Refreshing state... (ID: e395809e-0232-406b-9a95-e3b8459559db)
ddcloud_server.webapp-server: Refreshing state... (ID: 6e1f29cf-08ad-4b62-b2b6-77b4802bf33a)
ddcloud_server.db-server: Refreshing state... (ID: b5f99711-8f46-4cec-b2c0-5361075f5f2b)
ddcloud_server_nic.webapp-server: Refreshing state... (ID: cfe129d0-6986-4e36-8723-16402925d322)
ddcloud_nat.nat: Refreshing state... (ID: 1bc62bd8-b06d-480e-b44f-c3196ff176a4)
ddcloud_server_anti_affinity.server_anti_affinity: Refreshing state... (ID: ae573a1d-1342-4946-9884-b31b6878596f)
ddcloud_vip_node.vip-node: Refreshing state... (ID: b27ebac9-8729-4c6a-a743-4f1ea8f2bdf5)
ddcloud_server_nic.db-server: Refreshing state... (ID: 3ceeed53-70b4-469b-9164-372ebaa7e06b)
ddcloud_firewall_rule.firewall-rule-001: Refreshing state... (ID: 5a8e6032-0e5b-4d1a-9608-9bc9a6c0dc6b)
ddcloud_vip_pool.vip-pool: Refreshing state... (ID: 78703344-ca07-4ba0-9c19-a2ba552163f6)
ddcloud_virtual_listener.virtual-listener: Refreshing state... (ID: 7a63c5f0-675f-4c89-bff6-d11c0d21f5ea)
ddcloud_vip_pool_member.pool_member: Refreshing state... (ID: 320e2f9f-e0e8-468f-855a-a40716d4d1c3)
ddcloud_firewall_rule.firewall-rule-002: Refreshing state... (ID: d84a355e-f73f-4593-a69d-0ece4a66072f)
ddcloud_address_list.prod-list: Creating...
child_lists.#: "" => "2"
child_lists.0: "" => "ddcloud_address_list.dmz-list"
child_lists.1: "" => "ddcloud_address_list.trust-list"
ip_version:    "" => "IPv4"
name:          "" => "PROD_Address_List"
networkdomain: "" => "9c4033c9-3c2c-4ea0-bf20-52929c74140c"
Error applying plan:
1 error(s) occurred:

ddcloud_address_list.prod-list: Request to create IP address list 'PROD_Address_List' failed with status code 400 (RESOURCE_NOT_FOUND): IP Address List ddcloud_address_list.dmz-list not found.

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
I'll now read ur docs and see what I'm doing wrong... =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 3:12 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Oh, in the documentation.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257436184, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v90zRwvElkKOt_3-SWg6g1r-N4lJks5q5mfbgaJpZM4KgXeN.
itevomcid

OK it was missing the ending commas:
resource "ddcloud_address_list" "prod-list" {
name                 = "PROD_Address_List"
ip_version           = "IPv4"
child_lists          = [
"${ddcloud_address_list.dmz-list.id}",
"${ddcloud_address_list.trust-list.id}",
]
networkdomain        = "${ddcloud_networkdomain.networkdomain.id}"
depends_on           = ["ddcloud_networkdomain.networkdomain"]
}
You will want to update the documentation in the child_lists section in your example to add commas...
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: William Ninobla (ITaaS)
Sent: Monday, October 31, 2016 3:35 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
OK I updated my .tf file and it won't take as its expecting a comma or something:
resource "ddcloud_address_list" "prod-list" {
name                 = "PROD_Address_List"
ip_version           = "IPv4"
child_lists = [
"${ddcloud_address_list.dmz-list.id}"
"${ddcloud_address_list.trust-list.id}"
]
networkdomain        = "${ddcloud_networkdomain.networkdomain.id}"
depends_on           = ["ddcloud_networkdomain.networkdomain"]
}
Error is:
[root@192-168-104-251 test]# terraform plan
Error loading config: Error parsing /root/terraform/test/address_list.tf: At 58:2: error parsing list, expected comma or list end, got: STRING
[root@192-168-104-251 test]#
I'm not seeing the problem...  I know its simple but its not happy. =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: William Ninobla (ITaaS)
Sent: Monday, October 31, 2016 3:19 PM
To: DimensionDataResearch/dd-cloud-compute-terraform; DimensionDataResearch/dd-cloud-compute-terraform
Cc: Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
It's OK.  I retried the syntax I used on Friday but for some reason it looks like its reading it now although when I run it I get this:
[root@192-168-104-251 test]# terraform apply
ddcloud_networkdomain.networkdomain: Refreshing state... (ID: 9c4033c9-3c2c-4ea0-bf20-52929c74140c)
ddcloud_address_list.utility-list: Refreshing state... (ID: 1c061f76-658a-4322-b606-dd6fa0a46104)
ddcloud_vlan.trust-vlan: Refreshing state... (ID: b2cfad36-061b-46dc-996b-0e490b05793e)
ddcloud_vlan.dmz-vlan: Refreshing state... (ID: d2473a60-75df-4b86-9d6f-cbd14783ea84)
ddcloud_address_list.trust-list: Refreshing state... (ID: d3a73729-d87f-4f6d-bf67-3d7b0c0bb52c)
ddcloud_address_list.dmz-list: Refreshing state... (ID: 01ec9196-7c1d-44f5-bc66-b80bb97f7190)
ddcloud_vlan.utility-vlan: Refreshing state... (ID: cd1e9af8-7062-466b-992e-e40a681f22c3)
ddcloud_port_list.http-alt-list: Refreshing state... (ID: d7de85ac-3f6a-4633-8198-e24fd67a9293)
ddcloud_port_list.http-list: Refreshing state... (ID: 274bad7f-9031-42c8-b349-2982a7b56182)
ddcloud_port_list.https-list: Refreshing state... (ID: e395809e-0232-406b-9a95-e3b8459559db)
ddcloud_server.webapp-server: Refreshing state... (ID: 6e1f29cf-08ad-4b62-b2b6-77b4802bf33a)
ddcloud_server.db-server: Refreshing state... (ID: b5f99711-8f46-4cec-b2c0-5361075f5f2b)
ddcloud_server_nic.webapp-server: Refreshing state... (ID: cfe129d0-6986-4e36-8723-16402925d322)
ddcloud_nat.nat: Refreshing state... (ID: 1bc62bd8-b06d-480e-b44f-c3196ff176a4)
ddcloud_server_anti_affinity.server_anti_affinity: Refreshing state... (ID: ae573a1d-1342-4946-9884-b31b6878596f)
ddcloud_vip_node.vip-node: Refreshing state... (ID: b27ebac9-8729-4c6a-a743-4f1ea8f2bdf5)
ddcloud_server_nic.db-server: Refreshing state... (ID: 3ceeed53-70b4-469b-9164-372ebaa7e06b)
ddcloud_firewall_rule.firewall-rule-001: Refreshing state... (ID: 5a8e6032-0e5b-4d1a-9608-9bc9a6c0dc6b)
ddcloud_vip_pool.vip-pool: Refreshing state... (ID: 78703344-ca07-4ba0-9c19-a2ba552163f6)
ddcloud_virtual_listener.virtual-listener: Refreshing state... (ID: 7a63c5f0-675f-4c89-bff6-d11c0d21f5ea)
ddcloud_vip_pool_member.pool_member: Refreshing state... (ID: 320e2f9f-e0e8-468f-855a-a40716d4d1c3)
ddcloud_firewall_rule.firewall-rule-002: Refreshing state... (ID: d84a355e-f73f-4593-a69d-0ece4a66072f)
ddcloud_address_list.prod-list: Creating...
child_lists.#: "" => "2"
child_lists.0: "" => "ddcloud_address_list.dmz-list"
child_lists.1: "" => "ddcloud_address_list.trust-list"
ip_version:    "" => "IPv4"
name:          "" => "PROD_Address_List"
networkdomain: "" => "9c4033c9-3c2c-4ea0-bf20-52929c74140c"
Error applying plan:
1 error(s) occurred:

ddcloud_address_list.prod-list: Request to create IP address list 'PROD_Address_List' failed with status code 400 (RESOURCE_NOT_FOUND): IP Address List ddcloud_address_list.dmz-list not found.

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
I'll now read ur docs and see what I'm doing wrong... =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 3:12 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Oh, in the documentation.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257436184, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v90zRwvElkKOt_3-SWg6g1r-N4lJks5q5mfbgaJpZM4KgXeN.
itevomcid

Ah, sorry - was typing that in a browser! Will fix :)

Ok, so it works now?

Address and port lists are working.  I an writing a firewall rule not and got the port list to work but its erroring on the address list specifically on the source.  The plan works but the apply doesn't.  I change it to both a nested and non nested address list with the same error.  Here's what I got:
resource "ddcloud_firewall_rule" "firewall-rule-004" {
name                     = "mgmt.inbound"
placement                = "last"
action                   = "accept"
enabled                  = true
ip_version               = "ipv4"
protocol                 = "tcp"
source_address_list      = "${ddcloud_address_list.utility-list.id}"
destination_address_list = "${ddcloud_address_list.prod-list.id}"
destination_port         = "3389"
networkdomain            = "${ddcloud_networkdomain.networkdomain.id}"
depends_on               = ["ddcloud_virtual_listener.virtual-listener"]
}
Error applying plan:
1 error(s) occurred:

ddcloud_firewall_rule.firewall-rule-004: Request to create firewall rule in network domain '9c4033c9-3c2c-4ea0-bf20-52929c74140c' failed with unexpected status code 400 (INVALID_INPUT_DATA): At least source ip or ipAddressListId must be provided.

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
Can you check to see if its a bug?
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 4:17 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Ok, so it works now?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeN.
itevomcid

Ok, I’ll have a look this afternoon (meetings until then). Sorry about that.
On 1 Nov 2016, at 10:25 AM, wninobla <notifications<EMAIL_ADDRESS>wrote:
Address and port lists are working. I an writing a firewall rule not and got the port list to work but its erroring on the address list specifically on the source. The plan works but the apply doesn't. I change it to both a nested and non nested address list with the same error. Here's what I got:
resource "ddcloud_firewall_rule" "firewall-rule-004" {
name = "mgmt.inbound"
placement = "last"
action = "accept"
enabled = true
ip_version = "ipv4"
protocol = "tcp"
source_address_list = "${ddcloud_address_list.utility-list.id}"
destination_address_list = "${ddcloud_address_list.prod-list.id}"
destination_port = "3389"
networkdomain = "${ddcloud_networkdomain.networkdomain.id}"
depends_on = ["ddcloud_virtual_listener.virtual-listener"]
}
Error applying plan:
1 error(s) occurred:

ddcloud_firewall_rule.firewall-rule-004: Request to create firewall rule in network domain '9c4033c9-3c2c-4ea0-bf20-52929c74140c' failed with unexpected status code 400 (INVALID_INPUT_DATA): At least source ip or ipAddressListId must be provided.

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
Can you check to see if its a bug?
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman <notifications<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 4:17 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Ok, so it works now?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeN>.
itevomcid
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449275, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezJB1udcexjlYGoybjnM0QppmEexFks5q5njigaJpZM4KgXeN.

No problem.  The regular rule works but when I specify any nested list it complains.  Just let me know what you find.
Also, on the child_lists portion, slight bug in that it keeps switching the list members and as a result it wants to modify the child lists back and forth every time I run a "terraform apply".  If you want me to I can file that under a separate case.
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 4:26 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Ok, I'll have a look this afternoon (meetings until then). Sorry about that.
On 1 Nov 2016, at 10:25 AM, wninobla <notifications<EMAIL_ADDRESS>wrote:
Address and port lists are working. I an writing a firewall rule not and got the port list to work but its erroring on the address list specifically on the source. The plan works but the apply doesn't. I change it to both a nested and non nested address list with the same error. Here's what I got:
resource "ddcloud_firewall_rule" "firewall-rule-004" {
name = "mgmt.inbound"
placement = "last"
action = "accept"
enabled = true
ip_version = "ipv4"
protocol = "tcp"
source_address_list = "${ddcloud_address_list.utility-list.id}"
destination_address_list = "${ddcloud_address_list.prod-list.id}"
destination_port = "3389"
networkdomain = "${ddcloud_networkdomain.networkdomain.id}"
depends_on = ["ddcloud_virtual_listener.virtual-listener"]
}
Error applying plan:
1 error(s) occurred:

ddcloud_firewall_rule.firewall-rule-004: Request to create firewall rule in network domain '9c4033c9-3c2c-4ea0-bf20-52929c74140c' failed with unexpected status code 400 (INVALID_INPUT_DATA): At least source ip or ipAddressListId must be provided.

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
Can you check to see if its a bug?
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman <notifications<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 4:17 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Ok, so it works now?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039>>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeN<https://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeN>>.
itevomcid

You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449275https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449275>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABkezJB1udcexjlYGoybjnM0QppmEexFks5q5njigaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/ABkezJB1udcexjlYGoybjnM0QppmEexFks5q5njigaJpZM4KgXeN>.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449500, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v_Aoe6pbDFG-2lvrBolqI-k6KBIEks5q5nkzgaJpZM4KgXeN.

@wninobla can you try running terraform apply again with the following environment variables set:
TF_LOG=DEBUG
TF_LOG_PATH=Apply.log
DD_COMPUTE_EXTENDED_LOGGING=1
Then attach the generated log file?

OK let me create a variable file and do that.  Just in time too as I just shut my session down... LOL
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 4:29 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
@wninoblahttps://github.com/wninobla can you try running terraform apply again with the following environment variables set:
TF_LOG=DEBUG
TF_LOG_PATH=Apply.log
DD_COMPUTE_EXTENDED_LOGGING=1
Then attach the generated log file?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449985, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v_kCrYJ4rArnzOyTpEReofsjdtWWks5q5nnqgaJpZM4KgXeN.
itevomcid

Yeah please create a separate issue for that; it’s a bug (well, sort of) - CloudControl is not preserving the List order, so it should be changed to a Set instead.
On 1 Nov 2016, at 10:29 AM, wninobla <notifications<EMAIL_ADDRESS>wrote:
No problem. The regular rule works but when I specify any nested list it complains. Just let me know what you find.
Also, on the child_lists portion, slight bug in that it keeps switching the list members and as a result it wants to modify the child lists back and forth every time I run a "terraform apply". If you want me to I can file that under a separate case.
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman <notifications<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 4:26 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Ok, I'll have a look this afternoon (meetings until then). Sorry about that.
On 1 Nov 2016, at 10:25 AM, wninobla <notifications@github.commailto:notifications<EMAIL_ADDRESS>wrote:
Address and port lists are working. I an writing a firewall rule not and got the port list to work but its erroring on the address list specifically on the source. The plan works but the apply doesn't. I change it to both a nested and non nested address list with the same error. Here's what I got:
resource "ddcloud_firewall_rule" "firewall-rule-004" {
name = "mgmt.inbound"
placement = "last"
action = "accept"
enabled = true
ip_version = "ipv4"
protocol = "tcp"
source_address_list = "${ddcloud_address_list.utility-list.id}"
destination_address_list = "${ddcloud_address_list.prod-list.id}"
destination_port = "3389"
networkdomain = "${ddcloud_networkdomain.networkdomain.id}"
depends_on = ["ddcloud_virtual_listener.virtual-listener"]
}
Error applying plan:
1 error(s) occurred:

ddcloud_firewall_rule.firewall-rule-004: Request to create firewall rule in network domain '9c4033c9-3c2c-4ea0-bf20-52929c74140c' failed with unexpected status code 400 (INVALID_INPUT_DATA): At least source ip or ipAddressListId must be provided.

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
Can you check to see if its a bug?
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman <notifications@github.commailto:notifications<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 4:17 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Ok, so it works now?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039><https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257448039>>>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeN<https://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeN><https://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeN<https://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v9crqO9oh38VJ0LDQXHJTrFqkl6mks5q5ncQgaJpZM4KgXeN>>>.
itevomcid

You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449275https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449275<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449275https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449275>>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABkezJB1udcexjlYGoybjnM0QppmEexFks5q5njigaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/ABkezJB1udcexjlYGoybjnM0QppmEexFks5q5njigaJpZM4KgXeN<https://github.com/notifications/unsubscribe-auth/ABkezJB1udcexjlYGoybjnM0QppmEexFks5q5njigaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/ABkezJB1udcexjlYGoybjnM0QppmEexFks5q5njigaJpZM4KgXeN>>.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449500https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449500>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQe9v_Aoe6pbDFG-2lvrBolqI-k6KBIEks5q5nkzgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v_Aoe6pbDFG-2lvrBolqI-k6KBIEks5q5nkzgaJpZM4KgXeN>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257449922, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezHG4FILnCRh054ZD4xokD6awZ8vIks5q5nnOgaJpZM4KgXeN.

That should do it. Turns out CloudControl calls it ipAddressListId when creating a new rule, but ipAddressList.id when retrieving existing rules.

OK, cool.  I set a different case with the debug dump for you to review.  Just make sure it isn't something I'm doing that's dumb as that is totally possible. =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 4:43 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
That should do it. Turns out CloudControl calls it ipAddressListId when creating a new rule, but ipAddressList.id when retrieving existing rules.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257452185, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v5AYLoECJmLMxJaSlnblazWmi6Pnks5q5n0agaJpZM4KgXeN.
itevomcid

Nah, you were right it was a bug - see the notes #42 :)

OK cool.  I'll try it later on tonight and let you know if it behaves now or not.  Thanks for the quick fix!
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 5:03 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Nah, you were right it was a bug - see the notes #42https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42 :)

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeN.
itevomcid

Thanks heaps for taking the time to do so :)
On 1 Nov 2016, at 11:11 AM, wninobla <notifications<EMAIL_ADDRESS>wrote:
OK cool. I'll try it later on tonight and let you know if it behaves now or not. Thanks for the quick fix!
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman <notifications<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 5:03 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Nah, you were right it was a bug - see the notes #42<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42> :)

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeN>.
itevomcid
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257457446, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezLhOMfwwx9YN2eFRwF18iMqSDWkdks5q5oPKgaJpZM4KgXeN.

Let me know when the release is formally compiled else I guess I can compile this manually.  I'd just rather have an actual release. =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 5:16 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Thanks heaps for taking the time to do so :)
On 1 Nov 2016, at 11:11 AM, wninobla <notifications<EMAIL_ADDRESS>wrote:
OK cool. I'll try it later on tonight and let you know if it behaves now or not. Thanks for the quick fix!
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman <notifications<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 5:03 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Nah, you were right it was a bug - see the notes #42<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42>> :)

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814>>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeN<https://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeN>>.
itevomcid

You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257457446https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257457446>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABkezLhOMfwwx9YN2eFRwF18iMqSDWkdks5q5oPKgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/ABkezLhOMfwwx9YN2eFRwF18iMqSDWkdks5q5oPKgaJpZM4KgXeN>.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257458299, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v0uIGO-cJqF8cN-cysKukC1d3xVjks5q5oTegaJpZM4KgXeN.

Sure - later this afternoon:)
On 1 Nov. 2016, at 12:39 pm, wninobla <notifications<EMAIL_ADDRESS>wrote:
Let me know when the release is formally compiled else I guess I can compile this manually. I'd just rather have an actual release. =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman <notifications<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 5:16 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Thanks heaps for taking the time to do so :)
On 1 Nov 2016, at 11:11 AM, wninobla <notifications@github.commailto:notifications<EMAIL_ADDRESS>wrote:
OK cool. I'll try it later on tonight and let you know if it behaves now or not. Thanks for the quick fix!
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman <notifications@github.commailto:notifications<EMAIL_ADDRESS>Sent: Monday, October 31, 2016 5:03 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Question - ddcloud_address_list instructions for child_lists option not defined (#40)
Nah, you were right it was a bug - see the notes #42<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42><https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/42>>> :)

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814><https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257455814>>>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeN<https://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeN><https://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeN<https://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v3sJze6R50cwIOMPlvvx03y187VOks5q5oG5gaJpZM4KgXeN>>>.
itevomcid

You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257457446https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257457446<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257457446https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257457446>>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABkezLhOMfwwx9YN2eFRwF18iMqSDWkdks5q5oPKgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/ABkezLhOMfwwx9YN2eFRwF18iMqSDWkdks5q5oPKgaJpZM4KgXeN<https://github.com/notifications/unsubscribe-auth/ABkezLhOMfwwx9YN2eFRwF18iMqSDWkdks5q5oPKgaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/ABkezLhOMfwwx9YN2eFRwF18iMqSDWkdks5q5oPKgaJpZM4KgXeN>>.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257458299https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257458299>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQe9v0uIGO-cJqF8cN-cysKukC1d3xVjks5q5oTegaJpZM4KgXeNhttps://github.com/notifications/unsubscribe-auth/AQe9v0uIGO-cJqF8cN-cysKukC1d3xVjks5q5oTegaJpZM4KgXeN>.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/40#issuecomment-257469632, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezLXMK0B_J9EDMflGTa3rAQU23KYAks5q5phagaJpZM4KgXeN.

Here's v1.1.1 - have fun :)


[QUESTION] How can I use a buildah script for image generation using GitHub Actions?

Question
https://devops.stackexchange.com/questions/13524/how-can-i-use-a-buildah-script-for-image-generation-using-github-actions
Buildah scripts typically use shell. You can see an example of a script here,
#!/bin/sh
ctr=$(buildah from alpine:3)
buildah commit "$ctr" myAlpineImage

Let's say I have such a shell script that produces an image "myAlpineImage". How can I use GitHub CI to automate the creation of this image, and preferably uploading it to GitHub Container Registry?

If your use case is satisfied by this action, you can use this action to build image and push-to-registry action to push to Github Container Registry (or registry of your choice).
With this action you can also build image without dockerfile. Check this.
But, if you still want to build image typically using shell you can do something like:
- name: Test Build
  run: |
    #!/bin/sh
    ctr=$(buildah from alpine:3)
    buildah commit "$ctr" my-alpine-image

As Github Linux runners comes with buildah pre-installed https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md#installed-software

closing pending any further comments


Cannot use CausalTree as estimator

I try to use CausalTree as the estimator in why(), but seems like CausalTree.estimate() got unexpected keyword arguments.
Here is my code:

why1=Why(estimator='tree')
why1.fit(train_data,outcome,treatment='Card_Category')
effect1=why1.causal_effect(control='Blue',return_detail=True)

and error msg:

Traceback (most recent call last):
File "d:/06.Repo/YLearn-main/example_usages/case_study_bank.py", line 38, in
effect1=why1.causal_effect(control='Blue',return_detail=True)
File "C:\Users\peng.liu2\Anaconda3\envs\CV\lib\site-packages\ylearn_why.py", line 820, in causal_effect
return self._causal_effect_discrete(test_data, treat, control, return_detail=return_detail)
File "C:\Users\peng.liu2\Anaconda3\envs\CV\lib\site-packages\ylearn_why.py", line 850, in _causal_effect_discrete
effect = est.estimate(data=test_data, treat=t, control=c)
TypeError: estimate() got an unexpected keyword argument 'treat'

I found that  CausalTree.estimate() only accept data and quantity as arguments, so how can I use CausalTree as the estimator in why()

We have fixed this issue in the main branch which is not released yet. Upgrade ylearn from latest source code and try again please.

Hi, I just found an error after I upgrade Ylearn from latest source code,  here is the error msg:

ModuleNotFoundError                       Traceback (most recent call last)
Cell In [2], line 4
1 import numpy as np
2 import matplotlib.pyplot as plt
----> 4 from ylearn.estimator_model.causal_tree import CausalTree, CTCausalForest
5 from ylearn.exp_dataset.exp_data import sq_data
6 from ylearn.utils._common import to_df
File c:\Users\peng.liu2\Anaconda3\envs\CV\lib\site-packages\ylearn_init_.py:2
1 from ._version import version
----> 2 from ._why import Why
File c:\Users\peng.liu2\Anaconda3\envs\CV\lib\site-packages\ylearn_why.py:11
9 from ylearn import metric as M
10 from ylearn import sklearn_ex as skex
---> 11 from ylearn.causal_discovery import CausalDiscovery
12 from ylearn.causal_model import CausalModel, CausalGraph
13 from ylearn.effect_interpreter.policy_interpreter import PolicyInterpreter
ModuleNotFoundError: No module named 'ylearn.causal_discovery'
And I am not sure if there is a problem with my installation method. I just run python setup.py install with latest source code.

reopen for latest source code


Ignoring HTML comments in tag helper's body

This change addresses https://github.com/aspnet/Razor/issues/2062 issue.

@NTaylorMullen, @rynowak this is my first attempt. although the test passes, I would like to get your opinion about the approach.

Thanks @grahamehorner. I'll try to address that too...

Your email has been reported as SPAM and your email domain will be blocked if you continue to send unsolicited emails repeatedly.
iot-cloud
Gabriel Cloud System Limited
4 St. Gabriel Ave, Riverside Village,
Hebburn, Tyne & Wear, England NE31 1AG
CAUTION:This email and any attachments transmitted with it contain information that is CONFIDENTIAL and may be privileged or otherwise protected from disclosure. If you are not the intended recipient please notify us immediately and delete all copies of this email message and any attachments transmitted with it from your system. If you are not the intended recipient, any use, disclosure or copying of this email message and any attachments transmitted with it is strictly prohibited. This email message and any attachments transmitted with it cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed or incomplete. Although we routinely screen for viruses, it makes no representation or warranty as to the absence of viruses in this email or any attachments. The views expressed in this email are those of the sender and not necessarily those of Gabriel Cloud Systems LTD; if you require clarification please contact the sender.
proud sponsors of
Hebburn Town Juniors FC
(Junior Madrid)
Get Outlookhttps://aka.ms/sdimjr for iOS

From: Artak Mkrtchyan<EMAIL_ADDRESS>Sent: Tuesday, February 13, 2018 4:11:54 PM
To: aspnet/Razor
Cc: Grahame Horner; Mention
Subject: Re: [aspnet/Razor] Ignoring HTML comments in tag helper's body (#2061)
Thanks @grahamehornerhttps://github.com/grahamehorner. I'll try to address that too...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/Razor/pull/2061#issuecomment-365315452, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADvjzS4Dho9mPWSTV5TPnYrGp9QOlmIdks5tUbRIgaJpZM4SDRQn.
CAUTION: This email and any attachments transmitted with it contain information that is CONFIDENTIAL and may be privileged or otherwise protected from disclosure. If you are not the intended recipient please notify us immediately and delete all copies of this email message and any attachments transmitted with it from your system. If you are not the intended recipient, any use, disclosure or copying of this email message and any attachments transmitted with it is strictly prohibited. This email message and any attachments transmitted with it cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed or incomplete. Although we routinely screen for viruses, it makes no representation or warranty as to the absence of viruses in this email or any attachments. The views expressed in this email are those of the sender and not necessarily those of Gabriel Cloud Systems LTD; if you require clarification please contact the sender.

Ok folks. I've finished updating all the tests and everything is passing now. @NTaylorMullen, there is one issue I've noticed, which I would like to change, but wanted to run this by you first. When there is non-closed comment tag, the actual markup after the opening comment tag is not part of the comment block, but a new markup block. While this is a corner case scenario, I think it should still be part of the comment block, so I'd be happy to fix that too, if you agree.

Does this need a feature/version flag? This is a change in what the language accepts?

When there is non-closed comment tag, the actual markup after the opening comment tag is not part of the comment block, but a new markup block. While this is a corner case scenario, I think it should still be part of the comment block, so I'd be happy to fix that too, if you agree.

Hmm, so we need to abide by the HTML5 spec. It has rules for classifying what an HTML comment is and is not.

Does this need a feature/version flag? This is a change in what the language accepts?

Yes, for older versions of the runtime we need to still disallow HTML comments.

@ajaybhargavb , @NTaylorMullen please look through one more time. Thanks!

looking good to me, thanks for all your work on this guys

@ajaybhargavb, I've applied your feedback. The algorithm looks good, I've added cases and clarifying comments to show that all the cases are covered.

Thanks for the feedback, guys! The build is constantly failing on Mac, but succeeding on Linux. The failure is unrelated to the code change, so I'm going to finalize this now.


Error importing data_helpers in train.py

In train.py at line 13
import data_helpers
No data_helpers.py is available in the repo. And the function it calls to is batch_iter which is part of data_utils.py!

Thanks for pointing it out.
I am closing this issue as you have already resolved it with the PR.


chore(npm): sync package.json from npm-package-template

engines, version, release scripts for semantic-release, mocha, jsdoc and istanbul

Current coverage is 28.37%

Merging #9 into master will not affect coverage as of 6f81efe

@@            master      #9   diff @@
======================================
  Files            4       4
  Stmts           74      74
  Branches         8       8
  Methods          0       0
======================================
  Hit             21      21
  Partial          0       0
  Missed          53      53

Review entire Coverage Diff as of 6f81efe

Powered by Codecov. Updated on successful CI builds.


new node 20 version for pre-builds

@darora are you still able to help with pre-builds?
@benasher44 was interested in supported pre-builds for Node.js 20

cc @tomquist


Integrate genType docs into main docs as "TypeScript interop"

genType has moved into the compiler since 10.1 and flow support has been dropped
Let's move its docs into the main section as "TypeScript interop". Remove all mentions of "flowtype" and "Reason" and update the docs.

IMHO TypeScript interop shouldn't be treated as special. Except for gentype-specific config, most of it is required for general JS codebase interoperability. Instead, we can say that TypeScript is supported natively.
Instead of the "TypeScript interop" chapter, I suggest providing more generally useful guides in a "Working with JavaScript/TypeScript projects" chapter.
For example, https://rescript-collection.pages.dev/docs/javascript#pipe-operator describes how dealing with pipe patterns in JS codebase.

Moving those issues over from #697

[ ] GenType: Add moduleResolution option to customize extensions on emitted import statements. This helps to adjust output compatibility with TypeScript projects using ESM. https://github.com/rescript-lang/rescript-compiler/pull/6182

node (default): Drop extensions.
node16: Use TS output's extensions. Make it ESM-compatible.
bundler: Use TS input's extensions. Make it ESM-compatible.

[ ] GenType: add the option to use the @genType annotation at the module level, meaning that all the items in the module should be exported. https://github.com/rescript-lang/rescript-compiler/pull/6113
[ ] GenType: add support for @genType annotations on module definitions. https://github.com/rescript-lang/rescript-compiler/pull/6113
[ ] GenType: removed support for @genType.as for records and variants which has become unnecessary. Use the language's @as instead to channge the runtime representation without requiring any runtime conversion during FFI. https://github.com/rescript-lang/rescript-compiler/pull/6099 https://github.com/rescript-lang/rescript-compiler/pull/6101


boundingBoxGizmo dragging is buggy since v7.21.0

Repro

Bug repro on playground:
Expected result: Gizmos should follow the dragged direction
Current result: Gizmo drag axis are twisted (e.g. horizontal rotation gizmos are rotated by moving the mouse vertically)

Also, some of the gizmos have a wrong orientation, see the following screenshot:

Desktop (please complete the following information):

OS: Microsoft Windows 11 Business (10.0.22631 Build 22631)
Browser MS Edge
Version 128.0.2739.42 (Official build) (64-bit)

Additional Context
The styling of gizmos has changed in https://github.com/BabylonJS/Babylon.js/releases/tag/7.21.0. See https://github.com/BabylonJS/Babylon.js/pull/15415 for reference.

https://github.com/BabylonJS/Babylon.js/pull/15487
Thanks for testing snapshots when they are available @kai-dorschner-twinsity

Thank you guys for being this quick in solving issues 💯

Hey guys! There might've been an oversight regarding the issue. Title title said that the dragging itself is buggy, and, as a side node the handles are also twisted. As far as I can see only the twisted handles have been fixed, but not the dragging itself.
See playground to verify.
To be more precise:

grabbing the left middle handle, the rotation around the Y axis should happen by moving the mouse horizontally on the X axis, though it only rotates by moving the mouse vertically on the Y axis.
Here's an images indicated in RED what is expected and in BLUE what is actual

This goes on for many, but not all handles, here's a (maybe incomplete) list of broken and correct handles (RED: broken, GREEN: correct):

I'm taking a look.

I did 2 passes of testing https://github.com/BabylonJS/Babylon.js/pull/15503
thanks for doing checks on your side @kai-dorschner-twinsity :)


Add option for propagating all environment variables

Per the Elastic CI for AWS guidance (https://github.com/buildkite/elastic-ci-stack-for-aws#what-type-of-builds-does-this-support):

Each project should encapsulate it's dependencies via Docker and Docker Compose

This results in using this plugin for setting up build dependencies. It would be nice to add an option to propagate all environment variables to the container, e.g.
steps:
  - command: "echo \$BUILDKITE_COMMIT"
    plugins:
      - docker#v2.0.0:
         image: bash

Rather than having to specify that BUILDKITE_COMMIT propagates to the container (with environment)

Agreed! Any suggestions on what the syntax for that would look like?
steps:
  - command: "echo \$BUILDKITE_COMMIT"
    plugins:
      - docker#v2.0.0:
         image: bash
         build-environment: true

I think something like propagate-env: true or include-all-env: true or automatic-environment: true avoiding something like build as that is a bit confusing re docker build
steps:
  - command: "echo \$BUILDKITE_COMMIT"
    plugins:
      - docker#v2.0.0:
         image: bash
         propagate-env: true

Just to be clear… we'd just want the job environment variables sent down from the agent yeah? Not necessarily any environment variables picked up from the Elastic CI Stack environment? (like secrets)

I would have thought all of them, e.g what you'd normally have in a naked step?

Yeah, I'd imagine that we'd load all of them via the envfile.


Getting lstat error from docker on tcga1

Note: It is not clear that this issue belongs in Toil.
When I run a docker container from a toil script on tcga1 (CentOS), I get a persistent error:
lstat /inside/depot/users/jeltje/aligns/tmpVno9c1/localTempDir: permission denied"

This kills the job, deleting the tmp dir that had the problem (too fast to have a look at permissions).
This problem does not occur in on my Ubuntu VM.
I created a very simple docker container that creates a file, runs ls -l, deletes the file, then sleeps for 3 minutes. It works fine on the tcga1 command line, but when run via the toil script it dies almost instantly. Apparently it doesn't even get to the docker run (otherwise it would sleep before dying).
the failing script
wrapper to run it
stderr
I also created a non-docker toil script (bash echoes a statement). This script works fine.
the working script
wrapper to run it
stderr

Try adding
subprocess.check_call( [ 'ls', '-ld', work_dir ] )

just before
    with open(os.path.join(work_dir, uuid + '.bam'), 'w') as f_out:
        subprocess.check_call(docker_cmd + bamsort_command, stdout=f_out)

in the failing script. It's definitely a permission problem and we may be able to work around it generally in Toil.

The plot thickens...
From the error log:
WARNING:toil.leader:B/S/jobNJ0NCW:      WARNING:toil.resource:Can't localize module ModuleDescriptor(dirPath='/inside/home/jeltje/exp/readalign/git/toil-scripts/batch-alignment', name='toil_sleepy', extension='.py')
WARNING:toil.leader:B/S/jobNJ0NCW:      drwxrwxrwx 2 jeltje protein 2 Oct  1 11:22 /inside/depot/jeltje/aligns/tmpKI8QCz/localTempDir
WARNING:toil.leader:B/S/jobNJ0NCW:      time="2015-10-01T11:22:50-07:00" level="fatal" msg="Error response from daemon: lstat /inside/depot/users/jeltje/aligns/tmpKI8QCz/localTempDir: permission denied"

So the directory gets created as me, with full permissions.
I tried to find the lstat command from inside the docker container, but it doesn't come standard (weirdly) and I can't figure out which package to apt-get. Looks like it's docker itself that's doing this.

AHA! ls -d one level up:
WARNING:toil.leader:1/D/job6Du4tp:      drwx------+ 3 jeltje protein 4 Oct  1 11:42 /inside/depot/jeltje/aligns/tmpZQ4Wde

And what user does the docker daemon run as? I should be root, just double-checking.

Correct. User root, group root.

So this could be SELinux getting in the way. Could you send the contents of /etc/sysconfig/docker if it exists and is readable? Also, try adding this to your user script, just before the docker invocation:
subprocess.check_call( [ 'chmod', 'go+rx', work_dir, work_dir + '/..' ] )

Leave the ls invocation in place for verification that the chmod worked.

That totally fixed it!
Docker runs as expected now and creates correct output.
# /etc/sysconfig/docker
other_args="--graph=/data/docker"
DOCKER_CERT_PATH=/etc/docker

I suppose this is not the preferred fix, though?

We could ask the admins to add --selinux-enabled=false to /etc/sysconfig/docker in order to confirm that it is indeed SELinux that is causing this. I doubt they would want to disable it permanently and I doubt they have the time to do so temporarily just for us to confirm a hypothesis. Your call.
Ultimately, we should support running docker under SELinux. We could brute force it by always chmod'ing the work dir and its parent in the above way.
What is /inside/depot/jeltje/aligns? Is this a directory that you chose? Is it your home? Is it your TMPDIR?

It's my TMPDIR. inside/depot has several terabytes free so I can mess around with large bam files to my heart's content.

SElinux was disabled by Erich, but this doesn't fix the problem
# /etc/sysconfig/docker
other_args="--graph=/data/docker --selinux-enabled=false"
DOCKER_CERT_PATH=/etc/docker

If I leave the chmod command out of my toil script, I get the original problem again:
WARNING:toil.leader:i/k/jobIRPbYs:      drwx------+ 3 jeltje protein 4 Oct  2 09:04 /inside/depot/jeltje/aligns/tmpxXVAst
WARNING:toil.leader:i/k/jobIRPbYs:      drwxrwxrwx 2 jeltje protein 2 Oct  2 09:04 /inside/depot/jeltje/aligns/tmpxXVAst/localTempDir

So it looks like this a caused by a combination of facts:

The file is in a subdirectory of $TMPDIR
TMPDIR points at an NFS
The NFS is mount with root-squash (hypothesized)
Docker is running as root
The file, its parent, and its grandparent are owned by a different user (jeltje)
The grandparent was created by Python's tempfile.mkdtemp with mode 700

Overriding the mode or moving TMPDIR to a FS on a locally attached drive both fix the problem.
The question now is: Do we work around it in Toil by overriding the mode of work_dir and its parent to 755? I hesitate due to the specificity of the factors listed above.

Or maybe it should be a note in the toil manual eventually, describing a special case and the chmod solution?
Is it possible to have the toil system check permissions when it creates a tmpdir and issue a (non fatal) warning? That may save the next victim some time.

We'll enforce the mode to 755 for localWorkerTempDir.

Related to #480.


[Gene Expression] Heatmap Tooltip CellType Shows Tissue Id instead of CellType Name

Bug:
In prod - Heatmap Tooltip CellType Shows Tissue Id instead of CellType Name
Private Zenhub Image
DoD:

Fix this bug
Add a test to catch this bug

@niknak33 @signechambers1  please help add a priority tag thank you!

I put it down as a P0, mainly because it is a data quality issue. There is no workaround to the cell type, as the data in the field corresponds to a tissue ID. @signechambers1 let me know if you feel different.

Awesome thanks, Nik! @seve I know you have adding WMGv2 new tests this week, but are you able to send out a fix for this today 🙏 ? Thanks so much!

Should the tooltip still say Cell Type for organisms? I'm going to fix the bug and push for merging this because of the priority, but we may want to open a seperate ticket to address.

Should the tooltip still say Cell Type for organisms? I'm going to fix the bug and push for merging this because of the priority, but we may want to open a seperate ticket to address.
CC: @hthomas-czi @niknak33

@seve Just to double check: you meant the tooltip should say "Tissue" instead of "Cell Type" for tissue rows, right?


[INFINITY-2881] Move from HTTP to MESOS_HTTP health-checks on schedulers

@elezar Thanks.  Good catch.