text:
Can't get mid epoch resumption to work

Environment

OS: [MacOS 13.4]

To reproduce
Following this issue, I tested mid epoch resumption but I can't make it work.
Steps to reproduce the behavior:
from streaming import StreamingDataset
from streaming import StreamingDataLoader

dataset = StreamingDataset(local="cache", remote="path")
dataloader = StreamingDataLoader(dataset, batch_size=1)

state_dict = None
for i, batch in enumerate(dataloader):
    print(i, batch["sentence"])
    if i == 4:
        state_dict = dataloader.state_dict()
    if i == 5:
        break

dataloader2 = StreamingDataLoader(dataset, batch_size=1)
dataloader2.load_state_dict(state_dict)

for i, batch in enumerate(dataloader2):
    print(i, batch["sentence"])
    if i == 1:
        break

0 Macin Dos : 10 faits psychologiques int
1 rappelaient beaucoup les courbes des hippocampes a
2 2eme exemple, le noix ressemble au cerveau humain,
3 mais non. Ok? Ça me dit pas trop, je préfère me co
4 détecteur de gaz et vous donner nos astuces gratui
5 La nouveauté, c’est que cette colère née après la

0 Macin Dos : 10 faits psychologiques int
1 rappelaient beaucoup les courbes des hippocampes a

Dataloader2 restarts from scratch: the first 2 samples printed are the samples number 0 and 1 from the dataset, despite load_state_dict command.
Expected behavior
The first samples from dataloader2 should be the samples number 5, then 6.
Maybe I'm not using the StreamingDataLoader properly ?
Additional context

Hey! The reason why resumption isn't working as intended here is because you're using the same StreamingDataset for both dataloaders. If you instantiate a new StreamingDataset and use that for the second dataloader, it will have its own shared memory objects and the load_state_dict function will work for mid-epoch resumption. Thanks for creating this issue!

A fixed script:
from streaming import StreamingDataset
from streaming import StreamingDataLoader

dataset = StreamingDataset(local="cache", remote="path")
dataloader = StreamingDataLoader(dataset, batch_size=1)

state_dict = None
for i, batch in enumerate(dataloader):
    print(i, batch["sentence"])
    if i == 4:
        state_dict = dataloader.state_dict()
    if i == 5:
        break

dataset2 = StreamingDataset(local="cache", remote="path") # add this line
dataloader2 = StreamingDataLoader(dataset2, batch_size=1) # take in the new dataset
dataloader2.load_state_dict(state_dict)

for i, batch in enumerate(dataloader2):
    print(i, batch["sentence"])
    if i == 1:
        break


text:
Add traffic_model to accepted params list

This adds the traffic_model parameter to the list of accepted params to support the new traffic model feature in Google Maps distance and directions APIs that can be used to predict time in traffic based on historical averages.  The parameter traffic_model defaults to best_guess accepts the variables best_guess, pessimistic, and optimistic.

Please see this https://github.com/moshen/node-googlemaps/pull/100 as it included your change.
Thanks for the contribution anyway!

source: gharchive/pull-request

authors: KerryKDiehl fabriziomoscon

repo: moshen/node-googlemaps

license: mit

license_type: permissive

license_source: bigquery


text:
docs: add consul titles

ref https://github.com/mosn/htnn/issues/259

Merged. Thanks!

repo: mosn/htnn

license_source: github-api


text:
Integrate with wasmtime; 集成 wasmtime 运行时

1. Background
Currently, Layotto supports load and run *.wasm files by integrating wasmer-go and wasmer, now we want to support wasmtime as another WebAssembly Runtime.
2. Why is this needed?
Compared with wasmer, wasmtime has more advanced features, which allow us to make more settings for the running *.wasm files. For details, please refer to #607
3. draft design

Related code paths

Reference Code

MOSN has provided extension points. the interface is located in the file: pkg/types/wasm.go. In theory, we can use the wasmtime API to implement several interfaces in Layotto.
4. Other references

https://github.com/bytecodealliance/wasmtime
https://github.com/bytecodealliance/wasmtime-go

中文
一、背景
目前 Layotto 是通过集成 wasmer-go 跟 wasmer 来支持 *.wasm 文件的加载运行，现在我们希望支持 wasmtime 来加载运行 *.wasm 文件
二、意义&价值
相比于 wasmer，wasmtime 具备更多的高级特性，可以让我们对运行着的 *.wasm 文件做更多设置，具体可以参考 #607
三、设计草案

相关代码路径

参考代码

MOSN 已经留好了扩展点，接口所在文件：pkg/types/wasm.go，理论上应该在 Layotto 中结合 wasmtime 的 API 实现里面的几个接口即可。
四、其他参考资料

https://github.com/bytecodealliance/wasmtime
https://github.com/bytecodealliance/wasmtime-go

/assign

进展：

不需要写到 mosn 仓库里，可以注册进去
函数有差异，有适配成本

进展:
因为wasmtime对function注册相关的支持没有wasmer完备，还在单元测试

目前集成wasmtime单测通过，集成测试有点问题，给bytecodealliance提了issue
https://github.com/bytecodealliance/wasmtime-go/issues/145

https://github.com/bytecodealliance/wasmtime-go/issues/146

目前demo中function2可以正常加载及运行，function1有点问题
https://github.com/bytecodealliance/wasmtime-go/issues/149

https://github.com/bytecodealliance/wasmtime/issues/4194

source: gharchive/issue

authors: rayowang seeflood zhenjunMa

repo: mosn/layotto


text:
A history/change table for FLW language updates

A history/change table shall be created with old and new language for the existing FLW when language is updated.
Pulled out of #124

Looking at the code this looks complete

repo: motech-implementations/mim


text:
Nms.ft.mcts beneficiary import service bundle it

Added test-case for mcts upload

Looks good to me, I'm merging. But there is one comment to fix. Please include fix on the next change to this file.

Actually, I'm doing the merge and will fix the test heading...


text:
Include LICENSE file

Could you please attach a license file, for example MIT, Apache 2.0, GPL. A license file would make clear what I am allowed to do with this code and what not.
About the background: I am a student at the University of Ulm and am currently writing my my master thesis.
For my empirical study I am investigating vulnerable projects and evaluating different security tools.
I would like to choose your project as one of my test cases for my empirical study.
However, since there is no license file available, I am not sure if I am allowed to use this code for my empirical study or not.
Thank you! :)

@lorriborri License file was added. Thank you.
https://github.com/motikan2010/CVE-2020-5398/blob/master/LICENSE.md

license: MIT


text:
[Bug] Animation played twice in Firefox

1. Describe the bug
Animation played twice in Firefox when:

That element has the animated property. Eg: you animate opacity property and the element's style also has opacity property.
That animated property has transition property. Eg: transition: opacity 1s

2. IMPORTANT: Provide a CodeSandbox reproduction of the bug
https://codesandbox.io/s/loving-http-jizb9i?file=/src/index.js
3. Steps to reproduce

Make a div that has the style div {opacity: 0; transition: opacity 1s}
Animate that div: animate("div", {opacity: [0,1]})
Open in Firefox.
After finishing the first fade animation, it will play again.

4. Expected behavior
It should not play twice. MS Edge (Chromium) does not have this problem (might need a check on Safari).
5. Video or screenshots
https://user-images.githubusercontent.com/7108662/193212616-b5d2025d-bb64-4d94-9112-01d36e4664c5.mp4
6. Browser details

Windows 10 Pro 21H2 build 19044.2006
Firefox 105.0.1 (64 bit)
MS Edge 105.0.1343.53 (Official build) (64-bit)

I really appreciate you taking the time to respond. Thank you for your explanation.

Just had this problem. As stated by @mattgperry setting the transition to none on the problematic element completely fixed it. Thanks!

authors: ElusiveByte rootEnginear

repo: motiondivision/motionone


text:
Missing QtWidgets.QOpenGLWidget

The QQOpenGLWidget class is not available in QWidgets
The workaround is to import it from PySide2 directly
from PySide2.QtWidgets import QOpenGLWidget
It would be nice to have it exposed in the Qt.QWidgets module
Thanks

It's only available to Qt 5; for anything to qualify for Qt.py, it must be available in all bindings simultaneously, including PySide(1).

https://doc.qt.io/qt-5/qopenglwidget.html

Note "Since: Qt 5.4"

See Qt5.py if you no longer need support for Qt 4.

Thanks
I never realized that this logic was present in qt.py
It makes total sense.
I will use qt5.py instead
Cheers

authors: mottosso sylvainberger


text:
Add external guides to README

These should be in the README I think. :)

Sounds good!
It seems you got the load_ui changes into this PR by mistake.

It seems you got the load_ui changes of the README into this PR by mistake.

So I did, well spotted, fixing now.

authors: fredrikaverpil mottosso


text:
Add guard around zero width or height

in my usage of this via leaflet.heat I have a lifecycle where the canvas can be 0 width or 0 height which is causing getImageData to throw an error.
I placed a guard around the relevant section so this case is covered.
If you can accept this request I will contact the leaflet.heat upstream and ask for them to propagate the update to their release.

Any feedback if this can be included ?

This has been open for a long time, was it just an oversight?

Hello, great plugin. Wondering if this is something that can be merged?

Same issue here, is it going to be merged anytime soon?

authors: Bengreen Dumbaz corrigancd victorperezpiqueras

repo: mourner/simpleheat


text:
robot_description subscriber callback not being reached.

Hi @sjahr @sea-bass , as of https://github.com/moveit/moveit_drake/pull/18/commits/4dcb2169669438bf07c5619debb63798643b342f, I have made a few changes to log and report robot_description status. It seems that the callback to the robot_description subscription is not being called. I see that the ktopt planner manager is being initialized, however the lambda that implements the callback to the robot_description subcription does not get executed. Do you guys see something that I don't see?

Is the description published? If yes, as a very dirty workaround you could create a string in the ktop cpp file with the copy&pasted config and use that for the multibody plant (intermediately). I can maybe take a look into the publisher issue on the weekend

Yes it is! I'll do that

Solved in #18 and https://github.com/moveit/moveit_drake/pull/18/commits/ad817c26f72dcf254d864301eb3c8c0d1bd20e7c

authors: kamiradi sjahr


text:
🛑 t10n Services: Dynamic Image CDN (Das Quartier) is down

