GitLab

Change-Id: Ib6228b90ebf99c56ef8500968d61bdd60ab78324

* Implement stats collection for builds

Change-Id: If2ef82e55747522633fe2a3c458445f99332d7ac

* Load built-in templates via the repo parameter

Change-Id: I62265b3a60ecf7b651d9a22a32775e5d7434d5e5

We run 9-15 buildservers simultaneously and have a status page that
reports the /buildserver/vars foreach server. However it is hard to know
which status is for which buildserver. So we add the buildserver
hostname here.

Change-Id: I46fc59626cccf668ab57a5f81581273f0358fd1e

Change-Id: I5d7de7966f27b5ae64ea38662daa00ea12ab519e

Change-Id: I3f186175afcb254bc9a329c2a0f445fc0e42b48a

This commit is a further address to the issue #1518

Currently when the selected language is not English in login page, when login failed (e.g the password is incorrect), the login page will return with an English Page.
The commit fix this problem by adding an additional locale parameter to fail method in LoginServlet.java

Chrome 89 implements RFC8285 by default. It implements a general
mechanism for RTP header extensions. We do not use these....

Unfortunately the WebRTC library we are using in the Companion does not
understand the extension request in the WebRTC offer message and refuses
the offer completely, resulting in WebRTC not working from Chrome
89 (and presumably onward).

This change removes the extension from the offer prior to sending it to
the Companion, so WebRTC works again.

We believe this is harmless, because we do not use audio or video over
WebRTC and this extension has no impact on the data channel (which we do
use).

Change-Id: I68f4ebaa2099ca0b4bbc7b1abd0a565dbde1f4e6

Change-Id: I5338ee15a316828495e3782491a90785b46cdb1b

Change-Id: I931be1eb40f800d168aeb3b110f9a872b4e0385f

Change-Id: I11033332060ba9f9dee29fc41dd661a1e48f7081

Add two boolean fields. The “monall” field (in production for a while)
permits the monitoring of all key changes. This is used for statistics
gathering and research.

The “privileged” flag permits commands that manage the overall server. At
the moment the only such command is one to manually close specified
client connections.

Note: MIT App Inventor itself does not make use of these flags, but the
MIT App Inventor source tree is the canonical authoritative location for
the token format definition.

Change-Id: If7cd4ae7cf2fd49718607aeac51d8a56f76df877

Change-Id: I305dca87f36e6d6659a3586cb9b3b014bbcafa89

* Correct order of blocks affecting global variable references
* Fix renaming of global variables when keyword translated

Change-Id: Ic74aa9b4800d44a11ab1b5ddf7403d110aacf750

* Fix Chinese and Brazilian Portuguese translation loading
* Fix references to compiled messages in unit tests

Change-Id: Ib67aff12abc3538d0e5053d9d680d934f382abb5

When set we do not display the “Send to Gallery” Button, only the “Login
to Gallery” button. The Gallery itself enforces read only status, so if
the button is enabled but the gallery is in read only (for this
instance) then the user will receive an error when they attempt to send
a project to the gallery. But it is better if we can just avoid the
issue by not providing the button in the first place.

Another implementation here could be to have the server side actually
check in with the gallery itself to determine read-only status, but for
now we provide it as a config flag so we do not have to work out the
details of how and when the server would communicate with the Gallery as
well as how to handle errors and time-outs etc.

Change-Id: Ib6ca63ab2ca63636d7451762f782050dbffd9b3c