Fix tags for en-US JS pages

I want to know that all JS pages are tagged to their corresponding recipe in stumptown, so I can get complete results for the linting that will come out of #2784.
Acceptance criteria

[ ] scraper-ng identifies one and only one recipe for every JS page

Retitled in response to https://github.com/mdn/sprints/issues/2784#issuecomment-582889192.

Looked at the linter output for this and here's a checklist to burn down for some tagging party.
Non-unique recipes:

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Indexed_collections

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Working_with_Objects

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/Error

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/columnNumber

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/fileName

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/lineNumber

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/message

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/name

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/Stack

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/toSource

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/toString

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/EvalError/EvalError

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/InternalError/InternalError

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RangeError/RangeError

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ReferenceError/ReferenceError

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SyntaxError/SyntaxError

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypeError/TypeError

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/URIError/URIError

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WebAssembly/CompileError

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/Error.description

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/Error.number

[ ] https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/Error.stackTraceLimit

Missing recipe:

[ ] 1. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript
[ ] 2. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/About_JavaScript
[ ] 3. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Closures
[ ] 4. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/EventLoop
[ ] 5. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Differential_inheritance_in_JavaScript
[ ] 6. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Enumerability_and_ownership_of_properties
[ ] 7. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Equality_comparisons_and_sameness
[ ] 8. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Index
[ ] 9. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Introduction_to_using_XPath_in_JavaScript
[ ] 10. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions/Assertions
[ ] 11. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions/Character_Classes
[ ] 12. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions/Groups_and_Ranges
[ ] 13. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions/Quantifiers
[ ] 14. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions/Unicode_Property_Escapes
[ ] 15. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures
[ ] 16. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Language_Resources
[ ] 17. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference
[ ] 18. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/About
[ ] 19. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes
[ ] 20. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_fields
[ ] 21. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/constructor
[ ] 22. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/extends
[ ] 23. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/static
[ ] 24. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Deprecated_and_obsolete_features
[ ] 25. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Deprecated_and_obsolete_features/The_legacy_Iterator_protocol
[ ] 26. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators
[ ] 27. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Arithmetic_Operators
[ ] 28. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Array_comprehensions
[ ] 29. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Assignment_Operators
[ ] 30. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Bitwise_Operators
[ ] 31. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Comma_Operator
[ ] 32. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Comparison_Operators
[ ] 33. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Conditional_Operator
[ ] 34. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment
[ ] 35. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Expression_closures
[ ] 36. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/function
[ ] 37. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Generator_comprehensions
[ ] 38. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Grouping
[ ] 39. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Legacy_generator_function
[ ] 40. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Logical_Operators
[ ] 41. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing_operator
[ ] 42. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Object_initializer
[ ] 43. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Operator_Precedence
[ ] 44. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining
[ ] 45. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Pipeline_operator
[ ] 46. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Property_Accessors
[ ] 47. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax
[ ] 48. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/async_function
[ ] 49. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await
[ ] 50. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/class
[ ] 51. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/delete
[ ] 52. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/function*
[ ] 53. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/in
[ ] 54. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/instanceof
[ ] 55. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/new
[ ] 56. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/new.target
[ ] 57. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/super
[ ] 58. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/this
[ ] 59. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/typeof
[ ] 60. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/void
[ ] 61. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/yield
[ ] 62. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/yield*
[ ] 63. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions
[ ] 64. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Default_parameters
[ ] 65. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Method_definitions
[ ] 66. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/rest_parameters
[ ] 67. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/arguments
[ ] 68. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/get
[ ] 69. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/set
[ ] 70. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols
[ ] 71. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar
[ ] 72. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects
[ ] 73. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array
[ ] 74. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer
[ ] 75. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AsyncIterator
[ ] 76. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics
[ ] 77. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt
[ ] 78. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date
[ ] 79. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Generator
[ ] 80. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Infinity
[ ] 81. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl
[ ] 82. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Collator
[ ] 83. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat
[ ] 84. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat/DateTimeFormat_Options
[ ] 85. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat/formatRangeToParts
[ ] 86. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DisplayNames
[ ] 87. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ListFormat
[ ] 88. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Locale
[ ] 89. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat
[ ] 90. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/PluralRules
[ ] 91. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RelativeTimeFormat
[ ] 92. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Iterator
[ ] 93. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON
[ ] 94. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map
[ ] 95. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math
[ ] 96. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number
[ ] 97. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/defineProperty/Additional_examples
[ ] 98. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise
[ ] 99. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy
[ ] 100. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy/handler
[ ] 101. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Reflect
[ ] 102. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Reflect/Comparing_Reflect_and_Object_methods
[ ] 103. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set
[ ] 104. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer/Planned_changes
[ ] 105. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String
[ ] 106. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol
[ ] 107. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray
[ ] 108. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap
[ ] 109. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet
[ ] 110. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WebAssembly
[ ] 111. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/decodeURI
[ ] 112. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/decodeURIComponent
[ ] 113. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI
[ ] 114. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent
[ ] 115. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/escape
[ ] 116. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval
[ ] 117. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/isFinite
[ ] 118. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/null
[ ] 119. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/parseFloat
[ ] 120. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/parseInt
[ ] 121. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/undefined
[ ] 122. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/unescape
[ ] 123. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/uneval
[ ] 124. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements
[ ] 125. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/Legacy_generator_function
[ ] 126. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function
[ ] 127. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/block
[ ] 128. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/break
[ ] 129. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/class
[ ] 130. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const
[ ] 131. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/continue
[ ] 132. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/debugger
[ ] 133. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/default
[ ] 134. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/do...while
[ ] 135. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/Empty
[ ] 136. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export
[ ] 137. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for
[ ] 138. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for-await...of
[ ] 139. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for_each...in
[ ] 140. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...in
[ ] 141. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...of
[ ] 142. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function
[ ] 143. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*
[ ] 144. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/if...else
[ ] 145. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import
[ ] 146. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import.meta
[ ] 147. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/label
[ ] 148. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let
[ ] 149. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/return
[ ] 150. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch
[ ] 151. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/throw
[ ] 152. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/var
[ ] 153. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/while
[ ] 154. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/with
[ ] 155. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode
[ ] 156. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode/Transitioning_to_strict_mode
[ ] 157. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Trailing_commas
[ ] 158. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Shells
[ ] 159. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/JavaScript_technologies_overview
[ ] 160. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_Management
[ ] 161. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions
[ ] 162. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/at-cc-on
[ ] 163. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/at-if
[ ] 164. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/at-set
[ ] 165. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/ActiveXObject
[ ] 166. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/Debug
[ ] 167. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/Enumerator
[ ] 168. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/GetObject
[ ] 169. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript
[ ] 170. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_2015_support_in_Mozilla
[ ] 171. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_5_support_in_Mozilla
[ ] 172. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.1
[ ] 173. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.2
[ ] 174. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.3
[ ] 175. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.4
[ ] 176. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.5
[ ] 177. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.6
[ ] 178. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.7
[ ] 179. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.8
[ ] 180. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.8.1
[ ] 181. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.8.5
[ ] 182. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/The_performance_hazards_of__[[Prototype]]_mutation

@Elchi3 Thank you so much for doing this! 💯

I've fixed the "file-require-recipe-unique" ones. They are mostly because of error pages like ReferenceError() containing an "Error" tag. I wasn't sure whether we ought to remove them or choose something different to flag "javascript-error" recipes. But I decided to go for it in the end. But let me know if you think this was a bad choice, we can always reinstate.

I've tagged many more pages. The "funny" thing is that I'm now discovering pages I've never seen before. :neutral_face:

Some random thoughts for the remaining pages. Would love some feedback, so I feel more empowered to take some decisions :)
@chrisdavidmills What was the comment on the Microsoft docs in the PAB meeting? Do we need to start supporting this material in or stumptown efforts?
I'm not sure what to do with the "New in JS" pages. It's historical information. Maybe it should move to the archive?
https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat/DateTimeFormat_Options this is brand new. Someone created this. In APIs this would be a dictionary, I guess. I don't think I want to support this content type in JS docs, though. Not a fan of isolated dictionary docs.
If we remove the index page from jsSidebar, then I guess we could delete the index page.

I'm not sure what to do with the "New in JS" pages. It's historical information. Maybe it should move to the archive?

I know I'm not a decision maker on this, but I hope we delete or archive this stuff. All but one of those pages concerns changes that landed nearly a decade ago. I imagine BCD or browser release notes are going to be more meaningful for this sort of thing anyway.

If we remove the index page from jsSidebar, then I guess we could delete the index page.

