text:
MRIconView shapeLayer animation and appearance selectors.

Allows the shapeLayer of MRIconView to be animated. Adds the appearance selectors to MRIconView for setting the border and line widths, and also the animation duration.

So much great stuff in one single commit! :tada:
Didn't want to leave you alone without feedback: so would you mind to integrate your proposed changes a slight bit more into the existing code base by changing indentation from tabs to whitespaces and perhaps reverting the removal of the newlines in the public interface?
Otherwise I love the idea to have animated transitions for the overlay by implementing the animation pseudo-protocol. I guess, that's what you use it for, right? I would love to make that a bit more obvious by exposing the implemented selectors startAnimating, stopAnimating, … in the public interface with some little words of documentation, which could be basically just copied over from MRActivityIndicatorView.

authors: boherna mrackwitz


text:
Cypress 7.5.0 & record flag

Hi!
Got an error with cypress (version 7.5.0) first launch (OS windows 10 pro) :
PS myapp> npm run e2e

> blog@0.0.1-SNAPSHOT e2e \myapp
> npm run e2e:cypress

> blog@0.0.1-SNAPSHOT e2e:cypress \myapp
> cypress run --browser chrome --record ${CYPRESS_ENABLE_RECORD:-false}

You passed the --record flag but this project has not been setup to record.
This project is missing the 'projectId' inside of 'cypress.json'.
We cannot uniquely identify this project without this id.
You need to setup this project to record. This will generate a unique 'projectId'.
Alternatively if you omit the --record flag this project will run without recording.

https://on.cypress.io/recording-project-runs
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! blog@0.0.1-SNAPSHOT e2e:cypress: `cypress run --browser chrome --record ${CYPRESS_ENABLE_RECORD:-false}`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the blog@0.0.1-SNAPSHOT e2e:cypress script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     %USERPROFILE%\AppData\Roaming\npm-cache\_logs\2021-09-01T13_47_36_399Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! blog@0.0.1-SNAPSHOT e2e: `npm run e2e:cypress`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the blog@0.0.1-SNAPSHOT e2e script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     %USERPROFILE%\AppData\Roaming\npm-cache\_logs\2021-09-01T13_47_36_460Z-debug.log

To solve it, i disable the record flag (by removing it)
Cypress version 7.5.0
Edit the file package.json at root project dir :
"e2e:cypress": "cypress run --browser chrome --record ${CYPRESS_ENABLE_RECORD:-false}",
become :
"e2e:cypress": "cypress run --browser chrome",
Hope it helps ;-)
Thank you Matt for sharing this demo project!

This project was created with JHipster 7.0.1 and uses Cypress 6.6.0. https://github.com/mraible/jhipster7-demo/blob/main/package.json#L115
Are you using a more recent version of JHipster? If so, you might want to enter an issue in the JHipster GitHub project.

Thank you for your quick response Matt, indeed it must come from this latest version of cypress or jhipster.
My setup :
PS > & "$env:JAVA_HOME\bin\java" -version
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)

PS > node --version
v14.17.6

PS > npm version
{
  blog: '0.0.1-SNAPSHOT',
  npm: '6.14.15',
  ares: '1.17.2',
  brotli: '1.0.9',
  cldr: '39.0',
  icu: '69.1',
  llhttp: '2.1.3',
  modules: '83',
  napi: '8',
  nghttp2: '1.42.0',
  node: '14.17.6',
  openssl: '1.1.1l',
  tz: '2021a',
  unicode: '13.0',
  uv: '1.41.0',
  v8: '8.4.371.23-node.76',
  zlib: '1.2.11'
}

PS > & "$env:USERPROFILE\AppData\Roaming\npm\jhipster.cmd" --version
INFO! Using JHipster version installed locally in current project's node_modules
7.1.0

i'll submit an issue on jhipster github project as you suggest it ;-)
See you soon Matt!

source: gharchive/issue

authors: mraible yoborider

license_type: permissive

license_source: github-api


text:
Fix ** globs

This cuts the failing tests by half.

Thanks as always, I don't think canonicalizing the path in tests is needed after this commit.

That canonicalizes the .editorconfig paths, but if the input paths aren't also canonicalized then removing common prefixes causes problems. (I learned that the hard way.)

source: gharchive/pull-request

license: mit

license_source: bigquery


text:
chore: chore

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

TESTING spectrum-non-colors
READING spectrum-tokens: ./spectrum-tokens/packages/tokens/src/
READING  tokens studio: ./spectrum-tokens-studio-data/src/tokens-studio/spectrum-non-colors/

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-extra-large/spectrum/desktop [155b6273-1661-4ef5-85c0-a1688ce1ee72]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-large/spectrum/desktop [be9aed61-c7a1-4dce-80a7-07c9ecef1fd9]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-medium/spectrum/desktop [238ebdc2-e51c-459d-8cc7-abfeafed6451]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-small/spectrum/desktop [bf2e4550-f97e-4bd2-91e8-b0ddb5a8abe2]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-extra-large/spectrum/desktop [fd74d5a5-b966-4d26-abca-58c7a21f8136]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-large/spectrum/desktop [320abda8-9fe8-4f78-87d6-3f1be921e880]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-medium/spectrum/desktop [dd3b649d-12f8-427b-95a6-a4964d92d3b0]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-small/spectrum/desktop [cf748652-099a-4022-ae68-0e5dcb8eff9b]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-extra-large/spectrum/mobile [e04d9975-4a54-416b-b5fa-87f3ae930204]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-large/spectrum/mobile [3915ff73-11dd-4389-8d81-2f540ab060f4]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-medium/spectrum/mobile [5030babb-0017-4784-84ad-d3aaacf6fa05]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-small/spectrum/mobile [3b96ab4f-6628-4ebd-aba8-2837fce04709]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-extra-large/spectrum/mobile [c5d47ebf-c83f-43c3-b2f2-f4d51c40960b]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-large/spectrum/mobile [0926d8f3-bdd6-4dde-89d0-6d5d7ab9f094]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-medium/spectrum/mobile [7306fc00-67fd-4ccd-aec3-7a14e092da5e]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-small/spectrum/mobile [19adc707-4fc6-40f0-a972-340d6c935908]

TOKENS STUDIO DATA IS NON-COLOR ONLY
LOADED SPECTRUM TOKENS: 2701
LOADED STUDIO TOKENS:   1500
CHANGED VALUES: 11
CHANGED TOKENS: 6
Action URL

./logs/changedTokens.json

```
{
"background-opacity-down": {
"value": "0.2",
"uuid": "0718c9fc-3bb2-4887-97bd-e23b8ad308c5"
},
"contextual-help-body-size": {
"sets": {
"desktop": {
"value": "{heading-size-s}",
"uuid": "e458fa68-ab9c-4441-a7d5-a02f42df1cae"
},
"mobile": {
"value": "{heading-size-xs}",
"uuid": "c180fa75-254e-4ee1-8b79-31a3d90254cc"
}
}
},
"navigational-indicator-top-to-back-icon-extra-large": {
"sets": {
"desktop": {
"value": "17px",
"uuid": "ac4d18d5-361c-4425-82c3-83979d58f682"
},
"mobile": {
"value": "22px",
"uuid": "e68f2798-6a55-499a-b591-0cfc130607ba"
}
}
},
"navigational-indicator-top-to-back-icon-large": {
"sets": {
"desktop": {
"value": "14px",
"uuid": "c0e06d21-7372-401f-9ec2-926e2b1faf26"
},
"mobile": {
"value": "17px",
"uuid": "e84bc865-c89f-403e-bb14-2a11f03fd364"
}
}
},
"navigational-indicator-top-to-back-icon-medium": {
"sets": {
"desktop": {
"value": "11px",
"uuid": "5561a148-fd77-44d3-b29d-3ed7389122a1"
},
"mobile": {
"value": "13px",
"uuid": "74f8a686-0e06-4f7c-9e3d-694749beb420"
}
}
},
"navigational-indicator-top-to-back-icon-small": {
"sets": {
"desktop": {
"value": "7px",
"uuid": "70de4f97-bc4a-44af-9995-1042e3c7c78f"
},
"mobile": {
"value": "9px",
"uuid": "d11ab0de-19bd-4f56-8798-0192fd0cfe0e"
}
}
}
}
</p></details>

TESTING spectrum-non-colors
READING spectrum-tokens: ./spectrum-tokens/packages/tokens/src/
READING  tokens studio: ./spectrum-tokens-studio-data/src/tokens-studio/spectrum-non-colors/

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-extra-large/spectrum/desktop [155b6273-1661-4ef5-85c0-a1688ce1ee72]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-large/spectrum/desktop [be9aed61-c7a1-4dce-80a7-07c9ecef1fd9]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-medium/spectrum/desktop [238ebdc2-e51c-459d-8cc7-abfeafed6451]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-small/spectrum/desktop [bf2e4550-f97e-4bd2-91e8-b0ddb5a8abe2]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-extra-large/spectrum/desktop [fd74d5a5-b966-4d26-abca-58c7a21f8136]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-large/spectrum/desktop [320abda8-9fe8-4f78-87d6-3f1be921e880]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-medium/spectrum/desktop [dd3b649d-12f8-427b-95a6-a4964d92d3b0]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-small/spectrum/desktop [cf748652-099a-4022-ae68-0e5dcb8eff9b]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-extra-large/spectrum/mobile [e04d9975-4a54-416b-b5fa-87f3ae930204]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-large/spectrum/mobile [3915ff73-11dd-4389-8d81-2f540ab060f4]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-medium/spectrum/mobile [5030babb-0017-4784-84ad-d3aaacf6fa05]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-small/spectrum/mobile [3b96ab4f-6628-4ebd-aba8-2837fce04709]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-extra-large/spectrum/mobile [c5d47ebf-c83f-43c3-b2f2-f4d51c40960b]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-large/spectrum/mobile [0926d8f3-bdd6-4dde-89d0-6d5d7ab9f094]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-medium/spectrum/mobile [7306fc00-67fd-4ccd-aec3-7a14e092da5e]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-small/spectrum/mobile [19adc707-4fc6-40f0-a972-340d6c935908]

TOKENS STUDIO DATA IS NON-COLOR ONLY
LOADED SPECTRUM TOKENS: 2701
LOADED STUDIO TOKENS:   1500
CHANGED VALUES: 11
CHANGED TOKENS: 6
Action URL

./logs/changedTokens.json

{
  "background-opacity-down": {
    "value": "0.2",
    "uuid": "0718c9fc-3bb2-4887-97bd-e23b8ad308c5"
  },
  "contextual-help-body-size": {
    "sets": {
      "desktop": {
        "value": "{heading-size-s}",
        "uuid": "e458fa68-ab9c-4441-a7d5-a02f42df1cae"
      },
      "mobile": {
        "value": "{heading-size-xs}",
        "uuid": "c180fa75-254e-4ee1-8b79-31a3d90254cc"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-extra-large": {
    "sets": {
      "desktop": {
        "value": "17px",
        "uuid": "ac4d18d5-361c-4425-82c3-83979d58f682"
      },
      "mobile": {
        "value": "22px",
        "uuid": "e68f2798-6a55-499a-b591-0cfc130607ba"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-large": {
    "sets": {
      "desktop": {
        "value": "14px",
        "uuid": "c0e06d21-7372-401f-9ec2-926e2b1faf26"
      },
      "mobile": {
        "value": "17px",
        "uuid": "e84bc865-c89f-403e-bb14-2a11f03fd364"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-medium": {
    "sets": {
      "desktop": {
        "value": "11px",
        "uuid": "5561a148-fd77-44d3-b29d-3ed7389122a1"
      },
      "mobile": {
        "value": "13px",
        "uuid": "74f8a686-0e06-4f7c-9e3d-694749beb420"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-small": {
    "sets": {
      "desktop": {
        "value": "7px",
        "uuid": "70de4f97-bc4a-44af-9995-1042e3c7c78f"
      },
      "mobile": {
        "value": "9px",
        "uuid": "d11ab0de-19bd-4f56-8798-0192fd0cfe0e"
      }
    }
  }
}```

