sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Rust 1.81-nightly slower than Rust 1.79 ?
Labels: I-slow,O-macos,P-medium,C-bug,A-mir-opt-inlining,regression-untriaged,S-has-mcve,O-AArch64

Hi,

I've build my rust project with Rust 1.79 and now test with Rust 1.81 nightly.

I observe slower runtime.

This project is about parsing text files with polars.
Cargo.toml is the same in both context.

## With Rust 1.79

```sh
# cargo build release with 1.79.0
cargo +1.79.0 build --release      
...

# benchmark on release run 
bench ./target/release/pmsi_rust   
benchmarking ./target/release/pmsi_rust
time                 236.9 ms   (226.6 ms .. 249.0 ms)
                     0.998 R²   (0.991 R² .. 1.000 R²)
mean                 232.1 ms   (228.1 ms .. 236.8 ms)
std dev              5.880 ms   (3.339 ms .. 8.859 ms)
variance introduced by outliers: 14% (moderately inflated)
```

## With Rust 1.81

```sh
# With 1.81 version
% cargo --version      
cargo 1.81.0-nightly (bc89bffa5 2024-06-22)
# build release with 1.81
% cargo build --release           
...
# benchmark on release run
% bench ./target/release/pmsi_rust
benchmarking ./target/release/pmsi_rust
time                 614.8 ms   (528.0 ms .. 710.4 ms)
                     0.997 R²   (0.989 R² .. 1.000 R²)
mean                 644.2 ms   (622.9 ms .. 664.8 ms)
std dev              25.50 ms   (11.26 ms .. 31.11 ms)
variance introduced by outliers: 19% (moderately inflated)
```

It's an issue just to keep trace of this observation, is this feedback something you've encountered before?
Maybe it's just normal as 1.81 is a beta.


If not, I can make a reproducible example I think.

Thanks
Repository: tensorflow
Issue: bucketize -function wrong results on GPU
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

2.18.0-dev20240624

### Custom code

No

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Bucketize function returns wrong results when executed on GPU.   

Tested with  2.9.3, 2.15.0 and 2.18.0-dev20240624 and observed same incorrect behavior.

See the example below.   The CPU and GPU results are different so both can't be correct. GPU result seems to be wrong.

