mirror of
https://github.com/eclipse-sailing-analytics/sailing-analytics.git
synced 2026-09-19 04:05:36 +00:00
Merge branch 'master' into bug5905
This commit is contained in:
+1
-1
@@ -80,7 +80,7 @@ public class DiscardThresholdBoxes {
|
||||
private Widget createDiscardThresholdBoxesPanel(StringMessages stringMessages) {
|
||||
assert discardThresholdBoxes != null && discardThresholdBoxes.length == MAX_NUMBER_OF_DISCARDED_RESULTS;
|
||||
final VerticalPanel vp = new VerticalPanel();
|
||||
vp.add(new Label(stringMessages.discardRacesFromHowManyStartedRacesOn()));
|
||||
vp.add(new Label(stringMessages.applyDiscardsBasedOnNumberOfScoredRaces(MAX_NUMBER_OF_DISCARDED_RESULTS)));
|
||||
final Grid grid = new Grid(0, 2*NUMBER_OF_BOXES_PER_LINE);
|
||||
grid.setCellSpacing(3);
|
||||
vp.add(grid);
|
||||
|
||||
+1
@@ -63,6 +63,7 @@ public interface StringMessages extends com.sap.sse.gwt.client.StringMessages,
|
||||
String pleaseEnterAName();
|
||||
String pleaseEnterABoatClass();
|
||||
String discardRacesFromHowManyStartedRacesOn();
|
||||
String applyDiscardsBasedOnNumberOfScoredRaces(int maxNumberOfDiscardedResults);
|
||||
String leaderboardWithThisNameAlreadyExists();
|
||||
String discardThresholdsMustBeNumeric();
|
||||
String discardThresholdsMustBeAscending();
|
||||
|
||||
+3
-2
@@ -52,7 +52,8 @@ unlink=Unlink
|
||||
leaderboardName=Leaderboard Name
|
||||
pleaseEnterAName=Please enter a name
|
||||
pleaseEnterABoatClass=Please enter a boat class
|
||||
discardRacesFromHowManyStartedRacesOn=Discard one more race starting with how many started races
|
||||
discardRacesFromHowManyStartedRacesOn=Discard one or more races, starting with how many started races there are
|
||||
applyDiscardsBasedOnNumberOfScoredRaces=Configure discards. Enter into box X, the number of scored races required to apply the Xth discard. Maximum discards: {0}.
|
||||
leaderboardWithThisNameAlreadyExists=Leaderboard with this name already exists
|
||||
discardThresholdsMustBeNumeric=Discard thresholds must be numeric
|
||||
discardThresholdsMustBeAscending=Discard thresholds must be ascending
|
||||
@@ -2474,4 +2475,4 @@ errorSettingUserPreference=Error setting user preference with key "{0}": {1}
|
||||
scoringSchemeLowPointWithEliminatingMedalSeriesPromotingOneToFinalAndTwoToSemifinal=Low point system; Medal races as quarter final, semi final and grand final
|
||||
scoringSchemeLowPointWithEliminatingMedalSeriesPromotingOneToFinalAndTwoToSemifinalDescription=Low point system; the best-ranked competitor of the opening series advances directly to the grand final; the second and third ranking competitors are promoted directly to the semi final.
|
||||
incrementalScoreCorrectionInPoints=Incremental score correction (points)
|
||||
errorObtainingCourseAreasForLeaderboard=Error obtaining course areas for leaderboard {0}: {1}
|
||||
errorObtainingCourseAreasForLeaderboard=Error obtaining course areas for leaderboard {0}: {1}
|
||||
|
||||
+1
@@ -53,6 +53,7 @@ leaderboardName=Name der Rangliste
|
||||
pleaseEnterAName=Bitte geben Sie einen Namen ein.
|
||||
pleaseEnterABoatClass=Bitte geben Sie eine Bootsklasse ein.
|
||||
discardRacesFromHowManyStartedRacesOn=Discard one more race starting with how many started races
|
||||
applyDiscardsBasedOnNumberOfScoredRaces=Streicher konfigurieren: in Feld X die Anzahl gewerteter Wettfahrten eingeben, ab welcher der X-te Streicher angewendet werden soll. Maximal {0} Streicher.
|
||||
leaderboardWithThisNameAlreadyExists=Eine Rangliste mit diesem Namen existiert bereits.
|
||||
discardThresholdsMustBeNumeric=Discard thresholds must be numeric
|
||||
discardThresholdsMustBeAscending=Discard thresholds must be ascending
|
||||
|
||||
@@ -33,6 +33,7 @@ To start SDM debugging in Eclipse, do the following:
|
||||
* Start the backend as you would always do.
|
||||
* Start GWT Super Dev Mode by launching "SailingGWT sdm.launch" or "SailingGWT All SDM.launch".
|
||||
* Do not Click on the URLs provided in "Development view"!
|
||||
* Make sure that in the Debug Configuration chrome is the first browser used and not chromium.
|
||||
* Run "Debug SailingGWT SDM on Chrome.launch"
|
||||
* A new instance of Chrome is started and you will see a debug session running in Eclipse
|
||||
* Your Eclipse break points will now work in the running debug session.
|
||||
@@ -55,6 +56,7 @@ Be aware that some of the Eclipse debugger features do NOT work with this kind o
|
||||
* Variable naming is not 1:1 what you expect in the Java world
|
||||
* Stacks look different but clicking on Stack elements should
|
||||
* [[Stack Traces logged in Chrome do not use source maps|https://code.google.com/p/chromium/issues/detail?id=357958]], so you see the JavaScript Stack Trace instead.
|
||||
If you wish to debug in a different language, go to the `.gwt.xml file`, for the given page, and add `<extend-property name="locale" values="en,de" />`. Next, run the setup, the same way you would to use the debugger. After launching in Chrome, add the following after the .html: `?locale=de`
|
||||
|
||||
## Debugging SDM on Android devices
|
||||
|
||||
|
||||
@@ -247,3 +247,11 @@ Install the GWT Browser Plugin for the GWT Development mode. As of 2016-08-31 Fi
|
||||
### Create Hudson Job
|
||||
If you want a hudson job to run when you push your branch then you can run a script in `configuration` called . Run options for a branch titled `createHudsonJobForBug.sh`. For you bug branch titled `bug<bug number>`, create a build job, which will create a release, by running the script like so: `./createHudsonJobForBug.sh <bug number>`.
|
||||
If on Windows, you may need to disable any web shields in antivirus software, to allow `curl` to function.
|
||||
|
||||
###Issues when playing around with AWS
|
||||
- The problem: **aws cli (used for aws ec2 describe-tags) hangs in eu-west-2** in all AZs on new instances I created, using a target group which permitted all outbound connections and inbound https, http and ssh connections. I tried permitting everything but that didn’t work. When I attached (at Axel’s suggestion) the Java Application with Reverse Proxy security group, it worked but — even if I duplicated this security group, and applied that copy instead — it still didn’t work.
|
||||
Curl issue solution: it turns out that the network interface only permits certain outbound and inbounds from certain target groups.
|
||||
The path to the solution: On my instance in eu-west-2a, I ran aws --debug ec2 describe-tags (you may need to do aws configure first). This is much akin to verbose mode of other unix commands. I noticed it hang on a request to ec2.eu-west-2.amazonaws.com. If you do `dig -t any ec2.eu-west-2.amazonaws.com` you see 3 ip addresses, which — as you will see later — are IPs in each of the eu-west-2 availability zones. When I ran curl -v ec2.eu-west-2.amazonaws.com (the v flag is verbose), one of the IPs from dig was used (namely the one in eu-west-2a, where the instance resides) and it hangs. I then went to endpoints for the VPC and noticed a service for the service `com.amazonaws.eu-west-2.ec2`. It had the default security group, which turned out to only allow inbound rules from the default or Java Application with Reverse Proxy target group.
|
||||
- Problem: A load balancer's target group health checks fail. I was told the checks failed with 403 errors.
|
||||
Solution: This was occurring because the website didn't have any content in the /var/www/html. Whilst a site was still served (namely the Apache test page) it does throw a 403 error. If you fill the directory with and index.html the test then passes and a 200 code is returned
|
||||
|
||||
|
||||
Reference in New Issue
Block a user