how to solve this docker image issue.

when I enter "kubectl describe pods", it display like below, how to solve this issue.
cluster/ubuntu# kubectl describe pods
Name:		c-engine-test-3035214309-ge2nj
Namespace:	default
Node:		<IP_ADDRESS>/<IP_ADDRESS>
Start Time:	Thu, 12 Jan 2017 20:04:45 +0800
Labels:		app=c-engine-test
pod-template-hash=3035214309
Status:		Pending
IP:		<IP_ADDRESS>
Controllers:	ReplicaSet/c-engine-test-3035214309
Containers:
c-engine-new:
Container ID:
Image:			c-engine_redis_test
Image ID:
Ports:			8080/TCP, 9043/TCP, 9060/TCP, 9085/TCP
State:			Waiting
Reason:			ImagePullBackOff
Ready:			False
Restart Count:		0
Environment Variables:
Conditions:
Type		Status
Initialized 	True
Ready 	False
PodScheduled 	True
Volumes:
configcolud-205:
Type:	HostPath (bare host directory volume)
Path:	/data02/soft/soft/dockersoftware
default-token-f4m5v:
Type:	Secret (a volume populated by a Secret)
SecretName:	default-token-f4m5v
QoS Tier:	BestEffort
Events:
FirstSeen	LastSeen	Count	From			SubobjectPath			Type		Reason		Message

17m		17m		1	{default-scheduler }					Normal		Scheduled	Successfully assigned c-engine-test-3035214309-ge2nj to <IP_ADDRESS>
17m		2m		7	{kubelet <IP_ADDRESS>}	spec.containers{c-engine-new}	Normal		Pulling		pulling image "c-engine_redis_test"
16m		1m		7	{kubelet <IP_ADDRESS>}	spec.containers{c-engine-new}	Warning		Failed		Failed to pull image "c-engine_redis_test": Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/c-engine_redis_test/images. You may want to check your internet connection or if you are behind a proxy.
16m		1m		7	{kubelet <IP_ADDRESS>}					Warning		FailedSync	Error syncing pod, skipping: failed to "StartContainer" for "c-engine-new" with ErrImagePull: "Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/c-engine_redis_test/images. You may want to check your internet connection or if you are behind a proxy."
16m	3s	49	{kubelet <IP_ADDRESS>}	spec.containers{c-engine-new}	Normal	BackOff		Back-off pulling image "c-engine_redis_test"
16m	3s	49	{kubelet <IP_ADDRESS>}					Warning	FailedSync	Error syncing pod, skipping: failed to "StartContainer" for "c-engine-new" with ImagePullBackOff: "Back-off pulling image "c-engine_redis_test""

Could you share the image that you tried to use with your k8s setup?
As an FYI this would be get a more detailed answered if filed within the Kubernetes community:
https://github.com/kubernetes/kubernetes/issues

root@SZX1000137722:/var/lib/docker/k8soft/kubernetes-release-1.3.0/cluster# docker images

docker images
REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
c-engine_redis_test                                   latest              c1a770e48e7e        2 weeks ago         1.018 GB
redis                                                 latest              c1a770e48e7e        2 weeks ago         1.018 GB
mysql-server                                          latest              0d128360030a        5 weeks ago         1.479 GB
kubernetes/heapster                                   canary              897d92d87f62        3 months ago        1.028 GB
               e00cd41bd8e8        3 months ago        1.029 GB
gcr.io/google_containers/kubernetes-dashboard-amd64   v1.4.0              436faaeba2e2        3 months ago        86.27 MB
wjp719/redhat6.5                                      latest              7148b134ccd9        5 months ago        472 MB
gcr.io/google_containers/kubedns-amd64                1.5                 3afb7dbce540        6 months ago        50.82 MB
gcr.io/google_containers/kube-dnsmasq-amd64           1.3                 9a15e39d0db8        7 months ago        5.13 MB
gcr.io/google_containers/pause-amd64                  3.0                 99e59f495ffa        8 months ago        746.9 kB
gcr.io/google_containers/exechealthz-amd64            1.0                 82a141f5d06d        9 months ago        7.116 MB
gcr.io/google_containers/heapster_grafana             v2.6.0-2            b43443930626        10 months ago       230.1 MB
kubernetes/heapster_influxdb                          v0.5                a47993810aac        16 months ago       251 MB
root@SZX1000137722:/var/lib/docker/k8soft/kubernetes-release-1.3.0/cluster#

this docker version and linux system version is below, linux  system is Ubuntu 14.04
root@SZX1000137722:/var/lib/docker/k8soft/kubernetes-release-1.3.0/cluster# docker version

docker version
Client:
Version:      1.11.2
API version:  1.23
Go version:   go1.5.4
Git commit:   b9f10c9
Built:        Wed Jun  1 21:20:08 2016
OS/Arch:      linux/amd64

Server:
Version:      1.11.2
API version:  1.23
Go version:   go1.5.4
Git commit:   b9f10c9
Built:        Wed Jun  1 21:20:08 2016
OS/Arch:      linux/amd64
root@SZX1000137722:/var/lib/docker/k8soft/kubernetes-release-1.3.0/cluster#
root@SZX1000137722:/var/lib/docker/k8soft/kubernetes-release-1.3.0/cluster# uname -a

uname -a
Linux SZX1000137722 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
root@SZX1000137722:/var/lib/docker/k8soft/kubernetes-release-1.3.0/cluster#

it seems that the image was pulled properly, as it shows up in your docker images command.
What happens when you do: docker run c-engine_redis_test:latest ?


Support publishing with multiple images

          Maybe publishWithImage should be combined with publish and support multiple images in the same thread.

Originally posted by @FieryFlames in https://github.com/junhoyeo/threads-api/issues/70#issuecomment-1627872326
          This is what I'm seeing:

Instead of configure_text_post_app_feed, they use configure_text_post_app_sidecar
Originally posted by @FieryFlames in https://github.com/junhoyeo/threads-api/issues/70#issuecomment-1627881723

superr thank you so much for the reversing work!