I thought DocStatus used the index page: https://github.com/mdn/kumascript/blob/master/macros/DocStatus.ejs#L44 ? For the same reason I've been thinking that we can't remove the {{Index}} macro: https://github.com/mdn/sprints/issues/2524#issuecomment-593704900.

I've taken notes on the pages that still need handling. There's some new stuff here, but there's a little bit of recap too. I've tried to highlight new proposals that I'm making.
5. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Differential_inheritance_in_JavaScript
Proposal: Delete this page.
I can't figure out where this inherit() method comes from or I would've suggested moving to the method page's examples. But the sample code doesn't run anyway, so I say dump the page outright.
8. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Index
Discussed above. Seems like we're stuck with this one, for now. No action.
84. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat/DateTimeFormat_Options
Discussed above.
Proposal: fold this content into the parent DateTimeFormat page.
97. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/defineProperty/Additional_examples
Proposal: fold into the examples section of defineProperty.
102. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Reflect/Comparing_Reflect_and_Object_methods
I've tagged this as a guide page.
Proposal: correct me if I'm wrong. 😄
104. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer/Planned_changes
I guess this is a guide page, but if we ignore it long enough, it'll become historical and irrelevant. 🙈 Open to ideas on this one.
118. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/null
121. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/undefined
I'm tagging these as language features, since these hew closely to the recipes already.
Proposal: correct me if I'm wrong. 😄
161. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions
And it's children. Discussed above. We're waiting to hear from the PAB before we can act on these.
169. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript
And it's children. Discussed above. I think we need @chrisdavidmills for consensus on archiving or deleting.
182. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/The_performance_hazards_of__[[Prototype]]_mutation
This is a draft page, and one that hasn't been edited in nearly a year. I'd say that's abandoned, really. But I'm wondering if we ought to detect draft pages in the linter and demote all messages about them to warnings.
Proposal: Ignore or delete.

One thing to consider is how far we want to fix the content for its own sake, and how far we just want to make it scrapable, and worry about fixing it afterwards. For example, in some of these cases (like the "New in JS") the simplest thing is just tag them as guide pages. That avoids having conversations about "is this content really deletable". Treating pages as guide pages only becomes impossible when that have special custom content (like interactive examples) that guide pages don't support.
I'm not exactly saying we should do the minimum needed to make the content scrapable, but I am worried that once you start down the road of "fix the content on the way", then there's so much extra work in there, and I'm not sure where you stop.

https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/null
https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/undefined

I'm tagging these as language features, since these hew closely to the recipes already.
Proposal: correct me if I'm wrong. 😄

That sounds plausible to me. From what I can tell from the spec, they are the only values of the Null and Undefined types. So they're not "global objects". Should we also then move them out of "Global_Objects"? For things like the sidebar, we are implicitly assuming that all the things in /Global_Objects are actually "javascript-class" pages.

I'm wondering if we ought to detect draft pages in the linter and demote all messages about them to warnings.

I'm not sure about this. For one thing we are also planning to remove {{Draft}}. For another thing though: draft pages that are unscrapable still have to be dealt with, either by deleting them or fixing them.

I'm not sure about this. For one thing we are also planning to remove {{Draft}}. For another thing though: draft pages that are unscrapable still have to be dealt with, either by deleting them or fixing them.

One thing I proposed as part of my localization plan (the part about reducing the amount of content) was simply scrapping anything in draft that had bene in draft for any significant length of time, unless it really looks like content is valuable, in which case we should sort it out (maybe file a sprint P1 bug for it?)

One thing to consider is how far we want to fix the content for its own sake, and how far we just want to make it scrapable, and worry about fixing it afterwards.

This is a good point, but I'm still supportive of deletions, at least. It's less content to scrape and odds are good that it improves the corpus as a whole. I agree that fixes like combining pages is not essential to the overall scraping effort.
Items like 97. https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/defineProperty/Additional_examples are complicated, though. If they were part of a non-guide page, then we could scrape them as examples.

I thought DocStatus used the index page: https://github.com/mdn/kumascript/blob/master/macros/DocStatus.ejs#L44 ? For the same reason I've been thinking that we can't remove the {{Index}} macro: #2524 (comment).

I forgot about this. Thanks. Well, I think we could remove it from doc status and from the sidebar and then delete it. I think doc status pages shouldn't make it to github anyway.

https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Differential_inheritance_in_JavaScript Proposal: Delete this page.

Deleted.

https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat/DateTimeFormat_Options Proposal: fold this content into the parent DateTimeFormat page.

Done. Redirected to constructor page which documents this.

https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/defineProperty/Additional_examples Proposal: fold into the examples section of defineProperty.

Deleted. These examples were seriously old and the binary flag implementation of the method is like these little libraries that shouldn't be hosted on MDN at all.

https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer/Planned_changes I guess this is a guide page, but if we ignore it long enough, it'll become historical and irrelevant. see_no_evil Open to ideas on this one.

Yeah, Guide page now. This will be old in a year and then we can archive it.

https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/The_performance_hazards_of__[[Prototype]]_mutation This is a draft page, and one that hasn't been edited in nearly a year. I'd say that's abandoned, really. But I'm wondering if we ought to detect draft pages in the linter and demote all messages about them to warnings. Proposal: Ignore or delete.

Marked as Guide page for now. I searched for this and it seems to be relevant on stackoverflow and other sites, so we should finish this page one day.

null / undefined
Should we also then move them out of "Global_Objects"? For things like the sidebar, we are implicitly assuming that all the things in /Global_Objects are actually "javascript-class" pages.

Yeah, probably. I think this needs some sorting, but I assume we should split this out of this issue. Too much work to get into that now.

I think what is left here (or to be done as follow-ups) is:

remove index from the sidebar and doc status, then delete index page
remove "new in js" from sidebar, then move the doc tree to the archive
Get a word from Microsoft about their pages, then decide what to do with these.

Other follow-ups: Some pages like null and undefined should probably be moved around (also the Intl namespace, we have an issue for this). But I assume that work is out of scope for the moment, it will come back when we fix pages to comply with their recipes. Does that make sense?

@Elchi3 Thank you! I think opening follow up issues for these tasks and resolving this user story is the way to go. I'm not exactly quite sure how to write them or organize them though. Are they user stories of their own? What's the categorization of minor tasks like this?

Are they user stories of their own? What's the categorization of minor tasks like this?

Not sure. I just filed https://github.com/mdn/kumascript/pull/1340 to update the sidebar, after that the page updates should be really quick.
For the MS docs, we are dependent on outside teams, so we should file a separate issue I think, and not make it block this one.

Are they user stories of their own? What's the categorization of minor tasks like this?

I just filed https://github.com/mdn/kumascript/pull/1340 to update the sidebar.
I would suggest we file another story for the MS docs. If we wanted to, we could just tag those docs, for the sake of completing this story. I mean, it's fairly obvious what https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Microsoft_Extensions/at-if should be tagged as. It'll fail the linter, of course, but that's separate to this story.
I think "remove index from... doc status" is tricky. DocStatus is very dependent on Index, so much so that removing Index essentially means retiring DocStatus for the JS pages.

I think doc status pages shouldn't make it to github anyway.

I agree with this, but I thought doc status was still an important tool for localizers, while we are in Kuma.

If we wanted to, we could just tag those docs, for the sake of completing this story. I mean, it's fairly obvious

This is a good point. I've gone ahead and done this. That leaves only Index and the "New in JS" pages untagged. I supposed the "New" pages could also be tagged as guides, but it seems like the path to archiving them is pretty straight forward.

Awesome, I think we might get this done in time then. I agree on the MS docs tagging. It would be nice to hear if we need to further worry about these or not, though. Let's hope we'll get an answer.
Thanks for the sidebar PR, I have a question on that one, but good to go. If this is deployed, I will move the "New in JS" pages to the archive.
I'm tagging the Index page as "Guide", because Will is probably right, that it needs to stay for the moment.

Attempt to remove index from doc status https://github.com/mdn/kumascript/pull/1341

The JsSidebar updates from https://github.com/mdn/kumascript/pull/1340 are merged, deployed, and Ryan has rendered the pages: https://github.com/mdn/kuma/issues/6677
The changes to DocStatus are merged and deployed: https://wiki.developer.mozilla.org/en-US/docs/MDN/Doc_status/JavaScript
So I think we can archive "New in..." and delete the Index page, and then close this?

So I think we can archive "New in..." and delete the Index page, and then close this?

This is correct, though it'd probably be a good idea to open an issue for deciding on what to do with the Microsoft Extensions pages (though I'm not exactly sure what the issue should say — it's hard to formulate as a user story). That's not a blocker to completing this user story, but it seems like a good idea to track that work somewhere.

