I got this error in vscode

solana_frozen_abi_macro
proc_macro AbiExample
failed to resolve: could not find `log` in the list of imported crates
could not find `log` in the list of imported cratesrustc[E0433](https://doc.rust-lang.org/error-index.html#E0433)
conflicting implementations of trait `solana_frozen_abi::abi_example::AbiExample` for type `program::vote::authorized_voters::AuthorizedVoters`
conflicting implementation in crate `solana_frozen_abi`:
- impl<T> AbiExample for T;rustc[E0119](https://doc.rust-lang.org/error-index.html#E0119)

and also this error while build solana-client

fox:solana-client katopz$ cargo build
   Compiling rand v0.7.3
   Compiling zeroize v1.3.0
   Compiling sha2 v0.9.9
   Compiling borsh v0.9.3
   Compiling curve25519-dalek v3.2.1
   Compiling libsecp256k1 v0.6.0
   Compiling ed25519-dalek v1.0.1
   Compiling ed25519-dalek-bip32 v0.2.0
   Compiling solana-program v1.11.0
   Compiling solana-sdk v1.11.0
   Compiling solana-extra-wasm v1.11.0-alpha (/Users/katopz/git/katopz/solana-playground/wasm/utils/solana-extra)
error[E0433]: failed to resolve: could not find `log` in the list of imported crates
 --> utils/solana-extra/src/program/vote/authorized_voters.rs:7:72
  |
7 | #[derive(Debug, Default, Serialize, Deserialize, PartialEq, Eq, Clone, AbiExample)]
  |                                                                        ^^^^^^^^^^ could not find `log` in the list of imported crates
  |
  = note: this error originates in the derive macro `AbiExample` (in Nightly builds, run with -Z macro-backtrace for more info)

not sure what i miss, anyway what's rust version you have there?

Currently, the UI Console only displays Deployment Successful once the program is deployed and Deploy Program Tx Hash: in the Developer Console.

It will be great to have the Tx Hash displayed on the UI Console as well, making it easy to spot the Tx on the explorer for the dev.

failed to send transaction: Transaction simulation failed: Error processing Instruction 0: account data too small for instruction

let clock = clock::Clock::get()?; msg!("clock: {:#?}", clock);

Program deployed successfully, when i remove the above lines of code.

It works in localhost, problem with devnet.

Second tutorial which lets the developer give out sol to reward the players.

Would be super cool, if you or some anchor developer you know could review the program so that I am not teaching something wrong.

I asked a few people I know already and they said it makes sense how it is. But just to be sure.

Also do you think this is still easy or rather medium?

Did we have Docker for api for local implement?

I think we can add Run capability for simple client/helloworld.rs rust client that interact with program we already deploy. I know this may be out of scope of this project but what we have here is pretty close to rust's playground+solana create already.

FYI: I just having fun playing around here so feel free to say no. :)

Just riffing with the idea of code snippet sharing on SolPg.

• Share code snippets with a shortened URL, makes sharing small PoCs easier for devs.
• Have an option to import the code from a git repo like GitHub (May cause an issue with Anchor.toml, Cargo.toml file imports)
• Have an option to export the files from SolPg into a compressed package.

This account may not be used to pay transaction fees

use anchor_lang::prelude::*; use anchor_lang::solana_program::entrypoint::ProgramResult;

declare_id!("CLvLTsZ8seZ6E19b2FSA4B1BrumUatXiSe2RmDvbtG41");

#[program] pub mod crowdfunding { use super::*; pub fn create(ctx: Context, name: String, description: String) -> ProgramResult { let campaign = &mut ctx.accounts.campaign; campaign.name = name; campaign.description = description; campaign.amount_donated = 0; campaign.current_balance = 0; campaign.admin = *ctx.accounts.user.key; Ok(()) } pub fn withdraw(ctx: Context, amount: u64) -> ProgramResult { let campaign = &mut ctx.accounts.campaign; let user = &mut ctx.accounts.user; if campaign.admin != *user.key { return Err(ProgramError::IncorrectProgramId); } let rent_balance = Rent::get()?.minimum_balance(campaign.to_account_info().data_len());

    if **campaign.to_account_info().lamports.borrow() - rent_balance < amount {
        println!("Not enough funds");
        return Err(ProgramError::InsufficientFunds);
    }

    **campaign.to_account_info().try_borrow_mut_lamports()? -= amount;
    campaign.current_balance -= amount;

    **user.to_account_info().try_borrow_mut_lamports()? += amount;
    println!(
        "Current balance {}",
        **campaign.to_account_info().try_borrow_mut_lamports()?
    );
    Ok(())
}

