4.1 doesn't work in IE 11

https://storybooks-official.netlify.com shows a blank page in IE 11, without console error:
Expected ')'

And https://storybooks-official.netlify.com/iframe.html shows red box with the following error:

Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object with keys {%24%24typeof%2C type%2C key%2C ref%2C props%2C _owner}&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Yo-ho-ho!! I just released https://github.com/storybooks/storybook/releases/tag/v4.2.0-alpha.7 containing PR #5082 that references this issue. Upgrade today to try it out!
Because it's a pre-release you can find it on the @next NPM tag.
Closing this issue. Please re-open if you think there's still more to do.

Huzzah!! I just released https://github.com/storybooks/storybook/releases/tag/v4.1.4 containing PR #5082 that references this issue. Upgrade today to try it out!

Related to this - #4099, right ?

Ooh-la-la!! I just released https://github.com/storybooks/storybook/releases/tag/v4.2.0-alpha.9 containing PR #5081 that references this issue. Upgrade today to try it out!
Because it's a pre-release you can find it on the @next NPM tag.
Closing this issue. Please re-open if you think there's still more to do.


Default behaviour when the path parameters is not provided

First of all, I want to thank you guys for this piece of code. I was looking for something to bind functions to HTTP methods when using AWS lambdas and was about to write it myself, but lambdarest came to the rescue.
However, I'm experiencing issues with how the binding behaves when you don't provide the path parameters. The way I see it, the behavior should be to match any path, not "/". This would allow matching on event with path parameters(eg: "/your/object/{id}"). Correct me if I'm wrong, but currently, it is impossible to match path with path parameters, because the path will be different on each event.
To support my use case, I wrote a decorator to hijack the event and set its path to "/" before calling the handler on it.
I already have an idea of how to implement this, I could submit a pull request if you think that this behavior is a good idea.
Just some thought, keep up the great work!

Hi @simongarner. Thanks for engaging in the development.
As i understand it you are talking about two things:

Default behaviour with no path:
I agree that no path specified should match all

The addition of path params:
Is definetly a good idea but as the current handler lookup is using the path as key it would not work out of the box.
A solution could be to make the lookup handler a deep dict with defaultdicts as wildcards and then split path on slashes to keys to make a nested lookup for the handler.
Anyway from top of my head there is no simple solution for path vars atm but we could come up with it together 😊

Lets start with 1 and then colab on design of 2

johannes

Hey @sloev,
I'm gonna hit you with a PR later today!
Just to be clear, you'll still be able to specify "/" if you want to match exactly "/", but if you pass an empty string in the path parameter, any path is going to match. I will keep the default value to "/", to avoid breaking anybody's project.
Simon

Hi Simon thanks for the pr. Ive got a request for deleting a print statement and then we can merge. Lets open issue 2 in a seperate issue and close this one on merge

merged


Video Component Styling fix

What are the relevant tickets?
Closes https://github.com/mitodl/hq/issues/2305
Description (What does it do?)
Fixes sizing and spacing issues on the video component, stopping it from resizing the page
Screenshots (if appropriate):
Before:

After:

How can this be tested?
Load up, set up the video component in the CMS (/cms) if you have not already done so, and test the view on multiple widths.There IS a small shift on VERY small screens from the featured component which will be fixed in the next PR of changes.
Additional Context
Figma

Note - the red dashed lines are to show the confines of the text areas - those are not present on the page.

Thanks for the screenshots. LGTM.

Addressed the last 3 @collinpreston


Retry on connection issues doesn't seem to do anything (except print reconnect message)

It claims to be retrying but doesn't seem to do anything.
Slack was down today for a short period and after it came back up wee_slack claimed to be trying to reconnect but only after reloading the script it reconnected.
This happened on two different clients with a 30 minute period between reloading the script so fairly sure it is bugged.

Exerpienced the same thing

Yes, definitely something wrong here, I experience the same every time my computer wakes up from sleep


node-fetch v3.3.1 Could not load stream-browserify/web: ENOENT: no such file or directory

Reproduction
Steps to reproduce the behavior:
You can reproduce with this repo: https://github.com/helbing/node-fetch-issue-1724
Expected behavior
I use node-fetch@2 can build success, but not working in node-fetch@3, I expect it can work.

Screenshots

Your Environment

software
version

node-fetch
v3.3.1

node
v18.15.0

npm
v9.5.0

Operating System
macOS 13.2.1 (22D68)

Additional context

are you trying to browserify node-fetch?
node fetch is built for NodeJS
just use global fetch instead.

are you trying to browserify node-fetch?
node fetch is built for NodeJS just use global fetch instead.

It's work for an SSR service. It can build success with node-fetch@2 but will report an error with node-fetch@3. You can reproduce this with this repo: https://github.com/helbing/node-fetch-issue-1724

Any luck resolving this issue?

Anyone ever figure this out? I'm seeing the same error though coming from a different library. Wondering if there's a solution for both.


[Docs] Add manual testing instructions in DG

Fixes #165
Added tests except for reminders

Codecov Report
Base: 76.67% // Head: 76.67% // No change to project coverage :thumbsup:

Coverage data is based on head (06214cb) compared to base (fea48bc).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #184   +/-   ##
=========================================
  Coverage     76.67%   76.67%
  Complexity      790      790
=========================================
  Files           108      108
  Lines          2225     2225
  Branches        259      259
=========================================
  Hits           1706     1706
  Misses          423      423
  Partials         96       96

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

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


please add haproxy monitoring to telegraf plugin

Hi,
I'd like to use the telegraf, once I get it configured. I also run HAProxy on my OPNSense. It would be really nice to get the graffic stats exported from that one too into influxdb, and show it in my grafana instance.
So if possible, here would be the config for that to include into OPNSense Telegraf plugin:
https://github.com/influxdata/telegraf/tree/master/plugins/inputs/haproxy
I am glad to test it to get it developed.

FYI, I added it manually to telegraf.conf, and it works perfectly. This is all it takes:
[[inputs.haproxy]]
  servers = ["socket:/var/run/haproxy.socket"]

Having enable selection box in telegraf input conf for adding those lines would be great.

@fraenki will there only be one socket or are there some circumstances where multiple sockets exists?

@mimugmail Yes, only one socket and the plugin does not allow changing it's path, so you're safe assuming it is available from socket:/var/run/haproxy.socket. :)

Can we close this? It's already included

Thanks for adding this! Looking forward to try it, once it becomes available in released version.


Sentry support

Documentation
What is missing:

[ ] Do not initialize sentry if SENTRY_DSN is not specified
[ ] Review Environment struct

I'll close this as this was added on PR #37.


To Do List: Add and Remove Functionality Completed

The add and remove functionality has been added to the to-do-list project.

Work was implemented on tdl-add-remove branch;
All hardcoded items in the array removed and a new JS file was created.
Add, Delete and Editing functions on task descriptions were implemented.
New tasks completed property set to false and index set to value of new array length.
Deleting a task updates array index to original
All changes to the To Do List are be saved in local storage.

Linters were checked and passed.

Okay. Thanks for the reminder.


Further stac conversion improvements, tighten public api

Expansion of the stac converter so it can be used from other projects.

Use the stac created field instead of ODC's field name.

