sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: InternalError: too much recursion on Firefox
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://github.com/toptal-dave/nextjs-too-much-recursion

### To Reproduce

1. Install depedencies.
2. Run the `dev` task.
3. Open http://localhost:3000 in Firefox (I'm using 118.0.2, which should be latest)

### Current vs. Expected behavior

Following the steps above, without touching any code from the reproduction example, you will see an `InternalError: too much recursion` like the one screenshotted below:

![InternalError: too much recursion](https://github.com/vercel/next.js/assets/147034745/f466d451-f502-45f0-b1c2-f0f13b84946a)



### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #202307241739~1694621917~22.04~ac5e1a8 SMP PREEMPT_DYNAMIC Wed S
Binaries:
  Node: 18.18.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.9.2
Relevant Packages:
  next: 13.5.6-canary.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, CLI (create-next-app)

### Additional context

 - I've tried this on 2 different machines with 3 projects.
 - It seems to only happen with the App Router.
Repository: flutter
Issue: Provide a way of getting the flutter clock in Dart
Labels: c: new feature,framework,engine,P2,team-engine,triaged-engine

I am currently working on collecting app performance data of online users, specifically the fps and jank data for each route(page). 

The specific method involves adding a callback using` SchedulerBinding.instance?.addTimingsCallback(_computeFps) `and retrieving the **vsyncStartTime** of each frame using `curFrame.timestampInMicroseconds(FramePhase.vsyncStart)`. Then, I compare the obtained vsyncStartTime with the time of route pushing using `DateTime.now() ` and map the collected performance data to the specific route. 
 
However, I have noticed a difference in the clocks between **vsyncStartTime** and `DateTime.now()`. 

After researching [ref,](https://github.com/flutter/flutter/issues/80735) I found that timestampInMicroseconds(FramePhase.vsyncStart) retrieves a flutter clock `std::chrono::steady_clock::now().time_since_epoch()`, while DateTime.now() retrieves the clock of the DartVm. 
 
Therefore, I would like to know if there is a way to **directly get the result of steady_clock::now() in Dart code.**

ref : https://github.com/flutter/flutter/issues/85139
ref : https://github.com/flutter/flutter/issues/80735
Repository: PowerToys
Issue: Inconsistent Names when Viewed in Task Manager
Labels: Issue-Bug,Area-Build,Cost-Small,Status-Reproducible,Product-CropAndLock

### Microsoft PowerToys version

0.74.1

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

1. Have Crop And Lock and Always On Top enabled, along with any other PowerToys.
2. Open task manager.
3. Sort by name alphabetically.
4. Scroll down to 'PowerToys' and look at the application names.

### ✔️ Expected Behavior

That the names of the applications follow a consistent naming scheme, such as all following the `PowerToys.[Tool]` scheme, or `PowerToys [Tool]`.

### ❌ Actual Behavior

As shown in the image, the naming patterns of the applications Always On Top and Crop And Lock in Task Manager are inconsistent to the rest of the applications, using a space instead of a period.
![image](https://github.com/microsoft/PowerToys/assets/57434983/dfcbe644-6f38-46a2-8afa-45f22814b8bd)

This is just visual inconsistency with no impact on usage. Just noticed it so I thought to bring it up.

### Other Software

_No response_
Repository: stable-diffusion-webui
Issue: AttributeError: 'ImageDraw' object has no attribute 'multiline_textsize'[Bug]: 
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

Thank you for your excellent work！
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/66507490/3712a29e-8556-4a0f-8268-bd0c151888f5)
Multiple images cannot be generated

### Steps to reproduce the problem

choose two checkpoint name

### What should have happened?

 generate two images

### Sysinfo

a

### What browsers do you use to access the UI ?

Microsoft Edge

### Console logs

```Shell
while drawing.multiline_textsize(line.text, font=fnt)[0] > line.allowed_width and fontsize > 0:
              ^^^^^^^^^^^^^^^^^^^^^^^^^^
    AttributeError: 'ImageDraw' object has no attribute 'multiline_textsize'
```


### Additional information

_No response_
Repository: vscode
Issue: Terminal profile default discovery isn't working as expected
Labels: bug,help wanted,macos,linux,terminal-profiles

Type: <b>Bug</b>

I have followed the instructions to install fish with homebrew on my Apple Silicon mac. Fish is the default shell in any terminal and added to /etc/shells.

When starting VS Code and opening a terminal, it chooses zsh as my default. Even with forced `defaultProfile.osx` settings and overridden `profiles.osx` settings.

Fish is also not shown in the profiles list when selecting another terminal profile.

VS Code version: Code 1.83.1 (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:57:32.750Z)
OS version: Darwin arm64 23.0.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M1 (8 x 24)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (0.16GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (46)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-nginx-conf|ahm|0.3.2
github-markdown-preview|bie|0.3.0
vscode-fish|bma|1.0.37
vscode-intelephense-client|bme|1.9.5
vscode-eslint|dba|2.4.2
gitlens|eam|14.4.0
EditorConfig|Edi|0.16.4
prettier-vscode|esb|10.1.0
copy-relative-path-and-line-numbers|ezf|0.3.1
shell-format|fox|7.2.5
copilot|Git|1.126.0
copilot-chat|Git|0.8.0
todo-tree|Gru|0.0.226
prettier-sql-vscode|inf|1.6.0
vscode-just|kok|2.1.0
restructuredtext|lex|189.3.0
rainbow-csv|mec|3.7.1
dotenv|mik|1.0.1
vscode-filesize|mkx|3.1.0
vscode-docker|ms-|1.27.0
vscode-language-pack-de|MS-|1.83.2023101109
remote-containers|ms-|0.315.1
remote-ssh|ms-|0.106.5
remote-ssh-edit|ms-|0.86.0
remote-explorer|ms-|0.4.1
remote-server|ms-|1.4.3
vscode-just-php-cs-fixer|muu|0.6.2
vscode-sundial|muu|3.4.1
gremlins|nho|0.26.0
vscode-xml|red|0.26.1
vscode-yaml|red|1.14.0
git-autoconfig|shy|0.0.2
svg-preview|Sim|2.8.3
code-spell-checker|str|3.0.1
code-spell-checker-german|str|2.2.1
vscode-stylelint|sty|1.2.4
even-better-toml|tam|0.19.2
simple-rst|tro|1.5.4
sort-lines|Tyr|1.11.0
vscodeintellicode|Vis|1.2.30
vscode-swiftformat|vkn|1.6.7
vscode-icons|vsc|12.5.0
php-debug|xde|1.33.0
pretty-ts-errors|yoa|0.5.2
save-as-root|yy0|1.7.0
markdown-all-in-one|yzh|3.5.1

(1 theme extensions excluded)

</details>
<!-- generated by issue reporter -->
Repository: vscode
Issue: Diffing: Try to identify added lines
Labels: feature-request,diff-editor

![Image](https://github.com/microsoft/vscode/assets/2931520/b61a548a-9c00-474c-8a90-c847feabe35f)


[Playground Repro](https://microsoft.github.io/monaco-editor/playground.html?source=v0.45.0-dev-20231017#XQAAAAJbAwAAAAAAAABBqQkHQ5NjdMjwa-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWSxW3yscw4JAxRgmSatbNyrNa50VLHWwDOn0YI7IfU0xJ0CGYU1vRtgnKPmZzQcQ1IYSLB-5f-1dobOlrSyV9lhyCGfRXo5jrQmBvSpZ1Nvu5_93DaJZobb8dH8IEouC6qo9muLYq77M7TwUycu374dOuj9XgUPaKE4TPB1AVp7DrFcUmMMH6g0g_qUzQvAHBRFKQyum7QZVsRt1BdtTaovY67BhGFK0jvDbjKm7CoJnjpibwQ_EmBL3q3fc-hBBfa6TAni5vq_sJ2CvsnEjvdwAri3v7WmYujFecH6jCggO8fUQt8N254pNUfUpO-6L7LOV076ZBu57c0j_Dyvs1lnCzJrJXjDzFtExNXEwkDsDy5I0oIFv2-88-G8qunX72oo86ohGg4jBFIFUhr9iOQVMIP6XbZTKM8jAh-EOELqGdBeZdBnJws5U9c1WdAgQzOY0u4HceOEykST9shPpsav4K9diB9X6riI1w_4XLryw)
Repository: godot
Issue: Advanced mesh import dialogue missing parameter tooltips
Labels: bug,topic:editor,topic:3d

### Godot version

4.2beta1

### System information

Godot v4.2.beta1 - macOS 13.6.0 - Vulkan (Mobile) - integrated Apple M2 Pro - Apple M2 Pro (10 Threads)

### Issue description

When trying to fix some mesh importing issues (looks like this issue https://github.com/godotengine/godot/issues/83240) I encountered an issue I think might be a bug/oversight:

When hovering over the different import options, they don't display the appropriate tooltips, explaining what they do. It just seems like they display the current heading name, like "Meshes" (hovering the new Force Disable Compression). This seems to apply to all the controls in the advanced panel, not just this new setting. 

![Screenshot 2023-10-17 at 10 44 57](https://github.com/godotengine/godot/assets/17763524/05df6848-fd52-437f-bc1b-778bc5338422)

While if you hover the corresponding setting in the small import panel you get the appropriate tooltip (so they exist).

![Screenshot 2023-10-17 at 10 45 16](https://github.com/godotengine/godot/assets/17763524/705c9907-5565-4a15-afde-cc0f77c9420b)

I also noticed two other unexpected behaviors in this Advanced import panel, but I'm not sure if they're bugs:
- When changing a setting, the preview doesn't update to reflect this setting (which I'd assume was the point of the import panel?) For example toggling Force Disable Compression on fixes the normals in the model, but this isn't shown in the preview as you can see above.
- Clicking "Reimport" closes the panel, but the settings for the mesh in the regular small import panel aren't updated in case you've changed something (like Ensure tangents or Force Disable Compression), so it made me unsure if the changes in the Advanced import panel were applied.

### Steps to reproduce

Open the Advanced mesh import panel for a mesh. Hover over a parameter control.

### Minimal reproduction project

n/a editor interface issue
Repository: vscode
Issue: The `vscode.proposed.findTextInFiles.d.ts` proposal isn't self-contained
Labels: bug,search,confirmed

It occurred to me that you cannot consume the `src/vscode-dts/vscode.proposed.findTextInFiles.d.ts` proposal without also consuming the `src/vscode-dts/vscode.proposed.textSearchProvider.d.ts` proposal. That's because the `TextSearchQuery` is re-used. This isn't good and while we have the proposals we should copy the `TextSearchQuery` part over
Repository: godot
Issue: LightmapGI ignores ambient light when using the Scene environment mode
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

v4.1.1.stable.mono.official [bd6af8e0e]

### System information

Godot v4.1.1.stable.mono - macOS 14.0.0 - Vulkan (Forward+) - integrated Apple M1 Pro - Apple M1 Pro (10 Threads)

### Issue description

The `LightmapGI` node does not seem to pick up on ambient light set in the environment.

As a result, when using `LightmapGI` for baked lighting the scene is extra dark compared to dynamic, non-baked lighting.

**LightmapGI Hidden (Ambient light is showing)**

<img width="1799" alt="image" src="https://github.com/godotengine/godot/assets/2771466/0ae9ff26-34ab-40af-a424-b24e3ed0bba6">

**LightmapGI Shown (Clicked `Bake lightmaps`, Environment=`Scene`, Ambient light not present)**

<img width="1795" alt="image" src="https://github.com/godotengine/godot/assets/2771466/600a53d9-792c-476a-9caf-b134ddfba177">

---

The issue seems possible related to this previous issue https://github.com/godotengine/godot/issues/56138.

---

### Steps to reproduce

1. Open project
2. Open `main.tscn`
3. Observe bright ambient light shown in viewport coming from `WorldEnvironment` node
4. Toggle visibility of `LightmapGI` node
5. Bake lightmap of `LightmapGI` node to make sure it's up to date
6. Observe much darker visuals in viewport

Visual difference also observable in play mode.

### Minimal reproduction project

I couldn't upload the repro here because the environment file I'm using pushed the filesize over 25MB allowed by github.

I uploaded it to the open source [send.vis.ee](https://github.com/timvisee/send) service instead, please let me know if there is a better option. The only downside is the file will only be available for 10 downloads or 3 days, so if someone needs access I will need to re-upload it.

https://send.vis.ee/download/2925d81f52da8f12/#V6Ibyn2eYMGJDelxWsIneQ
Repository: Python
Issue: Error at `web_programming\instagram_crawler.py`
Labels: bug

### Repository commit

ac3bd1032c02ff5c2f6eb16f2bf5a1b24d106d1c

### Python version (python --version)

3.12.0

### Dependencies version (pip freeze)

beautifulsoup4==4.12.2
certifi==2023.7.22
charset-normalizer==3.3.0
colorama==0.4.6
contourpy==1.1.1
coverage==7.3.2
cycler==0.12.1
fake-useragent==1.3.0
fonttools==4.43.1
idna==3.4
imageio==2.31.5
iniconfig==2.0.0
joblib==1.3.2
kiwisolver==1.4.5
lxml==4.9.3
markdown-it-py==3.0.0
matplotlib==3.8.0
mdurl==0.1.2
mpmath==1.3.0
numpy==1.26.1
oauthlib==3.2.2
opencv-python==4.8.1.78
packaging==23.2
pandas==2.1.1
patsy==0.5.3
Pillow==10.1.0
pluggy==1.3.0
Pygments==2.16.1
pyparsing==3.1.1
pytest==7.4.2
pytest-cov==4.1.0
python-dateutil==2.8.2
pytz==2023.3.post1
requests==2.31.0
requests-oauthlib==1.3.1
rich==13.6.0
scikit-learn==1.3.1
scipy==1.11.3
setuptools==68.0.0
six==1.16.0
soupsieve==2.5
statsmodels==0.14.0
sympy==1.12
threadpoolctl==3.2.0
tweepy==4.14.0
tzdata==2023.3
urllib3==2.0.6
wheel==0.37.1
xgboost==2.0.0

### Expected behavior

I expect the instagram_crawler to fetch the Instagram user's information.

### Actual behavior

It gives an errror while fetching user information. I have tested on Windows and Ubuntu both. It gives the same error.
I have tested that it goes executes both `try` and `except` blocks and fails in both of them.
![Screenshot 2023-10-17 143621](https://github.com/TheAlgorithms/Python/assets/53044938/62303d9f-d09d-4cd4-8d2d-18d5d7cb9684)
Repository: transformers
Issue: Support reverse_prompt
Labels: WIP

### Feature request

Add a simple option to provide a stopping criteria in the generate method. This option could also be a stopping criteria.

### Motivation

Llama.cpp supports an option `--reverse-prompt`. It is very useful for chat models to stop at words like "USER:".

### Your contribution

This is how I implemented it, but it is not ideal:

```
def count_stop_words(text, stop_words):
    return Counter({expr: text.count(expr) for expr in stop_words})


class MyStoppingCriteria(StoppingCriteria):
    def __init__(self, stop_counter):
        self.stop_counter = stop_counter

    def __call__(self, input_ids, scores, **kwargs):
        # Get the generated text as a string
        generated_text = tokenizer.decode(input_ids[0])
        counter = count_stop_words(generated_text, self.stop_counter)
        if counter - self.stop_counter:
            return True
        return False

```

Then you can use this parameter:

```
            stopping_criteria=StoppingCriteriaList(
                [
                    MyStoppingCriteria(
                        count_stop_words(PROMPT, ["ASSISTANT:", "USER:", "SYSTEM:"])
                    )
                ]
            ),
```
Repository: vscode
Issue: Diffing: Improve Shifting
Labels: feature-request,diff-editor

## Description



![Image](https://github.com/microsoft/vscode/assets/2931520/49e42fa2-b140-4447-94c6-6650c8ff9816)



## Playground Example

[Monaco Editor Playground Repro](https://microsoft.github.io/monaco-editor/playground.html?source=v0.45.0-dev-20231017#XQAAAAJeBgAAAAAAAABBqQkHQ5NjdMeMm-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWdz-byd3CNqpfDYXg59SkfZBxUn-Ca9EE3-LoXKr5UWDDpr5iQrVZaDsthywfY96Baavw9pfMbsuR69ugQGTyZHczkJmqM7fpmwQ_WYT48YSArlMGqx6jfsEAWIr-6RLKtYB_cxmz57a-WQYYTmIz8uXw2YJx1Kvsd9_5-SFwemLfmZohNwonM2sX1y7AFW6aw-xEpjGxY5u996K3AJQEkvpVxO8C3syBixpR0KCvUdvowxsP5VS-ACmcxF5KZ-uWglnmTF_3IbtJ-uLZO3lrgIDqlJUUSCZ0Mm__-wIsfrPFT10y-k7TNO5_5je3HKOnhj9Ag8rw03PUo__uAHSsODDmOhqv-BwSP-9iCkcRnXLeewB09baNcboOPGMt6bd1VfuwOY19uTFh0iZmlFiUF-heQkcaBn2AG6vCM0pkCU16Q1Z_HN8jm1tOA0Hva1Kkc28WOvRjPuWx05jqvoK7kYdLeQG-GDuUBTOBXMr4tsf26Kep0mEvbbAbjRNozPHaQX3Ch-5wGcMB-aQT_WicdPLgOgS2qE1w5aoJAzSzAYyAJ8cZDC2o1oNKuuBRmEb8d5anpksKZ-4h0u_3y-Pi3YVPI10vuxRtZlV51mBANaKphDIrTHEKGPfJXD876C-m-Kox0mHcHISzLOyl4TCLhOAhOoa1VHoWhAAOAw9zVuGD9CQN_B2hMuw37AsssPfDT4uSKPXop_AwOuNtYkFWJRU1Jz_LGl_U8Gm8SrhvlIn1F3geQyKnZ78DQbWitoJw8P9453XVYNyNXh0I7BnGRdKdO5aQGkc603DsPxEudOU-x3sQz-xchT-q0npQdmcoxCI7QAmn5IKpMKLD9OuhuCZyBg_Iz3619ndjbXYVhBjNb3Pvx4W_ffCo4ZUkQRPh3VX9GECJIokqovX_VMF5AA) (click on "use latest dev" to verify a future bug-fix)
Repository: next.js
Issue: i18n domains does not match subdomaints
Labels: bug

### Link to the code that reproduces this issue

https://github.com/pavelglac/next-i18n-domains

### To Reproduce

next.config.js:

```javascript
  i18n: {
    locales: ['en', 'cs'],
    defaultLocale: 'en',
    localeDetection: false,
    domains: [
      {
        domain: 'example.com',
        defaultLocale: 'en',
      },
      {
        domain: 'example.cz',
        defaultLocale: 'cs',
      },
    ],
  },
```

1. www.example.cz will use `en` locale

### Current vs. Expected behavior

## current
www.example.cz use `en` locale

## expected
www.example.cz should use `cs` locale according [docs](https://nextjs.org/docs/pages/building-your-application/routing/internationalization#domain-routing) where provided examples according the table bellow should also match www variant.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
Binaries:
  Node: 16.18.1
  npm: 9.1.2
  Yarn: 3.5.0
  pnpm: N/A
Relevant Packages:
  next: 13.5.6-canary.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.0.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Internationalization (i18n)

### Additional context

_No response_
Repository: angular
Issue: i18n: support JSON nested translation files
Labels: feature,area: i18n,feature: insufficient votes

### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Right now, i18n supports JSON source files (fantastic, loving it).

One thing that is giving us a lot of extra work is that nested JSON does not seem to be supported.

Example: right now we have to flatten the structure, let's say we have a feature:

```
{
    "locale": "en",
    "translations": {
        "feature.title": "Lorem ipsum title",
        "feature.content": "Lorem ipsum content",
        "feature.para1": "Lorem ipsum 1",
        "feature.para2": "Lorem ipsum 2",
        "feature.para3": "Lorem ipsum 3",
        "feature.para4": "Lorem ipsum 4",
        "feature.para5": "Lorem ipsum 5",
        "feature.para6": "Lorem ipsum 6"       
    }
}
```

Ideally this should be possible instead:

```
{
  "locale": "en",
  "translations": {
      "feature": {
        "title": "Lorem ipsum title",
        "content": "Lorem ipsum content",
        "para1": "Lorem ipsum 1",
        "para2": "Lorem ipsum 2",
        "para3": "Lorem ipsum 3",
        "para4": "Lorem ipsum 4",
        "para5": "Lorem ipsum 5",
        "para6": "Lorem ipsum 6"
      }  
  }
}
```

The latter version makes it much more readable, and requires less repeated boilerplate.

Thanks

### Proposed solution

Support nested JSON language files

### Alternatives considered

Write scripts that convert nested source files, to flat versions.
Repository: material-ui
Issue: [material-ui][Tabs] How to make the scrollable button arrow transparent?
Labels: support: question,component: tabs,package: material-ui

### What's the problem? 🤔

I want to make the backgroundcolor of the arrow in the tab transparent so that I can see behind it the text hidden but I can't do it. I was able to change the color to any other color for example red, but not to set the color to transparent.

### What are the requirements? ❓

I have to make the div wrapping the arrow transparent to see the text behind it.

### What are our options? 💡

yes, but not working
<Tabs
    sx={{
      [`& .${tabsClasses.scrollButtons}`]: {
        '&.Mui-disabled': { opacity: 0 },
        '&::before, &::after': {
          content: "''",
          position: 'absolute',
          width: '100%',
          height: '100%',
          backgroundColor: 'transparent !important',
        },
      },
    }}
      value={value}
      onChange={(e, val) => void setValue(val)}
      variant='scrollable'
    >

### Proposed solution 🟢

_No response_

### Resources and benchmarks 🔗

import type { ReactElement } from 'react';
import { useState } from 'react';
import { Box, Tab, Typography, useMediaQuery, useTheme } from '@mui/material';
import Tabs, { tabsClasses } from '@mui/material/Tabs';

const MOCK_TAB_VALUES = [
  { month: 'August 2023', date: '20.08.2023' },
  { month: 'September 2023', date: '15.09.2023' },
  { month: 'October 2023', date: '20.10.2023' },
  { month: 'November 2023', date: '15.11.2023' },
  { month: 'December 2023', date: '15.11.2023' },
];

export const FormTabComponent = (): ReactElement => {
  const [value, setValue] = useState<number>(0);
  const theme = useTheme();
  const isLargeScreen = useMediaQuery(theme.breakpoints.up('lg'));

  return (
    <Tabs
    sx={{
      [`& .${tabsClasses.scrollButtons}`]: {
        '&.Mui-disabled': { opacity: 0 },
        '&::before, &::after': {
          content: "''",
          position: 'absolute',
          width: '100%',
          height: '100%',
          backgroundColor: 'transparent !important',
        },
      },
    }}
      value={value}
      onChange={(e, val) => void setValue(val)}
      variant='scrollable'
    >
      {MOCK_TAB_VALUES.map((tab, index) => (
        <Tab
          key={index}
          label={(
            <div style={{ paddingLeft: 0, paddingRight: 0 }}>
              <Typography
                variant={isLargeScreen ? 'headings.h4' : 'bodySmall.default'}
              >
                {`${tab.month.slice(0, 3)} ${tab.month.slice(-4)}`}
              </Typography>
              <br />
              <Typography variant="captions.default">
                {tab.date}
              </Typography>
            </div>
          )}
          sx={{ flexGrow: 1 }}
        />
      ))}
    </Tabs>
  );
};