AUTO-437 Investigate lack of intensity data on hokuyo

This PR addresses an issue with the reliability of the intensity data publishing. The main issue is this line:
https://github.com/botsandus/urg_node2/blob/6632d1ce1859a2ad8ad11d1c1b1117178769f263/src/urg_node2.cpp#L297
The is_intensity_supported() function checks the device supports intensity data by trying to read a single stream of distance + intensity. There are main ways this function can fail, or even not perform the check (this especially occurs when the sensor reconnects). This PR adds a loop to retry this check a few times (limited by the error_limit parameter).
I've tested this on the bench by disconnecting and reconnecting the LIDAR and it now recovers the intensity reliably (after a few retires in certain cases).

I've updated this PR to include the same fix for multiecho mode and also reverted the disable of their tests and move that to a different PR. This should allow us to pass on this and the other bugfix to the upstream repo.

Very cool @richardw347 thank you! I am getting this in the testing today and then let's get it in

Just updated this with changes from master to resolve conflicts, looking forward to getting it in.


Fixed the futur circular imports.

When adding the command line options for the observers in the list of default command line options, it creates a circular import. This fixes it.

This pull request looks really nice and simple. Let's merge it.


Ludox decision

Bug fixes for execution
examples of decision node in ludox protocol
improvements to execution engine to allow graceful failure and return errors/warnings
Change condition for FinalNode to be enabled to require any number (more than zero) tokens.

A large number of the changes are due to applying black formatting.  I plan to format everything after this gets merged.

@bbartley I'd like to rebase on this branch, so I'm wondering if you can have a look before I merge it.  Thanks!

The primitives in primitive_execution.py that define a compute_output() function were being added to the protocol doc.  I.e., we call get_primitive() to get the class, and then attach compute_output().  I didn’t want to change the default behavior of get_primitive(), which is to add the primitive to the doc.  I believe its used when importing libraries into a doc for the library.

On Mar 4, 2023, at 10:09 AM, bbartley @.***> wrote:
@bbartley commented on this pull request.
In labop/init.py:

@@ -276,7 +276,7 @@ def show_libraries():
for lib in labop.loaded_libraries.keys():
show_library(lib)

-def get_primitive(doc: sbol3.Document, name: str):
+def get_primitive(doc: sbol3.Document, name: str, copy_to_doc: bool = True):
I can anticipate the copy_to_doc flag might be useful in some cases. I'm curious, what was the use case that caused you to put it in?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.

I had merged your jetc-revert branch, which had this change.  Can you say more about that branch and whether we need it or not?

On Mar 4, 2023, at 10:11 AM, bbartley @.***> wrote:
@bbartley commented on this pull request.
In labop/container-ontology.ttl:

@@ -286,8 +274,7 @@ cont:width rdf:type owl:ObjectProperty ;
#################################################################

http://www.ontology-of-units-of-measure.org/resource/om-2/hasNumericalValue
-om:hasNumericalValue rdf:type owl:DatatypeProperty ;

                rdfs:range xsd:decimal .

+om:hasNumericalValue rdfs:range xsd:decimal .
If I am reading the diff correctly, it appears an important triple got deleted here:
om:hasNumericalValue rdf:type owl:DatatypeProperty
I think SBOLFactory will silently fail to generate the hasNumericalValue attribute if this is missing.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.

I applied the black formatter, which does this.  I plan to make this a global formatting change once we merge our outstanding branches.