Include dataset label as a 'title' property (perhaps there's a better option?)

Separate the LS8 instruments, following the spec example

Fall-back to WKT2 when dataset crs is not an epsg code.

Allow custom URLs, location to be used for the output paths.

Make all functions private except the main ones. Keep the public api small.

Add a link to the parent stac collection in Explorer

Coverage decreased (-0.2%) to 86.732% when pulling 37606e150ff2da485683e7a54b0ca460829040df on jeremyh:stac-api into fab96dfc51e2755e46160fd5ce3a2e8a44d00a90 on GeoscienceAustralia:eodatasets3.

Does changes in created field and instruments values will required updating existing STAC doc and metadata indexed in ODC DB, any thoughts?

I assume this shouldn't affect ODC-indexed datasets, as the original eo3 doc is unchanged. I don't know enough about our current use of stac outputs to know if the other change matters. Will it break anything that you know?
That seems to be the common way they're represented in the stac samples I've seen, and how the instruments field is represented on Explorer's current stac output.

Does changes in created field and instruments values will required updating existing STAC doc and metadata indexed in ODC DB, any thoughts?

I assume this shouldn't affect ODC-indexed datasets, as the original eo3 doc is unchanged. I don't know enough about our current use of stac outputs to know if the other change matters. Will it break anything that you know?
That seems to be the common way they're represented in the stac samples I've seen, and how the instruments field is represented on Explorer's current stac output.

Before indexing, we do STAC to DC metadata transform. So, we will need to update transform code for changes in created field and instruments values (https://github.com/opendatacube/odc-tools/blob/develop/libs/index/odc/index/stac.py)

I think we should consider moving this tool out of EO Datasets and into the odc-tools repo here: https://github.com/opendatacube/odc-tools/blob/develop/libs/index/odc/index/stac.py
Then it can sit next to the STAC to ODC conversion script linked above.

I think we should consider moving this tool out of EO Datasets and into the odc-tools repo here: https://github.com/opendatacube/odc-tools/blob/develop/libs/index/odc/index/stac.py
Then it can sit next to the STAC to ODC conversion script linked above.

We might need a wider discussion around how we're handling libraries. eo-datasets is basically all metadata handling/validation/conversion, so if this should be moved maybe all of it should? But ODC-Tools is advertising itself as experimental code and everything we have that uses eo-datasets wants extreme stability (no accidental metadata or output changes for products1). The ODC-Tools repo doesn't run its tests or have docs setup, or versioning, and isn't installable from normal pypi like eodatasets, so I'm hesitant to rely on it from other repos at the moment... (should I be?)2
This PR is exposing functions for use by Explorer's stac 1.0.0 support (and fixing the validation failures), so it's going to depend on its stability quite heavily too.
1 eo-datasets came about years ago from frustration with our metadata code, as they were diffuse and inconsistent, and slight mistakes were accidentally introduced multiple times without people noticing for months on produced products. Its tests+versioning are important.
2 I'm completely biased of course, but short-term I'd rather move stac-to-eo3 here rather than the other way around if we want them side-by-side as we have all the infrastructure set up here (and other projects already depend on eodatasets through pypi). Or else move both scripts to odc-core, but that would slow down the release cycle (?). This is the only blocker on Explorer's stac 1.0 PR  so I'm excited by any solutions that are easy :slightly_smiling_face:

Added a shim dc_to_stac function in the old place to maintain backwards compatibility.
I've also moved the API to eodataset3.stac, as the eodatasets3.script directory is more for CLI-scripts, not APIs.
So it's now eodatasets3.stac.to_stac_item()
Added docstrings etc too, and have tried to rename the parameters to be more understandable.

Added a verbose option to eo3-to-stac, so people can tell what it's doing.
Made schema downloads more robust

Use one session for all downloads
Use a timeout
Keep cached items much longer when they're stable Stac versions.
Allow skipping of the cache
Allow no-network-access usage


Slime slabs not working properly

The slime slabs do not have those piston sticky properties unlike normal slime blocks. They do not connect blocks and function like regular slabs. Tested in 1.20.1 fabric.

A log if the given minecraft instance would be great and any modpack to such was used for this.

Should be fixed in the latest release


get current session

I'm using FreeBSD 12.2 & macOS 11.2, both w/ fish shell.
I would like to know the current session's name and socket.
I found issue https://github.com/martanne/abduco/issues/33 but I don't have these env variables on either system.

Are you sure that you are using the latest version? The relevant code is present in current git HEAD.

According to man abduco , both systems have 0.6
I'm sorry, I guess I missed the fact that there hasn't been a release since then.
Is there any plan on when a new release will come out?
FreeBSD ports seem to rely on that…


🍒 Cherry pick PR #13284 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/13284 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.2.36-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @francoisl in version: 1.2.36-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 1.3.28-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


crictl images not response for a long time when crictl pull another image

Description
crictl images not response for a long time when crictl pull another image. There might have been a deadlock.
Steps to reproduce the issue
First: pull a image, such as ubuntu
crictl pull ubuntu

Second: exec command in another terminal
crictl -D images

Describe the results you received
crictl images not response for a long time
Additional information
Output of crio --version:
crio version 1.9.0-dev
commit: "5367b83ad8a85de2da79072d54f11f3996dd671f-dirty"

@nalind PTAL

I suspect this is the lock on the store which pervents listing when pulling (and probably vice-versa as well)

crictl images not response for a long time

can you make sure it does response just after the pull finishes @willstudy ?

can you make sure it does response just after the pull finishes @willstudy ?

@runcom  Yes, it is.

We're currently taking and holding a lock in github.com/containers/image/storage/storageImageDestination.PutBlob() while it applies the contents of a layer blob to create a layer in storage.  Because that method's applying the layer blob as it's read from the network, that lock will be held for a longer time if downloading the layer blob takes longer than it would take to read the layer blob from a file on disk.
We'll be switching to having PutBlob() save the downloaded layer blob as a file to disk (which should not require/acquire a lock) and having all of the image's layer blobs applied in the object's Commit() method (as part of https://github.com/containers/image/pull/305), so cases where that's a limiting factor should be faster after it's merged.

We switched to buffering layers to disk before applying them in #305, so the PutBlob() operation should be bound mainly by local CPU and disk in 1.9.3 and later.


It won't highlight on QtWebkit

Describe the issue
QtWebkit engine (e.g. wkhtmltopdf) is not highlighted in the browser.
(The environment is Windows 10 Pro)
This may not be a bug in highlight.js, but in the QtWebkit engine.
Sample Code to Reproduce
wkhtmltoimage https://highlightjs.org test.png
wkhtmltopdf https://highlightjs.org test.pdf

Additional context

The same thing happened with the other QtWebkit browsers, Midori (v0.5.11).

What version of Javascript does QtWebkit support?  Does it include all the new ES6 stuff and ES2018 stuff that's in most modern browsers?

% wkhtmltoimage  --debug-javascript  https://highlightjs.org test.png                                           2.7.1
Loading page (1/2)
Warning: https://highlightjs.org/static/highlight.site.pack.js:6 SyntaxError: Parse error
Warning: https://highlightjs.org/:10 SyntaxError: Parse error
Rendering (2/2)
Done

Likely that QtWebkit doesn't support all features of modern Javascript that most browsers do these days.  If someone wanted to build a better test case (without a packed lib) and get a line number that would tell us exactly what.

Thanks for the reply.
The Qt engine in wkhtmltopdf seems to use 4.8.
One possible factor is that the Qt engine is an older version and may not be able to support it.
If you look at https://en.wikipedia.org/wiki/Qt_version_history, it is not modern. It seems to be a factor that the version of ECMAScript supports the older version with it.
In addition, I used "highlight.js" for the code highlighting part using wkhtmltopdf in markdown to pdf.
The highlighting is fine for Chrome and Firefox.
highlight.js is very useful.
Thank you for being able to isolate the cause of the problem.

If you are building your own project you could try version 9, which does work in some older browsers (IE11) - though I can't speak for QtWebkit... but yeah it sounds like this is a ECMAScript issue with Qt just not supporting the more modern stuffs.

In fact, I've been aware of the lack of support for highlight.js since v9.
If wkhtmltopdf can get wkhtmltopdf to adopt v5 of the Qt engine, it still seems to be a possibility, so I'd like to check with wkhtmltopdf as well.
Thanks for the confirmation.
(Now it looks like it would be good to have something from the Chronium engine, not QtWebkit, since the Chronium forces are strong.)

Feel free to share anything useful you learn!


.duplicating() freshly created ImageTextures leads to corruption/crashes

Godot version
3.4.stable
System information
Windows 10, GLES3, NVIDIA 471.41
Issue description
If an ImageTexture is .duplicated() after immediately being created and having it's data set, the duplicate will have corrupted texture data.
Also, this appears to corrupt the heap and crash the application if the scale is sufficiently large (>2 works).
If I create an ImageTexture and fill it, then duplicate it, I'd expect two copies of the final product without corruption. I'd rather not have to wait on texture data being filled before I'm allowed to duplicate objects.
Steps to reproduce
Attaching the following script to a TextureRect that fills the screen produces corrupted graphics.
extends TextureRect

var main:ImageTexture
var other:ImageTexture

var test_image := true

var scale := 0.5 # displays corrupted memory
#var scale := 2.0 # outright crashes

func _bind(to_texture:ImageTexture, image:Image) -> void:
	image = image.duplicate() # optional, but the real project does similar
	image.resize(image.get_width()*scale, image.get_height()*scale, Image.INTERPOLATE_NEAREST)
	to_texture.set_data(image)

func _ready() -> void:
	var image := Image.new()

	if test_image:
		# test with an image
		image.load("res://icon.png")
	else:
		# or test with a solid fill
		image.create(32, 32, false, Image.FORMAT_RGBA8)
		image.fill(Color.blue)

	main = ImageTexture.new()
	main.create(image.get_width(), image.get_height(), Image.FORMAT_RGBA8, Texture.FLAG_FILTER)

	# if the texture has data set before duplicating, it becomes corrupted
	_bind(main, image)

	other = main.duplicate()

# swap between the two textures for debugging
var flicker := true
var flicker_time := 0.0
func _process(delta: float) -> void:
	flicker_time = move_toward(flicker_time, 0, delta)
	if flicker_time == 0:
		texture = main if flicker else other
		flicker_time = 0.5
		flicker = not flicker

Minimal reproduction project
No response

Theory: Race condition in Image.resize()? 🤷♂

Under set_data() it states that the image dimensions, format, and mipmaps need to match the existing texture's image configuration.  I'm assuming that when you resize the image, the imagetexture resource no longer has valid bounds compared to what's in memory (maybe increasing the scale when doing this clobbered memory), so setting other to a duplicate of that probably grabs some kind of invalid state.

Update 1 : Trying to fetch the size using get_size() of the respective image in the above code reports correctly after resizing, but the resource from main.get_data() does not reflect the new size, so indeed it seems using set_data() is not updating the resource, This is the source code for that method, and it doesn't seem to hold your hand at all with regards to what you feed it, except that it expects the image you set is not null:
void ImageTexture::set_data(const Ref<Image> &p_image) {
	ERR_FAIL_COND_MSG(p_image.is_null(), "Invalid image");

	VisualServer::get_singleton()->texture_set_data(texture, p_image);

	_change_notify();
	emit_changed();

	alpha_cache.unref();
	image_stored = true;
}

This makes a call to the current rasterizer loaded for your project (GLES2 or GLES3 for godot 3 projects) and somewhere in that method is probably where the state gets corrupted.  If you want to resize an ImageTexture, you probably want to use ImageTexture.set_size_override() instead, or call main.crate_from_image() again after resizing before calling set_data(), or else your duplicate will be accessing uninitialized memory (or out of bounds memory).
I have to assume this issue has existed for a while, since I found what may be a similar problem from the Godot Q&A going back to 2016.  Godot 4.0 seems to have changed the name of this method to ImageTexture.update() to better reflect what it's supposed to do (and what it's not expected to do), and it also has more bounds checks to make sure you don't blow stuff up using this method.

Thank you for you investigation! I understand how to avoid and fix this but I worry that merely documenting the heap corruption isn't enough. I lost an entire scene / unsaved code because this crashed in a tool script, that's not good!
If it's possible I'd like to see this become safer.

I'll try submitting a patch to 3.x to add more checks to the data sent to set_data() shortly.  :)

Do you know what code's responsible for the clobbering? I can't figure it out. But when the heap corruption sets in, I get notified on arbitrary allocations. In looking at RasterizerStorageGLES3::texture_set_data, it has some pathways that expect/adapt the image from different sizes.

Yes, I assume it's happening somewhere there, and that's as far as I got before I was in over my head, lol.  However that call seems very low-level and I believe is called all over the engine, so I won't be messing around in there.  It likely expects any other method which interacts with the user (ie:  you and me) to sanitize the inputs first so it can do what it's supposed to do as efficiently as possible.


"Failed to create the WebView control" issue

Environment
Windows build number:Microsoft Windows [Version 10.0.18363.836]
PowerToys version: Latest
PowerToy module for which you are reporting the bug (if applicable): Settings?

Steps to reproduce
Click icon in taskbar
Right click > settings

Expected behavior
opens settings

Actual behavior
Error message

Screenshots

I have followed previous posts and PowerToys isn't running elevated. UAC is enabled on 3rd setting

However, issue also occurs when running PowerToys as Admin and UAC off
Account is the only account on the PC (bar the built in Administrator which is disabled) and is an Admin
thanks!

Restarted explorer.exe and working now.. odd

Odd thing is you shouldn’t have seen the old settings screen on the latest version.

I'm facing the same issue, with v18.2

I'm facing the same issue, with v18.2

@lsasounian What version of Windows are you on

@crutkas I'm on 1809, comp OS 17763.1217. Can't go to 1909 due to an issue with my graphic card driver, if I update it, I won't be able to use my graphic card

@crutkas any update?

at the end of the day, this is issue #243 for WebView.  Our hope was WinUI 3 would be ready in time so we would get the backport ability from 19h1.  We don't know exactly what is causing this and long term plan here is to migrate to WinUI 3 stable and then deprecate the webview settings system.
we can't reproduce the issue and our attempts it have come up underwhelming.  If we were to use WebView2, that has a dependency on the new edge, which we can't assume you have installed so we're back at square one for a set of users

Can you try with the latest?  @jake8923948 we fixed a few os detection issues and this should cause you to leverage the new settings system.


Configuration missing

The ‘radius’ part of the configuration isn’t there. The gradient still works and I can make my backgrounds darker and different colored but they won’t actually blur no matter what I do

The radius in Blur+ is based on the vanilla blur strength that can be configured in the Accessibility Settings.
Are you on Fabric or NeoForge? There are currently still some issues on NeoForge, including Blur not working in various screens.


Bouncerate between AMP & PWA

It will be interesting to investigate and understand the behaviour of Google Analytics regarding the Bounce rate between AMP and PWA.
Specifically, how does analyticis meassure a user that goes from the AMP version to the PWA, clicking inside the AMP version. Does it count as the same visit? Is there a way to unify client ids?

Moved to https://github.com/frontity/saturn-theme/issues/15


Code smell in js.

https://github.com/Vivena/babelweb2/blob/506f97fed4662649abffd1f5089bf17fcc4e7ecb/static/js/initialize.js#L104-L105
The for loop seems fishy. i is unused, you don’t enumerate the elements since the first value is returned. Isn’t the for loop completely useless?

I have no idea what's going on with this isEmpty function.  And of course this particular function is written by me. So, yeh, thanks for (once again) decreasing my self-confidence.
As written right now, yes, the loop is useless, but I have a feeling that I had something different in my mind when I desperately tried to write this code. Maybe it's a bug, maybe just a silly quasi-typo, I guess we'll never know.


how load and save a model

Hi,
How do I load and save a model so I can run an app that predicts against loaded data set? Would I pickle the model?
Thanks

Hi again,
This forecasting algorithm does not have any trainable parameters, so the only thing you would need to save and load are the parameters you provided when you instantiated the Psf class (such as cycle_length and apply_diff), as well as the values of k and w. If you did not provide k and w at the start, you can access them after calling fit like this:
psf = Psf(cycle_length=12, apply_diff=True, diff_periods=12)
psf.fit(train)

print(f"k: {psf.k}")
print(f"w: {psf.w}")

Thank you.
On Thu, Jun 6, 2024 at 1:12 PM mamei16 @.***> wrote:

Hi again,
This forecasting algorithm does not have any trainable parameters, so the
only thing you would need to save and load are the parameters you provided
when you instantiated the Psf class (such as cycle_length and apply_diff),
as well as the values of k and w. If you did not provide k and w at the
start, you can access them after calling fit like this:
psf = Psf(cycle_length=12, apply_diff=True, diff_periods=12)psf.fit(train)
print(f"k: {psf.k}")print(f"w: {psf.w}")
—
Reply to this email directly, view it on GitHub
https://github.com/mamei16/PyPSF/issues/5#issuecomment-2153022631, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPTOI7DV54KRPS6GKYRXN3ZGCJ6TAVCNFSM6AAAAABI3L7WPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJTGAZDENRTGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Reduce metrics retention time to two weeks (Issue #7676, PR #7740)

Second phase for #7740

Processing this pull request

Merged into branches iso7 in df6ab10fc5ffaae7b9e2b7775ff48fcf419c55f8

Processing #7744.


Upload my presentation

I'm sorry for belated uploading.

Please put the .pdf into this repo, and link to it there. Currently, you're linking to your own fork.


Add support for custom activity?

There are some apps that need to use activity to open (OEM apps like OnePlus Shelf),Is there a way to add activity as a selection?

#18


Feature request - Piplines adding items so they align

I always have a challenge aligning components onto a pipeline. They always end up slightly off and when I scale the map up and down their alignment also changes even when it was perfect to start with.
Using the is map as an example:
https://github.com/swardley/Research2022/blob/main/construction/construction-alternative-construction
https://pbs.twimg.com/media/FR6fvOcXoAEZslT?format=jpg&name=large
And focusing on the following part:
component construction technologies [0.39, 0.52] label [28, -32]
pipeline construction technologies [0.35, 0.7]
component robotic [0.37, 0.45] label [-9, 25]
component 3D printing [0.37, 0.41] label [-60, 24]
I have a suggestion a new component type called pipelinecomponent this would lead to:
component construction technologies [0.39, 0.52] label [28, -32]
pipeline construction technologies [0.35, 0.7]
pipelinecomponent construction technologies, robotic [0.45] label [-9, 25]
pipelinecomponent construction technologies, 3D printing [0.41] label [-60, 24]
pipelinecomponent would just take the location on the pipeline rather than taking both the x and y locations much the same way as the pipeline takes it visibility location from the initial component.
Apart from that these would act like any other component.
(eg. you would be able to evolve a pipelinecomponent etc etc)
Update the syntax from the first submission I realised it needed the pipeline name in the pipelinecomponent type
pipelinecomponent   [} [label......]

working example: https://beta.onlinewardleymaps.com/#703Ni4Dth65U1mJBCf

bug.. The ability to create a square box without the surrounding box seems to have gone. (just a pipeline without options)

now live.


CO Sender - Validate test files from Vault

What you need to know

Vault has 2 states they report to that are requesting a switch over to ReportStream: Colorado and Delaware. Vault is already set up for Delaware, but now they need to be connected to Colorado.
Kickoff via email has already been completed.

Acceptance Criteria
...
To Do

[x] Once engineer is assigned, have @BerniXiongA6 forward all email chain along with sample file to be validated.

Tara Brook from redoxengine provided a sample message file for review.

note: The organization's name in ReportStream is reopenlab.

9/27 - Provided feedback on initial test file. Also, tried to get clarification on sending to Delaware.

Vault does not appear to be set up for DE yet either. There is some confusion about the LIVD values as the test kit used does not appear on the table. Sent email to integration engineer and Vault employees asking for clarification.

Message sent to Tara Broke<EMAIL_ADDRESS>"Hi Tara,
Other than the LIVD table value not matching, everything else looks good. While we wait for the folks at Vault, the next thing to decide will be whether you want to use token-based authentication or a shared secret key for connecting to the API. Both methods are described in the Programmer's Guide (https://reportstream.cdc.gov/resources/programmers-guid
CDC Prime ReportStream
ReportStream Dashboard Application
reportstream.cdc.gov
e) with examples.
We typically use Keybase encrypted messaging (Keybase.io) to share keys, so if possible if you could create a Keybase account and let me know your account name that would be great. If Keybase is not an option for your organization we can use secure email as an alternate method.
Thanks,
James"