Hi @FieryFlames, we now support sidecar attachments from v1.5.0 (#198)! 🎉

          Maybe publishWithImage should be combined with publish and support multiple images in the same thread.

Originally posted by @FieryFlames in #70 (comment)
          This is what I'm seeing:

Instead of `configure_text_post_app_feed`, they use `configure_text_post_app_sidecar`
Originally posted by @FieryFlames in #70 (comment)

          Maybe publishWithImage should be combined with publish and support multiple images in the same thread.

Originally posted by @FieryFlames in #70 (comment)
          This is what I'm seeing:

Instead of `configure_text_post_app_feed`, they use `configure_text_post_app_sidecar`
Originally posted by @FieryFlames in #70 (comment)

Hello @FieryFlames , can you tell me how you managed to sniff the traffic?

      Maybe publishWithImage should be combined with publish and support multiple images in the same thread.

Originally posted by @FieryFlames in #70 (comment)

      This is what I'm seeing:

Instead of configure_text_post_app_feed, they use configure_text_post_app_sidecar

Originally posted by @FieryFlames in #70 (comment)

      Maybe publishWithImage should be combined with publish and support multiple images in the same thread.

Originally posted by @FieryFlames in #70 (comment)

      This is what I'm seeing:

Instead of configure_text_post_app_feed, they use configure_text_post_app_sidecar

Originally posted by @FieryFlames in #70 (comment)

Hello @FieryFlames , can you tell me how you managed to sniff the traffic?

https://github.com/Eltion/Instagram-SSL-Pinning-Bypass/tree/9b15af2d984a2e39f8c677864c4b2bb7626f30b4 and mitmproxy


add usage documentation

A number of important configuration switches and use cases are not appropriately documented.
Some of the configuration switches as environment variables
VIV_NO_SETUPTOOLS
VIV_VERBOSE
VIV_CACHE
VIV_DEBUG

If this is still open, assign this to me, I'd like to work on this!

Sure, if you think you understand these features well enough to describe them you can add to docs/usage.md. The docs can generated locally using nox -s docs which will launch sphinx-autobuild.


[ApolloPagination] Add completion callbacks to fetch and refetch in GraphQLQueryPager for API Consistency

For API consistency, it makes sense that both fetch and refetch have completion blocks to indicate when their operations are completed. If we think about the way that the Async variant works, we always have a "completion" signal in the form of the await – whereas we don't for fetch and refetch in the GraphQLQueryPager.

Related: https://github.com/apollographql/apollo-ios/issues/3349

Changes in GraphQLQueryPager.swift:

public class GraphQLQueryPager<Model>: Publisher {: The refetch and fetch methods have been updated to include two new parameters: callbackQueue and completion. This allows users to specify a dispatch queue on which the completion callback should be fired and a completion block that triggers after the operation execution.

Changes in GraphQLQueryPagerCoordinator.swift:

public protocol PagerType {: The refetch and fetch methods in the PagerType protocol have been updated to include the callbackQueue and completion parameters, aligning with the changes made in the GraphQLQueryPager class.
class GraphQLQueryPagerCoordinator<InitialQuery: GraphQLQuery, PaginatedQuery: G: The refetch and fetch methods have been updated to include the callbackQueue and completion parameters. This allows users to specify a dispatch queue on which the completion callback should be fired and a completion block that triggers after the operation execution. [1] [2]

Do we need to update the usage docs for this? Maybe we should create a new branch for 0.2 and do this there, so that those docs don't get deployed until we push the 0.2 version release?

We probably should re-generate the docset, yeah. But since this is a non-breaking change, I can see an argument for a 0.1.1

SopheaSao Cambodia Enjoy with you ♥


[WIP] Separated generators from the main library

I couldn't put generators in their own library, because they depend on language-plutus-core and tests of the latter depend on generators, so there is a loop.
This also fixes an accident TODO: replaces fmap BSL.fromStrict . Gen.bytes by genLowerBytes.

Would you consider making a language-plutus-core-tests library as well? Or was that considered already and we decided against it?

Would you consider making a language-plutus-core-tests library as well?

I'd prefer to keep tests within libraries they test.

Or was that considered already and we decided against it?

I think, no. @mchakravarty, @michaelpj ^

@effectfully I'll give them a little while to look at this, then I'll force-merge it if it's still stuck (I've looked at the jobset and the jobs have in fact succeeded).

Okay, merging.


Naming Problem Causing Errors in  main.py

I got this error when following the instructions to run the project:
File "C:\Users\Gaspard\Desktop\Game_of_Life-Gaspard_Devoivre-CDOF4-main\rpfile_main_.py", line 3, in
from rplife import patterns, views
ModuleNotFoundError: No module named 'rplife'

Just a simple naming issue, easy fix with the dev tools on github browser


[Backend] TRT backend uses pinned memory

PR types(PR类型)

Backend
Describe

Introduced pinned host memory
Add a new buffer type FDDeviceHostBuffer
Integrate FDDeviceHostBuffer into FDTensor
TRT backend optimization with FDDeviceHostBuffer

After integrating pinned memory, the inference latency is comparable with trtexec. It mainly optimized the D2H latency.
The latency includes H2D, GPU inference and D2H.
Tested on P40.
The reason why yolov6s has only a little improvement is the output tensor shape of yolov6s(8400x85) is much smaller than yolov5s(2x25200x85) and yolov7(2x25200x85).

model
before
after
trtexec

yolov5s
11.0566ms
7.34001ms
6.76131ms

yolov6s
7.17801ms
6.483ms
5.69616ms

yolov7
25.7099ms
19.9956ms
19.8108ms


Can't open the doors for "A New Threat", no prompt

The 3 doors in "A New Threat" cannot be clicked to open a prompt to destroy them.  I've tried clicking either side, and I've tried the mission both as part of a campaign and as stand-alone.  Both of the crates in this mission can be clicked and claimed, and the blue starting location can be clicked, it's just the doors that are not registering clicks.
Without door destruction, the mission cannot progress.  Doors work correctly for "Aftermath" and "Under Siege".

Tested on Windows 10 with v.2.2.1 and v.2.2.2.

Hello, yes, we are aware of this issue.  The file that controls the Mission is missing some data, that's why this is happening.  It'll be corrected in the next update. 👍🏻

Thank you so much.  Love the app.


Enhancement (ci): Use set -eu in build.sh

this should be implemented, set -e has to be paired with -u so that undefined variables result in terminating errors.  set -e is also useful for terminating any errors during param parsing, configuration, validation.

if that were the case all scripts that support arguments and which have variable validation should use set -e with the script designed around terminating errors. this isn't the case as i understand

what about for the rest of the scripts after the param checks

the rest of the script after the checks shouldn't always require set -e.

agreed, but in most cases, it makes sense to have terminating errors, or else there must be explicit error handling for failures, which is missing in this script.

i can't say it's true that it makes sense to have terminating errors in most cases

in the above case, is all depends whether listing info using those commands is mandatory. Using set +e should not be a way to make commands optional.

the suggestion wasn't to make the commands execute with set +e, but to have set -e apply later like how it does presently.

set -e being applied late like how it is presently, makes param parsing, configuration, validation, and set -u at the top script no longer terminating errors. since the script has no explicit handling throughout, it makes sense to use set -e at the begninning.

adding || true is the only the inconvenience for those lines. but we get the benefit of set -e for param parsing, configuration, validation, and set -u.

set -e should not be relied on for param parsing, configuration, validation etc. .

what i mean is, when set -u is used, at the top of script, set -e will ensure undefined variables terminate immediately. So it sense to pair the two, so they apply to the entire script.
set -e presence means every line in a script must exit with 0 so that one knows that all lines below set -e "work" until either the end of script, or the first non-0 line. By using set -e only further down, these benefits do not apply lines above it.

when set -u is used, at the top of script, set -e will ensure undefined variables terminate immediately.

yes. from my experience tho it isn't a general practice to have set -e defined at the top of the script for scripts with such checks.

true, if you look in all the canonical's script's all over ubuntu, you can see a general style of scripts, e.g. casper scripts, e.g. the main casper script /usr/share/initramfs-tools/scripts/casper begins with set -e.
moreover, in general, CI jobs and build scripts are set -e by default, e.g. Dockerfile, because the deterministic, ephemeral (non-idemponent) pattern ensures everything succeeds (i.e. all lines are assertions, and all lines exit with 0).

the main casper script begins with # set -e.
build.sh is a CI script which is why it makes sense to have set -e applied for the majority of the script. what set -e shouldn't always be applied is from the top of every .sh script with param and validation checks.

looks like in the current casper script commented it out because they prefer the terse style [ -f file ] && a=1 shorthands instead of if else. i guess, it's even.

just like in PS using throw often requires the script to be designed in that fashion. while there are param checks in powershell most scripts or functions are better returning non-terminating errors. PS is object-oriented so the errors handling is important. yet i usually apply the same design for sh scripts and using if / else instead of relying on shorthands.

what set -e shouldn't always be applied is from the top of every .sh script with param and validation checks.

using if / else instead of relying on shorthands.

for param parsing, right now, the it is very simple, so set -e actually ensures the params lines "worked". i agree when param parsing requires grep or other commands that might need || true appended, then set -e might make things more difficult, but don't foresee that happening for this script.
for validation, this script does not use && shorthands so set -e is fine.

for simply for this script, but in general shorthands such as || true when extensively used indicates an issue of design with respect to error handling.

as said one doesn't always want to use $ErrorActionPreference = 'Stop' because terminating errors might not be wanted, but instead use if else handling:
$item = Get-Item foo
if ($item) {
  ...
}

in contrast to
$ErrorActionPreference = 'Stop'
try {
  $item = Get-Item
} catch {
  $item = $null
}`

Using || true in shell like wrapping each statement in a try catch in PS.

in fact ErrorActionPreference = 'Stop' in PS isn't often used. instead, $item = Get-Item foo -ErrorAction Stop does the same just exclusive to the line in question.

in fact ErrorActionPreference = 'Stop' in PS isn't often used. i

yes. it is used when the user wants most things to terminate by default, e.g. in build scripts.

Compile-SourceScript and PSModulePublisher use $ErrorActionPreference = 'Stop' because the steps are mainly deterministic as you describe. however i don't believe most PS functions and scripts you write start with $ErrorActionPreference = 'Stop'. same thing with sh, unless set -e is used for validation simply for convenience.

agreed. in my own ps scripts, i usually use $ErrorActionPreference = 'Stop', because i always use -ErrorAction SilentlyContinue for cmdlets that shouldn't terminate. which is also why for sh, i like set -e, and use || true whereever should not terminate. matter of preference i guess.

i'd say if a script is mostly deterministic in design, setting the default error preference to terminating would be preferred. in the majority of cases scripts aren't deterministic and so terminating errors are applied where necessary.
build.sh being a deterministic script should have its default error preference set to terminating. i can't exactly say like in this PR if the number of shorthands such as || true is considered excessive. yet i wouldn't still prefer defining set -e at the top of the script for validation since validation shouldn't require set -e. if set -e isn't used at the top of the script, the following || true shorthands wouldn't also be required for applicable commands.

validation since validation shouldn't require set -e

it is true that validation doesn't need set -e. set -e as applied to validation only ensures that the validation lines themselves did not exit with non-0.

if set -e isn't used at the top of the script, the following || true shorthands wouldn't also be required for applicable commands.

guess because those commands that may fail are actually not directly related to the building of the desired state. in this case, if set -e is used, those commands are "out of place" in a build script, hence the need to make them "optional" by using || true which you mentioned is only a few lines.

it is true that validation doesn't need set -e. set -e as applied to validation only ensures that the validation lines themselves did not exit with non-0 (in human words, "the script validation should work 100% correctly").

think it's better to find out how to better design param validation and error handling instead of relying on set -e.

guess because those commands that may fail are actually not directly related to the building of the desired state. in this case, if set -e is used, those commands are "out of place" in a build script, hence the need to make them "optional" by using || true which you mentioned is only a few lines.

same thing here. such shorthands can be avoided with set -e doesn't apply where unnecessary.

think it's better to find out how to better design param validation and error handling instead of relying on set -e.

set -e is not needed by param validation at all. it simply ensures that param validation lines, which use case esac and if else which don't terminate due to syntactical or any command that exit with non-0 within the param validation lines.

same thing here. such shorthands can be avoided where set -e doesn't unnecessary apply.

yes, is is only needed for those commands don't "fit" the rest of the deterministic build script. meaning:

those commands may be removed from the script, or
those commands may fail but they must not terminate the build script, hence || true is needed for them.

think it's better to find out how to better design param validation and error handling instead of relying on set -e.

set -e is not needed by param validation at all. it simply ensures that param validation lines themselves are fine:

syntactically correct
no undefined variables
no commands exiting with non-0

which is how one knows that validation "succeeded as expected".

same thing here. such shorthands can be avoided where set -e doesn't unnecessary apply.

yes, is is only needed for those commands don't "fit" the rest of the deterministic build script. meaning:

those commands may be removed from the script, or
those commands may fail but they must not terminate the build script, hence || true is needed for them.

no need for set -e for param validation. shouldn't have to rely on set -e for every script requiring param validation. again, it's better to learn to design params and scripts without set -e if possible. or, at least for elements which shoulnd't require set -e such as param validation, thereby only using set -e for scripts requiring it or in sections requiring so.

no need for set -e for param validation.

at least for elements which shoulnd't require set -e such as param validation

lol, set -e is not needed for param validation as i said.

it's better to learn to design params and scripts without set -e if possible.

yes

don't use set -e for non-deterministic scripts. but if else may be more verbose
use set -e for deterministic scripts, since makes things terser (need for explicit error handling).

thereby only using set -e for scripts requiring it or in sections requiring so.

yes. though specifying it for selective sections of the script can make things difficult to follow.

presently param validation already has exit * and variable parsing ?err both of which hande errors without the need for set -e. set -e can thus exist where it does presently without the need for this PR.

presently param validation already has exit * and variable parsing ?err both of which hande errors without the need for set -e

here, if else with exit * handles only semantic errors (i.e. when value is wrong, exit). does not handle:

syntax errors
commands which may exit with non 0 among the param validation lines.

those are handled by set -e, which ensures that all lines are assertions that exit with 0.

syntax errors

syntax errors are common and most frequently exposed simply by executing the script.

commands which may exit with non 0 among the param validation lines.

are there examples for those. especially within build.sh

"syntax" errors may end up being errors that are not recognized as syntax errors:
set +e
a=$( echo 1 | grep '1;' ) # should terminate, but doesn't

but when set -e is used:
set -e
a=$( echo 1 | grep '1;' ) # terminates

are there examples for those. especially within build.sh

when grep is used for validation, or exitz is used instead of exit. that kind of stuff.

set +e
a=$( echo 1 | grep '1;' ) # should terminate, but doesn't

grep used for validation would not result in termination without set -e. however in this case it is better to check for [ -n "$a" ] following those commands instead of simply relying on grep for validation.
never heard of exitz. using an incorrect binary with a similar name would be unfortunate. however the output after the command should lead to failures in resulting commands.

grep used for validation would not result in termination without set -e. however in this case it is better to check for [ -n "$a" ] following those commands instead of simply relying on grep for validation.

i guess what you mean is:
set +e
a=${a:-}
if [ "$a" = 0 ] || [ "$a" = 1 ] ; then
   :
else
  exit 1
fi

in the above example, the validation is performed immediately after the configuration. consider the case where validation is performed far further down:
set +e
a=${a:-}
b=${b:-}
echoz 1 # should terminate, but doesn't
c=${c:-}
if [ "$a" = 0 ] || [ "$a" = 1 ] ; then
   :
else
  exit 1
fi

the script does not error out on echoz.
Consider a simpler "syntax error" example:
set +e
set -u
a1=${a:-} # invalid variable! should terminate here, but not so
b=${b:-}
if [ "$a" = 1 ]; then  # Terminates here instead
  ..
fi

> never heard of exitz. using an incorrect binary with a similar name would be unfortunate. however the output after the command should lead to failures in resulting commands

it's deliberately misspelled, like the above `echoz` example, demonstrating a command may fail. Imagine if `exitz` is used, and `set +e` is used. The script keeps going instead of `exit`ing.

in the above examples, multiple lines are involved in param validation. in those cases perhaps set -e used with set -u might make sense applied at the top of the script. however the param validation within build.sh aren't as elaborate so as to require set -e

how about a simple example. suppose:
PIPELINE=${PIPELINE:?err}
if [ "$PIPELINEz" = 'build' ]; then # should terminate, but does not.
  ...
fi

such examples are not so common errors in variables used. in such cases as i mention issues would be seen via execution of the script. perhaps # set -e can be toggled for checking for such issues. but as for applying set -e throughout the script simply due to param validation requiring so would be unnecessary.
this reminds me however of #132 where the else section for the variable PIPELINE should have been moved to the above if-else block.

script should terminate when expected, not later than expected. just because an integration test passes, doesn't not mean the script should subscribe to the principle of failing as early as possible. set -e also makes it easier to catch errors in development (fail early philosophy).

again set -e shouldn't be the default error preference for every sh script written. specifically, with regard to build.sh or notify.sh which don't involve elaborate param validation steps, set -e needn't be defined at the top of the script, and instead seems ideal where it presently is.

ok, this is just a discussion about the benefits / drawbacks of using set -e. not saying that it must be used, but that it has very clear benefits, even in the present script as i demoed in the simple example https://github.com/startersclan/docker-sourceservers/pull/126#issuecomment-1475377514.

ok, this is just a discussion about the benefits / drawbacks of using set -e. not saying that it must be used, but that it has very clear benefits, even in the present script as i demoed in the simple example https://github.com/startersclan/docker-sourceservers/pull/126#issuecomment-1475377514.

if the complexity of a script requires extensive validation perhaps set -e would be preferred.
closing.

perhaps this discussion might come in handy in future.


get User media when initializeProxy

Coverage decreased (-0.005%) to 40.25% when pulling 4efc219b0ea42793d7314d9688d7161b33bc0385 on embbnux:bugfix/audioSetting into 1bc05abd9ba44b86864b421e06b672316fd2cb8f on ringcentral:master.


import scenes from a different file

Could you show an example of how to write a scene in a different file and then import it in?
Right now I'm using absolute path to import i.e. import { differentScene } from "/pub/examples/different_scene.js";
This is working but is this best practice? Is there a way to support relative path importing?

that sounds like a pretty good practice to me

is there a way to support relative path importing

That's not related to kaboom and depends on your project setup. If you're using the example editor it's looking for files via HTTP requests, if you're developing locally and using a bundler or something, you should be able to do relative path importing

@ghlai9665 If you're familiar with ES modules, I have been building out a small test game using kaboom and I attempted a multi-file / module approach. I am using relative paths as that is what the browser requires. So far I think it's been working well for me but could still probably use some refactoring. Feel free to check it out here https://github.com/srobertson421/kaboom-space-shooter
@slmjkdbtl PS. Loving kaboom! The api is very clean and I am having a blast working with it. Thanks!

@srobertson421 Thanks! and thanks for trying it out :D
@ghlai9665 Hi! Is your issue resolved?


user_journa fix to fit the new loot api with year history

Thank you for your PR & for reminding me this repo still exists :)
I'm currently working into remodeling the entire project, I'll soon push a new branch for this, if you are interested.
Also, I'll try update this repo with all the local updates I've made for my personnal Discord bot.


Close chat function

Hi! We have livechat in our IOS App, but there is no function to close the chat there.

@KristinaGenius there is a close button on the top right corner of the chat window. Is that what you are looking for?

Closed due to no activity.


Navigate to session expired page instead of showing notification

Proposed Changes

Navigate to session expired page instead of showing notification

@coronasafe/care-fe-code-reviewers @coronasafe/code-reviewers
Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.
[ ] Update product documentation.
[ ] Ensure that UI text is kept in I18n files.
[ ] Prep screenshot or demo video for changelog entry, and attach it to issue.
[ ] Request for Peer Reviews
[ ] Completion of QA

@rithviknishad can you fix the cypress failure

LGTM


Safari 15 issue - ReferenceError

Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
Several other similar issues have been raised that all lead back to this issue, but the solution to update the browserslistsrc did not work for me. I do not have a problem in Safari 16, but any version before that is throwing me this error.
I saw on other issues that the problem lies with animations, however in my case I am seeing this issue when trying to update several packages. Nothing new has been introduced to the angular app. In the linked issue, there was also a comment that the problem does not occur when devtools are opened, but that has not had any effect for me.

Please provide a link to a minimal reproduction of the bug
https://github.com/angular/angular-cli/issues/24355
Please provide the exception or error you saw
`ReferenceError: Can't find variable: _angular_material_core__WEBPACK_IMPORTED_MODULE_3__`

Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 16.2.5
Node: 18.17.0
Package Manager: yarn 1.22.19
OS: linux x64
Angular: 16.2.8
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1602.5
@angular-devkit/build-angular      16.2.5
@angular-devkit/core               16.2.5
@angular-devkit/schematics         16.2.5
@angular/cdk                       16.2.7
@angular/cli                       16.2.5
@angular/material                  16.2.7
@angular/material-moment-adapter   16.2.7
@schematics/angular                14.2.13
ng-packagr                         16.2.3
rxjs                               7.8.1
typescript                         5.1.6
zone.js                            0.13.3

Anything else?
No response

What are the contents of your .browserlistrc file?

last 2 Chrome version
last 2 Firefox version
last 2 Edge major versions
last 2 Safari major versions
last 2 iOS major versions
Firefox ESR

The above config does not include support for Safari 15, as such the error is expected. To support Safari 15, please change last 2 Safari major versions to last 3 Safari major versions.
See: https://browsersl.ist/#q=last+2+Chrome+version
last+2+Firefox+version
last+2+Edge+major+versions
last+2+Safari+major+versions
last+2+iOS+major+versions
Firefox+ESR

Closing as per above explanation.


Functional Components

There is something slightly odd happening here.
This does not throw an error but also doesn't provide the expected output.
doc = sbol2.Document()

fc1 = sbol2.FunctionalComponent("fc1")
fc2 = sbol2.FunctionalComponent("fc2")
cp1 = sbol2.ComponentDefinition("cp1")

doc.add(cp1)

fc2.definition = cp1

mod1 = sbol2.ModuleDefinition("mod1")
mod2 = sbol2.ModuleDefinition("mod2")

mod1.functionalComponents.add(fc1)
mod2.functionalComponents.add(fc1)

doc.add(mod1)
doc.add(mod2)

doc.write(file_path_out)

Whilst this throws an error:
doc = sbol2.Document()

fc1 = sbol2.FunctionalComponent("fc1")
fc2 = sbol2.FunctionalComponent("fc2")
cp1 = sbol2.ComponentDefinition("cp1")

doc.add(cp1)

fc2.definition = cp1

mod1 = sbol2.ModuleDefinition("mod1")
mod2 = sbol2.ModuleDefinition("mod2")

doc.add(mod1)
doc.add(mod2)

mod1.functionalComponents.add(fc1)
mod2.functionalComponents.add(fc1)

doc.write(file_path_out)

I am not sure if the issue is that functional components can't be referred to more than once. The error is: <SBOLErrorCode.SBOL_ERROR_URI_NOT_UNIQUE: 17>, 'Cannot update SBOL-compliant URI. An object with URI http://examples.org/ModuleDefinition/mod2/fc1/1 is already in the Document

Yes, I believe that error indicates that you can't add the same object fc1 to more than one parent ModuleDefinition

It is interesting as the error seems to indicate a difficulty with the specific uri e.g. http://examples.org/ModuleDefinition/mod2/fc1/1 and http://examples.org/ModuleDefinition/mod1/fc1/1 would work. Is it an SBOL thing that you can't have repeated functional components?

The error message is indirectly telling you that fc1 already has a parent and that you can't assign it to more that one parent.  The error message is not as clear and direct as it should be.
When you add a child object to a parent, pySBOL automatically generates the URI of the child object.  Once an object is assigned a URI, pySBOL prohibits you from changing the URI.  So when you attempt to add that child object to a different parent, pySBOL tries to change the URI, hence the error message.
It's not an error specific to FunctionalComponents.  It's that a child object (black diamond relationship in UML) cannot have more than one parent.  This is different from a reference association(white diamond relationship) which may be what you are expecting.

Is it possible to keep a copy unlinked so I can add the sub properties only once? like a template fc?

Yes, I believe so.  I think sbol-utilities may have some convenience method for handling template copies.  @tcmitchell or @jakebeal would know more about that.  Regardless, I think you should be able to implement something like this for your specific use case.

You could try the copy method and see if it works for your use case. I'm not sure it will, and it's worth a try. I have modified your erroring example to use copy:
doc = sbol2.Document()

fc1 = sbol2.FunctionalComponent("fc1")
fc2 = sbol2.FunctionalComponent("fc2")
cp1 = sbol2.ComponentDefinition("cp1")

doc.add(cp1)

fc2.definition = cp1

mod1 = sbol2.ModuleDefinition("mod1")
mod2 = sbol2.ModuleDefinition("mod2")

doc.add(mod1)
doc.add(mod2)

mod1.functionalComponents.add(fc1.copy())
mod2.functionalComponents.add(fc1.copy())

doc.write(file_path_out)

Please let us know if this works for you.

This works, thanks.


Applications that are quit and not on focused screen are not recognized by kwm

This is some seriously inexplicable behavior: Firefox and iTunes will not open up on the display I have focused, instead they open on my 2nd display, while stealing focus with out kwm knowing about it.
Local Daemon is now running..
DisplayID 441231622 has index 0
DisplayID 69733314 has index 1
CreateWindowNodeTree() Create Space 3
CreateBSPTree() Create pair of leafs
CreateBSPTree() Create pair of leafs
SetWindowDimensions()
SetWindowDimensions()
SetWindowDimensions()
CREATE NOTIFICATIONS
SetWindowRefFocus() Focused Window: zsh 20,44
window id window-2
ShouldBSPTreeUpdate() Add Window
AddWindowToBSPTree() Create pair of leafs
IsWindowOnActiveSpace() window found
SetWindowDimensions()
SetWindowDimensions()
SetWindowRefFocus() Focused Window: Shell — 100✕25 977,44
CREATE NOTIFICATIONS
SetWindowRefFocus() Focused Window: New Issue · koekeishiya/kwm 20,1077
CREATE NOTIFICATIONS
SetWindowRefFocus() Focused Window: zsh 977,44
CREATE NOTIFICATIONS
SetWindowRefFocus() Focused Window: New Issue · koekeishiya/kwm 20,1077
CREATE NOTIFICATIONS
SetWindowRefFocus() Focused Window: zsh 977,44
CREATE NOTIFICATIONS
SetWindowRefFocus() Focused Window: New Issue · koekeishiya/kwm 20,1077
CREATE NOTIFICATIONS
SetWindowRefFocus() Focused Window: kwm 22,44

There are no create notifications for these applications even though I opened them in between changing focus in the log.
If I give focus using the mouse or keyboard to the other display it recognizes the window. Kwm appears to not notice these applications for some reason, and also not notice that focus has been lost.
I have removed all kwmc capture commands, restarted kwm, restarted my computer, and still this issue remains.
The only applications I have found so far that have this behavior is iTunes and Firefox.
Firefox developer edition even works, but not regular Firefox.
Let me know if there is any more data I can get for you.
Edit:
One very strange thing I have noticed is this appears to be applications that I have at one time kwmc screen -m 1 at one point in time. Not sure if Applications remember last location or something.

Actually, on further investigation I don't think kwmc config capture is working at all. At least not as far as I can tell.

kwmc config capture could indeed be broken after all the internal changes recently, will investigate.
Regarding the issue at hand, I don't think this is something in particular to do with Kwm. OSX always stores and reopens applications at a "previous location", unless the application has some setting to explicitly disable this.

OSX always stores and reopens applications at a "previous location"

I now how proper steps to repo, and this has nothing to do with iTunes or Firefox.

Open any application.
Send open window from that application to another screen.
Focus that screen, and that window.
Quit the app while on that screen.
Change focus back to the original screen.
Open application again.

Expected Results: Window gets created in the focused container
Actual Results: Window gets created on original screen, entirely ignored by KWM.
Application / window must be manually focused in order for kwm to recognize window.
If Application / window is moved back to original screen and quit, it works as expected.
KWM appears to not be able to handle an application opening on a screen it didn't expect (not the focused screen)

KWM appears to not be able to handle an application opening on a screen it didn't expect (not the focused screen)

This is correct. Not entirely sure how to handle this yet.
Kwm does recognize it spawning, but ignores it as it is on a different screen. This is to make sure that it does not interfere with the windows that are supposed to be tiled on that screen.
What I have been thinking of doing, is the following:
If Kwm detects a window that is not on its current screen, check if it is either a) a floating window, or b) already tiled on a different screen.
If neither of these are true, tile it on the screen that has focus.