Also, I would archive the "New in…" pages, but I don't know how to do that. A pointer to instructions for that would be appreciated (assuming it's less work to tell me how to do it than to just do it).

what to do with the Microsoft Extensions pages

As an FYI - I asked the PAB crowd what they think about removing the MS-specific stuff, and they generally said it sounded reasonable, although we should probably look at the kind of usage figures the pages have, and see if anyone is going to miss them.
Funnily enough, we got no response at all from the MS reps.
I had a look at the usage figures on GA, and a few of the pages (like ActiveXObject) have a few thousand views per month. But most have very little. I guess the problem here is that it'd be a lot of work to get them updated to start passing linting against the page recipes, for very little gain.
What I think we should do is treat them in the same way as Mozilla/  and Archive/ pages - don't bother to fix them up or aim to get them into structured data, just dump them in the archive so they still exist if someone needs them.

So I think we can archive "New in..." and delete the Index page, and then close this?

I moved the "new in"  pages and I deleted the index page.

What I think we should do is treat them in the same way as Mozilla/ and Archive/ pages - don't bother to fix them up or aim to get them into structured data, just dump them in the archive so they still exist if someone needs them.

I agree wit this and would go forward with moving them to archive if that has consensus with Will and Daniel.

@chrisdavidmills thank you for asking the PAB!
@Elchi3 Moving to the archive works for me. 👍 And thanks for moving the "New in…" pages.

I just ran the linter and got:
Summary
Macro: jsxref                                                                 7393 warnings  jsxref
Macro: JSRef                                                                  677 warnings   jsref
Macro: JsSidebar                                                              233 warnings   jssidebar
Macro: optional_inline                                                        200 warnings   optional_inline
Macro: Glossary                                                               151 warnings   glossary
Missing from javascript-method: prose.description                             143 errors     javascript-method/prose.description
Linting data.info_box ingredient is unimplemented                             110 warnings   javascript-property/data.info_box
Missing from javascript-error: prose.short_description                        73 errors      javascript-error/prose.short_description
Missing from javascript-constructor: prose.description                        63 errors      javascript-constructor/prose.description
Macro: ReadOnlyInline                                                         61 warnings    readonlyinline
Missing from javascript-method: data.specifications                           50 errors      javascript-method/data.specifications
Macro: js_property_attributes                                                 49 warnings    js_property_attributes
Missing from javascript-method: data.examples                                 49 errors      javascript-method/data.examples
Macro: bug                                                                    43 warnings    bug
Macro: Non-standard_Header                                                    43 warnings    non-standard_header
Linting data.class_constructor ingredient is unimplemented                    35 warnings    javascript-class/data.class_constructor
Macro: PreviousNext                                                           32 warnings    previousnext
Expected SpecName macro for javascript-method: data.specifications            28 errors      javascript-method/data.specifications/expected-macro
Macro: Obsolete_Header                                                        26 warnings    obsolete_header
Missing from javascript-language-feature: data.examples                       24 errors      javascript-language-feature/data.examples
Missing from javascript-property: data.specifications                         24 errors      javascript-property/data.specifications
Macro: deprecated_header                                                      23 warnings    deprecated_header
Missing from javascript-method: data.browser_compatibility                    23 errors      javascript-method/data.browser_compatibility
Missing from javascript-property: prose.description                           22 errors      javascript-property/prose.description
Expected h2#Specifications                                                    22 errors      javascript-method/data.specifications/expected-heading
Expected h2#Browser_compatibility                                             22 errors      javascript-method/data.browser_compatibility/expected-heading
Missing from javascript-constructor: prose.syntax                             20 errors      javascript-constructor/prose.syntax
Missing from javascript-language-feature: prose.description                   19 errors      javascript-language-feature/prose.description
Missing from javascript-constructor: data.examples                            19 errors      javascript-constructor/data.examples
Expected SpecName macro for javascript-property: data.specifications          17 errors      javascript-property/data.specifications/expected-macro
Missing from javascript-property: data.examples                               17 errors      javascript-property/data.examples
Missing from javascript-language-feature: data.specifications                 14 errors      javascript-language-feature/data.specifications
Missing from javascript-class: data.examples                                  11 errors      javascript-class/data.examples
Macro: EmbedTest262ReportResultsTable                                         10 warnings    embedtest262reportresultstable
Missing from javascript-error: prose.message                                  9 errors       javascript-error/prose.message
Missing from javascript-error: prose.error_type                               9 errors       javascript-error/prose.error_type
Missing from javascript-error: prose.what_went_wrong                          9 errors       javascript-error/prose.what_went_wrong
Missing from javascript-method: prose.see_also                                9 errors       javascript-method/prose.see_also
Macro: DOMxRef                                                                8 warnings     domxref
Missing from javascript-language-feature: prose.syntax                        8 errors       javascript-language-feature/prose.syntax
Missing from javascript-property: prose.see_also                              8 errors       javascript-property/prose.see_also
Linting prose.overview ingredient is unimplemented                            7 warnings     landing-page/prose.overview
Linting data.link_lists ingredient is unimplemented                           7 warnings     landing-page/data.link_lists
Expected SpecName macro for javascript-language-feature: data.specifications  7 errors       javascript-language-feature/data.specifications/expected-macro
Expected h2#Specifications                                                    7 errors       javascript-language-feature/data.specifications/expected-heading
Missing from javascript-class: data.specifications                            7 errors       javascript-class/data.specifications
Expected h2#Specifications                                                    7 errors       javascript-property/data.specifications/expected-heading
Missing from javascript-namespace: data.examples                              6 errors       javascript-namespace/data.examples
Expected h2#Browser_compatibility                                             6 errors       javascript-property/data.browser_compatibility/expected-heading
Missing from javascript-property: data.browser_compatibility                  6 errors       javascript-property/data.browser_compatibility
Missing from javascript-language-feature: data.browser_compatibility          5 errors       javascript-language-feature/data.browser_compatibility
Expected h2#Browser_compatibility                                             4 errors       javascript-language-feature/data.browser_compatibility/expected-heading
Macro: Draft                                                                  4 warnings     draft
Expected SpecName macro for javascript-class: data.specifications             4 errors       javascript-class/data.specifications/expected-macro
Missing from javascript-class: data.browser_compatibility                     4 errors       javascript-class/data.browser_compatibility
Macro: EmbedLiveSample                                                        3 warnings     embedlivesample
Missing from javascript-language-feature: prose.see_also                      3 errors       javascript-language-feature/prose.see_also
Macro: SeeCompatTable                                                         3 warnings     seecompattable
Expected h2#Specifications                                                    3 errors       javascript-class/data.specifications/expected-heading
Expected h2#Browser_compatibility                                             3 errors       javascript-class/data.browser_compatibility/expected-heading
Macro: Previous                                                               2 warnings     previous
Missing from javascript-class: prose.see_also                                 2 errors       javascript-class/prose.see_also
Expected SpecName macro for javascript-constructor: data.specifications       2 errors       javascript-constructor/data.specifications/expected-macro
Missing from javascript-constructor: data.specifications                      2 errors       javascript-constructor/data.specifications
Macro: Next                                                                   1 warning      next
Macro: ListSubPages                                                           1 warning      listsubpages
Missing from javascript-constructor: prose.see_also                           1 error        javascript-constructor/prose.see_also
Missing from javascript-error: data.examples                                  1 error        javascript-error/data.examples
Missing from javascript-method: prose.short_description                       1 error        javascript-method/prose.short_description
Missing from javascript-constructor: prose.short_description                  1 error        javascript-constructor/prose.short_description
Expected h2#Specifications                                                    1 error        javascript-namespace/data.specifications/expected-heading
Missing from javascript-namespace: data.specifications                        1 error        javascript-namespace/data.specifications
Expected h2#Browser_compatibility                                             1 error        javascript-namespace/data.browser_compatibility/expected-heading
Missing from javascript-namespace: data.browser_compatibility                 1 error        javascript-namespace/data.browser_compatibility
Missing from javascript-method: prose.syntax                                  1 error        javascript-method/prose.syntax
Missing from javascript-property: prose.short_description                     1 error        javascript-property/prose.short_description

-> 0 recipe errors, so I think we can close this issue.

What I think we should do is treat them in the same way as Mozilla/ and Archive/ pages - don't bother to fix them up or aim to get them into structured data, just dump them in the archive so they still exist if someone needs them.

I agree with this and would go forward with moving them to archive if that has consensus with Will and Daniel.

