text:
Improve leaderboard UI on mobile

Fixed in 0cb1afc5b596ffa86b3d0f19392b97fd1aa9e824.

source: gharchive/issue

repo: muety/wakapi

license: MIT

license_type: permissive

license_source: github-api


text:
Kadane's Algorithm

Please explain the Kadane's Algorithm along with a suitable example. You can also add links of the questions related to it.

Can I work on this issue? @mugiwara798

Go for it @AshwinSriram11

I have raised a PR @mugiwara798 .Kindly check it.


text:
React.SFC is deprecated

    /**
     * @deprecated as of recent React versions, function components can no
     * longer be considered 'stateless'. Please use `FunctionComponent` instead.
     *
     * @see [React Hooks](https://reactjs.org/docs/hooks-intro.html)
     */
    type SFC<P = {}> = FunctionComponent<P>;

https://github.com/DefinitelyTyped/DefinitelyTyped/blob/a51e3613b44c4ae400d040592bb4f56fd3fa8a4f/types/react/index.d.ts#L528-L534
Here is one example:
https://github.com/mui-org/material-ui-pickers/blob/f8bc7ba4004e3eafe764346b39b882699409818e/lib/src/_shared/PickerToolbar.tsx#L65
The best resolution is probably to follow the definition style of the main repo:
diff --git a/lib/src/views/Calendar/CalendarHeader.tsx b/lib/src/views/Calendar/CalendarHeader.tsx
index 86174f9c..d7a2b96b 100644
--- a/lib/src/views/Calendar/CalendarHeader.tsx
+++ b/lib/src/views/Calendar/CalendarHeader.tsx
@@ -81,7 +81,8 @@ function getSwitchingViewAriaText(view: DatePickerView) {
     : 'calendar view is open, switch to year view';
 }

