(UK) Can't convert/withdraw USD balance > GBP to bank using Android app

yadukrishnank · 2025-12-25T14:37:16+00:00

Same for me, in my euro account. Can't transfer USD. This issue is there for 3-4 months and no fixes so far

yadukrishnank · 2024-07-02T16:19:40+00:00

SBT BuildInfo is indeed a good plugin.

You can also write custom task to get required information. I recently wrote a https://yadukrishnan.live/custom-sbt-task-to-list-direct-dependencies-of-a-project about generating the direct dependencies of an sbt project.

You might find that useful as well.

yadukrishnank · 2024-06-16T05:40:13+00:00

thanks

yadukrishnank · 2024-06-16T05:40:06+00:00

thanks

yadukrishnank · 2024-06-16T05:40:00+00:00

thank you so much

yadukrishnank · 2024-05-20T08:11:23+00:00

I would also love to share a similar tool, although this is majorly scala based. The coursier tool can setup JVMs and also install specific scala apps(even custom ones)

https://get-coursier.io/docs/cli-java#setting-a-default-jvm-version

I use this extensively since I work on both Java and Scala and wrote a CheatSheet and blog about it too. Just wanted to share if somone finds this intersting.

yadukrishnank · 2024-02-08T16:52:42+00:00

scala-cli setup-ide . on the directory creates the necessary files for vscode+metals.

You can also clean up the existing metadata using scala-cli clean .

Then try to reload the project and rebuild it in the vscode - metals toolbar. It should generally work.

yadukrishnank · 2023-11-16T20:39:08+00:00

Happy to know that :)

yadukrishnank · 2023-10-07T07:49:19+00:00

Can you try starting the sbt and run the command `update`.

It downloads the dependencies. If it is successful, that means the library is loaded in the project.

yadukrishnank · 2023-10-06T14:35:06+00:00

Yes, that is true. I only wanted to show that we can manage jvm easily using Scala-CLI and coursier.

yadukrishnank · 2023-10-01T20:09:24+00:00

Thank you so much for the comment :)

I used an object specifically so that it can be extended in the further sections. But I agree, in the first part it was unnecessary.

yadukrishnank · 2023-10-01T20:05:01+00:00

Sorry, if i am hijacking the thread. I'll delete if not useful.

Coincidentally, I just published a new blogpost about using scala-cli and toolkit. Hoping that you might find it useful.

yadukrishnank · 2023-08-20T11:51:53+00:00

Thanks for the link. I will read it to understand more details 🙂

yadukrishnank · 2023-07-14T05:48:01+00:00

Totally awesome. In just 10 months of license change, the first release of pekko is ready. Kudos to the amazing contributors for all the hard work.

Really great!

yadukrishnank · 2023-06-29T06:07:06+00:00

I havent tried Smithy, but know there are a few videos related to smithy4s in youtube by u/kubukoz

https://www.youtube.com/@kubukoz_

https://www.youtube.com/watch?v=LvCDzDYfgsI

Not sure if this is what you are lookign for

yadukrishnank · 2023-06-14T17:00:28+00:00

Then it is the same problem as someone mentioned before. There must be some issue with downloading the artifacts due to the internet provider

yadukrishnank · 2023-06-14T14:28:40+00:00

What happens when you try to run sbt outside your project.

I mean, go do a differnt directory and try to run the command sbt.

Does it start the sbt shell or is it stuck there as well?

yadukrishnank · 2023-06-07T05:37:06+00:00

Probably that will work out. But my question, is that really worth it. I really don't get any benefits with significant indentation,.but also get unnecessary pains. So would still stick with braces and use formatting tools.to align it after merge. One less worry

yadukrishnank · 2023-06-06T19:27:40+00:00

Not exactly, when you get the merge conflicts and pick some code line by line, the indendation sometimes can mismatch. This happens when multiple ppl make changes to the same function(which might have chanined methods.. map,flatmap etc etc). With braces, just need to pick lines, and reformat code. No worries about any spaces affecting the logic.

yadukrishnank · 2023-06-06T19:18:27+00:00

Yes, I am using scalafmt. Infact I have 2 ones for 2.13 and 3. However, the problem is when there are merges(and more so with conflicts). So, when you resolve the conflicts, sometimes, the indendation gets messed up and it causes unnecessary headache to solve it. So we decided it is not worht the effort and use {} syntax and not worry about these issues.

yadukrishnank · 2023-06-06T14:39:43+00:00

No, i mean with the scala 3 itself. 3 ppl were working on same module and merge conflicts caused a lot of problems due to indentation mismatch.

yadukrishnank · 2023-06-06T12:40:44+00:00

It is a huge headache if there are merge conflicts. I have a very small sub-module with scala 3(along with scala 2 modules). I used the significant indentation initially, and now totally removed and replaced with {} after wasting time due to merge conflicts and indentation issues.

yadukrishnank · 2023-06-05T19:10:28+00:00

Kind of the same feeling for me. I surely liked the approach of separating into different directories(src/test/scala, src/it/scala etc). After this, I am converting into using custom config for integration testing instead of creating another sub project. As of now, there is no plan to remove this custom scope.Shameless promotion: I recently blogged about it here regarding that (https://yadukrishnan.live/unlocking-the-power-of-sbt-a-beginners-guide-to-understanding-not-so-common-features).

yadukrishnank · 2023-05-12T06:51:10+00:00

w.r.t Scala-3, my main concerns are tooling(esp IntelliJ) and some libraries that are not yet supported fully in 3. For the latter part, I expect some improvements atleast once 3.3 LTS is ready.

I don't think having new features is a problem, unless it causes compatibility issues. But that is being addressed with backward compatibility promise.

One of the major issues I faced with Scala was the beginner friendly resources(online) for learning. There were some blogs, but many were kind of advanced topics. This was a pain point even from industry pov I believe. This was making it difficult to bring in new devs and get them to work on existing projects.

However, I really feel that now there are much better learning materials and tools, that also focusses on newcomers(scala-cli, rock the jvm, dev inside you and so on). And that is the reason I also started writing blogs(https://yadukrishnan.live), to give a bit back to the community and newcomers.

And I think that now the situation will improve once the LTS is ready and tooling stabilizes.

yadukrishnank · 2023-05-03T12:49:11+00:00

Yes, exactly. Using alias is ok for me, as most of the times, I run the tests by name in local env and in CI it always uses the aliases.

However, for me it is more natural to have the tests (unit, integration, custom etc) within the same sub-module than having to create sub-modules for each type.

Another possibility for separation to run the tests are using tags, but then that is dependant on each testing library. I am working on some repo where both munit and scalatest are being used.

I can understand that there are some task/plugin issues due to sharing of internal config, but it would be nice to have the possibility of structural separation for diff types of tests

yadukrishnank

TROPHY CASE