That sounds pretty reasonable to me. Another potential solution (no idea if the APIs allow for it though) is to watch for an application launching vs a window launching. If its an application launching there should be now windows for it, and therefore shouldn't be tiled anywhere.

That sounds pretty reasonable to me. Another potential solution (no idea if the APIs allow for it though) is to watch for an application launching

That is indeed possible, does the issue in question only occurr on actual application launch and not on separate windows?
I recall having this issue with finder multilpe times, and it basically makes me not wanna use my external monitors..

I recall having this issue with finder multiple times, and it basically makes me not wanna use my external monitors..

I have tested it with finder right now, and I don't experience that issue (since finder is "always" running).
I only appear to have this issue with a "fresh" application (one that wasn't running previously)

not entirely sure what issue you were having with Finder windows.

Uh, say I am on my main monitor. I move the mouse to my external monitor, which is empty at the moment. I use spotlight to open finder. The window spawns on my other display (same issue as you mention above). This can be mitigated by performing a left-mouse click on the monitor, before doing the spotlight -> open finder, which is also the reason why I have some left-click code left in Kwm still. (I want to get rid of all that completly, eventually)

So strange, using the steps you describe (expect I used Alfred to open finder) Finder opens on the display that has focus. Going to try with Spotlight to see if there is a difference in behavior

Ah, it appears to be an issue with opening a specific folder. If I use Spotlight or Finder to launch a window (just Finder) it opens correctly. If I use those tools to pick a specific folder, the issue described in this ticket occurs

If Kwm detects a window that is not on its current screen, check if it is either a) a floating window, or b) already tiled on a different screen.

