text:
wrong biome color for all 1.18+ biomes (through 1.19.4+)

Snowy peaks, etc, all have the wrong biome color

What is "wrong" with these colors?

jagged peaks is using the mushroom island color. meadows are using the desert color. snowy peaks are using the swamp color.

RBG Values that are used:
Stony Peaks		BF 00 FF
Mushroom Fields	FF 00 FF
Meadow			FF 95 00
Desert			FA 94 18
Snowy Slopes		00 FF D5
Swamp			07 F9 B2
So no, they do not use "the same" color.
But yes, the color is maybe not chosen well.
It is on my list to rework Biome colors anyway (mostly 1.18). I'm not sure if I will do that this summer.
But if you like, you can suggest "better" colors.
At the moment good colors are missing definitely for:
"minecraft:meadow",
"minecraft:mountain_meadow"
"minecraft:grove",
"minecraft:mountain_grove"
"minecraft:snowy_slopes",
"minecraft:frozen_peaks",
"minecraft:lofty_peaks"
"minecraft:snow_capped_peaks"
"minecraft:stony_peaks",
"minecraft:jagged_peaks",
"minecraft:lush_caves",

These are the biome colors for 1.18+ biomes that better correlate with the mountain biomes. Chunkbase and cubiomes use similar colors. Since 1.20 cherry grove will be added it will be shown here:
minecraft:meadow = #60A445
minecraft:stony_peaks = #7B8F74
minecraft:grove= #47726C
minecraft:jagged_peaks = #DCDCC8
minecraft:snowy_slopes = #C4C4C4
minecraft:frozen_peaks = #B0B3CE
minecraft:lush_caves = #283C00
minecraft:dripstone_caves = #4E3012
minecraft:deep_dark = #031F29
minecraft:mangrove_swamp = #24C48E
minecraft:cherry_grove = #FF91C8

Cherry Grove was already added with same color than Chunkbase.
I'm in contact with Cunkbase to align colors in the future. That is the job for this summer.
We used all AMIDST colors as long as this project was alive (up to 1.17). 1.18 and 1.19 was just random colors and with 1.20 I started to align with Chunkbase.

Could you please describe in more detail how you get to your colors? A description of a method, algorithm or other way to explain why the color is exactly like it is.
Here are some examples from my color choice:

minecraft:dripstone_caves #bc8f8f is located underground with large caves, so it should have some visible contrast on deeper Y levels. A very distinctive Block in these Biome is the Dripstone. Therefore I selected a color similar to it.
minecraft:cherry_grove#F7B9DC by chance I had Chunkbase open in that moment and I liked the color used there and just took it.

Chunkbase has the colors for 1.18/1.19 biomes, they should be similar to the colors above. The colors listed are from cubiomes.
I supposed the chunkbase colors could be used instead.

Link to color definition in cubiomes repository:
https://github.com/Cubitect/cubiomes/blob/960d5d64b61125eb09e72bfec70a0ffe439d01b0/util.c#L263

Alright, the new colors seem to be an improvement. One suggestion, change  "Unknown Biome", to render as #000000 color, since it seems to be falling back to plains, which causes confusion with unloaded chunks in the biome map view.

Yes, color alignment is in progress...
A very dark color might be mixed up with minecraft:deep_dark.
But at the moment it seems to be a random color for Unknown Biome, which is also not ideal.

#365 ensures a fixed color for "Unknown Biome"

repo: mrkite/minutor


text:
IMDB Watchlist

I can not access my Watchlist as my IMDB username begins with UR and specto only let's me enter numbers and not letters.

Hi, did you get this issue resolved? I to have the same problem, tried entering with just numbers, and also with UR and numbers but Specto not pulling my IMDB account.

I have same issue but i can't enter the UR letters as specto doesn't give me the full keyboard only numeric 0-9 and i'm pretty sure it won't work without the UR in the userid. On exodus it gives me full keyboard to enter urxxxxxx and imdb works great on exodus, You also MUST have your watchlist set to public for it to import it's default is set to private.

Hi,
No the problem is still the same. I use Exodus now, which is better than
the specto I think.
On 5 Oct 2016 23:48, "onthatb0mbshell" notifications@github.com wrote:

Hi, did you get this issue resolved? I to have the same problem, tried
entering with just numbers, and also with UR and numbers but Specto not
pulling my IMDB account.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/457#issuecomment-251822005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUW8ZSgYyEgFrc4EHimqq-KWOR4UmShUks5qxClTgaJpZM4Jw_Ah
.

source: gharchive/issue

repo: mrknow/filmkodi

license_type: permissive

license_source: bigquery


text:
Utf-8 doesnt work in IE9 w/o forceJSONP=true

Messages containing utf-8 (cyrillic for example) cause parse error on client in IE9 (without forcibly enabled jsonp)

I just updated the netty-socketio-demo. You should set utf-8 charset as meta param in your html head section.

didnt help

do you use 1.3.3 client?

yep

(without forcibly enabled jsonp) how did you do that?

(without forcibly enabled jsonp) how did you do that?

i simply did not set forceJSONP: true in io.connect opts
in that case socket.io.js uses b64=1 for IE9 (at least IE9, not sure about all other old browsers)

i have tried var socket =  io.connect('http://localhost:9092', {'forceJSONP': true}); and var socket =  io.connect('http://localhost:9092', {'forceJSONP': false}); and didn't encounter any problems with utf-8 encoding.

ok, i'll retry again with latest version from master and will provide test project if issue still exists

IE9 with default opts:

LOG: socket.io-client:manager readyState opening +2ms
LOG: socket.io-client:manager open +232ms
LOG: socket.io-client:socket transport is open - connecting +0ms
LOG: socket.io-parser decoded 0 as %j +0ms[object Object]
LOG: socket.io-client:manager error +17sError: server error
LOG: socket.io-client:manager writing packet %j +6s[object Object]
LOG: socket.io-parser encoding packet %j +23s[object Object]
LOG: socket.io-parser encoded %j as [object Object] +0ms2["chatevent",{"userName":"user56","message":"ыыыыыы"}]
LOG: socket.io-client:manager error +87msError: server error

latest Chrome with opts {forceBase64: true, transports: ['polling']};:

 engine.io-client:polling-xhr xhr data null +1ms
socket.io.js:1 socket.io-client:manager writing packet %j +6s Object {type: 2, data: Array[2], nsp: "/"}
socket.io.js:1 socket.io-parser encoding packet %j +6s Object {type: 2, data: Array[2], nsp: "/"}
socket.io.js:1 socket.io-parser encoded %j as Object +2ms 2["chatevent",{"userName":"user123","message":"бла"}]
socket.io.js:2 engine.io-client:socket flushing 1 packets in socket +7s
socket.io.js:2 engine.io-client:polling-xhr xhr open POST: http://socketio.dev/socket.io/?EIO=3&transport=polling&t=1423333172300-3&b64=1&sid=488054a6-e1c4-4375-8916-4b2a4462d270 +3ms
socket.io.js:2 engine.io-client:polling-xhr xhr data 57:42["chatevent",{"userName":"user123","message":"Ð±Ð»Ð°"}] +14ms
socket.io.js:2 engine.io-client:polling polling got data 57:42["chatevent",{"userName":"user123","message":"бла"}] +73ms
socket.io.js:2 engine.io-client:socket socket receive: type "error", data "parser error" +1ms
socket.io.js:1 socket.io-client:manager error +98ms Error: server error {code: "parser error", stack: (...), message: "server error"}

i guess no need to publish test project cuz i'm using master branch of backend without any changes + master branch of netty-socketio-demo with only changes - url

btw, this issue is fixed in my fork. hope it would be helpful for you, @mrniko

Ready! i migrated to your processUtf8 ;)

authors: alim-akbashev mrniko

repo: mrniko/netty-socketio


text:
Redisson store doesn't work in version 1.7.7

In version 1.7.7, I try to use RedissonStore, but it doesn't work while it works well in version 1.6.7.
I find from the source code, some code store the HandshakeData into redis in the AuthorizeHandler was removed from  version 1.7.7.
What need to do in version 1.7.7 if I want to store  something into redis with Redisson, for example HandshakeData?
Also I found the default store way is MemoryStore, but the method createMap in store factory is never called anywhere, which confused me.
Could you give me some help?
Thanks.

The HandshakeData now stores in com.corundumstudio.socketio.handler.ClientHead object. So storing in memoryStore is not needed anymore

And for the whole StoreFactory(RedissonStore, HazelcastStore, MemoryStore) module will not needed anymore? Because I don't find anywhere to store data with them or get data from them.
Thanks.

createStore and pubSubStore are still in use

@fcbflying Did you resove the problem?

authors: fcbflying mrniko


text:
Polling clients sporatically get prematurely disconnected

