text:
Can't recieve incoming calls in the VoiceQuickstart tutorial

Description
Hello Friends
I found a lot of issues describing my issue but none of them solved it.
I'm trying to implement the quickstart app. I'm reaching the 10th step 10. Receive an incoming call but I can't receive an incoming call. I made sure my VoIP certificates are correct, and also implemented push certificates. I made sure everything from the server side is implemented correctly, anyway makeCall.php is working perfect.
I'm trying to call "https://mymdline.tedmob.com/placeCall.php" from my browser to test if I receive an incoming call on my implemented app.
Thank you a lot
I'm receiving the below :
[Twilio.Api.V2010.CallInstance accountSid=XXXXXXXXXXXXXXXXXXXXXXXXXXX sid=XXXXXXXXXXXXXXXXXXXXXXXXXXX]sid
which I think means that everything is implemented correctly from the server-side.
yet I'm not receiving an incoming call
Code
$ACCOUNT_SID = 'Account-SID-from-my-main-account';
$API_KEY = 'from-the-voice-api-key-i-created';
$API_KEY_SECRET = 'from-the-voice-api-key-secret-i-created';
$PUSH_CREDENTIAL_SID = 'from-Push-Credentials-page';
$APP_SID = 'from-TwiMlApp-I-Created';
Expected Behavior
receiving an incoming call after calling "https://mymdline.tedmob.com/placeCall.php"
Actual Behavior
not receiving anything after "https://mymdline.tedmob.com/placeCall.php"
yet no errors are shown
Reproduces How Often
all the time
Twilio Call SID(s)
I think this is the call sid you need
[Twilio.Api.V2010.CallInstance accountSid=XXXXXXXXXXXXXXXXX sid=CAe02e2ddc8509f915d4fb2dccc0d8a17e]sid
Logs
// Log output when the issue occurs
2020-05-29 16:47:45.689426+0300 SwiftVoiceQuickstart[978:152432] Twilio Voice Version: 5.3.1
2020-05-29 16:47:45.692883+0300 SwiftVoiceQuickstart[978:152710] pushRegistry:didUpdatePushCredentials:forType:
2020-05-29 16:47:46.081846+0300 SwiftVoiceQuickstart[978:152432] providerDidBegin
2020-05-29 16:48:30.305014+0300 SwiftVoiceQuickstart[978:152985] StartCallAction transaction request successful
2020-05-29 16:48:30.312277+0300 SwiftVoiceQuickstart[978:152432] provider:performStartCallAction:
2020-05-29 16:48:30.874630+0300 SwiftVoiceQuickstart[978:152432] provider:didActivateAudioSession:
2020-05-29 16:48:31.478783+0300 SwiftVoiceQuickstart[978:152432] callDidStartRinging:
2020-05-29 16:48:32.924048+0300 SwiftVoiceQuickstart[978:152432] callDidConnect:
2020-05-29 16:48:33.001902+0300 SwiftVoiceQuickstart[978:152432] AVAudioSession setAggregatedIOPreference:error: Error Domain=NSOSStatusErrorDomain Code=560030580 "(null)"
2020-05-29 16:48:38.085050+0300 SwiftVoiceQuickstart[978:152432] Call disconnected
2020-05-29 16:48:38.254382+0300 SwiftVoiceQuickstart[978:152432] provider:didDeactivateAudioSession:

#### Voice iOS SDK
TwilioVoice (5.3.1)
COCOAPODS: 1.9.1
#### Xcode
11.3.1 (11C504)

#### iOS Version
iOS 13.5

#### iOS Device
iPhone XS

Hello @bchen-twilio
You're right I was using a wrong identity, I changed it to $identity = 'alice'; , and everything worked perfect.
anyway since this worked, I have another major inquiry, how can I make a call from an Android app to an iOS App, I'm checking the config file and it's indicating that I can only use one $PUSH_CREDENTIAL_SID, so how can I work with both apps
Thank you a lot.

Hi @MhmdRizk
Our server example uses request-based APIs which can process requests from your mobile clients and, in this case, return different access tokens based on the platform parameters from your mobile apps. For example, use https://your.serverurl/accessToken?platform=android on your Android devices and in server endpoint that returns access token use the Push Credential SID created from your FCM/GCM credentials. Similar way for iOS.

Thank you @bchen-twilio
I did exactly as you recommended and everything works perfectly now.

authors: MhmdRizk bchen-twilio

repo: twilio/voice-quickstart-ios


text:
Lang filter still not working

I have read other requests on this but the lang filter is still not working for me

Same! You can work around this manually by scraping all tweets and filtering afterwards for your wanted language. Additionally, I wanted to say how happy I am with this package (which is the next to SnScrape the only one still working to my knowledge)!

source: gharchive/issue

repo: twintproject/twint

license: MIT

license_type: permissive

license_source: github-api


text:
DISCONNECT from all channels

Expected behaviour
JOINED channels should behave
Actual behavior
Library suddenly disconnects from the channels and slowly rejoins them
Steps to reproduce
Not gonna lie, there isn't much i can tell here, other than just join top 500 channels and add a counter on the PRIVMSG event and watch it drop out of nowhere for no reason whatsoever(no errors either)
Your environment

Operating system(s): Ubuntu 14/windows 10 pro
TwitchJS version: latest
NodeJS version:14
Browser(s):NA

[Explanation]: My metrics server is constantly updating those values real time/every minute. As you can see, its properly displaying the cache, the cached users and the cache message count, only the message count is 0. This means no PRIVMSG events were emitted during that whole time of downage.
This might be the same thing from a previous issue with the library just halting and becoming unresponsive.
Though with metrics I'm safely logging them.
The bot is still on and connected, I've triple checked my connection(10 gigabit internet) and the process still is working, its definitely a library issue internally. Idk if its not handling that many events in a normal user(that isn't verified) or what, but even in production those errors are hard to catch since it cannot be caught unless a user attempts a command and reports it.
Here's my suggestion: Like me, add a simple counter to PRIVMSG event and increment each time its called. Every minute, log it somewhere. I'd like to gather more data from other people here to see if this is replicable on other ends, I'm willing to share snippets and sources of my code as well to figure this out if needed, as this has been quite an annoying issue so far.

@victorperin as you referenced similar errors in a previous issue, i'd like to ask you to do the same and add a counter on your PRIVMSG event and log them frequently somewhere persistent(like a database)

Thanks for marking me. I'll keep the talk in english to help others here, but you can msg me on telegram with the same username if this starts to get complicated.
We changed a generic function in the lib to reject some promises if got timedout, could be the case of this. #259
Tomorrow I will run some tests on the case you described and try to, at least, narrow down what the problem is. At this time I will not jump to any conclusions as it could be twitch servers limiting those pub/sub calls or something like that.
When we understand better what exactly causing it, we can implement an automated test so we can be sure it never occours again.

Also, can you save the logs of witch twitch produces, with date times and a time where you detected those stops? I want to see what twitch servers are responding in that period.

