META: Pull request volume too high

@philsquared has a lot of work on his plate.  @philsquared, have you considered pulling in additional maintainers to keep up with the volume of PRs?

I would love to!
There are a handful of very helpful, responsive and smart individuals in the community who frequently step in respond to questions and issues - for which I'm very grateful.
But keeping up with PRs is a different proposition.
What I'm really lacking right now is better testing infrastructure (ironically) - in particular running on multiple versions of GCC, Clang and VC++ - preferably on multiple platforms.
Personally I develop in Xcode (Clang) on my Mac, but tend to give it the most use during the day on a Windows project (currently VS2013). There are Travis builds for Clang and GCC - but only specific fixed versions (rarely the ones that seem to have all the problems, it seems).
Despite all that sometimes quite embarrassing regressions slip through if I don't review everything in excruciating detail (and even then).
A more comprehensive set of environments would be a huge help - and would let me - or some other trusted maintainers - accept PRs much more quickly.
My biggest bottleneck is that I do most of my Catch work on my commute (when I'm not preparing talks, writing blog posts, learning new languages or working on iOS projects) - with intermittent connectivity.  If anyone was in a position to help there it would be transformative!

As someone who works in test automation, you are describing a familiar problem.  Getting the right systems set up in the right way to build/test the right build configurations across all "supported" platforms is certainly a challenge, especially when you might have to deal with "non-free" software like Windows, where you need licenses to even run the operating system.
Is there any "requirements" written down anywhere about what sorts of things would be most helpful?  Is it Visual Studio versions?  Static analysis?  Build permutations? Virtualization?
Figuring this kind of stuff out is basically my day job, and I'd be happy to help you figure out a path forward.

There are some free hosting options from Microsoft Azure; maybe those would work for testing a few versions of Visual Studio.
If could run some service on my Windows machine that quietly assists with testing Catch in the background, I probably would.  It would be like SETI@Home but for software testing.  Just a random thought.

cough AppVeyor cough
They have a few versions of VS to run your tests with. And it's free.

Thanks for the replies.
Just to be clear the issue is one of time and connectivity - not services and platform availability (although I am open to suggestions there).
To give you an idea: it just took my five minutes to open this page and whether I can post this response straight away or will have to wait another 10-20 minutes I don't even know yet. Yesterday, on my way home, I could't get a single page downloaded!
So, for me, working with any cloud hosted environments is just not possible.
If anyone else would be happy to do that, though - at least to do most of the work of getting something set up - that's what would really help.
As for Windows licenses: Azure might work out to be a good option. But I also have a Mac Mini sitting idle at home that can run Windows in a VM (and I have licenses for XP and Windows 7, at least). I can also run different flavours of Linux in a VM (which is something I started doing on my laptop but any time I get stuck it just takes too long to be able to work stuff out without a reliable connection).
I can run TeamCity on my Mac Mini - which, apparently, can interact with local VMs - as well as Azure and AWS.
If anyone wants to volunteer I'd be happy to open up VNC ports to my Mac Mini if it would help.
If you have a preference for other cloud solutions I'm just as happy.
Next time I have a stable connection I'll take a look at AppVeyor (I currently can't reach it).

@michaelbprice - you asked about "requirements".
I'd like to be able to use as many representative OSes as possible (Windows 7 & 10, OS X - latest is fine - as I say I can provided that, and as many popular Lines as people are happy to set up and maintain).
On Windows I'd like to test with as many as possible of: VS2008 (still used by many), 2010, 2012, 2013, 2015. Ideally gcc/ clang, too. Any other compilers (e.g. Intel) a bonus.
On Mac & Linux a representative range of GCCs and Clangs in common use is the obvious requirement. Exactly which versions I couldn't say - the main thing would be getting it set up to run multiple versions (this is where I've got stuck before - even manually switching GCC versions on my Mac seems to be a lot more work than I would have expected). I would imagine that once it can work with 2-3 versions, adding more as required (e.g. a bug is filed against a specific version) would be relatively straightforward.
In terms of what needs to be run I have a reasonable start at a test suite. It can certainly do with being extended (in particular exercising more of the command line options - and combinations thereof). But I can do that here. I might still need to do some more work to make it runnable in a platform independent way. It does require Python, but I doubt that is an issue.
The way it works (currently) is to run the CatchSelfTest project with a range of command line options (at the moment it's mostly different reporters with some combinations of only successful tests, as well as (deliberately) failing tests). It captures the output in a text file, strips out some volatile information: e.g. line numbers and memory addresses, then does a textual diff against baselines.
As I say this can (and should) be extended in at least a couple of ways: (1) more command line combinations and (2) using both the multiple and single-file versions (currently it only runs the multi file version).
I am, of course, open to other ways that this could be extended.
One opposing force here is that the regression-based approach can tend to be quite noisy with false positives because any change in the output - including just adding new tests - requires manually "approving" the changes. This is usually manageable enough, although sometimes can be quite subtle and I've let bugs in - even though they did show up - because they've slipped past in the noise. Any suggestions for doing better there would be welcome.

+1 for AppVeyor for Windows testing, I've seen it used to great effect here: https://github.com/nlohmann/json

@philsquared If there existed systems that would do all of this coverage for you, but you were unable to see the results without asking someone with access... would that be a non-starter for you?
@Lexmark has an interest in keeping this project going, but we aren't really set up to expose our build infrastructure out to the public-at-large.  Of course, there's also the matter of whether or not you want your processes to depend so heavily on a corporation over which you have little-to-no control over.

It's been a while since this discussion started but this is a good time to reinvigorate it, I think.
As discussed here: http://www.levelofindirection.com/journal/2016/12/22/on-joining-jetbrains-1.html my circumstances have changed and (a) I should have more time for Catch (despite a slow start there) and (b) when I am working on it it's in a decent environment with stable internet now!
Additionally, I'm pleased to say that @horenmar has become a key maintainer and has been generously investing his time in helping to work through the backlog (thanks again, @horenmar!).
There's a way to go but it's going in the right direction now.
One of my focuses now is to get the test environments I mentioned before up and running. I've already done some work to make my release scripts more portable - as well as making CMake more useful.
I'm planning on getting a TeamCity server up and running, which can interact with build agents on different platforms. This was my plan even before I joined JetBrains - but makes even more sense now :-)
That doesn't preclude extending the use of Travis further, or using AppVeyor - but it feels like I should have more control over my own TC instance (especially after the issues with the Travis builds last year). That could just be my lack of experience with Travis or AV - feel free to try to persuade me otherwise.

I don't think there is a reason not to have Travis/AppVeyor as well as TC. To me the benefits of Travis and AppVeyor is that you get a free* CI service and CI is an incredibly useful thing (assuming you have good tests). You also don't have to care about standing up your own buildhosts, getting proper licences etc.

Free as in money, they can eat up a lot of time while trying to work around their pecularities and figure out their configurations.

As an aside: as someone who has set up AppVeyor many times, I can safely say that it works extremely well. The support from both them and Travis is really awesome, too.

The CI situation has improved (larger coverage on Travis, including C++11 builds)  and is still improving (Cygwin on AppVeyor is coming soon, TeamCity is also slowly moving along), and the backlog is decreasing, so I am going to close this.


Container with links cant startup in bridge network mode "Could not get container for xxx"

Rancher Version:

1.1.4
rancher/agent:v1.0.2

Docker Version:

1.12.2

OS and where are the hosts located? (cloud, bare metal, etc):

bare metal ubuntu 16.04 and Virtuozzo7 centos7 same failure

Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)

single node rancher
internal DB

Environment Type: (Cattle/Kubernetes/Swarm/Mesos)

Cattle

Steps to Reproduce:

first container -> addService image: ubuntu:14.04.3 Network:Bridge

second container -> addService image: ubuntu:14.04.3 Network:Bridge Link to first container

first container is running

second container cant start: "Could not get container for 13b5b54a-547c-48c8-8ea7-8905d55e7feb"

In a managed network it runs without problems

Results:
2016-11-17 08:58:24,982 ERROR agent [139919545746288] [event.py:112] Error in request : fb1c5074-ccbb-4a92-86ca-a9f6d27efd5b
Traceback (most recent call last):
File "/var/lib/cattle/pyagent/cattle/agent/event.py", line 95, in _worker_main
resp = agent.execute(req)
File "/var/lib/cattle/pyagent/cattle/agent/init.py", line 15, in execute
return self._router.route(req)
File "/var/lib/cattle/pyagent/cattle/plugins/core/event_router.py", line 13, in route
resp = handler.execute(req)
File "/var/lib/cattle/pyagent/cattle/agent/handler.py", line 34, in execute
return method(req=req, **req.data.dict)
File "/var/lib/cattle/pyagent/cattle/plugins/docker/compute.py", line 529, in instance_activate
self._do_instance_activate(instance, host, progress)
File "/var/lib/cattle/pyagent/cattle/plugins/docker/compute.py", line 607, in _do_instance_activate
progress)
File "/var/lib/cattle/pyagent/cattle/plugins/docker/compute.py", line 653, in _create_container
container = client.create_container_from_config(config, name)
File "/var/lib/cattle/pyagent/dist/docker/api/container.py", line 130, in create_container_from_config
return self._result(res, True)
File "/var/lib/cattle/pyagent/dist/docker/client.py", line 150, in _result
self._raise_for_status(response)
File "/var/lib/cattle/pyagent/dist/docker/client.py", line 146, in _raise_for_status
raise errors.APIError(e, response, explanation=explanation)
APIError: 500 Server Error: Internal Server Error ("Could not get container for 13b5b54a-547c-48c8-8ea7-8905d55e7feb")

@rdechow-magari - I verified that this is indeed a problem in 1.1.4 version of Rancher.  But I also retested in our master build and this has been fixed.  So when 1.2.0 is available please upgrade.  I'm going to close it.  If you find you are having problem after our next release, please re-open and let me know.


⚠ Bofrost.be has degraded performance

In 650ef6a, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 954 ms

Resolved: Bofrost.be performance has improved in 5f5e92b after 20 minutes.


fix: typings of flat operator

Wait, these should work with both Iterator and Iterable right? I'll need to make an adjustment.

That's great!
But I had to fix incorrect export for Descr ;)
https://github.com/vitaly-t/iter-ops/commit/57cd0758733361773a413018d1324b9b26ee034b

@RebeccaStevens I just had to refactor Decr...

Renamed it into Decrement
Exported it from the root

This was done because you added the use of the type for operator flat, but you forgot to export such a type from the library, and so as a result we could not generate docs anymore. And if we include such types into docs, they better have some meaningful name.

