text:
Results table names all additional unnamed columns "?column? (1)" and conflates their output

Describe the bug
If a query returns more than two unnamed columns, the results table mistakenly uses the values from only the last column for all the unnamed columns after the first.

To Reproduce
Steps to reproduce the behavior:

In a .sql file (the default connection log is excellent)
Add the SQL: "SELECT 1, 2, 3;"
Run on a connection
Observe: results table names the column headers:  "?column?",  "?column? (1)",  "?column? (1)"
Observe: results row shows values: 1, 3, 3. (The first 3--in the second column--is unexpected)

Expected behavior

The results table shows three column headers: "?column?",  "?column? (1)",  "?column? (2)"
The single results row shows values 1, 2, 3.

Screenshots
Attached showing "3" as wrong value in middle column of results table; column header wrong for last column in results table.
Desktop (please complete the following information):

SQLTools Version: v0.28.1
VS Code Version: 1.85.1
OS: macOS (local w/ DevContainer); GitHub Codespace
Driver:

[x] PostgreSQL/Cockroach 0.5.2

Database version:

PostgreSQL v16.1

This is a result of PostgreSQL's naming of anonymous columns or aggregate functions:
postgres=# select sum(a), sum(b), sum(c) FROM (select 1 a, 2 b, 3 c);
 sum | sum | sum
-----+-----+-----
   1 |   2 |   3
(1 row)

Other engines may generate distinct column names with aggregate functions:
sqlite> select sum(a), sum(b), sum(c) FROM (select 1 a, 2 b, 3 c);
sum(a)|sum(b)|sum(c)
1|2|3

I don't know if the columns names will always be distinct, and the error can be induced by forcing the columns to collide:
SELECT 1 AS count, 2 AS count, 3 AS count;

repo: mtxr/vscode-sqltools


text:
Tab's name after running query

Describe the bug
After running a query, and creating a tab for its result, the tab's name is getting huge. As I could see it is named as the query code. So, bigger queries are resulting in bigger names.
To Reproduce
Steps to reproduce the behavior:

Just run any query
See the tabs name

Expected behavior
Tab name should be something cleaner. Maybe "Result" or anything like that I guess would work better.
Or limit the number of char
Screenshots

Desktop (please complete the following information):

SQLTools Version [e.g. v0.23.0]
VSCode Version: [e.g 1.50.1]
OS: [Windows]
Driver:

[x] PostgreSQL/Redshift

+1
I work on queries having >400 lines and I really cannot orient myself among the different result set tabs.
Resul#1 - Result#n would be perfectly fine. Nice to have would be to add possibility to rename the tab or take just 1st line of query where I cann add some coment that would be displayed as a header.

Fixed by #774. Pending release

source: gharchive/issue

authors: Odwerneh miiguelkf mtxr

license: MIT

license_type: permissive

license_source: github-api


text:
Added spanish dictionary

We added a spanish :es: translation of the emoji dictionary :smile: :dancer:

@muan Any thoughts or/and updates? I would like to see this feature and start working on ru_RU.

source: gharchive/pull-request

authors: beeva-nievesabalos dimabory

repo: muan/emojilib

license: mit

license_source: bigquery


text:
Recorded video freezes while playing  at consecutive intervals

when I record video to node js it freezes while playing, recording audio and video from the remote side and audio-only from local side.
I am choosing streams like these
var arrayOfStreams = [localStream,remoteStream];
recorder = RecordRTC( arrayOfStreams, {
type: 'video'
});

Any solution?

Any solution?

repo: muaz-khan/RecordRTC


text:
Add input-specific propType.source type