@victorperin I already have most logs that indicate timestamps in the database itself(which is pulled on grafana), are you looking for anything other than the error timestamps + the error itself?
Also i dont have telegram, though im more than happy to use discord if you wish (Not Erwin#8753), also i can provide the whole script im using to loop this(which is producing the error). I can give some quick information out of the boo with this, the first is: there are two distinct errors here, one is produced when trying to join channels while still respecting the ratelimit(which likely is being affected by internal JOIN/reconnects, or the API itself not liking a normal user being on so many channels), and the second is the lib itself throwing timeout errors on its own without me adding more JOINS ontop.
These were the cases
Case 1: No chat.join()'s, simply giving errors.
Case 2: Multiple chat.join()'s, got errors on 421 streams, 709 and 287.
Case 3: Join with a VERY limited/close ratelimit (going 20 JOIN every 11 seconds), errors on 61, 98, 108, 187(and 8 more, totalling 8h to completely join(waiting 30m between to refresh API)).
From those cases, number 1 is related to the library internals error'ing itself.
From cases 2 and 3, im the one doing the calls so im fairly certain im the culprit in this case, though BOTH case respects ratelimits which is odd(my assumption is internals stacking with my JOIN attempts) and i dont see an exposed variable to be able to safely check the current limit without just 'being careful'

@victorperin Ive just started a mass query to produce some errors so we can take a look later.

Im only doing unhandled rejections for now, i did not find in the docs if client emits an 'ERROR' event that i can log too on this.
Those are being dumped into a temporary table in my database

Running the test on 3000 streams, this should yield at least one error every 400 or so streams(thats the avarage ive gathered so far)
Please let me know if the client instance emits an error/warn events i can hook into to dump into the database as well, my typescript is a bit borked and im not seeing the other emitted events(only saw PRIVMSG on the jelly docs too)

@erwin1234777 FYI, the library is suppose to handle the the rate limit automatically for you.
With the library's current implementation, the library isn't shielded from errors that may be thrown in consumer-provided event handlers, so this will be hard to debug.

@marcandrews So am i able to simply throw all the channels at it and wait for it to handle them rather than awaiting it and adding delay between each iteration?

@erwin1234777 Yes, but honestly, I haven't test the rate limiting functionality it at this scale.

@marcandrews thats exactly what i need right now, since im implementing a somewhat aggressive cache, i need to test it on a large scale to support my Discord traffic as well.

Im first populating the base cache, which needs to be always properly present.
Before i can get to the next step

i need to make sure the base cache scales fine and isnt being overly RAM intensive and double check that are no memory leaks anywhere. Adding that big stress chunk seems the best way to accomplish that, though im getting quite a few errors with chat timeouts

Closing #264 as its too similar

@marcandrews

i just attempted without no delays whatsoever, just awaiting the promises to fulfill

now its simply joining on every iteration, still got a timeout

@marcandrews Providing the whole script thats in charge of populating the cache
https://paste.awoo.rocks/nagiledusi.js

You can try listening to these events. I don't know where the red ERROR is coming from though.
I'll take a look at your implementation.

Im assuming all those should be enough for a start in logging the errors?

Yes.
Also

try not .catching the promise (L82-6) and handling the error in catch block
add logging to the catch block (L116)

Updated https://paste.awoo.rocks/buqonedeli.js

You should also console log out the error in the catch block (L110)

Updated: https://paste.awoo.rocks/sijixakiko.js

Most of those errors are due to chinese characters streams not being able to be joined. ive logged those before and forgot to explain. Asian characters tends to bork a bit on join

Use v5 to get the streams, and instead of display_name, use name.

isnt v5 deprecated?

Yes, but "deprecated" is not the same as "decommissioned".
https://dev.twitch.tv/docs/product-lifecycle

If you don't want to use v5, you'll have to use GET https://api.twitch.tv/helix/users and use data[].login to join the channels.

That is precisely what im doing. See line 122 https://paste.awoo.rocks/sijixakiko.js
and using user_name.toLowerCase() to match twitch's login(which should be exactly the same as user name but without upper case)

I know, but I don't think data[].user_name is the normalized Twitch user login that you need to join channels.

I can definitely add another chunk query, but i assume that would only increase the api call limits(which is the goal im trying to accomplish by caching), though for testing i can use that if you think it'll help

That's why I would just use v5.

im assuming v5 returns the login name ALONG with the channel data. The problem is the chunking for testing. Since it only returns 900 (and my cache test is aimed at roughly 8-10k streams for 7 days) it becomes a hindrance in my case

I'm not sure I understand; both endpoints only return a maximum of 100 entities per call.

Indeed, though according to v5 documentation, i get a limit of 900 streams offset in total.
In the Helix, the limit is way higher(hence why i can cache al
most 4000 within one big iteration

Though v5 does seem to have its benefits, providing me with specifically
partner and followers which i need for the second step of caching.
Those usually need to be retrieved from the /users endpoint iirc, which would increase more API calls

Although that could be an oversight in my implementation with using an Array for queue and not a Set, there is a chance of duplicates that im not taking into account, however i am definitely passing the 900 offset limit within the helix enpoint

so even with duplicates, helix seem to have a much higher offset limit

As i assumed, the only errors in join() are regards of chinese characters

Code Update: https://paste.awoo.rocks/visiqenona.js

Update:  @marcandrews

i could not get that red error either, though this is what ive logged so far.

The only events i was able to grather were from the STRESS_TEST
That ERROR is being emitted somewhere else that isnt one of these

Update: I did get a 1006 IRC error

not sure if this includes timeout(ratelimit)

Another update:
Im logging CONNECTED events as seen in here though im not receiving any logs on my end, not sure its being emitted.

Code

Logs dont show a single CONNECT event.

Im attempting to log CONNECT events as seen in here, no success(was hoping to catch last attempt before it error'd)

Not a single CONNECT event has been emitted

Are you binding the listener before calling chat.connect()?

I am not, the chat is connected before. I assumed a .join() would result in a CONNECT event to be triggered, though from what you just told me it sounds like thats only when the client/chat is created

@marcandrews @victorperin is there something else i can do to provide more logs or info about this for debugging that you guys can think of?

Try using chat.send() to manually join channels; .send() is still rate-limited, but it will not confirm channel joins with ROOMSTATE and USERSTATE messages like .join() will so it will not throw.
Until the library is updated to shield itself from errors that may be thrown in consumer-provided event handlers, it will be hard to determine the root cause unfortunately.

Alright, i assume the syntax would be chat.send('JOIN')?

@erwin1234777 can you simplify this code? It's pretty hard to understand what it's doing and this problem could be in this complexity instead the lib itself.
We need to understand only what api's are you using to figure out what kind of problem the lib could be generating.

I'm running this code since the day you opened the issue, to figure out what could be happenning, but it seems pretty stable.
This code can run without any other lib other than twitch-js:
const TwitchJS = require('twitch-js').default

const username = process.env.TWITCH_USERNAME
const token = process.env.TWITCH_TEST_BOT_TOKEN

const { chat } = new TwitchJS({ username, token })

const counter = new Map()
const count = ({ channel }) =>
        counter.set(channel, (counter.get(channel) || 0) + 1)

const joinAndListen = (channel) => chat.join(channel)

const joinAndListenReducer = async (prev, next) => {
        await prev
        return joinAndListen(next)
}

const channels = [
  // all channels you want to listen messages
]

chat.connect()
        .then( () => chat.on('PRIVMSG', count) )
        .then( () => {
                channels.reduce(joinAndListenReducer, Promise.resolve())
        })

let previousCache = JSON.stringify(Array.from(counter.entries()))
setInterval(() => {
        const counterCheck = JSON.stringify(Array.from(counter.entries()))
        if(previousCache === counterCheck) return;

        previousCache = counterCheck
        console.log(counter)
}, 1000)

@victorperin How many channels are you running that test on? Also i'm more than willing to allow you to clone the repo to test it if you so wish to have a local test copy of it

@victorperin can i take up on your offer to message you on telegram or Discord(preferably?) I did manage to grab an oversimplified version of my code that i can put on a repo for you

@marcandrews @victorperin i've sent you both an invitation to the repo. Its just 3 files. a test file to check if the bot is connected on the stream, the index and the stress test. I've attached my interfaces file on it as well

judging by the inactivity im assuming there'll be no more support for this case, though i provided code for further testing + info.

maybe it will be easier to manage and read so many channels in IRC
maybe that will help: https://github.com/gempir/go-twitch-irc/issues/102#issuecomment-510882229

maybe it will be easier to manage and read so many channels in IRC
maybe that will help: gempir/go-twitch-irc#102 (comment)
@spddl

I just checked the thread, it might be just that, though in fairness, the problem isnt mainly JOIN commands, but also their maintenence. Even AFTER the channels have been joined, it simply stops recieving events from it. I did provide a much smaller test in a private repo, but neither of the contributors joined.
As far as 300 channels in 5 minutes goes, that still a low end from what i experienced
Since one single connection isnt cutting(be it cuz of the lib or whatever) im attempting my clustering with slave/masters, and that seems much more stable, though still errors every now and again, though, with this at least i dont get all connections disconnected, only the ones the shard is taking care of.
 This test was done to see how well i could use IPC promisified to join the shards via a master. 30k channels joined within 15 seconds. While the QUICK JOIN effect of this isnt much of use for me, as im merely testing cache stability(still), sometimes when the library disconnects, having this quick 'recovery' is quite handy, as you saw, joining thousands of channels can take quite a few hours to complete.

This is one of the failed tests, i did optimize this enough to be able to join roughly 48k channels within 20 seconds without errors by sharding them. This makes it noticeable that the lib is at fault and cant handle large amount of channels at once, be it because of the lib or (what i assume is) the webscoket connection.
That link confirmed what i had in mind about a single connection being problematic when it comes to a single connection taking care of that many chanels, so i appreciate that since i wasnt aware of.
Thank you :D

https://github.com/twitch-js/twitch-js/issues/227#issuecomment-530615887

In an upcoming release (#238), joins will no longer timeout due to the queue.

@erwin1234777 can you try again with 2.0.0-beta.35?

@erwin1234777 can you try again with 2.0.0-beta.35?

will give it a try soon

@erwin1234777 can you try again with 2.0.0-beta.35?

will give it a try soon

Make sure to try the latest version :sweat_smile:

Make sure to try the latest version :sweat_smile:

@marcandrews just tried it, it still doesnt like quickly joining in 1k+ streams, i do sometimes see the graphs from the ws events dropping down to 0 or massive drops (meaning one or more of my shards died), still using the old code provided before

@marcandrews just tried it, it still doesnt like quickly joining in 1k+ streams, i do sometimes see the graphs from the ws events dropping down to 0 or massive drops (meaning one or more of my shards died), still using the old code provided before

Twitch documentation has been updated and you should only be able to join 10 channels every 30 seconds. The latest updates reflect this so it may take a few minutes to join 1000+ channels, but Chat#join should no longer reject prematurely.

Twitch documentation has been updated and you should only be able to join 10 channels every 30 seconds. The latest updates reflect this so it may take a few minutes to join 1000+ channels, but Chat#join should no longer reject prematurely.

thats what i meant, its not about taking a while to join the streams, but about the connection dropping for a couple minutes. The expected behaviour would be to join 10 channels, wait 30, then join 10 more, hence and fourth. What actually ends up happening is that loop, but eventually on the 100th or so i stop recieving all ws events from that cluster, and after a while, i recovers. But its that downtime that i see as an issue, not the slowness to join servers, as its intended to be respecting ratelimits.

thats what i meant, its not about taking a while to join the streams, but about the connection dropping for a couple minutes. The expected behaviour would be to join 10 channels, wait 30, then join 10 more, hence and fourth. What actually ends up happening is that loop, but eventually on the 100th or so i stop recieving all ws events from that cluster, and after a while, i recovers. But its that downtime that i see as an issue, not the slowness to join servers, as its intended to be respecting ratelimits.

On a side note, i also have my own coded cluster with IPC, so the 10 attempts per 30 seconds is easily avoidable on my frame, since i have a proxy with 46 ipv6's that im rotating for each cluster i spawn, and i also have a master controlling each node and what servers they should take care of. Though thats not the testing setup im testing, since it could be bugs in my implemention, the one im testing this one is a single file with a simple 1200+ request to join, without the complicated'ness i described

On a side note, i also have my own coded cluster with IPC, so the 10 attempts per 30 seconds is easily avoidable on my frame, since i have a proxy with 46 ipv6's that im rotating for each cluster i spawn, and i also have a master controlling each node and what servers they should take care of. Though thats not the testing setup im testing, since it could be bugs in my implemention, the one im testing this one is a single file with a simple 1200+ request to join, without the complicated'ness i described

Hopefully these are helpful:
https://stackoverflow.com/questions/17033631/node-js-maxing-out-at-1000-concurrent-connections
https://blog.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/
Until we can determine that the problem is with the library, I will close this issue, but please keep me updated and let me know if the above helps.

Hopefully these are helpful:
https://stackoverflow.com/questions/17033631/node-js-maxing-out-at-1000-concurrent-connections
https://blog.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/
Until we can determine that the problem is with the library, I will close this issue, but please keep me updated and let me know if the above helps.

Hopefully these are helpful:
https://stackoverflow.com/questions/17033631/node-js-maxing-out-at-1000-concurrent-connections
https://blog.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/
Until we can determine that the problem is with the library, I will close this issue, but please keep me updated and let me know if the above helps.

I had already taken this in consideration on my cluster with a 800 limit per shard since i've worked with socket.io before. Like i mentioned, its not the fact that it cant handle 1000, but throughout the whole process of getting to the 1000 it clogs and halts it for the next couple minutes (which really feels like it hit a ratelimit and is waiting to recieve events again). But i'll keep you updated of any changes.
A little bit more info on my production setup:
Each shard is its own unique process, it is created by a master process and is started with a custom argument on the startup command with a unique ID. Each ID fowards to one of the proxies, rotating each time theres a new spawned process. Each process is using its own ws connection. As far as the production goes, i got both the ratelimits and each node limited to 800 per, once that threshold gets filled, the master process spawns a new one and sends the new channels to be handled.
So all channel join events are distributed throughout different process, so its highly unlikely (specially with ip rotation) that im hitting the 1k ws limit you showed. But once again, i'll keep you updated if i find anything else (i havent properly debugged after you pushed the update, so all the info im providing rn is based off the last version), and the current test was tested on the current version you suggested me to use, but not nearly as deep as what i did before

Hopefully these are helpful:
https://stackoverflow.com/questions/17033631/node-js-maxing-out-at-1000-concurrent-connections
https://blog.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/
Until we can determine that the problem is with the library, I will close this issue, but please keep me updated and let me know if the above helps.

I had already taken this in consideration on my cluster with a 800 limit per shard since i've worked with socket.io before. Like i mentioned, its not the fact that it cant handle 1000, but throughout the whole process of getting to the 1000 it clogs and halts it for the next couple minutes (which really feels like it hit a ratelimit and is waiting to recieve events again). But i'll keep you updated of any changes.
A little bit more info on my production setup:
Each shard is its own unique process, it is created by a master process and is started with a custom argument on the startup command with a unique ID. Each ID fowards to one of the proxies, rotating each time theres a new spawned process. Each process is using its own ws connection. As far as the production goes, i got both the ratelimits and each node limited to 800 per, once that threshold gets filled, the master process spawns a new one and sends the new channels to be handled.
So all channel join events are distributed throughout different process, so its highly unlikely (specially with ip rotation) that im hitting the 1k ws limit you showed. But once again, i'll keep you updated if i find anything else (i havent properly debugged after you pushed the update, so all the info im providing rn is based off the last version), and the current test was tested on the current version you suggested me to use, but not nearly as deep as what i did before

How exactly are you spawning the sub processes, use worker threads?
What's the unique ID? Does it sub process have it's own credentials, or is one credential shared across all sub processes?
Are you just listening to channels, or are you posting messages in them too?

How exactly are you spawning the sub processes, use worker threads?
What's the unique ID? Does it sub process have it's own credentials, or is one credential shared across all sub processes?
Are you just listening to channels, or are you posting messages in them too?

How exactly are you spawning the sub processes, use worker threads?
What's the unique ID? Does it sub process have it's own credentials, or is one credential shared across all sub processes?
Are you just listening to channels, or are you posting messages in them too?

i tried with worker threads, but i did a fallback with a complete new process with fork, i dont remember why but i've had issues with worker threads before.

the sub process gets spawned by the master with basically this (theres a lot more code involved)

The index is generated before spawning checking for the previous already started subprocesses (to prevent duplicates)
Inside the code, i've got this

Which is the identifier it uses to do the rest of the functions, including using it to connect to the existing IPC line and use one of the proxy ips.

In this case, just listening.

How exactly are you spawning the sub processes, use worker threads?
What's the unique ID? Does it sub process have it's own credentials, or is one credential shared across all sub processes?
Are you just listening to channels, or are you posting messages in them too?

i tried with worker threads, but i did a fallback with a complete new process with fork, i dont remember why but i've had issues with worker threads before.

the sub process gets spawned by the master with basically this (theres a lot more code involved)

The index is generated before spawning checking for the previous already started subprocesses (to prevent duplicates)
Inside the code, i've got this

Which is the identifier it uses to do the rest of the functions, including using it to connect to the existing IPC line and use one of the proxy ips.

In this case, just listening.

What about the credentials?
What do you mean by "index is generated"? Are you creating a new JS file for each sub process and then using child_process to fork/spawn?

What about the credentials?
What do you mean by "index is generated"? Are you creating a new JS file for each sub process and then using child_process to fork/spawn?

Basically, if theres already 25 slave processes, the next index will be 26, to put it simply, which gets added and sent here.

The file is always there, its not being created, but rather RAN. fork() is targetting slaveChat.ts, which gets transpiled and run with npx

Basically, if theres already 25 slave processes, the next index will be 26, to put it simply, which gets added and sent here.

The file is always there, its not being created, but rather RAN. fork() is targetting slaveChat.ts, which gets transpiled and run with npx

What about the credentials?
Are you running it with ts-node or similar?
If you are trying to join 800 channels per sub process, you will be rate limited, so won't the setTimeout cause the _a to resolve with false?

What about the credentials?
Are you running it with ts-node or similar?
If you are trying to join 800 channels per sub process, you will be rate limited, so won't the setTimeout cause the _a to resolve with false?

What about the credentials?
Are you running it with ts-node or similar?
If you are trying to join 800 channels per sub process, you will be rate limited, so won't the setTimeout cause the _a to resolve with false?

im running it with npx, which is the same as ts-node. The controller is a lot more complicated than this, that even you see is simply the creation, not the distribution of channels. The initial CONNECT event is only responsible for spawning a new process, (in slavChat.ts) => set its own identifier, join twitch API, and once its done, send another IPC message stating that it has sucessfully connected. Let me show the order that this is done so its a bit more clear

step 1. Fork it
step 2. listen for CONNECT

After forking:
1.Initiate the Twitch-js.
2.chat.join() chained with a .then()
3. on the .then() chain, emit back to the IPC pipe to resolve the promise with CONNECT.
I've also marked some key points such as the CONNECT event being checked and the slave names being sent to assure the process sending it is the same as the one that the controller spawned

What about the credentials?
Are you running it with ts-node or similar?
If you are trying to join 800 channels per sub process, you will be rate limited, so won't the setTimeout cause the _a to resolve with false?

im running it with npx, which is the same as ts-node. The controller is a lot more complicated than this, that even you see is simply the creation, not the distribution of channels. The initial CONNECT event is only responsible for spawning a new process, (in slavChat.ts) => set its own identifier, join twitch API, and once its done, send another IPC message stating that it has sucessfully connected. Let me show the order that this is done so its a bit more clear

step 1. Fork it
step 2. listen for CONNECT

After forking:
1.Initiate the Twitch-js.
2.chat.join() chained with a .then()
3. on the .then() chain, emit back to the IPC pipe to resolve the promise with CONNECT.
I've also marked some key points such as the CONNECT event being checked and the slave names being sent to assure the process sending it is the same as the one that the controller spawned

What about the credentials?
So that _a is only for forking and not related to that actual chat connecting or channel joining?
I see that the sub process is sending CONNECTED, bit the master process is listening for CONNECT. When are you sending CONNECT

What about the credentials?
So that _a is only for forking and not related to that actual chat connecting or channel joining?
I see that the sub process is sending CONNECTED, bit the master process is listening for CONNECT. When are you sending CONNECT

I see that the sub process is sending CONNECTED, bit the master process is listening for CONNECT. When are you sending CONNECT

Ah this is my bad, i was fiddling with the code, but i checked in the prod github and its still written as CONNECT, not CONNECTED.
The credentials i assume you mean the token, client id, etc. Thats being passed using %.
Its getting the argv from process (aka the name) and replacing slave, to get the number process that slave is.
Then im simply doing a (max proxy % slave) and whatever comes next is the index of the proxy and tokens. I think i have roughly 8 or 9 tokens from different applications to connect.
As far as the proxy goes, is a similar method using % operator to pick which proxy it should use

I see that the sub process is sending CONNECTED, bit the master process is listening for CONNECT. When are you sending CONNECT

Ah this is my bad, i was fiddling with the code, but i checked in the prod github and its still written as CONNECT, not CONNECTED.
The credentials i assume you mean the token, client id, etc. Thats being passed using %.
Its getting the argv from process (aka the name) and replacing slave, to get the number process that slave is.
Then im simply doing a (max proxy % slave) and whatever comes next is the index of the proxy and tokens. I think i have roughly 8 or 9 tokens from different applications to connect.
As far as the proxy goes, is a similar method using % operator to pick which proxy it should use

I'm not sure if TMI cares about IPs, so as long as you're connecting with different tokens, that might be enough to increase your limits.
You should not use ts-node for production/memory-intensive code; compile your code with tsc and run the compiled code instead.
Add unit tests. Mock Chat#connect, Chat#join, and related events to simulated 5-10 connections to ensure your implementation is working.
Good luck!

I'm not sure if TMI cares about IPs, so as long as you're connecting with different tokens, that might be enough to increase your limits.
You should not use ts-node for production/memory-intensive code; compile your code with tsc and run the compiled code instead.
Add unit tests. Mock Chat#connect, Chat#join, and related events to simulated 5-10 connections to ensure your implementation is working.
Good luck!

Add unit tests. Mock Chat#connect, Chat#join, and related events to simulated 5-10 connections to ensure your implementation is working.
Good luck!

Will try, ty <3

Add unit tests. Mock Chat#connect, Chat#join, and related events to simulated 5-10 connections to ensure your implementation is working.
Good luck!

Will try, ty <3

authors: erwin1234777 marcandrews spddl victorperin

repo: twitch-js/twitch-js


text:
Bugfix: Setting TextEditorView.scrollView.delegate may broken some behaviour

Problems
We have public api scrollView in TextEditorView, and it is actually UITextView subclass.
If someone set scrollView.delegate for observing scroll event, the TextEditorView will forgot UITextViewDelegate things.
Solution
Implement DelegateForwarder for controlling delegate method invoke target.
DelegateForwarder forward UIScrollViewDelegate things to user side delegate, UITextViewDelegate things to internal implementation.
Testing
No plan 🙃
Discussion
We can implement same thing using Obj-C also, and I think it would be better performance around method dispatch.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This is really nice finding! A few thought on the approach to solve this.
The purpose of internal UITextView exposure as UIScrollView is to be honest, kind of cheating and not ideal solution at all, however, providing a way to control scroll view behavior would be needed for the application.
Therefore some type of proxying is needed anyways and as you pointed out, delegate is shared between accessing it breaks entire behavior for sure and worth to have this type of protection for it.
I think, however, number of delegate and selectors are known and limited for this case, therefore having a generic forwarder implementation seems kind of overkill for this problem. Probably instead just simply implement a proxy delegate class that has text view delegates used for text editor view and all scroll view delegates and forward them to each delegate would be simple...?

This is really nice finding! A few thought on the approach to solve this.
The purpose of internal UITextView exposure as UIScrollView is to be honest, kind of cheating and not ideal solution at all, however, providing a way to control scroll view behavior would be needed for the application.
Therefore some type of proxying is needed anyways and as you pointed out, delegate is shared between accessing it breaks entire behavior for sure and worth to have this type of protection for it.
I think, however, number of delegate and selectors are known and limited for this case, therefore having a generic forwarder implementation seems kind of overkill for this problem. Probably instead just simply implement a proxy delegate class that has text view delegates used for text editor view and all scroll view delegates and forward them to each delegate would be simple...?

Okie, I rewrited DelegateForwarder implementation to domain specific, to be TextViewDelegateForwarder.
Maybe it's reached ready for review 😄

Okie, I rewrited DelegateForwarder implementation to domain specific, to be TextViewDelegateForwarder.
Maybe it's reached ready for review 😄

Sorry for no update on this pull request for a while.
The change has been merged to the internal repository and being tested. When we publish the change here, I will close this pull request.

The change has been merged to the tip branch and pushed, closing the pull request.
Thank you for the contribution.

source: gharchive/pull-request

authors: CLAassistant niw tarunon

repo: twitter/TwitterTextEditor


text:
Provide a minified version of the source file

Minified version should be provided for client side use preferably with a version number in the file name (I don't see the current version of hogan.js anywhere?).

http://twitter.github.com/hogan.js/1.0.0/hogan.min.js

Putting the file on the website is good; linking it from the home page, so it's discoverable, would be better.

yeah i suppose... ideally however you would be pulling hogan down and bundling it with your other assets

huh i didn't mean that. I mean - you should bundle hogan with your other assets.... on the client. You shouldn't be using a minified hogan on the server

Exactly. The point is, there is no link anywhere to download a minified hogan.

I think you're missing it still... On the client you should be bundling all your assets together and minifying them as a single asset... so whether or not this is minified doesn't really matter... :/ Because it will be minified when it's included with your other javascript source files. no?

we can include the link though, that's fine.

authors: fat kpuputti laurie71

license_source: bigquery


text:
Access to field 'start' result in a dereference of a null pointer

Access to field 'start' result in a dereference of a null pointer (loaded from variable 'rsp_buffer')
https://github.com/twitter/twemproxy/blob/c5c725d2b45715e378909ebc909b0492591c4715/src/proto/nc_redis.c#L2943
in line 2940, Null pointer value stored to 'rsp_buffer'

This seems like a false positive from an automated analysis tool
It doesn't seem to happen for various edge cases such as immediate rejection, invalid redis responses, or a server that doesn't send a response.

authors: QiAnXinCodeSafe TysonAndre

repo: twitter/twemproxy


text:
Fix /wl team

Fixes #710 , and allows for "/wl team the red team" (before you could only add 1 argument)
Tested code

Can you amend the commit and perhaps make the commit message "Fix wl team command"? It's better to not have a / in a commit message, just for convention's sake.

@iEli2tyree011 done

merged

repo: twizmwazin/CardinalPGM

license: mit


text:
For future Issues or Pull Requests, PLEASE READ THIS.

It's sad that this package, is no longer maintained in very long time (latest commit when i wrote this was 4 years ago). So I decided to fork this package and continue the maintenance for future usage, supporting the newer version of Python also.
I also encountered some issues, such as #30 and #4. Thus, on my forked repository, lazuardy-tech/anfis, I decided to fix some of those issues, with some improvements for the package. You may install it with pip install lazuardy_anfis and use the package like it was before.
For testing and other documentation, please read it on the repository page. Thanks.
All credit goes to @twmeggs and @lazuardy-tech.

For future needs, please report issue or push PRs on lazuardy-tech/anfis so that we can maintain it.

repo: twmeggs/anfis


text:
No Markdown plugin installed with "gradle run"

When I follow the instructions at the Mac build and run page to install Beaker Notebook on a Mac (10.11.5), there is no working Markdown plugin. When I try and add it using the Language Manager, there is no item in the list for Markdown. I don't have a URL for a Markdown plugin and could not find any URLs for plugins with some Google searching.
My question is: what is required beyond the steps listed on the Mac build and run page in order to get Markdown working with Beaker Notebook?

it's called "text"

and it's not in the language manager, it's one of the blue buttons when you add cells.

repo: twosigma/beaker-notebook


text:
add UI options

in the BeakerX tab of the tree view, add a new tabbed view.  the current JVM options would all be on the first, top tab "JVM Options".  Add a new tab "UI Options" with the following configs:

checkbox to disable the auto parenthesis typing.
checkbox to allow wide code cells.
checkbox to make our font changes.

by default all are checked.  status saved in beakerx.json.

codecell.CodeCell.options_default.cm_config.autoCloseBrackets = false;

<style>.container { width:100% !important; }</style>

{
    "beakerx": {
        "ui_options": {
            "auto_close": false,
            "wide_code_cells": true,
            "improve_fonts": true
        },
        "jvm_options": {
            "heap_GB": 4,
            "other": [],
            "properties": [
                {
                    "name": "myproperty",
                    "value": "myval"
                }
            ]
        },
        "version": 2
    }
}

for notebook only, not lab.

@scottdraves
I've done:

wide_cells
auto_close
show_publication

Don't know what improve_fonts should do

authors: piorek scottdraves

repo: twosigma/beakerx


text:
Make userId in helix moderator filter optional

Type: Bugfix
Fixes: #
I noticed, since I wanted to get a list of moderators myself, that the "HelixModeratorFilter" always wants a UserID, even though this is optional from the Twitch Rest API. With this small bugfix it is now possible to get a bigger list than 20 moderators.

Please rebase this merge request onto the versions/6.0 branch so it can be released as a patch.

authors: ShortByte d-fischer

repo: twurple/twurple


text:
[RFC] Zero padding can be removed using torch-scatter

I have updated as little as possible of the code in order to remove zero-padding from the model. This means that the code can now consider more than a fixed number of neighbours without introducing new 'zero padding' atoms.
Such 'zero padding' atoms are potentially a problem as the use of affine transformations means that the 'zero padding' atoms affect the final result as the bias vectors will introduce no zero features vectors for these atoms.
The torch_scatter library has been used to perform the necessary scatter operations.
The pre-trained models have not been re-trained.
feel free to make changes to this PR.

Closed in favour of #18.


text:
Removing lodash-mix dependency from ReadMe

Removing the lodash-mix dependency (as starting from v1.1.66)

Thanks!

authors: IbrahimHd tybeck

repo: tybeck/pure-angular-advanced-searchbox


text:
Fix for Issue #2149

Fixes in docker-compose.yml and CONTRIBUTING.md to run correctly on Apple Silicon
Issue #2149

Thanks mate!

authors: alstepan jatcwang

repo: typelevel/doobie


text:
Use scoded for B and BS

This changes the decoding and representation of  the DynamoDb AttributeValue B and BS. Also this solves a big where the BS DynamoDB AttributeValue BS type was modelled as a single String that would fail the decoding.
B is a binary value Base64 encoded on the wire, while BS is an ordered set of binary base64 encoded value.
Given that feral depends already on scodec, it makes sense to use BinaryVector to model the binary value.

We need to bump the base version to 0.3 because this is a breaking change.
https://github.com/typelevel/feral/blob/424590163f05fd4d06692c0880815eff387708db/build.sbt#L21

Also this solves a big where the BS DynamoDB AttributeValue BS type was modelled as a single String that would fail the decoding.

Sorry, I couldn't quite understand. Would you mind sharing an example? Did we add a test for this case?

Also this solves a big where the BS DynamoDB AttributeValue BS type was modelled as a single String that would fail the decoding.

Sorry, I couldn't quite understand. Would you mind sharing an example? Did we add a test for this case?

Sure,
B on the wire is a Base64 encoded binary, and at this moment it is modelled as a string. Not ergonomic but it works.
{
  "B": "Base64..."
}

On the other hands BS on the wire is an array of Base64 encoded binary strings:
{
  "BS": [
    "Base64...",
    "Base64..."
  ]
}

But, right now, on feral, it is decoded as a single String, and so the circe decoding fails.
Does it make sense?

Oh, I totally missed that! That is indeed a bug, not related to String vs Bytevector but because we forgot List 🤦 thanks!

Oh, I totally missed that! That is indeed a bug, not related to String vs Bytevector but because we forgot List 🤦 thanks!

Yeah sorry I have conflated two things given that it was a breaking change anyway

authors: armanbilge filosganga

repo: typelevel/feral


text:
Bump Podspec Version

Fixes #131

:+1:

:boat:

Just pushed v0.4.1 to Pods trunk

authors: CodaFi mpurland

repo: typelift/SwiftCheck


text:
ArrayIndexOutOfBoundsException parsing class file

I'm getting an ArrayIndexOutOfBoundsException out of MiMa (link to full error):
java.lang.ArrayIndexOutOfBoundsException: 1515
	at com.typesafe.tools.mima.core.BufferReader.nextByte(BufferReader.scala:33)
	at com.typesafe.tools.mima.core.BufferReader.nextChar(BufferReader.scala:48)
	at com.typesafe.tools.mima.core.ClassfileParser.parseMembers(ClassfileParser.scala:216)
	at com.typesafe.tools.mima.core.ClassfileParser.parseFields(ClassfileParser.scala:208)
	at com.typesafe.tools.mima.core.ClassfileParser.parseClass(ClassfileParser.scala:261)
	at com.typesafe.tools.mima.core.ClassfileParser.parseAll(ClassfileParser.scala:68)
	at com.typesafe.tools.mima.core.ClassfileParser.parse(ClassfileParser.scala:59)

The offending jar file is http4s-jawn_2.11-0.13.0a, and the mima version is 0.1.9.
I found a similar issue, but not an answer.  Any idea what might be going on here?  Thanks!

Thanks for reporting. Would be great to isolate the issue and add a test to the regression suite before fixing it. Contribution welcomed! :-)

I've seen a similar issue here: https://github.com/fthomas/refined/pull/154. The problem went away after running mimaReportBinaryIssues before sbt-scoverage's coverage in the CI build.

I'm also seeing it in macro-compat.

We're also see it in Play builds: https://travis-ci.org/playframework/playframework/jobs/134935906#L613

It looks like the BufferReader is reading past the end of the array that's passed in.  I'll add some checks.

One thing that stands out is that in nextBytes the index pointer is being updated before the call to slice, and then buf.slice() will only slice up to the length of the actual array:
  def nextBytes(len: Int): Array[Byte] = {
    bp += len
    buf.slice(bp - len, bp)
  }

https://github.com/typesafehub/migration-manager/blob/master/core/src/main/scala/com/typesafe/tools/mima/core/BufferReader.scala#L41

Is there any activity on this?

@wsargent has a WIP about it, will you have some time to push it over the finish line Will?

@wsargent, I don't think that nextBytes can be the cause here because I've observed this in 0.1.9 and that nextBytes method appears to be unused as of that release.

Also fixed by #129?

yeah, please let us know, y'all, if you ever still see this after upgrading to 0.1.11

optimistically closing, we can reopen if needed

authors: JoshRosen SethTisue dotta dwijnand fthomas ktoso milessabin rossabaker wsargent

repo: typesafehub/migration-manager


text:
Link README to sbt plugin wiki page. Fixes #108

Fixes #108

Quick-fix submitted for early review. Happy to iterate.

Oh, cool :) That's definitely good to link from the readme!

:+1:

authors: dotta dwijnand ktoso


text:
Error NPM Installing when using Docusaurus 2.4.1

Description
The package.json has all docusaurus components hardcoded to 2.4.0, not allowing to upgrade to the recent release of 2.4.1
Steps to reproduce

In any package that uses typesense/docusaurus-theme-search-typesense, upgrade docusaurus to 2.4.1
run npm install or yarn install

Expected Behavior
npm/yarn install works
Actual Behavior
npm/yarn install throws error
example npm error
npm ERR! Found: @docusaurus/core@2.4.1
npm ERR! node_modules/@docusaurus/core
npm ERR!   @docusaurus/core@"2.4.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @docusaurus/core@"2.4.0" from docusaurus-theme-search-typesense@0.11.0

Metadata
Typesense Version: 0.11.0
OS: MacOS 13.3.1

I just published v0.12.0-0. Could you upgrade to this version and let me know if that fixes the issue?

@jasonbosco That solved it, thanks!

Great, thank you for confirming!

authors: jasonbosco nalham


text:
removed objc.setVerbose() call, which I don't think is needed, and is…

… in fact deprecated in recent versions of PyObjC, in favor of objc.options.verbose

Merci!

repo: typesupply/vanilla


text:
typings --version error

/usr/local/lib/node_modules/typings/node_modules/configstore/index.js:54
throw err;
^
Error: ENOTDIR: not a directory, open '/Users/xxx/.config/configstore/typings.json'
at Object.fs.openSync (fs.js:558:18)
at Object.fs.readFileSync (fs.js:468:33)
at Configstore.get (/usr/local/lib/node_modules/typings/node_modules/configstore/index.js:35:26)
at Configstore (/usr/local/lib/node_modules/typings/node_modules/configstore/index.js:28:44)
at Object. (/usr/local/lib/node_modules/typings/node_modules/typings-core/dist/utils/store.js:5:19)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)

Is there something there that's not a directory?

YES,this is nothing in "/Users/xxx/.config"

It looks like a file. It should be a directory.

but i dont konw why this is a file . and does not have sub file

I just use sudo npm install typings --global

It's not related to typings, it appears to be something else you've used that has created this file. I would recommend inspecting it and/or moving it (e.g. mv ~/.config ~/.config.bak).

move this file ,and is no problem ,thanks

authors: blakeembrey lansefengxinzi

repo: typings/typings


text:
Programmatically attaching labels to locatable elements

Description
Currently it is not possible to generatively attach labels to locatable elements like headings and then use those to refer to said elements. It is, however, possible to apply styles to those labels. That means, they are available during application of the style chain but not during introspection.
#show heading: it => {
  let key = lower(it.body.text.replace(" ", "-"))
  [#it #label(key)]
}

= Long Heading with long title
See @long-heading-with-long-title.

This currently errors with: Label <long-heading-with-long-title> does not exist in the document.
Use Case
Auto-generating label names and actually being able to reference them. It's not a big deal to specify label names yourself but it'd be nice to have since it is currently an implementation detail.

More context from Laurenz on Discord:

There is a copy of the heading with the label at one point in time, but it's not the one that ends up available for introspection because that one is collected before the heading show rule runs.

A workaround is possible with an invisible figure until this is resolved. The key generation can be further extended to more content like equations and such.
#let heading-numbering = "1"
#set heading(numbering: heading-numbering)
#show heading: it => {
  let key = lower(it.body.text.replace(" ", "-"))
  return [
    #it
    #v(-1em)
    #figure(
      kind: "heading",
      numbering: (..numbers) => numbering(heading-numbering, ..(counter(heading).get()), ),
      supplement: "Section"
    )[]
    #label(key)
  ]
}