If neither of these are true, tile it on the screen that has focus.

I'll probably implement this system, as it will deal with all the cases.

I have been able to implement the behaviour I described above. Hopefully this will work "flawlessly" so that I can actually start using multiple monitors again. This exact issue has been annoying me for like 4months now.
Will push the commit soon.

..So focus between screens seems to be really broken at the moment, and the above commit only seems to work from external display -> primary display.. Not sure what that is about..

So the behaviour this issue is for, should now be fixed.
I did notice some issues with the kwmc screen -f .. command, however it is not something that makes Kwm crash, it just sometimes stops working after using kwmc screen -m .. for no apparent reason. Using the mouse works fine as expected even in this case.


Run etcd using tmpfs storage

tip from way back :)
https://github.com/kubernetes-sigs/kind/issues/845#issuecomment-529154066

Hey Dims, just curious, what's the benefit of doing this in the ci?

https://github.com/chainguard-dev/actions/blob/ff2c577c1d08761d3af7d40be4e98848024c1728/setup-kind/action.yaml#L88-L91
https://kubernetes.slack.com/archives/C78F00H99/p1703617800661829?thread_ts=1703182754.896809&cid=C78F00H99


Blur on Enter key press caught by submit button

Hello,
I'm not sure if this is intended or if this is a bug but blur is not triggered when Enter key is pressed and caught by form's submit button.

I currently have a form with a few fields, and a submit button.
When I focus a field, then click the submit button, here are the actions triggered:

If I focus a field then press Enter key, the following actions are triggered:

Redux-form: v6.8.0

If this is an intended behaviour, what's the best way to handle blur on keyboard events ?
Thank you,

I don't think there's anything you can do about it other than manually blurring/dispatching blur on that field.
The reason is that the browser itself doesn't dispatch the blur event when you press enter:
https://jsfiddle.net/gustavohenke/se9d49s7/

Oh ok thank you for the precision. Just in case it could be useful for someone else, I went for a blur on active element inside the onSubmit handler:
// NOTE: Blur active element to trigger a blur on Enter key press
if (document && document.activeElement) document.activeElement.blur()

It was actually fixed in material-ui v0.18.6: https://github.com/callemall/material-ui/pull/7283


Update fix-libva1-compatibility.patch for 71.x

I've just found that the latest chromium build log for openSUSE Leap 42.3 (which still depends on libva 1.7.3) has failed because of this patch. Similar to an issue reported by another user here.
BTW, I took the patch from their repo.

Try this patch instead of the one proposed in this PR:
--- a/media/gpu/vaapi/vaapi_jpeg_decode_accelerator.cc
+++ b/media/gpu/vaapi/vaapi_jpeg_decode_accelerator.cc
@@ -38,6 +38,10 @@ enum VAJDADecoderFailure {
   VAJDA_DECODER_FAILURES_MAX,
 };

+#ifndef VA_FOURCC_I420
+#define VA_FOURCC_I420 VA_FOURCC('I', '4', '2', '0')
+#endif
+
 static void ReportToUMA(VAJDADecoderFailure failure) {
   UMA_HISTOGRAM_ENUMERATION("Media.VAJDA.DecoderFailure", failure,
                             VAJDA_DECODER_FAILURES_MAX + 1);

I haven't tried it yet, so I don't know if it works. It's assuming that VA_FOURCC('I', '4', '2', '0') works as it did in the current version of this patch.

I'm going to experiment with my changes and see where it leads me.

Thanks for the suggestion. I'll downgrade libva to try out your patch.


Category filter clear button styling

I'm submitting a...

[x] Bug report
[ ] Feature request
[ ] Documentation issue or request

Current behavior

Expected behavior
Button design should match the spec for input clear buttons.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

@danielleroux @nuke-ellington
I have been trying to find a solution to this issue.
Zeplin has two diferent styles for the hover depending on the theme as the following shows:
Classic Theme

Brand Theme

And this is the current implementation no matter what the theme is:

For the intended result to happen, it need to be implemented in the "ix-icon-button", but there is already a normal state and a oval state, that are separated and invoked using props.
With the following code used in ix-icon-button toggled on a prop, i can make the perfect result happen to the clear button without disturbing the ix-icon-button component in general. But this doesnt feel like the the correct fix, please give me suggestions how to toggle the changes between the Themes.
.clear-button {
border-radius: $variable ----> 0px or 6.25rem
height: 25px;
width: 25px;
min-width: 25px;
}

@goncalosard Have to check this, i give you feedback asap

[ ] Fix error in icon-button 24px size of button not existing
[ ] Add margin to clear button in expanding-search
[ ] Check other input's with clear button

clear icon is really smaller then the other icons!


Order of songs with same title incorrect in songbook

The songs should be ordered by recency (oldest first).
Currently they are ordered alphabetically by slug. The first song with a given title will always be last alphabetically.
song-title-2.pro
song-title-3.pro
song-title.pro

The TOC is now ordered by correctly (by sorttitle), but the actual order of the song sheets is still wrong

Fixed! I added a more sophisticated command to sort the songs:
find $(SRC_DIR) -name '*.pro' -exec basename {} .pro \; | sort -t '-' -k1,1 -k2V -k3n | sed 's/^/src\//' | sed 's/$$/.pro/' > $(SRC_DIR)/songbook.txt

And changed the chordpro config to sort the table of contents by songindex numberically with +songindex.


modes/ocb128.c: fix misaligned access in ILP32 builds on 64-bit processors.

One could have fixed the problem by arranging 64-bit alignment of
EVP_AES_OCB_CTX.aad_buf in evp/e_aes.c, but CRYPTO_ocb128_aad
prototype doesn't imply alignment and we have to honour it.
Fixes #2985.
I'm adding WIP, because I want to see if it would be appropriate to omit some of the casts. This commit is bare minimum and does fix the problem. So that there either be additional commit or this one alone...

Removed WIP, alternative is too invasive/messy for "drive-by" fix.


Outro animations in components don't apply on the correct element

Rendered directly: http://jsfiddle.net/0dn4qqw1/1/
This does exactly what I want.  Click on a row and you can smoothly see it collapse.
Rendered as a component in another view: http://jsfiddle.net/0dn4qqw1/2/
This does not.  You can see Ractive reorder the DOM, placing the row it is about to delete at the bottom.  Only after that does it remove the row. Since that row is at the bottom of the list now, the animation is visually disconnected from the action the user performed and it overall looks pretty jumpy.

Fixed in edge, though I'm not entirely sure when :smile:


irsa-operator fails to finish reconciliation – use patch instead of update

With v0.9.0:
irsa-operator-bccc68878-hp8p6 irsa-operator 2023-02-09T09:42:34.873853205+01:00 E0209 08:42:34.873775       1 capa_controller.go:140] capa-controller "msg"="failed to remove finalizer on AWSCluster CR" "error"="Operation cannot be fulfilled on awsclusters.infrastructure.cluster.x-k8s.io \"vaclavvtest\": the object has been modified; please apply your changes to the latest version and try again" "cluster"="vaclavvtest" "namespace"="org-giantswarm"

Do not use Update, but a patch helper object.

Released with https://github.com/giantswarm/irsa-operator/pull/100


Tarsier Space Technology with Galaxies Continued now downloads from Spacedock

