av9ash/GitBugs huggingface dataset:
Bug: Test Failure: dtest-offheap.client_request_metrics_local_remote_test.TestClientRequestMetricsLocalRemote.test_batch_and_slice
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 27/Sep/22 15:21
Resolved: 27/Sep/22 15:27

[Link|https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/dtest-offheap.client_request_metrics_local_remote_test/TestClientRequestMetricsLocalRemote/test_batch_and_slice/]

Error Message
{code}
subprocess.CalledProcessError: Command '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp', '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar', 'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.1', '--port', '8778', 'start', '2026')' returned non-zero exit status 1.
{code}

Stacktrace
{code}
           if check and retcode:
             raise CalledProcessError(retcode, process.args,
                                        output=stdout, stderr=stderr)
E               subprocess.CalledProcessError: Command '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp', '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar', 'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.1', '--port', '8778', 'start', '2026')' returned non-zero exit status 1.

/usr/lib/python3.8/subprocess.py:516: CalledProcessError
{code}
Bug: Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 26/Sep/22 11:57
Resolved: 26/Sep/22 14:21

Dears,

We are using the repo from url: https://www.apache.org/dist/cassandra/redhat/40x

 

During update we got an error:
yum update
Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager
Apache_Cassandra_4_0_Cassandra_40x      | 2.0 kB  00:00:00
rhel-7-server-optional-rpms                       | 3.2 kB  00:00:00
rhel-7-server-rpms                                      | 3.5 kB  00:00:00
Resolving Dependencies
--> Running transaction check
---> Package cassandra.noarch 0:4.0.4-1 will be updated
---> Package cassandra.noarch 0:4.0.5-1 will be an update
*Error: Invalid version flag: or*
Uploading Enabled Repositories Report
Loaded plugins: langpacks, product-id, subscription-manager

Do you have any idea how to solve it?

Best Regards,

Dan
Bug: Add pull request template
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 19/Aug/22 06:10
Resolved: 21/Sep/22 07:13

Add pull request template something like:

 ----- start of text

Issue resolved # CASSANDRA-

Pull request Description:
---- 
 - [  ] Commits have been squashed to remove intermediate development commit messages.
 - [  ] Key commit messages start with the issue number (CASSANDRA-xxxx)

either
 - [  ] this is a trivial documentation change. (e.g. fixes a typo)
or:
 - [  ] Tests are included.
 - [  ] Documentation changes and/or updates are included.