= Test
@test

== Test 2
@test-2

authors: Heinenen quachpas xkevio

repo: typst/typst


text:
Check ill body of contextual element early

When editing the code from #{context text.font} to #{context}, the typst_ide's analyze_expr panics at src/eval/call.rs:286:68.
thread 'analysis::track_values::tests::test_broken_expr' panicked at src/eval/call.rs:286:68:
called `Option::unwrap()` on a `None` value

https://github.com/typst/typst/blob/34f1a232463bafeb3d8d3fa9adeae33c4bb95b23/crates/typst/src/eval/call.rs#L284-L287
I printed the contextual element, and found that it is caused by the body of contextual expression Eof is not an expression.
context closure: Closure { node: Eof: "", defaults: [], captured: Scope {}, num_pos_params: 0 }

It is strange that typst-cli and webapp don't panic with this editing, but I indeed eliminate the panic by checking the legality of the body when constructing the contextual element.

Fixed more generally via https://github.com/typst/typst/pull/4288

authors: Myriad-Dreamin laurmaedje


text:
I like your theme solar

Hello tzvetkov I fall in love with solar theme on hexo it is beautiful, When I saw it on hexo I decided to install nodejs and hexo. I have had that guess when I type something on cmd prompt the documentation on hexo I think is very confused or I don't know if there is something wrong with the system.
Finally, I have cloned it:
git clone themes/ (it has created a folder) and I have followed your instructions (on config.yml I type in anywhere "theme: solar") "hexo generate" and then "hexo server" but it doesn't work.
Could you help me? Do you have experience on hexo?

