Eventing - Fix issue re timers in the v5.5 docs set #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Review complete. Looks good |
amarantha-k
pushed a commit
that referenced
this pull request
Oct 26, 2018
* Eventing - Fix issue re timers in the v5.5 docs set (#3) * Incorporating feedback * Incorporating feedback * incorporating feedback * Incorporate feedback * Incorporating feedback * Incorporating feedback * Incorporate feedback * DOC:3816: Changes to the doc as suggested in the bug along with local Git conflicts are resolved * DOC-4084: Adding Timers content consolidation section * DOC-4083: Indiv pages for each example and updates to the nav file * DOC-4019:Reordering of FAQs * DOC-4086:Added Timers page to the TOC * DOC-4083:updates to source and metadata bucket sections * DOC-4084:updates to timers page * DOC-4019: minor updates * DOC-4084: changes to the timers section * DOC-4307: Testing merging * DOC-4306: Testing merge pass, undoing the test change * DOC-4306: Added Author's note for Timer related content before Timers remote branch merge * DOC-4083: changes to source and metadata buckets sections. Added a link for TS and BP sections * DOC:4306: Heading changes to the example4 page * DOC-4306: Content changes in debug and timers sections + formating changes to other pages * DOC-4306: Incorporated changes as per initial PM review * DOC-4306:Suggested changes from AK has been incorporated * DOC-4306:Minor formating change the heading style * DOC-4306: Added short description for FAQ section * DOC-4306:QA suggested changes to the source bucket. Fixed * DOC-4306:changes to the FAQ section, parent bucket reworded
amarantha-k
pushed a commit
that referenced
this pull request
Oct 29, 2018
* Eventing - Fix issue re timers in the v5.5 docs set (#3) * Incorporating feedback * Incorporating feedback * incorporating feedback * Incorporate feedback * Incorporating feedback * Incorporating feedback * Incorporate feedback * DOC:3816: Changes to the doc as suggested in the bug along with local Git conflicts are resolved * DOC-4308:Changes as suggested in the bug
amarantha-k
pushed a commit
that referenced
this pull request
Oct 29, 2018
* Eventing - Fix issue re timers in the v5.5 docs set (#3) * Incorporating feedback * Incorporating feedback * incorporating feedback * Incorporate feedback * Incorporating feedback * Incorporating feedback * Incorporate feedback * DOC:3816: Changes to the doc as suggested in the bug along with local Git conflicts are resolved * DOC-4309:Updates as suggested in the bug
jon-strabala
added a commit
that referenced
this pull request
Feb 26, 2020
#1 Note "debugPort" is wrong it will not work the correct name is "eventing_debug_port" #2 The example is wrong it must be terminated by a period for example if we had the following in static_config {eventing_debug_port, 9444} {net_kernel_verbosity, 10} The couchbase server WILL NOT start but if we add a period after the closing brace {eventing_debug_port, 9444}. {net_kernel_verbosity, 10}. The couchbase server starts #3 make the syntax clear e.g. add "(enclosed in braces and terminated by a period)" #4 warn that this will flush all data and restart the server from scratch, e.g. "WARNING: Changing port mapping should be done on the initial node/cluster setup as the required reset and reconfiguration will also purge any data on the node. "
amarantha-k
pushed a commit
that referenced
this pull request
Mar 3, 2020
#1 Note "debugPort" is wrong it will not work the correct name is "eventing_debug_port" #2 The example is wrong it must be terminated by a period for example if we had the following in static_config {eventing_debug_port, 9444} {net_kernel_verbosity, 10} The couchbase server WILL NOT start but if we add a period after the closing brace {eventing_debug_port, 9444}. {net_kernel_verbosity, 10}. The couchbase server starts #3 make the syntax clear e.g. add "(enclosed in braces and terminated by a period)" #4 warn that this will flush all data and restart the server from scratch, e.g. "WARNING: Changing port mapping should be done on the initial node/cluster setup as the required reset and reconfiguration will also purge any data on the node. "
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.