I didn't intend for it to be a public type. It's a helper type used by the Flatten type. The outside world shouldn't need to know of its existence.

I'm not sure right now how to exclude those. Tags like @hidden or @ignore for some reasons do not work there...


Form in article not migrated

Register sub-domain form here not added:  https://community.superoffice.com/en/technical/documentation/identity-management/how-to/federated-sign-in-guide/register-idp/

created a "copy" of the register sub-domain form and placed it in a container called forms in the technical club. https://community.superoffice.com/en/technical/forms/register-sub-idp/


URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).
Fixed URLs
Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

http://maven.apache.org/xsd/maven-4.0.0.xsd with 3 occurrences migrated to:
https://maven.apache.org/xsd/maven-4.0.0.xsd (https result 200).
http://repo.spring.io/libs-milestone with 2 occurrences migrated to:
https://repo.spring.io/libs-milestone (https result 302).
http://repo.spring.io/libs-milestone-local with 4 occurrences migrated to:
https://repo.spring.io/libs-milestone-local (https result 302).
http://repo.spring.io/libs-release with 2 occurrences migrated to:
https://repo.spring.io/libs-release (https result 302).
http://repo.spring.io/libs-snapshot-local with 4 occurrences migrated to:
https://repo.spring.io/libs-snapshot-local (https result 302).
http://repo.spring.io/release with 2 occurrences migrated to:
https://repo.spring.io/release (https result 302).

Ignored
These URLs were intentionally ignored.

http://maven.apache.org/POM/4.0.0 with 6 occurrences
http://www.w3.org/2001/XMLSchema-instance with 3 occurrences

Closing this PR as this project is no longer actively developed.


Abbott Free Style Lite implementation

We are publishing the Abbott Free Style Lite driver implementation for your consideration.

I've made a number of changes and merged in other changes from master. Can you merge this branch and check that everything is still working on your side as well:
https://github.com/tidepool-org/chrome-uploader/tree/ioet-freeStyleLite
We can then finalise the review and merge this PR, instead of me having to create another PR.

ok, we have tested the device now and it works properly :smile:

I'm closing this PR, as I've now moved these changed to a new PR in #158. Thanks guys!


Generating Pdf is long

Hello
Generating Pdf of 4 pages take a long time with Firefox not with Chrome.
Any ideas ?
Thks

check your image references and js errors. if there is a broken image reference it won't load until it reaches the timeout.


Example unclear in Pod Overhead concept

This is a Bug Report

Problem:
In Pod Overhead, the page uses kata-fc (presumably Kata Containers with the Firecracker VMM), but doesn't explain where that name comes from or how that's associated with overhead.
Proposed Solution:
Either:

change the example to use a fictional hypervisor
explain where the name comes from