When running under load with ~500+ polling clients, we are seeing their connections getting disconnected from the server side causing a 'bloat' of TIME_WAIT connections on the server.
Under certain circumstances this bloat might exceed the configured limit on the back end system and thus cause a failure.
After some investigation and 'stack dumps' we found a common stack trace (see below).
Basically the EncoderHandler on sendMessage issues a writeandFlush().addListener(ChannelFuture.CLOSE);   which does fire and closes the channel.
We have subclassed EncoderHandler; copied all of the behavior EXCEPT for this 'addListener()',
and have run without the close issue and the channel is getting 'reused'.
Further investigation/testing is needed, but this appears to be 'a bug' as the client should initiate the close thus preventing TIME_WAIT bloat and introducing a 'possible' efficiency of channel reuse.
Please investigate on your end to verify this was your specific intent at line 162 in EncoderHandler.java.
Stack trace captured at NioSocketChannel in netty, but stems from EncoderHandler.handleHTTP
Thu Aug 06 15:20:10 EDT 2015 javaChannel().close() java.nio.channels.SocketChannel[connected local=/127.0.0.1:12013 remote=/127.0.0.1:53769]
java.lang.Throwable
at io.netty.channel.socket.nio.NioSocketChannel.dumpStack(NioSocketChannel.java:60)
at io.netty.channel.socket.nio.NioSocketChannel.doClose(NioSocketChannel.java:237)
at io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:558)
at io.netty.channel.DefaultChannelPipeline$HeadContext.close(DefaultChannelPipeline.java:1098)
at io.netty.channel.AbstractChannelHandlerContext.invokeClose(AbstractChannelHandlerContext.java:543)
at io.netty.channel.AbstractChannelHandlerContext.close(AbstractChannelHandlerContext.java:528)
at io.netty.channel.ChannelOutboundHandlerAdapter.close(ChannelOutboundHandlerAdapter.java:71)
at io.netty.channel.AbstractChannelHandlerContext.invokeClose(AbstractChannelHandlerContext.java:543)
at io.netty.channel.AbstractChannelHandlerContext.close(AbstractChannelHandlerContext.java:528)
at io.netty.channel.ChannelOutboundHandlerAdapter.close(ChannelOutboundHandlerAdapter.java:71)
at io.netty.channel.AbstractChannelHandlerContext.invokeClose(AbstractChannelHandlerContext.java:543)
at io.netty.channel.AbstractChannelHandlerContext.close(AbstractChannelHandlerContext.java:528)
at io.netty.channel.AbstractChannelHandlerContext.close(AbstractChannelHandlerContext.java:394)
at io.netty.channel.DefaultChannelPipeline.close(DefaultChannelPipeline.java:887)
at io.netty.channel.AbstractChannel.close(AbstractChannel.java:181)
at io.netty.channel.ChannelFutureListener$1.operationComplete(ChannelFutureListener.java:44)
at io.netty.channel.ChannelFutureListener$1.operationComplete(ChannelFutureListener.java:41)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:680)
at io.netty.util.concurrent.DefaultPromise.notifyLateListener(DefaultPromise.java:621)
at io.netty.util.concurrent.DefaultPromise.addListener(DefaultPromise.java:138)
at io.netty.channel.DefaultChannelPromise.addListener(DefaultChannelPromise.java:93)
at io.netty.channel.DefaultChannelPromise.addListener(DefaultChannelPromise.java:28)
at com.corundumstudio.socketio.handler.EncoderHandler.sendMessage(EncoderHandler.java:162)
at com.corundumstudio.socketio.handler.EncoderHandler.sendMessage(EncoderHandler.java:146)
at com.corundumstudio.socketio.handler.EncoderHandler.handleHTTP(EncoderHandler.java:258)
at com.corundumstudio.socketio.handler.EncoderHandler.write(EncoderHandler.java:197)
at io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:633)
at io.netty.channel.AbstractChannelHandlerContext.access$1900(AbstractChannelHandlerContext.java:32)
at io.netty.channel.AbstractChannelHandlerContext$AbstractWriteTask.write(AbstractChannelHandlerContext.java:908)
at io.netty.channel.AbstractChannelHandlerContext$WriteAndFlushTask.write(AbstractChannelHandlerContext.java:960)
at io.netty.channel.AbstractChannelHandlerContext$AbstractWriteTask.run(AbstractChannelHandlerContext.java:893)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:380)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
at java.lang.Thread.run(Thread.java:745)

We have found through wire analysis that the socket io server is not supporting piggy-backed message parts for polling clients.
We see socket.io js v1.3.5 polling clients sending messages and the underlying socket.io js code piggy-backs a ping on that same message  resulting in form:  ":[app-message]1:2" as the basic payload.
The socket.io server in the PollingTransport will only read and process the ":[app-message]" message and 'drop' the "1:2" piggy-backed message. Line 158  PollingTransport.java   v1.7.7 of socket-io server.
We are attempting to work around this by subclassing PollingTransport and pulling out the
code from decoder.preprocessJson(jsonIndex, content) into a new method that will return a LIST of ByteBuf by parsing the content in a loop stripping out each message part into a ByteBuf.
And then issuing multiple ctx.pipeline().fireChannelRead(new PacketsMessage(client, content, Transport.POLLING)); with each ByteBuf.
The side effect of us not doing this is the socket.io server does not respond to PING messages and the client 'gives up' and camps out without sending any other ping.... then it times out, and disconnects.

could you provide a client code to test it?

I don't have a generic client for a generic server, but reproducing it with 1 javascript client is fairly easy:

have javascript client connect up as polling (IE-11 should do)
After connect use javascript toInterval to emit a message every 10ms
I tried 500ms, 250ms, 100ms  no luck.... 10ms does it you get piggy backs quite regularly.
I have code handling it in the spot I indicate above and am able to see the piggy-backed messages with no issue. and (as you'd expect) it varies:
ping piggybacked on emit.
2 emits are piggy backed sometimes
emit piggybacked on ping

my piggyback code handles as many piggy backs until end of content, but I'm only seeing ~2 msgs per content tops.

I'm having a similar issue.  I wrote a quick client and pointed it against the netty-socketio-demo server.
I see this on the server side (started with mvn exec:java as the docs stated).
[nioEventLoopGroup-3-11] ERROR com.corundumstudio.socketio.transport.PollingTransport - 97a8f14f-1168-4c1f-ba01-f8230683d024 is not registered. Closing connection

And on the client:
Error! [com.github.nkzawa.engineio.client.EngineIOException: xhr poll error]

The client code is available at:  https://github.com/ryandietrich/socketIOStress
Fire up the demo server, then compile the code and run the "run_polling" and notice the errors that will spew out of the demo server.  Then restart the demo server (it doesn't re-use the port, so your OS may take a second or two to let go of the port before you can restart).  Then run the "run_websocket" and notice the lack of errors spewing out of the demo server (though depending on your ulimit you may run into thread limitations as this particular client spawns a thread for every connection (ugh!).

I think this issue is exacerbated by the policy change from socketIO 0.9 to 1.0.  Before it had a downgrade policy, and now it has an upgrade policy, meaning the javascript client will start with polling and will upgrade if the server says it is capable of supporting websockets.  To address this my team has added some client side detection and specified the transport instead of letting the client start with Polling.

We worked around the bug, and it is a bug. Very easy to fix, pain to work around.
ROOT CAUSE: PacketDecoder.preprocessJson()

strips out the 'd='     good
clean up the '\\n'    good
But then.... the bad:
parses the content to strip out only the 1st message in the payload, and then returns that to the calling class (PollingTransport.onPost())
FIX:
do not parse the content after strip out and clean up. Simply return the RESULTING payload up.

The remainder of the code tree handles piggy-backed messages nicely.
Our work around was painful because the bug is fairly 'deep' in the framework, so we had to subclass it from the SocketIOChannelInitializer down for a simple fix like this.

BTW: Nkzawa does NOT support JSONP polling it only does XHR, and so this pariticular piggy-back issue we found is NEVER hit by Nkzawa.   We are using both NKzawa and regular javascript clients and hit this issue with javascript.
I would advise you force Websockets with nkzawa clients this can easily be done.

So, is the test program I wrote hitting a totally different problem entirely?  socketIOStress is merely connect/disconnecting very quickly.  When you specify Polling transports, problems pop out of everywhere.  With websockets, no issues are seen.  Are you saying Websockets also have problems?

We have been using 2 varieties of load testing clients:
Node.JS using the stock latest socket.io js client
Java/Grinder load using Nkzawa client.
In both cases we have used polling clients along with websocket clients.
We're talking 3,000 polling and 12,000 total (9,000 websocket).
We did take to using the Node.JS more for polling clients because Nkzawa did not perform as well.
BUT Nkzawa was working at around 300-500 polling clients, with some sporadic connection drops which we have since attributed to the CLIENT (nkzawa) code because we don't see the same issue in our JS client.
Taking the long way to answer your question: 'yes' its a different problem entirely.

Oh, and to add to the rest of the setup:

We achieved these numbers AFTER fixing the piggy-backed JSONP issue (see mention in prior comment above)
We use NginX to 'offload' the SSL handling (I had previously posted another issue on slowness of SSL; many responded with NginX, and the slowness is (of course) common)

I am also facing the same issue as @ryandietrich When the client is using a browser not supporting websockets, it falls back to polling. It works for few seconds and then I see the same messages as pointed out by @ryandietrich :
Client Side:
Error: xhr post error at XHR.Transport.onError
Server Side:
2015-12-02 19:54:08,241 ERROR nioEventLoopGroup-3-40 PollingTransport 1045fa15-8c1e-40d8-b1a1-a030eed32fb4 is not registered. Closing connection
2015-12-02 19:54:08,248 ERROR nioEventLoopGroup-3-41 PollingTransport 1045fa15-8c1e-40d8-b1a1-a030eed32fb4 is not registered. Closing connection
Is this issue fixed? I am on version "1.7.5".

@pramodbms
Could you try to comment out .addListener(ChannelFutureListener.CLOSE) at EncoderHandler:162. And report me, does it help to resolve problem?

authors: lpage30 mrniko pramodbms ryandietrich


text:
How to set focus once to be the closest possible (ex for macro photography)❓

Question
Is there a way to set focus on a "device" to be fixed (unchanged) and be the closest possible?
How would I approach that?
P.S. Thank you for offering this great library!
What I tried
I know that the Camera API offers "Focus" function but that is based on a given Point (x.y).
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 questions in the issues page as well as in the discussions page and found none.

Hey!
Not sure about that, focus seems to turn off after a while again. Perhaps a workaround would be to repeatedly call it?

Hey - this is not a question but more like a feature request. Currently you can only focus on x,y screen coords, but I could add a feature to focus on a specific ƒ length. Create a feature request so I can track this for V3 :)

authors: cyprian mrousavy

repo: mrousavy/react-native-vision-camera

license: MIT

license_source: github-api


text:
🛑 Student Information System is down

In 92465ad, Student Information System (https://filemaker.oca.ac.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Student Information System is back up in eb7edc2.

repo: mrvinceo/ocaUptime


text:
i'am use put encounter 'Could not create file';

[connection] < '220 (vsFTPd 2.0.5)\r\n'
[parser] < '220 (vsFTPd 2.0.5)\r\n'
[parser] Response: code=220, buffer='(vsFTPd 2.0.5)'
[connection] > 'USER zgb'
[connection] < '331 Please specify the password.\r\n'
[parser] < '331 Please specify the password.\r\n'
[parser] Response: code=331, buffer='Please specify the password.'
[connection] > 'PASS Zgb4399'
[connection] < '230 Login successful.\r\n'
[parser] < '230 Login successful.\r\n'
[parser] Response: code=230, buffer='Login successful.'
[connection] > 'FEAT'
[connection] < '211-Features:\r\n EPRT\r\n EPSV\r\n'
[connection] < ' MDTM\r\n PASV\r\n REST STREAM\r\n SIZE\r\n TVFS\r\n UTF8\r\n211 End\r\n'
[parser] < '211-Features:\r\n EPRT\r\n EPSV\r\n MDTM\r\n PASV\r\n REST STREAM\r\n SIZE\r\n TVFS\r\n UTF8\r\n211 End\r\n'
[parser] Response: code=211, buffer='Features:\r\n EPRT\r\n EPSV\r\n MDTM\r\n PASV\r\n REST STREAM\r\n SIZE\r\n TVFS\r\n UTF8\r\nEnd'
[connection] > 'TYPE I'
[connection] < '200 Switching to Binary mode.\r\n'
[parser] < '200 Switching to Binary mode.\r\n'
[parser] Response: code=200, buffer='Switching to Binary mode.'
/Users/caozhihui/Desktop/code/web/module/androidMobile/resource/release/index.css
[connection] > 'PASV'
[connection] < '227 Entering Passive Mode (192,168,51,203,213,48)\r\n'
[parser] < '227 Entering Passive Mode (192,168,51,203,213,48)\r\n'
[parser] Response: code=227, buffer='Entering Passive Mode (192,168,51,203,213,48)'
[connection] PASV socket connected
[connection] > 'LIST'
[connection] < '150 Here comes the directory listing.\r\n'
[parser] < '150 Here comes the directory listing.\r\n'
[parser] Response: code=150, buffer='Here comes the directory listing.'
[connection] < '226 Directory send OK.\r\n'
[parser] < '226 Directory send OK.\r\n'
[parser] Response: code=226, buffer='Directory send OK.'
{ type: 'd',
name: 'www.4399.cn',
target: undefined,
sticky: false,
rights: { user: 'rwx', group: 'rwx', other: 'rwx' },
acl: false,
owner: '0',
group: '0',
size: 4096,
date: 2014-06-27T00:00:00.000Z }
[connection] > 'PASV'
[connection] < '227 Entering Passive Mode (192,168,51,203,157,117)\r\n'
[parser] < '227 Entering Passive Mode (192,168,51,203,157,117)\r\n'
[parser] Response: code=227, buffer='Entering Passive Mode (192,168,51,203,157,117)'
[connection] PASV socket connected
[connection] > 'STOR ./foo.remote-copy.txt'
[connection] < '553 Could not create file.\r\n'
[parser] < '553 Could not create file.\r\n'

I have a same problem, but my webstorm can upload files to same remote dir.

I have a same problem,but it is successful with FLASHFXP

I think you simply have no right to upload to the root folder. Use cwd function:
c.on('ready', function() {
  c.cwd('www.4399.cn', function() {
    c.put('foo.txt', 'foo.remote-copy.txt', function(err) {
        if (err) throw err;
        c.end();
      });
  });
});

我也遇到了同样的问题,无法新建文件夹,你们解决了吗,求告知
I have the same problem. I cannot create a new folder. Have you solved it? Please let me know

I have the same problem and I find that I think the file in FTP server is the remote file but it's the local file in the method, so maybe you can try to exchange the location of the parameters.

authors: OmegaZhou hjaiim icetee qiuzx20 rainer800hao sowdf

repo: mscdex/node-ftp

license: mit


text:
🛑 Do53 Roost IPv4 TCP is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv4 TCP is back up in c0de354 after 9 minutes.

repo: mschirrmeister/upptime-loopx


text:
🛑 Do53 Roost IPv4 TCP is down

In 2231e59, Do53 Roost IPv4 TCP (http://107.189.10.142:9203) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv4 TCP is back up in 100da4a after 9 minutes.


text:
Support: Gemini Pro Vision

Would you support Gemini Pro Vision API in your package?

Hi @doggy8088
What do you mean? It is already in since the very commit.
See tests and there in particular the files GoogleAi_GeminiProVision_Should.cs and VertexAi_GeminiProVision_Should.cs
The only change needed is to specify the model: Model.GeminiProVision and you are good to go.
Hint: See the type Model which lists all model names supported by the package.
All other methods work as expected. Since release 0.9.0 there are compatibility methods for the older PaLM 2 models.
Please let me know what's missing and I'll look into it.

I see. I didn't realize that. It because I don't see any example in your README.

Kindly look at the tests...
There is everything coded with examples. Every feature and functionality has a test.

Dear @doggy8088
The README has been extended. Thanks for pointing this out.

@jochenkirstaetter Don't you consider let TestExtensions.ReadImageFileBase64Async built-in to your library?

@doggy8088 yes, that's what I did today. There's going to be a Generative Content Request.AddMedia method with the next release that abstracts the handling of images. Probably tonight. Still writing the tests and checking against VertexAI. But it works with GoogleAI.
Bear with me...

Nice to hear. 👍

repo: mscraftsman/generative-ai


text:
直接检出有问题，即便我修改了Gradle也无济于事

Gradle 'clip-image-master' project refresh failed
Error:Could not find property 'BINTRAY_USER' on project ':clipimage'.

注释掉apply from 'bintray.gradle'这一行即可。

ok了

authors: hloong msdx

repo: msdx/clip-image


text:
Server run file

Where is the file so that I start node js server ?
Thank you

TeslaJS is a library, not a server application. Several example apps are provided that can be run under Node.

Thank you for answering me quickly.
I came out the errors, when I run login.js
Error: Cannot find module 'colors'
Do you know how I can solve this problem ?

Did you read the documentation about installing dependencies?
To install dependencies via npm, from the root level of the library directory type:
npm install

thank you

authors: mseminatore zerocooling

repo: mseminatore/TeslaJS


text:
Is mskelton.dev down?

When running:
yarn plugin import https://mskelton.dev/yarn-outdated/v4
it is freezing at:
➤ YN0000: Downloading https://mskelton.dev/yarn-outdated/v4

This is fixed now

Working now!

@dtarnawsky That's awesome to hear!

authors: dtarnawsky mskelton rgilsimoes

repo: mskelton/yarn-plugin-outdated

license: ISC


text:
A couple files not written to output directory

Hi,
It looks like a couple files are being written to the working directory that Jabba is run from, and not the output directory specified by --outdir:
raw.prm
raw.sols.rds
Thanks,
Will

Thanks Will – we will look into this shortly
From: Will Hooper notifications@github.com
Reply-To: mskilab/JaBbA reply@reply.github.com
Date: Tuesday, March 17, 2020 at 10:37 AM
To: mskilab/JaBbA JaBbA@noreply.github.com
Cc: Subscribed subscribed@noreply.github.com
Subject: [mskilab/JaBbA] A couple files not written to output directory (#25)
Hi,
It looks like a couple files are being written to the working directory that Jabba is run from, and not the output directory specified by --outdir:
raw.prm
raw.sols.rds
Thanks,
Will
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/mskilab/JaBbA/issues/25__;!!C6sPl7C9qQ!HtAv4jV3_10vUfnK0wPAmmgPf13rYoD0-KVax_kUjQI_yfQvZIgMFTtqOn8RHyFM-eQ$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ABFUFY77YYYPLHVSUOPVNPLRH6DLTANCNFSM4LNP2YLA__;!!C6sPl7C9qQ!HtAv4jV3_10vUfnK0wPAmmgPf13rYoD0-KVax_kUjQI_yfQvZIgMFTtqOn8RYGLZ-kw$.

This message is for the recipient’s use only, and may contain confidential, privileged or protected information. Any unauthorized use or dissemination of this communication is prohibited. If you received this message in error, please immediately notify the sender and destroy all copies of this message. The recipient should check this email and any attachments for the presence of viruses, as we accept no liability for any damage caused by any virus transmitted by this email.

cleaned up

authors: imielinski willhooper xtYao

repo: mskilab/JaBbA


text:
🛑 A Ciambra is down

In 3d9f706, A Ciambra (https://aciambra.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: A Ciambra is back up in 085df83.

repo: mswd-io/upptime


text:
React Native "Unable to resolve module http" (Advise needed)

Hello guys. Thank you for awesome lib! It works fine in my Node.js project. But I wonder, is there any instruction how to use it with RN? Currently, I am getting error: "Unable to resolve module http" when trying to use ClientRequestInterceptor.
Reading other issues, I understood that RN support is offered. Maybe there is special branch for RN or something?
p.s. Only FetchInterceptor works fine but I need Interceptor that sees http.request(s)
RN version: 0.66.4

Just tried XMLHttpRequestInterceptor. I am getting this error: "TypeError: Cannot read property 'prototype' of undefined, js engine: hermes". Currently I am trying to get more information of this error. Starting project with xCode did not gave me any additional information.
The code i am trying to run:
`
import { XMLHttpRequestInterceptor } from '@mswjs/interceptors/XMLHttpRequest';
const interceptor = new XMLHttpRequestInterceptor();
interceptor.apply()
interceptor.on('request', (request, requestId) => {
console.log(request.method, request.url)
})
interceptor.on('response', (response, request) => {
console.log('response to %s %s was:', request.method, request.url, response)
})
`

I'll try to get more information of this error and I'll edit comment if I know anything.

Sorry, I don't have enough insight into React Native to advise here.
Perhaps take a look at the RN usage example one of our contributors prepared https://github.com/mswjs/examples/pull/60 maybe you will find a missing piece there.

authors: RNEvok kettanaito

repo: mswjs/interceptors


text:
Cannot connect to the Docker daemon at unix:///home/rootless/.docker/run/docker.sock. Is the docker daemon running?

I do find your approach for setting up a rootless GitHub Actions Runner Docker image really great! So I decided to give it a try.
Unfortunately I'm facing some issues when executing the hello-world.yml you provide.
Runner is started with:
docker run --restart always --name github-runner \
  -e ACCESS_TOKEN="<MY_ACCESS_TOKEN>" \
  -e REPO_URL="https://github.com/abrokwasoft/test-repo/" \
  -e RUNNER_NAME="foo-runner" \
  -e RUNNER_WORKDIR="/tmp/github-runner-your-repo" \
  -e RUNNER_GROUP="my-group" \
  -e LABELS="my-label,other-label" \
  msyea/github-actions-runner:latest

Runner starts and registers at GitHub successfully so that it is able to execute the build job defined in hello-world.yml.
It fails with following error: Cannot connect to the Docker daemon at unix:///home/rootless/.docker/run/docker.sock. Is the docker daemon running?
Do you have any idea about the route cause of that issue?
Below you find the entire raw log of the executed build job:
2021-04-02T13:56:36.4294469Z ##[section]Starting: Request a runner to run this job
2021-04-02T13:56:36.5910584Z Found online and idle self-hosted runner in current repository that matches the required labels: 'self-hosted , linux'
2021-04-02T13:56:36.6512852Z ##[section]Finishing: Request a runner to run this job
2021-04-02T13:56:42.5162469Z Current runner version: '2.277.1'
2021-04-02T13:56:42.5187547Z Runner name: 'foo-runner'
2021-04-02T13:56:42.5189585Z Runner group name: 'Default'
2021-04-02T13:56:42.5192750Z Machine name: '550bf42c5784'
2021-04-02T13:56:42.5205129Z ##[group]GITHUB_TOKEN Permissions
2021-04-02T13:56:42.5207069Z Actions: write
2021-04-02T13:56:42.5207586Z Checks: write
2021-04-02T13:56:42.5208075Z Contents: write
2021-04-02T13:56:42.5208600Z Deployments: write
2021-04-02T13:56:42.5209117Z Issues: write
2021-04-02T13:56:42.5209596Z Metadata: read
2021-04-02T13:56:42.5210212Z OrganizationPackages: write
2021-04-02T13:56:42.5211103Z Packages: write
2021-04-02T13:56:42.5211802Z PullRequests: write
2021-04-02T13:56:42.5212372Z RepositoryProjects: write
2021-04-02T13:56:42.5212950Z SecurityEvents: write
2021-04-02T13:56:42.5213438Z Statuses: write
2021-04-02T13:56:42.5214077Z ##[endgroup]
2021-04-02T13:56:42.5218396Z Prepare workflow directory
2021-04-02T13:56:42.6295996Z Prepare all required actions
2021-04-02T13:56:42.7539112Z ##[group]Pull down action image 'hello-world'
2021-04-02T13:56:42.7653983Z ##[command]/usr/local/bin/docker pull hello-world
2021-04-02T13:56:42.8752838Z Cannot connect to the Docker daemon at unix:///home/rootless/.docker/run/docker.sock. Is the docker daemon running?
2021-04-02T13:56:42.8755714Z Using default tag: latest
2021-04-02T13:56:43.0413525Z ##[warning]Docker pull failed with exit code 1, back off 9.06 seconds before retry.
2021-04-02T13:56:52.0936230Z ##[command]/usr/local/bin/docker pull hello-world
2021-04-02T13:56:52.6591294Z Cannot connect to the Docker daemon at unix:///home/rootless/.docker/run/docker.sock. Is the docker daemon running?
2021-04-02T13:56:52.6595576Z Using default tag: latest
2021-04-02T13:56:52.7893670Z ##[warning]Docker pull failed with exit code 1, back off 2.286 seconds before retry.
2021-04-02T13:56:55.0820613Z ##[command]/usr/local/bin/docker pull hello-world
2021-04-02T13:56:55.6990875Z Cannot connect to the Docker daemon at unix:///home/rootless/.docker/run/docker.sock. Is the docker daemon running?
2021-04-02T13:56:55.6994025Z Using default tag: latest
2021-04-02T13:56:55.7404010Z ##[endgroup]
2021-04-02T13:56:55.7628985Z ##[error]Docker pull failed with exit code 1
2021-04-02T13:56:55.7789156Z Cleaning up orphan processes

Sorry it's taken so long to respond. @abrokwasoft you need the --privileged flag. I'll update the docs today.
Also FYI I'll be publishing a kubernetes solution soon.

@msyea First of all I just wanted to thank you for all of your work on this rootless solution for Github Runners.
I'm running to this same issue but when deploying the image to ECS Fargate. Unfortunately, privileged mode is not an option on Fargate, and ECS EC2 allows privileged mode, both of which make the rootless approach somewhat moot.
Is there any way to successfully run this image in Fargate and have builds executing?

authors: abrokwasoft msyea sremp

repo: msyea/github-actions-runner-rootless


text:
ARM runner has been stuck for multiple days

This CI job is running for days https://github.com/msys2-arm/msys2-autobuild/actions/runs/6508662089
@jeremyd2019

It managed to hang up right as I was leaving on a long weekend trip, and I didn't notice until I got back.  I wanted to get a fresh runner going anyway, for the latest Windows Updates, but was waiting until I got back to try to avoid any issues while I was gone :grin:.  New runner is going now

Could you setup a remote access for @lazka, So he could cancel jobs and clean them just in case (like this one).

@jeremyd2019 Would you like to check if this CI job is stuck again https://github.com/msys2-arm/msys2-autobuild/actions/runs/6570301888 ?

@jeremyd2019 https://github.com/msys2-arm/msys2-autobuild/actions/runs/6714121489/job/18246869719

@jeremyd2019 likely stuck https://github.com/msys2-arm/msys2-autobuild/actions/runs/6980352526/job/18995436393

I've been ruminating on the idea of some sort of 'watchdog' to detect and kill stuck pacman processes automatically, but I haven't settled on the best language/technology to do so.  It seems like python would be most convenient since autobuild is already python, I could put a background thread like I did to try polling the token, but I'm not familiar with process querying/killing modules.
What I've got so far is a cygwin commands to get the cygwin pid of the process I want to kill (what I really want is the child pacman process, this gets the newest pacman process older than 1800 seconds)
pgrep -xn -O 1800 pacman

coupled with the script I already had (because when stuck in this state cygwin kill is not sufficient)
https://github.com/jeremyd2019/winautoconfig/blob/master/msys2-runner-setup/setupscripts/wkill.sh

It would be a bit clear if the reason of such CI failure is explained.

lost power, so any lack of runner in the near future will be due to that

@jeremyd2019 https://github.com/msys2-arm/msys2-autobuild/actions/runs/7355161710

@jeremyd2019 https://github.com/msys2-arm/msys2-autobuild/actions/runs/7862352714

stuck again https://github.com/msys2-arm/msys2-autobuild/actions/runs/8401152114

unstuck it.  the powershell variant in https://github.com/git-for-windows/git-for-windows-automation/pull/61#issuecomment-2014464189 was intriguing, it seems like it could be close to being turned into a 'watchdog', would just need to also query CreationDate field to see any pacman processes that have been running a long time (like a half hour? or hour?), and then arrange for it to run continuously (scheduled task?).  Of course, I'd much rather get whatever bug is causing this fixed...

https://github.com/msys2-arm/msys2-autobuild/actions/runs/8938789079/job/24553638109

stuck again

There's a stuck job now, but it doesn't seem to be the runner this time.  Probably something on Github's end.

stuck again.

stuck again https://github.com/msys2-arm/msys2-autobuild/actions/runs/9336436265

stuck again https://github.com/msys2-arm/msys2-autobuild/actions/runs/9739288128

This seems to be a different issue.  I think maybe the machine rebooted.

stuck again https://github.com/msys2-arm/msys2-autobuild/actions/runs/10108768753

stuck again!

"echo: write error: No space left on device"

What?!?  I deleted some of the cruft under %USERPROFILE% (go, .cargo mainly) and increased some free space.  Will try to build rust again

Is #76 related?
Otherwise, try good old WinDirStat :)

https://github.com/msys2-arm/msys2-autobuild/actions/runs/10539907589

https://github.com/msys2-arm/msys2-autobuild/actions/runs/11418583395/job/31772208187

https://github.com/msys2-arm/msys2-autobuild/actions/runs/11418583395/job/31772208187

seems to have gotten unstuck and errored out after some hours.
Unrelated note: Runner groups are now available for everyone it seems. Not that it makes much difference with the current setup with a separate org, but good to know: https://github.blog/changelog/2024-10-17-actions-runner-groups-now-available-for-organizations-on-free-plan/

seems to have gotten unstuck and errored out after some hours. (or anyone poked at it?)
I killed the child pacman process, as usual.

Unrelated note: Runner groups are now available for everyone it seems. Not that it makes much difference with the current setup with a separate org, but good to know: https://github.blog/changelog/2024-10-17-actions-runner-groups-now-available-for-organizations-on-free-plan/

Yeah, I could do away with the extra labels to differentiate between autobuild and CI instances and enforce it with runner groups instead, presumably.

https://github.com/msys2-arm/msys2-autobuild/actions/runs/11604120891

Is it stuck again? This time with checking keyring... as the last line in the log:
https://github.com/msys2-arm/msys2-autobuild/actions/runs/11729327900/job/32674802852#step:11:507

yep, killed

Unrelated note: Runner groups are now available for everyone it seems. Not that it makes much difference with the current setup with a separate org, but good to know: https://github.blog/changelog/2024-10-17-actions-runner-groups-now-available-for-organizations-on-free-plan/

I set up runner groups in the msys2-arm org, and set the windows-arm64-autobuild group to only allow msys2-arm/msys2-autobuild repository and msys2-arm/msys2-autobuild/.github/workflows/build.yml@main workflow.  However, it looks like specifying a runner group works differently in the yaml:
runs-on:
  group: windows-arm64-autobuild

instead of
runs-on: ['Windows', 'ARM64', 'autobuild']

so I don't know how that would work out in the matrix...

I killed dirmngr and keyboxd processes, and deleted ~/.gnupg, hopefully will make it happier.  I'm clearing all the failed builds and am starting a build.

Looks like it happened again.  Killed pacman and dirmngr/keyboxd again.

Hmm, wasn't there a gnupg update recently?

yeah, it aligns with the update.. sadly

It looks like the runner is stuck again. This time checking package integrity... is the last line in the log.

During setup-msys2... that's different...


text:
Trailing slash

Add configuration option to ignore trailing slashes

https://github.com/mtag-dev/squall/issues/59

repo: mtag-dev/rs-squall-router


text:
Contraction sequence backends

This adds a variety of more efficient but potentially sub-optimal contraction sequence algorithms from OMEinsumContractionOrders.jl, based on the wrapper @GiggleLiu wrote in ITensorContractionOrders.jl.
It is based around a single function contraction_sequence(tn::ITensorNetwork; alg="optimal") where alg="optimal" chooses the optimal but exponentially scaling algorithm implemented in ITensors.jl (in the submodule ITensors.ContractionSequenceOptimization), and this PR provides the alternative backends "greedy", "tree_sa", "sa_bipartite", and "kahypar_bipartite" when OMEinsumContractionOrders.jl is loaded with using OMEinsumContractionOrders.
You can perform the contraction as follows:
seq = contraction_sequence(tn)
res = contract(tn; sequence=seq)

Note that this is slightly breaking since it removes the function optimal_contraction_sequence(tn::ITensorNetwork) in favor of the new interface contraction_sequence(tn::ITensorNetwork), where the default is alg="optimal".
Also note that it also accepts contraction_sequence(tn::Vector{ITensor}), in which case it outputs a sequence with integer vertices.

Note that this is slightly breaking since it removes the function optimal_contraction_sequence(tn::ITensorNetwork) in favor of the new interface contraction_sequence(tn::ITensorNetwork), where the default is alg="optimal".

@LinjianMa @JoeyT1994

source: gharchive/pull-request


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

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

HTTP code: 0
Response time: 0 ms

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

repo: mtitservice/site


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

In 9d12e68, https://reports.mtit.pna.ps (https://reports.mtit.pna.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://reports.mtit.pna.ps is back up in 2699c0a.


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

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

HTTP code: 0
Response time: 0 ms

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


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

In 1c2ddd4, https://hcie.ps (https://hcie.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://hcie.ps is back up in 9551363.


text:
🛑 https://verify.moj.pna.ps is down

In 9f3258d, https://verify.moj.pna.ps (https://verify.moj.pna.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://verify.moj.pna.ps is back up in 633f8a8.


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

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

HTTP code: 0
Response time: 0 ms

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


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

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

HTTP code: 0
Response time: 0 ms

Resolved: https://911.ps is back up in 019f1d7.


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

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

HTTP code: 0
Response time: 0 ms

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


text:
Add a blacklist option to ignore some games

Would be a great option because some don't require to be saved (online games, for example)

Good idea! I'll look into this.

Thanks ! and tyvm for your work, it is a great app.

An easy implementation of this might be to ignore any games with a specific tag and then let us tag any game with a phrase like "nobackup".

This is now available in v0.3.0 by creating a ludusavi-skip tag.
@N0tJust1n Good call on the tag suggestion :D Much better than what I was originally imagining.

Didn't know this plugin had such an option.
For better UX, please add a tick like this:

[ ] Remember my choice

To dialog window like this:

@jerrygreen Thanks for the suggestion! I've made a separate ticket to track that idea: https://github.com/mtkennerly/ludusavi-playnite/issues/31

repo: mtkennerly/ludusavi-playnite


text:
css: remove unused fonts from CSS

For a while now I have had the fonts on my website "jump" (rescale?) to a smaller size upon loading a page. I finally had time to track it down and found the cause. These lines here seem to be unused, and when removed they stop the fonts from jumping.
You can try to reproduce on my website.

This seems to be related to #57.

Thanks @Hjdskes and @seemethere.
I might be mistaken, but I think the result of this is that system fonts are used in place of ones from a CDN, at least for the list of posts. I'm going to first implement #57 to make it an option ton use all system fonts (because I think for many people the flicker effect might be more annoying than having the fancier fonts) and then look into getting rid of the flicker with the fancy font. So before I merge this, I'll probably surround it and other custom font sections with a conditional that can be set by the user.

I definitely dislike the flicker, but I naturally having fancy fonts without flickering is even better! Until then, my website will fall back to this approach :)

Yea, my first thought (caveat, not that much front-end experience) is that deferred loading is a likely culprit. But I'm pretty sure that it's standard practice to defer loading, so will look to some other themes for reference.

authors: Hjdskes mtn

repo: mtn/cocoa-eh-hugo-theme


text:
No highlight when tabing through search suggestion

When searching through adressbar, the selected search is not highlighted when using <Tab>. Mouse hover shows selection though.

--
And the shadow below the pop-up looks not quiet right.

Good catch - I'll look into that. The shadow seems to be a graphics glitch which means I might need to look for an alternative method for producing the shadow. It's quite challenging because depending on the OS, the popups and menus are styled (and behave) very differently and on Windows and Linux require some rather creative solutions to get nice, big shadows.

Same for arrows selection under macOS. I see the same issue with dropdown selects (https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select to try)

Yeah, your new issue should be fixed now too (in d7d471595dc60b5c8e6d6bd01827c4155ed9e56d).

authors: euh2 heubergen muckSponge

repo: muckSponge/MaterialFox


text:
Diffusers is not working at all. Load by default stablediffusion instead diffusers

LocalAI version:
2.2.0-ffmpeg
Environment, CPU architecture, OS, and Version:
Linux srv-gpt 5.15.131-1-pve https://github.com/mudler/LocalAI/issues/1 SMP PVE 5.15.131-2 (2023-11-14T11:32Z) x86_64 x86_64 x86_64 GNU/Linux, Proxmox LXC, AMD Ryzen 9 5900X, 128 GB RAM
Describe the bug
Diffusers is not working at all. Load by default stablediffusion instead diffusers
To Reproduce
I set up dreamlike-photoreal as stated in the docs. File "dreamlike-photoreal.yaml" in models folder with content:
name: dreamlike-photoreal
parameters:
  model: Linaqruf/dreamlike-photoreal
backend: diffusers
# Force CPU usage - set to true for GPU
f16: false
diffusers:
  pipeline_type: StableDiffusionPipeline
  cuda: false # Enable for GPU usage (CUDA)
  scheduler_type: euler_a

Then ran command as stated in docs:
curl http://localhost:8080/v1/images/generations \
    -H "Content-Type: application/json" \
    -d '{
      "prompt": "cat, outdoor, sun, tree|rain, night, people",
      "model": "dreamlike-photoreal",
      "step": 51,
      "size": "1024x1024"
    }'

It results always in this error:
Load by default stablediffusion instead diffusers

env with COMPEL=0
/tmp/localai/backend_data/backend-assets/grpc/stablediffusion

Expected behavior
Diffusers generate images.

good catch, this sounds a regression introduced with #1283 . cc @M0Rf30

authors: JZacharie mudler

repo: mudler/LocalAI


text:
Disable low-profile by default

with new versions seems there is a boost of performance by disabling this by default with new libp2p 0.23

Codecov Report
Base: 33.51% // Head: 33.46% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (5588b52) compared to base (042b7b2).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
- Coverage   33.51%   33.46%   -0.05%
==========================================
  Files          27       27
  Lines        2041     2041
==========================================
- Hits          684      683       -1
- Misses       1258     1259       +1
  Partials       99       99

Impacted Files
Coverage Δ

pkg/trustzone/peerguardian.go
67.44% <0.00%> (-2.33%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter mudler

repo: mudler/edgevpn


text:
Retrieve mudmie.com/roundabout

There is a link to mudmie.com/roundabout on Roudabout project, but the link is broken. Can't direct it to the actual roundabout website tho....

dont need anymore


text:
Somes questions about CVE-2007-4965

Hello,
When I run the "make" command, it promts the errors：
Python-2.2/Modules/dbmmodule.c:24:2: error: #error "No ndbm.h available!"
#error "No ndbm.h available!"
Python-2.2/Modules/dbmmodule.c:30:2: error: unknown type name ‘DBM’
DBM *di_dbm;
Python-2.2/Modules/dbmmodule.c:81:42: error: request for member ‘dptr’ in something not a structure or union
for ( key=dbm_firstkey(dp->di_dbm); key.dptr;
...
I can't find solutions online, please help.

You need one package - libgdbm-dev on Ubuntu or Debian. You could quickly search the error message in the google engine and double check the missing package.

repo: mudongliang/LinuxFlaw


text:
Static DatePicker

Firstly, wanna pay you gratitude for what you`re doing! Very useful. Much thanks!
In previous versions you could staticly place datepicker on the page without (or with) textfiled.
The problem is that you cannot do this in current verion (3.1.2)
I`ve read some previous issues on this theme and the code attached there is not working now. Much code has changed since, that is not surprisingly.
I think, these feature will be useful, cause now you can only use calendar.

Glad to have someone dealing with the same problem too!
I tried today, figured out that the behavior of  onChange is a bit strange.
You need to defined onChange prop again in the component.
<Calendar
    {...pickerProps}
    onChange={date => setDate(date)} // or your custom logic
/>

Same issue here: We want to place a <Picker/> inline alongside other components.
I am ware that there is some way of control over how the <Picker/> is rendered using property variant="dialog|line".
It would be great to have a 3rd value for variant that would prevent wrapping the <Picker/> in a popover.
Note: In previous versions we have solved this by importing internal components, but that is no longer possible unless you solely use named imports.

authors: crazytyper hinsxd shtelzerartem

repo: mui-org/material-ui-pickers


text:
Nesting typography creates warning

Trying to nest typography like this:
<Typography  className={classes.hashline} >
    hash: <Typography className={classes.hash} color="textSecondary" >{props.hash}</Typography>
</Typography>

Creates this error
Warning: validateDOMNesting(...): <p> cannot appear as a descendant of <p>.

Would it be possible to add a tag prop? So we could use <Typography tag="div"> and keep the regular typography formatting (just using <div>  doesn't have the nice materialui style). This would sidestep the issue.

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

@anchpop Use the component property.

Hey guys!
Im getting a very similar issue but when Im returning a component with steppers :
switch (step) {     case 0:       return <ConfigEnv />;    default:       return "Woops, Unknown step, Let's Go Back";   }
And my error is :
Warning: validateDOMNesting(...): <div> cannot appear as a descendant of <p>.
How can I use the component property to return this without warnings?

@yashank09
<Typography component="p">
    <Typography component="span />
</Typography>

Thanks for the reply @oliviertassinari  but Im not really using any typography which could be causing this problem. I am using a Textfield if you think that could be it? So far Ive found that the root warnings occur when I return  <ConfigEnv /> from the Steppers. If I just put normal text instead of the component, then the error goes away. Any idea?

authors: anchpop oliviertassinari yashank09

repo: mui-org/material-ui


text:
TextField onKeyDown typescript event type is incorrect

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

Expected Behavior
A function with an event arg of type KeyboardEvent should for the onKeyDown event handler.
Current Behavior
This event handler expects KeyboardEvent which is counter intuitive.
Steps to Reproduce
<TextField
   onKeyDown={(event: KeyboardEvent<HTMLInputElement>) => {}}
/>

Context
I'm using typescript in our environment and some TextField events like onChange will use HTMLInputElement type but the key down event expected HTMLDivElement. I would have expected all event handlers to use the same types.
Your Environment

Tech
Version

Material-UI
v^1.1.0

React
v^16.3.2

Chrome
v68.0.3440.106

TypeScript
v2.8.4

@Swazimodo
I took a look at the TextField props ... it doesn't expose onKeyUp/onKeyDown props for the input, like it does with onChange.   So when you use these props on TextField they are spread to the root div element, not passed down to the input.
You can use InputProps to access the Input's onKeyUp/onKeyDown props, which have the expected types.
<TextField
  InputProps={{
    onKeyDown: (event: React.KeyboardEvent<HTMLInputElement>) => {},
  }}
/>

@Swazimodo Is right that it does attach those listeners to a div but this is only relevant for currentTarget. The target will still be the input element: https://codesandbox.io/s/p90k1rwpym
As a workaround you can do what @Swazimodo suggested.
Doing this correct in our type declarations would require quite some work so I'm more than happy to accept PRs.

Accepted answer: https://github.com/mui-org/material-ui/issues/12946#issuecomment-423850042

authors: Swazimodo eps1lon lukePeavey


text:
[Select] Menu is moving to the right side in a drawer

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

Expected Behavior 🤔
The open menu should touch the select and should not move to the right side.
Current Behavior 😯
If I use the property container on the Select Component, then the open Menu moves to an complete different place, if this menu is open.
I need to use the container property, because the select is used in a ClickAwayListener-Container.
Steps to Reproduce 🕹
Take a look at this sandbox to reproduce the issue. You can open the chrome debugger tool verify the issue. The complete checkbox gets moved out of the drawer and the open menu will be displayed.
https://codesandbox.io/s/eager-visvesvaraya-nwtt1

Tech
Version

Material-UI
see Codesandbox

React
latest

Browser
latest Chrome

@oliviertassinari Do you have an idea how to fix it? :)

Did you try the disablePortal prop or the onClose callback instead of changing the container?

@oliviertassinari yes, I already tried it :/
I think I cannot always use container={this}. I just can use it in a ClickAwayListener context and if I am not in a ClickAwayListener context, then I have to unset the container to default.

As you can see in this sandbox: https://codesandbox.io/s/et2q4

@ffjanhoeck Thanks for the reproduction. Do you have an idea of what's wrong? (I won't have time to look into this problem)

Hmm, the first reproduction seems to work for me

@joshwooding You are right :o But I don't know why, I didn't changed anything :D

@joshwooding But great to see, that the other codesandbox has a working example :D

Could it be an update of the library that fixed it? What should we do here? Your use case sounds too advanced to justify us diving into the problem. Could you share the context in more detail? What's your inital objective?

I'm closing.

authors: ffjanhoeck joshwooding oliviertassinari


text:
Default Typography color

Following the migration to v4 (from v3), the Typography component has a different behavior regarding color (taken from the migration guide):

[Typography] Remove the default color from the typography variants. The color should inherit most of the time. It's the default behavior of the web.

This means that now text in Typography doesn't get the primary theme color by default.
In my case, I have the following theme:
export const theme = createMuiTheme({
  palette: {
    type: 'dark',
    primary: {
      main: '#fff',
    },
  },
})

Which is provided in a ThemeProvider.
However, child Typography components don't get colored white by default.
What is the expected way to handle this following the v4 upgrade?
Thanks

You're probably missing CssBaseline in your component tree.

Isn't that only needed for SSR? Also, does it take the provided theme into account, doesn't seen like it from the API.. Or am I missing something?

@bengry The concern was originally raised in https://github.com/mui-org/material-ui/pull/15100#discussion_r276254348. You need a CssBaseline component or a Typography color="primary" component="div" at the root of your document.

authors: bengry eps1lon oliviertassinari


text:
Tabs textColor primary refers to secondary palette text color

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

Expected Behavior 🤔
When you set <Tabs textColor="primary"> it should use the theme.palette.text.primary
Current Behavior 😯
When looking through the code in tabs.js in master branch, you can see the following code:

color refers to theme.palette.text.secondary
Your Environment 🌎

Tech
Version

Material-UI
v4.1.3

React
v16.8.6

Browser
Chrome

The same concern was raised in #16084.

authors: Luucky oliviertassinari


text:
Theme being reset to default when opening Dialog component

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

Current Behavior 😯

I set up a simple theme with ThemeProvider to define custom primary color
Checkboxes with primary color appear correct in the component tree
When a Dialog component opens, the checkbox has wrong default color in both dialog and even in the underlying form, where it was correct before.

Expected Behavior 🤔

I would expect the correct color of Checkbox defined by theme being forwarded.

Steps to Reproduce 🕹

https://codesandbox.io/s/material-demo-lzxu0?file=/demo.js
Create ThemeProvider setting primary color to red
Create MuiThemeProvider to be able to use Dialog (material-ui 0.20.2) with primary color blue
There is a Checkbox in main tree which has proper red color
Open the dialog, the Checkbox color changes to purple (default theme) in both main tree and dialog. Theme seems to be reset.

Context 🔦

In our project we use the latest release of material-ui in combination with old material-ui 0.20.2 components. I am thankful everything else is working nicely using two version of your library
Normally it seems there is no conflict in using two versions and theme, only the Dialog somehow resets the theme from context.

Your Environment 🌎
    "@material-ui/core": "4.9.11",
    "@material-ui/icons": "4.9.1",
    "@material-ui/lab": "4.0.0-alpha.50",
    "material-ui": "0.20.2",
    "react": "16.8.6",
    "react-dom": "16.8.6",

There's definitely something wrong. Opening a dialog shouldn't mount duplicate checkbox <style> elements.

Legacy context api

Did you manage to fix the issue @peterbartos @oliviertassinari ? I have a similar problem.
I created a custom a custom component that I am using in another project.
It uses a material-UI dialog.
When I open it in my project, the theme resets

@tran-simon This is unrelated, I'm resolving.

I'm having an issue with this, using purely the latest v4 components.
When I add a dialog to the DOM using render from 'react-dom' my custom theme is overwritten. This doesn't happen when dynamically adding a Typography component for example.
I made a codeSandbox, click the button and you'll see the dialog shows and the theme default button text changes from pink to blue.
https://codesandbox.io/s/material-theme-bug-cqjcl?file=/index.js

authors: alexstanbury eps1lon oliviertassinari peterbartos tran-simon


text:
[theme] Add capacity to apply styleOverrides with styled() instead of with createTheme()

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
There are certain properties that I cannot seem to access from the theme-level customization for a given component that I would like to access and define at the component level with styled() or even the sx prop.
Examples 🌈
Link to Material Design specification: https://mui.com/material-ui/customization/how-to-customize/
Expected implemented behavior:
import { styled } from '@mui/material/styles';
import MuiChip, { ChipProps } from '@mui/material/Chip';

const Chip = styled(MuiChip)<ChipProps>(({ theme }) => ({
  colorPrimary: {
    backgroundColor: theme.palette.primary.light
  },
  colorSecondary: {
    backgroundColor: theme.palette.secondary.light
  }
}));

export default Chip;

Current implemented behavior:
let myTheme = createTheme({
  palette: {
    ...
  },
  typography: {
    ...
  }
});

myTheme = createTheme(myTheme , {
  components: {
    MuiChip: {
      styleOverrides: {
        colorPrimary: {
          backgroundColor: myTheme .palette.primary.light
        },
        colorSecondary: {
          backgroundColor: myTheme .palette.secondary.light
        }
      }
    }
  }
});

Motivation 🔦
I'm trying to accomplish a pure separation of style overrides between the component and theme level. I want to treat the theme I'm creating as more of a way to define global styles and to handle what many designers and developers would consider design tokens (typography, color palette, etc.). And then, at the component-level, I want to be able to handle any customizations for a given component by wrapping it and applying any component-specific styles or usages of the theme being passed in with styled().

I don't really understand what you cannot achieve. Looks like you want to use the styled() instead of the theme.components[*].styleOverrdes, which is perfectly fine and works as expected. You can use the callback for accessing the props & theme. For the slots (the nodes inside the component) you can use class selectors (I believe this is different to the styleOverrides and you are referring to this in terms of difference). See https://mui.com/material-ui/customization/how-to-customize/#2-reusable-component for accessing the theme and adding styles to inner elements (the thumb).

Thanks for sharing the link to the documentation. The following approach seems to be able to work for me for style overrides at the component-level:
const Chip = styled(MuiChip)<ChipProps>(({ theme }) => ({
  '&.MuiChip-colorPrimary': {
    backgroundColor: theme.palette.primary.light
  },
  '&.MuiChip-colorSecondary': {
    backgroundColor: theme.palette.secondary.light
  }
}));

I do think that being able to use the Rule Names, instead of the Global Class, would improve readability of code. For example, the following does not work for me, but then again, I may not be using the right syntax:
const Chip = styled(MuiChip)<ChipProps>(({ theme }) => ({
  colorPrimary: {
    backgroundColor: theme.palette.primary.light
  },
  colorSecondary: {
    backgroundColor: theme.palette.secondary.light
  }
}));

I could see this being particularly useful when defining new variants or removing out-of-the-box variants at the component-level. Again, that may be possible, given the working syntax in the first code snippet in this comment. However, it doesn't seem intuitive, and most of the documentation around customizing component styles is centered around using createTheme and not styled().

authors: cdalto mnajdova

repo: mui/material-ui


text:
[material-ui][Chip] The skipFocusWhenDisabled prop skips the focus when set to false and when disabled is true

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
Steps:

Go to the Mui chip link https://mui.com/material-ui/react-chip/
Goto the clickable section
update the example with the following code
<Chip label="Clickable" disabled skipFocusWhenDisabled={false}  onClick={handleClick} />  <Chip label="Clickable" variant="outlined" onClick={handleClick} />

Current behavior 😯
If you inspect the first chip component that is disabled if you set skipFocusWhenDisabled={true} the tabIndex is set to -1 which I think is correct if you then set skipFocusWhenDisabled={false} the tabIndex is still  -1 which I think is incorrect.
Expected behavior 🤔
When disabled is set to true and skipFocusWhenDisabled={false} the Index should not be -1 it should allow it to have focus.
Context 🔦
No response
Your environment 🌎

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

@danilo-leal  i want to work on this issue, can you please assign this to ?

@aman44444 Assigned. Please let us know if you are facing any issues.

@brijeshb42 i attempted to change the value of tabIndex both directly and indirectly, but it's not working. after debugging, i discovered that the value only changes when 'disabled' is applied. there is no effect of 'skipFocusWhenDisabled,' and   i am sorry I couldn't determine how 'disabled' is changing the value. also sorry for the late reply.

It's a bug. The skipFocusWhenDisabled prop is broken which was added in #35065.

Hey @ZeeshanTamboli, I want to take on this task but I'm a little confused. Accessibility wise, shouldn't a disabled Chip always have a tabIndex of -1? That is how it is in the ButtonBase component which imo is correct.
I have removed the usage of this prop in my playground and it works as expected, the Chip is not focused, I did this to recreate the issue/PR you have sent. I feel like I'm missing an important piece.

@aacevski When the skipFocusWhenDisabled prop is set to false (either as its default value or when not explicitly provided to the component), the disabled Chip should be focusable. Conversely, when set to true, the disabled Chip should be non-focusable. The inclusion of this prop aimed to prevent a breaking change in #35065, as discussed in that thread. However, its current functionality falls short of expectations, working only when a disabled Chip has an onDelete prop, as shown in the example:
<Chip label="Chip Filled" onDelete={() => {}} disabled />

Considering the issues with its implementation, and ideal solution is to consider removing this prop and address #35038 properly, which the PR #35065 attempts to resolve. It's worth noting that such a change would introduce a breaking change.

Okay thank you @ZeeshanTamboli, I'll try to take on this and update you soon. 🙌🏼


text:
[v6] Skeleton component doesn't work

Steps to reproduce
Working in v5: https://v5.mui.com/material-ui/react-skeleton/#wave-example
Not working in v6: https://next.mui.com/material-ui/react-skeleton/#wave-example
Current behavior
v6 Skeleton seems broken
Expected behavior
v6 Skeleton should work as v5
Context
We are using Sketelon component and we couldn't move to MUI v6.0.0
Your environment

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

Search keywords: v6

Hey @trungutt, thanks for the report. This is a duplicate of https://github.com/mui/material-ui/issues/43470, fixed in https://github.com/mui/material-ui/pull/43474. It should be out in the next patch release.

authors: DiegoAndai trungutt


text:
[material-ui][Dialog] Broken scrolling in fullScreen dialogs (v6)

Steps to reproduce
Link to live example: https://codesandbox.io/s/wizardly-swirles-yw2t4t?file=/src/Demo.js
Steps:

Open repro
Adjust the number of list items in the dialog if you don't have enough items to fill the height of the dialog
Try to scroll

PS: repro is actually the example from the docs with more list items quickly copy-pasted to overflow the screen vertically
Current behavior
Scrolling doesn't work unless you manually target the element and add scrolling through CSS
Expected behavior
Scrolling should work with no additional steps, or at least there should be a sort of statement in the docs.
Context
This is one of the actually few things that broke while upgrading to v6.
Your environment

npx @mui/envinfo
  System:
    OS: macOS 14.6.1
  Binaries:
    Node: 22.6.0 - ~/.nvm/versions/node/v22.6.0/bin/node
    npm: 10.8.2 - ~/.nvm/versions/node/v22.6.0/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 128.0.6613.113
    Edge: 128.0.2739.54
    Safari: 17.6
  npmPackages:
    @emotion/react: 11.13.3 => 11.13.3
    @emotion/styled: 11.13.0 => 11.13.0
    @mui/base:  5.0.0-beta.40
    @mui/core-downloads-tracker:  6.0.1
    @mui/icons-material: 6.0.1 => 6.0.1
    @mui/lab: 5.0.0-alpha.173 => 5.0.0-alpha.173
    @mui/material: 6.0.1 => 6.0.1
    @mui/private-theming:  5.16.5
    @mui/styled-engine:  5.16.4
    @mui/system: 6.0.1 => 6.0.1
    @mui/types:  7.2.15
    @mui/utils:  5.16.5
    @mui/x-data-grid: 7.15.0 => 7.15.0
    @mui/x-date-pickers: 7.15.0 => 7.15.0
    @mui/x-internals:  7.15.0
    @types/react: 18.3.5 => 18.3.5
    react: 18.3.1 => 18.3.1
    react-dom: 18.3.1 => 18.3.1
    typescript: 5.5.4 => 5.5.4 ```
</details>

**Search keywords**: broken scrolling fullscreen dialog

It's a regression from #42283 where we removed overflowY: 'auto' from the Dialog's paper component (see https://github.com/mui/material-ui/pull/42283#discussion_r1610460750). Adding it back fixes the issue.

Can you provide the the actual folder or line of code whihc need to fix. Because for some reason I cant able to find it

Hello @ZeeshanTamboli I think I had fixed the issue of it. Can you please assing this issue to me.

@LuseBiswas thanks for reaching out, if you want please open a PR with the fix and add me as a reviewer, otherwise I'll open a PR tomorrow.

@ZeeshanTamboli https://github.com/mui/material-ui/issues/43572#issuecomment-2332357488 nice hunting this down 👍

authors: DiegoAndai LuseBiswas ZeeshanTamboli federico-ntr oliviertassinari


text:
W-11406774: updated doc concerning try scope

Two ways this doc can be updated:

The try scope example is not specific. Per the diagram, it should say that the http request is never executed as the error is re-thrown to the try-example flow. (I have updated the doc).
Or two diagrams should be included to elaborate both On-Error components with respect to the Try scope
2.1 the on-error-continue (placing it on top of the try scope error handler)
2.2 the on-error-propagate (placing it on top of the try scope error handler - the way it is now in the diagram)

also with the new version of AnyPoint Studio (7.12.1), when I was testing it, the top on-error component needed 'Any' type.

Writer's Quality Checklist
Before merging your PR, did you:

[ ] Run spell checker
[ ] Run link checker to check for broken xrefs
[ ] Check for orphan files
[ ] Perform a local build and do a final visual check of your content, including checking for:

Broken images
Dead links
Correct rendering of partials if they are used in your content
Formatting issues, such as:

Misnumbered ordered lists (steps) or incorrectly nested unordered lists
Messed up tables
Proper indentation
Correct header levels

[ ] Receive final review and signoff from:

Technical SME
Product Manager
Editor or peer reviewer
Reporter, if this content is in response to a reported issue (internal or external feedback)

[ ] If applicable, verify that the software actually got released

Hi, @Tsegaye Thanks for your contribution! We have put it in our queue to evaluate.

Hi @Tsegaye ! There are two on error handlers inside the Try scope. The first one propagates the error (thus breaking the flow of the execution), and the second one indeed handles the error (thus continuing with the flow execution).
Due to your contribution, we decided to modify the text to make it clearer. You can find the corrections in the following PR: https://github.com/mulesoft/docs-mule-runtime/pull/2286

authors: Tsegaye dmerlob dukesphere

repo: mulesoft/docs-mule-runtime


text:
Connectivity query

At the moment there is no functionality and the UI is ugly.
I wanted to get some initial feedback from @JackWilb about whether I set the component up correctly (I didn't use composition API).

[x] Fix logic to show appropriate number of dropdowns (currently doubled)
[x] Add more query logic (like contains and boolean operators
[ ] Hook up AQL logic

@JackWilb can you help with the following? I have stared at it too long to figure out what is wrong

[ ] there is something strange happening where not all of the node values in the template are stored
[ ] the modulo logic for generating the template doesn't work with odd number hops
[ ] and I'm not sure the AQL query works (it returns more nodes than when I use the Arango platform

I'd like to review the AQL query, too, but the variable names and what they mean are confusing me a little. Would you mind taking care of those first (using my suggestions or coming up with better names) before I get to the query?

yes totally, naming is hard, will fix!

repo: multinet-app/multimatrix


text:
Charset problem

Describe the bug
Sometimes in differents part of the code I see a unicode problem.
To reproduce

Take grandlarc.
Put this code
Type in chat something in Unicode

public OnPlayerText(playerid, text[])
{
    new pText[144];
    format(pText, sizeof (pText), "(%d) %s", playerid, text);
    SendPlayerMessageToAll(playerid, pText);
    return 0; // ignore the default text and send the custom one
}

Screenshots
https://youtu.be/v2sRGcl1AMk

I found a strange behavior.
It works fine when I put first sympl something like !@#$%^&*()-=_

https://translate.google.com/translate?hl=&sl=ru&tl=en&u=https%3A%2F%2Fpro-pawn.ru%2Fshowthread.php%3F13007-Баг-в-GetPVarString-GetSVarString-и-как-его-исправить
https://translate.google.com/translate?sl=ru&tl=en&u=https%3A%2F%2Fpro-pawn.ru%2Fshowthread.php%3F16186
Could anybody check it out?

Judging by the video in the 1'st post, the problem must be in string conversion from char to cell - since both types are signed, the conversion is probably done with sign extension, so if any of the source symbols has a value >= 128, then all bits in the higher 3 bytes of a cell are set to 1 (so, for example, 0x80 becomes 0xFFFFFF80 instead of 0x00000080), which is later treated as 3 cyrillic symbols 'я' being inserted before each source symbol ('я' has the code FF). At least that's the bug that most SA-MP string functions have; kinda funny seeing the same bug being repeated here :)

disinterpreter, can u help me? do u have a fix for this issue?

If the issue is open, so nobody fixed this issue

authors: Daniel-Cortez Disinterpreter

repo: multitheftauto/amx

license: Zlib


text: 2020-11-12-갤럭시탭S7-Visual-Studio-Code-사용하기-vscode


text:
"...?foo" syntax is ugly

I really like the bulk of the spread operator proposal (https://github.com/munificent/ui-as-code/blob/master/in-progress/spread-collections.md).
I am slightly concerned about the proposal at the end for a null-aware spread. I think it's important to support something like that, but the syntax ...?foo seems more line-noisy than idiomatic Dart.
Not sure what else to suggest, though. I agree that ...? is a logical way to express this.

Yeah, I agree it's pretty punctuation-heavy, but it's probably the natural-est solution.

Part of my concern is that I think this will be pretty common (unlike some of the other punctuationy things in Dart), and I fear Dart turning into Perl. :-)
The other part of my concern is that usually the question mark is after the thing that you're null-checking, not before:
foo ?? bar is about foo being null
foo ??= bar is about foo being null
foo?.bar is about foo being null
...?bar is about bar being null
Maybe if it was more like ...bar? it would be clearer? But it would be harder to parse.
Maybe the ... should be on the rhs in general?
var args = [
  testArgs...,
  '--packages=${PackageMap.globalPackagesPath}',
  '-rexpanded',
  filePaths...
];

Widget build(BuildContext context) {
  return new CupertinoPageScaffold(
    child: new ListView(
      children: <Widget>[
        new Tab2Header(),
        buildTab2Conversation()...,
      ],
    ),
  );
}

var params = {
  "userId": 123,
  "timeout": 300,
  uri.queryParameters...
};

[1, "234".runes..., 5]

var first = {"key": "value"};
var second = {"a": "b", first..., "c": "d"};

var command = [
  engineDartPath,
  '--target=flutter',
  extraFrontEndOptions...?,
  mainPath
];

I kinda like that better in general, actually. It reads more like English. Would it be sufficiently unambiguous to parse?

those seem equally confusing to me... ..., whether as prefix or suffix, looks like it binds more tightly than +. (That's a problem we run into with .., where it looks like it binds more tightly than it does, which makes the code a bit confusing to read sometimes... to the point where sometimes I encourage people to add more parens than strictly necessary.)
If we make ... bind tightly, it would end up being one of these:
var command = [
  engineDartPath,
  ...(stuff + moreStuff),
  another,
  (stuff + moreStuff)...,
  more
];

Both work ok here, but I think I prefer the latter. What about something more elaborate:
  var arguments = <String, Object>{
    'foo': bar,
    ...?tabStops?.map<String, Object>(
      (String int, Direction direction) => new MapEntry('--tab$int', direction.toString()),
    ),
    'baz': quux,
  };

  var arguments = <String, Object>{
    'foo': bar,
    tabStops?.map<String, Object>(
      (String int, Direction direction) => new MapEntry('--tab$int', direction.toString())
    )...?,
    'baz': quux,
  };

I think the suffix form has a (very) slight edge, mostly because it's not actually necessary to understand the code (obviously if it's valid code, and you have a random expression in the middle of the literal, it's going to be adding that value to the map -- the ... is only really required to disambiguate between adding the list itself or expanding the list, in the case of a list literal where the list itself would be a valid value). Since it's not strictly necessary for readability, the prefix form is IMHO slightly hurt by the in-your-face-ness of its leading ? coming before an alphabetic character and it being before the thing you're null-checking instead. (Especially egregious in the example above where there's a question mark before and after the first identifier.)

Closing since this syntax is locked down now.

authors: Hixie munificent

repo: munificent/ui-as-code


text:
location report map height change

I see the map size is set to 500px for height.  I made a change to my code to set it up so it fills the browsers window.  Here is the code I changed in location.php:
line 9:

line 11:

I tested in Safari 9, Firefox 43 and Chrome 48.

If you could send a Pull Request with your code, we can review your changes. Testing on iPhone recommended as well.

I just did the pull request with changes.  Hopefully I did it correctly.

authors: bochoven rfitzwater

repo: munkireport/munkireport-php


text:
update it.json with the news descriptions

@WildBoni I added one description, but two others will come soon x)

It's okay x)

repo: muonium/translations

license: WTFPL


text:
🛑 KD Home is down

In e8833ff, KD Home (http://kadambarid.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KD Home is back up in 07272f8 after 7 minutes.

repo: muse-amuse/status


text:
MA - Failed to Setup

What version of Music Assistant has the issue?
2022.11.0
The problem
Setting up MA for the first time and getting "Failed to set up. Check the logs". Logs are below.
This is being running a RPi 4 and DietPi as the OS
How to reproduce
Download 2022.11.0 from HACS
Restart HA
Add MA
Choose 2 entities
No other options enabled (no TuneIn, YT, Spotify etc..)
Submit
Relevant log output
Logger: homeassistant.config_entries
Source: deps/lib/python3.9/site-packages/sqlalchemy/engine/cursor.py:164
First occurred: 10:14:06 (1 occurrences)
Last logged: 10:14:06
Error setting up entry Music Assistant for mass
Traceback (most recent call last):
File "/home/homeassistant/.pyenv/versions/3.9.15/lib/python3.9/site-packages/homeassistant/config_entries.py", line 365, in async_setup
result = await component.async_setup_entry(hass, self)
File "/mnt/dietpi_userdata/homeassistant/custom_components/mass/init.py", line 197, in async_setup_entry
raise exc
File "/mnt/dietpi_userdata/homeassistant/custom_components/mass/init.py", line 190, in async_setup_entry
await mass.setup()
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/music_assistant/mass.py", line 79, in setup
await self.database.setup()
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/music_assistant/controllers/database.py", line 43, in setup
await self._migrate()
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/music_assistant/controllers/database.py", line 216, in _migrate
await self.set_setting("version", str(SCHEMA_VERSION))
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/music_assistant/controllers/database.py", line 60, in set_setting
return await self.insert(
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/music_assistant/controllers/database.py", line 137, in insert
return await self.get_row(table, lookup_vals)
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/music_assistant/controllers/database.py", line 115, in get_row
return await self._db.fetch_one(sql_query, match)
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/databases/core.py", line 148, in fetch_one
return await connection.fetch_one(query, values)
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/databases/core.py", line 257, in fetch_one
return await self._connection.fetch_one(built_query)
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/databases/backends/sqlite.py", line 120, in fetch_one
metadata = CursorResultMetaData(context, cursor.description)
File "/mnt/dietpi_userdata/homeassistant/deps/lib/python3.9/site-packages/sqlalchemy/engine/cursor.py", line 164, in init
(
ValueError: not enough values to unpack (expected 5, got 4)
Additional information
No response
What version of Home Assistant Core are your running
2022.11.4
What type of installation are you running?
Home Assistant Core
On what type of hardware are you running?
Raspberry Pi

Possibly a dependency is missing. sqlalchemy is mentioned at the top. You might not have the correct version. Recommend running HassOS to avoid these issues

Reading around a bit more, seems I did the 2nd half of the paragraph for my first install 😟:

I've upgraded my HA and it still doesn't work so it seems like I'm a bit stuck on this
OzGav, thanks for the suggestion but I don't think I can upgrade to HassOS due to what I'm currently running on the Pi

Closing this off as did a fresh install of HA 2022.11 and MA 2022.11 and all working fine now

Thanks for reporting back, and enjoy the working setup!

authors: Alexis-Grant OzGav erkr

repo: music-assistant/hass-music-assistant


text:
pgHead not valid in MEI basic

The following snipped with a /pgHead within /scoreDef seems to be not valid in MEI basic
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="https://music-encoding.org/schema/dev/mei-basic.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="https://music-encoding.org/schema/dev/mei-basic.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<mei xmlns="http://www.music-encoding.org/ns/mei" meiversion="5.0.0-dev+basic">
	<meiHead>
		<fileDesc>
			<titleStmt>
				<title>Untitled score</title>
				<respStmt>
					<persName role="composer">Composer / arranger</persName>
				</respStmt>
			</titleStmt>
			<pubStmt>
				<date isodate="2023-05-23-19:19:58" />
			</pubStmt>
		</fileDesc>
	</meiHead>
	<music>
		<body>
			<mdiv>
				<score>
					<scoreDef>
						<pgHead>
							<rend halign="left" valign="top">
								<rend>Flute part</rend>
							</rend>
						</pgHead>
						<staffGrp>
							<staffDef n="1" lines="5" meter.count="4" meter.unit="4">
								<label>Flute</label>
								<labelAbbr>Fl.</labelAbbr>
								<clef shape="G" line="2" />
							</staffDef>
						</staffGrp>
					</scoreDef>
				</score>
			</mdiv>
		</body>
	</music>
</mei>

However, pgHead is included in the MEI basic customization since it was not excluded from the shared module https://github.com/music-encoding/music-encoding/blob/7386533bf85c70c13d4f399018d34949d291eb62/customizations/mei-basic.xml#L63
However, it is not included here
https://github.com/music-encoding/music-encoding/blob/7386533bf85c70c13d4f399018d34949d291eb62/customizations/mei-basic.xml#L972-L974
Wasn't the original idea was for it to be allowed?

@lpugin This issue was fixed with #1141, right?

authors: lpugin musicEnfanthen

repo: music-encoding/music-encoding


text:
build: use linter to format files in a standardized way

We should probably introduce some kind of (automatic) linting for the XML(XSLT files in the repository some day to aim for a standardized way of formatting. Via git hooks this could be applied with every commit.
Possible linters:

https://github.com/prettier/plugin-xml
https://gnome.pages.gitlab.gnome.org/libxml2/xmllint.html

Others?

I played around with some of those and they would bring some massive changes. I'd propose to introduce this first for our XSLTs in the encoding tools. Any thoughts?

authors: musicEnfanthen rettinghaus