pub fn donate(ctx: Context<Donate>, amount: u64) -> ProgramResult {
    let ix = anchor_lang::solana_program::system_instruction::transfer(
        &ctx.accounts.user.key(),
        &ctx.accounts.campaign.key(),
        amount,
    );

    anchor_lang::solana_program::program::invoke(
        &ix,
        &[
            ctx.accounts.user.to_account_info(),
            ctx.accounts.campaign.to_account_info(),
        ],
    );
    (&mut ctx.accounts.campaign).amount_donated += amount;
    (&mut ctx.accounts.campaign).current_balance += amount;
    Ok(())
}

} #[derive(Accounts)] pub struct Create<'info> { #[account( init, payer=user, space=9000, seeds =[b"CAMPAIGN_DEMO".as_ref(), user.key().as_ref()], bump )] pub campaign: Account<'info, Campaign>, #[account(mut)] pub user: Signer<'info>, pub system_program: Program<'info, System>, } #[derive(Accounts)] pub struct Withdraw<'info> { #[account(mut)] pub campaign: Account<'info, Campaign>, #[account(mut)] pub user: Signer<'info>, } #[derive(Accounts)] pub struct Donate<'info> { #[account(mut)] pub campaign: Account<'info, Campaign>, #[account(mut)] pub user: Signer<'info>, pub system_program: Program<'info, System>, } #[account] pub struct Campaign { pub admin: Pubkey, pub name: String, pub description: String, pub amount_donated: u64, pub current_balance: u64, } //3S9nB8j5Jod3tP74uWXKcyn1UeTSF2qykqsrTpEDNonf

Instruction index: 0 Reason: Cross-program invocation with unauthorized signer or writable account.

I have created a Counter PDA Tutorial for the Solana Playground. This will be an easy tutorial to get a better understanding of accounts, PDAs, and how basic operations work on Solana Anchor Programs.

Is designed to be an introductory tutorial, where the user will have to fill the gaps in functions following the instructions from the pages of the tutorial.

Hey there! Ajay from the Alchemy team. Given our new Solana support, I added the latest Alchemy devnet public RPC Url for Solana. Pls let me know if there are any questions, appreciate what you guys are doing at SOL Playground :) I'm definitely using your product for our tutorials!

• Update Seahorse to the latest current commit. This is pre-release, but fixes the issue that stopped it compiling in wasm
• Slight change to lib.rs because the compile signature has changed a bit. We pass a PathBuf in, it's optional but defaults to finding the current directory - which is a runtime error in wasm
• I've bumped the toolchain version. I was getting an error that 2022-06-27 doesn't exist, and it doesn't seem to be in releases. Not sure what's going on there, but I've bumped to the latest version

Note that this still doesn't give us the multi-file python imports feature that seahorse now has. We're still using compile which will only work with a single Python source file. But it brings us up to date with the latest seahorse features/fixes within that existing constraint.

Fixes #75, #86

Hi, thanks for the awesome tool!

I may be wrong in the way that I use the playground but after one or two deployments/upgrades, I started to get this error.

Create buffer error: failed to send transaction: Transaction simulation failed: This account may not be used to pay transaction fees

My workaround is to create a new wallet every time I hit this error and re-deploy the program again or to create a new program credentials before deploying again.

Thanks!

It would be nice to have all popular program ids in a constant that's globally available in playground client.

For example: PROGRAM_ID.SPL_MEMO to access spl-memo's program id.

Commandline for airdropping is "solana airdrop 2" or any value replacing 2.

But if we give any other value than integer (invalid input) , terminal gets stuck. Even clean button doesnt work since it cleans everything else other than the invalid input line.

No error message is dropped. Neither backspace , ctrl+c or enter button works.

Error :-

After cleaning terminal :-

(As you can see,there is no way to get rid of that buggy line. )

In Seahorse when using Pyth, it is an optional dependency that is enabled using anchor build -- --features pyth-sdk-solana

This enables code in the generated src/lib.rs:

    #[cfg(feature = "pyth-sdk-solana")]
    pub use pyth_sdk_solana::{load_price_feed_from_account_info, PriceFeed};

I think for Playground to compile this code we'd need to have it pass the feature flag.

I think ideally we should be able to pass features: ["pyth-sdk-solana"] to the /build server, alongside rust files + uuid, and then have the build server include this feature flag when building

One thing I'm not sure about is how dependencies work in the build server, because we don't pass cargo.toml in. I guess the build server would need to detect the pyth dependency only if that feature flag is passed in?

Playground already generates UI for interacting with programs that have Anchor IDL(either built inside playground or uploaded the file manually) but it doesn't fetch on-chain IDLs.

Playground should check the program id to see if there is an Anchor IDL on-chain. This not only would allow anyone to easily interact with all programs with on-chain IDL without manually uploading it to playground, but since playground also works with localhost, it would also make the local development experience smoother.

It would be good to have a copy button for the markdown code blocks. We are using React Markdown and the default functionality can be extended by their plugins.