Can reproduce in [colab](https://colab.research.google.com/drive/1hSHgt5f31eUG-OsAy0FJ0zlcBhMgPV-c?authuser=0#scrollTo=nCDoKVOFw3ML)





### Standalone code to reproduce the issue

```shell
from tensorflow.python.ops.gen_math_ops import bucketize
import tensorflow as tf

print(tf.__version__)
gpus = tf.config.list_physical_devices('GPU')
assert gpus

x = [0,1,2,3]
boundaries = [0.1, 1.1]
with tf.device("/CPU:0"):
    print(bucketize(x, boundaries=boundaries))
with tf.device("/GPU:0"):
    print(bucketize(x, boundaries=boundaries))
```


### Relevant log output

```shell
2.18.0-dev20240624
tf.Tensor([0 1 2 2], shape=(4,), dtype=int32)
tf.Tensor([1 2 2 2], shape=(4,), dtype=int32)
```
Repository: material-ui
Issue: [joy-ui] When using styled('div') all its properties are lost
Labels: on hold,package: joy-ui

Hello!
When using the latest version of joy-ui (5.0.0-beta.36), I encountered a problem. When I try to styled('div') a component, all the component properties are lost, and the component itself becomes any. I tried on other versions, this problem starts around version 5.0.0-beta.20. I couldn't find any information about this anywhere. This looks more like a bug, but what could be the reason?

### Steps to reproduce

Link to live example: (required)

Steps:
1. Create a styled div component.
![image](https://github.com/mui/material-ui/assets/113048205/c5788cbf-8979-4751-8b15-781c6779983e)
3. Use it somewhere.
5. We see that the component itself becomes of the any type, and has no more properties.
![image](https://github.com/mui/material-ui/assets/113048205/398f89fc-9c2d-46e7-8ab7-4674d5dffccf)
![image](https://github.com/mui/material-ui/assets/113048205/c4314137-f933-4e9c-8707-90d0b1598bfd)



### Current behavior

Properties and type of styled component are lost

### Expected behavior

Properties and type styled of the component are displayed correctly

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 20.12.2 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Edge: Chromium (126.0.2592.68)
    @mui/system:  6.0.0-dev.240424162023-9968b4889d
    @mui/types:  7.2.14
    @mui/utils:  6.0.0-dev.20240529-082515-213b5e33ab
    @types/react: 18.0.28 => 18.0.28
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 5.4.5 => 5.4.5
</details>



**Search keywords**: joy-ui, material-ui, styled, div
Repository: storybook
Issue: [Bug]: Can't build storybook after setCustomElementsManifest
Labels: bug,help wanted,web-components

### Describe the bug

Using the open-wc project template for a LitElement project that includes a Storybook setup (using `@storybook/web-components`), after adding configuration to generate autodocs from the custom-elements.json, the project is unable to run `storybook build` to generate a static version of the site. It fails with the following error:

> RollupError: Expected ';', '}' or <eof>
    at Object.getRollupError (./node_modules/rollup/dist/shared/parseAst.js:282:41)
    at ParseError.initialise (./node_modules/rollup/dist/shared/rollup.js:12774:40)
    at convertNode (./node_modules/rollup/dist/shared/rollup.js:14524:10)
    at convertProgram (./node_modules/rollup/dist/shared/rollup.js:13841:12)
    at Module.setSource (./node_modules/rollup/dist/shared/rollup.js:15681:24)
    at async ModuleLoader.addModuleSource (./node_modules/rollup/dist/shared/rollup.js:19983:13)

### Reproduction link

https://github.com/jwynveen/open-wc-custom-elements-repro

### Reproduction steps

1. Clone the above repo
2. Install npm modules (`npm install`)
3. Run storybook in dev mode to confirm that autodocs are generated and include element attributes from custom-elements.json ('npm run storybook`)
4. Close dev storybook
5. Run storybook build (`npm run storybook:build`)
6. 

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.4.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.0 - ~/.nvm/versions/node/v20.12.0/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.0/bin/npm <----- active
  Browsers:
    Chrome: 126.0.6478.126
    Safari: 17.4.1
  npmPackages:
    @storybook/addon-a11y: ^7.6.20 => 7.6.20 
    @storybook/addon-essentials: ^7.6.20 => 7.6.20 
    @storybook/addon-links: ^7.6.20 => 7.6.20 
    @storybook/web-components: ^7.6.20 => 7.6.20 
    storybook: ^7.6.20 => 7.6.20
```


### Additional context

This repo was generated from the open-wc template using the following process:

1. Init project: `npm init @open-wc`
    - Scaffold a new project
    - Web Component
    - Select all options to include (linting, testing, demoing)
    - Typescript: no
    - name: open-wc
    - install dependencies with NPM
2. Setup autodocs
    - Update `.storybook/main.js`
    - ```
      const config = {
        ...
        docs: {
          autodocs: true,
        },
        addons: [
          '@storybook/addon-essentials',
          '@storybook/addon-links',
        ],
        ...
      }
      ```
    - Follow setup instructions from https://github.com/storybookjs/storybook/blob/v7.6.19/code/addons/docs/web-components/README.md to add `.storybook/preview.js` file with reference to `custom-elements.json`
    - ```
      import { setCustomElementsManifest } from '@storybook/web-components';
      import customElements from '../custom-elements.json' with { type: "json" };
      setCustomElementsManifest(customElements);
      ```
Repository: PowerToys
Issue: High memory usage - Run, PowerAccent, ColorPickerUI
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.81.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Memory leak PowerToys. Software is running in background and opens on startup. Not had these issues before. Restarted Powertoys and computer but same issue everytime.

### ✔️ Expected Behavior

Relatively low memory usage from PowerToys - colleague has less 100Mb usage for PowerToys run

### ❌ Actual Behavior

![Screenshot 2024-06-25 121100](https://github.com/microsoft/PowerToys/assets/173795618/fa14e497-89e1-4537-be92-72ee69ffcf39)

Memory usage for PowerToys Run, PowerAccent, ColorPickerUI in way to high for each - almost a GB. Please can this be investigated


### Other Software

N/A
Repository: TypeScript
Issue: Type 'any' cannot be used as an index type silently fails when used in generics (TS2538)
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

TS2538 ts2538 silently fails

### 🕗 Version & Regression Information


- This is the behavior in every version I tried, and I reviewed the FAQ for entries about ts2538


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.5.2#code/C4TwDgpgBAsiAq5oF4oG0DeAzA9jgXFAM7ABOAlgHYDmAvgLpQA+UGARgIamGUCuAtmwilaAbgBQ4gPRSo8ABbkiUYaRyllAd3LB5UUJCgByDpRBGoAY1OUcwKEKi8iEACZQOy01CquIAD30kcQNoAGV5HF4AG1cAUVI1UihUOERINFMQeglpWQUlKFccCGVbe1V1D0p3InJoiEpgaJArUggOYFLq6pAQpCgAERwwnH4IXSpqAB54FX8umuU0pAA+FLlMsxz+wwB1euiAIQgAQTMN4dHxyZpplchV0SA

### 💻 Code

```ts
type MyType = [{foo: string}] | {bar: number};

// This errors with type 'any' cannot be used as an index type
type ShouldError = MyType[any];

// This does not error and silently creates an any
type DoSomething<T extends MyType> = T[any];
type WillBeAny = DoSomething<MyType>;
```


### 🙁 Actual behavior

When using a generic type, typescript fails to error with error TS2538 which should say that `type 'any' cannot be used as an index type`, instead, it does not errors and silently turns the type indexed in `[any]` to a any itself.

### 🙂 Expected behavior

I would expect typescript compilation to fail as it does when you directly access a type with any (in the example above as `MyType[any]` )

### Additional information about the issue

This seems to be an issue from all versions I tested (several > 3.3). But I did not found an issue acknowledging this is either expected or indeed a bug.
Repository: vscode
Issue: Hover accessible view shows icons as space
Labels: bug,editor-hover

Testing #217237

<img width="621" alt="image" src="https://github.com/user-attachments/assets/a0eb712f-a15b-4268-a996-0c23f5be299b">

I don't know what the norm is for screen readers, but it might be nice to have something other than "space" read when keying to an icon.
Repository: vscode
Issue: SCM Graph - history item context menu actions
Labels: feature-request,scm

It would be really nice if the SCM commit graph would have a context menu with actions such as
- Checkout Commit
- Revert Commit
- Reset Commit
- Maybe contributable ones (open commit on github, ...)
- Share
- . . .
Repository: go
Issue: x/sys/windows: add some missing SetupAPI functions
Labels: OS-Windows,NeedsFix

### Proposal Details

At least the following functions are missing from the x/sys/windows package:
- SetupDiEnumDeviceInterfaces
- SetupDiGetDeviceInterfaceDetail
- SetupDiGetDeviceInterfacePropertyKeys
- SetupDiGetDeviceInterfaceProperty

I originally wanted to implement these functions myself. Before calling the `SetupDiGetDeviceInterfaceDetail` function, it is necessary to set the size for the `size` member of the `windows. DevInfoData` structure. However, the `size` member of the `windows. DevInfoData` structure was not exported.
Repository: electron
Issue: [Bug]: Use input in the webview tag. The selected content moves left away from webviw, and the cursor is abnormal
Labels: platform/windows,bug :beetle:,22-x-y,stale,29-x-y,30-x-y,33-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

22.3.2

### What operating system are you using?

Windows

### Operating System Version

Windows10

### What arch are you using?

x64

### Last Known Working Electron version

1.0.0

### Expected Behavior

The cursor in the input field moves backward

### Actual Behavior

When using the webview label, if the Input box is used, if I move the selected input content from the right side to the left side and move it to the outside of the webview boundary, I find that the cursor in the input box keeps moving to the leftmost side, then the input 123 will change to 321 I still have this problem with the latest electron version, please ask if there is a good solution

### Testcase Gist URL

_No response_

### Additional Information

![111](https://github.com/electron/electron/assets/50290023/3a93d1e6-0911-40a8-9963-d75251ab9e3a)
Repository: ui
Issue: [bug]: Landing page crashes when examples > forms > account >  language selection dropdown clicked.
Labels: bug

### Describe the bug

UI breaks with following errors on https://ui.shadcn.com. Not issue with any components.
<img width="1512" alt="image" src="https://github.com/shadcn-ui/ui/assets/94426452/ab44a5d5-d53c-4afd-b4f1-ecc76f298ab1">


This happens due to `CommandItem` component


### Affected component/components

Dropdown/Select or `CommandItem`. 

Works fine when h2 or other element is used.
<img width="636" alt="image" src="https://github.com/shadcn-ui/ui/assets/94426452/b7590c60-7c1f-42a1-9b0b-92053426690d">


### How to reproduce

1. Go to https://ui.shadcn.com/
2. From examples section click the following:
<img width="1512" alt="image" src="https://github.com/shadcn-ui/ui/assets/94426452/713d1194-bd99-47e6-8899-fc6c57afa6e3">
3. Open console to see error as suggested:
<img width="1512" alt="image" src="https://github.com/shadcn-ui/ui/assets/94426452/b0f0677f-ace8-4f18-ae45-61157bb88d29">



### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
TypeError: items is undefined
    NextJS 12
97525-01e51dd4c392194a.js:1:5105
    NextJS 66
The resource at “https://ui.shadcn
```

#### On local:
```bash
react-dom.development.js:20702 Uncaught 
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at Function.from (<anonymous>)
    at A (index.mjs:20:4277)
    at U (index.mjs:20:3290)
    at eval (index.mjs:20:2050)
    at eval (index.mjs:20:13055)
    at Map.forEach (<anonymous>)
    at eval (index.mjs:20:13044)
    at commitHookEffectListMount (
```


### System Info

```bash
Mozilla Firefox v 127.0.1 on Macbook M2
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: storybook
Issue: [Bug]: Failed to resolve import
Labels: bug,needs triage

### Describe the bug

Hello

I'm using storybook version 7.6.19. When running `storybook dev` command storybook dev, I get following runtime error:
```
[vite] Pre-transform error: Failed to resolve import "C:UsersUserprogect
eact" from "../../../../virtual:/@storybook/builder-vite/vite-app.js". Does the file exist?

Plugin: vite:import-analysis
  File: /virtual:/@storybook/builder-vite/vite-app.js:3:32
  1  |  // Ensure that the client API is initialized by the framework before any other iframe code
  2  |      // is loaded. That way our client-apis can assume the existence of the API+store
  3  |      import { configure } from 'C:\Users\User\project\node_modules\@storybook\react';
     |                                 ^
  4  |
  5  |      const { logger } = __STORYBOOK_MODULE_CLIENT_LOGGER__;
    at formatError (file:///C:/Users/User/project/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:52003:46)
      at TransformContext.error (file:///C:/Users/User/project/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:51997:19)
      at normalizeUrl (file:///C:/Users/User/project/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:67300:33)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async file:///C:/Users/User/project/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:67455:47
      at async Promise.all (index 0)
      at async TransformContext.transform (file:///C:/Users/User/project/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:67376:13)
      at async Object.transform (file:///C:/Users/User/project/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:52312:30)
      at async loadAndTransform (file:///C:/Users/User/project/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:55067:29)
      at async viteTransformMiddleware (file:///C:/Users/User/project/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:64914:32)
```

### Reproduction link

-

### Reproduction steps

_No response_

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 AMD Ryzen 5 5600H with Radeon Graphics
  Binaries:
    Node: 20.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers:
    Edge: Chromium (126.0.2592.68)
  npmPackages:
    "@storybook/addon-essentials": "7.6.19"
    "@storybook/addon-interactions": "7.6.19"
    "@storybook/addon-links": "7.6.19"
    "@storybook/addon-onboarding": "^1.0.11"
    "@storybook/blocks": "7.6.19"
    "@storybook/react": "7.6.19"
    "@storybook/react-vite": "7.6.19"
    "@storybook/test": "7.6.19"
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: StoryBook + NextJS based NPM is not working
Labels: bug,needs triage

### Describe the bug

After making an build, NextJS is building an **.next** folder. While importing an NPM package using my organization based package which is looking for an **dist** folder. In this case, StoryBook + NextJS based NPM is not working. I am not able to find any solution for this. Attaching an NPM Package link.

### Reproduction link

https://www.npmjs.com/package/@uber9/zolvit-micro-next-common-lib

### Reproduction steps

_No response_

### System

```bash
npm run build
npm publish

In my repo,
npm i and just importing the component it is not able to find the module.
```


### Additional context

_No response_
Repository: tauri
Issue: [bug] Custom menu items don’t work after updating app menu
Labels: type: bug,status: needs triage

### Describe the bug

My app has a main window and a sub window that can be launched from the main window. In the main window I’ve created a menu and call `menu.setAsAppMenu()` to activate it. One of the menu items is a custom MenuItem to launch the sub window.

When I launch the sub window I want a different app menu. So I create a completely different menu and listen for `tauri://window-created` to activate it. I listen for ‘tauri://destroyed' on the sub window to reset the menu back to the original menu.

When I open the sub window the new menu is updated correctly. When I close the sub window the original menu is also updated correctly. Except none of the custom MenuItem’s in the original menu work anymore. They still show up and look clickable but nothing happens when they are clicked. PredefinedMenuItem’s work fine.

### Reproduction

Reproduction: https://github.com/BjornDCode/tauri-app-menu-bug

1. Run `npm run tauri dev`
2. Click on 'File' -> 'New sub window'
3. Check that it opens a new window
4. Close the newly opened window
5. Click on 'File' -> 'New sub window' again
6. Verify that action doesn't work the 2nd time

### Expected behavior

I would expect custom menu items to work after the menu is updated

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 13.3.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.78.0 (9b00956e5 2024-04-29)
    ✔ cargo: 1.78.0 (54d8815d0 2024-03-26)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.7.0
    - pnpm: 8.14.2
    - yarn: 1.22.21
    - npm: 10.1.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.22
    - tauri-build [RUST]: 2.0.0-beta.17
    - wry [RUST]: 0.40.1
    - tao [RUST]: 0.28.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.13
    - @tauri-apps/cli [NPM]: 2.0.0-beta.20

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: [Error] Blocked script execution in...
Labels: bug,web,safari,confirmation-pending,network

* safari
* open https://insiders.vscode.dev/
* from the extension viewlet, open the python extensions
* scroll the extension page
* :bug: the error log fills up with errors like below 

```
[Error] Blocked script execution in 'https://0puitlngfbsk1kpqfqpcibi1c5b6vmc5br981jd8s1712krv6ci9.vscode-cdn.net/insider/43f70eca0c428e6f1a5bfad59a9b2a66f99b748d/out/vs/workbench/contrib/webview/browser/pre/index.html?id=209683a4-b666-4d65-a686-fe82eefb370e&origin=f1f9dbdf-5e62-42cd-a51c-bdfb5730c581&swVersion=4&extensionId=&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Finsiders.vscode.dev&disableServiceWorker=true&vscode-coi=3#' because the document's frame is sandboxed and the 'allow-scripts' permission is not set. (x603)
```
Repository: deno
Issue: Deno cache database errors when on a shared drive
Labels: bug,cli

I upgraded deno from `1.43.6` to `1.44.4` on my Linux system and ever since I've been getting errors:
```
Could not initialize cache database '/mnt/compendium/.deno/v8_code_cache_v2', deleting and retrying... (disk I/O error

Caused by:
    Error code 522: Unable to obtain number of requested bytes (file truncated?))
Could not initialize cache database '/mnt/compendium/.deno/dep_analysis_cache_v2', deleting and retrying... (disk I/O error

Caused by:
    Error code 522: Unable to obtain number of requested bytes (file truncated?))
Failed to open cache file '/mnt/compendium/.deno/v8_code_cache_v2', performance may be degraded.
Failed to open cache file '/mnt/compendium/.deno/dep_analysis_cache_v2', opening in-memory cache.```

I always launch deno with: `DENO_DIR=/mnt/compendium/.deno DENO_NO_UPDATE_CHECK=1 DENO_NO_PACKAGE_JSON=1 deno run ...
```

`/mnt/compendium/.deno` is on a NFS drive shared between 2 systems, each with the same version of deno, running deno scripts periodically.

If I delete the `.deno` dir and have it re-create it, the errors go away for a few hours, maybe half a day or so, then come back again.

The NFS mount is fine, as is the hard drive, this only started happening with the latest deno upgrade.

Maybe something was introduced into deno where it tries to do some sort of atomic operations on the cache file database that breaks if said cache is shared between systems on a shared drive where multiple deno processes from different systems may try and modify it at the same time?

Let me know if you want me to run any additional commands, gather any additional info.