av9ash/GitBugs huggingface dataset:
Bug: CVE-2020-17516 mitigation in 2.2.x branch
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 17/Feb/21 15:49
Resolved: 15/Sep/21 07:11

As a Cassandra 2.2.x user
I would like to know if a fix is planned for CVE-2020-17516 in this branch

https://mail-archives.apache.org/mod_mbox/cassandra-user/202102.mbox/%3c6E4340A5-D7BE-4D33-9EC5-3B505A626D8D@apache.org%3e
{quote}CVE-2020-17516: Apache Cassandra doesn't enforce encryption setting on inbound internode connections

Severity:
Important

Vendor:
The Apache Software Foundation

Versions Affected:
Cassandra 2.1.0 to 2.1.22
Cassandra 2.2.0 to 2.2.19
Cassandra 3.0.0 to 3.0.23
Cassandra 3.11.0 to 3.11.9
....
....
....

Mitigation:
Users of ALL versions should switch from ‘dc’ or ‘rack’ to ‘all’ internode_encryption
setting, as they are inherently insecure
3.0.x users should additionally upgrade to 3.0.24
3.11.x users should additionally upgrade to 3.11.24
{quote}

I can't find any ticket tracking implementing this fix in 2.2.x or 2.1.x.
Bug: Upgrade to Jackson Databind 2.9.10.8 or later fix high vulnerabilities 
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 19/Feb/21 19:51
Resolved: 04/Mar/21 14:16

There are 22 high CVEs


CVE ID | Severity | Packages | Source Package | Fixed Package Version
-- | -- | -- | -- | --
CVE-2020-24750 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.6
CVE-2020-24616 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.6
CVE-2020-14195 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.5
CVE-2020-14062 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.5
CVE-2020-14061 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.5
CVE-2020-14060 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.5
CVE-2020-35491 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-35490 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-35728 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2021-20190 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.7
CVE-2020-25649 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.10.5.1, 2.9.10.7, 2.6.7.4
CVE-2020-36187 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36188 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36189 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36186 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36185 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36183 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36184 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36182 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36179 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36180 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
CVE-2020-36181 | high | com.fasterxml.jackson.core_jackson-databind | 2.9.10.4 | fixed in 2.9.10.8
Bug:  bin/cqlsh writes unwanted output to stderr while validating python version if python 2.6 is installed as system python
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 24/Mar/21 17:48
Resolved: 24/Mar/21 17:54

The cqlsh.py script requires Python >= 2.7 on Cassandra 4.0 and checks to make sure it’s a supported version, looking for alternate python versions if the default is 2.6.  Unfortunately the check writes output to stderr that may confuse some users/tools consuming it.

{code}
python -c 'import os; print('\''{}.{}'\''.format(os.sys.version_info.major, os.sys.version_info.minor))'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: 'tuple' object has no attribute 'major'
{code}


The output adds no value and can be suppressed  by redirecting to /dev/null
Bug: Fix flaky LongSharedExecutorPoolTest.testPromptnessOfExecution
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 12/Jan/21 23:25
Resolved: 11/Mar/21 16:47

https://ci-cassandra.apache.org//job/Cassandra-trunk/226//testReport/junit/org.apache.cassandra.concurrent/LongSharedExecutorPoolTest/testPromptnessOfExecution_2/

Currently reporting "Failed 56 times in the last 90 runs. Flakiness: 43%, Stability: 37%"
Bug: cassandra-stress fails when node with port specified
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 19/Mar/21 17:06
Resolved: 19/Mar/21 20:28

When running {{cassandra-stress .... -node 127.0.0.1:53439}}

{noformat}
java.lang.RuntimeException: java.lang.IllegalArgumentException: Failed to add contact point: 127.0.0.1:53439
	at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:146)
	at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:114)
	at org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:66)
	at org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:154)
	at org.apache.cassandra.stress.StressAction.run(StressAction.java:56)
	at org.apache.cassandra.stress.Stress.run(Stress.java:155)
	at org.apache.cassandra.stress.Stress.main(Stress.java:63)