On Mar 4, 2023, at 10:27 AM, bbartley @.***> wrote:
@bbartley commented on this pull request.
In labop/execution_engine.py:

     if isinstance(source, uml.Pin):

       src_parameter = source.get_parent().pin_parameter(source.name).property_value

       src_parameter = (

Are the parentheses here for line continuation recommended by PEP 8 style guide, or is it a personal preference? I don't have a problem with it, just trying to get a feel for your stylistic preferences.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.

This was also part of the jetc-revision branch.

On Mar 4, 2023, at 10:49 AM, bbartley @.***> wrote:
@bbartley commented on this pull request.
In labop_convert/behavior_specialization.py:

-def validate_spec_query(query: str) -> "tyto.URI":

if type(query) is tyto.URI:

   return query

if '#' in query:

   # Query is assumed to be a URI

   tokens = query.split('#')

   if len(tokens) > 2 or tokens[0] != ContO.uri:

       raise ValueError(f"Cannot resolve container specification '{query}'. The query is not a valid URI")

   return tyto.URI(query, ContO)

Query is assumed to be a qname

if ':' in query:

   tokens = query.split(':')

Removing this is going to break the labware inference example as well.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.

I don't think we need the jetc-revert branch.  That branch should be pruned.  I can't recall the problem I was trying to fix, but I think that I ended up resolving it without reverting.
Looking back, the revisions for the manuscript were merged into main in #180

I rebased on main without that jetc-revert branch and pushed remove-jetc-revert.  I want to merge this new branch to main, and will delete the one attached to this PR.  Sound okay?

On Mar 6, 2023, at 11:25 AM, bbartley @.***> wrote:
I don't think we need the jetc-revert branch. That branch should be pruned. I can't recall the problem I was trying to fix, but I think that I ended up resolving it without reverting.
Looking back, the revisions for the manuscript were merged into main in #180
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.

Good to go!

Obviated by #187 (rebased on main)


Additional EVM optimizations

This PR introduces optional additional optimizations for some of the EVM opcodes. It eliminates the word stack overflow and underflow checks, relying on the hypothesis that EVM bytecode coming from Solidity will not cause a stack overflow or underflow. The speed-up on our real-world engagements ranges between 5% and 20%, as per the following tables:

PR
master
Speedup

1
38
38
0.00%

2
30
30
0.00%

3
38
41
7.32%

4
41
43
4.65%

5
309
360
14.17%

6
460
575
20.00%

7
148
176
15.91%

PR
master
speedup

T1
164
170
3.53%

T2
128
132
3.03%

T3
100
106
5.66%

T4
321
342
6.14%

T5
1610
1702
5.41%

T6
297
334
11.08%

T7
178
199
10.55%

T8
103
110
6.36%

T9
112
120
6.67%

T10
947
993
4.63%

Could we do this based on a cell like <stackChecks> false </stackChecks> instead of as lemma inclusion? That would allow us to turn it on/off without rekompiling, by changing the value of that cell.

Could we do this based on a cell like <stackChecks> false </stackChecks> instead of as lemma inclusion? That would allow us to turn it on/off without rekompiling, by changing the value of that cell.

Yes, we could.

Hm, but then how do I formulate these? Structurally as well, with the <stackChecks> cell? I don't think I can?
    rule #stackUnderflow(_, _) => false [priority(30)]
    rule #stackOverflow(_, _) => false [priority(30)]

It would appear that the <stackChecks> approach speeds up the execution further when stack checks are deactivated (NSC), but slows down the execution by ~3% when they are activated (SC). Data from one of the engagements:

NSC
SC
master
NSC vs master
SC vs master

1
37
40
38
2.63%
-5.26%

2
30
31
30
0.00%
-3.33%

3
34
42
41
17.07%
-2.44%

4
38
44
43
11.63%
-2.33%

5
245
368
360
31.94%
-2.22%

6
460
587
575
20.00%
-2.09%

7
119
182
176
32.39%
-3.41%

Some interesting updates. There are essentially three version of this optimization:

V1: redefines stack overflow/underflow as always false, brings in a number of optimization rules. These simplifications are added at build time.
V2: Instead of redefining the stack overflow/underflow functions, it brings in two additional rules that override the treatment of #next so that stack overflow and underflow are never computed. Instead of adding all at build time, it introduces an additional configuration cell so that .
V3: V1, but with the two additional rules introduced by V3. This is what is currently in the PR.

The results on our largest real-world engagement as follows:

V1
V2
V3
master
V1 speedup
V2 speedup
V3 speedup

T1
164
161
160
170
3.53%
5.29%
5.88%

T2
128
123
123
132
3.03%
6.82%
6.82%

T3
100
93
93
106
5.66%
12.26%
12.26%

T4
321
307
306
342
6.14%
10.23%
10.53%

T5
1610
1529
1520
1702
5.41%
10.16%
10.69%

T6
297
259
256
334
11.08%
22.46%
23.35%

T7
178
157
156
199
10.55%
21.11%
21.61%

T8
103
96
95
110
6.36%
12.73%
13.64%

T9
112
107
107
120
6.67%
10.83%
10.83%

T10
947
907
892
993
4.63%
8.66%
10.17%

and we see that V2 and V3 outperform V1, and that V3 is consistently slightly faster than V2. In addition, V2 exhibits a slowdown with respect to V1/V3 of ~3% when stack checks are turned on, probably due to the combination of an additional cell and additional high-priority rules that are always checked.
V1, given these results, is out of the picture.
The pros of the V2 approach are that we don't have to rekompile between runs of the same proof with and without stack checks. A semi-pro is that it the speed-up is comparable to V2. The cons are that we introduce a new cell into the configuration and that there is a slowdown when stack checks are turned on.
The pros of the V3 approach are that it is the fastest, and that there is no slowdown when stack checks are turned back on. The cons are that one does have to rekompile if one wants to use re-run a proof stack checks. The mitigation of that con is that our working hypothesis is strong and that we would want to re-run a proof with stack checks very rarely.
Given this data, my choice is V3. Thoughts?

We are going with V2 in the end, everything is in place and CI is passing. @ehildenb

I approved, but something to fix. When doing kontrol show ... --to-kevm-rules, it attempts to produce KEVM rules for the given KCFG that can be tested/used directly as summaries, which we have some clients using. This isn't tested very well, on CI, but changing the configuration structure of Kontrol can break it.

In particular, here we extract the KEVM sub-configuration to produce rules runnable with KEVM, and this extraction pattern needs to be updated with the new cell.
Second, the rules produced should not execute past rules that do not exist in KEVM, like the Kontrol cheatcodes or other instrumentation. So when new rules are added, it's good to include them in the list of rules that are done with --break-on-cheatcodes here, so that we can make sure that every time a non-KEVM rule fires we save off the node before and after. This ensures that kevm show ... --to-kevm-rules can filter out those KCFG edges (done here) which contains steps from Kontrol that aren't in KEVM.

We should also add a test of kontrol show --to-kevm-rules, because it's something that we use for another engagement.

If these rules are included in --break-on-cheatcodes, they will make the feature completely unusable in any real-world debugging since they will fire on every #next, it’d be like --break-every-step, which simply does not scale. It is essential to be able to debug use of actual cheatcodes.
I am also not quite understanding in which context --to-kevm-rules is useful, hasn’t this been replaced by CSE? Which client would be running KEVM and not Kontrol?
All of this indicates to me that these rules should perhaps be added to KEVM (just like the <useGas> rules), not Kontrol.

When it comes to testing --to-kevm-rules, that feels like a job for the next PR.


MRI: Improve definition of bvec file

Closes #243.
Making an attempt to resolve this issue as ensuring that the definition here is robust and consistent across different softwares will be essential to verifying the definition of orientation encoding for BEP016 MRI diffusion models.
References:

FSL documentation
Implementation changes we made to MRtrix3 on load and save
Announcement on the MRtrix3 community forum regarding how our prior support for this format was flawed and how it was fixed.

I'm listing this as a draft PR as it's entirely possible that the phrasing can be fine-tuned. Pinging @jdtournier; if anyone knows of an appropriate person from FMRIB to ping please do so.
One note here is that I've intentionally avoided the use of "radiological" vs. "neurological" coordinate systems. I've always thought of these as being in reference to two-dimensional projections of image data. There seems to be some confusion about which of these terms apply in reference to three-dimensional coordinate systems. Therefore I chose to stick to "left-handed vs. right-handed" / "positive vs. negative determinant". Not strictly against use of such terms, but the ambiguity would need to be resolved.

Looks good to me. I might suggest a very minor rewording, but it might be more a matter of personal preference than clarity...
This sentence:

Further, if the rotation component of the NIfTI image header transformation possesses a positive determinant (a "right-handed" coordinate system), then the sign of the first element of each 3-vector must be inverted to be interpreted as cosines with respect to the first image axis orientation.

Modify to:

Moreover, if the image axes defined in the corresponding NIfTI image header form a right-handed coordinate system (in other words, the 3×3 matrix of direction cosines has a positive determinant), then the sign of the first element of each 3 vector must be inverted before any further interpretation.

In fact, I'd be tempted to mention this particular aspect before describing the interpretation as relative to the image axes, to ensure that there is no confusion about when the sign flip takes place: it applies to the original entry in the bvec table, not the x-component following transformation into scanner space or something.
I would also have a more upfront statement about the fact that bvecs are relative to some reference image, maybe in the second sentence, with something like:

In this format, the gradient directions are specified relative to a reference image, which must also be provided in order to correctly interpret the information.

As it stands, the fact that the reference image must be supplied is implicit from the later discussion, but in my opinion it's a really important consideration that deserves to be stated very upfront.

if anyone knows of an appropriate person from FMRIB to ping please do so

Maybe Mark Jenkinson, @markj789?

Had a go at some minor tweaks. The directions being defined with respect to the image axes is stated explicitly twice, and the ordering of statements about flipping of first element / contrast against DICOM convention is hopefully better.

Marked as ready for review.

Thanks @Lestropie for the PR, and thanks all for the reviews!


What was wrong with HTA?

Bad architecture is impossible to change, on the delivered whatever.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0f6a3fc4-ae92-1353-9600-a6547082b1e2
Version Independent ID: abdf9451-f4ba-5b3f-f516-c5d0361d2d32
Content: Introduction to Microsoft Edge WebView2 - Microsoft Edge Development
Content Source: microsoft-edge/webview2/index.md
Product: microsoft-edge
Technology: webview
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thank you for reaching out, but I fail to see how this is relevant to improving the Microsoft Edge developer documentation. So I will close this issue now.


[okina] Support for ComputeL2Error grid function method

A feature that would be nice to have is support for the ComputeL2Error grid function method when using Okina/Okina memory manager. If I have  GPU capabilities enabled, i.e.
config::useCuda();
config::enableGpu(0);
config::SwitchToGpu();

I get assertion errors or if i try to switch to the cpu, i.e.
config::SwitchToCpu()

I get the following error
mm::Ptr

I'll make a reproducer using example 9.

Switching back to host for the mass CG solver allows to get the right solution.
This solves #762 and #768.


public declaration removing

I have read the CLA Document and I hereby sign the CLA

All committers have signed the CLA.

recheckcla


at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:289:26)
Test Name: create-megaraid-spec.js "before all" hook: Check schema definition
Error Details: expected { Object (copyright, title, ...) } to have a property 'describeJob'
Stack Trace: AssertionError: expected { Object (copyright, title, ...) } to have a property 'describeJob'
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:119:32)