Please check that metadata in for Tarsier Space Technology with Galaxies Continued points to spacedock http://spacedock.info/mod/143/Tarsier Space Technology with Galaxies Continued...
Still have Kerbalstuff 404 error being shown after updating client repository.  Would have thought that the mod move to Spacedock would have fixed this. Have been watching and let it for wait for a while.
Perhaps now it is worth deeper check now. Thanks for all your hard work.

Closed in ref to pending NetKAN fix above


Tile Cache

Tile Serving is currently very slow due to each tile being calculated from scratch at every request.
This PR implements a Tile Cache which will serve precomputed tiles if they exist in the cache before falling back to a re-render.
Cleaning the cache is currently a manual process but the end goal will be:

Port tile-cover to rust
On each delta calculate covered tiles and invalidate affected

Next Steps

Add a CREATION column to the tiles table that invalidates the tiles after a given time. IE 1 day. This can be used as a stop-gap for the future work/fallback

Future Work

Finish building https://github.com/ingalls/tilecover which will allow each uploaded delta to selectively invalidate the tiles that it covers.


Create a namespace table with functions

I want to make a table with functions added to it, to act as a namespace. Can anyone tell me how to do this correctly?:
	void BindCommands(sol::state* L)
	{
		sol::table t;

		t["Initialize"] = Steamworks::Initialize;
		t["Shutdown"] = Steamworks::Shutdown;
		t["Update"] = Steamworks::Update;

		L->set("Steamworks", t);
	}

Usage in Lua:
Steamworks.Initialize()
Steamworks.Update()
Steamworks.Shutdown()

There is always  way with sol...
	void BindCommands(sol::state* L)
	{
		sol::table t(*L, sol::create);

:)


Windows Client - Enable to Login (Database Provisioning Error / Error 505)

Hi, I just recently signed up with Keybase (via website; e-mail confirmed) however I'm having trouble actually logging into the Windows client (1.0.20-20170317111045+6cc2f52).
The same results happen whether I use the GUI or the CLI.
If I choose to enter my username on either client, it immediately throws an exception.  GUI says "There was a provisioning error" then below that "Unknown Error: DB error"; CLI simply says "ERROR DB error (error 505)".  If I instead enter my e-mail address, it seems to accept this, but then throws the same error as before when I correctly enter my password.
:heart: bleeding-edge tech! 😄

Hi!  Sorry about this, we're in the middle of an outage at the moment.  Should be back up soon.

It's backup and running for me!

Same; everything is working great and I can dive in (well, during my lunch break)!  I thought it actually had to do with a creation of a local db; if I knew it was actually trying to access the site then I would have left it be for an hour and tried again then (the Internet version of "unplugging something and then plugging it back in").


Be possible to run into a Web Runtime

Hello,
I noted the library is using node-fetch as HTTP client:
https://github.com/grammyjs/grammY/blob/main/package.json#L28
If the library uses an isomorphic like isomorphic-unfetch instead, it will enable running the library in more places, like Vercel Edge Functions.

You are only looking at the backport for Node.js. The library is not written for Node.js. It does not require node-fetch (unless you are using the Node.js backport).

FYI you can already get a version that runs in modern browsers at<EMAIL_ADDRESS>but please follow #111 because that is still experimental.

#116 is related, too


Fix bug with hung web worker

Added upper limit to stop property of active chunk request

Motivation and context

Fixes #3080. The unzip_imgs web worker was not getting terminated when loading the last chunk in a task. I added a stopFrame limit to the chunk request so that the web worker gets properly terminated once it unzips all images.
How has this been tested?

I manually tested this by uploading 71 frames, all 2048 x 2448 to exceed the cache limit, and made sure that the web worker is correctly terminated after loading the last chunk. I also made sure that scrolling back through the previous frames worked and that frames that had been removed from the cache are successfully loaded back in.
Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage remained the same at 74.055% when pulling b889a658a065ef93d2c62a89236a950870e8bd5d on maximusunc:mw/fix_hung_webworker into 6988e2b98f9cfc7e0f98142a7c2829640d4fffcf on openvinotoolkit:develop.

@maximusunc , thanks for the contribution. Could you please add information about the fix into CHANGELOG.md?

@maximusunc , could you please update the version of cvat-core? Run npm version patch command.

Hi @nmanovic Looking at the test output, it looks like the tests timed out while running some canvas3d tests. I don't think my changes had anything to do with this test failure, but I will wait to hear back from you.


VM trait/struct refactoring

Part of #152.

Coverage decreased (-0.1%) to 77.935% when pulling 6cf0186756090bc048f96b867977650cc717e210 on sorpaas:master into 865d83ac930c2f9ae43b43623bc764d8821e145b on ethereumproject:master.

Coverage decreased (-0.1%) to 77.935% when pulling 6cf0186756090bc048f96b867977650cc717e210 on sorpaas:master into 865d83ac930c2f9ae43b43623bc764d8821e145b on ethereumproject:master.

Coverage decreased (-0.1%) to 77.935% when pulling 6cf0186756090bc048f96b867977650cc717e210 on sorpaas:master into 865d83ac930c2f9ae43b43623bc764d8821e145b on ethereumproject:master.

Coverage decreased (-0.1%) to 77.935% when pulling 6cf0186756090bc048f96b867977650cc717e210 on sorpaas:master into 865d83ac930c2f9ae43b43623bc764d8821e145b on ethereumproject:master.


:star: Enhancing Installer Package.

Add support for passwordless installation.
Added sample product in both CLI and GUI installations.
Fixed some UI issues with fonts, etc.
Added support for all possible currencies.

Issues reported in Single Locale and Single currency CLI installation.
-> Root Category missing
-> Exceptional Error in category create


PointLight2D does not support dynamic Texture2Ds

Tested versions

Found in: Godot 4.2.1
Reproducible in: Godot 4.0, 4.1, 4.2
Not Reproducible in: Godot 3.5

System information
Godot v4.2.1.stable - Linux Mint 20.2 (Uma) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (nvidia; 545.29.06) - Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 Threads)
Issue description
When using a PointLight2D with a dynamic texture, like an AnimatedTexture or a ViewportTexture, the light texture does not update. I would expect the light to represent the current state of the texture it is using.
Additionally, if another Light2D using a static texture has that texture is updated, the Light2D with a dynamic texture will be updated to the current value of the dynamic texture and remain in that state.
Steps to reproduce

Add a light impacted node such as a Sprite2D ot a scene
Add a PointLight2D to the scene and place it over the node from step one
Add an AnimatedTexture as the texture of the PointLight2D
Add more than one frame to the AnimatedTexture

Initially no frames from the animated texture will show in the PointLight2D but it is important to add more than one frame so that the static nature of the texture can be seen even if the texture is updated via the second point in the issue description.

The included minimal reproduction project contains two scenes that reproduce the issue:

light_repro.tscn reproduces this issue with an AnimatedTexture
light_repro_with_viewport.tscn reproduces this issue with a ViewportTexture

Minimal reproduction project (MRP)
LightTextureRepro.zip

Thank you for your report
For AnimatedTexture (which is deprecated) this is tracked in:

https://github.com/godotengine/godot/issues/67706

For ViewportTexture this is tracked in:

https://github.com/godotengine/godot/issues/75868

Consolidating there

My apologies, I am not sure how I did not find these


Documentation improvement style

Reference Issue
issue #696
issue #561

@arthurevans take a look when you can and  if I need modify anything, please let me know.

@arthurevans okay, my apologize, I forgot to import css and js.
Thank you for the review.
Okay, I'll wait @justinfagnani and @sorvell

Just a little information, in the docs the file are just a .css but in my test project, I'm using stylus:
import { LitElement, html, css, unsafeCSS } from 'lit-element'
import style from './style.styl'

class MyComponenet extends LitElement {
    static get styles() {
        return [css`${unsafeCSS(style)}`]
    }
.....

@sorvell @justinfagnani Hey guys, any news about this PR?

@sorvell @justinfagnani any news ?

@arthurevans a example of how use the information of this PR
https://github.com/danielbarion/instruct-contacts

@justinfagnani please, can you take a look here when you can?

@danielbarion I took a look, but I don't see how this applies to #696 or #561. This change doesn't mention minification and it appears to use the external styles that don't work in the polyfill.

This is not in docs and maybe some peoples want to do this like me.
I prefer a separated file for styles and I like to use stylus, if you think this is not necessary to be in docs, no problem.
I've build a simple app with this information, app module.
I can make some changes to fix what you think need be modified.
Just let me know, thanks

Should it be enough to document unsafeCSS and let people get the CSS source there however they can, with whatever tools they use? My problem with the way these docs are written is that they appear to assume a specific tool that allowing importing CSS, but the docs aren't in a tools section, nor do they mention the tool needed to make it work.

Yeah, you're right. When I finish the build, all css, js and html (generated by lit-element) are just one file, so, the css is not a external file in the production or development mode.
I've used the point of "if the unsafeCSS import any css code, I just need parse the css in the URL resolve flow before everything.
The unsafeCSS give-me the possibility to import a style from another file, but I need parse the Stylus and / or SASS before give him to unsafeCSS.
I don't know what I need to do now, I just want to share this possibility with another devs, how can I do this @justinfagnani ? Can you help me please ? Do you have any suggestion ?

I think from what you and @justinfagnani said, it seems like this is a good topic to address in the upcoming tooling section. I'll add that into my outline.

That's very great @arthurevans, thank you!
If you guys have any suggestion, I can make some changes; or if I can help with anything, please let me know.

I think we can close this in favor of the docs on lit.dev


Passing custom logger during initialisation

This makes the API more elegant for people who want to pass their own loggers. Prevents code like this -
n := negroni.New()
nRecover := negroni.NewRecovery()
nRecover.Logger = logger
n.Use(nRecover)
nLogger := negroni.NewLogger()
nLogger.ALogger = logger
n.Use(nLogger)

I understand this breaks the API for NewRecovery() and NewLogger() but people wanting to explicitly call these would usually want better control over their code. Otherwise, they can simply call Classic(). Now since the call to Classic() remains the same, I would think we have more to gain by improving the API than by keeping it the same and forcing users to do it in a round-about way.

My 0.2c, when I proposed turning logger into an interface, I deliberately chose not to change the API interface. It's pretty easy to turn this into a helper function and you really only invoke this once when initializing negroni, so it's not really a burden.

I understand. My primary goal was to come to an understandable compromise between API stability and elegance. If the owners choose stability over all else, I have nothing against it. But with the reasoning I have already mentioned above, I feel its a compromise worth making.

Hi @agnivade, thank you for this suggestion!
Unfortunately, I would err towards compatibility, especially for a library in the mature stage of its life like this one. For negroni.Logger, since it only has one attribute, I think requiring users to do negroni.Logger{ALogger: foobar} is not overly burdensome. For negroni.Recovery, I could maybe see a negroni.NewRecoveryWithLogger(foobar) since this is the most likely attribute to be overridden. I'd have to think a bit more on the latter.
We could also consider something like functional options.

negroni.Logger{ALogger: foobar} is certainly an option !
Thanks for looking into this.

Thank you for the discussion!


Fix "Location Tracking Notification" on android

Description
Fixes issue #50 where on Android missed notification that location tracking was disabled.
How to test
Toggle on/off Location Service in settings.

your history got broken, git merge develop does not fix it.. try recreating it with git rebase -i develop


gRPC support

Is this a BUG REPORT or FEATURE REQUEST?:
Feature request
What you expected to happen:
I would like to use gRPC as protocol to call lambda functions.

Can you expand on this ?
I presume you are talking from within the cluster.
A few user stories would help


Typo: add missing space

Approved this commit

@jawn Thank you for your contribution, I am merging it now and it should be live shortly. Please accept our apologies for this initial delay while we work though the initial backlog of contributions.


Podfile requires that the plugin cocoapods-art be installed

I am using cocoapods-art with a Fastlane build but continue to see this error about not finding the plugin:

Your Podfile requires that the plugin cocoapods-art be installed. Please install it and try installation again. (FastlaneCore::Interface::FastlaneShellError)

I verified:

pod plugins shows:

-> CocoaPods Artifactory Plugin (1.0.2)
Enables usage of Artifactory as an index for CocoaPods repo and as a repository for pods.
- Gem:     cocoapods-art
- URL:     https://github.com/JFrogDev/cocoapods-art

Artifactory repo is configured from the pod repo command.

Are you using the bundler to run the cocoapods within your fastlane script?
Try add the cocoapods-art plugin to your gemfile and then bundle install.

I don't use the bundler to run Fastlane commands. Are there any clearer steps to follow to integrate this plugin with Fastlane?
Here is my Fastfile:
fastlane_version "2.64.0"

default_platform :ios

platform :ios do
  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "Create Beta IPA"
  lane :beta do
    cocoapods(
      try_repo_update_on_error: true
    )
    match(type: 'enterprise')
    gym(
      workspace: "./MyProject.xcworkspace",
      scheme: "MyProjectAppCert",
      clean: true,
      configuration: "Cert",
      export_method: 'enterprise',
      export_options:{compileBitcode: false},
      include_bitcode: false,
      include_symbols: true,
      output_directory: "build/exportedIPAs",
      output_name: "MyProject-Cert"
    )
  end