This looks like it's on hold due to their device not being FDA approved.


⚠ Bofrost.at has degraded performance

In d20811c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1408 ms

Resolved: Bofrost.at performance has improved in 9504d35 after 50 minutes.


AMD Infinity Fabri Link not working

Hi everybody,
here is my problem:
I have 2 gpu MI100 in my server and they are seen by the system:
========================== Link Type between two GPUs ==========================
GPU0 GPU1
GPU0 0 PCIE
GPU1 PCIE 0

Instead, If I connect them with through a bridge (AMD Infinity Fabri Link) then the system doesn't see them anymore at all.
The bridge is a 4 slots bridge, but I have only 2 MI100, so, is it possible that having a 4 slots bridge for only 2 MI100 then it does not work?
regards

Hi @question12345
Thanks for reaching out.
Its not architect-ed to work like that.
The bridge tells the firmware that its a 4p hive.
The routing on the bridge is static. It expects to find a GPU in every slot. The PSP firmwares of all GPUs need to coordinate during boot-up. There is some HW topology ID that the firmwares get from the bridge. If you have a 4P bridge, they expect to fine 3 peer GPUs to synchronize with.
Hope this helps.
Thank you.


Cannot switch from nvim to tmux pane

I've had a working config for some time on my MacBook and I've copied it to a new machine running Ubuntu 19.10, but now cannot switch out of a pane running neovim into a tmux pane. (Switching between tmux panes or from a tmux pane to neovim works fine).
neovim init.vim (installation via vim-plug):
call plug#begin()

" Common navigation of tmux and nvim windows
Plug 'christoomey/vim-tmux-navigator'

call plug#end()

tmux.conf:
set -g @plugin 'tmux-plugins/tpm'
set -g @plugin 'tmux-plugins/tmux-sensible'
set -g @plugin 'christoomey/vim-tmux-navigator'

run -b '~/.tmux/plugins/tpm/tpm'

output from :verbose nmap <C-j> in neovim:
n  <NL>        * :TmuxNavigateDown<CR>
        Last set from ~/.config/nvim/plugged/vim-tmux-navigator/plugin/tmux_navigator.vim

I've also tried running :TmuxNavigateDown directly from within neovim to ensure it's not a key binding issue and nothing happens.
I'm on tmux 2.9 and neovim 0.3.8
Update
I've now tried this with vim (rather than neovim) and it's also not working there.
I was also on tmux 2.8 on my MacBook, so I updated to 2.9 and it all still works perfectly.

Hmm, that's surprising. Can you clarify if this happens in all directions? Also, can you confirm the output for each direction of the vim keybinding?
:verbose nmap <C-h>
:verbose nmap <C-j>
:verbose nmap <C-k>
:verbose nmap <C-l>

It's the same in all directions - not working from within neovim but working from tmux.
The nmap output for each binding is TmuxNavigateLeft, TmuxNavigateRight etc. as expected.
Each of those commands does nothing when run directly in neovim.

Anything else I can do to debug this?