Hi Karolinehc,
happy to hear that you like the theme. Probably, these are the points that will help

the git clone should be executed under the themes folder. In this folder are the hexo themes, like 'landscape'
the string "theme: solar' must match the name of the folder that you cloned.  If you have used the default name - solar-theme-hexo, than rename the folder to 'solar', with  mv solar-theme-hexo solar
hope this helps

Thank you ;)

I like this theme too~ the solar system is really what I want

thanks @soleverlee

authors: Karolinehc soleverlee tzvetkov75


text:
[Snyk] Upgrade @vitest/coverage-v8 from 0.32.2 to 0.34.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @vitest/coverage-v8 from 0.32.2 to 0.34.3.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 7 versions ahead of your current version.
The recommended version was released 24 days ago, on 2023-08-25.

Release notes

Package name: @vitest/coverage-v8

0.34.3 - 2023-08-25   🚀 Features

coverage: Add allowExternal option  -  by @ vojvodics and @ AriPerkkio in #3894 (c03fa)
vitest: Export all reporters in vitest/reporters  -  by @ Dunqing and @ sheremet-va in #3980 (5704b)

   🐞 Bug Fixes

Should remove mockPath from callstack whether success or failed  -  by @ miserylee and lijifei in #3971 (5eb85)
Add workspace config files to default coverage excludes  -  by @ FelixGraf and @ AriPerkkio in #3973 (20263)
Report file error as a  on JUnit  -  by @ 3c1u in #3997 (00c43)
jsdom: Correctly resolve buffer on typed arrays  -  by @ sheremet-va in #3998 (b42cf)
ui: Use web hash history in ui  -  by @ segevfiner and @ sheremet-va in #3481 and #3487 (8caab)
vite-node: Inline HMR types  -  by @ sheremet-va in #3993 (dff60)
vitest: Correctly resolve optimizer status  -  by @ sheremet-va in #3992 (74dc5)

    View changes on GitHub