and in either case, explain that it's the runtime's overhead that needs accounting for (not the app's overhead).
Page to Update:
https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/

Additional Information:
/language en

Aside: maybe https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/ belongs inside https://kubernetes.io/docs/concepts/workloads/ but with a clear signpost to it from the pages about resource management (ResourceQuota etc) and about scheduling.

I will try to solve this issue.

/assign will raise a PR this

I will raise a PR for this
/assign

/assign me
I will look into it

/triage accepted
/priority backlog

Raised PR in : #45454

Raised PR in - #45470

The issue is resolved
we can close this issue as PR got merged

closing the issue as it get resolved in ref of PR #45454
/close


chore(master): release 8.0.0

:robot: I have created a release beep boop
8.0.0 (2024-09-13)
⚠ BREAKING CHANGES

add act (#942)

Features

add act (#942) (09f22ee)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/bee-js/releases/tag/v8.0.0 :sunflower:

Release v8.0.0 addresses this.


add aws profile support

what

add support for AWS profile in remote-state

why

to allow support for specifying an AWS Profile name instead of a role_arn to access the s3 backend

/test all


Cannot upload files into an Empty Directory

Hello,
I noticed when you create a new directory, and try to upload files within it, you receive an error in the JS console. Thus, the upload popup never appears. See a screenshot below:

Temporary Fix
Simply create a text file in your directory, upload the files, and then delete the text file 😄

Hello @torch2424! Thanks for the report. I'll try to solve this ASAP.


FancyZones bug on 2 monitors

Microsoft PowerToys version
0.45.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones, FancyZones Editor
Steps to reproduce
i have 2 monitors, and different layouts for each one. i've set "priority grid" on first monitor and 2 columns on second monitor, but every time i restart pc / log on, it's reset and it's just priority grid on both monitors

Besides, i tried to reinstall powertoys, disable/enable fancyzones and etc. and nothing worked.
I tried to change layouts but it keeps resetting.
✔ Expected Behavior
both monitors keep their own layout (first monitor has priority grid and second has 2 columns)
❌ Actual Behavior
both monitors have priority grid
Other Software
_No response
FZEditorCrashLog.txt
_

Duplicate of https://github.com/microsoft/PowerToys/issues/13069


Video completely distorted and glitchy

When using SceneKitVideoRecorder on an ARSCNView, the video is completely distorted.
This is happening on my iPhone 7 Plus running Beta 10.

Wow. Strange yet cool. Will update iOS now to see whats wrong.

Tested on iPhone SE iOS 11 Beta 10. Can’t reproduce.

Weird, I've even created a new AR Kit project and I still see the error. What device were you using?

I was on iPhone SE
Can you share your setup options and pod version?

I was testing on an iPhone 7 Plus with SceneKitRecorder 1.0.3. I created a new Xcode Project with the ARKit template.

I've just tested the same project on my iPad Pro. The video is not distorted, but it is really choppy.

Can you test this issue with 1.2.0 please?

As you showed there is a bug in 1.2.0
Can you try this with 1.1.0 until i fix 1.2.0 please

The issue still persists with 1.1.0

Please try with sample configuration. Don't forget to add prepare() on viewDidAppear

I've tried the sample configuration, but the video still looks like that.

I have the same issue. I'm using an iPhone 6S on iOS 11, I think I was on the 1st beta. I'm currently updating to the last one (beta 10). I'll retry after and tell you.

I updated my iPhone 6S to iOS 11 beta 10. I retested and I'm still having the same issue.

I have a strange theory and a really bad way to test it.
@LeonardRockstar @mariedm
Can you paste the following code on line 21 in PixelBufferFactory.swift just under let destinationTexture = currentDrawable.texture
        case .invalid: print("invalid"); break;
        case .a8Unorm: print("a8Unorm"); break;
        case .r8Unorm: print("r8Unorm"); break;
        case .r8Unorm_srgb: print("r8Unorm_srgb"); break;
        case .r8Snorm: print("r8Snorm"); break;
        case .r8Uint: print("r8Uint"); break;
        case .r8Sint: print("r8Sint"); break;
        case .r16Snorm: print("r16Snorm"); break;
        case .r16Uint: print("r16Uint"); break;
        case .r16Sint: print("r16Sint"); break;
        case .r16Float: print("r16Float"); break;
        case .rg8Unorm: print("rg8Unorm"); break;
        case .rg8Snorm: print("rg8Snorm"); break;
        case .rg8Uint: print("rg8Uint"); break;
        case .rg8Sint: print("rg8Sint"); break;
        case .a1bgr5Unorm: print("a1bgr5Unorm"); break;
        case .abgr4Unorm: print("abgr4Unorm"); break;
        case .bgr5A1Unorm: print("bgr5A1Unorm"); break;
        case .r32Sint: print("r32Sint"); break;
        case .r32Float: print("r32Float"); break;
        case .rg16Unorm: print("rg16Unorm"); break;
        case .rg16Snorm: print("rg16Snorm"); break;
        case .rg16Uint: print("rg16Uint"); break;
        case .rg16Sint: print("rg16Sint"); break;
        case .rg16Float: print("rg16Float"); break;
        case .rgba8Unorm: print("rgba8Unorm"); break;
        case .rgba8Unorm_srgb: print("rgba8Unorm_srgb"); break;
        case .rgba8Snorm: print("rgba8Snorm"); break;
        case .rgba8Uint: print("rgba8Uint"); break;
        case .rgba8Sint: print("rgba8Sint"); break;
        case .bgra8Unorm: print("bgra8Unorm"); break;
        case .bgra8Unorm_srgb: print("bgra8Unorm_srgb"); break;
        case .rgb10a2Unorm: print("rgb10a2Unorm"); break;
        case .rgb10a2Uint: print("rgb10a2Uint"); break;
        case .rg11b10Float: print("rg11b10Float"); break;
        case .rgb9e5Float: print("rgb9e5Float"); break;
        case .bgr10a2Unorm: print("bgr10a2Unorm"); break;
        case .bgr10_xr: print("bgr10_xr"); break;
        case .bgr10_xr_srgb: print("bgr10_xr_srgb"); break;
        case .rg32Sint: print("rg32Sint"); break;
        case .rg32Float: print("rg32Float"); break;
        case .rgba16Unorm: print("rgba16Unorm"); break;
        case .rgba16Snorm: print("rgba16Snorm"); break;
        case .rgba16Uint: print("rgba16Uint"); break;
        case .rgba16Sint: print("rgba16Sint"); break;
        case .rgba16Float: print("rgba16Float"); break;
        case .BGRA10_XR: print("BGRA10_XR"); break;
        case .bgra10_XR_sRGB: print("bgra10_XR_sRGB"); break;
        case .rgba32Sint: print("rgba32Sint"); break;
        case .rgba32Float: print("rgba32Float"); break;
        case .pvrtc_rgb_2bpp_srgb: print("pvrtc_rgb_2bpp_srgb"); break;
        case .pvrtc_rgb_4bpp: print("pvrtc_rgb_4bpp"); break;
        case .pvrtc_rgb_4bpp_srgb: print("pvrtc_rgb_4bpp_srgb"); break;
        case .pvrtc_rgba_2bpp: print("pvrtc_rgba_2bpp"); break;
        case .pvrtc_rgba_2bpp_srgb: print("pvrtc_rgba_2bpp_srgb"); break;
        case .pvrtc_rgba_4bpp: print("pvrtc_rgba_4bpp"); break;
        case .pvrtc_rgba_4bpp_srgb: print("pvrtc_rgba_4bpp_srgb"); break;
        case .eac_r11Snorm: print("eac_r11Snorm"); break;
        case .eac_rg11Unorm: print("eac_rg11Unorm"); break;
        case .eac_rg11Snorm: print("eac_rg11Snorm"); break;
        case .eac_rgba8: print("eac_rgba8"); break;
        case .eac_rgba8_srgb: print("eac_rgba8_srgb"); break;
        case .etc2_rgb8: print("etc2_rgb8"); break;
        case .etc2_rgb8_srgb: print("etc2_rgb8_srgb"); break;
        case .etc2_rgb8a1: print("etc2_rgb8a1"); break;
        case .etc2_rgb8a1_srgb: print("etc2_rgb8a1_srgb"); break;
        case .astc_5x4_srgb: print("astc_5x4_srgb"); break;
        case .astc_5x5_srgb: print("astc_5x5_srgb"); break;
        case .astc_6x5_srgb: print("astc_6x5_srgb"); break;
        case .astc_6x6_srgb: print("astc_6x6_srgb"); break;
        case .astc_8x5_srgb: print("astc_8x5_srgb"); break;
        case .astc_8x6_srgb: print("astc_8x6_srgb"); break;
        case .astc_8x8_srgb: print("astc_8x8_srgb"); break;
        case .astc_10x5_srgb: print("astc_10x5_srgb"); break;
        case .astc_10x6_srgb: print("astc_10x6_srgb"); break;
        case .astc_10x8_srgb: print("astc_10x8_srgb"); break;
        case .astc_10x10_srgb: print("astc_10x10_srgb"); break;
        case .astc_12x10_srgb: print("astc_12x10_srgb"); break;
        case .astc_12x12_srgb: print("astc_12x12_srgb"); break;
        case .astc_4x4_ldr: print("astc_4x4_ldr"); break;
        case .astc_5x4_ldr: print("astc_5x4_ldr"); break;
        case .astc_5x5_ldr: print("astc_5x5_ldr"); break;
        case .astc_6x5_ldr: print("astc_6x5_ldr"); break;
        case .astc_6x6_ldr: print("astc_6x6_ldr"); break;
        case .astc_8x5_ldr: print("astc_8x5_ldr"); break;
        case .astc_8x6_ldr: print("astc_8x6_ldr"); break;
        case .astc_8x8_ldr: print("astc_8x8_ldr"); break;
        case .astc_10x5_ldr: print("astc_10x5_ldr"); break;
        case .astc_10x6_ldr: print("astc_10x6_ldr"); break;
        case .astc_10x8_ldr: print("astc_10x8_ldr"); break;
        case .astc_10x10_ldr: print("astc_10x10_ldr"); break;
        case .astc_12x10_ldr: print("astc_12x10_ldr"); break;
        case .astc_12x12_ldr: print("astc_12x12_ldr"); break;
        case .r16Unorm: print("r16Unorm"); break;
        case .rg8Unorm_srgb: print("rg8Unorm_srgb"); break;
        case .b5g6r5Unorm: print("b5g6r5Unorm"); break;
        case .r32Uint: print("r32Uint"); break;
        case .rg32Uint: print("rg32Uint"); break;
        case .rgba32Uint: print("rgba32Uint"); break;
        case .bc1_rgba: print("bc1_rgba"); break;
        case .bc1_rgba_srgb: print("bc1_rgba_srgb"); break;
        case .bc2_rgba: print("bc2_rgba"); break;
        case .bc2_rgba_srgb: print("bc2_rgba_srgb"); break;
        case .bc3_rgba: print("bc3_rgba"); break;
        case .bc3_rgba_srgb: print("bc3_rgba_srgb"); break;
        case .bc4_rUnorm: print("bc4_rUnorm"); break;
        case .bc4_rSnorm: print("bc4_rSnorm"); break;
        case .bc5_rgUnorm: print("bc5_rgUnorm"); break;
        case .bc5_rgSnorm: print("bc5_rgSnorm"); break;
        case .bc6H_rgbFloat: print("bc6H_rgbFloat"); break;
        case .bc6H_rgbuFloat: print("bc6H_rgbuFloat"); break;
        case .bc7_rgbaUnorm: print("bc7_rgbaUnorm"); break;
        case .bc7_rgbaUnorm_srgb: print("bc7_rgbaUnorm_srgb"); break;
        case .pvrtc_rgb_2bpp: print("pvrtc_rgb_2bpp"); break;
        case .eac_r11Unorm: print("eac_r11Unorm"); break;
        case .astc_4x4_srgb: print("astc_4x4_srgb"); break;
        case .gbgr422: print("gbgr422"); break;
        case .bgrg422: print("bgrg422"); break;
        case .depth16Unorm: print("depth16Unorm"); break;
        case .depth32Float: print("depth32Float"); break;
        case .stencil8: print("stencil8"); break;
        case .depth24Unorm_stencil8: print("depth24Unorm_stencil8"); break;
        case .depth32Float_stencil8: print("depth32Float_stencil8"); break;
        case .x32_stencil8: print("x32_stencil8"); break;
        case .x24_stencil8: print("x24_stencil8"); break;
      }```

This huge switch is because printing the enum or its rawValue didn't work. I am getting `bgra8Unorm_srgb` and my theory is that somehow yours is different and causing this psychedelic recording.

Just tried it, it keeps printing "invalid".

Interesting. Are you getting a whole video like this, or do you crash or do you have a video with one frame frozen?

I'm getting the whole video like that.

Another idea: can you try with 30fps video please. This is really hard to debug when i cant reproduce the issue

@mariedm are you using 6s or 6s plus?

Still looks the same when using 30fps.

@LeonardRockstar can you put the switch to SceneKitVideoRecorder.swift under line 74 ...frameBufferOnly = false
and also changing switch to
switch metalLayer.pixelFormat {

It prints bgra8Unorm_srgb

That looks correct. One more thing to try. Can you pass in a block to updateFrameHandler of SceneKitVideoRecorder and get an image from there to see if its the same with the video.

I don't know if I understand you correctly. The UIImage returned by PixelBufferFactory.make (and passed into updateFrameHandler) is also distorted, but looks a lot brighter than the video.

same issue

@GoodbyeCain can you please share your device, os version, pod version so we can check if a pattern is forming.

I’m using a regular 6S.
In PixelBufferFactory: the switch statement on metalLayer.pixelFormat prints invalid.
In SceneKitVideoRecorder: the switch statement on metalLayer.pixelFormat after framebufferOnly (line 64 for me) also prints invalid.

If I put a breakpoint on updateFrameHandler in SceneKitVideoRecorder to get the image, here's what I get (much more white, or brighter like @LeonardRockstar said):

After a lot of googling and presumptions I think there is something wrong with the colorSpace of the buffer provided. https://stackoverflow.com/questions/34913005/color-space-mapping-ycbcr-to-rgb the example here looks much like this problem. Will try to manually convert ycbcr to rgb if colorSpace is invalid

Love this repo, I am also getting the same issue on an iPhone 7+ running iOS 11 GM (15A372)

@sanboxapps thanks. Can you also try the script above please?

I just tried the code on an iPad pro (10", iOS 11 GM), and got the same result
as far as the switch statements I am getting invalid for both
I have tried with 30, and 60 fps it I am getting the same effect but with a slight difference in the colors from 30 to 60

Thanks alot for the input.

No problem 👍 please let me know if you need further information, I would be happy to help.

Can you guys try this after replacing line 46 on Options.swift
kCVPixelBufferPixelFormatTypeKey as String: NSNumber(value: kCVPixelFormatType_32BGRA),
with
kCVPixelBufferPixelFormatTypeKey as String: NSNumber(value: kCVPixelFormatType_420YpCbCr8BiPlanarVideoRange),

got this exception:
'_validateGetBytes:95: failed assertion rowBytes(1924) must be >= (2160).'
on this line
destinationTexture.getBytes(tempBuffer!, bytesPerRow: Int(bytesPerRow), from: region, mipmapLevel: 0)
in PixelBufferFactory

Hmm. Can you try adding        print(bytesPerRow, currentDrawable.layer.drawableSize.width, currentDrawable.layer.drawableSize) to PixelBufferFactory.swift under line #28         let bytesPerRow = CVPixelBufferGetBytesPerRow(pixelBuffer)  and one of the outputs please

I'm getting the same error as @sanboxapps.
The output is: 1932 1080.0 (1080.0, 1867.0)

I updated the pod, when calling startWriting() I got Error Domain=SceneKitVideoRecorder.SceneKitVideoRecorder.PreparationError Code=1 "(null)".
I readded both switch statements. The one in SceneKitVideoRecorder is now printing  bgra8Unorm_srgb(instead of invalid before).
Then in the Options file I changed kCVPixelFormatType_32BGRA to kCVPixelFormatType_420YpCbCr8BiPlanarVideoRange and still got the same error, I can't record.

@mariedm if you are seeing bgra8Unorm_srgb as pixelFormat I don't know why but it should be fixed for you. Can you run the demo project in the latest pod please.

I didn't manage to run the demo project but I recreated it. I could record and I have the audio (!) but the video is distorded.
The switch statement in SceneKitVideoRecorder prints bgra8Unorm_srgb and the one in PixelBufferFactory prints invalid.
If I change to 30 fps I get the same outputs.
If I change to kCVPixelFormatType_420YpCbCr8BiPlanarVideoRange in Options I get the same outputs + _validateGetBytes:95: failed assertion rowBytes(1156) must be >= (1500) in  PixelBufferFactory when it crashed on the line destinationTexture.getBytes(tempBuffer!, bytesPerRow: Int(bytesPerRow), from: region, mipmapLevel: 0).

Please try this when the video is colorful like above and share the output. Thanks all!
print(bytesPerRow, currentDrawable.layer.drawableSize.width, currentDrawable.layer.drawableSize) to PixelBufferFactory.swift under line #28 let bytesPerRow = CVPixelBufferGetBytesPerRow(pixelBuffer)

This is the output: 3008 750.0 (750.0, 1294.0).

@warrenm I found your answer about Metal Video Recording on StackOverflow. This issue looks like a corruption you wrote on SO. Can you help us solve it?

Sure. The texture whose bytes you're copying probably has a format of MTLPixelFormatRGB10A8_2P_XR10_sRGB or something. As I said very explicitly in my answer on SO, that snippet depends on the source format being MTLPixelFormatBGRA8Unorm. You'll either need to figure out how to set the pixel format of the CAMetalLayer underlying the Scene Kit view to have that format, or else run a conversion step (fragment shader, compute shader, vImage, etc.) that transforms the pixel data into the necessary format. Naively copying from the drawable texture into a pixel buffer isn't going to cut it in this case.

@warrenm Thank you very much for your guidance. It provided some perspective to try other solutions.
@mariedm @LeonardRockstar @sanboxapps @GoodbyeCain Can you please run the latest (1.2.7) version of this project and let me know about the results please?

It crashed at line 20 in PixelBufferFactory: var destinationTexture = currentDrawable.texture.makeTextureView(pixelFormat: .bgra8Unorm)
with the error: validateArgumentsForTextureViewOnDevice, line 1037: error 'source texture pixelFormat (MTLPixelFormatRGB10A8_2P_XR10_sRGB) not compatible with texture view pixelFormat (MTLPixelFormatBGRA8Unorm).' validateArgumentsForTextureViewOnDevice:1037: failed assertion source texture pixelFormat (MTLPixelFormatRGB10A8_2P_XR10_sRGB) not compatible with texture view pixelFormat (MTLPixelFormatBGRA8Unorm).'`

@warrenm Can you suggest a source for how to convert these pixelFormats to one another?

I have the same crash & error outputs than @LeonardRockstar.

@okaris It's unfortunate that this breaking change occurred, and that neither the change nor the format itself is documented. I don't know if XR biplanar format can be read or sampled by a shader, but if it can, you could bind the framebuffer as a source texture and "re-render" the frame to a bgra8Unorm target (with a full-screen quad pass) in order to get around this limitation. That will measurably impact the performance of the recorder. You might be able to recover part of the framerate hit by not taking a copy and building a UIImage every frame; that's an extremely expensive operation that doesn't seem to be necessary for the primary function of the framework.

Thank you @warren. I am still working on the pixel format but dropping UIImage helped for the performance.
@mariedm @LeonardRockstar @sanboxapps @GoodbyeCain
I am discussing this with Apple Developer Technical Support. Can you please confirm that this is reproducable with iOS11 GM and XCode9 GM. And also please include your device model. Thank you.

I can reproduce this readily on iPhone 7, iOS 11 GM.

I am actually working on xCode 9 GM with an iPhone 7 on iOS 11 GM.

I'm using the Xcode 9 GM and iOS 11 GM on an iPhone 7 Plus.

Response from Apple:
‘’’
After some investigation into the pixel format and how it is encountered by your library at run time, we’ve determined that your current approach is not recommended and you should consider alternatives.
In particular, the currentDrawable’s texture vended by SceneKit is not intended to be used this way and the texture format could change at any time. This is partly why this format is undocumented.
I’m unable to disclose more, and don’t want to encourage you further down a non-viable path, so that’s all there is to say about the current approach.
‘’’
I am planning on changing this core functionality over the weekend.
I am sorry that we could not find a viable solution.

Please try the latest version (1.3.1)

The distortion is gone on my iPhone 7 Plus!!

I can't make the new version work. I'm probably doing something wrong.
I call recorder=try! SceneKitVideoRecorder(withARSCNView: sceneView) in viewDidLoad(). Then recorder.setupMicrophone() and recorder.startWriting() when pushing the record button. But startDisplayLink() is never called. So when finishWriting is called, isRecording is false and it returns without stoping the recording.

@mariedm I just updated the demo project. Please try that and if that doesn't work please open a new issue.

The only difference is the setupMicrophone() moved to viewWillAppear which I tried and it's still not working. I'll open a new issue.
Congrats for the image distortion btw!


Can you start a transaction from a php website and then pay with the card reader?

Can you start a transaction from a php website and then pay with the card reader?

Hi, @glitcha
This is not possible workflow. If you have other similar questions that are not connected to this project you can ask them at<EMAIL_ADDRESS>


[#5361] improvment(hadoop-catalog): Introduce a timeout mechanism to get Hadoop File System.

What changes were proposed in this pull request?
Introduce a timeout mechanism when getting a Hadoop FileSystem instance.
Why are the changes needed?
Cloud filesystem like S3 and OSS(10 minutes) has a very long connection and can't be tune by configuration, this will cause deadlock as it will hold the tree lock for a long time
Fix: #5361
Does this PR introduce any user-facing change?
N/A.
How was this patch tested?
Existing test.

@jerryshao
Please help look if this should be included in release 0.7.0.

@jerryshao
Do you have any suggestions on this issue and should I proceed with it?


support placeholder !PIXEL_WIDTH!

To support placeholder !PIXEL_WIDTH!.
"Useful for limiting the density of points or calculating a localized importance ranking." https://github.com/mapbox/postgis-vt-util#labelgrid

Now being addressed in #477


This article is astoundingly confusing. First, Don't install Azure AZ, then ten ways to override that advice and install it?

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 108ead93-fd5d-f4c6-c3ee-0f4c6478e8dd
Version Independent ID: bd4fb194-d6af-e442-5ced-793e09c3fa83
Content: Install Azure PowerShell with PowerShellGet
Content Source: docs-conceptual/azps-4.6.0/install-az-ps.md
GitHub Login: @mikefrobbins
Microsoft Alias: mirobb

@kimballjohnson Thank you for the feedback!  We are investigating this and will get back to you shortly.

@kimballjohnson It is confusing, especially if you are new to PowerShell.  I'm sorry about that.  The documentation talks a bit about why the decision was made to introduce a new module and we believe that the benefits of the new module warranted the change.
Hopefully this will help clear up some common points of confusion:

PowerShell 7.x and later is currently the newest version and we recommend using that.
Azure Powershell has no additional requirements as long as it's run on PowerShell 6.2.4 or later (another reason to use PowerShell 7.x).
If you are using PowerShell 5.1 (which is already installed on more recent versions of Windows 10) instead of a more recent version of PowerShell, you'll need to follow the installation instructions.
There's a workaround if you need AzureRM for legacy reasons that involves installing AzureRM on PowerShell 5.1 and Az module on PowerShell 6.2.4 or later (as you can't have both the older AzureRM module and Az modules installed on PowerShell 5.1).

@kimballjohnson Hopefully that helps to clear up some of the confusion!  We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Ok, thanks for rewriting the content of the article.
My question is about the irony and confusion of the article’s clear message that AzureRM and AZ should not be deployed to a system simultaneously, while simultaneously providing instructions for simultaneously deploying both of them in every variety of installation scenario.
If they are not to be deployed together, what more needs to be said, unless you want responsible people to try what you are advising them not to do?
Let’s not try to explain it, or just agree that you are not sure whether they will successfully coexist!
From: kobulloc-MSFT<EMAIL_ADDRESS>Sent: Wednesday, August 26, 2020 1:21 AM
To: MicrosoftDocs/azure-docs-powershell<EMAIL_ADDRESS>Cc: Kimball Johnson<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs-powershell] This article is astoundingly confusing. First, Don't install Azure AZ, then ten ways to override that advice and install it? (#1545)
@kimballjohnsonhttps://github.com/kimballjohnson It is confusing, especially if you are new to PowerShell. I'm sorry about that. The documentation talks a bit about why the decision was made to introduce a new modulehttps://docs.microsoft.com/en-us/powershell/azure/new-azureps-module-az?view=azps-4.6.0#why-a-new-module and we believe that the benefits of the new module warranted the change.
Hopefully this will help clear up some common points of confusion:

PowerShell 7.x and later is currently the newest version and we recommend using that.
Azure Powershell has no additional requirements as long as it's run on PowerShell 6.2.4 or later (another reason to use PowerShell 7.x).
If you are using PowerShell 5.1 (which is already installed on more recent versions of Windows 10) instead of a more recent version of PowerShell, you'll need to follow the installation instructions.
There's a workaround if you need AzureRM for legacy reasons that involves installing AzureRM on PowerShell 5.1 and Az module on PowerShell 6.2.4 or later (as you can't have both the older AzureRM module and Az modules installed on PowerShell 5.1).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs-powershell/issues/1545#issuecomment-680734054, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAP65M3G5BWM2BE3TNBTIA3SCTAVBANCNFSM4QLCRXQA.