SOLVED
My nvim config set the shell variable to the path to bash - however, it was using the Mac's version of that path rather than the correct path on Ubuntu. All working perfectly now that the correct path is in there.

SOLVED
My nvim config set the shell variable to the path to bash - however, it was using the Mac's version of that path rather than the correct path on Ubuntu. All working perfectly now that the correct path is in there.

What did you change?

@geoffharcourt probably you've already solved it by now, but I also found this thread in my quest to solve this issue.
In the end, added default-shell and shell to both tmux and nvim config solved the issue, pointing them to the same shell.
# tmux config
set-option -g default-shell /run/current-system/sw/bin/zsh

# nvim config
set shell=/run/current-system/sw/bin/zsh

Obviously you'd want the value of default-shell and shell to point correctly to what shell you wanna use, which might be different than above.


@conda-forge-admin, please add bot automerge

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/tiled-suite-feedstock#9.


Is it possible to draw a curved line?

I guess the title says it all... How could I draw a curved line between markers/points in Polymaps?
For example, let's say I wanted to draw a point in Australia to a point in Europe with curvature, much like one might see a flight route mapped?
Thanks!

Take a look at D3's support for great arcs:
https://github.com/mbostock/d3/blob/master/examples/great-arc/great-arc.html
http://mbostock.github.com/d3/talk/20111116/#14


How to get both attached node models from a link information.

My nodes are custom model is holding data inside , when nodes are linked i need to some how know programmatically which node attached to which node , i tried Diagram.Nodes.First().Links and then lost where is next node information is stored.
any idea to identify programmatically , the both nodes models attached to a link as source and target
currently I am trying version 3 and its just excellent , please accept a heartly thanks from my side.

If you are connecting links between 2 nodes directly:
var sourceNode = (link.SourceAnchor as ShapeIntersectionAnchor)!.Node;
// OR
var sourceNode = link.SourceAnchor.Model as NodeModel; // or your custom type

If you're using ports:
var sourceNode = (link.SourceAnchor as SinglePortAnchor)!.Port.Parent;
// OR
var sourceNode = (link.SourceAnchor.Model as PortModel)!.Parent; // or your custom type

thanks , this worked for me , TaskPort is my custom port.
var targetNode = (link.Target.Model as TaskPort).Parent;


Recipes are somewhat special

See #115
We should enable developers to roll their own, separate from gocassa.

Should be nice to keep the recipes in Gocassa.
My idea is when someone has a new use case, it can share it with all the other users of Gocassa. In this way the lib will be more and more useful .

I have exported the toMap (now ToMap) function, I believe that this should allow third party developers to use their own recipes.
If you believe there are other changes required feel free to reopen the issue.


Kitty does not start more

Describe the bug
Kitty does not start more
To Reproduce
Steps to reproduce the behavior:

Run nixos-unstable
Start Kitty
Does not start

Expected behavior
Its working
Screenshots
[055 09:05:46.416468] [glfw error 65542]: GLX: No GLXFBConfigs returned
[055 09:05:46.416497] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[055 09:05:46.416512] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers.

Additional context
Add any other context about the problem here.
Metadata

system: "x86_64-linux"
host os: Linux 5.5.5, NixOS, 20.09pre214390.ea79a830dcf (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.3
channels(shyim): "nixos-20.03pre208171.2e8fc97dbfa"
channels(root): "nixos-20.09pre214390.ea79a830dcf"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: kitty
# a list of nixos modules affected by the problem
module:

What does nix run nixpkgs.glxinfo -c glxinfo | grep OpenGL says?

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 19.3.3
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 19.3.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.3.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Try setting running kitty with env MESA_GL_VERSION_OVERRIDE=3.3 kitty

Still don't running
❯ env MESA_GL_VERSION_OVERRIDE=3.3 kitty
[055 16:02:21.181352] [glfw error 65542]: GLX: No GLXFBConfigs returned
[055 16:02:21.181372] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[055 16:02:21.181380] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers.

Are you using wayland/sway? Did a previous version of kitty work?

I am using I3. I guess it happend with Kernel update I will downgrade to test that :thinking:

Same with 5.4 kernel 🙈

Could this be the same as https://github.com/NixOS/nixpkgs/issues/75868 ?

It may be but I can't reproduce it on the same machine where I tested #75868.

I think it's worth trying LIBGL_DEBUG=verbose in any case.

❯ LIBGL_DEBUG=verbose kitty
[056 11:43:24.816491] [glfw error 65542]: GLX: No GLXFBConfigs returned
[056 11:43:24.816512] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[056 11:43:24.816535] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers.

Similar issue happends also with alacritty. I guess it's a general problem

I have the same issue after an upgrade. The whole gl context is missing and glxinfo also screams
name of display: :1 Error: couldn't find RGB GLX visual or fbconfig
This doesnt happen on the 19.09 channel

Bump. I have accidentally spotted this issue, I also use kitty and have been hesitant in updating my unstable channel until this is resolved.

It's not only kitty. The whole gl context is broken in 20.03 / unstable.

I tried to bisect the problem, but for some reason it just vanished. Now I cannot reproduce it anymore on the same machine with the same configuration and the same pinned nixpkgs. Very weird.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nix-bisect-bisect-nix-builds/5584/10

@timokau I just upgraded to master again but the issue is still there. I am trying your bisect package now

If it's hard to reproduce and seems to appear/disappear randomly maybe it has to do with the /run/opengl-driver impurity of the system and not much with nixpkgs itself.

Right, I would not expect these issues to happen if you have this path matching (i.e. booted NixOS version) with the package version you are using.  I suspect the culprit is glibc update done during the 20.03 cycle.

Right, I would not expect these issues to happen if you have this path matching (i.e. booted NixOS version) with the package version you are using. I suspect the culprit is glibc update done during the 20.03 cycle.

In an effort to test this, I wanted to go back to a revision before this error occurred (8130f3c1c2bb0e533b5e150c39911d6e61dcecc2), reboot into that and then switch back to a more recent one to see if the problem re-appears.
It turns out that the problem now actually occurs after rebooting into 8130f3c1c2bb0e533b5e150c39911d6e61dcecc2. That revision was definitely good before, and I did reboot. So that confirms that there is some impurity going on (that goes both directions), but rebooting does not fix it. Not sure what does, but apparently at some point some switch was flipped for me.

I have the same issue here with kitty (but with others packages like glxinfo, compton, ...)
the solution was to remove the package and to reinstall it ... don't ask me why

@fatpat that worked for me as a work around. I removed kitty from my configuration.nix, and instead installed it with nix-env now it works. Go figure.

Same for me :)

@shyim please don't close this. We still need to be able to install it without nix-env. A workaround is not a bug fix!

FWIW my kitty actually was failing in my ~/.config/nixpkgs/config.nix (installed with nix-env) but worked when I installed it in my user packages (/etc/nixos/configuration.nix).

On unstable, no matter how I install it, I get
fast_data_types.FreeTypeError: Failed to load face, with error: cannot open resource
[251 06:40:21.964670] Failed to convert descriptor to face for symbol_map font

That error seems very different; best put that in a separate issue.

I have the same problem, but not with just Kitty. Picom, among others is problematic too. The output of nix run nixpkgs.glxinfo -c glxinfo | grep OpenGL has only one change between the working and broken configurations:
-OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.7
+OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.9

I have the same problem, but not with just Kitty. Picom, among others is problematic too. The output of nix run nixpkgs.glxinfo -c glxinfo | grep OpenGL has only one change between the working and broken configurations:
-OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.7
+OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.9

I am experiencing the same issues, and it's also just this diff. It's preventing me from upgrading my system at the moment. I might try installing it with nix-env instead of with home-manager, maybe that helps. But it's generally undesirable.

I'm experiencing this with Julia / Makie.jl as well.
using ModernGL, GLFW
window = GLFW.Window(resolution = (10, 10), major = 3, minor = 3, visible = false, focus = false)

After updating to latest release-20.09 (fd2044d846b590328b8995fd490258bfea3bf468), the error has now changed for me. I now get:
❯ glxinfo
name of display: localhost:10.0
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  154 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  41
  Current serial number in output stream:  42

The Julia code similarly gives:
julia> using GLFW
julia> window = GLFW.CreateWindow(640, 480, "GLFW.jl")
ERROR: GLFWError (VERSION_UNAVAILABLE): GLX: Failed to create context: BadValue

I have this same error installing kitty with home-manager running Debian Testing. Installing via nix-env gives the same error.

@syzygyzer AFAIK, on non-NixOS distros, openGL applications won't work by default because they can't find the driver.
You can try using https://github.com/guibou/nixGL to workaround this issue.

This has started failing for me again after updating to latest 20.09. Any ideas?
kitty
[029 12:35:41.007051] [glfw error 65542]: GLX: No GLXFBConfigs returned
[029 12:35:41.007061] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[029 12:35:41.007067] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers

nix run nixpkgs.glxinfo -c glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce RTX 3080/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 455.38
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 455.38
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 455.38
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

This has started failing for me again after updating to latest 20.09. Any ideas?
kitty
[029 12:35:41.007051] [glfw error 65542]: GLX: No GLXFBConfigs returned
[029 12:35:41.007061] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[029 12:35:41.007067] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers

nix run nixpkgs.glxinfo -c glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce RTX 3080/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 455.38
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 455.38
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 455.38
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Not stale, still an issue.