Build finished.

BUILD on-tasks #1654 : ABORTED

** BUILD build-config-setup  #120256: SUCCESS

** BUILD unit-tests  #9540: UNSTABLE

** BUILD smoke-test  #3505: ABORTED

** BUILD on-taskgraph #1575: UNSTABLE

** BUILD build-config-setup  #120260: SUCCESS
** BUILD unit-tests  #9541: UNSTABLE

** BUILD on-http #2635: SUCCESS

** BUILD build-config-setup  #120263: SUCCESS
** BUILD unit-tests  #9542: SUCCESS

BUILD unit-tests  #9540  Error Logs:
Test Name: Task serialization should serialize a job for an instance
Error Details: Invalid token "undefined" requested!
Stack Trace: Error: Invalid token "undefined" requested!
at Injector.get (node_modules/di/dist/cjs/injector.js:112:13)
at Task.instantiateJob (lib/task.js:9:13644)
at spec/lib/task-spec.js:469:22
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Task timer should have a default timeout with null or unsupported values
Error Details: Invalid token "undefined" requested!
Stack Trace: Error: Invalid token "undefined" requested!
at Injector.get (node_modules/di/dist/cjs/injector.js:112:13)
at Task.instantiateJob (lib/task.js:9:13644)
at Task._run (lib/task.js:9:17175)
at spec/lib/task-spec.js:629:26
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Task timer should not timeout when value is 0
Error Details: expected 'failed' to equal 'succeeded'
Stack Trace: AssertionError: expected 'failed' to equal 'succeeded'
at spec/lib/task-spec.js:652:43
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Task timer should not timeout when value is -1
Error Details: expected 'failed' to equal 'succeeded'
Stack Trace: AssertionError: expected 'failed' to equal 'succeeded'
at spec/lib/task-spec.js:667:43
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Task timer should timeout with options._taskTimeout
Error Details: expected 'failed' to equal 'timeout'
Stack Trace: AssertionError: expected 'failed' to equal 'timeout'
at spec/lib/task-spec.js:682:43
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Task timer should timeout with options.schedulerOverrides
Error Details: expected 'failed' to equal 'timeout'
Stack Trace: AssertionError: expected 'failed' to equal 'timeout'
at spec/lib/task-spec.js:699:43
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Task cancellation/completion of task should cancel
Error Details: Invalid token "undefined" requested!
Stack Trace: Error: Invalid token "undefined" requested!
at Injector.get (node_modules/di/dist/cjs/injector.js:112:13)
at Task.instantiateJob (lib/task.js:9:13644)
at Context.<anonymous> (spec/lib/task-spec.js:752:22)
Test Name: Task cancellation/completion of job "before each" hook: task-spec-job-cancellation beforeEach for "should cancel a job"
Error Details: Invalid token "undefined" requested!
Stack Trace: Error: Invalid token "undefined" requested!
at Injector.get (node_modules/di/dist/cjs/injector.js:112:13)
at Task.instantiateJob (lib/task.js:9:13644)
at Context.<anonymous> (spec/lib/task-spec.js:784:22)
Test Name: Task task schema should retrieve the task schema information
Error Details: expected { Object (allOf) } to deeply equal { describeJob: 'Job.noop' }
Stack Trace: AssertionError: expected { Object (allOf) } to deeply equal { describeJob: 'Job.noop' }
at assertEqual (node_modules/chai/lib/chai/core/assertions.js:439:19)
at ctx.(anonymous function) (node_modules/chai/lib/chai/utils/addMethod.js:40:25)
at doAsserterAsyncAndAddThen (node_modules/chai-as-promised/lib/chai-as-promised.js:298:33)
at null.<anonymous> (node_modules/chai-as-promised/lib/chai-as-promised.js:251:21)
at ctx.(anonymous function) [as equal] (node_modules/chai/lib/chai/utils/overwriteMethod.js:48:33)
at spec/lib/task-spec.js:833:66
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: shell-commands-spec.js task-data expected properties should have valid default option values
Error Details: Task definition job name (string) is required
Stack Trace: AssertionError: Task definition job name (string) is required
at AssertService.(anonymous function) [as string] (node_modules/on-core/lib/common/assert.js:30:28)
at Function.validateDefinition (lib/task.js:9:22382)
at lib/task.js:9:24252
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Function.Promise.attempt.Promise.try (node_modules/on-core/node_modules/bluebird/js/main/method.js:31:24)
at Function.create (lib/task.js:9:24156)
at Context.<anonymous> (spec/lib/task-data/tasks/base-tasks-spec.js:112:29)
Test Name: flash-ami-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-ami-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-ami-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-ami-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-ami-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-ami-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-ami-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: flash-ami-spec.js validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-ami-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-ami-spec.js validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-ami-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-ami-spec.js validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-ami-spec.js validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: linux-command-spec.js common linux command validation "before all" hook: Check schema definition
Error Details: expected { Object (copyright, definitions, ...) } to have a property 'describeJob'
Stack Trace: AssertionError: expected { Object (copyright, definitions, ...) } to have a property 'describeJob'
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:119:32)
Test Name: linux-catalog-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: linux-catalog-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: linux-catalog-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: linux-catalog-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: linux-catalog-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: linux-catalog-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: linux-catalog-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: catalog-raid-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: catalog-raid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: catalog-raid-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: catalog-raid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: catalog-raid-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: catalog-raid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: catalog-raid-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: catalog-raid-spec.js validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: catalog-raid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: catalog-raid-spec.js validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: catalog-raid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: catalog-raid-spec.js validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: catalog-raid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: download-file-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: download-file-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: download-file-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: download-file-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: download-file-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: download-file-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: download-file-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: download-file-spec.js validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: download-file-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: download-file-spec.js validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: download-file-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: download-file-spec.js validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: download-file-spec.js validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: delete-megaraid-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: delete-megaraid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: delete-megaraid-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: delete-megaraid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: delete-megaraid-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: delete-megaraid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: delete-megaraid-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: delete-megaraid-spec.js validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: delete-megaraid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: delete-megaraid-spec.js validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: delete-megaraid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: delete-megaraid-spec.js validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: delete-megaraid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: sku-firmware-update-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: sku-firmware-update-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: sku-firmware-update-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: sku-firmware-update-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: sku-firmware-update-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: sku-firmware-update-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: sku-firmware-update-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: sku-firmware-update-spec.js validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: sku-firmware-update-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: sku-firmware-update-spec.js validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: sku-firmware-update-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: sku-firmware-update-spec.js validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: sku-firmware-update-spec.js validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: sku-firmware-update-spec.js schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: set-bmc-credentials-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: set-bmc-credentials-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: set-bmc-credentials-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: set-bmc-credentials-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: set-bmc-credentials-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: set-bmc-credentials-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: set-bmc-credentials-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: set-bmc-credentials-spec.js validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: set-bmc-credentials-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: set-bmc-credentials-spec.js validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: set-bmc-credentials-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: set-bmc-credentials-spec.js validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: set-bmc-credentials-spec.js validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: firmware-update-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: firmware-update-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: firmware-update-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: firmware-update-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: firmware-update-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: firmware-update-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: firmware-update-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: firmware-update-spec.js validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: firmware-update-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: firmware-update-spec.js validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: firmware-update-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: firmware-update-spec.js validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: firmware-update-spec.js validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-megaraid-spec.js common linux command validation validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-megaraid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-megaraid-spec.js common linux command validation validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-megaraid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-megaraid-spec.js common linux command validation validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-megaraid-spec.js common linux command validation validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-megaraid-spec.js common linux command validation schema negative unset testing should violate the schema if "commands" is unset
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:347:26)
Test Name: flash-megaraid-spec.js validate task common options should fail if '_timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-megaraid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=-2
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-megaraid-spec.js validate task common options should fail if '_timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-megaraid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'=1.5
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: flash-megaraid-spec.js validate task common options should fail if '_timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:199:22)
Test Name: flash-megaraid-spec.js validate task common options should fail if 'schedulerOverrides.timeout'="100"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:103:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:170:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:205:26)
Test Name: create-megaraid-spec.js "before all" hook: Check schema definition
Error Details: expected { Object (copyright, definitions, ...) } to have a property 'describeJob'
Stack Trace: AssertionError: expected { Object (copyright, definitions, ...) } to have a property 'describeJob'
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:119:32)
Test Name: analyze-os-repo-spec.js "before all" hook: Check schema definition
Error Details: expected { Object (copyright, properties, ...) } to have a property 'describeJob'
Stack Trace: AssertionError: expected { Object (copyright, properties, ...) } to have a property 'describeJob'
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:119:32)