@kimballjohnson If you are getting a fresh start, PowerShell 7 and the AZ module is the recommendation.  If you already have legacy processes that depend on the AzureRM module and cannot migrate at this time for one reason or another, then you'll need to use the workaround described in the documentation.


Fixed the linkout resolvers to return the correct results structure.

This should've been included in the big PR that updated all entrypoint fields to use a results field, but it somehow got missed!

Works for me! :+1:


enable sanitizers on CI

2weso appears to be timing out when built with instrumentation. Perhaps TSAN and ASAN builds need to run smaller problems

I came across another issue in 1weso_test and 2weso_test where they would not exit with and error code in case the test failed. I fixed that in the top commit as well as allowed the CI to run fewer iterations for TSAN and ASAN builds

I'm going to merge as this should fix non vdf_client use cases


Orderbook Allowance Error

I've using the sdk for a couple of days.
Today I started to get an error after call the "postOrder" method:
{errorCode: "INSUFFICIENT_MAKER_ALLOWANCE",…} errorCode: "INSUFFICIENT_MAKER_ALLOWANCE" errorMessage: "Maker does not have sufficient allowance of 0xc778417e063141139fce010982780140aa0cd5ab (ERC20)"

Resolved


15749 addressing customer feedback

Description
This PR address these issues raised by a customer:

I suggest to rephrase the info message along the lines of: “The name to give the root key that will be created to encrypt your stored secrets. Not used if supplying an existing key.”
I suggest to rename the default value: sm-cos-key → sm-data-encryption-key
Its not clear what is the propose of the skip_kms_iam_authorization_policy field.
I suggest to rename the default value: sm-cos-key-ring → sm-data-encryption-key-ring
Only used if provision_sm_instance is set to true” ? The context of this DA is to provision an SM instance, also there is no provision_sm_instance field option in this page.
Its not clear what is the propose of the skip_en_iam_authorization_policy field.
Given the required name of the resource group to provision the instance of SM, what is the perpose of the optional existing_resource_group field?

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

