Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions crates/pink/pink/src/logger.rs
Original file line number Diff line number Diff line change
Expand Up @@ -78,15 +78,15 @@ macro_rules! panic {

/// An extension for Result<T, E> to log error conveniently.
pub trait ResultExt {
/// Log the the error message with `pink::error!` with a tip `msg` in front if the Result is Err.
/// Log the error message with `pink::error!` with a tip `msg` in front if the Result is Err.
fn log_err(self, msg: &str) -> Self
where
Self: Sized,
{
self.log_err_with_level(Level::Error, msg)
}

/// Log the the error message with `level` and a tip `msg` in front if the Result is Err.
/// Log the error message with `level` and a tip `msg` in front if the Result is Err.
fn log_err_with_level(self, level: Level, msg: &str) -> Self
where
Self: Sized;
Expand Down
2 changes: 1 addition & 1 deletion crates/sidevm/host/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ sidevm-host <sideprogram.wasm>
## Push messages to the sidevm program
Sidevm programs can receive messages from the host. There are three message channels:

- message: A arbitrary message can be sent from an ink contract in the the phat contract.
- message: A arbitrary message can be sent from an ink contract in the phat contract.
- sysmessage: A message sent from the phat contract host to the sidevm program to inform some system events: ink logs, ink message outputs, ink events emitted by commands.
- query: A query is sent from a external user via a worker local RPC in the phat contract system.

Expand Down
2 changes: 1 addition & 1 deletion pallets/phala/src/phat_tokenomic.rs
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ pub mod pallet {
///
/// If users stake on a contract doesn't deployed yet. The deposit would send to the cluster
/// even if the contract is deployed later. User can re-stake with or without changing the amount
/// to sync the depoit the the cluster after the contract is actually deployed.
/// to sync the depoit the cluster after the contract is actually deployed.
#[pallet::call_index(0)]
#[pallet::weight({0})]
pub fn adjust_stake(
Expand Down
Loading