</p></details>

TESTING spectrum-non-colors
READING spectrum-tokens: ./spectrum-tokens/packages/tokens/src/
READING  tokens studio: ./spectrum-tokens-studio-data/src/tokens-studio/spectrum-non-colors/

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-extra-large/spectrum/desktop [155b6273-1661-4ef5-85c0-a1688ce1ee72]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-large/spectrum/desktop [be9aed61-c7a1-4dce-80a7-07c9ecef1fd9]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-medium/spectrum/desktop [238ebdc2-e51c-459d-8cc7-abfeafed6451]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-small/spectrum/desktop [bf2e4550-f97e-4bd2-91e8-b0ddb5a8abe2]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-extra-large/spectrum/desktop [fd74d5a5-b966-4d26-abca-58c7a21f8136]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-large/spectrum/desktop [320abda8-9fe8-4f78-87d6-3f1be921e880]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-medium/spectrum/desktop [dd3b649d-12f8-427b-95a6-a4964d92d3b0]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-small/spectrum/desktop [cf748652-099a-4022-ae68-0e5dcb8eff9b]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-extra-large/spectrum/mobile [e04d9975-4a54-416b-b5fa-87f3ae930204]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-large/spectrum/mobile [3915ff73-11dd-4389-8d81-2f540ab060f4]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-medium/spectrum/mobile [5030babb-0017-4784-84ad-d3aaacf6fa05]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-small/spectrum/mobile [3b96ab4f-6628-4ebd-aba8-2837fce04709]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-extra-large/spectrum/mobile [c5d47ebf-c83f-43c3-b2f2-f4d51c40960b]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-large/spectrum/mobile [0926d8f3-bdd6-4dde-89d0-6d5d7ab9f094]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-medium/spectrum/mobile [7306fc00-67fd-4ccd-aec3-7a14e092da5e]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-small/spectrum/mobile [19adc707-4fc6-40f0-a972-340d6c935908]

TOKENS STUDIO DATA IS NON-COLOR ONLY
LOADED SPECTRUM TOKENS: 2701
LOADED STUDIO TOKENS:   1500
CHANGED VALUES: 11
CHANGED TOKENS: 6
Action URL

./logs/changedTokens.json