-export const CalendarHeader: React.SFC<CalendarHeaderProps> = ({
+export function CalendarHeader(props: CalendarHeaderProps) {
+  const = {
   view: currentView,
   views,
   currentMonth: month,
@@ -99,7 +100,7 @@ export const CalendarHeader: React.SFC<CalendarHeaderProps> = ({
   leftArrowButtonText = 'previous month',
   rightArrowButtonText = 'next month',
   getViewSwitchingButtonText = getSwitchingViewAriaText,
-}) => {
+} = props;
   const utils = useUtils();
   const classes = useStyles();

Fixed by #2045

authors: dmtrKovalenko oliviertassinari

repo: mui-org/material-ui-pickers


text:
Issue with Preact throwing an error

[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 🤔
No error should be thrown.
Current Behavior 😯
An error is thrown.
Context 🔦
https://github.com/developit/preact/issues/1293

No error should be thrown.No error should be thrown.

It should. We declared it in our public API: https://material-ui.com/api/modal/#props
Does preact not validate propTypes? Please include the code that triggered this error.

Given the discussion on preact side, I think that it's safe to close the issue. It would be great to add an example with preact.

authors: eps1lon oliviertassinari roberthmiller

repo: mui-org/material-ui


text:
Square prop makes no effect on Alert components

[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 😯
<Alert> components accept props from <Paper> but can't seem to get a squared alert passing the square prop or overriding borderRadius from the sx prop.

Expected Behavior 🤔
<Alert> should override the border radius when square is passed as prop.

Steps to Reproduce 🕹
Simply add the square prop to an <Alert> component.

A Codepen example illustrating this issue can be found here.

Your Environment 🌎

`npx @mui/envinfo`
  System:
    OS: macOS 11.4
  Binaries:
    Node: 14.16.0 - ~/.nvm/versions/node/v14.16.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.11 - ~/.nvm/versions/node/v14.16.0/bin/npm
  Browsers:
    Chrome: 92.0.4515.159
    Edge: Not Found
    Firefox: Not Found
    Safari: 14.1.1
  npmPackages:
    @emotion/react: ^11.4.1 => 11.4.1
    @emotion/styled: ^11.3.0 => 11.3.0
    @mui/codemod:  5.0.0-rc.0
    @mui/core:  5.0.0-alpha.45
    @mui/docs:  5.0.0-rc.0
    @mui/envinfo:  2.0.0
    @mui/icons-material:  5.0.0-rc.0
    @mui/lab:  5.0.0-alpha.45
    @mui/markdown:  5.0.0
    @mui/material:  5.0.0-rc.0
    @mui/private-theming:  5.0.0-rc.0
    @mui/styled-engine:  5.0.0-rc.0
    @mui/styled-engine-sc:  5.0.0-rc.0
    @mui/styles:  5.0.0-rc.0
    @mui/system:  5.0.0-rc.0
    @mui/types:  7.0.0-rc.0
    @mui/utils:  5.0.0-rc.0
    @types/react: ^17.0.19 => 17.0.19
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    styled-components:  5.3.0
    typescript: ^4.4.2 => 4.4.2

need to find out why Alert inherits Paper (only to get elevation styles?) and continue on that
for now, you can theme Alert to affect global or use sx prop for specific location.

@siriwatknp note that setting the borderRadius doesn't work on the sx prop as well. It works however if it is set as '0 px'. Something is off here - https://codepen.io/mnajdova/pen/MWobXbW

The reason why the Paper's square prop is not working is because the Alert is setting the borderRadius without any condition https://github.com/mui-org/material-ui/blob/next/packages/mui-material/src/Alert/Alert.js#L50
We can drop this line:
index e37f174d4c..161a974fad 100644
--- a/packages/mui-material/src/Alert/Alert.js
+++ b/packages/mui-material/src/Alert/Alert.js
@@ -47,7 +47,6 @@ const AlertRoot = styled(Paper, {

   return {
     ...theme.typography.body2,
-    borderRadius: theme.shape.borderRadius,
     backgroundColor: 'transparent',
     display: 'flex',
     padding: '6px 16px',

Thanks everyone. To your point @siriwatknp, I don't think the motivation was to get the elevation from <Paper/> as it seems to be overridden too 🤷♂

Thanks everyone. To your point @siriwatknp, I don't think the motivation was to get the elevation from <Paper/> as it seems to be overridden too 🤷♂

the elevation works currently. https://codesandbox.io/s/eager-wildflower-rwrc2?file=/src/App.tsx
<Alert elevation={4}>

@siriwatknp note that setting the borderRadius doesn't work on the sx prop as well

Is it a bug on sx side? if string works, I also expect the number to work. Or I misunderstood something here?
<Alert sx={{ borderRadius: 0 }}>

diff --git a/packages/material-ui-system/src/borders.js b/packages/material-ui-system/src/borders.js
index 9e7d223993..201bc96a1f 100644
--- a/packages/material-ui-system/src/borders.js
+++ b/packages/material-ui-system/src/borders.js
@@ -68,7 +68,7 @@ export const borderLeftColor = style({
 });

 export const borderRadius = (props) => {
-  if (props.borderRadius) {
+  if (props.borderRadius !== undefined || props.borderRadius !== null) {
     const transformer = createUnaryUnit(props.theme, 'shape.borderRadius', 4, 'borderRadius');
     const styleFromPropValue = (propValue) => ({
       borderRadius: getValue(transformer, propValue),

@mnajdova I think it is a bug.

Great job folks! Thanks for solving this issue so quickly 👍

authors: m-ocana mnajdova siriwatknp


text:
createStyles return never type

[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 😯
import { createStyles, makeStyles, Theme } from "@mui/material/styles";

const useStyles = makeStyles((theme: Theme) =>
  createStyles({
    circularProgress: {
      position: 'absolute',
      top: theme.spacing(14),
      left: '50%',
      transform: 'translateX(-50%)'
    },

    circularProgressCentered: {
      position: 'absolute',
      top: '50%',
      left: '50%',
      transform: 'translate(-50%, -50%)',
    }
  })
);

useStyles has never type.
Expected Behavior 🤔
useStyles has valid type for hook
Steps to Reproduce 🕹

Use my code example
Context 🔦

Your Environment 🌎

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

You should use the createStyles from @mui/styles. Take a look on https://mui.com/guides/migration-v4/#styles


text:
Update flow-type lib defs

Closes #11106

@prastut Thank you!

source: gharchive/pull-request

authors: oliviertassinari prastut


text:
[website] Refactor page context with next router

The issue is I got unexpected error when copy installation page to docs/pages/material/getting-started/installation (it should not throw error).
The error occurs in AppTableOfContent because there is no active page. However, it does not make sense that the AppTableOfContent should know about the active page. Instead, it should just read the browser URL (provided by nextjs) and apply a hash to the URL when clicked.
I feel that this is simpler and easier to maintain, so open this small PR to check that I don't miss anything important.

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

@oliviertassinari Do you see anything that I might be missing?

Actually, I can see why docs/src/modules/components/AppTableOfContents.js makes sense in isolation. It's more flexible. For the change docs/src/modules/components/Link.tsx I don't follow the reasoning. I would expect the pathname to never include the language, so the extra check to be a topology.

For the change docs/src/modules/components/Link.tsx I don't follow the reasoning. I would expect the pathname to never include the language, so the extra check to be a topology.

@oliviertassinari The change is correct because in AppTOC, the href use router.asPath (the URL) so it can contain $user_language/*. It makes sense for the Link to consider this case so other component does not need to think about languages.

@mnajdova Could you review this PR? thanks 🙏

authors: oliviertassinari siriwatknp


text:
[TimePicker] Min/max is not respected if it doesn't have a default value

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
the time range min/max isn't respected for a  Time component that has the value = null;
it's only after first selected a time that the time range is respected.
https://stackblitz.com/edit/react-ix5es1?file=demo.tsx
Expected behavior 🤔
should always respect the min/max
Steps to reproduce 🕹
Steps:

https://stackblitz.com/edit/react-ix5es1?file=demo.tsx
click to add time
you will see you it displays all the time options and not limited to the min/max

Context 🔦
No response
Your environment 🌎

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

I am having the same problem, datepicker is still working well

authors: lechiduc spaceexperiment

repo: mui/material-ui


text:
Is there a way to have horizontal scroll similar to Tabs but on Cards?

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Steps:

Current behavior 😯
No response
Expected behavior 🤔
Is there a way to have horizontal scroll similar to Tabs but on Cards?
I tried using Tabs just for the beautiful scroll + scrollButtons, But Tabs do not take anything else as child (or throw random errors difficult to fix)
Context 🔦
No response
Your environment 🌎

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

Can you maybe share what you are trying to build. It's not really clear what the horizontal scroll should do. Is it about componsing cards? Are you referring to the content of the card?

I just wanted a horizontal carousel for cards

authors: mnajdova nandeshwarshubh


text:
Issues in MUI build access [question]

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

The problem in depth 🔍
I am creating the build file of my project in which I have used MUI, and then I am serving this build file onto my local machine, and I have also used one library called as react-to-webcomponent which creates a custom web component to be accessible in any HTML file as a normal tag. Then I am getting an issue " MUI: Unsupported `` color. The following formats are supported: #nnn, #nnnnnn, rgb(), rgba(), hsl(), hsla(), color().". Please help me in debugging this.
Your environment 🌎

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

@paramsurgeryclinic Can you provide some kind of reproduction for the issue?
(Here are some tips: https://stackoverflow.com/help/mcve)


text:
On mobile pull refresh ui screen render multiple time showing same ui multiple time in react material ui

On mobile pull refresh ui screen render multiple time showing same ui multiple time.
Find many solution but not working.
desktop working find but in mobile ui break multiple time.
any solution please let me know.
Search keywords:

@vaishaligour2016 Can you please explain more or add a reference for the above issue.

@KumarNitin19
when we refresh in mobile view same ui getting multiple time in every screen. not able to understand why it getting multiple time in some mobile phone.
I think this may be css issue.
using "@mui/material": "^5.14.9",
"react-router-dom": "^6.22.1",


text:
Autocomplete with limitTags, the dropdown disappears weirdly

Steps to reproduce
Link to live example: (required)
https://mui.com/material-ui/react-autocomplete/#:~:text=You can use the,Forrest Gump
Steps:

Place your cursor over the "favourites" placeholder
Hold down click
After a second release

Current behavior
The drop down disappears when on mouse up. Resulting in a sudden flash of the dropdown if navigating normally. If you keep the mouse down, then place the cursor back over the input box (or outside of the autocomplete comp), the drop down box doesn't disappear.
This issue only occurs if the input text has to move down a row due to the occupying chips.
Expected behavior
One click should prompt the drop down menu to appear.
Context
No response
Your environment
No response
Search keywords: Autocomplete, limitTags

Duplicate of #42432

authors: ZeeshanTamboli tajbowness


text:
[joy-ui][FormLabel] Add undefined checks for htmlFor and id attributes

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

Hey @ReaZzy,
I have a few suggestions, your PR currently lacks a description. To help the reviewers understand the changes you've made, could you please add a brief description that outlines the purpose of the PR, any proposed changes, and if applicable, mention if you've added or modified tests.
Additionally, as this PR addresses a specific issue, you can link it by adding Closes: #40112 in your description to link this PR to the original issue. This helps in tracking and closing the associated issue once the PR is merged.
Thanks for your contribution! A member of the team will review your PR soon.

authors: DarhkVoyd ReaZzy


text:
Which name is correct ng2-owl-carousel or angular-owl-carousel?

On the npm page I see:
npm install ng2-owl-carousel --save

But inside github I see:
import { OwlModule } from 'angular-owl-carousel';

ng2-owl-carousel is the only one that works... so... but you're correct the documentation is probably outdated... ie based on angular

authors: AlexanderKozhevin Serjster

license: mit

license_source: bigquery


text:
Actor bindings architecture

The actor bindings open new ways of building bots; FSM actors will greatly simplify the creation of stateful workflows leveraging over a widely known and used model (FSM Actors).
Actor bindings can be added by mixing ActorDispatcher.
Here's an example of a very simple per-chat dispatcher:
Per-chat actor dispatcher
The purpose of this issue is to agree on a general design for a more powerful abstraction.
Possibly including:

FSM
Expiring actors
State management and persistency

@zifeo PTAL

Looks good! A few ideas/comments unordered:

might the name dispatcher be confused with the system dispatcher?
should be clear whether the availability of other commands changes when a worker is active for a given channel?
would the broker example be included in the lib?

authors: mukel zifeo


text:
Feature: flex gateway registrations

We are currently automating deployment for lots of Flex Gateways, in Kubernetes.
We do so using a mix of Terraform and Helm Charts.
As we are looking into automating registrations, currently the "best" approach may just be to use some "null_resource", so that I can execute some flexctl commands in Terraform ... then somehow store the resulting file into our parameter store ... in our case using some aws / ssm with kms encryption ... All from my null_resource.
This is not ideal.
I found about that terraform provider here ... Sounds pretty nice ...
but all I can see is some data, fetching registration tokens?
In my case, I have some client-id/client-secret/oidc-lookalike credentials, ... Isn't there a way to generate a registration out of those?
Would be nice to have here.

@faust64
The registration process is a one time action similar to getting a token. so the most suitable would be to develop a datasource.
However, since the registration process relies on the CLI, we would need to reverse engineer the process... not ideal in this case, since it would require a bigger effort for maintenance.
This project is an open source initiative aiming to provide the community something reliable and that can be maintained fairly easily :)
On the other hand, what you can eventually do is to create a terraform module that you can execute when you need to. The module will use the data source to get the token and then you can create execute the registration command using some virtual machine or a docker image that you execute to:
A - Create the registration file
B - Copy the registration file to a bucket, vault or something
Having this in a terraform module, will allow you to destroy the virtual machine or whatever resource you've used to host the registration process.
This how I would do it. Good luck.
Thanks for using this tool.


text:
Broken link to the code repository

Hi,
I was going through "custom-response-policy-example.adoc" and found a broken link to the code repository:
https://github.com/mulesoft/api-gateway-custom-policies-examples
I would like to know proper repository link.
Thanks

Hello,
Thanks so much for bringing this to our attention. Unfortunately, the linked GitHub repository is no longer public, and another repository hasn't been made available.
I'll submit a documentation PR that removes the line containing the broken link.
Thank you again.
Regards,
Chris Campbell

repo: mulesoft/docs-api-manager


text:
Update apply-oauth-token-policy-task.adoc

typos

Closing as PR is no longer relevant.

authors: glenn-rodgers-sf jmjdamen


text:
建议：默认头像能不能换成名字首写字母or汉字或者用qq头像，磨人的太丑了

或者教我怎么换也行(￣3￣)

解决了，用了个插件就可以了，我改了一下头像源，可以直接拿来用，可以获取qq头像，可以设置默认头像风格（每个人都不一样）。插件：https://github.com/shuaiplus/GravatarServer

会不会有暴露对方qq号的风险

我觉得不会暴露把

加密了，那可以，这个插件我回头丢使用文档里去

我的小恐龙为啥不跑了？挂了代理也不跑

按空格呀，你网站发来我看看

按空格呀，你网站发来我看看

没认真看提示，my bad

我找泽泽了解了下最新的做法，目前新用法已更新到使用文档了，你可以查看头像换源那篇了解一下，比你这个插件省事多了

牛啊，其实我想找的就是这种，接口里自带qq头像的，辛苦了

authors: mulingyuer shuaiplus


text:
Simplify & introduce versioning

This PR simplifies the build process, and introduces git-tag-based versions to Docker tags.
Most specifically, each successful GIT TAG build results in Docker deployment that pushes two Docker tags for each built image:

one moving, that is updated with each new passing build, ex. :latest, :register, or :arm, and
one version-specific, that will never change, ex :v4.0.0-5, :register-v4.0.0-5, or :arm-v4.0.0-5.

Other changes:

Github release deployment now happens using native deploy mechanism,
Docker push happens only if build was triggered by pushing a git tag,
All x86_64_ prefixes are stripped since, as of now it's the only supported architecture anyway,
Triggering build of a new version is as simple as this, namely:

Adjust URL in .travis.yml file to point to the newest qemu release

Commit said line change, ex:
git add .travis.yml
git commit -m 'qemu version bumped to X'

Tag & push, ex:
git tag -sa v4.0.0-5 -m "v4.0.0-5"
git push origin v4.0.0-5

Wait :)

Travis needs to be configured with DOCKER_USER, and DOCKER_PASS environment variables.

Github deployment
Note, since I don't have write rights to this repository, api_key used here needs to be regenerated by someone who does have access :).  The easiest way I've found to do it so far is:
cd qemu-user-static/
travis setup releases --com

Unfortunately, running this command has a nasty habit of changing .yml file a bit more than necessary, so I advice just copying the encrypted API key from there, and pasting it to the restored file.
Outcomes
You can see how successful releases & Github uploads look like here: https://github.com/meeDamian/qemu-user-static/releases .
All Docker tags pushed during Travis builds can be found here: https://hub.docker.com/r/meedamian/qemu-user-static/tags
Happy to hear feedback.  The issue that inspired me to get to it was https://github.com/multiarch/qemu-user-static/issues/74 .

I've noticed you use travis-ci.org, as opposed to travis-ci.com, in which case the --com flag to the travis setup command should not be used :).

Hi @meeDamian , I really appreciate your contribution!
Yes, the versioning is very important feature with high priority for this project.
I proposed the feature at below ticket too.
https://github.com/multiarch/qemu-user-static/issues/74#issuecomment-515768341
I will take a look at your code later.
But please be patient as I will be in vacation next week. :)
Thank you!

I've noticed you use travis-ci.org, as opposed to travis-ci.com, in which case the --com flag to the travis setup command should not be used :).

Yes "travis-ci.org" is used for a free Travis CI plan. Open source project use it. "travis-ci.com" is for non-free Travis CI. :)

In a mean time, is it possible to do squash current 9 commits to 1 commit by git rebase -i <commit hash> and etc to make the code review easier?

I had the commits so that I could generate git tags for qemu versions, trigger and reference Travis builds, and docker hub tags.
That being said, I've moved them to another branch and squashed in this one :).

Note that the most recent build overrides all floating Docker tags, so it's best to push said tags in strictly increasing order.

@moul Wow, thanks for the quick review. :) Could you give me a short time for my review?

yep sure, I was mostly approving the overall approach, I may have miss some details, take the time you need :)

@moul Thanks.
@meeDamian Your approach to simplify is amazing! Thank you.
Let's me comment on one by one.
First about a big picture.
Image tag version format

one version-specific, that will never change, ex :v4.0.0-5, :register-v4.0.0-5, or :arm-v4.0.0-5

I would prefer "ex :v4.0, :register-v4.0, or :arm-v4.0" than "ex :v4.0.0-5, :register-v4.0.0-5, or :arm-v4.0.0-5".
Because

Reason 1: I want to consider to align with our sister project: https://github.com/dbhi/qus (DockerHub: https://hub.docker.com/r/aptman/qus/tags) with a balancing.
In aptman/qus, the tag is f4.0.0 (from fedora qemu) or d3.1 without a qemu package release number.
Reason 2: To save the number of containers as our project's small start.

That means below kind of logic to replace v3.1.0-3 with v3.1 or v4.0.0 with v4.0 is needed at early step.
TAG_VERSION=$(echo  ${TRAVIS_TAG} | sed 's/something/something/')

Pipeline to rerun already git tagged version
While the pipeline based on TRAVIS_TAG is great, the pipeline can be failed because of some issue.
And maybe we also want to run old tag's pipeline to upload old qemu version's tag.
That means below kind of logic might be useful.
TAG_VERSION=${TAG_VERSION-TRAVIS_TAG}

When people want to rerun or run for old qemu version, we can set like this in .travis.yml.
ADHOC_TAG=v3.1.0-3
TAG_VERSION=${ADHOC_TAG:-TRAVIS_TAG}

In that case, the deploy condition might be like this.
  - name: deploy
    if: tag IS present OR <ADHOC_TAG is not empty>

x86_64 prefix

All x86_64_ prefixes are stripped since, as of now it's the only supported architecture anyway,

I disagree for this change. Please keep the prefix.
https://github.com/multiarch/qemu-user-static/releases
We have already released the x86_64 prefix tar.gz x86_64_qemu-aarch64-static.tar.gz.
Changing the prefix breaks backward compatibility.
Users are confused as a possibility.
x86_64 prefix is to implement new host arch's container images or tar.gz on GitHub releases.
Now only x86_64 are supported. It's for future's preparation.
Now we are trying to implement other arch host's images and tar.gz files, that are aarch64, s390x prefix and etc.
https://github.com/multiarch/qemu-user-static/issues/77
I like that below .gitignore modification is reverted.
-/containers/x86_64_qemu-*/
+/containers/qemu-*/

Detail
I comment it on the line.

I think we do not include TRAVIS_TAG and TRAVIS_REPO_SLUG variables in '*.sh".
Because we (at least me) want to run the shell scripts on my local environment.
If you keep below variables, it is possible not to use the TRAVIS-* in .*.sh.
-    global:
-        - VERSION=4.0.0-5
-        # See qemu-user-static's RPM spec file on Fedora to check the new version.
-        # https://src.fedoraproject.org/rpms/qemu/blob/master/f/qemu.spec
-        - DOCKER_SERVER=docker.io
-        # - DOCKER_SERVER=quay.io
-        # Git repository
-        - REPO=multiarch/qemu-user-static
-        # Container repository
-        - DOCKER_REPO=$DOCKER_SERVER/multiarch/qemu-user-static
-        # - DOCKER_REPO=$DOCKER_SERVER/your_username/qemu-user-static
-        - PACKAGE_URI="https://kojipkgs.fedoraproject.org/packages/qemu/4.0.0/5.fc31/x86_64/q
emu-user-static-4.0.0-5.fc31.x86_64.rpm"
-        - PACKAGE_FILENAME=$(basename "$PACKAGE_URI")

Keep docker images that is after building containers on local.
That's useful to check actual created containers with tags.

Travis needs to be configured with DOCKER_USER, and DOCKER_PASS environment variables.

We are already running with DOCKER_PASSWORD in this repository.
I do not think it is necessary change for this PR.

Sorry @meeDamian I sent another PR to implement versioning with minimal steps.
https://github.com/multiarch/qemu-user-static/pull/84
I think you want to see it is implemented soon.
But I think we need more time to accomplish this PR.
After https://github.com/multiarch/qemu-user-static/pull/84 is merged, I want to see this PR focusing "simplifies the build process".
Thank you for your understanding.

Image tag version format

one version-specific, that will never change, ex :v4.0.0-5, :register-v4.0.0-5, or :arm-v4.0.0-5

I would prefer "ex :v4.0, :register-v4.0, or :arm-v4.0" than "ex :v4.0.0-5, :register-v4.0.0-5, or :arm-v4.0.0-5".
Because

Reason 1: I want to consider to align with our sister project: dbhi/qus (DockerHub: hub.docker.com/r/aptman/qus/tags) with a balancing.
In aptman/qus, the tag is f4.0.0 (from fedora qemu) or d3.1 without a qemu package release number.
Reason 2: To save the number of containers as our project's small start.

That means below kind of logic to replace v3.1.0-3 with v3.1 or v4.0.0 with v4.0 is needed at early step.
TAG_VERSION=$(echo  ${TRAVIS_TAG} | sed 's/something/something/')

The issue with that is that my original problem would remain unsolved with this approach:  v4.0.0-5 didn't work work me, but v4.0.0-4 did.
What I can do, is to add an extra floating vMAJOR-MINOR tag that always points to the latest MINOR version.  It's a very common practice in Docker, because that gives one the flexibility to use a specific version, as well as stay always-up-to-date stay on a chosen minor version.

Pipeline to rerun already git tagged version
While the pipeline based on TRAVIS_TAG is great, the pipeline can be failed because of some issue.
And maybe we also want to run old tag's pipeline to upload old qemu version's tag.
That means below kind of logic might be useful.
TAG_VERSION=${TAG_VERSION-TRAVIS_TAG}

When people want to rerun or run for old qemu version, we can set like this in .travis.yml.
ADHOC_TAG=v3.1.0-3
TAG_VERSION=${ADHOC_TAG:-TRAVIS_TAG}

In that case, the deploy condition might be like this.
  - name: deploy
    if: tag IS present OR <ADHOC_TAG is not empty>

I think there are several issues with that, that would necessitate adding firther complexity, ex:  What to do with github release uploads?  If there's no git tag, there's no place for them to go.
Also, I like the consistency of github tags corresponding directly to releases, and docker version tags.  Keep in mind that changing binary version is now literally a single line change in the .travis.yml file.
Namely, if you do what I did with bump qemu… commits here: https://github.com/meeDamian/qemu-user-static/commits/simplify-with-tags tag them all approriately, and push all tags - everything will fall in place nicely.

x86_64 prefix

All x86_64_ prefixes are stripped since, as of now it's the only supported architecture anyway,

I disagree for this change. Please keep the prefix.
multiarch/qemu-user-static/releases
We have already released the x86_64 prefix tar.gz x86_64_qemu-aarch64-static.tar.gz.
Changing the prefix breaks backward compatibility.
Users are confused as a possibility.
x86_64 prefix is to implement new host arch's container images or tar.gz on GitHub releases.
Now only x86_64 are supported. It's for future's preparation.
Now we are trying to implement other arch host's images and tar.gz files, that are aarch64, s390x prefix and etc.
#77
I like that below .gitignore modification is reverted.
-/containers/x86_64_qemu-*/
+/containers/qemu-*/

Ok, no problem :)

I think we do not include TRAVIS_TAG and TRAVIS_REPO_SLUG variables in '*.sh".
Because we (at least me) want to run the shell scripts on my local environment.
If you keep below variables, it is possible not to use the TRAVIS-* in .*.sh.
-    global:
-        - VERSION=4.0.0-5
-        # See qemu-user-static's RPM spec file on Fedora to check the new version.
-        # https://src.fedoraproject.org/rpms/qemu/blob/master/f/qemu.spec
-        - DOCKER_SERVER=docker.io
-        # - DOCKER_SERVER=quay.io
-        # Git repository
-        - REPO=multiarch/qemu-user-static
-        # Container repository
-        - DOCKER_REPO=$DOCKER_SERVER/multiarch/qemu-user-static
-        # - DOCKER_REPO=$DOCKER_SERVER/your_username/qemu-user-static
-        - PACKAGE_URI="https://kojipkgs.fedoraproject.org/packages/qemu/4.0.0/5.fc31/x86_64/q
emu-user-static-4.0.0-5.fc31.x86_64.rpm"
-        - PACKAGE_FILENAME=$(basename "$PACKAGE_URI")

Keep docker images that is after building containers on local.
That's useful to check actual created containers with tags.

If you run the script with:
TRAVIS_REPO_SLUG=multiarch/qemu-user-static ./test.sh

it should work, that being said I'm happy to add fallback to all TRAVIS_ vars in .sh: ${TRAVIS_REPO_SLUG:-$REPO}, or hardcoded ${TRAVIS_REPO_SLUG:-multiarch/qemu-user-static}.  Main reason I've added TRAVIS_ vars there is because I couldn't get .travis.yml-defined global vars to be available in scripts.

Keep docker images that is after building containers on local.
That's useful to check actual created containers with tags.

👍🏻

Please explain the adhoc pipeline more to me.

Ah could you also explain the :register image to me?  It's not exactly clear what it does, or what it is useful for to me, thank you :).

I think I've addressed most issues, but I would still like to know what exactly you want to achieve with the adhoc pipeline?

I used "adhoc pipeline" means the one without "git" tagging", and  same with "Pipeline to rerun already git tagged version".

You can do that from Travis's interface, can't you?

You can do that from Travis's interface, can't you?

For rerun, it is possible from Travis interface.
But it is not enough when running past tagged qemu version with latest fixes and features.
The scenario of commits is

Run pipeline with version A.
Add commit to fix to a bug.
Add commit to add new feature
Run pipeline with version B.
Then rerun pipeline with version A with above fix and the new feature.

Thank you, that makes it clearer :).
The only question I have is wouldn't that warrant a new git tag?  Either an extra one, or previous one changed to point to the correct source version.  Otherwise you have a case where containers shipped, are not what the source code would claim they are.
To use your scenario:

Run pipeline with version A (say v4.0.0).
Add commit to fix to a bug.
Add commit to add new feature
Create a new git tag

Either something along the lines of v4.0.0-bugfix-1, if you want previous version to be preserved as well, or
delete previous tag, and create it anew for the now fixed, and correct source

Run pipeline with version B.
Then rerun pipeline with version A with above fix and the new feature. Push the tag

The issue with that, in both approaches, is that build A would overwrite the floating tags, even if version B is newer.  I reckon the easiest way to address that would be to:

Each fix commit of this nature, would also add BUGFIXBUILD=true in .travis.yml, which would prevent overwriting of any floating tags, or
Before each bugfix build said variable is added to build config variables in Travis's interface.

In both cases the variable needs to be removed after the build.

Ah could you also explain the :register image to me? It's not exactly clear what it does, or what it is useful for to me, thank you :).

It's only to add binfmt_misc files with "flags: " (empty).
binfmt_misc file is a special file, that is a Linux kernel feature. The benefit of the file is people can run arch specific binary (= arch container) without specifying the qemu interpreter file (qemu-$arch-static file).
The register image was the only way to run arch container until a few weeks ago, until "mutlarch/qemu-user-static" (latest) was released.
I think still many people using the register image.
And I can imagine register image is preferred than "mutlarch/qemu-user-static" in some case for people who wants to create the minimal resourced (memory and disk size) container image.

Thank you for your contributing. Let me close this big PR at once.

Long overdue :).  Sorry I haven't closed it before myself - I forgot.

authors: junaruga meeDamian moul

repo: multiarch/qemu-user-static


text:
promer script fails on test data.

I am running the following command on some of the recommended data files and I get an error postpro part of the promer script. Here is the command line and output. Not sure how to go about debugging it. Obviously, the query file is being parsed in the previous by the prepro and mummer programs. Any suggestion on what the issue is would be helpful:
$ promer D_melanogaster_2Rslice.fasta D_pseudoobscura_contigs.fasta
1: PREPARING DATA
2,3: RUNNING mummer AND CREATING CLUSTERS
4: FINISHING DATA
3210101
ERROR: Could not parse input from 'Query File'.
Please check the filename and format, or file a bug report
ERROR: postpro returned non-zero
Shekars-MacBook-Pro:test shekar$ promer
USAGE: promer  [options]
Try '/usr/local/bin/promer -h' for more information.
The intermediate files that are generated is as follows:
$ ls
D_melanogaster_2Rslice.fasta	out.aaqry			out.delta
D_pseudoobscura_contigs.fasta	out.aaref			out.mgaps
Thanks.

Please read my comment in [(https://github.com/mummer4/mummer/issues/55)]. Hope it would help.

authors: jerviedog shekarm


text:
Add Events history time setting

Adds ability to set time for how far back events are displayed from.

The events module moved here: https://github.com/munkireport/event

authors: bochoven rfitzwater

repo: munkireport/munkireport-php


text:
Remove commented-out code and hints.

Breaking change

Proposed change

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] I have followed the perfect PR recommendations
[ ] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
[ ] Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

[ ] I have reviewed two other open pull requests in this repository.

Motivation: Removing commented-out code and hints is considered a good practice in software development. I deleted them to improve the maintainability and understandability.

changed code does not match the motivation

authors: fatemeshbth munterkalmsteiner

repo: munterkalmsteiner/core


text:
Feature Request: Disable Auto-Diff

Every time I try to Diff large files, as soon as I make a change, the package auto-diffs again, sometimes it takes even a few minutes.
I would like an option / command to stop auto-diff and to diff again whenever I want.
Thanks :)

I totally agree, this would be a fantastic feature. Closing as this is a duplicate of #139, but your request has absolutely been heard.

authors: DiegoLpVn mupchrch

repo: mupchrch/split-diff


text:
Any chance of getting a Naked Mode?

S-expressions don't have to be as verbose as they usually are. Example 1, example 2, example 3. Basically the insight is indentation and line breaks make most parens unnecessary, and inferring them in a lot of cases can be done unobtrusively. I also like my Termpose's pairing operator :3 a:b → (a b), quite a lot of structures benefit from it.

Not likely.
I know there are endless jokes about copious parentheses in Lisp, but I'm not convinced that it's a serious issue when reading or writing code. Naked syntax has its share of drawbacks, too. Some of these are noted in your second link. Another drawback is complexity of parser code.
As for pairing syntax, the form :foo is already in use for keyword values.

@makoConstruct it shouldn't be too difficult to translate "naked mode" to s-expressions by reading reading with sweet-expressions enabled, and printing using the normal common lisp printer, you could write one yourself (if there are not already, are there?). Or maybe more efficient: parse directly into ketos lists, using a function defined in ketos

authors: makoConstruct murarth porky11

repo: murarth/ketos


text:
代码提交的安全扫描关不了，关闭之后重新打开又选上了，如果是BUG请解决一下

感谢您的反馈，关闭之后重新打开是插件BUG，我们会在最近的插件升级版本中解决掉

authors: CN-You YunlongChen


text:
Stream error and "no attribute 'decode'"

I can't play anything from Spotify. My Google speakers pling as if they're ready, and then nothing. The process icon keeps spinning for a while and then everything stops. I have tried all of my 8 Nest speakers.
I get the following errors:
Stream error on spotify://track/************
Job [Analyze audio for ProviderType.SPOTIFY://track/*************] failed with error 'NoneType' object has no attribute 'decode'.
Error executing service: <ServiceCall media_player.play_media (c:0180cbfc99f4695aec51c265dc80501f): entity_id=['media_player.stuen_hoyttaler'], extra=enqueue=True, media_type=music, media_id=http://192.168.86.45:8095/media_player.stuen_hoyttaler.flac, enqueue=True>
In the last error, there's a reference to FLAC. Could there be something wrong with the decoder vs Spotify's file type?
***** = tracks

Strange, Google cast platform should work rock solid with this integration.
Can you tell me a little bit about your Home Assistant setup ? What installation type hardware etc...
Are you running version 1.1.3 of the integration ?
Music Assistant internally works with PCM audio (so it decodes ogg vorbis) to do volume normalization, crossfading, gapless etc. The audio sent to the player is a long stream of the queue tracks, encoded as flac (instead of the raw pcm) to save bandwidth. So that's where the reference to FLAC comes from. In your setup the whole decode from Spotify seems to be failing, hence my questions about your setup.

I am also seeing this on version 1.1.18 on HASS core-2022.5.5, installed on Home Assistant OS (OVA) with HACS.
System Health

version
core-2022.5.5

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.9.9

os_name
Linux

os_version
5.15.41

arch
x86_64

timezone
Europe/Copenhagen

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4635

Installed Version
1.25.2

Stage
running

Available Repositories
1129

Downloaded Repositories
28

Home Assistant Cloud

logged_in
true

subscription_expiration
May 28, 2022, 2:00 AM

relayer_connected
true

remote_enabled
true

remote_connected
true

alexa_enabled
false

google_enabled
true

remote_server
eu-west-2-0.ui.nabu.casa

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 8.1

update_channel
stable

supervisor_version
supervisor-2022.05.3

docker_version
20.10.14

disk_total
20.0 GB

disk_used
11.3 GB

healthy
true

supported
true

board
ova

supervisor_api
ok

version_api
ok

installed_addons
Check Home Assistant configuration (3.10.0), File editor (5.3.3), Genie (3.0.0), ZeroTier One (0.13.3), Node-RED (11.1.2), AirCast (3.3.0), SSH & Web Terminal (10.1.3), Nginx Proxy Manager (0.11.0), AppDaemon (0.8.2), MariaDB (2.4.0), Samba share (9.6.1), ESPHome (2022.3.1), Zigbee2mqtt (1.25.1-1)

Dashboards

dashboards
4

resources
14

views
11

mode
storage

Spotify

api_endpoint_reachable
ok

@ullebe1 what do you experience exactly ?
Please describe step by step what you did...
Please be aware that port 8095 needs to be reachable between your media player and HA

@marcelveldt Steps to replicate the problem shown below. I have the Cast devices and the VM running Home Assistant OS on the same network with no firewalling in between. Do I need to do anything on the Home Assistant OS side to open the port?
Installation and setup:

Install with HACS
Add as integration in HASS

Set up Spotify as only account
Leave everything else at defaults

Kodi is only media player found in the next screen, not setting room
Observe that the rest of my players are added when refreshing integrations page

Use:

Open Music Assistant pane
Select playback device (single Google/Nest Home or a speaker group)
Select an album
Press play
Press play now
Hear cast device say the "pling" sound indicating a connection
First song is shown on bottom bar, but playback doesn't start
Press the play button
Nothing continues to happen
Observe error logs appearing

Logger: music_assistant.mass.stream
Source: /usr/local/lib/python3.9/site-packages/music_assistant/controllers/stream.py:525
First occurred: 7:16:26 PM (22 occurrences)
Last logged: 7:16:52 PM

Stream error on spotify://track/3OfLNqMm0llO3uVi7rH9jf
Stream error on spotify://track/3mnkwuW3cUvpNuG0nw9zFx
Stream error on spotify://track/12Nel1DynDYCV8jwvPRqFn
Stream error on spotify://track/5bnLFoPAVzWaWLfhGYgL8Q
Stream error on spotify://track/6LyawiMzyPI1mbk3GMHjpW

Logger: audio
Source: /usr/local/lib/python3.9/site-packages/music_assistant/helpers/audio.py:172
First occurred: 7:16:26 PM (22 occurrences)
Last logged: 7:16:52 PM

Could not determine integrated loudness of spotify/3OfLNqMm0llO3uVi7rH9jf - received empty value
Could not determine integrated loudness of spotify/3mnkwuW3cUvpNuG0nw9zFx - received empty value
Could not determine integrated loudness of spotify/12Nel1DynDYCV8jwvPRqFn - received empty value
Could not determine integrated loudness of spotify/5bnLFoPAVzWaWLfhGYgL8Q - received empty value
Could not determine integrated loudness of spotify/6LyawiMzyPI1mbk3GMHjpW - received empty value

Logger: homeassistant.core
Source: components/cast/media_player.py:715
First occurred: 7:16:35 PM (5 occurrences)
Last logged: 7:17:15 PM

Error executing service: <ServiceCall media_player.play_media (c:01810684f298c350833f838bc52ce230): entity_id=['media_player.nestmini2383'], extra=, media_type=music, media_id=http://192.168.1.164:8095/media_player.nestmini2383.flac>
Error executing service: <ServiceCall media_player.play_media (c:01810684f4c13a9b0cccc80db6b2fb89): entity_id=['media_player.nestmini2383'], extra=enqueue=True, media_type=music, media_id=http://192.168.1.164:8095/media_player.nestmini2383.flac, enqueue=True>
Error executing service: <ServiceCall media_player.play_media (c:01810684f528f31b4dd86063bbadf27d): entity_id=['media_player.nestmini2383'], extra=enqueue=True, media_type=music, media_id=http://192.168.1.164:8095/media_player.nestmini2383.flac, enqueue=True>
Error executing service: <ServiceCall media_player.play_media (c:01810684f58e629fbef302bda184b0ba): entity_id=['media_player.nestmini2383'], extra=enqueue=True, media_type=music, media_id=http://192.168.1.164:8095/media_player.nestmini2383.flac, enqueue=True>
Error executing service: <ServiceCall media_player.play_media (c:01810684f5f27ab3f74bb5a4fb55093f): entity_id=['media_player.nestmini2383'], extra=enqueue=True, media_type=music, media_id=http://192.168.1.164:8095/media_player.nestmini2383.flac, enqueue=True>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 1645, in catch_exceptions
    await coro_or_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1664, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 677, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 964, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 714, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/cast/media_player.py", line 715, in async_play_media
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.9/site-packages/pychromecast/quick_play.py", line 77, in quick_play
    controller.quick_play(**data)
  File "/usr/local/lib/python3.9/site-packages/pychromecast/controllers/media.py", line 544, in quick_play
    raise PyChromecastError()
pychromecast.error.PyChromecastError

Logger: homeassistant.components.cast.media_player
Source: components/cast/media_player.py:388
Integration: Google Cast (documentation, issues)
First occurred: 7:18:25 PM (1 occurrences)
Last logged: 7:18:25 PM

Failed to cast media http://192.168.1.164:8095/media_player.nestmini2383.flac. Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address

Thanks for the detailled response, that is very helpful!
So it looks like the whole Spotify session fails somehow. Note the "stream error" where there was no audio data received from "librespot", the open source spotify client.
I think that if you try a radio station or local music file it will work.
I'm trying to understand the issue and why it fails. Anything special about your internet connection ?
Just to be sure: You do have a Spotify premium account right? Free accounts will not work.

@kongjudas can you confirm that you have a Spotify premium account ?

@marcelveldt Thanks for looking into it. This component is really cool!
I can confirm that I have a Premium account - it is a family subscription if that makes a difference.
Shouldn't be anything special about the the internet connection. I have an ordinary OPNsense firewall with no special rules. I'm also running an Adguard Home, I'll try to see if there is any logs there indicating something being blocker. Spotify works for both streaming and casting for other devices, so at least in most cases connecting to Spotify isn't a problem.
I'll try adding some local files or a radio station and let you know how that goes.

OK great. Please note that in this case the spotify playback device (=librespot) is actually the Home Assistant device so maybe that is important for your firewall rules ?
If changing the firewall rules has no impact, I'd like to do some more tests together with you to find out the issue.

I've discovered a low level issue today which might have caused the issue mentioned in this issue report. Please give the latest version 2022.6 a testdrive as it might fix it, thanks!

My firewall allows any outgoing connection, so that shouldn't be an issue.
I've also tried disabling my DNS filtering, also didn't help.
I've updated to the newest 2022.6.0b2 but unfortunately my issue wasn't one of the ones that has been fixed.
Is there anything I can do to get more detailed logs or debug information, to help pinpoint the issue?

I have the same problem :(

Hey Marcel. I have now updated, but now i Can not select any speakers (in my case Chrome cast audio)

Click "configure" on the Music Assistant card in "Integrations" and select which players you want to use with Music Assistant. I think that will do the trick.

Please give step by step details of what is not working and details about your setup please:

Home Assistant installation method (HAOS, Supervised, Core)
Hardware running HA e.g. raspberry pi 4, Intel NUC etc)
Type of speaker(s) you are trying to control with Music Assistant
What is the issue exactly ? What did you do and what was the expectation ?
Please share your Home Assistant logfile (homeassistant.log) or any relevant parts from it.

I have HAos installed on a rpi 4, i have a chromecast audio, that plays fine with a internet radio addon in homeassistant.
the problem is, when i Press the little speaker in Music Assistant then there is no options. When i start Spotify and cast it to chromecast and go to media in homeassistant, then i Can se the son and artist just fine.
Shall i send the log file on mail to you ?

There's a small error in the config flow at the moment, you need to manually select the players you want to use with Music Assistant:
Home Assistant settings --> Integrations --> Click "configure" on the Music Assistant card --> select your chromecast players there

I have done that. Its the One Callesen bang Olufsen

@ENGBERG80 I'm not familiar with the B&O device to know if it should support "play url".
Can you play something like a radio stream from the built-in Media panel ?
What integration is used for the B&O streamers ? Is it a predefined standard like DLNA or does it have it's own integration ? Please note that Airplay based devices do still not work with MA due to lack of support in the apple_tv integration

I can confirm this was still an issue on BETA 5, will retest on the stable release.
I also had the same issue as @ENGBERG80 where even after selecting the player entities in the configuration they would fail to show up in Music Assistant. This was however a temporary issue. It lasted at least half an hour, but then I went to sleep and didn't check until next morning where they were present. Unfortunately I was quite busy and didn't have time to fill out a proper bug report.
I'll retest during the weekend to see which of these issues are still actual and then do a proper bug report. I'll probably also be available in the Discord for interactive bug-hunting, if that will help.

See here if you are located in Denmark. A fix is on the way:
https://github.com/music-assistant/hass-music-assistant/issues/352

@marcelveldt I am. That's awesome, thanks! What a weird issue.

Yeah... I was like WTF when I found out that it was specific to Denmark. Appears there is one server unreachable.

Fix available in 2022.6.1

This issue has been solved and Spotify playback works for me, as of 2022.6.1. Thanks for all your work!

Its alive 😃😃😃😃😃 now it would be cool if you could make a script that starts a playlist 👍 i have tried throug HA media but Music assistent does noget work there

Thanks for verifying!

repo: music-assistant/hass-music-assistant


text:
YouTube Music only shows Episodes for Later in playlist (Auto Playlist) instead of my playlists

What version of Music Assistant has the issue?
2.2.7
What version of the Home Assistant Integration have you got installed?
No response
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
YouTube Music only shows Episodes for Later in playlist (Auto Playlist) instead of my playlists.
How to reproduce
Open Music Assistant and click on playlists
Music Providers
YouTube Music
Player Providers
YouTube Music
Full log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2024.10.1
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Alternative

@MarvinSchenkel

Duplicate of https://github.com/music-assistant/hass-music-assistant/issues/2973

authors: MarvinSchenkel OzGav mac-city


text:
Code formatted with ruff

There are still linter errors, for following pull requests/commits

Won't merge, sorry. I'm purposefully avoiding ruff lint/format. The reason is that I first need to add type hints, to avoid formating the whole project two times, which would cause massive line changes. I plan to do that soon, but I need to do other things first regarding the optimizers and TOML configuration formating.
Thanks for sending the PR though.

authors: efonte muslll

repo: muslll/neosr


text:
[Windows] Build error

Hi,
I'm on W10 x64 with node v8.9.4 and yarn v1.5.1.
I tried use this module and I got this error:
 ERROR  Failed to compile with 1 errors                                 17:21:38
This relative module was not found:
* ./C:\Users\derev\AppData\Local\Temp\nuxt-bulma-slim.sass in ./.nuxt/App.js
  nuxt: Call close hooks (2) +4s
  nuxt: server closed +2ms
 OPEN  http://localhost:3000

So...
  modules: [
    '@nuxtjs/pwa',
    [
      'nuxt-bulma-slim',
      {
        sassTempPath: './tmp/nuxt-bulma-slim.sass'
      }
    ]
  ]

I changed my nuxt.config.js to customize sassTempPath and  I got this error too:
 ERROR  Failed to compile with 1 errors                                 17:26:27

 error  in ./tmp/nuxt-bulma-slim.sass

Module build failed:
@import "D:\dev\lenyeg\cruzeirovirtual\node_modules\bulma\bulma.sass"
^
      File to import not found or unreadable: D:Þvlenyeg
                                                        ruzeirovirtualnode_modu
les
      File to import not found or unreadable: D:Þvlenyeg
       ulma.sass.                                       ruzeirovirtualnode_modules
Parent style sheet: stdin                                                         ulma
      in D:\dev\lenyeg\cruzeirovirtual\tmp\nuxt-bulma-slim.sass (line 1, column       ulma.sass.
Parent style sheet: stdin
      in D:\dev\lenyeg\cruzeirovirtual\tmp\nuxt-bulma-slim.sass (line 1, column 1)

 @ ./tmp/nuxt-bulma-slim.sass 4:14-201 13:3-17:5 14:22-209
 @ ./.nuxt/App.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi webpack-hot-middleware/client?name=client&reload=true&timeout=30000&path=/__webpack_hmr ./.nuxt/client.js

 OPEN  http://localhost:3000

Could u help me?

Hey André, thanks for checking out this module. I haven't had a chance to test it on Windows, so lets figure this out.
So with the default value, the leading ./ in the path must be the problem. Seems like the path to the temp .sass isn't treated as an absolute path. Unfortunately I haven't found related Nuxt.js issues. What I can do is to convert the absolute paths back to relatives.
I guess thats also the same problem with the second problem, it can not resolve the absolute path.
So I'll make a fix to only use relative paths. Probably today or tomorrow. Would you help me test it?

i got exactly the same problem !!!

Had the same errors.
Made some small changes in my fork which fix it for me: https://github.com/kfrederix/nuxt-bulma-slim
Also opened a PR.

Merged in @kfrederix code and published version 0.3.1 to NPM. Still works for me on *nix, but still no way to test on a Windows machine. So if anybody runs into problems on Windows, let me know.

authors: derevandal frederic117 kfrederix mustardamus

repo: mustardamus/nuxt-bulma-slim


text:
why the viewController's life cycle function do not execute？

when i change the center viewController, i found the old center viewController's disappear lifecycle function(viewWillDisappear/viewDidDisappear) do not execute ? if i want to stop the timer what can i do？

I have the same issue, I solve it by calling
beginAppearanceTransition(false, animated: true)
on the current VC before calling setCenterViewController

I'm having the same issue but it is for a UIViewController I add as a childViewController on the MMDrawerViewController - have any good work arounds?

authors: amazing-longdd maxx555 rksaraf

repo: mutualmobile/MMDrawerController