For those of you who experience this issue on an OS other than NixOS (like @drbeefsupreme using debian, like me), the solution is to install nixGL ( https://github.com/guibou/nixGL ) and use the wrapper to launch kitty

I ran into this with nix-env and nix-shell, with 20.05 channel.
$ kitty
[323 01:22:47.635093] [glfw error 65542]: GLX: No GLXFBConfigs returned
[323 01:22:47.635109] [glfw error 65545]: GLX: Failed to find a suitable GLXFBConfig
[323 01:22:47.635116] Failed to create GLFW temp window! This usually happens because of old/broken OpenGL drivers. kitty requires working OpenGL 3.3 drivers.

However, it worked via environment.systemPackages, most likely because my system nixpkgs is significantly newer, pinned to a weeks old nixos-unstable: b67e752c29f18a0ca5534a07661366d6a2c2e649
The same contrast happened with glxinfo:
$ glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig

vs
$ glxinfo | grep OpenGL
OpenGL vendor string: AMD
OpenGL renderer string: Radeon RX 570 Series (POLARIS10, DRM 3.42.0, 5.15.0, LLVM 12.0.1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.2.5
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.2.5
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.2.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

So maybe this is fixed now?

I had the same error, glxinfo gave me
$ glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig

and upgrading my system from my initial version of 20.05 to 20.11 or unstable did nothing for me either.
I had previously installed both nvidia and amd drivers because I was using my config on multiple PCs, what worked was changing a few options:
- boot.initrd.kernelModules = [ "amdgpu" "nvidia" ];
- boot.kernelModules = [ "amdgpu" "nvidia" ];
+ boot.initrd.kernelModules = [ "amdgpu" ];
+ boot.kernelModules = [ "amdgpu" ];
+ services.xserver.videoDrivers = [ "amdgpu" ];

Hopefully this fix isn't specific to me and will work for some of you ^^

I encountered this issue when upgrading to NixOS 21.11. The cause for me was kitty (and others, like picom) being installed from home-manager. I had updated nixos, but not home-manager, causing kitty to look for the wrong driver (?). Went through all kinds of attempts to fix, but in the end simply rebuilding my home-manager config with the 21.11 channel did it. Maybe someone can learn from my mistakes if they find this :)

I encountered this issue when upgrading to NixOS 21.11. The cause for me was kitty (and others, like picom) being installed from home-manager. I had updated nixos, but not home-manager, causing kitty to look for the wrong driver (?). Went through all kinds of attempts to fix, but in the end simply rebuilding my home-manager config with the 21.11 channel did it. Maybe someone can learn from my mistakes if they find this :)

I just upgraded my flakes and also encountered this: kitty, alacritty. wezterm or glxinfo all fail in some way or another. No home-manager, just regular NixOS.
Any placed to look or commands to run to try and narrow this down?

@j-steinbach Could you please specify your exact kernel version and the package name for your nvidia drivers?

@lapp0 For the kernel I simply use the latest one: boot.kernelPackages = pkgs.linuxPackages_latest; I don't know how this option exactly works, but uname results in Linux 5.16.3 #1-NixOS SMP PREEMPT x86_64 GNU/Linux.
For the nvidia drivers package name I don't understand what you want to know. All I have set is the services.xserver.videoDrivers = [ "nvidia"], as mentioned above. This results in nvidia-smi: NVIDIA-SMI 495.46       Driver Version: 495.46       CUDA Version: 11.5
To be sure, I also rg'ed both "kernel" and "nvidia", and those are the only lines I could find.
Mabe the flake inputs are also interesting. Here I specify inputs.nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";

Hmm, doesn't work with my switch to unstable

Linux 5.16.8 #1-NixOS SMP PREEMPT x86_64 GNU/Linux
NVIDIA-SMI 510.39.01    Driver Version: 510.39.01    CUDA Version: 11.6

When I was on Linux 5.15 and CUDA Version: 11.4 it also didn't work.
For consistency with your configuration, I changed
services.xserver.videoDrivers = [ "intel" "nvidia" ];
to
services.xserver.videoDrivers = [ "nvidia" ];
Which also resulted in
glxgears
Error: couldn't get an RGB, Double-buffered visual

Here are some relevant bits of my configuration. Please let me know what is different in your setup.
services.xserver.videoDrivers = [ "intel" "nvidia" ];
boot.kernelModules = [ "nvidia-uvm" ];
services.openssh.forwardX11 = true;

# custom zfsUnstable with zfs-head-master and linux 5_16
hardware.nvidia.package = pkgs.zfsUnstable.latestCompatibleLinuxPackages.nvidia_x11_beta;
boot.kernelPackages = pkgs.zfsUnstable.latestCompatibleLinuxPackages
boot.initrd.availableKernelModules = [ "ehci_pci" "ahci" "isci" "usbhid" "usb_storage" "sd_mod" ];

@lapp0 I have good and bad news :)
The good news is: you are still sane, this indeed doesn't work again!
The bad news: it now is also broken for me :)
I wanted to share my config with you, updated my flake and... the rest is known.
My guess is that we need to identify the correct mix of kernel and nvidia packages. And then withhold from updating if they don't match. How to do that? No idea.

 ↳ glxgears
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  28
  Current serial number in output stream:  29

 ↳ nvidia-smi
Failed to initialize NVML: Driver/library version mismatch

Hmm, I don't have the same error. This post suggests rebooting works https://stackoverflow.com/a/43023000

Definitely. In the meantime you can already take a look at them here. I hope its readable. Still WIP.