Also since you are updating var names here, you will need to update the tests. They currently fail with:
 2024/03/28 18:55:42 Terraform plan | Error: Invalid function argument
 2024/03/28 18:55:42 Terraform plan |
 2024/03/28 18:55:42 Terraform plan |   on ../../main.tf line 15, in locals:
 2024/03/28 18:55:42 Terraform plan |   15:   validate_auth_policy = var.kms_encryption_enabled && var.skip_kms_iam_authorization_policy == false && var.existing_kms_instance_guid == null ? tobool("When var.skip_kms_iam_authorization_policy is set to false, and var.kms_encryption_enabled to true, a value must be passed for var.existing_kms_instance_guid in order to create the auth policy.") : true
 2024/03/28 18:55:42 Terraform plan |     ├────────────────
 2024/03/28 18:55:42 Terraform plan |     │ while calling tobool(v)
 2024/03/28 18:55:42 Terraform plan |
 2024/03/28 18:55:42 Terraform plan | Invalid value for "v" parameter: cannot convert "When
 2024/03/28 18:55:42 Terraform plan | var.skip_kms_iam_authorization_policy is set to false, and
 2024/03/28 18:55:42 Terraform plan | var.kms_encryption_enabled to true, a value must be passed for
 2024/03/28 18:55:42 Terraform plan | var.existing_kms_instance_guid in order to create the auth policy." to bool;
 2024/03/28 18:55:42 Terraform plan | only the strings "true" or "false" are allowed.
 2024/03/28 18:55:42 Terraform plan |
 2024/03/28 18:55:42 Terraform plan | Error: Missing required argument
 2024/03/28 18:55:42 Terraform plan |
 2024/03/28 18:55:42 Terraform plan |   with module.kms[0].module.kms_key_rings["sm-data-encryption-key-ring"].ibm_kms_key_rings.key_ring,
 2024/03/28 18:55:42 Terraform plan |   on .terraform/modules/kms.kms_key_rings/main.tf line 7, in resource "ibm_kms_key_rings" "key_ring":
 2024/03/28 18:55:42 Terraform plan |    7:   instance_id   = var.instance_id
 2024/03/28 18:55:42 Terraform plan |
 2024/03/28 18:55:42 Terraform plan | The argument "instance_id" is required, but no definition was found.
 2024/03/28 18:55:42 Terraform plan |
 2024/03/28 18:55:42 Terraform plan | Error: Error in function call
 2024/03/28 18:55:42 Terraform plan |
 2024/03/28 18:55:42 Terraform plan |   on .terraform/modules/kms/main.tf line 28, in locals:
 2024/03/28 18:55:42 Terraform plan |   28:   existing_instance_validate_check = regex("^${local.existing_instance_validate_msg}$", (!local.existing_instance_validate_condition ? local.existing_instance_validate_msg : ""))
 2024/03/28 18:55:42 Terraform plan |     ├────────────────
 2024/03/28 18:55:42 Terraform plan |     │ while calling regex(pattern, string)
 2024/03/28 18:55:42 Terraform plan |     │ local.existing_instance_validate_condition is true
 2024/03/28 18:55:42 Terraform plan |     │ local.existing_instance_validate_msg is "A value must be provided for 'existing_key_protect_instance_guid' when 'create_key_protect_instance' is false"
 2024/03/28 18:55:42 Terraform plan |
 2024/03/28 18:55:42 Terraform plan | Call to function "regex" failed: pattern did not match any part of the given
 2024/03/28 18:55:42 Terraform plan | string.
 2024/03/28 18:55:42 Terraform PLAN error: Terraform PLAN errorexit status 1

Making the changes to the code to address the changes that are in the box note.

closing this PR after @ocofaigh made a seperate PR to improve on this PR: https://github.com/terraform-ibm-modules/terraform-ibm-secrets-manager/pull/93


Toggle Invisible Mode

Currently, as a user, I do not get to know whether I am in invisible or not. A better representation of the state would be awesome

Agreed @ankitmadan .
I am planning to involve a designer to fix all these UX issues.

That will be awesome, a design overhaul will do wonders to this


How could I combine ASP.NET Core with AngularClass/angular2-webpack-starter?

I'm a fan of the AngularClass/angular2-webpack-starter boilerplate. It is a very good foundation for starting an Angular project (they use webpack too). Has best practices, karma-jasmine, perhaps too opinionated, but a very good foundation with a solid backing community imo.
I really want to achieve a fusion of both asp.net core and that boilerplate, but am pretty lost. Could anyone give some tips on how I could achieve such an environment?
I imagine this repo is the closest chance to getting help on the dilemma, out there on the internet. Without being experienced in both technologies already.

Hello @amivit there is certainly an option to combine the starter kit with an asp.net core application and use the webpack nuget package but it's not something really trivial. One of my priorities is to provide an Angular 2 sample with webpack and after that it should be more easily to change it to use the starter kit.

Sounds very cool. Will be exciting to see. You can maybe get some inspiration here, because in the meantime I discovered this yeoman generator developed by Stevens Anderson, which is capable of setting up an Angular 2 + webpack + .net core environment.
I have been trying to learn from his implementation, to adapt it to the AngularClass starter-kit, but without much success (I really prefer their opinionated boilerplate). I am still in the early learning phase of becoming a developer, I'm just too excited with all the bleeding edge technology, when in reality, I should be more focused on just studying :)
Let me know if you come up with anything new & shiny for me to work with!


"Error: Remix Vite plugin can't detect preamble. Something is wrong." when running component tests with Vitest

Reproduction
Go to https://stackblitz.com/edit/remix-run-remix-b7fgeb?file=tests%2Fexample.spec.tsx and run npx vitest to see the error.
Regular unit tests run fine, problem appeared when integrating component testing with @testing-library/react (which in turn required me to install happy-dom or jsdom for the testing environment).
Defining the components inside the test do not cause an error.
I was able to trace the issue to the vite.config.ts file, where including any configurations related to vitest will cause it to fail. Moving the vitest configurations to vitest.config.ts and merging the two configuration files as advised by the official documentation also causes the same error.
The only (temporary) solution I found was to separate vitest.config.ts and vite.config.ts, then everything works as expected. But that is not a good solution as according to the official documentation, overrides the vite file.
System Info
System:
    OS: macOS 14.2.1
    CPU: (8) arm64 Apple M1
    Memory: 116.03 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - /usr/local/bin/node
    Yarn: 1.22.21 - ~/.yarn/bin/yarn
    npm: 10.3.0 - /opt/homebrew/bin/npm
    pnpm: 8.15.1 - /opt/homebrew/bin/pnpm
    bun: 1.0.29 - ~/.bun/bin/bun
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Safari: 17.2.1
  npmPackages:
    @remix-run/dev: ^2.8.0 => 2.8.0
    @remix-run/node: ^2.8.0 => 2.8.0
    @remix-run/react: ^2.8.0 => 2.8.0
    @remix-run/serve: ^2.8.0 => 2.8.0
    @remix-run/testing: ^2.8.0 => 2.8.0
    vite: ^5.1.0 => 5.1.5

Used Package Manager
npm
Expected Behavior
Tests should work as expecting without throwing
Actual Behavior
Test fail because of reasons unrelated to tests

It ran into the same error too while trying to run react component tests

I am also having this exact error.

Any update on this ?

@martialanouman

The only (temporary) solution I found was to separate vitest.config.ts and vite.config.ts, then everything works as expected. But that is not a good solution as according to the official documentation, overrides the vite file.

Thanks @amanape
I saw that and use it for now, but that doesn't feel clean

Currently we recommend that the remix plugin is omitted when running with Vitest.
There's a bit of work to do on our end to figure out how best to integrate with tools like Vitest and Storybook so that this sort of workaround isn't required.

If I did the conditional logic of process.env.VITEST && remix() I would get a new error in some of my tests:
ReferenceError: React is not defined

If you were on a Vite React SPA previously, I'm finding that you would need to keep your @vitejs/plugin-react around just for vitest:
import reactVitest from '@vitejs/plugin-react'
import { vitePlugin as remix } from '@remix-run/dev';
import { defineConfig, loadEnv } from "vite";

export default defineConfig({
  plugins: [process.env.VITEST ? reactVitest() : remix()],
  // rest of the config
});

Currently we recommend that the remix plugin is omitted when running with Vitest.
There's a bit of work to do on our end to figure out how best to integrate with tools like Vitest and Storybook so that this sort of workaround isn't required.

This generally works well, but I'm facing some issues when trying to test remix routes using @remix-run/testing. Basically, no matter what I pass, when rendering the RemixStub, it always results in a 404 error page.
Could that be related with the fact that the remix vite plugin is not loaded while running tests with vite?

Currently we recommend that the remix plugin is omitted when running with Vitest.
There's a bit of work to do on our end to figure out how best to integrate with tools like Vitest and Storybook so that this sort of workaround isn't required.

This generally works well, but I'm facing some issues when trying to test remix routes using @remix-run/testing. Basically, no matter what I pass, when rendering the RemixStub, it always results in a 404 error page.
Could that be a side effect of not loading the remix vite plugin while running tests with vite?

Currently facing the same issue. The "Remix Vite plugin can't detect preamble. Something is wrong." was solved. However now my tests using createRemixStub always render 404 error page which makes them fail.
Any solution?

I am running into this exact error with a fresh remix app which attempts to use vitest with jsdom. I have another project which uses React Router which I want to port over to remix. While the app works, the tests cannot due to this issue and I am blocked.
Reproduction
https://github.com/brianbancroft/remix-cant-use-vitest

This will fix the issue
import { vitePlugin as remix } from "@remix-run/dev";
import { installGlobals } from "@remix-run/node";
import tsconfigPaths from "vite-tsconfig-paths";
import { defineConfig } from "vite";

installGlobals();

const MODE = process.env.NODE_ENV;

export default defineConfig({
  build: {
    cssMinify: MODE === "production",
    rollupOptions: {
      external: [/node:.*/, "stream", "crypto", "fsevents"],
    },
  },
  server: {
    watch: {
      ignored: ["**/playwright-report/**"],
    },
  },
  plugins: [
    process.env.NODE_ENV === "test"
      ? null
      : remix({
          ignoredRouteFiles: ["**/*.css"],
        }),
    tsconfigPaths(),
  ],
  test: {
    include: ["**/__tests__/**.{js,jsx,ts,tsx}"],
    environment: "jsdom",
    setupFiles: ["./tests/setup/setup-tests-env.ts"],
    restoreMocks: true,
    coverage: {
      exclude: ["**/__tests__/**"],
      include: ["app/**/*.{ts,tsx}"],
      all: true,
    },
    alias: {
      "~": "/app",
    },
  },
});

This is a typical config file
 plugins: [
    process.env.NODE_ENV === "test"
      ? null
      : remix({
          ignoredRouteFiles: ["**/*.css"],
        }),
    tsconfigPaths(),
  ],

Checkout this issue https://github.com/remix-run/remix/issues/9871


Add Apache Portable Runtime

This will improve performance on deploying servers, as well as need to be built into SSL changes so I believe this should supercede those changes. Then this can be deployed.

Closed By #24


BUG: Fix the profile page

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Fix the profile page
this error is showing

Record

