ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
columbarius has joined #dri-devel
co1umbarius has quit [Ping timeout: 480 seconds]
luc4 has quit []
jljusten has quit [Ping timeout: 480 seconds]
cef has quit [Quit: Zoom!]
cef has joined #dri-devel
pendingchaos_ has joined #dri-devel
pendingchaos has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
cef has quit [Quit: Zoom!]
cef has joined #dri-devel
oneforall2 has quit [Remote host closed the connection]
oneforall2 has joined #dri-devel
pixelcluster has quit [Ping timeout: 480 seconds]
pixelcluster has joined #dri-devel
kts has joined #dri-devel
camus has joined #dri-devel
<ishitatsuyuki>
what do you use to review large MRs? GitLab Web UI perf wreaks havoc even with just 2k lines of additions, the VSCode extension doesn't allow you to review commit-by-commit nor submit comments in batch, so I'm seriously struggling with the tooling here...
alanc has quit [Remote host closed the connection]
<Frogging101>
There's a setting in your gitlab account to view diffs one file at a time. I don't know if that will help you
alanc has joined #dri-devel
<Frogging101>
Other than that, maybe you just have to fetch the branch and look at diffs locally
<Frogging101>
I think the one file at a time setting should be the default. I don't like how it puts all the files on one page
<ishitatsuyuki>
sad noise
<Frogging101>
maybe someone else who actually does review large MRs has a better answer though :)
<Frogging101>
I've printed out diffs on paper and used a highlighter before, lol
nirya has quit []
Lyude has quit [Remote host closed the connection]
Lyude has joined #dri-devel
rcf has quit [Quit: WeeChat 3.4.1]
rcf has joined #dri-devel
rcf has quit [Quit: WeeChat 3.4.1]
rcf has joined #dri-devel
ella-0 has joined #dri-devel
ella-0_ has quit [Read error: Connection reset by peer]
i-garrison has quit [Read error: Connection reset by peer]
garrison has quit []
i-garrison has joined #dri-devel
Duke`` has joined #dri-devel
Jeremy_Rand_Talos_ has quit [Remote host closed the connection]
Jeremy_Rand_Talos_ has joined #dri-devel
srslypascal has quit [Ping timeout: 480 seconds]
genpaku has quit [Remote host closed the connection]
genpaku has joined #dri-devel
soreau has quit [Read error: Connection reset by peer]
soreau has joined #dri-devel
lemonzest has joined #dri-devel
thellstrom has joined #dri-devel
sdutt has quit [Read error: Connection reset by peer]
oneforall2 has quit [Remote host closed the connection]
oneforall2 has joined #dri-devel
thellstrom has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #dri-devel
danvet has joined #dri-devel
jljusten has joined #dri-devel
srslypascal has joined #dri-devel
CME has quit [Ping timeout: 480 seconds]
rasterman has joined #dri-devel
CME has joined #dri-devel
lemonzest has quit [Quit: WeeChat 3.5]
gouchi has joined #dri-devel
zf` has joined #dri-devel
zf`_ has quit [Ping timeout: 480 seconds]
gouchi has quit [Quit: Quitte]
luc4 has joined #dri-devel
Haaninjo has joined #dri-devel
ine-one1 has joined #dri-devel
ine-one1 has quit [Excess Flood]
ine-one1 has joined #dri-devel
ine-one1 has quit [Excess Flood]
ine-one1 has joined #dri-devel
ine-one1 has quit [Ping timeout: 480 seconds]
pochu has quit [Quit: leaving]
OftenTimeConsuming has quit [Remote host closed the connection]
OftenTimeConsuming has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
gio has joined #dri-devel
sul has joined #dri-devel
luc4 has quit []
devilhorns has joined #dri-devel
dv_ has quit [Quit: WeeChat 2.8]
Lucretia has quit [Remote host closed the connection]
ptrc has quit [Remote host closed the connection]
ptrc has joined #dri-devel
Lucretia has joined #dri-devel
kts_ has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
camus has quit [Remote host closed the connection]
camus has joined #dri-devel
lygstate_ has joined #dri-devel
lygstate has quit [Read error: Connection reset by peer]
Lucretia has quit [Read error: Connection reset by peer]
Lucretia has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
sdutt has joined #dri-devel
kts has joined #dri-devel
devilhorns has quit []
lina_ has joined #dri-devel
lina has quit [Ping timeout: 480 seconds]
Lucretia has quit []
Lucretia has joined #dri-devel
lygstate has joined #dri-devel
heat_ has joined #dri-devel
lygstate_ has quit [Ping timeout: 480 seconds]
lygstate_ has joined #dri-devel
lygstate has quit [Read error: Connection reset by peer]
sul has quit [Ping timeout: 480 seconds]
sul has joined #dri-devel
lygstate has joined #dri-devel
lygstate_ has quit [Read error: Connection reset by peer]
lygstate_ has joined #dri-devel
lygstate has quit [Read error: Connection reset by peer]
srslypascal is now known as Guest737
srslypascal has joined #dri-devel
Guest737 has quit [Ping timeout: 480 seconds]
Duke`` has quit []
Duke`` has joined #dri-devel
<KunalAgarwal[m]>
what can be probable reasons for gl error 1282 :(
<karolherbst>
KunalAgarwal[m]: depends on the API
<karolherbst>
1282 is a bit too generic to even make guesses
sul has quit [Ping timeout: 480 seconds]
<KunalAgarwal[m]>
using GLES
<karolherbst>
yeah.. I meant which API call
<karolherbst>
the docs usually describe which error code is returned and why
<karolherbst>
but with mesa you can also get more debug logging somehow. Debug context would do that automatically.
<karolherbst>
MESA_DEBUG=context if you don't want to change the code
<KunalAgarwal[m]>
probably its after glGetProgramiv() which I use to get the Link status.. But GL_LINK_STATUS returns true. so I am confused what can the error be
<karolherbst>
creating a debug context should help you out with this
<KunalAgarwal[m]>
sure thanks
sul has joined #dri-devel
heat has joined #dri-devel
heat_ has quit [Read error: Connection reset by peer]
<kchibisov>
KunalAgarwal[m] are you mixing RGB and RGBA textures?
<kchibisov>
Since you can do that with OpenGL 2.1, but not GLES for example, unless you bind OpenGL api.
<kchibisov>
But in geneneral docs.gl could give you a hint on that if you know a call that fails.
<kchibisov>
It's pretty verbose on what could cause a particular error. MESA_DEBUG=1 could show it as well.