I also found this interesting X log bit
[  6082.686] (II) AIGLX: Screen 0 is not DRI2 capable
[  6082.716] (EE) AIGLX error: dlopen of /run/opengl-driver/lib/dri/swrast_dri.so failed (/run/opengl-driver/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[  6082.716] (EE) AIGLX error: unable to load driver swrast
[  6082.716] (EE) GLX: could not load software renderer
[  6082.716] (II) GLX: no usable GL providers found for screen 0

Updating made it work again. Thanks for the tip.
I've noticed that we use a different architecture:

amd  kernelModules = [ "kvm-amd" ];
availableKernelModules = [ "nvme" "xhci_pci" "ahci" "usb_storage" "usbhid" "sd_mod" ];
no ZFS

You probably did this, but have you tried it with a stripped-to-the-bones minimal config?

I tried running a few of your commands so that we maybe can see some differences:
 ↳ modinfo nvidia
filename:       /run/booted-system/kernel-modules/lib/modules/5.16.7/misc/nvidia.ko
firmware:       nvidia/510.47.03/gsp.bin
alias:          char-major-195-*
version:        510.47.03

 ↳ sudo lshw -c display
  *-display
       physical id: 0
       bus info: pci@0000:1c:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:57 memory:f6000000-f6ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:f000(size=128) memory:c0000-dffff

I have boot.kernelModules = [ "kvm-intel" ];
I will try a barebones config.

I've also just discovered that we can choose different nvidia packages. Besides that I think I'm out of things to try.

I tried a mostly plain configuration as well as nvidia_x11 and nvidia_x11_beta. Thanks for trying, I'm going to ask on discourse.

https://discourse.nixos.org/t/forwarding-x11-to-nvidia-server-couldnt-find-rgb-glx-visual-or-fbconfig/17730

Issues with the same error (at least I'm not alone)
https://github.com/NixOS/nixpkgs/issues/85866
https://github.com/NixOS/nixpkgs/issues/66755
https://github.com/NixOS/nixpkgs/issues/132045
https://github.com/NixOS/nixpkgs/issues/82959
https://github.com/NixOS/nixpkgs/issues/94958
https://github.com/NixOS/nixpkgs/issues/101202
https://github.com/NixOS/nixpkgs/issues/55191
https://github.com/NixOS/nixpkgs/issues/147377
https://github.com/NixOS/nixpkgs/issues/84692
https://github.com/NixOS/nixpkgs/issues/80702
https://github.com/NixOS/nixpkgs/issues/105024

(Note: I am forwarding X11. I have tried with ssh -X, ssh -Y, ssh -XY, and vglconnect, all resulting in the above error)

X11 forwarding with OpenGL?  I don't expect that's even meant to work.

The nvidia package doesn't contain a lib/dri/swrast_dri.so failed, the only way I can think of handling this would be to add mesa to hardware.opengl.extraPackages, so that you inherit some of the missing directories like /lib/dri

Thanks for responding.
@vcunat virtualgl (via vglconnect and vglrun) is supposed to handle 3D rendering on the server, and then the 2D stuff is rendered on the clients forwarded X server.
@jonringer I did that, but I still have the same error. (hardware.opengl.extraPackages = [ pkgs.mesa ];)
Mesa doesn't appear to have that library:
 find /nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/share
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/share/drirc.d
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/share/drirc.d/00-mesa-defaults.conf
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/lib
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/lib/libglapi.so
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/lib/libglapi.so.0.0.0
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/lib/libgbm.so.1
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/lib/libgbm.so
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/lib/libgbm.so.1.0.0
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/lib/libglapi.so.0
/nix/store/5j7k2nrgvl6vnichkg4c1fwj1907nvgg-mesa-21.3.5/etc

Anything you would recommend to find the missing library?

oh sorry, it's pkgs.mesa.drivers

Thanks! That resolved the error when I simply run glxgears on my server.
Do you have any insights into why I might get the "fbconfig" error when I run it in vglrun?
$ TVNC_WM=/run/current-system/sw/bin/twm vncserver

Desktop 'TurboVNC: host:2 (remote)' started on display host:2

Starting applications specified in /home/user/.vnc/xstartup.turbovnc
Log file is /home/user/.vnc/host:2.log

$ cat /home/user/.vnc/host:2.log | grep running
18/02/2022 03:15:45 VNC extension running!

$ vglrun -d :2 glxgears
[VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to
[VGL]    <IP_ADDRESS>, the IP address of your SSH client.
Error: couldn't get an RGB, Double-buffered visual

Seems turbovnc has the drivers linked already
nix-store -q --references $(which vncviewer) | grep drivers
/nix/store/2gl456ql1g1pj9qwkgkpjajknc1j702h-mesa-21.3.5-drivers

However virtualgl doesn't
$ nix-store -q --references $(which vglrun) | xargs nix-store -q --references | uniq
/nix/store/4s21k8k7p1mfik0b33r2spq5hq7774k1-glibc-2.33-108
/nix/store/6pdb0rz2w2hsfsy66kwrbz67jd424wv7-libX11-1.7.2
/nix/store/a3yw11i2iskvr1zx2za4mwrj9sawq7hz-libXext-1.3.4
/nix/store/5lzlfgrc37wqj400b4qgpaa6kc9d2wr1-libglvnd-1.4.0
/nix/store/ndnqiz3nnifj1blhg9q626xlmkqq1nmh-gcc-10.3.0-lib
/nix/store/04yj0nllw5bqzzlay5m6zzbmyw7csgnk-glu-9.0.2
/nix/store/a6i6c7hkfn5s9bbgc1x6j1cnd5dppzkv-libjpeg-turbo-2.1.2
/nix/store/pi2h6nky70gww75w05zq1ch9fmycrvvy-libGL-1.4.0
/nix/store/0yb5b9wq3y7wn5l9akcz7hcyyk2bc6rk-fltk-1.3.8
/nix/store/1dw67iap73klp5rqcvqpf8sadrvr8y8d-ocl-icd-2.3.1
/nix/store/n8k71gd1a759s9mmi85iinfdb0ckkzkv-glibc-2.33-108
/nix/store/fp08p7c881knk9h135vj1acb47q218id-gcc-10.3.0-lib
/nix/store/1l82d038523bapkkc0qkgjyzdblfxbri-gcc-10.3.0
/nix/store/290xnrwys55hbnv9xggcc98q2sfgqf6g-libXtst-1.2.3
/nix/store/2dv93bbc06c7zg866qid73j3r36zz3jx-gcc-10.3.0
/nix/store/4k40gdgf7ckimb3hlwywx76dj5435ack-libXv-1.0.11
/nix/store/cmq9rapgxx18h99r0yp6vvzk1fkwjs3j-libX11-1.7.2
/nix/store/nca9ls2cla27qal0p01k2g17agmd62bf-libXext-1.3.4
/nix/store/64hrj9wbf9yvqwkjwr2r7qsdl99f8wcm-libXtst-1.2.3
/nix/store/hrc96ak11li2czfqj0xf2fc1clpn6gvx-libglvnd-1.4.0
/nix/store/aqj8zmgxvx44r5kf7jnqyyiwwfpbhj0x-libGL-1.4.0
/nix/store/bqkimn04bkknc2ngl01ipmjlq782d7m6-libjpeg-turbo-2.1.2
/nix/store/zhh1ppg81ahlvbf7qlfirj1pzlm8gizr-glu-9.0.2
/nix/store/aa5m1mpvsamdx7pi92fbkfhwh19q62z3-fltk-1.3.8
/nix/store/rycnmssyan6nd1dzas6v6b886qvk663m-ocl-icd-2.3.1
/nix/store/vnm9fwc6hj2igr5as9x2bjwx5nm8g0w8-libXv-1.0.11
/nix/store/nicc84inpa08zi5m52l30nfbp411apnw-virtualgl-lib-2.6.5
/nix/store/sp7fy3jh5ikc2f0g61h164nn3vvcky4a-virtualgl-lib-2.6.5

nix-store -q --references /run/opengl-driver
/nix/store/2gl456ql1g1pj9qwkgkpjajknc1j702h-mesa-21.3.5-drivers
/nix/store/vlp25l161q65qnm8my6zj9i87gkfh748-nvidia-x11-510.47.03-5.16.8

For now I'm trying to recreate the virtualgl package definition with pkgs.mesa.drivers included.

export LD_LIBRARY_PATH="/run/opengl-driver/lib:/run/opengl-driver-32/lib" resulted in it rendering a black screen, so it seems I have an issue that is likely unrelated now. Thanks so much!

That's not how finding OpenGL is supposed to work in NixOS (but we did use it in past).  Nowadays it should be indirected through libgnvnd.  (well, I have no idea about virtualgl in particular...)

FYI: I use nixos-unstable as my system flake. Stuff works fine when running, e.g., nix run nixos-unstable#glxinfo. However, if I use an older flake such as nix run nixos-21.11#glxinfo, I get the same errors mentioned in this thread.
I bumped into this because nixos-unstable#calibre is broken at the moment, and I cannot run nixos-21-.11#calibre either.

As for workarounds for such cases, I'd:

look at https://hydra.nixos.org/job/nixpkgs/trunk/calibre.x86_64-linux
nix build /nix/store/70mp9j7lxbyy0ckg22y3g865y9mszlc0-calibre-5.37.0
and use that for now... or you can see git commit hashes there, too.
I generally keep older profiles and fall back to those versions in case of encountering problems; not all issues get discovered during built time or even when using a package.

Thank you for tthis tip! I can build calibre, but I get the same GLX error.Failed to finding matching FBConfig.

For reference, the above calibre starts up without any errors on my 21.11 system.

Indeed, that's interesting...

The issue is back for kitty as well.

One year later, sadly still a problem. I've hit it with alacritty and realsense-viewer. Previously, multiple times, nixGL solved it for alacritty for me, but have issues with that currently. And as for realsense-viewer, nixGL doesn't work on arm which is where I'm using the realsense-viewer.

One year later, sadly still a problem. I've hit it with alacritty and realsense-viewer. Previously, multiple times, nixGL solved it for alacritty for me, but have issues with that currently. And as for realsense-viewer, nixGL doesn't work on arm which is where I'm using the realsense-viewer.

I just got used to rebooting after upgrading, and it's not always needed.

I just got used to rebooting after upgrading, and it's not always needed.

Rebooting doesn't work in my case.
If anyone knows where the error is being thrown (source code), I'm be interested in digging into the problem.
For reproducability, I've also uploaded a 32Gb bootable image for a raspberry pi 3b here username: csce635 password bumpnrun (obviously there's no sensitive information on it)

I'm encountering this exact same error almost 4 years later.....

I'm encountering this exact same error almost 4 years later.....

I followed the rabbit hole on this thread and solved the problem as so:
The issue was an out of date home-manager flake in ~/.config/home-manager
nix flake update
home-manager switch
Boom, problem solved!

Reproduced on nixpkgs 1a9df4f74273f90d04e621e8516777efcec2802a, on Fedora 40. Neither Kitty nor Alacrity work.

On Fedora it will be more like topics around #9415


MacOS Silicon build issues

Hi,
I managed to get a few modules up and running, but this playerbot is giving errors when building. These are a couple of the issues:
In file included from /azerothcore/modules/mod-playerbots/src/ChatFilter.cpp:7:
In file included from azerothcore/modules/mod-playerbots/src/Playerbots.h:11:
azerothcore/modules/mod-playerbots/src/PlayerbotAI.h:187:5: error: expected identifier
HUGE   = 250
^
/Library/Developer/CommandLineTools/SDKs/MacOSX14.0.sdk/usr/include/math.h:733:15: note: expanded from macro 'HUGE'
#define HUGE            MAXFLOAT
^
/Library/Developer/CommandLineTools/SDKs/MacOSX14.0.sdk/usr/include/math.h:704:21: note: expanded from macro 'MAXFLOAT'
#define MAXFLOAT    0x1.fffffep+127f
^
In file included from azerothcore/modules/mod-playerbots/src/AiFactory.cpp:8:
azerothcore/modules/mod-playerbots/src/PlayerbotAI.h:187:5: error: expected identifier
HUGE   = 250
^
/Library/Developer/CommandLineTools/SDKs/MacOSX14.0.sdk/usr/include/math.h:733:15: note: expanded from macro 'HUGE'
#define HUGE            MAXFLOAT
^
/Library/Developer/CommandLineTools/SDKs/MacOSX14.0.sdk/usr/include/math.h:704:21: note: expanded from macro 'MAXFLOAT'
#define MAXFLOAT    0x1.fffffep+127f
^

I wonder if this module is looking for some M'x' CPU instructions that yours don't have, or maybe are different?! ie. the module works on M1 or M2 but not on M3 or pro versions

I'm running a M2 Pro btw. I think I lack some instructions for this yes. Game works perfect with other modules.

这个HUGE定义跟sdk里面的宏冲突了.
This HUGE definition conflicts with a macro in the sdk.


Inconsistent internal variable names

The "11" used to describe the 11 km boundary in the layers of the atmosphere is mislabeled "ll" in some internal variable names. Needs search/replace and re-check.

Corrected with commit 097bf79.


Isolate cluster upgrades for management and workload clusters

Implementation of proposed solution in #5622.
/hold
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Updated the tests myself
/unhold

/approve


First version of our changelog file 😎

This PR introduces a first version of a changelog of Kimchi, starting on November 14th. Feel free to make any suggestions about the versioning numbers.

oh and I just thought about something else, we probably need a CHANGELOG.md per crate! (for example https://github.com/RustCrypto/elliptic-curves/)

sorry to hijack this one! https://github.com/o1-labs/proof-systems/pull/986


Add 'cs setup' tests

Requires a release of Coursier after coursier/coursier#2657 is merged.

needs a trigger
/cc @lwronski

Interesting, it failed with “no main class detected” during the cs setup execution: https://github.com/VirtusLab/coursier-m1/actions/runs/3985837517/jobs/6834993515#step:7:351

I won’t be able to look at the underlying issue, unfortunately. If someone with an M1 architecture wants to help, that would be very much appreciated!

It fails because cs setup tries to install sbtn, and while doing so it tries to build a native launcher (because there is no one yet on macOS and aarch64, see https://github.com/sbt/sbt/issues/7143), and fails to do it.

Follow-up PR: https://github.com/sbt/sbtn-dist/pull/4

Installing sbt now works, but the next app fails.

I cannot reproduce the issue locally. cs setup did work on my M1:
./cs setup --jvm 17
Checking if a JVM is installed
  No JVM found, should we try to install one? [Y/n] y
  Should we update ~/.profile, ~/.zprofile? [Y/n]
Some shell configuration files were updated. It is recommended to close this terminal once the setup command is done, and open a new one for the changes to be taken into account.

Checking if ~/Library/Application Support/Coursier/bin is in PATH
  Should we add ~/Library/Application Support/Coursier/bin to your PATH via ~/.profile, ~/.zprofile? [Y/n]

Checking if the standard Scala applications are installed
  Installed ammonite
  Installed cs
  Installed coursier
  Installed scala
  Installed scalac
  Installed scala-cli
  Installed sbt
  Installed sbtn
  Installed scalafmt


Events are not supported

Events like <Button Click="SomeHandler" /> are not supported.

Or perhaps events like < Button Click =' {Event Path=ClickEvent, EventStream Path= MyClickStream }' />?  A hook to trigger and a hook to subscribe.
Either way, events are essential!

I'd actually prefer this to work directly against the DataContext - it'd lead people towards better designs.  Something like <Button Click='{EventBinding SomeHandler}' /> where SomeHandler was defined in the DataContext.
Ideally, you'd have the option of doing a conversion for the EventArgs -> T, so you could have SomeHandler be defined as a delegate property, ie:
<Canvas OnMouseMove='{EventBinding Move, Converter=MouseEventArgsToPointConverter}' />
with
private void _move(Point location)
{
   // ...
}
public Action<Point> Move { get { return this._move; } }

I like that syntax a lot. Of course, this is a very important feature. I need to take a look at how to implement it.

+1 to the DataContext, @ReedCopsey

The nice things are:

The handler works in the VM, not the View layer, leading to better designs by default
No requirement for compile-time support - can all wire at runtime
Decouples from View types in the handler via a converter (optional), so your VM/Model layers can stay "pure"

Another option for event handling: Create your own Observable<T> class, and use it as a binding target:
class VM
{
   // ...
   // Having property:
   public Observable<Point> Move { get; } = new Observable<Point>();
}

Then the xaml could be <Canvas OnMouseMove='{Observe Move, Converter=MouseEventArgsToPointConverter}' />
If Observer implemented IObservable, it'd allow you to very easily compose reactive streams, even from languages like C#.

^ Now that sounds great

Any progress on implementing this?

I think the ideas mentioned by @ReedCopsey are a really good idea, but I think for us they'll be Perspex markup extensions, as OmniXAML doesn't know anything about binding and DataContexts etc.
For OmniXAML it would be good to just have basic event support.

Super basic event support is in #106. It has built in handling for non-attached events and provides enough information and tooling to users to implement support for attached events. I'll continue to work on implementing attached events support and trying to minimize the new API surface.

Merged in the "events" branch. Thanks, Jeremy!

Was this merged into master?

@zezba9000 Not yet. It's in the v2 branch, but I'll turn this branch into master soon. The problem is that I don't know how to proceed with the switch. I've never done something similar with Git.

@SuperJMN there are two ways.

Change the default branch to omnixaml-v2
Push master to a new branch and then force push omnixaml-v2 to master.

I'd suggest doing the first option.

I've successfully made the change. Thanks for the suggestions! I discarded merging both branches because, they are essentially 2 different projects. V2 started from scratch and, although it reuses some code from v1, it's a minimal part of the whole, so a merge could be confusing and far more problematic.


WIP: allows using plugins without marker

this is something i hacked together because i could not figure out how to make use of pluginManagement.resolutionStrategy.eachPlugin properly since refreshVersions seems to override it
so instead a lambda is passed to the refreshVersions call
usage:
bootstrapRefreshVersions(
    pluginResolution = { pluginId, version ->
        logger.lifecycle("picking group and name for $pluginId with version $version")
        when (pluginId) {
            "com.android.application", "com.android.library" -> "com.android.tools.build:gradle"
            "kotlin-android", "kotlin-kapt", "kotlin-android-extensions" -> "org.jetbrains.kotlin:kotlin-gradle-plugin"
            "androidx.navigation.safeargs.kotlin" -> "androidx.navigation:navigation-safe-args-gradle-plugin"
            "com.google.gms.google-services" -> "com.google.gms:google-services"
            "realm-android" -> "io.realm:realm-gradle-plugin"
            "de.mannodermaus.android-junit5" -> "de.mannodermaus.gradle.plugins:android-junit5"
            else -> null
        }
    }
)

The buildscript way that these plugins without markers require is supported by refreshVersions already FYI.

when i tried to use it on 0.97 and 0.98-SNAPSHOT it did not work, maybe verify that with plugins other than the android plugin that has a workaround hardcoded in refreshVersions ?

Hello @NikkyAI, is that a feature you still want?

it would be nice to have the same syntax of id("some-plugin") in the buildscript and define the lookup of the dependency in pluginManagement.resolutionStrategy
i have not run into this problem as much recently.. and if i did.. i declared the depenencies in the root project buildScript.depenencies
but i think the closer this can model to the usual buildscripts the easier it is to pick up refreshVersions without frustration in complex projects


Document new name and semantics of external labels.

Fixes https://github.com/prometheus/docs/issues/203

@fabxc

:+1:

:+1:
On Wed, Sep 30, 2015 at 12:42 PM Brian Brazil<EMAIL_ADDRESS>wrote:

[image: :+1:]
—
Reply to this email directly or view it on GitHub
https://github.com/prometheus/docs/pull/220#issuecomment-144352124.

...and of course I forgot to open this against next-release instead of master. Sigh. Well, hopefully the full release is not far away.


Improve caching in CI/CD jobs

CI/CD jobs, specially E2E, can be pretty intensive. In order to improve performance and be more eco-friendly, we should cache stuff when possible. At least, we should consider:

[ ] Caching go modules so runners don't need to download them each time
[ ] Caching docker layers (https://github.com/satackey/action-docker-layer-caching)

Seems like caching layers is slower than pulling them, so I'd remove this out of the scope of the issue.


Adding MQTT for local APRS packet storage.

Adding MQTT for sending all received aprs packets to a MQTT broker. MQTT Server and Topic can configurate in is-cfg.json.

thanks @KeyOz for the great implememtation! i have just one small request to change 👍
other than this i am very happy with your implementation!
I can take care of the failing version and format check on the CI 😉

Thanks @KeyOz for the implementation!


HEIC parser reaches EOF inside get32() call

The attached HEIC image was taken with an iPhone XR and when I try to extract the metadata using exifread.process_file(fobj, details = False) then I get the following Traceback:
Traceback (most recent call last):
  File "create_photo_album_JSON.py", line 83, in <module>
    tags = exifread.process_file(fobj, details = False)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/exifread/__init__.py", line 242, in process_file
    offset, endian = heic.find_exif()
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/exifread/heic.py", line 229, in find_exif
    meta = self.expect_parse('meta')
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/exifread/heic.py", line 122, in expect_parse
    return self.parse_box(box)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/exifread/heic.py", line 133, in parse_box
    probe(box)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/exifread/heic.py", line 155, in parse_meta
    psub(box)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/exifread/heic.py", line 221, in parse_iloc
    extent_length = self.get_int(box.length_size)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/exifread/heic.py", line 74, in get_int
    return self.get32()
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/exifread/heic.py", line 58, in get32
    return struct.unpack('>L', self.get(4))[0]
struct.error: unpack requires a buffer of 4 bytes

The script was run on MacOS Big Sur 11.1 using Python 3.8.6 and ExifRead 2.3.1 from MacPorts.

Not sure what's going on, but it didn't like this hdlr thing.
DEBUG HEIC: skipping <box 'hdlr'>

Was able to get past the error with this inside of get_parser in heic.py.
        except (IndexError, KeyError) as err:
            #raise NoParser(box.name) from err
            self.skip(box)

and get exif data out
...
INFO EXIF LensMake (ASCII): Apple
INFO EXIF LensModel (ASCII): iPhone XR back camera 4.25mm f/1.8
INFO EXIF LensSpecification (Ratio): [17/4, 17/4, 9/5, 9/5]
INFO EXIF MakerNote (Undefined): [65, 112, 112, 108, 101, 32, 105, 79, 83, 0, 0, 1, 77, 77, 0, 25, 0, 1, 0, 9, ... ]
INFO EXIF MeteringMode (Short): Pattern
INFO EXIF OffsetTime (ASCII): Z
...


[Bug Report] The table row-style callback function not working after v2.12.0

Element UI version
2.13.0
OS/Browsers version
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Safari/537.36
Vue version
2.6.0
Reproduction Link
https://codepen.io/bigplum/pen/dyYGYYL
Steps to reproduce
Set the row-style property and callback:
  <el-table
    :data="tableData"
    :row-style="logRowStyle">

      logRowStyle({ row, rowIndex }) {
        return 'color:red';
      }

What is Expected?
The table row text color should all be red.
What is actually happening?
Those text are all not changed by row-style function.
If change the element ui version to 2.12.0, the row-style do the right thing that all texts show red color.

OK, I read the release log, and there is an update about the row-style function. It should return an object not string. The string could work in elder version, but not in 2.13 and after.


differ: fix deadlock on commit error

In https://github.com/moby/buildkit/issues/960 differ error is produced that was fixed in https://github.com/containerd/continuity/pull/140 . When this error was reached the writer was not properly released resulting a "locked" message for next invocations. This PR fixes the line involved so the error does not get masked, and two other cases where errors would have also been swallowed previously.
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

LGTM


[Android] [BugBash] Container.SelectAction.json

Container.SelectAction.json
Tooltip works only for the container with Emphasis link. The card has three tooltips one for each container.

Addressing this issue is not currently on our roadmap, so closing. Please feel free to continue the conversation in this issue for future consideration.


When is Gen-next coming out?

Last commit was jan19, is it coming out ever?

The Gen-NEXT mod is always available in the PS main server via challenges.
Please, read its README to find out more about it.


Failed: unable to run hubot-rocketchat-boilerplate | UnhandledPromiseRejectionWarning: Error: Asteroid connection timeout | ERROR Unable to connect: {}

can some explain why throwing this error
hubot@staging-rocket:~/hubot-rocketchat-boilerplate$ bin/hubot
audited 345 packages in 2.343s
found 1 low severity vulnerability
run npm audit fix to fix them, or npm audit for details
body-parser deprecated undefined extended: provide extended option node_modules/hubot/src/robot.js:445:21
[Thu Sep 27 2018 12:41:09 GMT+0000 (UTC)] INFO [startup] Rocket.Chat adapter in use
[Thu Sep 27 2018 12:41:09 GMT+0000 (UTC)] INFO [startup] Respond to name: Hubot
[Thu Sep 27 2018 12:41:09 GMT+0000 (UTC)] INFO [startup] Respond to alias: mybotuser
[Thu Sep 27 2018 12:41:09 GMT+0000 (UTC)] INFO [connect] Connecting { username: 'mybotuser',
password: 'mypassword',
ldap: false,
host: 'chatqa.imobisoft.co.uk',
useSsl: true,
timeout: 20000,
rooms: [ 'general' ],
allPublic: false,
dm: false,
livechat: false,
edited: false,
integrationId: 'js.SDK',
roomCacheMaxSize: 10,
roomCacheMaxAge: 300000,
dmCacheMaxSize: 10,
dmCacheMaxAge: 100000 }
[Thu Sep 27 2018 12:41:29 GMT+0000 (UTC)] INFO [connect] Timeout (20000)
[Thu Sep 27 2018 12:41:29 GMT+0000 (UTC)] ERROR Unable to connect: {}
[Thu Sep 27 2018 12:41:29 GMT+0000 (UTC)] ERROR undefined
[Thu Sep 27 2018 12:41:29 GMT+0000 (UTC)] ERROR Unable to login: {}
[Thu Sep 27 2018 12:41:29 GMT+0000 (UTC)] ERROR undefined
[Thu Sep 27 2018 12:41:29 GMT+0000 (UTC)] ERROR Unable to subscribe {}
(node:1667) UnhandledPromiseRejectionWarning: Error: Asteroid connection timeout
at Timeout._onTimeout (/home/hubot/hubot-rocketchat-boilerplate/node_modules/@rocket.chat/sdk/dist/lib/driver.js:94:25)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
at Timer.listOnTimeout (timers.js:290:5)
(node:1667) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1667) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Hello @jitendra-kr
I'm glad you resolved the issue, but could you be so kind and share the solution?

Check if it is possible to connect with provided login and password.
If you can log in with bot's credentials, check if the chat's host is accessible from bot's host.
If above didnt help, make sure websocket protocol is not blocked by any kind of proxy.

@p-hash thanks for the reply.
I have installed bot in my local host(running hubot.cmd from here using bat file (instead of .env) as mine is windows os) and i would be able to connect to that through browser and postman and getting responses but not from CLI when running hubot.cmd command
How to check this -->[ make sure websocket protocol is not blocked by any kind of proxy.]

I am facing similar issue. Please share the resolution

same issue here
in .env :: export ROCKETCHAT_USESSL=true
in log :: useSsl: False
...
so :: export ROCKETCHAT_URL="https://mydomain.com"
( rather than :: export ROCKETCHAT_URL=mydomain.com )
and ... voilà

Not sure if this is really the best solution but for me it was good enough to allow also self signed certificates with another environment variable NODE_TLS_REJECT_UNAUTHORIZED=0
after setting that variable the connection worked just fine

@rdgx Solution works.

@rdgx I don't have SSL enabled, so in .env it is set to false and in in log it is coming the same, so what could be the reason?

Did u solve that?

@rdgx I don't have SSL enabled, so in .env it is set to false and in in log it is coming the same, so what could be the reason?

Did u solve that?


I am using Kibana 5, when you plug in support

I am using Kibana 5, when you plug in support

@ytc301 no plans for this plugin to support 5.x at this time, sorry!


Add NavBar to Team Page

Self Explanatory

i want to work on this issue under jwoc

I want to work on this issue under JWOC


Installer Packages vs. Compatibility List missmatch

Context
From my Point of view, in https://adoptium.net/supported-platforms/ is only Ubuntu Listed as Compatible OS - for DEB Based Operation Systems.
In https://adoptium.net/installation/linux/ is Debian listed as possible "DEB Based" OS.
What is correct? Seems to be a mismatch in your website.
Thank you very much for clarify!

See: https://adoptium.net/installation/linux/
In particular this section in that doc:
See [Supported Platforms](https://adoptium.net/supported-platforms) for a list of our officially supported installers by Linux distribution / version. Other Linux distributions / versions are supported on a best-effort basis.


previewed

moved to fresh PR -
old structure in the other PR
#2135

This fixes #1995

Moved the PR to this one - didn't see the duplicate in time 🤦
#2350


Is this abandoned?

Seeing a meaningful amount of activity from the community in issues and pull requests. Not seeing a ton of responsiveness from folks who can actually merge and maintain the library. Just a friendly nudge / check-in! ❤🔥

I have created my fork https://github.com/ModyQyW/vite-plugin-eslint2. Hope this helps.


Format errors; Restructure main

@Devcon4 So we've got a problem: Handlers, like these, cannot return anything, even nil, which kinda breaks your error handling schema. In the meantime, I just log them and move on, as those handlers won't encounter panic-worthy errors.
Also, the errors package you're using is out of date, I'll look into the newer method. It looks like it's almost identical but doesn't use that package.

@jakobottar That is fine, those run in a different context anyways so it doesn't even make sense for them to throw a panic. They should log the error then close quietly. As far as pkg/errors it is unfortunate, neither the standard library replaces what it's goal is nor is the package still maintained. I would replace it with fmt.Errorf("My wrapper message: %w", err.Error()) or make a simple helper like this.
func Wrapf(err error, format string, args ...interface{}) error {
	if err == nil {
		return nil
	}

	return fmt.Errorf(fmt.Sprintf(format, args...)+": %w", err)
}

This is basically a simplified version of errors.wrapf, the source for .wrapf and fmt.Errorf is easy to read and do basically the same thing if you want to make your own. Cool thing with go is it's very easy to read the standard library code and is what everyone uses as an example of good go code.
I would also consider using a Structured Logging library like zerolog or zap. In cases where you want to log extra info when an error happens (timestamp, interfaces, etc) you wouldn't want that to be wrapped in an error. Instead you should have a simple error which is handled but log an error event with all of that info.

too old, closing in favor of new error-handling branch


Allow filtering exported metrics in OperatorConfig

Add an OperatorConfig section to set the --export.match flag.
Fix CRD YAML generation concatenation
Ensure that e2e tests are truly e2e by default (verify writes to GCM)

Running GCM validation with make test doesn't make sense as the provided projectID etc. aren't real.


Lodash function are imported all at once

more info in PR #92

Can you give any response please? The size of my application bundle is critical for me and fixing this issue will help me to reduce it significantly.

Yup. I'll pull in your PR.


Ntueeplus 15. Improve Appearance of Column Text

What is this PR for?

indent every subsection
reduce white and gray part and it won't change in different view percent!
delete subtitle's subtitle
What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
improvement
Todos

[ ] - No

What is the Jira issue?

https://ntueeplus.atlassian.net/browse/NTUEEPLUS-15
Screenshots (if appropriate)
150%:

100%:

@featherchen
here

@vwvwMM  Thanks for contribution, I just wonder if we can delete the white place at the leftest of 100%, and if we can let the indent words align to the words below.

@vwvwMM Thanks for contribution, I just wonder if we can delete the white place at the leftest of 100%, and if we can let the indent words align to the words below.

@featherchen you say the area between the number title and the content?

@vwvwMM  Remember to modify the title to fit the format.

@featherchen you say the area between the number title and the content?

@noidname01  Actually I mean that the space out of the leftest sidebar, but I think the space you mentioned is too big either.

Oh @vwvwMM  remember to rebase the repo and solve the conflict.

@vwvwMM Thanks for contribution, I just wonder if we can delete the white place at the leftest of 100%, and if we can let the indent words align to the words below.
do you mean this?

@vwvwMM Thanks for contribution, I just wonder if we can delete the white place at the leftest of 100%, and if we can let the indent words align to the words below.

@featherchen you say the area between the number title and the content?

that space is for longer title, i'm not sure if it can auto adjust the space base on the length of title

@vwvwMM Thanks for contribution, I just wonder if we can delete the white place at the leftest of 100%, and if we can let the indent words align to the words below.

@featherchen you say the area between the number title and the content?

that space is for longer title, i'm not sure if it can auto adjust the space base on the length of title

I think we won't have too long title, and I want to take a look what will it look like. I mean reduce that area.

@vwvwMM Thanks for contribution, I just wonder if we can delete the white place at the leftest of 100%, and if we can let the indent words align to the words below.

@featherchen you say the area between the number title and the content?

that space is for longer title, i'm not sure if it can auto adjust the space base on the length of title

I think we won't have too long title, and I want to take a look what will it look like. I mean reduce that area.

then the statement about maximum words i previous write in the PR will change(i just want to remind this, i'll reduce the space

@noidname01  i let the title be aligned-center. It looks great i think. How about u?

@noidname01 i let the title be aligned-center. It looks great i think. How about u?

Cool, But I think the white area is still a little bit too more.

@noidname01 i let the title be aligned-center. It looks great i think. How about u?

Cool, But I think the white area is still a little bit too more.
where?

@noidname01 i let the title be aligned-center. It looks great i think. How about u?

Cool, But I think the white area is still a little bit too more.
where?

Title


feature generate ExprId from 0 for each statement

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221015035609_clickbench_pr_29551.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 38.75 seconds
load time: 583 seconds
storage size:<PHONE_NUMBER>2 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221018095243_clickbench_pr_30408.html


is Puma + Grape not threadsafe?

my online Grape Project change unicorn to puma deploy.
so much users get other users data from api.
develop by Rails 4.2 + puma 3.0.1 + Grape 0.9.0.
some code like as:
base.rb
module V3
  class Base < Grape::API
    helpers V3Helpers

    include V3::Photos
  end
end

v3_helpers.rb
def current_user
return @current_user if defined? @current_user

@current_user = User.find(params[:uid])
end

photos.rb
module V3
  module Photos
    extend ActiveSupport::Concern

    included do

      resources :photos do

        get do
          photos = Photo.where(user_id: current_user.id)
          photos.to_json
        end

      end

    end
end
end

is my code not threadsafe ?

Are you worried specifically about @current_user? That's not automatically threadsafe. Grape or Puma won't take locks on that. That said, I am not sure what @current_user actual scope is, it might be executed in the context of a block that belongs to the current executing thread. So you might be ok.

Finally, whatever we find should be documented.

I found it difficult to trace the instantiation of middleware and helpers in Grape's internals, but a simple test of self.object_id from within each of (a) a middleware class invoked by use and (b) a helper class invoked by helpers confirmed that the calling context is that of a different object on each request. This would point to instance variables (like in the above example) being isolated to the request and thus safe to use.
It's possible there are other thread-safety issues I'm missing. Happy to research more if anyone can point me to the relevant code.

Maybe use warden to attach current_user to fix this ?

@wxianfeng have you solved/figure out this issue? I want to use grape with puma in my project,but thread safe is a serious problem.

@MoonShining Just to be clear, we're using Grape successfully with Puma on a large scale production application just fine. There're some questions around thread safety that seem to indicate that there's potential for non-thread-safe behavior, but this issue is still open to make sure we aren't missing anything.

Re-reading this thread I am happy with @joeyAghion's answer and am going to close this.

this issue is not Grape problem
at last i found active_model_serializers problem, am use not release code,  it's use class variables, not threadsafe !
gem 'active_model_serializers', git: 'https://github.com/rails-api/active_model_serializers.git', ref: '2df8804'
active_model_serializers/lib/active_model/serializer.rb
def read_attribute_for_serialization(attr)
  if self.class._serializer_instance_method_defined?(attr)
    send(attr)
  elsif self.class._fragmented
    self.class._fragmented.read_attribute_for_serialization(attr)
  else
    object.read_attribute_for_serialization(attr)
  end
end