Anchor IDL Does Not Support Calling RPCs With "Numbers" In The Handler Name

[bonedaddy]

Overview

Attempting to call anchor programs that have rpcs which include a number in the handler name. Attempting to call these functions results in the fallback function error (Fallback functions are not supported. If you have a use case, please file an issue.)

For example using the following program you will be unable to call test_log_1 or test_log_2:

use anchor_lang::prelude::*;

#[program]
pub mod margin {
    use super::*;
    pub fn initialize(ctx: Context<Initialize>) -> ProgramResult {
        Ok(())
    }
    pub fn test_log_1(ctx: Context<Initialize>) -> ProgramResult {
        msg!("{}", "a");
        Ok(())
    }
    pub fn test_log_2(ctx: Context<Initialize>) -> ProgramResult {
        msg!(format!("{}", "a").as_ref());
        Ok(())
    }
}

#[derive(Accounts)]
pub struct Initialize {}

Test code:

import * as anchor from '@project-serum/anchor';

describe('margin', () => {

  // Configure the client to use the local cluster.
  anchor.setProvider(anchor.Provider.env());
    // Add your test here.
    const program = anchor.workspace.Margin;
  it('Is initialized!', async () => {
    const tx = await program.rpc.initialize();
    console.log("Your transaction signature", tx);
  });
  it("tests log 1", async () => {
    await program.rpc.testLog1();
  })
  it("tests log 2", async () => {
    await program.rpc.testLog2();
  })
});

If you change the handler names to test_log_one and test_log_two everything works:

use anchor_lang::prelude::*;

#[program]
pub mod margin {
    use super::*;
    pub fn initialize(ctx: Context<Initialize>) -> ProgramResult {
        Ok(())
    }
    pub fn test_log_one(ctx: Context<Initialize>) -> ProgramResult {
        msg!("{}", "a");
        Ok(())
    }
    pub fn test_log_two(ctx: Context<Initialize>) -> ProgramResult {
        msg!(format!("{}", "a").as_ref());
        Ok(())
    }
}

#[derive(Accounts)]
pub struct Initialize {}

test code

import * as anchor from '@project-serum/anchor';

describe('margin', () => {

  // Configure the client to use the local cluster.
  anchor.setProvider(anchor.Provider.env());
    // Add your test here.
    const program = anchor.workspace.Margin;
  it('Is initialized!', async () => {
    const tx = await program.rpc.initialize();
    console.log("Your transaction signature", tx);
  });
  it("tests log 1", async () => {
    await program.rpc.testLogOne();
  })
  it("tests log 2", async () => {
    await program.rpc.testLogTwo();
  })
});

Version

anchor-cli 0.5.0

[callensm]

this does not apply to instructions that don't have an underscore proceeding the number.

(i.e. my_ix5 workings properly, but my_ix_5 does not)

[barelooksrare]

This issue occurs whenever a token containing a single case glyph after an underscore is converted to camel case.

Any name with an underscore preceding a number will be converted to the same camel case as with no underscore preceding the number, and therefore hashed as if no underscore preceded the number e.g. do_5_times -> do5Times -> do5_times

[GuidoDipietro]

Bug that might be related:

Naming an instruction hello1a will give Error: program.methods.hello1a is not a function when calling it from the TS client.

Removing the trailing a makes it work again.

[acheroncrypto]

Fixed in #2824.