+1
Færdig

Suspend Tool is not working properly in warewolf version 2.6.6

Hemant Chauhan 4 år siden opdateret af anonymous 4 år siden 2

WareWolf Version : 2.6.6

Please find attached workflow and perform below steps to check two different errors in suspend Tool.


Error 1

1) Copy the input payload from comment section.

2) Execute the workflow 

Error 2

1) Copy the input payload from comment section.

2) Uncheck Manual resumption from suspend tool.

3) Execute the workflow.

 

AdvanceSuspendTesting.bite

0
Færdig

Test Case Is getting failed in Dev & Staging environment.

Hemant Chauhan 4 år siden opdateret af Siphamandla Dube 4 år siden 3

Test Cases is sometimes getting failed and some times getting pass in dev and stagging environment. Please find below details for more information. 

newjourney_serverLog.log

TestCasePassReport.png

CoverageReport.PNG

TestCaseReport.PNG

Note: This is high priority blocker for us

Svar
Siphamandla Dube 4 år siden

Closing ticket as the is no longer any further communication in this regard. 

0
Besvaret

Configure SSL certificate for port 3143?

Timothy Boyden 4 år siden i Server opdateret af Elmo 4 år siden 2

How do you secure port 3143 with a real SSL certificate? Haven't been able to find any documentation on this. Using server version 2.6.2.0.

server
+1
Færdig

Facing Issue while deleting test cases

Hemant Chauhan 4 år siden opdateret af Siphamandla Dube 4 år siden 3

Werewolf Version : 2.6.6

We are facing the issue while deleting the test cases. Please check attached file for the same. 

WW Issue-20211115_174356-Meeting Recording.mp4

Server Log

Svar
Siphamandla Dube 4 år siden

Hello Hermant,

In regards to: "Thus, we will keep this ticket open and use it to track the work needed to adjust the mechanism to cater to this." This has been revised and the best solution with this enhancement would be to manually clean the "%programdata%\Warewolf\CoverageReports" folder as with each test we run the Test Coverage report is generated.

Steps:

  1. Delete all Coverage Reports inside "%programdata%\Warewolf\CoverageReports"
  2. Run http://localhost:3142/secure/.tests or of that specific folder
  3. Run http://localhost:3142/secure/.coverage should at this point regenerate all the reports you just removed

With this suggestion, this ticket will be closed.

0
Færdig

Facing Issue While Creating Unit Test Cases.

Hemant Chauhan 4 år siden opdateret af Siphamandla Dube 4 år siden 2

Warewolf Version : 2.6.6

Issue Detail : API long response is getting cut down in test framework. Please check attached video for more detail. 

Test Framework Issue-20211112_185932-Meetin....mp4

+1

Suspend Tool Failing

Anonym 4 år siden i Server / Execution 0

There is a problem with the suspend tool. I have two workflows created in 2.6.6.0, one works fine and the other does not.

Works fine: SuspendToolTest

Does not work: suspendtest

suspendtest.bite
SuspendToolTest.bite


Image 975

Image 976

+1
Planlagt

Dark Theme in Warewolf Studio

Hemant Chauhan 4 år siden opdateret af Gandalf 4 år siden 2

its all about the choice but I am suggesting you because it help to reduce the eyes stress of developer. 

Svar
Gandalf 4 år siden

Hi Hemant

We are working on a web UI and will include this in that version. In the interim, why dont you try https://justgetflux.com/

There is a specific "Reduce Eyestrain" feature which I use.

0

Warewolf-2.6.4: Facing issue with input parameters which persist value from another workflow with same name but in different folder.

maya khambhayata 4 år siden i Studio 0

Discussion-20211022_125108-Meeting Recording.mp4Warewolf-2.6.4: Create workflow with name "Main" in 2 folder "PreWelcome" and "Welcome". Both workflows have same name "Main" but logic is different in different folder. but input parameters are same for both the workflows like "journeyname" and "referenceid" but value is different. It creating problem with the persistent of value in workflows.  I am posting video and workflows for the same.workflow.zip

0

Warewolf-2.6.4: Trigger: On Local environment trigger is not picking the data from Rabbit MQ in most cases.

maya khambhayata 4 år siden i Server 0

Discussion-20211022_124100-Meeting Recording.mp4 in Warewolf-2.6.4 version, I have created 4 triggers in local environment and set the concurrency to more than 1. It created the queue in RabbitMQ. While pushing the data to queue in RMQ. It is not picking data most of the time. I have to edit something in trigger and save again. For example i have to change concurrency from 2 to 3 OR 3 to 2. then only trigger is picking data from RMQ. Also checked with other team members too. They are also facing same issue. Here I am attaching video recording for same.

0
Ikke en bug

Exception: Unable to contact Server

Timothy Boyden 4 år siden i Studio opdateret 4 år siden 4

Trying to connect local instance of Studio to remote instance of Server. Receiving error "Exception: One or more errors occurred. Inner Exception: Unable to contact Server".

I tried debugging this with the source version of Studio in Visual Studio this morning. When clicking the New button, the code throws an exception and execution pauses. Attached are the messages from the Visual Studio output window.

New button exception messages.txt

I click continue in Visual Studio so I can test the Test Server function. That throws another exception, messages attached.

Test Server exception messages.txt

Image 961

The messages themselves are not helpful for that exception message. But here are the data contents of the comsController object:

ServicePayload --> args(0) --> {[ServerSource, {{"$id":"1","$type":"Dev2.Common.ServerSource, Dev2.Common","ServerName":null,"Address":"http://192.168.1.190:3142","AuthenticationType":3,"UserName":null,"Password":null,"TestCommand":null,"TestMessage":null,"ID":"04bb532e-2b67-413c-973f-fdbb1551381b","Name":null,"ResourcePath":null}}]}

It looks like the Test Connection button is trying to execute the test against the localhost server instead of the specified remote server. Here are the screenshotted contents of the connection object uses in the comsController.ExecuteCommand call:

Image 962

Because there is no local server running, I would expect that call to return null, and thus throw an exception per the code. Because it throws an exception, no log entry is being made for the failed Test Connection call. Hence why no attempt shows up in the Warewolf Studio logs. Attaching the log anyways, even though it doesn't show any of the above activity occurring:


Warewolf Studio.log

Here is the server log when doing the remote Hello World test via the local web browser:

wareWolf-Server.log

studio


Kundesupport af UserEcho