Overwrite existing values when picking "node types"

This might be a help question, rather than a real issue. If so, sorry!
In  this instance, roads with possibly wrong maxspeeds are shown. Four node types are available, three of which offer a correction to the current maxpeed value. I have set the correct value (90 or 70) in the "Nodes types" descriptions. However, when I select a "wrong" road with current maxspeed=90 and try to set it to one of the "Node types" with maxspeed=70, the tag value isn't changed by default. I played around with the settings, but nothing seemed to work.

Hi @joostschouppe,
I think you're right, I will do that.

Do think about it, maybe it has some side-effects in other use cases.
It would also be useful to have a visible difference between adding tags and changing key values...

When the contribution column is opening, the tags are are displayed in that order:

Presets tags
Non-OSM data tags
OSM element tags

Currently, the last tag displayed overwrites the previous ones so OSM tags are always wining. I propose to keep that behavior except when a preset tag has is value set to read only.
In that way, you can set presets and force values without breaking the old behavior. Is that ok for you?

Yes, the behaviour seems fine. That would imply that a "read only preset" means that "this preset will not be overwritten by the original OSM element tag". That doesn't sound very intuitive to me. How about calling these fields "overwrite existing key", "overwrite existing value"?

I don't think that changing the labels to overwrite existing stuff is the best move because:

You can't overwrite a key. If your key is different, it will display another tag in the contribution form.
You can indeed overwrite a value, but it is not the only feature. The initial purpose was to set a default value for a tag.

But I can add an information icon with explanations near the read only value checkbox, maybe it's the simpler choice. What do you think about it?

Or maybe, replace the Read-only value label with Read-only and forced value?

Ok I did the change, it will be released with the new MapContrib version coming soon :)
in the meantime, you can test it on the test instance if you want (changelog here).

@joostschouppe It's live in the 1.6.0 version and already available in the main MapContrib instance!

I was checking it out this very moment. Looks really good!
2017-03-17 12:12 GMT+01:00 Guillaume AMAT<EMAIL_ADDRESS>
@joostschouppe https://github.com/joostschouppe It's live in the 1.6.0
version and already available in the main MapContrib instance!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MapContrib/MapContrib/issues/252#issuecomment-287328126,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJp1jxdOFGPBUK79PgLuG9oNtMUQaAwLks5rmmqigaJpZM4Mdny0
.

--
Joost Schouppe
OpenStreetMap http://www.openstreetmap.org/user/joost schouppe/ |
Twitter https://twitter.com/joostjakob | LinkedIn
https://www.linkedin.com/pub/joost-schouppe/48/939/603 | Meetup
http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/


Make divline a valid child of layer

We added the module model.layerPart.neumes to divline in MEI.neumes.xml to make divline a valid child of layer. We have also validate the new schema. Attached are the screenshot of the successful validation, the new schema, and the test file. Please let us know if there is a better way to do this. Thank you!