[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSOC'24 contributor
[ ] I want to work on this issue

this is also related with the database, null  value are being passed which is breaking this

I want to work on this project. Kindly assign this issue to me. So that I can start working on this task.


Resolve syncing conflicts from live-sync-work to live

Pull request opened by OPS to resolve syncing conflicts from live-sync-work to live.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\05gn-s, target branch: live, target branch commit: 4f5e98aff1652989c9ce737693e9cedc751658c1, source branch: live-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


ISPN-11889 Remove deprecated parser attributes

~~https://issues.redhat.com/browse/ISPN-11889~~

Updated to remove test XML configurations for versions 7.0-8.5.

After the Zulip discussion, I reverted the attribute removals and I only changed the parser to reject some replication queue attributes that were silently ignored.

LGTM, just restarting the CI build as the last one was interrupted.

Thanks @danberindei


An unexpected error occurred

Hi, after installing the add-on (latest C<IP_ADDRESS>) we have difficulties to log-in again to our local installation. "An unexpected error occurred. File does not exist at path /Applications/MAMP/htdocs/C5-ART/packages/free_cookies_disclosure/vendor/autoload.php".
When searching for the autoload.php file in the downloaded zip, we can't find any. Exchanging the install folder with a new one does not solve it. At present we can't log-in to our site.
Could you give us a tip what needs to be changed ..simply removing the add folder results in more errors. (no log-in possible) We want to make it clear, we are new to concrete5.
Many regards. (here's a screenshot)

Please follow the installation instructions in the README file, it should fix this problem.

Hi, thanks for the feedback. Do you mean .."Make sure you have Composer installed."?
At present we can't do much via the gui/can't log-in. If you could provide some infos, it
would helpful. Many regards.

You don't need GUI for installing composer or the composer packages. Infos for installing the composer packages are basically in the add-on installation instructions. If you need help with composer, please refer to their documentation (also linked in the installation instructions).

Hi Antii Hukkanen,
thanks for the reply. It is the php tool composer what we didn't install
before going any further. We thought Composer is already integrated
in Concrete5  ..it is, but not the php tool (we now know).
Installing without the GUI is something we haven't done before. So it
seems ..our road ends here.
Many regards.

Antti Hukkanen<EMAIL_ADDRESS>2. Dezember 2015 15:04
You don't need GUI for installing composer or the composer packages.
Infos for installing the composer packages are basically in the add-on
installation instructions. If you need help with composer, please
refer to their documentation (also linked in the installation
instructions).
—
Reply to this email directly or view it on GitHub
https://github.com/mainio/c5_free_cookies_disclosure/issues/1#issuecomment-161303733.

If you remove the package row from the Packages table you can get the add-on uninstalled. Here's the SQL you need to run manually:
DELETE FROM Packages WHERE pkgHandle = 'free_cookies_disclosure';

After that, this add-on is uninstalled.
You are not unfortunately able to install this add-on without getting familiar with composer and running it through the command line. If we ever decide to publish this to the marketplace, the required composer packages will ship with that version.


Read the file and save it again. The file before and after is inconsistent。

The file is 935kb before reading, and is saved directly without any operation. After saving, it is 1014kb. Is there any way to save the same size as the original file? Due to the company's network is limited, so only text description, please help to see the problem, thank you.

Matlab can read the saved file, and the content is the same as before, but the program made in other languages can't parse the file.My English is not very good, use the translation program, please understand, thank you

I've tried to use some other parameters when using the loadmat function, but the results are not ideal

Matlab 2010b

My mat file version is v7.0. Can savemat set this version number? It seems that you can only set two formats: format = 5 'or format = 4'

https://github.com/tbeu/matio/issues/154
In this link, I also raised the same question, the above picture and explanation, please help to have a look, thank you very much.

@Alex Henrie

@alexhenrie

This is to be expected, there's no requirement to read in a file produced from Matlab, save it back out and have it be identical. We should produce a valid file, so if both scipy.io and Matlab can again read the file, that's good enough for us.
https://github.com/tbeu/matio/issues/154 has useful discussion, thanks. I'll leave it open for now, but I don't think there's much we can do.

No further discussion and nothing we can do, so I'll close this issue. Thanks for the report @Qianzujin


Fixes #6795 : Sort Taxonomies Terms failed

TermQuery have to be sliced after sorting

There is still an issue when page size is 0.
I have to fix that before merge.


Expanding Test Suite

This helps to address https://github.com/bitwalker/timex_ecto/issues/20
Worked on by the Elixir |> CLE folks on our PR night :)

You guys rock! Thanks so much for this!


Declare Buildkite pipelines

The .buildkite directory is still empty as I still need to iterate on the pipelines themselves. I would like to do that on a branch if possible as the pipeline is a bit tricky with Python tests running various Docker commands so I can't use a Dockerfile as I don't think Docker-in-Docker is supported.

This looks good and passes the Backstage validator.
The only thing I would defer to @jarpy is around declaring the dependency on marbi.

Ooops!
Sorry for merging. I thought I was in a different repo. 😳

I don't think Docker-in-Docker is supported.

It's supported if you opt to run on VMs instead of containers, but we encourage everyone to use containers if possible, and we appreciate the effort.

Thanks for the reviews and merge! Appreciated. Most of our tests don't rely on Docker, but for those that do we'll use VMs.


Solved issue #152

#152
Added documentation to all functions

Hi, I added the additional line. Sorry for the delay, I've been busy :(

Hi, I added the additional line. Sorry for the delay, I've been busy :(

No worries! Thank you for submitting the pull request!


why forcing tf_romevision_opt_in 1 by default ?

I recently rearranged my config files and saw that robots had additional hats on. I found that for some reason, the command 'tf_romevision_opt_in 1' was in the comfig.cfg file.
I want to know if this is impacting the game performance in a good way, because adding the hats to the robots seems like doing the opposite + the new carrier tank look.
Therefore, how is it working ? is this an additional texture on top of the original one ? is this removing the classic one with the rome model ? and if so, which one is lighter ?

That's a good point. I never thought about the performance impact. I will look into it.


new routes

@digitallysavvy I was using this PR for the code changes as well. Instead of creating a new PR for only the content, I figured we could just use this.
Feel free to comment on the code changes too, but the scope of this review is the TOKENS.md


Add GitHub repo setup guidelines

i.e. describe basic settings etc

From @korikuzma:

We can change the default squash and merge settings to use PR title / description so less copy/pasta


More flexible project directory support

Hi,
This pull request adds/improves a few features. Hopefully, you'll like them all. If not, let me know and I'll split the commits into separate PRs.

Support for Django 1.4-style project layouts, where the project module is a subdirectory of the main project. This works by simply looking for a manage.py one level up from where it looks currently.
Some projects don't use manage.py at all - they just use django-admin.py for everything. In this case, guessing the project layout won't work. I added a --projdir flag to the management command to explicitly set the project dir.
I also added a --dump flag, which simply prints the merged config file and exits. This is really, really useful for debugging.

Cheers!

Thanks j4mie - just wanted to assure you that I'm not ignoring this, I'm just moving house at the moment so I'm a bit short on spare cycles.  Might need to wait a week or so before I can sit down with this, merge and release.

No problem, thanks.

Wow, I have no idea how I missed the getconfig argument.  Please ignore the commit that adds --dump which does exactly the same thing! Sorry about that!

I've made a couple of tweaks and pushed this into trunk, and you please test it out and let me know if it works for you?
(most notable tweak: I went with --project-dir instead of --projdir, to mirror the name of the template var that it will end up in)

Ah, thanks for tracking that down.  I really need to get some automated tests going on this thing!
I am about to release v0.2.4 with your changes.


cellBottomLabel not show, how to define the height?

I want to show "hh:mm" label below message content. Similar to image below (see the purple circle)

Here is how I change the cellBottomLabel:
 override func collectionView(collectionView: UICollectionView, cellForItemAtIndexPath indexPath: NSIndexPath) -> UICollectionViewCell {
    let msg = messages[indexPath.item]
    let cell = super.collectionView(collectionView, cellForItemAtIndexPath: indexPath) as! JSQMessagesCollectionViewCell
    cell.textView?.textColor = UIColor(CGColor: CGColor.colorWithHex(0x4f4f4fff))
    cell.cellBottomLabel?.text = Common.hourMinuteLabel(msg.date)

    return cell
}

My assumption is, I need to define the height of cellBottomLabel, how to do that?

Override this func:
override func collectionView(collectionView: JSQMessagesCollectionView!, layout collectionViewLayout: JSQMessagesCollectionViewFlowLayout!, heightForCellBottomLabelAtIndexPath indexPath: NSIndexPath!) -> CGFloat {
return CGFloat(20)
}
It's found in the JSQMessagesCollectionViewDelegateFlowLayout.

Also instead of hacking into the cell to display the text in the cellBottom you can use this func:
override func collectionView(collectionView: JSQMessagesCollectionView!, attributedTextForCellBottomLabelAtIndexPath indexPath: NSIndexPath!) -> NSAttributedString! {
     return NSAttributedString(string:"test")
}

That's correct. Thanks @radoslavyordanov ! :smile:

Thank you, it works! @radoslavyordanov


Update Data Source tool crashing in Pro 3.1 for Specific map

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Open Pro 3.1 Project.
Add tool UtilityDataManagementSupport to Toolboxes
Import Map "Electric Network Editor"
Execute Tool "Update Data Source" found in Map folder of UtilityDataManagementSupport toolbox.  Can use python below
arcpy.ImportToolbox(r"D:\Projects\ESRI-BZ\BZ_Check.atbx")
arcpy.udms.AdjustDataSources(
target_workspace=r"D:\Projects\ESRI-BZ\Electric_UtilityNetwork.gdb",
maps="'Electric Network Editor'",
update_sr=True
)

Expected behavior
Data source of layers to change instead of crashing pro
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 11
Browser Edge
Version 113

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
Data: \pleblanc\public\FromJohn\Issue36

It is crashing in Pro 3.2 on PyArcGISLayerModule::GetFIDSetForSubtypeGroupLayer+0x3d3 [C:\ArcGIS\Geoprocessing\Python\arcgisscripting\PyLayer.cpp @ 241]


erroneous structural cycle detection

What version of CUE are you using (cue version)?

$ cue version
cue version 0.4.0-beta.2 darwin/amd64

Does this issue reproduce with the latest release?
yes
What did you do?
I am trying to transform a potentially complex recursive structure into a flattened (one-level) dictionary
The file I am using as a simplified example is

-- test.cue --
// A simple discriminated element
#AC: {
  k: "simple"
  d: #C
}

// A recursive discriminated element
#AS: {
  k: "complex"
  d: #S
}

#R: {
  a: #AC | #AS
}

// The structure of the recursive element
#S: {
  n: string
  r: [string]: #R
}

// The structure of the simple element
#C: {
  n: string
}