In df8326c, t10n Services: Dynamic Image CDN (Das Quartier) (https://dq-images.t10n.de) was down:

HTTP code: 403
Response time: 216 ms

Resolved: t10n Services: Dynamic Image CDN (Das Quartier) is back up in 57ae923.

repo: moximoti/upptime


text:
wreong

When doing npm install I get among other messages also:
npm http 200 https://registry.npmjs.org/grunt-jscs-checker
npm WARN deprecated grunt-jscs-checker@0.4.4: Package was renamed to 'grunt-jscs'

Should be a matter of updating the package.json here, did you get any other warnings I should take a look at?

tofumatt (Sent from mobile)

On 5 April 2015 01:31:51 EEST, Matěj Cepl notifications@github.com wrote:When doing npm install  I get among other messages also:  npm http 200 https://registry.npmjs.org/grunt-jscs-checker npm WARN deprecated grunt-jscs-checker@0.4.4: Package was renamed to 'grunt-jscs'    —Reply to this email directly or view it on GitHub.

I think, that's it:
matej@mitmanek: high-fidelity (master %)$ grep -E -i '(warn|err)' npm-log.txt
npm WARN package.json high-fidelity@2.0.1 No repository field.
npm WARN deprecated grunt-jscs-checker@0.4.4: Package was renamed to 'grunt-jscs'
matej@mitmanek: high-fidelity (master %)$

Closing as we'll be fixing up the codebase and want to keep the issues here for the new version we're working on.

authors: mcepl tofumatt

repo: mozilla/high-fidelity


text:
Check upload status API (bug 1208572)

https://bugzilla.mozilla.org/show_bug.cgi?id=1208572

@kumar303 I'd like to write some serialiser tests but how does this look?

I'm a little worried that we won't get around to adding API docs since we don't have the scaffolding yet. Hmm, let's try not to let that slip.

I'm r- so far because I think there could be a better way to change the data model. I asked some questions for clarification on that. Everything else looks good.

r+wc. After chatting about the model changes I understand them better now. I think these columns need a comment explaining that addon and version are not final in the case that validation might fail.

repo: mozilla/olympia


text:
how to  implement the demo???

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: chrome
PDF.js version:2.0.305

i have a question.
i'd like to know the all page width, height before rendering page.
this demo is loadingbar in unrendering page.
i only know how to get page size to use this function
==> pdf.getPage(all page)
but this function use all page render...
so how to implement loadingbar empty page size???
What is the expected behavior? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

The example at https://github.com/mozilla/pdf.js/blob/master/examples/node/getinfo.js#L43 shows how to do this. The getPage API doesn't render the page; it only renders if you call https://github.com/mozilla/pdf.js/blob/master/examples/learning/helloworld.html#L54.

authors: juuuuuuuuuuuuuu timvandermeij


text:
Error: The API version "2.6.33" does not match the Worker version "2.6.36"

just started to get the error:
Error: The API version "2.6.33" does not match the Worker version "2.6.36"
index.html

main.js
pdfjsLib.GlobalWorkerOptions.workerSrc = '//mozilla.github.io/pdf.js/build/pdf.worker.js';

looks like it works now.


text:
Hyperlinks not extracted for particular PDF

Hyperlinks are not getting extracted for this particular PDF. Other PDF viewers, including Chrome, Mac Preview & Acrobat, do render hyperlinks correctly.
Link to PDF file: https://cdn.relayto.com/media/files/ftV2Quw9QaWGCh7vZZbZ_BearingPoint_Annual_Report_2015.pdf
Configuration:

Web browser and its version: Chrome 52
Operating system and its version: Mac OS
PDF.js version: http://mozilla.github.io/pdf.js/web/viewer.html (12.08.2016)
Is an extension: No

Steps to reproduce the problem:

Upload the PDF into http://mozilla.github.io/pdf.js/web/viewer.html
Get 0 hyperlinks

Those are not actually proper Link annotations, but instead that PDF file  they (for some inexplicable reason) use Widget annotations which we don't fully support yet.

Those are not actually proper Link annotations, but instead that PDF file (for some inexplicable reason) uses Widget annotations to simulate normal links.
Note that currently, we only support a subset of the possible Widget annotations.

Duplicate of #4872?

They're using an acroform push button (with no appearance stream) with an URI action, e.g. for the "HyperCube" link on page 6:
Root/AcroForm/Fields/[84]/A/URI
Root/Pages/Kids/[0]/Kids/[1]/Annots/[7]/A/URI
Yes it's a duplicate, the only difference is that the other issue has an annotation with an appearance stream.

I have another PDF where internal hyperlinks fail(page 3, table of contents): https://cdn.relayto.com/media/files/Wq7cashxQCO2JyWvkTlo_rapport-transparence-pwc-septembre2016.pdf
I'm not very familiar with a different type of annotations Link vs. Widget. Is there a way to convert from one type of annotations to another via a third-party tool, like Adobe Acrobat or similar?

@timvandermeij will the work you doing on buttons https://github.com/mozilla/pdf.js/issues/7613 be a solution for this issue?

Yes, this will be fixed once pushbuttons (with actions and appearance streams) are implemented, which is all tracked in that issue. Your PDF generator is doing a somewhat bad job by making links a Widget annotation, while the Link annotation is the standard for this. Essentially it's emulating a normal link by a transparent button, which is a bit of a workaround. I'm not sure why your PDF generator does that, but you might want to check the export settings to make sure it's not exported as a form.
Note: Since a recent PR, we now show these kinds of issues in the console in a more specific manner. Opening the PDF in the first message in this thread now shows Warning: Unimplemented button widget annotation: pushbutton in the console.

@timvandermeij Thanks for the explanation! I've just pulled the latest and saw the warning. Is there an approximate timeline for the pushbuttons?

No, there is no timeline. I think https://github.com/mozilla/pdf.js/issues/7613#issuecomment-251895091 describes the situation quite well. It's a large project and it takes a good amount of time to fully understand the specification and implement it properly. Rendering the pushbuttons themselves is not too difficult, but the associated actions (what happens when the button is clicked) and the appearance streams (how should it look) are much harder, yet required for proper pushbutton support.

authors: Snuffleupagus THausherr timvandermeij websirnik


text:
Replace css color rgb(...) by #...

it's faster to generate the color code in using a table for components
it's very likely a way faster to parse (when setting the color in the canvas)

Interesting find; should the cases in https://github.com/mozilla/pdf.js/blob/master/src/display/svg.js be converted as well and possibly the Util.makeCssRgb method removed if becomes unused?

/botio-linux test

I ran benchmarks with this file:
foo.pdf
I generated using a python script.
In this file, makeHexColors is called 406,890 times and the perf comparison before/after the change:
-- Grouped By browser, stat --
browser | stat         | Count | Baseline(ms) | Current(ms) | +/- |    %  | Result(P<.05)
------- | ------------ | ----- | ------------ | ----------- | --- | ----- | -------------
firefox | Overall      |    50 |         4578 |        4509 | -69 | -1.51 |        faster
firefox | Page Request |    50 |            6 |           8 |   2 | 25.81 |
firefox | Rendering    |    50 |         4571 |        4501 | -71 | -1.54 |        faster

Good improvement! If you can fix the comment above and re-run the benchmark with that fix applied, I'll also trigger the tests here.

I already ran the benchmark with the template string.

/botio test

Looks good!
/botio makeref

/botio-linux makeref

just for information see also this https://stackoverflow.com/a/55200387 that also approve the idea to make a pre created table for performance.

authors: SamyCookie Snuffleupagus calixteman timvandermeij


text:
Revert "Revert "XFA - Fix the way to select page on breaking""

and fix the error which caused the backout: add an $extra property when creating html.
switch to next content area when breaking on page area.

/botio test

@calixteman there seems to be some regressions

/botio test

/botio makeref

killed the bots accidentally
/botio makeref

authors: brendandahl calixteman marco-c


text:
Prevent run-time errors in BaseViewer when it's falling back to SimpleLinkService (issue 14442, PR 14295 follow-up)

Fixes #14442

/botio-linux preview

Thank you for fixing this!

authors: Snuffleupagus timvandermeij


text:
Fix error on empty response headers

Fixes https://github.com/mozilla/pdf.js/issues/18957
https://github.com/mozilla/pdf.js/pull/18682 introduced a regression that causes the following error:
Uncaught TypeError: Failed to construct 'Headers': Invalid name
    at PDFNetworkStreamFullRequestReader._onHeadersReceived (pdf.mjs:10214:29)
    at NetworkManager.onStateChange (pdf.mjs:10103:22)

The mentioned PR replaced a call to getResponseHeader() with getAllResponseHeaders() without handling cases where it may return null or an empty string. Quote from the docs:

Returns:
A string representing all of the response's headers (except those whose field name is Set-Cookie) separated by CRLF, or null if no response has been received. If a network error happened, an empty string is returned.

Reproduction steps
Run the following code and observe the error in the console. Note that the URL is intentionally set to an invalid value to simulate network error
<script src="//mozilla.github.io/pdf.js/build/pdf.mjs" type="module"></script>

<script type="module">
  var url = 'blob:';

  pdfjsLib.GlobalWorkerOptions.workerSrc = '//mozilla.github.io/pdf.js/build/pdf.worker.mjs';

  var loadingTask = pdfjsLib.getDocument(url);
  loadingTask.promise
    .then((pdf) => console.log('PDF loaded'))
    .catch((reason) => console.error(reason));

</script>

/botio unittest

authors: CyberAndrii Snuffleupagus


text:
[EnhanceTextSelection] Make expandTextDivs more efficient by updating all styles at once instead of piecewise

I intended to provide proper benchmarking results here, as outlined in https://github.com/mozilla/pdf.js/wiki/Benchmarking-your-changes, but after wasting a couple of hours over the weekend getting weird results I gave up.
It appears that there's a lot of, i.e. way too much, variance between subsequent runs of text tests for the results to be meaningful.
(Previously I've only benchmarked eq tests, so I don't know if the text tests has never worked well or if it's a newer problem. For reference, please see the results of back-to-back benchmark runs on the current master with a very simple manifest file: https://gist.github.com/Snuffleupagus/eec3acc22f519eddce6404be883b6960.)
Instead I used console.time/timeEnd in appendText and expandTextDivs to be able to compare the performance with/without the patch. The entire viewer was (skip-cache) reloaded between measurements, and the result are available here: https://gist.github.com/Snuffleupagus/33fc971b653e6524bc889216ff95499c.
Given the troubles I've had with benchmarking, I've not yet computed any statistics on the results (e.g. mean, variance, confidence intervals, and so on).
However, just by looking at the data I think it's safe to say that this patch first of all doesn't seem to regress the current performance. Secondly it certainly looks very likely that this patch actually improves the performance, especially for the one-glyph-per-text-div case (cf. issue 7224).
Re: issue #7584.
/cc @timvandermeij

This change is

/botio test

Comments have been addressed.
/botio test

/botio-linux preview

/botio makeref

Awesome work!


text:
add db strings extraction command?

SUMO has some infrastructure for extracting strings from the database and putting them in a Python file which then gets passed over for strings extraction.
Input is going to need that, too.
Can we add that to Puente?

The relevant part of the Sumo infrastructure is kitsune/sumo/management/commands/extract_db.py.

I think I'm going to nix this idea. Less features makes it easier to ditch this library down the road.

authors: mythmon willkg

repo: mozilla/puente


text:
Update to Electron 1.1.1

We need this fix to reduce a dep on VS2015 redistributable

Be sure to update docs/building.md when this is fixed

We updated to 1.2.1 https://github.com/mozilla/tofino/commit/6ec5e8b7c6c11a9361aba8a8a3c335974dacbe5a
@jsantell ping

authors: jsantell victorporof

repo: mozilla/tofino


text:
API using RedisFuture with in a "push style" throwing error

I am having the following error when using future and sadd:
WRONGTYPE Operation against a key holding the wrong kind of value
private RedisAsyncCommands<String, String> asyncCommands;
asyncCommands = client.connect().async();
RedisFuture futureResult = asyncCommands.set(..)
futureResult.thenAccept(value -> System.out.println(value));
Any idea what's wrong ?
Thanks.

My bad. internal error insertion type.

Hi @IdanFridman,
RedisFuture.get throws ExecutionExceptions since 4.0 when an error occured. That's different to 3.x, in which a RedisFuture.get returned null in case an execution error happened. See also Asynchronous API (4.0) Error Handling in the Wiki.


text:
expected ')' near ':' Error

I am getting the following error, but I think it is a false positive.
The block in question is the following --
client.ConnectionComplete:add(function(s : object, e : System.EventArgs) : void
	client:JoinChannel('#meow')
end)

I am getting the following error --
resources/[gameplay]/irc/irc_run.lua:8:42: expected ')' near ':'

How do I suppress the error message?

This is not valid Lua syntax (see for yourself, Lua itself fails with the same syntax error: https://www.lua.org/cgi-bin/demo ).
It looks like you are using some custom typing layer on top of normal Lua?

@mwild1 yes, it is. I will look at another way to deal with it. I tried exclude_files = { } but it didn't work.

How exactly did you use exclude_files?

The folder is the main folder is the following resources/* which is what luacheck is scanning.
The file that I excluded was the following within a subfolder in resources was exclude_files = {"resources/[gameplay]/irc/*.lua"} The actual file was irc_run.lua

Trying to reproduce this problem. With this directory structure:
.
├── .luacheckrc
└── resources
    └── gameplay
        └── irc
            └── irc_run.lua

And exclude_files = {"resources/gameplay/irc/*.lua"} in .luacheckrc irc_run.lua is excluded.
If you have literal [gameplay] as a directory name:
.
├── .luacheckrc
└── resources
    └── [gameplay]
        └── irc
            └── irc_run.lua

Then using resources/[gameplay]/irc/*.lua as the exclusion pattern would cause [gameplay] to be interpreted as a pattern matching a single character (one of g, a, etc.), you need to escape the opening bracket: exclude_files = {"resources/[[]gameplay]/irc/*.lua"} works.

Perfect! Thank you. I really appreciated your assistance on this. The Luacheck is a great tool and is already catching simple mistakes too.

authors: SGTGunner mpeterv mwild1

repo: mpeterv/luacheck


text:
Video playback in Pannellium "Partial Panorama"

I want to create a virtual exhibition where video can be displayed on a 180 degree surface. If it is possible to play video on the "Partial Panorama" surface, I think it will be a solution for me. I do not have enough knowledge about coding, I created a merged html file from two different documents on your site, but I could not show the video. Can you help with this?
(The video size I want to show is 5120x720px)

Yes, the partial panorama and video functionality can be combined. Starting from the video example, you'll need to modify the Pannellum configuration; replace
videojs('panorama', {
    plugins: {
        pannellum: {}
    }
});

with
videojs('panorama', {
    plugins: {
        pannellum: {
            vaov: 180,
            haov: 360
        }
    }
});

to get started. Then configure the vaov and haov parameters to match the vertical angle of view and horizontal angle of view of your video, in degrees. Based on the aspect ratio of the video resolution you mentioned, I'm assuming that the video does not reach the zenith and nadir, so you'll want to decrease the vaov parameter to match. Note that the video needs to use the equirectangular projection for the display to be accurate.

For it to work in Chrome, you need to set Video.js's autoplay option to 'muted', e.g.,
videojs('panorama', {
    autoplay: 'muted',
    plugins: {
        pannellum: {
            vaov: 180,
            haov: 360
        }
    }
});

That will probably fix it on mobile as well.

authors: gokhanmar mpetroff

repo: mpetroff/pannellum


text:
Suspected memory leak

The following polling code results in a memory leak which consumes additional ram in each iteration.
function redx(){
      client = redis.createClient();
      client.get("tally", function(err, reply) {
            console.log(reply);
            client.quit();
      });
      setTimeout(function(){ redx() },1000);
}

redx()

Isn't this just closure leak, where using
setTimeout(function(){ process.nextTick(function() {redx() }) },1000);

would fix it?

If you have a heap dump that shows a leak without the closure leak, please let me know.

authors: BridgeAR jalava pacmac


text:
Ammo for weapons is being deducted from the actor, rather than the token, for non-linked tokens.

Describe the bug
When using the HUD to make a ranged attack for a non-linked token the ammo is not deducted from the token's ammo inventory, but from the ammo of the actor.
Steps to reproduce

Select a token that is not linked to the associated actor.
Click on weapons
Choose a ranged weapon with ammo
Make the attack roll
The ammo counter for the actor will change, but not for the token.

Versions:

Token Action HUD Core: [e.g. 1.5.6]
Token Action HUD SWADE: [e.g. 1.2.0]
Swade System: [e.g. swade 4.1.0]
Foundry VTT: [e.g. 12 build 331]
Browser: [e.g. Google Chrome 127.0.6533.120]

Additional context
Note: Not sure if the issue lies with Token Action HUD SWADE, or Token Action HUD Core. Using the module with SWADE, so putting the issue here. If the issue is with Core we can create the issue there and close this one.
Also Note: The issue only occurs when initiating the attack from the HUD. Initiating the attack from the token sheet works as expected, implying the issue is with how the HUD is activating the roll card.

Update: Appears to be working as expected with latest version (2.0.0).

Thanks for the update @sroakjp
I still need to review the code to make sure i'm using the references to the token and not to the actor itself.
I'll probably do some rework in the logic to fix any other issues and make this hud better.

authors: mrcomac sroakjp

repo: mrcomac/token-action-hud-swade


text:
If I am unable to post a message, because all nodes are frozen, I should see an descriptive error message when I hit "post"

Here's how this works.
If nodes are frozen, it means I cannot post to them. But I can still read messages.
So I see a bunch of messages, but when I hit the POST button, I get the following error, and maybe it links to a documentation page (coming soon).
"You cannot post messages until you are friends with someone who has their own node. Alternatively, you can start a node yourself."

@mreider  Wouldn't it be more correct to show this message at once instead of the posting form?

authors: dimakrsna mreider

repo: mreider/koto


text:
fix: lower path constraint to make compatible with flutter_test

Fixes
Note: path is pinned to version 1.8.3 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.

Because autoequal_gen >=0.9.0 depends on path ^1.9.0 and every version of flutter_test from sdk depends on path 1.8.3, autoequal_gen >=0.9.0 is incompatible with flutter_test from sdk.
So, because optox depends on both flutter_test from sdk and autoequal_gen ^0.9.0, version solving failed.

which prevents autoequal 0.9.0 from being used with Flutter 3.13 and 3.16.

Closing this PR as it has already been addressed in https://github.com/mrgnhnt96/autoequal/commit/a9d77168a33bee8ff75f5ed33b44682186943b69


text:
Cannot use program. Says ADB isn't installed.

Describe the bug:
I am attempting to make use of an old Fire tablet from 2017, but i simply can't use the program because it thinks ADB isn't installed. (platform-tools folder is in my home folder. Fire-Tools is also in there.)
Developer Mode and USB debugging is turned on on my fire.
Expected behavior:
To be able to use the program and have it detect ADB installed.
Platform:

Linux, Latest script

Device:

Model: Fire HD 10 (7th Gen)
Version: Fire OS 5.7.0.0

Additional context:

ADB works with my fire tablet.

The tool expects adb to be installed through your distros package manager (apt, pacman, dnf, etc). I see you're running Debian through Chrome OS's Linux container, so you would use apt.
sudo apt install adb

It works, but now i get this error instead:
./ui.sh: 32: zenity: not found
what is it trying to find?

Zenity is the GUI tool needed for Fire-Tools, it can be installed using:
sudo apt install zenity

I'll update the setup instructions to include Chrome OS so it's not as confusing.

Got it fixed but it's not recognizing my fire or my phone anymore.
USB Debugging is turned on in Developer Settings.

I've had that happen a couple times to fix it, on your Fire Tablet go to Device Options > Developer Options > Default USB Configuration and set it to File Transfer

I tried it and it still won't work. the Fire's cable is good and the Chromebook detects it but adb won't.

I have a USB converter dongle laying around.
The USB-C plug fits into my phone only (fire uses a different type.) I can plug my fire's cable into the converter and then plug it into my Chromebook and that's the only way.

After a reboot of ChromeOS and clearing USB debugging authorizations, It recognized the device!!

FIre Tools says device is unknown/unsupported??

could enabling/disabling widgets be a feature? just tried it with a command and it worked:
adb shell appwidget grantbind --package com.teslacoilsw.launcher --user 0

I found a bug. Tried to switch the launcher but it tried installing an already installed app.

I'm working on a way to automatically enable widgets for whatever launcher you choose, even .apks.

That error is my bad I forgot to add the Nova and Lawnchair .apks for the latest release but I'll have an updated version by tomorrow.

Apparently debloat worked with one app but Fire OS fixed it and now it stopped...
All i'm getting are java.lang.IllegalArgumentExceptions when it tries to run.

Looks like adb is having problems connecting because those packages are present on all fire tablets & the tool will skip to the next package if it can't disable the one that it's working on.

authors: SparklingWaterBurns mrhaydendp

repo: mrhaydendp/Fire-Tools


text:
Add more verbs from A through D

We ran into more missing verbs. So I figured instead of adding them a
few at a time when we run into issues, let's investigate what we
actually have used historically and batch add them. I did the
following for our largest repository, this is the only place where we
currently enforce git commit message style with this action:
https://github.com/mullvad/mullvadvpn-app/.
I grabbed all the first words from the subject line of our commits:
git log --format=%s | \
    awk '{print tolower($1)}' | \
    tr -cd '\n[:alnum:]._-' | \
    sort -u > first-words

I then filtered out the ones not already in
mostFrequentEnglishVerbs.ts:
for word in $(cat first-words);
do
    if ! grep -x "  '$word'," mostFrequentEnglishVerbs.ts > /dev/null;
    then
        echo "$word";
    fi;
done

I then manually started going through the list of words. Many of them
are not even verbs, or verbs not in imperative form, since we have not
enforced this style before. But many of them are perfectly fine
imperative form verbs and I suggest they are added to this action.
I stopped at the letter D and decided to submit this PR. That's
because I was not sure if you wanted this addition or not, and
figured I should reach out for feedback before spending more time.
I'll likely continue the filtering anyway, and add it to a local
path-to-additional-verbs in case you don't want them upstream. But
having them upstream would be way more handy, since then we can easily
run this on multiple repositories without having to duplicate the verb
list.
Semi-related question: Does it make sense to separate
"Verbs specific to programming"?
I personally think that distinction is not very important.

WHY does this enforce line length in PR descriptions? :joy: The formatting of PR descriptions are done by github. It renders fine without having limited line length.

Fixed. But I had to make not-desired changes to my bash code to make it fit really :P

I found in total 184 verbs that I initially classified as reasonable verbs to have. I have a PR up to add this as an additional wordlist to our own repository. But I would love if we could upstream as much as possible! When we want to start checking multiple repositories it would be really good if we did not have to maintain a separate wordlist or a fork of this action. https://github.com/mullvad/mullvadvpn-app/pull/5992
Tell me if you want this or not, so I know how to proceed :)

Hi @faern ! This is definitely a nice addition!

Semi-related question: Does it make sense to separate
"Verbs specific to programming"?
I personally think that distinction is not very important.

No, not at this scale. Feel free to re-order the verbs alphabetically.
You can go ahead and add all the verbs -- I can quickly skim through the list to check that all of them are actually verbs so that nothing slips. Just ping me once I should review.

Awesome! I'm glad to hear that. I have now pushed all our words! The first commit just adds our additional words. The second commit removes the distinction between "normal" and programmer verbs and sorts the list, so it's mostly automatically generated noise. Probably easiest to review the PR per commit.

@mristin Ping ;) This wordlist has passed internal review in my team, so it's already partially sanity checked. I hope you will like it.
One question that did pop up was whether or not abbreviations such as init and dedup should be in the list or not. I left them in since I felt they are very common programmer abbreviations for imperative verbs. But I can remove them if you think otherwise.

Thanks a lot, @faern ! Please let me know when I should publish a new patch version.

Awesome, thank you! Having a release would be amazing. I mean, I can't promise I won't come with more words in the coming few days also, but currently we could really use these 185 extra verbs :P

I'm not fluent in github actions. When I depend on this action, does it actually run the code in the dist/ directory? Because I tried depending on the commit hash for the master branch on this repo now, but it still does not accept "Source" as an OK verb.
uses: mristin/opinionated-commit-message@623037eb118a24335513cd7c4b2d4adabf292a8d

authors: faern mristin

repo: mristin/opinionated-commit-message


text:
[Feature]: :LegendaryScratch command should accept arguments to override the default display mechanism (e.g. float vs. split)

Similar Issues

[X] Before filing, I have searched for similar issues.

Description
It would be cool to be able to have the default set in config to float but then be able to run :LegendaryScratch split to open it in a split instead, overriding the configured default.

We should support:

:LegendaryScratch split
:LegendaryScratch vsplit
:LegendaryScratch float


text:
How to debug failing calls?

Hi,
I really like this gem, but am running into an issue where a Python call to spaCy is hanging my entire app. This happens only when I make that via through a Sinatra endpoint, while it's running. The tests (including the integration tests that go through the endpoint), all pass, and making this call in irb/pry console also works correctly. It's literally only when it's called via the endpoint. This is clearly a huge wtf.
I've already tried switching out Sinatra, since I'm at the point of trying anything. Didn't help.
This app has a second endpoint, also using pycall to call into fastText, which works fine in all cases, so I'm guessing this is something related to spaCy, but I want to be able to debug it, and I don't know how. I lose the trail at return self.__send__(name, *args) in PyCall::PyObjectWrapper#method_missing
Is there any way at all to get more info about what's happening here?

I've put up a small app that recreates the hang at https://github.com/xxx/pycall_hang
I'm just looking for pointers on how to debug the hang, since it only happens when I go through the web endpoint.

I'm having the exact same problem with puma!

I'm having the exact same problem with puma!

@ricardovj, the problem seems to be related to multithreading, which as previously mentioned is not yet supported.
For me, setting max_threads_count = 1 in the puma initializer solves the problem with the server freezing, though this might affect the server's performance when handling concurrent requests.

authors: andreaslillebo ricardovj xxx


text:
Symbol "," at the end of namespace

I have symbol "," at the end of namespace (using client library https://github.com/shuoli84/SocketIOCocoa) maybe I am doing something wrong? But I used same client and worked with node js server-side (https://github.com/Automattic/socket.io) without such problems.

#211

authors: dkorkin mrniko

repo: mrniko/netty-socketio


text:
Checking if the client connected successfully

Hi,
On the client side, is it possible to check if the connect() call was successful?
var iosocket = io.connect('http://localhost:8081');
I see that the iosocket has few attributes : connected, disconnected, readyState.
But the values of these variables seems to be the same even when the io.connect() failed. It always shows up as:
connected : false, disconnected:true. iosocket.io.readyState="opening" .
My use case is to check if the connect() was successful and if it failed, to handle the error gracefully on the client side.

I guess you may want to check for the onConnect() event (when client gets connected) or onError() event for any error. Please be advised that your question is related to socket.io protocol, not netty-socketio specific, so you may want to double check in another forum.

Ok.
solved this issue by registering a handler for "connect_error" event.

authors: pablojr pramodbms


text:
🐛 CameraViewManager cannot be cast to ViewGroupManager

What were you trying to do?
I'm trying to run the app and use the camera screen on an Android device.
Reproduceable Code
No response
What happened instead?
I'm receiving this error when I open up the camera screen of my app. Everything builds fine. The app runs with no warnings.
Then, I receive com.mrousavy.camera.CameraViewManager cannot be cast to com.facebook.react.uimanager.ViewGroupManager when I open the camera screen.
react-native: 0.66.3
It appears this issue has been encountered before. Did we find a solution?:
Okay so first off those are all very different errors.

the error CameraViewManager cannot be cast to ViewGroupManager happened

This seems really weird. I have never seen that error before and do not know how to reproduce it, if you can provide me a GitHub repository that I can run to reproduce it that would help me.

but when refreshing the c++ linking this happens
ninja: error: '../../../../build/react-native-0.64.2.aar/jni/armeabi-v7a/libjscexecutor.so', needed by '../../../../build/intermediates/cmake/debug/obj/armeabi-v7a/libVisionCamera.so', missing and no known rule to make it

This should be fixed by running the build twice. See https://github.com/mrousavy/react-native-vision-camera/issues/338

Now I did also try running the example project. Downloaded it and ran yarn install. Try running it on the phone with "Run 'app'" and got error:
ninja: error: "../../../../build/third-party-ndk/hermes/jni/arm64-v8a/libhermes.so", needed by "../../../../build/intermediates/cmake/debug/obj/arm64-v8a/libVisionCamera.so", missing and no known rule to make it

Same as above. See https://github.com/mrousavy/react-native-vision-camera/issues/338. Also you want to run yarn in both the root directory and in the example/ directory. Then open example/android/ in Android Studio.

But another error "parallel-video-processing-not-supported".

This happens in the Example app? See "the supportsParallelVideoProcessing prop", or related issue: https://github.com/mrousavy/react-native-vision-camera/issues/315

Maybe this whole thing has to do with you using an M1 laptop? the CameraViewManager cannot be cast to ViewGroupManager still seems so weird to me....
Originally posted by @mrousavy in https://github.com/mrousavy/react-native-vision-camera/issues/388#issuecomment-904680871
Relevant log output
No response
Device
Issues on both Motorola Moto E (physical device) and Google Pixel 4 (emulated), no issue on iPhone 11 (physical device)
VisionCamera Version
2.10.0
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

@mrousavy @trta2352 did you all ever find a solution to #388?

My bad! Issue derived from using SafeAreaView in combination with the Camera component.

My bad! Issue derived from using SafeAreaView in combination with the Camera component.

@willcray can you please elaborate what the solution was? I encountered the same problem but I couldn't find the solution. Much appreciated 😄

@willcray can you please elaborate what the solution was? I encountered the same problem but I couldn't find the solution. Much appreciated 😄

Yes, it was a simple fix. I stopped using SafeAreaView in the same JSX component as the Camera. I removed it from the component that renders the camera.

I have exactly the same error and I may know what is causing the issue. In my case I needed to render some elements on top of camera view so I'm rendering the as a children of Camera element. It works fine on iOS but crashes with:

com.mrousavy.camera.CameraViewManager cannot be cast to com.facebook.react.uimanager.ViewGroupManager

I'm not using SafeAreaView as Camera parent but regular View.

Yes, i am facing the same issue with Android. Did you guys find work around?

Same issue, dont have SafeAreaView but just View.

I'm also seeing the same issue.

authors: MrMole96 arthwood didithilmy gary-cohen vladimirevstratov willcray

repo: mrousavy/react-native-vision-camera


text:
Catch errors in deploy.yml ERB better

If you make a mistake in deploy.yml, especially with the ERB definitions, like referencing missing credentials, the error message is obtuse and the backtrace hard to parse. Let's improve this and make it easier to know exactly what went wrong.

What about validating raw_config with json-schema?
https://github.com/voxpupuli/json-schema

Interesting idea. Worried it might be too heavy, but we could try!

Don't actually need ERB now by default. So not really relevant. Still should validate the schema, though.

authors: dhh kjellberg

repo: mrsked/mrsk


text:
maximize app when click notification

Hi, i want to know if existe ahi param or method for open the app when click the notification.
This is my part of code for windows_notification:
    NotificationMessage messagePopup = NotificationMessage.fromPluginTemplate(
      "Alarga Error Job",
      "Nombr de job: $message",
      "Error: $cuerpo",
    );
    _winNotifyPlugin.showNotificationPluginTemplate(messagePopup);

thanks!

Hi, i want to know if existe ahi param or method for open the app when click the notification.
This is my part of code for windows_notification:
    NotificationMessage messagePopup = NotificationMessage.fromPluginTemplate(
      "Alarga Error Job",
      "Nombr de job: $message",
      "Error: $cuerpo",
    );
    _winNotifyPlugin.showNotificationPluginTemplate(messagePopup);

thanks!

hi, you must use Launch property with your app deeplink uri.

Hi, i want to know if existe ahi param or method for open the app when click the notification.
This is my part of code for windows_notification:
    NotificationMessage messagePopup = NotificationMessage.fromPluginTemplate(
      "Alarga Error Job",
      "Nombr de job: $message",
      "Error: $cuerpo",
    );
    _winNotifyPlugin.showNotificationPluginTemplate(messagePopup);

thanks!

hi, you must use Launch property with your app deeplink uri.

Hi @mrtnetwork , deeplink uri not is only for mobile pplataform?

i mean

Hi, i want to know if existe ahi param or method for open the app when click the notification.
This is my part of code for windows_notification:
    NotificationMessage messagePopup = NotificationMessage.fromPluginTemplate(
      "Alarga Error Job",
      "Nombr de job: $message",
      "Error: $cuerpo",
    );
    _winNotifyPlugin.showNotificationPluginTemplate(messagePopup);

thanks!

hi, you must use Launch property with your app deeplink uri.

Hi @mrtnetwork , deeplink uri not is only for mobile pplataform?

Maybe I am using the wrong name to explain it, take a look at this package, it worked for me applink

Thanks for the reply @mrtnetwork .When i use this package and configure the launch params, this open another app. So for new notification and make click, open a app instance. THis is correct  ? or i doing something wrong?
Thaks!

authors: anvers mrtnetwork


text:
Add support for a data-attribute to close open submenus

Now that it's possible to close an open submenu from anywhere in the DOM (#18), it would be a very nice developer convenience to declaratively use that feature.
So my current thought is this:
<button data-close-clicky-menus="menu-id">Close Open Menu</button>
Where "menu-id" is the ID of a valid clicky-menu instance. If that were in the DOM when the script first executes, I could find those instances and then automatically handle closing submenus when the button is clicked, reducing requirements for custom code.

This would be amazing. I'm starting to have close menu buttons within mega menus more often so that would make life a lot easier.

authors: ajplopez mrwweb

repo: mrwweb/clicky-menus


text:
[ BUG ] TypeScript not working

Describe the bug
My TypeScript won't work anyway.
To Reproduce
Copying the components as per the documentation, I make sure all the copied paths are okay
Expected behavior
Type inference should work properly
Screenshots

Platform (please complete the following information):

OS: MacOS
IDE: WebStorm
Nodejs: v20
TypeScript: 5.4.3

Additional context
Here is my tsconfig
{
  "extends": "expo/tsconfig.base",
  "compilerOptions": {
    "allowSyntheticDefaultImports": true,
    "jsx": "preserve",
    "lib": [
      "dom",
      "esnext"
    ],
    "moduleResolution": "node",
    "noEmit": true,
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "target": "esnext",
    "allowJs": true,
    "forceConsistentCasingInFileNames": true,
    "esModuleInterop": true,
    "module": "esnext",
    "isolatedModules": true,
    "strict": true,
    "baseUrl": "./src",
    "types": [
      "nativewind/types"
    ],
    "paths": {
      "@/*": [
        "./*"
      ]
    }
  },
  "include": [
    "app.d.ts",
    "**/*.ts",
    "**/*.tsx"
  ],
}

Seems related to: https://github.com/redwoodjs/redwood/issues/5104
When I add the following lines to tsconfig.json, the type works correctly.
"compilerOptions": {
    "paths": {
      "react": [
        "./node_modules/@types/react"
      ]
    }
}

I had this issue when updating my packages with npx expo install --fix. I had to delete my node_modules and install them again to fix it.

authors: AprilNEA mrzachnugent

repo: mrzachnugent/react-native-reusables


text:
A little question without your python code?

I saw the source code in pysplit.
There is a function that aims to genarate the CONTROL file
and later run the hysplit model, hyts_std.exe.
but i run hyts_std.exe in cmd.exe while the CONTROL was existed.
it still need to give some parameters line by line?
how can i solve it?

I have never run hyts_std.exe directly because the generate_bulktraj() method in PySPLIT  is more convenient and user-friendly.
Have you tried generate_bulktraj()?  If you are having difficulties with this then make sure the hysplit keyword argument is pointing to the correct location of hyts_std.exe.

repo: mscross/pysplit


text:
nested numpy array rather than 2d array

Because imread is deprecated from scipy 1.3, i use imread from matplotlib instead. But problem occurs on the line:
images = np.array([imread(str(f)).astype(np.float32) for f in files[start:end]])
It returns a nested numpy array, likes array([array([...]), ...]), rather than 2d array. To make the code precise, do you know how to convert the nested array to 2d numpy array?

I would recommend using imageio instead of matplotlib to read images. It has the same interface as the old scipy.misc.imread method. At some point, I will switch to this in the code as well.

Thanks for you reply.
The reason for this issue is not just what I said. After debuging, I found it is because the image size is not same. All matplotlib, imageio and even skimage work! Hence, I rewrite it into pytorch ImageFolder and doing the data preprocessing in the pytorch way. The preprocess includes the resize.
By the way, I find there are only options for using gpu or not. So I change it to be able to select specific device.
I can pull the modified version to yours, if you wish.

Thank you, but there is already a PR pending for including Pytorch-style data loading. If you want, you could submit a PR regarding choosing a specific device.

authors: JiaBob mseitzer

repo: mseitzer/pytorch-fid


text:
segmentation fault in ustl replace algorithm

Hi, please help to solve that issue or give your recomendations.
#ifdef USE_USTL
#include <ustl.h>
#define STL ustl
#else
#include <string>
#include <algorithm>
#include <iostream>
#define STL std
#endif //USE_USTL

#include <string.h> //strlen

#define PRINT(X) STL::cout<<X<<STL::endl
int main()
{
    char Str[]="test";
    PRINT("char * testing: "<<Str);
    STL::replace(Str,Str+strlen(Str),'t','z');
    PRINT("char * testing: "<<Str);

    STL::string Strng="test";
    PRINT("string testing: "<<Strng);
    STL::replace(Strng.begin(),Strng.end(),'t','z');
    PRINT("string testing: "<<Strng);
}

$ g++ replace.cxx -o replace.x
$ ./replace.x
char * testing: test
char * testing: zesz
string testing: test
string testing: zesz
$ g++ replace.cxx -DUSE_USTL -lustl -o replace.x
$ ./replace.x
char * testing: test
char * testing: zesz
string testing: test
Ошибка сегментирования (core dumped)
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.2 (Debian 4.9.2-10)

This is intentional. Please read the string section on the uSTL documentation page. uSTL strings constructed on const char* will create a linked string. Use the explicit operator= to create a writable string as below.
STL::string Strng;
Strng = "test";

thank you!)

