Setting up TryOptionAsync in unit tests

[speterson-zoll]

I have a data service like so:

public Task<TryOptionAsync<IEnumerable<MyData>>> GetById(IEnumerable<string> ids,
            CancellationToken cancellationToken = default)
{
  //Database operations
}

This is called by a service:

public async Task<TryOptionAsync<IEnumerable<MyData>>> GetById(IEnumerable<string> ids,
      CancellationToken cancellationToken = default)
    {
        var result = await _myRepository.GetById(ids, cancellationToken);

        return result;
    }

I have a unit test:

[Fact]
    public async Task ReturnExpected_WhenGettingById()
    {
      //Arrange
      TryOptionAsync<IEnumerable<MyData>> tryWithMyData = ryOptionAsync(Option<IEnumerable<MyData>>.Some(_myDatas));
      A.CallTo(() =>
        _myRepository.GetById(_ids, A<CancellationToken>.Ignored))
        .Returns(tryWithMyData);

      //Act
      var result = await _sut.GetById(_ids, CancellationToken.None);

      //Assert
      (await result).ShouldBeSome(x => x.Should().BeEquivalentTo(_myDatas));
    }

However, I'm getting the error:

Failure message: Value is in a bottom state and therefore not valid.  This can happen when the value was filtered and the predicate returned false and there was no valid state the value could be in.  If you are going to use the type in a filter you should check if the IsBottom flag is set before use.  This can also happen if the struct wasn't initialised properly and then used.

The result in the //Act step comes back with the TryOptionAsync in a failed state.

I looked this up but didn't find anything that directly addressed my issue. I have other methods and tests that do not deal with IEnumerable return types. In those cases, I set up my TryOptionAsync this way:

TryOptionAsync<int> _tryWithSome = TryOptionAsync(Option<int>.Some(TestReturnValue));

Tests using this setup work fine; the mock returns the expected TryOptionAsync value and all is well. I'm uncertain why my setup with an IEnumerable is an issue.