teleren/devto huggingface dataset:
Failed verify the JWT: There is no issuer named https://sts.windows/{tenant}/
Published: 2023-08-12 01:06:02

Have you ever encountered the error message "Failed to verify the JWT: There is no issuer named https://sts.windows/{tenant}/" while working on your software development project? If so, you're not alone! This error can be frustrating, but fear not, as we're here to help you understand and resolve this issue.

First, let's break down the error message. JWT stands for JSON Web Token, which is a commonly used method for securely transmitting information between parties as a JSON object. The issuer, in this context, refers to the entity that issues the JWT. In this case, the issuer is expected to be "https://sts.windows/{tenant}/".

When you encounter the error "Failed to verify the JWT: There is no issuer named https://sts.windows/{tenant}/", it means that the system couldn't find the specified issuer. This could be due to various reasons, such as a misconfiguration or an incorrect issuer value.

To resolve this issue, here are a few steps you can take:

1.  Double-check the issuer value: Make sure that the issuer value specified in your code or configuration matches the expected value. It's easy to make a typo or use an incorrect URL, so carefully review your code.
2.  Verify the issuer's existence: Ensure that the issuer URL is valid and accessible. You can try opening the URL in a web browser to see if it loads without any issues.
3.  Check the authentication provider: If you're using a third-party authentication provider, such as Azure Active Directory, make sure that it is properly configured and integrated with your application. The issuer value might be different depending on the provider.
4.  Review the documentation: Consult the documentation or support resources of the library or framework you're using for JWT authentication. They might have specific guidelines or troubleshooting steps for handling this error.

Remember, debugging software issues can sometimes be a bit like searching for a needle in a haystack. So, don't forget to keep your sense of humor intact! As Albert Einstein once said, "The only way to escape the corruptible effect of praise is to go on working." So, keep calm, stay focused, and keep coding!

References:

*   [JSON Web Tokens - jwt.io](https://jwt.io/)
*   [Quickstart: Add sign-in with Microsoft to an ASP.NET Core web app](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v2-aspnet-core-webapp)
Android Studio 2022.3.1 (Mac Intel) cannot create Flutter projects
Published: 2023-08-12 01:03:07

Are you an Android developer using a Mac Intel machine and facing issues with creating Flutter projects on Android Studio 2022.3.1? Well, you are not alone! Many developers have encountered this peculiar problem, and we are here to shed some light on the issue and provide possible solutions.

Android Studio 2022.3.1 is a popular Integrated Development Environment (IDE) used by developers worldwide. However, it seems that the latest version has a glitch when it comes to creating Flutter projects on Mac Intel machines. It's like trying to fit a square peg into a round hole - it just doesn't work!

So, what can you do if you find yourself in this predicament? Don't worry; we've got your back! Here are a few possible workarounds to get you back on track:

1.  **Try using an older version of Android Studio:** Sometimes, the latest version of a software comes with unforeseen bugs. You can try downgrading to a previous version of Android Studio that is known to work well with Flutter projects. Just be careful not to go too far back, or you might miss out on some exciting new features!
2.  **Use a different IDE:** While Android Studio is the go-to IDE for Android development, there are other options available. You can try using Visual Studio Code with the Flutter extension or IntelliJ IDEA with the Flutter plugin. These IDEs have proven to be reliable alternatives for Flutter development.
3.  **Seek help from the Flutter community:** The Flutter community is known for its helpfulness and camaraderie. If you're stuck, reach out to the community through forums, social media groups, or even the official Flutter Slack channel. Chances are, someone has encountered the same issue and found a workaround or solution.

Remember, software development can sometimes feel like a roller coaster ride with unexpected twists and turns. But don't let a little bug dampen your spirits! Keep your sense of humor intact, and you'll conquer any challenge that comes your way.

In conclusion, if you're using Android Studio 2022.3.1 on a Mac Intel machine and struggling to create Flutter projects, don't panic. Try one of the workarounds mentioned above, and you'll be back to coding Flutter apps in no time. Happy coding, and may the bugs be forever in your favor!

References:
-----------

*   Official Android Studio Documentation: [https://developer.android.com/studio](https://developer.android.com/studio)
*   Flutter Community: [https://flutter.dev/community](https://flutter.dev/community)
*   Visual Studio Code: [https://code.visualstudio.com/](https://code.visualstudio.com/)
*   IntelliJ IDEA: [https://www.jetbrains.com/idea/](https://www.jetbrains.com/idea/)
Failed verify the JWT: There is no issuer named https&#58;&#47;&#47;sts.windows&#47;{tenant}&#47;
Published: 2023-08-12 01:02:09

Failed to Verify the JWT: There is no issuer named https://sts.windows/{tenant}
-------------------------------------------------------------------------------

In the world of software development, encountering errors and issues is a common occurrence. One such error that developers often come across is the "Failed to Verify the JWT: There is no issuer named https://sts.windows/{tenant}". While the error message may sound cryptic and confusing, fear not! In this article, we will delve into what this error means, its possible causes, and how to resolve it.

### Understanding the Error

JWT, short for JSON Web Token, is a compact and self-contained way of securely transmitting information between parties as a JSON object. It consists of three parts: a header, a payload, and a signature. The error message "Failed to Verify the JWT: There is no issuer named https://sts.windows/{tenant}" indicates that the issuer specified in the token cannot be found or recognized.

### Possible Causes

There can be several reasons why this error occurs. One possibility is that the token was issued by a different issuer than the one expected by the system. It could also be due to a misconfiguration in the system settings or a problem with the token itself.

### Resolving the Issue

To resolve the "Failed to Verify the JWT" error, you can follow these steps:

1.  Double-check the issuer: Ensure that the issuer specified in the token matches the expected issuer. Typos or incorrect URLs can often be the culprit.
2.  Verify system configuration: Check the system settings and configuration to ensure that the expected issuer is correctly configured.
3.  Validate the token: Use a JWT library or tool to validate the token and ensure it is well-formed and contains the necessary information.
4.  Check token generation: If you are responsible for generating the tokens, ensure that the issuer is correctly set during the token creation process.

Remember, debugging errors can be a frustrating task, but keeping a sense of humor can lighten the mood. As software developers, we often encounter issues that make us scratch our heads in confusion. Just like a programmer trying to fix a bug, let's approach this error with a smile and a cup of coffee!

### Conclusion

The "Failed to Verify the JWT: There is no issuer named https://sts.windows/{tenant}" error can be a tricky one to tackle. However, armed with the knowledge of what the error means and the possible causes, you can now confidently troubleshoot and resolve this issue. Remember to double-check the issuer, verify system configuration, validate the token, and review token generation. Happy coding!

### References

*   JWT Official Website: [https://jwt.io/](https://jwt.io/)
*   Microsoft Identity Platform Documentation: [https://docs.microsoft.com/en-us/azure/active-directory/develop/](https://docs.microsoft.com/en-us/azure/active-directory/develop/)
Failed verify the JWT: There is no issuer named https://sts.windows/{tenant}/
Published: 2023-08-12 00:59:46

Failed verify the JWT: There is no issuer named https://sts.windows/{tenant}/
-----------------------------------------------------------------------------

When working on software development projects, encountering errors and bugs is inevitable. One such error that developers often come across is the infamous "Failed verify the JWT: There is no issuer named https://sts.windows/{tenant}/". This error can be frustrating and time-consuming to troubleshoot, but fear not! In this article, we will delve into the causes of this error and explore possible solutions.

### Understanding the Error

The error message indicates that the JSON Web Token (JWT) verification process failed because the specified issuer, which in this case is "https://sts.windows/{tenant}/", could not be found. The issuer is an important component of JWT as it identifies the entity that issued the token.

### Possible Causes

There are several reasons why this error may occur:

*   The issuer URL is incorrect or misspelled.
*   The issuer URL is not registered or recognized by the system.
*   The JWT token is malformed or tampered with.
*   There is an issue with the authentication or authorization process.

### Solutions

Now that we understand the possible causes, let's explore some solutions to resolve this error:

1.  Double-check the issuer URL: Ensure that the issuer URL is correct and matches the expected format. It should be in the form of "https://sts.windows/{tenant}/".
2.  Verify issuer registration: If the issuer URL is correct, make sure that it is registered and recognized by the system. Contact the appropriate authorities or administrators to ensure the issuer URL is properly registered.
3.  Check JWT token integrity: Validate the integrity of the JWT token. Ensure that it is not malformed or tampered with. You can use libraries or tools to decode and verify the token.
4.  Review authentication and authorization process: Examine the authentication and authorization process to identify any potential issues. Check if the correct authentication mechanisms are in place and if the necessary permissions are granted.

### Conclusion

Encountering the "Failed verify the JWT: There is no issuer named https://sts.windows/{tenant}/" error can be frustrating, but with the right approach, it can be resolved. By double-checking the issuer URL, verifying issuer registration, checking token integrity, and reviewing the authentication and authorization process, developers can overcome this error and ensure the smooth functioning of their software.

### References

*   JWT.io - JSON Web Tokens: [https://jwt.io/](https://jwt.io/)
*   Microsoft Identity Platform Documentation: [https://docs.microsoft.com/en-us/azure/active-directory/develop/](https://docs.microsoft.com/en-us/azure/active-directory/develop/)
A simple portfolio template for developer/designers built with React
Tags: portfoliopage
Published: 2023-08-12 20:10:24

---
title: A simple portfolio template for developer/designers built with React
published: true
date: 2023-08-12 00:43:00 UTC
tags: PortfolioPage
canonical_url: https://reactjsexample.com/a-simple-portfolio-template-for-developer-designers-built-with-react-2/
---

### Description
 ![A simple portfolio template for developer/designers built with React](https://reactjsexample.com/content/images/2023/08/code_2023-11-11-38-26.jpg)

A simple portfolio template for developer/designers built with React.

![A simple portfolio template for developer/designers built with React](https://github.com/Duerme/cybersecurity-portfolio-webpage/raw/main/src/assets/images/page.gif)

### Setup

**Install the git repo**

```
git clone https://github.com/Duerme/cybersecurity-portfolio-webpage.git
```

**Install yarn**

Install yarn to test and build the website. You can use the link [here](https://classic.yarnpkg.com/lang/en/docs/install/).

**Install required dependencies**

```
yarn install
```

**Start the server**

```
yarn start
```

**Build the web-page**

```
yarn build
```

### More

Modify pages content in `src/content_option.js`.

### Thanks!

Like the page? Leave a ⭐!

## GitHub

[View Github](https://github.com/Duerme/cybersecurity-portfolio-webpage?ref=reactjsexample.com)
Exploring React Native
Tags: reactnative, react, javascript
Published: 2023-08-12 08:36:33

---
title: Exploring React Native
published: true
date: 2023-08-12 00:00:00 UTC
tags: reactnative, react, javascript
canonical_url: https://www.maxphillips.dev/blog/exploring-rn/
---

How does React Native, _React Native??_

React Native is a pretty cool tool, although when learning it I encountered a rather strange difficulty curve:
![](https://www.maxphillips.dev/rn-frustration.png)

Yeah, a bit strange :(

While this curve is just my own experience with React Native, I like to think I am not alone in this. Upgrades in particular [were listed as the number one pain point for React Native developers in the _State of React Native_ survey,](https://results.stateofreactnative.com/opinions/#opinions_pain_points) with debugging coming in second. More recent tools in the React Native ecosystem (such as [Expo](https://expo.dev/)) even seem designed to directly address these sorts of issues.

The truth is that React Native feels kind of magical to use, and that is both a blessing and curse. Writing app logic in React and being able to run it on a mobile device it awesome, but if you stray too far off the beaten path you might start to encounter weird bugs and need to use dark spells like `BatchedBridge.spy()`, `UIManager.dispatchViewManagerCommand()`, or even [`React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED;`](https://github.com/facebook/react-native/blob/9f7dfcc35ff603de42cfa5e3fa63701916a86784/packages/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js#L37C4-L37C4) to patch them up. (ok maybe not that last one)

As someone who came from the web dev side of things I was pretty reluctant to touch native code at first, but after working with it for a bit I gotta say it has helped make those earlier pain points a lot less annoying to deal with. Logbox errors seem less esoteric, upgrades seem (just a bit) less scary, and when something breaks it has made it a lot easier to know where to start looking.

Anyway, that's enough preamble :) The main reason I made this post is because I wanna start sharing some of this weird React Native stuff on this blog, and I reckon a neat infographic would be a good place to start.

Please let me know in the comments below what you think (or if I goofed anything up lol), and if you enjoyed it then check back soon for a follow up where I wanna cover some stuff about the React Native Bridge system :)
![](https://www.maxphillips.dev/rn-intro.png)
Reflexionando sobre el mundo del código
Tags: webdev, programming, productivity, career
Published: 2023-08-12 00:25:38

Hola #readers, espero que estén muy bien, yo estoy saliendo de unas semanas muy atareadas del trabajo, en las que hemos estado creando un servicio core para nuestra aplicación móvil, [por cierto pueden bajarla en la App Store o Google Play.](https://www.fintonic.mx/es-MX/inicio/)

En esta ocasión vengo a escribir acerca de unas ideas locas que se me ocurrieron mientras estaba por empezar un pequeño freelance para un cliente y creo que te pueden ser útiles. Son pequeños puntos que recopilé que me ayudan a poder completar una tarea o incluso enfrentarme con un proyecto nuevo y no estar teniendo ese pequeño dilema de si usar una tecnología sobre otra, o que si la base de datos X es mejor que otra, ya saben dilemas de la vida.

## Software más allá del código.

No es solo escribir las líneas más optimizadas o seguir los estándares al pie de la letra. Es sobre cómo podemos hacer una diferencia real en la vida de las personas. Cada vez que escribimos código, estamos creando soluciones. Nunca olvides eso.

## La perspectiva del usuario.

Mientras estamos sumergidos en patrones de diseño, pruebas y arquitecturas, al final del día, nuestros usuarios solo quieren algo que funcione. Así que, si alguna vez te encuentras en el dilema de optar por la última versión de una tecnología o hacer que algo simplemente funcione para el usuario, ya sabes qué elegir.

## Encuentra el balance con tus clientes.

Sabemos que a veces puede ser complicado. Pero, ¿sabes? Ni tú ni ellos tienen siempre la razón. La clave está en encontrar un término medio donde ambos se sientan satisfechos.

## Las montañas y valles de ser programador.

Hay días en los que todo fluye, y hay otros en los que quisieras tirar tu computadora por la ventana. Es parte del viaje, y es lo que hace que nuestra profesión sea única y apasionante.

Pues bueno, espero te haya gustado este pequeño post, ¿tienes otras ideas que te ayudan a ser mejor? Te veo en Twitter(X) o en los comentarios 😃 [@fromchiapasdev](https://twitter.com/devfromchiapas)
Preview Geometry Nodes on web using React
Tags: graph
Published: 2023-08-12 20:10:44

---
title: Preview Geometry Nodes on web using React
published: true
date: 2023-08-12 00:14:00 UTC
tags: Graph
canonical_url: https://reactjsexample.com/preview-geometry-nodes-on-web-using-react/
---

 ![Preview Geometry Nodes on web using React](https://reactjsexample.com/content/images/2023/08/code_2023-08-23-08-46.jpg)

![Preview Geometry Nodes on web using React](https://github.com/whoisryosuke/geometry-node-graph/raw/main/docs/screenshot.png)

# Geometry Node Graph

Preview Geometry Nodes on web using React

## Getting Started

1. Clone this project: `git clone https://github.com/whoisryosuke/geometry-node-graph.git`
2. Install dependencies: `yarn`
3. Start the dev server: `yarn dev`

Open the app in your web browser, you should see a node graph.

## Previewing your nodes

This app works by using JSON files with geometry node data exported from Blender using a custom plugin (TBD). But I included the WIP script below, it should work to export some basic graphs (haven’t tested stuff like custom nodes, groups, etc).

1. Save your file somewhere.
2. Select the object with the geometry nodes modifier.
3. Go to the Scripting tab in Blender (or change one of the windows to scripting)
4. Create a new script (click the “New” button on top of window)
5. Paste in [the script from here](https://github.com/whoisryosuke/geometry-node-graph/blob/main/scripts/export-geometry-nodes.py)
6. Run the script.
7. Look inside the folder where your file is saved, you should a JSON file
8. Copy and paste that JSON file into the `src/data/` folder of this app.
9. Open up the `src/App.tsx` and swap your JSON filename for the one imported in there.
10. Hard refresh the browser/app to see changes.

## How it works

This app uses react-flow to display the node graph. It provides a lot of nice stuff out of the box, like the zooming and panning.

The nodes are generated from a JSON file that is exported from Blender using a custom Python script. It basically reads the geometry node data and creates a JSON file with the data.

> Interested in learning more? [Check out my blog](https://whoisryosuke.com/blog), where I break down how this works.

## Release

1. Bump version in `package.json`
2. `yarn build`
3. `npm publish`

## GitHub

[View Github](https://github.com/whoisryosuke/geometry-node-graph?ref=reactjsexample.com)
GKE multi-arch guide
Tags: cloud, arm64, kubernetes
Published: 2023-08-11 23:00:08

I came across [this fabulous resource from SADA](https://github.com/sadasystems/gke-multiarch-guide) on working with Arm64 CPUs (powered by Ampere Altra) on Google Compute. The repo goes into a lot of detail around all aspects of running Kubernetes applications on Arm64, including:

- Using Google Cloud Build to build containers containing your application for multiple architectures
- Provisioning a heterogeneous x86/aarch64 GKE cluster
- Scheduling containers to run on a specific architecture

This is an excellent resource for getting started with GKE and multi-arch containers! The next step after this tutorial would be to deploy a cloud native application like a containerized WordPress deployment into your hybrid cluster.

You can find more information about using GitHub Actions to build multi-arch containers from scratch [on the SADA blog](https://engineering.sada.com/shipping-multi-platform-docker-images-for-arm-on-google-cloud-with-github-actions-e80d03ea83df).
DWS Web Tools 🔨
Tags: webtools, webdev, api, dakidarts
Published: 2023-08-11 22:54:01


![Image description](https://cdn.dakidarts.com/image/11231517/DWS-KID-BP.jpg)

Hey there, digital dynamos and cyber sorcerers! Are you tired of the World Wide Wait and ready to wield some serious web magic? Well, saddle up your virtual broomsticks because [DWS Web Tools](kit.dakidarts.com) is here to turn your online journey into an enchanted adventure!

Let's face it, navigating the digital realm can feel like deciphering an ancient spell book written in code. But fear not, dear netizens, for DWS Web Tools has your back! Our collection of enchanting online utilities is designed to empower you with the prowess of a wizard and the finesse of a hacker (minus the dark side, of course).

Remember, in the grand tapestry of the internet, you're the master weaver, and DWS Web Tools is your loom of enchantment. Embark on this adventure at [kit.dakidarts.com](kit.dakidarts.com), and let's conjure some digital marvels together!

**P.S.** No dragons were harmed in the making of these tools – we promise!😎