  desc "Create App Store IPA"
  lane :release do
    cocoapods(
      try_repo_update_on_error: true
    )
     match(type: 'enterprise')
    # snapshot
    gym(
      scheme: "MyProjectAppProd",
      clean: true,
      configuration: "Release",
      export_method: "enterprise",
      output_name: "MyProject-Release",
      output_directory: "build/exportedIPAs"
    )
  end
end

My .Gemfile in the project:
source "https://myartifactoryurl.com/artifactory/api/gems/rubyfeed/"

gem "fastlane"
gem "cocoapods-art"

Same error here did you find a solution ?

if you encounter a problem like these:

"Your Podfile requires that the plugin cocoapods-art be installed"
"Unknown command: "repo-art"
maybe you have much more cocoapods installation on your machine, or have installed cocopods from brew.
Uninstall all of theme; install cocoapods from gem and run pod repo-art again.

do u know please how to increment the number_build because i am using the lane increment_build_number but i continue to see the error :
"Cannot set build number with plist path containing $(SRCROOT)
Please remove $(SRCROOT) in your Xcode target build settings"

bundle exec pod install


Simple fix to porcupine not able to read access_key at line 60.

Read the README.MD and at the bottom you will know what todo.

Thank you for your contribution, @Predatorr2!


Replace ARCCache with TwoQueueCache to avoid patent issue

As per @zeripath's suggestion.

Codecov Report

Merging #16240 (8bb6362) into main (0393a57) will increase coverage by 1.23%.
The diff coverage is 48.93%.

@@            Coverage Diff             @@
##             main   #16240      +/-   ##
==========================================
+ Coverage   44.24%   45.47%   +1.23%
==========================================
  Files         695      705      +10
  Lines       82341    83154     +813
==========================================
+ Hits        36429    37817    +1388
+ Misses      40014    39271     -743
- Partials     5898     6066     +168

Impacted Files
Coverage Δ

cmd/generate.go
0.00% <0.00%> (ø)

cmd/hook.go
0.00% <0.00%> (ø)

models/action.go
47.12% <ø> (ø)

models/oauth2.go
28.00% <0.00%> (-1.17%)
:arrow_down:

models/repo_archiver.go
0.00% <0.00%> (ø)

models/user.go
52.32% <ø> (-1.07%)
:arrow_down:

modules/context/repo.go
52.99% <0.00%> (-0.30%)
:arrow_down:

modules/generate/generate.go
0.00% <0.00%> (-16.00%)
:arrow_down:

modules/git/error.go
50.00% <0.00%> (-4.24%)
:arrow_down:

modules/git/last_commit_cache_nogogit.go
35.84% <0.00%> (+0.66%)
:arrow_up:

... and 184 more

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 71c5a8f...8bb6362. Read the comment docs.


Update items based on ide

add the function of gpio and RTC

add gpio and rtc function and example

RTC is working fine - i already use this functions. Thank you very much.


PickerIOS and DatePickerIOs generate warnings about refs when mocked by jest

Is this a bug report?
Yes

Have you read the Contributing Guidelines?
Yes
Environment

Environment:
OS:  macOS Sierra 10.12.6
Node:  7.7.2
Yarn:  Not Found
npm:  4.1.2
Watchman:  4.7.0
Xcode:  Xcode 9.0 Build version 9A235
Android Studio:  2.3 AI-162.3934792
Packages: (wanted => installed)
react: 16.0.0-alpha.12 => 16.0.0-alpha.12
react-native: 0.48.3 => 0.48.3
Steps to Reproduce

Run the attached test with jest

Expected Behavior

No warning should be generated.
Actual Behavior

Warning: Stateless function components cannot be given refs. Attempts to access this ref will fail.

    Check the render method of `PickerIOS`.
        in Unknown (created by PickerIOS)
        in View (created by View)
        in View (created by PickerIOS)
        in PickerIOS

Reproducible Demo

import React from 'react';
import { PickerIOS } from 'react-native';
import renderer from 'react-test-renderer';

describe('StateLessMocks', () => {
  it('generates a warning', () => {
    const tree = renderer.create(<PickerIOS />).toJSON();
    expect(tree).toMatchSnapshot();
  });
});

Facing the same problem here


Cypress test

Fixes ISSUE #xxx
Description
What will be the pain point if you don't make this change?
Tests
Before fix
screenshots, console outputs or logs are acceptable.
After fix
screenshots, console outputs or logs are acceptable.

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

Coverage data is based on head (30dd137) compared to base (e4d44c6).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage   43.70%   43.70%
=======================================
  Files          10       10
  Lines        1167     1167
=======================================
  Hits          510      510
  Misses        624      624
  Partials       33       33

Flag
Coverage Δ

unittests
43.70% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Auto scaling DynamoDB tables

I'm looking for some help to complete this PR.
This adds the ability to auto scale DynamoDB provisioned capacity.
Steps:

[x] Define the raw CF resources
[ ] Figure out how to pass required references to each resource
[ ] Figure out how to add the resources to the final template conditionally (either in code or with a CF condition)

Closing this PR as it is stale and such changes to the CLI functions requiring design and API reviews. @alexjurkiewicz feel free to open an issue if you are still interested seeing this feature in the CLI and you think it would be useful.


feat/run trap signals

refactor: rename HandleInterrup -> Trap Trap now accepts the signals it traps
feat: move SimpleAnimationScreen to anim pkg

Had to create a patch from since updated much since then.


Part2: Vectorize operations for Radix-2 FFT & re-work vectorization part

The target branch eh/fft_radix2_and_re_work_sim would be merged into master when two parts are done: #253 #254
Part2

Vectorize operations for Radix-2 FFT
Re-work also vectorization part to avoid duplication codes

@slaperche-scality could you review it?

Could you squash all the "rename *" commits into the one that introduced the uppercase names?
(basically, edit the commit that introduces these functions instead of adding extra commit on the top).
That would ease the review and keep the git log readable :slightly_smiling_face:

@slaperche-scality sure, the commits are squashed. Thanks :)

Nice squashing, the PR looks better now.
I think we can still squash some:

"SIMD 256 u16 u32: remove useless files" + "SIMD 256 u16 u32: remove useless files" =  "SIMD{128,256}/{u16,u32}: remove useless files"
"FFT_2n.h: compute indices for SIMD" + "FFT_2n.cpp: compute indices for SIMD" = "FFT_2n: compute indices for SIMD"
"FEC RS FNT: simd indices as member variables" + "FEC Vectorisation: use FNT's simd indices"

@slaperche-scality thank you 👍


Fix Python distribution test

The Python wheel command is quite strange, its may not well documented the version that added the additional argument.
So, I presume an upgrade of the package may solve the problem.
Failed log:

They started failing here: https://source.cloud.google.com/results/invocations/98c11d21-a520-493c-a566-1b8ebebafee4/log

Related PR #18306

I have seen three version of the wheel package commends set. The official document seems obsolete long ago.

Oldest version: {keygen,sign,unsign,verify,unpack,install,install-scripts,convert,version,help}.
Documented version: {unpack,pack,convert,version,help} with destination argument -d/--dest-dir.
Latest version: {unpack,pack,convert,version,help} with destination argument -d/--dest.

I will use the -d for destination argument, so it will compliant with the two latter versions.

@jtattermusch This fix solved the distribtest bug in last pull request, here is the log:
https://source.cloud.google.com/results/invocations/d3f7d1db-e829-4578-a797-6a3ac9141b88/targets
However, there is csharp distribtest failure:
+ PLATFORM_ARCH=linux_x64
++ uname
+ '[' Linux == Darwin ']'
++ getconf LONG_BIT
+ '[' 64 == 32 ']'
+ PROTOC=../packages/Grpc.Tools.1.20.0-dev201903132050/tools/linux_x64/protoc
+ PLUGIN=../packages/Grpc.Tools.1.20.0-dev201903132050/tools/linux_x64/grpc_csharp_plugin
+ ../packages/Grpc.Tools.1.20.0-dev201903132050/tools/linux_x64/protoc --plugin=protoc-gen-grpc=../packages/Grpc.Tools.1.20.0-dev201903132050/tools/linux_x64/grpc_csharp_plugin --csharp_out=. --grpc_out=. -I . testcodegen.proto
test_codegen/test_codegen.sh: line 34: ../packages/Grpc.Tools.1.20.0-dev201903132050/tools/linux_x64/protoc: Is a directory
+ FAILED=true
+ '[' '' '!=' '' ']'
+ docker rm -f build_and_run_docker_b3a567bd-1b1b-4ac8-b977-da7a3f6c9131
build_and_run_docker_b3a567bd-1b1b-4ac8-b977-da7a3f6c9131
+ '[' true '!=' '' ']'
+ exit 1

Linux Distribtest: https://source.cloud.google.com/results/invocations/8971512e-5056-484c-8d26-047597786b95/targets/grpc%2Fcore%2Fmaster%2Flinux%2Fgrpc_distribtests/log
maxOS Distribtest: https://source.cloud.google.com/results/invocations/2e062cde-d8b9-4bcd-a368-fff2f2f9a00c/log