test this please


Refactor frame

I see a lot of repeater color definitions in the code. Can we replace those by a define with a name of the color?

Why did the jenkins test not run? Can you rebase to latest master so we see CPU usage in CI?


Add Japanese language support and translate some docs into Japanese

What kind of changes does this PR include?

Changes or translations of Starlight docs site content
Changes to Starlight code

Description

Add Japanese language support.
Translate some pages of the docs into Japanese.

@delucis While this PR includes changes to the Starlight code, the majority of the changes are translations. Should I add a changeset in this case?

Thanks for this @morinokami!
Yes, we should add a patch changeset so that the next release notes say that Japanese support was added 🥳
You can add one by running pnpm changeset add in the repo or clicking the “add a changeset” link in the bot message above. Let me know if you have any questions.
We should also update this line in the i18n docs to mention Japanese support: https://github.com/withastro/starlight/blob/de24b54971577912979a3fb67570f4c95efe27a6/docs/src/content/docs/guides/i18n.md?plain=1#L113

@delucis Ah, it was the middle of the night in Japan, so I had to stop working on it😅 Thank you for taking over and completing the rest!


Revamping Buttons and Text

The intro text is small for the desktop view and I would like to change the button to a larger size.

#17 This issue is solved in the PR mentioned


CookieJar Option