{
  "background-opacity-down": {
    "value": "0.2",
    "uuid": "0718c9fc-3bb2-4887-97bd-e23b8ad308c5"
  },
  "contextual-help-body-size": {
    "sets": {
      "desktop": {
        "value": "{heading-size-s}",
        "uuid": "e458fa68-ab9c-4441-a7d5-a02f42df1cae"
      },
      "mobile": {
        "value": "{heading-size-xs}",
        "uuid": "c180fa75-254e-4ee1-8b79-31a3d90254cc"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-extra-large": {
    "sets": {
      "desktop": {
        "value": "17px",
        "uuid": "ac4d18d5-361c-4425-82c3-83979d58f682"
      },
      "mobile": {
        "value": "22px",
        "uuid": "e68f2798-6a55-499a-b591-0cfc130607ba"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-large": {
    "sets": {
      "desktop": {
        "value": "14px",
        "uuid": "c0e06d21-7372-401f-9ec2-926e2b1faf26"
      },
      "mobile": {
        "value": "17px",
        "uuid": "e84bc865-c89f-403e-bb14-2a11f03fd364"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-medium": {
    "sets": {
      "desktop": {
        "value": "11px",
        "uuid": "5561a148-fd77-44d3-b29d-3ed7389122a1"
      },
      "mobile": {
        "value": "13px",
        "uuid": "74f8a686-0e06-4f7c-9e3d-694749beb420"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-small": {
    "sets": {
      "desktop": {
        "value": "7px",
        "uuid": "70de4f97-bc4a-44af-9995-1042e3c7c78f"
      },
      "mobile": {
        "value": "9px",
        "uuid": "d11ab0de-19bd-4f56-8798-0192fd0cfe0e"
      }
    }
  }
}

TESTING spectrum-non-colors
READING spectrum-tokens: ./spectrum-tokens/packages/tokens/src/
READING  tokens studio: ./spectrum-tokens-studio-data/src/tokens-studio/spectrum-non-colors/

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-extra-large/spectrum/desktop [155b6273-1661-4ef5-85c0-a1688ce1ee72]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-large/spectrum/desktop [be9aed61-c7a1-4dce-80a7-07c9ecef1fd9]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-medium/spectrum/desktop [238ebdc2-e51c-459d-8cc7-abfeafed6451]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-small/spectrum/desktop [bf2e4550-f97e-4bd2-91e8-b0ddb5a8abe2]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-extra-large/spectrum/desktop [fd74d5a5-b966-4d26-abca-58c7a21f8136]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-large/spectrum/desktop [320abda8-9fe8-4f78-87d6-3f1be921e880]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-medium/spectrum/desktop [dd3b649d-12f8-427b-95a6-a4964d92d3b0]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-small/spectrum/desktop [cf748652-099a-4022-ae68-0e5dcb8eff9b]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-extra-large/spectrum/mobile [e04d9975-4a54-416b-b5fa-87f3ae930204]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-large/spectrum/mobile [3915ff73-11dd-4389-8d81-2f540ab060f4]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-medium/spectrum/mobile [5030babb-0017-4784-84ad-d3aaacf6fa05]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-bottom-to-handle-small/spectrum/mobile [3b96ab4f-6628-4ebd-aba8-2837fce04709]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-extra-large/spectrum/mobile [c5d47ebf-c83f-43c3-b2f2-f4d51c40960b]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-large/spectrum/mobile [0926d8f3-bdd6-4dde-89d0-6d5d7ab9f094]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-medium/spectrum/mobile [7306fc00-67fd-4ccd-aec3-7a14e092da5e]

WARNING - STUDIO INCLUDES DEPRECATED TOKEN: slider-control-height-small/spectrum/mobile [19adc707-4fc6-40f0-a972-340d6c935908]

TOKENS STUDIO DATA IS NON-COLOR ONLY
LOADED SPECTRUM TOKENS: 2701
LOADED STUDIO TOKENS:   1500
CHANGED VALUES: 11
CHANGED TOKENS: 6

./logs/changedTokens.json

{
  "background-opacity-down": {
    "value": "0.2",
    "uuid": "0718c9fc-3bb2-4887-97bd-e23b8ad308c5"
  },
  "contextual-help-body-size": {
    "sets": {
      "desktop": {
        "value": "{heading-size-s}",
        "uuid": "e458fa68-ab9c-4441-a7d5-a02f42df1cae"
      },
      "mobile": {
        "value": "{heading-size-xs}",
        "uuid": "c180fa75-254e-4ee1-8b79-31a3d90254cc"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-extra-large": {
    "sets": {
      "desktop": {
        "value": "17px",
        "uuid": "ac4d18d5-361c-4425-82c3-83979d58f682"
      },
      "mobile": {
        "value": "22px",
        "uuid": "e68f2798-6a55-499a-b591-0cfc130607ba"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-large": {
    "sets": {
      "desktop": {
        "value": "14px",
        "uuid": "c0e06d21-7372-401f-9ec2-926e2b1faf26"
      },
      "mobile": {
        "value": "17px",
        "uuid": "e84bc865-c89f-403e-bb14-2a11f03fd364"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-medium": {
    "sets": {
      "desktop": {
        "value": "11px",
        "uuid": "5561a148-fd77-44d3-b29d-3ed7389122a1"
      },
      "mobile": {
        "value": "13px",
        "uuid": "74f8a686-0e06-4f7c-9e3d-694749beb420"
      }
    }
  },
  "navigational-indicator-top-to-back-icon-small": {
    "sets": {
      "desktop": {
        "value": "7px",
        "uuid": "70de4f97-bc4a-44af-9995-1042e3c7c78f"
      },
      "mobile": {
        "value": "9px",
        "uuid": "d11ab0de-19bd-4f56-8798-0192fd0cfe0e"
      }
    }
  }
}

repo: mrcjhicks/spectrum-tokens-studio-data


text:
No trimmed read files were identified to run SPAdes

Hello,
I would like to assemble chloroplastic DNA using Fast-Plast.
Unfortunately, the process stops after providing 2-Bowtie_index.
Actually, the process is stopped with this error message :
ERROR: No trimmed read files were identified to run SPAdes.  Please check 1_Trimmed_Reads, found in Begonia_4_35_fastplast_assembly_Fast-Plast_Progress.log file.
I don't really understand the problem because my input files are raw data of sequencing with fq.gz format files.
If someone already faced this issue, please tell me how you solved it.
Thanks !

Hi,
Sorry for (again) missing emails for this. I changed my email address for notices, so things should be better now.  If you still are having issues, please send me the output files.
Thanks!
Michael

repo: mrmckain/Fast-Plast


text:
How does one render the footnote number in References / Bibliography (PDF output)?

Hi Moritz,
First off, thanks a lot for unbuch! I've been playing with it lately and I'm thinking of using it for typesetting my lecture notes for the upcoming semester.
One thing I'm currently struggling with relates to the way the bibliography is rendered in PDF. While the bib entries themselves are rendered correctly, they somehow miss the footnote number corresponding to the citation (I'm trying to replicate the setup of the mlstory book where each entry is preceded by the corresponding superscript):

Any chance you could share the relevant part of the setup? I've been exploring pandoc and citeproc, but no luck thus far. (Is that something one is supposed to adapt the .csl for?).
In case it helps, here is the relevant output of my pandoc --version:
pandoc 2.14
Compiled with pandoc-types 1.22, texmath 0.12.3, skylighting 0.10.5.1,
citeproc 0.4, ipynb 0.1.0.1

Hi Laurent,
I'm sorry I missed this comment. The mlstory setup is indeed a bit different from the basic unbuch version. Here is the part of the Makefile that sets the book.
## Step 1: Give each markdown file a chapter heading.
## Step 2: Compile markdown sources into tex using pandoc
## Step 3: Compile tex sources using pdflatex
publish/pdf/$(bookfilename).pdf: $(CHAPTERS) templates/book.tex templates/references.md Makefile $(FILTERS) templates/shared-macros.tex references.bib sources/preface.md sources/acknowledgments.md
	$(foreach chapter,$(CHAPTERS),\
      pandoc --template templates/chapter.md $(chapter) \
      --id-prefix=$(notdir $(chapter)) \
      --output tmp-$(notdir $(chapter));) \
    pandoc \
    --natbib \
    --metadata link-citations=false \
    --filter ./filters/whitespace.py \
    --filter ./filters/numenvs.py \
    --filter ./filters/crossrefs.py \
    --filter ./filters/svgimagext.py \
    --filter ./filters/sidenote.py \
    --template templates/book.tex \
    --variable book-layout=true \
    --variable booktitle="${booktitle}" \
    --variable booksubtitle="${booksubtitle}" \
    --variable bookauthors="${bookauthors}" \
    --variable lastupdate="`date`" \
    --variable titlepagefootnote="${titlepagefootnote}" \
    --variable acknowledgments="`pandoc -t latex sources/acknowledgments.md`" \
    --variable preface="`pandoc -t latex sources/preface.md`" \
    --variable macros="`cat templates/shared-macros.tex`" \
    --output $(bookfilename).tex \
    $(foreach chapter,$(CHAPTERS),tmp-$(notdir $(chapter))); \
    $(foreach chapter,$(CHAPTERS),rm tmp-$(notdir $(chapter));) \
    mkdir -p tex/assets; \
    cp assets/*.pdf tex/assets; \
    cp assets/*.png tex/assets; \
    cp assets/*.jpg tex/assets; \
    cp references.bib tex/; \
    mv $(bookfilename).tex tex/; \
    cd tex; \
    pdflatex $(bookfilename).tex; \
    makeindex $(bookfilename); \
    bibtex $(bookfilename); \
    pdflatex $(bookfilename).tex; \
    pdflatex $(bookfilename).tex; \
    rm *.aux *.log *.blg *.out *.bib; \
    mv $(bookfilename).pdf ../publish/pdf;```

The other edits are in the template `book.tex`:

```\documentclass[oneside,12pt]{book}

\usepackage[utf8]{inputenc}

\usepackage{graphicx}
\setkeys{Gin}{width=\linewidth,totalheight=\textheight,keepaspectratio}

\usepackage{xcolor}
\definecolor{darkblue}{HTML}{00416A}

\usepackage{longtable}
\usepackage{booktabs}
\usepackage{amssymb}
\usepackage{amsmath}
\usepackage{amsthm}
\usepackage{boxedminipage}
\usepackage{microtype}
\usepackage{makeidx}
\usepackage{hyperref}
\usepackage{ifthen}
\usepackage{array}
\usepackage{calc}

\usepackage{titlesec,titletoc}

\usepackage[letterpaper,textwidth=5.5in,textheight=8.5in]{geometry}

\usepackage[osf,sc]{mathpazo}
\RequirePackage[scaled=0.90]{helvet}
\RequirePackage[scaled=0.85]{beramono}
\RequirePackage[T1]{fontenc}
\RequirePackage{textcomp}

\usepackage[square,sort,comma,numbers]{natbib}
\usepackage[superscript,biblabel]{cite}
\renewcommand{\citep}[1]{\cite{#1}}

\pagestyle{plain}

%%
% Make Tuftian-style section headings and TOC formatting

\titleformat{\chapter}%
  [display]% shape
  {\relax}% format applied to label+text
  {\itshape\huge\thechapter}% label
  {0pt}% horizontal separation between label and title body
  {\huge\rmfamily\itshape}% before the title body
  []% after the title body

\titleformat{\section}%
  [hang]% shape
  {\normalfont\Large\itshape}% format applied to label+text
  {\thesection}% label
  {1em}% horizontal separation between label and title body
  {}% before the title body
  []% after the title body

\titleformat{\subsection}%
  [hang]% shape
  {\normalfont\large\itshape}% format applied to label+text
  {\thesubsection}% label
  {1em}% horizontal separation between label and title body
  {}% before the title body
  []% after the title body

\titleformat{\paragraph}%
  [runin]% shape
  {\normalfont\itshape}% format applied to label+text
  {\theparagraph}% label
  {1em}% horizontal separation between label and title body
  {}% before the title body
  []% after the title body

\titlespacing*{\chapter}{0pt}{50pt}{40pt}
\titlespacing*{\section}{0pt}{3.5ex plus 1ex minus .2ex}{2.3ex plus .2ex}
\titlespacing*{\subsection}{0pt}{3.25ex plus 1ex minus .2ex}{1.5ex plus.2ex}

\makeatother

\newtheorem{Definition}{Definition}
\newtheorem{Theorem}{Theorem}
\newtheorem{Lemma}{Lemma}
\newtheorem{Exercise}{Exercise}
\newtheorem{Fact}{Fact}
\newtheorem{Proposition}{Proposition}
\newtheorem{Assumption}{Assumption}
\newenvironment{Algorithm}{\begin{center}\begin{boxedminipage}{0.92\textwidth}}{\end{boxedminipage}\end{center}}
\newenvironment{Proof}{\begin{proof}}{\end{proof}}
\newtheorem*{summary*}{Summary}
\newenvironment{Summary}{\begin{center}\begin{minipage}{0.92\textwidth}\begin{summary*}}{\end{summary*}\end{minipage}\end{center}\medskip}
\newenvironment{EmphBox}{\begin{center}\begin{minipage}{0.8\textwidth}}{\end{minipage}\end{center}\medskip}

\providecommand{\tightlist}{%
  \setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}

\renewcommand{\bot}{\perp}
\renewcommand{\hat}{\widehat}

\usepackage{wrapfig}
\usepackage{marginfix}
\usepackage[morefloats=100]{morefloats}

\newcommand{\marginnote}[1]{
\begin{wrapfigure}{o}{0.4\textwidth}
\footnotesize #1
\end{wrapfigure}
}

\renewcommand{\footnote}[1]{\marginnote{#1}}

\setcounter{secnumdepth}{0}
\makeatletter
\renewcommand{\@seccntformat}[1]{}
\makeatother

$macros$

%
% Book specific layout
%

$if(book-layout)$

\usepackage{ifthen}
\usepackage{chngcntr}
\counterwithout{figure}{chapter}
\counterwithout{table}{chapter}

\hypersetup{
  colorlinks,
  linkcolor = black,
  urlcolor = black,
  pdftitle = {$booktitle$},
  pdfauthor = {$bookauthors$},
  hyperindex = true
}

\usepackage{eso-pic}
\newcommand\BackgroundPic{%
\put(0,0){%
\parbox[b][\paperheight]{\paperwidth}{%
\vfill
\centering
\includegraphics[width=\paperwidth,height=\paperheight,%
keepaspectratio]{assets/cargo-cult-pixels-lower.png}%
\vfill
}}}
\title{$booktitle$}
\author{$bookauthors$}
\setcounter{tocdepth}{1}

\makeindex

\newif\ifshowchapternumber

\let\OLDthebibliography\thebibliography
\renewcommand\thebibliography[1]{
  \OLDthebibliography{#1}
  \setlength{\parskip}{0pt}
  \setlength{\itemsep}{0pt plus 0.5ex}
}

\begin{document}
\AddToShipoutPicture*{\BackgroundPic}

\pagenumbering{roman}

\definecolor{browntext}{RGB}{85,70,44}
\definecolor{authortext}{RGB}{118,16,0}

\noindent{\Huge\tt\color{browntext}\uppercase{$booktitle$}}

\vspace{1cm}

\noindent{\huge\tt\color{browntext} $booksubtitle$}

\vspace{3cm}

\noindent{\LARGE \tt \color{authortext} $bookauthors$}

\thispagestyle{empty}

\pagebreak

\vfill

\noindent Licensed under the \href{https://creativecommons.org/licenses/by-nc-nd/4.0/}{Creative Commons BY-NC-ND 4.0} license.

\vspace{1cm}

\noindent Compiled on $lastupdate$.

\noindent Latest version available at \url{https://mlstory.org}.

\thispagestyle{empty}

\pagebreak

\vspace{2cm}

For Isaac, Leonora, and Quentin

\thispagestyle{empty}

\pagebreak

\tableofcontents

\chapter*{Preface}

$preface$

\chapter*{Acknowledgments}

$acknowledgments$

\mainmatter

\sloppy

\setcounter{page}{1}
\pagenumbering{arabic}

$body$

\backmatter

\footnotesize

\bibliographystyle{unsrt}
\bibliography{references}

\listoffigures
\listoftables
\printindex

$endif$

%
% Layout for individual chapters
%
$if(chapter-layout)$

\hypersetup{
  colorlinks,
  linkcolor = darkblue,
  urlcolor = darkblue,
  pdftitle = {$booktitle$ - $title$},
  pdfauthor = {$bookauthors$}
}

\title{$booktitle$ - $lastupdate$}
\author{$bookauthors$}

\begin{document}

\noindent {\huge\textit{\textbf{$chapter-number$}}}

\vspace{1cm}

\noindent {\huge\it $title$}

\vspace{1.5cm}

$body$

\bibliographystyle{unsrt}
\bibliography{references}

$endif$

\end{document}

authors: lvanbever mrtzh

repo: mrtzh/unbuch

license: MIT


text:
backtrace corrupted if ensure block exist

ensure.rb
def a(b)
  raise if b > 2
  b += 1
  c(b)
end

def c(d)
  a(d)
end

begin
  a(1)
ensure
  puts 1
end

% ruby ensure.rb
1
ensure.rb:2:in `a': unhandled exception
from ensure.rb:8:in `c'
from ensure.rb:4:in `a'
from ensure.rb:8:in `c'
from ensure.rb:4:in `a'
from ensure.rb:12:in `<main>'
% mruby ensure.rb
1
trace:
[5] ensure.rb:2:in Object.a
[2] mruby/mrbgems/mruby-print/mrblib/print.rb:29:in Kernel#puts
[1] ensure.rb:14
ensure.rb:2: RuntimeError

It's already fixed.

authors: matz yasuyuki

repo: mruby/mruby


text:
Add SECURITY.md

Hey there!
I belong to an open source security research community, and a member (@lfama) has found an issue, but doesn’t know the best way to disclose it.
If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.
Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)

@zidingz can you assign this issue to me

Hey there! I work with Zi, are you a contributor of express cart?

authors: Shu12388y psmoros zidingz

repo: mrvautin/expressCart


text:
Is the search function available by default?

I can see a search input in docs but I was expecting this search functionality would come built-in in squido, I cannot see the plugin search.js anywhere... So it could be possible to have this functionality by default?Thanks in advance

The docs Github repo is here.
You can see the search.js plugin file + the frontend site.js

How can I get the search input? I've put search.js into my source/plugins/ directory and added the:
plugins: [
      {
        name: 'search',
        options: {}
      }
    ]

but I cannot see it still. I guess it's missing some html somewhere to make it show but I don't know how...
Also, which would be the plugin options?
PS: I'm not a developer and BTW the project aims to be dead simple and to not need to know about developing to get it up and running, but I think docs should be little improved to help get what you see in the demo/example page IMHO. Don't get me wrong (maybe my english doesn't help) I love your work and appreciate it but I felt some things were tricky to get it working by someone who doesn't have enough developing skills.
I've test some other static site-generators and yours is what's best for my needs, it's simple, beautiful and customizable, but I think it should be better if I could follow a guide on how to customize it. I hope you understand me. Thanks

You need to add the data so the frontend can read it. Maybe you are missing this line from your layout.hbs: https://github.com/mrvautin/squido-docs/blob/e35760385951d73dc36f006f2d03aa9770ce83ce/source/layouts/layout.hbs#L61

Also, which would be the plugin options?

The plugin options can be left blank how you have them.

PS: I'm not a developer and BTW the project aims to be dead simple and to not need to know about developing to get it up and running, but I think docs should be little improved to help get what you see in the demo/example page IMHO. Don't get me wrong (maybe my english doesn't help) I love your work and appreciate it but I felt some things were tricky to get it working by someone who doesn't have enough developing skills.
I've test some other static site-generators and yours is what's best for my needs, it's simple, beautiful and customizable, but I think it should be better if I could follow a guide on how to customize it. I hope you understand me. Thanks

This is good feedback. I'm a developer and don't know where the gaps in the docs are until I'm told.
If you have some time would you be able to details the steps where you got stuck? I will then update the docs for the next person.

I think there's some ambiguity. I expected to get what I saw in the demo page, but until I get templates page I didn't realize the demo page (squido-docs) was a template for squido. At this point, I belived squido was just what the template squido-docs provides you.
I've to say that the templates page is very well designed and self-explanatory. Maybe a brief text in github's page explaining what you see in the squido-docs is just a piece of what squido can provide you and telling is just a template of many? I don't know :)
So far I have found this problem:
First time I uploaded a markdown I get this on console,
/usr/lib/node_modules/squido/lib/common.js:55
    if(meta.permalink.slice(-1) !== '/'){
                      ^

Yeah, if you read carefully posts section you get the permalink's required (my fault), but then you get this:
/usr/lib/node_modules/squido/node_modules/feed/lib/atom1.js:58
      updated: item.date.toISOString()
                         ^

so maybe point out date meta is also mandatory.
I've found this also but I should open an issue for this:
adding tags meta I realized that If I edit post.hbs, page.hbs, 404.hbs or tag.hbs then tags in /tag/<tag_name> multiplies (except if I edit index.hbs), like shown here:
https://user-images.githubusercontent.com/34288954/231145224-871ff4a1-3f88-4ff7-afdb-1b50554b29a7.mp4
And if you add a new tag to an existing markdown you have to restart squido to see applied changes, otherwise if you click to that newly created tag it shows a 404 not found...I dunno if that's fixable.

First time I uploaded a markdown I get this on console,
/usr/lib/node_modules/squido/lib/common.js:55
if(meta.permalink.slice(-1) !== '/'){
^
Yeah, if you read carefully posts section you get the permalink's required (my fault), but then you get this:
/usr/lib/node_modules/squido/node_modules/feed/lib/atom1.js:58
updated: item.date.toISOString()
^
so maybe point out date meta is also mandatory.

Agreed. The error handling is not good enough around this bit. I will add something more helpful.

I've found this also but I should open an issue for this:
adding tags meta I realized that If I edit post.hbs, page.hbs, 404.hbs or tag.hbs then tags in /tag/<tag_name> multiplies (except if I edit index.hbs), like shown here:

I think this is due to not having the -c flag (Clean build dir) on your squido command. So the command in your terminal would be squido serve -w -b -c. Maybe -c should be enabled by default. I can't recall exactly why but maybe I added so the build/watch was faster.

I've been using -bwc all the time:
https://user-images.githubusercontent.com/34288954/231400429-ebaa7dc5-f8f7-4a05-baaf-2581ed0f3537.mp4

Regarding search. Could the search result in the dropbox layer follow the anchor? I mean, if I click on a result, it loads only the markdown where the result were, but not the specific anchor where really it is.

authors: Neules mrvautin

repo: mrvautin/squido


text:
qt.qpa.plugin: Could not load the Qt platform plugin "windows" in "" even though it was found

Describe the bug
qt.qpa.plugin: Could not load the Qt platform plugin "windows" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: direct2d, minimal, offscreen, windows..
Environment information:

OS version: win10

@WestbrookZero Thanks for reporting this issue. Can you also specify what distro (e.g., Melodic, Noetic, or Foxy) and some steps how you run into this?

Thanks for your answer!

I use Melodic on win10, i set environment path :
Path
C:\opt\ros\melodic\x64\bin
QT_PLUGIN_PATH
C:\opt\ros\melodic\x64\plugins
QT_QPA_PLATFORM_PLUGIN_PATH
C:\opt\ros\melodic\x64\plugins\platforms
when i start "x64 Native Tools Command Prompt for VS 2019",Run as Administrator，as below：
cd C:\opt\ros\melodic\x64
setup.bat
rosrun rviz rviz
i still have the error:
qt.qpa.plugin: Could not load the Qt platform plugin "windows" in "C:\opt\ros\melodic\x64\plugins\platforms;" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: direct2d, minimal, offscreen, windows.

fixed in noetic.

authors: IoTDan WestbrookZero seanyen

repo: ms-iot/ROSOnWindows


text:
how to handle exception when not any file uploaded

const file = (req, user) => {     return new Promise((resolve, reject) => {         const busboy = new Busboy({ headers: req.headers });         busboy.on('field', function (fieldname, val) {             // some code         });         busboy.on('file', async (fieldname, file, filename, encoding, mimetype) => {             //some code             return resolve()         });        busboy.on('finish', function() {            return reject()        });         busboy.end(req.rawBody);     }) }
when not any file uploaded then it works file but it also reject file uploaded
if i remove busboy.on('finish', function() {            return reject()        });
and not upload any file then it not return any response unless request fail

I'm not quite sure I follow, but the 'finish' event handler should always be called, so it would probably be best to put your accept/reject logic in there instead. You could set a flag in your 'file' event handler that you then check in the 'finish' event handler to know whether to accept or reject the promise.

hi @mscdex
is there any way to handle, if i upload any file against key or even not pass any param in body?
anyways above sound good let me try, then i will let you know if will in trouble
thanks

This issue can be closed.

authors: markstos mscdex umar0107

repo: mscdex/busboy


text:
🛑 Do53 Roost IPv4 UDP is down

In 19c1152, Do53 Roost IPv4 UDP (http://107.189.10.142:9202) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv4 UDP is back up in 485e150 after 1 hour, 1 minute.

repo: mschirrmeister/upptime-loopx


text:
🛑 Do53 Roost IPv4 TCP is down

In 993fa3c, Do53 Roost IPv4 TCP (http://107.189.10.142:9203) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv4 TCP is back up in f7814aa after 18 minutes.


text:
How to use custom custom libraries/tools/packages

Hi there,
Great tool you've made. I am trying to use it with a specific package say jq, or even good old curl. Both are present on my system but missing in shell2http's script contexts. I've check with PATHs but nothinhg there. It seems that everything is running contained, which is nice and secure. How could I install those packages without calling the apt-get in my script (which would be overkill) ?
Thanks fo your help

Hi,
if the tool is present in the OS (and in the PATH) and then it should be available for run in shell2http.
What operating system do you using? If is it Linux/macOS, for testing please run script like this:
shell2http /path 'echo $PATH' /jq 'type jq'

What is the response to the requests:
curl http://localhost:8080/path
curl http://localhost:8080/jq

?

I'm using a ubuntu 16.04
launching
shell2http /path 'echo $PATH' /jq 'type jq' /curl 'which curl'
curl http://localhost:8080/path gives
/snap/shell2http/14/usr/sbin:/snap/shell2http/14/usr/bin:/snap/shell2http/14/sbin:/snap/shell2http/14/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
curl http://localhost:8080/jq gives
exec error: exit status 127
and
curl http://localhost:8080/curl
exec error: exit status 1
I've also tried to come up with a custom Docker as per your https://github.com/msoap/shell2http#run-from-docker-container...
Adding  RUN apk add --no-cache jq curl in test.Dockerfile
and calling a docker build on that, without success so far. And I'd like to know wether ther's something simpler before I go down that path
Thank you for your time and answers

This is snap-specific problem. Snap package has own /usr/bin (see https://forum.snapcraft.io/t/missing-commands-in-usr-bin/3502), where jq or curl is not present :(
as I see, there is only one solution: uninstall snap package (sudo snap remove shell2http) and install via deb-package (dpkg -i shell2http_1.13_amd64.deb) or build from source (go get -u github.com/msoap/shell2http)

HI Sergey,
Thanks a lot, that did the trick. I guess I came accross "containerization" limitation.

authors: cwartel msoap


text:
Steam p2p testing example

Updated the simple box example to work with steam p2p :)

i'll create a pull request on the lightyear repo directly 😄

repo: msvbg/lightyear


text:
🛑 A Chjana is down

In f66b7b3, A Chjana (https://achjana.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: A Chjana is back up in e4722cf.

repo: mswd-io/upptime


text:
Feature/murmurhash3 hashes

Since cryptographic hashes (sha*) are quite heavy at calculation and may also experience collisions on large amounts of data, propose to use more efficient algorithms, like Murmurhash3.

Thank you !

authors: eigokor mtakemi

repo: mtakemi/fluent-plugin-genhashvalue


text:
add support for Mac

Trying to docker up this project on Mac throws this error.

To resolve this issue and ensure smooth Docker image setup for Mac users, it's necessary to include the Mac platform in the gem lock file. This can be achieved by executing the following command:
bundle lock --add-platform aarch64-linux

/shipit

repo: mtantawy/job-hunt-tracker


text:
🛑 https://911.ps is down

In 9c269a0, https://911.ps (https://911.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://911.ps is back up in 6b609fc.

repo: mtitservice/site


text:
🛑 https://detulkarm.edu.ps is down

In c7e8ad3, https://detulkarm.edu.ps (https://detulkarm.edu.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://detulkarm.edu.ps is back up in c349279.


text:
🛑 https://salfeet.plo.ps is down

In 3d86099, https://salfeet.plo.ps (https://salfeet.plo.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://salfeet.plo.ps is back up in a1abec1.


text:
🛑 https://palpost.ps is down

In 12100ba, https://palpost.ps (https://palpost.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://palpost.ps is back up in 34afbd4.


text:
🛑 https://mtit.pna.ps is down

In b1bf544, https://mtit.pna.ps (https://mtit.pna.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://mtit.pna.ps is back up in 98b2d0b.


text:
🛑 https://911.ps is down

In f99ca96, https://911.ps (https://911.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://911.ps is back up in 532724a.


text:
🛑 https://911.ps is down

In a30e987, https://911.ps (https://911.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://911.ps is back up in 51a8ec7.


text:
Send CTRL-ALT-Del key sequence needs to be under the Actions menu

To use TinyPilot with Windows Server OS, from NT 3.51 forward requires sending the Ctrl-Alt-Del key sequence to start the logon process.  Many commercial remote console products, like VMware's Remote Console have buttons to send this key sequence, because pressing those keys is handled by the local machine first.  Currently to do this with TinyPilot, you must bring up the virtual keyboard and press the keys individually.  This is a feature that is required is TinyPilot is going to make any in roads to data centers that employ Windows Server machines.

Thanks! I agree, this is something we need to add.
We're currently tracking this in #481.

authors: glendady mtlynch

repo: mtlynch/tinypilot


text:
32_text.models.awdlstm: create docments

Add documents to 32_text.models.awdlstm.
See the style guide and contribution guide for more details (links will be added when created).
This requires a moderate familiarity with pytorch, otherwise very little fastai specific knowledge needed. This notebook defines how to create the awd-lstm model. Some reading to understand decisions may be required.
Documents progress(only one section):

[ ] Basic NLP modules

I can give this one a shot

authors: arampacha marii-moe

repo: muellerzr/fastai-docment-sprint


text:
How to print std::exception

`#include
#include "easylogging++.h"
INITIALIZE_EASYLOGGINGPP
void mch(int sig){
LOG(ERROR) << "ohh, crash";
el::Helpers::logCrashReason(sig, true);
el::Helpers::crashAbort(sig);
}
int main() {
std::cout << "begin " << std::endl;
el::Helpers::setCrashHandler(mch);
//    int* x;
//    *x=1; //This print correct stack trace
std::vector v(1);
v.at(2); // not print stack
std::cout << "crash end!" << std::endl;
return 0;
}`
How to print the std::exception stack trace use easyloggingpp ?
Thinks

You can try Logging Third-Party class - let us know how you go

authors: abumusamq zhm-nico-nico-ni

repo: muflihun/easyloggingpp


text:
material-ui-icons-next wrong peerDependencies

Currently I'm using material-ui v0.20 and I want start the migration to v1.
As it is written on the page: https://material-ui-next.com/guides/migration-v0.x I've installed the package material-ui-next to have to versions of material-ui (npm install material-ui-next).
Now I want to use material-ui-icons package.
So my idea was to install the material-ui-icons-next that analogous should have the dependencies to material-ui-next not to material-ui package.
Current Behavior
npm WARN material-ui-icons-next@1.0.0-beta.17-next requires a peer of material-ui@^1.0.0-beta.16 but none was installed.
material-ui-icons-next package.json:
"peerDependencies": {
    "material-ui": "^1.0.0-beta.16",
    "react": "^15.3.0 || ^16.0.0",
    "react-dom": "^15.3.0 || ^16.0.0"
  }

Expected Behavior
material-ui-icons-next package.json:
"peerDependencies": {
    "material-ui-next": ...
}

This issue will be solved once we release Material-UI under a new npm organization in #9673. We will be able to close #9469 too.
Current workaround: https://github.com/mui-org/material-ui/pull/8473#issuecomment-333472103

Ok, I still have a problem with that.
My current situation:
In package.json I have:
    "material-ui": "^0.20.0",
    "material-ui-icons-next": "^1.0.0-beta.17-next",
    "material-ui-next": "^1.0.0-beta.31",

My whole app is based on v0.20, but I want to migrate all icons to material-ui-icons-next and I'm using them like this:
import {
    CheckCircle as CheckCircleIcon,
    KeyboardArrowDown as KeyboardArrowDownIcon,
    PersonOutline as PersonOutlineIcon
} from 'material-ui-icons-next';
// ...
<PersonOutlineIcon className="ico" />

And now, after the build on Bamboo I have an error:
npm ERR! peer dep missing: material-ui@^1.0.0-beta.16, required by material-ui-icons-next@1.0.0-beta.17-next
On the beginning of my App.js I've added the code that was mentioned as a workaround, but probably is not completely related to my case.
import SvgIcon from 'material-ui-next/SvgIcon';
global.__MUI_SvgIcon__ = SvgIcon;

I'm closing the issue as the pain point was solved temporarily with #9469. No need to keep it open.
Why don't you do?
- "material-ui-icons-next": "^1.0.0-beta.17-next",
+ "material-ui-icons": "^1.0.0-beta.17",

There is no matter if I'm using material-ui-icons-next or material-ui-icons.
Problem appears during npm install...
npm ERR! peer dep missing: material-ui@^1.0.0-beta.16, required by material-ui-icons@1.0.0-beta.17
So the error is saying that im missing material-ui@^1.0.0-beta.16
but I have this package but on the other name (material-ui-next like it was recommended in docs).
So in my opinion in dependencies of material-ui-icons should be:
peerDependencies: material-ui@^1... OR material-ui-next@^1...
Am I right?

@nitkapawel I used to have this warning too. It's should be temporary the time of the migration. At the end of the day, it's a warning reminding you to complete the migration. It's not a blocker.

peerDependencies: material-ui@^1... OR material-ui-next@^1...

This would suppress the warning. But I'm note sure it's a good thing.
Especially given the situation is already pretty ugly with:
import SvgIcon from 'material-ui-next/SvgIcon';
global.__MUI_SvgIcon__ = SvgIcon;

authors: nitkapawel oliviertassinari

repo: mui-org/material-ui


text:
ChromeVox on Google Chrome doesn't announce ascending/descending sorting on  button

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔

When using ChromeVox as a screenreader on Google Chrome, tabbing through table header buttons should announce if a button sorts a table and the current sorting & direction.
Examples of tables that work with ChromeVox:
https://dequeuniversity.com/library/aria/tables/sf-table-sortable
https://heydon.github.io/react-sortable-table-demo/
Current Behavior 😯

Only the text of the button and "button" is read out, even if that button is being used for sorting.
Steps to Reproduce 🕹

Link: https://material-ui.com/components/tables/#sorting-amp-selecting

Turn on ChromeVox extension with Google Chrome.
Tab to a sorting button on the table in the demo above (like Calories).
Click it and listen to the screenreader.
No sorting announcements!

Context 🔦

A11y for ChromeVox :) We want to reuse this table but a lot of our users use ChromeOS and ChromeVox
Your Environment 🌎

Tech
Version

Google Chrome
Version 75.0.3770.142 (Official Build) (64-bit)

ChromeVox
53.0.2784.5

MacBook Pro 2018
macOs Mojave 10.14.5

It is also the same on ChromeOS.

This seems to be an issue of screen readers not supporting the aria-sort property (which appears to be correctly applied in the Material-UI table).
The two "working" examples use a visually hidden text description of the sort order. One challenge with this approach is l10n (the descriptions will be announced in English), but I imagine that is preferable to no description at all.

It is going to be an issue for us alright, so if there's a clever way that MUI can allow us to supply the visually hidden text description (and let us handle the internationalisation), that would work.

Also opened a bug for ChromeVox in the meantime: https://bugs.chromium.org/p/chromium/issues/detail?id=987997

@ahayes91 Looks like we can fix it in the demo: https://deploy-preview-16767--material-ui.netlify.com/

Should there be an announcement on change of the sorting (as opposed to having to navigate away from the button and back to hear the new sorting order)?

Should there be an announcement on change of the sorting

@ahayes91 I'm really confused. That's exactly how this was behaving with ChromeVox when I submitted this PR, but testing now in response to your comment, it doesn't seem to work any more.
I wish I'd recorded it, as there's no logical explanation for why it should stop working, but I promise you it was working before. I'll take another look, but if you have any ideas, I'm all ears.

🤔 very strange if it was working before. The other solution could be to use a visually hidden aria-live="polite" span that announces the sorting of the table (both the header name and the sort direction).
Do the MUI components get audited by accessibility SMEs at any point?

The other solution could be to use a visually hidden aria-live="polite"

Thanks, yes, that would have been my next step if it hadn't apparently been working already.

Do the MUI components get audited by accessibility SMEs at any point?

Sadly not – we depend on members of the community with an interest in accessibility to point out issues when they find them, and do our level best to fix them (which is why I jumped on this one, albeit with limited success). Unfortunately it doesn't seem to be a high priority for many developers.
If you have any ideas as to how we can improve this, we'd love to know!


text:
Invariant Violation Maximum update depth exceeded on TextareaAutosize with Meiryo font in Firefox

Current Behavior 😯
This bug is similar with #16685.
With the specific font (Meiryo font), bug has not been fixed.
Firefox (69) NG
Chrome (76) OK.
Steps to Reproduce 🕹
https://codesandbox.io/s/create-react-app-c69fh
Your Environment 🌎

Tech
Version

Material-UI
v4.4.1

React
v16.9.0

Firefox
v69

Chrome
v76

It seems that the bug occuring conditions are limited.

TextField contained with ExpansionPanel and ExpansionPanelDetails -> not occured.
TextField contained with Dialog and DialogContent -> occured.

Investigation an issue related to this.
Resolved by removing the 'rows' attribute from TextField

Could you confirm that this diff solves the problem?
diff --git a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
index 6634f0e6b2..6ac6e9742e 100644
--- a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
+++ b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
@@ -21,6 +21,8 @@ const styles = {
     height: 0,
     top: 0,
     left: 0,
+    // Create a new layer, increase the isolation of the computed values
+    transform: 'translateZ(0)',
   },
 };

I could reproduce the problem on Firefox v69 with a zoom of 133%. Otherwise, removing the possibility for an infinite rendering loop, as proposed in this comment https://github.com/mui-org/material-ui/issues/16685#issuecomment-513948427 sounds good to me too.

@oliviertassinari
I tried this diff.
I confirmed the bug was not occurred.
'translateZ()' CSS function will fix the bug.

Nice, do you want to submit a pull request?
@bitoverflow would it solve your issue too?

@oliviertassinari
I think it is better that material-ui library includes this bug fix.

@hatanaka-akihiro agree, do you want to make it happen?

@oliviertassinari Yes.

@oliviertassinari
The patch did not solve it for us, but are starting to see a pattern on what is triggering it

The screen needs to have a wide resolution
The size of the browser window needs to have an odd number

..strange things

@bitoverflow Thanks, in this case, I think that we can also remove the infinite loop potential with https://github.com/mui-org/material-ui/issues/16685#issuecomment-513948427. I'm tired of seeing this class of issue report. It seems that layout text measurement is instable.

A user of mine is also having this issue, they are on Firefox 69, newish macbook air.
Setting zoom to 80% stops it from crashing and having the console open stops if from crashing. Will keep troubleshooting to see what else is a factor.
I am also on Firefox 69, windows 10 and am not having this issue.

Are now also seeing this in Internet Explorer 11.
Triggered a little different.
TextField with multiline, rows 3, inside a Dialog. Crashes when user fills the area with text and it needs to grow.
Stabilize by removing the rows parameter

Does somebody want to work on the problem and submit a pull request?

I am still seeing this in 4.5.0 with IE11
rows=3. Crashes with Maximum update depth exceeded when typing the TexField full
Sandbox are not loading in IE11, så are not able to give an example

Solving IE 11 wasn't an expectation of the issue nor the pull request.

@bitoverflow If you have a reproduction, we would appreciate it. This issue was about Firefox.

@oliviertassinari Created a new issue https://github.com/mui-org/material-ui/issues/17672 with demo

authors: bitoverflow hatanaka-akihiro joziahg oliviertassinari


text:
Question / Bug. How to change React Material UI slider label text

I need to change text in label, not background color

const theme = createMuiTheme({ overrides:{     MuiSlider: {          valueLabel: {              color: 'black',          },     } }

[x ] The issue is present in the latest release.
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
It changes only tbackground  color, not text color
Expected Behavior 🤔

It should change only text color, not background color

Tech
Version

Material-UI
v4.9.0

React
16.12.0

Browser
Google Chrome 80

I fixed this problem by changing constrastText to "my color" pallete theme

@Ghost180195 Thanks for raising this issue. At first glance, it seems that we will need to update the style of the component:

https://material.io/components/sliders/#anatomy

https://www.google.com/flights
We should be able to move from 3 to 1 or 2 elements. In any case, it's likely a breaking change, so something to plan for v5.
In the meantime, I would propose that we make the SliderValueLabel a public component:
diff --git a/packages/material-ui/src/Slider/ValueLabel.js b/packages/material-ui/src/Slider/ValueLabel.js
index e2f21ec0d..6b57749d5 100644
--- a/packages/material-ui/src/Slider/ValueLabel.js
+++ b/packages/material-ui/src/Slider/ValueLabel.js
@@ -69,4 +69,4 @@ function ValueLabel(props) {
   );
 }

-export default withStyles(styles, { name: 'PrivateValueLabel' })(ValueLabel);
+export default withStyles(styles, { name: 'MuiSliderValueLabel' })(ValueLabel);

@Ghost180195 Do you want to work on the problem? :)

The latest design of the slider I could find on Google's product:

https://www.google.com/travel

https://www.google.com/travel/flights

Google Pixel 4 (2019) Android 11 (Latest version)
Any other idea where we could find a slider to benchmark?

More sources to benchmark:

Adobe XD kit released in August 2020:

Flutter component https://api.flutter.dev/flutter/material/Slider-class.html

Material Components Android: https://github.com/material-components/material-components-android


text:
[Autocomplete] Scroll to bottom not working

Scroll through a list of items not working if I'm switching arrow keys on the keyboard and mouse scroll into the Autocomplete component

[x ] The issue is present in the latest release.
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

I'm using the mouse to scroll/navigate through a list of dropdown items, after that I'm switching to keyboard arrow keys scroll and it's not working, I see just "jump", but since then I can't reach the last element in the list.
Expected Behavior 🤔

When I'm using arrow keys and move mouse I can navigate through the list, scroll works well and I can navigate to the last item of the list.
Steps to Reproduce 🕹

Steps:

Open page - https://material-ui.com/components/autocomplete/
Focus first Combobox example on the page
Try to scroll the dropdown list using the mouse
While dropdown still open try to continue scrolling using arrow keys
Check if you can reach the last item of the list (I see just "jumping")

Context 🔦

Scroll to the bottom of the dropdown list
Your Environment 🌎
Chrome browser Version 85.0.4183.121 (Official Build) (64-bit)

Tech
Version

Material-UI
v4.11.0

React

Browser

TypeScript

etc.

@hyggesoftware This is expected, the arrow moves the highlight, the scroll bar doesn't.

authors: hyggesoftware oliviertassinari


text:
[typescript] Upgrade types, use string index fallback for CSSProperties to allow nested pseudos

Resolves #11004.
My PR to @types/react to make CSSProperties a closed type (sans string index fallback) indirectly broke Material UI, which was relying on it. The problem is that React's CSSProperties are only meant to capture what is expressible by inline styles, but Material UI's JSS API allows nested pseudo selectors, for example. So we need to make a new CSSProperties specific to Material UI, based on CSSType, which allows a string index.

So, from this on, we should be importing CSSProperties from material-ui rather than using React.CSSProperties, right?

@franklixuefei in the context of writing styles for use with withStyles, yes. Only use React.CSSProperties in the context of inline styles.

@pelotom Thanks. There can't be nested styles or psuedo selectors in inline styles of course... I understand it now.

Material UI also supports array syntax and default unit (e.g. margin: [[2, 8]] translates to margin: 2px 8px) which is now broken with the new typings. Can we also fix this?

@varoot

Material UI also supports array syntax and default unit (e.g. margin: [[2, 8]] translates to margin: 2px 8px) which is now broken with the new typings. Can we also fix this?

Interesting, I wasn't aware of this. Is the outer array used for fallbacks?
It looks like this only worked before with the old anything-goes React.CSSProperties because margin was defined as
        margin?: CSSWideKeyword | any;

According to JSS documentation, the outer array represents comma-separated values and the inner one for space-separated values.

Hm, currently @types/jss doesn't support these things, I guess that's a change that needs to be made there.

Apparently JSS also accepts callback function as value but I'm not sure about whether Material UI supports this or how to use it.

Yeah, in general I'm not sure which things from JSS are supported by Material UI and which not. My understanding was that it was a strict subset somehow, but I don't know exactly what the differences are. Maybe @oliviertassinari could shed some light on this?

I’m working on a PR for @types/jss to make all the examples in that link work, @varoot. There are lots of deficiencies currently. Then we can use those types (or whatever subset of them makes sense) in MUI. Until then I think this PR is good to merge as an intermediate improvement.

Material UI also supports array syntax and default unit (e.g. margin: [[2, 8]] translates to margin: 2px 8px) which is now broken with the new typings. Can we also fix this?

@varoot Material-UI doesn't support it out of the box. This feature is coming from: jss-expand. A JSS plugin that doesn't come by default (the plugin cost 1.3 kB gzipped).

Apparently JSS also accepts callback function as value but I'm not sure about whether Material UI supports this or how to use it.

No, we don't support it yet. Not supporting it allow allow a better cache strategy and a lighter bundle.
@pelotom The pull-request looks good to me. Any blocker for mergin it?

@oliviertassinari Thanks for the info. This is good to merge.

@oliviertassinari I could use the syntax without installing any other plugin so I'm pretty sure this is JSS's standard syntax (as documented on their Core JSON Syntax page). JSS Expand seems to offer different syntax (only one level of array needed and allowing object syntax).
I have a repository to prove it but you can also try it yourself. But since people don't seem to be aware of this feature, maybe I just shouldn't use it.

@varoot I have never used it but I can trust you on this.

@oliviertassinari I could use the syntax without installing any other plugin so I'm pretty sure this is JSS's standard syntax (as documented on their Core JSON Syntax page). JSS Expand seems to offer different syntax (only one level of array needed and allowing object syntax).
I have a repository to prove it but you can also try it yourself. But since people don't seem to be aware of this feature, maybe I just shouldn't use it.

It definitely seems to work, and I don't see why it shouldn't be supported by the typings!
From my further experimentation it looks like the function and observable options from that page are not supported by Material UI, probably because link: true isn't being specified? Though I think there has been some talk of someday allowing styles to depend on props using the function mechanism.

authors: franklixuefei oliviertassinari pelotom varoot


text:
[docs] Fix typo in the icons section

Just fixed the GitHub typo, sorry.

@PolGuixe Thanks

authors: PolGuixe oliviertassinari


text:
[Tabs] Update onChange signature to match docs

Contributor Checklist

[ ✓ ] I have followed (at least) the PR section of the contributing guide.

Summary
Changed the value from any to number to match the documentation at https://material-ui.com/api/tabs/

Oh. If it is meant to be any, then should this be changed?
https://github.com/mui-org/material-ui/blob/next/packages/material-ui/src/Tabs/Tabs.js#L462

The value has an unknown type at compile time (any is used for older code). TypeScript can't infer what possible types are passed. The linked docs only make a statement about the default behavior if no value is passed. If a value is passed then that one is used.

@jharrilim Thanks.


text:
[LoadingButton] Change LoadingButton prop pending to loading

This pull request renames the pending prop of the LoadingButton component to loading, as per issue 21593

I'm not sure the related issue had reached enough maturity to go to the implementation phase.

Moving the discussion back to #21593

I'm not sure the related issue had reached enough maturity to go to the implementation phase.

The issue is marked as "good to take"...

@mbrookes True, why I reopened it. Do we want to move forward with this direction?

🍿

The pull request has been updated, the unit tests were fixed. The tests that were failing because the original code had an incorrect casing in these props: endIconLoadingEnd, startIconLoadingStart, and labelLoadingCenter.

OK, re-reading the linked issue a couple of weeks later, I think that we should go all-in on loading. The button isn't in a pending state that's the application or some task. However, the button displays a loader. So I think that that loading, even if not perfect is better, it better describe the state or the button which I think we should optimize for.

However, we didn't receive a clear approval in the team for going forward so closing both PR and issue.

authors: guillermaster mbrookes oliviertassinari


text:
[website] Add about page

Preview: https://deploy-preview-27599--material-ui.netlify.app/branding/about/
waiting for #27598

added tooltip to show location on hover. I think it is nice to see the location apart from country flag.

[ ] I have followed (at least) the PR section of the contributing guide.

Hey! You missed me on the team grid, I'm actually sad! 😭😭😭

Hey! You missed me on the team grid, I'm actually sad! 😭😭😭

Actually, the last is the most important one! 😂

Hey! You missed me on the team grid, I'm actually sad! 😭😭😭

Added, you have the most outstanding background! how cool is that.

@oliviertassinari by removing this line
<Person
-  sx={{ height: '100%' }}
  {...profile}
/>

you got,

Have you considered this?

@siriwatknp Oops, I was initially aiming to remove the duplication (x3)

@siriwatknp Oops, I was initially aiming to remove the duplication (x3 sx={{ height: '100%' }}).

Okay, no prob. I have brought it back. I don't think there is anything left for this page (checked the lighthouse in the PR description, it looks good to me)

When the font loads, the layout shifts, it's distracting. OS font:

Font loaded:

In https://next.material-ui.com/branding/about/, we fixed it by forcing the line break where we want it (with a <br>)

Here are no h1 on the page, this one should have it. (Found with Wave Chrome extension)

The img are used as links, you can add an alt, it's not decorative

I think that we could challenge the UI/UX of the button.

For instance, should it have the ripple when focused or an outlined as in https://next.material-ui.com/branding/about/

Something is off with the companies in dark mode

@oliviertassinari For 4 and 5, I am waiting to hear from @danilo-leal opinion but I don't think it is a priority and can be improved later.

@oliviertassinari For 4 and 5, I am waiting to hear from @danilo-leal opinion but I don't think it is a priority and can be improved later.

About 4, what would you make it different? And about 5, we're going to revisit that in a refinement phase (updating the companies we use + the coloring and sizing of the logo - to all pages). Agree with not being a priority :) Very awesome work!

@michaldudak 👍  I recall @mbrookes did it for the current logos on the homepage.

I'm not sure what the illustration is for here

Decorating the logo also goes against the visual identity guidelines (ours, and in general). @danilo-leal let me know if you don't have them.

authors: danilo-leal mbrookes oliviertassinari siriwatknp


text:
[Doc] Add import Option 2 in the Material Icons page

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
https://mui.com/components/material-icons/
Right now the following page allows you to 1-click copy the import. Which is very useful to search for an icon and import it immediately. However it only offers Option 1, which is not our prefer way of importing.
Options reference from the usage section: https://mui.com/material-ui/icons/#usage

Motivation 🔦

Option 2 is a much better Dev Experience, we use Tree Shaking and bundle size isn't much of an issue for us in the first place, efficient development is.

I feel like I'm missing some key information to make sense of this issue. What are "Option 1" and "Option 2"?

I have added a link and image to the description. Hopefully that should be clearer !

repo: mui/material-ui


text:
Select with more than 100 items in Modal appears on the left before repositioning

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Currently when we have a MUI modal that contains a MUI select with more than 100 items, the first time you open that select, the items appear glued to the left of the screen, before repositioning to their intended spot.
Expected behavior 🤔
The items should immediately appear in their intended spot, relative to the input.
Steps to reproduce 🕹
Steps:

Create a Modal
Add a Select with more than 100 elements
Click on the Select

Context 🔦
I'm trying to make a Select inside a modal that contains a list of countries.
Your environment 🌎
Working example: https://stackblitz.com/edit/react-ts-xefudx?file=App.tsx

@AngelGenchev95 I tried your stackblitz but I could not see the issue. Can you check?

Here's a video of the issue:
https://user-images.githubusercontent.com/41321846/182336688-45bc69fb-0925-4231-b62f-37202a2b9c21.mov
I'm using a macbook pro, Chrome

The same issue even without Dialog component.
Please see my screen record.
https://user-images.githubusercontent.com/5411244/183246611-5247f0f3-82e5-47b0-a08e-1d7dbf873f7d.mov
React version: 18.2
MUI version: 5.9.3

Hi there,
The reason of this behavior is a big amount of options that are rendered simultaneously when select is opening. Even with 20 - 30 options this issue this error becomes noticeable. If we use 1000 options, the list is rendered at the left and only after ~3 seconds moves to the proper position.
I've found a several possible solutions/ideas:

Use native select. This is the simplest solution (just add one prop), but unfortunately options list is out of common design and it looks a little bit ugly.

Use virtualization for the options list.  I tried to use Virtuoso for the options list but unfortunately I didn't find how to do it properly.

Use Autocomplete instead of Select. It uses virtualization inside, options renders properly. But it provides a little bit another functionality then Select, also there are visual deferences.

Render just one MenuItem component on select opening and then render all options after small delay.  This solution I applied for my project.
Initially I render just one MenuItem disabled component with progress bar inside. After 300ms delay all other options are rendered.

const FormPhoneNumber: FC<FormPhoneNumberProps> = ({}) =>
{
    const {data: countries = []} = useGetCountriesQuery();
    const [countryCode, setCountryCode] = useState<number | ''>('');
    const [isOpened, setIsOpened] = useState<boolean>(false);

    return (
        <TextField
            select
            SelectProps={{
                onOpen: () => setTimeout(() => setIsOpened(true), 300),
                onClose: () => setIsOpened(false),
                renderValue: () =>
                {
                    const item = countries.find(({phoneCode}) => countryCode === phoneCode);
                    return item ? getOptionLabel(item) : '';
                },
            }}
            label="Country"
            value={countryCode}
            onChange={(event) => setCountryCode(Number(event.target.value))}
            fullWidth
        >
            {!isOpened && (
                <MenuItem
                    disabled
                    sx={{
                        opacity: '1 !important',
                        justifyContent: 'center',
                    }}
                    value={countryCode}
                >
                    <CircularProgress size={20} disableShrink />
                </MenuItem>
            )}

            {isOpened && countries.map((item) => (
                <MenuItem key={item.code} value={item.phoneCode}>
                    {getOptionLabel(item)}
                </Option>
            ))}
        </TextField>
    );
};

@AngelGenchev95, probably this solution will be also acceptable for you.

Yes, this is a duplicate of #33308.

authors: AlexKrupko AngelGenchev95 michaldudak siriwatknp


text:
[Chip] Deletable Chip has the pointer cursor on the whole chip as if it were clickable

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://stackblitz.com/edit/react-7vbdzr?file=Demo.tsx
Current behavior 😯
Deletable Chip has the pointer cursor on the whole chip as if it were clickable
Expected behavior 🤔
Deletable Chip has the pointer cursor only on the erase x button
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Thanks for the report @Nic-S!
I'll work on it

authors: DiegoAndai Nic-S


text:
Allow Menu Items to be focused via keyboard when wrapped in  and  tags

Summary
While trying to create a keyboard accessible dropdown menu, MenuItems were wrapped in a <Tooltip> and  became inaccessible and broke the accessibility of the dropdown menu. The Menu itself was selectable via keyboard, but the items wrapped in both <Tooltip> and  within it were completely inaccessible.
Example of an inaccessible MenuItem:
<Tooltip title={"This is menu item 1"} placement="top" arrow>

    <MenuItem>
      Menu Item 1
    </MenuItem>

</Tooltip>

Examples
This menu is not keyboard accessible.
Specific keystrokes were tab to select the menu, return to open, and then I tried both tab and arrow keys to try and focus a specific Menu Item.
<Button onClick={handleMenuOpen}>Dropdown Menu</Button>
<Menu
  open={isOpen}
  onClose={handleMenuClose}
>
  <Tooltip title={"This is menu item 1"} placement="top" arrow>

      <MenuItem>
        Menu Item 1
      </MenuItem>

  </Tooltip>
  <Tooltip title={"This is menu item 2"} placement="top" arrow>
    <MenuItem>
      Menu Item 2
    </MenuItem>
  </Tooltip>
</Menu>

This example is keyboard accessible. When opened with tab + return the first menu item is auto-focused.
<Button onClick={handleMenuOpen}>Dropdown Menu</Button>
<Menu
  open={isOpen}
  onClose={handleMenuClose}
>
  <Tooltip title={"This is menu item 1"} placement="top" arrow>
    <MenuItem>
      Menu Item 1
    </MenuItem>
  </Tooltip>
  <Tooltip title={"This is menu item 2"} placement="top" arrow>
    <MenuItem>
      Menu Item 2
    </MenuItem>
  </Tooltip>
</Menu>

Both examples built by using create-react-app to generate a clean application and then MUI was installed with in the application.
Expanded code snippets
Full code for breaking PoC app
import { useState } from 'react';
import { Button, Menu, MenuItem, Tooltip } from '@mui/material';

function App() {
  const [isOpen, setIsOpen] = useState(false)

  const handleMenuOpen = () => {
    setIsOpen(true)
  }

  const handleMenuClose = () => {
    setIsOpen(false)
  }

  return (

        <Button onClick={handleMenuOpen}>Dropdown Menu</Button>
        <Menu
          open={isOpen}
          onClose={handleMenuClose}
        >
          <Tooltip title={"This is menu item 1"} placement="top" arrow>

              <MenuItem>
                Menu Item 1
              </MenuItem>

          </Tooltip>
          <Tooltip title={"This is menu item 2"} placement="top" arrow>
            <MenuItem>
              Menu Item 2
            </MenuItem>
          </Tooltip>
        </Menu>

  );
}

export default App;

Relevant `package.json` properties
"dependencies": {
    "@emotion/react": "^11.11.4",
    "@emotion/styled": "^11.11.5",
    "@mui/material": "^5.15.20",
    "@testing-library/jest-dom": "^5.17.0",
    "@testing-library/react": "^13.4.0",
    "@testing-library/user-event": "^13.5.0",
    "react": "^18.3.1",
    "react-dom": "^18.3.1",
    "react-scripts": "5.0.1",
    "web-vitals": "^2.1.4"
  },

Motivation
I am trying to create a keyboard accessible dropdown menu with MenuItems that are wrapped in  tags for formatting, styling, and some minor control functions.
Search keywords: MenuItem Span Accessibility

Hey @BenSullivanWP, thanks for the report!
Similarly to https://github.com/mui/material-ui/issues/14943#issuecomment-474318783, the Menu component relies on the MenuItems not being wrapped in any elements. The Tooltip is a special case as it doesn't wrap the MenuItem. This is a known limitation, but it can be improved. Soon we'll start to refactor components on top of Base UI, so I'll add this issue to that milestone. This way we'll review it while we rework the Menu components.

authors: BenSullivanWP DiegoAndai


text:
[blog] Add release post for MUI X Premium

Blog post to announce the Premium plan release.
preview: https://deploy-preview-32720--material-ui.netlify.app/blog/premium-plan-release

@joserodolfofreitas If you want to add the notification about the blog post, I suggest doing it in another PR so that it is independent (the notification will appear immediately once it is merged to master without deploying)

authors: joserodolfofreitas siriwatknp


text:
[styled-engine-sc] Fix types for css function of styled-engine-sc

[x] I have followed (at least) the PR section of the contributing guide.

Fixes https://github.com/mui/material-ui/issues/40498

Can you please create a sandbox using the build packages from the PR, that will validate the fix? These are the package version:

@mui/material: https://pkg.csb.dev/mui/material-ui/commit/ef9f9180/@mui/material
@mui/styled-engine-sc: https://pkg.csb.dev/mui/material-ui/commit/ef9f9180/@mui/styled-engine-sc

You can find them here: https://ci.codesandbox.io/status/mui/material-ui/pr/40640/builds/461016

Can you please create a sandbox using the build packages from the PR, that will validate the fix? These are the package version:

To be honest. I never understood how i can create a codesandbox for the styled-engine-sc, since we have to this mapping in the webpack config. And your parcel thingy never really worked for me 🫣

Can you please create a sandbox using the build packages from the PR, that will validate the fix? These are the package version:

To be honest: This codesandbox situation when using styled-engine-sc really overwhelms me. The parcel version does not work correctly and if i create a devbox myself, .. i could also not figure out how to get this working. Even created an issue some time ago: https://github.com/mui/material-ui/issues/40497.
Is there any existing, working, codesandbox out there, using typescript and styled-engine-sc, which i could re-use, in order to satisfy your request?

Can you please create a sandbox using the build packages from the PR, that will validate the fix? These are the package version:

Ok, somehow i was able to create something that might work:
https://codesandbox.io/p/devbox/mui-styled-engine-sc-parcel-n7f2h6?file=%2Fsrc%2FApp.tsx

Let me know if i can help somehow in order to go on with this @mnajdova

Tagging @siriwatknp and @brijeshb42 to help with pushing this, together with https://github.com/mui/material-ui/pull/40656/files to the finish line. I won't have bandwidth to look into it this week, and I don't want to need to postpone it any further.

authors: delijah mnajdova


text:
[styled-engine] Add back removed internal function

Fixes https://github.com/mui/material-ui/issues/44112

Hi, anything blocking this fix?
We just started working on the MUI 6 migration and this is blocking us from finalizing it, as the app crashes at runtime in dev.
Our workaround is:
  "pnpm": {
    "overrides": {
      "@mui/styled-engine": "npm:@mui/styled-engine-sc@6.1.7",
      "@mui/system": "6.1.7"
    }
  }

authors: mnajdova wilomgfx


text:
[RFC] Rename AppProvider export for Next.js and react-router integrations

What's the problem?
I followed the example and found the example fails (keep refresh the whole page when click the nested links) when import the "AppProvider" with
import { AppProvider } from "@toolpad/core/AppProvider";

but works when use
import { AppProvider } from "@toolpad/core/react-router-dom"'

It's very confusing with the same name export but actual different. And not type 'Navigation' found of the 'core-vite' example line:
import { AppProvider, type Navigation } from '@toolpad/core/react-router-dom';

What are the requirements?
No response
What are our options?
Rename the export name and mention it in the documentation would be perfect.
Proposed solution
No response
Resources and benchmarks
No response
Search keywords:

One option that I considered before and thought about bringing up for consideration again was to export the router with React router only, to be passed as a prop to the standard AppProvider.
This requires creating an extra component sometimes, but when using createBrowserRouter instead of BrowserRouter that's already needed anyway, and it probably makes more sense.
Besides that or a possible rename, we can also consider exporting all the types from the standard AppProvider in the other AppProvider alternatives.

My idea is to add a type declaration file called "AppProviderTypes.ts", export it globally and remove the "AppProvider" export at the same time, but the changes are huge. Or add "AppProviderComponent.ts", keep the types in "AppProvider.ts", that would be a better idea.

I think we eventually want to be able to do more in the next.js app provider than just routing. A hook may be a but limited in that sense?
I'm not sure it's a good idea to export the same interfaces from multiple places (barrel filles excluded). We don't do that anywhere, it could become confusing.
I think renaming it to something like AppRouterAppProvider makes quite a lot of sense, it would be analog to the AppRouterCacheProvider we have in @mui/material-nextjs.

we lately created a new project with the toolpad and mistakenly imported the AppProvider from the wrong url, this was vaery hard to find out! each time we navigated between routes in the sidebar the app reloaded instead smoothly navigation

Note: make sure we also solve the confusion in https://github.com/mui/toolpad/pull/4513 with this.

authors: EstherPerelmanCommit Janpot apedroferreira garryxiao

repo: mui/toolpad


text:
$(...).owlCarousel is not a function Error:

Hello,
Using webpack and i get the above error?
In my index.html

I have imported { OwlModule } from 'ng2-owl-carousel'; in my app.module.ts
Then in my component i have imported { OwlCarousel } from 'ng2-owl-carousel';
and finally my HTML
<owl-carousel [options]="{items: 3, dots: false, navigation: false}"
[items]="images"
[carouselClasses]="['owl-theme', 'row', 'sliding']">

</owl-carousel>

Any ideas why its throwing this error

You  don't need to include owl carousel 2 in your index.html file. This package already includes the owl.carousel 2.2.0 (Not Owl Carousel 2) and this issue is fixed in the latest release.
#install latest version
npm install --save ng2-owl-carousel@0.1.7

Thank you this did resolve the issue.

I've only reopened the issue because i'm unsure how to use the options element?
Much like your next function i tried to apply the same logic to add options
@Input() options: Object;
@ViewChild('owlElement') owlElement: OwlCarousel
fun() {
this.owlElement.next([200]);
this.owlElement.options = {
loop: true,
margin: 10,
responsiveClass: true,
responsive: {
0: {
items: 1,
nav: true
},
600: {
items: 3,
nav: false
},
1000: {
items: 7,
nav: true,
loop: false
}
}
};
}
however nothing changes...

After making some change in options you need to call component's refresh method currently Like this:

fun() {

  this.owlElement.next([200]);

  this.owlElement.options = {
    loop: true,
    margin: 10,
    responsiveClass: true,
    responsive: {
      0: {
        items: 1,
        nav: true
      },
      600: {
        items: 3,
        nav: false
      },
      1000: {
        items: 7,
        nav: true,
        loop: false
      }
    }
  };
}

this.owlElement.refresh();

confirmed working
thanks

I have the same issue, after doing some research I have found that owl carousel tries to get initialized at ngAfterViewInit while the carousel-child is NOT STILL LOADED, please keep in mind that I use my app inside a page with high loading time... The problem occurs mostly when I change roots in my application. Any help would be greatly appreciated.

authors: evabat gwsampso mujtaba01


text:
Change the color

Hi, thanks for the library. I want to change the background color from Black, which I'm currently getting to white which is there in the library image currently. How to do that?

to solve this you can use the country picker as a fragment and display it as a dialog fragment

authors: bhargavbvs mukeshsolanki

repo: mukeshsolanki/country-picker-android


text:
Change error-chain to thiserror

Changed error-chain to thiserror, and updated dependencies.
Maybe you would also want to remove error-chain from examples and tests.
Closes #66

This change is

Fixed?

Absolutely everything regarding the internal details of these errors are exposed

Still don't understand why is it bad

Absolutely everything regarding the internal details of these errors are exposed

Still don't understand why it's bad

Again, see https://github.com/mullvad/udp-over-tcp/pull/57. If every aspect of the error is part of the public API then every small "internal" change becomes a breaking change. Let's say we wanted to change InvalidRuleCombination(String), into InvalidRuleCombination(&'static str), for some reason. Because it's part of the public API we now need to release this as a breaking change (0.5.0 instead of 0.4.7). Because otherwise it would break compilation for users who might hypothetically destructure the error and rely on the embedded enum variant type to be a String.
If we don't expose details that a user usually won't ever need to rely on, the API surface both becomes cleaner, and we are freer to change the internals without breaking stuff.

I see the reasoning, but I don't understand why would you lose a part of the error. For InvalidRuleCombination(String), string is the part of the error's display implementation. If you drop it, how would you display it? And also I don't understand why would anybody match and rely on the internal string, if they don't need it. Maybe they actually would need that string? Because that string makes this variant different from the same variant with the different string. It's not as "internal" as you claim.

If that is "internal", but internally we don't use it, maybe we actually don't need it then?

Thanks for wanting to contribute! However, we merged a different solution to this issue over in #107. The main issue in this PR was how the entire API of the error was still public. Part of wanting to get rid of error-chain was that we wanted the API of the errors ta change. A much less public API surface of the errors allows changing the error more without breaking the API.

authors: RoDmitry faern

repo: mullvad/pfctl-rs


text:
Add eth-evm-code codec

This is the binary found in a smart contract account, referenced in ethereum by keccak256(evm_code_binary). It is binary data, which the Ethereum Virtual Machine (EVM) interprets.

This is yet another distinct ethereum format?

@whyrusleeping It is a raw binary. The work around is using 0x55 to reference it. We would like to have a code for meta purposes, i.e. We would know "Oh, this IPLD is an EVM Code"

Hrm... if there isnt any inherent structure to the data, then i really hesitate to add another new code for it.

In general, that's not what CIDs are for. CIDs allow one to interpret unstructured binary into structured data but shouldn't (usually) be used to determine the intended use of the data (unixfs currently does this but it but shouldn't).
For example, we've considered adding a code for webasm but that's because it's an AST, not just raw binary. However, if a user provided a CBOR-encoded webasm AST, an IPLD webasm VM shouldn't care.

I see. I'm short on argumentations, as I am not particularly clear on the overall vision of CID. While the points expressed above makes sense to me, I'd like to get @kumavis feedback, as he is the "end user" of this information.

Basically, IPLD == structured data. CIDs exist to allow us to be compatible with existing merkledags (e.g., eth, git, our own protobuf-based merkledag (used in unixfs), etc.). In general, IPLD does not encode type information beyond basic primitives such as: byte array, array, string, number, float, map, etc... (exact primitives TBD by the end of this week or I start kidnapping people).

yeah theres not a lot of structure to this. you could index it by program counter or op code index (skipping inline data associated with an opcode) but no external links.
but there is value in identifying what the data is "this is evm code"
im indifferent

@diasdavid

Is there a need for this to be "serialized and deserialized"?
Is there any local resolve to happen?

No and no. 😄
Just a little bit of context...
We have eth-account-snapshots. One of their fields is the codeHash (for now, just a keccak256 hash of the actual EVM code this account holds, but wanting it to become a CID, so we can fetch it).
What are we doing now? We are importing this data, making it a "raw" (0x55) elementand hashing it as a "keccak256" (0x1b). One example is zb34VweGrraA5TkNXMLYj1AEUw9GfqsU9ov6PM9QiKjxKFf6J. We already imported 30,261 of these, which are the unique versions of the 1845516  smart contracts of the current mainnet ethereum blockchain (yeah, there is a huge number of dups in there).
So, as @kumavis said, there is value on identifying that this is not just ordinary raw information hashed into keccak256, but actual ethereum smart contract code. I second him, as I see a meta value in figuring out the contents of a cid via its codec, But @Stebalien well argues that CID shouldn`t convey this information. Both arguments make sense to me, therefore I am indiferent.
Do we close this PR then?

@Stebalien is right, CID should not convey that information. That doesn't mean that the metadata information should not exist in the whole data structure. Think of CID such as Content Address + File Extension, the File Extension part lets the IPLD resolver figure out what content it is, how to parse it and traverse through it and that is pretty much it (for now).

All clear. Closing this issue.

authors: Stebalien diasdavid hermanjunge kumavis whyrusleeping

repo: multiformats/multicodec


text:
New logo

short legs logo
favicon for all the platforms
fixed header on mobile
fixed duplicate multiformats in title

Build https://ipfs.io/ipfs/QmS3FaApdKYKxzm2FP4scRBL4RCp1qpELumMcEg9bBdZf4/

New build, now with cards: https://ipfs.io/ipfs/QmTh1f6dkW5f1Z2biRmm6GLjNyAmcsFbNci1xDDQJj98rm/

repo: multiformats/website


text:
platform darwin/arm64 added

Reference Issues/PRs
darwin/arm64 support

@sharjilk Thanks! This isn't correct in terms of both config and yaml syntaxes. So I've submitted a PR to your branch, which can be found at https://github.com/sharjilk/config-registry/pull/1.
Would you mind merging it on your fork? Then this pull request will be automatically updated with the change.

thanks @mumoshu I have merged it. Please merge this PR so I can check it.

authors: mumoshu sharjilk

repo: mumoshu/config-registry


text:
Update Analysis-IG in interest-groups.md

This pull request updates the description for the Analysis-IG as submitted to the Board on 6 May 2024

Thank you, @mss2221


text:
tdslite works on ESP32, but need helps for displaying the queried data.

@mustafakemalgilor I tried tdslite on my ESP32 DeviKitC board, it works well.
However, since I am a newbie for C++, I would need your helps. I used  tdslite/tests/sketches/esp/esp.cpp and modified to accommodate my WiFi SSID/PWD, SQL Server addres/username/password ....
And changed setup() and loop() to have tdslite_loop() run only once.
// --------------------------------------------------------------------------------
void setup() {
    bool r = {false};
    r      = init_serial();
    r      = r && wifi_setup();
    r      = r && tdslite_setup();
    if (not r) {
        SERIAL_PRINTLNF("... setup failed ...");
        for (;;) {
            delay(1000);
        }
    }
    SERIAL_PRINTLNF("--- setup finished ---");

    tdslite_loop();
}

// --------------------------------------------------------------------------------

void loop() {
    // tdslite_loop();
    // delay(250);
}

The Serial output from ESP32 is as below
...
received COLMETADATA token -> column count [3]
row field 0 -> []
row field 1 -> []
row field 2 -> []
row: 1  2       1701998412
received done token -> status [16] | cur_cmd [193] | done_row_count [1]
cc: done token -- affected rows(1)
network_impl_base::do_receive_tds_pdu(...) -> packet_data_cb needs 0 more bytes
netbuf: [consumed 282, inuse 0, free 8192]
netbuf: [consumed 0, inuse 0, free 8192]
'>> Report: row count [1] <<
For the output of "row: 1  2       1701998412", I believe the third column is a pointer printed as uint32. I would like the output be like "row:1 2 Lorem ipsum ...  velit.".
I know I should modify the codes in row_callback(), but as a C++ newbie, I have no idea how to modify the codes
    for (const auto & field : row) {
        SERIAL_PRINTF("%d\t", field.as<tdsl::uint32_t>());
    }

Sorry for the C++ newbie question, your helps would be much appreciated.

Hello @NodeMCU-Kang
You need to access the fields by index and cast them to their respective data type. Assume that you have a table like: CREATE TABLE TEST(a int, b real, c varchar(50)), you can use the following callback to display the rows:
static void row_callback(void * u, const tdsl::tds_colmetadata_token & colmd,
                         const tdsl::tdsl_row & row) {
    SERIAL_PRINTLNF("row: %d %f %s", row[0].as<int>(), row[1].as<float>(), row[2].as<tdsl::char_view>().data());
}

Hi @mustafakemalgilor Thank you very much. The complier complained about "row[0].as<int>()" and "row[1].as<float>()". I changed them to int32_t then it works,
SERIAL_PRINTLNF("row: %d, %d, %s", row[0].as<tdsl::int32_t>(), row[1].as<tdsl::int32_t>(), row[2].as<tdsl::char_view>().data());

authors: NodeMCU-Kang mustafakemalgilor

repo: mustafakemalgilor/tdslite


text:
Riot is not usable from inside web workers

I've discovered that riot can't be used from inside web workers due to init logic on the window object.
It seems to be solved by changing the initializing closure call to use self instead of undefined, like this:
})(typeof window != 'undefined' ? window : self);

But I'm not sure if that breaks something else. The web worker's global scope is always called "self", as far as I'm aware.

could you post an example please?

authors: GianlucaGuarini magwo

repo: muut/riotjs


text:
Invalid signature using the java client

The signature of a message sent by the java client applikation seems to be invalid:

deleted the flawed java client with commit b9b1cf02d03777d0c05563296b20baa2af440dfc


text:
Change Ip

When pressing configure I like to be able to change IP adress for my receiver.

Not sure what is the best way to build and test that, but will take a look at that.

This is now possible with the v7.1.0 release.
The procedure is a bit clumsy, but doing it this way allows me reuse the existing configuration flow and avoid adding a lot of code to maintian and test.

Q: How can I change the connection settings
When the integration can not connect to the receiver (e.g. due to changed IP address) you can use the "Configure" button on the integration card. A dialog appears with a message that it can't connect. Press "Submit" in this dialog to mark the integration for reconfiguration. Home Assistant will now allow you to reconfigure the integration (reload of the page in the browser seems required to show the reconfigure card).

authors: bootstrapbats mvdwetering


text:
String are localized

I've used the build-in NSLocalizedString to localize the displayed string in the entire plugin.

Hi Dennis, I've actually just implemented this myself and I'm about to push it! Thanks for the recommendation.

authors: DennisMadsen mwaterfall

repo: mwaterfall/MWPhotoBrowser