By submitting this pull request, I acknowledge that I am making a contribution to the Apache Software Foundation under the terms and conditions of the [Contributor's Agreement]([https://www.apache.org/licenses/contributor-agreements.html]).
----
See the [Apache Cassandra "Contributing to Cassandra" guide]([https://cassandra.apache.org/_/development/index.html]) and/or the [Apache Cassandra "Working on Documentation" guide]([https://cassandra.apache.org/_/development/documentation.html])
Bug: Cassandra repo not updated with latest 4.0.6 package
Status: Resolved
Priority: Normal
Resolution: Not A Problem
Created: 21/Sep/22 05:59
Resolved: 21/Sep/22 06:17

Hi Team,

 

The repo is not updated with latest package -[Index of /cassandra/redhat/40x (apache.org)|https://downloads.apache.org/cassandra/redhat/40x/]

 

we are looking to download 4.0.6 from the above link but 4.0.5 package is getting downloaded

 

we are following below steps and 4.0.6 is not part of the yum repository

- [Install Cassandra In CentOS Linux - OSTechNix|https://ostechnix.com/install-cassandra-in-centos/]
Bug: Cassandra repo not updated with latest 4.0.6 package
Status: Resolved
Priority: Normal
Resolution: Not A Problem
Created: 19/Sep/22 05:52
Resolved: 19/Sep/22 11:22

Hi Team,

 

The repo is not updated with latest package -[Index of /cassandra/redhat/40x (apache.org)|https://downloads.apache.org/cassandra/redhat/40x/]

 

we are looking to download 4.0.6 from the above link but 4.0.5 package is getting downloaded

 

this is the new version support - [Apache Cassandra | Apache Cassandra Documentation|https://cassandra.apache.org/_/blog/Apache-Cassandra-Changelog-18-August-2022.html]
Bug: Support high PRIORITY thread pool for use trriged compaction
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 14/Sep/22 12:16
Resolved: 19/Sep/22 09:21

For cassandra compaction thread pool is of min priority ,so if we trriged a major compaction through nodetool compact ,the task is submit to the exector that is created at CompactionManager.java 
{code:java}
CompactionExecutor executor = new CompactionExecutor();
{code}

But sometime we may want the task to be of high PRIORITY, so that the compaction can be make more fast.
Bug: Test Failure: org.apache.cassandra.distributed.test.SchemaTest
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 16/Sep/22 17:28
Resolved: 16/Sep/22 17:35

Seen this failure pop up a couple times on circle now on different tickets in different configurations.

{code}
org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in org.apache.cassandra.distributed.test.SchemaTest that uses org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
	at org.apache.cassandra.distributed.test.SchemaTest.schemaReset(SchemaTest.java:115)
	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)
{code}
Bug: Fix flaky test_archive_commitlog_point_in_time
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 13/Sep/22 20:35
Resolved: 15/Sep/22 14:15

Spotted in butler to fail for 4.0, 4.1 and trunk:
h3.  
{code:java}
Error Message
AssertionError: It's been over a {s}s and we haven't written a new commitlog segment. Something is wrong.

Stacktrace
self = <snapshot_test.TestArchiveCommitlog object at 0x7efe72087d00> def test_archive_commitlog_point_in_time(self): """ Test archive commit log with restore_point_in_time setting """ > self.run_archive_commitlog(restore_point_in_time=True) snapshot_test.py:259: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ snapshot_test.py:301: in run_archive_commitlog advance_to_next_cl_segment( _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
{code}
Bug: Fix flaky test_no_base_column_in_view_pk_complex_timestamp_with_flush
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 09/Sep/22 14:35
Resolved: 12/Sep/22 16:08

It seems flaky lately on 4.1 per Butler:

[https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-4.1/failure/materialized_views_test/TestMaterializedViews/test_no_base_column_in_view_pk_complex_timestamp_with_flush]

I was not able to reproduce it on 4.0 and 4.1 in Circle. 
h3.  
{code:java}
Error Message
AssertionError: Expected [[1, 1, 1, None, None, None]] from SELECT * FROM t, but got []

Stacktrace
self = <materialized_views_test.TestMaterializedViews object at 0x7fc5fb98a880> @flaky @since('3.0') def test_no_base_column_in_view_pk_complex_timestamp_with_flush(self): > self._test_no_base_column_in_view_pk_complex_timestamp(flush=True) materialized_views_test.py:1451: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ materialized_views_test.py:1541: in _test_no_base_column_in_view_pk_complex_timestamp assert_one(session, "SELECT * FROM t", [1, 1, 1, None, None, None]) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
{code}
Bug: Filter out NULL tokens entries from the peers table 
Status: Triage Needed
Priority: Normal
Created: 01/Sep/22 21:45

Similar to the issue reported in [CASSANDRA-16518|https://issues.apache.org/jira/browse/CASSANDRA-16518]. 

https://issues.apache.org/jira/browse/CASSANDRA-15193 adds a check for node version, which reverts the protocol version to V3 if any peer fails the version check. However, the version check should only consider the node which is already joined, i.e., the tokens entry should not be NULL. 

CASSANDRA-16518 fixed the issue by filtering out the NULL release_version entries, which doesn't solve the problem for all the cases. In our test case, we see rows in the system.peers table with non-null release_version (although it's obsolete entry) but the tokens are NULL. 

We should filter out the NULL tokens entries as well.
Bug: WEBSITE - Community page - encourage users to search answered questions on Stack Overflow, Stack Exchange
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 24/Aug/22 04:05
Resolved: 26/Aug/22 14:55

We need to encourage users to first search the {{[cassandra]}} tag on [Stack Overflow|http://stackoverflow.com/questions/tagged/cassandra] and [Stack Exchange|https://dba.stackexchange.com/questions/tagged/cassandra] before asking a question so contributors are not repeatedly asking the same questions over and over.
Bug: WEBSITE - Add guide for Asking Good Questions
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 25/Aug/22 00:44
Resolved: 26/Aug/22 13:44

This is for publishing the guide to *Asking Good Questions* [proposed on the Dev ML|https://lists.apache.org/thread/fnlzos2v78xmgxhz37xsskpdc30dl95l].

The draft guide is [available here|https://docs.google.com/document/d/1-ZYpl9tif9OAMdAxFLxA1mTPNp0zkNW4kzXvfvRBHUc/edit?usp=sharing].
Bug: WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 19/Aug/22 00:40
Resolved: 20/Aug/22 15:05

This ticket is to capture the work associated with publishing the July 2022 blog "Apache Cassandra Changelog #18"

If this blog cannot be published by the *August 19, 2022 publish date*, please contact me, suggest changes, or correct the date when possible in the pull request for the appropriate time that the blog will go live (on both the blog.adoc and the blog post's file).
Bug: Sporadic CL switch from LOCAL_QUORUM to ALL
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 24/Aug/22 10:02
Resolved: 24/Aug/22 10:45

Team - we see that the Consitency Level is changing to ALL, when there is a read timeout.

Used Cassandra session has next main properties:
 * Load balancing policy - DCAwareRoundRobinPolicy(localDc, usedHostPerRemoteDc = 3, allowRemoteDcForLocalConsistencyLevel = true)
 * Retry policy - DefaultRetryPolicy
 * Query options - QueryOptions with set consistency level to ConsistencyLevel.{*}LOCAL_QUORUM{*}

 

we have the table as defined below.
{code:java}
CREATE TABLE table_name (
    key text,
    column1 text,
    column2 text,
    value text,
    PRIMARY KEY (key, column1, column2)
) WITH COMPACT STORAGE
    AND CLUSTERING ORDER BY (column1 ASC, column2 ASC)
    AND bloom_filter_fp_chance = 0.1
    AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
    AND comment = ''
    AND compaction = {'class': 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy', 'sstable_size_in_mb': '180'}
    AND compression = {'chunk_length_in_kb': '64', 'class': 'org.apache.cassandra.io.compress.SnappyCompressor'}
    AND crc_check_chance = 1.0
    AND dclocal_read_repair_chance = 0.0
    AND default_time_to_live = 0
    AND gc_grace_seconds = 864000
    AND max_index_interval = 2048
    AND memtable_flush_period_in_ms = 0
    AND min_index_interval = 128
    AND read_repair_chance = 0.0
    AND speculative_retry = '99PERCENTILE'; {code}
 

On Read Timeout, below exception is observed.
{code:java}
Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency ALL (5 responses were required but only 4 replica responded)
    at com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:88) ~[cassandra-driver-core-3.1.4.jar!/:?]
    at com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:25) ~[cassandra-driver-core-3.1.4.jar!/:?]
    at com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37) ~[cassandra-driver-core-3.1.4.jar!/:?]
    at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245) ~[cassandra-driver-core-3.1.4.jar!/:?]
    at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:68) ~[cassandra-driver-core-3.1.4.jar!/:?] {code}
This could be an issue re-occurred in Cassandra 3.11.0, which is the version used currently.Also - this could be related to https://issues.apache.org/jira/browse/CASSANDRA-7868

Please provide your feedback on the same.
Bug: Unable to Access Convenience Package Download Sites
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 24/Aug/22 19:28
Resolved: 24/Aug/22 20:24

The web addresses setup in CASSANDRA-17748 don't seem to be accessible.  The specific download sites are:
 * [https://redhat.cassandra.apache.org/]
 * [https://debian.cassandra.apache.org|https://debian.cassandra.apache.org/]

They were definitely working on the 16th of August (when I last ran a test installation) but have been failing since at least 2022-08-22T07:24Z and are still failing now.

Attempting to access the raw [https://redhat.cassandra.apache.org/] results in a connection timeout, but accessing the underlying [https://apache.jfrog.io/ui/native/cassandra-rpm] works OK.

These affected web addresses are also referred to in the installation documentation at:
 * [https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-rpm-packages]
 * [https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-debian-packages]
Bug: Add support in CQLSH for COPY FROM / TO in compact Parquet format
Status: Open
Priority: Normal
Created: 17/Aug/22 23:42

CQL supports only CSV as a format for import and export. A binary big data format such as Avro and/or Parquet would be more compact and highly portable to other platforms.

Parquet does not require a schema, so it appears the easier format to support.

The existing syntax supports adding key value pair options, such as FORMAT = PARQUET

{{     COPY table_name ... FROM 'file_name'[, 'file2_name', ...] }}

                     {{[WITH option = 'value' [AND ...]]}}

Side by side comparisons of CSV and Parquet show a 80% plus saving in disk space.

[https://towardsdatascience.com/csv-files-for-storage-no-thanks-theres-a-better-option-72c78a414d1d]
Bug: libjemalloc2 is not detected by cassandra script
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 27/Jul/22 10:56
Resolved: 27/Jul/22 13:03

I noticed that there was this log message when I started a Cassandra node on a machine in AWS on Ubuntu Jelly (22.04).
{code:java}
WARN  [main] 2022-07-27 11:04:16,731 StartupChecks.java:200 - jemalloc shared library could not be preloaded to speed up memory allocations
{code}
Hence, I went ahead and I tried to install that package, on 22.04, 
{code:java}
$ apt search libjemalloc
Sorting... Done
Full Text Search... Done
libjemalloc-dev/jammy 5.2.1-4ubuntu1 amd64
    development files and documentation for jemalloc

libjemalloc2/jammy,now 5.2.1-4ubuntu1 amd64
    general-purpose scalable concurrent malloc(3) implementation {code}
So I did apt install libjemalloc2.

But the problems didnt go away because cassandra script didnt recognised it. The value of JVM property the jemalloc startup check is reading from is an environment property called CASSANDRA_LIBJEMALLOC (1) which is set by us looking into various library paths, trying to find "libjemalloc.so.1"(2). But there is no "1" version of it. We have version "2".
{code:java}
$ sudo dpkg -L libjemalloc2
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libjemalloc.so.2  <---- our tasty libjemalloc
/usr/share
/usr/share/doc
/usr/share/doc/libjemalloc2
/usr/share/doc/libjemalloc2/README
/usr/share/doc/libjemalloc2/changelog.Debian.gz
/usr/share/doc/libjemalloc2/copyright{code}
(1) [https://github.com/apache/cassandra/blob/cassandra-4.0/bin/cassandra#L160]
(2) [https://github.com/apache/cassandra/blob/cassandra-4.0/bin/cassandra#L157]

I checked what Debian is offering and Bullseye and Buster do not have libjemalloc1 anymore, they have version 2, 1 is gone. Strech and Jessie have version 1 and not 2 (obviously). Ubuntu Jelly has 2, I am not sure when they started to ship 2 instead of 1 but I assume that if a user runs Cassandra on "anything recent", this is broken, jemalloc is not used and I think that performance can suffer quite significantly.

This logic is present from 3.0 onwards.

The patch should fix this and it should take both versions into account. I will provide patch with my solution shortly.
Bug: Cassandra COPY command ignore QUOTE option
Status: Triage Needed
Priority: Normal
Created: 19/Aug/22 07:48

I am not able to copy data into a CSV file and have them wrapped with single quotes:

e.g.

{*}Table{*}: myks.mytable
||column1||column2||
|value1|value2|

command used: {{copy myks.mytable (column1,column2) to 'myfile.csv' WITH HEADER=FALSE AND DELIMITER=';' AND QUOTE='"';}}

*expected result:*

The CSV file to have one row: {{"value1";"value2"}}

*actual result:*

The CSV file has one row: {{value1:value2}}
Bug: SSL Validation Error
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 18/Aug/22 06:03
Resolved: 18/Aug/22 10:20

Hi,

 

SSL is configuring  for security purpose and while configuring getting the issues.

 

Issue : Creating keystore name of “keystore.cass4” with password Cassandra but after that creating a second certificate using keystore.cass4 getting error Keystore was tampered with, or password was incorrect.

 

I’m verified the password and excute same password but getting above error. Below chain mail I mentioned the entire using commands , references links ,Error screen shot etc..

Getting Error while generating SSL certificates, 1{^}st{^} certificate generated after that trying for second certificate getting error.

 

Using same password but getting error Keystore was tampered with, or password was incorrect.

 

Error Msg : {color:#000000}Keytool error : Java.io.IOException : Keystore was tampered with, or password was incorrect{color}.

 

please do need full..
Bug: Enable using a deterministic table id at table creation time
Status: Triage Needed
Priority: Normal
Created: 16/Aug/22 22:13

When the *CREATE TABLE* statement is executed on a coordinator node, it is assigned a new random, globally unique ID (i.e., time UUID). That ID doesn't change on the  *ALTER TABLE* statement, whereas the *DROP* and then *CREATE* table will create a new ID. Cassandra relies on the fact that tables with the same table ID have compatible schemas and use the table ID to reach the schema agreement.

One of the issues with the random UUID is when concurrent schema changes are running on different coordinator nodes since clients may implement the schema change programmatically and issue the events from different nodes concurrently. Since Cassandra is an eventually consistent system, not just in terms of data it stores, but also in terms of schemas by relying on the gossip protocol, it may take a non-deterministic amount of time before all the nodes in the cluster converge on one schema version. 

Once a cluster is in the state of schema disagreement, it is a non-trivial effort to recover the cluster to a healthy state, and such a recovery process may potentially involve downtime.

Therefore, we propose an option of using the deterministic table id per the *CREATE TABLE* statement. Some key properties of the deterministic id are:
 * The *CREATE TABLE* queries which are syntactically the same should always generate the same table id. And the id should be globally unique. 
 * The *CREATE TABLE* queries which are semantically the same should also guarantee to have the table id, even though the queries may look syntactically different. For example, the parsed query should ignore white spaces, lower/upper cases, etc.. 
 * Similar to the requirement #2, queries with the default options/parameters should always have the same id, no matter if they are declared implicitly or explicitly. 
 * Queries which are semantically different should generate the different table ids, even though they may have the same keyspace name and table name. 

To fulfill all the requirements discussed above, the input of the hash function should include the full metadata of the CREATE TABLE statement. Therefore, we use the serialized version of the class *CreateTableStatement* in Cassandra{*},{*} which includes all the metadata of the CREATE TABLE statement.
Bug: Harry test failure - conflicting replica can be added (expected unique endpoints)
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 16/Aug/22 15:43
Resolved: 16/Aug/22 15:44

Changes to natural and pending replicas are not synchronized, so it can happen that a replica is in the natural set a replication strategy calculates but is also in pending endpoints in the StorageService. We need to filter out all pending replicas that are also present in the natural set so we don't end up with duplication between them in our {{EndpointsForToken}} calculations.
Bug: WEBSITE - August 2022 blog "Cassandra Day in Berlin Announced"
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 12/Aug/22 16:36
Resolved: 12/Aug/22 21:05

This ticket is to capture the work associated with publishing the August 2022 blog "Cassandra Day in Berlin Announced"

If this blog cannot be published by the *August 12, 2022 publish date*, please contact me, suggest changes, or correct the date when possible in the pull request for the appropriate time that the blog will go live (on both the blog.adoc and the blog post's file).
Bug: AlterTypeStatement validate is missing checks
Status: Resolved
Priority: Normal
Resolution: Won't Fix
Created: 05/Aug/22 17:48
Resolved: 08/Aug/22 18:10

All the checks for a valid AlterTypeStatement are happening in apply() not validate()

 

Same problem in CreateTypeStatement.  [https://github.com/apache/cassandra/blob/45f4f8c1e89e4b221b569ff3bd3e78675eff7747/src/java/org/apache/cassandra/cql3/statements/schema/CreateTypeStatement.java#L66]

 

Perhaps all schema statements should be checked for validations
Bug: WEBSITE - August 2022 blog "Watch the Cassandra World Party"
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 04/Aug/22 00:39
Resolved: 07/Aug/22 17:03

This ticket is to capture the work associated with publishing the August 2022 blog "Watch the Cassandra World Party"

If this blog cannot be published by the *August 4, 2022 publish date*, please contact me, suggest changes, or correct the date when possible in the pull request for the appropriate time that the blog will go live (on both the blog.adoc and the blog post's file).