Caused by: java.lang.IllegalArgumentException: Failed to add contact point: 127.0.0.1:53439
	at com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:943)
	at org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:134)
	at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:137)
	... 6 more
Caused by: java.net.UnknownHostException: 127.0.0.1:53439: invalid IPv6 address
	at java.net.InetAddress.getAllByName(InetAddress.java:1170)
	at java.net.InetAddress.getAllByName(InetAddress.java:1127)
	at com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:939)
	... 8 more
{noformat}

It may work using {{-port native=53439}}, but that would not be suitable for {{-node ... whitelist}} when nodes are on different ports.

I'm not sure if {{host:port}} ever worked here, but {{ccm}} [seems to think it should|https://github.com/riptano/ccm/blob/6a519280e1775fe8777f93310b93b3ccb1ffd976/ccmlib/cluster.py#L645], and it's handled [elsewhere|https://github.com/apache/cassandra/blob/c591978f4d265e42d0132418005ba63a99278c75/tools/stress/src/org/apache/cassandra/stress/settings/SettingsNode.java#L102] in the tool.
Bug: Prioritisation for sized-tier and TW compactions is based on outdated estimation
Status: In Progress
Priority: Normal
Created: 30/Mar/21 12:42

Due to the way getEstimatedRemainingTasks() works, it looks that compactions prioritisation are based on outdated estimations (see https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/compaction/CompactionStrategyHolder.java#L109).
Bug: Increased Read Latency With Cassandra >= 3.11.7
Status: Open
Priority: Normal
Created: 22/Feb/21 09:31

After upgrading Cassandra from 3.11.3 to 3.11.9, Cassandra read latency 99% increased significantly. Getting back to 3.11.3 immediately fixed the issue.

I have observed "SStable reads" increases after upgrading to 3.11.9.

The same behavior was observed by some other users: [https://www.mail-archive.com/user@cassandra.apache.org/msg61247.html]

According to Paulo Motta's comment, this behavior may be caused by https://issues.apache.org/jira/browse/CASSANDRA-15690 which was introduced on 3.11.7 and removed an optimization that may cause a correctness issue when there are partition deletions.
Bug: Fail to init Cassandra Startup with an API connected with other cluster machines (3.11.9 version)
Status: Resolved
Priority: Normal
Resolution: Won't Fix
Created: 24/Mar/21 20:14
Resolved: 23/Jul/21 15:36

The code in the function "VerifyPortsAreAvailable", look for the ports: 7000, 9042, 7199 and 9160 in the "netstat -an" command output.

 

If we have an API connected to the cluster in a node, and we try to start the execution of cassandra (with that API working, accesing ports 9042 of the other cluster machines), the output of that command return us that the port is already in use, and Cassandra´s startup process fails, showing the output message : "port already in use" in the .log file.

Thus, if we change the code of the function, adding the line: " -and $line -match "LISTENING" ", just next to the "$line -match "TCP" ", we will only interrupt the execution if the load port is in the state: "LISTENING", but no if it´s an active connection on the other node of the cluster.

!image-2021-03-24-21-12-32-709.png|width=470,height=159!

!image-2021-03-24-21-13-46-704.png|width=526,height=119!
Bug: speculative retry should allow more friendly params, allowing upgrade from 2.x not to break
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 23/Feb/21 20:07
Resolved: 15/Jul/21 20:18

2.x speculative retry params are case insensitive, while 3.0 and 3.11 have added case sensitivity. As as result of this, one of our internal applications suffered an issue during 
C* upgrade from 2.x to 3.0.

This ticket is to propose making 3.0 and 3.11 speculative_retry params case insensitive as well (essentially a slightly modified backport of CASSANDRA-13876, but not to allow something like "99p" which 4.0 allows)
Bug: Add a method to IMessageFilters.IFilter to return the number of message that it has matched
Status: Triage Needed
Priority: Normal
Created: 17/Feb/21 10:30

For some tests like the ones of {{CASTest}} it will be great to be able to check how many message have been matched by the {{IFilter}} instances to check that everything has occured has expected.
One way of doing that would be to add a method to IMessageFilters.IFilter to return the number of message that it has matched.
Bug: Add possibility to copy SSTables in SSTableImporter instead of moving them
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 26/Jan/21 21:06
Resolved: 05/Mar/21 10:09

SSTableImporter moves data from source to target. Modify the current code in such a way that source files / SSTables might be copied over, not moved. The reason behind this is that if I have a backup, I do not want to lose that backup after I import it. Backup should stay as it was, untouched. Callers might choose what behavior they require, either importing by moving or importing by copying.

Please keep in mind that SSTableImporter was firstly introduced in 4.0 trunk and this is seen as a bug basically, I was dedicing between a bug and improvement. I still believe that this should happen BEFORE 4.0 gets out.

https://github.com/apache/cassandra/pull/875/files

https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/376/
Bug: Flaky ValidationExecutorTest
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 19/Mar/21 08:41
Resolved: 26/Mar/21 10:51

Flaky ValidationExecutorTest see [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/347/testReport/junit/org.apache.cassandra.db.compaction/ValidationExecutorTest/testQueueOnValidationSubmission_cdc/]
Bug: cqlsh cannot DESC TYPE with non-ascii character in the identifier
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 22/Jan/21 19:06
Resolved: 17/May/21 19:57

cqlsh fails to describe types with non-ascii characters. This is specific to Python 2 and does not occur in Python 3 (only tested on trunk so far).

{code}
CREATE TYPE ks."ࠑ " (
    v int
);
{code}

{noformat}
aholmberg-rmbp16:cassandra adamholmberg$ pyenv shell 2.7.17
aholmberg-rmbp16:cassandra adamholmberg$ bin/cqlsh
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 4.0-beta4-SNAPSHOT | CQL spec 3.4.5 | Native protocol v4]
Use HELP for help.
cqlsh> desc types;
Traceback (most recent call last):
  File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1391, in do_describe
    self.describe_list(result)
  File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1438, in describe_list
    names.append(str(row['name']))
UnicodeEncodeError: 'ascii' codec can't encode character u'\u0811' in position 1: ordinal not in range(128)
{noformat}


3.11 appears to handle everything properly.
Bug: Improve LICENSE/NOTICE compliance with ASF guidance 
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 31/Mar/21 03:52
Resolved: 31/Mar/21 19:17

PRs on GitHub:

[https://github.com/apache/cassandra/pull/943]

[https://github.com/apache/cassandra/pull/944] 

 

A number of issues were identified with our LICENSE.txt and NOTICE.txt files (https://lists.apache.org/thread.html/r66496e495c96efeb31c6531eb748ec739bfb734d5c115077d925ebac%40%3Cdev.cassandra.apache.org%3E), specifically related to identifing bundled source and their respective licenses in accordance with ASF guidance ([https://infra.apache.org/licensing-howto.html]).

 

*LICENSE.txt*

We don't specifically identify the licenses of a number of bundled components included with the source distro of Apache Cassandra in our License file in accordance with ([https://infra.apache.org/licensing-howto.html]). Specifically:
 # src/java/org/apache/cassandra/index/sasi/utils/AbstractIterator.java
 # src/java/org/apache/cassandra/utils/LongTimSort.java
 # src/java/org/apache/cassandra/index/sasi/utils/trie/Cursor.java
 # test/resources/tokenization/adventures_of_huckleberry_finn_mark_twain.txt
 # content in doc/source/data_modeling/

Note: src/java/org/apache/cassandra/utils/vint/VIntCoding.java makes reference of borrowing ideas from Google Protocol Buffers.

I'm not sure if this is code, concepts or a reference to the concepts in the documentation for an understanding of the idea. I've included it as its a compatible licenses to be on the safe side.

I've also removed the reference to the lib/ folder as this license (as I understand) currently applies to the source release rather than convenience binaries.

 

*NOTICE.txt*

Removing references for dependencies that are not bundled (e.g. pulled in dynamically).

Bundled dep src/java/org/apache/cassandra/utils/LongTimSort.java uses ALv2 but is not owned by ASF so providing attribution.
Bug: Fix flaky TestDynamicEndpointSnitch.test_multidatacenter_local_quorum test
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 01/Mar/21 20:38
Resolved: 16/Mar/21 19:19

https://ci-cassandra.apache.org/job/Cassandra-devbranch/434/testReport/junit/dtest-large.snitch_test/TestDynamicEndpointSnitch/test_multidatacenter_local_quorum/history/ has gotten flaky in the somewhat recent past.
Bug: Scheduled (Delayed) Schema Pull Tasks May Run After MIGRATION Stage Shutdown During Decommission
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/Mar/21 21:48
Resolved: 07/Apr/21 20:06

A new test added in CASSANDRA-16181 stumbled across this, although it doesn’t happen consistently. When [failure occurs|https://app.circleci.com/pipelines/github/maedhroz/cassandra/235/workflows/eb8133ce-9373-4136-b404-ceca167353f6/jobs/1355/tests], it appears to be because a delayed schema pull happens after decommission shuts down the MIGRATION stage’s thread pool.

{noformat}
ERROR [node1_isolatedExecutor:1] node1 2021-02-15 19:35:36,284 CassandraDaemon.java:579 - Exception in thread Thread[node1_NonPeriodicTasks:1,5,node1] java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut down at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:72) 
at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825) 
at java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1355) 
at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.execute(DebuggableThreadPoolExecutor.java:176) 
at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at org.apache.cassandra.concurrent.Stage.submit(Stage.java:129) 
at org.apache.cassandra.schema.MigrationCoordinator.lambda$scheduleSchemaPull$2(MigrationCoordinator.java:362) 
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) 
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) 
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) 
at java.base/java.lang.Thread.run(Thread.java:834)
{noformat}

