repo stringclasses 21
values | pull_number float64 88 192k | instance_id stringlengths 16 34 | issue_numbers stringlengths 6 20 | base_commit stringlengths 40 40 | patch stringlengths 266 270k | test_patch stringlengths 350 165k | problem_statement stringlengths 38 24k | hints_text stringlengths 1 33.2k ⌀ | created_at stringdate 2016-01-11 17:37:29 2024-10-18 14:52:41 | language stringclasses 4
values | Dockerfile stringlengths 100 3.03k | P2P stringlengths 2 216k | F2P stringlengths 11 10.5k | F2F stringclasses 26
values | test_command stringlengths 27 5.49k | task_category stringclasses 3
values | is_no_nodes bool 2
classes | is_func_only bool 2
classes | is_class_only bool 2
classes | is_mixed bool 2
classes | num_func_changes int64 0 238 | num_class_changes int64 0 70 | num_nodes int64 0 264 | is_single_func bool 2
classes | is_single_class bool 2
classes | modified_nodes stringlengths 2 42.2k |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
mui/material-ui | 14,023 | mui__material-ui-14023 | ['12996'] | abb0f18a78d933bd9ea9f16c2991fd512527c80f | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of the @material-ui/core modules',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '95.2 KB',
+ limit: '95.3 KB',
},
{
name: 'T... | diff --git a/packages/material-ui/src/InputAdornment/InputAdornment.test.js b/packages/material-ui/src/InputAdornment/InputAdornment.test.js
--- a/packages/material-ui/src/InputAdornment/InputAdornment.test.js
+++ b/packages/material-ui/src/InputAdornment/InputAdornment.test.js
@@ -1,84 +1,183 @@
import React from 're... | [InputAdornment] Automatically inherit the variant
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should... | Seems like you forgot the TextFields in the codesandbox.
Ah you're right I guess I forgot to press save. I updated the link, should be working now!
https://codesandbox.io/s/43y02726z7
@Anwardo It's not following the documentation:
```diff
InputProps={{
startAdornment: (
- ... | 2018-12-28 19:25:02+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > cust... | ['packages/material-ui/src/InputAdornment/InputAdornment.test.js-><InputAdornment /> prop: variant should have the filled root and class when variant is filled', 'packages/material-ui/src/InputAdornment/InputAdornment.test.js-><InputAdornment /> should render children', 'packages/material-ui/src/InputAdornment/InputAdo... | ['packages/material-ui/src/InputAdornment/InputAdornment.test.js-><InputAdornment /> prop: variant warnings should warn if the variant supplied is equal to the variant inferred', "packages/material-ui/src/InputAdornment/InputAdornment.test.js-><InputAdornment /> prop: variant should inherit the TextField's variant", "p... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/InputAdornment/InputAdornment.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 5 | 0 | 5 | false | false | ["docs/src/pages/demos/text-fields/FilledInputAdornments.js->program->class_declaration:FilledInputAdornments->method_definition:render", "packages/material-ui/src/InputAdornment/InputAdornment.js->program->function_declaration:InputAdornment", "docs/src/pages/demos/text-fields/FormattedInputs.hooks.js->program->functi... |
mui/material-ui | 14,036 | mui__material-ui-14036 | ['10831'] | f946f19a5c8a6b38759e02bd86c9b77e89232caa | diff --git a/packages/material-ui-lab/src/Slider/Slider.js b/packages/material-ui-lab/src/Slider/Slider.js
--- a/packages/material-ui-lab/src/Slider/Slider.js
+++ b/packages/material-ui-lab/src/Slider/Slider.js
@@ -68,7 +68,6 @@ export const styles = theme => {
transition: trackTransitions,
'&$activated':... | diff --git a/packages/material-ui/src/Fade/Fade.test.js b/packages/material-ui/src/Fade/Fade.test.js
--- a/packages/material-ui/src/Fade/Fade.test.js
+++ b/packages/material-ui/src/Fade/Fade.test.js
@@ -87,7 +87,6 @@ describe('<Fade />', () => {
);
assert.deepEqual(wrapper.find('div').props().style, {
... | What the will-change issue might be?
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like thi... | @leedstyh We don't use the `willChange` property much: https://github.com/mui-org/material-ui/search?utf8=%E2%9C%93&q=willchange&type=. Can you provide a isolated reproduction example? The warning could come from a third party library.
Not appears every time, so I'll close this now. Will ping you back here if I have mo... | 2018-12-30 14:27:39+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > cust... | ['packages/material-ui/src/Fade/Fade.test.js-><Fade /> should render a Transition', 'packages/material-ui/src/Zoom/Zoom.test.js-><Zoom /> transition lifecycle handleExit() should set the style properties', 'packages/material-ui/src/Zoom/Zoom.test.js-><Zoom /> transition lifecycle handleEnter() should set the style prop... | ['packages/material-ui/src/Zoom/Zoom.test.js-><Zoom /> prop: appear should work when initially hidden', 'packages/material-ui/src/Fade/Fade.test.js-><Fade /> prop: appear should work when initially hidden'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Fade/Fade.test.js packages/material-ui/src/Zoom/Zoom.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/Fade/Fade.js->program->class_declaration:Fade->method_definition:render", "packages/material-ui/src/Zoom/Zoom.js->program->class_declaration:Zoom->method_definition:render"] |
mui/material-ui | 14,266 | mui__material-ui-14266 | ['14231'] | 345be3452c528fe46b8be965b3a8846dffedf50d | diff --git a/docs/src/modules/components/MarkdownDocsContents.js b/docs/src/modules/components/MarkdownDocsContents.js
--- a/docs/src/modules/components/MarkdownDocsContents.js
+++ b/docs/src/modules/components/MarkdownDocsContents.js
@@ -33,13 +33,13 @@ function MarkdownDocsContents(props) {
## API
${headers.compo... | diff --git a/packages/material-ui/src/TextField/TextField.test.js b/packages/material-ui/src/TextField/TextField.test.js
--- a/packages/material-ui/src/TextField/TextField.test.js
+++ b/packages/material-ui/src/TextField/TextField.test.js
@@ -94,6 +94,11 @@ describe('<TextField />', () => {
assert.strictEqual(... | [TextField] helperText accessibility
`<TextField />` property `helperText` is not accessible. I believe `aria-describedby` should be applied to the `InputElement` and not to the `FormControl` 🤔
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github... | @enagy-earnup I think that you are right: https://www.w3.org/TR/WCAG20-TECHS/ARIA21.html. How do you think that we should solve the issue? Fix the demos with a documentation section on the accessible error messages?
@oliviertassinari moving the `aria-describedby` to the input solves the accessibility issue - I just tes... | 2019-01-22 13:15:09+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > cust... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> shallow structure should have an Input as the only child', 'packages/material-ui/src/TextField/TextField.test.js-><TextField /> shallow structure should forward the fullWidth prop to Input', 'packages/material-ui/src/TextField/TextField.test.js-><Tex... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> shallow with a helper text should add accessibility labels to the input'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TextField/TextField.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 11 | 0 | 11 | false | false | ["packages/material-ui/src/useMediaQuery/unstable_useMediaQuery.js->program->function_declaration:unstable_useMediaQuery", "packages/material-ui-styles/src/makeStyles.js->program->function_declaration:makeStyles", "docs/src/pages/demos/text-fields/InputAdornments.hooks.js->program->function_declaration:InputAdornments"... |
mui/material-ui | 14,465 | mui__material-ui-14465 | ['12632'] | aad72ed7af8f49354ff261d96a3cc97b4ff500de | diff --git a/packages/material-ui/src/Collapse/Collapse.js b/packages/material-ui/src/Collapse/Collapse.js
--- a/packages/material-ui/src/Collapse/Collapse.js
+++ b/packages/material-ui/src/Collapse/Collapse.js
@@ -21,6 +21,11 @@ export const styles = theme => ({
height: 'auto',
overflow: 'visible',
},
+ ... | diff --git a/packages/material-ui/src/Fade/Fade.test.js b/packages/material-ui/src/Fade/Fade.test.js
--- a/packages/material-ui/src/Fade/Fade.test.js
+++ b/packages/material-ui/src/Fade/Fade.test.js
@@ -87,6 +87,7 @@ describe('<Fade />', () => {
);
assert.deepEqual(wrapper.find('div').props().style, {
... | [Accordion] Make follow accessibly standards
<!--- Provide a general summary of the feature in the Title above -->
Currently, if you have a link of any kind inside your panel and you tab through the page, the tab sequence will tab to hidden items in the closed expansions. The tab sequence should skip links inside of c... | @salientknight I believe it's a duplicate of #10569. There is a known workaround, as far as I remember, the issue is about improving the API. | 2019-02-08 14:06:19+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > cust... | ['packages/material-ui/src/Slide/Slide.test.js-><Slide /> transition lifecycle handleEntering() should reset the translate3d', 'packages/material-ui/src/Slide/Slide.test.js-><Slide /> transition lifecycle handleExiting() should set element transform and transition according to the direction', 'packages/material-ui/src/... | ['packages/material-ui/src/Zoom/Zoom.test.js-><Zoom /> prop: appear should work when initially hidden: appear=false', 'packages/material-ui/src/Fade/Fade.test.js-><Fade /> prop: appear should work when initially hidden, appear=true', 'packages/material-ui/src/Slide/Slide.test.js-><Slide /> mount should work when initia... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Slide/Slide.test.js packages/material-ui/src/Fade/Fade.test.js packages/material-ui/src/Zoom/Zoom.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 6 | 0 | 6 | false | false | ["packages/material-ui/src/Grow/Grow.js->program->class_declaration:Grow->method_definition:render", "packages/material-ui/src/Slide/Slide.js->program->class_declaration:Slide->method_definition:updatePosition", "packages/material-ui/src/Collapse/Collapse.js->program->class_declaration:Collapse->method_definition:rende... |
mui/material-ui | 15,097 | mui__material-ui-15097 | ['13799'] | 2c2075e6c62fb55aacae61adad048630b2788201 | diff --git a/docs/src/pages/demos/selection-controls/CheckboxLabels.js b/docs/src/pages/demos/selection-controls/CheckboxLabels.js
--- a/docs/src/pages/demos/selection-controls/CheckboxLabels.js
+++ b/docs/src/pages/demos/selection-controls/CheckboxLabels.js
@@ -1,5 +1,5 @@
import React from 'react';
-import { makeSty... | diff --git a/packages/material-ui/src/Switch/Switch.test.js b/packages/material-ui/src/Switch/Switch.test.js
--- a/packages/material-ui/src/Switch/Switch.test.js
+++ b/packages/material-ui/src/Switch/Switch.test.js
@@ -35,22 +35,22 @@ describe('<Switch />', () => {
assert.strictEqual(wrapper.hasClass('foo'), tru... | [Switch] focused, OFF switch should have a dark grey indicator, instead of white
The Switch component has a white circle focus indicator in OFF state instead of a dark grey one.
- [X] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [X] I have searched the [issues](https://github.com/mui-org/mat... | It's not just the Switch specification that we need to update, the Radio and the Checkbox.
@oliviertassinari
The Checkbox is looking fine for me from this issue's aspect.
Actual:
Spec:
![checkbox spe... | 2019-03-28 15:04:39+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Switch/Switch.test.js-><Switch /> default Switch export should render a span with the root and user classes', 'packages/material-ui/src/Switch/Switch.test.js-><Switch /> styleSheet should have the classes required for SwitchBase'] | ['packages/material-ui/src/Switch/Switch.test.js-><Switch /> default Switch export should render SwitchBase with a custom span icon with the thumb class', 'packages/material-ui/src/Switch/Switch.test.js-><Switch /> default Switch export should render the track as the 2nd child'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Switch/Switch.test.js --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 4 | 0 | 4 | false | false | ["docs/src/pages/demos/selection-controls/CustomizedSwitches.js->program->function_declaration:CustomizedSwitches", "docs/src/pages/demos/selection-controls/RadioButtons.js->program->function_declaration:RadioButtons", "docs/src/pages/demos/selection-controls/CheckboxLabels.js->program->function_declaration:CheckboxLab... |
mui/material-ui | 15,430 | mui__material-ui-15430 | ['15407'] | 947853d0fde0d3048f653069bb1febe6dbde9577 | diff --git a/packages/material-ui/src/FilledInput/FilledInput.js b/packages/material-ui/src/FilledInput/FilledInput.js
--- a/packages/material-ui/src/FilledInput/FilledInput.js
+++ b/packages/material-ui/src/FilledInput/FilledInput.js
@@ -243,10 +243,6 @@ FilledInput.propTypes = {
* Maximum number of rows to displa... | diff --git a/packages/material-ui/src/InputBase/Textarea.test.js b/packages/material-ui/src/InputBase/Textarea.test.js
--- a/packages/material-ui/src/InputBase/Textarea.test.js
+++ b/packages/material-ui/src/InputBase/Textarea.test.js
@@ -137,10 +137,10 @@ describe('<Textarea />', () => {
assert.strictEqual(getH... | [Textarea] Remove rowsMin, use the rows prop instead
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Expected Behavior 🤔
rowsMin prop should be ... | You're right TextField doesn't have a `rowsMin` prop. I don't see any harm in adding one to pass down.
Not sure if it's a bug or enhancement though. I would probably say enhancement since nothing is 'broken'.
cc @oliviertassinari
I think it does end up causing a minor bug. In my scenario we want to show a defaul... | 2019-04-21 11:46:27+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> Material-UI component API does spread props to the root component', 'packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> layout should take the padding into account with content-box', 'packages/material-ui/src/InputBase/Textarea.test.js->... | ['packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> layout should have at least height of "rows"'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha test/regressions/tests/Textarea/Textarea.js packages/material-ui/src/InputBase/Textarea.test.js --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/InputBase/InputBase.js->program->class_declaration:InputBase->method_definition:render"] |
mui/material-ui | 15,495 | mui__material-ui-15495 | ['8191'] | a97c70fcbd4891e283e2efa2ba9c067f524826be | diff --git a/packages/material-ui/src/ListItem/ListItem.js b/packages/material-ui/src/ListItem/ListItem.js
--- a/packages/material-ui/src/ListItem/ListItem.js
+++ b/packages/material-ui/src/ListItem/ListItem.js
@@ -30,7 +30,6 @@ export const styles = theme => ({
container: {
position: 'relative',
},
- // To... | diff --git a/packages/material-ui/test/integration/MenuList.test.js b/packages/material-ui/test/integration/MenuList.test.js
--- a/packages/material-ui/test/integration/MenuList.test.js
+++ b/packages/material-ui/test/integration/MenuList.test.js
@@ -51,19 +51,34 @@ function assertMenuItemTabIndexed(wrapper, tabIndexed... | Select menu does not fully implement keyboard controls
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox sh... | Given that this would require the component to hold internal state, rolling it in may not be the best move. Perhaps add a demo for this that hooks into the Input's onKeyUp handler though. Thoughts?
I'm glad we expose a native select version too that don't suffer from this issue.
>Material UI is an amazing asset, but in... | 2019-04-26 01:50:14+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration keyboard controls and tabIndex manipulation - preselected item should focus the third item', 'packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration keyboard controls and tabIndex manipulation should focus the secon... | ['packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration MenuList text-based keyboard controls should not move focus when no match', 'packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration MenuList text-based keyboard controls should not move focus when additional keys ma... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/test/integration/MenuList.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/MenuList/MenuList.js->program->function_declaration:moveFocus", "packages/material-ui/src/MenuList/MenuList.js->program->function_declaration:textCriteriaMatches"] |
mui/material-ui | 16,137 | mui__material-ui-16137 | ['16136'] | adaa66d3737b563c6f88df2fe7e77671287bcf8d | diff --git a/docs/src/pages/components/selects/CustomizedSelects.js b/docs/src/pages/components/selects/CustomizedSelects.js
--- a/docs/src/pages/components/selects/CustomizedSelects.js
+++ b/docs/src/pages/components/selects/CustomizedSelects.js
@@ -19,7 +19,6 @@ const BootstrapInput = withStyles(theme => ({
back... | diff --git a/packages/material-ui/src/Select/SelectInput.test.js b/packages/material-ui/src/Select/SelectInput.test.js
--- a/packages/material-ui/src/Select/SelectInput.test.js
+++ b/packages/material-ui/src/Select/SelectInput.test.js
@@ -41,7 +41,7 @@ describe('<SelectInput />', () => {
it('should render a correc... | Down arrow in NativeSelect OutlinedInput is not clickable
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox... | null | 2019-06-10 14:37:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ["packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed ArrowUp key on select", "packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed key on select", 'packages/material-ui/src/Select/SelectInput.... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> should render a correct top element'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,882 | mui__material-ui-16882 | ['16475'] | 14e595fb18f781d2f49c83f85b006d86111ae328 | diff --git a/packages/material-ui-styles/src/styled/styled.js b/packages/material-ui-styles/src/styled/styled.js
--- a/packages/material-ui-styles/src/styled/styled.js
+++ b/packages/material-ui-styles/src/styled/styled.js
@@ -80,17 +80,18 @@ function styled(Component) {
const classes = useStyles(props);
... | diff --git a/packages/material-ui-styles/src/styled/styled.test.js b/packages/material-ui-styles/src/styled/styled.test.js
--- a/packages/material-ui-styles/src/styled/styled.test.js
+++ b/packages/material-ui-styles/src/styled/styled.test.js
@@ -45,12 +45,21 @@ describe('styled', () => {
});
describe('prop: cl... | Box clone ignores SyntheticEvent
Adding clone property to Box component will cause SyntheticEvent to break. It's actually passing styling props and nothing more.
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) ... | @fafamx So far, we have been spreading the props when using the cloneElement API in the codebase. Doing the same in this case sounds reasonable. We would need to change the spread logic around those lines: https://github.com/mui-org/material-ui/blob/143124dc944f61c9f4456ea3cd7e4a3e6cebd668/packages/material-ui-styles/s... | 2019-08-04 12:53:26+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-styles/src/styled/styled.test.js->styled should work as expected', 'packages/material-ui-styles/src/styled/styled.test.js->styled warnings warns if it cant detect the secondary action properly', 'packages/material-ui-styles/src/styled/styled.test.js->styled prop: clone should be able to clone the... | ['packages/material-ui-styles/src/styled/styled.test.js->styled prop: clone should be able to pass props to cloned element'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-styles/src/styled/styled.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-styles/src/styled/styled.js->program->function_declaration:styled"] |
mui/material-ui | 17,005 | mui__material-ui-17005 | ['11910'] | 10ed7cfb308de1d978886c13ac5a7c31700f7068 | diff --git a/packages/material-ui/src/Grid/Grid.js b/packages/material-ui/src/Grid/Grid.js
--- a/packages/material-ui/src/Grid/Grid.js
+++ b/packages/material-ui/src/Grid/Grid.js
@@ -64,6 +64,11 @@ function generateGrid(globalStyles, theme, breakpoint) {
}
}
+function getOffset(val, div = 1) {
+ const parse = pa... | diff --git a/packages/material-ui/src/Grid/Grid.test.js b/packages/material-ui/src/Grid/Grid.test.js
--- a/packages/material-ui/src/Grid/Grid.test.js
+++ b/packages/material-ui/src/Grid/Grid.test.js
@@ -1,8 +1,9 @@
import React from 'react';
-import { assert } from 'chai';
+import { assert, expect } from 'chai';
impo... | [Grid] Replace px to rem in spacing prop
Now
```jsx
<Grid spacing={8/padding: 4px|16/padding: 8px|32/padding: 16px|40/padding: 32px}>
```
Need
```jsx
<Grid spacing={8/padding:0.25rem|16/padding:0.5rem|32/padding:0.75rem|40/padding:1rem}>
```
or add another prop spacingRem
| @udanpe The Grid component aims to be as simple as possible. You don't have to use the spacing property, you can keep it to 0 and use rem on your side.
I changed the spacing function to output a `rem` string as per the 'bootstrap strategy' example(https://material-ui.com/customization/spacing/). However, this breaks th... | 2019-08-14 22:07:38+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Grid/Grid.test.js-><Grid /> prop: xs should apply the flex-grow class', 'packages/material-ui/src/Grid/Grid.test.js-><Grid /> prop: alignItems should apply the align-item class', 'packages/material-ui/src/Grid/Grid.test.js-><Grid /> Material-UI component API should render without errors in Re... | ['packages/material-ui/src/Grid/Grid.test.js-><Grid /> gutter should generate the right values'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Grid/Grid.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/Grid/Grid.js->program->function_declaration:getOffset", "packages/material-ui/src/Grid/Grid.js->program->function_declaration:generateGutter"] |
mui/material-ui | 17,301 | mui__material-ui-17301 | ['10763'] | 0ddd56f5d389bfd19120d38fc4302f32f238be6f | diff --git a/docs/pages/api/speed-dial-action.md b/docs/pages/api/speed-dial-action.md
--- a/docs/pages/api/speed-dial-action.md
+++ b/docs/pages/api/speed-dial-action.md
@@ -24,16 +24,16 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| Name | Type | Default | Description |
|:--... | diff --git a/packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js b/packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js
--- a/packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js
+++ b/packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js
@@ -7,6 +7,7 @@ import {
getClasses,
wrapsIntrinsicElement,... | [SpeedDial] SpeedDialAction visibility is poor on dark themes
<!--- Provide a general summary of the issue in the Title above -->
The icon and button colors on SpeedDialActions have weak visibility on dark themes. This can be seen on the material-ui site itself by switching to the dark theme and viewing the SpeedDial... | @ryanfields You're quite right. Would you like to try and improve it?
@mbrookes Started looking into a fix, but I need to spend time familiarizing myself with Material-UI's structure and inner workings. This is the first time I've tried working with the code. I will circle back to this in a couple weeks.
Thanks. Shou... | 2019-09-03 17:31:37+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/SpeedDialIcon/SpeedDialIcon.test.js-><SpeedDialIcon /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/SpeedDialIcon/SpeedDialIcon.test.js-><SpeedDialIcon /> should render the icon with the icon and iconOpen classe... | ['packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js-><SpeedDial /> dial focus actions navigation ignores array keys orthogonal to the direction', 'packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js-><SpeedDialAction /> should render the button with the fab class', 'packages/material-ui-lab/src/... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tooltip/Tooltip.test.js packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js test/regressions/tests/SpeedDial/Directions.js packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js packages/material-... | Refactoring | false | true | false | false | 5 | 0 | 5 | false | false | ["docs/src/pages/components/speed-dial/SpeedDialTooltipOpen.js->program->function_declaration:SpeedDialTooltipOpen", "docs/src/pages/components/speed-dial/OpenIconSpeedDial.js->program->function_declaration:OpenIconSpeedDial", "packages/material-ui/src/Tooltip/Tooltip.js->program->function_declaration:Tooltip", "packag... |
mui/material-ui | 17,640 | mui__material-ui-17640 | ['17634'] | 05c533bd1f044593b772191066f25dd8b916ff5d | diff --git a/docs/pages/api/button.md b/docs/pages/api/button.md
--- a/docs/pages/api/button.md
+++ b/docs/pages/api/button.md
@@ -61,6 +61,12 @@ Any other props supplied will be provided to the root element ([ButtonBase](/api
| <span class="prop-name">focusVisible</span> | <span class="prop-name">Mui-focusVisible</sp... | diff --git a/packages/material-ui/src/Button/Button.test.js b/packages/material-ui/src/Button/Button.test.js
--- a/packages/material-ui/src/Button/Button.test.js
+++ b/packages/material-ui/src/Button/Button.test.js
@@ -40,8 +40,12 @@ describe('<Button />', () => {
expect(button).not.to.have.class(classes.contained... | Bigger horizontal padding for small size button
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Summary 💡
The padding of the small size button is : `4px 8px`. It doesn't look good to my eyes:
 but 12px would be good for me
@lcswillems Interesting concern, it seems that... | 2019-09-30 17:15:17+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Button/Button.test.js-><Button /> should render an inherit outlined button', 'packages/material-ui/src/ButtonGroup/ButtonGroup.test.js-><ButtonGroup /> can pass fullWidth to Button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a text secondary button', 'packages/... | ['packages/material-ui/src/Button/Button.test.js-><Button /> should render a large text button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a small outlined button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a small contained button', 'packages/material-ui/... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Button/Button.test.js packages/material-ui/src/ButtonGroup/ButtonGroup.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,691 | mui__material-ui-17691 | ['17568'] | 9122b600f5671c7a3563f2ca73d64ef8fdf3fc1b | diff --git a/docs/pages/api/select.md b/docs/pages/api/select.md
--- a/docs/pages/api/select.md
+++ b/docs/pages/api/select.md
@@ -41,7 +41,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">open</span> | <span class="prop-type">bool</span> | | Control `sel... | diff --git a/packages/material-ui/src/InputBase/InputBase.test.js b/packages/material-ui/src/InputBase/InputBase.test.js
--- a/packages/material-ui/src/InputBase/InputBase.test.js
+++ b/packages/material-ui/src/InputBase/InputBase.test.js
@@ -594,7 +594,7 @@ describe('<InputBase />', () => {
InputProps={{
... | Value for Select which allows to not select any of the options
- [x ] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Summary 💡
In this example: https://material-ui.com/components/selects/, you see on the first select co... | @giorgi-m How would you envision this to be documented?
@oliviertassinari This is problematic only if I have InputLabel and set as value some random value, see: https://codesandbox.io/s/material-demo-w5r5f
the label is shown on top, whereas if you set value to '', then the label isn't set on top anymore.
If ... | 2019-10-03 17:14:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed ArrowUp key on select', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: multiple selects value based on their stringified equality when theyre not objects', 'packages/material-ui/src/TablePagination/TablePaginat... | ['packages/material-ui/src/Select/Select.test.js-><Select /> prop: value warnings warns when the value is not present in any option'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/Select.test.js packages/material-ui/src/InputBase/InputBase.test.js test/utils/consoleError.js packages/material-ui/src/TablePagination/TablePagination.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/pages/components/selects/DialogSelect.js->program->function_declaration:DialogSelect"] |
mui/material-ui | 17,829 | mui__material-ui-17829 | ['17718'] | 5d564f9c1be5bf20b51be1a479d292bf443291ba | diff --git a/docs/pages/api/chip.md b/docs/pages/api/chip.md
--- a/docs/pages/api/chip.md
+++ b/docs/pages/api/chip.md
@@ -29,7 +29,7 @@ Chips represent complex entities in small blocks, such as a contact.
| <span class="prop-name">classes</span> | <span class="prop-type">object</span> | | Override or extend the styl... | diff --git a/packages/material-ui/src/Chip/Chip.test.js b/packages/material-ui/src/Chip/Chip.test.js
--- a/packages/material-ui/src/Chip/Chip.test.js
+++ b/packages/material-ui/src/Chip/Chip.test.js
@@ -423,8 +423,8 @@ describe('<Chip />', () => {
key: ' ',
};
wrapper.find('div').simulate('... | [Chip] No Ripple effect
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x] -->
- [x... | null | 2019-10-10 16:16:31+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to keyboard chip has children that generate events should call handlers for child event', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> clickable text chip should have a tabIndex prop', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to ... | ['packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to keyboard chip onClick is defined should call onClick when `enter` is pressed ', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to keyboard chip onClick is defined should call onClick when `space` is pressed '] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Chip/Chip.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,744 | mui__material-ui-18744 | ['16357'] | 53ef743ec2d8f08286f2e0d56ceaea0765417e39 | diff --git a/docs/pages/api/button.md b/docs/pages/api/button.md
--- a/docs/pages/api/button.md
+++ b/docs/pages/api/button.md
@@ -29,6 +29,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">color</span> | <span class="prop-type">'default'<br>| 'in... | diff --git a/packages/material-ui/src/Button/Button.test.js b/packages/material-ui/src/Button/Button.test.js
--- a/packages/material-ui/src/Button/Button.test.js
+++ b/packages/material-ui/src/Button/Button.test.js
@@ -309,6 +309,13 @@ describe('<Button />', () => {
expect(button.querySelector('.touch-ripple')).to... | [Buttons] Disable elevation
I have buttons that I don't want to have a box-shadow. Instead of custom CSS, using the `elevation` key would be ideal for me, as that's how we handle `<Paper />` shadows
| I’m not sure if this should be in the core library. I guess we should see what other users wants. I would close this in the mean time let’s see what @oliviertassinari thinks :)
@joshwooding I agree. Personally, I would override the box shadow, or start from the ButtonBase component.
It just seems kind of 'silly' for p... | 2019-12-08 14:57:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Button/Button.test.js-><Button /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render an inherit outlined button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a large ou... | ['packages/material-ui/src/Button/Button.test.js-><Button /> can disable the elevation'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Button/Button.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 19,612 | mui__material-ui-19612 | ['19653'] | 5794780fc25a39c3ebee20f946b4a1b4e92b59d2 | diff --git a/docs/pages/api/alert.md b/docs/pages/api/alert.md
--- a/docs/pages/api/alert.md
+++ b/docs/pages/api/alert.md
@@ -30,7 +30,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">closeText</span> | <span class="prop-type">string</span> | <span class=... | diff --git a/packages/material-ui-lab/src/Pagination/Pagination.test.js b/packages/material-ui-lab/src/Pagination/Pagination.test.js
--- a/packages/material-ui-lab/src/Pagination/Pagination.test.js
+++ b/packages/material-ui-lab/src/Pagination/Pagination.test.js
@@ -8,18 +8,18 @@ import Pagination from './Pagination';
... | [PaginationItem] Incorrect style sheet name?
https://material-ui.com/api/pagination-item/
Shouldn't that be `MuiPaginationItem` instead of `PaginationItem`, to be consistent with every other component?
... | null | 2020-02-08 13:20:48+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui-lab/src/Pagination/Pagination.test.js-><Pagination /> Material-UI component API should render without errors in ReactTestRenderer', 'packages/material-ui-lab/src/PaginationItem/PaginationItem.test.js-><PaginationItem /> Material-UI component API spreads props to the root component', 'packages/mat... | ['packages/material-ui/src/SvgIcon/SvgIcon.test.js-><SvgIcon /> prop: titleAccess should be able to make an icon accessible', 'packages/material-ui-lab/src/Pagination/Pagination.test.js-><Pagination /> Material-UI component API spreads props to the root component'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/PaginationItem/PaginationItem.test.js packages/material-ui-lab/src/Pagination/Pagination.test.js packages/material-ui/src/SvgIcon/SvgIcon.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 5 | 0 | 5 | false | false | ["docs/src/modules/utils/generateMarkdown.js->program->function_declaration:generateProps", "docs/src/pages/components/pagination/PaginationControlled.js->program->function_declaration:PaginationControlled", "packages/material-ui-lab/src/PaginationItem/PaginationItem.js->program->function_declaration:defaultGetAriaLabe... |
mui/material-ui | 19,794 | mui__material-ui-19794 | ['19778'] | eec5b60861adb72df83b6de80c602940ce773663 | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -1,7 +1,7 @@
/* eslint-disable no... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -913,6 +913,25 @@ describe('<Autocompl... | [Autocomplete] Drop list no close outline mouse
| Tech | Version |
| ----------- | ------- |
| Material-UI | v4.9.3 |
| React | v16.12.0 |
| Browser | Chrome |
| TypeScript | |
| etc. | |
Hi, please, look at the gif with the problem
 _may_ be a good starting point. Thank you! | 2020-02-21 09:58:34+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup closed opens on ArrowDown when focus is on the textbox without moving focus', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> wrapping behavior wraps around when navigating the list by default... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input should focus the input when clicking on the open action'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 20,133 | mui__material-ui-20133 | ['19975'] | 7b12c4a4e58195846d4f21c2453ba2883db963fd | diff --git a/docs/pages/api-docs/tree-item.md b/docs/pages/api-docs/tree-item.md
--- a/docs/pages/api-docs/tree-item.md
+++ b/docs/pages/api-docs/tree-item.md
@@ -31,6 +31,7 @@ The `MuiTreeItem` name can be used for providing [default props](/customization/
| <span class="prop-name">children</span> | <span class="prop... | diff --git a/packages/material-ui-lab/src/TreeItem/TreeItem.test.js b/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
--- a/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
+++ b/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
@@ -227,6 +227,28 @@ describe('<TreeItem />', () => {
});
});... | [TreeView] Add disabled support
<!-- Provide a general summary of the feature in the Title above -->
A way to include a TreeItem in a TreeView which is disabled. Disabled being no hover, no click, greyed out styling.
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid ... | Adding the support for a `disabled` prop sounds like a great idea. I could at least find the following benchmark:
- https://www.telerik.com/kendo-angular-ui/components/treeview/disabled-state/
Working on this | 2020-03-15 19:56:43+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> Accessibility Expansion enter key interaction expands a node with children', 'packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> Accessibility Single Selection mouse should not select a node when click and disableSelection', 'packa... | ['packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> prop: disabled selection keyboard should prevent range selection by keyboard + space', 'packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> prop: disabled selection keyboard should prevent selection by keyboard home', 'packages/mate... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/TreeView/TreeView.test.js packages/material-ui-lab/src/TreeItem/TreeItem.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 20,247 | mui__material-ui-20247 | ['20193'] | 5a794bd4974b02536b59d09029b12b4e76824301 | diff --git a/packages/material-ui-lab/src/PaginationItem/PaginationItem.js b/packages/material-ui-lab/src/PaginationItem/PaginationItem.js
--- a/packages/material-ui-lab/src/PaginationItem/PaginationItem.js
+++ b/packages/material-ui-lab/src/PaginationItem/PaginationItem.js
@@ -1,7 +1,7 @@
import * as React from 'reac... | diff --git a/packages/material-ui-lab/src/Pagination/Pagination.test.js b/packages/material-ui-lab/src/Pagination/Pagination.test.js
--- a/packages/material-ui-lab/src/Pagination/Pagination.test.js
+++ b/packages/material-ui-lab/src/Pagination/Pagination.test.js
@@ -5,6 +5,7 @@ import { createMount, getClasses } from '... | [Pagination] Missing RTL support
I am currently using the material ui pagination and after passing the rtl option they appear as so
<img width="208" alt="Screen Shot 2020-03-20 at 7 12 25 AM" src="https://user-images.githubusercontent.com/9379960/77129549-6cac3180-6a7a-11ea-9c80-90d20a321f03.png">
The order is cor... | @hawky93 Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. [This **codesandbox.io** template](https://material-ui.com/r/issue-template) is a good starting point. Thank you!
@hawky93 Thanks for the report. Regarding the reproduction, the steps are 1. navigate to ... | 2020-03-23 13:43:32+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui-lab/src/Pagination/Pagination.test.js-><Pagination /> Material-UI component API should render without errors in ReactTestRenderer', 'packages/material-ui-lab/src/Pagination/Pagination.test.js-><Pagination /> should render', 'packages/material-ui-lab/src/Pagination/Pagination.test.js-><Pagination ... | ['packages/material-ui-lab/src/Pagination/Pagination.test.js-><Pagination /> renders controls with correct order in rtl theme'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Pagination/Pagination.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 20,376 | mui__material-ui-20376 | ['20372'] | b3446f4eb90249f91dd044d9e67c3ff0b06e4495 | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.d.ts b/packages/material-ui-lab/src/Autocomplete/Autocomplete.d.ts
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.d.ts
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.d.ts
@@ -27,6 +27,7 @@ export type GetTagProps = ({ index ... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -905,6 +905,33 @@ describe('<Autocompl... | Async autocomplete not working with groupBy
When you use groupBy with a asynchronous autocomplete, that is adding options dynamically the wrong option is selected when you select an option. A reproducable example from the docs for autocomplete and just adding the groupBy for the first letter:
https://codesandbox.io/... | Could you follow our issue template? It would be awesome. Most specifically, on the actual, expected and reproduction steps. Thanks.
@oliviertassinari Done
@FerusAndBeyond I can't reproduce.
@oliviertassinari Go to https://codesandbox.io/s/material-demo-dt5o7, click on the autocomplete, select "Algeria". When I do so... | 2020-04-01 22:05:52+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup closed opens on ArrowDown when focus is on the textbox without moving focus', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> wrapping behavior wraps around when navigating the list by default... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> warnings warn if groups options are not sorted'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 20,781 | mui__material-ui-20781 | ['6955'] | 480fa73c18a00549e5893e938b8aed9bed6afac7 | diff --git a/.eslintrc.js b/.eslintrc.js
--- a/.eslintrc.js
+++ b/.eslintrc.js
@@ -116,6 +116,10 @@ module.exports = {
// does not work with wildcard imports. Mistakes will throw at runtime anyway
'import/named': 'off',
+ // upgraded level from recommended
+ 'mocha/no-exclusive-tests':... | diff --git a/packages/material-ui/src/Tabs/Tabs.test.js b/packages/material-ui/src/Tabs/Tabs.test.js
--- a/packages/material-ui/src/Tabs/Tabs.test.js
+++ b/packages/material-ui/src/Tabs/Tabs.test.js
@@ -10,6 +10,7 @@ import describeConformance from '../test-utils/describeConformance';
import Tab from '../Tab';
import... | [Tabs] Implement arrow keyboard
<!-- Have a QUESTION? Please ask in [StackOverflow or gitter](http://tr.im/77pVj. -->
### Problem description
The Tabs component doesn't implement keyboard support as specified by [the WAI-ARIA 1.1 authoring practices][1]. Ideally it would be best if this was implemented in the a... | Yes, indeed. I'm closing this issue in favor of #4795. Good point.
This comment is relevant too https://github.com/mui-org/material-ui/pull/5604#issuecomment-262122172.
Is anybody currently working on this issue? The lack of keyboard navigation between tabs via the left and right arrow keys is a deal breaker for what I... | 2020-04-26 19:11:15+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: value indicator should render the indicator', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> Material-UI component API applies the root class to the root component if it has this class', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: cente... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> keyboard navigation when focus is on a tab when focus is on a tab element in a horizontal rtl tablist ArrowRight moves focus to the previous tab without activating it', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> keyboard navigation when focus is on a tab... | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tabs/Tabs.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 20,851 | mui__material-ui-20851 | ['20785'] | 024e176b9d2d0dc96826b0fec630823254372683 | diff --git a/packages/material-ui/src/Slider/Slider.js b/packages/material-ui/src/Slider/Slider.js
--- a/packages/material-ui/src/Slider/Slider.js
+++ b/packages/material-ui/src/Slider/Slider.js
@@ -425,6 +425,8 @@ const Slider = React.forwardRef(function Slider(props, ref) {
setOpen(-1);
});
+ const isRtl =... | diff --git a/packages/material-ui/src/Slider/Slider.test.js b/packages/material-ui/src/Slider/Slider.test.js
--- a/packages/material-ui/src/Slider/Slider.test.js
+++ b/packages/material-ui/src/Slider/Slider.test.js
@@ -129,39 +129,6 @@ describe('<Slider />', () => {
});
});
- // TODO: use fireEvent for all t... | [Slider] RTL keyboard handling issue
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x... | A possible fix:
```diff
diff --git a/packages/material-ui/src/Slider/Slider.js b/packages/material-ui/src/Slider/Slider.js
index 9379e1874..28c180300 100644
--- a/packages/material-ui/src/Slider/Slider.js
+++ b/packages/material-ui/src/Slider/Slider.js
@@ -422,6 +422,8 @@ const Slider = React.forwardRef(functio... | 2020-04-30 00:10:32+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui/src/Slider/Slider.test.js-><Slider /> keyboard should reach right edge value', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> prop: ValueLabelComponent receives the formatted value', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> Material-UI component API should render w... | ['packages/material-ui/src/Slider/Slider.test.js-><Slider /> keyboard should handle RTL'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Slider/Slider.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 21,192 | mui__material-ui-21192 | ['20402'] | 010058b818913bbd9c507b4ef3014dd194b31e5c | diff --git a/docs/pages/api-docs/native-select.md b/docs/pages/api-docs/native-select.md
--- a/docs/pages/api-docs/native-select.md
+++ b/docs/pages/api-docs/native-select.md
@@ -55,6 +55,7 @@ Any other props supplied will be provided to the root element ([Input](/api/inpu
| <span class="prop-name">iconOpen</span> | <... | diff --git a/packages/material-ui/src/Select/Select.test.js b/packages/material-ui/src/Select/Select.test.js
--- a/packages/material-ui/src/Select/Select.test.js
+++ b/packages/material-ui/src/Select/Select.test.js
@@ -78,14 +78,14 @@ describe('<Select />', () => {
);
});
- it('should have an input with [typ... | Implement native Select validation for non-native select field
<!-- Provide a general summary of the feature in the Title above -->
Previously there have been requests (#12749, #11836) to allow native `required` validation on `Select` fields without using the native UI, and [it was never tackled because it wasn't se... | @benwiley4000 Thanks for taking the time to write this issue. Have you looked into the a11y implications? We would at least need to remove the `<select>` from the tab sequence, but I wonder about the potential duplicated announcements by screen readers.
@oliviertassinari great points. I *think* this is solved with the ... | 2020-05-24 19:36:01+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed ArrowUp key on select', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: multiple selects value based on their stringified equality when theyre not objects', 'packages/material-ui/src/TextField/TextField.test.js-... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> prop: select creates an input[hidden] that has no accessible properties', 'packages/material-ui/src/Select/Select.test.js-><Select /> should have an input with [aria-hidden] by default', 'packages/material-ui/src/Select/Select.test.js-><Select /> pro... | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/Select.test.js packages/material-ui/src/TextField/TextField.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 21,226 | mui__material-ui-21226 | ['20488'] | f62b4b4fc1c10fc7304720d3903fcfcd097a23dd | diff --git a/docs/pages/api-docs/table-pagination.md b/docs/pages/api-docs/table-pagination.md
--- a/docs/pages/api-docs/table-pagination.md
+++ b/docs/pages/api-docs/table-pagination.md
@@ -35,7 +35,7 @@ The `MuiTablePagination` name can be used for providing [default props](/customi
| <span class="prop-name">compone... | diff --git a/packages/material-ui/src/TablePagination/TablePagination.test.js b/packages/material-ui/src/TablePagination/TablePagination.test.js
--- a/packages/material-ui/src/TablePagination/TablePagination.test.js
+++ b/packages/material-ui/src/TablePagination/TablePagination.test.js
@@ -45,7 +45,7 @@ describe('<Tabl... | [Table] Extended `labelRowsPerPage` support from string to ReactNode
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked ch... | @romanyanke Thanks for mentioning this inconsistency. Would the following solve the problem?
```diff
diff --git a/packages/material-ui/src/TablePagination/TablePagination.js b/packages/material-ui/src/TablePagination/TablePagination.js
index 8ab941190..9c7a0302b 100644
--- a/packages/material-ui/src/TablePaginat... | 2020-05-27 15:16:56+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: labelDisplayedRows should use the labelDisplayedRows callback', 'packages/material-ui/src/TablePagination/TablePagination.test.js-><TablePagination /> Material-UI component API prop: component can render another root component... | ['packages/material-ui/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: labelRowsPerPage accepts React nodes', 'packages/material-ui/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: labelRowsPerPage labels the select for the current page'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TablePagination/TablePagination.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 23,174 | mui__material-ui-23174 | ['22253'] | 41cd2bc7425bb7fa7016eecb7c70e05f2b7ce98b | diff --git a/docs/pages/api-docs/input-base.md b/docs/pages/api-docs/input-base.md
--- a/docs/pages/api-docs/input-base.md
+++ b/docs/pages/api-docs/input-base.md
@@ -40,7 +40,7 @@ The `MuiInputBase` name can be used for providing [default props](/customization
| <span class="prop-name">error</span> | <span class="pro... | diff --git a/packages/material-ui/src/InputBase/InputBase.test.js b/packages/material-ui/src/InputBase/InputBase.test.js
--- a/packages/material-ui/src/InputBase/InputBase.test.js
+++ b/packages/material-ui/src/InputBase/InputBase.test.js
@@ -166,15 +166,10 @@ describe('<InputBase />', () => {
it('should inject ... | Got "Does not recognize the 'inputRef' prop" warning after providing TextareaAutosize to OutlinedInput
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the follo... | @liketurbo Thanks for the report. The relevant lines in the codebase are in https://github.com/mui-org/material-ui/blob/a5f59f9de6bbd498bd99d25890f04e496b4fb7eb/packages/material-ui/src/InputBase/InputBase.js#L364-L372
I wonder if we shouldn't move to the usage of the `ref` prop instead of the `inputRef`. The curren... | 2020-10-20 07:28:34+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> with FormControl propagates filled state when uncontrolled', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> with FormControl registering input should not warn when toggling between inputs', 'packages/material-ui/src/InputBase/In... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputComponent with prop: inputProps should call onChange inputProp callback with all params sent from custom inputComponent', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputComponent errors throws on change if ... | ['packages/material-ui-lab/src/SliderStyled/SliderStyled.test.js-><Slider /> range should support mouse events', 'packages/material-ui-lab/src/SliderStyled/SliderStyled.test.js-><Slider /> prop: orientation should report the right position', 'scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'p... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/InputBase/InputBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/src/pages/components/text-fields/FormattedInputs.js->program->function_declaration:NumberFormatCustom", "docs/src/pages/components/text-fields/FormattedInputs.js->program->function_declaration:TextMaskCustom"] |
mui/material-ui | 23,364 | mui__material-ui-23364 | ['19651'] | 161fb8565f532df5766b0e152f21e4a88a8d8baa | diff --git a/docs/pages/api-docs/unstable-trap-focus.md b/docs/pages/api-docs/unstable-trap-focus.md
--- a/docs/pages/api-docs/unstable-trap-focus.md
+++ b/docs/pages/api-docs/unstable-trap-focus.md
@@ -31,6 +31,7 @@ Utility component that locks focus inside the component.
| <span class="prop-name">disableEnforceFocus... | diff --git a/packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js b/packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js
--- a/packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js
+++ b/packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js
@@ -2,7 +... | [TrapFocus] Make possible to avoid focusing wrapper
<!-- Provide a general summary of the feature in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should loo... | @dmtrKovalenko Thanks for opening this issue. For context, and for the next person that will have a look at the problem, the current behavior is the result of a tradeoff taken in #14545 to save bundle size. There is likely an opportunity to do better ✨.
If it can inspire a solution:
- https://github.com/Hacker0x01/... | 2020-11-02 01:39:29+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js-><TrapFocus /> does not steal focus from a portaled element if any prop but open changes', 'packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js-><TrapFocus /> should not attempt to focus nonexistent children', 'packages/material... | ['test/utils/user-event/index.test.js->userEvent tab should handle radio', 'test/utils/user-event/index.test.js->userEvent tab should tab', 'packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js-><TrapFocus /> should focus on first focus element after last has received a tab click', 'packages/material-... | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/material-ui/src/BottomNavigationAction/BottomNavigationAction.test.js-><BottomNavigationAction /> touch functionality should fire onClick on touch tap', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> should only listen t... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha test/utils/createClientRender.js packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js test/utils/user-event/index.js test/utils/user-event/index.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 5 | 0 | 5 | false | false | ["packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.js->program->function_declaration:isNodeMatchingSelectorFocusable", "packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.js->program->function_declaration:isNonTabbableRadio", "packages/material-ui/src/Unstable_TrapFocus/Unstable_TrapFocus.js->... |
mui/material-ui | 25,784 | mui__material-ui-25784 | ['25528'] | b3c85de69ddf15a4a2e21b78b13e4c066b94ca2d | diff --git a/docs/pages/api-docs/unstable-trap-focus.json b/docs/pages/api-docs/unstable-trap-focus.json
--- a/docs/pages/api-docs/unstable-trap-focus.json
+++ b/docs/pages/api-docs/unstable-trap-focus.json
@@ -1,13 +1,19 @@
{
"props": {
- "getDoc": { "type": { "name": "func" }, "required": true },
- "isEnabl... | diff --git a/packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js b/packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js
--- a/packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js
+++ b/packages/material-ui-unstyled/src/Unstable_TrapFocus/... | [TrapFocus] Improve props
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Summary 💡
1. Have `() => document` as the default prop value of `<TrapFocus getDoc />`.
2. Have `() => true` as the default prop value of `<... | While looking at the TrapFocus [page](https://next.material-ui.com/components/trap-focus/) I noticed that the keys are not visible on the dark theme. Since the docs will be updated this could be fixed too.
... | 2021-04-15 22:59:43+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js-><TrapFocus /> interval prop: disableAutoFocus should not trap', 'packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js-><TrapFocus /> does not steal focus from a portaled element if any prop but open changes', '... | ['packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js-><TrapFocus /> should warn if the root content is not focusable', 'packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js-><TrapFocus /> should not return focus to the children when disableEnforceFocus is true', '... | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/material-ui/src/useAutocomplete/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded', 'packages/material-ui/src/BottomNavigationAction/BottomNavigationAction.test.js-><BottomNavigationAction /> touch funct... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.test.js --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 7 | 0 | 7 | false | false | ["docs/src/pages/components/trap-focus/PortalTrapFocus.js->program->function_declaration:PortalTrapFocus", "docs/src/pages/components/trap-focus/DisableEnforceFocus.js->program->function_declaration:DisableEnforceFocus", "packages/material-ui-unstyled/src/Unstable_TrapFocus/Unstable_TrapFocus.js->program->function_decl... |
mui/material-ui | 26,170 | mui__material-ui-26170 | ['26166'] | 215794b567669951a61183d748c0b2be6483c3ea | diff --git a/docs/pages/api-docs/tab-list.json b/docs/pages/api-docs/tab-list.json
--- a/docs/pages/api-docs/tab-list.json
+++ b/docs/pages/api-docs/tab-list.json
@@ -1,5 +1,5 @@
{
- "props": { "children": { "type": { "name": "arrayOf", "description": "Array<element>" } } },
+ "props": { "children": { "type": ... | diff --git a/packages/material-ui-lab/src/TabList/TabList.test.js b/packages/material-ui-lab/src/TabList/TabList.test.js
--- a/packages/material-ui-lab/src/TabList/TabList.test.js
+++ b/packages/material-ui-lab/src/TabList/TabList.test.js
@@ -49,4 +49,15 @@ describe('<TabList />', () => {
expect(tabOne).to.have.at... | [TabList] Conditional rendering of Tab fails
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like ... | null | 2021-05-06 20:57:48+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/material-ui-lab/src/TabList/TabList.test.js-><TabList /> Material-UI component API applies the className to the root component', 'packages/material-ui-lab/src/TabList/TabList.test.js-><TabList /> Material-UI component API prop: component can render another root component with the `component` prop', 'packages... | ['packages/material-ui-lab/src/TabList/TabList.test.js-><TabList /> should accept a null child'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/material-ui/src/useAutocomplete/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded', 'packages/material-ui/src/BottomNavigationAction/BottomNavigationAction.test.js-><BottomNavigationAction /> touch funct... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/material-ui-lab/src/TabList/TabList.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 26,173 | mui__material-ui-26173 | ['24855'] | 205258b56faf4ac8096d10b62e22458dab52fb8e | diff --git a/docs/pages/api-docs/autocomplete.json b/docs/pages/api-docs/autocomplete.json
--- a/docs/pages/api-docs/autocomplete.json
+++ b/docs/pages/api-docs/autocomplete.json
@@ -40,12 +40,12 @@
"type": { "name": "func" },
"default": "(option) => option.label ?? option"
},
- "getOptionSelected... | diff --git a/packages/material-ui/src/Autocomplete/Autocomplete.test.js b/packages/material-ui/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui/src/Autocomplete/Autocomplete.test.js
@@ -1237,7 +1237,7 @@ describe('<Autocomplete />', () => ... | [Autocomplete] Rename getOptionSelected to optionEqualValue
<!-- Provide a general summary of the feature in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox ... | Would recommend using `optionEqualsValue` or `isOptionEqualToValue` to use natural language (just like React has `arePropsEqual`).
@mbrookes a preference?
I'd say most fields on the autocomplete would benefit from a rename. It's really hard to tell what the role of anything is just by looking at the name. I even ha... | 2021-05-06 23:53:54+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/material-ui/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: onHighlightChange should pass to onHighlightChange the correct value after filtering', 'packages/material-ui/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> warnings warn if the type of the value is wrong', 'packages/material-u... | ['packages/material-ui/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> warnings warn if isOptionEqualToValue match multiple values for a given option'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/material-ui/src/useAutocomplete/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded', 'packages/material-ui/src/BottomNavigationAction/BottomNavigationAction.test.js-><BottomNavigationAction /> touch funct... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/material-ui/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/src/pages/components/autocomplete/Asynchronous.js->program->function_declaration:Asynchronous", "packages/material-ui/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 26,231 | mui__material-ui-26231 | ['26157'] | b5f12b03ddff2fc4720be473c7ea2cbc61ca11ef | diff --git a/packages/material-ui/src/FilledInput/FilledInput.js b/packages/material-ui/src/FilledInput/FilledInput.js
--- a/packages/material-ui/src/FilledInput/FilledInput.js
+++ b/packages/material-ui/src/FilledInput/FilledInput.js
@@ -21,7 +21,12 @@ const useUtilityClasses = (styleProps) => {
input: ['input'],... | diff --git a/packages/material-ui/src/FilledInput/FilledInput.test.js b/packages/material-ui/src/FilledInput/FilledInput.test.js
--- a/packages/material-ui/src/FilledInput/FilledInput.test.js
+++ b/packages/material-ui/src/FilledInput/FilledInput.test.js
@@ -32,4 +32,9 @@ describe('<FilledInput />', () => {
const ... | [TextField] classes is not forwarded correctly on FilledInput
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox ... | Thanks for the report @nuanyang233. There are two problems regarding the issue. The first one, we need to pass all classes to the `InputCommponent` in the `FilledInput` x other input components (`OutlinedInput`, `Input`). This diff should help out with this specific use-case:
```diff --git a/packages/material-ui/src... | 2021-05-10 10:18:16+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/material-ui/src/Input/Input.test.js-><Input /> Material-UI component API should render without errors in ReactTestRenderer', 'packages/material-ui/src/Input/Input.test.js-><Input /> Material-UI component API spreads props to the root component', 'packages/material-ui/src/FilledInput/FilledInput.test.js-><Fil... | ['packages/material-ui/src/FilledInput/FilledInput.test.js-><FilledInput /> should forward classes to InputBase'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/material-ui/src/useAutocomplete/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded', 'packages/material-ui/src/BottomNavigationAction/BottomNavigationAction.test.js-><BottomNavigationAction /> touch funct... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/material-ui/src/FilledInput/FilledInput.test.js packages/material-ui/src/Input/Input.test.js packages/material-ui/src/OutlinedInput/OutlinedInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 26,323 | mui__material-ui-26323 | ['19696'] | bb0bbe22d77dabe69cd6cd64971158aaa70068c4 | diff --git a/docs/pages/api-docs/dialog-title.json b/docs/pages/api-docs/dialog-title.json
--- a/docs/pages/api-docs/dialog-title.json
+++ b/docs/pages/api-docs/dialog-title.json
@@ -2,13 +2,12 @@
"props": {
"children": { "type": { "name": "node" } },
"classes": { "type": { "name": "object" } },
- "disa... | diff --git a/packages/material-ui/src/DialogTitle/DialogTitle.test.js b/packages/material-ui/src/DialogTitle/DialogTitle.test.js
--- a/packages/material-ui/src/DialogTitle/DialogTitle.test.js
+++ b/packages/material-ui/src/DialogTitle/DialogTitle.test.js
@@ -8,18 +8,18 @@ describe('<DialogTitle />', () => {
descri... | [Dialog] Flatten DialogTitle DOM structure
## Summary 💡
`DialogTitle` should be flatter
## Examples 🌈
- https://codesandbox.io/s/old-pond-bpjb9
## Motivation 🔦
- Aligning items of the title
```jsx
<DialogTitle style={ display: 'flex', alignItems: 'center' }>
<SomeIcon />
My Title
</Dial... | Always in favor of removing DOM nodes when possible.
In this case, would it still allow developers to use a close button in the header? would it still allow a border-bottom on the element? I imagine it would in both cases.
> In this case, would it still allow developers to use a close button in the header? would it s... | 2021-05-16 07:03:20+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/material-ui/src/DialogTitle/DialogTitle.test.js-><DialogTitle /> should render string children as given string', 'packages/material-ui/src/DialogTitle/DialogTitle.test.js-><DialogTitle /> Material-UI component API should render without errors in ReactTestRenderer', 'packages/material-ui/src/DialogTitle/Dialo... | ['packages/material-ui/src/DialogTitle/DialogTitle.test.js-><DialogTitle /> Material-UI component API spreads props to the root component', 'packages/material-ui/src/DialogTitle/DialogTitle.test.js-><DialogTitle /> Material-UI component API ref attaches the ref'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/material-ui/src/useAutocomplete/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded', 'packages/material-ui/src/BottomNavigationAction/BottomNavigationAction.test.js-><BottomNavigationAction /> touch funct... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/material-ui/src/DialogTitle/DialogTitle.test.js --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 3 | 0 | 3 | false | false | ["docs/src/pages/components/dialogs/CustomizedDialogs.js->program->function_declaration:CustomizedDialogs", "docs/src/modules/utils/defaultPropsHandler.js->program->function_declaration:getPropsPath", "docs/src/pages/components/dialogs/SimpleDialog.js->program->function_declaration:SimpleDialog"] |
mui/material-ui | 26,460 | mui__material-ui-26460 | ['21503'] | bb0bbe22d77dabe69cd6cd64971158aaa70068c4 | diff --git a/docs/pages/api-docs/checkbox.json b/docs/pages/api-docs/checkbox.json
--- a/docs/pages/api-docs/checkbox.json
+++ b/docs/pages/api-docs/checkbox.json
@@ -40,7 +40,7 @@
"spread": true,
"forwardsRefTo": "HTMLSpanElement",
"filename": "/packages/material-ui/src/Checkbox/Checkbox.js",
- "inheritance"... | diff --git a/packages/material-ui/src/Checkbox/Checkbox.test.js b/packages/material-ui/src/Checkbox/Checkbox.test.js
--- a/packages/material-ui/src/Checkbox/Checkbox.test.js
+++ b/packages/material-ui/src/Checkbox/Checkbox.test.js
@@ -4,7 +4,7 @@ import { spy } from 'sinon';
import { createMount, describeConformanceV5... | Can't override IconButton styles in theme without affecting Checkbox and Switch
- [X] The issue is present in the latest release.
- [X] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
Any changes to Ic... | @depiction What change are you making that should only affect IconButton? A wrapper component may be more appropriate.
@mbrookes I changed the styles for all three variants to match my project's design (default, primary, secondary). The size, color, background color, border color, and border radius change based on the ... | 2021-05-26 08:27:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/material-ui/src/Checkbox/Checkbox.test.js-><Checkbox /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/internal/SwitchBase.test.js-><SwitchBase /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Radio/Radio.t... | ['packages/material-ui/src/internal/SwitchBase.test.js-><SwitchBase /> should render an icon and input inside the button by default', 'packages/material-ui/src/internal/SwitchBase.test.js-><SwitchBase /> can have edge'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/material-ui/src/useAutocomplete/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded', 'packages/material-ui/src/BottomNavigationAction/BottomNavigationAction.test.js-><BottomNavigationAction /> touch funct... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/material-ui/src/internal/SwitchBase.test.js packages/material-ui/src/Checkbox/Checkbox.test.js packages/material-ui/src/Radio/Radio.test.js --reporter /testbed/custom-reporter.js --exit | Refactoring | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 26,600 | mui__material-ui-26600 | ['26531'] | 1e9eda08729e3c51f081116c2f6b38816de27d57 | diff --git a/packages/mui-lab/src/internal/pickers/hooks/date-helpers-hooks.tsx b/packages/mui-lab/src/internal/pickers/hooks/date-helpers-hooks.tsx
--- a/packages/mui-lab/src/internal/pickers/hooks/date-helpers-hooks.tsx
+++ b/packages/mui-lab/src/internal/pickers/hooks/date-helpers-hooks.tsx
@@ -57,7 +57,7 @@ export ... | diff --git a/packages/mui-lab/src/DesktopTimePicker/DesktopTimePicker.test.tsx b/packages/mui-lab/src/DesktopTimePicker/DesktopTimePicker.test.tsx
--- a/packages/mui-lab/src/DesktopTimePicker/DesktopTimePicker.test.tsx
+++ b/packages/mui-lab/src/DesktopTimePicker/DesktopTimePicker.test.tsx
@@ -201,6 +201,29 @@ describe... | [TimePicker] Switching am pm does not change the time
<!-- Time picker not getting trigger on am pm change From timepicker popup -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked chec... | null | 2021-06-05 10:17:57+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-lab/src/DesktopTimePicker/DesktopTimePicker.test.tsx-><DesktopTimePicker /> opens when "Choose time" is clicked', 'packages/mui-lab/src/DesktopTimePicker/DesktopTimePicker.test.tsx-><DesktopTimePicker /> input validation should dispatch "shouldDisableTime-minutes" error', 'packages/mui-lab/src/DesktopTim... | ['packages/mui-lab/src/DesktopTimePicker/DesktopTimePicker.test.tsx-><DesktopTimePicker /> fires a change event when meridiem changes'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/mui-core/src/AutocompleteUnstyled/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-lab/src/DesktopTimePicker/DesktopTimePicker.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 26,746 | mui__material-ui-26746 | ['21902'] | 9acf8be6d2fd08210665c294830df3c85c014214 | diff --git a/docs/src/modules/branding/BrandingRoot.tsx b/docs/src/modules/branding/BrandingRoot.tsx
--- a/docs/src/modules/branding/BrandingRoot.tsx
+++ b/docs/src/modules/branding/BrandingRoot.tsx
@@ -101,15 +101,6 @@ let theme = createTheme({
'"Segoe UI Symbol"',
].join(','),
},
- breakpoints: {
- ... | diff --git a/packages/material-ui-system/src/createTheme/createBreakpoints.test.js b/packages/material-ui-system/src/createTheme/createBreakpoints.test.js
--- a/packages/material-ui-system/src/createTheme/createBreakpoints.test.js
+++ b/packages/material-ui-system/src/createTheme/createBreakpoints.test.js
@@ -18,7 +18,... | [theme] Improve the breakpoints values
According to the official https://material.io/design/layout/responsive-layout-grid.html#breakpoints, the breakpoints should be as follow:
xs: 0 - 600
sm: 600 - 1024
md: 1024 - 1440
lg: 1440 - 1920
xl: > 1920
Yet currently, MUI has the following as default
xs: 0 - 600
... | @matthewkwong2 Thanks for raising this issue, I have been keen to look into how we can improve the breakpoint values to better match the requirements of today's devices. IMHO we should partially ignore the recommendation of Material Design and look at what most teams use in their application/website, it will allow us t... | 2021-06-14 06:25:19+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/material-ui-system/src/createTheme/createBreakpoints.test.js->createBreakpoints down should work for xs', 'packages/material-ui/src/Grid/Grid.test.js-><Grid /> Material-UI component API should render without errors in ReactTestRenderer', 'packages/material-ui/src/styles/adaptV4Theme.test.js->adaptV4Theme the... | ['packages/material-ui/src/styles/responsiveFontSizes.test.js->responsiveFontSizes should disable vertical alignment', 'packages/material-ui-system/src/createTheme/createBreakpoints.test.js->createBreakpoints between should work', 'packages/material-ui-system/src/createTheme/createBreakpoints.test.js->createBreakpoints... | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes', 'packages/material-ui/src/useAutocomplete/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded', 'packages/material-ui/src/BottomNavigationAction/BottomNavigationAction.test.js-><BottomNavigationAction /> touch funct... | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/material-ui/src/Grid/Grid.test.js packages/material-ui/src/styles/responsiveFontSizes.test.js packages/material-ui/src/Stack/Stack.test.js packages/material-ui-system/src/createTheme/createBreakpoints.test.js packages/material-ui/sr... | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/styles/cssUtils.js->program->function_declaration:responsiveProperty", "packages/material-ui-system/src/createTheme/createBreakpoints.js->program->function_declaration:createBreakpoints"] |
mui/material-ui | 28,813 | mui__material-ui-28813 | ['28520'] | 182d4dc7726f6d77f0ca3863ca6fcdf9eec23a23 | diff --git a/docs/src/pages/system/properties/properties.md b/docs/src/pages/system/properties/properties.md
--- a/docs/src/pages/system/properties/properties.md
+++ b/docs/src/pages/system/properties/properties.md
@@ -62,6 +62,12 @@ Note that this table only lists custom properties, all other regular CSS propert
| `m... | diff --git a/packages/mui-system/src/spacing.test.js b/packages/mui-system/src/spacing.test.js
--- a/packages/mui-system/src/spacing.test.js
+++ b/packages/mui-system/src/spacing.test.js
@@ -168,6 +168,12 @@ describe('system spacing', () => {
paddingBottom: 8,
paddingTop: 8,
});
+ const ou... | Logical padding/margin properties should follow spacing rules
All `padding`/`margin` should use the `theme.spacing` function, but `padding{Inline/Block}{Start/End}` use value as pixel
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to MUI by creating a... | A work around could be including "px" or "rem" suffix for example `sx={{paddingInlineStart: '2px'}}` or `sx={{paddingInlineStart: '2rem'}}` Please do include your values in single quotes [Work around ](https://codesandbox.io/s/competent-mestorf-iqjvf)
We don't have support for the `paddingInline*` properties in the sy... | 2021-10-04 08:08:09+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/spacing.test.js->system spacing spacing should support string values', 'packages/mui-system/src/spacing.test.js->system spacing spacing warnings should warn if non integer value is used with theme.spacing defined as array', 'packages/mui-system/src/spacing.test.js->system spacing margin should... | ['packages/mui-system/src/spacing.test.js->system spacing padding should support full version', 'packages/mui-system/src/spacing.test.js->system spacing margin should support full version', 'packages/mui-system/src/spacing.test.js->system spacing spacing should support full version'] | ['packages/mui-core/src/AutocompleteUnstyled/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/spacing.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 30,560 | mui__material-ui-30560 | ['30230'] | 9acc563325ed3e9b2f741a4e422e5fec222a74b5 | diff --git a/packages/mui-material/src/OutlinedInput/NotchedOutline.js b/packages/mui-material/src/OutlinedInput/NotchedOutline.js
--- a/packages/mui-material/src/OutlinedInput/NotchedOutline.js
+++ b/packages/mui-material/src/OutlinedInput/NotchedOutline.js
@@ -21,7 +21,7 @@ const NotchedOutlineRoot = styled('fieldset... | diff --git a/packages/mui-material/src/OutlinedInput/NotchedOutline.test.js b/packages/mui-material/src/OutlinedInput/NotchedOutline.test.js
--- a/packages/mui-material/src/OutlinedInput/NotchedOutline.test.js
+++ b/packages/mui-material/src/OutlinedInput/NotchedOutline.test.js
@@ -54,4 +54,14 @@ describe('<NotchedOutl... | [TextField] Notch appears when no label has been added
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
When using `TextField` without setting a `label` it seems to show a notch that spans the whole length of the Input. With ... | Please create an isolated reproduction using Codesandbox (https://mui.com/r/issue-template-latest).
@michaldudak
Textfields with cutouts Version 5.2.4
(https://codesandbox.io/s/formpropstextfields-material-demo-forked-5ynnp?file=/demo.tsx)
Works fine with 5.2.3
@mbrookes why was this closed? It's still occurring ... | 2022-01-09 13:36:47+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/TextField/TextField.test.js-><TextField /> MUI component API spreads props to the root component', 'packages/mui-material/src/TextField/TextField.test.js-><TextField /> with a helper text should apply the className to the FormHelperText', 'packages/mui-material/src/TextField/TextField.test.j... | ['packages/mui-material/src/TextField/TextField.test.js-><TextField /> with an outline should render `0` label properly'] | ['packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.test.js->useAutocomplete should warn if the input is not binded'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/TextField/TextField.test.js packages/mui-material/src/OutlinedInput/NotchedOutline.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-material/src/OutlinedInput/NotchedOutline.js->program->function_declaration:NotchedOutline"] |
mui/material-ui | 33,312 | mui__material-ui-33312 | ['33258'] | 03b616a1e015ff6ccfb665c5156e1b5359d2a6f1 | diff --git a/docs/pages/base/api/use-autocomplete.json b/docs/pages/base/api/use-autocomplete.json
--- a/docs/pages/base/api/use-autocomplete.json
+++ b/docs/pages/base/api/use-autocomplete.json
@@ -155,6 +155,11 @@
"default": "false",
"required": true
},
+ "expanded": {
+ "type": { "name": "... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -2895,4 +2895,39 @@ describe('<Autocomplete />', (... | [Autocomplete] Add additional class names to Autocomplete if it is expanded
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
We'd like to introduce ~~3~~ an additional CSS "state"-classes to the Autocomplete component:
- ... | null | 2022-06-27 15:28:21+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> should apply the expanded class when listbox having options is opened', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> should apply the expanded class when listbox having no options is opened'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 34,138 | mui__material-ui-34138 | ['34137'] | 67073cc35a741e9f45aa0d54bc00918a9c05fdb4 | diff --git a/docs/pages/material-ui/api/step.json b/docs/pages/material-ui/api/step.json
--- a/docs/pages/material-ui/api/step.json
+++ b/docs/pages/material-ui/api/step.json
@@ -4,6 +4,7 @@
"children": { "type": { "name": "node" } },
"classes": { "type": { "name": "object" } },
"completed": { "type": { ... | diff --git a/packages/mui-material/src/Step/Step.test.js b/packages/mui-material/src/Step/Step.test.js
--- a/packages/mui-material/src/Step/Step.test.js
+++ b/packages/mui-material/src/Step/Step.test.js
@@ -16,7 +16,7 @@ describe('<Step />', () => {
muiName: 'MuiStep',
testVariantProps: { variant: 'foo' },
... | Stepper and Step use unstructured markup
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
Currently, Stepper and Step generate <div>s for markup, which is not semantic/structured.
### Expected behavior 🤔
Using a list would... | null | 2022-08-30 20:20:01+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Stepper/Stepper.test.tsx-><Stepper /> step connector should pass completed prop to connector when second step is completed', 'packages/mui-material/src/Stepper/Stepper.test.tsx-><Stepper /> step connector should have a default step connector', 'packages/mui-material/src/Stepper/Stepper.test.... | ['packages/mui-material/src/Stepper/Stepper.test.tsx-><Stepper /> MUI component API prop: component can render another root component with the `component` prop', 'packages/mui-material/src/Step/Step.test.js-><Step /> MUI component API prop: component can render another root component with the `component` prop'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Stepper/Stepper.test.tsx packages/mui-material/src/Step/Step.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,158 | mui__material-ui-34158 | ['33901'] | d88ab9ebdc63157a7efcf582e65d4f6c58e5f576 | diff --git a/docs/data/base/components/select/UnstyledSelectControlled.js b/docs/data/base/components/select/UnstyledSelectControlled.js
--- a/docs/data/base/components/select/UnstyledSelectControlled.js
+++ b/docs/data/base/components/select/UnstyledSelectControlled.js
@@ -165,7 +165,7 @@ export default function Unsty... | diff --git a/packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts b/packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts
--- a/packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts
+++ b/packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts
@@ -1,3 +1,4 @@
+impo... | [SelectUnstyled] Event is not passed to the onChange handler
The SelectUnstyled's (and MultiSelectUnstyled's) onChange handler is called with the selected value as the first parameter. This is not in line with other components (and native elements) that have an event associated with the change as the first parameter.
... | null | 2022-08-31 12:57:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/SelectUnstyled/SelectUnstyled.test.tsx->SelectUnstyled closes the listbox without selecting an option when focus is lost', 'packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts->useListbox defaultReducer action: optionClick remove the clicked value from the selection if selectMult... | ['packages/mui-base/src/MultiSelectUnstyled/MultiSelectUnstyled.test.tsx->MultiSelectUnstyled sets a value correctly when interacted by a user and external code', 'packages/mui-base/src/MultiSelectUnstyled/MultiSelectUnstyled.test.tsx->MultiSelectUnstyled prop: onChange is called when the Select value changes', 'packag... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/ListboxUnstyled/useControllableReducer.test.tsx packages/mui-base/src/MultiSelectUnstyled/MultiSelectUnstyled.test.tsx packages/mui-base/src/SelectUnstyled/SelectUnstyled.test.tsx packages/mui-base/src/ListboxUnstyled/d... | Feature | false | true | false | false | 10 | 0 | 10 | false | false | ["docs/data/base/components/select/UnstyledSelectObjectValuesForm.js->program->function_declaration:UnstyledSelectObjectValues", "packages/mui-base/src/ListboxUnstyled/useControllableReducer.ts->program->function_declaration:useStateChangeDetection", "docs/data/base/components/select/UnstyledSelectObjectValues.js->prog... |
mui/material-ui | 34,207 | mui__material-ui-34207 | ['34198'] | 1a4263a50af00eaffdca2e58b8ff16d62c4408a7 | diff --git a/docs/data/material/components/checkboxes/CheckboxLabels.js b/docs/data/material/components/checkboxes/CheckboxLabels.js
--- a/docs/data/material/components/checkboxes/CheckboxLabels.js
+++ b/docs/data/material/components/checkboxes/CheckboxLabels.js
@@ -7,6 +7,7 @@ export default function CheckboxLabels() ... | diff --git a/packages/mui-material/src/FormControlLabel/FormControlLabel.test.js b/packages/mui-material/src/FormControlLabel/FormControlLabel.test.js
--- a/packages/mui-material/src/FormControlLabel/FormControlLabel.test.js
+++ b/packages/mui-material/src/FormControlLabel/FormControlLabel.test.js
@@ -179,6 +179,23 @@ ... | [FormControlLabel] Support `required`
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
Implementing a labeled checkbox with a "required" asterisk, such as the following, is currently not possible without workarounds:
![ima... | null | 2022-09-06 17:04:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> with FormControl enabled should be overridden by props', 'packages/mui-material/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> MUI component API merges the class names provided in slotsProps.typography with ... | ['packages/mui-material/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> with FormControl required should be overridden by props', 'packages/mui-material/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> prop: required should visually show an asterisk but not include it in the a11y ... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/FormControlLabel/FormControlLabel.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/data/material/components/switches/SwitchLabels.js->program->function_declaration:SwitchLabels", "docs/data/material/components/checkboxes/CheckboxLabels.js->program->function_declaration:CheckboxLabels"] |
mui/material-ui | 34,478 | mui__material-ui-34478 | ['34410'] | 17695ff6be0aa6c7e4c81cadee5b9c8fb0c1a0b8 | diff --git a/packages/mui-joy/src/Radio/Radio.tsx b/packages/mui-joy/src/Radio/Radio.tsx
--- a/packages/mui-joy/src/Radio/Radio.tsx
+++ b/packages/mui-joy/src/Radio/Radio.tsx
@@ -236,6 +236,7 @@ const Radio = React.forwardRef(function Radio(inProps, ref) {
onChange,
onFocus,
onFocusVisible,
+ readOnly... | diff --git a/packages/mui-joy/src/Radio/Radio.test.js b/packages/mui-joy/src/Radio/Radio.test.js
--- a/packages/mui-joy/src/Radio/Radio.test.js
+++ b/packages/mui-joy/src/Radio/Radio.test.js
@@ -35,6 +35,18 @@ describe('<Radio />', () => {
expect(getByRole('radio')).to.have.property('name', 'bar');
});
+ it(... | [Joy][Radio] `required` prop does not work
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
When joy ui Radio compoment has required props, it can't passing down to `<input type="radio"/>` .
### Current behavior 😯
_No ... | null | 2022-09-26 07:19:17+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ["packages/mui-joy/src/Radio/Radio.test.js-><Radio /> MUI component API theme default components: respect theme's defaultProps", 'packages/mui-joy/src/Radio/Radio.test.js-><Radio /> the Checked state changes after change events', 'packages/mui-joy/src/Radio/Radio.test.js-><Radio /> MUI component API applies the root cl... | ['packages/mui-joy/src/Radio/Radio.test.js-><Radio /> renders a `role="radio"` with the required attribute', 'packages/mui-joy/src/Radio/Radio.test.js-><Radio /> renders a `role="radio"` with the readOnly attribute'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/Radio/Radio.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,548 | mui__material-ui-34548 | ['31203'] | 139724acb3ff53e7f4c8a3a3be90d004f8b8309f | diff --git a/packages/mui-system/src/palette.js b/packages/mui-system/src/palette.js
--- a/packages/mui-system/src/palette.js
+++ b/packages/mui-system/src/palette.js
@@ -1,20 +1,30 @@
import style from './style';
import compose from './compose';
+function transform(value, userValue) {
+ if (userValue === 'grey') ... | diff --git a/packages/mui-system/src/palette.test.js b/packages/mui-system/src/palette.test.js
new file mode 100644
--- /dev/null
+++ b/packages/mui-system/src/palette.test.js
@@ -0,0 +1,30 @@
+import { expect } from 'chai';
+import palette from './palette';
+
+const theme = {
+ palette: {
+ grey: { 100: '#f5f5f5' ... | [system] `grey` is no more recognized as color with the sx prop
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
I migrating project from v4 to v5
`backgroundColor:"grey"` doesn't work anymore with SX style. I ha... | The `grey` is part of the palette, so the `sx` prop will try to use the value from the palette if provided. However, in this case the value provided is an object, which is not a valid CSS property. You should use `grey.100` or any other palette value, for example: https://codesandbox.io/s/69629346-mui-v5-theming-with-e... | 2022-10-01 20:55:20+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/palette.test.js->palette should treat grey.100 as theme color'] | ['packages/mui-system/src/palette.test.js->palette should treat grey as CSS color'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/palette.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/mui-system/src/style.js->program->function_declaration:getValue", "packages/mui-system/src/palette.js->program->function_declaration:transform"] |
mui/material-ui | 36,426 | mui__material-ui-36426 | ['26492'] | a0c6c43187da86b1538685afdb529971ef57932f | diff --git a/docs/pages/base-ui/api/use-autocomplete.json b/docs/pages/base-ui/api/use-autocomplete.json
--- a/docs/pages/base-ui/api/use-autocomplete.json
+++ b/docs/pages/base-ui/api/use-autocomplete.json
@@ -68,6 +68,12 @@
"description": "(option: Value) => boolean"
}
},
+ "getOptionKey": ... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -2654,6 +2654,27 @@ describe('<Autocomplete />', (... | [Autocomplete] Not working properly with repeated options values
## Current Behavior 😯
Autocomplete when receiving repeated options does not filter and does not work correctly
## Expected Behavior 🤔
This only happens in version 5, in version 4 this works correctly.
## Steps to Reproduce 🕹
Enter this C... | Thanks for the report.
> Autocomplete when receiving repeated options does not filter and does not work correctly
Could you be a bit more specific what you mean with "correctly"? What are the concrete differences between v4 and v5? A screen recording might help here.
> Thanks for the report.
>
> > Autocomplete... | 2023-03-04 22:34:31+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> should specify option key for duplicate options'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["packages/mui-base/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete", "packages/mui-base/src/useAutocomplete/useAutocomplete.spec.ts->program->function_declaration:Component->method_definition:getOptionKey", "packages/mui-base/src/useAutocomplete/useAutocomplete.spec.ts->program->f... |
mui/material-ui | 37,118 | mui__material-ui-37118 | ['36283'] | 5b6e6c5ccf19ffbf251cd19ead587774f17f6ec0 | diff --git a/docs/data/base/components/select/UnstyledSelectIntroduction.js b/docs/data/base/components/select/UnstyledSelectIntroduction.js
--- a/docs/data/base/components/select/UnstyledSelectIntroduction.js
+++ b/docs/data/base/components/select/UnstyledSelectIntroduction.js
@@ -83,6 +83,7 @@ Button.propTypes = {
... | diff --git a/packages/mui-base/src/useList/listReducer.test.ts b/packages/mui-base/src/useList/listReducer.test.ts
--- a/packages/mui-base/src/useList/listReducer.test.ts
+++ b/packages/mui-base/src/useList/listReducer.test.ts
@@ -22,7 +22,7 @@ describe('listReducer', () => {
focusManagement: 'activeDescenda... | [Select][base] Consistency in props naming
Decide on the naming convention of functional props in SelectUnstyled. Currently, they are named inconsistently: `getSerializedValue`, `optionStringifier`, `renderValue`.
The possible options include:
1. A noun: `valueSerializer`, `optionStringifier`, `valueRenderer`.
2... | > 3. A noun with a "get" prefix: getSerializedValue, getStringifiedOption, getRenderedValue
This feels most intuitive for me. This is the pattern we use in other components too, for e.g. the Material UI's Autocomplete.
Thanks for your opinion. For me, either option 1 or 3 sounds best. Option 2 kind of suggests it's ... | 2023-05-01 12:05:18+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/useSelect/selectReducer.test.ts->selectReducer action: buttonClick highlights the first value if the select was closed and nothing was selected', 'packages/mui-base/src/useList/listReducer.test.ts->listReducer action: keyDown Enter key is pressed replaces the selectedValues with the highlighted ... | ['packages/mui-base/src/useList/listReducer.test.ts->listReducer action: textNavigation should highlight first match that is not disabled', 'packages/mui-base/src/useList/listReducer.test.ts->listReducer action: textNavigation should move highlight to disabled items if disabledItemsFocusable=true', 'packages/mui-base/s... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/useSelect/selectReducer.test.ts packages/mui-base/src/useList/listReducer.test.ts --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 4 | 0 | 4 | false | false | ["packages/mui-base/src/useMenu/useMenu.ts->program->function_declaration:useMenu", "packages/mui-base/src/useList/listReducer.ts->program->function_declaration:handleTextNavigation", "packages/mui-base/src/useList/useList.ts->program->function_declaration:useList", "packages/mui-base/src/useSelect/useSelect.ts->progra... |
mui/material-ui | 37,615 | mui__material-ui-37615 | ['37597'] | b97b3345e81931d588e5cf54e9a7ea6b4315c9df | diff --git a/docs/pages/base-ui/api/select.json b/docs/pages/base-ui/api/select.json
--- a/docs/pages/base-ui/api/select.json
+++ b/docs/pages/base-ui/api/select.json
@@ -1,5 +1,6 @@
{
"props": {
+ "areOptionsEqual": { "type": { "name": "func" } },
"autoFocus": { "type": { "name": "bool" }, "default": "fals... | diff --git a/packages/mui-base/src/Select/Select.test.tsx b/packages/mui-base/src/Select/Select.test.tsx
--- a/packages/mui-base/src/Select/Select.test.tsx
+++ b/packages/mui-base/src/Select/Select.test.tsx
@@ -851,6 +851,24 @@ describe('<Select />', () => {
});
});
+ describe('prop: areOptionsEqual', () => ... | [Select] onChange fired on init when passing initial values
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/hopeful-visvesvaraya-r527yc?file=/demo.tsx
Linked with [36783](... | null | 2023-06-16 19:57:12+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: onChange is called after initial render with `null` when the controlled value is set to a nonexistent option', "packages/mui-base/src/Select/Select.test.tsx-><Select /> MUI unstyled component API sets custom properties on the root slot's element with a ca... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: areOptionsEqual should use the `areOptionsEqual` prop to determine if an option is selected'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/Select/Select.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["packages/mui-base/src/utils/useControllableReducer.ts->program->function_declaration:useStateChangeDetection", "packages/mui-base/src/utils/useControllableReducer.ts->program->function_declaration:useControllableReducer", "packages/mui-base/src/useSelect/useSelect.ts->program->function_declaration:useSelect"] |
mui/material-ui | 37,845 | mui__material-ui-37845 | ['37000'] | ab2cb8cf9614ccab02b62a22de5129a1c2774d96 | diff --git a/packages/mui-joy/src/styles/extendTheme.ts b/packages/mui-joy/src/styles/extendTheme.ts
--- a/packages/mui-joy/src/styles/extendTheme.ts
+++ b/packages/mui-joy/src/styles/extendTheme.ts
@@ -379,8 +379,8 @@ export default function extendTheme(themeOptions?: CssVarsThemeOptions): Theme {
const fontFamilyF... | diff --git a/packages/mui-joy/src/styles/extendTheme.test.js b/packages/mui-joy/src/styles/extendTheme.test.js
--- a/packages/mui-joy/src/styles/extendTheme.test.js
+++ b/packages/mui-joy/src/styles/extendTheme.test.js
@@ -92,6 +92,16 @@ describe('extendTheme', () => {
});
});
+ it('should have correct font ... | [Joy] Using extendTheme with fontFamily can lead to invalid CSS variable names
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
From https://gitlab.com/sagotch/teztale-dataviz/ (and more precisely this merge request: https:... | Looks like a bug to me. | 2023-07-06 12:54:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/cssVars/createGetCssVar.test.ts->createGetCssVar default without prefix should return correct CSS var with comma', 'packages/mui-system/src/cssVars/createGetCssVar.test.ts->createGetCssVar does not add var() to CSS value', 'packages/mui-joy/src/styles/extendTheme.test.js->extendTheme theme.uns... | ['packages/mui-joy/src/styles/extendTheme.test.js->extendTheme should have correct font family'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/styles/extendTheme.test.js packages/mui-system/src/cssVars/createGetCssVar.test.ts --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-joy/src/styles/extendTheme.ts->program->function_declaration:extendTheme"] |
mui/material-ui | 37,908 | mui__material-ui-37908 | ['32967'] | 8db6cf291c07117b75173fbf2218bf530dfd78e3 | diff --git a/docs/data/joy/guides/themeable-component/StatComponent.js b/docs/data/joy/guides/themeable-component/StatComponent.js
new file mode 100644
--- /dev/null
+++ b/docs/data/joy/guides/themeable-component/StatComponent.js
@@ -0,0 +1,30 @@
+import * as React from 'react';
+import { styled } from '@mui/joy/styles... | diff --git a/packages/mui-system/src/createStyled.test.js b/packages/mui-system/src/createStyled.test.js
--- a/packages/mui-system/src/createStyled.test.js
+++ b/packages/mui-system/src/createStyled.test.js
@@ -89,6 +89,42 @@ describe('createStyled', () => {
});
});
+ it('default overridesResolver', () => {
... | Give the possibility to create new Components using the Material theming system for unique behavior
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
Lets say I use material ui and want to create a generic component of some s... | Thanks for the feedback, you can import the `useThemeProps` hook from '@mui/material/styles`. We could add a bit of docs around it.
Actually, I really like the idea for adding guide for how to create custom components, that would behave and have all features common for all Material UI components. One potential issue... | 2023-07-11 06:55:18+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/createStyled.test.js->createStyled displayName falls back to the decorated tag name', 'packages/mui-system/src/createStyled.test.js->createStyled styleOverrides callback support template string return from the callback', 'packages/mui-system/src/createStyled.test.js->createStyled styleOverride... | ['packages/mui-system/src/createStyled.test.js->createStyled default overridesResolver'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/createStyled.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/mui-system/src/createStyled.js->program->function_declaration:createStyled", "packages/mui-system/src/createStyled.js->program->function_declaration:defaultOverridesResolver"] |
mui/material-ui | 38,167 | mui__material-ui-38167 | ['38070'] | e9b324c880892e9c6ebd2a627f0311478f50252b | diff --git a/docs/data/joy/components/input/InputFormProps.js b/docs/data/joy/components/input/InputFormProps.js
--- a/docs/data/joy/components/input/InputFormProps.js
+++ b/docs/data/joy/components/input/InputFormProps.js
@@ -8,6 +8,9 @@ export default function InputFormProps() {
<form
onSubmit={(event) =>... | diff --git a/packages/mui-base/src/Select/Select.test.tsx b/packages/mui-base/src/Select/Select.test.tsx
--- a/packages/mui-base/src/Select/Select.test.tsx
+++ b/packages/mui-base/src/Select/Select.test.tsx
@@ -523,7 +523,7 @@ describe('<Select />', () => {
const handleSubmit = (event: React.FormEvent<HTMLForm... | Joy UI Select should support "required" prop for native validation
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
Autocomplete, Input and Textarea all support "required" prop for native validation, but not Select. The feature exists... | @michaldudak @mj12albert Which approach do you recommend? I feel that we should start with how Base UI will support this first.
The ways I see it:
1. use `aria-required` on the Select button slot
2. use the existing hidden `input` and add `required` to it.
The first option, I think. I don't know if setting `requir... | 2023-07-26 12:40:52+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: onChange is called after initial render with `null` when the controlled value is set to a nonexistent option', "packages/mui-base/src/Select/Select.test.tsx-><Select /> MUI unstyled component API sets custom properties on the root slot's element with a ca... | ['packages/mui-base/src/useSelect/useSelect.test.tsx->useSelect getHiddenInputProps [multiple with object value] returns correct value for the hidden input', 'packages/mui-base/src/useSelect/useSelect.test.tsx->useSelect getHiddenInputProps returns props for hidden input', 'packages/mui-base/src/useSelect/useSelect.tes... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/Select/Select.test.tsx packages/mui-base/src/useSelect/useSelect.test.tsx --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 4 | 0 | 4 | false | false | ["docs/data/joy/components/select/ControlledOpenSelect.js->program->function_declaration:ControlledOpenSelect", "packages/mui-base/src/useSelect/useSelect.ts->program->function_declaration:useSelect", "packages/mui-base/src/useSelect/useSelect.ts->program->function_declaration:defaultFormValueProvider", "docs/data/joy/... |
mui/material-ui | 38,788 | mui__material-ui-38788 | ['39281'] | 5047813ad0927fc040eca65d484ef4d6a8c8e9ec | diff --git a/packages/mui-base/src/useAutocomplete/useAutocomplete.js b/packages/mui-base/src/useAutocomplete/useAutocomplete.js
--- a/packages/mui-base/src/useAutocomplete/useAutocomplete.js
+++ b/packages/mui-base/src/useAutocomplete/useAutocomplete.js
@@ -293,21 +293,13 @@ export function useAutocomplete(props) {
... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -823,6 +823,83 @@ describe('<Autocomplete />', () ... | [Autocomplete] Pressing ArrowDown key behaves incorrectly when remaining options are disabled
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/https-github-com-mui-ma... | null | 2023-09-03 13:00:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: getOptionDisabled should skip disabled options at the end of the list when navigating via keyboard', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: getOptionDisabled should skip the first and last... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete->function_declaration:validOptionIndex"] |
mui/material-ui | 39,071 | mui__material-ui-39071 | ['38478'] | ba4c5596cdbbdf07e78cb10ca7231db9968812db | diff --git a/packages/mui-system/src/style.js b/packages/mui-system/src/style.js
--- a/packages/mui-system/src/style.js
+++ b/packages/mui-system/src/style.js
@@ -35,6 +35,14 @@ export function getStyleValue(themeMapping, transform, propValueFinal, userValue
value = getPath(themeMapping, propValueFinal) || userVal... | diff --git a/packages/mui-material/src/Typography/Typography.test.js b/packages/mui-material/src/Typography/Typography.test.js
--- a/packages/mui-material/src/Typography/Typography.test.js
+++ b/packages/mui-material/src/Typography/Typography.test.js
@@ -112,6 +112,20 @@ describe('<Typography />', () => {
});
}... | [material] Invalid `color` prop has no effect
- [X] I have searched the existing issues
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: [CodeSandbox fork](https://codesandbox.io/s/mui-invalid-color-is-silently-swallowed-gtwdg2) based on the [Typography demo](https://mui.com... | Hey @o-alexandrov, thanks for the report!
This is a bug. I think what's happening is that "background" is a key in the [theme palette](https://mui.com/material-ui/customization/default-theme/?expand-path=$.palette), so we try to use that value, but it's an object (with `"paper"` and `"default"` keys). The expected b... | 2023-09-20 09:27:35+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/Typography/Typography.test.js-><Typography /> MUI component API applies the root class to the root component if it has this class', 'packages/mui-material/src/Typography/Typography.test.js-><Typography /> should render body1 root by default', 'packages/mui-material/src/Typography/Typography.... | ['packages/mui-material/src/Typography/Typography.test.js-><Typography /> prop: color should check for invalid color value', 'packages/mui-system/src/style.test.js->style getStyleValue should warn on acceptable object', 'packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js->styleFunctionSx system resolves sy... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/style.test.js packages/mui-material/src/Typography/Typography.test.js packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js packages/mui-system/src/palette.test.js --reporter /testbed/custom-reporter.js --ex... | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-system/src/style.js->program->function_declaration:getStyleValue"] |
mui/material-ui | 40,180 | mui__material-ui-40180 | ['40112'] | 33f16fb66f22f99ea6cba9e4b6bc26fd85335390 | diff --git a/packages/mui-joy/src/FormLabel/FormLabel.tsx b/packages/mui-joy/src/FormLabel/FormLabel.tsx
--- a/packages/mui-joy/src/FormLabel/FormLabel.tsx
+++ b/packages/mui-joy/src/FormLabel/FormLabel.tsx
@@ -62,7 +62,16 @@ const FormLabel = React.forwardRef(function FormLabel(inProps, ref) {
name: 'JoyFormLabel... | diff --git a/packages/mui-joy/src/FormControl/FormControl.test.tsx b/packages/mui-joy/src/FormControl/FormControl.test.tsx
--- a/packages/mui-joy/src/FormControl/FormControl.test.tsx
+++ b/packages/mui-joy/src/FormControl/FormControl.test.tsx
@@ -505,4 +505,22 @@ describe('<FormControl />', () => {
expect(getByR... | [joy-ui][FormLabel] `htmlFor` attribute not working as expected (disappears when set to undefined)
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/p/sandbox/epic-turin... | I just realized that exactly the same behaviour can be observed with the `id` attribute (setting it to undefined overrides the default behaviour and removes it completely).
I can confirm it's a bug and appears to be easily fixable. Are you interested in creating a pull request? | 2023-12-11 23:13:31+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ["packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl /> MUI component API theme default components: respect theme's defaultProps", 'packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl /> Input should linked the label', 'packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl... | ['packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl /> should inherit id from FormControl if id is undefined', 'packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl /> should inherit htmlFor from FormControl if htmlFor is undefined'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/FormControl/FormControl.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 88 | tailwindlabs__tailwindcss-88 | ['18', '18'] | 1ab8bfbe15bdc630aad637f77fac7155256f3b0c | diff --git a/docs/source/docs/functions-and-directives.blade.md b/docs/source/docs/functions-and-directives.blade.md
--- a/docs/source/docs/functions-and-directives.blade.md
+++ b/docs/source/docs/functions-and-directives.blade.md
@@ -8,7 +8,7 @@ Tailwind exposes a few custom CSS functions and directives that can be us... | diff --git a/__tests__/fixtures/tailwind-input-with-explicit-screen-utilities.css b/__tests__/fixtures/tailwind-input-with-explicit-screen-utilities.css
new file mode 100644
--- /dev/null
+++ b/__tests__/fixtures/tailwind-input-with-explicit-screen-utilities.css
@@ -0,0 +1,11 @@
+@responsive {
+ .example {
+ ... | Screen-Utilities – problem with other postcss plugins
Hey there,
I love my utilities to be marked as ```!important``` because i've seen some people overwriting utilities (which is more than bad). If specitifity of e.g. a bem-item is higher the utility gets overridden.
## Example:
```css
.mx-auto { … }
/* t... | I think this is a reasonable idea.
What if we did something like this:
- Add an optional marker like `@tailwind screen-utilities` and in the processing phase where we generate those utilities, we first looked for that marker and if it was present, output the screen specific utilities there
- If that marker is ... | 2017-11-03 18:47:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/sanity.test.js->generates the right CSS',... | ['/testbed/__tests__/sanity.test.js->generates the right CSS with implicit screen utilities'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 109 | tailwindlabs__tailwindcss-109 | ['108'] | 9210b7f747d73888a6da5dc554e627f01e2c7265 | diff --git a/defaultConfig.js b/defaultConfig.js
--- a/defaultConfig.js
+++ b/defaultConfig.js
@@ -204,6 +204,7 @@ module.exports = {
'Fira Sans',
'Droid Sans',
'Helvetica Neue',
+ 'sans-serif',
],
'serif': [
'Constantia',
| diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -672,7 +672,7 @@ button,
}
.font-sans {
- font-family: -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Oxygen, Ubuntu, Canta... | .font-sans missing sans-serif
So the defaultConfig `.font-sans` font stack doesn't have `sans-serif` as the last fallback.
Although be unlikely that every font is missing, but if so the font stack actually falls back to Times New Roman on Chrome and Firefox (and most likely others).
ps.: Actually the only windows d... | Yeah, good point @tlgreg. I'll add that. | 2017-11-06 12:27:45+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/defineClasses.test.js->it generates a set... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 116 | tailwindlabs__tailwindcss-116 | ['112'] | ca366ee12d1f0f9bba4ae8ada0ccb43f865f84aa | diff --git a/css/preflight.css b/css/preflight.css
--- a/css/preflight.css
+++ b/css/preflight.css
@@ -528,6 +528,14 @@ iframe {
* Tailwind custom reset styles
*/
+*,
+*::before,
+*::after {
+ border-width: 0;
+ border-style: solid;
+ border-color: config('borderColors.default', currentColor);
+}
+
textarea {... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -528,6 +528,14 @@ iframe {
* Tailwind custom reset styles
*/
+*,
+*::before,
+*::after {
+ border-width: 0;
+ border-style: so... | Border Styles
`.border-dotted` is outputting `border-width: 0` due to the `borderStylesReset` (afaict). This means that `border-dotted` and `border-dashed` output `border-width: 0` nullifying the border style (as it removes the border).
Is this a bug or am I not understanding something? I can get `class=".border-dot... | null | 2017-11-06 16:20:37+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/defineClasses.test.js->it generates a set... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["src/generators/borderWidths.js->program->function_declaration:defaultBorder", "src/generators/borderWidths.js->program->function_declaration:sizedBorder"] |
tailwindlabs/tailwindcss | 119 | tailwindlabs__tailwindcss-119 | ['118'] | 7b5c4412e8f4333054fa4820775f279c4dd69361 | diff --git a/css/preflight.css b/css/preflight.css
--- a/css/preflight.css
+++ b/css/preflight.css
@@ -536,7 +536,7 @@ svg { fill: currentColor; }
button, input, optgroup, select, textarea { font-family: inherit; }
-input::placeholder {
+input::placeholder, textarea::placeholder {
color: inherit;
opacity... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -548,7 +548,8 @@ textarea {
font-family: inherit;
}
-input::placeholder {
+input::placeholder,
+textarea::placeholder {
color... | Default placeholder color discrepancy
The placeholder text for a textarea seems to be a different color from that of the inputs.
_Screenshot from Chrome Canary 64.0.3260.0_... | null | 2017-11-06 17:09:30+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/defineClasses.test.js->it generates a set... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 165 | tailwindlabs__tailwindcss-165 | ['159'] | 6bc3b0a9dd53f77555418b7b18d9b85ae7902c6e | diff --git a/src/generators/cursor.js b/src/generators/cursor.js
--- a/src/generators/cursor.js
+++ b/src/generators/cursor.js
@@ -3,6 +3,7 @@ import defineClasses from '../util/defineClasses'
export default function() {
return defineClasses({
'cursor-auto': { cursor: 'auto' },
+ 'cursor-default': { cursor:... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -3533,6 +3533,10 @@ button,
cursor: auto;
}
+.cursor-default {
+ cursor: default;
+}
+
.cursor-pointer {
cursor: pointer;
... | More cursor helpers
<!--
👋 Hey, thanks for taking an interest in Tailwind!
Please only open an issue here if you have a bug to report or a feature proposal you'd like to discuss.
If you need help, have questions about best practices, or want to start a discussion about anything else related to Tailwind, open ... | I think this is mostly because the ones you most commonly use are `pointer` and `not-allowed`, plus we have `auto` to set it back to the browser default.
Adding all the options would simply add bloat to the framework, and not really add much extra value. Plus, it's trivial to [add new utilities](https://tailwindcss.... | 2017-11-09 14:59:30+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/defineClasses.test.js->it generates a set... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 211 | tailwindlabs__tailwindcss-211 | ['210'] | a33596831e8762a985aad6902539c108d0ddfc82 | diff --git a/src/generators/spacing.js b/src/generators/spacing.js
--- a/src/generators/spacing.js
+++ b/src/generators/spacing.js
@@ -2,93 +2,78 @@ import _ from 'lodash'
import defineClasses from '../util/defineClasses'
function definePadding(padding) {
- return _.flatMap(padding, (size, modifier) => {
- retu... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -2680,25 +2680,36 @@ button,
max-height: 100vh;
}
-.pt-0 {
- padding-top: 0;
+.p-0 {
+ padding: 0;
}
-.pr-0 {
- padding-ri... | Unexpected padding specificity due to rule definition order
I noticed that `.pl-0` is defined _before_ `.p-4`, and thus they cannot be used together in order to set general-then-more-specific styles, e.g.
```
<div id="foo" class="p-4 pl-0">foo</div>
```
Expected: `#foo { left-padding: 0; }`
Actual: `#foo { l... | We can definitely look into tweaking the order these are defined to make that possible. It's hard to make this always work for everyone exactly as expected though, so generally we recommend avoiding using colliding styles, instead setting them separately:
```
<div class="py-4 pr-4"></div>
```
I think we can fix... | 2017-11-16 18:22:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/testbedlyClassPrefix.test.js->it prefixes... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Refactoring | false | true | false | false | 3 | 0 | 3 | false | false | ["src/generators/spacing.js->program->function_declaration:defineNegativeMargin", "src/generators/spacing.js->program->function_declaration:definePadding", "src/generators/spacing.js->program->function_declaration:defineMargin"] |
tailwindlabs/tailwindcss | 216 | tailwindlabs__tailwindcss-216 | ['215'] | d9c3f7b6cf3584858ea59bb191c87c95b6efc6f7 | diff --git a/css/preflight.css b/css/preflight.css
--- a/css/preflight.css
+++ b/css/preflight.css
@@ -535,11 +535,10 @@ fieldset {
*
* We can remove this when the reversion is in a normal Chrome release.
*/
-input[type="button" i],
-input[type="submit" i],
-input[type="reset" i],
-input[type="file" i]::-webkit-f... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -535,11 +535,10 @@ fieldset {
*
* We can remove this when the reversion is in a normal Chrome release.
*/
-input[type="button" i... | Border-radius preflight is always aplied
When I have a button: `<input type="button">` and apply the `rounded` class to it, it will still always be `border-radius: 0`.
The css that takes the highest priority is in the preflight: https://github.com/tailwindcss/tailwindcss/blob/be3f9d38505ff7be9e5f507c054c08d5cc221960... | Yeah, they have an element in the selector too.
This would be the best I think without fighting specificity and not increasing the size of utilities:
```css
input[type="button" i]:not([class*="rounded" i]),
input[type="submit" i]:not([class*="rounded" i]),
input[type="reset" i]:not([class*="rounded" i]),
input[... | 2017-11-18 15:39:14+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/testbedlyClassPrefix.test.js->it prefixes... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 236 | tailwindlabs__tailwindcss-236 | ['234'] | b696cbcbf00a1cb1d13f409fc2ca69e63600b6b8 | diff --git a/src/generators/position.js b/src/generators/position.js
--- a/src/generators/position.js
+++ b/src/generators/position.js
@@ -6,19 +6,23 @@ export default function() {
fixed: { position: 'fixed' },
absolute: { position: 'absolute' },
relative: { position: 'relative' },
- 'pin-t': { top: 0... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -3413,19 +3413,17 @@ button,
position: relative;
}
-.pin-t {
- top: 0;
+.pin-none {
+ top: auto;
+ right: auto;
+ bottom: au... | FR: Unsetting pin utilities
Right now it's not possible to "undo" pin properties of tailwind, for example if you want to pin something to the left, but on a different breakpoint pin it to the right:
`<div class="absolute pin-l sm:pin-r">Some thing</div>`
This will just cause the div to be full width, not pin it t... | Or as there is already a `pin-x` and `pin-y`, maybe `auto` the opposite side by default?
Though that adds unnecessary properties in most cases, so yeah, new classes sound better for me too. | 2017-11-24 14:58:59+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/mergeConfigWithDefaults.test.js->user modules are merged with default modules', '/testbed/__tests__/generateModules.test.js->variants can be different for each module', '/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/focusableAtRule.test.js->it adds... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 416 | tailwindlabs__tailwindcss-416 | ['413'] | 7831312c122fae4939744bfcf0d774f7d9927d8d | diff --git a/src/generators/textStyle.js b/src/generators/textStyle.js
--- a/src/generators/textStyle.js
+++ b/src/generators/textStyle.js
@@ -3,7 +3,7 @@ import defineClasses from '../util/defineClasses'
export default function() {
return defineClasses({
italic: { 'font-style': 'italic' },
- roman: { 'font... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -4205,7 +4205,7 @@ button,
font-style: italic;
}
-.roman {
+.not-italic {
font-style: normal;
}
@@ -4251,7 +4251,7 @@ butt... | Font styles and weights naming
Hi! I’m testing Tailwind, and have a question about some class naming.
I was expecting these rules to be declared by these classes:
- `font-style: normal` from `.font-normal` or `.normal`
- `font-weight: regular` from `.font-regular` or `.regular`
But Tailwind works this way:
- `... | You can change `.font-normal` to `.font-regular` in your own config if you like; we chose the font weight names based on this document from the W3C:
https://www.w3.org/TR/css-fonts-3/#font-weight-numeric-values
The `.roman` situation is admittedly more annoying. We wanted `.italic` for italicized text, so similar... | 2018-03-12 16:16:52+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/parseObjectStyles.test.js->it parses nested pseudo-selectors', '/testbed/__tests__/processPlugins.test.js... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Refactoring | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 417 | tailwindlabs__tailwindcss-417 | ['392'] | 02bac50589b69d0159c3d71fa1e4b0b3c10cf413 | diff --git a/src/lib/substituteVariantsAtRules.js b/src/lib/substituteVariantsAtRules.js
--- a/src/lib/substituteVariantsAtRules.js
+++ b/src/lib/substituteVariantsAtRules.js
@@ -48,7 +48,7 @@ export default function(config) {
atRule.before(atRule.clone().nodes)
- _.forEach(['focus', 'hover', 'group-hov... | diff --git a/__tests__/variantsAtRule.test.js b/__tests__/variantsAtRule.test.js
--- a/__tests__/variantsAtRule.test.js
+++ b/__tests__/variantsAtRule.test.js
@@ -69,9 +69,9 @@ test('it can generate group-hover variants', () => {
})
})
-test('it can generate hover and focus variants', () => {
+test('it can genera... | State Variants Priority Order
## Foreword ##
People are (or at least, I am) increasingly excited about the possibility of having everything they need out of the box thanks to Tailwind, and state variants are a vital part of building user interfaces.
Tailwind already supports a bunch of them, but new ones are always p... | ## Hover vs. Focus ##
Currently, hover has a higher priority than focus. However, as discussed in the PR #379, this choice has his pros and cons.
As it is now, buttons have huge benefits, whilst inputs may lack consistency.
Are you relying on or fighting against this order?
| 2018-03-12 16:46:11+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/parseObjectStyles.test.js->it parses nested pseudo-selectors', '/testbed/__tests__/processPlugins.test.js... | ['/testbed/__tests__/variantsAtRule.test.js->it can generate all variants', '/testbed/__tests__/variantsAtRule.test.js->it wraps the output in a responsive at-rule if responsive is included as a variant'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 445 | tailwindlabs__tailwindcss-445 | ['439'] | 14f1ba6cb9133a9eaddf17f124b80b76882d1dbd | diff --git a/src/generators/overflow.js b/src/generators/overflow.js
--- a/src/generators/overflow.js
+++ b/src/generators/overflow.js
@@ -8,6 +8,10 @@ export default function() {
'overflow-scroll': { overflow: 'scroll' },
'overflow-x-auto': { 'overflow-x': 'auto' },
'overflow-y-auto': { 'overflow-y': 'a... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -3215,6 +3215,22 @@ button,
overflow-y: auto;
}
+.overflow-x-hidden {
+ overflow-x: hidden;
+}
+
+.overflow-y-hidden {
+ overf... | Add overflow-x-hidden and overflow-y-hidden
They're useful because sometimes you want `overflow-x-hidden overflow-y-auto` (the default `overflow-x` when `overflow-y` is set to `auto` is also `auto`).
| Yes! I just had to manually add these to a site I was working on yesterday. I guess @adamwathan will be okay with a PR that includes this as well as tests for them (probably a PR for the docs too).
@benface do you wanna take care of it or should I open the PR myself?
@hacknug Actually after posting this issue I real... | 2018-04-02 16:59:13+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/parseObjectStyles.test.js->it parses nested pseudo-selectors', '/testbed/__tests__/variantsAtRule.test.js... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 463 | tailwindlabs__tailwindcss-463 | ['459'] | 737e0628dac5f0bfde43337ecf35927375e842ea | diff --git a/defaultConfig.stub.js b/defaultConfig.stub.js
--- a/defaultConfig.stub.js
+++ b/defaultConfig.stub.js
@@ -852,6 +852,7 @@ module.exports = {
| - responsive
| - hover
| - focus
+ | - focus-within
| - active
| - group-hover
|
diff --git a/src/lib/substituteVariantsAtRules.js b/... | diff --git a/__tests__/variantsAtRule.test.js b/__tests__/variantsAtRule.test.js
--- a/__tests__/variantsAtRule.test.js
+++ b/__tests__/variantsAtRule.test.js
@@ -70,6 +70,27 @@ test('it can generate focus variants', () => {
})
})
+test('it can generate focus-within variants', () => {
+ const input = `
+ @var... | Feature Proposal: Add :focus-within @variant
I'd be useful to have a `:focus-within` variant, for better styling control in forms.
Functionality-wise, it'd work exactly the same has `focus`, `active`, and `hover`, as its rules would too follow the structure `.[variant-name]:[class-name]:[variant-name]`, with no side... | If I'm not mistaken, this’d only imply changes in these two:
https://github.com/tailwindcss/tailwindcss/blob/0f0a4f45e8e2122e99850d11ad2c576be249e366/src/lib/substituteVariantsAtRules.js#L21-L34
https://github.com/tailwindcss/tailwindcss/blob/0f0a4f45e8e2122e99850d11ad2c576be249e366/src/lib/substituteVariantsAtRu... | 2018-05-08 10:02:22+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/responsiveAtRule.test.js->it can generate responsive variants', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/cli.test.js->stdout o... | ['/testbed/__tests__/variantsAtRule.test.js->it can generate focus-within variants'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 537 | tailwindlabs__tailwindcss-537 | ['525'] | 95f1d90b70c4bb318f35ea475b903d07aee01fb4 | diff --git a/css/preflight.css b/css/preflight.css
--- a/css/preflight.css
+++ b/css/preflight.css
@@ -1,17 +1,15 @@
-/*! normalize.css v7.0.0 | MIT License | github.com/necolas/normalize.css */
+/*! normalize.css v8.0.0 | MIT License | github.com/necolas/normalize.css */
/* Document
============================... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -1,17 +1,15 @@
-/*! normalize.css v7.0.0 | MIT License | github.com/necolas/normalize.css */
+/*! normalize.css v8.0.0 | MIT License |... | Normalize.css 8.0.0
I love Tailwind CSS! Great job. Thank you.
Tailwind uses normalize.css 7.0.0. Version 8.0.0 is now available. Does Tailwind use 7.0.0 for some very specific reason?
I would create a pull request with an update, but normalize.css is outside `package.json` – it functions as a part of `css/prefli... | My interpretation of the preflight file is that you use it if you want as little trouble as possible to get started.
If you want to use another version of normalize.css, I suggest you add postcss-normalize to your project. And put the tailwind specific styles of preflight.css in your css file. Maybe you don't need a... | 2018-08-19 23:06:43+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/responsiveAtRule.test.js->it can generate responsive variants', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/cli.test.js->stdout o... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Refactoring | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 553 | tailwindlabs__tailwindcss-553 | ['544'] | a63c976dc77137d6b67d718560a4b9847907880c | diff --git a/src/lib/substituteClassApplyAtRules.js b/src/lib/substituteClassApplyAtRules.js
--- a/src/lib/substituteClassApplyAtRules.js
+++ b/src/lib/substituteClassApplyAtRules.js
@@ -29,16 +29,29 @@ function normalizeClassName(className) {
return `.${escapeClassName(_.trimStart(className, '.'))}`
}
-function ... | diff --git a/__tests__/applyAtRule.test.js b/__tests__/applyAtRule.test.js
--- a/__tests__/applyAtRule.test.js
+++ b/__tests__/applyAtRule.test.js
@@ -192,3 +192,27 @@ test('you can apply utility classes that do not actually exist as long as they w
expect(result.warnings().length).toBe(0)
})
})
+
+test('you ca... | Allow prefix to be optional in @apply
Hi, I'm currently using tailwind with a prefix.
The one thing I don't particularly like is that it requires me to add the prefix before every @apply rule, which is more annoying the longer the prefix is.
I would love to be able to skip the prefix.
I think something like this w... | Would totally look at a PR for this, I think it's a reasonable suggestion 👍 | 2018-09-14 13:15:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/responsiveAtRule.test.js->it can generate responsive variants', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/cli.test.js->stdout o... | ['/testbed/__tests__/applyAtRule.test.js->you can apply utility classes without using the given prefix'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["src/lib/substituteClassApplyAtRules.js->program->function_declaration:findClass"] |
tailwindlabs/tailwindcss | 773 | tailwindlabs__tailwindcss-773 | ['771'] | 41d1c29d62dd3073e41e0d59de5e785cf3912d27 | diff --git a/src/lib/substituteScreenAtRules.js b/src/lib/substituteScreenAtRules.js
--- a/src/lib/substituteScreenAtRules.js
+++ b/src/lib/substituteScreenAtRules.js
@@ -1,17 +1,17 @@
import _ from 'lodash'
import buildMediaQuery from '../util/buildMediaQuery'
-export default function(config) {
+export default fun... | diff --git a/__tests__/screenAtRule.test.js b/__tests__/screenAtRule.test.js
new file mode 100644
--- /dev/null
+++ b/__tests__/screenAtRule.test.js
@@ -0,0 +1,47 @@
+import postcss from 'postcss'
+import plugin from '../src/lib/substituteScreenAtRules'
+import config from '../stubs/defaultConfig.stub.js'
+
+function r... | [beta.1] `No "md" screen found` error on build
I encountered a `No "md" screen found` error upon trying out `beta.1`. To attempt to rule out anything goofy I may have done with my own setup, here are reproduction steps using the Jigsaw Blog Starter Template upon which my site is based.
```shell
mkdir tailwind-next-... | What does your config file look like? My first guess is it’s still in the
old format.
On Sat, Mar 16, 2019 at 11:10 AM Michael Moussa <notifications@github.com>
wrote:
> I encountered a No "md" screen found error upon trying out beta.1. To
> attempt to rule out anything goofy I may have done with my own setup, here
> ... | 2019-03-16 18:20:21+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->plugins can add base styles with object syntax', '/testbed/__tests__/plugins/borderColor.test.js->colors can be a nested object', '/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->sele... | ['/testbed/__tests__/screenAtRule.test.js->it can generate media queries from configured screen sizes'] | ['/testbed/__tests__/cli.compile.test.js->compiles CSS file', '/testbed/__tests__/cli.test.js->compiles CSS file with autoprefixer'] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 774 | tailwindlabs__tailwindcss-774 | ['770'] | 8699f39ce17693a73cb7669cd2476729baea17a9 | diff --git a/src/util/resolveConfig.js b/src/util/resolveConfig.js
--- a/src/util/resolveConfig.js
+++ b/src/util/resolveConfig.js
@@ -2,12 +2,15 @@ import mergeWith from 'lodash/mergeWith'
import isFunction from 'lodash/isFunction'
import defaults from 'lodash/defaults'
import map from 'lodash/map'
+import get from... | diff --git a/__tests__/resolveConfig.test.js b/__tests__/resolveConfig.test.js
--- a/__tests__/resolveConfig.test.js
+++ b/__tests__/resolveConfig.test.js
@@ -322,8 +322,8 @@ test('functions in the default theme section are lazily evaluated', () => {
magenta: 'magenta',
yellow: 'yellow',
},
- ... | Replacing all colors breaks the build
This bug occured while beta testing the new v1 config, it's not an issue in the stable release.
With the following config:
```js
module.exports = {
theme: {
colors: {
blue: "#084062",
red: "#ee585f",
paper: "#f5f2ea"
}
}
};
```
The b... | You can work around this by explicitly defining `borderColor` in your theme.
```
module.exports = {
theme: {
colors: {
blue: "#084062",
red: "#ee585f",
paper: "#f5f2ea"
},
borderColor: "#333",
}
}
```
Trying to think through the best way to solve this problem at a general... | 2019-03-16 20:32:00+00:00 | TypeScript | FROM node:8.17
WORKDIR /testbed
COPY . .
RUN npm install
RUN npm run prebabelify
RUN npm run prepare | ['/testbed/__tests__/processPlugins.test.js->plugins can add base styles with object syntax', '/testbed/__tests__/plugins/borderColor.test.js->colors can be a nested object', '/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->sele... | ['/testbed/__tests__/resolveConfig.test.js->functions in the user theme section are lazily evaluated', '/testbed/__tests__/resolveConfig.test.js->theme values in the extend section extend the existing theme', '/testbed/__tests__/resolveConfig.test.js->the theme function can use a default value if the key is missing', '... | ['/testbed/__tests__/cli.compile.test.js->compiles CSS file', '/testbed/__tests__/cli.test.js->compiles CSS file with autoprefixer'] | npx jest --json --forceExit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["src/util/resolveConfig.js->program->function_declaration:resolveFunctionKeys"] |
tailwindlabs/tailwindcss | 849 | tailwindlabs__tailwindcss-849 | ['833'] | 4f58205d1d139dd2c296aaa8a01cb98383a7ea0a | diff --git a/src/util/configurePlugins.js b/src/util/configurePlugins.js
--- a/src/util/configurePlugins.js
+++ b/src/util/configurePlugins.js
@@ -1,7 +1,7 @@
export default function(pluginConfig, plugins) {
return Object.keys(plugins)
.filter(pluginName => {
- return pluginConfig[pluginName] !== false
+ ... | diff --git a/__tests__/configurePlugins.test.js b/__tests__/configurePlugins.test.js
--- a/__tests__/configurePlugins.test.js
+++ b/__tests__/configurePlugins.test.js
@@ -16,3 +16,15 @@ test('setting a plugin to false removes it', () => {
expect(configuredPlugins).toEqual(['fontSize', 'backgroundPosition'])
})
+
... | Ability to disable all core plugins (corePlugins: false?)
As discussed on Discord, it would be useful to be able to disable all core plugins without explicitly listing them all, for instance when using Tailwind in a test suite for a plugin. Adam suggested `corePlugins: false`.
| Looking for this as well! I use Tailwind to generate mini util files for use in Shadow DOM.
How can we provide a whitelist of plugins instead? | 2019-04-17 12:17:23+00:00 | TypeScript | FROM node:8.17
WORKDIR /testbed
COPY . .
RUN npm install
RUN npm run prebabelify
RUN npm run prepare | ['/testbed/__tests__/processPlugins.test.js->plugins can add base styles with object syntax', '/testbed/__tests__/plugins/borderColor.test.js->colors can be a nested object', '/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->sele... | ['/testbed/__tests__/configurePlugins.test.js->passing only false removes all plugins'] | ['/testbed/__tests__/cli.compile.test.js->compiles CSS file', '/testbed/__tests__/cli.test.js->compiles CSS file with autoprefixer'] | npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
coder/code-server | 4,597 | coder__code-server-4597 | ['4176'] | 9e583fa562322bfba95ec06c0537d112f51d61eb | diff --git a/ci/helm-chart/Chart.yaml b/ci/helm-chart/Chart.yaml
--- a/ci/helm-chart/Chart.yaml
+++ b/ci/helm-chart/Chart.yaml
@@ -20,4 +20,4 @@ version: 1.0.5
# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Ver... | diff --git a/test/unit/node/test-plugin/package.json b/test/unit/node/test-plugin/package.json
--- a/test/unit/node/test-plugin/package.json
+++ b/test/unit/node/test-plugin/package.json
@@ -3,7 +3,7 @@
"name": "test-plugin",
"version": "1.0.0",
"engines": {
- "code-server": "^3.7.0"
+ "code-server": "^4... | release: 4.0.0
<!-- Maintainer: fill out the checklist -->
## Checklist
- [x] Assign to next release manager
- [x] Close previous release milestone
- [x] Create next release milestone
- [x] Associate issue with next release milestone
| Any progress? There were some problems with the previous release. I want to experience 3.12.1
@pavlelee Very close! You'll see some remaining TODOs from [this PR](https://github.com/cdr/code-server/pull/4414). We need to create issues and add those to [this milestone](https://github.com/cdr/code-server/milestone/32). F... | 2021-12-09 20:43:13+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:14
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ['/testbed/test/unit/common/emitter.test.ts->should run the correct callbacks', '/testbed/test/unit/node/proxy_agent.test.ts->should return false when NO_PROXY is set to https://example.com', '/testbed/test/unit/node/util.test.ts->should return true with a hashedPassword for a SHA256 password', '/testbed/test/unit/node... | ['/testbed/test/unit/node/plugin.test.ts->plugin /test-plugin/test-app (websocket)', '/testbed/test/unit/node/plugin.test.ts->plugin /test-plugin/error', '/testbed/test/unit/node/plugin.test.ts->plugin /test-plugin/test-app', '/testbed/test/unit/node/plugin.test.ts->plugin /api/applications'] | ['/testbed/test/unit/node/testbed.test.ts->createApp should unlink a socket before listening on the socket'] | yarn test:unit --json --silent | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
coder/code-server | 4,678 | coder__code-server-4678 | ['4675'] | 3d999986b28fc01148650fc1122d321e16950ea2 | diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -22,6 +22,14 @@ VS Code v99.99.999
## [Unreleased](https://github.com/cdr/code-server/releases)
+VS Code v0.00.0
+
+### Changed
+
+- Add here
+
+## [4.0.1](https://github.com/cdr/code-server/releases/tag/v4.0.1) - 2022-01-04
+
VS Co... | diff --git a/test/e2e/extensions.test.ts b/test/e2e/extensions.test.ts
--- a/test/e2e/extensions.test.ts
+++ b/test/e2e/extensions.test.ts
@@ -7,6 +7,6 @@ describe("Extensions", true, () => {
await codeServerPage.executeCommandViaMenus("code-server: Get proxy URI")
- await codeServerPage.page.waitForSelecto... | release: 4.0.1
<!-- Maintainer: fill out the checklist -->
## Checklist
- [x] Assign to next release manager
- [x] Close previous release milestone
- [x] Create next release milestone
- [x] Associate issue with next release milestone
| null | 2022-01-04 17:27:59+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:14
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ["/testbed/test/unit/node/util.test.ts->should return ARGON2 for password with 'argon2'", '/testbed/test/unit/node/update.test.ts->should keep existing information', '/testbed/test/unit/node/routes/health.test.ts->/healthz (websocket)', '/testbed/test/unit/node/util.test.ts->should return true if is match', '/testbed/t... | ['/testbed/test/unit/node/plugin.test.ts->plugin /test-plugin/test-app (websocket)', '/testbed/test/unit/node/plugin.test.ts->plugin /test-plugin/error', '/testbed/test/unit/node/plugin.test.ts->plugin /test-plugin/test-app', '/testbed/test/unit/node/plugin.test.ts->plugin /api/applications'] | ['/testbed/test/unit/node/routes/vscode.test.ts->vscode should not redirect when last opened is ignored', '/testbed/test/unit/node/routes/vscode.test.ts->vscode should have a default workspace', '/testbed/test/unit/node/routes/vscode.test.ts->vscode should redirect to last query folder/workspace', '/testbed/test/unit/n... | yarn test:unit --json --silent | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
coder/code-server | 4,923 | coder__code-server-4923 | ['1466'] | 78658f1cf48a5e019a82cde937cfa8feed8b986b | diff --git a/src/node/app.ts b/src/node/app.ts
--- a/src/node/app.ts
+++ b/src/node/app.ts
@@ -11,7 +11,7 @@ import { disposer } from "./http"
import { isNodeJSErrnoException } from "./util"
import { handleUpgrade } from "./wsRouter"
-type ListenOptions = Pick<DefaultedArgs, "socket" | "port" | "host">
+type Listen... | diff --git a/test/unit/node/app.test.ts b/test/unit/node/app.test.ts
--- a/test/unit/node/app.test.ts
+++ b/test/unit/node/app.test.ts
@@ -107,6 +107,18 @@ describe("createApp", () => {
app.dispose()
})
+ it("should change the file mode of a socket", async () => {
+ const defaultArgs = await setDefaults({... | Add option to set unix socket permissions
Hello,
when using the --socket option, I can tell code-server which socket to use, but not the permissions. At the moment the default permissions are 0755, which means that only the user is able to write to the socket while it's world readable...
When running together wit... | I'd agree with this. Setting users/groups seems a bit odd to me though. Is there an example of software you know that has this syntax?
Usually a program/system has a configuration file where these settings are defined in. As most of the socket related stuff is handled by systemd on a newer Linux system, the settings lo... | 2022-02-28 14:07:07+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:14
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ["/testbed/test/unit/node/util.test.ts->should return ARGON2 for password with 'argon2'", '/testbed/test/unit/node/update.test.ts->should keep existing information', '/testbed/test/unit/node/routes/health.test.ts->/healthz (websocket)', '/testbed/test/unit/node/util.test.ts->should return true if is match', '/testbed/t... | ['/testbed/test/unit/node/cli.test.ts->parser should parse all available options', '/testbed/test/unit/node/cli.test.ts->parser should override with --link'] | ['/testbed/test/unit/node/routes/vscode.test.ts->vscode should do nothing when nothing is passed in', '/testbed/test/unit/node/routes/vscode.test.ts->vscode should load all route variations', '/testbed/test/unit/node/routes/vscode.test.ts->vscode should not redirect when last opened is ignored', '/testbed/test/unit/nod... | yarn test:unit --json --silent | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["src/node/cli.ts->program->function_declaration:setDefaults"] |
coder/code-server | 5,633 | coder__code-server-5633 | ['5632'] | 71a127a62befeff1d55efe70be8f182e01cb29b6 | diff --git a/src/browser/pages/login.html b/src/browser/pages/login.html
--- a/src/browser/pages/login.html
+++ b/src/browser/pages/login.html
@@ -10,7 +10,7 @@
http-equiv="Content-Security-Policy"
content="style-src 'self'; script-src 'self' 'unsafe-inline'; manifest-src 'self'; img-src 'self' data:; fon... | diff --git a/test/unit/node/cli.test.ts b/test/unit/node/cli.test.ts
--- a/test/unit/node/cli.test.ts
+++ b/test/unit/node/cli.test.ts
@@ -67,6 +67,8 @@ describe("parser", () => {
"1",
"--verbose",
+ ["--app-name", "custom instance name"],
+ ["--welcome-text", "welcome to code"... | [Feat]: allow setting the app name and a welcome text on login page
## What is your suggestion?
allowing to change the text and app / instance name on the login page
## Why do you want this feature?
telling apart multiple instances
## Are there any workarounds to get this functionality today?
you can fork ... | null | 2022-10-09 14:39:46+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:16
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ['/testbed/test/unit/node/heart.test.ts->should log a warning when isActive rejects', "/testbed/test/unit/node/util.test.ts->should return ARGON2 for password with 'argon2'", '/testbed/test/unit/node/routes/login.test.ts->should return correct app-name when unset', '/testbed/test/unit/node/util.test.ts->should return f... | ['/testbed/test/unit/node/cli.test.ts->parser should parse all available options', '/testbed/test/unit/node/routes/login.test.ts->login /login should return correct welcome text when none is set but app-name is', '/testbed/test/unit/node/routes/login.test.ts->login /login should return correct welcome text', '/testbed/... | ['/testbed/test/unit/node/testbed.test.ts->createApp should unlink a socket before listening on the socket'] | yarn test:unit --json --silent | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
coder/code-server | 6,115 | coder__code-server-6115 | ['5311'] | a44bd71043d5550f751ff6d06d6ea16ac2742118 | diff --git a/src/node/cli.ts b/src/node/cli.ts
--- a/src/node/cli.ts
+++ b/src/node/cli.ts
@@ -571,6 +571,9 @@ export async function setDefaults(cliArgs: UserProvidedArgs, configArgs?: Config
// Filter duplicate proxy domains and remove any leading `*.`.
const proxyDomains = new Set((args["proxy-domain"] || []).m... | diff --git a/test/unit/node/cli.test.ts b/test/unit/node/cli.test.ts
--- a/test/unit/node/cli.test.ts
+++ b/test/unit/node/cli.test.ts
@@ -43,6 +43,7 @@ describe("parser", () => {
delete process.env.PASSWORD
delete process.env.CS_DISABLE_FILE_DOWNLOADS
delete process.env.CS_DISABLE_GETTING_STARTED_OVERRI... | [Feat]: make VSCODE_PROXY_URI use the subdomain proxy when it is enabled
## What is your suggestion?
When `VSCODE_PROXY_URI` is enabled, use the subdomain proxy.
## Why do you want this feature?
Popular extensions like Tabnine can't use relative paths and need to be able to talk to code-server on specific por... | We might also want a way to override this for cases like Coder where we already provide a subdomain proxy outside of code-server. For this we can probably just check if that variable is already set and if so avoid overriding.
To implement we need to check the `proxy-domain` flag and use that in the environment vari... | 2023-03-28 20:03:27+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:16
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ['/testbed/test/unit/node/heart.test.ts->should log a warning when isActive rejects', "/testbed/test/unit/node/util.test.ts->should return ARGON2 for password with 'argon2'", '/testbed/test/unit/node/routes/login.test.ts->should return correct app-name when unset', '/testbed/test/unit/node/util.test.ts->should return f... | ['/testbed/test/unit/node/cli.test.ts->parser should set proxy uri to first domain', '/testbed/test/unit/node/cli.test.ts->parser should set proxy uri'] | ['/testbed/test/unit/node/testbed.test.ts->createApp should unlink a socket before listening on the socket'] | yarn test:unit --json --silent | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["src/node/cli.ts->program->function_declaration:setDefaults"] |
coder/code-server | 6,225 | coder__code-server-6225 | ['6195'] | 74af05dfbe0d5085ad2d1b71685cac4638372657 | diff --git a/patches/proxy-uri.diff b/patches/proxy-uri.diff
--- a/patches/proxy-uri.diff
+++ b/patches/proxy-uri.diff
@@ -113,7 +113,7 @@ Index: code-server/lib/vscode/src/vs/code/browser/workbench/workbench.ts
interface ICredential {
service: string;
-@@ -511,6 +512,38 @@ function doCreateUri(path: string, qu... | diff --git a/test/unit/node/cli.test.ts b/test/unit/node/cli.test.ts
--- a/test/unit/node/cli.test.ts
+++ b/test/unit/node/cli.test.ts
@@ -413,7 +413,7 @@ describe("parser", () => {
const defaultArgs = await setDefaults(args)
expect(defaultArgs).toEqual({
...defaults,
- "proxy-domain": ["coder.com... | Support proxying ports without separate sub-domains
### Is there an existing issue for this?
- [X] I have searched the existing issues
### OS/Web Information
- Web Browser: EDGE
- Local OS: Windows
- Remote OS: Linux
- Remote Architecture: x64
- `code-server --version`: 4.12.0
### Steps to Reproduce
config e... | Ah yeah the subdomain proxy requires that the port be the first and only part of the sub-domain, so something like `{{port}}.code.domain.tld` (with `proxy-domain` set to `code.domain.tld`) or `{{port}}.domain.tld` (with `proxy-domain` set to `domain.tld`) instead would work.
> Ah yeah the subdomain proxy requires that ... | 2023-05-20 11:02:02+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:16
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ['/testbed/test/unit/node/heart.test.ts->should log a warning when isActive rejects', '/testbed/test/unit/node/routes/login.test.ts->should return correct app-name when unset', '/testbed/test/unit/node/http.test.ts->http://localhost:8080 -> [forwarded: for=127.0.0.1, host=localhost:8081, proto=http]', '/testbed/test/un... | ['/testbed/test/unit/node/cli.test.ts->parser should set proxy uri to first domain', '/testbed/test/unit/node/cli.test.ts->parser should set proxy uri', '/testbed/test/unit/node/cli.test.ts->parser should filter proxy domains'] | ['/testbed/test/unit/node/testbed.test.ts->createApp should unlink a socket before listening on the socket'] | yarn test:unit --json --silent | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["src/node/cli.ts->program->function_declaration:setDefaults", "src/node/http.ts->program->function_declaration:getHost"] |
coder/code-server | 6,423 | coder__code-server-6423 | ['6422'] | 913fc3086678a9f265bdcb8ebbc68c1c199c33a7 | diff --git a/src/node/cli.ts b/src/node/cli.ts
--- a/src/node/cli.ts
+++ b/src/node/cli.ts
@@ -732,6 +732,9 @@ export function bindAddrFromArgs(addr: Addr, args: UserProvidedArgs): Addr {
if (args["bind-addr"]) {
addr = parseBindAddr(args["bind-addr"])
}
+ if (process.env.CODE_SERVER_HOST) {
+ addr.host ... | diff --git a/test/unit/node/cli.test.ts b/test/unit/node/cli.test.ts
--- a/test/unit/node/cli.test.ts
+++ b/test/unit/node/cli.test.ts
@@ -789,6 +789,50 @@ describe("bindAddrFromArgs", () => {
expect(actual).toStrictEqual(expected)
})
+ it("should use process.env.CODE_SERVER_HOST if set", () => {
+ const ... | [Feat]: Set the host address with environment variable
## What is your suggestion?
It would be nice if we could set the host address with an environment variable, just as like as the port.
## Why do you want this feature?
There is a [docker-based project](https://github.com/linuxserver/docker-code-server), and I c... | null | 2023-09-08 02:49:51+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:16
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ['/testbed/test/unit/node/heart.test.ts->should log a warning when isActive rejects', '/testbed/test/unit/node/routes/login.test.ts->should return correct app-name when unset', '/testbed/test/unit/node/http.test.ts->http://localhost:8080 -> [forwarded: for=127.0.0.1, host=localhost:8081, proto=http]', '/testbed/test/un... | ['/testbed/test/unit/node/cli.test.ts->bindAddrFromArgs should use process.env.CODE_SERVER_HOST if set'] | ['/testbed/test/unit/node/testbed.test.ts->createApp should unlink a socket before listening on the socket'] | yarn test:unit --json --silent | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["src/node/cli.ts->program->function_declaration:bindAddrFromArgs"] |
Significant-Gravitas/AutoGPT | 4,652 | Significant-Gravitas__AutoGPT-4652 | ['3681'] | 9150f32f8b8602395534795ddd2d930a1684e419 | diff --git a/autogpt/memory/message_history.py b/autogpt/memory/message_history.py
--- a/autogpt/memory/message_history.py
+++ b/autogpt/memory/message_history.py
@@ -14,7 +14,8 @@
is_string_valid_json,
)
from autogpt.llm.base import ChatSequence, Message, MessageRole, MessageType
-from autogpt.llm.utils import ... | diff --git a/tests/unit/test_message_history.py b/tests/unit/test_message_history.py
new file mode 100644
--- /dev/null
+++ b/tests/unit/test_message_history.py
@@ -0,0 +1,145 @@
+import math
+import time
+from unittest.mock import MagicMock
+
+import pytest
+
+from autogpt.agent import Agent
+from autogpt.config impor... | COMMAND = list_files - openai.error.InvalidRequestError: This model's maximum context length is 4097 tokens
### ⚠️ Search for existing issues first ⚠️
- [X] I have searched the existing issues, and there is no existing issue for my problem
### Which Operating System are you using?
Docker
### Which version of Auto-... | I also encountered the same problem and couldn't continue the project
It's coming from updating memory summary. That appears to be a global behaviour. Your are constrained by 4096 tokens context window given the model you are using - likely gpt 3.5 - if you used gpt-4, you would not error out here. I can think of addin... | 2023-06-11 09:10:14+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
# Set the working directory in the container
WORKDIR /testbed
# Install git and other dependencies
RUN apt-get update && apt-get install -y git
# Copy the current directory contents into the container at /testbed
C... | [] | ['tests/unit/test_message_history.py:None:test_message_history_batch_summary'] | null | python -m pytest /testbed/tests/unit/test_message_history.py -v | Bug Fix | false | false | false | true | 2 | 1 | 3 | false | false | ["autogpt/memory/message_history.py->module->class_definition:MessageHistory->function_definition:update_running_summary", "autogpt/memory/message_history.py->module->class_definition:MessageHistory->function_definition:summarize_batch", "autogpt/memory/message_history.py->module->class_definition:MessageHistory"] |
huggingface/transformers | 3,198 | huggingface__transformers-3198 | ['2508'] | 292186a3e7e1a819aa591901591673639c752157 | diff --git a/src/transformers/tokenization_xlm_roberta.py b/src/transformers/tokenization_xlm_roberta.py
--- a/src/transformers/tokenization_xlm_roberta.py
+++ b/src/transformers/tokenization_xlm_roberta.py
@@ -104,6 +104,7 @@ class XLMRobertaTokenizer(PreTrainedTokenizer):
vocab_files_names = VOCAB_FILES_NAMES
... | diff --git a/tests/test_tokenization_xlm_roberta.py b/tests/test_tokenization_xlm_roberta.py
--- a/tests/test_tokenization_xlm_roberta.py
+++ b/tests/test_tokenization_xlm_roberta.py
@@ -14,14 +14,113 @@
# limitations under the License.
+import os
import unittest
-from transformers.tokenization_xlm_roberta impo... | XLMRobertaTokenizer is a wrong tokenizer for XLMRoberta
## 🐛 Bug
<!-- Important information -->
Model I am using (Bert, XLNet....): XLMRoberta
Language I am using the model on (English, Chinese....): multi-language, but mostly english
The problem arise when:
try to tokenise a sentence that contains the ... | null | 2020-03-09 22:43:53+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
C... | ['tests/test_tokenization_xlm_roberta.py:XLMRobertaTokenizationTest:test_encode_plus_with_padding', 'tests/test_tokenization_xlm_roberta.py:XLMRobertaTokenizationTest:test_encode_input_type', 'tests/test_tokenization_xlm_roberta.py:XLMRobertaTokenizationTest:test_batch_encode_plus_padding', 'tests/test_tokenization_xlm... | ['tests/test_tokenization_xlm_roberta.py:XLMRobertaTokenizationTest:test_add_special_tokens', 'tests/test_tokenization_xlm_roberta.py:XLMRobertaTokenizationTest:test_full_tokenizer', 'tests/test_tokenization_xlm_roberta.py:XLMRobertaTokenizationTest:test_added_tokens_do_lower_case', 'tests/test_tokenization_xlm_roberta... | null | python -m pytest -v /testbed/tests/test_tokenization_xlm_roberta.py | Bug Fix | false | false | false | true | 2 | 2 | 4 | false | false | ["src/transformers/tokenization_xlm_roberta.py->module->class_definition:XLMRobertaTokenizer->function_definition:vocab_size", "src/transformers/tokenization_xlm_roberta.py->module->class_definition:XLMRobertaTokenizer->function_definition:__init__", "src/transformers/tokenization_xlm_roberta.py->module->class_definiti... |
huggingface/transformers | 3,716 | huggingface__transformers-3716 | ['3711'] | f8208fa456039b46873a2e497b6318d30a4fc84e | diff --git a/src/transformers/modeling_transfo_xl.py b/src/transformers/modeling_transfo_xl.py
--- a/src/transformers/modeling_transfo_xl.py
+++ b/src/transformers/modeling_transfo_xl.py
@@ -859,7 +859,7 @@ def forward(self, input_ids=None, mems=None, head_mask=None, inputs_embeds=None,
Return:
:obj:`tu... | diff --git a/tests/test_modeling_transfo_xl.py b/tests/test_modeling_transfo_xl.py
--- a/tests/test_modeling_transfo_xl.py
+++ b/tests/test_modeling_transfo_xl.py
@@ -164,7 +164,7 @@ def create_transfo_xl_lm_head(self, config, input_ids_1, input_ids_2, lm_labels)
return outputs
def check_transfo... | TransfoXLLMHead doesn't shift labels internally when called for loss
# 🐛 Bug
When called with labels to get the language-modeling loss, `TransfoXLLMHead.forward` computes the NLLLoss of the outputs directly against the labels, rather than against the shifted labels like the documentation indicates (and like the oth... | null | 2020-04-09 10:16:32+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
C... | ['tests/test_modeling_transfo_xl.py:TransfoXLModelTest:test_head_pruning_save_load_from_pretrained', 'tests/test_modeling_transfo_xl.py:TransfoXLModelTest:test_initialization', 'tests/test_modeling_transfo_xl.py:TransfoXLModelTest:test_head_pruning_save_load_from_config_init', 'tests/test_modeling_transfo_xl.py:Transfo... | ['tests/test_modeling_transfo_xl.py:TransfoXLModelTest:test_transfo_xl_lm_head'] | null | python -m pytest -v /testbed/tests/test_modeling_transfo_xl.py | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["src/transformers/modeling_transfo_xl_utilities.py->module->class_definition:ProjectedAdaptiveLogSoftmax->function_definition:forward", "src/transformers/modeling_transfo_xl.py->module->class_definition:TransfoXLLMHeadModel->function_definition:forward"] |
huggingface/transformers | 5,749 | huggingface__transformers-5749 | ['7665'] | 5668fdb09e1bcd888930c1ff242bf200649da39c | diff --git a/src/transformers/tokenization_bert.py b/src/transformers/tokenization_bert.py
--- a/src/transformers/tokenization_bert.py
+++ b/src/transformers/tokenization_bert.py
@@ -398,6 +398,7 @@ def tokenize(self, text, never_split=None):
"""
# union() returns a new set by concatenating the two se... | diff --git a/tests/test_tokenization_bert.py b/tests/test_tokenization_bert.py
--- a/tests/test_tokenization_bert.py
+++ b/tests/test_tokenization_bert.py
@@ -222,6 +222,17 @@ def test_is_punctuation(self):
self.assertFalse(_is_punctuation("A"))
self.assertFalse(_is_punctuation(" "))
+ def test_c... | tokenizer_bert.py not call _clean_text?
for transformers/src/transformers/tokenization_bert.py, there is a function called _clean_text.
But seems this function is not be called at all?
In google bert(https://github.com/google-research/bert/blob/master/tokenization.py) there exists a same function and that function ... | null | 2020-07-14 14:22:48+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
C... | ['tests/test_tokenization_bert.py:BertTokenizationTest:test_rust_and_python_full_tokenizers', 'tests/test_tokenization_bert.py:BertTokenizationTest:test_batch_encode_plus_batch_sequence_length', 'tests/test_tokenization_bert.py:BertTokenizationTest:test_is_punctuation', 'tests/test_tokenization_bert.py:BertTokenization... | ['tests/test_tokenization_bert.py:BertTokenizationTest:test_clean_text'] | null | pytest -v /testbed/tests/test_tokenization_bert.py | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["src/transformers/tokenization_bert.py->module->class_definition:BasicTokenizer->function_definition:tokenize"] |
huggingface/transformers | 6,744 | huggingface__transformers-6744 | ['4411'] | 42fddacd1cac3cc57c3326aa51a409f5090b1261 | diff --git a/docs/source/main_classes/pipelines.rst b/docs/source/main_classes/pipelines.rst
--- a/docs/source/main_classes/pipelines.rst
+++ b/docs/source/main_classes/pipelines.rst
@@ -21,6 +21,7 @@ There are two categories of pipeline abstractions to be aware about:
- :class:`~transformers.TokenClassificationPi... | diff --git a/tests/test_pipelines.py b/tests/test_pipelines.py
--- a/tests/test_pipelines.py
+++ b/tests/test_pipelines.py
@@ -28,6 +28,9 @@
]
TF_TRANSLATION_FINETUNED_MODELS = [("patrickvonplaten/t5-tiny-random", "translation_en_to_fr")]
+TEXT2TEXT_FINETUNED_MODELS = ["patrickvonplaten/t5-tiny-random"]
+TF_TEXT2TE... | Pipeline for Conditional Generation (T5 type models)
As text-to-text models (like T5) increase the accessibility of multi-task learning, it also makes sense to have a flexible "Conditional Generation" pipeline.
For example, I should be able to use this pipeline for a multitude of tasks depending on how I format the ... | Yes having a "Conditional Generation" pipeline makes sense given that variety of tasks can be solved using it. We can use T5, BART for these tasks as well as the new Encoder-Decoder. I would like to call it `TextToTextPipeline` though, since we can solve non-generative tasks also as demonstrated in the T5 paper. I thin... | 2020-08-26 12:14:44+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8.16-slim-buster
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
&& rm -rf /var/lib/apt/lists/*
# Install Python depen... | ['tests/test_pipelines.py:MonoColumnInputTestCase:test_torch_summarization', 'tests/test_pipelines.py:ZeroShotClassificationPipelineTests:test_torch_zero_shot_classification', 'tests/test_pipelines.py:MonoColumnInputTestCase:test_torch_fill_mask_with_targets', 'tests/test_pipelines.py:MonoColumnInputTestCase:test_torch... | ['tests/test_pipelines.py:MonoColumnInputTestCase:test_torch_text2text'] | null | pytest -v /testbed/tests/test_pipelines.py --junitxml=test-results.xml | Feature | false | false | false | true | 1 | 2 | 3 | false | false | ["src/transformers/pipelines.py->module->class_definition:Text2TextGenerationPipeline", "src/transformers/pipelines.py->module->class_definition:Text2TextGenerationPipeline->function_definition:__call__", "src/transformers/pipelines.py->module->class_definition:Text2TextGenerationPipeline->function_definition:__init__"... |
huggingface/transformers | 7,075 | huggingface__transformers-7075 | ['7072'] | 28cf873036d078b47fb9dd38ac3421a7c874da44 | diff --git a/examples/benchmarking/run_benchmark.py b/examples/benchmarking/run_benchmark.py
--- a/examples/benchmarking/run_benchmark.py
+++ b/examples/benchmarking/run_benchmark.py
@@ -20,7 +20,25 @@
def main():
parser = HfArgumentParser(PyTorchBenchmarkArguments)
- benchmark_args = parser.parse_args_into_... | diff --git a/tests/test_benchmark.py b/tests/test_benchmark.py
--- a/tests/test_benchmark.py
+++ b/tests/test_benchmark.py
@@ -24,10 +24,10 @@ def test_inference_no_configs(self):
benchmark_args = PyTorchBenchmarkArguments(
models=[MODEL_ID],
training=False,
- no_inference=... | Clean up `benchmark_args_utils.py` "no_..." arguments
# 🚀 Feature request
Currently we have a mixture of negative and positive formulated arguments, *e.g.* `no_cuda` and `training` here: https://github.com/huggingface/transformers/blob/0054a48cdd64e7309184a64b399ab2c58d75d4e5/src/transformers/benchmark/benchmark_ar... | null | 2020-09-11 16:15:48+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8.16-slim-buster
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
&& rm -rf /var/lib/apt/lists/*
# Install Python depen... | [] | ['tests/test_benchmark.py:BenchmarkTest:test_inference_encoder_decoder_with_configs', 'tests/test_benchmark.py:BenchmarkTest:test_save_csv_files', 'tests/test_benchmark.py:BenchmarkTest:test_inference_no_configs', 'tests/test_benchmark.py:BenchmarkTest:test_train_with_configs', 'tests/test_benchmark.py:BenchmarkTest:te... | null | pytest -v /testbed/tests/test_benchmark.py /testbed/tests/test_benchmark_tf.py | Refactoring | false | false | false | true | 40 | 14 | 54 | false | false | ["src/transformers/benchmark/benchmark_args.py->module->class_definition:PyTorchBenchmarkArguments", "src/transformers/benchmark/benchmark_utils.py->module->class_definition:Benchmark->function_definition:print_results", "src/transformers/benchmark/benchmark_utils.py->module->function_definition:measure_peak_memory_cpu... |
huggingface/transformers | 7,272 | huggingface__transformers-7272 | ['6256'] | 2c8ecdf8a87019c438262d8c692e1bdffe05149f | diff --git a/src/transformers/configuration_longformer.py b/src/transformers/configuration_longformer.py
--- a/src/transformers/configuration_longformer.py
+++ b/src/transformers/configuration_longformer.py
@@ -67,6 +67,5 @@ class LongformerConfig(RobertaConfig):
model_type = "longformer"
def __init__(self,... | diff --git a/tests/test_modeling_auto.py b/tests/test_modeling_auto.py
--- a/tests/test_modeling_auto.py
+++ b/tests/test_modeling_auto.py
@@ -183,14 +183,14 @@ def test_token_classification_model_from_pretrained(self):
def test_from_pretrained_identifier(self):
model = AutoModelWithLMHead.from_pretrained... | LongformerForSequenceClassification has unused layers, making it unable to fine-tune with Data Distributed Parallel (required for gradient checkpointing)
## Environment info
<!-- You can run the command `transformers-cli env` and copy-and-paste its output below.
Don't forget to fill out the missing fields in tha... | Hey @Weilin37 , sorry to answer so late - this looks like a difficult bug. Let's start with this:
Can you check if your code works on this branch: `try_if_works_for_longformer_mult_gpu` . The changes I did to the branch can be seen here: https://github.com/huggingface/transformers/pull/6607. Since the pooler is not ne... | 2020-09-20 18:33:14+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8.16-slim-buster
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
&& rm -rf /var/lib/apt/lists/*
# Install Python depen... | ['tests/test_modeling_auto.py:AutoModelTest:test_parents_and_children_in_mappings'] | ['tests/test_modeling_auto.py:AutoModelTest:test_from_pretrained_identifier', 'tests/test_modeling_auto.py:AutoModelTest:test_from_identifier_from_model_type'] | null | pytest -v /testbed/tests/test_modeling_auto.py | Bug Fix | false | false | false | true | 8 | 70 | 78 | false | false | ["src/transformers/modeling_mobilebert.py->module->class_definition:MobileBertModel->function_definition:__init__", "src/transformers/modeling_mobilebert.py->module->class_definition:MobileBertModel", "src/transformers/modeling_tf_bert.py->module->class_definition:TFBertForMaskedLM", "src/transformers/modeling_bert.py-... |
huggingface/transformers | 7,562 | huggingface__transformers-7562 | ['7514'] | 52f44dd6d23f5c1b3d550685c50281fa6ca12ff3 | diff --git a/docs/source/model_doc/longformer.rst b/docs/source/model_doc/longformer.rst
--- a/docs/source/model_doc/longformer.rst
+++ b/docs/source/model_doc/longformer.rst
@@ -90,6 +90,32 @@ LongformerTokenizerFast
.. autoclass:: transformers.LongformerTokenizerFast
:members:
+Longformer specific outputs
+~... | diff --git a/tests/test_modeling_common.py b/tests/test_modeling_common.py
--- a/tests/test_modeling_common.py
+++ b/tests/test_modeling_common.py
@@ -220,12 +220,13 @@ def test_attention_outputs(self):
for model_class in self.all_model_classes:
inputs_dict["output_attentions"] = True
... | [Longformer] Output both local attentions and global attentions when `output_attentions=True` -> Good Second Issue
# 🚀 Feature request
**Good Second Issue** - A more advanced issue for contributors who want to dive more into Longformer's attention mechanism.
Longformer currently only outputs global attentions, w... | I am working on a pull request to address this. I don't see any major challenge so far, but this made me realize how much `attentions` in Bert-like models and in Longformers are different. Why not replace `attentions` in the Longformer by `local_attentions`?
This means that the interface of Longformers would become ... | 2020-10-04 01:44:37+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8.16-slim-buster
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
&& rm -rf /var/lib/apt/lists/*
# Install Python depen... | ['tests/test_modeling_longformer.py:LongformerModelTest:test_for_multiple_choice', 'tests/test_modeling_longformer.py:LongformerModelIntegrationTest:test_mask_invalid_locations', 'tests/test_modeling_longformer.py:LongformerModelTest:test_head_pruning', 'tests/test_modeling_longformer.py:LongformerModelTest:test_initia... | ['tests/test_modeling_longformer.py:LongformerModelIntegrationTest:test_layer_attn_probs', 'tests/test_modeling_longformer.py:LongformerModelIntegrationTest:test_layer_global_attn', 'tests/test_modeling_longformer.py:LongformerModelIntegrationTest:test_layer_local_attn'] | null | pytest -v -s --disable-warnings /testbed/tests/test_modeling_common.py /testbed/tests/test_modeling_longformer.py /testbed/tests/test_modeling_tf_common.py /testbed/tests/test_modeling_tf_longformer.py | Feature | false | false | false | true | 16 | 11 | 27 | false | false | ["src/transformers/modeling_tf_longformer.py->module->class_definition:TFLongformerSelfAttention", "src/transformers/modeling_tf_longformer.py->module->class_definition:TFLongformerSelfAttention->function_definition:_compute_global_attn_output_from_hidden", "src/transformers/modeling_longformer.py->module->class_defini... |
huggingface/transformers | 8,435 | huggingface__transformers-8435 | ['5142'] | 4185b115d4b3fd408265ffd91581698325652c47 | diff --git a/src/transformers/tokenization_t5.py b/src/transformers/tokenization_t5.py
--- a/src/transformers/tokenization_t5.py
+++ b/src/transformers/tokenization_t5.py
@@ -249,8 +249,17 @@ def _convert_id_to_token(self, index):
def convert_tokens_to_string(self, tokens):
""" Converts a sequence of to... | diff --git a/tests/test_tokenization_t5.py b/tests/test_tokenization_t5.py
--- a/tests/test_tokenization_t5.py
+++ b/tests/test_tokenization_t5.py
@@ -222,3 +222,18 @@ def test_eos_in_input(self):
self.assertEqual(expected_src_tokens, src_ids)
self.assertEqual(expected_tgt_tokens, tgt_ids)
+
+ de... | T5 special tokens not mapped to unique indices in vocabulary
The docs recommend adding the special eos_token `<\s>` to the end of each string when encoding/decoding with `T5Tokenizer`. However, this (and the other special tokens e.g. `unk_token`, `pad_token` aren't assigned unique ids in the lookup vocabulary (they are... | Hey @sarahwie,
Thanks for your issue. I can reproduce the problem and see the reason for it. Currently, we rely on Google's sentencepiece tokenizer: https://github.com/google/sentencepiece for encoding and decoding in T5. What happens is that the `tokenizer.decode(tokens)` depends on the function
`sp_model.deco... | 2020-11-10 11:10:09+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8.16-slim-buster
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
&& rm -rf /var/lib/apt/lists/*
# Install Python depen... | ['tests/test_tokenization_t5.py:T5TokenizationTest:test_build_inputs_with_special_tokens', 'tests/test_tokenization_t5.py:T5TokenizationTest:test_number_of_added_tokens', 'tests/test_tokenization_t5.py:T5TokenizationTest:test_call', 'tests/test_tokenization_t5.py:T5TokenizationTest:test_batch_encode_plus_overflowing_to... | ['tests/test_tokenization_t5.py:T5TokenizationTest:test_fast_and_slow_same_result'] | null | pytest -v /testbed/tests/test_tokenization_t5.py | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["src/transformers/tokenization_t5.py->module->class_definition:T5Tokenizer->function_definition:convert_tokens_to_string"] |
huggingface/transformers | 12,981 | huggingface__transformers-12981 | ['12970'] | 75b8990d9068a2c6ef448c190f2595c17fbcb993 | diff --git a/src/transformers/trainer.py b/src/transformers/trainer.py
--- a/src/transformers/trainer.py
+++ b/src/transformers/trainer.py
@@ -1005,6 +1005,7 @@ def train(
kwargs:
Additional keyword arguments used to hide deprecated arguments
"""
+ resume_from_checkpoint = ... | diff --git a/tests/test_trainer.py b/tests/test_trainer.py
--- a/tests/test_trainer.py
+++ b/tests/test_trainer.py
@@ -827,6 +827,20 @@ def test_resume_training_with_randomness(self):
self.assertAlmostEqual(a, a1, delta=1e-8)
self.assertAlmostEqual(b, b1, delta=1e-8)
+ # regression for this issue... | `Trainer.train(resume_from_checkpoint=False)` is causing an exception
Since `resume_from_checkpoint` can be `str` and `bool` it should be possible to pass `False` to it.
But when `resume_from_checkpoint` is `False` it causes an exception here:
https://github.com/huggingface/transformers/blob/3d4b3bc3fd77e0e48e23644... | That seems like the right fix indeed. Please go ahead with a PR, thanks! :-) | 2021-08-02 16:23:41+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
COPY . .
# Install Py... | ['tests/test_trainer.py:TrainerIntegrationTest:test_number_of_steps_in_training', 'tests/test_trainer.py:TrainerIntegrationTest:test_resume_training_with_gradient_accumulation', 'tests/test_trainer.py:TrainerIntegrationTest:test_resume_training_with_randomness', 'tests/test_trainer.py:TrainerIntegrationTest:test_traini... | ['tests/test_trainer.py:TrainerIntegrationTest:test_training_with_resume_from_checkpoint_flase'] | null | python -m pytest /testbed/tests/test_trainer.py -v --junitxml=test-results.xml | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["src/transformers/trainer.py->module->class_definition:Trainer->function_definition:train"] |
huggingface/transformers | 13,436 | huggingface__transformers-13436 | ['13430'] | 2dd975b235118a578d34f7293e193d79a6437102 | diff --git a/src/transformers/models/clip/configuration_clip.py b/src/transformers/models/clip/configuration_clip.py
--- a/src/transformers/models/clip/configuration_clip.py
+++ b/src/transformers/models/clip/configuration_clip.py
@@ -230,6 +230,8 @@ class CLIPConfig(PretrainedConfig):
Dictionary of config... | diff --git a/tests/test_modeling_clip.py b/tests/test_modeling_clip.py
--- a/tests/test_modeling_clip.py
+++ b/tests/test_modeling_clip.py
@@ -20,6 +20,8 @@
import tempfile
import unittest
+import numpy as np
+
import requests
from transformers import CLIPConfig, CLIPTextConfig, CLIPVisionConfig
from transformer... | Difference between `logit_scale` initialisation in Transformers CLIP and the original OpenAI implementation.
I tried another training code based on the OpenAI'CLIP version: I found a difference at logit_scale between them. Does it mean temperature parameter? Is it the reason for loss rising?
huggingface transformers' ... | null | 2021-09-06 05:51:46+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
COPY . .
# Install Py... | ['tests/test_modeling_clip.py:CLIPModelTest:test_model_outputs_equivalence', 'tests/test_modeling_clip.py:CLIPVisionModelTest:test_hidden_states_output', 'tests/test_modeling_clip.py:CLIPVisionModelTest:test_torch_fx', 'tests/test_modeling_clip.py:CLIPTextModelTest:test_correct_missing_keys', 'tests/test_modeling_clip.... | ['tests/test_modeling_clip.py:CLIPModelTest:test_initialization'] | null | python -m pytest /testbed/tests/test_modeling_clip.py -v --junitxml=test-results.xml | Bug Fix | false | false | false | true | 1 | 3 | 4 | false | false | ["src/transformers/models/clip/modeling_flax_clip.py->module->class_definition:FlaxCLIPModule->function_definition:setup", "src/transformers/models/clip/configuration_clip.py->module->class_definition:CLIPConfig->function_definition:__init__", "src/transformers/models/clip/modeling_clip.py->module->class_definition:CLI... |
huggingface/transformers | 13,573 | huggingface__transformers-13573 | ['13463'] | 41c186d2a4c0b9ae24a388e341710b33b2c2cc4f | diff --git a/docs/source/model_doc/gpt2.rst b/docs/source/model_doc/gpt2.rst
--- a/docs/source/model_doc/gpt2.rst
+++ b/docs/source/model_doc/gpt2.rst
@@ -41,6 +41,8 @@ Tips:
pre-computed values in the context of text generation. For PyTorch, see `past_key_values` argument of the
:meth:`~transformers.GPT2Model.fo... | diff --git a/tests/test_modeling_gpt2.py b/tests/test_modeling_gpt2.py
--- a/tests/test_modeling_gpt2.py
+++ b/tests/test_modeling_gpt2.py
@@ -15,6 +15,7 @@
import datetime
+import math
import unittest
from transformers import GPT2Config, is_torch_available
@@ -96,7 +97,9 @@ def __init__(
def get_large_mo... | Upcasting of attention computation for reliable pretraining of GPT-2 models
# 🚀 Feature request
In a recent [talk](https://youtu.be/AYPOzc50PHw?t=3662) about pretraining language models as part of the [Mistral](https://github.com/stanford-crfm/mistral/) project @siddk mentioned that in order to achieve stable pretr... | Also related are https://github.com/huggingface/huggingface_hub/issues/300 and https://github.com/stanford-crfm/mistral/issues/86
Hey folks, sorry I'm late to the party. Replying here to just to centralize things.
The upcasting + scaled-dot product attn reordering + scaling implemented in Mistral is a pretty straig... | 2021-09-15 04:32:03+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
COPY . .
# Install Py... | ['tests/test_modeling_gpt2.py:GPT2ModelTest:test_load_with_mismatched_shapes', 'tests/test_modeling_gpt2.py:GPT2ModelTest:test_gpt2_double_lm_head_model', 'tests/test_modeling_gpt2.py:GPT2ModelTest:test_group_beam_search_generate_dict_output', 'tests/test_modeling_gpt2.py:GPT2ModelTest:test_sample_generate', 'tests/tes... | ['tests/test_modeling_gpt2.py:GPT2ModelTest:test_gpt2_weight_initialization'] | null | python -m pytest /testbed/tests/test_modeling_gpt2.py -v --junitxml=test-results.xml | Feature | false | false | false | true | 4 | 7 | 11 | false | false | ["src/transformers/models/gpt2/modeling_gpt2.py->module->class_definition:GPT2Attention->function_definition:_upcast_and_reordered_attn", "src/transformers/models/gpt2/modeling_gpt2.py->module->class_definition:GPT2Model->function_definition:__init__", "src/transformers/models/gpt2/modeling_gpt2.py->module->class_defin... |
huggingface/transformers | 13,865 | huggingface__transformers-13865 | ['13847'] | 3a8de58c5192b620228128430ea52e6eda81c40a | diff --git a/src/transformers/hf_argparser.py b/src/transformers/hf_argparser.py
--- a/src/transformers/hf_argparser.py
+++ b/src/transformers/hf_argparser.py
@@ -17,6 +17,7 @@
import re
import sys
from argparse import ArgumentDefaultsHelpFormatter, ArgumentParser, ArgumentTypeError
+from copy import copy
from enum... | diff --git a/tests/test_hf_argparser.py b/tests/test_hf_argparser.py
--- a/tests/test_hf_argparser.py
+++ b/tests/test_hf_argparser.py
@@ -126,8 +126,10 @@ def test_with_default_bool(self):
expected = argparse.ArgumentParser()
expected.add_argument("--foo", type=string_to_bool, default=False, const=... | Default arguments of clm example are confusing
I was having a look at the `run_clm.py` script and which new arguments are available to push to the hub.
```sh
python transformers\examples\pytorch\language-modeling\run_clm.py -h
```
I see the following options (note the True defaults for all):
```
--no_keep... | Unfortunately, since the two arguments are accepted, there is no way for us to automate a better documentation of them from the `HfArgumentParser` (if you have ideas, by all means!) so you should rely on the documentation of [`TrainingArguments`](https://huggingface.co/transformers/main_classes/trainer.html#trainingarg... | 2021-10-04 15:07:51+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
COPY . .
# Install Py... | ['tests/test_hf_argparser.py:HfArgumentParserTest:test_with_list', 'tests/test_hf_argparser.py:HfArgumentParserTest:test_with_required', 'tests/test_hf_argparser.py:HfArgumentParserTest:test_integration_training_args', 'tests/test_hf_argparser.py:HfArgumentParserTest:test_basic', 'tests/test_hf_argparser.py:HfArgumentP... | ['tests/test_hf_argparser.py:HfArgumentParserTest:test_with_default_bool'] | null | python -m pytest /testbed/tests/test_hf_argparser.py -v --junitxml=test-results.xml | Bug Fix | false | false | false | true | 1 | 1 | 2 | false | false | ["src/transformers/hf_argparser.py->module->class_definition:HfArgumentParser", "src/transformers/hf_argparser.py->module->class_definition:HfArgumentParser->function_definition:_add_dataclass_arguments"] |
huggingface/transformers | 13,919 | huggingface__transformers-13919 | ['13880'] | 279ce5b705a0b8689f2a8e5d5258dbb5421c9e6c | diff --git a/src/transformers/generation_stopping_criteria.py b/src/transformers/generation_stopping_criteria.py
--- a/src/transformers/generation_stopping_criteria.py
+++ b/src/transformers/generation_stopping_criteria.py
@@ -71,6 +71,12 @@ class MaxNewTokensCriteria(StoppingCriteria):
"""
def __init__(sel... | diff --git a/tests/test_generation_utils.py b/tests/test_generation_utils.py
--- a/tests/test_generation_utils.py
+++ b/tests/test_generation_utils.py
@@ -24,7 +24,13 @@
if is_torch_available():
import torch
- from transformers import BartForConditionalGeneration, BartTokenizer, top_k_top_p_filtering
+ fr... | GPT-J float16 model output stopping after first word
## Environment info
- `transformers` version: 4.11.2
- Platform: Linux-5.4.0-1045-aws-x86_64-with-glibc2.29
- Python version: 3.8.10
- PyTorch version (GPU?): 1.9.1+cu102 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU?): ... | Hi! This is because the`max_length` argument specifies the total length including the length of prompt tokens and here the length of prompt tokens is 209, which is more than `max_length` hence only one token is generated.
If you instead want to specify how many new tokens to generate then use the `max_new_tokens` ar... | 2021-10-07 10:27:12+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
COPY . .
# Install Py... | ['tests/test_generation_utils.py:GenerationIntegrationTests:test_max_length_backward_compat_greedy', 'tests/test_generation_utils.py:GenerationIntegrationTests:test_max_length_backward_compat_group_beam_search', 'tests/test_generation_utils.py:GenerationIntegrationTests:test_max_length_backward_compat_sample', 'tests/t... | ['tests/test_generation_utils.py:GenerationIntegrationTests:test_max_new_tokens_decoder_only', 'tests/test_generation_utils.py:GenerationIntegrationTests:test_max_new_tokens_encoder_decoder'] | null | python -m pytest /testbed/tests/test_generation_utils.py --json-report --json-report-file=report.json -v | Bug Fix | false | false | false | true | 2 | 1 | 3 | false | false | ["src/transformers/generation_utils.py->module->class_definition:GenerationMixin->function_definition:_get_stopping_criteria", "src/transformers/generation_stopping_criteria.py->module->class_definition:MaxNewTokensCriteria->function_definition:__init__", "src/transformers/generation_utils.py->module->class_definition:... |
huggingface/transformers | 13,989 | huggingface__transformers-13989 | ['13522'] | 408b2d2bd08f667cf4154730cc323c4e49657eed | diff --git a/docs/source/model_doc/auto.rst b/docs/source/model_doc/auto.rst
--- a/docs/source/model_doc/auto.rst
+++ b/docs/source/model_doc/auto.rst
@@ -27,7 +27,32 @@ Instantiating one of :class:`~transformers.AutoConfig`, :class:`~transformers.Au
will create a model that is an instance of :class:`~transformers.B... | diff --git a/tests/test_configuration_auto.py b/tests/test_configuration_auto.py
--- a/tests/test_configuration_auto.py
+++ b/tests/test_configuration_auto.py
@@ -14,6 +14,7 @@
# limitations under the License.
import os
+import tempfile
import unittest
from transformers.models.auto.configuration_auto import CON... | The new impl for CONFIG_MAPPING prevents users from adding any custom models
## Environment info
<!-- You can run the command `transformers-cli env` and copy-and-paste its output below.
Don't forget to fill out the missing fields in that output! -->
- `transformers` version: 4.10+
- Platform: Ubuntu 18.04
-... | Adding a config/model/tokenizer to those constants wasn't really supported before (but I agree it may have worked in some situations). A mechanism to add a custom model/config/tokenizer is on the roadmap!
Slightly different but which may be of interest, we are also starting to implement support for custom modeling (so... | 2021-10-13 18:33:16+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
&& rm -rf /var/lib/apt/lists/*
# Copy the repository contents
COPY . .
# Install Py... | ['tests/test_modeling_auto.py:AutoModelTest:test_from_pretrained_identifier', 'tests/test_modeling_auto.py:AutoModelTest:test_parents_and_children_in_mappings', 'tests/test_configuration_auto.py:AutoConfigTest:test_config_model_type_from_model_identifier', 'tests/test_modeling_auto.py:AutoModelTest:test_from_pretrained... | ['tests/test_tokenization_auto.py:AutoTokenizerTest:test_new_tokenizer_fast_registration', 'tests/test_configuration_auto.py:AutoConfigTest:test_new_config_registration', 'tests/test_modeling_tf_auto.py:TFAutoModelTest:test_new_model_registration', 'tests/test_tokenization_auto.py:AutoTokenizerTest:test_new_tokenizer_r... | null | python -m pytest -v /testbed/tests/test_configuration_auto.py /testbed/tests/test_modeling_auto.py /testbed/tests/test_modeling_tf_auto.py /testbed/tests/test_tokenization_auto.py --junitxml=test-results.xml | Feature | false | false | false | true | 18 | 7 | 25 | false | false | ["src/transformers/models/auto/auto_factory.py->module->class_definition:_LazyAutoMapping->function_definition:items", "src/transformers/models/auto/tokenization_auto.py->module->class_definition:AutoTokenizer->function_definition:register", "src/transformers/models/auto/auto_factory.py->module->class_definition:_LazyA... |
huggingface/transformers | 14,355 | huggingface__transformers-14355 | ['14332'] | 700a748fe6f0ed62185710f20e1c78e083edc14b | diff --git a/docs/source/model_doc/segformer.rst b/docs/source/model_doc/segformer.rst
--- a/docs/source/model_doc/segformer.rst
+++ b/docs/source/model_doc/segformer.rst
@@ -38,6 +38,58 @@ Cityscapes validation set and shows excellent zero-shot robustness on Cityscapes
This model was contributed by `nielsr <https://h... | diff --git a/tests/test_feature_extraction_beit.py b/tests/test_feature_extraction_beit.py
--- a/tests/test_feature_extraction_beit.py
+++ b/tests/test_feature_extraction_beit.py
@@ -17,6 +17,7 @@
import unittest
import numpy as np
+from datasets import load_dataset
from transformers.file_utils import is_torch_a... | `SegformerFeatureExtractor` trying to access non-existent `.ndim` attribute
## Environment info
- `transformers` version: 4.12.3
- Platform: AWS Sagemaker with Amazon Linux 2 base
- Python version: 3.8.12
### Who can help
@NielsRogge or @sgugger
## Information
Model I am using (Bert, XLNet ...): Segforme... | I did some more debugging on this and it looks like the problem is with the application of `self.pad()` to the `segmentation_maps`.
The `segmentation_maps` are `PIL.Image` objects when they are passed to `self.pad()`. This is not a problem for the `images` when they are passed to `self.pad()` because `images` have a... | 2021-11-10 12:20:52+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install system dependencies
RUN apt-get update && apt-get install -y \
git \
build-essential \
python3-dev \
&& rm -rf /var/lib/apt/lists/*
# Copy reposit... | ['tests.test_feature_extraction_segformer.SegformerFeatureExtractionTest:test_init_without_params', 'tests.test_feature_extraction_beit.BeitFeatureExtractionTest:test_init_without_params', 'tests.test_feature_extraction_beit.BeitFeatureExtractionTest:test_feat_extract_to_json_string', 'tests.test_feature_extraction_bei... | ['tests.test_feature_extraction_segformer.SegformerFeatureExtractionTest:test_call_pil:', 'tests.test_feature_extraction_segformer.SegformerFeatureExtractionTest:test_call_numpy:', 'tests.test_feature_extraction_segformer.SegformerFeatureExtractionTest:test_call_pytorch:', 'tests.test_feature_extraction_segformer.Segfo... | null | python -m unittest /testbed/tests/test_feature_extraction_beit.py /testbed/tests/test_feature_extraction_segformer.py -v | Bug Fix | false | false | false | true | 16 | 8 | 24 | false | false | ["src/transformers/models/segformer/feature_extraction_segformer.py->module->function_definition:is_seq_of", "src/transformers/models/segformer/feature_extraction_segformer.py->module->function_definition:_scale_size", "src/transformers/models/beit/feature_extraction_beit.py->module->class_definition:BeitFeatureExtract... |
huggingface/transformers | 14,779 | huggingface__transformers-14779 | ['12118'] | 7ae6f070044b0171a71f3269613bf02fd9fca6f2 | diff --git a/src/transformers/generation_utils.py b/src/transformers/generation_utils.py
--- a/src/transformers/generation_utils.py
+++ b/src/transformers/generation_utils.py
@@ -43,6 +43,7 @@
from .generation_stopping_criteria import (
MaxLengthCriteria,
MaxTimeCriteria,
+ StoppingCriteria,
Stopping... | diff --git a/tests/test_generation_utils.py b/tests/test_generation_utils.py
--- a/tests/test_generation_utils.py
+++ b/tests/test_generation_utils.py
@@ -52,7 +52,7 @@
TopKLogitsWarper,
TopPLogitsWarper,
)
- from transformers.generation_stopping_criteria import MaxLengthCriteria, StoppingCrit... | Passing a custom stopping_criteria list to model.generate() yields a multiple value error for that keyword arg
---
name: "\U0001F41B Bug Report"
about: Submit a bug report to help us improve transformers
title: ''
labels: ''
assignees: ''
---
## Environment info
<!-- You can run the command `transformers-... | Hey @bitbanger,
Could you provide a reproducible code snippet that we could just copy paste into a python shell to reproduce the error? :-) Thanks!
Hi there! Thanks for your response! Sure, here you go. I've confirmed that this code yields the error when run in the environment described in my report:
```
import ... | 2021-12-15 11:28:36+00:00 | Python | FROM public.ecr.aws/docker/library/python:3.8-slim as builder
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
WORKDIR /testbed
# Install build dependencies
RUN apt-get update && apt-get install -y git build-essential python3-dev && rm -rf /var/lib/apt/lists/*
# Copy all repository files
... | ['tests/test_generation_utils.py:GenerationIntegrationTests:test_encoder_decoder_generate_with_inputs_embeds', 'tests/test_generation_utils.py:GenerationIntegrationTests:test_max_length_backward_compat_group_beam_search', 'tests/test_generation_utils.py:GenerationIntegrationTests:test_generate_too_many_encoder_kwargs',... | ['tests/test_generation_utils.py:GenerationIntegrationTests:test_custom_stopping_criteria', 'tests/test_generation_utils.py:GenerationIntegrationTests:test_custom_logits_processor', 'tests/test_generation_utils.py:GenerationIntegrationTests:test_custom_stopping_criteria_overload_error'] | null | python -m pytest -v --tb=short /testbed/tests/test_generation_utils.py | Bug Fix | false | false | false | true | 5 | 1 | 6 | false | false | ["src/transformers/generation_utils.py->module->class_definition:GenerationMixin", "src/transformers/generation_utils.py->module->class_definition:GenerationMixin->function_definition:_get_stopping_criteria", "src/transformers/generation_utils.py->module->class_definition:GenerationMixin->function_definition:generate",... |
huggingface/transformers | 15,158 | huggingface__transformers-15158 | ['15156'] | c4f7eb124b218741d66dd1d86b5d744024a78f6f | diff --git a/src/transformers/models/bert/tokenization_bert_fast.py b/src/transformers/models/bert/tokenization_bert_fast.py
--- a/src/transformers/models/bert/tokenization_bert_fast.py
+++ b/src/transformers/models/bert/tokenization_bert_fast.py
@@ -188,15 +188,17 @@ def __init__(
**kwargs,
)
-... | diff --git a/tests/test_tokenization_bert.py b/tests/test_tokenization_bert.py
--- a/tests/test_tokenization_bert.py
+++ b/tests/test_tokenization_bert.py
@@ -299,3 +299,40 @@ def test_offsets_with_special_characters(self):
[e[1] for e in expected_results], tokenizer_r.convert_ids_to_tokens(tokens[... | the `tokenize_chinese_chars` argument is not always taken into account with the fast version of the bert tokenizer
## Environment info
<!-- You can run the command `transformers-cli env` and copy-and-paste its output below.
Don't forget to fill out the missing fields in that output! -->
- `transformers` versi... | null | 2022-01-14 12:19:38+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
# Set the working directory in the container
WORKDIR /testbed
# Copy the current directory contents into the container at /testbed
COPY . ... | ['tests/test_tokenization_bert.py:BertTokenizationTest:test_rust_and_python_full_tokenizers', 'tests/test_tokenization_bert.py:BertTokenizationTest:test_batch_encode_plus_batch_sequence_length', 'tests/test_tokenization_bert.py:BertTokenizationTest:test_saving_tokenizer_trainer', 'tests/test_tokenization_bert.py:BertTo... | ['tests/test_tokenization_bert.py:BertTokenizationTest:test_change_tokenize_chinese_chars'] | null | pytest -v --tb=short --show-capture=no --json-report --json-report-file=test_output.json /testbed/tests/test_tokenization_bert.py | Bug Fix | false | false | true | false | 0 | 1 | 1 | false | true | ["src/transformers/models/bert/tokenization_bert_fast.py->module->class_definition:BertTokenizerFast->function_definition:__init__"] |
huggingface/transformers | 15,473 | huggingface__transformers-15473 | ['15466'] | b9418a1d97d33dac0e7ec1df7fc1178f361104c5 | diff --git a/examples/pytorch/language-modeling/run_clm.py b/examples/pytorch/language-modeling/run_clm.py
--- a/examples/pytorch/language-modeling/run_clm.py
+++ b/examples/pytorch/language-modeling/run_clm.py
@@ -30,7 +30,7 @@
from typing import Optional
import datasets
-from datasets import load_dataset
+from da... | diff --git a/tests/test_trainer.py b/tests/test_trainer.py
--- a/tests/test_trainer.py
+++ b/tests/test_trainer.py
@@ -288,6 +288,7 @@ def get_regression_trainer(a=0, b=0, double_output=False, train_len=64, eval_len
data_collator = kwargs.pop("data_collator", None)
optimizers = kwargs.pop("optimizers"... | Preprocess/transform logits before caching them for computing metrics.
# 🚀 Feature request
I think it'd be nice to have a simple way to preprocess the logits before caching them for computing metrics.
## Motivation
When the `Trainer` `compute_metrics` are set, during evaluation the logits are accumulated (som... | I think it would be a valuable addition, as you describe the problematic situation very well, when someone wants to compute perplexity with a language model having a very large vocab size, for instance.
The `TrainingArguments` can't have a new argument of type callable, but I think we could have a new argument in th... | 2022-02-02 07:06:19+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
# Set the working directory in the container
WORKDIR /testbed
# Copy the current directory contents into the container at /testbed
COPY . ... | ['tests/test_trainer.py:TrainerOptimizerChoiceTest:test_fused_adam_no_apex', 'tests/test_trainer.py:TrainerIntegrationTest:test_trainer_works_with_dict', 'tests/test_trainer.py:TrainerOptimizerChoiceTest:test_fused_adam', 'tests/test_trainer.py:TrainerIntegrationTest:test_no_wd_param_group', 'tests/test_trainer.py:Trai... | ['tests/test_trainer.py:TrainerIntegrationTest:test_number_of_steps_in_training', 'tests/test_trainer.py:TrainerIntegrationTest:test_resume_training_with_gradient_accumulation', 'tests/test_trainer.py:TrainerIntegrationPrerunTest:test_training_loss', 'tests/test_trainer.py:TrainerIntegrationTest:test_training_arguments... | null | pytest -v --tb=short --show-capture=no --json-report --json-report-file=test_output.json /testbed/tests/test_trainer.py | Feature | false | false | false | true | 7 | 2 | 9 | false | false | ["src/transformers/trainer.py->module->class_definition:Trainer->function_definition:__init__", "examples/pytorch/language-modeling/run_mlm.py->module->function_definition:main->function_definition:preprocess_logits_for_metrics", "examples/pytorch/language-modeling/run_clm.py->module->function_definition:main->function... |
huggingface/transformers | 15,795 | huggingface__transformers-15795 | ['15739'] | 8481ecefbd7e701bc061b321cb1695d16eac95a9 | diff --git a/src/transformers/hf_argparser.py b/src/transformers/hf_argparser.py
--- a/src/transformers/hf_argparser.py
+++ b/src/transformers/hf_argparser.py
@@ -14,13 +14,13 @@
import dataclasses
import json
-import re
import sys
from argparse import ArgumentDefaultsHelpFormatter, ArgumentParser, ArgumentTypeEr... | diff --git a/tests/utils/test_hf_argparser.py b/tests/utils/test_hf_argparser.py
--- a/tests/utils/test_hf_argparser.py
+++ b/tests/utils/test_hf_argparser.py
@@ -88,8 +88,17 @@ def __post_init__(self):
self.required_enum = BasicEnum(self.required_enum)
+@dataclass
+class StringLiteralAnnotationExample:
+ ... | Add compatibility for Postponed Evaluation of Annotations (PEP 563)
Hello,
The code says that it will add compatibility for Postponed Evaluation of Annotations ([PEP 563](https://www.python.org/dev/peps/pep-0563/)) when Python 3.9 is released (which already happened on 2020.10.5). Is there any plan to complete this?... | Hey! We don't have to do the bandwidth to do it right now, but we'd welcome contributions! Let me tag this as a first good issue, and let me know if you're interested in taking a stab at it!
I'm glad to help with that, maybe it'll take some time. I never contribute here, I'll try to follow the CONTRIBUTING.md, post pro... | 2022-02-23 18:01:27+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
# Set the working directory in the container
WORKDIR /testbed
# Copy the current directory contents into the container at /testbed
COPY . ... | ['tests/utils/test_hf_argparser.py:HfArgumentParserTest:test_basic', 'tests/utils/test_hf_argparser.py:HfArgumentParserTest:test_with_optional', 'tests/utils/test_hf_argparser.py:HfArgumentParserTest:test_with_list', 'tests/utils/test_hf_argparser.py:HfArgumentParserTest:test_with_default_bool', 'tests/utils/test_hf_ar... | ['tests/utils/test_hf_argparser.py:HfArgumentParserTest:test_with_string_literal_annotation'] | null | pytest -v --tb=short /testbed/tests/utils/test_hf_argparser.py --junitxml=test-results.xml | Feature | false | false | false | true | 2 | 1 | 3 | false | false | ["src/transformers/hf_argparser.py->module->class_definition:HfArgumentParser", "src/transformers/hf_argparser.py->module->class_definition:HfArgumentParser->function_definition:_parse_dataclass_field", "src/transformers/hf_argparser.py->module->class_definition:HfArgumentParser->function_definition:_add_dataclass_argu... |
huggingface/transformers | 15,831 | huggingface__transformers-15831 | ['15109'] | ad0d7d17451fea6457c9ee81898f7f64ad7ef848 | diff --git a/src/transformers/models/marian/configuration_marian.py b/src/transformers/models/marian/configuration_marian.py
--- a/src/transformers/models/marian/configuration_marian.py
+++ b/src/transformers/models/marian/configuration_marian.py
@@ -112,6 +112,7 @@ class MarianConfig(PretrainedConfig):
def __init... | diff --git a/tests/marian/test_modeling_marian.py b/tests/marian/test_modeling_marian.py
--- a/tests/marian/test_modeling_marian.py
+++ b/tests/marian/test_modeling_marian.py
@@ -268,6 +268,58 @@ def test_generate_fp16(self):
model.generate(input_ids, attention_mask=attention_mask)
model.generate(num_... | Why is Marian to Torch converter hardcoded for tied vocab ?
I see the following condition:
https://github.com/huggingface/transformers/blob/16f0b7d72c6d4e122957392c342b074aa2c5c519/src/transformers/models/marian/convert_marian_to_pytorch.py#L462
While training my Marian model, I do not want to tie my source and tar... | I understand that this was created only to add support for [baseline models released from Tatoeba Challenge](https://github.com/Helsinki-NLP/Tatoeba-Challenge/tree/master/models).
But it would be great if we can generalize it. Thanks!
cc @patil-suraj
Hi @sshleifer
Just saw your comment on this thread: https://github... | 2022-02-25 13:27:44+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
# Set the working directory in the container
WORKDIR /testbed
# Copy the current directory contents into the container at /testbed
COPY . ... | ['tests/marian/test_tokenization_marian.py:MarianTokenizationTest:test_padding_with_attention_mask', 'tests/marian/test_modeling_marian.py:MarianStandaloneDecoderModelTest:test_feed_forward_chunking', 'tests/marian/test_modeling_marian.py:MarianStandaloneDecoderModelTest:test_save_load_keys_to_ignore_on_save', 'tests/m... | ['tests/marian/test_modeling_marian.py:MarianModelTest:test_share_encoder_decoder_embeddings', 'tests/marian/test_modeling_marian.py:MarianModelTest:test_resize_decoder_token_embeddings'] | null | pytest -v --tb=short --show-capture=no --json-report --json-report-file=test_output.json /testbed/tests/marian/test_modeling_marian.py /testbed/tests/marian/test_tokenization_marian.py | Feature | false | false | false | true | 29 | 11 | 40 | false | false | ["src/transformers/models/marian/convert_marian_to_pytorch.py->module->function_definition:load_layers_", "src/transformers/models/marian/tokenization_marian.py->module->class_definition:MarianTokenizer->function_definition:get_tgt_vocab", "src/transformers/models/marian/modeling_marian.py->module->class_definition:Mar... |
huggingface/transformers | 15,913 | huggingface__transformers-15913 | ['15888'] | 439de3f7f98ccc0d0fc4b1e3a02fac9bb761c809 | diff --git a/src/transformers/models/clip/processing_clip.py b/src/transformers/models/clip/processing_clip.py
--- a/src/transformers/models/clip/processing_clip.py
+++ b/src/transformers/models/clip/processing_clip.py
@@ -23,17 +23,17 @@ class CLIPProcessor(ProcessorMixin):
r"""
Constructs a CLIP processor w... | diff --git a/tests/clip/test_processor_clip.py b/tests/clip/test_processor_clip.py
--- a/tests/clip/test_processor_clip.py
+++ b/tests/clip/test_processor_clip.py
@@ -21,7 +21,7 @@
import numpy as np
import pytest
-from transformers import CLIPTokenizer
+from transformers import CLIPTokenizer, CLIPTokenizerFast
fr... | CLIPProcessor with CLIPTokenizerFast
# 🚀 Feature request
Current `CLIPProcessor` doesn't support `CLIPTokenizerFast` requiring `CLIPTokenizer`.
In my thinking, there is no reason not to support `CLIPTokenizerFast` for `CLIPProcessor`
## Motivation
<!-- Please outline the motivation for the proposal. Is your ... | Hey @cosmoquester !
The `CLIPTokenizerFast` was not used in the processor because there was an issue with it which is now fixed, cf #15067
So yes, we can now support `CLIPTokenizerFast` for `CLIPProcessor`. Feel free to open a PR! | 2022-03-03 13:04:08+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
# Set the working directory in the container
WORKDIR /testbed
# Copy the current directory contents into the container at /testbed
COPY . ... | ['tests/clip/test_processor_clip.py:CLIPProcessorTest:test_processor', 'tests/clip/test_processor_clip.py:CLIPProcessorTest:test_tokenizer_decode', 'tests/clip/test_processor_clip.py:CLIPProcessorTest:test_feature_extractor', 'tests/clip/test_processor_clip.py:CLIPProcessorTest:test_tokenizer'] | ['tests/clip/test_processor_clip.py:CLIPProcessorTest:test_save_load_pretrained_additional_features', 'tests/clip/test_processor_clip.py:CLIPProcessorTest:test_save_load_pretrained_default'] | null | pytest -v --tb=short /testbed/tests/clip/test_processor_clip.py --junitxml=test-results.xml | Feature | false | false | false | true | 3 | 1 | 4 | false | false | ["src/transformers/models/clip/processing_clip.py->module->class_definition:CLIPProcessor->function_definition:__call__", "src/transformers/models/clip/processing_clip.py->module->class_definition:CLIPProcessor", "src/transformers/models/clip/processing_clip.py->module->class_definition:CLIPProcessor->function_definiti... |
huggingface/transformers | 16,661 | huggingface__transformers-16661 | ['16660', '16660'] | 33cb21150c034aae0f11b9ab6e38752a7c6d1784 | diff --git a/src/transformers/tokenization_utils_base.py b/src/transformers/tokenization_utils_base.py
--- a/src/transformers/tokenization_utils_base.py
+++ b/src/transformers/tokenization_utils_base.py
@@ -1150,35 +1150,35 @@ def additional_special_tokens_ids(self) -> List[int]:
@bos_token_id.setter
def bo... | diff --git a/tests/byt5/test_tokenization_byt5.py b/tests/byt5/test_tokenization_byt5.py
--- a/tests/byt5/test_tokenization_byt5.py
+++ b/tests/byt5/test_tokenization_byt5.py
@@ -332,3 +332,41 @@ def test_convert_tokens_to_string_format(self):
string = tokenizer.convert_tokens_to_string(tokens)
... | Tokenizers setter of ids of special tokens don't work
## Environment info
<!-- You can run the command `transformers-cli env` and copy-and-paste its output below.
Don't forget to fill out the missing fields in that output! -->
- `transformers` version:
- Platform:
- Python version:
- PyTorch version (GPU?)... | 2022-04-08 01:31:48+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
# Set the working directory in the container
WORKDIR /testbed
# Copy the current directory contents into the container at /testbed
COPY . ... | ['tests/byt5/test_tokenization_byt5.py:ByT5TokenizationTest:test_is_fast', 'tests/canine/test_tokenization_canine.py:CanineTokenizationTest:test_special_tokens_initialization_with_non_empty_additional_special_tokens', 'tests/canine/test_tokenization_canine.py:CanineTokenizationTest:test_save_sentencepiece_tokenizer', '... | ['tests/byt5/test_tokenization_byt5.py:ByT5TokenizationTest:test_tokenizers_common_ids_setters', 'tests/canine/test_tokenization_canine.py:CanineTokenizationTest:test_tokenizers_common_ids_setters'] | null | pytest -v --tb=short --show-capture=no /testbed/tests/byt5/test_tokenization_byt5.py /testbed/tests/canine/test_tokenization_canine.py /testbed/tests/test_tokenization_common.py | Bug Fix | false | true | false | false | 8 | 0 | 8 | false | false | ["src/transformers/tokenization_utils_base.py->module->class_definition:SpecialTokensMixin->function_definition:additional_special_tokens_ids", "src/transformers/tokenization_utils_base.py->module->class_definition:SpecialTokensMixin->function_definition:eos_token_id", "src/transformers/tokenization_utils_base.py->modu... | |
huggingface/transformers | 17,082 | huggingface__transformers-17082 | ['15735'] | d76d2a2af7babf73d6c5bc53facaccab05e912f8 | diff --git a/src/transformers/convert_slow_tokenizer.py b/src/transformers/convert_slow_tokenizer.py
--- a/src/transformers/convert_slow_tokenizer.py
+++ b/src/transformers/convert_slow_tokenizer.py
@@ -407,7 +407,7 @@ def converted(self) -> Tokenizer:
tokenizer.decoder = decoders.ByteLevel()
tokenize... | diff --git a/tests/models/deberta/test_tokenization_deberta.py b/tests/models/deberta/test_tokenization_deberta.py
--- a/tests/models/deberta/test_tokenization_deberta.py
+++ b/tests/models/deberta/test_tokenization_deberta.py
@@ -88,6 +88,12 @@ def test_full_tokenizer(self):
input_bpe_tokens = [0, 1, 2, 15, 1... | `DebertaTokenizer` always assigns token type ID 0
## Environment info
- `transformers` version: 4.16.2
- Platform: Linux-5.15.13-051513-generic-x86_64-with-glibc2.34
- Python version: 3.9.7
- PyTorch version (GPU?): 1.9.0+cu111 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU... | Looks like this is the change that introduced this behavior.
https://github.com/huggingface/transformers/commit/57c1749efabf5c86bcfd4e4e078567a63a7c8a81#diff-7ff4f35b72b8541520ea52c851b55bc2682da83e01e6e0ceeb5289f7dd2f0620R217
Good catch! Would you like to open a PR to fix this? | 2022-05-04 11:51:41+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
# Set the working directory in the container
WORKDIR /testbed
# Copy the current directory contents into the container at /testbed
COPY . ... | ['tests/models/deberta/test_tokenization_deberta.py:DebertaTokenizationTest:test_special_tokens_map_equal', 'tests/models/deberta/test_tokenization_deberta.py:DebertaTokenizationTest:test_max_length_equal', 'tests/models/deberta/test_tokenization_deberta.py:DebertaTokenizationTest:test_fast_only_inputs', 'tests/models/... | ['tests/models/deberta/test_tokenization_deberta.py:DebertaTokenizationTest:test_token_type_ids'] | null | pytest -v --tb=short --show-capture=no --json-report --json-report-file=test_output.json /testbed/tests/models/deberta/test_tokenization_deberta.py | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["src/transformers/models/deberta/tokenization_deberta_fast.py->module->class_definition:DebertaTokenizerFast->function_definition:create_token_type_ids_from_sequences", "src/transformers/models/deberta/tokenization_deberta.py->module->class_definition:DebertaTokenizer->function_definition:create_token_type_ids_from_se... |
huggingface/transformers | 19,073 | huggingface__transformers-19073 | ['19057'] | 5e636eee4af48ccd03b4d9c1a1e6f7a1b92a643f | diff --git a/src/transformers/tokenization_utils_base.py b/src/transformers/tokenization_utils_base.py
--- a/src/transformers/tokenization_utils_base.py
+++ b/src/transformers/tokenization_utils_base.py
@@ -1726,6 +1726,8 @@ def from_pretrained(cls, pretrained_model_name_or_path: Union[str, os.PathLike],
for f... | diff --git a/tests/test_tokenization_common.py b/tests/test_tokenization_common.py
--- a/tests/test_tokenization_common.py
+++ b/tests/test_tokenization_common.py
@@ -31,6 +31,7 @@
from typing import TYPE_CHECKING, Any, Dict, List, Tuple, Union
from huggingface_hub import HfFolder, delete_repo, set_access_token
+fr... | Loading tokenizer using from_pretrained seems to be broken for v4
### System Info
According to following `FutureWarning` loading tokenizer using a file path should work in v4:
```
FutureWarning: Calling AlbertTokenizer.from_pretrained() with the path to a single file or url is deprecated and won't be possible anymor... | cc @sgugger
Indeed. I can reproduce, a fix is coming. This was caused by #18438 and this particular use case slipped through the cracks since it's untested (probably because it's deprecated behavior). | 2022-09-16 17:48:35+00:00 | Python | # Use an official Python runtime as a parent image
FROM public.ecr.aws/docker/library/python:3.10-slim
RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
# Set the working directory in the container
WORKDIR /testbed
# Copy the current directory contents into the container at /testbed
COPY . ... | ['tests/test_tokenization_common.py:TrieTest:test_trie_final', 'tests/test_tokenization_common.py:TrieTest:test_trie_skip', 'tests/test_tokenization_common.py:TrieTest:test_trie_suffix_tokens', 'tests/test_tokenization_common.py:TrieTest:test_trie_split', 'tests/test_tokenization_common.py:TrieTest:test_cut_text_harden... | ['tests/test_tokenization_common.py:TokenizerUtilTester:test_legacy_load_from_one_file'] | null | pytest /testbed/tests/test_tokenization_common.py -v --tb=short --json-report --json-report-file=test_output.json | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["src/transformers/tokenization_utils_base.py->module->class_definition:PreTrainedTokenizerBase->function_definition:from_pretrained"] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.