[VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy release. Livy enables programmatic, fault-tolerant, multi-tenant submission of Spark jobs from web/mobile apps (no Spark client needed). So, multiple users can interact with your Spark cluster concurrently and reliably. Vote thread: https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E (Note I messed up the subject on the first e-mail, that thread is for the RC2 vote.) Result thread: https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E The RC is based on tag v0.6.0-incubating-rc2: https://github.com/apache/incubator-livy/commit/28be98cabc The release files can be found here: https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ The staged maven artifacts can be found here: https://repository.apache.org/content/repositories/orgapachelivy-1008 The list of resolved JIRAs in this release can be found here: https://issues.apache.org/jira/projects/LIVY/versions/12342736 Vote will be open for at least 72 hours. Thanks! -- Marcelo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
This test is consistently failing when I build, any idea what’s wrong in my setup? - should print unicode correctly *** FAILED *** (101 milliseconds) ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal ExecuteSuccess(JObject(List((text/plain,JString(☺) (PythonInterpreterSpec.scala:272) On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin wrote: > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy release. > > Livy enables programmatic, fault-tolerant, multi-tenant submission of > Spark jobs from web/mobile apps (no Spark client needed). So, multiple > users can interact with your Spark cluster concurrently and reliably. > > Vote thread: > > https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E > > (Note I messed up the subject on the first e-mail, that thread is for > the RC2 vote.) > > Result thread: > > https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E > > The RC is based on tag v0.6.0-incubating-rc2: > https://github.com/apache/incubator-livy/commit/28be98cabc > > The release files can be found here: > https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ > > The staged maven artifacts can be found here: > https://repository.apache.org/content/repositories/orgapachelivy-1008 > > The list of resolved JIRAs in this release can be found here: > https://issues.apache.org/jira/projects/LIVY/versions/12342736 > > Vote will be open for at least 72 hours. Thanks! > > -- > Marcelo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
On Thu, 28 Mar 2019 at 05:25, Felix Cheung wrote: > This test is consistently failing when I build, any idea what’s wrong in my > setup? > > - should print unicode correctly *** FAILED *** (101 milliseconds) > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal > ExecuteSuccess(JObject(List((text/plain,JString(☺) > (PythonInterpreterSpec.scala:272) > > I have seen such errors before; usually it is because the test source file has been incorrectly encoded/decoded at some point. Although they are harder to maintain, it may be worth coding the test files using Unicode escapes rather than the non-ASCII characters. ASCII is much harder to mangle... > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin > > wrote: > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy > release. > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of > > Spark jobs from web/mobile apps (no Spark client needed). So, multiple > > users can interact with your Spark cluster concurrently and reliably. > > > > Vote thread: > > > > > https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E > > > > (Note I messed up the subject on the first e-mail, that thread is for > > the RC2 vote.) > > > > Result thread: > > > > > https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E > > > > The RC is based on tag v0.6.0-incubating-rc2: > > https://github.com/apache/incubator-livy/commit/28be98cabc > > > > The release files can be found here: > > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ > > > > The staged maven artifacts can be found here: > > https://repository.apache.org/content/repositories/orgapachelivy-1008 > > > > The list of resolved JIRAs in this release can be found here: > > https://issues.apache.org/jira/projects/LIVY/versions/12342736 > > > > Vote will be open for at least 72 hours. Thanks! > > > > -- > > Marcelo > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
I see, thanks. Perhaps the way I unzip the src zip file then. Is it a better approach to unpack it? On Thu, Mar 28, 2019 at 2:03 AM sebb wrote: > On Thu, 28 Mar 2019 at 05:25, Felix Cheung wrote: > > > This test is consistently failing when I build, any idea what’s wrong in > my > > setup? > > > > - should print unicode correctly *** FAILED *** (101 milliseconds) > > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal > > ExecuteSuccess(JObject(List((text/plain,JString(☺) > > (PythonInterpreterSpec.scala:272) > > > > > I have seen such errors before; usually it is because the test source file > has been incorrectly encoded/decoded at some point. > Although they are harder to maintain, it may be worth coding the test files > using Unicode escapes rather than the non-ASCII characters. > ASCII is much harder to mangle... > > > > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin > > > > > wrote: > > > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy > > release. > > > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of > > > Spark jobs from web/mobile apps (no Spark client needed). So, multiple > > > users can interact with your Spark cluster concurrently and reliably. > > > > > > Vote thread: > > > > > > > > > https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E > > > > > > (Note I messed up the subject on the first e-mail, that thread is for > > > the RC2 vote.) > > > > > > Result thread: > > > > > > > > > https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E > > > > > > The RC is based on tag v0.6.0-incubating-rc2: > > > https://github.com/apache/incubator-livy/commit/28be98cabc > > > > > > The release files can be found here: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ > > > > > > The staged maven artifacts can be found here: > > > https://repository.apache.org/content/repositories/orgapachelivy-1008 > > > > > > The list of resolved JIRAs in this release can be found here: > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736 > > > > > > Vote will be open for at least 72 hours. Thanks! > > > > > > -- > > > Marcelo > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > >
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
On Thu, 28 Mar 2019 at 15:42, Felix Cheung wrote: > I see, thanks. Perhaps the way I unzip the src zip file then. Is it a > better approach to unpack it? > > Have a look at the test file source to see if it looks OK. > > On Thu, Mar 28, 2019 at 2:03 AM sebb wrote: > > > On Thu, 28 Mar 2019 at 05:25, Felix Cheung > wrote: > > > > > This test is consistently failing when I build, any idea what’s wrong > in > > my > > > setup? > > > > > > - should print unicode correctly *** FAILED *** (101 milliseconds) > > > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal > > > ExecuteSuccess(JObject(List((text/plain,JString(☺) > > > (PythonInterpreterSpec.scala:272) > > > > > > > > I have seen such errors before; usually it is because the test source > file > > has been incorrectly encoded/decoded at some point. > > Although they are harder to maintain, it may be worth coding the test > files > > using Unicode escapes rather than the non-ASCII characters. > > ASCII is much harder to mangle... > > > > > > > > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin > > > > > > > > wrote: > > > > > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy > > > release. > > > > > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of > > > > Spark jobs from web/mobile apps (no Spark client needed). So, > multiple > > > > users can interact with your Spark cluster concurrently and reliably. > > > > > > > > Vote thread: > > > > > > > > > > > > > > https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E > > > > > > > > (Note I messed up the subject on the first e-mail, that thread is for > > > > the RC2 vote.) > > > > > > > > Result thread: > > > > > > > > > > > > > > https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E > > > > > > > > The RC is based on tag v0.6.0-incubating-rc2: > > > > https://github.com/apache/incubator-livy/commit/28be98cabc > > > > > > > > The release files can be found here: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ > > > > > > > > The staged maven artifacts can be found here: > > > > > https://repository.apache.org/content/repositories/orgapachelivy-1008 > > > > > > > > The list of resolved JIRAs in this release can be found here: > > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736 > > > > > > > > Vote will be open for at least 72 hours. Thanks! > > > > > > > > -- > > > > Marcelo > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > >
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
Are you using a different encoding that UTF-8 in your environment? The source file contains unicode escapes, so that shouldn't be the problem. It may be the test is expecting the output of child processes (in this case the python interpreter) to be UTF-8. On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung wrote: > This test is consistently failing when I build, any idea what’s wrong in my > setup? > > - should print unicode correctly *** FAILED *** (101 milliseconds) > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal > ExecuteSuccess(JObject(List((text/plain,JString(☺) > (PythonInterpreterSpec.scala:272) > > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin > > wrote: > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy > release. > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of > > Spark jobs from web/mobile apps (no Spark client needed). So, multiple > > users can interact with your Spark cluster concurrently and reliably. > > > > Vote thread: > > > > > https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E > > > > (Note I messed up the subject on the first e-mail, that thread is for > > the RC2 vote.) > > > > Result thread: > > > > > https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E > > > > The RC is based on tag v0.6.0-incubating-rc2: > > https://github.com/apache/incubator-livy/commit/28be98cabc > > > > The release files can be found here: > > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ > > > > The staged maven artifacts can be found here: > > https://repository.apache.org/content/repositories/orgapachelivy-1008 > > > > The list of resolved JIRAs in this release can be found here: > > https://issues.apache.org/jira/projects/LIVY/versions/12342736 > > > > Vote will be open for at least 72 hours. Thanks! > > > > -- > > Marcelo > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Marcelo
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
Also is that failing when running the Python2 or the Python3 version of that test? Maybe it doesn't work as expected in some newer version of Python3... On Thu, Mar 28, 2019 at 10:02 AM Marcelo Vanzin wrote: > Are you using a different encoding that UTF-8 in your environment? > > The source file contains unicode escapes, so that shouldn't be the > problem. It may be the test is expecting the output of child processes (in > this case the python interpreter) to be UTF-8. > > On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung > wrote: > >> This test is consistently failing when I build, any idea what’s wrong in >> my >> setup? >> >> - should print unicode correctly *** FAILED *** (101 milliseconds) >> ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal >> ExecuteSuccess(JObject(List((text/plain,JString(☺) >> (PythonInterpreterSpec.scala:272) >> >> >> On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin >> >> wrote: >> >> > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy >> release. >> > >> > Livy enables programmatic, fault-tolerant, multi-tenant submission of >> > Spark jobs from web/mobile apps (no Spark client needed). So, multiple >> > users can interact with your Spark cluster concurrently and reliably. >> > >> > Vote thread: >> > >> > >> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E >> > >> > (Note I messed up the subject on the first e-mail, that thread is for >> > the RC2 vote.) >> > >> > Result thread: >> > >> > >> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E >> > >> > The RC is based on tag v0.6.0-incubating-rc2: >> > https://github.com/apache/incubator-livy/commit/28be98cabc >> > >> > The release files can be found here: >> > >> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ >> > >> > The staged maven artifacts can be found here: >> > https://repository.apache.org/content/repositories/orgapachelivy-1008 >> > >> > The list of resolved JIRAs in this release can be found here: >> > https://issues.apache.org/jira/projects/LIVY/versions/12342736 >> > >> > Vote will be open for at least 72 hours. Thanks! >> > >> > -- >> > Marcelo >> > >> > - >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > For additional commands, e-mail: general-h...@incubator.apache.org >> > >> > >> > > > -- > Marcelo > -- Marcelo
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
On Thu, 28 Mar 2019 at 17:02, Marcelo Vanzin wrote: > Are you using a different encoding that UTF-8 in your environment? > > The source file contains unicode escapes, so that shouldn't be the problem. > It may be the test is expecting the output of child processes (in this case > the python interpreter) to be UTF-8. > > If that is the case, then the test case ought to be fixed... > On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung > wrote: > > > This test is consistently failing when I build, any idea what’s wrong in > my > > setup? > > > > - should print unicode correctly *** FAILED *** (101 milliseconds) > > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal > > ExecuteSuccess(JObject(List((text/plain,JString(☺) > > (PythonInterpreterSpec.scala:272) > > > > > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin > > > > > wrote: > > > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy > > release. > > > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of > > > Spark jobs from web/mobile apps (no Spark client needed). So, multiple > > > users can interact with your Spark cluster concurrently and reliably. > > > > > > Vote thread: > > > > > > > > > https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E > > > > > > (Note I messed up the subject on the first e-mail, that thread is for > > > the RC2 vote.) > > > > > > Result thread: > > > > > > > > > https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E > > > > > > The RC is based on tag v0.6.0-incubating-rc2: > > > https://github.com/apache/incubator-livy/commit/28be98cabc > > > > > > The release files can be found here: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ > > > > > > The staged maven artifacts can be found here: > > > https://repository.apache.org/content/repositories/orgapachelivy-1008 > > > > > > The list of resolved JIRAs in this release can be found here: > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736 > > > > > > Vote will be open for at least 72 hours. Thanks! > > > > > > -- > > > Marcelo > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > -- > Marcelo >
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
I can reproduce it with this: LC_ALL=en_US.ASCII mvn -Pspark-2.4 -Pthriftserver test -pl :livy-repl_2.11 -Dsuites=*.Python2* Seems that Livy's fake python shell expects UTF-8 when running on Python 2. This is not a new bug, so while we should fix it, not sure we need to fix it in this release. On Thu, Mar 28, 2019 at 11:24 AM sebb wrote: > On Thu, 28 Mar 2019 at 17:02, Marcelo Vanzin > wrote: > > > Are you using a different encoding that UTF-8 in your environment? > > > > The source file contains unicode escapes, so that shouldn't be the > problem. > > It may be the test is expecting the output of child processes (in this > case > > the python interpreter) to be UTF-8. > > > > > If that is the case, then the test case ought to be fixed... > > > > On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung > > wrote: > > > > > This test is consistently failing when I build, any idea what’s wrong > in > > my > > > setup? > > > > > > - should print unicode correctly *** FAILED *** (101 milliseconds) > > > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal > > > ExecuteSuccess(JObject(List((text/plain,JString(☺) > > > (PythonInterpreterSpec.scala:272) > > > > > > > > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin > > > > > > > > wrote: > > > > > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy > > > release. > > > > > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of > > > > Spark jobs from web/mobile apps (no Spark client needed). So, > multiple > > > > users can interact with your Spark cluster concurrently and reliably. > > > > > > > > Vote thread: > > > > > > > > > > > > > > https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E > > > > > > > > (Note I messed up the subject on the first e-mail, that thread is for > > > > the RC2 vote.) > > > > > > > > Result thread: > > > > > > > > > > > > > > https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E > > > > > > > > The RC is based on tag v0.6.0-incubating-rc2: > > > > https://github.com/apache/incubator-livy/commit/28be98cabc > > > > > > > > The release files can be found here: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ > > > > > > > > The staged maven artifacts can be found here: > > > > > https://repository.apache.org/content/repositories/orgapachelivy-1008 > > > > > > > > The list of resolved JIRAs in this release can be found here: > > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736 > > > > > > > > Vote will be open for at least 72 hours. Thanks! > > > > > > > > -- > > > > Marcelo > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > -- > > Marcelo > > > -- Marcelo
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
I have LANG=“en_US.UTF-8”
I tried a couple of things finally it passed when I use virtualenv - my
python is Python 3, forcing that to Python 2 passed the test. However, now
another test failed (maybe connection blocked by firewall?)
=== FAILURES
===
test_create_new_session_without_default_config
def test_create_new_session_without_default_config():
> mock_and_validate_create_new_session(False)
src/test/python/livy-tests/client_test.py:105:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _
:3: in wrapper
???
src/test/python/livy-tests/client_test.py:48: in
mock_and_validate_create_new_session
load_defaults=defaults)
src/main/python/livy/client.py:88: in __init__
session_conf_dict).json()['id']
src/main/python/livy/client.py:388: in _create_new_session
headers=self._conn._JSON_HEADERS, data=data)
src/main/python/livy/client.py:500: in send_request
json=data, auth=self._spnego_auth())
.eggs/requests-2.21.0-py2.7.egg/requests/api.py:60: in request
return session.request(method=method, url=url, **kwargs)
.eggs/requests-2.21.0-py2.7.egg/requests/sessions.py:533: in request
resp = self.send(prep, **send_kwargs)
.eggs/requests-2.21.0-py2.7.egg/requests/sessions.py:646: in send
r = adapter.send(request, **kwargs)
.eggs/responses-0.10.6-py2.7.egg/responses.py:626: in unbound_on_send
return self._on_request(adapter, request, *a, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _
self =
adapter =
request =
kwargs = {'cert': None, 'proxies': OrderedDict(), 'stream': False,
'timeout': 10, ...}
match = None, resp_callback = None
error_msg = "Connection refused by Responses: POST
http://machine:8998/sessions/ doesn't match Responses Mock"
response = ConnectionError(u"Connection refused by Responses: POST
http://machine:8998/sessions/doesn't match Responses Mock",)
On Thu, Mar 28, 2019 at 11:52 AM Marcelo Vanzin
wrote:
> I can reproduce it with this:
>
> LC_ALL=en_US.ASCII mvn -Pspark-2.4 -Pthriftserver test -pl :livy-repl_2.11
> -Dsuites=*.Python2*
>
> Seems that Livy's fake python shell expects UTF-8 when running on Python 2.
> This is not a new bug, so while we should fix it, not sure we need to fix
> it in this release.
>
>
> On Thu, Mar 28, 2019 at 11:24 AM sebb wrote:
>
> > On Thu, 28 Mar 2019 at 17:02, Marcelo Vanzin >
> > wrote:
> >
> > > Are you using a different encoding that UTF-8 in your environment?
> > >
> > > The source file contains unicode escapes, so that shouldn't be the
> > problem.
> > > It may be the test is expecting the output of child processes (in this
> > case
> > > the python interpreter) to be UTF-8.
> > >
> > >
> > If that is the case, then the test case ought to be fixed...
> >
> >
> > > On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung
> > > wrote:
> > >
> > > > This test is consistently failing when I build, any idea what’s wrong
> > in
> > > my
> > > > setup?
> > > >
> > > > - should print unicode correctly *** FAILED *** (101 milliseconds)
> > > > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not
> equal
> > > > ExecuteSuccess(JObject(List((text/plain,JString(☺)
> > > > (PythonInterpreterSpec.scala:272)
> > > >
> > > >
> > > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin
> > > > > > >
> > > > wrote:
> > > >
> > > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
> > > > release.
> > > > >
> > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission
> of
> > > > > Spark jobs from web/mobile apps (no Spark client needed). So,
> > multiple
> > > > > users can interact with your Spark cluster concurrently and
> reliably.
> > > > >
> > > > > Vote thread:
> > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
> > > > >
> > > > > (Note I messed up the subject on the first e-mail, that thread is
> for
> > > > > the RC2 vote.)
> > > > >
> > > > > Result thread:
> > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
> > > > >
> > > > > The RC is based on tag v0.6.0-incubating-rc2:
> > > > > https://github.com/apache/incubator-livy/commit/28be98cabc
> > > > >
> > > > > The release files can be found here:
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
> > > > >
> > > > > The staged maven artifacts can be found here:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachelivy-1008
> > > > >
> > > > > The list of resolved JIRAs in this release can be found here:
> > > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736
> > > > >
> > > > > Vote will be open for at least 72 hours. Thanks!
> > > > >
> > > > > --
> > > > > Marcelo
> > > > >
> > > > >
> --
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
On Thu, Mar 28, 2019 at 3:57 PM Felix Cheung wrote: > I have LANG=“en_US.UTF-8” > I tried a couple of things finally it passed when I use virtualenv - my > python is Python 3, forcing that to Python 2 passed the test. Hmmm, that tells me that the python 3 path in the fake shell might not be as unicode-safe as it seems, and that this test should also be running against python 3... As a separate issue, things could be enhanced so that they force use of "python2" when running the python 2 tests. But in the spirit of "these are not regressions, just bugs", I'd rather not block the release for that. (I filed a but for the ASCII thing already, I'll file others for the above.) > However, now > another test failed (maybe connection blocked by firewall?) > That seems likely, if you have a local firewall? (8998 is Livy's default port. Or maybe you have something running on that port and the tests should be trying an ephemeral one...) > error_msg = "Connection refused by Responses: POST > http://machine:8998/sessions/ doesn't match Responses Mock" > response = ConnectionError(u"Connection refused by Responses: POST > http://machine:8998/sessions/doesn't match Responses Mock",) > -- Marcelo
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
Hi, +1 (binding) Released software can have bugs and failing tests, the only requirement from an ASF release point of view is that it can compile. Of course teh project may decided not to release it if the bug is serious. I checked: - incubating in name - signatures and hashes correct - DISCLAIMER exists - LICENSE good, but missing the license for the glyphicons halflings font [1] (and a few other files) - NOTICE needs year updating - No unpacked binary files - All source files have ASF headers - Can compile from source Thanks, Justin 1. apache-livy-0.6.0-incubating/docs/assets/themes/apache/bootstrap/fonts/glyphicons-halflings-regular.svg - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
+1 (binding) And thanks Marcelo for resolving the issues raised on rc1. On Fri, Mar 29, 2019 at 19:13 Justin Mclean wrote: > Hi, > > +1 (binding) > > Released software can have bugs and failing tests, the only requirement > from an ASF release point of view is that it can compile. Of course teh > project may decided not to release it if the bug is serious. > > I checked: > - incubating in name > - signatures and hashes correct > - DISCLAIMER exists > - LICENSE good, but missing the license for the glyphicons halflings font > [1] (and a few other files) > - NOTICE needs year updating > - No unpacked binary files > - All source files have ASF headers > - Can compile from source > > Thanks, > Justin > > 1. > apache-livy-0.6.0-incubating/docs/assets/themes/apache/bootstrap/fonts/glyphicons-halflings-regular.svg > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sent from my Mobile device
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
I’m happy to give +1 (binding) But definitely ran into more problems with this and more time than I anticipated. checked: - name includes incubating - DISCLAIMER exists Signature and hashes - LICENSE and NOTICE all good Copyright year, url to and copy full text for license - No unexpected binary files (except below) - All source files have ASF headers - Can compile form source (with issues) I switched to another environment, found out I needed to manually pip install configparser just to build (skipTest) And then without skipTest it failed even earlier on rsc tests Running org.apache.livy.rsc.TestSparkClient Tests run: 19, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 30.948 sec <<< FAILURE! - in org.apache.livy.rsc.TestSparkClient testJobSubmission(org.apache.livy.rsc.TestSparkClient) Time elapsed: 0.486 sec <<< FAILURE! org.mockito.exceptions.verification.WantedButNotInvoked: Wanted but not invoked: listener.onJobStarted( org.apache.livy.rsc.JobHandleImpl@75805562 ); -> at org.apache.livy.rsc.TestSparkClient$1.call(TestSparkClient.java:101) And then the earlier python2 utf-8 issue. Quite a number of binary resources in the src release, ttf, svg etc also this looks like standard bootstrap script, does it have to be in the src release (vs to include in binary release)? docs/assets/themes/apache/bootstrap/css/bootstrap.css if that's doc only there's another copy similarly at server/src/main/resources/org/apache/livy/server/ui/static/css/bootstrap.min.css On Thu, Mar 28, 2019 at 4:05 PM Marcelo Vanzin wrote: > On Thu, Mar 28, 2019 at 3:57 PM Felix Cheung > wrote: > > > I have LANG=“en_US.UTF-8” > > I tried a couple of things finally it passed when I use virtualenv - my > > python is Python 3, forcing that to Python 2 passed the test. > > > Hmmm, that tells me that the python 3 path in the fake shell might not be > as unicode-safe as it seems, and that this test should also be running > against python 3... > > As a separate issue, things could be enhanced so that they force use of > "python2" when running the python 2 tests. > > But in the spirit of "these are not regressions, just bugs", I'd rather not > block the release for that. (I filed a but for the ASCII thing already, > I'll file others for the above.) > > > > However, now > > another test failed (maybe connection blocked by firewall?) > > > > That seems likely, if you have a local firewall? (8998 is Livy's default > port. Or maybe you have something running on that port and the tests should > be trying an ephemeral one...) > > > > error_msg = "Connection refused by Responses: POST > > http://machine:8998/sessions/ doesn't match Responses Mock" > > response = ConnectionError(u"Connection refused by Responses: POST > > http://machine:8998/sessions/doesn't match Responses Mock",) > > > > > -- > Marcelo >
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
On Fri, Mar 29, 2019 at 10:41 PM Felix Cheung wrote: > I switched to another environment, found out I needed to manually pip > install configparser just to build (skipTest) There are probably things that could be better documented. Or maybe could be handled better by the build scripts. But these should be reported to the project (on jira), since it seems clear that those working on the project are not running into these problems or have long forgotten about it (after they fixed their local builds). > And then without skipTest it failed even earlier on rsc tests Yes there are a few known flaky tests. > Quite a number of binary resources in the src release, ttf, svg etc > also this looks like standard bootstrap script, does it have to be in the > src release (vs to include in binary release)? > docs/assets/themes/apache/bootstrap/css/bootstrap.css This is the way I've seen most ASF projects handling these kinds of artifacts. e.g. I see multiple copies of bootstrap in the Hadoop repo. Same in Spark. And you can't get rid of all binaries in a source release... e.g. images and fonts. Fonts could come from 3rd party places and downloaded when building the sources, but is that worth the extra cost (everyone downloading this thing from the net all the time)? Is there any maven plugin or something like that for aiding with this sort of thing? Images will in many cases be project-specific. Not saying that the current state is optimal but you're not really providing an alternative here. -- Marcelo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2
Hi - > On Apr 1, 2019, at 10:54 AM, Marcelo Vanzin > wrote: > > On Fri, Mar 29, 2019 at 10:41 PM Felix Cheung wrote: >> I switched to another environment, found out I needed to manually pip >> install configparser just to build (skipTest) > > There are probably things that could be better documented. Or maybe > could be handled better by the build scripts. But these should be > reported to the project (on jira), since it seems clear that those > working on the project are not running into these problems or have > long forgotten about it (after they fixed their local builds). This is a very common situation with complex builds. Just try to build OpenOffice ;-) > >> And then without skipTest it failed even earlier on rsc tests > > Yes there are a few known flaky tests. > >> Quite a number of binary resources in the src release, ttf, svg etc >> also this looks like standard bootstrap script, does it have to be in the >> src release (vs to include in binary release)? >> docs/assets/themes/apache/bootstrap/css/bootstrap.css > > This is the way I've seen most ASF projects handling these kinds of > artifacts. e.g. I see multiple copies of bootstrap in the Hadoop repo. > Same in Spark. > > And you can't get rid of all binaries in a source release... e.g. > images and fonts. Fonts could come from 3rd party places and > downloaded when building the sources, but is that worth the extra cost > (everyone downloading this thing from the net all the time)? Is there > any maven plugin or something like that for aiding with this sort of > thing? > > Images will in many cases be project-specific. > > Not saying that the current state is optimal but you're not really > providing an alternative here. Images (png, jpg, .ico, etc.) and similar types of binary only resources have long been acceptable although I cannot find a resource about this at the moment as the legal affairs committee is reorganizing documentation. BTW - SVG like CSS is textual language. Minified Javascript should not be in the source …. Any included binaries should consider the license for inclusion just like included source code. And NO compiled source although a testing jar can be rationalized. And of course these can be documented in rat-excludes and other locations. Questions should go to legal-discuss@a.o Regards, Dave > > -- > Marcelo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