A fix might be as simple as shutting down ScheduledExecutors.nonPeriodicTasks in StorageService#decommission(). See the original discussion [here|https://issues.apache.org/jira/browse/CASSANDRA-16181?focusedCommentId=17293329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17293329].
Bug: Update Python 2 references in docs to point to python 3
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 09/Mar/21 01:43
Resolved: 09/Mar/21 23:17

Several references in the docs still point to python 2 urls. Update them to point to python 3.

I opened a PR for this here: https://github.com/apache/cassandra/pull/920
Bug: Flaky testRecoverOverflowedExpirationWithSSTableScrub
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 30/Mar/21 07:19
Resolved: 31/Mar/21 20:19

See [here|https://ci-cassandra.apache.org/job/Cassandra-trunk-test/627/jdk=jdk_11_latest,label=cassandra,split=4/testReport/junit/org.apache.cassandra.cql3.validation.operations/TTLTest/testRecoverOverflowedExpirationWithSSTableScrub/]
Bug: 4.0 node sending a repair prepare message to a 3.x node breaks the connection on 4.0 side
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 26/Mar/21 16:12
Resolved: 26/Mar/21 17:49

An {{AssertionError}} is thrown in {{PrepareMessage#serializedSize()}} method that causes internode connections to be repeatedly torn down until affected instances are restarted.
Bug: nodetool status doesn't work without system_traces
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 28/Jan/21 15:16
Resolved: 19/Feb/21 21:38

bq. Error: The node does not have system_traces yet, probably still bootstrapping

There's no reason we can't show status because of this, we can simply log that the effective ownership is unknown, like we used to, rather than forcing a user to go to another machine to find out what's going on in the ring.
Bug: Add Jenkins arm64 jobs to ci-cassandra.a.o
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 02/Mar/21 18:59
Resolved: 26/Mar/21 21:43

Hauwei has donated arm64 servers intended for ci-cassandra.apache.org

The first two have been tested over a numbers of issues and fixes already. Now that all the jobs work, the arm64 architecture is read to be added Jenkins. (Four more servers are on their way as well.)
Bug: BinLogTest is flaky
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 18/Mar/21 14:38
Resolved: 30/Mar/21 00:00

Probably due to increasing the runners:

{noformat}
java.lang.RuntimeException: java.lang.IllegalStateException: Expected file to exist for cycle: 1616021848, file: /home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test-compression/jdk/jdk_11_latest/label/cassandra/tmp/foo17bar/20210317-225728T.cq4.
minCycle: 1616021850, maxCycle: 1616021852
Available files: [20210317-225730T.cq4, 20210317-225732T.cq4]
	at org.apache.cassandra.utils.binlog.BinLogTest.readBinLogRecords(BinLogTest.java:492)
	at org.apache.cassandra.utils.binlog.BinLogTest.lambda$testTrucationReleasesLogSpace$8(BinLogTest.java:444)
	at org.apache.cassandra.Util.spinAssertEquals(Util.java:605)
	at org.apache.cassandra.Util.spinAssertEquals(Util.java:595)
	at org.apache.cassandra.utils.binlog.BinLogTest.testTrucationReleasesLogSpace(BinLogTest.java:444)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Caused by: java.lang.IllegalStateException: Expected file to exist for cycle: 1616021848, file: /home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test-compression/jdk/jdk_11_latest/label/cassandra/tmp/foo17bar/20210317-225728T.cq4.
minCycle: 1616021850, maxCycle: 1616021852
Available files: [20210317-225730T.cq4, 20210317-225732T.cq4]
	at net.openhft.chronicle.queue.impl.single.SingleChronicleQueue$StoreSupplier.nextCycle(SingleChronicleQueue.java:1157)
	at net.openhft.chronicle.queue.impl.WireStorePool.nextCycle(WireStorePool.java:66)
	at net.openhft.chronicle.queue.impl.single.SingleChronicleQueue.nextCycle(SingleChronicleQueue.java:507)
	at net.openhft.chronicle.queue.impl.single.StoreTailer.nextIndexWithNextAvailableCycle(StoreTailer.java:507)
	at net.openhft.chronicle.queue.impl.single.StoreTailer.endOfCycle(StoreTailer.java:323)
	at net.openhft.chronicle.queue.impl.single.StoreTailer.next0(StoreTailer.java:295)
	at net.openhft.chronicle.queue.impl.single.StoreTailer.readingDocument(StoreTailer.java:202)
	at net.openhft.chronicle.queue.impl.single.StoreTailer.readDocument(StoreTailer.java:108)
	at org.apache.cassandra.utils.binlog.BinLogTest.readBinLogRecords(BinLogTest.java:481)
{noformat}
Bug: WEBSITE - Publish a new landing page for the 2021 World Party marketing efforts
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 26/Mar/21 01:29
Resolved: 26/Mar/21 08:06

Request from [~mklogan] at Constantia.io to create a new landing page for the 2021 World Party to support marketing efforts.

Attached are the page draft and assets.
Bug: WEBSITE - Place a World Party button on the homepage
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 31/Mar/21 02:49
Resolved: 09/Apr/21 07:22

Place a World Party button on the [homepage|https://cassandra.apache.org/] to promote the event in April 2021.

+ninja: Remove title from [World Party|https://cassandra.apache.org/worldparty/] landing page for cosmetic reasons.
Bug: WEBSITE - Update World Party pages to indicate all times are April 28 UTC
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 26/Mar/21 22:25
Resolved: 27/Mar/21 10:34

The World Party landing page and blog post list the event times as:
 * 1-2pm UTC / 6-7am PDT
 * 9-10pm UTC / 3-4pm PDT
 * 5-6am UTC / 10-11pm PDT

This is confusing for attendees because it suggests that the third timeslot is the following day, i.e. April 29 5am UTC.

We need to update the assets to list the event times explicitly as April 28 UTC to avoid confusion:
 * April 28 5:00am UTC
 * April 28 1:00pm UTC
 * April 28 9:00pm UTC
Bug: BLOG - Changelog #5 Mar 2021
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/Mar/21 22:19
Resolved: 15/Mar/21 07:59

Draft by [~Calico] – [C* Blog: Cassandra Changelog #5|https://docs.google.com/document/d/1eQhBM4UAqC_MToJnEMaJn6hAaHjPNDGveccnA8dhkdE/edit?usp=sharing]