I'm fine with this, but I don't really have any particular authority to decide what to do with these pages. An alternative, if we want to keep them in /JavaScript, is to tag them as guide pages, which I think would work OK (they don't contain any exciting macros we'd need to worry about, although they do use things like <dl> which would be a little, um. modified in the transition).

An alternative, if we want to keep them in /JavaScript, is to tag them as guide pages, which I think would work OK

Wouldn't that be a bit of a hack though? It seems wrong to start hacking stumptown this early on in the process ;-) I like the idea of doing it properly, or not at all. If we were to put them in the archive, they would still be available, and redirects would make sure that any links in place won't break?

Wouldn't that be a bit of a hack though? It seems wrong to start hacking stumptown this early on in the process

We talked a little about this risk when we were in London. It's pretty unrealistic to expect that we'd be able to clean up and structure everything coming into Stumptown. The guide pages are the shallowest of shallow structure, so I don't think this is a hack, so much as admission that we're going to have to drag some legacy content along or rely on the community to help us do some cleanup in Stumptown.

I don't think this is a hack, so much as admission that we're going to have to drag some legacy content along or rely on the community to help us do some cleanup in Stumptown.

OK, WFM. Thanks for the explanation!


conflicting actions from multiple deploy_maven usages in the same package

Similar to the issue in https://github.com/graknlabs/bazel-distribution/issues/215, if you define two java libraries, two assemble_maven targets, and two deploy_maven targets in the same package (same BUILD file), then the build fails with:
ERROR: file 'deploy.py' is generated by these conflicting actions:
Label: //:a_deploy_maven, //:b_deploy_maven
RuleClass: deploy_maven rule
Configuration: c459523ff98608ba9e7e7cae41b6408e94f5281c4537939d1c1bcfebf2509c7e
Mnemonic: TemplateExpand
Action key: b67a129538095ef2529e96303d414bb80c61d6cf0f7e3f201d24bd2a150cb666, 62daaeb89d652cfbfa69c1322a9de03ff015aff48e0a5cdd381a8e0ca05f8aa7
Progress message: Expanding template deploy.py
PrimaryInput: File:[/private/var/tmp/_bazel_dsilva/c65e62889b3448fbc3eab4f5ca51b208[source]]external/graknlabs_bazel_distribution/maven/templates/deploy.py
PrimaryOutput: File:[[<execution_root>]bazel-out/darwin-fastbuild/bin]deploy.py
Owner information: //:a_deploy_maven BuildConfigurationValue.Key[c459523ff98608ba9e7e7cae41b6408e94f5281c4537939d1c1bcfebf2509c7e] false, //:b_deploy_maven BuildConfigurationValue.Key[c459523ff98608ba9e7e7cae41b6408e94f5281c4537939d1c1bcfebf2509c7e] false
MandatoryInputs: are equal
Outputs: are equal
ERROR: com.google.devtools.build.lib.actions.MutableActionGraph$ActionConflictException: for deploy.py, previous action: action 'Expanding template deploy.py', attempted action: action 'Expanding template deploy.py'

Is that because deploy.py in https://github.com/graknlabs/bazel-distribution/blob/2618fa815cc1d2843db2d52c2df723b9faba0826/maven/templates/rules.bzl#L431 isn't prefixed with ctx.attr.name?

Fixed in:

#336


Add notationPatterns to kos.yaml

I deleted some notationPatterns from before, because they didn't work right. Still, someone should better check again.

In commit 2769388cbf7a192edd79e156334d6e4186d30556 I was able to fix a few sntactic errors.


Bug report: paragon-extfs

Davids-MacBook-Pro:Downloads dave$ brew cask install paragon-extfs
==> Downloading http://dl.paragon-software.com/demo/extmac10_trial.dmg
######################################################################## 100.0%
==> No checksum defined for Cask paragon-extfs, skipping verification
==> Running installer for paragon-extfs; your password may be necessary.
==> Package installers may write to any location; options such as --appdir are i
Error: pkg source file not found: '/usr/local/Caskroom/paragon-extfs/latest/FSInstaller.app/Contents/Resources/Paragon ExtFS for Mac OS X.pkg'
Error: nothing to install

From the issue template that shows when opening a new issue:

Before opening your issue you must check our instructions for reporting bugs (…) [it] has several links to help diagnose and fix common issues.
(…)
if it is apparent you ignored the instructions for reporting issues, we may close the issue without review.

That seems to be the case, which is why I closed this issue. We worked hard  on those guides to keep things running smoothly, so I ask that you go back and follow them. It is OK to open a new issue for that.
If I was wrong in closing this issue, please do reply stating why! Closing an issue does not mean the conversation is over.
I understand sometimes we’re tired and don’t want to sift through a guide to make what we feel is a simple bug report. But when each user ignores the guides to save a few minutes, maintainers lose hours and get fatigued. I ask you take that into consideration.
Thank you for understanding.

It's literally two lines of error messages. Didn't think I could simplify it much more.
Anyway, thanks for opening the new ticket.

It's literally two lines of error messages.

That you could’ve fixed yourself if you followed the guide, since it teaches you how to.


volpiano doesn't render when printing

I tried printing http://<IP_ADDRESS>/chants/?source=699578, and found this bit of volpiano:

and it's not just this page: http://<IP_ADDRESS>/chant/702097:


Moved jsdoc to standard dependency, otherwise npm complains about unm…

…et peer dependency (despite jsdoc being installed)

unmet peer dependency means you haven't installed a dependency to your project that something else believes is required.
peerDependency means: "Don't install this, but I do require it. Ensure that any project using me also depends on this". If you have jsdoc installed to a project, but are seeing this error still then you are using a jsdoc version that is incompatible with the one listed in the package.json here.
peerDependency is a lot less necessary now that npm is flattening dep folders, but the reason I did it this way is because we are a plugin to jsdoc not a consumer of it.

I installed jsdoc specifically to satisfy this module, tried 3.4.0 and
3.4.3, didn't satisfy. I then installed my fork, installs and functions
fine.
On Fri, Jun 9, 2017, 8:47 PM Chad Engler<EMAIL_ADDRESS>wrote:

unmet peer dependency means you haven't installed a dependency to your
project that something else believes is required.
peerDependency means: "Don't install this, but I do require it. Ensure
that any project using me also depends on this". If you have jsdoc
installed to a project, but are seeing this error still then you are using
a jsdoc version that is incompatible with the one listed in the
package.json here.
peerDependency is a lot less necessary now that npm is flattening dep
folders, but the reason I did it this way is because we are a plugin to
jsdoc not a consumer of it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/englercj/tsd-jsdoc/pull/27#issuecomment-307530821,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEvJ58MgcC7pVQnrqol7sNzCNIAduq3ks5sCeeNgaJpZM4N1j-W
.

--
Jon Langevin
<EMAIL_ADDRESS>910-241-0433

I'd love to see a project that depends on both this module and jsdoc, but still produces this error. All of my projects work as expected using peerDependency. Can you provide a repo that reproduces, along with your node/npm version?

Closing this since it is stale.


Sphinx autodoc broken

Our docs do not currently include our docstrings.

Good catch - this is a problem. Which is more likely: a) that there's a bug with Sphinx's autodoc, or b) that our config is somehow wrong? I assume b but want to make sure.

99% sure it's B

some debugging notes from looking at this a bit with @galbramc

autodoc currently builds fine on my mac
autodoc did not build fine for @galbramc on Ubuntu
@galbramc was able to fix this on his machine by editing conf.py in 8da0392d9e09a81a45c6d7527b844832b41b84c9

Glossary is still not building on RTD; we seem to be getting the import errors described in http://read-the-docs.readthedocs.io/en/latest/faq.html#my-project-isn-t-building-with-autodoc
@bqpd, that FAQ mentions changing settings on admin page; I think you're our admin?

I'm not sure we can install into a virtualenv, though, because of numpy...

But hey! It worked! Great success.

Looks like it doesn't install the packages requirements, thankfully.

Wait, what happened? It just worked!

I see an extra command in the last build, namely "python setup.py install --force"
http://readthedocs.org/projects/gpkit/builds/4377446/
That seems to have done the trick. @bqpd, did you change some settings in RTD?

Yup.


Could Not able To load "IF-MIB" using loadModules

