Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TS] LPS-125037 Apply button in Filter by Field panel is not shown correctly after trying to modify the value that we set earlier #638

Closed
wants to merge 1 commit into from

Conversation

bakayattila
Copy link

@bakayattila bakayattila commented Dec 17, 2020

hi Team,
Could you please review this pull request?
https://issues.liferay.com/browse/LPS-125037

best,
Attila


Steps

Setup Liferay DXP 7.2 with
Create a new structure with a Text field
Create a new web content with the structure
In the field
On the Home page add an Asset Publisher
Go to the configuration panel of the Asset Publisher→Display Settings
Asset Selection: Dynamic
Asset Type: Web Content Article
Web Content Article Structures: Basic Web Content
Filter by Field: YES
Click on Select
Check the new form

Expected Behavior
Only the apply button of the selected radio button is enabled

Actual Behavior
All the apply buttons enabled

The main reason behind the null check here is to prevent unnecessary modification on any form that is not related to asset selection.

@liferay-continuous-integration
Copy link
Collaborator

CI is automatically triggering the following test suites:

  •     ci:test:relevant
  •     ci:test:sf

@bakayattila bakayattila changed the title [TS] LPS-125037 [TS] LPS-125037 Apply button in Filter by Field panel is not shown correctly after trying to modify the value that we set earlier Dec 17, 2020
@liferay-continuous-integration
Copy link
Collaborator

✔️ ci:test:sf - 1 out of 1 jobs passed in 8 minutes

Click here for more details.

Base Branch:

Branch Name: master
Branch GIT ID: ff0e5e147ea14773fc626b3a4024d041bfefb138

Sender Branch:

Branch Name: LPS-125037
Branch GIT ID: c98f7abbefe679e577e0cf2e3fd4e09a1b1642c0

1 out of 1jobs PASSED
1 Successful Jobs:
For more details click here.

@liferay-continuous-integration
Copy link
Collaborator

@liferay-continuous-integration
Copy link
Collaborator

✔️ ci:test:stable - 9 out of 9 jobs passed

❌ ci:test:relevant - 20 out of 23 jobs passed in 2 hours 53 minutes

Click here for more details.

Base Branch:

Branch Name: master
Branch GIT ID: ff0e5e147ea14773fc626b3a4024d041bfefb138

Copied in Private Modules Branch:

Branch Name: master-private
Branch GIT ID: 0ff04d9f73a4643abdd2b335581feef26b985b8a

ci:test:stable - 9 out of 9 jobs PASSED
9 Successful Jobs:
ci:test:relevant - 20 out of 23 jobs PASSED
20 Successful Jobs:
For more details click here.

Failures unique to this pull:


Failures in common with acceptance upstream results at ff0e5e1:
  1. test-portal-acceptance-pullrequest-batch(master)/semantic-versioning-jdk8/0
    Job Results:

    0 Tests Passed.
    1 Test Failed.

    1. AXIS_VARIABLE=0,label_exp=!master #481963

      Please fix semantic versioning on bakayattila/LPS-125037

           [exec] 			+   return     void
           [exec] 		+   method     <init>(java.lang.String)
           [exec] 			+   return     void
           [exec] 		+   method     <init>(java.lang.String,java.lang.Throwable)
           [exec] 			+   return     void
           [exec] 		+   method     <init>(java.lang.Throwable)
           [exec] 			+   return     void
           [exec] 		+   method     addSuppressed(java.lang.Throwable)
           [exec] 			+   access     final
           [exec] 			+   return     void
           [exec] 		+   method     clone()
           [exec] 			+   access     protected
           [exec] 			+   return     java.lang.Object
           [exec] 		+   method     equals(java.lang.Object)
           [exec] 			+   return     boolean
           [exec] 		+   method     fillInStackTrace()
           [exec] 			+   return     java.lang.Throwable
           [exec] 		+   method     finalize()
           [exec] 			+   access     protected
           [exec] 			+   return     void
           [exec] 		+   method     getCause()
           [exec] 			+   return     java.lang.Throwable
           [exec] 		+   method     getLocalizedMessage()
           [exec] 			+   return     java.lang.String
           [exec] 		+   method     getMessage()
           [exec] 			+   return     java.lang.String
           [exec] 		+   method     getStackTrace()
           [exec] 			+   return     java.lang.StackTraceElement[]
           [exec] 		+   method     getSuppressed()
           [exec] 			+   access     final
           [exec] 			+   return     java.lang.Throwable[]
           [exec] 		+   method     hashCode()
           [exec] 			+   return     int
           [exec] 		+   method     initCause(java.lang.Throwable)
           [exec] 			+   return     java.lang.Throwable
           [exec] 		+   method     printStackTrace()
           [exec] 			+   return     void
           [exec] 		+   method     printStackTrace(java.io.PrintStream)
           [exec] 			+   return     void
           [exec] 		+   method     printStackTrace(java.io.PrintWriter)
           [exec] 			+   return     void
           [exec] 		+   method     setStackTrace(java.lang.StackTraceElement[])
           [exec] 			+   return     void
           [exec] 		+   method     toString()
           [exec] 			+   return     java.lang.String
           [exec] [Baseline Report] Mode: diff (persisted)
           [exec] Semantic versioning is incorrect while checking /opt/dev/projects/github/liferay-portal/portal-kernel/portal-kernel.jar against /opt/dev/projects/github/liferay-portal/.gradle/caches/modules-2/files-2.1/com.liferay.portal/com.liferay.portal.kernel/9.18.0/471e51c2d8cc477362ba9dd7449b8c3974545660/com.liferay.portal.kernel-9.18.0.jar