Excuse me, there is no cookiejar option for tls-client?

@yiming1995 not exactly sure why you need to define a separate cookiejar. a default cookie jar will be used in the http client and you can set / get cookies by calling GetCookies or SetCookies on the client.
Nevertheless i added the option in v0.2.1 to define a custom cookiejar. You just have to implement the http.CookieJar interface. The client interface was also extended to have a function to get the cookiejar from the client: GetCookieJar() http.CookieJar


Provide example on how to handle device rotation.

When you request a permission, Dexter makes note that a permission request is outstanding. If I previously denied a permission, I'll get the callback showPermissionRationale(PermissionToken). We're supposed to use this to continue our permission request with PermissionToken.continuePermissionRequest() or cancel it with PermissionToken.cancelPermissionRequest(). However, if I choose to show an AlertDialog (as is done in the SampleActivity, the user could rotate the device, leading to me losing access to my token and being unable to cancel or continue the request.
This would lead to the crasher described in #14, which was fixed by locking the orientation of the sample app.
What I'd like to see is an example on how you suggest we recover our state after a device rotation. Specifically, what is your suggested way to persist the PermissionToken?
It'd be great if this were in the sample app.

Thanks @greysonp I'm working on it :)

Version 2.1.0 contains methods and an example of how to handle this with the library. Thank you all for your contribution!


sg3_utils: 1.47 -> 1.48

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/sg3-utils/versions.
meta.description for sg3_utils is: Utilities that send SCSI commands to devices
meta.homepage for sg3_utils is: https://sg.danny.cz/sg/
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.48 with grep in /nix/store/3rigd7d5hd84vxwwm2yxpzjk8jplc4kh-sg3_utils-1.48
found 1.48 in filename of file in /nix/store/3rigd7d5hd84vxwwm2yxpzjk8jplc4kh-sg3_utils-1.48

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
gtkpod
ledmon
libgpod
rhythmbox
sasutils
sg3_utils
strawberry
tgt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3rigd7d5hd84vxwwm2yxpzjk8jplc4kh-sg3_utils-1.48 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sg3_utils https://github.com/r-ryantm/nixpkgs/archive/63e4ff8bde4e1f9067b9149fbac4a30b03d8fb06.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3rigd7d5hd84vxwwm2yxpzjk8jplc4kh-sg3_utils-1.48
ls -la /nix/store/3rigd7d5hd84vxwwm2yxpzjk8jplc4kh-sg3_utils-1.48/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

8 packages built:

gtkpod
ledmon
libgpod
rhythmbox
sasutils
sg3_utils
strawberry
tgt

Maintainer pings

Result of nixpkgs-review pr 251462 run on x86_64-linux 1

10 packages built:

gtkpod
ledmon
libgpod
libgpod.dev
rhythmbox
sasutils
sasutils.dist
sg3_utils
strawberry
tgt


Remove duplicate recurring events

Expected behaviour

When there are repetitive events e.g. daily / weekly there should be an option to only show x many of these e.g. over the next 7days or 30days
Current behaviour

Cant currently do this only able to hideDuplicates of the same event on the same day.
Screenshot

Possible solutions

Add a new option recurringEvent: 7 which would remove any events with the same title at the same time after 7 days.
Context and reason

User requested as the calendar is flooded with these events such as football practice which aren't needed to be shown until the week they happen.
Checklist

[x] I searched the current issues and the feature is not known.
[x] I am mostly sure that the feature will bring more good than bad.

Recurring events, such as birthdays, appear on every month on the day they occur on. I believe this is covered under this issue? Is there a workaround or solution for this type of issue?

Please respond if this repository is still being maintained.  It does not appear to be.