@lidizheng  thanks for the heads up with C# distribtest - I believe that's unrelated to your change. I'll investigate.


                                                 TestSuite['id'],'true','full')
                        |                        ^ (bad-continuation)
C:428, 0: Exactly one space required after comma
                                                 TestSuite['id'],'true','full')
                                                                ^ (bad-whitespace)
C:428, 0: Exactly one space required after comma
                                                 TestSuite['id'],'true','full')
                                                                       ^ (bad-whitespace)
C:435, 0: Trailing whitespace (trailing-whitespace)
C:437, 0: Exactly one space required around assignment
        projects=self.getProjects()
                ^ (bad-whitespace)
C:445, 0: Trailing whitespace (trailing-whitespace)
C:448, 0: Trailing whitespace (trailing-whitespace)
C:450, 0: Exactly one space required around assignment
        projects=self.getProjects()
                ^ (bad-whitespace)
C:458, 0: Trailing whitespace (trailing-whitespace)
C:461, 0: Trailing whitespace (trailing-whitespace)
C:463, 0: Exactly one space required around assignment
        projects=self.getProjects()
                ^ (bad-whitespace)
C:466, 0: Trailing whitespace (trailing-whitespace)
C:470, 0: Trailing whitespace (trailing-whitespace)
C:480, 0: Trailing whitespace (trailing-whitespace)
C:483, 0: Trailing whitespace (trailing-whitespace)
C:491, 0: Trailing whitespace (trailing-whitespace)
C:492, 0: Trailing whitespace (trailing-whitespace)
C:497, 0: Exactly one space required around assignment
        projects=self.getProjects()
                ^ (bad-whitespace)
C:498, 0: Exactly one space required around assignment
        result=-1
              ^ (bad-whitespace)
C:500, 0: Trailing whitespace (trailing-whitespace)
C:500, 0: Unnecessary parens after 'if' keyword (superfluous-parens)
C:505, 0: Trailing whitespace (trailing-whitespace)
C:513, 0: Trailing newlines (trailing-newlines)
C:  1, 0: Missing module docstring (missing-docstring)
C: 61, 8: Invalid attribute name "stepsList" (invalid-name)
C: 64, 4: Invalid method name "_changePositionalArgConfig" (invalid-name)
C:100, 4: Missing method docstring (missing-docstring)
E:101,15: Too many positional arguments for method call (too-many-function-args)
W:103, 4: Parameters differ from overridden 'getTestCaseIDByName' method (arguments-differ)
C:119,11: Using type() instead of isinstance() for a typecheck. (unidiomatic-typecheck)
W:124, 4: Parameters differ from overridden 'createTestCase' method (arguments-differ)
C:162, 4: Invalid method name "getProjectIDByNode" (invalid-name)
E:166,20: Too many positional arguments for method call (too-many-function-args)
E:168,20: Too many positional arguments for method call (too-many-function-args)
C:171, 4: Invalid method name "copyTCnewVersion" (invalid-name)
C:171, 4: Invalid argument name "origTestCaseId" (invalid-name)
C:171, 4: Invalid argument name "origVersion" (invalid-name)
C:191, 4: Invalid method name "copyTCnewTestCase" (invalid-name)
C:191, 4: Invalid argument name "origTestCaseId" (invalid-name)
C:191, 4: Invalid argument name "origVersion" (invalid-name)
C:216, 4: Invalid method name "_copyTC" (invalid-name)
C:216, 4: Invalid argument name "origTestCaseId" (invalid-name)
C:216, 4: Invalid argument name "changedArgs" (invalid-name)
C:216, 4: Invalid argument name "origVersion" (invalid-name)
C:240, 8: Invalid variable name "origArgItems" (invalid-name)
E:240,23: Too many positional arguments for method call (too-many-function-args)
E:240,23: Unexpected keyword argument 'version' in method call (unexpected-keyword-arg)
C:245, 9: Invalid variable name "posArgValues" (invalid-name)
C:245,23: Invalid variable name "newArgItems" (invalid-name)
C:251, 4: Invalid method name "_copyTCbuildArgs" (invalid-name)
C:251, 4: Invalid argument name "origArgItems" (invalid-name)
C:251, 4: Invalid argument name "changedArgs" (invalid-name)
R:251, 4: Too many local variables (16/15) (too-many-locals)
C:269, 9: Invalid variable name "posArgNames" (invalid-name)
C:269,22: Invalid variable name "optArgNames" (invalid-name)
C:269,35: Invalid variable name "manArgNames" (invalid-name)
C:276, 8: Invalid variable name "externalArgNames" (invalid-name)
C:278, 8: Invalid variable name "externalTointernalNames" (invalid-name)
C:288, 8: Invalid variable name "newArgItems" (invalid-name)
C:289,12: Invalid variable name "exArgName" (invalid-name)
C:290,12: Invalid variable name "inArgName" (invalid-name)
C:296,12: Invalid variable name "changedProjID" (invalid-name)
C:300,13: Invalid variable name "argName" (invalid-name)
C:300,22: Invalid variable name "argValue" (invalid-name)
C:304, 8: Invalid variable name "posArgValues" (invalid-name)
C:305,12: Invalid variable name "argName" (invalid-name)
W:269,35: Unused variable 'manArgNames' (unused-variable)
C:315, 4: Invalid method name "listKeywordsForTC" (invalid-name)
E:336,19: Too many positional arguments for method call (too-many-function-args)
E:336,19: Unexpected keyword argument 'testcaseexternalid' in method call (unexpected-keyword-arg)
E:343,24: Unexpected keyword argument 'testcaseid' in method call (unexpected-keyword-arg)
C:348, 4: Invalid method name "listKeywordsForTS" (invalid-name)
E:354,24: Too many positional arguments for method call (too-many-function-args)
E:354,24: Unexpected keyword argument 'getkeywords' in method call (unexpected-keyword-arg)
C:372, 4: Invalid method name "countProjects" (invalid-name)
C:379, 4: Invalid method name "countTestPlans" (invalid-name)
C:384, 8: Invalid variable name "nbTP" (invalid-name)
E:386,18: Too many positional arguments for method call (too-many-function-args)
C:387,12: Invalid variable name "nbTP" (invalid-name)
C:390, 4: Invalid method name "countTestSuites" (invalid-name)
C:395, 8: Invalid variable name "nbTS" (invalid-name)
C:397,12: Invalid variable name "TestPlans" (invalid-name)
E:397,24: Too many positional arguments for method call (too-many-function-args)
C:398,16: Invalid variable name "TestPlan" (invalid-name)
C:399,16: Invalid variable name "TestSuites" (invalid-name)
E:399,29: Too many positional arguments for method call (too-many-function-args)
C:400,16: Invalid variable name "nbTS" (invalid-name)
C:403, 4: Invalid method name "countTestCasesTP" (invalid-name)
C:408, 8: Invalid variable name "nbTC" (invalid-name)
C:410,12: Invalid variable name "TestPlans" (invalid-name)
E:410,24: Too many positional arguments for method call (too-many-function-args)
C:411,16: Invalid variable name "TestPlan" (invalid-name)
C:412,16: Invalid variable name "TestCases" (invalid-name)
E:412,28: Too many positional arguments for method call (too-many-function-args)
C:413,16: Invalid variable name "nbTC" (invalid-name)
C:416, 4: Invalid method name "countTestCasesTS" (invalid-name)
C:421, 8: Invalid variable name "nbTC" (invalid-name)
C:423,12: Invalid variable name "TestPlans" (invalid-name)
E:423,24: Too many positional arguments for method call (too-many-function-args)
C:424,16: Invalid variable name "TestPlan" (invalid-name)
C:425,16: Invalid variable name "TestSuites" (invalid-name)
E:425,29: Too many positional arguments for method call (too-many-function-args)
C:426,20: Invalid variable name "TestSuite" (invalid-name)
C:427,20: Invalid variable name "TestCases" (invalid-name)
E:427,32: Too many positional arguments for method call (too-many-function-args)
C:429,24: Invalid variable name "TestCase" (invalid-name)
C:430,24: Invalid variable name "nbTC" (invalid-name)
W:429,24: Unused variable 'TestCase' (unused-variable)
C:433, 4: Invalid method name "countPlatforms" (invalid-name)
C:438, 8: Invalid variable name "nbPlatforms" (invalid-name)
C:440,12: Invalid variable name "TestPlans" (invalid-name)
E:440,24: Too many positional arguments for method call (too-many-function-args)
C:441,16: Invalid variable name "TestPlan" (invalid-name)
C:442,16: Invalid variable name "Platforms" (invalid-name)
E:442,28: Too many positional arguments for method call (too-many-function-args)
C:443,16: Invalid variable name "nbPlatforms" (invalid-name)
C:446, 4: Invalid method name "countBuilds" (invalid-name)
C:451, 8: Invalid variable name "nbBuilds" (invalid-name)
C:453,12: Invalid variable name "TestPlans" (invalid-name)
E:453,24: Too many positional arguments for method call (too-many-function-args)
C:454,16: Invalid variable name "TestPlan" (invalid-name)
C:455,16: Invalid variable name "Builds" (invalid-name)
E:455,25: Too many positional arguments for method call (too-many-function-args)
C:456,16: Invalid variable name "nbBuilds" (invalid-name)
C:459, 4: Invalid method name "listProjects" (invalid-name)
C:468, 4: Invalid method name "initStep" (invalid-name)
C:481, 4: Invalid method name "appendStep" (invalid-name)
C:493, 4: Invalid method name "getProjectIDByName" (invalid-name)
C:493, 4: Invalid argument name "projectName" (invalid-name)
C:493, 4: Missing method docstring (missing-docstring)
C:496, 4: Invalid method name "getProjectByName" (invalid-name)
C:496, 4: Invalid argument name "projectName" (invalid-name)
C:496, 4: Missing method docstring (missing-docstring)
C:507, 4: Invalid constant name "tl_helper" (invalid-name)
C:509, 4: Invalid constant name "myTestLink" (invalid-name)
C: 25, 0: standard import "import sys" should be placed before "from .testlinkapigeneric import TestlinkAPIGeneric, TestLinkHelper" (wrong-import-order)

----------------------------------------------------------------------
Your code has been rated at -10.11/10 (previous run: -10.11/10, +0.00)

closed PR #27


Add BLE support on ESP32 target

Add a feature on ESP32 target to send data over BLE simulating a Tilt.

Added to dev


[Emma] HomePage Mobile Hover Effect

Summary
The css effects that are done on the hover effect on the homepage do not translate well to the mobiles. Hover effect is difficult to replicate and therefore in the emma theme the entire page just looks like a gallery of images as opposed to posts/articles/guides whatever. Until a user clicks it they realize o this is something that can be clicked on. It's not intuitive and would look much nicer if a different style of effect was used on mobile devices.
Perhaps just a slight animation every few seconds forcing the hover vs non-hover view.
Basic example
Sorry my css skills are lacking which is why i decided to use a theme. My best guess would be something along the lines of.
I would recommend on mobile view to possibly consider using a different style like

  <Image />

    <Title />
    <Subdescription />

