Bug Report: Game Freezes while trying to load the last free play song (only loads easy then freezes)

It just freezes when trying to load the last free play song it only loads easy

Nevermind I fixed it


Remove trailing comma from parameters list of packages

@anweshan can you take a look at this?

@anweshan ☝


[QUESTION] Case folding of dataset namespace in URI format

Details:
https://github.com/OpenLineage/OpenLineage/pull/2826#discussion_r1665199638
User may pass JDBC URL or other connection strings in both lower and upper cases, e.g. jdbc:postgresql://host:5432/mydb and JDBC:POSTGRESQL://HOST:5432/MYDB. This may lead to producing different dataset namespaces - postgres://host:5432/mydb vs. POSTGRES://HOST:5432/MYDB.
My questions are:

Should OpenLineage case fold the scheme and authority part of URI to lowercase? Like POSTGRES://HOST:5432/MYDB -> postgres://host:5432/MYDB.
Should OpenLineage try to convert database name (MYDB) to canonical form as well? For Postgres, object names are in lower case, but Oracle prefer UPPERCASE.

#2831 converts scheme and authority to lowercase, but left intact instance/database part.


Error uploading XML file

I am trying to upload an XML using the webui with the content of the PDF file attached (funny enough this page didn't allow me to update the XML file, so, I ended up printing it as a PDF for you to have a look at the content). Before it finishes uploading it throws this error:
Initializing daemon...
Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /ip6/fd6a:f97c:3cf6:1:49e:333c:903c:871d/tcp/4001
Swarm listening on /ip6/fd6a:f97c:3cf6:1:5d70:a134:c2e9:bfc4/tcp/4001
API server listening on /ip4/<IP_ADDRESS>/tcp/5001
Gateway (readonly) server listening on /ip4/<IP_ADDRESS>/tcp/8080
Daemon is ready
15:57:38.981 ERROR core/serve: Path Resolve error: not a key gateway_handler.go:509
sample.pdf

Hi @vensa-emonzon! Sorry you didn't get any feedback on this error. A lot has changed in IPFS and the Web UI since you reported this issue, so I'm going to close this out, but if it happens again, please feel free to open another issue with steps to recreate it.


Ruby 2.3 preparedness

With 2.3 around the corner we need to make sure the code works. Right now all tests pass in 2.3 (run locally) and I don't see anything that should cause us problems. We need to make sure 2.3 is added to our Travis CI runs when it becomes available.
Ruby 2.3 is introducing a pragma to make all strings immutable by default. The though is that by Ruby 3 this will be standard. It works by adding # frozen_string_literal: true to the top of the file. Then all strings created using single or double quotes are immutable. If you need a mutable string it will need to be created using String.new.
I would like to adopt the new pragma so that people using 2.3 can get the performance benefit and we're ready for Ruby 3 ahead of time. @tfausak thoughts?

One thing to consider is that we need to make sure the string coming back from a string filter is mutable. That would be an unexpected surprise for people.

Instead of adding the pragma, why don't we .freeze all our literal strings? That way previous versions would get frozen strings and we would accidentally give frozen strings back to the user.

On second thought, freezing every string is going to be super annoying. They are created in a variety of ways that are hard to grep for. You've got normal string literals, which can be delimited with ' or '" or % and friends, and then you've got string array literals, which can be %w and friends. And then you've got things that happen to return strings, like to_s and inspect. I'd rather let the magic comment take care of things.
That being said, I think we should benchmark our codebase against 2.3 with and without frozen strings. It might not make much of a difference.


Correct this '&' to '&&'

Mentioned in #648
Issues found: https://sonarcloud.io/project/issues?resolved=false&rules=csharpsquid%3AS2178&id=nikcio_lucenenet
Check the Lucene 4.8.1 source on this to see whether this is a translation bug or a bug carried over from Lucene, and report appropriately.

If this is a bug in the translation from Java to .NET, we should simply fix it.
If this is a bug that still exists in the current version of Lucene, we should both fix it and report it to them.
If this is a bug that existed in 4.8.1 but was fixed since, we need to track down the JIRA/GitHub issue number and leave a comment indicating the issue number of the patch that has been applied. The entire patch should be analyzed and we should bring over all changes from the patch. We should also look up and include the Lucene version number(s) it was released in so we know when to remove the comment.

I'll look into this one 😄

I've tracked down this commit in the Lucene repository: https://github.com/apache/lucene/commit/55594bad9b07af90de4ab2a2fb0bac8e8c2b0b3c#diff-ccf964ce5c3d619df7e73dd7c1467cd88265240d7bdc1c35c27bfc02d669d6c8
It seems the file was deleted and I haven't been able to find it in versions 5.0.0 and above. I can see that the single '&' was still in the 4.10.4 version: https://github.com/apache/lucene/blob/69175ad4fe8d224ad6a348d05f686105999a92e8/lucene/analysis/common/src/java/org/apache/lucene/analysis/nl/DutchStemmer.java#L193
So it might just be to fix the issue.

Well, being that it doesn't make any sense to use a bitwise & operator here, it makes sense just to change it.
Looks like the current version is using the snowball stemmer: https://github.com/apache/lucene/blob/cc342ea7407c729a743123d8f7957aff6c6f9792/lucene/analysis/common/src/java/org/apache/lucene/analysis/nl/DutchAnalyzer.java. Snowball is poached from: https://github.com/weavejester/snowball-stemmer. The Snowball DutchStemmer exists in 4.8.0, but apparently, they hadn't gotten around to upgrading it yet.


Does vtkImageView2D support overlaying image

Hello everyone. I want to add a mask image(such as the segmentation mask) over vtkImageView2D. The mask image has the same dimension, same spacing and same extent as the slice image. The correct display I want is that the mask point with value 1 can display over the slice image and the mask point with value 0 does not display ( shown in picture 1). I try to use SetInput() with the mask image in a new render layer, but the result is the whole mask image cover the slice image(shown in picture 2). I review the part of paint code(paint toolbox). I can not find where vtkImageView2D is used to set mask image. It seems that medAbstractImageView is used to render the mask image, which I don't want to use. Can someone give me any guidance? Thanks in advance.

Hi ! Sorry for the delay in answering, we have been quite busy these past weeks.
I am not sure to understand fully your question. Are you trying to use vtkimageview from the medinria code outside of medinria ? Is that so ?
In any case, I can answer that yes it is able to have overlay of other images. Inside medinria this is tackled by the view system that prepares the data to be given as new layer to vtkimageview2d. This is done for example in the itkDataImage plugin inside the interactor part (SetInput methods if I remember well).
This is what I can answer from my understanding of your problem. Thanks for reaching us and your interest in medinria


Adding sysctl, returners and removal of six module

moved salt.modules.linux_sysctl to hubblestack.modules.linux_sysctl
moved salt.modules.mac_sysctl to hubblestack.modules.mac_sysctl
moved salt.modules.openbsd_sysctl to hubblestack.modules.openbsd_sysctl
moved salt.modules.netbsd_sysctl to hubblestack.modules.netbsd_sysctl
moved salt.modules.freebsd_sysctl to hubblestack.modules.freebsd_sysctl
Added salt.returners._init_ to hubblestack.returners._init_
Removal of six module

Overall changes look ok. Thanks for adding unit tests.
We need to cover the referenced code(salt imports) as well. Since we have not taken separate tasks for these.
Many of those files/functions are already added. You need to see which are the functions which are not there.


Command Buffer without world in constructor

As I was developing a prototype in DefaultECS, a thought occurred to me.
"Why are queries tied to worlds?"  - They don't deal with worlds. They only deal with entities. So do systems. Systems operate on entities (its components). To access the components of an entity, queries are often used. Queries are simply descriptions of what set of entities the system is interested in.
I really like that in Arch Worlds don't have tight relationship with systems and queries. You write world.InlineQuery<YourOperation>(query); and its possible to use same query and system with different worlds at the same time(I found this really cool)
But Command Buffers are coupled with worlds instance.
What if Command buffers would be able to work with multiple worlds?
Entity entity = buffer.Create(archetype);
buffer.Set<SomeComponent>(entity);

buffer.PlayBack(world);

Is that make sense?

Thats actually a good idea! That would work and would further decouple the buffer from the world itself.

Introduced in 5f5b058c74f257333e44fdc40266e1ea57d8f3c8


ci: dismiss stable PR approvals Graphite support

#365  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


No info on how to use docker-machine behind proxy

File: get-started/part4.md, CC @johndmulhausen
I think it would be worth mentioning how to use docker-machine behind proxy. This would be consistent with the mention of proxy settings for docker in part 2.

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


Using TemporaryError, but handler is not being called again.

Long story short
When raising TemporaryError, the custom resource create handler is not being called after delay to try again.
Description
Logs show:
│ eduk8s-operator [2020-05-05 08:12:57,051] kopf.objects         [DEBUG   ] [None/eduk8s-training-portal] Invoking handler 'eduk8s'.                  │
│ eduk8s-operator [2020-05-05 08:12:57,058] kopf.objects         [ERROR   ] [None/eduk8s-training-portal] Handler 'eduk8s' failed temporarily: Worksh │
│ op lab-k8s-fundamentals is not available.                                                                                │
│ eduk8s-operator [2020-05-05 08:12:57,058] kopf.objects         [DEBUG   ] [None/eduk8s-training-portal] Patching with: {'status': {'kopf': {'progre │
│ ss': {'eduk8s': {'started': '2020-05-05T08:12:57.050903', 'stopped': None, 'delayed': '2020-05-05T08:13:27.058567', 'retries': 1, 'success': False, │
│  'failure': False, 'message': 'Workshop lab-k8s-fundamentals is not available.'}}}}}                                                                │
│ eduk8s-operator [2020-05-05 08:12:57,065] kopf.objects         [DEBUG   ] [None/eduk8s-training-portal] Sleeping was skipped because of the patch,  │
│ 29.999904 seconds left.

but it is never retried.
What is odd is that it works fine on Minikube, and previously worked fine on a separate production grade cluster, but now the production grade cluster no longer works. Also works when run kopf on macOS connected to Minikube in place of operator running in cluster.
Going to keep trying to debug it, but suggestions on how to do that would be welcome.
Environment

Kopf version:

kopf==0.26
kubernetes==11.0.0

Kubernetes version:

1.17

Python version:

3.7.7 (in container)
3.7.3 (on macOS)

OS/platform:

Using official python3.7 docker image from Docker Hub. Presumably Debian or Ubuntu based.
Python packages installed

