You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The readme was updated to 3.1.2, but the release did not succeed via Actions.
Thanks for letting me know, the GitHub action currently gets an exception
status: 422 Unprocessable Entity
at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed (ArtifactTransportListener.java:52)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run (BasicRepositoryConnector.java:369)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector.put (BasicRepositoryConnector.java:288)
The same occurs locally on my machine and I have not yet found a workaround.
Can you build from sources?
@johspaeth When will 3.1.2 be released? I can't currently use the flow-sensitive static field strategy because it is broken in 3.1.1 (fixed in this commit). I'm also having an issue with the PathTrackingBoomerang taking a really long time for certain cases, even for really simple programs, but I'm not sure if 3.1.2 will fix that.
@tiganov
Unfortunately, I couldn't yet work out the issue above neither locally nor via GitHub Actions. Can't give an estimate on when this is fixed. Working with a local build - even if sub-optimal - doesn't work for you?
I'm also having an issue with the PathTrackingBoomerang taking a really long time for certain cases, even for really simple programs, but I'm not sure if 3.1.2 will fix that.
Do you have a minimal (Java) program for reproducing the case? No changes have been made in 3.1.2 regarding PathTrackingBoomerang.
Working with a local build - even if sub-optimal - doesn't work for you?
I could pull a local build into SWAN, but I wouldn't want to push any code that depends on that.
Do you have a minimal (Java) program for reproducing the case?
I've modified boomerangPDS/src/main/java/boomerang/example/ExampleMain1.java and boomerangPDS/src/main/java/boomerang/example/BoomerangExampleTarget1.java (at the end of this post).
If I remove one of the sink(sunk: strings[0]);, then execution is quick. Otherwise, I'm not sure if it ever finishes executing. It seems that the DataFlowPathWeights (not edges) grow bigger and bigger. The call PDS stack gets very deep with many addWeightForTransitions and onOutTransitionAdded calls.
However, that example is a bit misleading because the actual Swift Intermediate Language (SIL) code will look different. I've tried to recreate its semantics with this Java example (modified BoomerangExampleTarget1.java). Just like in the Swift example, if I remove one of the StringPointer/getter/sink blocks, it will execute quickly.
That's right. I've tried it with 1,2,3,4, and 5 blocks, and more than 3 will cause a timeout but 3 or less will swiftly execute. The difference between 1 and 3 is still noticeable.
Activity
johspaeth commentedon Jun 6, 2021
Thanks for letting me know, the GitHub action currently gets an exception
The same occurs locally on my machine and I have not yet found a workaround.
Can you build from sources?
tiganov commentedon Jun 6, 2021
Yes, I think I can build from sources (if I clone the repo and run
mvn clean install -DskipTests).tiganov commentedon Jul 7, 2021
@johspaeth When will 3.1.2 be released? I can't currently use the flow-sensitive static field strategy because it is broken in 3.1.1 (fixed in this commit). I'm also having an issue with the PathTrackingBoomerang taking a really long time for certain cases, even for really simple programs, but I'm not sure if 3.1.2 will fix that.
johspaeth commentedon Jul 17, 2021
@tiganov
Unfortunately, I couldn't yet work out the issue above neither locally nor via GitHub Actions. Can't give an estimate on when this is fixed. Working with a local build - even if sub-optimal - doesn't work for you?
Do you have a minimal (Java) program for reproducing the case? No changes have been made in 3.1.2 regarding PathTrackingBoomerang.
tiganov commentedon Jul 19, 2021
I could pull a local build into SWAN, but I wouldn't want to push any code that depends on that.
I've modified
boomerangPDS/src/main/java/boomerang/example/ExampleMain1.javaandboomerangPDS/src/main/java/boomerang/example/BoomerangExampleTarget1.java(at the end of this post).My Java example comes from this Swift example.
I use a forward query on the result of
source().If I remove one of the
sink(sunk: strings[0]);, then execution is quick. Otherwise, I'm not sure if it ever finishes executing. It seems that theDataFlowPathWeights(not edges) grow bigger and bigger. The call PDS stack gets very deep with manyaddWeightForTransitionsandonOutTransitionAddedcalls.However, that example is a bit misleading because the actual Swift Intermediate Language (SIL) code will look different. I've tried to recreate its semantics with this Java example (modified
BoomerangExampleTarget1.java). Just like in the Swift example, if I remove one of the StringPointer/getter/sink blocks, it will execute quickly.I've also changed
createAnalysisTransformer()inExampleMain1.java.johspaeth commentedon Jul 19, 2021
Thanks for the code for reproducing, that's an interesting case.
I.e. the timeout only occurs when we have more than 3 blocks of
?
If we only have 1,2 or 3 such blocks, the analysis terminates quickly? I cannot yet see a logical explanation for that behavior.
tiganov commentedon Jul 19, 2021
That's right. I've tried it with 1,2,3,4, and 5 blocks, and more than 3 will cause a timeout but 3 or less will swiftly execute. The difference between 1 and 3 is still noticeable.