Hi
I am having problem to load "IF-MIB" using loadModules.
Using PYSNMP-4.3.8.
after I call mibBuilder.loadModules('IF-MIB') its just hangs there.
Debug log attached.
Reproducible: Yes.
snmp_debug_log.txt
>>> from pysnmp.smi import builder, view, compiler, rfc1902, error
>>> custom_mib_paths = "/usr/share/snmp/mibs/"
>>> mibBuilder = builder.MibBuilder()
>>> compiler.addMibCompiler(mibBuilder, sources=custom_mib_paths)
>>> from pysnmp import debug
>>> debug.setLogger(debug.Debug('all'))
2017-07-05 09:06:01,505 pysnmp: running pysnmp version 4.3.8
2017-07-05 09:06:01,506 pysnmp: debug category 'all' enabled
>>> mibViewController = view.MibViewController(mibBuilder)
>>> mibBuilder.loadModules('IF-MIB')

Please close this case its because the dependency MIB IANAifType-MIB was missing. My bad.

I guess you should have enable the pysmi debugger to see why MIB load hangs.
Anyway, good to know you resolved this!


ability to customize data-registration rules/logic

Currently all transactions which wish to register arbitrary data have to prefix this data with the Prefix NonSia, this prefix should probably be customizable per blockchain implementation.
The transaction fee is currently also hardcoded, while it should probably also be customizable for each blockchain implementation, even though it should have sane defaults.

The transaction fee for the tfchain is for example currently desired to be set at 0.1 TFT, but those requirements can change.

An open question is also how complex we should allow those transaction fees (related to registration data should be). Should a transaction which wishes to register arbitrary data cost more? If so, should its cost increase together with the size of that arbitrary data.

While we are working on this, we should probably also think about custom transaction rules in general. In general, I feel it might be best to allow people to supply a custom function with a predefined signature (something like func (Transaction) Currency), taking a transaction as input and calculating a required minimum transaction fee which is then returned. Then everyone could make these as complex as they want. The same could apply to other validation rules

Does sounds like it would give a lot of flexibility indeed. Could you elaborate on what other validation rules you had in mind? So we're all on the same page.

I was referring to this mainly with the idea of the authorized addresses in mind. But coming to think of it, that might be more difficult because you need to know if an address is authorized, which is beyond the context of just a transaction. Though we could also pass a reference to the consensus set as well as this would then make it easy to get a reference to the current height and or other things to make it easy to create soft forks. Disregarding that it feels useful even if its just in case that someone want to create some crazy logic e.g. I want every transaction to create an even number of outputs I guess

Could also do this to establish something like a minimum transaction amount: You must s(p)end at leat 0.01C fore example

Yeah it's true, but again, as Rivine is supposed to be a protocol to implement a blockchain, we should allow flexibility where it is possible. These rules, while having sane defaults (e.g. a minimum transaction amount), should be able to change, when required.

As part of #165, the NonSia prefix has been removed and is no longer needed.
The only thing left to do for this issue would be provide the option to customize the transaction fees based on stuff like data size. But that is not important for now, so moving it to a later milestone.


EIPs with required options seems not to indicate this

The ref option is required on process eip
https://github.com/apache/camel/blob/main/core/camel-core-model/src/generated/resources/org/apache/camel/model/process.json#L15
However when I remove the value (making it blank) then karavan does not indicate its a required option.
Maybe it should highligh this in the panel. And also show that in the tooltip.

Indicator and tooltip added.
verification will be implemented later


ReadLightNovel say's Chapter not Available for The Beginning After the End

Source information
ReadLightNovel
Steps to reproduce

Open LNReader
Open ReadLightNovel
Open "The Beginning After the End"
Open Latest Chapter
Says Chapter not available. Report if it's available in webview.

Expected behavior
Should open normally since Webview works and the chapters are updated.
Actual behavior
Says Chapter not available. Report if it's available in webview.
LNReader version
1.1.13
Android version
Android 12; Samsung One UI 4.1
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.1.12.
[X] I have updated all installed extensions.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Closing since all the chapters are working fine for me.
Reopen if the issue still persists.


Add labeled Mockup in Part 2

Fix issue #27

Request to change: The structure is lacking a VBox inside the ScrollPane.

Request to change: The structure is lacking a VBox inside the ScrollPane.

@laney0808 can you elaborate?

Request to change: The structure is lacking a VBox inside the ScrollPane.

@laney0808 can you elaborate?

Hi Prof! I added this comment because I realized the new graph is lacking a label on the VBox. I'll add it in the next commit.

I like how this provides a clear idea of what the hierarchy graph will look like. Is Input one of the nodes too, or do you think it can be removed to avoid confusion? Perhaps something like this? I believe that's the text in the original UI. Sure! let's change it to the new version to avoid confusion.

Requested change completed.

LGTM!


Importing GAMS files to GlobalModel.

WIP... Wil merge master into this once I get all the tests to work with the JuMP.Model refactor.

Can't believe gams files can now be imported into GlobalModels. Not guaranteed to be able to solve problems yet, but will merge and PR the bug fixes as they arise. Otherwise src and sagemark tests are passing, which bodes well.


Closes #266: Add support of (un)registering global dynamic modules

Closes #266

@danielroe I tried to build it locally but it was failed. I think nuxt-typed-vuex needs vuex as dev dependency as well in order to make this work.


Please support a server model that not require odata service, just an URL and customs params

Hello, i saw on your online docs that OpenUI5 support 4 types of models
OpenUI5 provides the following predefined models:

The JSON model can be used to bind controls to JavaScript object data, which is usually serialized in the JSON format. The JSON model is a client-side model and, therefore, intended for small datasets, which are completely available on the client. The JSON model supports two-way (default), one-way and one-time binding modes.
The XML model is a client-side model intended for small datasets, which are completely available on the client. The XMLModel does not contain mechanisms for server-based paging or loading of deltas. The XML model supports two-way (default), one-way and one-time binding modes.
The Resource model is designed to handle data in resource bundles, mainly to provide texts in different languages. The Resource model only supports one-time binding mode because it deals with static texts only.
The OData model enables binding of controls to data from OData services. The OData model is a server-side model: the dataset is only available on the server and the client only knows the currently visible rows and fields. This also means that sorting and filtering on the client is not possible. For this, the client has to send a request to the server. The OData model currently supports OData version 2.0. The OData model supports two-way (default), one-way and one-time binding modes. However, two-way binding is currently only supportes for properties, and not for aggregations.

Please can you support a new server model that does not require an OData service on the server?
For example, KendoUI data source you define
dataSource: {
type: "json",
transport: {
read: {
url: "URL of server service",
type: "POST",
dataType: "json",
data: additionalDataFunctionToServerFiltering
}
}
This way we can implement the server side part with minimal requirements, for already implemented server part, it is easier to provide a custom model than migrate all server implementation to support OData. Maybe the implementation could be like:
var oModel = sap.ui.model.ServerModel("url-to-server", "POST");
oModel could have events so we can hook before a request is sent to the server to add custom data for filtering the results.
Syncfusion components for example, have an URL adaptor that can be used to support this kind of scenarios, and also support OData services in their Grid.
Can you provide a new model implementation that does not require an OData service on the server?
Thanks.

It already exists :)
How about
var oModel = new sap.ui.model.json.JSONModel("http://www.yourdomain.com/rest/yourservice");
From the API doc at https://sapui5.hana.ondemand.com/#docs/api/symbols/sap.ui.model.json.JSONModel.html, the constructor accepts "either the URL where to load the JSON from or a JS object"

Valid requirement. Our JSONModel is very limited and there is a lot of custom code required to use it with a Restful-API (no OData).
@qualiture this works for read only (one time). But there's no way to post data back or do pagination, etc.

qualiture: JSONModel is a client model, it reads the data once, what about server pagination and server filtering? Do you return a million of records in one query? Only ODataModel support that kind of scenario, i think that a custom server model could made OpenUI5 a better framework, the API details is up to SAP developers, as long as we as developers can hook on the model without pain.

@eusebio-garcia, @matz3 You are totally right, I misinterpreted your requirement...
Actually, I have built a basic "RESTModel" a while ago, which is basically an extension to JSONModel with additional create, update and delete functionality. I will try and dig it up tonight

@qualiture I'm pretty new on OpenUI5, i feel that i don't have the skills yet to make a complex contribution like the implementation of a rest model, i would really appreciate if you can make a contribution like this, no only me, the entire community