aiohttp==3.6.2
aiojobs==0.2.2
async-timeout==3.0.1
attrs==19.3.0
bcrypt==3.1.7
cachetools==4.1.0
certifi==2<IP_ADDRESS>
cffi==1.14.0
chardet==3.0.4
click==7.1.2
google-auth==1.14.1
idna==2.9
iso8601==0.1.12
kopf==0.26
kubernetes==11.0.0
multidict==4.7.5
oauthlib==3.1.0
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycparser==2.20
pykube-ng==20.4.1
python-dateutil==2.8.1
PyYAML==5.3.1
requests==2.23.0
requests-oauthlib==1.3.0
rsa==4.0
six==1.14.0
typing-extensions==<IP_ADDRESS>
urllib3==1.25.9
websocket-client==0.57.0
wrapt==1.12.1
yarl==1.4.2

So this is going to be the problem when using v1 of CRDs, of not allowing for kopf object in the status as examples in https://github.com/zalando-incubator/kopf/issues/321 show. IOW,
            status:
              type: object
              x-kubernetes-preserve-unknown-fields: true

or:
            status:
              type: object
              properties:
                result:
                  type: string
                  description: The result from the handler
                  enum:
                  - created
                  - updated
                # Other structured subresource schema data...
                kopf:
                  type: object
                  x-kubernetes-preserve-unknown-fields: true

I can't see that the need for using  x-kubernetes-preserve-unknown-fields: true is mentioned in the documentation, so perhaps something at least needs to be added in there in a section related specifically to v1 CRD. This of course assumes I am not blind and couldn't find it.
Was only getting this issue on the one cluster as the person who installed it there used the v1 versions of the CRDs and not the v1beta1 versions.

@GrahamDumpleton Thanks for reporting this.
Indeed, we also had few little issues on our side with these "structural schemas" of Kubernetes 1.16+ and v1beta1->v1 transition.
I've now added few special notes to the docs (#364).
The whole problem is also addressed in #331 with switching from status to annotations by default (docs). This should keep Kopf running out of the box for all CRs & builtins.
There is also a PR #339 to warn if the resulting object does match the patching intentions, but it is slightly more complicated to implement — we'll try to add it to Kopf 0.28 (with a general topic: stability & recoverability) a bit later. Otherwise, Kubernetes silently ignores the patches and returns HTTP 200 OK, despite the patch is not applied — which cause this and similar issues in Kopf.

I got another thing for you to think about (not creating separate issue for it as yet), although it goes counter a little bit to the idea of using annotations to track operator state. But then am not seeing this as something you rely on, but informational only.
I would like to see one kopf status field that tracks the overall processing state, but persists and doesn't go away when the processing of the custom resource is complete, which is usually when kopf state is removed. Whether anyone relies on this would be optional.
The issue is that when going 'kubectl get crdname', it is hard to have a 'STATUS' field as printer column which reflects overall processing state.
I would like to be able to say:
  additionalPrinterColumns:
  - name: Status
    type: string
    priority: 0
    description: Overall processing state of custom resource.
    JSONPath: .status.kopf.processingState

When CR just created and nothing done, would show empty value in 'kubectl get' output.
Once kopf/operator starts processing it, could change value based on what is happening, eg., processing, retrying, failed, error.
Importantly, when the operator has successfully finished processing and all is good, the 'status.kopf.processingState' wouldn't be removed. Instead, would be updated with value of success or complete.
This would make it much easier when using 'kubectl get' to see what is going on without delving into the YAML or using 'describe'.
The only other option is one has to have two state columns, one for kopf side which tracks something from its state (although that will stop working now if you use annotations) and another displaying something from the users status output by the operator.
Hopefully you understand what suggesting. If you want to compare it to something, imagine the 'STATUS' field of a pod.

First, to note: now, both annotations AND status are used. And in general, I would prefer status stanza, because it is a status of resource. Annotations are there only because of "structural schemas" in K8s 1.16+ by default and silent loss of payload in PATCHes of status without x-kubernetes-preserve-unknown-fields: true, see #364) — for which I have no good solution yet except as persisting in annotations.
Second: This is actually a good feature request! I.e. making the handling progress/state exposable via "printer columns", both individually per-handler and aggregated. Which includes persisting the progress after the handling is done; but also implies few more columns for better presentation.
One way, which works right now, would be to return things from handlers, which are persisted in the status under the handlers' names without cleanups (see: results delivery). But there is no aggregated result of the whole group of handlers.
This is what we do now in our apps: report from children pods and other children resource to status.children.{podname}. And in @kopf.on.field(..., field='status.children'), we aggregate and summarise and calculate the overall status as status.message. Which works, but adds a lot of boilerplate code. It would be nicer if that is supported by the framework (for children, there is https://github.com/zalando-incubator/kopf/issues/58#issuecomment-580660781; but for just handlers in general, there is no issue yet).
I never thought of reporting the handlers' statuses or the overall processing state in the printed columns.
I'll definitely think on this now!


[DEMO]React QnA, full featured and barebones

Problem this feature will solve
The starter needs demo projects. Let's start with React.
Background
Examples are great for showing what the starter can do with a single workspace URL.
Proposed Solution
Have two versions of a react demo that showcases q-and-a-challenge
Just the files needed  from q-n-a-challenge to be added to this starter project can be found in QnA-demo-skeleton

EXAMPLE ID 1: Full features

phpmyadmin, github changelog generator, laravel UI, NPM update

EXAMPLE ID 2: Barebones

None of the items above (should build much quicker)

Constraints and Assumptions
The README will need a section listing what each EXAMPLE id will give you.

Depends on https://github.com/apolopena/gitpod-laravel8-starter/issues/79


Enabling sync server makes web version super slow

It makes sense, but it's not really usable.
here's some timings for reading site-packages files:
[FG] parsing: file:///Testing_Pyright/.venv/lib/site-packages/_pytest/logging.py [fs read 0ms] (815ms)
[FG] binding: file:///Testing_Pyright/.venv/lib/site-packages/_pytest/logging.py (73ms)
[FG] parsing: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/re.pyi [fs read 0ms] (282ms)
[FG] binding: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/re.pyi (46ms)
[FG] parsing: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/enum.pyi [fs read 0ms] (226ms)
[FG] binding: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/enum.pyi (40ms)
[FG] parsing: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/logging/__init__.pyi [fs read 0ms] (491ms)
[FG] binding: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/logging/__init__.pyi (93ms)
[FG] parsing: file:///Testing_Pyright/.venv/lib/site-packages/_pytest/monkeypatch.py [fs read 0ms] (343ms)
[FG] binding: file:///Testing_Pyright/.venv/lib/site-packages/_pytest/monkeypatch.py (32ms)
[FG] parsing: file:///Testing_Pyright/.venv/lib/site-packages/_pytest/recwarn.py [fs read 0ms] (201ms)
[FG] binding: file:///Testing_Pyright/.venv/lib/site-packages/_pytest/recwarn.py (24ms)
[FG] parsing: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/warnings.pyi [fs read 0ms] (89ms)
[FG] binding: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/warnings.pyi (12ms)

The parse time is about 10x what we'd get locally.
There's something else that's weird, it seems we rebind/parse builtins over and over again:
[FG] parsing: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 0ms] (1950ms)
[FG] binding: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/builtins.pyi (395ms)
[FG] binding: file:///Testing_Pyright/test_django.py_chained___skip__completion__.py (0ms)
[FG] parsing: file:///Testing_Pyright/test_django.py (39ms)
[FG] binding: file:///Testing_Pyright/test_django.py (9ms)
[FG] parsing: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/bundled/stubs/django-stubs/db/models/base.pyi [fs read 0ms] (79ms)
[FG] binding: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/bundled/stubs/django-stubs/db/models/base.pyi (16ms)
[FG] parsing: file:///Testing_Pyright/.venv/lib/site-packages/django/db/models/base.py (59ms)
[FG] binding: file:///Testing_Pyright/.venv/lib/site-packages/django/db/models/base.py (3ms)
[FG] parsing: file:///Testing_Pyright/test_django.py_chained___skip__completion__.py (0ms)
[FG] parsing: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 0ms] (1909ms)
[FG] binding: https://ms-python.vscode-unpkg.net/ms-python/vscode-pylance/2023.12.104/extension/dist/typeshed-fallback/stdlib/builtins.pyi (373ms)
[FG] binding: file:///Testing_Pyright/test_django.py_chained___skip__completion__.py (0ms)

This is with no changes.

I think we may be using the remote file API for the dist.url as well. That would be part of the problem. We should be able to use the old way to read stuff from the dist folder.

Part of the problem here is the bundle is obfuscated. Splitting the bundle is harder than it was in AZNB because VS code rewrites the Worker object to not allow us to pass our own blob.url (where we rewrite the worker import scripts). They're passing their own blob url where they rewrite the importScripts here:
https://github.com/microsoft/vscode/blob/1be73b4a517ad5c4b6361b1fdbeedb8fc6d0d3a1/src/vs/workbench/api/worker/extensionHostWorker.ts#L131
Might need to look into computing this at runtime (and overwrite what webpack does in its calls to importScripts). Hard part is getting the distUrl to the webpack script.


feat(aws-lambda): added support for payload version format 2.0

refs #34347
https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html

[ ] manually test 1.0 and 2.0

FYI When creating a Gateway REST API with lambda proxy there is no option to define the payload format. It is currently always 1.0. When creating a AWS Gateway HTTP API you can choose between 2.0 and 1.0 [2.0 is default].


Handle non-JSON WebSocket messages as reasons for errors

And take proper actions with them (log or failover to HTTP etc..). I'll comment here what once I formulate how to handle them. Please comment if you have any ideas.
Related: https://github.com/Starcounter/Home/issues/174#issuecomment-342473427
Comment on https://github.com/Starcounter/Home/issues/174, https://github.com/Starcounter/Home/issues/340 when done.

As explained in Starcounter/Home#174 (comment), Palindrom will try to parse any WebSocket message as JSON. If the message does not parse as JSON (for example because it is a stack trace text), this is considered a fatal error end the text that did not parse will be logged as error in the browser console.

As explained in https://github.com/Starcounter/Home/issues/174#issuecomment-342473427:

Sorry for the last now-deleted comment, I misread. Maybe we can send a normal string error from the server. And in Palindrom we can simply try before JSON.parse and throw the raw message in catch and that's it. Without any protocol changes.

Palindrom will try to parse any WebSocket message as JSON. If the message does not parse as JSON (for example because it is a stack trace text), this is considered a fatal error end the text that did not parse will be logged as error in the browser console.

Level1 part is done: https://github.com/Starcounter/Home/issues/340

PR in https://github.com/Palindrom/Palindrom/pull/191


"Cached" error message from non-existent .bashrc

Windows Version
10.0.22621.2506
WSL Version
2
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu-22.04
Other Software
Docker version 24.0.6, build ed223bc
Repro Steps
Not sure how it happened, I didn't do much
Expected Behavior