// Problematic traversal.
#sub: {
  $p=#p: #AS
  dict: [string]: _

  for rn, rd in $p.d.r if rd.a.k == "complex" {
    let subs = #sub & {#p: rd.a}
    for sn, sd in subs.dict {
      dict: "\(rn)_\(sn)": sd
    }
  }
  for rn, rd in $p.d.r if rd.a.k == "simple" {
    dict: "\(rn)": rd
  }
}

// Data
_test: {
  c1: #AC
  c1: d: {
    n: "c1"
  }

  s3: #AS
  s3: d: {
    n: "s3"
    r: r1: a:c1
  }

  s2: #AS
  s2: d: {
    n: "s2"
    r: {
      r1: a: c1
      r2: a: s3
    }
  }

  s1: #AS
  s1: d: {
    n: "s1"
    r: {
      r1: a: c1
      r2: a: s2
    }
  }
}

//  Test

out: #sub & {#p: _test.s1}

I ran cue export test.cue
What did you expect to see?

{
    "out": {
        "dict": {
            "r1": {
                "a": {
                    "k": "simple",
                    "d": {
                        "n": "c1"
                    }
                }
            },
            "r2_r1": {
                "a": {
                    "k": "simple",
                    "d": {
                        "n": "c1"
                    }
                }
            },
            "r2_r2_r1": {
                "a": {
                    "k": "simple",
                    "d": {
                        "n": "c1"
                    }
                }
            }
        }
    }
}

What did you see instead?

structural cycle:
    ./test.cue:34:16

If I reduce in one level the structure I pass to #sub then the error is avoided. E.g., if the test is
out: #pre & {#p: _test.s2}, then I get the expected result for this case:

{
    "out": {
        "dict": {
            "r1": {
                "a": {
                    "k": "simple",
                    "d": {
                        "n": "c1"
                    }
                }
            },
            "r2_r1": {
                "a": {
                    "k": "simple",
                    "d": {
                        "n": "c1"
                    }
                }
            }
        }
    }
}

I tried other variations of a two-level struct, and the error is avoided in those cases, but not when the structure is more than two level deep.

Well,
apparently the error appears also when the original structure is altered, as in the example presented above.
If the structure is preserved (along the path of the recursion), the error does not appear.
For instance, the traversal function below preserves the structure it is passed (except for the hidden field _in):

#traversal: {
  _in: #AS

  let $in = _in.d

  k: "complex"
  d: n: $in.n
  for rn, v in $in.r {
    if v.a.k == "simple" {
      d: r: "\(rn)": v
    }

    if v.a.k == "complex" {
      d: r: "\(rn)": v & {
        a: #traversal & {_in: v.a}
      }
    }
  }
}

Running cue export as in the original post on out: #traversal & {_in: _test.s1}computes the expected value with no cycle errors.
HOWEVER, removing unification with v in the recursive step within the code above (second if statement), as in,

#traversal: {
  _in: #AS

  let $in = _in.d

  k: "complex"
  d: n: $in.n
  for rn, v in $in.r {
    if v.a.k == "simple" {
      d: r: "\(rn)": v
    }

    if v.a.k == "complex" {
      d: r: "\(rn)": {
        a: #traversal & {_in: v.a}
      }
    }
  }
}

Makes a cycle error appear again:

out.d.r.r2.a.d.r.r2.a: structural cycle

where such unification, to my eyes, introduces nothing!
All in all, we have not found a way to reliably perform recursive traversals within CUE above 0.2.2.

Part of the problem here is that the code iterates over the same struct in which it is inserting new fields. It is technically not entirely the same struct (as it iterates over a copy).
This is an area where arguably CUE should be more permissive. At the moment it is not, though.

FTR, here is a simplified reproducer:
#AC: {
  k: "simple"
  n: string
}

#AS: {
  k: "complex"
  r: [string]: #AC | #AS
}

// Problematic traversal.
#sub: {
  #p: #AS
  dict: [string]: _

  for rn, rd in #p.r {
    let subs = #sub & {#p: rd}
    for sn, sd in subs.dict {
      dict: "\(rn)_\(sn)": sd
    }
  }
}

// Data
_test: {
  s3: r: r1: n: "c1"
  s2: r: r2: s3
  s1: r: r2: s2
}

//  Test

out: #sub & {#p: _test.s1}

Part of the problem here is that the code iterates over the same struct in which it is inserting new fields. It is technically not entirely the same struct (as it iterates over a copy).

Yes, as you say, it is not the same struct.
In essence, this is a function that takes a struct, and computes over it.
The result is another struct. If there are no bounds on the depth of the struct it operates on, one needs to use a
recursive approach to perform the transformation. In the versions of CUE above 0.2.2, this seems to raise
cycle errors except in  narrow cases (like the one I show in my second post above)

This is an area where arguably CUE should be more permissive. At the moment it is not, though.

To me this is incorrect behavior, is it not?
Specially in the second case, where the behavior changes by eliminating a unification which should introduce nothing new.
That was quite baffling to me.
At the end of the day, we are talking about a recursive traversal of a structure of unknown depth,
building a result as the traversal goes on.
From the docs, we understood this was a legitimate case of usage. We certainly have acted on that belief, although
the consequence right now is that we are stuck with version 0.2.2 of CUE, which apparently allowed such recursive traversals (it had many other problems that are gone in the latest releases, though).

Specially in the second case, where the behavior changes by eliminating a unification which should introduce nothing new.

I understand that intuition, but that doesn't mean it should be allowed. The cycle detection sometimes skips the first recursion, knowing that it is fine to detect the recursion further down, from a correctness point of view.
In this case, one could argue it should probably be allowed, though, indeed, as you mentioned.
One temporary solution may be to allow configuring an allotted recursion, allowing users, for instance, to do a total of a 1k or 1M recursions. Let me know if that would solve a pressing need.

Hi @mpvl ,
Thanks for the suggestion.
Yes, I think being able to configure the number of recursions would allow us to make progress .
The scenarios we contemplate theoretically allow arbitrary depth, but realistically, in the short term, we can cap that depth for a while.

Following the suggestion about limiting recursion depth, a solution can be found within CUE itself to transform a recursive function into an ordered dictionary of basically identical functions where each function, when ready to perform the recursive call, calls the next function instead.

#RecurseN: {
  // Maximum depth of recursion
  _depth: uint
  _funcFactory: {_next: _, func: _}

  for k, it in _depth*["iter"] {
    _Funcs: "\(it)\(k)": (_funcFactory & {_next: _Funcs["\(it)\(k+1)"]}).func
  }
  _Funcs: "iter\(_depth)": null

  // Export the function at position 0
  Func: Funcs.iter0
}

It is straightforward to obtain a function factory out of a recursive function: include all its code within the func output of the factory, and, instead of making the recursive call, call the _next parameter of the factory.
E.g., a simple depth calculator would be

import "list"

#DepthF: {
  _next: _

  func: {
    #Value: string|int|bool|null
    _in: _
    out: {
      if (_in & #Value) != _|_ {
        0
      }
      if (_in & #Value) == _|_ {
        list.Max([for k,v in _in {(_next & {_in: v}).out}]) + 1
      }
    }
  }
}

From which we could get a function that computes the depth of structures.
For instance, to compute depths up to a maximum of 10

#depth: (#RecurseN & {_depth: 11, _funcFactory: #DepthF}).Func

The performance hit does not seem too bad for building the dictionary of functions.

This issue has been migrated to https://github.com/cue-lang/cue/issues/990.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Bug: PNG drawer does work in version 2.1.7 as a React component

I am using React in Next.js.
I created a React component to render a chemical structure and I found. When using SmilesDrawer.Drawer, the canvas is not updated and no structure is drawn. Using SmilesDrawer.SvgDrawer does work. After a bit of experimentation I found this appears to be a bug with version 2.1.7. Rolling back to earlier 2.1.x versions resulted in an import error. Rolling back to version 2.0.3 the SmilesDrawer.Drawer class does work.
Also, it would be very helpful if the documentation showed how to use smiles-drawer with React as it is not immediately obvious.
Summary of issues:

SmilesDrawer.Drawer does not render PNG image in version 2.1.7.
SmilesDrawer.SvgDrawer works correctly in 2.1.7.
Versions 2.1.1 to 2.1.6 throw SyntaxError: Cannot use import statement outside a module when importing.
SmilesDrawer.Drawer works correctly in version 2.0.3.

Example code
This code is for a component to render a structure either as PNG or SVG.
import React, { useRef, useEffect } from "react";
import SmilesDrawer from "smiles-drawer";

const USE_SVG = false;

const SETTINGS = {
  width: 800,
  height: 400,
};

const SmileDrawerContainer = ({ smilesStr }: { smilesStr: string }) => {
  if (USE_SVG) {
    // SVG version (versions: <=2.0.3 and 2.1.7)
    const svgRef = useRef<SVGElement>(null);

    let drawer = new SmilesDrawer.SvgDrawer(SETTINGS);

    useEffect(() => {
      SmilesDrawer.parse(smilesStr, function (tree: any) {
        drawer.draw(tree, "structure-svg", "light");
      });
    }, []);

    return (

        <svg id="structure-svg"></svg>

    );
  } else {
    // Canvas version (versions: <=2.0.3 only)
    const canvasRef = useRef<HTMLCanvasElement>(null);

    let drawer = new SmilesDrawer.Drawer(SETTINGS);

    useEffect(() => {
      SmilesDrawer.parse(smilesStr, function (tree: any) {
        drawer.draw(tree, "structure-canvas", "light");
      });
    }, []);

    return (

        <canvas
          className="relative"
          id="structure-canvas"
          ref={canvasRef}
          width={"800px"}
          height={"400px"}
        />

    );
  }
};

export default SmileDrawerContainer;

Thanks for writing this out - I've been so confused.

const source = 'CC(=O)Nc1ccccc1C(=O)O'
const img = container.createEl('img') as HTMLImageElement // container is a HTMLDivElement, decleared above
const theme = 'dark'

let drawer = new SmilesDrawer.SmiDrawer();
drawer.draw(source, target, theme)

This renders PNG file in v 2.1.7.

If that is the case, the documentation really needs to be updated to reflect that a canvas element no longer works

If that is the case, the documentation really needs to be updated to reflect that a canvas element no longer works

2.1.7 smiles-drawer still works with canvas.
Look at example/next.html file in lib repository and go this way. In case you'll draw a lot of different molecules, create a function which generates unique classname for each of those canvas element


Add FilledStacks channel

FilledStacks by Dane Mackier  (@filledstacks) is an awesome channel for flutter and I think its worth being in the list.

Thanks @Henriquedn appreciate the effort to get me on the list.

