Skip to content

Commit

Permalink
Fix codespell errors after tool update
Browse files Browse the repository at this point in the history
Required-githooks: true

Change-Id: I56dd48c9f447034be3cd8891a9efac4fc07939aa
Signed-off-by: Jeff Olivier <jeffolivier@google.com>
  • Loading branch information
jolivier23 committed May 28, 2024
1 parent 868bf18 commit a9f9963
Show file tree
Hide file tree
Showing 15 changed files with 18 additions and 15 deletions.
3 changes: 3 additions & 0 deletions ci/codespell.ignores
Original file line number Diff line number Diff line change
Expand Up @@ -35,3 +35,6 @@ expres
signalling
laf
cacl
rin
assertin
checkin
2 changes: 1 addition & 1 deletion src/bio/bio_wal.c
Original file line number Diff line number Diff line change
Expand Up @@ -587,7 +587,7 @@ fill_trans_blks(struct bio_meta_context *mc, struct bio_sglist *bsgl, struct ume
left = blk_sz - entry_blk.tb_off;
/* Current entry block is full, move to next entry block */
if (left < entry_sz) {
/* Zeoring left bytes for csum calculation */
/* Zeroing left bytes for csum calculation */
if (left > 0)
memset(entry_blk.tb_buf + entry_blk.tb_off, 0, left);
next_trans_blk(bsgl, &entry_blk);
Expand Down
2 changes: 1 addition & 1 deletion src/client/array/dc_array.c
Original file line number Diff line number Diff line change
Expand Up @@ -1647,7 +1647,7 @@ dc_array_io(daos_handle_t array_oh, daos_handle_t th,
/*
* verify that the dkey is the same as the one we are working on
* given the array index, and also compute the number of records
* left in the dkey and the record indexin the dkey.
* left in the dkey and the record indexing the dkey.
*/
rc = compute_dkey(array, array_idx, &num_records, &record_i,
&dkey_val);
Expand Down
2 changes: 1 addition & 1 deletion src/client/dfuse/ops/readdir.c
Original file line number Diff line number Diff line change
Expand Up @@ -364,7 +364,7 @@ dfuse_do_readdir(struct dfuse_info *dfuse_info, fuse_req_t req, struct dfuse_obj
/* If there is no seekdir but there is valid cache data then use the cache.
*
* Directory handles may not have up-to-date values for doh_rd_nextc in some cases
* so perform a seek here if necessairy.
* so perform a seek here if necessary.
*/
struct dfuse_readdir_c *drc;
size_t written = 0;
Expand Down
2 changes: 1 addition & 1 deletion src/control/security/testdata/certs/source.txt
Original file line number Diff line number Diff line change
@@ -1 +1 @@
This tile is here to act as a source file for generating hash and signiture files to test the sign and verify signature functionality.
This tile is here to act as a source file for generating hash and signature files to test the sign and verify signature functionality.
2 changes: 1 addition & 1 deletion src/engine/module.c
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ dss_module_init_all(uint64_t *mod_facs)

/*
* first register global tls accessible to all modules,
* it'll be first initialized and last finialized.
* it'll be first initialized and last finalized.
*/
dss_register_key(&daos_srv_modkey);

Expand Down
4 changes: 2 additions & 2 deletions src/include/daos_api.h
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ daos_tx_commit(daos_handle_t th, daos_event_t *ev);
* Create a read-only transaction from a snapshot. This does not create the
* snapshot, but only a read transaction to be able to read from a snapshot
* created with daos_cont_create_snap. If the user passes an epoch that is not
* snapshoted, or the snapshot was deleted, reads using that transaction may
* snapshotted, or the snapshot was deleted, reads using that transaction may
* get undefined results.
*
* \param[in] coh Container handle.
Expand Down Expand Up @@ -188,7 +188,7 @@ daos_anchor_init(daos_anchor_t *anchor, __attribute__((unused)) unsigned int opt
* Finalizie an iteratror anchor, free resources allocated
* during the iteration.
*
* \param[in] anchor Anchor to be finialized
* \param[in] anchor Anchor to be finalized
*/
static inline void
daos_anchor_fini(__attribute__((unused)) daos_anchor_t *anchor)
Expand Down
2 changes: 1 addition & 1 deletion src/include/daos_errno.h
Original file line number Diff line number Diff line change
Expand Up @@ -235,7 +235,7 @@ extern "C" {
ACTION(DER_FETCH_AGAIN, (DER_ERR_DAOS_BASE + 32), Fetch again) \
/** Hit uncertain DTX, may need to try with other replica. */ \
ACTION(DER_TX_UNCERTAIN, (DER_ERR_DAOS_BASE + 33), TX status is uncertain) \
/** Communicatin issue with agent. */ \
/** Communication issue with agent. */ \
ACTION(DER_AGENT_COMM, (DER_ERR_DAOS_BASE + 34), Agent communication error) \
/** ID mismatch */ \
ACTION(DER_ID_MISMATCH, (DER_ERR_DAOS_BASE + 35), ID mismatch) \
Expand Down
2 changes: 1 addition & 1 deletion src/include/daos_srv/bio.h
Original file line number Diff line number Diff line change
Expand Up @@ -427,7 +427,7 @@ int bio_nvme_init(const char *nvme_conf, int numa_node, unsigned int mem_size,
unsigned int hugepage_size, unsigned int tgt_nr, bool bypass);

/**
* Global NVMe finilization.
* Global NVMe finalization.
*
* \return N/A
*/
Expand Down
2 changes: 1 addition & 1 deletion src/include/daos_srv/dtx_srv.h
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ struct dtx_handle {

/* The count the DTXs in the dth_dti_cos array. */
uint32_t dth_dti_cos_count;
/* The array of the DTXs for Commit on Share (conflcit). */
/* The array of the DTXs for Commit on Share (conflict). */
struct dtx_id *dth_dti_cos;
/** Pointer to the DTX entry in DRAM. */
void *dth_ent;
Expand Down
2 changes: 1 addition & 1 deletion src/object/srv_obj.c
Original file line number Diff line number Diff line change
Expand Up @@ -2232,7 +2232,7 @@ obj_ioc_begin_lite(uint32_t rpc_map_ver, uuid_t pool_uuid,
* 2. The current replica was NOT the old leader if
* with the old pool map version. But it becomes
* the new leader with the new pool map version.
* In the subsequent modificaiton, it may hit
* In the subsequent modification, it may hit
* some 'prepared' DTX when make availability
* check, it will return -DER_INPROGRESS that
* will cause client to retry. It is possible
Expand Down
2 changes: 1 addition & 1 deletion src/placement/tests/jump_map_place_obj.c
Original file line number Diff line number Diff line change
Expand Up @@ -1188,7 +1188,7 @@ one_is_being_reintegrated(void **state)
* so find_reint() and find_addition() might both find
* some candidates if there are UP targets in the pool map,
* no matter these UP targets are from NEW or DOWNOUT.
* But reintegration and extening will never happen at the
* But reintegration and extending will never happen at the
* same time, so it is ok for now. To satisfy the test,
* let's set both reint and new number as 1 for now.
*/
Expand Down
2 changes: 1 addition & 1 deletion src/tests/ftest/util/pool_security_test_base.py
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ def modify_acl_file_entry(self, file_name, entry, new_entry):
line = line.split("\n")[0]
if line == entry:
line = new_entry
self.log.info("==>replaceing \n %s with\n %s", entry, new_entry)
self.log.info("==>replacing \n %s with\n %s", entry, new_entry)
new_permissions = new_permissions + line + "\n"
if entry is None:
new_permissions = new_permissions + new_entry + "\n"
Expand Down
2 changes: 1 addition & 1 deletion src/tests/suite/daos_base_tx.c
Original file line number Diff line number Diff line change
Expand Up @@ -294,7 +294,7 @@ dtx_fetch_committable(void **state, bool punch)

/* Reset fail_loc, repeat fetch from any replica. If without specifying
* the replica, and if fetch from non-leader hits non-committed DTX, it
* will retry with leader, finially, the expected data will be returned
* will retry with leader, finally, the expected data will be returned
* from the leader replica.
*/
daos_fail_loc_set(0);
Expand Down
2 changes: 1 addition & 1 deletion src/vos/vos_layout.h
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ enum vos_gc_type {
/** Lowest supported durable format version */
#define POOL_DF_VER_1 23

/** Individual version specific featuers are assigned to a release specific durable
/** Individual version specific features are assigned to a release specific durable
* format version number. This allows us to add multiple features in a release cycle
* while keeping checks related to the feature rather than the more ambiguous version
* number. Each new feature should be assigned to the latest VOS durable format.
Expand Down

0 comments on commit a9f9963

Please sign in to comment.