text:
Feature request: support .svelte files

Is your feature request related to a problem? Please describe.
When editing a Svelte component, many blocks are not foldable when using Better Folding. They are foldable when Better Folding is disabled.
Specifically, a Svelte component contains zero or more <script> blocks and zero or more <style> blocks as well as normal HTML. It can also contain conditional blocks: {#if condition} … {:else} … {/if}.
Describe the solution you'd like
I'd like it if Better Folding supported Svelte, as this is what I'm mainly developing in. I prefer the way Better Folding folds things when I'm using file formats it supports, but having it not work with Svelte is a bit of a blocker for me…
Describe alternatives you've considered
Currently, I've disabled Better Folding so I can use the Visual Studio Code default folder, which loses the Better Folding improvements, but works with Svelte.
The only other alternative I could think of would be to surround blocks I want to fold with region comments, but this is a bit of a hack (and leads to complaints if any of them get committed, as other devs "don't want IDE-specific stuff in the codebase" 🙄)
Additional context
Changing the extension to .html makes Svelte blocks foldable with Better Folding, so enabling this support for .svelte files would at least let me collapse a long <style> block when I don't need to see it. Adding support for the other Svelte-specific stuff like {#if} … {:else} … {/if} could come later.
With Better Folding disabled:

With Better Folding enabled:

With Better Folding enabled, and the file type changed to .html:

Hey, thanks for making such a detailed issue.
Svelte is definitely on the upcoming supported languages, hopefully soon(ish).
As a temporary fix, did you try adding svelte to the excluded languages list in the settings?

Thanks — I hadn't spotted that setting. That's helped for now 👍

repo: mtbaqer/vscode-better-folding


text:
Missing nontraditional cards

As @KingSupernova31 pointed out in https://github.com/mtgjson/mtgjson4/issues/67#issuecomment-430437889, we are currently missing vanguards, schemes, planes, etc. While not traditional cards, these are Magic cards and should be included.

Contemplating how to go about it. Prob just a custom gatherer scrape. Seems feasible for 4.1

I just checked and vanguards, schemes, planes, phenomena, and conspiracies all seem to be on Scryfall. Only Explorers of Ixalan events, quests, and sites are missing.

cc: @jhallbachner

Ok, so Events, Quests, and Sites are tiles, not cards. As such, I don't plan on indexing them into MTGJSON at this time.

source: gharchive/issue

authors: ZeldaZach fenhl

license: MIT

license_type: permissive

license_source: github-api


text:
Fixed local download path to verify with MD5.

local_file_path is not defined anywhere. Chef fails on first time run. Second run is fine because distribution archive is already there, ruby_block resource is not notified.
Fixed security issue - the second chef run wouldn't check downloaded file vs MD5.

Hi @DmitrySolodovnyk, the md5sum is only checked the first time a release is downloaded, and the sha256 is used by Chef to check whether the remote and local file are the same, and if it's not it'll download the remote file again, which will trigger the md5 check as well, so don't really need to run it on every Chef run.

Merged in c0ea1488e58a91d6e4de3b52d3b14c007e77f8cb.

source: gharchive/pull-request

authors: DmitrySolodovnyk mthssdrbrg

repo: mthssdrbrg/kafka-cookbook

license_source: bigquery


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

In b192b6e, https://minfo.ps (https://minfo.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://minfo.ps is back up in c4075db.

repo: mtitservice/site


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

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

HTTP code: 0
Response time: 0 ms

Resolved: https://gcc2.mtit.pna.ps is back up in f726319.


text:
🛑 https://db.hcys.ps is down

In 1720088, https://db.hcys.ps (https://db.hcys.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://db.hcys.ps is back up in 979f0da.


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

In 995121e, https://diaspora.ps (https://diaspora.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://diaspora.ps is back up in fe6f6a8.


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

In 333bf27, 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 4ca2323.


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

In 6163bea, https://palpost.ps (https://palpost.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://palpost.ps is back up in 0cde0af.


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

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

HTTP code: 0
Response time: 0 ms

Resolved: https://911.ps is back up in cf76ccf.


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

In f5629ad, https://palcp.ps (https://palcp.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://palcp.ps is back up in f7e3835.


text:
🛑 https://archive.minfo.ps is down

In 9569511, https://archive.minfo.ps (https://archive.minfo.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://archive.minfo.ps is back up in d90d457.


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

In 620d68d, https://takaful.salfeet.plo.ps (https://takaful.salfeet.plo.ps) was down:

HTTP code: 0
Response time: 0 ms

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


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

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

HTTP code: 0
Response time: 0 ms

Resolved: https://911.ps is back up in f301113.


text:
Update fly.io.md

The previous URL is wrong

Thanks! They must have updated that recently.

authors: mtlynch wasauce

repo: mtlynch/logpaste


text:
Option for video pass-through

Currently it goes like
server <==usb(hid)==> tinypilot <==ip(hid+video)==> localhost
  |--------video-------->

But when the server and the localhost are geographically close, it should be possible for the video to bypass tinypilot:
server <==usb(hid)==> tinypilot <==ip(hid)==> localhost
   |--------------------video------------------>

This way, the whole workload of video compression and transmission is freed from tinypilot. Pi Zero W should then be a feasible alternative device (see https://github.com/mtlynch/tinypilot/issues/93).
This could be implemented by a websocket daemon on localhost for the video capture dongle + a video source picker in the UI.

Thanks for filing and for the suggestion!
This unfortunately is not possible. For the server to send video directly to the user's browser, there would need to be a TinyPilot agent application running on the server to send the video data. But if you can run software on the target server, then TinyPilot likely isn't the right tool, because the value of TinyPilot is that you don't need special software running on the target device.
Put another way, imagine that you're trying to capture a BIOS interface in TinyPilot. I'm not aware of any BIOS that allows you to redirect video to a remote websocket daemon, so the direct connection solution wouldn't work.

Thanks for the quick response.
But I'm not sure I understand your points, because all it takes to let the server send video data is a single hdmi cable plugged into it (with a hdmi capture dongle on the other side). No TinyPilot agent should be necessary.

That's an interesting alternative, but then the user's computer would need extra software on it to process the incoming video. I'd like to keep TinyPilot's requirements on the end-user machine to browser-only with no additional software.

Indeed there would be hassle on the user's side, therefore the status quo should definitely remain as the default.
But when the user experiences more lag than they can bear, it would be nice if there's an option to reduce the lag with a one-off cost. Ideally the user only has to run a one-liner copied from the UI page, something like curl http://raspberrypi.local/dongle_deamon_linux.sh | sh, so the workflow is not drastically interrupted.

Unfortunately, it would add too much complexity for too niche a scenario. We'd have to provide installers for each supported client OS, which is a substantial amount of work.

authors: champignoom mtlynch

repo: mtlynch/tinypilot


text:
Please streamline the user experience

Ensure every area where text can be entered that this user is aware of what input is accepted.
Do not force the user to "press enter to continue" at any point in time. The user doesn't want to have to repeatedly press enter.

?

User no longer has to press enter when being asked yes or no to exiting and saving.  User also can now tab complete scratch/current when deciding type of save.

Unfortunately, the use of the keyboard module was outlawed and as a result this issue will need to be reworked.

New implementation has been added to handle y/n/c without the need for admin privs.  Tab complete now also works and gives a drop down list to tab through to auto complete your option.


text:
Pictures issue

When I want to export a card a picture from background disappears. What should I do?

what do you mean? I'm not sure i quite understand what you're asking about.

what do you mean? I'm not sure i quite understand what you're asking about.

I added a picture to card but when I want to export it doesn't show

oh hmm that's odd. what's the image's format? gif? jpg? png?

oh hmm that's odd. what's the image's format? gif? jpg? png?

Its jpg

I found the issue. It's a really dumb optimization issue. If the images are too big, the card's image handler will sometimes fail. I've swapped out some of the inner implementation details so it should work better now,,, in theory...


text:
[docs] Fix select multiple prop description

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

It was released in v3.6.2
https://github.com/mui-org/material-ui/releases/tag/v3.6.2

@AkselsLedins Thank you!

authors: AkselsLedins oliviertassinari

repo: mui-org/material-ui


text:
[Autocomplete] Fix GitHub's demo behavior

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

Closes #19836

Hii @oliviertassinari,
Can you explain below about test regressions?

Visual regression test
$ argos upload test/regressions/screenshots/chrome --token $ARGOS_TOKEN
error: option '-T, --token ' argument missing
error Command failed with exit code 1.

@hasanozacar I think that the priority should be to update the pull request to match the proposed direction in #19836. As far as I know, fixing this bug shouldn't request to change any existing test. I believe in its current form, the logic would introduce a regression, inputValue is never supposed to be undefined.

You can blame the line and the corresponding tests to gain more insight into the why. It should lead you to the underlying GitHub issues (that are now closed).

@hasanozacar Do you plan to follow up on the proposed changes?

@oliviertassinari  sorry , I didn't have enough time to implement.I don't understand the "yarn proptypes"

@hasanozacar Thanks!

authors: hasanozacar oliviertassinari


text:
[WIP][core] Create new @material-ui/theming package

This PR will serve as a POC that we can remove the dependency of @material-ui/styles in @material-ui/core. Things planned to be done:

[x] extract things used in both @material-ui/styles & @material-ui/core under one @material-ui/theming package
[x] add dependency to this package in @material-ui/styles & @material-ui/core for using the common utilities from this one

After this we have two options:
Option 1
Makes the use of ThemeProvider required for the @material-ui/styles. In that case we will need to:

[ ] remove the duplicated utilities in @material-ui/core/styles: makeStyles, styled withStyles & withTheme in favor of the ones in @material-ui/styles that will use the defaultTheme
[ ] update docs & demos

Option 2
Make everything work as previously by extracting more things in the @material-ui/theming package

[ ] extract createMuiTheme in the new package, so that we can create defaultTheme outside of the core (are we fine with this?)
[ ] safely remove the duplicated utilities in @material-ui/core/styles: makeStyles, styled withStyles & withTheme in favor of the ones in @material-ui/styles that will use the defaultTheme

The two options will be done in a separate PRs on top of this one, so we can see the changes required.

I'm not too keen on the idea of @material-ui/theming as it seems to only fix a migration issue, not relevant in the long term.
Regarding the different options available, I tried to poor more thoughts into it (and not reading this PR description to not be biased). Is Option A, viable?

@material-ui/styles has its own ThemeProvider. Only relevant for devs that can't migrate, so it lives as a custom styling solution.
@material-ui/core has its own ThemeProvider, for our own components, the main one we document.
@material-ui/styled-engne has its own ThemeProvider, for emotion or sc.
Developers that want to keep on using @material-ui/styles would be forced to use its ThemeProvider, in addition to the core. They would also be forced to import from @material-ui/styles.

It actually seems to be Option 1.

I'm not too keen on the idea of @material-ui/theming as it seems to only fix a migration issue that is not relevant in the long term.

How about we make this package private, and maybe rename it to @material-ui/theming-internal. I extracted there things that are used in both packages. It has only few dependencies, and none of the JSS dependencies.

@mnajdova This could work, the advantage would be that developers that depend on @material-ui/styles will only need to change the import paths, but not the theme provider, correct?

@mnajdova This could work, the advantage would be that developers that depend on @material-ui/styles will only need to change the import paths, but not the theme provider, correct? Then, I think that we will need to drop this package in v6.

Correct.

@oliviertassinari @eps1lon are we onboard that we are good to go with Option 1 - making the use of ThemeProvider required for @material-ui/styles?
If that is the case, we can go with reviewing with this PR, and as a follow up I would remove all dependencies of @material-ui/styles from @material-ui/core. I would probably do it in multiple PRs removing one dependency at a time. I will update the docs for @material-ui/styles regarding the ThemeProvider being required in the first breaking change.

Option 1 - making the use of ThemeProvider required for @material-ui/styles?

👍  for it (BC on ThemeProvider and the import paths). This will require most of the existing projects in v4 to make the change, but the proposed alternative doesn't seem practical.

Edit: Should we name the new package to @material-ui/theming-internal?

@material-ui/private-theming? Assuming we do the above, does this package still solve a problem?

@material-ui/private-theming? Assuming we do the above, does this package still solve a problem?

Agree on the name. The package will at least allow us to have common theme context and utils between the two packages without requiring developers to have both @material-ui/styles and @material-ui/core. Long term if we drop @material-ui/styles we can just move the utils in core.

@material-ui/theming => @material-ui/private-theming rename done.

authors: mnajdova oliviertassinari


text:
Outlined text field shows line through label

[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 the TextField or Select renders with input in it, the label is rendered above the input and the line moves away.
Current Behavior
The label does move up, but the line remains, going through the text.

Steps to Reproduce
I am unable to reproduce this issue consistently. It does happen the majority of the time in the project I'm working. The outline does update as soon as interaction has taken place with the page like clicking on an element, opening a dropdown, etc. or anything that manipulates the state of the current component.
I've seen this happen in v3.2.x, I have never used the variant="outline" in prior versions so am unaware if this bug existed prior to v3.2.
Link: https://codesandbox.io/s/q361rzjpy4
Context
N/A
Your Environment

Tech
Version

Material-UI
v3.2.x

React
v16.5

Browser
Edge, Firefox, Chrome

@Studio384 We would love to have a way to consistently reproduce the issue. It's very hard to work on this type of issue without.

The code sandbox does reproduce it most often in Edge 18y. Other browsers appear to be less consistent in reproducing the issue or are only showing it for a short time (Chrome) before updating the view again to move the line away from the label.

I'm also experiencing this issue when a OutlinedSelect is mounted with a prefilled value. The label corrects itself after a re-render. I suspect it has something to do with the labelRef from the <InputLabel> being unavailable at initial render, since it's offsetWidth is used to control the width of the gap.
Version: 3.2.2 (latest at writing time)
Browser: Chrome  69.0.3497.100

I'm closing for #13297. I could reproduce the issue on Edge. The issue disappears as soon as I hover the input. It's a rendering glitch

It's not the same issue as #13297. In Firefox you have to interact with the page for it to go away and when you do it will animate the line (which shouldn't happen if this was a rendering glitch).

Outline text field look terrible in Firefox but working in Chrome. When clicking the textfield in Chrome there's also a color change, not happening in Firefox.

Hi, I've had this issue too. It occured whenever I changed the label of the Textfield dymically at runtime (I needed to switch languages).
I would write the new label to state, and even though the Textfield showed the new label, it didn't update the outline. However it updated the outline once a rerender was triggered anywhere else.
So in my case I had a function to merge my new labels into current state. My solution was to promisify this function and then force an update. I think this is very ugly, but not as much as the linethroughs ;)
I did:
`let update = new Promise((resolve, reject)=>{
this.setState(state => ({
formFields: currentStateFormFields
}), resolve(true) )
});
update.then(result =>{
  if(result) {
    this.forceUpdate();
  } else {
    throw new Error("MERGING LANGUAGE FAILED");
  }
})`

Fixed in v4.4.0: https://codesandbox.io/s/material-ui-text-field-bug-m4ujq.
-- credits to @oliviertassinari

This does not appear to be fully fixed on v4.4.0.

I'm having the same problem the original poster explained. I mean, this happens when any change to the state that contains the field is done. Re-rendering the field by changing any of its properties makes this problem disappear, but I'm not sure how to "force" such thing.

@danielo515 You could update the key, which would cause a re-render of the component.

@danielo515 You could update the key, which would cause a re-render of the component.

Yes, that is what I ended doing. Thanks for your answer in any case.

Does anyone has a reproduction?

It is tricky to reproduce. Can't say what triggers it. For example on my case it only happens on 2 out of 3 elements in the same parent component. The only difference is that those two are inline while the other is full width.

Hello,
I have this bug too and I don't find how to solve it. It appeared on a form when I used tabs component (I took "simple tabs" example).
 <TabPanel value={value} index={0}>         <ProductInfos           selectedInfos={selectedInfos}           onChange={onChange}         />       </TabPanel>       <TabPanel value={value} index={1}>         <OrderInfos           selectedInfos={selectedInfos}           onChange={onChange}         />       </TabPanel>       <TabPanel value={value} index={2}>         <SupplierInfos           selectedInfos={selectedInfos}         />       </TabPanel>
The form displayed by  is good, the render of  is ok. But this isn't good in the 2 other tabs. I have the same problem with  labels' as discribed above, for my forms displayed by  and .
Is there a temporary solution to fix it and make labels override the outlined borders?
Sorry for my bad english and thanks in advance for help.

@rikku28 This sounds like a duplicate of #17355.

@rikku28 This sounds like a duplicate of #17355.

Hola,
también tengo este error y no encuentro cómo solucionarlo. Apareció en un formulario cuando utilicé el componente de pestañas (tomé el ejemplo de "pestañas simples").
 <TabPanel value={value} index={0}> <ProductInfos selectedInfos={selectedInfos} onChange={onChange} /> </TabPanel> <TabPanel value={value} index={1}> <OrderInfos selectedInfos={selectedInfos} onChange={onChange} /> </TabPanel> <TabPanel value={value} index={2}> <SupplierInfos selectedInfos={selectedInfos} /> </TabPanel>
El formulario que se muestra es bueno, el renderizado es correcto. Pero esto no es bueno en las otras 2 pestañas. Tengo el mismo problema con las etiquetas 'como se describe anteriormente, para mis formularios mostrados por y.
¿Existe una solución temporal para arreglarlo y hacer que las etiquetas anulen los bordes delineados?
Perdón por mi mal inglés y gracias de antemano por la ayuda.

I have exactly this problem, I have tried many things without obtaining an effective result ... I have even copied the form of the first Tab and this happens ...

It seems that the TabPanel demos we have are a common source of the observation of the problem. In this context, I would propose the following diff in the demos:
diff --git a/docs/src/pages/components/tabs/SimpleTabs.js b/docs/src/pages/components/tabs/SimpleTabs.js
index 02e6d8ce3..0ce8c959d 100644
--- a/docs/src/pages/components/tabs/SimpleTabs.js
+++ b/docs/src/pages/components/tabs/SimpleTabs.js
@@ -19,7 +19,7 @@ function TabPanel(props) {
       aria-labelledby={`simple-tab-${index}`}
       {...other}
     >
-      <Box p={3}>{children}</Box>
+      {value === index ? <Box p={3}>{children}</Box> : null}
     </Typography>
   );
 }