Motivation
The mobile user's hover effect is really bad. It is not user-intuitive and upon research into this problem, I discovered hover effect on mobile can cause a need to double-tap the image to open it up as well.

Hi, thanks for the issue!
Implementing hover effects for mobile users is a really big topic and people try to solve it in different ways for years now. I've seen a lot of similar websites to that theme solve it in the same way, meaning there is no distinctive hover style for mobile users. So I won't change anything.
However, you can of course change the theme to your liking by applying CSS. I wouldn't recommend the on-off animation you suggested but maybe showing the overlay with 50% and the text 100%?
Hope that helps. Thanks for using the theme!


solved issue of Navbar responsiveness

solved the issue of navbar responsiveness by removing github logo for small devices and decreasing padding-x for button get started

#88


Regression in 0.7.3 compiler handling of inline constants in debug output

The compiler in 0.7.3 emits constants differently in debug output than was done in 0.7.2.  Release output is unchanged.
In 0.7.3 the constant member is included on the class, but the value is inline where used, the member is never referenced.
In 0.7.2 the constant member is included on the class, a member reference is used rather than an inline value.
I suspect one of the following was actually intended:

The member should not be emitted, causing debug and release output to be the same.
The member should be referenced rather than placing the value inline.

Fixed in <IP_ADDRESS> - debug and release outputs exhibit same behavior now ... internal const is not generated as its value has been inlined.


Design: (right sidebar) Change "On this page" to "Contents" (or "Table of Contents")

Describe the changes you'd like
Title says it all.
Describe alternatives you've considered
None. Status quo is OK. Suggested change is nicer, but I'm obviously biased. :)
Additional context
This seems to be the phrasing for the in-page-navigation-tree on all 3-column documentation-oriented themes that I know of (except this theme and the pydata theme). Sample Screenshots: https://gist.github.com/pradyunsg/eeb74ac5b580d502c3d0e248310f273f
I'm happy to file a PR for this, if there's interest in this idea. :)

I think it's a reasonable idea. My question is what those themes call the left sidebar, in that case. I just wanna make sure that our naming is consistent so we don't confuse the mental model that folks have.

Navigation is what I've seen most often (the default Sphinx theme, and the entire lineage of themes that led to it, uses that).

Cool - then we should just make sure it's consistent in our docs etc, and I'm +1 on making it "contents" or "table of contents", whichever you think makes most sense.

not table of contents (that confuses it with the left side bar)

"Contents" it is. :)

yeh or "Page Contents", no strong opinion though

BTW, feel free to also propose such changes in the pydata-sphinx-theme!


Electric Motor Temperature Analysis

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : Electric Motor Temperature Analysis
:red_circle: Aim : Analyse the temperature of the motors given in the dataset.
:red_circle: Dataset : https://www.kaggle.com/datasets/wkirgsn/electric-motor-temperature
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' and 'JWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID (If not, then put NA) :
Approach for this Project :
What is your participant role? (Mention the Open Source Program name. Eg. HRSoC, GSSoC, GSOC etc.)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Full name : NIRVIK GHOSH
GitHub Profile Link : @Nirvik07
Participant ID (If not, then put NA) : NA
Approach for this Project : To analyse the Electric Motor Temperature.
What is your participant role? HRSoC 2022 Participant.

Issue assigned to you, also create a prediction model by which we can predict the temperature of the motors based on the particular parameters.
@Nirvik07


Setup analytics log with basic user queries

We need a better understanding of how our users use KnetMiner e.g. search terms used (plus other search data), genes clicked to visualize network. Collected data can improve the usability of KnetMiner and provide users advanced features such as recommendations, trends and a search history.

We want to see analytics data for KnetMiner instances that were tagged with a knetminer-analytics code.
The Analytics dashboards we would like to see for genome and genepage endpoint:

Keywords by time
Keywords by frequency
Gene by time
Gene by frequency
Frequent Gene and Keyword combinations

The Analytics dashboards we would like to see for network endpoint:

Genelist by time
Gene by frequency
Size of network (nodes + edges)

Reviewing this ticket again, I think the minimum requirement is to have an analytics log stored in the cloud (eg S3) to which all different KnetMiner instances can write. The main information we want to learn from the logs (at the moment) is which keywords, genes, regions and their combinations are used. For example, how many times do users search for

just keywords
just gene list
just region
gene list + keyword
region + keyword

The ticket can be closed with an early PoC. @mdonepudi

HOST :: PORT :: TAXID :: SPECIESNAME :: KEYWORD :: LIST :: QTL

IMPLEMENTATION
Brief description of the POC implemented.

writes analytics log in JSON format to <TOMCAT_HOME>/logs/
using AWS CLI and CRON job, the logs are synced to S3 bucket every hour.

CONFIGURATION
Before building an Docker image:

Configure S3 credentials at /common/quickstart/.aws/credentials
Configure S3 bucket region in common/quickstart/.aws/config
Configure S3 bucket name in the S3 sync command in /common/quickstart/analytics-s3-sync.sh
(OPTIONAL) To sync more/less regularly, change cron job configuration in /common/quickstart/analytics-cron

FYI, to deploy https://github.com/Rothamsted/knetminer/blob/analytics-poc-410/common/quickstart/aws/Dockerrun.aws.json needs port set too if not using 8080

When deploying the 410 POC code, I get the following error:
2019-10-14 16:42:13,170 ERROR JSONLayout contains an invalid element or attribute "objectMessageAsJsonObject"
Thoughts, @KeywanHP @mdonepudi ?


Add Event Type: Kafka

This package implements a Kafka queue trigger feed in OpenWhisk.
https://github.com/openwhisk/openwhisk-package-kafka
Add a new event type to bind this to functions.
events:
  - kafka: ...

This should be a clone of the Message Hub event with less parameters.


How can I donate?

I really like this project and I feel compelled to give something back. What do you think about adding a donations link?
I know this was discussed in #49 and the result was negative but I would like you to reconsider it. If you don't want the money for yourself you can just buy a gift for somebody!

I don't really want to accept donations because this is really a side project and if someone gives me money for the project then I feel obliged to do a certain amount of work for it which I might not always have the time for.
I really appreciate the generosity and I'm really glad you like the project but I think the best way to help out is just to use it. Thanks!

Maybe consider to add a donation link to some kind of charity you care about...


Documentation of programmatic configuration to XML translation feature

@albinsuresh Isn't it weird that this is at the "getting started" level?

@henri-tremblay I'm confused. It IS currently in the XML specific xml.adoc file. And the sample code is also in the xml specific GettingStarted class and NOT in the main GettingStarted class. You wanted it elsewhere?

No. My bad. I read too quickly...

test this please


decorator defined in Metaclass triggers reportUndefinedVariable

Environment data

Language Server version: v2022.5.1
OS and version: Ubuntu 22.04 LTS
Python version (& distribution if applicable, e.g. Anaconda): Python 3.9.12

Code Snippet

class CustomMetaClass(type):
    @classmethod
    def __prepare__(cls, *_):
        def my_decorator(method):
            def _inner_function(self, *method_args, **method_kwargs):
                print("Wrapping function")
                method(self, *method_args, **method_kwargs)
                print("Wrapping completed")

            return _inner_function

        return {
            "my_decorator": my_decorator,
        }

class BaseClass(metaclass=CustomMetaClass):
    def __init__(self, name: str):
        self.name = name

    @my_decorator
    def my_function(self):
        print(f"{self.name} function")

if __name__ == "__main__":
    base_class = BaseClass("BaseClass")
    base_class.my_function()

Expected behavior
Pylance should not complain about my_decorator not being defined in the Baseclass implementation. The whole point of the metaclass is to avoid to write @Metaclass.my_decorator. This metaclass makes the decorator accessible from any child classes as if it were defined in it.
Actual behavior
Line 21, Pylance is Reporting an undefined variable wrongfully.

Logs

(24586) [FG] parsing: /home/jocelyn/.vscode/extensions/ms-python.vscode-pylance-2022.5.1/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 1ms] (7ms)
(24586) [FG] binding: /home/jocelyn/.vscode/extensions/ms-python.vscode-pylance-2022.5.1/dist/typeshed-fallback/stdlib/typing_extensions.pyi (2ms)
(24586) [FG] parsing: /home/jocelyn/.vscode/extensions/ms-python.vscode-pylance-2022.5.1/dist/typeshed-fallback/stdlib/typing.pyi [fs read 1ms] (34ms)
(24586) [FG] binding: /home/jocelyn/.vscode/extensions/ms-python.vscode-pylance-2022.5.1/dist/typeshed-fallback/stdlib/typing.pyi (9ms)
(24586) [FG] parsing: /home/jocelyn/.vscode/extensions/ms-python.vscode-pylance-2022.5.1/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 1ms] (15ms)
(24586) [FG] binding: /home/jocelyn/.vscode/extensions/ms-python.vscode-pylance-2022.5.1/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (2ms)
(24586) [FG] parsing: /home/jocelyn/.vscode/extensions/ms-python.vscode-pylance-2022.5.1/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (3ms)
(24586) [FG] binding: /home/jocelyn/.vscode/extensions/ms-python.vscode-pylance-2022.5.1/dist/typeshed-fallback/stdlib/abc.pyi (0ms)
(24586) [FG] parsing: /tmp/pyright-24586-c32ugZvjArF3/builtins-24586-0QLab55J3ny2-.py [fs read 2ms] (89ms)
(24586) [FG] binding: /tmp/pyright-24586-c32ugZvjArF3/builtins-24586-0QLab55J3ny2-.py (23ms)

This sort of dynamic behavior isn't supported by a static type checker like pyright (which is the type checker that underlies pylance). You're dynamically injecting new symbols into the namespace of classes that derive from this metaclass.
This behavior is also unsupported by other type checkers like mypy.
You have a few options:

Don't use the __prepare__ technique.
Disable the reportUndefinedVariable diagnostic check within pylance.
Use a # type: ignore comment to silence specific instances of this diagnostic.

Thanks for the enlightment


How to combine different module use cases

Hi @kgrzybek, firstly thank you for this great repository.
I would like to talk about a case that I have in my project.
For instance, we have 2 modules in our project. Let's call them Reservation and Profile modules
I want to update my profile and before updating should check the reservation status which includes that profile.
So, we have a process that includes 2 different modules use cases
Would you suggest that using IProfileModule and IReservationModule interfaces in the same endpoint or another handler?
or Would you suggest that we should define these aggregates in the same module?
or any other suggestion?

Hello,
May i suggest to see the problem from module point of view.
When your Reservation Module update the status you can send domain even and catch with your Profile Module (apply some business transformation) and store the result, than you don't need to interact with many modules.
This is Hollywood Principle : "Don't Call Us, We'll Call You"
This issue is a bit older mmaybe you have found an other solution to share, I hope my comment can help you


stacks on board

Normally everything should merge correctly

Understood that this was solved and you are doing something else