authors: andrey-zibrov msharov

repo: msharov/ustl


text:
Feature request for console: Link to open logfile

atom-latextools already has great support for hyperlinks for errors, linking them to the correct line in the editor. But sometimes, as already reported in https://github.com/msiniscalchi/atom-latextools/issues/136 , the information is not allways enough. I think it would be great if it was possible to hyperlink to the actual logfile also. I see various ways that this could be accomplished:

Click the parsing directory/foo.log-line, leading to the logfile.
A simple button on top, leading to the logfile.
ctrl-click an error, leading to the correct line in the log. click without ctrl leads to the line in the editor(as is already happening.

Thank you for making such a great tool. and hoping that you and others find this useful.

Thanks for the suggestion. That's a really good idea.

repo: msiniscalchi/atom-latextools


text:
refactor: node-outdated rewritten "just for fun";

Fixes: #10
I created a project from scratch, and copied your code as needed. I made some modifications to the code, trying to use as many features as possible in vscode itself.
Then you would see that a lot of files were removed and that maybe it wasn't ideal. I wanted to know from your point of view which files are important to keep so I can work on an additional commit to bring them back.
Anyway, these are the improvements themselves:

Now Windows OS is fully supported;
Additional check for invalid package version (eg. "@types/next": "invalid-version");
Additional check for version higher than the last distribution version (eg. I'm using next on version 1.0.7-canary.3, however, the distribution version is 1.0.6). It is not treated as an error, just as information, as it is likely intentional;
Support for prefix use >= and <= during quick-fix;

It was all done more with the intent of having fun and learning a bit about extensions in vscode. I intend to work on other projects in the future, and this was a good start, and I really like this feature (I use a similar one in PhpStorm).

Also, the screenshot.jpg file needs to be moved to the wiki, otherwise the vsce package will store it inside the final package unnecessarily (and it represents 70% of the final package size).

@mskelton I think I managed to apply all your points. When you can, double-check that it's as expected.

repo: mskelton/vscode-npm-outdated

license: ISC


text:
Migrate to Flux v2 AKS Extension

Move from bootstrapping the cluster with Flux manually after deployment to using the Flux AKS Extension to bootstrap the cluster WITH the deployment.

Update to AKS 1.22.4

Update to Kured 1.9.0

Thanks for your review @magrande

repo: mspnp/aks-baseline


text:
Display the absolute address for relative jumps on x86

yaxpeax doesn't have support for doing this natively so just shim it on top.

Excellent, thanks!

authors: jrmuizel mstange

repo: mstange/samply


text:
🛑 Stress Positions is down

In 47d4612, Stress Positions (https://stresspositions.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Stress Positions is back up in c994e1c.

repo: mswd-io/upptime


text:
cache installer in the toolcache

Some concern about caching the entire install, but this should at least save self-hosted runners having to download the installer every run.
Enhancement for #145

Unfortunately, this is not working as intended.  It seems that the date is not passing the check of a valid semver, and causing the toolcache to not find any version.  Stupid thing.

@jeremyd2019 do you need a new release of this action (since #148 was merged)?

Not personally.  I've moved to using release: false to reuse the msys2 install on my self-hosted runner, I just have to remember to install it manually when setting up the runner.


text:
Memory leaks with Opcache

In PHP 5.5 with the builtin Opcache enabled for the CLI using the CronExpression causes memory leaks.
opcache.enable_cli = 1
Execute the following script on the command line:
use Cron\CronExpression;

$expression = CronExpression::factory('25 0 1 * *');

while (true) {
    $expression->isDue();

    usleep(100000);
}

The used memory (RSS) will increase rapidly and PHP will eventually throw a fatal error.
Please note that when changing the expression to * * * * * this issue does not occur.
It may very well be an issue with the Opcache, however I haven't been able to pinpoint exactly what is happening here.
Tested on CentOS 6.4 and Mac OS X 10.9.2 with PHP 5.5.10 and PHP 5.5.11

Fix released by PHP:
http://php.net/ChangeLog-5.php#5.6.5
http://php.net/ChangeLog-5.php#5.5.21

With this fixed in PHP, I think this can be closed.

repo: mtdowling/cron-expression


text:
Compilation problem

(From a fresh clone)
Already up-to-date.
   Compiling void v1.0.2
   Compiling num-integer v0.1.39
   Compiling num-iter v0.1.37
   Compiling num-bigint v0.2.0
   Compiling num-rational v0.2.1
   Compiling num-complex v0.2.0
   Compiling libc v0.2.34
   Compiling downcast v0.9.1
   Compiling num-traits v0.1.41
   Compiling num-traits v0.2.5
   Compiling unreachable v0.1.1
   Compiling termion v1.5.1
   Compiling ordered-float v0.5.0
   Compiling num v0.2.0
   Compiling rusty-wam v0.7.9 (file:///opt/gupu/rusty-wam)
error[E0658]: non-reference pattern used to match a reference (see issue #42640)
    --> src/prolog/ast.rs:1578:16
     |
1578 |         if let IndexPtr::Undefined = index_ptr {
     |                ^^^^^^^^^^^^^^^^^^^ help: consider using a reference: `&IndexPtr::Undefined`

error: aborting due to previous error

error: Could not compile `rusty-wam`.

To learn more, run the command again with --verbose.
ulrich@p0:/opt/gupu/rusty-wam$ history|tail
  501  git pull && cargo run
  502  git pull --recurse-submodules
  503  git pull && cargo run
  504  cd ,,
  505  cd ..
  506  mv rusty-wam rusty-wam.old2
  507  git clone https://github.com/mthom/rusty-wam --recursive
  508  cd rusty-wam
  509  git pull && cargo run
  510  history|tail
ulrich@p0:/opt/gupu/rusty-wam$ date
Wed Aug 22 11:10:24 CEST 2018

Which version of rustc are you using?

Under Ubuntu 14.04.05 LTS there is no more recent compiler.
Same for 18.04 LTS.

Ok, I reverted it back. It should now compile on 1.25.0.

Perfect!

authors: UWN mthom

repo: mthom/rusty-wam


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

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

HTTP code: 0
Response time: 0 ms

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

repo: mtitservice/site


text:
🛑 https://www.perc.ps is down

In 48f94fc, https://www.perc.ps (https://www.perc.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://www.perc.ps is back up in 6decf6b.


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

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

HTTP code: 0
Response time: 0 ms

Resolved: https://mtit.pna.ps is back up in 8367ffc.


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

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

HTTP code: 0
Response time: 0 ms

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


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

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

HTTP code: 0
Response time: 0 ms

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


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

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

HTTP code: 0
Response time: 0 ms

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


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

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

HTTP code: 0
Response time: 0 ms

Resolved: https://palcp.ps is back up in 79b6ffc.


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

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

HTTP code: 0
Response time: 0 ms

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


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

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

HTTP code: 0
Response time: 0 ms

Resolved: https://911.ps is back up in 36b4689.


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

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

HTTP code: 0
Response time: 0 ms

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


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

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

HTTP code: 0
Response time: 0 ms

Resolved: https://911.ps is back up in 022f78c.


text:
Added Logging

@mtniehaus  Can we add some logging? 😸

Already handled

authors: mtniehaus sandytsang

repo: mtniehaus/AutopilotBranding


text:
About IScroll

I'm able to work on IScroll  but receiving the compilation error as
error TS2304: Cannot find name 'IScroll'.

That is a TypeScript (.ts) compiler error and is probably caused by not supplying any typing information for the IScroll library.
Please take a look at https://www.npmjs.com/package/@types/iscroll and see if that can help you.

repo: mtr/angular-iscroll


text:
Replace lunaris/src/main/java/dev/tricht/lunaris/WindowsAPI.java with a cross-platform-compatible solution

Although that code is pretty platform-specifically written, I think this file can more or less easily be adapted for Linux and MacOS, as well as Windows too. I'll link to the source I found just now:
https://stackoverflow.com/questions/5226212/how-to-open-the-default-webbrowser-using-java
I really like your solution so far. But I'm playing on Linux, so I would love to be able to natively use this program. Since it's Java, I don't think we need to do more than to adapt the platform-specific code to be more cross-platform-compatible. It could really be a stand-out feature of this solution.
I'd take this any day over an Electron-based solution. Good god...

Hey, nice to hear from someone playing on Linux.
Linux support will be my next task this weekend. I usually don't game on Linux but it is my preferable platform.
Things that will need to be changed:

WindowsAPI
System tray AWT (Perhaps https://github.com/dorkbox/SystemTray)
Use something else than APPDATA for storing configuration and cached data
Create a launch script (lunaris.sh)

I believe that would be all. The key and mouse listener library we use is already cross-platform.

Hey! Awesome to hear, man. I was already able to open and build your program in Netbeans using Maven, after switching to Openjdk-13. I was on Openjdk-8 before due to another project and of course couldn't compile everything. :D
So yeah, I don't think we'd need to change that much. I've quickly went over your code and it was already mostly cross-platform-compatible. Another benefit of coding in Java! Let me know what the shell script would need to do. Maybe I'll have some spare time between my exams!

You can follow my progress here: https://github.com/mtricht/lunaris/commits/linux
The only things missing are:

Get active X11 window to determine if Path of Exile is active. I hope someone has some suggestions on how to do this.
The overlay does not seems to work when Path of Exile is running. Sadly no exceptions are thrown... When Path of Exile is closed the tooltip does work. So I'll have to debug whether it's Swing or JavaFX that's causing issues and figure out why.

See https://github.com/mtricht/lunaris/pull/28
Is any of you willing to test it on your end?

Fundamentally its working on my end. I have a three monitor setup, with poe in the middle and the offset is working fine.
https://i.imgur.com/bdldcV8.jpg
The window is a tad cut short to the right i suppose, but i can live with that. Better than tabbing out to the browser. With the patches in #28 the config branch also works for me quite well. In theory. I patched the config branch by hand before i noticed linux had its own because im blind xD
Anyway, keep it coming, im happy to test more things :)

@mkalte666 Thanks for testing! Could test out the master branch? We've added quite a few improvements.
@thorsten-passfeld would you also mind testing the master branch? We've revamped how we get the item text from in game, so alt+D should now also work for you.

Okay, some good and some "bad" news:

F5 works flawlessly now
alt + D actually does exactly what it's supposed to do, but the tooltip does not appear in front of the windowed-fullscreen game
alt + W reluctantly opens my browser after a few tries and then still resorts to Chromium, where Firefox is actually my main/default browser -> The "GLib-GIO-WARNING" warning appears in the console
alt + A didn't really seem to work on one map I tried (maybe that map is not yet supported?)

For the record, this is the log of that "session":
23:11:27.284 DEBUG dev.tricht.lunaris.Lunaris - Ready!
23:13:32.396 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Registered clipboard listener for dev.tricht.lunaris.listeners.ItemPriceListener
23:13:32.406 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Pressed ctrl+c
23:13:32.766 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Got clipboard text:Rarity: Magic
Warlock's Prophecy Wand of Euphoria
Wand
Physical Damage: 35-64
Critical Strike Chance: 8.00%
Attacks per Second: 1.20
Requirements:
Level: 68
Int: 245
Sockets: B-B B
Item Level: 69
40% increased Spell Damage (implicit)
22% increased Spell Damage
+32 to maximum Mana
58% increased Mana Regeneration Rate
23:13:32.801 DEBUG dev.tricht.lunaris.com.pathofexile.PathOfExileAPI - Affix 22% increased Spell Damage found as explicit.stat_2974417149
23:13:32.801 DEBUG dev.tricht.lunaris.com.pathofexile.PathOfExileAPI - Affix +32 to maximum Mana found as explicit.stat_1050105434
23:13:32.802 DEBUG dev.tricht.lunaris.com.pathofexile.PathOfExileAPI - Affix 58% increased Mana Regeneration Rate found as explicit.stat_789117908
23:13:32.833 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Unregistered clipboard listener
23:14:03.313 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Registered clipboard listener for dev.tricht.lunaris.listeners.ItemPriceListener
23:14:03.314 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Pressed ctrl+c
23:14:03.610 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Got clipboard text:Rarity: Magic
Warlock's Prophecy Wand of Euphoria
Wand
Physical Damage: 35-64
Critical Strike Chance: 8.00%
Attacks per Second: 1.20
Requirements:
Level: 68
Int: 245
Sockets: B-B B
Item Level: 69
40% increased Spell Damage (implicit)
22% increased Spell Damage
+32 to maximum Mana
58% increased Mana Regeneration Rate
23:14:03.610 DEBUG dev.tricht.lunaris.com.pathofexile.PathOfExileAPI - Affix 22% increased Spell Damage found as explicit.stat_2974417149
23:14:03.610 DEBUG dev.tricht.lunaris.com.pathofexile.PathOfExileAPI - Affix +32 to maximum Mana found as explicit.stat_1050105434
23:14:03.611 DEBUG dev.tricht.lunaris.com.pathofexile.PathOfExileAPI - Affix 58% increased Mana Regeneration Rate found as explicit.stat_789117908
23:14:03.611 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Unregistered clipboard listener
23:14:11.450 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Registered clipboard listener for dev.tricht.lunaris.listeners.ItemPriceListener
23:14:11.451 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Pressed ctrl+c
23:14:19.553 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Registered clipboard listener for dev.tricht.lunaris.listeners.ItemPriceListener
23:14:19.554 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Pressed ctrl+c
23:16:47.366 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Registered clipboard listener for dev.tricht.lunaris.listeners.ItemInfoListener
23:16:47.367 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Pressed ctrl+c
23:17:34.249 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Registered clipboard listener for dev.tricht.lunaris.listeners.WikiListener
23:17:34.250 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Pressed ctrl+c
23:17:38.051 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Registered clipboard listener for dev.tricht.lunaris.listeners.WikiListener
23:17:38.052 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Pressed ctrl+c
23:17:40.854 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Registered clipboard listener for dev.tricht.lunaris.listeners.WikiListener
23:17:40.855 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Pressed ctrl+c
23:17:41.057 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Got clipboard text:Rarity: Currency
Scroll of Wisdom
Stack Size: 37/40
Identifies an item
Right click this item then left click an unidentified item to apply it.
Shift click to unstack.
(java:14208): GLib-GIO-WARNING **: 23:17:41.060: /etc/xdg/kde-mimeapps.list contains a [Added Associations] group, but it is not permitted here.  Only the non-desktop-specific mimeapps.list file may add or remove associations.
23:17:41.091 DEBUG dev.tricht.lunaris.listeners.ClipboardListenerStack - Unregistered clipboard listener

I built  9d9fdf6ff9fbe66b13929ba2655d37e0c97d07bd for this.
Alt-D is still cut off to the right https://i.imgur.com/Qwlo4Df.jpg
Alt-A is working for me (at least with what i have around) https://i.imgur.com/c52v5UG.jpg
Alt-W works, but i also use the skill bound to W when using it. I'll probably just rebind it, but maybe a different default would help?
Alt-Q works as intended.
Pressing those outside of POE does not cause harm aside from overwriting the clipboard as far i can see btw, so theres that.
I'll test trading hotkeys etc as soon as im actually getting a whisper. Thanks for your work!
For reference, my system is
$ java --version
openjdk 11 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11+28)
OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)
$ echo $DESKTOP_SESSION
cinnamon
$ uname -a
Linux maltasar 5.4.10_2 #1 SMP PREEMPT Fri Jan 10 12:11:53 UTC 2020 x86_64 GNU/Linux

Steam is the Beta Client; Proton is  4.11; wine is 4.11 as well ($PROTONPATH/dist/bin/wine --version => wine-4.11)  and

authors: mkalte666 mtricht thorsten-passfeld

repo: mtricht/lunaris


text:
Add support for sending telemetry events on throws and exits

Relevant to your interests @martasaur.
@bryannaegele, is this compatible downstream as-is? Any changes I can / should make to help if not?

Looks like it's just expanding the scope of the current functionality and the signature is the same, so I think it would "just work"?

Yep, strictly additive

authors: bryannaegele mtrudel

repo: mtrudel/bandit


text:
Multiple queries fail with: Cannot read properties of undefined (reading 'undefined')

Description
Queries with more than one statement DML statement fail with error:
Cannot read properties of undefined (reading 'undefined')

Queries that fail
UPDATE postal_address
    SET address_1 = 'ACME inc.'
    WHERE person_id = 9;

SELECT * FROM postal_address WHERE person_id = 9;

USE dbThisSchema;
UPDATE postal_address
    SET address_1 = 'ACME inc.'
    WHERE person_id = 9;

SELECT * FROM postal_address WHERE person_id = 9;

UPDATE postal_address
    SET address_1 = 'ACME inc.'
    WHERE person_id = 9;

SELECT ROW_COUNT();

Queries that succeed
UPDATE postal_address
    SET address_1 = 'ACME inc.'
    WHERE person_id = 9;

USE dbThisSchema;
UPDATE postal_address
    SET address_1 = 'ACME inc.'
    WHERE person_id = 9;

Expected behavior
Expect result window with tab for result of each query.
Desktop (please complete the following information):

SQLTools Version  v0.27.1

VS Code Version: Version: 1.77.1,

Commit: b7886d7461186a5eac768481578c1d7ca80e2d21
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Darwin x64 21.6.0
Sandboxed: No

OS: Mac
Driver:

[ ] PostgreSQL/Redshift
[x] MySQL/MariaDB v0.5.1
[ ] MSSQL/Azure
[ ] SQLite
[ ] Other? Which...

Database version: MySQL v8.0.32

I've got the same issue.

I've got the same issue.

I have same issue as well

repo: mtxr/vscode-sqltools


text:
Make Event a concrete struct instead of an interface

The Event object are objects that only exit from the sse API: once they are out of the API, the consumer is free to do anything with it, as this will not affect us.
The definition is directly bound to the EventSource specification: the list of properties will not grow/shrink as long as the EventSource spec does not changes.

So I think that events should be exposed as concrete objects instead of interfaces. This removes one indirection layer.
I have a branch that implements this change but it is based on master, not on #24.

PS: I think that Event (whether it is a struct or an interface) has to change because it does not reflect the MessageEvent of the EventSource specification regarding the handling of IDs.

I see. I agree it needs to change, there is some work missing to fully mimic the MessageEvent interface. Also note the spec says the attributes should be readonly, interface looks nice for that, probably Data() should return string instead of []byte.

My branch also makes Data as a string, but mostly because the spec says everything is UTF-8.
The readonly-ness of MessageEvent is irrelevant to us. As I wrote, our Event are just existing the API. If the consumer want to make them readonly he can still convert them to a private struct with a public interface. But we should not impose him the cost of the interface indirection while it is not necessary from the inside.
I will improve my branch once #24 is merged.

I saw the commit, looks good. You convinced me. I just merged #24.

Also, feel free to name it MessageEvent if you want.

This pull request #28 has some improvements and fixes issue #26. However, I will bring some small conflicts on your work. I have no problem to keep it on hold until your work here is merged. If you don´t mind then I will merge it.

authors: alevinval dolmen

repo: mubit/sse


text:
draft: add openvoice backend

Part of https://github.com/mudler/LocalAI/issues/1126
Fixes: https://github.com/mudler/LocalAI/issues/1639

This needs more testing - but easier to do that with container images in master

repo: mudler/LocalAI


text:
Can't make the cell none-editable

Currently, the only way to make the field non-editable is by removing the type. We need to provide a flag to determine if the is cell is editable or not

Fixed with v0.1.0-beta.8 release

repo: muhimasri/b-editable-table


text:
MUI throws warning about theme override for selected state

Environment

Tech
Version

material-ui-pickers
2.0.5

material-ui
3.8.1

React
16.7.0

Browser
any

Peer library
date-fns

Steps to reproduce

Add theme override for MuiPickersDay.selected
Load a page with date picker on it

Expected behavior
No MUI warnings
Actual behavior
Material UI throws a warning:
Warning: Material-UI: the `MuiPickersDay` component increases the CSS specificity of the `selected` internal state.
You can not override it like this:
{
  "selected": {
    "backgroundColor": "#002d52",
    "color": "#fff",
    "&:hover": {
      "backgroundColor": "#003B64"
    }
  } ...
}

Instead, you need to use the $ruleName syntax:
{
  "&$selected": {
    "backgroundColor": "#002d52",
    "color": "#fff",
    "&:hover": {
      "backgroundColor": "#003B64"
    }
  }
}

https://material-ui.com/customization/overrides#internal-states

The code for this warning was introduced here:
https://github.com/mui-org/material-ui/pull/13919
It seems there are conventions around the specific keys 'disabled', 'focused', 'selected', 'checked'
Live example
https://codesandbox.io/s/vyx915vll7

@RobelTekle it worked for me after wasting few hours thanks.

Thanks for this. My code was working, but I was getting an error. I had to change:
MuiBottomNavigationAction: { selected: { color: "#2179ee", }, },
to:
MuiBottomNavigationAction: { root: { "&$selected": { color: "#2179ee", }, }, },
@jrwstevenson
remove the commas like this { root: { "&$selected": { color: "#2179ee" } } }

remove the commas like this { root: { "&$selected": { color: "#2179ee" } } }

@wkarim86 Thank you for supplying a code example of how to remove commas from a object.
Will this be more performant? Reduce the chance errors? Help in testing?  Or just shave off a few  kb and contradict my companies style guide of using comma dangle to prevent git blame issues?
Unsolicited and irrelevant advice written as an order is not helpful and does not make you look clever.

I have the following problem...
This works:
MuiInput: {
disabled: {
color: '#282c2e',
'&:before': {
borderColor: '#e5e5e5 !important',
pointerEvents: 'none',
},
}
},...
But this Material UI recommendation returns error:
"&$disabled": {
"color": "#282c2e",
"&:before": {
"borderColor": "#e5e5e5 !important",
"pointerEvents": "none"
}
}
How can I disable that annoying warning?
My version: "@material-ui/core": "^3.9.3",

I have the following problem...
This works:
MuiInput: {
disabled: {
color: '#282c2e',
'&:before': {
borderColor: '#e5e5e5 !important',
pointerEvents: 'none',
},
}
},...
But this Material UI recommendation returns error:
"&$disabled": {
"color": "#282c2e",
"&:before": {
"borderColor": "#e5e5e5 !important",
"pointerEvents": "none"
}
}
How can I disable that annoying warning?
My version: "@material-ui/core": "^3.9.3",

the same problem

Same issue here with MuiListItem disabled
@andrispraulitis

The MuiListItem Component is a Component of the @material-ui/core package and isnt in any relation with this project.
But never mind - I can help you :)
Just do something link this in your theme:
"MuiListItem": {
     "root": {
          "&$disabled": {
                // your disabled styles here
          }
     }
}

It works for my MuiButton

authors: jrwstevenson michaeldaineka novascreen pmasharov rafamem wkarim86

repo: mui-org/material-ui-pickers


text:
Unable to use selected class of MenuItem to style backgroundColor

According to docs MenuItem allows to pass selected class. I want to use it to overwrite color and background color of selected item. However, only color property is applied, backgroundColor not.

[x] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
backgroundColorshould be applied without !important. Also, there is a weird ripple effect with color equal to color which you can see on example below, which I am not sure is a correct behaviour.

Current Behavior
backgroundColor is not applied, unless used with !important.

Steps to Reproduce (for bugs)
Go to https://codesandbox.io/s/oxlp02w4o5 and just play with item selection, see that only color is applied, not backgroundColor and observe a weird ripple effect.

Your Environment

Tech
Version

Material-UI
v1.2.1

React
16.4

browser
latest Chrome

@oliviertassinari I hope it is not considered as a question? Bot seems to be wrong ;)

@klis87 It's a recurrent question.

Following the documentation and how style modifiers are handled, you need to increase the specificity:
https://material-ui.com/customization/overrides/#overriding-with-classes.
https://codesandbox.io/s/093ow40jw

@oliviertassinari Apologies it this is a duplicate, and thx for your patience. I investigated for instance #10961, but I really find this rule not logical and I thought that my way should also work, and why color works and backgroundColor doesnt? It should be consistent at least.
Also, pls see this video: http://nimb.ws/kCailh
You can see color flickering there, is it intended behaviour?

@oliviertassinari I guess I answered question about color myself, it was not set by any css rule in contrast to backgroundColor, hence !important wasnt necessery.
However, this flickering is an issue I thing, I you would like, I could create another issue if this is indeed a bug.

@klis87 I can't reproduce your flickering issue.

but did u see a movie?

repo: mui-org/material-ui


text:
ADA Compliance documentation

It would go a long way to help pitch Material UI as a solution if I could link to documentation covering the library's support for ADA compliance.
I know Material UI does have at least some support for ADA/WCAG compliance, for instance through the use of "aria-" and "role" html attributes throughout the codebase to assist screen readers and the support for keyboard navigation such as in the Select component.
Meanwhile, Material Design itself seems to lend itself nicely to following the WCAG guideline, for instance with regards to readability, navigation and high contrast text.
However, without being a core contributor myself, I cannot speak to the library's compliance overall. I searched the material-ui.com website as well as past/present GitHub tickets and could not find a page in the documentation whose sole purpose was to outline what it does and does not do to be ADA compliant. Therefore, I am opening this ticket as a feature request to please create said documentation.

Hello! I'm really glad to join this thread about ADA. I found great article about WCAG & ADA web compliance. If you want you can read it and share your thoughts after reading. Hope you like it! Because I found it really useful.

Does anyone know an audit accessibility company that could audit all our components for the ADA compliance? Bonus point if they can sponsor it for a popular OSS project.

We've been using https://www.powermapper.com/buy/all/sortsite/
On Wed, May 15, 2019, 6:12 AM Olivier Tassinari notifications@github.com
wrote:

Does anyone know an audit accessibility company that could audit all our
components for the ADA compliance? Bonus point if they can sponsor it for a
popular OSS project.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mui-org/material-ui/issues/14187?email_source=notifications&email_token=ABLMBUK5KMQILUUSVMKF3F3PVPVZ5A5CNFSM4GQFAB22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVOKMLQ#issuecomment-492611118,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLMBUJ6D3QHNW3G4UI34O3PVPVZ5ANCNFSM4GQFAB2Q
.

@bramick I'm looking for manual tests.

This might be a good one to reach out to: https://accessible360.com/
Michele Landis looks like a good member to reach out to.
--
R. Blake Ramick
Mobile: 214.454.5760
www.LinkedIn.com/in/bramick
On Wed, May 15, 2019 at 9:13 PM Olivier Tassinari notifications@github.com
wrote:

@bramick https://github.com/bramick I'm looking for manual tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mui-org/material-ui/issues/14187?email_source=notifications&email_token=ABLMBUOHD2X4CB5P7XVO3MLPVS7LPA5CNFSM4GQFAB22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQOLNQ#issuecomment-492889526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLMBUNOFFKIZLM2OQJ2723PVS7LPANCNFSM4GQFAB2Q
.

Or perhaps https://www.linkedin.com/in/connor-born-b8738328/
R. Blake Ramick
Mobile: 214.454.5760
www.LinkedIn.com/in/bramick
On Thu, May 16, 2019 at 8:47 AM Blake Ramick bramick@gmail.com wrote:

This might be a good one to reach out to: https://accessible360.com/
Michele Landis looks like a good member to reach out to.
--
R. Blake Ramick
Mobile: 214.454.5760
www.LinkedIn.com/in/bramick
On Wed, May 15, 2019 at 9:13 PM Olivier Tassinari <
notifications@github.com> wrote:

@bramick https://github.com/bramick I'm looking for manual tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mui-org/material-ui/issues/14187?email_source=notifications&email_token=ABLMBUOHD2X4CB5P7XVO3MLPVS7LPA5CNFSM4GQFAB22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQOLNQ#issuecomment-492889526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLMBUNOFFKIZLM2OQJ2723PVS7LPANCNFSM4GQFAB2Q
.

Our components won't meet WCAG by default. The look&feel are more important (see #22541). It's not viable to document all possible techniques to makes the components meet WCAG 2.1. We'll revisit this in the future once we have the bandwidth for it.

oliviertassinari reopened this in 1 hour

@oliviertassinari Did you change your mind after #22541? Could you explain why you want to follow ADA but not WCAG?

@eps1lon From what I understand this issue is about providing a list of all the known issues around accessibility. With a comprehensive list, we could then prioritize work on the most important items. With such a list, developers can then evaluate each component and decide if they want to use it or not, individually. So I think this should stay open until we can provide a comprehensive list. I think it's where an a11y audit with severity for each failure would help a lot. I would be leaning toward doing both an internal and external audit.
Regarding the Rating, I believe that by using different shapes (in addition to the different existing colors) we can address 1.4.1: #22554.
Can somebody confirm that ADA compliance is reached with the AA level of WCAG?
Regarding the look & feel, I don't think that great looking application makes it impossible to have them accessible. However, it makes it harder, and I don't t think that it's something we should trade.
Why? Because it seems that most product teams make the same tradeoff. If Material-UI isn't used, whatever advancement we bring to the a11y won't have as much impact as it could have.

ADA recommends WCAG AA 2.0... (note 2.1 is now out)
On Thu, Sep 10, 2020, 1:22 PM Olivier Tassinari notifications@github.com
wrote:

@eps1lon https://github.com/eps1lon From what I understand this issue
is about providing a list of all the known issues around accessibility.
With a comprehensive list, we could then prioritize work on the most
important items. With such a list, developers can then evaluate each
component and decide if they want to use it or not, individually. So I
think this should stay open until we can provide a comprehensive list. I
think it's where an a11y audit with severity for each failure would help a
lot. I would be leaning toward doing both an internal and external audit.
Regarding the Rating, I believe that by using different shapes (in
addition to the different existing colors) we can address 1.4.1: #22554
https://github.com/mui-org/material-ui/pull/22554.
Can somebody confirm that ADA compliance is reached with the AA level of
WCAG?
Regarding the look & feel, I don't think that great looking application
makes it impossible to have them accessible. However, it makes it harder,
and I don't t think that it's something we should trade.
Why? Because it seems that most product teams make
https://material-ui.com/blog/2020-developer-survey-results/#6-what-are-your-key-criteria-when-choosing-a-ui-library
the same tradeoff. If Material-UI isn't used, whatever advancement we bring
to the a11y won't have as much impact as it could have.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mui-org/material-ui/issues/14187#issuecomment-690656196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLMBUNF52J24S2VULIPPDDSFERN7ANCNFSM4GQFAB2Q
.

A benchmark of the type of outcome we can expect from this issue:

https://www.telerik.com/kendo-react-ui/components/accessibility/accessibility-compliance/
https://ej2.syncfusion.com/react/documentation/accessibility/
https://ag-grid.com/javascript-grid-accessibility/

Note that I could only find that on paid UI libraries, and considering we are pushing in this direction, it makes sense to move forward on this issue too. In the public roadmap, we have an item on this matter.
Out of this benchmark, I would propose the following plan:

We add a new https://material-ui.com/discover-more/accessibility/ page.
This page starts with an overview, e.g. https://www.telerik.com/kendo-react-ui/components/accessibility/
The page continues with a compliance section: e.g. https://www.telerik.com/kendo-react-ui/components/accessibility/accessibility-compliance/.
We run an internal and/or an external audit. Maybe could continue on the initial idea of @chaance in https://github.com/reach/reach-ui/issues/439#issuecomment-581536853.
In the compliance section, we link each ## Accessibility section component have, for instance, the DataGrid or #20600.

I will look into it and report back here what (if anything) has evolved from a MUI centric effort.  Soon after my post here the focus shifted to feature based compliance which makes more sense and closing gaps with middleware (internal api library) which can also be faulted for being too opaque and breaking a11y features supported by MUI.  Another downside to the middleware approach is the massive version gap (major versions behind).  The biggest issues we found in our own features where the following

keyboard navigation and tab focus indicator (sliders, tabs, menus, floating menus, drawers, modals, clickable toasts, popover focus, chip adornments)
color contrast ratio (purely design issue) 5:1 is pretty stark
high contrast mode (partially blind)
lots of grid keyboard navigation issues particularly around headers, grouped headers, footer and embedded footer components (not MUI)
label targeting (example label-for must be an id and thusly global)
mostly lots of issues with screen reader but without a JAWS license you can't even test this as it is the de-facto standard for blind users on desktop, don't even bother with NVDA
since then MUI has come a very long way indeed supporting most (if not all the issues mentioned) but now you have a grid so welcome to that world of pain

Just seeing this because I was tagged, but:

mostly lots of issues with screen reader but without a JAWS license you can't even test this as it is the de-facto standard for blind users on desktop, don't even bother with NVDA

I believe this is a mistake. NVDA has gained significant market adoption in the past several years. This survey by WebAIM was in 2019 and showed NVDA actually overtaking JAWS for the #1 spot. https://webaim.org/projects/screenreadersurvey8/
NVDA is available for free. It is very much worth getting a JAWS license if possible and testing on both platforms if at all possible, given their large user base.

It is very much worth getting a JAWS license and testing on both platforms

It really does need to be tested by someone who uses these tools on a daily basis though. Getting a license isn't necessarily the issue, it's having the experience to know whether the output "makes sense" to a regular screen reader user.

Would a11y audits be performed for both styled and unstyled components (something to consider as v5 is being planned)?

It is very much worth getting a JAWS license and testing on both platforms if at all possible, given their large user base.

My problem is that this is a one-year license that I still don't even know how to get in Germany. After that you're stuck with an older version. I don't know how upgrades are handled by actual users. Do they upgrade every year? Every 5 years? If almost everybody is on the latest version then how useful is testing for 1-2 year old versions?

It really does need to be tested by someone who uses these tools on a daily basis though.

While I agree with that generally I don't think you need it for component testing. Most of SR related bugs are components flat out not working.
For testing UI itself app devs are responsible. We're also not testing usability of our components with actual users.

Would a11y audits be performed for both styled and unstyled components

Styled for now. For unstyled we first would need to determine what kind of properties we want to audit. For example, it wouldn't make much sense to audit "use of color" for the unstyled variant since the color is most certainly changed when people use the unstyled variant.

FWIW I think unstyled components are likely more a11y compliant than styled because the contrast ratio doesn't come into play (just user defaults) and fewer edge cases to worry about wrt specificity for user defined styles

FWIW I think unstyled components are likely more a11y compliant than styled because the contrast ratio doesn't come into play (just user defaults)

Sure but what is an audited component worth if it's never used in its default state? Styled components are much more likely to be used as-is or with little changes.
We're not choosing the version that is more likely to pass but the version where an audit is useful to the end-user.

authors: Mobilunity-Com bramick chaance eps1lon jmadson josgraha mbrookes oliviertassinari petermikitsh