@eusebio-garcia See https://github.com/qualiture/ui5-restmodel
I haven't used it in a long while, but hopefully the readme is explanatory enough. Basically you have a create, update and delete function, and by default it loads all the (updated) data from the specified service url.
Beware, it is really rudimentary, so no paging, lazy loading, filtering etc (although it's fairly easy to implement, the main logic sits in your serverside RESTfull service anyway :smile:
It's just basic CRUD, but it can be "easily" extended to accommodate those requirements -- I just haven't had the need for it
Hope it helps a bit, and hopefully you can use it for your own good (and I welcome you to make updates on it where others can benefit from as well)

@qualiture Thanks, i will give it a try and see how can i hook to implement paging and all that stuff...
@matz3 I see that the issue is tagged as an enhancement, how can i know when this requirement can be implemented? This same issue is changed or do i need to see it in other place?

@eusebio-garcia I just marked it as enhancement rather than e.g. "bug".
This doesn't mean that we will implement this in the near future (or not).
It still needs to be clarified if this should be something part of the framework.
@qualiture thanks for sharing!

@matz3 Thanks for your answer, i hope this requirement get implemented, OData is very powerful but also very complex and exists a lot of apps that does not have an OData service, just REST and even classic web services with XML.
@matz3 or @qualiture Exists a good tutorial on which i can see how the table control interact with the model, so it can help me to implement server paging, filtering and lazy loading? I will implement that and later make a contribution to the community, but i need a little of help on this. In some point the table must ask the model about the data, maybe that method is the one that i need to implement in a new model, how the table call that method is important, i think for example, in pagination, i need that the table send the current page or number of rows to skip....

Interesting suggestion... this topic has come up many times, so it seems to be worth looking into.
At the same time it always makes me wonder: how will this RESTModel look in the end? Will it really be so much simpler than OData?
When we are talking about paging, server-side sorting etc., we need to define a protocol, something that both, server and client, understand. We need to define how we tell the server that we now need the "page" with items 40-60.
REST is not a protocol, it's just a principle for architecture. REST says something like "use PUT to edit data", but it doesn't say how we specify we want to edit the data for player 15 in our current collection:

PUT http://xy.de/service/players/15
PUT http://xy.de/service/players(15)
PUT http://xy.de/service/players/{15}
PUT http://xy.de/service/players/Hugo  (because player "Hugo" has number 15)
PUT http://xy.de/service/players/number/15
PUT http://xy.de/service/players?id=15
POST http://xy.de/service/players/15
I'm sure that each of these ways to address an item is implemented in one or the other REST API. But we need to define the one used by our model.

And as soon as we are defining a protocol, we are in the OData ballpark. There are much more complex questions than how to address which data element we are addressing. All the same difficulties and requirements will come up sooner or later and make the protocol more complete - and more complex. And we need a server implementation that speaks the same protocol.
Are there popular simple alternatives to OData? We wouldn't want to re-invent one...
I'm totally in favor of having such a model and supporting an alternative to OData, I just wonder how it can be kept simple. I currently feel "restricting its functionality" is the only way.
Regards
Andreas

@akudev Actually a Rest model is very simple, the protocol is defined by a developer, look at Telerik KendoUI or Syncfusion components as an example, almost all good frameworks and widget toolkits support the three common scenarios, local, Rest and OData, i wonder why OpenUI only support 2....
Here is an example of how it is done with KendoUI, if you look at that sample you will see that they left developers make their own protocol (since it is their own rest service too), the only thing that you must define is that the list method will sent you pageIndex/pageSize  and the datasource need that the returning list will be an object with a Data parameter, if your service return other thing, you can add an adapter and return the data.....
dataSource: {
type: "json",
transport: {
read: {
url: "URL of LIST method",
type: "POST",
dataType: "json",
contentType: "application/json",
data: functionOfAdditionalDataToFiltering
},
create: {
url: "URL to create",
type: "POST",
dataType: "json"
},
update: {
url:"URL to update",
type: "POST",
dataType: "json"
},
destroy: {
url: "URL to delete",
type: "POST",
dataType: "json"
}
.........
It is very simple, maybe on OpenUI could be like this
var oModel = new JsonRestModel({
read:{},//definition of read, list, get or some other name
create:{},//definition of create
...... //rest of defined methods
});
and if some parameter is missing, for example the protocol, use conventions, for example POST to insert, PUT to update...... I know WHAT to do, but i don't know HOW......

@eusebio-garcia that fits to what I had in mind. The model just needs some basic API (read, write, update, delete) and could even have something like paging but leaves the protocol to the developer so e.g. you have to implement some callback which creates the URL for a paged request.
@akudev what do you think? I would label this as contribution welcome to get some more API proposals or even implementations. Then we may see if it works out or not.

Exactly, that is what i think, just implement a basic and common API and leave the details to developers, i also think that the model must leave a couple of doors opened in order to hook the implementation e.g before send request, after request, before binding, etc... you get the idea.....

@eusebio-garcia while I can not guarantee that this will make it into OpenUI5 please feel free to share some ideas or even code.
It might also be a possible candidate for a project here: https://github.com/UI5Community

Any sugestion on how to use the “growing” property of lists and tables with a jsonDataModel? I too have a requirement of building a sapui5 frontend that consumes an existing restful style backend (no odata)

@Megale Someone had the same question to which I suggested to make use of list's ScrollEnablement delegate: https://stackoverflow.com/a/47633857/5846045.

Hi @boghyon, thanks for the tip. I forgot to mention I was using SAPUI5 1.44.7. I didn'f find the namespace sap.m.library. Do you know if its under a different name?

@Megale Can you copy-paste your comment / question in the comment section of the answer? Not to pollute this issue thread

Hi,
Stumbled on this old thread as it was the top 3 results in Google search (Keywords used: "UI5 without OData"). I'm pretty new to UI5 as well, and am facing similar challenges as first mentioned by @eusebio-garcia . Has there been any updates since then?
Cheers,
Amos

There is an open source library https://github.com/mauriciolauffer/openui5-model-json-crud that might help you.
But for productive environments I would always recommend using OData.

Hi @eusebio-garcia ,
we discussed this long ongoing requirement multiple times in the respective teams.
Currently, the capacity is fully blocked by other requirements, so this enhancement will not be developed in the next months.
Also, there are already multiple community projects available covering this scenario:

https://github.com/mauriciolauffer/openui5-model-json-crud

https://github.com/clouddnagmbh/RestModel
https://blogs.sap.com/2020/06/23/restmodel-for-sap-ui5/

https://github.com/qualiture/ui5-restmodel

There might come such a generic RestModel but not in the medium run. Therefore, closing this issue.

@flovogt, the official and out-of-box support of the full-fledged RESTful API Model can contribute to wider use the framework, since the standard RESTful API is much more common and widespread than OData, thus OpenUI5 can easily replace an alternative frontend framework without any or with minimum changes on the backend.
Hopefully, the RESTful API Model support will land to UI5 in some later but still reasonable time.


xml.etree.ElementTree.ParseError: not well-formed (invalid token)

Hello,
I have this crash and do not what is wrong.. Can you help ?
Traceback (most recent call last):
  File "deleteoldlogs.py", line 87, in <module>
    checkDeletion(getExecutionDate(getExecutionsForAJob(jobid)))
  File "deleteoldlogs.py", line 56, in getExecutionDate
    root = ET.fromstring(executionsinfo_xml)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML
    parser.feed(text)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in feed
    self._raiseerror(v)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
    raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 3725, column 77

Hi Mathieu,
can you give me more information about this problem?
What version of rundeck are you running?
What is the name of the project? And the jobid?

Name of project Mobistep-Dev-App
job id:  49dbddc6-20f8-4b17-8238-c015555381b7
still current error with latest rundeck. I had it from beginning and could never pass through. Was hoping 2.6.9 would help

Hi @mathieuchateau,
I think your XML might contain some invalid characters.
Anyway, I applied this patch: http://stackoverflow.com/a/20204635/333348
You can find the new code here: https://github.com/danifr/rundeck-scripts/blob/dev/py_scripts/deleteoldlogs.py
Can you please test it and let me know if this change fixes your issue?
Thanks!

thanks @danifr
now it fails immediately after displaying project name:

project:        xxx-Dev-App
Traceback (most recent call last):
File "deleteoldlogs.py", line 86, in
jobids = getJobIDs(listJobsForProject(project))
File "deleteoldlogs.py", line 42, in getJobIDs
root = ET.fromstring(jobsinfo_xml, parser=PARSER)
File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML
parser.feed(text)
File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1640, in feed
self._parser.Parse(data, 0)
AttributeError: 'XMLParser' object has no attribute '_parser'

Ummh, sorry to hear that :/
I'll try to come up with a better (and properly tested) solution for this.

Hi again @mathieuchateau,
I'm trying to reproduce your problem but I am not able to (using the original code from master)
To test it, I created a new job, that uses non ascii characters:
<joblist>
  <job>
    <description>Some characters in the description too: á é í ó ú ç ñ</description>
    <executionEnabled>true</executionEnabled>
    <id>57a6eb5f-f85b-4abb-a88e-789c35d04969</id>
    <loglevel>INFO</loglevel>
    <name>¿Print date? ¡yes!</name>
    <scheduleEnabled>true</scheduleEnabled>
    <sequence keepgoing='false' strategy='node-first'>
      <command>
        <description>¡¡¡¡!!!!!</description>
        <exec>date</exec>
      </command>
      <command>
        <script><![CDATA[echo "áéíóú"]]></script>
        <scriptargs />
      </command>
    </sequence>
    <uuid>57a6eb5f-f85b-4abb-a88e-789c35d04969</uuid>
  </job>
</joblist>

But even with this job the script seems to be working perfectly:
[danifr@centos ~]$ python deleteoldlogs.py
project:	Test
	jobid:	57a6eb5f-f85b-4abb-a88e-789c35d04969
[danifr@centos ~]$

Can you export your job as xml/yaml and send it to me via email? gmail --> daferoes
Remove everything you consider sensitive, although try to not change it a lot so I can try to reproduce the issue.
Cheers,
Daniel.

Hello,
I am pretty sure I am not using any special character.
In the mean time, I used this project, with which is does work, even if quite slow (due to H2 and >500K execution more than the script itself):https://github.com/phwitservices/RundeckLogfileCleanup

I am getting below xml parsing error in rhel_7_6_x86_64 platform, but same xml parsing is success with rhel_7_2_x86_64 platform
root = ET.fromstring(xml_without_namespace)

File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML
parser.feed(text)
File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in feed
self._raiseerror(v)
File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 36, column 874
Error: xmls merging failure.
Can anyone pls help ?
Thanks in advance

Hi @RameshKumarRajender, are you using my deleteoldlogs.py? What XML are you trying to parse?

Thanks Daniel for the response.
No, I am not using deleteoldlogs.py.
This is proprietary xml, that i am using.
Interestingly, this xml works on rhel_7_2_x86_64 platform.
But getting above error on rhel_7_6_x86_64 platform.
On Mon, 3 Aug 2020 at 13:51, Daniel Fernández<EMAIL_ADDRESS>wrote:

Hi @RameshKumarRajender https://github.com/RameshKumarRajender, are you
using my deleteoldlogs.py? What XML are you trying to parse?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/danifr/rundeck-scripts/issues/5#issuecomment-667882618,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO2ZRKNFADW555WJEQKAUCTR6ZXRVANCNFSM4CBYW6NQ
.

--
Thanks & Regards,R.Ramesh KumarMitel,Bangalore.

Hmm I don't think this has something to do with my code then. This is just a script to delete old logs from rundeck.
You can try to check what are the package changes between rhel 7.2 and 7.6: python version you are using and these kind of things.

OK Thanks Daniel. WIll check and get back.
On Mon, 3 Aug 2020 at 17:06, Daniel Fernández<EMAIL_ADDRESS>wrote:

Hmm I don't think this has something to do with my code then. This is just
a script to delete old logs from rundeck.
You can try to check what are the package changes between rhel 7.2 and
7.6: python version you are using and these kind of things.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/danifr/rundeck-scripts/issues/5#issuecomment-667972989,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO2ZRKOQOFBQGRA26W225U3R62OLLANCNFSM4CBYW6NQ
.

--
Thanks & Regards,R.Ramesh KumarMitel,Bangalore.

I close this issue for now. Feel free to open a new one.


Section background colours

Experiment with different background colours for sections.

This would effectively remove the need for horizontal line breaks.

I like the horizontal line breaks. Instead, I changed the background colour of the footer to bg-accent.


Match way to ignore root

I'm using Match component to pass isCurrent to a child component.
    <Match path={`/${to}`}>
      {({ match }) => (
        <Link to={to}>
          <Item selected={Boolean(match)}>
            {children}
          </Item>
        </Link>
      )}
    </Match>

But the problem is I have some nested routes and I need to match them too. If I match /${to}/*, it going to be true for / root route too. Anyway to overcome this?

Hey @iamchathu I'd love to take a closer look. Mind providing a codesandbox so myself and others can better help out?


default header-img when page does not define one

When you forget to set page.header-img the rendered page is not readable (white header on white bg). Also, in most cases (at least for me) I do not create a special post-bg-img.
So I define a site.header-img that is used as default.
This PR:

_config with site.header-img
index without page.header-img (proof)
if statements in _layouts/(page|post).html

I solved it this way. In _config.yml I added the following so posts don't need a header-img.
defaults:
  -
    scope:
      path: ""
      type: "posts"
    values:
      header-img: "img/home-bg.jpg"

thanks!


[WIP] Define service as a package type

Proposed changes
This PR defines the service package as a part of the PackageType class
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[x] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Codecov Report

Merging #150 (02eee94) into main (c2e697b) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #150      +/-   ##
==========================================
- Coverage   94.90%   94.84%   -0.07%
==========================================
  Files         309      309
  Lines       24816    24820       +4
==========================================
- Hits        23552    23540      -12
- Misses       1264     1280      +16

Flag
Coverage Δ

unittests
94.84% <100.00%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

aea/configurations/constants.py
100.00% <100.00%> (ø)

aea/configurations/data_types.py
99.70% <100.00%> (+<0.01%)
:arrow_up:

aea/cli/utils/package_utils.py
88.62% <0.00%> (-3.68%)
:arrow_down:

aea/cli/run.py
85.50% <0.00%> (-3.63%)
:arrow_down:

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 c2e697b...02eee94. Read the comment docs.


add route, controller, client side javascript, and some handlebars fo…

…r basic homepage functionality

no conflicts! easy peasy!!


Child node missing in the test explorer

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.95.1 (user setup)
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100

As the screenshot shows, in test explorer, it's expected that the node MetaAnnotationTest should have child node. But actual it does not.
While in the editor and test results panel, the test myFastTest() is discovered.
During debug, it shows that myFastTest()is child of MetaAnnotationTest.

@connor4312 Do you have any idea what could be the reason that the child node is not displayed in the tree view? From my side this behavior happens in a random manner. So far I have no idea how to find the root cause of it.

Not off hand. Do you have a repro case you're able to share?


[Question] config functions

Hello. Thank you for the new version!
Q1: why in the new version are not parsed biomes like the old? As well as not all the configuration is available in the old version?
At the moment, the older version is more flexible than the new settings, unfortunately it is. When do you plan to return all of their features or an improved version?

Q2:
`biometypes {
            S:Included <
                FOREST
             >
            S:Excluded <
             >
        }`
FOREST = minecraft.FOREST? While the cause of the same name biomes? For example vanilla  biomes and biomes bop?
or EXBL and vanilla: minecraft.Birch Forest and extrabiomes.Birch Forest,
biome in which then will be generated?
And as the search goes only biome dictionary? Can I paint how it works on details, for that would have been easier in the future.

Actually, as I understand it, the new configuration is as flexible as the old, but a lot more tidy.
You can still select biomes both by biome dictionary group and by specific name. The only downside is that you have to know the specific name of biomes (you can use mods like NEI and No Id Conflicts to find the names).
The second question does not make sense. Some phrases lacks verbs and are really not understandable this way.

@Zarzuf I not completely fix what did Google translator.

As @Zarzuf has said, the new configuration should be as flexible as the old, with a lot less config.
Most of the config is done with forge biome dictionary tags, so FOREST is any biome that is tagged as a forest. A list of vanilla biomes and tags can be found here
I'm planning to set up a website for the mod to explain configs and such more in depth. I could also generate a file that contains the name of all the registered biomes.
The main reason behind the changes is that the previous configs were quite verbose, confusing and not extendable. I have some cool plans going forward, for example biome specific overrides for wood types. The new configs (trees per chunk & chance per tree) are also more light weight than before. Before when decorating a forest biome, there were probably somewhere between 1000 and 2000 tries to generate a tree per chunk. With the new system, I would guess there's 10-15 tries.

@vidaj FOREST this tags? Ok, thanks :)


GUAC-1053: Move manage sections into tabbed settings page

Beware that this change is made up mainly of converting the old manage pages into directives under a new settings module.


[JUnit 5] Add support for nested tests

Nested test docs: https://junit.org/junit5/docs/current/user-guide/#writing-tests-nested
Currently snapshot matching within nested test classes is not supported.
Example:
class Demo {
    @BeforeAll
    static void beforeAll() {
        SnapshotMatcher.start();
    }

    @AfterAll
    static void afterAll() {
        SnapshotMatcher.validateSnapshots();
    }

    @Test
    void one() {
        expect("one").toMatchSnapshot();       // succeeds
    }

    @Nested
    class NestedTest {
        @Test
        void two() {
            expect("two").toMatchSnapshot();         // fails
        }

        @Nested
        class DeeplyNestedTest {
            @Test
            void three() {
                expect("three").toMatchSnapshot();       // fails
            }
        }
    }
}

Stack trace:
io.github.jsonSnapshot.SnapshotMatchException: Could not find method two on class class java.lang.Object
Please annotate your test method with @Test and make it without any parameters!

	at io.github.jsonSnapshot.SnapshotMatcher.lambda$getMethod$4(SnapshotMatcher.java:174)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at io.github.jsonSnapshot.SnapshotMatcher.getMethod(SnapshotMatcher.java:172)
	at io.github.jsonSnapshot.SnapshotMatcher.lambda$getMethod$3(SnapshotMatcher.java:171)
	at java.util.Optional.map(Optional.java:215)
	at io.github.jsonSnapshot.SnapshotMatcher.getMethod(SnapshotMatcher.java:171)
	at io.github.jsonSnapshot.SnapshotMatcher.expect(SnapshotMatcher.java:99)

just stumbled on this issue too. are there any "workarounds"?

@teosarca You may want to look at this fork https://github.com/origin-energy/java-snapshot-testing - it is maintained (unlike this project) and supports nested tests.
We have recently switched to it in my project and so far everything works smoothly.


Quad Tailsitter: Bugfixes

@jingego As discussed please write down the biggest issues at the moment with the quad tailsitter.

I will write it soon.

Looks like it's still relevant.

partial fix in #13249


Changes in parameters

Hello!
I've noticed that you changed the beta parameter in the "india" examples from beta=0.0155 (as in your paper) to beta  = 0.0298, is this estimate from new data? If so from when?
Thanks!
Btw, really like the paper.
Cheers!
Nadia

@nbfigueroa this is a good observation. We use the same data but different models.
In our paper, we have used the SIR model. In this new example, you are referring to now, we are using the SEIR model. Both these models have been fitted to the same data and since beta is a fitting parameter given all other parameters, it is natural for it to be different in the two cases as SEIR has more parameters than SIR.
Thanks for your comments on your paper. Much appreciated.
Cheers,
Rajesh


total calculation is zero

Redmine version                3.0.3.stable.14369
Ruby version                   2.0.0-p643 (2015-02-25) [x86_64-linux]
Rails version                  4.2.2
Environment                    production
Redmine plugins:
advanced_roadmap_v2            2.4.3
clipboard_image_paste          1.10
progressive_projects_list      3.0.1
redmine_agile                  1.4.0
redmine_code_review            0.7.0
redmine_lightbox2              0.2.5
redmine_scm                    0.5.1
redmine_slack                  0.1
redmine_tags                   3.1.1
redmine_theme_changer          0.2.0
redmine_wiki_extensions        0.7.0
no errors in the log, a few NaN though.
Started GET "/milestones/total_graph?percentajes%5B%5D=NaN&percentajes%5B%5D=NaN&size=500x400&versions%5B%5D=50k+v1.0.0&versions%5B%5D=50k+v1.1.0" for <IP_ADDRESS> at 2016-06-02 08:33:32 -0400
Processing by MilestonesController#total_graph as HTML
Parameters: {"percentajes"=>["NaN", "NaN"], "size"=>"500x400", "versions"=>["50k v1.0.0", "50k v1.1.0"]}
Current user: jxxxx (id=6)
Rendered text template (0.0ms)
Sent data  (1.5ms)
Completed 200 OK in 93ms (Views: 1.1ms | ActiveRecord: 0.3ms)

won't fix


[JSX render]: A  which has a direct child text node blocks render

Describe the bug
See this JSX:

Name

            iPhone

              13

In the template above, a
 has a text node as its child. As expected, malform syntaxes like this should be blocked in build stage. However this syntax somehow passes the validation, and result in a unclosed template like _$template(`<div><table><thead><tr>Name</tr></thead><tbody><tr><td>iPhone`). It will cause any insert efforts failed with TypeError: Cannot read properties of null (reading 'nextSibling') , since the template is not correct and browser explain it to something not expected.
Your Example Website or App
https://codesandbox.io/p/devbox/great-leaf-tyf99q?file=%2Fsrc%2FApp.tsx%3A21%2C21-21%2C51
Steps to Reproduce the Bug or Issue

Open the devbox and everything should render correctly
De-comment Line 15 -17
Render will failed and in console a TypeError should be thrown

Expected behavior
Templates should be correctly generated, or a JSX validation error should be thrown.
Screenshots or Videos
No response
Platform

OS: Windows
Browser: Not related
SolidJs Version: 1.8.14

Additional context
No response

Yeah this needs a validation error. We can't really fix it as it is a browser correction. So far we only look for elements allowed in other elements using this package: https://github.com/MananTank/validate-html-nesting. Elements that can't accept text directly isn't a part of it. So this is a different sort of check.


chore(deps): update terraform github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vpc to v7.2.0

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vpc
module
minor
v7.0.1 -> v7.2.0

Release Notes

terraform-ibm-modules/terraform-ibm-landing-zone-vpc
v7.2.0
Compare Source
Features

add access tags support (#537) (3194ff7)

v7.1.0
Compare Source
Features

add the ability to remove all rules from the default VPC security group (using variable clean_default_security_group) (#516) (0a575f4)
add the ability to remove all rules from the default VPC ACL (using variable clean_default_acl) (#516) (0a575f4)

NOTES:

Both of these features are optional. If clean_default_security_group or clean_default_acl are set to true, then a value must be passed for ibmcloud_api_key. It also means the runtime must have the ibmcloud cli and the vpc-infrastructure[infrastructure-service/is] plugin installed
Removal of VPC default rules is not supported by the IBM Terraform provider at this time, so the rules are removed using a back-end command. You will not see the removal of default rules in either Terraform plan or in the Terraform logs.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 2.3.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


cant install FIVEM server with this module

i tried selling FIVEM servers with this module but its not working.
this is the error code :Failed to create the server, received the error code: 422. Enable module debug log for more info.
i am already selling Minecraft and discord bot servers so I know something isn't working just with this FIVEM

You didn't even follow the instructions to troubleshoot.
This isn't a problem with the module, you didn't set up the product right.
Selling FiveM servers is against the ToS and you won't receive any help to do so.

You cannot sell fivem servers unless you have an agreement with the fivem team.
We will not support the breaking of their TOS either way.


Auto refresh Table of Contents using docx

Hi,
I am adding new content to an existing Word document and I want an approach to auto-refresh my document's Table of contents. I've used below code but it is not showing any result and the document created out of it is struck in background process for which i had to kill from task manager.
import win32com.client
def update_toc(docx_file):
word = win32com.client.DispatchEx("Word.Application")
doc = word.Documents.Open(docx_file)
toc_count = doc.TablesOfContents.Count
if toc_count == 1:
toc = doc.TablesOfContents(1)
toc.Update()
print('TOC should have been updated.')
else:
print('TOC has not been updated for sure...')
update_toc(r"C:\Users\Mydocument.docx")
Will someone help me with the details to auto refresh my word document?

I also would like a solution to this issue, in my application that uses this library to generate a document I don't know if the user has MS Word, LibreOffice or some other office app installed, so workarounds like this and the one in #1207 don't really help me as they are dependent on an application outside this library


Can't find my username

now the registration require the first name and the last name not the username
i can see only the first name and the last name in the portal but i can't find the my username
software version
v0.9.14-53-g982fe24

This is intentional, as we are going to drop username support in the long run. For now, we still use usernames under the hood because they function as keys in the db. However, all api calls where a user is targeted should be able to be performed with the validated userinfo instead (validated phone or email).


Fix type error in Redux Essentials.

name: "Fix error in Redux Essentials tutorial"
about: Fixes a type error in the Redux Essentials tutorial
PR Type: Documentation Fix
Does this PR add a new feature, or fix a bug?
This PR fixes a bug in the Redux Essentials Tutorial, fixing issue #3812.
Why should this PR be included?
New users who go through the Redux Essentials tutorial will have code that might not work as expected if this fix is not added.
Checklist

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Is there an existing issue for this PR?

See #3812.

[x] Have the files been linted and formatted?
[x] Have the docs been updated to match the changes in the PR?
[x] Have the tests been updated to match the changes in the PR?
[x] Have you run the tests locally to confirm they pass?

What docs changes are needed to explain this?
See above.
Bug Fixes
What is the current behavior, and the steps to reproduce the issue?
When the user visits the route /posts/1 or /posts/2, the not found screen appears.
What is the expected behavior?
The post for id 1 or id 2 should display.
How does this PR fix the problem?
This PR adds a .toString() call in a comparison function to fix a type error where the selector was comparing an integer and a string (which will always return false).

Thanks!