0.34.2 - 2023-08-17 Read more

0.34.1 - 2023-08-01   🐞 Bug Fixes

Pass --experimental-vm-worker-memory-limit to tinypool  -  by @ AriPerkkio in #3856 (3c67a)

    View changes on GitHub

0.34.0 - 2023-08-01 Read more

0.33.0 - 2023-07-06   🚨 Breaking Changes

Revert default include patterns  -  by @ so1ve #3729

0.32.0 changed the default include globs to be compatible with Jest. After a discussion with the community, we are reverting this change because it turned out to be non-intuitive.

   🐞 Bug Fixes

Add missing JSDom living keys  -  by @ DerZade in #3702 (83a86)
vite-node:

Don't fail when importing Promise module  -  by @ sheremet-va (08192)
Allow importing node:test  -  by @ sheremet-va (db22c)

    View changes on GitHub

0.32.4 - 2023-07-03   🐞 Bug Fixes

browser: Correctly optimize CJS dependencies  -  by @ sheremet-va (3d090)

    View changes on GitHub

0.32.3 - 2023-07-03 Read more

0.32.2 - 2023-06-16   🐞 Bug Fixes

browser: Don't fail on importing diff-sequences  -  by @ sheremet-va (00b0e)

    View changes on GitHub

    from @vitest/coverage-v8 GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

duplicate #138

repo: u-sho/quantum-game-arena


text:
Tag a new version so that pkg.go.dev works

https://github.com/golang/go/issues/50021

golang/go#50021

tks, done


text:
Лічильник дати реєстрації починає відлік спочатку

Лічильник дати реєстрації починає відлік з 0 після досягнення місяця з дати реєстрації.

@AoHeaven Додав фікс, перевір будь ласка, якшо не праціює перевідкрий:

@AoHeaven Додав фікс, перевір будь ласка, якшо не праціює перевідкрий:

Працює, дякую

authors: AoHeaven jmas

repo: uJournal/ujournal-ui


text:
Create Banda Transportadora Cubos y Cilindros

Banda Transportadora Cubos y Cilindros

https://github.com/uLatinaPma-Mechatronics/Sistemas-flexibles-manufactura/assets/153786722/c90a3eaa-0f45-4123-b476-670bb1a1f13b
Uploading Proyecto.Final.Elsa.Pineda.Orlando.Castro.Jose.Sanchez.zip…


text:
ws->getUserData() is always returning the newest client's data

I can use ws->setUserData() and ws->getUserData() to set and retrieve a clientNumber variable for a single client, however as soon as a second client connects, ws->getUserData() always returns the clientNumber of the second (newest) client, regardless which client the messages are coming from.
I'm getting the exact same error with uWS v0.14.1 and v0.14.0. I'm running Ubuntu 16.04.2 LTS.
Here is a short code segment that I can use to replicate it:
int main(){
	int clientNumber = 0;
	uWS::Hub h;

	h.onConnection([&](uWS::WebSocket<uWS::SERVER> *ws, uWS::HttpRequest req){
		cout << "Setting user data to " << ++clientNumber << endl;
		ws->setUserData((void *) &clientNumber);
	});

	h.onMessage([](uWS::WebSocket<uWS::SERVER> *ws, char *message, size_t length, uWS::OpCode opCode){
		cout << "Input received from client: " << *(int*)ws->getUserData() << endl;
    });

    h.listen(3000);
    h.run();
}

Here is what the output would look like:
Setting user data to 1      <-- Client 1 connects
Input received from client: 1
Input received from client: 1
Input received from client: 1
Setting user data to 2      <-- Client 2 connects
Input received from client: 2
Input received from client: 2
Input received from client: 2
Input received from client: 2      <-- These messages are from Client 1
Input received from client: 2
Input received from client: 2

Even after reading through these two issues: https://github.com/uWebSockets/uWebSockets/issues/521 https://github.com/uWebSockets/uWebSockets/issues/546, I'm still not sure what I'm doing wrong.

You're setting both user data values as pointers to the same integer, which is changing.  =D

Oh, of course. Thanks!