[fix_divline.zip](https://github.com/music-encoding/music-encoding/files/7305020/fix_divline.zip)

Hi @yinanazhou ,
could you please explain a little more why you made this change, and what issue you are trying to fix?
Typically we try to raise an issue about these types of changes before submitting a PR so that others know the reasons and justification for the change, and whether other options have been explored to fix your particular issue without changing the schema.
Thanks!

Hi @ahankinson, sorry about that! I have raised issue #861 about this PR to explain the reasons. Please let me know what you think. Thank you!


Can't add parameter to header

Here is the code that I have
`public class SetVersionHeader : IOperationFilter
{
public void Apply(Operation operation, OperationFilterContext context)
{
		var parameter = new NonBodyParameter();
		parameter.Name = "api-version";
		parameter.In = "2";
		parameter.Type = "integer";
		try
		{
			if (operation.Parameters == null)
			{
				operation.Parameters = new List<IParameter>();
			}
			operation.Parameters.Add(parameter);
		}
		catch (Exception ex)
		{

			throw ex;
		}
	}
    }

}`
and in my startup class
`private void ConfigureSwaggerServices(IServiceCollection services, List SwaggerInfo)
{
services.AddSwaggerGen(c =>
{
c.MultipleApiVersions(
SwaggerInfo,
ResolveVersionSupportByVersionsConstraint
);
			c.OperationFilter<SetVersionHeader>();
			c.DescribeAllEnumsAsStrings();
		});

		services.ConfigureSwaggerGen(c =>
		{
			c.IncludeXmlComments(GetXMLFile());
		});
	}`

I am able to get the header to appear in the UI

But they don't appear in the header

What is the deal?

nevermind I figured it out.  The In variable was wrong.


Implement locking in DNS resolver

Updated #33260; please take a look at the last commit there in case there's something that should be shifted to this PR.

please take a look at the last commit there in case there's something that should be shifted to this PR.

The last commit looked good, no need to shift anything to this one. I will give +1 after it is normal PR.


Inference task could not be completed

Non of the AI models are working ? "Inference task could not be completed"  CRITICAL    Error : Inference task could not be completed

hello, which OS and QGIS version are you using?
Please make sure the plugin has access to the models (Settings -> Models Directory) and the right input layer is selected (RGB raster layer). If you are using "current view" as extent it is not necessary for the layer to only have RGB bands.


GEODE-6115: add log4j dependency to jmh compile

This will fix the issue of IntelliJ builds sometimes not inheriting the
dependency from main at compile time. At worst, this line will be
redundant, at best it will provide the required dependency for the
build.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Upgrade test failure is a known flaky test.
https://issues.apache.org/jira/browse/GEODE-5625


chore: create buildroot files for notify-server

Overview
Create files required to include notification server in buildroot build
Acceptance criteria

[ ] buildroot.mk created
[ ] Config.in created
[ ] monorepo project added to buildroot project.


[338] Personal detail progress state

Context

https://trello.com/c/oozmGsPe/338-m-personal-details-progress-state

Changes proposed in this pull request

Implements storing of progress for different sections using a jsonb column as per this spike https://github.com/DFE-Digital/register-trainee-teachers/pull/95
Bundles the https://github.com/DmitryTsepelev/store_model gem to allow us to wrap jsonb columns in ActiveModel like objects.
Introduce a service to check for the progress state for a particular section. The ProgressService accepts a validator object (which can be an ActiveModel or ActiveRecord object) and a progress value which comes from one of the section values via trainee.progress.#{section_key} and will return one of three status values defined in Progress::StATUSES. This model is simply an activemodel wrapper around the progress jsonb column provided by the gem above.
This PR lays the foundation for toggling the progress field for all the current sections in the Trainee summary page.
This PR only implements querying the status for the personal details section. Other sections will need to be added in separate PRs. We would just need to call ProgressService.call(validator:, progress_value:) giving it a model which deals with the values for that section and the progress value from the trainee.progress. This same service can be used in a controller before_action to redirect straight to the confirmation page if that section has been filled out.

Guidance to review

Visit the review app https://dfe-twd-rttd-pr-161.herokuapp.com/
Build a trainee, go to the overview page and assert the personal detail section says  not started
Fill in some valid details, confirm without marking for complete, the section should say in progress
Go back to the personal details, mark as complete and save, the section should say completed.

If you go back and uncheck mark as complete, then return the overview - the personal details section should revert to in progress.

 [M] Personal details progress/state

 Contact details progress/state


Research index operation permission check

Research how to run permission check for index operation when user choose that option from action dropdown list

Didn't find an elegant solution to check permissions required to run an operation. We have a workaround but hesitate to implement it due to potential side impact, since the requirement is a nice to have, we prefer to wait for security team to provide a general solution.


feat: Added expire and issued timestamps in attachment

Added methods to extract expiration and issued timestamps from url
dpp::embed test{};
test.set_title("Test for file")
    .add_field("filename", fileAttachment.filename)
    .add_field("description", fileAttachment.description)
    .add_field("url", fileAttachment.url)
    .add_field("proxy_url", fileAttachment.proxy_url)
    .add_field("Expiration timestamp", std::to_string(fileAttachment.get_expire_time()))
    .add_field("issuing timestamp", std::to_string(fileAttachment.get_issued_time()));

Code change checklist

[x] I have ensured that all methods and functions are fully documented using doxygen style comments.
[x] My code follows the coding style guide.
[x] I tested that my change works before raising the PR.
[x] I have ensured that I did not break any existing API calls.
[x] I have not built my pull request using AI, a static analysis tool or similar without any human oversight.

approved and good to merge, would be nice if there were unit tests for this though

A todo list for stuff would be lovely


error on container run "exec format error"

Run command:
podman run -d --name hildr-1711574776203 \
-v "/home/ubu/.config/NiceNode/nodes/hildr-1711574776":/data:z -p 8549:8549  \
ghcr.io/optimism-java/hildr:latest-native  --sync-mode full --jwt-file /data/jwtsecret \
--l1-rpc-url http://<IP_ADDRESS>:8545/ --l1-ws-rpc-url http://<IP_ADDRESS>:8546/ \
--l1-beacon-url http://<IP_ADDRESS>:5052/ --l2-rpc-url http://host.containers.internal:8547/ \
--l2-engine-url http://host.containers.internal:8553/ --rpc-port 8549 --network optimism

error: {"msg":"exec container process /usr/local/bin/hildr-node: Exec format error","level":"error","time":"2024-03-27T21:30:15.845010Z"}

ghcr.io/optimism-java/hildr:latest-native image execution platform architecture only supports linux/amd64. I think it may be that the platform architecture does not match.

On a linux/amd64 architecture server, I tested running with Docker and it ran normally.

Ah yes, I was testing on an arm64 board. noted

Ah yes, I was testing on an arm64 board. noted

Indeed a bug in native image, i just published v0.3.3, you can retry once the new image generated.

Just tried. Seems like same {"msg":"exec container process /usr/local/bin/hildr-node: Exec format error","level":"error","time":"2024-03-28T23:48:48.314113Z"}

Just tried. Seems like same {"msg":"exec container process /usr/local/bin/hildr-node: Exec format error","level":"error","time":"2024-03-28T23:48:48.314113Z"}

@thinkAfCod Can you help to check?

I may not be able to reproduce the issue you encountered. Could you provide more environment information?
This is the result of running uname -a on my server:
Linux VM-0-4-ubuntu 5.15.0-86-generic #96-Ubuntu SMP Wed Sep 20 08:23:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Then,I tried to start using Podman on the server.
At the same time, I ran the image using Podman on my own Mac.
This is the result of running uname -a on my Mac:
Darwin MacBook-Pro 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000 arm64

Podman version info on my Mac:
Client:       Podman Engine
Version:      5.0.0
API Version:  5.0.0
Go Version:   go1.22.1
Git Commit:   e71ec6f1d94d2d97fb3afe08aae0d8adaf8bddf0
Built:        Tue Mar 19 17:47:46 2024
OS/Arch:      darwin/arm64

Server:       Podman Engine
Version:      5.0.0-dev-8a643c243
API Version:  5.0.0-dev-8a643c243
Go Version:   go1.21.8
Built:        Mon Mar 18 08:00:00 2024
OS/Arch:      linux/arm64

On the Mac, if executed directly, it will prompt to initialize the virtual machine and provide corresponding instructions. Follow the instructions provided to initialize the virtual machine:
podman machine init
podman machine start

Then start the container with the additional --platform linux/amd64 parameter compared to on the server:
podman run --platform linux/amd64 --rm --name hildr -p 8549:8549  ghcr.io/optimism-java/hildr:v0.3.3-native \
--sync-mode full --jwt-secret bf549f5188556ce0951048ef467ec93067bc4ea21acebe46ef675cd4e8e015ff \
--l1-rpc-url https://eth-sepolia.g.alchemy.com/v2/<token_id> \
--l1-ws-rpc-url wss://eth-sepolia.g.alchemy.com/v2/<token_id> \
--l1-beacon-url https://few-sleek-sound.ethereum-sepolia.quiknode.pro/<token_id> \
--l2-rpc-url http://<IP_ADDRESS>:8545 --l2-engine-url http://<IP_ADDRESS>:8551 --rpc-port 8549 \
--network optimism-sepolia

What surprised me is that it could actually start normally.
Because on a Mac, even with the --platform linux/amd64 parameter added, Docker still prompts an error:
The current machine does not support all of the following CPU features that are required by the image: [CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA].
Please rebuild the executable with an appropriate setting of the -march option.

On the Mac, when I shut down the virtual machine and remove the --platform linux/amd64 parameter, the startup will display the following error message, but it does not prompt the expected exec Format error message:
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM

sorry, wasn't using a proper archival rpc for l1 🤕


run sample fail because of webview2

is it possible to support old edge ?

Certainly, but only if someone implements it. If you're interested, please consider sending a PR :)

@drearyrainDeng you can start playing with #16

well done!


Fix:v2 rn 0 69 crash

Summary
NativeBase v. 2 causes a crash when used within a project running React Native v. 0.69 and higher.
Check out this issue Native-Base 2.15.2 incompatible with React-Native 0.69 #5358
This is because prop types have been internally in RN changed to static type checking using Flow - see RN Changelog. prop types are no longer available in the react-native package and calling this api will throw an invariant error.
For backwards compatibility RN team created a separate package deprecated-react-native-prop-types.
This PR simply changes the calls to deprecated internal API to the new ones from the dedicated package.
Changelog
[General] [Fixed] - fixed a crash on projects using react-native v. 0.69 and later caused by calling removed prop-types API
Test Plan
No tests planned for this.

when can we expect a release for this in v2? It's preventing a build on RN 0.69.

@inspmoore Thank you for that PR!
when can we expect a release for this in v2? It's preventing a build on RN 0.69.

My pleasure. I'm not a maintainer of this repo, so I guess it's a question for @rayan1810.

@rayan1810 @surajahmed can we please have this merged in v2. It's critical and preventing production use of v2 with RN 0.69

Do we have any news? I am stuck with expo SDK47 as well.

@inspmoore Is there any solution to this? It's critical for me

@inspmoore Is there any solution to this? It's critical for me

@GSolari79 You're welcome to use my clone until that fix is merged. I'm using it on my production app. This is what you have to add to your package.json
  "dependencies":  {
    "native-base": "https://github.com/inspmoore/NativeBase.git#fix/v2-rn-0-69-crash",
}

@rayan1810 is there anything I can help with to make this fix be merged and deployed?

@rayan1810 @surajahmed @ankit-tailor
Nativebase 2.15.2 is the second most downloaded version according to NPM.  This should be a high priority review.

@rayan1810 @surajahmed I totally agree with @kpheasey.

Native Base 3.0 is basically an entirely different project. Im not sure why the name was kept the same. It's not even remotely similar. No migration shim was provided. Its an i
@inspmoore Version 2 should be permanently forked and maintained if a 2 month old critical patch can't be merged in.

@rayan1810 Can this be merged and released in native-base v2 as a new version to support RN 0.69+?


Upgrade Cassandra to 4.1.0

Ensured that all existing unit and integration tests for Cassandra passed.

Thanks @sekikn


Init with date value on input messes up format (problem 2)

Describe the bug
When having 2 inputs with the value filled with a correct date, litepicker rearranges the DD-MM. This is unwanted behaviour.
To Reproduce
See codepen down below
Expected behavior
Litepicker should leave the format as it's written in the value and not messing it up or rehussle it.
jsfiddle.net / codepen.io / etc
https://codepen.io/kevinmu/pen/PoZNXzB (SEE PROBLEM 2)
The weirdest thing is, this happens only with certain values like in the pen now. But when starting the input with dates like 15-07-2020 > 28-07-2020 it is working like it's supposed to. So my gues is that it has something to do with the days + months having a 0 as a starting number.

fixed in v1.4.7

I too was seeing this problem and am not anymore after the v1.4.7 update. In fact, @kevinmu17 's CodePen to have the Litepicker version the problem is resolved:

I did notice the regular CDN link is still not updated to v1.4.7.


Copy to release/

pypa/gh-action-pypi-publish is too greedy and thinks docs.tar.gz is another python package. Unfortunately svenstaro/upload-release-action doesn't support multiple paths besides globbing.
Keeping dist/ only for PyPI and staging release files in release/ to mitigate this problem.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.00%. Comparing base (74c3299) to head (7db00a6).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #37   +/-   ##
=======================================
  Coverage   98.00%   98.00%
=======================================
  Files           2        2
  Lines          50       50
  Branches        8        8
=======================================
  Hits           49       49
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


changed the logout button further right

The tools and settings menus seem to me crammed between the logout button and the language settings. I would suggest to place the logout botton further right, maybe even to the right of the helper icon. Like that the UI features the two important drop-down menus more prominently.

IMO the order should be (from left to right):

Logout
Settings/Tools
Tools/Settings
Language
Help Icon

@v1r0x which is exactly the current layout. While using it yesterday I found it more important and intuitive if the tools and settings are the first things within the menu. People are interacting more with those I think.


How to register a built-in extension module?

I have a Rust app that hosts Python interpreter.  I want to register a built-in module so that Python code can call back into the app.
Not sure how to convert #[pymodule] fn ..., into something I can give to PyImport_AppendInittab...  Also, I need to support both Python 2 and 3, and it looks like I can't use wrap_pymodule! with Python2?
Would you mind providing an example?

I made it https://github.com/kngwyu/pyo3/blob/append-init-tab-example/examples/word-count/src/main.rs
But honestly I don't know when we should use PyImport_AppendInittab.
I also wrote an example of exposing function via locals(example2) and think it's enough for most cases.
Could you please let me know you use case more concretely?

Sidenote: It's normally better to use PyModule::new() instead of make_module because make_module is not part of the public api (it's marked as #[doc(hidden)])

Also, I need to support both Python 2 and 3, and it looks like I can't use wrap_pymodule! with Python2?

Yes, wrap_pymodule! currently only supports python 3, because python 2 support would required some work on the python2 part which is going to be removed soon anyway.

@kngwyu: PyImport_AppendInittab is typically used when a module only makes sense in the context of an application (for example if Python is used for scripting application logic), so module code is linked statically to the main app binary.
The solution I can up with is this:
unsafe {
    #[cfg(Py_2)]
    let module_init = initmymodule;
    #[cfg(Py_3)]
    let module_init = PyInit_mymodule;
    pyo3::ffi::PyImport_AppendInittab("mymodule\0".as_ptr() as *const c_char, Some(module_init));
}

...but I was wondering if there's a more elegant way to do it..

because python 2 support would required some work on the python2 part which is going to be removed soon anyway.

I hope not before 1/1/2020?

I hope not before 1/1/2020?

No, definitely before. See https://python3statement.org/

As there has been no discussion on this question for some time, I'm going to close it. Thank you for the discussion.

As there has been no discussion on this question for some time, I'm going to close it. Thank you for the discussion.


Integration tests workflow pipeline issue

Describe the bug
Hello,
I am having trouble setting up the copilot-run-integration-tests.yml GitHub actions pipelines in my fork for chat-copilot.
Can you please point me to documentation or share some details on what should I set for values of these secrets?
Should I create an app registration in Azure and create a dummy username and password that can be used for testing ?
https://github.com/microsoft/chat-copilot/blob/583f2c3a9280977c51ddd04bcfbc989427444b57/.github/workflows/copilot-run-integration-tests.yml#L32C1-L32C1
      TenantId: ${{ secrets.COPILOT_CHAT_TEST_TENANT_ID }}
      WebApiClientId: ${{ secrets.COPILOT_CHAT_TEST_APP_AAD_WEBAPI_CLIENT_ID }}
      WebAppClientId: ${{ secrets.COPILOT_CHAT_TEST_APP_AAD_WEBAPP_CLIENT_ID }}
      Username: ${{secrets.COPILOT_CHAT_TEST_USER_ACCOUNT1}}
      Password: ${{secrets.COPILOT_CHAT_TEST_USER_PASSWORD1}}

To Reproduce
Steps to reproduce the behavior:

Run copilot-run-integration-tests pipeline.

Expected behavior
Documentation or comments required to understand the expected values for secrets.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform

Github actions
Additional context
Add any other context about the problem here.

If I don't wish to put my own AAD credentials in secrets, is there a way to create a temporary user in the app registration that would work? What do you do ?

@tushardhadiwal this is what we have done. we have a test user created that has access to the app. you should be able to create a user under the same tenant and then use that user's credentials in in the secrets.


do not merge: testing new jenkins slave

Closing this as it shows that the newly-added Jenkins slave is good to add to the pool of build nodes.


unexpected database load with JpaEventStorageEngine::fetchEvents ramping up

Basic information

Axon Framework version: 4.7.1
JDK version:  Amazon Corretto 17

Description
Hi,
We have identified an issue with one of our applications that is built using Spring Boot 3, JPA, and Axon Framework 4.7.1. In a particular environment, we have noticed that despite low traffic, the database load is uneven.

(requests to RDS grouped by query)
Upon investigation, we have found that JpaEventStorageEngine::fetchEvents appeared to be ramping up over time, as indicated by the increasing blue bars. It is worth noting that during this time period, there was no scaling activity apart from a single deploy at 23 Feb 1500, which only caused a small bump. Interestingly, the UPDATE token_entry statement shown in the yellow bars was running at a constant rate.
Is this something you've seen in the past? Any ideas on how we could investigate this further?
Expected behavior
During no load, JpaEventStorageEngine::fetchEvents should be invoked at a more-or-less constant rate.
Actual behaviour
In one of our environments, it ramped up over time.

What is the scale on the graph, and how many events are there? Since for a relational database all rows/events are considered the same, I would expect a fetch events query to be getting a bit slower over time. The tokens are limited in size, so indeed I would expect token-related operations to stay constant over time.

Closing this issue due to inactivity.
Feel free to add comments at a later stage, @junkdog, when your time allows it!
Based on that, we should be able to reopen the issue and work on it if necessary.


Race condition when creating security groups

I seem to be suffering from a race condition when creating security group in EC2.
The problem is intermittent but common.
The error message suggests that the security group does not exist. However it does if you look in the console. Since the same block of code that created the security group is trying to populate it I stands to reason that it's just too fast.
I put a sleep in the block in a hope that it might slow it down. < grasping at straws.
Below are some samples of error and code.
================================================================================
Error executing action `create` on resource 'aws_security_group[CloudX-rabbitmq-server-sg]'
================================================================================

AWS::EC2::Errors::InvalidGroup::NotFound
----------------------------------------
The security group 'sg-80f01ee4' does not exist

Resource Declaration:
---------------------
# In /tmp/kitchen/cache/cookbooks/x_provisioning/definitions/rabbitmq_servers.rb

  14:   aws_security_group "#{cloud['id']}-rabbitmq-server-sg" do
  15:     vpc cloud['vpc_id']
  16:     # 22 tcp - SSH aacess to linux servers.
  17:     # (1/2)5672 - RabbitMQ ports for web access, clustering and messaging.
  18:     sleep(2)
  19:     inbound_rules  [
  20:         {:port => 22, :protocol => :tcp, :sources => [node['x']['Provisioning']['Subnets']['Office'], cloud['vpc_cidr']] },
  21:         {:port => 5672, :protocol => :tcp, :sources => [node['x']['Provisioning']['Subnets']['Office'], cloud['vpc_cidr']] },
  22:         {:port => 15672, :protocol => :tcp, :sources => [node['x']['Provisioning']['Subnets']['Office'], cloud['vpc_cidr']] },
  23:         {:port => 25672, :protocol => :tcp, :sources => cloud['vpc_cidr'] }
  24:     ]
  25:   end

I'm guessing this is failing during tagging of the resource.  I have https://github.com/chef/chef-provisioning-aws/pull/299 in progress which should fix this

@morfien101 Are you still experiencing this issue with the ChefDK 0.9.0 and the latest version of chef-provisioning / chef-provisioning-aws ?  It should be fixed.