It would also help with performance, as only rendering the visible nodes, at least, until React improves the handling of hidden. cc @mbrookes and @eps1lon.

@oliviertassinari Thanks for the help. That's working now, with this modification. :)
Best regards

Not sure it helps, but I was still having this issue because a previous dev was using  and  instead of  with label=""
Once I made the change the line went away when typing into the field.

For anyone who found this thread but the suggestions here didn't help, I found that the displayEmpty prop was causing this issue for us. Once we removed it from our Select components it looked as expected.

authors: JanKaifer Resumane Studio384 clathrop danielo515 dnavamosler itsmarkdarling joglr joshwooding nicovalencia oliviertassinari rikku28 theRealEmu

repo: mui/material-ui


text:
Media queries merged in wrong order when some of them have default breakpoint

[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 😯

The order of merged media queries is
@media (min-width:600px)
@media (min-width:0px) and (orientation: landscape)
Expected Behavior 🤔

The order of merged media queries should be
@media (min-width:0px) and (orientation: landscape)
@media (min-width:600px)
Steps to Reproduce 🕹

Repro: https://codesandbox.io/s/bitter-worker-7koq6?file=/src/App.tsx
Steps:

<Drawer/> has wrong marginTop when screen width is greater then 600px.
If you add a space character to the end of @media (min-width:600px) in paperStyles, the marginTop will be right.

Context 🔦

In styleFunctionSx, the styles are merged into an object which has empty default breakpoints. It makes all custom media queries have latter order in merged styles.
Your Environment 🌎

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

You can define the "@media (orientation: landscape)" inside the "@media (min-width:0px)":
  const paperStyles = useMemo(
    () => ({
      marginTop: "56px",
      "@media (min-width:0px)": {
        "@media (orientation: landscape)": {
          marginTop: "48px"
        }
      },
      "@media (min-width:600px)": {
        marginTop: "64px"
      }
    }),
    []
  );

See https://codesandbox.io/s/recursing-water-quxgj?file=/src/App.tsx
If we don't have any sorting with the media queries, it will break many scenarios where styles are merged, and the media queries for smaller screens end up after the ones for larger screens.

@mnajdova this issue has (more or less) unexpected implications. The toolbar mixin is defined like this:
toolbar: {
  minHeight: 56,
  [`${breakpoints.up('xs')} and (orientation: landscape)`]: {
    minHeight: 48,
  },
  [breakpoints.up('sm')]: {
    minHeight: 64,
  },
}

Because of that, unexpected results can occur if you use the mixin in different environments (Babel, CRA, ...) because as it seems the order is not guaranteed like this.
If I use the <Toolbar> component without any adjustments (knowing that it uses the mixin internally), in one example I get this:

If I then use <Box sx={theme => theme.mixins.toolbar}>, I get this:

It might be related to other issues too, but this here is the most precise one which might even offer a solution.

I have to add that an unintuitive solution is to do this:
<Toolbar sx={theme => theme.mixins.toolbar }>
At which point the styling engine will at least be deterministic (wrong or not).

Right, we need to update the toolbar mixin, by moving the {orientation: landscape) inside the xs breakpoint. @hbjORbj I remember we discussed this already, would you like to create a PR and validate that it works as expected?

@mnajdova Sure, I will own this.

Right, we need to update the toolbar mixin, by moving the {orientation: landscape) inside the xs breakpoint.

Can I know why we need to move? How does the order affect by doing this? Why it won't work with the and keyword?

Review my comment earlier to see why the order is a problem.
To elaborate some more: Media query rules do not increase specificity if you add more terms to the query on the same level; CSS rules dictate that all media query rules that evaluate to true are processed in the order given in the CSS text. By moving the {orientation: landscape) inside the xs breakpoint, you get a media query within a media query (also refer to this earlier comment) which increases specificity and produces the desired results plus it removes the order requirement that is induced by the current implementation.

Media query rules do not increase specificity if you add more terms to the query on the same level

We don't want to increase specificity anyway. We actually want sm breakpoint to take more priority over xs, right?

CSS rules dictate that all media query rules that evaluate to true are processed in the order given in the CSS text

It's an object (return type of createMixins method) that is converting to CSS text. Why is it adding xs after sm in the stylesheet whereas it should be other way around so that sm takes priority when it's beyond 600px?

By moving the {orientation: landscape) inside the xs breakpoint, you get a media query within a media query (also refer to https://github.com/mui/material-ui/issues/27532#issuecomment-891613219) which increases specificity

Actually the specificity decreased right? With the and keyword it was always getting applied even beyond 600px.
More details in the PR description of #32713

Ah maybe I got it wrong because it's already a few months ago since I looked into this.
The thing is that there is extra code provided by MUI which merges styles for the individual screen size breakpoints and guarantees order. The media query with the "and" does not get merged (since it constitutes a different media query string) and then it's not guaranteed in which order the CSS text is rendered.
The things I said about specificity probably was a red herring, I'm sorry.

The media query with the "and" does not get merged (since it constitutes a different media query string) and then it's not guaranteed in which order the CSS text is rendered.

That is my theory as well after looking into the styleFunctionSx method but I cannot confirm. Anyway thanks for your input even after a few months.

We are ordering the media queries after the sx prop is resolved from xs to xl so that the order is predictable. However, as this media query is more complex, it does not fit in the simple media queries that we are considering for ordering. This is why moving the second part of the and query is fixing the issue.

authors: SpringNyan ZeeshanTamboli hbjORbj mnajdova p2k


text:
[Radio][Joy] Button indicator is not centered

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://mui.com/joy-ui/react-radio-button/
Steps:

Open a RadioGroup demo.

Current behavior 😯
The dot indicating the active RadioGroup option isn't properly centerd in any size.
Small:

Medium:

Large:

This happens in all browsers. How to dot is misaligned varies from scenario to scenario. E.g.:

In the first demo the button is off-center to the bottom right, the second demo has it off-center to the bottom left, and the third demo has it off-center to the top left (the demo under it - not in the screenshot - has the dot off-center to the top right.
Expected behavior 🤔
The dot is consistently shown in the center of the radio button.
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  System:
    OS: Windows 10 10.0.22623
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.16.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22621.1037.0), Chromium (108.0.1462.46)
  npmPackages:
    @emotion/react: 11.10.5 => 11.10.5
    @emotion/styled: 11.10.5 => 11.10.5
    @mui/base:  5.0.0-alpha.110
    @mui/core-downloads-tracker:  5.11.0
    @mui/joy: 5.0.0-alpha.58 => 5.0.0-alpha.58
    @mui/lab: 5.0.0-alpha.112 => 5.0.0-alpha.112
    @mui/material: 5.11.0 => 5.11.0
    @mui/private-theming:  5.11.0
    @mui/styled-engine:  5.11.0
    @mui/system:  5.11.0
    @mui/types:  7.2.3
    @mui/utils:  5.11.0
    @mui/x-date-pickers: 5.0.11 => 5.0.11
    @types/react: 18.0.26 => 18.0.26
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 4.9.4 => 4.9.4

Firefox 106

I've experimented with the exact same demo you've used, and these are my results. Code-wise, the dot is properly aligned to the center (with align-items and justify-content both to center). I wonder why this happens on your end. Do you still reproduce the issue?

Can you inspect the element and hover over the component to show the dimensions on left/right side as in the screenshot below?

Blowing up your first screenshot, I'd like to note that it is in fact happening there as well. I assume your higher pixel density just made it harder to see. See above, the dot is not vertically centered.
As for my own:

Thanks for your input.
I think the following should fix the issue.
--- a/packages/mui-joy/src/Radio/Radio.tsx
+++ b/packages/mui-joy/src/Radio/Radio.tsx
@@ -204,8 +204,8 @@ const RadioIcon = styled('span', {
   slot: 'Icon',
   overridesResolver: (props, styles) => styles.icon,
 })<{ ownerState: RadioOwnerState }>(({ ownerState }) => ({
-  width: '50%',
-  height: '50%',
+  width: 'calc(var(--Radio-size) / 2 - var(--variant-borderWidth))',
+  height: 'calc(var(--Radio-size) / 2 - var(--variant-borderWidth))',


text:
CSS prop not supported, contrary to documentation

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: the documentation
https://mui.com/material-ui/guides/interoperability/#the-css-prop
Current behavior 😯
No overload matches this call.

  Overload 1 of 2, '(props: { component: ElementType<any>; } & { color?: "primary" | "secondary" | undefined; components?: { Root?: ElementType<any> | undefined; Track?: ElementType<any> | undefined; ... 5 more ...; Input?: ElementType<...> | undefined; } | undefined; componentsProps?: { ...; } | undefined; classes?: (Partial<...> & { ...; }) | undefined; size?: "small" | ... 1 more ... | undefined; sx?: SxProps<...> | undefined; } & Omit<...> & Omit<...>): Element | null', gave the following error.

    Property 'component' is missing in type '{ children: ReactNode; classes?: (Partial<ButtonClasses> & Partial<ClassNameMap<never>>) | undefined; color?: "inherit" | ... 6 more ... | undefined; ... 287 more ...; css: SerializedStyles; }' but required in type '{ component: ElementType<any>; }'.

  Overload 2 of 2, '(props: DefaultComponentProps<ExtendSliderUnstyledTypeMap<SliderTypeMap<"span", {}>>>): Element | null', gave the following error.

    Type '{ children: ReactNode; classes?: (Partial<ButtonClasses> & Partial<ClassNameMap<never>>) | undefined; color?: "inherit" | ... 6 more ... | undefined; ... 287 more ...; css: SerializedStyles; }' is not assignable to type 'IntrinsicAttributes & { color?: "primary" | "secondary" | undefined; components?: { Root?: ElementType<any> | undefined; Track?: ElementType<any> | undefined; ... 5 more ...; Input?: ElementType<...> | undefined; } | undefined; componentsProps?: { ...; } | undefined; classes?: (Partial<...> & { ...; }) | undefined; ...'.

      Property 'css' does not exist on type 'IntrinsicAttributes & { color?: "primary" | "secondary" | undefined; components?: { Root?: ElementType<any> | undefined; Track?: ElementType<any> | undefined; ... 5 more ...; Input?: ElementType<...> | undefined; } | undefined; componentsProps?: { ...; } | undefined; classes?: (Partial<...> & { ...; }) | undefined; ...'.ts(2769)

Expected behavior 🤔
The documentation says it works, it should work.
Context 🔦
I want to style Mui components in a DRY way, without gigantic SX chains (ugly, not readable).
Your environment 🌎
NOT APPLICABLE - but included anyways

npx @mui/envinfo
  System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 19.3.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 4.0.0-rc.9 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 9.2.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0)
  npmPackages:
    @emotion/react: ^11.10.5 => 11.10.5
    @emotion/styled: ^11.10.5 => 11.10.5
    @mui/base:  5.0.0-alpha.113
    @mui/core-downloads-tracker:  5.11.4
    @mui/icons-material: ^5.11.0 => 5.11.0
    @mui/material: ^5.11.4 => 5.11.4
    @mui/private-theming:  5.11.2
    @mui/styled-engine:  5.11.0
    @mui/system: ^5.11.4 => 5.11.4
    @mui/types:  7.2.3
    @mui/utils:  5.11.2
    @types/react: ^18.0.26 => 18.0.26
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.9.4 => 4.9.4

Workaround (not using CSS prop)
import type { ButtonProps } from '@mui/material/Button'
import Button from '@mui/material/Button'
import type { SxProps, Theme } from '@mui/material/styles'
import useMediaQuery from '@mui/material/useMediaQuery'
import type { ReactNode } from 'react'

// I couldn't find a "container of SxProps" type in Material.
type UseStyles = {
  [key: string]: SxProps<Theme>
}

// This is a super inefficient way to share styles, but it works.
const useStyles = (): UseStyles => {
  const mobile = useMediaQuery((theme: Theme) => theme.breakpoints.down('sm'))

  return {
    button: {
      borderRadius: '20%',
      height:       mobile ? '32px' : '38px',
      minWidth:     0,
      width:        mobile ? '32px' : '38px',
    },
  }
}

type Props = ButtonProps

export default function MyButton(props: Props): ReactNode {
  const {
    children,
    ...rest
  } = props

  const classes = useStyles()

  return <Button sx={classes.button} {...rest}>
    {children}
  </Button>
}

@AlbinoGeek can you share a reproduction where the CSS prop doesn't work? Looks correct in the demo you linked above - here is a codesandbox: https://codesandbox.io/s/m7qh7d?file=/demo.tsx

Hmm, after re-re-re-viewing the sample code, I noticed a missing comment:
/** @jsxImportSource @emotion/react */

So, am I to understand this is required in every file in my project if I want to use the css property?
This is rather confusing and obtuse. However, I apologize, if that's the case, this issue is on my end.

Hmm, I'm going to close this as "not your problem" -- seems like I'm going to have to complain to @motion/react .

In case anyone comes back to this. Add
"compilerOptions": {   "jsxImportSource": "@emotion/react" }

authors: AlbinoGeek joshnosal mnajdova


text:
[Collapse] Support anchoring content to the bottom/right

Summary
Would like to be able to anchor the collapsed content to the bottom of to container. The effect can be achieved by adding following styles to the Collapse but it would be nice to have a prop that can handle this:
sx={{
  display: "flex",
  flexDirection: "column-reverse",
}}

Perhaps the direction prop can even be expanded to account for this use-case. If not accepted, perhaps this use-case could be added to the docs?
Examples
Here's a codesandbox that displays the desired behavior: https://codesandbox.io/p/sandbox/lucid-heyrovsky-wrjrnp?file=%2Fsrc%2FDemo.tsx%3A47%2C45
https://github.com/user-attachments/assets/9e8f89dc-5d60-4ee6-80f0-ddd286fe6a8a
Motivation
I struggled a bit with this when building Toolpad component catalog, which feels better when it looks like the drawer is pulled from under the left edge, rather than it being already in place and revealed gradually. Now I'm running into it again with another component.
https://github.com/user-attachments/assets/0398c9c8-7fb3-42df-a94f-ecd53b223b31
vs.
https://github.com/user-attachments/assets/5aa03937-8810-4541-b021-af2caea3d114
Search keywords: collapse reverse

Perhaps the direction prop can even be expanded to account for this use-case. If not accepted, perhaps this use-case could be added to the docs?

That's a good start.

authors: Janpot siriwatknp


text:
[material-ui][Dialog] Compatibility between MUI's dialogs and React Hook Form with FormProvider

Search keywords
React Hook Form FormProvider Dialog
Latest version

[X] I have tested the latest version

Summary
It is currently not possible to make use of React Hook Form context in Material UI dialogs as the <form> element is commonly encapsulated in a FormProvider component.
That FormProvider component is a context provider, and no style can be applied to is as a result.
This makes it impossible to pass a FormProvider instance to the component property on the PaperProps property of the MUI Dialog component.
ℹ That limitation is not restricted to the use of React Hook Form only, but to any use of context providers used as form parents.
Motivation
A MUI dialog can be configured to be used for forms, as described on Material UI's docs. Simple forms will work fine, but complex forms using React Hook Form with FormProvided can't be used.
Here's why 🙂
To put it in context, a dialog form has to encapsulate all the following children of the Dialog component:

DialogTitle
DialogContent
DialogActions

This allows to get form fields (which are part of the DialogContent children) to be submitted when clicking on the submit button as a child of the DialogActions component.
To make it work, the parent Dialog component can be configured so that its inner Paper child can be configured to be rendered as a form element with some specific properties:
<Dialog
  // ...
  PaperProps={{
    component: 'form',
    onSubmit: (event) => {
      event.preventDefault();
      // ...
    },
  }}
>

And here is the limitation I am facing. Complex forms using React Hook Form commonly encapsulate the <form> element in a <FormProvider> component so that form children components can get access to React Hook Form's context (see FormProvider documentation):
<FormProvider {...methods}>
  // pass all methods into the context
  <form onSubmit={methods.handleSubmit(onSubmit)}>
    <NestedInput />
    // ...
  </form>
</FormProvider>

It is currently not possible to define this FormProvider as a parent of the form element when using forms in MUI's dialogs.

@michaelperrin I haven't used RHF recently but wouldn't this work?
<Dialog>
  <FormProvider> // or it could be placed even higher up?
    <form>
      <DialogTitle>
        A Title
      </DialogTitle>
      <DialogContent>
        <TextField />
      </DialogContent>
      // etc

Thanks for your answer @mj12albert . That's the first approach I tried. And this wasn't working when using Material UI 6.0.1 due to scrolling issues inside the dialog (the dialog couldn't be scrolled if the form was long).
I then realized the scrolling issue was fixed when upgrading to Material UI 6.1.5. And it looks like it actually got fixed from version 6.1.0 👍
One of the remaining issues with this is that the whole dialog content (including header and footer) scrolls, but that's not the point of the issue I opened.


text:
[docs] Improve ordering of slots in Slots section in API pages

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

Follow-up on https://github.com/mui/material-ui/pull/36328#issuecomment-1464980498
This PR makes changes to the "Slots" section in API pages

places root slot at the top of the list in the "Slots" section
sorts other slots except root slot in alphabetical order

Before:

base
joy

After:

base
joy

An alternative to #36499?

Closing this PR in favour of #36499

@hbjORbj I think that you were right to prioritize time on this problem, simple to change, but also a nice DX win 👍

authors: hbjORbj oliviertassinari


text:
[docs-infra] Add icon to callouts

Closes #38519
This PR adds icons to the documentation callouts! We also took advantage of the opportunity to clean instances of it that were using emojis instead of the built-in icons. There might be more spread out throughout the docs ⎯ it was just a quick check.
https://deploy-preview-38525--material-ui.netlify.app/experiments/docs/callouts/

Light
Dark

To-dos:

[x] Put the correct SVG path in the icons (<symbols/> ids are already correct)
[ ] Improve the CSS (I did something crappy to highlight where CSS rules are)

A few duplicated icons

https://github.com/mui/material-ui/issues/38689 created.

authors: alexfauquette oliviertassinari


text:
[POC][Do not merge] ESM module distribution improvements

POC for improving the ESM module distribution of the packages.

Add exports key pointing to import and require files
Add file extensions with babel-plugin-add-import-extension

Missing:

Types
UMD build broke, have to figure out why, removed it for the POC

The first test is working as expected ✅
The next step is to sort the CI tests out.

All of this looks reasonable to me 👍

Regarding the CI issues. It looks like the snapshot size test is looking for the umd build. Which was removed in this PR. We can also get rid of the size test as well:
diff --git a/scripts/sizeSnapshot/create.js b/scripts/sizeSnapshot/create.js
index b8b68e60b4..1ed2f343e1 100644
--- a/scripts/sizeSnapshot/create.js
+++ b/scripts/sizeSnapshot/create.js
@@ -56,11 +56,7 @@ async function getWebpackSizes(webpackEnvironment) {
 async function run(argv) {
   const { analyze, accurateBundles } = argv;

-  const rollupBundles = [path.join(workspaceRoot, 'packages/mui-material/size-snapshot.json')];
-  const bundleSizes = lodash.fromPairs([
-    ...(await getWebpackSizes({ analyze, accurateBundles })),
-    ...lodash.flatten(await Promise.all(rollupBundles.map(getRollupSize))),
-  ]);
+  const bundleSizes = lodash.fromPairs(await getWebpackSizes({ analyze, accurateBundles }));

   await fse.writeJSON(snapshotDestPath, bundleSizes, { spaces: 2 });
 }

authors: DiegoAndai Janpot


text:
Add GA events in Toolpad demo

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡

Before clicking on create, which template did the user choose or if they clicked on Continue with my last app.

No. of clicks coming on:

Self-host button
roadmap
schedule demo

Examples 🌈
No response
Motivation 🔦
No response

Whenever I use this UI, it's not very clear to me. It feels like I have to click create, but a template is forced on me.
I wonder whether we should just show a grid where the options are all equal in effort to pick. e.g. show a grid of options:

create blank application
start from template 1
start from template 2
continue where you left off last time

Whenever I use this UI, it's not very clear to me. It feels like I have to click create, but a template is forced on me.
I wonder whether we should just show a grid where the options are all equal in effort to pick. e.g. show a grid of options:

create blank application
start from template 1
start from template 2
continue where you left off last time

Yeah, it probably could be better designed... Making everything seem equal in the UI sounds like a good thing to do.
Another alternative could be for all the action buttons to be centered like the template button and stacked vertically, instead of having those actions in the corner.
Not sure if it would be worthwhile to get Gerda's input on this so we can have something that looks ok?

Agree on the thought of creating a grid like UI. There is an existing issue for this: https://github.com/mui/mui-toolpad/issues/1390

authors: Janpot apedroferreira prakhargupta1

repo: mui/mui-toolpad


text:
Create component for chat link display

Create a react component that will take content as a prop.
Functionalities:

It'll have a copy button
Clicking on the copy button, the content will be copied to the clipboard.
If someone clicks on the text it should get selected.

Example:

I am working on this issue and I am trying to use useRef hook to access copy the text inside the textarea but I am encountering the attached error.

Never mind, resolved.


text:
feat: add CheckIntegrity method on Decoder

Why we need this and best practice to use it is specified on https://developer.garmin.com/fit/cookbook/isfit-checkintegrity-read/

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (74224ed) 100.00% compared to head (423b239) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##            master       #84   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           28        28
  Lines         3102      3147   +45
=========================================
+ Hits          3102      3147   +45

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter muktihari

repo: muktihari/fit


text:
Tableau Dashboard

Added platform metrics current consolidated dashboard
Added tableau strategy request in postman collection
Fixed splunk current consolidated dashboard metrics calculations
Fixed metrics collection for BGs with no environments (API requests that does not require an environment id will be executed if BG does not have environments)
Fixed some logs typos
Fixed rawData flag handling (flag was not being taken into account when loaded from loadDetails coming from a POST API request)
Changed tableau.path property to tableau.outputDir
Changed tableau strategy JSON file generation rule
Added isMaster flag to indicate if BG is master organization
Added ratedAssets and unratedAssets in exchangeMetrics
Fixed overallSatisfaction calulation to use ratedAssets only
Changed ARM maxConcurrency from 100 to 3 to avoid 503 errors
Updated README.md with tableau instructions

Closing PR. New features and bug fixes will be submitted in separate pull requests.

Closing PR. New features and bug fixes will be submitted in separate pull requests.

repo: mulesoft-catalyst/metrics-accelerator

license: Unlicense


text:
Libuv SDK Version Problems with Xcode 7

Currently if building on OS X I get the following make output:
        cc src/aux/wren_aux_meta.c        -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/aux/wren_aux_random.c      -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/vm/wren_compiler.c         -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/vm/wren_core.c             -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/vm/wren_debug.c            -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/vm/wren_primitive.c        -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/vm/wren_utils.c            -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/vm/wren_value.c            -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/vm/wren_vm.c               -O0 -DDEBUG -g -std=c99 -fPIC
        ar lib/libwrend.a                 rcu
        cc lib/libwrend.dylib             -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/cli/main.c                 -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/cli/modules.c              -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/cli/vm.c                   -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/module/io.c                -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/module/scheduler.c         -O0 -DDEBUG -g -std=c99 -fPIC
        cc src/module/timer.c             -O0 -DDEBUG -g -std=c99 -fPIC
        cc bin/wrend                      -O0 -DDEBUG -g -std=c99 -fPIC
ld: warning: object file (build/libuv.a(core.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(fs.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(tty.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(uv-common.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(loop.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(pipe.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(stream.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(timer.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(async.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(loop-watcher.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(kqueue.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(fs-poll.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(darwin.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(poll.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(process.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(signal.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(tcp.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(udp.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(threadpool.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(inet.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(thread.o)) was built for newer OSX version (10.11) than being linked (10.10)
ld: warning: object file (build/libuv.a(fsevents.o)) was built for newer OSX version (10.11) than being linked (10.10)

It looks like the SDK version being used to build libuv is different to that being used to build Wren. It looks like i'm currently using XCode 7 with Clang 7 to build this. Maybe we need to set -mmacosx-version-min=version when building Wren on OS X?

That's annoying. :(
I like your idea for a fix, though I'm not sure what min version to set it too. We don't want to require 10.10. It looks like it's not an issue with building Wren itself so much as it is compiling libuv. You can probably tweak this by adding the right flag when we call xcodebuild in libuv.py.
I can't upgrade to XCode 7 yet, but if you figure out a fix, send it my way and I'll try it out and see how it goes on Xcode 6.

Having had a look around at this it seems that you can't target OS 10.10 with the Xcode 7 xcodebuild. Listing SDKs shows that only the 10.11 SDK is installed. Looks like there must be something wrong with the setup of the command line tools though as they're still managing to compile Wren to target 10.10.
Because there isn't a 10.10 SDK avaiable to xcodebuild it looks like this isn't a simple fix. It might be a case of ignoring the warning until a newer version of the command line tools are available.

Yeah, if it's just a warning and you're still able to build, I guess let's ignore it for now. :-/

This is no longer a problem when building. Not sure what fixed it, but I'm guessing an update to the Xcode command line tools.

Bugs that magically fix themselves are my favorite kind of bugs! 😄

authors: iwillspeak munificent

repo: munificent/wren

license: mit


text:
Revise attribute classes containing @n

See https://github.com/music-encoding/music-encoding/issues/361 for discussion of @n.

Closed by 95426a5

repo: music-encoding/music-encoding


text:
Rotation during crop on vertical image is incorrect

Using photo https://github.com/project802/Focus-Points-Sample-Images/blob/master/Nikon/D800/D800-C9-90deg.NEF
when a user rotates the photo during a crop, the focus point is off. See screens for reference

closing this as duplicate ticket.

you can assign it to me anyway

yours.

Solved in #73

authors: musselwhizzle rderimay

repo: musselwhizzle/Focus-Points


text:
Fix Bug: Passthrough Sourcemaps

Closes issue #1.
Prior to this change, building with Vite using this plugin yielded the warning message:

"(remove-attributes plugin) Sourcemap is likely to be incorrect:
a plugin (remove-attributes) was used to transform files, but didn't
generate a sourcemap for the transformation.
Consult the plugin documentation for help"

The sourcemaps of all files, even JS files which weren't affected by the plugin looked like this:
{
    "version":3,
    "file":"myFile.js",
    "sources":[],
    "sourcesContent":[],
    "names":[],
    "mappings":";;;;;;;;;;;;;;"
}

Comments in the issue pointed out how the same issue was fixed elsewhere, and another one shared a solution.
This commit incorporates these comments into the repository.

Hello @philipp-tailor , I will check your pr and other issue ASAP. Sorry, I am not available novadays.

Thank you @philipp-tailor  . Pr merged and bug fixed.

@mustafadalga, Could you please release this fix on NPM?

@m3hari I have published this fix on NPM

authors: m3hari mustafadalga philipp-tailor

repo: mustafadalga/remove-attr


text:
顶栏颜色css修改

大佬您好，我用以下代码想把四周工具栏改改颜色，但是改了顶栏的标签页不显示，请教下大佬是哪里错了
:root[data-theme-mode=light]{
#toolbar {
--b3-toolbar-background: rgb(224,232,234) !important;
background-color:  rgb(224,232,234) !important;
}
#dockLeft.dock.dock--vertical{
 background-color: rgb(224,232,234) !important
}
#dockRight.dock.dock--vertical{
 background-color: rgb(224,232,234) !important
}
}

添加这个
.layout-tab-bar {
    z-index: 3;
}

添加这个
.layout-tab-bar {
    z-index: 3;
}

感谢大佬，好了

https://github.com/mustakshif/Asri/assets/63196026/56bed39a-1721-4597-a0d6-3e0e9d4d9dc5
大佬再帮忙看看左上角为什么有一小块颜色会切换，我用选择器点选不到

body:not(.body--mobile, .body--window) .layout__dockl.layout--float::before {
    background-color: rgb(224,232,234);
}

body:not(.body--mobile, .body--window) .layout__dockl.layout--float::before {
    background-color: rgb(224,232,234);
}

厉害了我滴神

:root[data-theme-mode=light] {
--b3-theme-background: rgb(241,246,246) !important;
--b3-theme-surface: rgb(232, 239, 240);
--b3-toolbar-blur-background: rgb(47,54,61);
}

大佬，还有个问题是手机端上用--b3-theme-background这个改不了编辑器的背景颜色，客户端一直是255,255,255的纯白，但是在深色模式下又可以，是手机端的日间模式背景颜色设置哪不一样嘛

:root[data-theme-mode=light] .body--mobile {
    background-color: rgb(241,246,246);
}

之前为了修复 #39 强制将亮色模式背景色转为 hex 白色了。你可以试试看 rgb 颜色会不会有问题，如果有就用 hex 颜色

之前为了修复 #39 强制将亮色模式背景色转为 hex 白色了。你可以试试看 rgb 颜色会不会有问题，如果有就用 hex 颜色

:root[data-theme-mode=light] .body--mobile {
--b3-theme-background: #F1F6F6;
}

试了rgb颜色不生效，换成hex就行，感谢大佬

repo: mustakshif/Asri


text:
python protobuf version bump

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Type of changes
Please delete options that are not relevant.

[ ] 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 not work as expected)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

/rerun-all


text:
Fallback options?

Hi, I've read the documentation but it seems like that we don't have fallback options in case the browser does not support the format of the video. How can I provide fallback options?

which video provider and video formats are you using?

I just store it on my hosting server. The format I'm using is AV1.  I just wanted to be sure

ah yes, best to use the player only then with <source> tags. similar to
https://next-video-demo.vercel.app/source-tag
you'd probably need to add a fallback to h.264 or so to support all browsers.
source code:
https://github.com/muxinc/next-video/blob/main/examples/default-provider/app/(default)/source-tag/page.tsx

Could I use it with BackgroundVideo? The video I used is just a background

authors: bquangDinh luwes

repo: muxinc/next-video


text:
It is better for interfacer not to analyze vendor folder

interfacer is a good tool for gophers. I have tried it and got many help. I have a small issue that is currently the interfacer tries to analyze the vendor folder in the golang repo. In my opinion, It is better for interfacer not to analyze vendor folder.
$interfacer ./...
/Users/tony/Test/GoToolsProjects/src/app-weixin/vendor/github.com/astaxie/beego/session/couchbase/sess_couchbase.go:40:12: could not import github.com/couchbase/go-couchbase (cannot find package "github.com/couchbase/go-couchbase" in any of:
	/Users/tony/Test/GoToolsProjects/src/app-weixin/vendor/github.com/couchbase/go-couchbase (vendor tree)
	/Users/tony/.bin/go17/src/github.com/couchbase/go-couchbase (from $GOROOT)
	/Users/tony/Test/GoToolsProjects/src/github.com/couchbase/go-couchbase (from $GOPATH))

The generally suggested (by Go authors) unix-y solution to this is to use grep -v /vendor/:
$ interfacer $(go list ./... | grep -v /vendor/)

That way each tool doesn't have to re-implement this functionality.

Agreed. Otherwise this should make its way to a library like go/loader.

@mvdan I accept the suggestion by @shurcooL . Btw,  Add this to README is better.

authors: baisibei bigwhite mvdan shurcooL

repo: mvdan/interfacer


text:
update icons

The icons have been updated on Heroicons.
They added aria-hidden="true" + 8 new icons.

Thank you @quentin-bettoum ❤
I'll cut a new release with these. We're also tracking automating these upgrades here: https://github.com/mveytsman/heroicons_elixir/issues/6

@quentin-bettoum do you mind fixing the tests before I merge this https://github.com/mveytsman/heroicons_elixir/runs/5277134654?check_suite_focus=true

It should be good now.

0.3.2 released!

authors: mveytsman quentin-bettoum


text:
--pulseaudio option not working

Apologies in advance if this is a simple fix.
I'm running x11docker with
sudo ./x11docker -acpdf --hostipc --size="1920x1080" --homedir="myhomedir" --user="myuser" -- "-p 1935:1935" myimagename

(--hostipc seems to be required for using the x11grab input in ffmpeg, not sure if that's correct but it's a separate issue.)
My dockerfile extends x11docker/xfce, with the relevant lines being:
RUN sed -i "s/buster main/buster main contrib non-free/" /etc/apt/sources.list
RUN echo "deb http://http.debian.net/debian buster main contrib non-free" >> /etc/apt/sources.list
RUN apt-get update && apt-get install -y ffmpeg pulseaudio-utils pavucontrol

When I run x11docker as above, pavucontrol in the container tries unsuccessfully to connect to pulseaudio in the host, repeating every 5s.
In the container I have
$ echo $PULSE_SERVER
unix:/pulse/native

$ cat /etc/pulse/client.conf
# Connect to the host's server using the mounted UNIX socket
default-server = unix:/pulse/native
# Prevent a server running in the container
autospawn = no
daemon-binary = /bin/true
# Prevent the use of shared memory
enable-shm = false

as expected.
In the host I have
$ sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                    PORTS                      NAMES
a7482c40e7de        063534af197c        "env /bin/sh - /x11d…"   27 minutes ago      Up 27 minutes             0.0.0.0:1935->1935/tcp     x11docker_X101_04c384_mycontainername
$ getent group audio video
audio:x:29:pulse
video:x:44:

$ sudo docker inspect -f '{{ .Mounts }}' a7482c40e7de
[{bind  ~~~/x11docker/myhomedir /home/myuser  rw true rprivate}\
 {bind  /tmp/.X11-unix/X101 /X101  rw true rprivate}\
 {bind  /run/user/1000/pulse /pulse  rw true rprivate}\
 {bind  /~~~/.cache/x11docker/X101-myimagename/pulseclient.conf /etc/pulse/client.conf  rw true rprivate}\
 {bind  /usr/bin/docker-init /x11docker/tini  ro false rprivate}\
 {bind  /~~~/.cache/x11docker/X101-myimagename/share /x11docker  rw true rprivate}]
$ sudo docker inspect -f '{{ .HostConfig.GroupAdd }}' a7482c40e7de
[29 44]
$ sudo docker inspect -f '{{ .HostConfig.Devices }}' a7482c40e7de
[]

I add the devices info because of the comment here, but as I expected, adding "--device /dev/snd" after -- in the x11docker args doesn't change anything.
Running pulseaudio -k in the host after the container is up doesn't change anything.
The line load-module module-native-protocol-unix is in /etc/pulse/system.pa in both host and container.
Not sure what else could be the problem...

Thanks for reporting!
On the first glance I see one bug, not sure if that is the cause of the issue:
RUN sed -i "s/buster main/buster main contrib non-free/" /etc/apt/sources.list
RUN echo "deb http://http.debian.net/debian buster main contrib non-free" >> /etc/apt/sources.list

x11docker/xfce is based on debian stretch. With the commands above you get a mix of stretch and buster repositories, you don't replace the stretch line.
To have a clean base, rather change the Dockerfile of x11docker/xfce:
Replace:
FROM debian:stretch

with:
FROM debian:buster
RUN echo "deb http://deb.debian.org/debian buster non-free contrib" >> /etc/apt/sources.list

and build again.
A first test with another pulseaudio image on my system succeeds,  sound is working here.
Please try with a clean buster build again. I will check with buster, too, maybe something changed.

Thanks for the quick reply!
I've rebuilt x11docker/xfce as you recommend (moving the DEBIAN_FRONTEND export to the second line), and slimmed the testing dockerfile down to
FROM local_xfce:buster
RUN apt-get update && apt-get install -y ffmpeg pulseaudio pavucontrol --no-install-recommends

However, running pavucontrol still displays "Connection to Pulseaudio failed. Automatic retry in 5s", etc.
As further information, I am running Ubuntu 18.04 with Unity in the host. Also the pulseaudio version in host and container is now the same, pulseaudio 11.1.
Something like docker run -it -v "/run/user/$UID/pulse:/run/user/1000/pulse" thebiggerguy/docker-pulseaudio-example works fine for me. Can I know what image you are using to test pa with locally?

I managed to get pulseaudio working, but without being able to send sound to the host yet.
The fix was to replace --user="myuser" with --hostuser="myuser", so that the host pa server can accept connection from the container. Now pavucontrol in the container shows AudioIPC Server: AudioCallbackDriver in the Playback menu, same as in host.
After including lines
RUN apt-get install -y apt-transport-https ca-certificates curl gnupg --no-install-recommends
RUN apt-get install -y iceweasel

in the testing dockerfile, and in the container browsing to eg http://www.szynalski.com/tone-generator/ , I'm not able to hear sound as yet though. (For some reason youtube refuses to play buffered video either, but I'm sure I've just forgot to include a dependency...)

After restarting, I was able to confirm streaming video + audio from the container, so that's good enough for me. Not being able to receive sound from the container was likely due to host and container being different users, but it's not an issue any more. Thanks and feel free to close this issue :)

Good to hear you got it working!
Clever that you found out the issue is due to different host user/container user, I just missed that. I will look if I find a solution for that.
Formerly I set up pulseaudio in container with a TCP connection, but switched to sharing pulseaudio unix socket due to some annoying issues with the pulseaudio TCP module. Also, sound over unix socket is more performant.
Though, the TCP solution does not have issues with different users.

--hostipc seems to be required for using the x11grab input in ffmpeg, not sure if that's correct but it's a separate issue

Feel free to open a ticket for this.

authors: ajhamwood mviereck


text:
onOpen event fires twice

When I open the chat application. I can see in the console that the on Open event fired twice:

I an also see two websocket connection opened in the browser:

By the way, the msg.to="/chat.nsf/*" works in the chat application.

fires twice because there are two open websocket connections on that page
(one for pbar example).
On Tue, Nov 1, 2016 at 12:10 PM, Csaba Kiss notifications@github.com
wrote:

When I open the chat application. I can see in the console that the on
Open event fired twice:
[image: image]
https://cloud.githubusercontent.com/assets/2583367/19896818/3b5c5de4-a01b-11e6-9676-348cb5304659.png
I an also see two websocket connection opened in the browser:
[image: image]
https://cloud.githubusercontent.com/assets/2583367/19896847/59a7a312-a01b-11e6-81de-acee2271150a.png
By the way, the msg.to="/chat.nsf/*" works in the chat application.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mwambler/xockets.io/issues/31, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEI46XWXhRvs3eB-kDrTwaEMsXGJl--Jks5q52SGgaJpZM4KmRDL
.

--
Mark Ambler

Oh, ok, It's by design.  :+1:

authors: csakis mwambler


text:
ionic Keyboard plugin

Hi i think it would be nice to add this plugin on startup https://github.com/driftyco/ionic-plugin-keyboard because we always need it

+1

repo: mwaylabs/generator-m


text:
Fix Xcode 6 LLVM compiler error

See: http://stackoverflow.com/questions/24922913/too-many-arguments-to-function-call-expected-0-have-3
By default, Xcode now enforces strict checking of objc_msgSend calls. When trying to integrate PromiseKit as a dependency for a new pod I'm creating, I was unable to compile because of this issue.

Hi, any plan when this will be available through cocoapods ? :)

@mxcl +1 on this, annoying to modify pod source each time I update just for this right now

Sorry, I've been offline. Reviewing now.

I'm tempted to remove the promiseSegue stuff altogether. It's way too hacky and potentially dangerous and I'm not convinced anyone uses it.
It was a PR a while ago.

authors: dmiotti krzysztofzablocki mxcl stevenp

repo: mxcl/PromiseKit


text:
Feature Request: Rudder Position Indicator

Would it be possible to add an option on one of the linear gauge widgets to only show a single mark vs. coloring from the minimum value up to the value?  The application for this would be a ruder angle indicator.

Added a new "Color" option on linear gauges, to allow no progress bar (and thickens the needle a bit) a0af75f8d745cd626365e9354830710b44dbdec5
Note will need to wait for next version to be released :)

repo: mxtommy/Kip


text:
Feature Request: Add BookmarkService

Packages/Tools

[ ] at_identifier
[ ] nsid
[ ] at_uri
[ ] xrpc
[ ] multiformats
[ ] atproto_core
[ ] atproto
[x] bluesky
[ ] bluesky_text
[ ] bluesky_cli
[ ] bluesky_post
[ ] others

Proposal

#911

Risks

https://github.com/bluesky-social/atproto/pull/1771


text:
Mybatis automatically adds a LIMIT clause to the statement

In some cases, mybatis automatically added a LIMIT clause to my statement when the query was executed, resulting in the data I received was missing.
here is my mybatis query:

select id, name, parent_id, url, perms, type, icon, order_num, create_by, create_time, last_update_by, last_update_time, del_flag from sys_menu

here is app log query:
==>  Preparing: select id, name, parent_id, url, perms, type, icon, order_num, create_by, create_time, last_update_by, last_update_time, del_flag from sys_menu LIMIT ?
==> Parameters: 2(Integer)
I am using MyBatis 3.5.5

You should check to see if it exists paginationintercepter

@dongbaibai I don't use the Mybatis interceptor, the LIMIT clause is sometimes automatically added, sometimes not

Hello @Hublxc118 ,
MyBatis never adds LIMIT automatically.
You must be using some 3rd party extension like page helper, mybatis plus, etc..

Hello @harawata ,
I don't use pagination intercepter for this case.
This is the statement I get the data back:
private List findTree(String userName){
return sysMenuExMapper.selectAll();
}
This is the Mapper file:
public interface SysMenuExMapper {
List findByUserName(@Param("userName")  String userName);
List<SysMenu> findRoleMenus(@Param("roleId") Long roleId);

List<SysMenu> selectAll();

}

@Hublxc118 ,
If you could create and share a small project like these that replicate the problem, I would take a look.

No reply. This cannot be a MyBatis issue.

authors: Hublxc118 dongbaibai harawata


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/91840

TagBot fix

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/92425


text:
Does this support browser environment ?

I wrote xhtml2pug library to convert pug to html. I've test it in codesandbox and it works well https://codesandbox.io/s/vibrant-clarke-whgj4?file=/src/index.js but I can't start with parcel or vite.
Do you know how to resolve this problem?

Hey! Thank you for reporting this, I have not tried to build it with Parcel yet. Will try today/tomorrow and get back to you.

Hey! Thank you for reporting this, I have not tried to build it with Parcel yet. Will try today/tomorrow and get back to you.

In the meantime, could you show some error messages or other output you get when the build fails?

In the meantime, could you show some error messages or other output you get when the build fails?

Ok, just tried to build with Parcel the same app you have in codesandbox. Locally everything works fine, let's see the errors you get on your side.
The app I'm building, just in case:
import { convert } from "xhtml2pug";

const inputHTML = `

Hello Vanilla!

  We use the same configuration as Parcel to bundle this sandbox, you can find more
  info about Parcel
  here.

`

const pug = convert(inputHTML)

console.log(pug)

Ok, just tried to build with Parcel the same app you have in codesandbox. Locally everything works fine, let's see the errors you get on your side.
The app I'm building, just in case:
import { convert } from "xhtml2pug";

const inputHTML = `

Hello Vanilla!

  We use the same configuration as Parcel to bundle this sandbox, you can find more
  info about Parcel
  here.

`

const pug = convert(inputHTML)

console.log(pug)

Well.... idk what the shit happens. But now it's working...
But parcel polyfills stream api with stream-browserfily.

But sometimes he cannot do this and throw error in StreamTokinizer.

Well.... idk what the shit happens. But now it's working...
But parcel polyfills stream api with stream-browserfily.

But sometimes he cannot do this and throw error in StreamTokinizer.

Hm... ok, good that it works now, but Parcel should not even bundle stream polyfills as you are not using them, stream modules in Hytax are completely decoupled. I'll figure this out, maybe I messed up the way I expose the modules.
In the meantime you can change hyntax imports in your package to be:
const tokenize = require('hyntax/lib/tokenize')
const constructTree = require('hyntax/lib/construct-tree')

This way Parcel will not bundle anything extra for sure. Could you try and tell me if it works for you?

Hm... ok, good that it works now, but Parcel should not even bundle stream polyfills as you are not using them, stream modules in Hytax are completely decoupled. I'll figure this out, maybe I messed up the way I expose the modules.
In the meantime you can change hyntax imports in your package to be:
const tokenize = require('hyntax/lib/tokenize')
const constructTree = require('hyntax/lib/construct-tree')

This way Parcel will not bundle anything extra for sure. Could you try and tell me if it works for you?

Yep, i'll try.

Yep, i'll try.

I not sure help it or not.

Could you plz don't close issue? I'll try working on this.
Also thanks, you're the best.

I not sure help it or not.

Could you plz don't close issue? I'll try working on this.
Also thanks, you're the best.

No problem, I'll keep the issue open 👍
Seems like it helped, there are not plyfills in the bundle, so you should not get that error anymore and your package bandle should be a bit smaller now as a side effect.

No problem, I'll keep the issue open 👍
Seems like it helped, there are not plyfills in the bundle, so you should not get that error anymore and your package bandle should be a bit smaller now as a side effect.

Thanks, now my home project can work without backend :tada:
https://html2pug.now.sh/

Thanks, now my home project can work without backend :tada:
https://html2pug.now.sh/

authors: dimensi mykolaharmash

repo: mykolaharmash/hyntax


text:
Kristupenis ir Mygolas nedirba

labai mazai prisideda prie projekto. pagrinde tik mes su Sarunu pahalinam

axujiel vps

pradejo dirbt

repo: mykolas-milasius/ImmunityTD


text:
fix(smart-mode): Consider untracked files

closes #104
closes #112

It's awkward to say, but I was able to reproduce neither #104 nor #112.
Do you think there is still a case when untracked files are needed to be processed separately?

Fair point - this was superseded by the rendered folder missing application detection.

authors: Zebradil fritzduchardt

repo: mykso/myks


text:
Error Installing paystack on Erpnext Version-14

I have solved this problem and sent a pull request accordingly "https://github.com/mymi14s/frappe_paystack/pull/3"
The problem was with the "create_payment_gateway" in "/home/harry2/frappe_paystack/frappe_paystack/frappe_paystack/doctype/paystack_settings/paystack_settings.py".
While the "create_payment_gateway" method has been moved to "payments.utils" it was still called from "frappe.integrations.utils" hence the error. However, this has been modified in my pull request and hopefully, it would be accepted and merged. Thank you.

Version-14 release is now available.


text:
🛑 Hacker News is down

In 6b95b42, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 244 ms

Resolved: Hacker News is back up in ce0963f.

repo: mymovielist/uptime


text:
JSON outputter cannot handle CCG categories

Example:
$ java -cp "*" jigg.pipeline.Pipeline -annotators "ssplit,kuromoji,jaccg" -outputFormat json
Loading parser model in ccg-models/parser/beam=64.ser.gz ...done [5.2 sec]
> 東京は晴れです
Exception in thread "main" com.fasterxml.jackson.core.JsonParseException: Unrecognized character escape 'N' (code 78)
 at [Source: {".tag":"root",".child":[{".tag":"document","id":"d0",".child":[{".tag":"sentences",".child":[{".tag":"sentence","text":"東京は晴れです","id":"s0","characterOffsetBegin":"0","characterOffsetEnd":"7",".child":[{".tag":"tokens","annotators":"kuromoji",".child":[{".tag":"token","id":"s0_0","form":"東京","characterOffsetBegin":"0","characterOffsetEnd":"2","pos":"名詞","pos1":"固有名詞","pos2":"地域","pos3":"一般","cType":"*","cForm":"*","lemma":"東京","yomi":"トウキョウ","pron":"トーキョー"},{".tag":"token","id":"s0_1","form":"は","characterOffsetBegin":"2","characterOffsetEnd":"3","pos":"助詞","pos1":"係助詞","pos2":"*","pos3":"*","cType":"*","cForm":"*","lemma":"は","yomi":"ハ","pron":"ワ"},{".tag":"token","id":"s0_2","form":"晴れ","characterOffsetBegin":"3","characterOffsetEnd":"5","pos":"名詞","pos1":"一般","pos2":"*","pos3":"*","cType":"*","cForm":"*","lemma":"晴れ","yomi":"ハレ","pron":"ハレ"},{".tag":"token","id":"s0_3","form":"です","characterOffsetBegin":"5","characterOffsetEnd":"7","pos":"助動詞","pos1":"*","pos2":"*","pos3":"*","cType":"特殊・デス","cForm":"基本形","lemma":"です","yomi":"デス","pron":"デス"}]},{".tag":"ccg","annotators":"jaccg","root":"s0_sp0","id":"s0_ccg0","score":"319.1745958328247",".child":[{".tag":"span","id":"s0_sp0","begin":"0","end":"4","symbol":"S[mod=nm,form=base,fin=f]","rule":">","children":"s0_sp1 s0_sp4"},{".tag":"span","id":"s0_sp1","begin":"0","end":"2","symbol":"S[fin=f]/S[fin=f]","rule":"<","children":"s0_sp2 s0_sp3"},{".tag":"span","id":"s0_sp2","begin":"0","end":"1","symbol":"NP[mod=nm,case=nc,fin=f]","children":"s0_0"},{".tag":"span","id":"s0_sp3","begin":"1","end":"2","symbol":"(S[fin=f]/S[fin=f])\NP[mod=nm,case=nc,fin=f]","children":"s0_1"},{".tag":"span","id":"s0_sp4","begin":"2","end":"4","symbol":"S[mod=nm,form=base,fin=f]","rule":"<","children":"s0_sp5 s0_sp6"},{".tag":"span","id":"s0_sp5","begin":"2","end":"3","symbol":"NP[mod=nm,case=nc,fin=f]","children":"s0_2"},{".tag":"span","id":"s0_sp6","begin":"3","end":"4","symbol":"S[mod=nm,form=base,fin=f]\NP[mod=nm,case=nc,fin=f]","children":"s0_3"}]}]}]}]}]}; line: 1, column: 1609]
	at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1581)
	at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:533)
	at com.fasterxml.jackson.core.base.ParserMinimalBase._handleUnrecognizedCharacterEscape(ParserMinimalBase.java:510)
	at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._decodeEscaped(ReaderBasedJsonParser.java:2208)
        ...

The problem seems in escaping backslash \ in CCG categories like N\N.

Sorry for the inconvenience. And thanks for your notification.
This problem seems to be related with a rendering method of Jackson.
I'll modify it soon.

I modified this bug with escaping a backslash \ to \\.
Example:
$ echo "東京は雨です。" | java -cp "./target/*" jigg.pipeline.Pipeline -annotators "ssplit,kuromoji,jaccg" -outputFormat json
Loading parser model in ccg-models/parser/beam=64.ser.gz ...done [4.0 sec]
{
  ".tag" : "root",
  ".child" : [ {
...
          }, {
            ".tag" : "span",
            "id" : "s0_sp7",
            "begin" : "3",
            "end" : "4",
            "symbol" : "S[mod=nm,form=base,fin=f]\\NP[mod=nm,case=nc,fin=f]",
            "children" : "s0_3"
          }, {
...
}

authors: nozyh tomeken-yoshinaga

repo: mynlp/jigg


text:
too many scala files to compile

I have a large, old database with many schemas (>20) and many un-documented dependencies between them. Therefore I need to generate scala code for all of them as I don't know what will be used and what won't. With Beans off, this generates around 2200 scala files which compiles perfectly. But if I turn beans on, it generated 5437 files (in one directory ) and that fails to compile,  with an error from the compiler, not the code being compiled. See below for the error. I don't know what the root cause of this is, but I wondered if the code generation mechanism could be modified to create a separate directory for each schema. Then no one directory would have too many files. I don't know if its the number of files per directory, or just the total number of files that is breaking it though. I tried issuing separate export commands, putting each schema in is own directory and package, but then dependencies between schemas break because needed classes from other schemas are not imported properly. I'm open to any ideas about how to get this to compile. Thanks.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Web Services Project
[INFO]    task-segment: [compile]
[INFO] ------------------------------------------------------------------------
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [resources:copy-resources {execution: default-copy-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] [yuicompressor:compress {execution: default}]
[INFO] nb warnings: 0, nb errors: 0
[INFO] snapshot com.mysema.querydsl:querydsl-apt:2.3.0.BUILD-SNAPSHOT: checking for updates from defancea
[WARNING] repository metadata for: 'snapshot com.mysema.querydsl:querydsl-apt:2.3.0.BUILD-SNAPSHOT' could not be retrieved from repository: defancea due to an error: Authorization failed: Access denied to: http://defrancea-mvn-dep.goo
[INFO] Repository 'defancea' will be blacklisted
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [scala:compile {execution: default}]
[INFO] Checking for multiple versions of scala
[INFO] includes = [/*.scala,/*.java,]
[INFO] excludes = []
[INFO] /home/khoran/development/web_services/src/main/scala:-1: info: compiling
[INFO] Compiling 5437 source files to /home/khoran/development/web_services/target/classes at 1327869844590
[ERROR] error: java.lang.StackOverflowError
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:143)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)

 1000 lines ommitted

INFO]    at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]
[INFO] java.lang.reflect.InvocationTargetException
[INFO]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO]   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[INFO]   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO]   at java.lang.reflect.Method.invoke(Method.java:616)
[INFO]   at org_scala_tools_maven_executions.MainHelper.runMain(MainHelper.java:161)
[INFO]   at org_scala_tools_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
[ERROR] Caused by: java.lang.StackOverflowError
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:143)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)

 1000 lines ommitted

INFO]    at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO]   at scala.tools.nsc.symtab.Scopes$Scope.enterInHash(Scopes.scala:144)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] wrap: org.apache.commons.exec.ExecuteException: Process exited with an error: 240(Exit value: 240)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 39 seconds
[INFO] Finished at: Sun Jan 29 12:44:39 PST 2012
[INFO] Final Memory: 48M/335M
[INFO] ------------------------------------------------------------------------

You should be able to verify if the classes per folder really affects the issue by just moving a part of them into a different folder. As Scala is not strict about the folder matching the package, this should work.

Also try to change the memory settings for the Scala compiler plugin in Maven.

Good point. I split all the generated files into directories with only 200 files per directory and increased the memory  (-Xmx) to 8GB. On start up it allocated 4GB of virtual memory, but only used 300MB before spitting out the same error as above. Perhaps it sucks in everything in the same package, regardless of the directory? I could try putting each of these sub directories into a separate package and then importing all of them into every file, just to see. Thanks for your help.

ok, split everything into 27 different packages (200 files per package), added import statements, and increased memory to 8GB and it compiled successfully. So its how many files per package that seems to be the important thing.

Ok, I will see how the schema to package mapping could be added.

Great! Thanks. This would also help prevent potential name conflicts between schema members, since they are in a different namespace. I don't think my database has any such issues though because the search path has always included every schema anyway. Thanks for your work on this project, strongly typed queries are such a great idea!

Follow up handled here : https://github.com/mysema/querydsl/issues/92

Fixed : https://github.com/mysema/querydsl/issues/92
Could you verify that it works for you? You can use the latest snapshot.

Timo,
I tried this option but it didn't seem to do anything. I removed all
my querydsl jars from the maven repo to make sure it was grabbing the
latest BUILD-SNAPSHOT. It still generates all the classes in one
directory and does not add any schema information to the package name.
Here is my plugin config:

2.9.1
2.3.0.BUILD-SNAPSHOT

UTF-8
${project.build.sourceEncoding}

1.2-m1
scaladocs/
http://scala-tools.org/mvnsites/liftweb

......

com.mysema.querydsl
querydsl-maven-plugin
2.3.0

           <configuration>
             <jdbcDriver>org.postgresql.Driver</jdbcDriver>
             <jdbcUrl> jdbc:postgresql://postgres.us.grn:5432/gr_database</jdbcUrl>

             <jdbcUser>xxxxxxx</jdbcUser>
             <jdbcPassword>xxxx</jdbcPassword>

             <packageName>net.globalrecordings.gr_database</packageName>
             <targetFolder>${project.basedir}/src/main/scala</targetFolder>
             <createScalaSources>true</createScalaSources>

             <schemaPattern>${schema}</schemaPattern>
             <exportBeans>true</exportBeans>
             <schemaToPackage>true</schemaToPackage>
           </configuration>
           <dependencies>
        <dependency>
         <groupId>postgresql</groupId>
         <artifactId>postgresql</artifactId>
         <version>9.0-801.jdbc4</version>
        </dependency>
             <dependency>
              <groupId>com.mysema.querydsl</groupId>
              <artifactId>querydsl-scala</artifactId>
              <version>${querydsl.version}</version>
             </dependency>
             <dependency>
              <groupId>org.scala-lang</groupId>
              <artifactId>scala-library</artifactId>
              <version>${scala.version}</version>
            </dependency>
          </dependencies>
		 </plugin>

The ${schema} variable is set on the command line, like so:
mvn querydsl:export -Dschema=languages
Here is the start of a generated file:
package net.globalrecordings.gr_database
import com.mysema.query.types._
import com.mysema.query.scala._
import com.mysema.query.types.PathMetadataFactory._;
import com.mysema.query.scala.sql.RelationalPathImpl
import com.mysema.query.sql._
Am I missing something? Thanks.
Kevin
On Sun, Feb 05, 2012 at 02:25:19AM -0800, Timo Westkämper wrote:

Fixed : https://github.com/mysema/querydsl/issues/92
Could you verify that it works for you? You can use the latest snapshot.

Reply to this email directly or view it on GitHub:
https://github.com/mysema/querydsl/issues/91#issuecomment-3816783

You need to update the version of the plugin as well.

Ok, that did it. However it fails to compile with:
[INFO] Compiling 5522 source files to /home/khoran/development/gr_database_dsl/target/classes at 1328560758305
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] wrap: org.apache.commons.exec.ExecuteException: Process exited with an error: 137(Exit value: 137)
Not a very helpful error. I'll keep looking to see what else I can find out.

Great. Could you also confirm that the schema distribution worked?

Timo,
I'm not sure what you mean by 'distribution'. A different sub
directory and package was created for each schema, and all references to
other generated classes where fully qualified. Since the schema pattern
mechanism is not powerful enough to match an arbitrary list of schemas,
I run mvn querydsl:export once for each schema. That means that each run
only ever sees one schema at a time. Hopefully that covers what you
wanted, else let me know. Thanks.
Kevin
On Mon, Feb 06, 2012 at 11:14:58PM -0800, Timo Westkämper wrote:

Great. Could you also confirm that the schema distribution worked?

Reply to this email directly or view it on GitHub:
https://github.com/mysema/querydsl/issues/91#issuecomment-3843679

authors: khoran timowest

repo: mysema/querydsl


text:
Great work!!!

How to use in C#, thanks!

Sorry, can not be used in C#, this is for web development, if you want use in C#, use official Windows app development - UWP app developer.

Thanks.

repo: myxvisual/react-uwp


text:
Fix Cargo.toml formatting error and refactor files

Fix Cargo.toml parsing error

'alpha' causes error in package version

Refactoring main and access_doc files

ok

authors: Writtic myyrakle

repo: myyrakle/rustywiki


text:
The drone will suddenly soar high when taking off.

When the drone takes off, it will suddenly rush very high and then descend to the set position. How can I ensure that it takes off at a certain height and does not exceed the set position?

Hi. It is been years since I used this package. So I hope it still works. For your issue, you may need to tune the geometric controller gains to have the desired response.

authors: mzahana zhouleiqiang


text:
the weight of ViT/L 14

Thanks for your wonderful work.  Can you share the weigh of ViT/L 14? since coop do not have ViT/L 14, dim=768

Hi, thx for reaching out.
For TTA model, we do not user ViT-L/14. We use ViT-B/16.

For reward model, when using ViT-L/14, we use the original models from openai withot further tuning.

Close due to inactivity. Feel free to re-open.

repo: mzhaoshuai/RLCF


text:
MZmine 3 for GC-MS data?

Basic information

My operating system:  Monterey 12.5, Mac
My MZmine version: 3.2.3

**What happened:**Confusing workflow for GC-MS and failure to obtain SD
I have downloaded this version about 6 times... to see if there is a bug in the version I had... But I haven't been successful so far.
I want to use MZmine 3.2.3 to process some GC-MS experiments, unsuccessfully.
The workflow I am using:

load mzML files
Mass detection:  Centroid, Noise Level 2E2
feature detection:  LCMS:  ADAP module,
min group size of scans: 8
Group intensity threshold: 2E2 (same as noise level)
Min highest intensity:  6E2 (three times the noise level)
scans accuracy (0.5 m/z or 300 ppm as it is low res)
Chromatogram deconvolution:  I use chromatogram resolver: ADAP resolver
S/N threshold:  4
S/N estimator Wavelet Coeff SN (peak Wave mult. 3 (defalut))
min feature height:  200
coefficient/area threshold:  200
peak duration range:  0.01 to 0.15
RT wavelet range:  0.00 to 0.2

I obtain better chromatogram deconvolution using the local minimum resolver (the form of the peaks), yet less detected features.

Spectral deconvolution:  Multivariate curve deconvolution
Chromatograms (the ones from the deconvolution selected in selected files)
Peaks (the ones from the chromatogram builder in selected files).
Deconvolution window width (min):  0.2
Retention time tolerance (min) 0.02
Min Number of Peaks:  1
Adjust Apex:  False

But then when I tried to evaluate in Show preview, nothing is there to see. I thought that I have selected the files reversed, but then when selected, nothings is there to see.  When using the other method for Spectral deconvolution, it reports an error.

So my questions are:  is MZmine 3 ready for GC-MS?  If I have to go back to 2.53, java is preventing to run the program (already tried)....

Hi, I used the latest MZmine 3.2.8 for windows to analyse my GC-MS data and encountered exactly the same problem as @gistamayo described. May I know if you @gistamayo  found the solution already? I have also a question for the developer if this Mzmine version is already optimized for GC-MS data?

@asmirn1 @du-lab Could you check this issue please?

@MuhammadRizaludin @gistamayo
We have fixed a few errors with the Spectral Deconvolution a few days ago, but they are not in the release yet.
Could you try the pre-release version and let us know if you still having the issue?
https://github.com/mzmine/mzmine3/releases/tag/Development-release
Alex

authors: MuhammadRizaludin asmirn1 gistamayo tomas-pluskal