If there is no .bashrc, .profile or .bash_profile, no error message should show when running wsl or bash from the terminal or wsl or Ubuntu from the start menu.
Actual Behavior
Even when moving/deleting .bashrc, .profile & .bash_profile, I get an error when doing the aforementioned action. Additionally, the error message that shows contains the string that was in the .bashrc previously but which should now no longer exist inside the VM.
Diagnostic Logs
I made a reddit thread to rant about this issue when I tried to debug what was happening and it contains some more info I don't have type to retype here:
https://www.reddit.com/r/wsl2/comments/17kosqp/weird_bug/

Apparently there's a thing called /etc/profile and I guess I knew about that before this....


Package nouveau

In order to release Nouveau in 3.4 we'd want to at least package it into our deb and rpm packages.
There are a few tasks:

Ensure deb and rpm package creation script use --enable-nouveau when configuring them. But we can't hard-code it as we might want to still patched release before 3.4
Manage optional presence of a minimum viable JRE on the users' machines.
Include some service start / stop scripts to start it and stop Nouveau

is a JRE available for running nouveau? Maybe which env-Vars?

I would say this must be user-supplied and we shouldn’t worry about it, just document that you need a JRE installed.

Include some service start / stop scripts to start it and stop Nouveau.

For the first iteration of the macOS binaries, I’m going with: I ship all the bits, if folks add a JRE, I’ll document how to start nouveau manually in a terminal. Once Nouveau is no longer experimental, I’ll hook up a nice service.


deps: update to<EMAIL_ADDRESS>

Closes #942

I believe we shall update camunda-bpmn-js, too?

Correct. I will update it.

Done via https://github.com/camunda/camunda-modeler/commit/833c3a4b7ddfd11c7499326670908e7497294cfa


merge from arlac77/template-kronos-module,arlac77/template-github

package.json

chore(scripts): add ava --timeout 2m (scripts.test)
chore(scripts): add c8 -x 'tests/**/*' --temp-directory build/tmp ava --timeout 2m && c8 report -r lcov -o build/coverage --temp-directory build/tmp (scripts.cover)

Codecov Report

Merging #666 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #666   +/-   ##
=======================================
  Coverage   85.53%   85.53%
=======================================
  Files           8        8
  Lines         560      560
  Branches       67       67
=======================================
  Hits          479      479
  Misses         80       80
  Partials        1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c8d6671...7a783e5. Read the comment docs.

:tada: This PR is included in version 7.5.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Changing Interface Return

The method root() in TreeManagerCore is returning the TreeSession. Adapt to return the Set instead.

Done.


Storybook doesn't display Docs page