repo: uWebSockets/uWebSockets


text:
🛑 guaca-soc is down

In 08e539d, guaca-soc (https://aules.ccss.uab.cat/guacamole/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: guaca-soc is back up in 5360e8f.

repo: uab-dtic/guacamole-uab-monitoring


text:
Add parent workflow information to WorkflowInfo

The structure returned workflow.GetInfo() should include parent workflow information.
Also we should make sure that any other relevant information (like previous runId) is also available.

https://github.com/uber-go/cadence-client/pull/655

repo: uber-go/cadence-client


text:
Use new resource struct for matching / worker

Use new resource struct for matching initialization logic
Use new resource struct for worker initialization logic
Update worker scanner initialization logic

Coverage increased (+0.7%) to 67.197% when pulling 8b88ba078dc896cadf4d4e86921705618e530579 on dependencies-matching-worker into 9f314d7c479bb6ec11d4197d05490fc5dee426e1 on master.

repo: uber/cadence


text:
Update 12_activity_async_completion.md

Fix returned error to match go client https://github.com/uber-go/cadence-client/blob/master/activity/activity.go#L47

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: claassistantio luizbranco


text:
add pause/resume APIs to publisher and consumer

This patch adds pause/resume APIs to publisher and consumer. When paused, we'll just return an empty list of input/output hosts in the reconfiguration thread.

Coverage increased (+2.1%) to 83.038% when pulling 5fef1a036cf7bb183819ebcfbd802f19f45d293c on pause into ccfe5e5b6acff3ffa7f0482df25a17d9db13d788 on master.

Coverage remained the same at 80.903% when pulling d0fedb320dcee4ee74f429dcb02bbebd68fda718 on pause into ccfe5e5b6acff3ffa7f0482df25a17d9db13d788 on master.

authors: coveralls datoug

repo: uber/cherami-client-go


text:
Hide overlapping icons when zooming out

Hi guys
I was wondering if it was possible to have a big set of icons but when zooming out and they overlap, to just not show the ones that are overlapping.
Like in this demo: http://alex3165.github.io/react-mapbox-gl/demos
thanks!

deck.gl natively doesn't support clustering, but you can check our demo and example code.


text:
JSON converter: No registered class of type Feature

Description
In PyDeck, when initializing a GeoJsonLayer with a features object, we get a warning and no polygons are displayed in the map.
Repro Steps
import pydeck
import requests as req
DATA_URL = "https://raw.githubusercontent.com/uber-common/deck.gl-data/master/examples/geojson/vancouver-blocks.json"
data_geojson = req.get(DATA_URL).json()

INITIAL_VIEW_STATE = pydeck.ViewState(
  latitude=49.254,
  longitude=-123.13,
  zoom=11,
  max_zoom=16,
)

gg = pydeck.Layer(
    'GeoJsonLayer',
    data_geojson,
    stroked=False,
    filled=True,
    extruded=True,
    wireframe=True,
    pickable=True,
    get_line_color=[255, 255, 255]

)

r = pydeck.Deck(
    layers=[gg],
    initial_view_state=INITIAL_VIEW_STATE)

r.to_html()

Thanks for reporting. Fixing this bug that will require changes to how we generate intermediate JSON as described in #3767.
In the meantime, if you don't need to process the GeoJSON in Python, can you just pass the URL to the layer?
gg = pydeck.Layer(
    'GeoJsonLayer',
    DATA_URL,
    ...

This way the GeoJSON won't be part of the JSON sent between Python and the browser but instead loaded directly into the browser without any intermediate processing.
Passing URL would work in the JavaScript API so I assume it should work in pydeck as well... @ajduberstein ?

@ibgreen The problem is that I load the GeoJson from a file, it's not hosted anywhere. Is there another workaround to use files instead of urls?

@pancho111203 In that case I can't think of an easy workaround. The problem that we do special processing on JSON "type": "..." fields and these are also used by GeoJSON, and when your GeoJSON data is "inline" with the JSON we use to describe the layers, everything gets processed the same way.
My current sense is that we should be able to fix this in one of our weekly deck.gl v7.3 patch releases, i.e. you should not have to wait for a new major release to get this fixed.

Thank you for reporting this, @pancho111203. I've written a demo notebook here named after this issue–click deck.gl #3836 Example.ipynb to see the workaround. You can use pandas clean the data and pass the result to a deck.gl PolygonLayer. The code in that notebook:
import pandas as pd
import pydeck

# Load in the JSON data
DATA_URL = 'https://raw.githubusercontent.com/uber-common/deck.gl-data/master/examples/geojson/vancouver-blocks.json'
json = pd.read_json(DATA_URL)
polygon_df = pd.DataFrame()

# Parse the geometry out in Pandas and pass it to deck.gl's PolygonLayer
# I'll make the next release such that you don't have to do this
# manual extraction.
polygon_df['coordinates'] = json['features'].apply(lambda row: row['geometry']['coordinates'])
polygon_df['valuePerSqm'] = json['features'].apply(lambda row: row['properties']['valuePerSqm'])
polygon_df['growth'] = json['features'].apply(lambda row: row['properties']['growth'])
polygon_df.head()

INITIAL_VIEW_STATE = pydeck.ViewState(
    latitude=49.254,
    longitude=-123.13,
    zoom=11,
    max_zoom=16,
    pitch=45,
    bearing=0
)

geojson = pydeck.Layer(
    'PolygonLayer',
    polygon_df,
    opacity=0.8,
    get_polygon='coordinates',
    stroked=False,
    filled=True,
    extruded=True,
    wireframe=True,
    get_elevation='valuePerSqm / 20',
    get_fill_color='[255, 255, growth * 255]',
    get_line_color=[255, 255, 255],
    pickable=True
)

r = pydeck.Deck(
    layers=[geojson],
    initial_view_state=INITIAL_VIEW_STATE)
r.to_html(iframe_width=1000)

Unambiguously we should have support for parsing GeoJSON built into pydeck–expect this in the next release.

Great, I'll use that workaround in the meantime. Thank you both for your help!

This is fixed in pydeck 0.2.0–please update your installation. Feel free to re-open this issue if something doesn't work as expected.

authors: ajduberstein ibgreen pancho111203


text:
Add support for RGB color format

For #3197
There is a small save on resources, but this is most useful when using external buffers.
Change List

Add colorFormat prop
Fix positionFormat support in PolygonLayer
Documentation

Coverage decreased (-0.08%) to 82.113% when pulling 9e68962dbbc7cad588225b6e375e54c754e98859 on x/rgb-color into 6aeb98305cbd9efb7684ba9f6ad32ad4f5117c52 on master.

authors: Pessimistress coveralls


text:
_hex2dToCoordIJK() redundant code or something else

I found the following code  when learning your algorithm.
https://github.com/uber/h3/blob/d610a226df755b0a91d1012cb12496525b1a1926/src/h3lib/lib/coordijk.c#L67-L83
In this way, under any condition, r1==r2==0. Only this code
https://github.com/uber/h3/blob/d610a226df755b0a91d1012cb12496525b1a1926/src/h3lib/lib/coordijk.c#L78-L79
will execute and the following bunch of if statements make no sense, does it? There should be some judgment in previous version according to your comment(line 67 71). Seems that you had modified some code here, I want to know if this execution process can execute the algorithm correctly?

Hi, I believe this code is reachable in at least this case from the test files:
v.x = 17.499999999962203
v.y = -6.0621778265014115

In this case,
a1 = 17.499999999962203
a2 = 6.0621778265014115

x2 = 7.0000000000119407
x1 = 20.999999999968175

m1 = 20
m2 = 7

r1 = 0.99999999996817479
r2 = 0.000000000011940670674448484

I think the thing to note here is that m1 and m2 are integers, so lines 68 and 69 are truncating (rounding), which is why lines 72 and 73 are not necessarily 0. It might be clearer to explicitly cast to int in the code so that's clearer.

Thanks! I failed to notice data type.

authors: isaacbrodsky zhaone


text:
Refactor storage configuration

Fixes #296

Coverage remained the same at 100.0% when pulling 9f6e691dfabb1b186e42aa9db16a98c07996d714 on pavolloffay:refactor-storage into a2ffdac74560526886732234445b1fd19ccee0fd on uber:master.

Coverage remained the same at 100.0% when pulling 9f6e691dfabb1b186e42aa9db16a98c07996d714 on pavolloffay:refactor-storage into a2ffdac74560526886732234445b1fd19ccee0fd on uber:master.

Coverage remained the same at 100.0% when pulling e5a7a835eb6693cd861f614c6af5e817dd9d3417 on pavolloffay:refactor-storage into 7daccda31e93e05d9244ad038e8d0297ddd72cca on uber:master.

PR updated and rebased

Coverage remained the same at 100.0% when pulling 1ed58c52568b6d10ad6f15b0fbe14770d7f21e91 on pavolloffay:refactor-storage into e1d79b8840b91a1974bd2d58a98d4211f90afc28 on uber:master.

Coverage remained the same at 100.0% when pulling c1ed70d21727ca4ef805479c207acfd0447eef38 on pavolloffay:refactor-storage into 43ef964c095bb3c4f08a620f0b5171342be0435a on uber:master.

Coverage remained the same at 100.0% when pulling c1ed70d21727ca4ef805479c207acfd0447eef38 on pavolloffay:refactor-storage into 43ef964c095bb3c4f08a620f0b5171342be0435a on uber:master.

Coverage remained the same at 100.0% when pulling 8466e12efcb84bf45577ce7ad8b23ea094f91f6d on pavolloffay:refactor-storage into 763c96a6663750b70611a239e6da87aa45287406 on uber:master.

PR updated and rebased. Is there anything blocking merge?

authors: coveralls pavolloffay

repo: uber/jaeger


text:
symbol: Account for prelinked shared objects

Some projects, such as those derived from Yocto, tend to prelink their
binaries and libraries to reduce runtime overhead. Currently this trips
up pyflame in its symbol address calculations, and leads to ptrace
failures due to spurious addresses:
$ pyflame -t python -c "print 'foo'"
Unexpected ptrace(2) exception: Failed to PTRACE_PEEKDATA (pid 1482, addr 0x9f9b1d70): Input/output error
Unexpected ptrace(2) exception: Failed to PTRACE_PEEKDATA (pid 1482, addr 0x9f9b1d70): Input/output error
Unexpected ptrace(2) exception: Failed to PTRACE_PEEKDATA (pid 1482, addr 0x9f9b1d70): Input/output error
Unexpected ptrace(2) exception: Failed to PTRACE_PEEKDATA (pid 1482, addr 0x9f9b1d70): Input/output error
Unexpected ptrace(2) exception: Failed to PTRACE_PEEKDATA (pid 1482, addr 0x9f9b1d70): Input/output error
...
Add support for reading a prelinked base p_vaddr out of the ELF and
adjust the PyAddresses values accordingly.
Signed-off-by: Andrew Jeffery andrew@aj.id.au

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm chasing up the CLA with the lawyers, hopefully will be able to sign it soon.

Is there anything I can do to move this along? I've signed the CLA.

authors: CLAassistant amboar

repo: uber/pyflame


text:
EmpiricalMarginal.mean can return nan; make test problem [bug]

I'm starting to use pyro for a (physics) research project and have been testing different posterior inference methods on very simple models. I've found that EmpiricalMarginal.mean returns nan when _log_weights is small. I'm on the dev branch and can provide an example if it would be helpful.
The problem stems from this helper method:
https://github.com/uber/pyro/blob/5643a749b7a7c4a654ae41d7b9212dd67411542f/pyro/distributions/empirical.py#L132-L137
When max_val.exp() is very small, _weighted_mean() returns zero, causing mean() to return a tensor of nans. However, the max_val.exp() factors will always cancel in the numerator and denominator when computing the mean:
https://github.com/uber/pyro/blob/5643a749b7a7c4a654ae41d7b9212dd67411542f/pyro/distributions/empirical.py#L155
The same _weighted_mean() function appears in two other places:
    pyro/examples/rsa/search_inference.py
    pyro/tutorial/source/search_inference.py

It's simple to fix this and I would submit a pull request, but make test is failing on my machine with the following error:
[gw4] [ 74%] FAILED tests/ops/test_stats.py::test_autocorrelation
...
    def autocorrelation(input, dim=0):
        """
        Computes the autocorrelation of samples at dimension `dim`.

        Reference: https://en.wikipedia.org/wiki/Autocorrelation#Efficient_computation

        :param torch.Tensor input: the input tensor.
        :param int dim: the dimension to calculate autocorrelation.
        :returns torch.Tensor: autocorrelation of `input`.
        """
        if (not input.is_cuda) and (not torch.backends.mkl.is_available()):
>           raise NotImplementedError("For CPU tensor, this method is only supported "
                                      "with MKL installed.")
E           NotImplementedError: For CPU tensor, this method is only supported with MKL installed.

I have MKL installed. Here's my environment info:
-OS: macOS Mojave 10.14.1 (18B75)
-python -c 'import torch; print(torch.__version__)' returns 0.4.0
-python -c 'import pyro; print pyro.__version__' returns 0.2.1
Does someone know how to fix this? I'd really like to contribute to pyro, even if it's just a small thing like this!

Nice observation! For mkl, you can just ignore it I guess. You don’t have to redo all the tests. If you want to deal with that issue, I suggest to try calling ‘torch.backends.mkl.is_available()’ to see if you have installed torch with mkl backend or not.

Thanks for reporting - It will be great if you could submit your PR fixing this. Don't worry about this particular test, but it will be nice to add your failing example to test_empirical.py and assert that it passes now..
@fehiepsi - I think we should just skip or xfail if we don't have mkl available, I am not sure how it is passing on travis.

Okay, I see why this wasn't failing on travis. That is using the wheels that I built with MKL and not the default wheels. @fritzo has addressed this issue in #1550.

Closed by https://github.com/uber/pyro/pull/1558

authors: adam-coogan fehiepsi neerajprad

repo: uber/pyro


text:
Rebalance tests to prevent travis timeouts

This is a short term fix to address #612.

It moves a couple of tests to the integration batch 2, that seems to be the furthest from timeout.
It also adds a flag to the pytest runs on travis to output the slowest tests in the unit and integration tests, so that we can remove/refactor them periodically.

Hopefully, PyTorch 0.3 should solve a lot of these pain points, and a slightly longer term plan is to run the integration tests as a cron job instead.

@neerajprad do you have a printout of runtimes? i'd feel pretty comfortable removing a few tests right now, even we'll be rethinking test coverage down the line. e.g.
test_elbo_reparameterized_N_is_17
test_elbo_nonreparameterized_N_is_7
test_elbo_nonreparameterized_three_layers_model_permuted

@martinjankowiak - Here are the tests in the different batches. Let me know what we can skip for now.
unit tests:
343.93s call     tests/infer/test_sampling.py::ImportanceTest::test_importance_guide
326.47s call     tests/infer/test_sampling.py::ImportanceTest::test_importance_prior
227.06s call     tests/infer/test_enum.py::test_gmm_elbo_gradient[flat-sample-single]
222.68s call     tests/infer/test_enum.py::test_gmm_elbo_gradient[dense-sample-single]
197.86s call     tests/infer/test_enum.py::test_gmm_elbo_gradient[dense-sum-single]
136.68s call     tests/infer/test_enum.py::test_gmm_elbo_gradient[flat-sample-batch]
130.76s call     tests/infer/test_inference.py::BernoulliBetaTests::test_elbo_nonreparameterized
129.69s call     tests/infer/test_enum.py::test_gmm_elbo_gradient[dense-sample-batch]
106.04s call     tests/infer/test_inference.py::NormalNormalTests::test_elbo_nonreparameterized
69.55s call     tests/infer/test_inference.py::ExponentialGammaTests::test_elbo_nonreparameterized
42.23s call     tests/infer/test_inference.py::NormalNormalTests::test_elbo_reparameterized
28.79s call     tests/infer/test_gradient.py::test_subsample_gradient[TraceGraph-subsample-reparam]
28.61s call     tests/infer/test_gradient.py::test_subsample_gradient[Trace-subsample-reparam]
27.85s call     tests/infer/test_gradient.py::test_subsample_gradient[TraceGraph-subsample-nonreparam]
27.74s call     tests/infer/test_gradient.py::test_subsample_gradient[TraceGraph-full-reparam]
25.98s call     tests/infer/test_gradient.py::test_subsample_gradient[TraceGraph-full-nonreparam]
25.61s call     tests/infer/test_gradient.py::test_subsample_gradient[Trace-full-reparam]
25.20s call     tests/infer/test_gradient.py::test_subsample_gradient[Trace-subsample-nonreparam]
23.62s call     tests/infer/test_gradient.py::test_subsample_gradient[Trace-full-nonreparam]
17.38s call     tests/infer/test_enum.py::test_bern_elbo_gradient[flat-sample]

Integration batch 1:
547.06s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianPyramidTests::test_elbo_nonreparameterized_three_layers_model_permuted
297.19s call     tests/integration_tests/test_tracegraph_elbo.py::RaoBlackwellizationTests::test_vectorized_map_data_in_elbo_with_superfluous_rvs
285.30s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianChainTests::test_elbo_reparameterized_N_is_17
135.90s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianChainTests::test_elbo_reparameterized_N_is_8
132.97s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianChainTests::test_elbo_nonreparameterized_N_is_7
121.72s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianPyramidTests::test_elbo_nonreparameterized_two_layers
100.59s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianChainTests::test_elbo_nonreparameterized_N_is_5
85.54s call     tests/poutine/test_mapdata.py::test_elbo_mapdata[list-8]
82.99s call     tests/poutine/test_mapdata.py::test_elbo_mapdata[list-None]
77.35s call     tests/poutine/test_mapdata.py::test_elbo_mapdata[list-7]

Integration batch 2:
688.65s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianPyramidTests::test_elbo_nonreparameterized_three_layers
428.70s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianPyramidTests::test_elbo_reparameterized_three_layers
271.85s call     tests/infer/test_inference.py::PoissonGammaTests::test_elbo_nonreparameterized
198.78s call     tests/integration_tests/test_tracegraph_elbo.py::NormalNormalNormalTests::test_elbo_nonreparameterized_both_baselines
194.54s call     tests/integration_tests/test_conjugate_gaussian_models.py::GaussianPyramidTests::test_elbo_nonreparameterized_two_layers_model_permuted
179.27s call     tests/integration_tests/test_tracegraph_elbo.py::NormalNormalNormalTests::test_elbo_nonreparameterized_nn_baseline
149.32s call     tests/integration_tests/test_tracegraph_elbo.py::NormalNormalNormalTests::test_elbo_nonreparameterized_decaying_baseline
97.52s call     tests/infer/test_inference.py::LogNormalNormalTests::test_elbo_with_transformed_distribution
89.76s call     tests/infer/test_inference.py::LogNormalNormalTests::test_elbo_nonreparameterized
84.58s call     tests/infer/test_inference.py::LogNormalNormalTests::test_elbo_reparameterized

@martinjankowiak - Made a change to skip the 3 tests you mentioned, should get us back 10 mins! :)

authors: martinjankowiak neerajprad


text:
Module loggers w/ individually configurable levels

Some apps like to log. Some apps don't. Some logs are nice to have for debugging. Some logs aren't. Module loggers allow different Ringpop components/modules to have individually configurable logging levels which are settable in the Ringpop constructor or over the /admin/config/set endpoints.
reviewers: @thanodnl @benfleis
cc: @uber/ringpop

added a couple thoughts, trlgtm.

authors: benfleis jwolski

repo: uber/ringpop-node


text:
Adding workqueue disabling if user is on SSD

This is a pretty easy fix, but currently only if you have one SSD partition, so the command will be more complex in the end:
lsblk -d -o name,rota | grep -E '^nvme|^sd' | awk '{print $1}' | head -n 1 && printf 'discard,no-read-workqueue,no-write-workqueue' | sudo tee -a /etc/crypttab && notify-send -a "optimizer" "Encrypted SSD performance optimized"

This command detects if you have any SSD, and just adds the parameters to the last line of the crypttab file.
Problems:

only working if one SSD works
encrypted SSD + encrypted HDD not working

Something building on top of that will be helpful for performance.

I feel like this is out of scope for ublue, if this really gives a significant performance boost you should go to upstream Fedora and try to push it there.

authors: ArtikusHG trytomakeyouprivate

repo: ublue-os/config


text:
feat: display warning about mismatch in configured vs login shells

if .fleek.yml contains a shell: line that doesn't match the user's login shell, display a warning at the end of a fleek command run.

fixes #63

repo: ublue-os/fleek


text:
feat: Add brazilian portuguese locale support

This PR creates an initial implementation of the PT_BR locale translation, sadly some options could not be translated, such as --version and --help, as specified by #72

Wow thank you!

authors: bketelsen tulilirockz


text:
shotwell to follow guidelines

This change is

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

authors: dholbach didrocks

repo: ubuntu/snappy-playpen


text:
Generate MathML and improve LaTeX output

There are lots of spurious spaces in generated LaTeX expressions (especially after fractions) and occasionally some missing, like after minus signs.
Would also be good if the syntax tree could output MathML too, to be put onto the scope; but if possible not sent back to the server as it used to be (it's not needed, and really long inside the stored JSON!)

I'm removing spaces, but can you make tests for these?

repo: ucam-cl-dtg/isaac-app


text:
Implement mobile break points

Add correct breakpoints and adjusted padding for mobile. Sub #47

Style Adjustments

Search box is breaking mobile viewport on homepage
Top sections of the individual people/subject/work info pages + search results page should be full width when the viewport is < max width of content area.
Not mobile-specific (and maybe this should be split into its own issue?) but the text on search results pages seems more spread out than elsewhere in site. Wondering if line-height is different/messed up somehow?

Search Results
People/Subject/Work Info Pages

Is this possible?
Is it possible control icon alignment based on either # of text lines or content height?
Because item icons looks kind of weird when center-aligned on items with lots of text and is then better when top-aligned, but when there's not a lot of text, it looks super weird if it's not centered. Essentially I am asking:

If not, we can leave as is. Centered icons on lots of text is less visually offensive to me than when the icon is top-aligned to minimal text in this context.

Style Adjustments

Search box is breaking mobile viewport on homepage
Top sections of the individual people/subject/work info pages + search results page should be full width when the viewport is < max width of content area.
Not mobile-specific (and maybe this should be split into its own issue?) but the text on search results pages seems more spread out than elsewhere in site. Wondering if line-height is different/messed up somehow?

Search Results
People/Subject/Work Info Pages

Is this possible?
Is it possible control icon alignment based on either # of text lines or content height?
Because item icons looks kind of weird when center-aligned on items with lots of text and is then better when top-aligned, but when there's not a lot of text, it looks super weird if it's not centered. Essentially I am asking:

If not, we can leave as is. Centered icons on lots of text is less visually offensive to me than when the icon is top-aligned to minimal text in this context.

@wrenaria whats the px threshold for making the top section 100% viewport width? 480px?

@wrenaria whats the px threshold for making the top section 100% viewport width? 480px?

@wrenaria after re-reading your comments, i see max-content width should be the threshold. so 970px?

@wrenaria after re-reading your comments, i see max-content width should be the threshold. so 970px?

@spelkey-ucd Correct.

@spelkey-ucd Correct.

@wrenaria adjustments made.
Re, line height. it was set to 1.625 of the default text pixel size (16). So anything with 14px font seemed wider. I changed the base rule to be just plain 1.625. Soooo some other line heights might look a little different. let me know if further adjustments are needed.

@wrenaria adjustments made.
Re, line height. it was set to 1.625 of the default text pixel size (16). So anything with 14px font seemed wider. I changed the base rule to be just plain 1.625. Soooo some other line heights might look a little different. let me know if further adjustments are needed.

@spelkey-ucd OH MY GOD the line-height and icon changes made such a huge difference. Looks great!
Looks like one change is missing: The search results top section should be full width sub-970px. I'm still seeing margins there.

@spelkey-ucd OH MY GOD the line-height and icon changes made such a huge difference. Looks great!
Looks like one change is missing: The search results top section should be full width sub-970px. I'm still seeing margins there.

ahh yes forgot about search

ahh yes forgot about search

authors: jrmerz spelkey-ucd wrenaria

repo: ucd-library/rp-ucd-client


text:
Created API Endpoints to GET List of Users from User Group and vice versa

In this PR, we created an endpoint that will GET all of the groups that a given user is in. In addition, another endpoint was created that can GET all of the members of a given group. These endpoints will only support GET requests. They are clearly important, as an API user may want to get information relating Users to Groups
We support a GET request to the endpoint: /api/users/<user_id>/groups to get the groups from a given user. This endpoint allows us to specify the user through the user_id, and then we can look up the groups of this user.
We also support a GET request to the endpoint: /api/groups/<group_id>/members to get all the users/members of a given group. This endpoint allows us to specify the group through the group_id, and then we can look up the members of the group.

Slug functionality for users/<username_slug>/groups implemented. Also refactored the slug checking/lookup into a separate helper function called get_user

Closing Comment:
In this PR, we implemented the endpoint /api/users/<slug>/groups, which supports GET requests and returns back all of the groups that the user corresponding with the given slug is a part of. The slug can either be the user_id or the username of the User. We also implemented the endpoint /api/groups/<group_id>/members in order to get all the User objects that are a part of a certain Group, specified by the group_id

Issue Score: Excellent
Comments:
Nice work! Good closing comment.

authors: abrahmasandra majorsylvie

repo: uchicago-cs/chigame


text:
We need documentation

If this going to be open-source and targeting a broad audience I think we need good, clear documentation. We can use SphinX to generate it automatically from the Docstrings but we need to Docstring every function and class in a consistent format to do that.

Got a first draft going. It automatically builds from the gh-pages branch at each new push.
It is "functional" but super ugly and the images are not displaying.
The intro page definitely needs some padding out and improving.
I think eventually we also need to include an example section in here with an integrated Jupyter Notebook- that way we have all the examples/docs etc in one same place- this will also avoid users having to download an additional notebook as well as the package itself...

repo: ucl-sgnl/FSPSimulator


text:
Persistent bug with csvtools.missingKeywords()

csvtools.missingKeywords() sometimes reports some missing keywords that definitely should be in the attribute dictionary. The behavior is erratic, and I haven't been able to trace down the cause. The misssing keywords generally seem to be ['motion_controller', 'motion_receptacle'].
An example error:
Processing run: 23 Processing probe: ('tdiode', 'tdiode') Running lapdToRaw Traceback (most recent call last):   File "/Users/dereks/Desktop/Research/Codes/Data/LAPD/Python/make_LAPD_Jan2019.py", line 75, in <module>     rawfile =  lapdtools.lapdToRaw(run, probe[0], hdf_dir, csv_dir, rawfile, verbose=True)   File "/Users/dereks/Documents/GitHub/uclahedp/uclahedp/lapdtools.py", line 65, in lapdToRaw     csvtools.missingKeys(attrs, req_keys, fatal_error=True)   File "/Users/dereks/Documents/GitHub/uclahedp/uclahedp/csvtools.py", line 391, in missingKeys     raise ValueError("Missing columns in metadata attributes! The following keys were not found, and are required: " + str(missing_keys)) ValueError: Missing columns in metadata attributes! The following keys were not found, and are required: ['motion_controller', 'motion_receptacle']

This issue seems to have been solved, or otherwise disappeared? Closing for now, unless it comes up again.

repo: uclahedp/uclahedp


text:
[bug] content_harvest image size error

[ ] Log for 27297 mapped task 3 (legacy mapper: csa-omeka) - permanent link to create_stage_index

Run ID: manual__2024-03-14T00:54:58+00:00
PIL.Image.DecompressionBombError: Image size (219775150 pixels) exceeds limit of 178956970 pixels, could be decompression bomb DOS attack.

Perhaps take a look at error handling to try to get an item ID.

Skimming through the isShownBy URLs/file types for collection 27297 to see if there were any TIFFs -- it looks like they are all JPEGs (could be a supersize one in there, though):

This object with title eichler_f3274_115_001 in collection 27297 has a 19.9MB thumbnail:
https://calisphere.org/item/c4b3852afa1319f81453e8709e8549cf/
The thumbnail server throws a 500 error when trying to serve up the image:
https://calisphere.org/crop/210x210/31f86e330cca408122a535b8d9afd23e
I'm guessing it's the same PIL.Image.DecompressionBombError we're getting from PIL in the content harvester.
Here's the legacy thumbnail that we harvested to S3:
https://static-ucldc-cdlib-org.s3.us-west-2.amazonaws.com/harvested_images/31f86e330cca408122a535b8d9afd23e

For this particular image:

download this file
resize the image
upload to s3

Options to explore post-mvp:

temporarily increase the image size limit (would result in a CSphere record with a broken thumbnail image)
during content_harvesting to resize the image (should fix the thumbnail)
let the image pass as a non-blocking error (likely would still index the record)

Thanks @barbarahui! This looks great!! Also ran this collection through to ETL, and it all looks great!
https://calisphere-stage.cdlib.org/item/c4b3852afa1319f81453e8709e8549cf/

authors: aturner barbarahui christinklez

repo: ucldc/rikolti


text:
Add a parameter to adjust number of decimals for other referentials

Actually, only UD referential have a parameter to adjust decimals numbers. It could be great to add this for other referentials.

The decimals are already applied to all referentials. But it makes no sense in the quantitative view because ther are only integers.

I have a doubt about the fact that decimals are already applied to all referentials. Decimals makes sense in quantitative view with scientific display. For instance, 1.78987 TMB –> 1.78 TMB.
By the way, I can't open preference window, it crash:
  File "/home/moul/Documents/cutecoin/build/src/cutecoin/gui/mainwindow.py", line 194, in open_preferences_dialog
    dialog = PreferencesDialog(self.app)
  File "/home/moul/Documents/cutecoin/build/src/cutecoin/gui/preferences.py", line 60, in __init__
    self.combox_proxytype.setCurrentText(self.app.preferences.get('proxy_type', "HTTP"))
AttributeError: 'PreferencesDialog' object has no attribute 'combox_proxytype'
Traceback (most recent call last):
  File "/home/moul/Documents/cutecoin/build/src/cutecoin/gui/mainwindow.py", line 194, in open_preferences_dialog
    dialog = PreferencesDialog(self.app)
  File "/home/moul/Documents/cutecoin/build/src/cutecoin/gui/preferences.py", line 60, in __init__
    self.combox_proxytype.setCurrentText(self.app.preferences.get('proxy_type', "HTTP"))
AttributeError: 'PreferencesDialog' object has no attribute 'combox_proxytype'

Should be fixed !

Thanks :dart:

repo: ucoin-io/cutecoin


text:
mmSpoof changes: added ---- ending line

added ---- ending line

Check rendering

check rendering


text:
Results on the other MOT datasets like MOT15, MOT17 etc?

Thank you for the nice work.
Have you computed the results using your pipeline on the other Multiple Object Tracking datasets like MOT15, MOT17 etc?

Thank you for your interest.
Our approach combines a universal detector (PP-YOLOE) and a tracker (ByteTrack) to complete the challenge. Moreover, these two components have been published. For specific information on tracking performance, please refer to ByteTrack, a concise and effective method.
It is worth noting that the specific implementation varies in terms of framework and parameter details.

repo: ucsk/ppbytetrack


text:
gcc>=4.5 not 5.4

gcc>=4.5 not 5.4 as given as a pre-requisite in README.md

GCC 5.4 was released June 2016. My mistake to think we should use 4.5.


text:
数据可视化简介 > 数据面板简介

课程导航+地址
数据可视化简介 > 数据面板简介
截图

具体描述
这里的视屏链接是 Youtube 的，需墙外才行。

替换为vimeo链接~

authors: Kyliewang PoBlue

repo: udacity/band-issues-cn