Most of the current sources read HTML values / attributes, but for input elements it is sometimes needed to get the actual "current" value from the JS API, since it could have been changed before the component was initialized.
Example; a text input could get auto-filled, but the getAttribute('value') returns the server-rendered value, which is outdated.
Proposal:
// when `name` is given, the `target` should be the form
// it will then use the `FormData` to access the values
// this supports cases where multiple elements share the same `name` attribute (like checkboxes)
propType.source({ type: 'form', target: 'formRef', name: 'choices');

// or a simple way to extract a value from a single form element
propType.source({ type: 'form', target: 'inputRef' });

Specifications
target is input with type="text|number|date|password|...", textarea or select
Return its value.
<input type="text" />
<input type="number" />
<input type="date" />
<textarea></textarea>
<select> ... </select>

propType.string.source({ type: 'form', target: 'inputRef' })
propType.number.source({ type: 'form', target: 'numInputRef' })
propType.date.source({ type: 'form', target: 'dateInputRef' })
propType.string.source({ type: 'form', target: 'textareaRef' })
propType.string.source({ type: 'form', target: 'selectRef' })

Note: the type should support any type that we don't support specifically in one of the other cases below.

target is input with type="checkbox"
Detect the propType of the prop

when boolean, return the checked property (either true or false)
else (mostly string), return the value when the checkbox is checked

<input data-ref="input" type="checkbox" value="foo" />
<input data-ref="inputChecked" type="checkbox" value="foo" checked />

propType.boolean.source({ type: 'form', target: 'inputRef' }) // false
propType.string.source({ type: 'form', target: 'inputRef' }) // undefined
propType.boolean.source({ type: 'form', target: 'inputCheckedRef' }) // true
propType.string.source({ type: 'form', target: 'inputCheckedRef' }) // foo

target is select with multiple
Use the selectedOptions to return an Array of the values.
We should expect a propType.array here, if it's not we should log an Error, but still convert the values to the requested data type (e.g. comma-separated string).
<select multiple> ... </select>

propType.array.source({ type: 'form', target: 'selectRef' }) // ['foo', 'bar']
propType.string.source({ type: 'form', target: 'selectRef' }) // 'foo,bar' + error log

target is input with type="file"
We make use of the files property to return a FileList.

When specified propType.array, we return that list as an Array.
When specified propType.object, we return the first File item – and log an Error when it could accept multiple.

<input data-ref="input" type="file" />
<input data-ref="inputMultiple" type="file" multiple />

propType.array.source({ type: 'form', target: 'inputRef' }) // [File]
propType.object.source({ type: 'form', target: 'inputRef' }) // File
propType.array.source({ type: 'form', target: 'inputMultipleRef' }) // [File, File, File]
propType.object.source({ type: 'form', target: 'inputMultipleRef' }) // [File] + error log
// anything else = undefined + error log

target is form
Use the FormData api to retrieve the value.

When name option is present, return the matching FormData entry
When the name option is omitted, return the complete FormData object – and log an Error when propType.object is not specified.

Using this method, we cannot detect if a field can or will appear multiple time (e.g. a multiple select, or checkboxes). Unless specified otherwise, we will use the getAll, and depending on the propType we return an Array or stringified version.
<form>
  <input name="firstName" type="text" />
  <textarea name="description"></textarea>
  <select name="preference"> ... </select>

  <input name="optionA" type="checkbox" />
  <input name="optionB" type="checkbox" checked />
  <input name="choices" type="checkbox" value="apple" />
  <input name="choices" type="checkbox" value="banana" checked />

  <select name="candidates" multiple> ... </select>

  <input name="photo" type="file" />
</form>

// complete form
propType.object.source({ type: 'form', target: 'formRef'); // FormData

// individual fields
propType.string.source({ type: 'form', target: 'formRef', name: 'firstName');
propType.string.source({ type: 'form', target: 'formRef', name: 'description');
propType.string.source({ type: 'form', target: 'formRef', name: 'preference');

propType.boolean.source({ type: 'form', target: 'formRef', name: 'optionA'); // false
propType.boolean.source({ type: 'form', target: 'formRef', name: 'optionB'); // true
propType.array.source({ type: 'form', target: 'formRef', name: 'choices'); // ['banana']

propType.array.source({ type: 'form', target: 'formRef', name: 'candidates'); // ['John', 'Jane']

propType.object.source({ type: 'form', target: 'formRef', name: 'photo'); // File

Unclear

What to do with the indeterminate setting of a checkbox? return undefined ?

Good proposal. I think we could do things based on the propType:

For a checkbox is the propType is boolean return the checked value. If it's a string return the checked value if the checkbox is checked, otherwise return undefined.
Agree about your suggestion about Arrays. Maybe we should show an error when there are multiple values, but the propType is not an Array?
What about files? There is currently no propType for that. Or we ignore this, because we probably never need it.

What should happen if you specify a name, but the target is not a <form>?

What should happen if you specify a name, but the target is not a ?
log an error, and return undefined?

For a checkbox is the propType is boolean return the checked value. If it's a string return the checked value if the checkbox is checked, otherwise return undefined.
Sounds like a plan :)

Agree about your suggestion about Arrays. Maybe we should show an error when there are multiple values, but the propType is not an Array?
Could work as well, but what would we return in that case?

What about files? There is currently no propType for that. Or we ignore this, because we probably never need it.
Good one, we could support it with the value that would otherwise come out of the FormData.

Agree about your suggestion about Arrays. Maybe we should show an error when there are multiple values, but the propType is not an Array?
Could work as well, but what would we return in that case?

Let's do your proposal of a comma separated string

I updated the issue itself based on the above conversation, and added some clear examples.
There is one "unclear" thing remaining. But I feel we could already start the implementation.

although the browsers don't support this

What do you mean with "don't support" ?
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/checkbox#indeterminate_state_checkboxes
I think undefined might be a good option, since:

Note: If you submit a form with an indeterminate checkbox, the same thing happens as if the checkbox were unchecked — no data is submitted to represent the checkbox.

authors: ThaNarie ThijsTyZ

repo: mubanjs/muban


text:
Timer

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@Vaibhav202020 What is this issue about?
Please add details in the descriptive text.


text:
Cleaned Up / Finished Class.Java

Added toString
Added equals
Added Junit Test Cases

Yeah, I could not decide if we should change that or not. I agree with you feel free to change it and merge.

Fixed the comment. Merging now.

authors: cjnissle ianreger


text:
Gui image

make a screenshot and save it

Let me know if anything needs changed


text:
PhantomJs requires flags for HTTPS sites

Hey there,
I tried implementing this gem, but my site uses ssl encryption and PhantomJs requires the following flags to handle ssl sites (courtesy of Penthouse):
to run on HTTPS sites two flags must be passed in, directly after phantomjs in the call:
    --ignore-ssl-errors=true --ssl-protocol=tlsv1

I've tried digging through the PhantomJs gem but can't seem to find a solution for this, any thoughts?

Little more detail on this, here's the error that's thrown:
Error opening url 'https://www.example.com/': SSL handshake failed

I've added the recommended flags for PhantomJS via #16. I'll close this issue for now, but please feel free to reopen if the problem persists.

The problem persists on Heroku:
remote: -----> Preparing app for Rails asset pipeline
remote:        Running: rake assets:precompile
remote:        Phantomjs does not appear to be installed in /app/.phantomjs/1.9.8/x86_64-linux/bin/phantomjs, installing!
remote:        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
remote:        Dload  Upload   Total   Spent    Left  Speed
remote:        0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
remote:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
remote:        19 12.5M   19 2539k    0     0  14.7M      0 --:--:-- --:--:-- --:--:-- 14.7M
remote: 100 12.5M  100 12.5M    0     0  42.7M      0 --:--:-- --:--:-- --:--:-- 80.5M
remote:        Successfully installed phantomjs. Yay!
remote:        Removed temporarily downloaded files.
remote:        Error opening url 'https://example.com/': SSL handshake failed
remote:        Asset precompilation completed (8.04s)

It would be really nice to have it fixed because there is still no reliable way to activate mod_pagespeed on heroku!

@darmenise , I just tried this on one of our Heroic instances, and here are my results:
remote:        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
remote:        Dload  Upload   Total   Spent    Left  Speed
remote:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
remote:        100 12.5M  100 12.5M    0     0  32.7M      0 --:--:-- --:--:-- --:--:-- 32.7M
remote:        Successfully installed phantomjs. Yay!
remote:        Removed temporarily downloaded files.
remote:        Cache write: critical-path-css:/ ({:namespace=>"critical-path-css", :expires_in=>nil})
remote:        Dalli::Server#connect XXXXXXX.com:11211
remote:        Dalli/SASL authenticating as 6a59e1
remote:        Dalli/SASL: 6a59e1
remote:        Asset precompilation completed (7.07s)```

In my `critical_path_css.yml`, I'm using a `base_url` with a known working SSL certificate. Are you using the most up to date version of this gem, `0.3.1`?

One thing I still need to do is update PhantomJS, but barring that, I'm currently unable to replicate the SSL handshake issue.

I'm using the edge version actually. I'm also using a custom domain and Cloudflare, maybe something goes wrong there... But the SSL certificate is definitely working:

If you want I could privately give you more details.

Update: if I don't use the custom domain the SSL handshake is successful.
In other words if i put https://appname.herokuapp.com as base_url for production it works.
Maybe the problem is in some Cloudflare configuration..

Just tried your fix @darmenise and it worked for me as well. My company uses GoDaddy for our domain names, so maybe it's something to do with Heroku's SSL implementation. Regardless, using the base Heroku url seems to fix the issue!

That being said, I'm fine with the issue being closed if you're happy with the solution @michael-misshore

I'm glad to know that :-)
I'm still in trouble because my app uses subdomains and so I can't use that fix but it would be for another issue. This one I think it could be closed too.

Closed!

authors: bartboy011 darmenise michael-misshore

repo: mudbugmedia/critical-path-css-rails


text:
halfquake: buttons with grid, remove ledge or make it impossible

jace: I think it was in first HQ, you enter a large room with two lava pits which have buttons just above 'em
You're meant to backtrack a bit and press a button to have floors extended over the lava pits
First two playthroughs, I wasn't even aware of the button :P
There was barely one pixel wide ledge at the button and you were just able to jump out of it with pixel-precise jumps

make the ledge appear like this:
___
  /
/__________________________

repo: muddasheep/hqtrilogy

license: unlicense


text:
Expose mobile{Keyboard,Default}ViewIcon props from PickerToolbar

This PR closes #1693.

@Philipp91 Thanks for the pull request. Unfortunately, we can't accept it here. On-going work was moved to v5 in the main repository: https://next.material-ui.com/components/date-picker/.
I have transferred the linked issue to https://github.com/mui-org/material-ui/issues/23604.

repo: mui-org/material-ui-pickers


text:
Invalid hook call

If you use this component:
https://github.com/mui-org/material-ui/tree/master/docs/src/pages/getting-started/page-layout-examples/album
With this example project:
https://github.com/mui-org/material-ui/tree/master/examples/nextjs
You get:
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app

How do we fix?

Can you reproduce the issue on another computer?

@oliviertassinari I don't have another computer, but I can add that the problem shows up here:
./pages/_document.js:60
   7 | const sheets = new ServerStyleSheets();
  58 | const originalRenderPage = ctx.renderPage;
  59 |
> 60 | ctx.renderPage = () =>
  61 |   originalRenderPage({
  62 |     enhanceApp: App => props => sheets.collect(<App {...props} />),
  63 |   });

and if you remove everything from the bottom up to and including this line, it goes away.

@sorleone Something is wrong with your setup.

@sorleone how did you fix it?

same issue with Stepper component

authors: ThomasGHenry cdll oliviertassinari sorleone

repo: mui-org/material-ui


text:
Input type files for TextFields

Create optional type=file
Now it show the default button to insert a file on top.
I think it would be better if we could replace it with a iconButton and the Text entry is disable until a file is selected, after that the name of the file fill the TextField
This implementation shows how I think wath should be espected when you set type="file"
const [filesTimes, setFilesTimes] = useState();
const setTimes = evt => setFilesTimes(evt.target.files[0]);

        <input
          id="files"
          name="files"
          type="file"
          size="1"
          accept=".xlsx"
          onChange={setTimes}
          style={{ display: 'none' }}
        ></input>
        <label htmlFor="files">
          <div>
            <Grid container spacing={1} alignItems="flex-end">
              <Grid item>
                <TimerIcon color="primary"/>
              </Grid>
              <Grid item>
                <TextField disabled label="Tempos de Usinagem" value={filesTimes && filesTimes.name || ""} onClick={() => document.getElementById("files").click()}/>
              </Grid>
            </Grid>
          </div>
        </label>

it is a feature requests


text:
React Hook "useBabelRc" cannot be called at the top level

Following "Minimize bundle size" guide with my CRA (option 2 with babel-plugin-import), I get a red warning in VSCode on override(useBabelRc())within the file config-overrides.js, but no compilation error.
"React Hook "useBabelRc" cannot be called at the top level. React Hooks must be called in a React function component or a custom React Hook function".
However, I can access any of the components, the ThemeProvider to pass the dark mode works.
When building the code, I have a bundle size of 104kB. Not sure what it should be.

[ 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 😯
VSCode red warning and no compilation error.

Expected Behavior 🤔
No warning with VSCode.

Steps to Reproduce 🕹

yarn add -D babel-plugin-import
create & copy the file .babelrc.js from the doc in root folder
yarn add -D react-app-rewired customize-cra
create & copy config-overrides.js in root folder
=> red warning override(useBabelRC())
package.json: script.start: react-app--rewired start => no compilation error

My code & package.json
https://github.com/ndrean/navbar where you can check the settings.

Steps:

Context 🔦
Drying code with import { Button, TextField } from '@material-ui/core';.

Your Environment 🌎

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

@ndrean can you please create a small repro with just the changes related to the problem you are facing? It's a bit hard to follow how to reproduce at this moment. A simple create react app, with just your config and a page that imports some MUI component should be enough.

I  joined the github repo so you can open it in codesandbox by adding "box":

from https://github.com/ndrean/navbar do:
https://githubbox.com/ndrean/navbar

and you will see the problem in the "config-overrides.js". It is not a VScode pb (Atom displays the same error).

I'd say you should just suppress that eslint error in the config-overrides-.js file. Based on the documentation this is the correct usage, to it should be safe.
https://codesandbox.io/s/material-ui-issue-forked-q5g1n?file=/config-overrides.js:0-48

Yes, as mentioned, with or without the flag "eslint-disable react-hooks", it seems to works as I can use the one-liner multiple import argument. Most probably not related to MUI I believe.

Yeah, I would say is not related to MUI anyhow. Feel free to close the issue if there isn't anything else :)

authors: mnajdova ndrean


text:
[Pickers] Add ability to pass props to the open picker button icon

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

Summary 💡
The only way to modify the look and feel of the open picker button icon is by adding custom styles through a class on any of the parent components of the icon. This is due to the lack of any props being passed down to the icon itself.
Examples 🌈
Code Example
Source Code
Motivation 🔦
I am trying to make the open picker button smaller. I can make the IconButton component small using the OpenPickerButtonProps, but I cannot change the font size (or any other property) of the icon except through manually styling the icon by using a CSS selector to get at the svg component with a MuiSvgIcon-root class.

Hello, could I try working on this issue?
It seems like a new OpenPickerIconProps prop could be added to date / time Picker-related components (DatePicker, DesktopDatePicker, MobileDatePicker, etc) and finally to the internal KeyboardDateInput component.
KeyboardDateInput can then be modified so that the OpenPickerIcon renders with this new prop:
   <IconButton
            edge={adornmentPosition}
            data-mui-test="open-picker-from-keyboard"
            disabled={other.disabled || other.readOnly}
            aria-label={getOpenDialogAriaText(other.rawValue, utils)}
            {...OpenPickerButtonProps}
            onClick={openPicker}
   >
            <OpenPickerIcon {...OpenPickerIconProps} />     // <----- modified line
   </IconButton>

Hello.
I also looked for ways to change OpenPickerIcon and OpenPickerIconProps.
My solution.
https://codesandbox.io/s/wild-lake-5lb29

authors: BrianWhiting maksymrudiuk zenje


text:
[Autocomplete] Let developers determine the value that is set by clear

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Currently clear sets the value of an autocomplete to either null if multiple == false or [] if multiple == true. Depending on the shape of your values / options, this might not be desirable. But there is no way to change this.
For example I'm using an Option/Maybe container. Clearing an input should set the value to value: { _tag: "None" } instead of null.
Examples 🌈
No response
Motivation 🔦
No response

I agree with this, this would certainly helps me in my office work
+1 Upvoted

@florianbepunkt Thanks for the suggestion.
@oliviertassinari What do you think about this?

+1
Setting to null also cause troubles with yup, having to set a nullable or typeError validation. I want to customize the default behavior of my Autocomplete to an empty string

when i click next it is go next but my input value is empty.how to slve this?

In fact, as @otaviobps suggested, using reason argument of either onChange or onInputChange prop will do the job, and hence I will close this issue.
@nannu-coder Please create a separate issue with a codesandbox that clearly shows the error. You can fork this template (https://material-ui.com/r/issue-template-latest).

authors: ahmad-reza619 florianbepunkt hbjORbj nannu-coder otaviobps


text:
[Slider] should support setting colors not in the theme

Problem description
The style and sliderStyle properties in Slider don't actually affect the slider colors. They create a background-color box but the component colors remain unchanged from the ancestor theme. This is not a useful thing.
There are use-cases for needing to easily change the color, just like one can change an icon or fab color, without going through all the details of creating a new mui-theme just to wrap the slider.
Workarounds involving CSS aren't dynamic because the CSS is only loaded once. Workarounds involving finding the relevant divs and setting their colors don't work on the "knob" of the slider because the div is re-rendered, so the style (somehow) needs to be re-applied on every value change.
Thus, the only consistent workaround is to create a new dynamic theme just for the color change here, which seems to be a lot of code for such a little need.
Versions

Material-UI: 0.16.7

attempting to insert an alternate theme doesn't seem to work.
            <MuiThemeProvider muiTheme={getMuiTheme(sliderTheme)}>               <Slider className="current-time" min={0} max={state.duration} step={1} value={state.currentTime} {...sliderEvents}/>             </MuiThemeProvider>
and instead I end up with a slider with the default light theme's blue color instead.

Well, not a lot of code for the user, but a bit of execution code creating the alt theme. (I originally posted that it didn't work, but I'd not structured the alt theme correctly, so removed that as being my fault).
put this in your own theme file
export var replaceSliderTheme = function(posColor, negColor) {   console.log("replace", posColor, negColor);   var rv = {     spacing: spacing,     fontFamily: 'Roboto, sans-serif',     palette: {       primary1Color: posColor,       accent1Color: posColor,       disabledColor: negColor || fade(fullWhite, 0.3),       // (and rest of the colors being your original theme     }   }   return rv; }
then call it by
 const sliderTheme = replaceSliderTheme(myAltColor);
and
            <MuiThemeProvider muiTheme={getMuiTheme(sliderTheme)}>               <Slider className="current-time" min={0} max={state.duration} step={1} value={state.currentTime} {...sliderEvents}/>             </MuiThemeProvider>
so having a more direct mechanism would be nice, but this workaround suits my purposes without having to style-hack the divs.

being able to just pass a prop to the Slider component to change the color would be ideal.

We plan on migrating the component to the v1-beta branch. I'm closing the issue for #4793.

Heh - I hadn't realized the slider wasn't in "@next" yet. Is there a timetable on that because I'm gonna need it somewhat soon (working on a rewrite of a music player). :)

anyways, theme creation doesn't seem as heavyweight as i thought it would be, so if changing the theme instead of just passing in a property is the way to do it still, I'll be ok with that...but having properties certainly makes it easier.

authors: acroyear dehjli85 oliviertassinari


text:
[v0] Update react-event-listener to 0.6.2

Updating react-event-listener to prevent bringing in newest babel-runtime (https://github.com/oliviertassinari/react-event-listener/issues/86)

@oliviertassinari Thanks. I understand that v0 is no longer maintained but I am still working on upgrading to v1.

We will do a new release of v0.x by the end of the day.

Thanks you for the pull request.

Released as 0.20.2

authors: matthoffner oliviertassinari


text:
[TrapFocus] Guard against dropped memo cache

It's still potentially unsafe for concurrent mode but at least it's now safe against useMemo dropping the cache because we create our own cache via useRef.**
Also adds a warning for a potential memory leak since nodeToRestore.current could be unmounted while the modal is open. Though this is pretty unlikely to be an issue since you usually don't have many open modals.

Any idea how we could solve this?

What are you trying to solve?

What are you trying to solve?

I was wondering about the concurrent mode issue you have raised and added as a comment.

I was wondering about the concurrent mode issue you have raised and added as a comment.

Which is not an issue for the first 3 links. They obviously are meant to work in concurrent mode.
During a passive effect is too late for autoFocus.
I think I made it clear that it's unclear whether this is actually an issue in concurrent mode considering how the committed effects relate to the nodeToRestore usage.


text:
[test] Compensate for Circle CI's low performance

The changes are motivated by the performance issue Circle CI has had since Friday, test_unit-1 takes 6-7 minutes to run. It's x2 slower than usual. This leads to our slower tests to timeout 50% of the time.
Under normal conditions, the test in my env runs in 1min and in the CI, in about 2-3 minutes, hence the factor of x3. From what I recall, I don't have the faster machine in the team, I hope the 1s as the max timeout is enough for everybody. We might need to adjust it.
I have used this opportunity to remove the usage of a setTimeout(500ms) in a test case.

It's x2 slower than usual.

Do you know why that is?

It's x2 slower than usual.

Do you know why that is?

Do you know why that is?

@eps1lon I don't know. I couldn't find any lead.

Do you know why that is?

@eps1lon I don't know. I couldn't find any lead.


text:
[Button] Remove label span

Preview
https://deploy-preview-26666--material-ui.netlify.app/components/buttons/#main-content
Changes Summary

remove label classes and element from Button and LoadingButton
fix LoadingButton position: center styling because it rely on label before.

History
button > span > children exists as a workaround for flex container bug on button BUT not anymore, so this PR remove the span.

✅ Chrome 83+ (latest 90)
✅ Safari 11+ (latest 14)
✅ Edge
✅ Firefox 63 (latest 89)

https://github.com/philipwalton/flexbugs#flexbug-9

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

I believe that merging these changes means closing #26412. AFAIK, the solution was depending on the span, cc @eps1lon to confirm or not.

Regarding the transition when centered, the only solution I could find is adding the span back for the loading label. So it can also support more complex children

In my opinion, adding the span back is a no go as we learned from other components that the structure should not surprise people.
https://user-images.githubusercontent.com/18292247/121457129-61bc2480-c9d1-11eb-8c44-327fc160fec7.mov
Here, I think it is better. remove color from transition only for loadingPosition: 'center'. This way it does not affect other position.

There are two issues with the current animation: 1. the icons disappear instantly (which is quite visible), 2. the border-radius color isn't in sync with the text color. It doesn't feel as smooth as on https://github.com/mui-org/material-ui/pull/26666#pullrequestreview-680214403. Both fixed if we add a <span>.
Another issue of not using a span: this do no longer work:
      <LoadingButton
        onClick={handleClick}
        loading={loading}
        loadingIndicator="Loading..."
        variant="outlined"
      >
        Notifications <Badge>9</Badge>
      </LoadingButton>

PR: https://codesandbox.io/s/loadingbuttonstransition-material-demo-forked-0116b?file=/demo.js:1232-1443

HEAD: https://codesandbox.io/s/zch00?file=/demo.tsx

is a no go as we learned from other components that the structure should not surprise people

Agree with this downside. It's definitely a tradeoff

@siriwatknp I have updated #20012 to check [ ] and link this PR. If you could do it for the other efforts, it will be 👌.

authors: oliviertassinari siriwatknp


text:
[core] update root package version

As far as I know, the version of the docs reads from root package JSON.

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

Yes, we missed it :\

Actually, this is on me 🥲. I revert the release in the previous PR run yarn release:version again because it was easier to pick the version from the terminal, but forgot to update root package version.

This value is shown at

so I added the docs label 😁


text:
[example] Avoid double rendering in the Remix example

Resolves https://github.com/mui-org/material-ui/pull/29952#discussion_r762576860
The goal is to avoid double rendering on the server. It was solved by injecting the emotion style tag after a specific meta tag in the head. It is similar to the new insertionPoint option recently added in emotion - https://github.com/emotion-js/emotion/pull/2521
I could use some help testing out, to make sure I didn't miss anything.

Tried replacing my solution that has double rendering with this one and I'm getting

Prop className did not match. Server: "MuiFormControl-root MuiFormControl-fullWidth makeStyles-root-2 makeStyles-root-6 MuiTextField-root makeStyles-textField-1 makeStyles-textField-5 css-wb57ya-MuiFormControl-root-MuiTextField-root" Client: "MuiFormControl-root MuiFormControl-fullWidth makeStyles-root-2 makeStyles-root-8 MuiTextField-root makeStyles-textField-1 makeStyles-textField-7 css-wb57ya-MuiFormControl-root-MuiTextField-root"

Not sure on whose side the problem is

@jansedlon The class names mismatch is from @mui/styles. This package is for legacy usages. The examples are no longer covering it. So what you experience is expected.
Should handle https://github.com/mui-org/material-ui/pull/30213#issuecomment-1001553981 here?

@oliviertassinari You're right. I had a few issues with css order so I just added prepend: true to cache and switched positions of <Links /> and <meta           name="emotion-insertion-point"           content="emotion-insertion-point"         /> and so far except one error Expected server HTML to contain a matching <link> in <head>. it's working well. The performance is the same (in dev env)

Should we handle #30213 (comment) here?

Will handle it in a follow up, thanks for linking it.

Nice, this looks great!

authors: jansedlon mnajdova oliviertassinari


text:
[field] Label doesn't blur unlinked input on mouse down

Steps to reproduce
Steps:

https://deploy-preview-477--base-ui.netlify.app/base-ui/react-field/#controlled-validity / https://master--base-ui.netlify.app/components/react-field/#realtime-and-async-validation

https://github.com/user-attachments/assets/88333bd0-b586-4350-a9ed-edfac5b687a4
Current behavior
Doesn't blur on mouse down
Expected behavior
Should blue on mouse down
https://github.com/user-attachments/assets/035a2e87-39b6-4200-8d85-e360cc0e91a6
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/label
Context
I noticed this on #477. It got me a bit confused at first, I wasn't sure I clicked right when I didn't saw the input blurred, or it made me feel a bit like the UI is unresponsive.
Your environment

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

Search keywords: -

I much prefer that it doesn't blur the label's own/linked input, which always felt strange to me. However I guess unrelated/unliked ones should still blur

I guess unrelated/unliked ones should still blur

💯

I much prefer that it doesn't blur the label's own/linked input, which always felt strange to me.

Tricky, it feels like the UI is lagging if I don't see the input blur when I mouse down on something else. https://mui.com/material-ui/react-text-field/#basic-textfield feels right:
https://github.com/user-attachments/assets/ee434023-de91-4b8e-8dcf-66bd0e4c2061

authors: atomiks oliviertassinari

repo: mui/base-ui


text:
@mui/lab Masonry Component is Not Rendered Correctly With SSR

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
The Masonry component from @mui/lab package is not rendered correctly on the server side. Therefore when JavaScript is disabled on the client, it's not rendered.
Initially, it will render one column despite the value of the column prop. After hydration is done, it'll show the correct number of columns.
The main issue here is the layout shifting during the client-side rendering.
Expected behavior 🤔
When using the Masonry component from @mui/lab package, I expect it to be fully rendered on the server-side.
Steps to reproduce 🕹
Steps:

In a Next.js project, set up mui with emotion engine.
Install mui/lab package and import Masonry component.
Use the Masonry component and set the column prop to a fixed number (e.g. 3).
Build your project and run a production env.
Disable javascript in the browser.
You will see the Masonry component rendered with one column.

Context 🔦
I'm trying to implement a Masonry fully rendered on the server without any client-side rendering to avoid layout shifting.
Your environment 🌎
My browser is Chrome 101.0.4951.54

`npx @mui/envinfo`
  System:
    OS: macOS 12.2.1
  Binaries:
    Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.14.0/bin/yarn
    npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
  Browsers:
    Chrome: 101.0.4951.54
    Safari: 15.3
  npmPackages:
    @emotion/react: ^11.9.0 => 11.9.0
    @emotion/styled: ^11.8.1 => 11.8.1
    @mui/base:  5.0.0-alpha.79
    @mui/icons-material: ^5.6.2 => 5.6.2
    @mui/lab: ^5.0.0-alpha.80 => 5.0.0-alpha.80
    @mui/material: ^5.6.4 => 5.6.4
    @mui/private-theming:  5.6.2
    @mui/styled-engine:  5.6.1
    @mui/system:  5.6.4
    @mui/types:  7.1.3
    @mui/utils:  5.6.1
    @mui/x-date-pickers:  5.0.0-alpha.0
    @types/react: 18.0.8 => 18.0.8
    react: ^18.1.0 => 18.1.0
    react-dom: ^18.1.0 => 18.1.0
    typescript: 4.6.4 => 4.6.4

created a minimal reproduction repo
👉 https://github.com/ammar-oker/mui-issue-32688-reproduction

I don't know this related or not, this issue also occurred in nextjs-with-typescript.
Steps to reproduce

Clone nextjs-with-typescript example
Add a drawer https://mui.com/material-ui/react-drawer/#responsive-drawer
Disable JS

I did change the react version to 17.0.2 and the problem solved.

Setting the defaultHeight and defaultColumns solved the issue. Thanks for your assistance!

setting default* props fixes layout issues in non-ssr contexts as well

authors: ammar-oker degitgitagitya noahehall

repo: mui/material-ui


text:
[TextareaAutosize] Instability in height of memoized multiline TextField component

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/jovial-frog-qyyd04?file=/demo.tsx
Steps:

Click the switch
Observe that the the height of the memoized TextField (on the left) flashes, while the non-memoized TextField (on the right) is stable.

Current behavior 😯
The TextField lags to adjust its height.
Expected behavior 🤔
The TextField should maintain its height and no flashing should occur.
Context 🔦
The application I am working on renders multiline TextFields in different tabs, which are hidden by setting the display to none. Each tab has a large component tree, where there could be a memoized component anywhere within the tree, which I believe will cause this problem.

Since the MemoizedTextField does not rerender, it changes its height only via the ResizeObserver (implemented in TextareaAutosize). Its handler is debounced by 166ms, which causes the layout shift you described.
I think we could solve this by removing the debounce from the resize observer handler (but keep it on the window's resize event).
Would you like to prepare a PR with the fix?

Hi,
I will raise a PR for fixing this.

authors: alexbisaillion amal-qb michaldudak


text:
[material-ui][docs] codemods require certain version of nodejs otherwise fails with "Unexpected token ."

Related page
https://mui.com/material-ui/migration/migration-v4/#run-codemods
Kind of issue
Missing information
Issue description
I've spen the last hour trying to run codemods but getting "Unexpected token .".
Eventually through trial and error I tried running older codemods and one of them told me that I need at least nodejs v12 (I was on v10). Sure enough after updating (I went to v20) the latest codemods get past the error.
Context
Migrating from mui 4 to 5
Search keywords: codemod unexpected token

Thanks for the report. We have a section on supported browser and node version: https://mui.com/material-ui/migration/migration-v4/#supported-browsers-and-node-versions. Do you think we should move this to another section to make it clearer?

Somehow I missed that section when doing my migration. That's on me, I guess. It could be command line tools checked for this themselves when executed, though

authors: RyanEwen mnajdova


text:
OutlinedInput should have helperText and other features that Text Field has

Summary
OutlinedInput should have the option to add helper text that would show below it like it does with Text Field. Sometimes I'm forced to use OutlinedInput insted of Text Field and I just can't customize it the same way, which makes me question why such a component exists at all.
Examples
No response
Motivation
I need a number input which has helper text below it.
Search keywords: outlinedinput text field helper text

Hey @CzechCoder, thanks for the report.
The TextField's component purpose is to include additional features to the input components, like OutlinedInput. OutlinedInput doesn't include helperText by design.
If you need to access the OutlinedInput directly while still having a helper text, you can do so by composing the components themselves, here's an example example: https://mui.com/material-ui/react-text-field/#components

authors: CzechCoder DiegoAndai


text:
[material-ui][Typography] Color prop check for primitive type

Changes Made:

Updated the getStyleValue function to check if the provided color value is a primitive type (string, number, boolean, etc.) before setting the property's value.
If the provided color value is not a primitive type, the function will not set the property's value and will log an error to the console in development mode.
Added tests to ensure the correctness of the generated CSS when using invalid color values.

Testing:
I have added tests to the Typography.test.js file to ensure that the changes work as expected. The tests include checking the correctness of generated CSS when using invalid color values.

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

Closes #38478

@brijeshb42 Can you please help me with these failed checks?

@brijeshb42 kindly review these changes.

@DarhkVoyd Can you take a look at the failing tests here and make sure they or fix the tests accordingly - https://circleci.com/gh/mui/material-ui/587030 https://circleci.com/gh/mui/material-ui/587028

Sure, I am looking at the failing tests.

@brijeshb42 I have made changes to getStyleValue, added some test cases and resolved other failed checks. I am unable to understand this failed test because running npm release:build script works fine locally.

Seems like an error failing on master as well. You'll have to rebase when it's fixed on master.

@brijeshb42 I have made necessary changes, kindly tell me when to rebase.

@DarhkVoyd Can you rebase and push again? The build should pass now.

@brijeshb42 Yes, the build passes now.


text:
Add imgur api integration

https://apidocs.imgur.com/#c85c9dfc-7487-4de2-9ecd-66f727cf3139
Currently, there is the only integration that is https://imgbb.com/
Add support for imgur as well, let the developer choose the hosting.

Hi, can I please take a stab at this?

@Opyskoty Hey sure!!

I would like to work on this card please let me know if no one is working on it.
Thanks

@vvkpd Hi, sure!
@Opyskoty most likely not working on it.

Can I take this issue?

@code-star-1 sure!

I'd like to take a crack at it!

@carmonaalex12 sure!

Hasn't been an update in awhile, can I give it  try?

@badcaptcha hi! Sure, go ahead

Hey, can you please tell me what has to be done briefly ? May be I can work on this.

Hi, may be you can look into existing integration https://github.com/muke1908/chat-e2ee/blob/master/backend/external/imagebb.js
Similarly, you can implement Imgur API integration https://apidocs.imgur.com/#c85c9dfc-7487-4de2-9ecd-66f727cf3139

Hey sure, I'm on it.

@muke1908 Mate, I have some doubts.
1. I replaced the existing imgbb with imgur. But you state

Add support for imgur as well, let the developer choose the hosting.

How to do that?
2. I have integrated just the anonymous part as per this link you provided

Similarly, you can implement Imgur API integration https://apidocs.imgur.com/#c85c9dfc-7487-4de2-9ecd-66f727cf3139

Is this fine or do I need to do Authorization as well?

@GJ-16 authorization is not required.


text:
message_thread_id in sendmessenger

I can't send messenger to some topic in supoergroup by add message_thread_id.  Anyone have solution for this

The last update of the library was almost 2 years ago. Therefore, this package does not support topics. Alternatively, you can switch to node-telegram-bot-api, the syntax is similar to telebot and is constantly updated.

after I reply to topic ID, everything is ok

repo: mullwar/telebot


text:
Can multi hash be compatible with RFC 6920

Just wondering if the devs here have seen the work at the IETF:
https://tools.ietf.org/html/rfc6920
Could the two efforts be compatible?

I think so, the IETF proposal seems more limited than multihash (not clear if it supports 64 algorithms (it reserves 6 bits for that) or 32 as it says). It doesn't specify the size making binary interpretation of truncated hashes more problematic than with multihash too.
Conversion between the two formats should be very easy though.
I just noticed that this RFC is linked from the README so @jbenet knew about it 3 years ago when he added that line at least.

Also see #49

authors: hsanjuan melvincarvalho pawal

repo: multiformats/multihash


text:
Create list.plist

经过整理后的列表

谢谢整理

authors: KIDXO mumuy


text:
Port value in $conf['connection'] is not applied for mysql

The $conf associative array in config_default.php shows a 'port' key as an option, but that value is not applied when the mysql dsn is created. There is a function, getdbh() in app/helpers/site_helper.php, that creates the dsn, on line 83, which currently reads:
$dsn = "mysql:host={$conn['host']};dbname={$conn['database']}";
It should be:
$dsn = "mysql:host={$conn['host']};port={$conn['port']};dbname={$conn['database']}";

tx for reporting

authors: bochoven sctthffnr

repo: munkireport/munkireport-php


text:
윈도우 bat 화면관련 건의사항입니다

에러는 간단하게 표시하고..
녹화중인 것의 상세정보를 표시하는게 낫지 않을까 생각됩니다.
녹화중인 파일을 확인 전까지는 녹화가 되는지 안되는지 잘 모르겠더라고요

조금 전에 코드 수정했는데 원하시는 대로 되었는지 확인 부탁드립니다

조금 전에 코드 수정했는데 원하시는 대로 되었는지 확인 부탁드립니다

감사합니다. 잘되는거 확인했습니다 고생많으십니다 ㅠㅠ


text:
Music starts automatically after having played a tts message

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

[X] Yes

The problem

Song (album) from Spotify is played on Google Nest Speaker through / on MA
Song (album) is paused or the speaker in MA is turned off.
Through HA a tts message is being played on this Nest Mini Speaker
Song (album) is unpaused and is played, but that is not what I want in this situation.

(I cannot seem to unload the song from the nest speaker
How to reproduce
See above
Music Providers
Spotify
Player Providers
Only have Google Nest Minis (which all have this problem)
Relevant log output
NA
Additional information
Let me know if more info needs to be provided or if this is intended behaviour.
What version of Home Assistant Core are your running
2024.2.1
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
ODROID

You ticked the box saying you looked at the closed issues https://github.com/music-assistant/hass-music-assistant/issues/1853

Sorry, missed this. 🫣 thanks for all the work!

authors: OzGav pmkruyen

repo: music-assistant/hass-music-assistant


text:
Add chapters for plex audio books

Finally the chapters are now available in the plexapi library 🥳

Great, now we have a reason to actually use this :-)

repo: music-assistant/server


text:
Dynamic Partials and Partial Collections through Coercion

I've just created a pull request over at https://github.com/janl/mustache.js/pull/242
I am using this solution in a couple of projects and it addresses a number of concerns I often hear with regards dynamic partials in Mustache, please see ticket (https://github.com/janl/mustache.js/pull/242) and documentation here:

https://github.com/thelucid/mustache.js#dynamic-partials
https://github.com/thelucid/mustache.js#partial-collections

Really, I urge everyone to have a play with it as it has cleaned up my templates no end.
Kind regards,
Jamie

bump
Any movement on a v2 spec that includes this feature?

bump
Any movement on a v2 spec that includes this feature?

^

To anyone still hoping for a feature that involves detecting a hard-coded name such as partial in the context: I don't see that ever happening. Not that I'm the one to decide, but I think too many people are against it (for reasons that I agree with).
To anyone still looking for a way to dynamically select a partial based on context, I suggest the following approach based on feature detection.
Data:
{
  items: [
    { content: 'Some text' },
    { url: 'Some URL' }
  ]
}

Templates:
{{!base.mustache}}
{{#items}}

{{>polymorphic}}

{{^items}}

{{!polymorphic.mustache}}
{{#content}}
    {{>text}}
{{/content}}
{{#url}}
    {{>image}}
{{/url}}

{{!text.mustache}}
{{content}}

{{!image.mustache}}

I know, I know. This looks suspiciously like the code that @thelucid was trying to avoid. The base template is not dynamically selecting a partial at all, to the contrary. It's expanding the same one every time, polymorphic, and that just contains the if-else again that @thelucid wanted to get rid of. You might think that I just moved the problem. But consider the following.

polymorphic.mustache is performing dynamic partial selection. And nothing else. So we have a clean separation of concerns.
base.mustache no longer contains the if-else; it is as clean as the "fine-grained control" version of what @thelucid was suggesting.
With this approach, you don't need to tag your data in any way. No hard-coded partial property that names a partial, no html property with a lambda. Just the actual data.
By extension, the code that prepares the data no longer needs to contain an if-else construction for injecting the tags. So I have actually moved the solution. Arguably to a better place, since Mustache templates are portable while your data-preparing code is not.

Last but not least: this already works, even without the lamdas extension, so you don't need to wait for anyone to change a specification in highly controversial ways.

polymorphic.mustache is performing dynamic partial selection. And nothing else. So we have a clean separation of concerns.
Yes, it is performing dynamic partial selection, but it's not an ideal solution for all cases: in your example your dynamic loading is bounded to your data structure / template, which is fairly limited

In my template I want to dynamically load contents of a page, following your example this is what my code would look like:
{{!template.mustache}}
{{>header}}
{{>content}}
{{>footer}}

{{!content.mustache}}
{{#mainpage}}
  {{>mainpage}}
{{/mainpage}}
{{#aboutpage}}
  {{>aboutpage}}
{{/aboutpage}}
{{#foobarpage}}
  {{>foobarpage}}
{{/foobarpage}}
{{!and so on... for all my pages in the database}}

I could use lambdas to solve this but I find it kinda tedious (not to mention the fact that this way I'm still tagging the data).
(Also I have no idea how to do it).
Or I could dynamically generate templates with a wrapper language
Wrapper:
<?php
$content_file = "foobar.mustache";
ob_start();
include("template.mustache.php");
$content = ob_get_clean();
// (mustache rendering here)
?>

template.mustache.php:
{{>header}}
{{><?=$content_file;?>}}
{{>footer}}

Pretty bad right?

you don't need to wait for anyone to change a specification in highly controversial ways.

We don't want to change a specification, we just want to add a feature, a new token.
Here's the proposal:
Data:
  content: "mainpage"
}```
Templates:

{{!template.mustache}}
{{>header}}
{{*content}}
{{>footer}}
Pretty simple, right?
This would make life easier for a lot of people.
PS. I didn't know which operator to choose, so I just picked up `*`, we can change it.

I'm new to this discussion and the top post has mostly dead links. Can proponents of the change point to a post that clearly explains the feature being proposed?
I have the impression that some use-cases are in common with "template inheritance" which was finally accepted as an optionally-supported feature (see https://github.com/mustache/spec/pull/125):
base.mustache:
header...
{{ $content }}
footer...

main.mustache:
{{< base }}{{$content}}
main page content...
{{/content}}{{/base}}

aboutpage.mustache:
{{< base }}{{$content}}
about page content...
{{/content}}{{/base}}

(This can be extended to pass a title to the base template, etc.)

some use-cases are in common with "template inheritance" which was finally accepted as an optionally-supported feature (see #125)

Yes, you're right, some use cases are common.
What we're proposing is to solve the problem the other way,  "forward" (with "includes"/dynamic partials) rather than "backwards" (with inheritance).
It's way more clean.
Data:
{
  content: "aboutpage"
}

Templates:
{{!base.mustache}}
{{>header}}
{{*content}}
{{>footer}}

{{!main.mustache}}
main page content...

{{!aboutpage.mustache}}
about page content...

@gasche The originally proposed feature is described in detail in https://github.com/janl/mustache.js/pull/242.
@anomal00us You are proposing a different feature, although it serves the same purpose and the suggested syntax may have been inspired on the discussion. To be honest, I find your proposal more sensible than the original. The syntax is less surprising and it doesn't involve a hard-coded special name.
I must point out that this is the spec repository. If you only want to add a feature to one particular implementation, you should probably take the discussion to that implementation. There is nothing wrong with discussing it here (again, as I said, I actually like what you're describing), but anything discussed here is about changing the specification, by definition.

Following up on what I just wrote: I realized that the syntax {{*key}} could theoretically be generalized to also supporting similar constructions with parents or even sections. This is why the discussion contained more radical suggestions such as {{> &key}} and {{> "name"}}. I pondered for a moment whether dynamic parents should be possible, and if so, how.
I ended up deciding that I like the language more in the minimalist form that it has today. As far as I'm concerned, there is still room for dynamic partials with a {{*key}} syntax, but we shouldn't take the dereferencing any further than that. There doesn't need to be a dynamic parent for parity, because as @anomal00us pointed out, inheritance and dynamic partials are to some extent alternatives. I certainly wouldn't want to complicate the internals of tags in order to support key dereferencing more generally.

I must point out that this is the spec repository. If you only want to add a feature to one particular implementation, you should probably take the discussion to that implementation.

Yes, I know. I already added this into my implementation, that's also why I am here.
It would be cool if this will be merged into the spec!

I realized that the syntax {{*key}} could theoretically be generalized to also supporting similar constructions with parents or even sections.

Can you make an example?
Do you mean something like this: (?)
Data:
{
  items: [
    { content: 'header' },
    { content: 'mainpage' },
    { content: 'footer' },
  ]
}

Template:
{{!template.mustache}}
{{#items}}{{*content}}{{/items}}

but we shouldn't take the dereferencing any further than that.

I totally agree.

There doesn't need to be a dynamic parent for parity, because as @anomal00us pointed out, inheritance and dynamic partials are to some extent alternatives. I certainly wouldn't want to complicate the internals of tags in order to support key dereferencing more generally.

So if we're writing a pull request for this we're going to keep things simple and allow deferencing only on simple data?

Can you make an example?

Ah I think I got it. Making * a deference operator and allowing to combine it with all the other tags, right?
{{#*deferencedarray}}
  {{&*deferencedunescaped}}
{{/*deferencedarray}}
{{**doubledeference}}
{{<*deferencedparent}}

Well, I don't feel like this is a good idea.. it's probably better to keep things simple.
I may be wrong but I can't come up with ideas where you could possibly need to deference a section.
Also implementing this would imply to change a lot of things, first of all the tokenizer, which will need to detect the * operator, then the abstract syntax tree generated by the parsers: we need an extra field to tell whether something is deferenced or not, and at last the compiler, which will need to "deference" the stuff.
Not to mention all the existing specifications.
So yeah, my proposal is to have * as dynamic partial only (stand alone) operator.

@anomal00us

So if we're writing a pull request for this we're going to keep things simple and allow deferencing only on simple data?

Honestly, I am probably not going to write a pull request for this, at least not soon, because I haven't implemented the feature myself (yet). But if you were to write one, I would definitely be in favor of keeping it simple, allowing only single-level dereferencing specifically for the purpose of interpolating plain partials (i.e., not parents). Basically, {{*key}} being a composition of {{key}} and {{>value}}. Also, I would be happy to review it.

Great, I'm planning to write it soon.
@jgonggrijp  do you know if there is a tool for getting the json from the yml, or did people here write everything by hand?

Okay I made PR #134

@anomal00us There is a command for it, which is mentioned in the Readme if I'm right. I suppose you already found it.

Probably a bad idea, but what if we spec general purpose dereferencing instead?
{{*variable}}
{{#*list}}
{{>*template}}
{{/*list}}

{
  variable: "a",
  list: "b",
  template: "c",
  a: "foo",
  b: [
    {name: "bar"},
    {name: "baz"},
  ],
  c: "somepartial"
}

{{!somepartial.mustache}}
{{name}}

@bobthecow

Probably a bad idea, but what if we spec general purpose dereferencing instead?

It crossed other people's minds before, so at least it's not stupid. It was first discussed in 2012, from https://github.com/mustache/spec/issues/54#issuecomment-8679169 onwards. That never led to anything (at least not in the spec). It was again discussed by me and @anomal00us just a few days ago, from https://github.com/mustache/spec/issues/54#issuecomment-985633165 onwards. Bottom line of the latter discussion is that we both preferred not complicating the tag contents. See also #134.
For me personally, Mustache's syntactic simplicity is one of its main selling points. A general purpose dereference operator would arguably make the language even more powerful than it already is, but I think the added value is questionable for all tags except partials (where it enables a template equivalent of polymorphism through tagged unions, similar to how parents and blocks enable polymorphism through inheritance). I feel it would also start a slippery slope towards a bloated language like Handlebars or Jinja. Besides dereferencing, can we apply other general purpose operators within tag contents? Can we dereference multiple levels? Etcetera... it's a direction I rather not explore.
On another note, I would be highly interested in your opinion on #131.

ahahahahah i clicked through from #134 and didn't expand all the collapsed past conversation here and missed that I proposed this exact thing a decade ago when it first came up 😛
https://github.com/mustache/spec/issues/54#issuecomment-8674827

The question of dynamic tag names has come up for more than just partials in the past. To me it feels far more consistent to add a general purpose dereference operator (while I do acknowledge the slope we start slipping down) than to introduce a special form of partial that pulls the template name from the view model.

My question is this: can't we make a hard choice to not start slipping down that slope? We could have dereferencing in other ways. For example, we could give lambdas (read-only) access to the context stack through an additional argument.

I agree with @bobthecow a general purpose dereference operator might be useful when trying to reference things that would normal iterate or be conditional especially in the context of #135 .
That is the only need of dereferencing in my implementation since we don't support dynamic partials (or templates in general) is to pass lists and booleans around to lambdas.
Currently the easiest solution for my case is to use virtual keys instead of a new sigil. e.g. to reference a list instead of iterating I do the following:
{{#someList.this}}
{{#someLambdaExpectsListOnTopOfStack}}
{{/someLambdaExpectsListOnTopOfStack}}
{{/someList.this}}

this being the special virtual key that would kind of be equivalent to {{#*someList}}.
I am starting to get the idea that a large amount of problems that should be easy in mustache can be solved with virtual keys notable index information (e.g. -last, @last a boolean virtual binding that indicates if you are on the last item in a list).
Virtual keys are much easier to add to existing implementations than a new sigil albeit I'm not sure if that holds up to dynamic partial needs (to be frank I'm like @gasche in that I'm not sure if I even follow all the ideas in this thread).

@agentgt In my particular implementation, adding virtual keys like @last would actually be much harder than adding new sigils. That's because my tokenizer and parser already have generic facilities for sigils, but there is nothing yet to handle special reserved key names (other than the entire key being the implicit iterator .).
Power lambdas would make it possible to add your own virtual keys, but we already discussed that in #135. I understand it doesn't help in your case, and I figure that your implementation probably does already inspect key names inside the template, since it aims to typecheck everything. Mustache was clearly conceived as a dynamically typed language.
For context, dynamic partials did make it into the spec eventually, in #134.

authors: agentgt anomal00us bobthecow gasche hydrastro jgonggrijp spiffytech thelucid

repo: mustache/spec


text:
[chat_history] poor experience for keyboard in landscape layout

https://www.youtube.com/watch?v=us4grO1alQA
To fix this, we should probably create a dedicated UI for landscape keyboards. Something like this: https://stackoverflow.com/questions/58308754/flutter-how-to-open-full-screen-keyboard-in-landscape-mode/67334523#67334523
This will probably have to handle slash commands differently from the main UI, but we should create a custom text input overlay UI.

This is partially fixed by #1322 we will need a new UI for handling slash commands in landscape mode

repo: muxable/rtchat


text:
feat: retry future up to three times with a one second delay

Add retry logic to the getTwitchBadges method in lib/models/adapters/chat_state.dart to handle the firebase_functions/unavailable error.

Use a loop to attempt the Firebase function call up to three times.
Add a one second delay between each retry attempt.
Catch the firebase_functions/unavailable error and retry if the attempt count is less than three.
Return an empty list if all attempts fail.

For more details, open the Copilot Workspace session.

@SputNikPlop can you verify this works? Just check that badges still load.

@SputNikPlop can you verify this works? Just check that badges still load.

They all still load


text:
The express&nextjs example can't worked.

nextjs err: timeout;
express err: can't get req.body;
position: body or the pipeBody function.

const { Server } = require('@webserverless/fc-express')
const express = require('express');
const bodyParser = require('body-parser');

const app = express();
app.use(bodyParser.text());
app.all("*", (req, res) => {
  res.send(req.body);
});

const server = new Server(app);

// http trigger entry
module.exports.handler = function(req, res, context) {
  server.httpProxy(req, res, context);
};

The above code is working

bodyParser.text() is ok, but bodyParser.json() not successed.

try to replace
// http trigger entry
module.exports.handler = function(req, res, context) {
  server.httpProxy(req, res, context);
};

with
export const handler = (request, response, context) => {
  if (server.isListening) {
   server.httpProxy(request, response, context);
  } else {
    getRawBody(request, function (err, body) {
      if (err) {
        response.end(JSON.stringify({
          resCode: 500,
          msg: err.message
        }));
      }
      request.body = body;
     server.httpProxy(request, response, context);
    });
  }
};

this is because the 'data' event of ctx.request is missing during the server is starting (getRawBody, line 14, http-trigger-proxy.ts)

@gorphone Thx,  the express example worked, but next.js example cannot working.

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
import * as express from 'express';
import * as proxy from '@webserverless/fc-express';
import { SwaggerModule, DocumentBuilder } from '@nestjs/swagger';
import {
  ExpressAdapter,
} from '@nestjs/platform-express';
import { ExceptionsFilter } from './filter/exception';
import { TransformInterceptor } from './interceptor/transform';
import * as getRawBody from 'raw-body';

const server = express();
const FCServer: proxy.Server = new proxy.Server(server);

/// 参考https://blog.theodo.com/2019/06/deploy-a-nestjs-app-in-5-minutes-with-serverless-framework/
async function bootstrap() {
  const app = await NestFactory.create(
    AppModule,
    new ExpressAdapter(server)
  );
  app.useGlobalFilters(new ExceptionsFilter());
  app.useGlobalInterceptors(new TransformInterceptor());

  app.use(proxy.eventContext());
  await app.init();
}

export const initializer = async function(context, callback) {
  try{
    FCServer.startServer();
    await bootstrap();
    callback(null, '');
  } catch (e){
    callback(e, '');
  }
};

export const handler = (request, response, context) => {
  if (FCServer.isListening) {
    FCServer.httpProxy(request, response, context);
  } else { // 若sever尚未完成启动，需要手动处理body，避免body丢失
    getRawBody(request, function (err, body) {
      if (err) {
        response.end(JSON.stringify({
          resCode: 500,
          msg: err.message
        }));
      }
      request.body = body;
      FCServer.httpProxy(request, response, context);
    });
  }
};

@Victorkangsh here is  my nest.js practice and work well for me, wish it could help

@gorphone Thank you, and I found a better method to deploy web app that is use custom runtime.

authors: Victorkangsh gorphone muxiangqiu

repo: muxiangqiu/webserverless


text:
Clipboard not working when using --xwayland

Hey, thanks for this script to make my life easier.
I am having issues with clipboard not working whenever I run x11docker with --xwayland, I need it because the electron app does not play nicely without gpu even with --gpu args passed, but this break the clipboard sharing (bi-directional) functionality, so currently I am using the shared "file" workaround in which I saved clipboard contents in a file which is accessible from both container and host.

Does clipboard sharing work e.g. with Xephyr?

Yeah, clipboard works with xephyr, but I wanted to use xwayland, since the GPU acceleration is better there.

Odd that it works in Xephyr, but not in Xwayland.
Just tried to reproduce and found that since my recent update to Debian bookworm the weston window with Xwayland does not show Xwayland at all, however, no error appears. So I cannot check the clipboard immediately.
I'll have to check and fix that first before I can check the clipboard issue.

I use hyprland (Wayland compositor) and it has support for xwayland, that's what I use for running my custom docker image based on debian with xfce.

authors: CoolnsX mviereck


text:
Warning with Xcode7.2: MWPhotoBrowser.m:550:1: Conflicting return type in implementation of 'supportedInterfaceOrientations'

hi,
/Pods/MWPhotoBrowser/Pod/Classes/MWPhotoBrowser.m:550:1: Conflicting return type in implementation of 'supportedInterfaceOrientations': 'UIInterfaceOrientationMask' (aka 'enum UIInterfaceOrientationMask') vs 'NSUInteger' (aka 'unsigned long')

:+1:
Additionally, it's looks like there is pull-request already provided with fix for it (#450)

repo: mwaterfall/MWPhotoBrowser


text:
Remove trailing slash from requests

e.g. when using
this.setEndpoint('users/' + userId + '/preferences');

the uikit will prepend a slash / at the end such that the request goes to [...]/preferences/ instead of [...]/preferences. This is unnecessary and leads to, should the user decide to do so, /preferences/?someQueryParm=foo which destroys the query parameter

Why does it destroy the query parameter? Isn't the example just a valid URL?

Isn't the example just a valid URL?

Good point, it is, and the query parameter works.
Still i would enjoy not having it added automatically since its confusing

authors: axelhodler t-beckmann

repo: mwaylabs/uikit


text:
Hook for linting IaC configs?

Stumbled across repo this from a discussion in the Trivy repo regarding pre-commit hooks. Was wondering if you would be interested in adding support for the config flag for e.g. scanning Dockerfiles and other IaC? I can create a PR to add if so.

Sounds interesting, not sure I complete follow ?
You mean having another hook that only reacts on the trivy.yaml ?

If I'm understanding how everything works correctly, it would basically be another check. Something like the following would be the raw Docker command, which I think would map to pre-commit.
This should work against any repo with a Dockerfile in it if you want to try testing.
run -t --rm -v $PWD:/src -v /tmp/trivycache:/root/.cache/ aquasec/trivy conf --severity HIGH,CRITICAL /src

Potentially something like this in pre-commit?
- id: trivyconfig-docker
  name: trivyconfig-docker
  entry: aquasec/trivy:0.37.1 config --cache-dir /src/.pre-commit-trivy-cache --severity HIGH,CRITICAL
  language: docker_image
  pass_filenames: false

Sorry for responding so late. Could you create a PR?
I created a example repo as well, maybe you could create a show case there too

Sure thing, will try to get around to it in the next few days here.

https://github.com/mxab/pre-commit-trivy/pull/7.
Will get a PR going in the example repo as well.

Nice, currently without my computer. Will look at it begin of next week

Thank you :)
Created a new release

Nice, I will give it a test and update docs in the example repo.

authors: jmreicha mxab

repo: mxab/pre-commit-trivy


text:
add array-based overloads for variadic parameterized functions (join, race)

solves issue https://github.com/mxcl/PromiseKit/issues/326

The reason this wasn't there is: it crashed certain versions of the Swift compiler.
Probably we're safe now, but well… just a warning.

Will test before merging.

Ah the pains of swift we take for the good, huh?
That's understandable, and I don't have every version of Xcode ever to test em all, so do with this what you wish

Although wait has had this since August of last year, so I think it'll be alright
https://github.com/mxcl/PromiseKit/commit/a2718b2d3ef2aedab42bca376aec45ee343ed9a4#diff-65c2204ae94d363ee89e320cf7f237d3

Don't merge, think I found an issue. Will also include tests from #375 in final

Not sure if it's proper to take someone else's code. Push up your fix though. I'll see if @rbobbins would like to resubmit her PR with only the tests. Or we'll figure out some other arrangement. You both have contributed so I think both of you should be credited for your respective work.

@rbobbins do you want to replay your commit on top of mine? I'll make you a contributor to my fork if you'd like

added join tests and array-based race tests. Anything else preventing this from merge?

Will review at length ASAP. Though at first glance everything seems good.

Thanks a bunch to @feighter09  and @rbobbins both.

authors: feighter09 mxcl nathanhosselton

repo: mxcl/PromiseKit


text:
[Docs] What is DX?

The term "DX" is used in the README, but it is not explained anywhere. Perhaps draw from how this project explains it https://github.com/skidding/cosmos

Thanks!

repo: mxstbr/react-boilerplate


text:
Constructor id arguments don't need to be listed first

I was working on using MyBatis with pre-existing classes and i ran into the problem that according to the DTD idArgs need to come before args in the constructor.
This following example doesn't validate, although MyBatis doesn't actually have this restriction:
<resultMap id="MyClass" type="test.MyClass">
	<constructor> <!-- Error: The content of element type "constructor" must match "(idArg*,arg*)". -->
		<arg column="name" javaType="string" />
		<idArg column="id" javaType="string" />
	</constructor>
</resultMap>

Can mybatis-3-mapper.dtd be changed from:
<!ELEMENT constructor (idArg*,arg*)>
to
<!ELEMENT constructor ((idArg|arg)*)>

I just noticed that you have an XSD as well, which also would need to change:
Old:
<xs:element name="constructor">
	<xs:complexType>
		<xs:sequence>
			<xs:element minOccurs="0" maxOccurs="unbounded" ref="idArg"/>
			<xs:element minOccurs="0" maxOccurs="unbounded" ref="arg"/>
		</xs:sequence>
	</xs:complexType>
</xs:element>

New:
<xs:element name="constructor">
	<xs:complexType>
		<xs:choice minOccurs="0" maxOccurs="unbounded">
			<xs:element ref="idArg"/>
			<xs:element ref="arg"/>
		</xs:choice>
	</xs:complexType>
</xs:element>

Hello @Condor70 ,
I didn't know this was possible with DTD.
Would you send us a PR?
If you are busy, please just let me know and I'll take care of it later.
FYI, if you specify name, the order of idArg/arg does not matter.
See #721


text:
Gateway Last Seen

The gateway last seen is never updated and after some time it says the gateway is "Down" with the red icon. All other sensor nodes are working.

@seant100 I have added a fix for this issue. You can check with SNAPSHOT version.
When a gateway node(node Id: 0), goes down. Gateway will be reloaded. Status updated wrongly. I hope I have fixed this wrong status update.

@seant100 I tested this in my environment for the last 5 days. works well. If you see this issue in your environment kindly reopen this issue.

@jkandasa Sorry for the delay. I installed the latest snapshot today and checked 2 hours later and the Gateway node is down. So the problem is still there.
Also, you state you trigger a reload when the node goes down. I have rules setup that send me an email if a node goes down. So that method means I will still get Gateway is down emails.
Can you not assume a Gateway is working if any of its Nodes are working. Since all traffic essentially comes from the Gateway then you can set the "Last Seen" on the Gateway when ANY data is received from any node.

repo: mycontroller-org/mycontroller


text:
iOS 9 Black Screen Issue

While Appearing Status bar the screen gets black on iOS 9

Hello, please try this change, it helps in my case:
nihilenz@565488e

:+1:
Thanks it worked!

thanks

This helped but didn't completely fix my issue. Now the status bar will be shown correctly on iOS 6, 7, and 8, but on iOS 9 it is only shown on the iPad - it doesn't show on the iPod.

Thanks it helped me!!

:+1: cool! how did you managed to know that using -init: instead of -initWithFrame: will fix the black screen problem??

When we display message on status bar using MTStatusbaroverlay class then message doesn't display properly in portrait & landscape mode on iOS 9 devices. Its working fine on iOS 8 or lower devices.

Any update regarding above issue?

authors: Emmo213 hlung nihilenz shweta-techjini skumawat suhailrashidbhat xiaoMingChina


text:
Error when saving a go file

What version of Vim/Gvim are you using?
Vim/Gvim version
$ vim --version
8.1

What version of Go are you using (go version)?

$ go version
go1.12.5

What operating system and processor architecture are you using (go env)?
go env Output
$ go env
mac, amd64

What version/commit of govim are you using?
master
What is the output of :messages in Vim?
Vim channel logfile: /var/folders/jn/803dcg5976z37rtnb5lvqc9h6n00dn/T//vim_channel_log_20190508_1522_13_np13VFhZzBb7
govim logfile: /var/folders/jn/803dcg5976z37rtnb5lvqc9h6n00dn/T/govim_20190508_1522_13.743731000_676704289
Do the Vim channel or govim log files show anything interesting?
Nothing I can tell in a cursory look

How did you install govim?

Vim 8 packages
What did you do?
Save a file

What did you expect to see?
File is saved
What did you see instead?
an error message

Thanks @varun06:

can you give a bit more context here? For example, was this the first file in a new package? A main package? etc
can you specify the commit of govim that you were using (master is a branch, which means the commit to which it is pointing changes over time)

My guess at this stage is that you're running into https://github.com/myitcv/govim/issues/86 (which is being tracked in https://github.com/golang/go/issues/31522)

yeah, it's a new go file in package. So looks like that I am hitting 86 for sure.

Ok thanks. I think I'll close this in favour of #86. We can always re-open if it subsequently transpires there's another issue.

repo: myitcv/govim


text:
前端增加版本号显示

建议在前端增加版本号显示或者更新的内容，
可以考虑在右上角用户名下拉里增加

感谢建议，已经添加，不过为了避免干扰用户，放到页面底部了，详见 1.0.7

感谢建议，已经添加，不过为了避免干扰用户，放到页面底部了，详见 1.0.7

好的感谢

repo: mylxsw/wizard


text:
想请教下文章页面的 css 用的是？

文章页面的 css 貌似和 vue 官网一样，请教下用的是哪个开源的 css 吗？

自己照着扒的


text:
German translation

I started translating your fantastic project into German.
I'll comment here when all posts and pages are finished.

This is awesome!

I made some changes to the docs locally yesterday. So I'll merge this PR now and update my commits to the repo as well. Please sync and make another PR once the docs are done. Many thanks.
The file userdata/posts/2017/use-social-commenting-services.md is changed.


text:
Heterogeneous dict?

Is it possible to create a heterogeneous dict? i.e. values of different type?

It is possible to create keys of different types but not values

authors: YichengDWu mzaks

repo: mzaks/compact-dict


text:
Auto logout on timeout

Have it automatically logout after a 15 minutes timeout

Completed this feature

repo: mzijlstra/flowcharts


text:
Postprocess_wikitext does not separate wikipedia articles.

The LM needs to be trained on long articles to be useful for downstream tasks. We solve it in wikitext-103 by splitting articles as follows:
def istitle(line):
    return len(re.findall(r'^ = [^=]* = $', line)) != 0

postporcess_wikitext need to add similar separators to the articles to train correctly BOS and EOS tokens.  Until this is fixed the training of LM on custom wikipedia will break.

I noticed that titles were still in tokens and my quick fix was to force number of words/tokens per line in [lang].wiki.[split].tokens to be between 10 and 250 (I found sentences with 4k tokens!). Does this make sense?

@abedkhooli long sentences are fine for language modeling as they are joined together into one super long string anyway and then chopped to bppt chunks.  So 4k is fine. The problem appears when we have very short sentences as the training examples are randomized before they are joined so then our language models never learn long dependencies and they start to thread "." as EOS. Which completely breaks imdb.

I see you already fixed titles and merged refactor into master. Great efforts!
My worry about extra long 'sentences' is one BOS/EOS for a full article (average sentence length for Arabic wiki is around 36 words including title effect).

My worry about extra long 'sentences' is one BOS/EOS for a full article
What's wrong with one BOS/EOS per article?

My worry about extra long 'sentences' is one BOS/EOS for a full article
What's wrong with one BOS/EOS per article?
I thought it was odd to have a sentence that long (in this case it is a full charter of 4903 words due to bad punctuation - no spaces after periods, no new lines.
I just rebuilt the wiki tokens from new scripts and noticed there are still one-word items (before applying postprocess) and the mean words per line was less than before (this depends on the distribution of title lengths so can't make conclusions). So, may be another filtering step is needed.

New scripts just add articles separators so that one article (not a sentence) become a training example separated by BOS.
That way LM learns to forget parts of the sentence when it sees "." and to reset it self when it sees "BOS" as it means that the completely
new context is comming.
I still don't see how this behaviour may cause issues though, are you worried that there will be to llitle bos /eos for LM to learn something meaningful?

On 1 Jan 2019, at 19:05, Abed khooli notifications@github.com wrote:
My worry about extra long 'sentences' is one BOS/EOS for a full article
What's wrong with one BOS/EOS per article?
I thought it was odd to have a sentence that long (in this case it is a full charter of 4903 words due to bad punctuation - no spaces after periods, no new lines.
I just rebuilt the wiki tokens from new scripts and noticed there are still one-word items (before applying postprocess) and the mean words per line was less than before (this depends on the distribution of title lengths so can't make conclusions). So, may be another filtering step is needed.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/n-waves/ulmfit-multilingual/issues/25#issuecomment-450747143, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUw1FQKTjmNQjsIyy4fhsSB5j1lNIOaks5u-6N-gaJpZM4ZlYHI.

Not sure about the effect, but filtering out similar cases as outliers (one long sentence articles are not expected to be seen in real life). Basically, the article goes like this:
"I went to the shop.The shop was closed.I did not buy anything."

authors: PiotrCzapla abedkhooli

repo: n-waves/ulmfit-multilingual


text:
Logic Analyzer should report channels it was unable to render

At this point, if a channel is requested, but not found in the log, the renderer just renders a blank channel.
I want it to ignore that channel and report back to the user it was unable to render said channel.

I've changed the functionality of the ScreenRenderer class to ignore missing channels, tests show it rendering an image 3 channels tall even when 4 are requested.
I've added a report_failed_signals method. It's a bit more passive than having the class actively throw an error of some kind, but it should work just fine. For the time being though it is a facade.
I'll be implementing the actual logic here shortly.

I've added a way to extrapolate all signals not used from the requested_signals list and return them as failed_signals.
It's a hack, but it works. I'm closing this issue. I'll address the mess when I clean up the code for #3.


text:
C implementation of arbitrary length Dice coefficient

A fast implementation for non 1024 bit arrays

Resolved by #63.

authors: hardbyte mhsiah


text:
Enable use of GCC on OSX

Like it says in the title.

To help I've added the compiler to the Jenkins node labels. So you can build on a node with e.g., "osx&&python3.6&&clang"

This probably needs to be started again. Tracked in #71.

authors: hardbyte unzvfu


text:
create $f for 0.1ETH

:)

create $f for 0.1ETH

create $f for 0.1ETH :)

create $f for 0.1ETH lol

create $f for 0.1ETH lol dew

create $f for 0.1ETH lol dew ewf

create $f for 0.1ETH lol dew ewf frew

create $f for 0.1ETH lol dew ewf dew

create $f for 0.1ETH lol dew ewf dew few

license: ISC


text:
🛑 rasp.n1l.dev is down

In 3e89d58, rasp.n1l.dev (https://rasp.n1l.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: rasp.n1l.dev is back up in a40335a after 25 minutes.


text:
TerminalView (scheduled for removal in a future release)

What happened?
IntelliJ IDEA Ultimate 2023.2.6Compatible. 1 usage of scheduled for removal API and 1 usage of deprecated API (Restart)
1 usage of scheduled for removal API
Flutter-Toolkit 2.4.6 uses API scheduled for removal in future releases
Scheduled for removal class usage (1)
TerminalView (1) (scheduled for removal in a future release)
Deprecated class TerminalView is referenced in BaseGenerationAnAction.execCommand(...). This class will be removed in a future release
1 deprecated API usage
Flutter-Toolkit 2.4.6 uses deprecated API, which may be removed in future releases leading to binary and source code incompatibilities
Deprecated method usage (1)
TerminalView.getInstance(Project) (1)
Deprecated method TerminalView.getInstance(Project) is invoked in BaseGenerationAnAction.execCommand(...)
IntelliJ IDEA Ultimate 2023.1.6Compatible. 1 usage of scheduled for removal API (Restart)
1 usage of scheduled for removal API
Flutter-Toolkit 2.4.6 uses API scheduled for removal in future releases
Scheduled for removal class usage (1)
TerminalView (1) (scheduled for removal in a future release)
Deprecated class TerminalView is referenced in BaseGenerationAnAction.execCommand(...). This class will be removed in a future release
Relevant log output or stack trace
No response
Steps to reproduce

Gradle IntelliJ Plugin version
1.16.0
Gradle version
8.2.1
Operating System
None
Link to build, i.e. failing GitHub Action job
No response

Is there any solution? This plugin not working in android studio koala

authors: myxzlpltk nEdAy

repo: nEdAy/Flutter-Toolkit


text:
Error with updating modules when scripts are defined on the composer.json file

Hi,
I've come across an issue when defining a custom script on one of my modules. Here is the composer.json file:
{
    "name": "creode/externalapiauthentication",
    "description": "",
    "authors": [
        {
            "name": "Creode",
            "email": "contact@creode.co.uk"
        }
    ],
    "extra": {
        "laravel": {
            "providers": [],
            "aliases": {

            }
        }
    },
    "autoload": {
        "psr-4": {
            "Modules\\ExternalApiAuthentication\\": ""
        }
    },
    "scripts": {
        "build-docs": "npx redoc-cli --output Docs/api/docs.html build Docs/api/document-retrieval-api.yml"
    }
}

Upon running the php artisan module:update command I get an error stating: array_merge(): Argument #1 must be of type array, string given.
This is when using PHP 8.0.21.

just like in composer.json the scripts expect an array so yous can be changed to:
"scripts": {
        "build-docs": [
            "npx redoc-cli --output Docs/api/docs.html build Docs/api/document-retrieval-api.yml"
        ]
    }

This will then run the command

Perfect, thank you for this. 👍

authors: dcblogdev jaymeh

repo: nWidart/laravel-modules


text:
Use modules to another project

How can i use one of my previously developed module to my new laravel project? Basically, how to import and register modules in newly created projects?

I'll close this as there hasn't been a reply in a while, feel free to comment if needed.

I have same question I have sample module git@github.com:sarmadmahar/module1.git how can I use it into my another project XYZ ?  composer require sarmadmahar/module1 not working

authors: John-Dear nWidart sarmadmahar


text:
Text-Overflow

If the text is too long in two adjacent cell, the text will overlay each other and hard to distinct.
Is there a way to support text-overflow?
I have tried text-overflow to  but it seems not working.

@HaolinWang8 Duplicate of #25 #7
For just hiding text overflowing you can add the following to your css :
table.data-grid tr td.cell {
overflow: hidden;
}

is it a way similar to
text-overflow: ellipsis;

repo: nadbm/react-datasheet


text:
itemRerender is so complicated

I can not use item rerender feature as when I use it the items disapear.. I try to make the shape of a card  like this ( https://ant.design/components/card/#header )
but when I use it the items disapear ..can anyone help by providing some examples for diffrenent shapes for items
thanks in advance

I would suggest starting from here
https://codesandbox.io/s/k0wn41y0o7
this is a full example of itemRenderer. Try coding your item from this starting point and post the codesandbox here so we can help figure it out together

authors: Ilaiwi MrOttimista

repo: namespace-ee/react-calendar-timeline


text:
help!!

Hello I try to run wowned.exe it opens and closes quickly, could you explain to me how to solve?

Have you launched it using the CLI as advised in the README ?

I extract the wowned files from my wow local folder, run wowned.exe and it closes quickly, am i doing wrong? if you can explain me I appreciate

show it, and close quickly.

Well if you run it by clicking on it it will not work. You must use a terminal (cmd on windows) to run the program with the needed arguments as explained in the readme document.

If you are not familiar with the terminal a quick search with your favorite search engine will help you to get started: https://duckduckgo.com/?q=basic+use+of+windows+cmd

error

I applied I put login and any password to try to login, and disconnects me from the server.

show it, and close quickly.

The error is shown in the output:
ERROR: No method chosen
This exploit is actually two in one as there were two similar bugs found at more-or-less the same time.  You have to specify --1 or --2 when running.

authors: GuillaumeHemmen namreeb neltharionbr

repo: namreeb/wowned


text:
🛑 addrespect.ch is down

In 9ccbd35, addrespect.ch (https://addrespect.ch) was down:

HTTP code: 0
Response time: 0 ms

Resolved: addrespect.ch is back up in 9cfc1b2 after 4 days, 18 hours, 39 minutes.

repo: nanhosting/monitoring


text:
Pause outer stopwatch

All but the inner filter in a nested filter call won’t be recorded properly when compilation gets suspended.
Timing is hard :(

Codecov Report

Merging #1116 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1116      +/-   ##
==========================================
+ Coverage   98.64%   98.64%   +<.01%
==========================================
  Files         446      446
  Lines       18101    18116      +15
==========================================
+ Hits        17856    17871      +15
  Misses        245      245

Impacted Files
Coverage Δ

...nanoc/cli/commands/compile/timing_recorder_spec.rb
100% <100%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b2413cf...9570af5. Read the comment docs.

authors: codecov-io ddfreyne

repo: nanoc/nanoc


text:
Proposal: features

Hello, I'm working in jnano-node a JVM implementation of the protocol and I came up with an idea: features.
During the handshake we could exchange information about the capability of each node and decide how to communicate. and this can cover a most of situation like:

New fatures (vote-by-hash)
Experimental features (new serialization protocol)
Expose characteristics (historical node)

This could lead to way more flexible protocol allowing to introduce big chances without waiting for other nodes to upgrade and after enough adoption you could make an experimental feature part of protocol.

https://github.com/nanocurrency/raiblocks/issues/1120 is somewhat relevant

This is similar to SMTP's EHLO

authors: cryptocode rkeene rotilho

repo: nanocurrency/raiblocks