Can you add the DoingITeasyChannel
https://www.youtube.com/user/DoingITeasyChannel

Move it to the bottom of the list and I'll merge


Fixed response for GetStateValidatorBalances in OpenAPI docs

PR Description
Fixed Issue(s)

Fixed response for GetStateValidatorBalances in OpenAPI docs

Documentation
As I understood, the generated documentation will be automatically fixed after this PR, but I've no permissions to assign any label to this PR in any case.

[x] I thought about documentation and added the documentation label to this PR if updates are required.

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

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


Missing ClientInterfaceName in GenerateConfig?

I get this error which looks like an error caused by some missing config
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x14807b3]

goroutine 1 [running]:
github.com/Yamashou/gqlgenc/clientgen.RenderTemplate(0xc0000a9ba0, 0xc006672320, 0x0, {0x1954870, 0x0, 0x0}, {0xc018f11740, 0x8, 0x8}, {0xc018f11600, ...}, ...)
        /Users/johanhyrefeldt/.gvm/pkgsets/go1.18/global/pkg/mod/github.com/!yamashou/gqlgenc@v0.0.6/clientgen/template.go:22 +0x313
github.com/Yamashou/gqlgenc/clientgen.(*Plugin).MutateConfig(0xc000091810, 0xc0000a9ba0)
        /Users/johanhyrefeldt/.gvm/pkgsets/go1.18/global/pkg/mod/github.com/!yamashou/gqlgenc@v0.0.6/clientgen/client.go:80 +0x607
github.com/Yamashou/gqlgenc/generator.Generate({0x163e5a8, 0xc0000300b0}, 0xc0001d61e0, {0xc0000e7ed8, 0x1, 0xc00005e601?})
        /Users/johanhyrefeldt/.gvm/pkgsets/go1.18/global/pkg/mod/github.com/!yamashou/gqlgenc@v0.0.6/generator/generater.go:52 +0x2e5
main.main()
        /Users/johanhyrefeldt/.gvm/pkgsets/go1.18/global/pkg/mod/github.com/!yamashou/gqlgenc@v0.0.6/main.go:30 +0x3b5

I'm using go1.18 so I have installed the executable gqlgenc via go install github.com/Yamashou/gqlgenc since go get doesn't install executables in go1.18. Prior to that I did run go get -u github.com/Yamashou/gqlgenc. The .gqlgenc.yml that i use looks like
model:
  package: backend
  filename: ./internal/backend/graphql-service_gen.go # https://github.com/99designs/gqlgen/tree/master/plugin/modelgen
client:
  package: backend
  filename: ./internal/backend/graphql-service.go # Where should any generated client go?
query:
  - "./internal/backend/graphql/graphql-service/query/*.graphql" # Where are all the query files located?
endpoint:
  url: <the url to the graphql api endpoint that I want to generate from>

What happens that the models in graphql-service_gen.go does seem to be generated correctly. And I have not done any changes to the queries in ./internal/backend/graphql/graphql-service/query so I don't expect any changes in ./internal/backend/graphql-service.go. But since I get the error above I want to double check that I'm not missing some important config.

I have the same issue but you were on the right track spoting its root cause!
Seems @Yamashou fixed it in clientgenv2 (Yamashou/gqlgenc@7c74e5d7739df1e579d80261f30e928cdb242a3c) but not in clientgen.
The following patch fixes it for clientgen:
diff --git a/clientgen/template.go b/clientgen/template.go
index 8a8017e..89ffa89 100644
--- a/clientgen/template.go
+++ b/clientgen/template.go
@@ -19,7 +19,7 @@ func RenderTemplate(cfg *config.Config, query *Query, mutation *Mutation, fragme
                        "Operation":           operations,
                        "OperationResponse":   operationResponses,
                        "GenerateClient":      generateCfg.ShouldGenerateClient(),
-                       "ClientInterfaceName": generateCfg.ClientInterfaceName,
+                       "ClientInterfaceName": generateCfg.GetClientInterfaceName(),
                },
                Packages:   cfg.Packages,
                PackageDoc: "// Code generated by github.com/Yamashou/gqlgenc, DO NOT EDIT.\n",

@hyrefeldt-ourstudio
Do you have to use v1 clients? If so, I will try to correct v1 as well as v2


Why spyder terminal doesn't output as what windows terminal does

Problem Description
When I am using scipy or sklearn. For example 'fmin_l_bfgs_b' from scipy, I want to output the progress, and I set the flag 'disp' to 1. It works perfect in windows terminal as shown below:

At iterate   91    f=  2.52430D-01    |proj g|=  5.95514D-04
At iterate   92    f=  2.52041D-01    |proj g|=  4.30313D-04
At iterate   93    f=  2.51853D-01    |proj g|=  8.88174D-04
At iterate   94    f=  2.51738D-01    |proj g|=  4.72683D-04
At iterate   95    f=  2.51651D-01    |proj g|=  3.06761D-04
At iterate   96    f=  2.51566D-01    |proj g|=  3.62897D-04
At iterate   97    f=  2.51396D-01    |proj g|=  3.21496D-04
At iterate   98    f=  2.50996D-01    |proj g|=  5.72155D-04
At iterate   99    f=  2.50837D-01    |proj g|=  3.61951D-04
At iterate  100    f=  2.50718D-01    |proj g|=  3.03547D-04

But in spyder, it just output nothing, I have to wait until it ends and having no idea what is going on.
Same things happened to tensorflow. In windows terminal, if you start to train, tensorflow will output something like the fellowing information:

2019-10-11 02:04:29.810448: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2                                                                                2019-10-11 02:04:29.821933: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library nvcuda.dll                                                                                2019-10-11 02:04:29.909687: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 0 with properties:                                                                                name: GeForce RTX 2070 major: 7 minor: 5 memoryClockRate(GHz): 1.815                                                                                pciBusID: 0000:01:00.0                                                                                2019-10-11 02:04:29.920598: I tensorflow/stream_executor/platform/default/dlopen_checker_stub.cc:25] GPU libraries are statically linked, skip dlopen check.                                                                                2019-10-11 02:04:29.933072: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1763] Adding visible gpu devices: 0                                                                                2019-10-11 02:04:31.378291: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1181] Device interconnect StreamExecutor with strength 1 edge matrix:                                                                                2019-10-11 02:04:31.391202: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1187]      0                                                                                2019-10-11 02:04:31.398304: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 0:   N                                                                                2019-10-11 02:04:31.403961: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 6315 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2070, pci bus id: 0000:01:00.0, compute capability: 7.5)

But in spyder terminal, such info will not show up.
Versions

Spyder version: 3.3.6
Python version: 3.7
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

Are you working on Windows?

Are you working on Windows?

Yes

Then what you're asking for is not possible due to limitations of the architecture behind our IPython console.
However, it works as expected on Linux and macOS.

I can't get this to print the output on runfile or runcell in linux but I can in to I copy to the console.
from scipy.optimize import fmin_l_bfgs_b
import numpy as np

mpl.rcParams['svg.fonttype'] = 'none'
mpl.rcParams['font.sans-serif'] = 'Arial'

x_true = np.arange(0,10,0.1)
m_true = 2.5
b_true = 1.0
y_true = m_true*x_true + b_true

def func(params, *args):
    x = args[0]
    y = args[1]
    m, b = params
    y_model = m*x+b
    error = y-y_model
    return sum(error**2)

initial_values = np.array([1.0, 0.0])

fmin_l_bfgs_b(func, x0=initial_values, args=(x_true,y_true), approx_grad=True, disp=True)

I can't get this to print the output on runfile or runcell in linux but I can in to I copy to the console.
from scipy.optimize import fmin_l_bfgs_b
import numpy as np

x_true = np.arange(0,10,0.1)
m_true = 2.5
b_true = 1.0
y_true = m_true*x_true + b_true

def func(params, *args):
    x = args[0]
    y = args[1]
    m, b = params
    y_model = m*x+b
    error = y-y_model
    return sum(error**2)

initial_values = np.array([1.0, 0.0])

fmin_l_bfgs_b(func, x0=initial_values, args=(x_true,y_true), approx_grad=True, disp=True)

exactly the same behavior as I have on Win10. Even this is due to the limitations of the IPython, I would also like to know where exactly in IPython causes this problem.


Fingerless insulated gloves

About the PR

Adds fingerless insulated gloves to the maint locker random loot pool
About as rare as real insuls for increased humor, getting fingerless insuls every three lockers would dilate the funny
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

no changelog for surprise

even how?

how lmao

oops yeah forgot the meta.json

who is jason

why does this have a vox variant.
This should use the same loot pool as insuls, not increase it if anything.

why does this have a vox variant.
This should use the same loot pool as insuls, not increase it if anything.

I removed the vox stuff
I dont know a lot about the code, please elaborate

I dont know a lot about the code, please elaborate

The gloves look identical to insuls which just dilutes information as you can't tell at a glance if something is budget insuls, insuls, or fingerless insuls.

its a joke item, it's supposed to trick you

Get better humor.

make them visually distinct and cut insuls/budgets to get them

If you can craft them from normal insuls doesn't that defeat the rarity joke?

make them visually distinct and cut insuls/budgets to get them

they are different though,

above are regular insuls
below are fingerless insuls
as you might be able to tell, the fingers were cut off

they called me madman

Loot change not reflected in the wall locker.
All three variants of insuls should be in an orgroup at this point.

do we really need more fake insul items? we already have budget insuls. This is just a less funny version of that.

hold on, wheres the butchering code, I might be able to make insuls cuttable

above are regular insuls

I had to open the images in another tab, zoom in, and physically move closer to the monitor to see a difference

you can make the same argument about regular fingerless gloves. also the sprites look bigger in game

you can make the same argument about regular fingerless gloves. also the sprites look bigger in game

I think the difference between fingerless gloves and normal gloves is MUCH less significant than insuls and fingerless insuls.
If you mistake the former you leave prints.
If you mistake the later you get zapped (and leave prints).

I think this is funny. Insulated gloves are valuable items and a few useless versions make for an interesting learning experience. The warning from the name and description already make it adequately clear that this is useless.

If you mistake the former you leave prints. If you mistake the later you get zapped (and leave prints).

if you mistake them, you deserve it.

also this isn't a competitive game, taking this as a super serious balancing change is just not how it should be recieved, this is supposed to be a rare joke item. the point is to confuse or make people laugh, not trick them

Ofc. The thing is that any reduction to insul availability reduces antag opportunities and by extension chaos (which is literally what the game is about)
Just make sure this does not reduce the chance of acquiring insuls

syndies have plenty of ways to acquire insuls that isn't getting them in maint lockers