MDX story is not rendering for 0.1.3 version. I see these two messages in console:
render was not supported :( !
renderToDOM was not supported :( !

MRP is available here https://github.com/morewings/forge/tree/master/packages/library-vite

I ran into something similar, although I haven't confirmed its directly related to storybook-vite

Reproduction
https://github.com/blowsie/vue3-vitesse-storybook-pnpm/tree/master/packages/ui

@blowsie can you please try upgrading to the latest version of storybook-builder-vite?

Oh I see in your reproduction that you have.  Hmmmmm.  I'll take a look.

Oh I see in your reproduction that you have. Hmmmmm. I'll take a look. This should have been fixed in 0.1.22. maybe try clearing your node_modules and browser cache, just in case?

This was a clean installation today, I rimraf node_modules a few times whilst getting things up and running, and have cache disabled in my browser when dev tools is open

@blowsie I cloned your repo, tried to npm install and got errors about artifactory, removed the package-lock.json, ran npm i (in the sub-package), and npm run storybook worked fine, showing the story correctly.  I then removed node_modules, and ran pnpm i in the root project, and then again, npm run storybook in the ui project, and that worked fine too.  I think you must somehow have an old version of the builder, perhaps in a parent node_modules.  If you're still having troubles, would you mind opening a new issue, since I don't think it's related to the one in this issue.
Speaking of which, since 6.4.0 has been released I'm going to close out this issue.  If anyone still has problems that isn't already captured in another issue, please open one with a reproduction repo, that's extremely helpful.

@IanVS just to be sure, did you check the docs tab?

@blowsie yep, works fine!


Improve warning for ignored values in sequence expressions - fixes #4228

fixes #4228

ping @KevinRansom @dsyme for review

Awesome work, thank you
It's possible a similar improvement could be made for async expressions?


Remove email and phone number with the customer service link in footer

Description
Pretty self-explanatory.
Setup
Add any steps or code to run in this section to help others prepare to run your code:
make server_run
make client_run

Code Review Verification Steps

[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

Screenshots

🚢


Manual Create User with access Token

I am developing a Mobile API for social Auth.
Once received Social access token and email from API, I want to create a social user based on Email ID received. Creating just a user(with received emailID) will not work.
Is it require to create a record in User Social Auth Model too?

@jas-odoo What exactly do you mean by social user?


Select item by value

Is your feature request related to a problem? Please describe.
I would like to select an item by value and not by label
Describe the solution you'd like
Having a selectByValue that works like select

Hi @franckLdx, thank you for your feedback, I will implement this feature asap.

Hi @franckLdx, thank you for your feedback, I will implement this feature asap.

Hi @franckLdx , I have published v1.17.0 with the feature you have asked for.

Hi @franckLdx , I have published v1.17.0 with the feature you have asked for.


Release 3.17.0

Features

Allow non-owners to execute confirmed (rejection) transactions (#3151)
Use public RPCs for suggested wallet configs (#3167)
configurable GATEWAY_URL (#3186)

Improvements

Add name and address to modules (#3125)
Add Safe load error (#3251)
Increase backoff cap loading safe (#3226)
Use generic Discord link (#3235)
Persist local tx statuses (#3211)
Migrate owner management to Safe Core SDK (#3056)

Fixes

New tx nonce never smaller than the current Safe nonce (#3191)
Remove email + update Discord link (#3233)
Remove uncaught transaction execution promise (#3258)
Fix: Increase clickable area of Add Safe button (#3242)
fix: Reference connected user to show tx actions (#3253)
Fix: return if transactionsToGo is NaN (#3245)
Fix: redirect when invalid chain prefix in URL (#3228)
Fix: Use recommended nonce for already executed nonce message (#3227)
fix: Remove bottom margin on close button (#3238)
fix: Truncate long token name (#3237)
Fix: deeplink nonce order (#3217)
fix: Append further grouped, next txs (#3213)
Fix: deeplinked, out of nonce order transactions allow confirmation  (#3210)
Fix desktop app bundle (#3212)
Fix: use estimations v2 endpoint for tx nonce (#3201)
Fix: deep-linked tx status and internal state (#3156)
Fix: catch spending limits error (#3174)
Fix: deep-linked tx – use current timestamp as fallback (#3146)
Fix: Errors in console while tx is in "pending" status #3274

Chores

Migrate Safe Apps endpoint to load directly from CGW (#3195)
Remove transaction service usage (#3189)
chore: Add GA appearance/EIP-3770 tracking (#3177)
Chore: unpromisify localStorage (#3181)
Chore: add a debug toggle for prod CGW (#3180)
Chore: staging backend on the staging site
prefix envs with REACT_APP_ (#3198)

Electron app

Allow cert errors only for the Electron backend (#3208)
Make Electron server listen only on localhost. (#3206)
Pin the action to a hash instead of a tag (#3207)

Issues found:
Issues fixed:

[x] https://github.com/gnosis/safe-react/issues/3280
[x] https://github.com/gnosis/safe-react/issues/3289
[x] https://github.com/gnosis/safe-react/issues/3197
[x] https://github.com/gnosis/safe-react/issues/3261
[x] https://github.com/gnosis/safe-react/issues/3267
[x] https://github.com/gnosis/safe-react/issues/3274
[x] https://github.com/gnosis/safe-react/issues/3275

Still I got again the issue with the "cancelled" status in non-rinkeby safes when executing a tx. Can we check with the guys from backend if there are issues there that might cause this? At least know it if it comes to happen in prod
Steps: 1 out of x signatures, create a tx and execute it right away, in non-rinkeby networks.

Besides this I didn't find anything else that worries me for release

It looks like this cancelled status is coming from the backend. No bueno per se but it's a not a regression.


Convert old string formatting to new formatting

Sorry can't accept it since the project is superseded by torrt and I have no further intention to push it forward. We probably need a GUI for torrt but another story.

Ohkay


@docusaurus/plugin-content-docs-types missing from plugin-content-docs/package.json

https://github.com/facebook/docusaurus/blob/83c5e2ae34765fbd3838432e93048d7eac5fbb25/packages/docusaurus-plugin-content-docs/src/index.ts#L41

What should done here?
I can handle it if no one working on it.
I think i just have to add '@docusaurus/plugin-content-docs-types' to package.json. is it right?

What should done here?
I can handle it if no one working on it.
I think i just have to add '@docusaurus/plugin-content-docs-types' to package.json. is it right?

Yep.
On Sun 24. Jan 2021 at 20:24, Ali Hosseini<EMAIL_ADDRESS>wrote:

What should done here?
I can handle it if no one working on it.
I think i just have to add '@docusaurus/plugin-content-docs-types' to
package.json. is it right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/4057#issuecomment-766417291,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACEWRNHCKTRAADMZTJHMO3S3RXYNANCNFSM4WHPXFUQ
.

Yep.
On Sun 24. Jan 2021 at 20:24, Ali Hosseini<EMAIL_ADDRESS>wrote:

What should done here?
I can handle it if no one working on it.
I think i just have to add '@docusaurus/plugin-content-docs-types' to
package.json. is it right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/4057#issuecomment-766417291,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACEWRNHCKTRAADMZTJHMO3S3RXYNANCNFSM4WHPXFUQ
.

Hey @vjpr, if this is still pending, I'd love to get it done.

still pending @rajrajhans 👍 just one ine to add :p

Yep, just needed some clarification. I couldn't find any package named @docusaurus/plugin-content-docs-types. However, I did find that PermalinkToSidebar is being exported from here. Considering this, shall I still proceed adding @docusaurus/plugin-content-docs-types as a dependency in package.json or should I change index.ts to import it from here?
PS: I'm a novice in TypeScript, so do let me know if I'm making any mistake : )

Hi I have made the changes and created a pull request please review it.
First timer here :)

https://github.com/facebook/docusaurus/pull/4149

https://github.com/facebook/docusaurus/pull/4150

I'm sorry, I finally think there's nothing to be done here.
@docusaurus/plugin-content-docs-types is not a package but an ambient TS declaration, not sure what you want to be done @vjpr , please re-open a new issue with better context, as I'm not able to figure out what we should do

I wanted to fork the docs-plugin. I copied the folder to my monorepo. Then it fails to build because it cannot find this package which is required for building.
If a package is referenced from a file it should be included in the package.json. Even if it is just types.

@vjpr but there is no such package 😅 it's TS declaration here: docusaurus-plugin-content-docs/src/plugin-content-docs.d.ts

How does it get resolved? Is it an alias or some configuration of tsc
maybe. Sorry I am on phone and cannot look at code myself right now.
Maybe I got around it in a different way.
On Tue 2. Feb 2021 at 15:25, Sébastien Lorber<EMAIL_ADDRESS>wrote:

@vjpr https://github.com/vjpr but there is no such package 😅 it's TS
declaration here:
docusaurus-plugin-content-docs/src/plugin-content-docs.d.ts
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/4057#issuecomment-771669930,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACEWRPZDWE6LKENXGU3EBDS5ADMFANCNFSM4WHPXFUQ
.

@slorber @vjpr  It is failing to build because it is imported from that package which doesn't actually exist. Instead, it should be imported from this file

Ah, okay - this is where the module is being defined. I was unfamiliar with this ambient creation of type data.
declare module '@docusaurus/plugin-content-docs-types' { <---
  export type PermalinkToSidebar = {
    [permalink: string]: string;
  };

@slorber Is this a common pattern in TS? Why would you not just export the types without wrapping them in this "virtual" package.
@docusaurus/plugin-content-docs/types or something like that.

I agree that there is something weird in our current TS setup.
Unfortunately, I don't have much time to fix these issues right now, but yeah I'd rather have regular imports than ambient TS defs.
The thing is I'd like content plugins to expose both server/node code and browser code APIs, both with proper typedefs (not handwritten ones). We are not there yet 😅


Add "freebsd" as an operating system filter

Is your feature request related to a problem? Please describe.
I use zot to manage both linux and freebsd images and filtering for freebsd would be useful.
Describe the solution you'd like
The 'Operating systems' pane on the 'View all' page should include "freebsd" as well as "windows", "linux".
Describe alternatives you've considered
None
Additional context
None

@dfr close this issue since your PR has been merged?


fix: update config.yml

Interchanged c1r1p2 with c1r1p1 to order them correctly

Thanks, and yes, the list of hosts matches up with the maps of the clusters.

Good job @ssim22


BEiT with smaller patch sizes

I tried training a ViT model with the BEiT procedure using smaller patch sizes (i.e. 8 x 8) by changing args.second_input_size to 224 instead of 112 - was this tried before in the experiments accompanying this behavior? The loss seems to decrease to a higher number than the default run with 16 x 16 patches.

Hi @linden-li , we haven't tried the above setting. The argument --num_mask_patches can also be changed to keep the masking probability the same.

Hi @linden-li , we haven't tried the above setting. The argument --num_mask_patches can also be changed to keep the masking probability the same.

Hi，have u testified  the effect of mask ratio for beit.


Transfer to FLORIS v4

FLORIS v4 adaptation
FLORIS v4 was released and OFF will change its interface to the new code.
Necessary changes entail

[ ] New wake model
[ ] New wake solver interface (?)
[ ] Adapted input files
[ ] tbd

Possible extensions could include the use of new FLORIS v4 features. This includes, but is not exclusive to

[ ] turning off turbines
[ ] AWM control

Hey @MarcusBecker-GitHub I'm happy to help here however I can. Just let me know if / how I can help.

Thanks for the offer @rafmudaf !
Today I got it working - the main "issues" were that OFF generates the input files for FLORIS, that needed a bit of fixing, and how the results are retrieved. But everything was resolved fairly quick. Overall a smooth transition.
Now I am working on the flow field visualization.

Plotting works!
Each tile is an individual FLORIS simulation used to approximate the flow conditions at the location of the respective turbine.
The code automatically assigns the grid points to each simulation, only a sufficient resolution is needed.
There is even a version of the plot where every FLORIS simulation has one of 5 colormaps, to highlight that different simulations are taking place at the same time.
Normal tile plot

5-color tile plot (not scaled yet)


selfhost/typechecker: Typecheck structs

I've been working on porting this for a while now :^)
I can't really check if everything is working as it is supposed to, as struct codegen is not implemented yet. But in order to work on codegen we need to typecheck first anyway.
This PR will conflict with #701 as both implement resolve_type_var().

@jntrnr Yes, I noticed that. I didn't mention it in my comment, but I took a look at all the tests that pass with the current version of main and fail in my branch. Here are the 8 tests my branch fails that main passes
[ PASS ] samples/enums/empty_enum.jakt
[ PASS ] samples/enums/parse.jakt
[ PASS ] samples/weak/question_mark_required.jakt
[ PASS ] samples/weak/reject_immutable_weak.jakt
[ PASS ] tests/codegen/out_of_order_types.jakt
[ PASS ] tests/parser/enum_correct_typename_in_typed_variant.jakt
[ PASS ] tests/parser/unclosed_brace_in_enum.jakt
[ PASS ] tests/parser/unclosed_brace_in_ref_enum.jakt

and here's the 1 test my branch passes that main fails
[ PASS ] samples/namespaces/hello_namespace.jakt

The reason they pass in main is that they do not expect an output and since main does not try to typecheck structs or classes, it just acts like they aren't even there. So all such tests that expect no output think that main passes them, even though it does not correctly typecheck them. Whereas in my branch those tests will run into todo(...) calls in the typechecker and fail. :^)

@greytdepression - ah okay, so they'll break but they're breaking because more is getting checked rather than ignored.
Sounds like we're good to land?
For the clash, do you want #723 to land first and then rebase this PR?

@jntrnr Sure, sounds good! I'll just wait for #723 then

should be in now

@jntrnr Rebased and passing checks :^)


sa id number is outdated

Hello tacking down your code is great but we no longer officialy use the "race digit" and  you can just set this to either 8/9 it will become valid again
line: 158         $raceDigit = 8;//self::randomNumber(1);
file: vendor/fzaninotto/faker/src/Faker/Provider/en_ZA/Person.php
i am a bit new to git or i'd just send ya a pull request or something ?

yes please open a pull request to fix this.

wonderful i believe i have done this
#1358

@majamusan You forgot a comma
-         $raceDigit = self:numberBetween(8,9);//self::randomNumber(1);
+         $raceDigit = self:numberBetween(8, 9);//self::randomNumber(1);

dhow! was a busy day :(

Sorry, not a comma, but a space after the comma! I think the build will pass after that. Run make sniff test, it's in the contribution file.

danki, fraid i can't run it localy
On 27 November 2017 at 13:43, Pieter Pelgrims<EMAIL_ADDRESS>wrote:

Sorry, not a comma, but a space after the comma! I think the build will
pass after that. Run make sniff test, it's in the contribution file.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fzaninotto/Faker/issues/1357#issuecomment-347158015,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEe3a9COKLIpuZa0Yd5FlLvfq64O83-Bks5s6qBKgaJpZM4Qj2_p
.

--
Jamie
www.earthling.za.org

Just make another commit in your PR and the CI tests will run again, they'll probably pass.

sorry too new to this, i made another request
#1364

I use this as a guideline how to do forks and pull requests: https://gist.github.com/Chaser324/ce0505fbed06b947d962
The errors are listed here per php version: https://travis-ci.org/fzaninotto/Faker/builds/307919260 return types were only introduced in php7.
Did you run composer install for this package? Otherwise you will not have a vendor folder and phpunit will not work.

Fixed by #1354


Issue on page /intro.html, BEM introduction is too mathsy

As mentioned by @jahargreaves , things like $\Omega\subset\mathbb{R}^n$ will scare a lot of people away instantly. This needs to be made more accessible.

I think this has been addressed now, but there are some strange formatting issues going on?


Cordova android branch

marge android branch into swift branch
to change app name from Cordova_Qa_App to Example_App

need to fix marge conflicts

need to fix marge conflicts


Switch component

Everything is great. But I miss the main feature of the component - control it via v-model )

Decided to implement with Vue3 approach using defineEmits as in Alert component
If I get correctly we can control this way as well as via v-model?

@RustemYuzlibaev, I think the best way to implement it is to use modelValue as prop and update:modelValue as event, so it will be possible to use switch component like this:
<SSwitch v-model="checked" />


Fix #310,  No File Found Documentation Workflow

Checklist (Please check before submitting)

[x] I reviewed the Contributing Guide.
[ ] I signed and emailed the appropriate Contributor License agreement to<EMAIL_ADDRESS>and copied<EMAIL_ADDRESS>
Describe the contribution
Fixes #310
Workflow was failing due to files not persisting between jobs. Used cache action.
Testing performed
Tested on fork: https://github.com/ArielSAdamsNASA/cFS-JSF-Rules/actions/runs/1057135024
Expected behavior changes
PDFs should generate.
Additional context
PDFs will generate when push on main branch.
Contributor Info - All information REQUIRED for consideration of pull request
Ariel Adams, ASRC Federal

@ArielSAdams could you squash?

@ArielSAdams could you squash?

Having issues trying to fix the conflicting files and squash them.

@ArielSAdamsNASA can you see if my fixes look right?
https://github.com/astrogeco/cFS/actions/runs/1057482277/workflow

@ArielSAdamsNASA can you see if my fixes look right?
https://github.com/astrogeco/cFS/actions/runs/1057482277/workflow

Looks good!


Update README.md with live link and screenshot

Has this been assigned yet?

Hi @Tamsauce,
Can you take a look at this one instead?


Fix the "Escaping Interpolated Strings" documentation

MarkupLineInterpolated instead of MarkupInterpolated
Use an actual interpolated string in sample code to make it valid

Merged! Thank you for your contribution. Much appreciated! 👍


Auto set QEMU_IRIX if qemu-irix can be found in $PATH

I mean, I don't think many people would have a different qemu-irix in their $PATH, so having make assume it's the correct one would probably be helpful.

I think we're working on something like this atm


Added support for Ledgers informations

The Ledgers API call documented here was missing.

Thanks for your contribution!


Out of Memory error

This may be an upstream issue, but with this fork, the error is different, so I'll just post this here as well.
Step 4 does not execute (for example 1) on a K80 with 12gb vram.
...
loading matting laplacian...    gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
<csv>   parsing file: gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
PANIC: unprotected error in call to Lua API (not enough memory)
...

I've reduced the image size in mattinglaplacian.py from 700 to 500 and it seems to run. There should cli args for single file processing and image size. I'll see if I get around to this.

Result with size 500:

I have no idea if this is the result of simply changing the one value in the python script. Maybe the input files also need to be adapted somehow.

I have the same issue. When trying to use deepmatting_seg.lua, I get the following errors:
loading matting laplacian...    gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
<csv>   parsing file: gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
PANIC: unprotected error in call to Lua API (not enough memory)

loading matting laplacian...    gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
<csv>   parsing file: gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
/home/ubuntu/torch/install/bin/luajit: not enough memory

I believe this issue is related to Lua's 2GB memory limit, and not one's GPU.

Wow, this seems extremely silly to me. Maybe someone with Lua knowledge could work around this? Apparently, not all kinds of objects count towards the memory limit.

Well, turns out this is the reward:
$ make clean && make
find . -type f | xargs -n 5 touch
rm -f libcuda_utils.so
/usr/local/cuda-7.5/bin/nvcc -arch sm_35 -O3 -DNDEBUG --compiler-options '-fPIC' -o libcuda_utils.so --shared cuda_utils.cu -I/home/ubuntu/torch/install/include/THC -I/home/ubuntu/torch/install/include/TH -I/home/ubuntu/torch/install/include -L/home/ubuntu/torch/install/lib -Xlinker -rpath,/home/ubuntu/torch/install/lib -lluaT -lTHC -lTH -lpng
cuda_utils.cu(510): error: identifier "luaL_openlib" is undefined

1 error detected in the compilation of "/tmp/tmpxft_00006ef4_00000000-9_cuda_utils.cpp1.ii".
make: *** [libcuda_utils.so] Error 2

Hi guys. A problem with the original repo was that some flags were missing that help reduce memory footprint a fair bit. I didn't add them back when I forked, but have added them now. Another potential issue is that it may depend somewhat on how your environment is built. I'll post a dockerfile shortly that has worked for me (I made a small change and just want to check that it builds OK before committing). I can run  500 width images on my 980tis (6GB) using this.

@themightyoarfish If you drop to 500 in the matting laplacian script you also need to downscale all of the images too - so I suspect that is what generated the odd results.

I thought the memory issue is some lua-specific thing and not related to GPU memory. But I'm happy to be proven wrong.

That might be an issue too, but certainly I've got results out at 500 width without running into it.

Yes, at 500 it worked for me too, but I had those flags enabled, so I don't actually know if my reducing the image size made it work.

@ProGamerGov So the problem with Lua 5.2 seem to be that Torch doesn't really work well with it, several people have had the issue that luarocks install cutorch fails complaining about absent cwrap module, although that one installs successfully. I haven't found anything definitive, only this comment from 2 years ago stating that at that point, LuaJIT was the only way to go.

@themightyoarfish Even with the cudnn flags I can't run at 700 with 6GB GPU.

The Lua memory errors always happen after this line is printed:
<csv>   parsing file: gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
Which leads me to believe that the problem is that parsing the CSV takes too much memory for Lua, to handle properly.

It looks like the issue is with the file size of the .csv file, LuaJIT gives the error /root/torch/install/bin/luajit: not enough memory After a few seconds of processing this line of code:
local CSR = torch.Tensor(csvigo.load({path=CSR_fn,header='false',mode="raw"})):cuda()
Which indicates to me that LuaJIT is the culprit of the memory issue. I have tried a Lua5.2 installation of torch but can't seem to get it to work with the script. Changing the tensor to store within GPU memory still results in the 'not enough memory' error which might mean the process of loading the file through csvigo causes the memory error. Does anybody more experienced than me know how to either increase the LuaJIT memory limit, or run csvigo directly into GPU memory, or run Lua5.1 for csvigo and LuaJIT for everything else.

There is a "large" option in csvigo - designed for reading large files - but it didn't seem to work for me. May be worth a look if someone has chance.

@ProGamerGov  Did you downsize all the images, targets, segmentation as well as as dropping the parameter to 500. The sizes and parameter all have to agree to the pixel, which is pretty annoying. It'd be better to have one overall size parameter and add a resizing wrapper in gen_py.all.

Using the "large" option in csvigo fixed the memory issue however there is now a new issue with CSR:size(1) & CSR:size(2) being 'out of range'.
loading matting laplacian...	gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
<csv>	parsing file: gen_laplacian/Input_Laplacian_3x3_1e-7_CSR1.csv
<csv>	parsing done
Exp serial:	examples/final_results
Setting up style layer  	2	:	relu1_1
Setting up style layer  	7	:	relu2_1
Setting up style layer  	12	:	relu3_1
Setting up style layer  	21	:	relu4_1
Setting up content layer	23	:	relu4_2
Setting up style layer  	30	:	relu5_1
/root/torch/install/bin/luajit: deepmatting_seg.lua:300: bad argument #1 to 'size' (out of
range) stack traceback:
  [C]: in function 'size'
  deepmatting_seg.lua:300: in function 'MattingLaplacian'
  deepmatting_seg.lua:269: in function 'opfunc'
  /root/torch/install/share/lua/5.1/optim/lbfgs.lua:66: in function 'lbfgs'
  deepmatting_seg.lua:296: in function 'main'
  deepmatting_seg.lua:623: in main chunk
  [C]: in function 'dofile'
  /root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:150: in main chunk
  [C]: at 0x00405d50

@Multiboxer  Yeah, it seemed to me that the result was just empty when i tried. Good for memory, bad for getting stuff done!!

Alright fixed the memory issue by switching over to torch to load the CSV file, so csvigo is no longer needed in deepmatting_seg.lua. Just gonna clean up the code a bit and post.

Seems the first few lines of the CSV being read are a little off, resulting in corrupted looking results like this:

Here is what I have so far anyway
deepmatting_seg.lua.zip
Gonna have to fix this.

@Multiboxer Does the CSV file have headers?
[Line number 130]https://gist.github.com/ProGamerGov/1524e9710a576586042114fefa06b229#file-deepmatting_seg-lua-L130), has a line of code omitting the first row:
local ROWS = i - 1

Yeah, the results vary quite a lot even if its just one or two incorrect lines in the CSV variable. I'm gonna try and output the variables of the csvigo and torch approach in a text format and compare the files to see if I can find out what is going wrong.

Yeah the header was the issue, it was deleting a non existent header.
Here is the (hopefully) fully working version of the script:
deepmatting_seg.lua.zip

Thanks @Multiboxer. I incoporated your code - seems to be working well!


README - Added Toolchain section

@dgrove-oss  or @seabaylea  or anyone involved with the Linux Swift port to proofread this please

I actually got this info from @seabaylea page in github:
https://gist.github.com/seabaylea/cad7808615c52cfd2fc9d1debcad832f

I'm not disputing that, but since I never build for linux or almost, I'd rather have someone who does review, that's the point of the review process :)

Got back from vacation today; will dryrun instructions by tomorrow.  At first glance they look like they will work.
However, do we want this level of detail in README.md?  The INSTALL file has similar (and more detailed) information about building a Swift toolchain that includes libdispatch using utils/build-script --libdispatch -- --install-dispatch.  Perhaps README.md should have an explicit pointer to INSTALL for building/install instructions (since this PR suggests that it isn't obvious where to find the information).

It is ok to have this info in INSTALL and point to it from README.md however can we change INSTALL file to be INSTALL.md (mark down format) just like README.md ?
Sent from my iPhone

On Aug 8, 2016, at 10:37 AM, David Grove<EMAIL_ADDRESS>wrote:
Got back from vacation today; will dryrun instructions by tomorrow. At first glance they look like they will work.
However, do we want this level of detail in README.md? The INSTALL file has similar (and more detailed) information about building a Swift toolchain that includes libdispatch using utils/build-script --libdispatch -- --install-dispatch. Perhaps README.md should have an explicit pointer to INSTALL for building/install instructions (since this PR suggests that it isn't obvious where to find the information).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I agree this should live in INSTALL

@MadCoder: any objection to having @amraboelela  include changing INSTALL to INSTALL.md when the pull request is updated?

nope, fine with me

Does that mean I have to do the change and then make another pull request?
Sent from my iPhone

On Aug 8, 2016, at 1:47 PM, David Grove<EMAIL_ADDRESS>wrote:
@MadCoder: any objection to having @amraboelela include changing INSTALL to INSTALL.md when the pull request is updated?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yeah, I agree that this fits better in INSTALL, which should become INSTALL.md. In fact, the whole document could do with refactoring/cleanup.
In terms of the content, I would remove the information on commenting out the tests, and just state that (currently) you have to add libdispatch and install-libdispatch to the build-presets.ini. That should go away shortly once there's libdispatch is fully integrated into the toolchain.
@amraboelela You can either do the work in your existing branch and squash your commits, or create a new PR.

Done. Please check.

@seabaylea please review, and if it feels ok @amraboelela  please squash in a single commit

I was trying to do the squash but I failed :)
Any help is appreciated

Here's my "goto cheatsheet" for squashing commits: https://github.com/ginatrapani/todo.txt-android/wiki/Squash-All-Commits-Related-to-a-Single-Issue-into-a-Single-Commit

Created new pr #136


Godot4 Support

I've added support for Godot4 at least the video publish is working perfectly and much faster with the new version of Godot4 with Vulkan.

@RDaneelOlivav this is super super cool work!!!! I am interested since it sounds like you've tried it out with Godot 4: did you try anything yet related to their new GDExtensions feature? I think that is eventually what this module should use...but there still isnt much documentation for it lats time I looked.

@flynneva Hi! We did a video showing this, we will release it next week I think .
I downloaded the latest version of the main branch of Godot4, didn't test that GDExtensions I'm afraid.
I would like to do a small tech demo with more ROS2 related game, like a robot or so, but depends on our schedule. At least it seems that it works really well.

@RDaneelOlivav I've made the edits I talked about above with #6 and went ahead and merged it. LMK if you have any questions / issues with it and we can edit it.


Work Item linking

DO NOT MERGE

Can one of the admins verify this patch?

[test]

[test]

whitelist @harrybabu

[test]

[test]
@harrybabu please let us know when this is ready for review.

[test]

@harrybabu @sanbornsen @joshuawilson do we need to consider a work item link entry component in a manner similar to work-item-list-entry.component?

Try to create a new link while there is no linked item
Click on the arrow right by "0 Total links"
This comes up -
Click on the Create link button
It shows -
Do nothing and close the accordion.
Reopen the accordion and it shows the second screen instead of first.

@mindreeper2420 is it expected?

UX verify 2

Open the link accordion.
This comes up -
Change the details page by clicking any other item on list and it stays open for that item too.

@mindreeper2420 is it expected?

Link type in the drop down stays left aligned as per the design -

IDs should be listed with the item names in suggestion in bold.
The hover highlight background design seems broken.
Suggestion box has no fixed height, which leads to a parental scroll.
No error message anywhere on trying to link unsupported item.

There should be some instruction of the linking definition based on the link type, otherwise how will user understand what are the items can be linked with the current item?
With my understanding, it should work like this -

Based on current item's type we fetch the available link types for the link type list.
Based on what user selects on the list we show the search results.

@Mgranfie @essjaysee can either of you look at this as well?

@team remember that UX completion is not necessarily required for story completion.

@michaelkleinhenz With the UX having completed designs for this, shouldn't a requirement of the story be that they are verified with UX before including in the production environment? If UX review is a blocker due to time, then there will most likely be issues filed against it once in production.

@mindreeper2420 agreed, just saying that if we can break out a part of the story to do it in a later sprint is better than blowing the whole story for this sprint. So if there is a real implementation blocker of UX not yet implemented, then we can do this in a seperate story or a (known) bug next sprint.

That's a huge PR. From the code level, it looks ok. I am a bit concerned about the scss definitions all on top level, but that's a minor and a general problem. We need to use hierarchies there or we will end up in hell when the system gets more complex.

Checked it out. In inmemory mode it drops errors when I open a detail view of a work item:
user.service.ts?9fae:70 An error occurred Response {_body: Object, status: 404, ok: false, statusText: "Not Found", headers: Headers…}
VM1691:54 Error: Uncaught (in promise): Response with status: 404 Not Found for URL: null
I think it does not use inmemory service, right?
With demo.almighty.io, it also runs errors, but these seems to be some CORS mismatch:
XMLHttpRequest cannot load http://demo.api.almighty.io/api/workitemlinktypes. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://<IP_ADDRESS>:8088' is therefore not allowed access. The response had HTTP status code 404.

Try this - to get the functional tests running cleanly again.
In work-item-detail.page.js:
REPLACE THIS:
   workItemTitleDiv:  {         get: function ()         {        return element(by.id("title-click-div")); }   },
WITH THIS
   workItemTitleDiv:  {         get: function ()         {        return element(by.id("wi-detail-title-click")); }   },

Wait - there is something else going on....

On Mon, Nov 28, 2016 at 10:36 AM, Sudipta Sen<EMAIL_ADDRESS>wrote:

Try to create a new link while there is no linked item
Click on the arrow right by "0 Total links"
This comes up - [image: screen shot 2016-11-28 at 8 56 20 pm]
https://cloud.githubusercontent.com/assets/2410474/20673990/3265e0e6-b5ad-11e6-8033-14ab1cd71dbc.png
Click on the Create link button
It shows - [image: screen shot 2016-11-28 at 9 00 33 pm]
https://cloud.githubusercontent.com/assets/2410474/20674135/bb564328-b5ad-11e6-967b-98d5276c03c4.png
Do nothing and close the accordion.

Which Accordion?

Reopen the accordion and it shows the second screen instead of
first.

a. Yes. The accordion can be sticky and stay opened. Let's see how that
feels. LMK when it's in and we can check it out.
b. If the second accordion to enter data has fields that are populated, can
these be sticky and persist the choice, during the log in or browser
session? If not, and it's easier to clear the fields, then we don't and
address at a later time.

LMK if you have more ?'s.
Thanks,
Monica

@mindreeper2420 https://github.com/mindreeper2420 is it expected?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-ui/pull/314#issuecomment-263303024,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq2lAWHKtK8i0eGOlCNu5U9ZmNk6Mks5rCvUXgaJpZM4KxD-z
.

Yes, this is left aligned text and the DD field a little smaller : )
Also am thinking we don't need the comma "," after "to".
On Mon, Nov 28, 2016 at 10:43 AM, Sudipta Sen<EMAIL_ADDRESS>wrote:

Link type in the drop down stays left aligned as per the design -
[image: screen shot 2016-11-28 at 9 11 23 pm]
https://cloud.githubusercontent.com/assets/2410474/20674570/7b4f5d58-b5af-11e6-9fac-0e6c89e60f9c.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-ui/pull/314#issuecomment-263304934,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq6v-gL5mecoe8FpCzr-8CjeRbvNJks5rCvaZgaJpZM4KxD-z
.

On Mon, Nov 28, 2016 at 10:49 AM, Sudipta Sen<EMAIL_ADDRESS>wrote:

[image: screen shot 2016-11-28 at 9 15 08 pm]
https://cloud.githubusercontent.com/assets/2410474/20674687/d70ae6da-b5af-11e6-996b-bfff61671b84.png

IDs should be listed with the item names in suggestion in bold. (MG)Yes,
if you can, otherwise no highlighting until mouse over and click.

The hover highlight background design seems broken.

Suggestion box has no fixed height, which leads to a parental
scroll. (MG) The two fields should be the same height. Here is the PF
link to the DD field and the CSS with height.
calendar.google.com/calendar/render?tab=mc#main_7

No error message anywhere on trying to link unsupported item. (MG) This
can use the PatternFly inline error treatment, showing ONLY the red error
text under the field with selected WI. Although can we detect and not show
an unsupported WI? If we can't here is the link to the under field error
return in PF. Please ignore the banner error, we will not use that here.

http://www.patternfly.org/pattern-library/forms-and-controls/errors-and-validation/#/api

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-ui/pull/314#issuecomment-263306918,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwqyXpKI8O_o4xrDDiKJ8rj3NFn-c6ks5rCvgZgaJpZM4KxD-z
.

What are the challenges with the nested accordions and will the suggestions
offered here resolve these issues?
thanks,
Monica
On Mon, Nov 28, 2016 at 3:00 PM, Adam Jolicoeur<EMAIL_ADDRESS>wrote:

@mindreeper2420 commented on this pull request.
In src/app/work-item/work-item-list/work-item-detail/work-
item-link/work-item-link.component.scss
https://github.com/almighty/almighty-ui/pull/314#pullrequestreview-10402241
:

@@ -0,0 +1,129 @@
+@import "../../../../../assets/stylesheets/custom";
+@import "../../../../../assets/stylesheets/mixins";
+@import "../../../../../assets/stylesheets/color-variables";

@michaelkleinhenz https://github.com/michaelkleinhenz @joshuawilson
https://github.com/joshuawilson I believe these can all be contained
within the parent scss file and still compile properly? Seems like a large
amount of subnavs to go through...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-ui/pull/314#pullrequestreview-10402241,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq7Y4cyiR2RdEC2bvzw33TfOUw6AOks5rCzLvgaJpZM4KxD-z
.

The html that is being generated looks correct - but whatever changed is preventing Jasmine/Protractor from finding some elements - and these elements (e.g., work item title) are used in multiple tests which are now failing.  None of this is a problem with what's currently in master.
https://github.com/almighty/almighty-ui/pull/314
....FF..FFF............F................FF.........   (firefox)
....FF..FFF............F................FF.........   (phantomJS)
After https://github.com/almighty/almighty-ui/pull/314#issuecomment-263349932
.........FF.............................FF.........   (firefox)
....FF..F.F.F..........F..F.F..................F.F.   (phantomJS)
Question - What changed in the display of the workitem page - http://localhost:8088/work-item-list?

@ldimaggi i havent changed anything on workitem page - http://localhost:8088/work-item-list.
problem looks strange

[test]

[test]

[test]

[test]

Approving this PR. Created #368 and #369 for tracking two comments.

[test]

Hi Len,
I don't completely understand the issue that you explain.
It sounds like the design somehow degrades in those browsers?
What I am trying to understand is if we need to tweak the designs at all,
and or are we targeting these browsers and how should the experience
degrade to make them operable. If we need to do this, what is
programmatically possible?
If this is strictly a coding challenge, lmk. Otherwise, just trying to
understand so we can work out a solution, if it's the design that is the
challenge.
Thanks,
Monica
On Tue, Nov 29, 2016 at 6:59 AM, Konrad Kleine<EMAIL_ADDRESS>wrote:

@kwk requested changes on this pull request.
As discussed on Bluejeans, the target WI of a link doesn't render the link
but only the source WI does.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-ui/pull/314#pullrequestreview-10520121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq0S467-01NeQQUjMdlvzxat5NEcoks5rDBO9gaJpZM4KxD-z
.

Hey Great demo today! This is looking really good.
There was one outstanding issue around navigating to a referenced work
item. This was not in the original requirements and we have not thought
through the interaction and navigation around this scenario.
We can create a story for this and address it moving forward. If we feel
this is a high priority need to get in now, let me know and we can look at
reworking our sprint items.
Thanks,
Monica
On Tue, Nov 29, 2016 at 8:22 AM, Monica Granfield<EMAIL_ADDRESS>wrote:

Hi Len,
I don't completely understand the issue that you explain.
It sounds like the design somehow degrades in those browsers?
What I am trying to understand is if we need to tweak the designs at all,
and or are we targeting these browsers and how should the experience
degrade to make them operable. If we need to do this, what is
programmatically possible?
If this is strictly a coding challenge, lmk. Otherwise, just trying to
understand so we can work out a solution, if it's the design that is the
challenge.
Thanks,
Monica
On Tue, Nov 29, 2016 at 6:59 AM, Konrad Kleine<EMAIL_ADDRESS>wrote:

@kwk requested changes on this pull request.
As discussed on Bluejeans, the target WI of a link doesn't render the
link but only the source WI does.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-ui/pull/314#pullrequestreview-10520121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq0S467-01NeQQUjMdlvzxat5NEcoks5rDBO9gaJpZM4KxD-z
.

@kwk pushed the changes. Can you please check

[test]

@harrybabu please rebase
@nimishamukherjee @ldimaggi @kwk do you approve of this PR?

@joshuawilson rebase done

[test]


Added OAuth Test Application that includes test classes

The application extends everything that's included in the OAuthAPI,
plus any additional components required for testing.

Coverage remained the same at 100.0% when pulling fd143c3823b759f0c32a2a90bdfef27849f712f6 on feature/test_oauth_app into 2d68ab3735ffcc8e6124e60b2aaaeebcf2d92adc on develop.


Clean Makefile

A little bonus, you can run make in parallel (make -j2) to have both outputs faster.
The dependencies are handled better.

LGTM

LGTM


Licenses not appearing in Bonsai

Expected behavior:
The "license" field in the sidebar populates with the license applied to the GitHub repository.
Current behavior:
License shows as "unknown" for assets that have licenses applied in GitHub. Example: https://bonsai.sensu.io/assets/sensu/sensu-pagerduty-handler

Pending review in pull request #92


Add ability to send HTTP headers in GraphQLTestTemplate

I use an Authorization: Bearer {jwt} HTTP header for permissions on various parts of the graph. My tests use GraphQLTestTemplate which is super useful but I don't see any way to send the required header for tests of those parts that require it.
(Excuse my kotlin here but the code should be very similar to Java.)
@RunWith(SpringRunner::class)
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
class ApplicationTests {
    @Autowired
    private lateinit var graphQLTestTemplate: GraphQLTestTemplate

    @Test
    fun testQueryThatRequiresPermissions() {
        val response = graphQLTestTemplate.postForResource("graphql/query-that-requires-permissions.graphql")
        assertEquals(1, response.get("$.data.thingQueried.id", Int::class.java))
    }
}

GraphQLTestTemplate has a postRequest method that looks like it might be useful to fiddle with the request before it goes to the endpoint but unfortunately it is private.
Any obvious workaround or should I not use GraphQLTestTemplate for this?

Hadn't thought about that use case before actually. Just quickly looked at the current code. I've tried to keep the public API of that class simple and at the same level, so having to deal with queries or resources representing queries. Not the lower lever of the actual HttpEntity. What we could do is add a method with an additional HttpHeaders or Map<String,String> parameter allowing you to pass in headers you'd want to add. Would that work for you?

Bit difficult to read like this, but looks ok. It does assume you want to use the same headers for each test in the same test class. That might work for most use cases, but if you'd want to be able to test several different header values you might want a way to alter that. Either by overriding these headers by passing in headers as a parameter, or by letting addHeader work more like setHeader where it overrides any previously provided header.
If that build problem is a local thing then the chance is high that when you create the PR the build will be ok.

I fixed my build issue (it was Java version-related) and sent a PR here: #176. Let me know what you think.


Wrong input width calculated

Search input width is currently calculated by subtracting 10 pixels from it's second parent width. But it should be the same, as the drop-down button width.

Thanks for the PR, can you check why the tests are failing.
Second please add a test  to test the behavior for now and in the future.

HI @easyest , I have merged my PR could you rebase to the master?
Thanks.

I would be glad to do that, but I do not use git at all. This PR was done by a simple edit in the web form :)

okay, i just saw that this is a duplicated issue. So closing it down as the other has a PR.


tektoncd-cli: 0.18.0 -> 0.19.0

Motivation for this change
Bump tektoncd-cli/tkn to 0.19.0
Commented out version check as it currently outputs empty without a remote tekton cluster
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126256 run on x86_64-linux 1

1 package built:

tektoncd-cli


fix(Docs): Add babel-polyfill so that the Docs work in IE11

Codecov Report

Merging #2884 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2884   +/-   ##
=======================================
  Coverage   99.67%   99.67%
=======================================
  Files         161      161
  Lines        2733     2733
=======================================
  Hits         2724     2724
  Misses          9        9

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6d6f6eb...054413d. Read the comment docs.

Can you throw in
useBuiltIns: 'entry'
Into the .babelrc file for the babel-preset-env plugin?

yup

This is an easy merge, however, what feature are we using that is not IE 11 compliant?  This is a target browser.

Promise

Released in<EMAIL_ADDRESS>


Bug: process_partial_response or processor does not catch raised errors in subroutine

Expected Behaviour
Inline with the provided examples:
https://docs.powertools.aws.dev/lambda/python/latest/utilities/batch/#accessing-processed-messages and https://docs.powertools.aws.dev/lambda/python/latest/utilities/batch/#recommended
the expected behavior is that in case record_handler raises and exception. either processor or process_partial_response catches this for further controlled handling.
Current Behaviour
In case record_handler raises an exception, this results in a BatchProcessingError
Code snippet
def record_handler(record: SQSRecord):
    raise Exception("not ok")
def lambda_handler(event, context: LambdaContext):
    return process_partial_response(
        event=event,
        record_handler=record_handler,
        processor=processor,
        context=context,
    )

Possible Solution
No response
Steps to Reproduce
Not yet tested when running in a lambda; reproduced when running locally.
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.8
Packaging format used
Lambda Layers
Debugging logs
No response

Hey @mhboon, that's the expected behaviour when all records in the batch fail to be processed.
https://docs.powertools.aws.dev/lambda/python/latest/utilities/batch/#partial-failure-mechanics
If you however have a partial failure, that is one successful amongst many failures, then it won't raise.
We do raise in total failure scenarios with all exceptions collected to help you diagnose an unwanted scenario. For poison pills, partial failures, etc. we handle just as fine.
Does that help? Or did you notice a regression and an exception is being raised despite a partial success?

Got it; in that case, I misunderstood and will close the issue. Thanks for clarifying.


libreadline.so.6 issue in ubuntu 18.04

I upgrade my system to 18.04 and when trying to run yosys I get issue below:

yosys: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory

I try to uninstall libreadline-dev with

sudo apt-get purge libreadline-dev

and install the libreadline.6 with

sudo apt-get install libreadline6-dev

but the system install the latest version (libreadline-dev_7.0-3) again:

Note, selecting 'libreadline-dev' instead of 'libreadline6-dev'

Is there a way to fix the issue?

Did you rebuild Yosys after updating Ubuntu?

Closing as issues seems to be abandoned by OP. Simply rebuilding Yosys, as suggested by daveshah1, should fix the problem.


Escape capture group for redirects

Confirmation

[X] This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
[X] I have searched the issue tracker and my issue isn't already found.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.5.7
Affected resource(s)
cloudflare_ruleset
Terraform configuration files
rules {
    action = "redirect"
    action_parameters {
      from_value {
        status_code = 301
        target_url {
          expression = "concat(\"https://www.something.com/bla\",regex_replace(http.request.uri.path, \"^content_display/.+/(.+)/.+\", \"/${1}\"))"
        }
        preserve_query_string = false
      }
    }
    expression  = "(http.host eq \"www.something.com\" and http.request.uri.path matches \"/content_display/.+/(.+)/.+\")"
    description = "something blabla display redirect"
    enabled     = true
  }

Link to debug output
none
Panic output
No response
Expected output
redirects to path /1
Actual output
│ 'concat("https://www.something.com/bla",regex_replace(http.request.uri.path,
│ "^/.+/(.+)/.+", "/\$\{1\}"))' is not a valid value for target_url because
│ the expression is invalid: Filter parsing error (1:104):
│ concat("https://www.something.com/bla",regex_replace(http.request.uri.path,
│ "^/.+/(.+)/.+", "/\$\{1\}"))

or
│ Error: Invalid escape sequence
│
│   on cloudflare_ruleset.tf line 1796, in resource "cloudflare_ruleset" "redirect_to_sso":
│ 1796:           expression = "concat(\"https://www.something.com/bla\",regex_replace(http.request.uri.path, \"^/.+/(.+)/.+\", \"/\\$\{1\}\"))"
│
│ The symbol "{" is not a valid escape sequence selector.
╵

or
│ Error: Invalid escape sequence
│
│   on cloudflare_ruleset.tf line 1796, in resource "cloudflare_ruleset" "redirect_to_sso":
│ 1796:           expression = "concat(\"https://www.something.com/bla\",regex_replace(http.request.uri.path, \"^/.+/(.+)/.+\", \"/\$\{1\}\"))"
│
│ The symbol "$" is not a valid escape sequence selector.
╵

│   with cloudflare_ruleset.redirect_to_sso,
│   on cloudflare_ruleset.tf line 502, in resource "cloudflare_ruleset" "redirect_to_sso":
│  502: resource "cloudflare_ruleset" "redirect_to_sso" {
│
│ 'concat("https://www.something.com/bla",regex_replace(http.request.uri.path,
│ "^/.+/(.+)/.+", '/1'))' is not a valid value for target_url because the
│ expression is invalid: Filter parsing error (1:101):
│ concat("https://www.something.com/bla",regex_replace(http.request.uri.path,
│ "^/.+/(.+)/.+", '/1'))
│                                                                                ^^^^^^ unrecognised input
│  (20083)

Steps to reproduce
see code above
Additional factoids
regex_replace(http.request.uri.path, "^content_display/.+/(.+)/.+", "/${1}") -> this doesn't work
regex_replace(http.request.uri.path, "^content_display/.+/(.+)/.+", "/${1}") -> this doesn't work
regex_replace(http.request.uri.path, "^content_display/.+/(.+)/.+", "/\$\{1\}") -> this doesn't work
References
No response

Managed to find a workaround by using
expression = "concat("https://www.something.com/bla\",regex_replace(http.request.uri.path, "^/.+/(.+)/.+", "${local.first_capture_group}"))"
with
locals {
first_capture_group = "/$${1}"
}

thanks for the issue. this isn't a provider bug but a quirk of the escape sequences in HCL. you can check out the documentation in order to get the correct expressions here.

noted, thanks again for the feedback!


Replace old missed modals with new ones

While working on replacing what I thought was the last modals (#4682) I found a few others that all of us missed (so can't be commonly used). They need to be migrated though to be able to remove the old code planned for next/upcoming milestone:
deletion:

[ ] confirm delete slide (odyssey) in table/slides/panel.js#L301-L313

warnings:

[ ] show Gmaps deprecation in table/mapview.js#L356-L369

[ ] confirm edit geom in table/geom_editor.js#L167-L179

go man go!


Cannot see data in the multiple widgets in Tenant mode

Description:
Cannot see data in the following widgets in Tenant mode.


phonzammi/error-handling-for-server-routing

Hi @brillout and @AurelienLourot
What is inside this PR ?

Sync dependencies

Remove "@vue/compiler-sfc" and "@vue/server-renderer". The Reasons
Downgrade "vite": "^5.0.7", to "vite": "^4.5.1",
Up vike to "vike": "^0.4.150",
Up vue to "vue": "^3.3.12"
Rebase lockfile, please take a look what is changed to see if something important is missing 🙏

Workarounds for error handling (renderToString & renderToNodeStream)
This is meant for server routing since onRenderHtml only run with server routing (on the first page visit or when page reload).
Whereas for client routing (especially for pages with <script setup> or Composition API), I think we let the user (developer) create their own error handler, e.g. with Error Boundary. Even they can choose to replace /pages/_error/+Page.tsx with custom Error Boundary when the page reload or not (I've tested both).

Minor change ssr to vike inside vite.config.ts

As always, my PR is far from perfect, please review and improve this PR for the best of vike-vue.

phonzammi requested review from brillout

👍 LGTM as well. One thing: I think there is potential that we're swallowing errors. I'd be extra careful that errors emitted by app.config.errorHandler are always shown to the user. E.g. what happens if an error is thrown while streaming? I think it will be swallowed.

@brillout not sure I get it. Are you saying this patch introduces a problem or are you saying it doesn't cover everything yet?


Unable to connect to web server 'IIS Express' when domain name specified

After I entered http://api.plamobi.com:3497/ instead of http://localhost:3497/ into App URL field in project properties, I get Unable to connect to web server 'IIS Express'

Resolved by using the workaround from http://stackoverflow.com/questions/35675747/asp-net-5-mvc-unable-to-connect-to-web-server-iis-express/36801686
But it is weird, error is absolutely non informative.

I resolve this problem by changing port number of my ASP.Net Core app to something else in:
Properties page of the project and in Debug tab in App URL: section I changed the conflicted port number to a free port number bigger than 1024 and something other than the current one!
http://overengineer.net/fixing-unable-to-connect-to-web-server-iis-express

How do you connect to an IP address?

Yes, that works.
Now I run Visual Studio from admin so that it launch IIS Express from admin and it could bind IP or domain.

But Visual Studio behavior is very contra intuitive

@bill

This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.

So was error message updated to more clear?

@xperiandri Visual Studio is smarter now (VS2017 15.7 Preview 2 at least) to force update applicationHost.config whenever launchSettings.json is changed. That should remedy most errors caused by their out-of-sync.

@Tratcher any news on why it happen again ?
It is not working for both IIS Express AND Console
i tried to :

dotnet dev-certs http --clean
dotnet dev-certs http --trust
delete .vs/
change launchSettings.json to anything else
removed UseHttpsRedirection()
removed UseHsts()
not working for IP / dns in the browser

Also i do not a new behavior is vs2019 when running chrome

i beleive it has something to do with the way chrome is ran to be able to debug Front stuff, it was not doing that "previously" (can't really define that)
pretty sure all i did was update Vs2019, it was workign 2 weeks ago on the same SDK
>dotnet --version
3.0.100-preview3-010431

<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Mvc.NewtonsoftJson" Version="3.0.0-preview3-19153-02" />
  </ItemGroup>

</Project>

Comments on closed issues are not tracked, please open a new issue with the details for your scenario.


Example can not build and run

Example can not build and run
Open SwiftEntryKit.xcworkspace
Build and run
SwiftEntryKit-master/Source/MessageViews/EKMessageContentView.swift:10:8: No such module 'QuickLayout'

Please stick to the installation guide in the README.md.
Also, please review issue #31

Working Fine. Thanks for your support

Hey there, It still seems to be showing for me, I cloned the file as listed in the installation guide, opened the workspace and tried running, and still seems to be giving me the same error.


Bump to go1.7

Ref: #2028
@dmcgowan let's see how this goes.

This fails with go vet error:
Now using version stable
+ vet
registry/storage/driver/swift/swift.go:213: literal copies lock value from ct: github.com/docker/distribution/vendor/github.com/ncw/swift.Connection contains sync.Mutex
registry/storage/driver/swift/swift.go:787: literal copies lock value from d.Conn: github.com/docker/distribution/vendor/github.com/ncw/swift.Connection contains sync.Mutex
exit status 1
make: *** [vet] Error 1

I assume this check is added to go vet recently with go1.7. Should we pull in the maintainer of swift driver?

It will probably be quicker to fix this ourselves.  I'll have a look today.

@RichardScothern I can take this up.

thanks @ahmetalpbalkan

Current coverage is 50.90% (diff: 100%)

No coverage report found for master at 93a48e3.

Powered by Codecov. Last update 93a48e3...af0d4f7

@RichardScothern it's green now!

excellent.  Were you able to test it at all?

@RichardScothern I've been building the source on go1.7.1 myself for the past month or so. It seems to be working.

@ahmetalpbalkan that comment was meant for the other PR, mea culpe

Oh the swift driver PR? Nope, I have not tested it.

LGTM


Make external DNS webhook tests importable again

In https://github.com/cert-manager/cert-manager/pull/5880 we moved the ACME DNS solver test framework to an internal submodule, however this is imported by external DNS solver implementations as per our example DNS webhook https://github.com/cert-manager/webhook-example/blob/master/main_test.go#L7
This PR:

moves the ACME DNS solver test framework back to the main module
additionally moves the functionality for setting up a control plane for tests back to the main module, so it can be used by the DNS tests
motivation behind this PR. If there's a related issue or PR, link to it here! -->

I have tested locally that this unbreaks the example webhook's tests.
NONE

/test pull-cert-manager-master-e2e-v1-22
/test pull-cert-manager-master-e2e-v1-23

/kind cleanup

/test pull-cert-manager-master-e2e-v1-22
/test pull-cert-manager-master-e2e-v1-23

These passed


Improve GitLab projects name verification

This PR addresses https://github.com/pypi/warehouse/issues/15852
Notably, it prevents names from :

being in the reserved GitLab name list
ending with .atom or .git
ending with something else than a-zA-Z0-9
consecutive special characters

The keywords list are extracted from GitLab code. As noted by @facutuesca , this is mostly a cosmetic change, so having unsynchronized lists should not introduce a security risk.
Of note, we could slightly improve the regexes by limiting the number of potential matches to a fixed upper bound and prevent ReDos types of attacks.

Thanks @DarkaMaul! I want to pare this back a bit to avoid depending on assumptions internal to GitLab's code, but the consecutive character check makes a lot of sense to me to add.

Is this ready for review?

I think we are still unsure if we want to introduce a dependency on Gitlab internal code (for the list of forbidden project names).
I can refactor the PR to only include the following rules :

no consecutive special characters
no ending with a special character

We can leave the two others out of this PR:

not a reserved name
does not ends with .git or .atom

IMO having those lists of forbidden names is fine, since they are documented on GitLab's docs.  For me the important question is if having such exhaustive checking is worth it. @di what do you think?

The purpose of these validators is to prevent likely typos or misunderstandings about what the value of this field should be.
I think it's fairly unlikely that a user would frequently be trying to use these forbidden names, and even if they were, it would be fairly clear why it was failing.
TL;DR: I don't think being so exhaustive is necessary or worth it.

does not ends with .git or .atom

I think this could happen frequently enough that it's worth including.

does not ends with .git or .atom

I think this could happen frequently enough that it's worth including.

Agreed! Let's cover those two suffixes but leave the reserved names out.


[RAC-6176] add unit test for wsman-tool and wsman base job

Background
As the RACADM replacement work squad, we need to work on common wsman-tools functionality, so that everyone can focus on their own tasks.
Details

add unit test for wsman-tool and wsman base job
refine JobUtils.WsmanTool
refine DellWsmanBaseJob

Reviewers
@RackHD/corecommitters @nortonluo @yaolingling

BUILD on-tasks #285 : FAILURE

BUILD on-tasks #285  Error Logs  ▼Test Name: Should send request to smi service successfully
Error Details: undefined (string) is required
Stack Trace: AssertionError: undefined (string) is required
    at AssertService.(anonymous function) [as string] (node_modules/on-core/lib/common/assert.js:30:28)
    at new WsmanTool (lib/utils/job-utils/wsman-tool.js:9:689)
    at Context.<anonymous> (spec/lib/jobs/dell-wsman-bios-spec.js:130:25)
Test Name: Should fail to get respone from smi service
Error Details: undefined (string) is required
Stack Trace: AssertionError: undefined (string) is required
at AssertService.(anonymous function) [as string] (node_modules/on-core/lib/common/assert.js:30:28)
at new WsmanTool (lib/utils/job-utils/wsman-tool.js:9:689)
at Context.<anonymous> (spec/lib/jobs/dell-wsman-bios-spec.js:150:25)


Invalid seeds cause crash on startup

If you have seed configs with invalid ids, the game crashes on startup.
This is happens on its own if you add & remove other mods:

ResourcefulCrops adds configs for new mods automatically
You remove the other mod again
ResourcefulCrops auto-generated seed config stays
You now get a crash on startup as it can no longer find the material

This should not happen, it should just disregard the entry, log that and startup normally.
Both with ResourcefulCrops-1.10.2-2.0.0-56 and 57

Can't do much without a log.

crash-2017-03-06_10.44.37-client.txt


When changing date from 31st of any month, it jumps to same day in next month in calendar

Hi,
I could be able to reproduce this even in Demo in here https://www.webcomponents.org/element/bendavis78/paper-date-picker/demo/demo/index.html.
First set a date to 31st in any month.
Ex: 31st of May 2017
Then change it to any other date in very next month
Ex: Try to set 5th of June 2017
It will automatically set to 5th of July 2017 instead.

My workaround to this was to repeat a statement under paper-calendar.html, _tapDay function:
var item = event.model.item; //for example, we select June 5th
var newDate = new Date(this.date.getTime()); //the current date is May 31st
newDate.setYear(item.year);
newDate.setMonth(item.month); //after this statement, newDate suddenly becomes July
newDate.setMonth(item.month); //after this statement, newDate returns to June
newDate.setDate(item.day);
this.date = newDate;

This was addressed in another PR already.


Bug? D3Dshot continously giving lower frames when benchmarked

Out of d3dshot's ReadMe Is robust and very stable. You can run it for hours / days without performance degradation
I was trying to compare d3dshot to python mss and pyautogui (backend pillow). My frametest works fine for these other two libraries, but when I try to apply it onto d3dshot, my average frames continously get lower the longer the while loop runs ... Why?
Hardware:
monitor 2560 x 1440p 144hz
cpu amd ryzen 5 5600x 6x core @ 4.3 ghz
meaning optimal results would be 144 frames per second
import time, cv2, mss, numpy, d3dshot, pyautogui

# d3dshot (supports capture outputs: pil, numpy, numpy_float, pytorch, pytorch_float)
img = d3dshot.create(capture_output='numpy')

number_list = []

while True:
    last_time = time.perf_counter()

    # MSS get raw pixels from the screen, save it to a Numpy array
    # img = numpy.array(mss.mss().grab({"top": 40, "left": 0, "width": 800, "height": 640})) # getting 144 fps

    # d3dshot
    img.screenshot(region=(0,40, 800, 640))

    # pyautogui (pillow)
    # img = pyautogui.screenshot(region=(0,40, 800, 640)) # 31 fps

    fps = 1 / (time.perf_counter() - last_time)
    # print(f"fps: {fps}")

    # calc avg
    number_list.append(fps)
    avg = sum(number_list)/len(number_list)
    print(f"averages {round(avg, 2)} fps")

python 3.10.2 | windows 10 64 bit

There are some flaws for the benchmark:

you need newly rendered frames to test the mss/d3dshot screenshot. If you are just idling then the benchmark will gives inaccurate results (higher on mss/probably lower on d3dshot).
To test accurately, you need something that can constantly render new frames (ideally sync with your monitor refreshing rate). I recommend opening Blurbuster UFO test in chrome and doing the testing.

My own benchmark: (5900X + 3090; 240hz monitor)

DXcam
python-mss
D3DShot

Average FPS
238.79
75.87
118.36

Std Dev
1.25
0.5447
0.3224

Ok tbh that sounds more like a self-advertising: For DXcam see -> https://github.com/ra1nty/DXcam


Add functional tests

Summary
Add an end-to-end test to check that running each CLI command in turn gives no errors.
Detail
Adds a functional test in test_functional.py that runs each of the CLI commands in the proper order. That unit test expects a postgres db to be up and running and to have a database named src. In the GitHub action, we set up such a database. Since the unit test is destructive (it overwrites any src and dst databases it connects to) we require an env var to be set to run the test.
Misc
Closes #10

@myyong The functional tests run fine for me and on the GH Action. Could you check that they work for you and let me know if I should add some more explanation to the Testing section of the README?