@liferay-continuous-integration
Copy link
Collaborator

@jbalsas
Copy link

jbalsas commented Dec 21, 2020

Test error was flagged last week, so I'm going to rerun to see this green.

@bakayattila, while we wait to get confirmation from CI, could you please take some time to read through the following submission guidelines and update the PR with the suggestions below?

In summary, we'd appreciate if you could provide:

  • Descriptive title beyond a mere LPS ✅
  • Thorough description of the issue, things you tried, why you thing your solution is the right approach and any other considerations that might help us in our review 🔴
  • Test plan with simple steps to validate the issue (or get a feeling of how it has been validated by you) 🔴

I understand some of these might already be covered in the LPS itself, but having some of that data here helps us track it down and trace it when things move from user to user and allows us to focus on the review itself.

Thanks for your help in making this process better for everyone!! ❤️

@jbalsas
Copy link

jbalsas commented Dec 21, 2020

ci:test:relevant

@bakayattila
Copy link
Author

Hi @jbalsas , I updated the PR. I hope it is acceptable now.

@jbalsas
Copy link

jbalsas commented Dec 21, 2020

Hi @jbalsas , I updated the PR. I hope it is acceptable now.

Thanks @bakayattila, appreciate the effort!! 🤗

The main reason behind the null check here is to prevent unnecessary modification on any form that is not related to asset selection.

This is the kind of information that is interesting and helps speed up the process! 😉

@liferay-continuous-integration
Copy link
Collaborator

✔️ ci:test:stable - 9 out of 9 jobs passed

✔️ ci:test:relevant - 22 out of 23 jobs passed in 1 hour 42 minutes

Click here for more details.

Base Branch:

Branch Name: master
Branch GIT ID: dab7ad790ee947a2abc6cc6b656a1caa46943ac5

Copied in Private Modules Branch:

Branch Name: master-private
Branch GIT ID: 15218ef33680a1fe233ea812e8d097cfcb0feb42

ci:test:stable - 9 out of 9 jobs PASSED
9 Successful Jobs:
ci:test:relevant - 21 out of 23 jobs PASSED
21 Successful Jobs:
For more details click here.

This pull contains no unique failures.


Failures in common with acceptance upstream results at dab7ad7:
  1. test-portal-acceptance-pullrequest-batch(master)/modules-integration-mysql57-jdk8/0
    Job Results:

    367 Tests Passed.
    1 Test Failed.

    1. AXIS_VARIABLE=0,label_exp=!master #449788
      1. PortalLogAssertorTest.testScanXMLLog
        junit.framework.AssertionFailedError: 
        HikariPool-1 - Connection is not available, request timed out after 600000ms.
        	at com.liferay.portal.log.assertor.PortalLogAssertorTest.scanXMLLogFile(PortalLogAssertorTest.java:171)
        	at com.liferay.portal.log.assertor.PortalLogAssertorTest$1.visitFile(PortalLogAssertorTest.java:98)
        	at com.liferay.portal.log.assertor.PortalLogAssertorTest$1.visitFile(PortalLogAssertorTest.java:88)
        	at java.nio.file.Files.walkFileTree(Files.java:2670)
        	at java.nio.file.Files.walkFileTree(Files.java:2742)
        	at com.liferay.portal.log.assertor.PortalLogAssertorTest.testScanXMLLog(PortalLogAssertorTest.java:86)
        

@jbalsas
Copy link

jbalsas commented Dec 21, 2020

I haven't tested this, but changes kinda make sense, so I'm going to take your word for it assuming you've done the proper manual testing since this is an old part of portal and automatic test coverage is not going to help us much.

Thanks!

@jbalsas
Copy link

jbalsas commented Dec 21, 2020

ci:forward

@liferay-continuous-integration
Copy link
Collaborator

CI is automatically triggering the following test suites:

  •     ci:test:relevant
  •     ci:test:sf

The pull request will automatically be forwarded to the user brianchandotcom if the following test suites pass:

  •     ci:test:relevant
  •     ci:test:sf
  •     ci:test:stable

@liferay-continuous-integration
Copy link
Collaborator

Skipping previously passed test suites:
ci:test:relevant
ci:test:sf

@liferay-continuous-integration
Copy link
Collaborator

All required test suite(s) passed.
Forwarding pullrequest to brianchandotcom.

@liferay-continuous-integration
Copy link
Collaborator

Pull request has been successfully forwarded to brianchandotcom#97149

@liferay-continuous-integration
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants