[Question] Function deploy debug | Debug prepare container

Is this a BUG REPORT or FEATURE REQUEST?: Question
What happened:
When I try to deploy a function with ContentType: url+zip, I got "container terminate (code: 35)".

What you expected to happen:
Is there anyway that we can get the log for each step?
How to reproduce it (as minimally and precisely as possible):
Nope :)
Anything else we need to know?:
Nope :)
Environment:

Kubernetes version (use kubectl version): v1.19.4
Kubeless version (use kubeless version): v1.0.7-dirty
Cloud provider or physical cluster: physical cluster

Any help will be appreciated :)

I think remove the command flag --silent in curl is a good way to debug. :)

Update: I think the kubeless/unzip can not resolve internal domain correctly. I use kubeless/unzip and busybox in same namespace with same resolv.conf but kubeless/unzip give a strange address.


Proposal: Why not consider using LLM to do some review work?

For example:
package main

import "fmt"

func main() {
	i := 0
	go func() {
		for i < 10 {
			i += 1 // want i to be 10
		}
	}()

	// do another thing

	fmt.Println(i)
}

when I ask LLM: Is there something abnormal in this code?
LLM:
Yes, there is a race condition in this code. The variable i is accessed from two different goroutines: the main goroutine and the anonymous goroutine you created. Both are trying to modify i without any form of synchronization, which can lead to unpredictable behavior.
In Go, you can use primitives provided by the sync package, such as sync.WaitGroup and sync.Mutex, to avoid race conditions. Here's how you could modify your code:
package main

import (
    "fmt"
    "sync"
)

func main() {
    var i int
    var wg sync.WaitGroup
    var mu sync.Mutex

    wg.Add(1)
    go func() {
        defer wg.Done()
        for {
            mu.Lock()
            if i >= 10 {
                mu.Unlock()
                break
            }
            i++
            mu.Unlock()
        }
    }()

    // do another thing

    wg.Wait()
    mu.Lock()
    fmt.Println(i)
    mu.Unlock()
}

In this example, we use sync.Mutex to protect access to i and sync.WaitGroup to ensure that the main goroutine waits for the anonymous goroutine to finish before accessing i.

@CarlJi Thank you for your reply.
I use github copilot daily to help me write code and check errors. I think copilot is fully qualified for this job. But I don’t know if github copilot can be called through open api, or we can use gpt4+prompt to achieve similar effects.

use #390 to track.


Enhanced RDoc for CSV::Row

Methods:

to_h
to_csv
dig
inspect

Thanks!

@kou:  Do users more often use CSV with headers?  Or without?

I don't know but both of them are typical use cases.
There are many CSVs with/without headers in the real world.


accountId request param added in delete api

We prefer small, well tested pull requests.
Please refer to Contributing to Spinnaker.
When filling out a pull request, please consider the following:

Follow the commit message conventions found here.
Provide a descriptive summary for your changes.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Add inline code comments to changes that might not be obvious.
Squash your commits as you keep adding changes.
Add a comment to @spinnaker/reviewers for review if your issue has been outstanding for more than 3 days.

Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.
https://devopsmx.atlassian.net/browse/OP-6834

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://spin.prod.opsmx.com/#/applications/gitprtrigger/executions/details/01FA2FV1MN85CGVVB88CPC30TD

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://spin.prod.opsmx.com/#/applications/gitprtrigger/executions/details/01FA2H7CDJPNNDN2M7V0AQJTJW

RunTestJar RESULT: Total tests run: 276, Failures: 2, Skips: 0 Reviewers , please check that the changes in this PR did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-gitpr-parallel/ws/emailable-report-571.html


Remove auth null checks in ExerciseController and HistoryController methods

Summary
Remove auth null checks + fixed indentation both
Close issue(s)
Close #83
Close #84

Hi @dmitriydb ! Thanks again for your contribution and for applying the changes. Well done 👍 All looks good now and this will be merged soon 🎉 I will reply to your comment on the other PR.

@all-contributors add @dmitriydb for code


Added layered Fractal noise

Generates 3D noise which is a sum of low frequency to high frequency noise.
Increasing the octave adds another higher layer of frequency.
The persistence parameter adjusts how much each following octave affects the whole noise output.

Well sorry for saying it but I don't want to merge this mess. This is basically the same as #24 but with extra, unwanted commits.
I appreciate your effort, if you want to try again you can open up a new PR with just commit d80d018cbb8e5793a3e1408e2f6019acd33a40df.
Easiest way to do that is to make a new branch (based on my dev branch, not one of your patch branches), merge in the single commit to that new branch (make sure it's autoformatted) and send a PR.


GHC-8.8 compatibility

Looks like the base bound is too tight:
[__2] next goal: sws (user goal)
[__2] rejecting: sws-<IP_ADDRESS> (conflict: base==<IP_ADDRESS>/installed-<IP_ADDRESS>, sws
=> base>=4.11.1 && <4.13)
[__2] skipping: sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS>,
sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS>,
sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS>, sws-<IP_ADDRESS> (has the same
characteristics that caused the previous version to fail: excludes 'base'
version <IP_ADDRESS>)
[__2] fail (backjumping, conflict set: base, sws)

Thanks for the prod. I actually had a local change bumping the version for almost a year.


fix(deps): update husky package to the latest

🎉 Thanks for sending this pull request! 🎉
Please make sure the title is clear and descriptive.
If you are fixing a typo or documentation, please skip these instructions.
Otherwise please fill in the sections below.
Which problem is this pull request solving?
Example: I'm always frustrated when [...]
List other issues or pull requests related to this problem
Example: This fixes #5012
Describe the solution you've chosen
Example: I've fixed this by [...]
Describe alternatives you've considered
Example: Another solution would be [...]
Checklist
Please add a x inside each checkbox:

[x] I have read the contribution guidelines.
[x] The status checks are successful (continuous integration). Those can be seen below.

In order for this to apply, manual steps will be needed in your projects:

remove husky from the upstream devDependencies
create the needed changes to migrate

The second step can be done semi-automatically, there are instructions in the husky releases page.

This looks good, thanks!
Would you like to please change the commit message from chore: to fix:? This will ensure our release-please bot creates a new release for this change.

Can't you change it when squashing and merging? I'm away from my main
machine right now
On Mon, Jan 10, 2022, 20:35 ehmicky @.***> wrote:

This looks good, thanks!
Would you like to please change the commit message from chore: to fix:?
This will ensure our release-please bot creates a new release for this
change.
—
Reply to this email directly, view it on GitHub
https://github.com/netlify/eslint-config-node/pull/403#issuecomment-1009225576,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVLNJLNLSSKGOFIHH5GFDUVMRHHANCNFSM5LQO6BYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

I have tried it in https://github.com/netlify/js-client/pull/657, and there might be a few additional tweaks needed:

https://github.com/netlify/eslint-config-node/pull/413
https://github.com/netlify/eslint-config-node/pull/414
https://github.com/netlify/eslint-config-node/pull/415

Sorry, about that! It worked fine for this project here and I thought it was OK. Feel free to revert the update if it's too much trouble :)
PS. I'm on Windows so I couldn't have noticed the permission issue :)

Also, to clarify, someone will need to make the related changes to each project, i.e. it's not just a simple update. I should have communicated this better. So, this should have been a major version bump probably.

No worries @XhmikosR! We needed to make that upgrade, so this is very helpful. We just need to make a few tweaks and it will work. Also, I believe the old Husky setup still seems to work until the changes you are mentioned are performed.
You also did communicate the changes to be done :+1:
The problem is that our bot is automatically merging the upgrade PRs, so we have to do this in separate PRs
I am currently trying to make it work on the netlify/js-client repository to see which are those changes, so we can then apply it on the other repositories :+1:

Thanks for your patience, I misjudged the upgrade for sure. Ideally, you should update but it looks like it might be a lot of trouble.
I'd be curious to see one project migrated. And don't feel bad reverting this PR if needed. I'd at least make it a major bump due to the manual work required :)


How to Install and Use in Azure Data Studio?

Please Guide

what's the electron & node versions for win10? what's the diff?

Please Guide

I would like to know in order to contribute. I like so much this repo.


adding the line install

Adding the line of code on how to install the package

Ty :)

Coverage remained the same at 100.0% when pulling 231ddc050874fab3cd5d56cbb5130df9b84d9351 on MarcusMann:patch-1 into 0d2e5860f9d2f0fc03d08cedb26b5f81bf1e8fd8 on yury-dymov:master.


Defect: mvapich2 build fails to run tests

Avg response time

Please make sure to put any logs, terminal output, or code in
[fenced code blocks]. Please also read the [contributing guidelines]
before submitting a new issue.
Defect/Bug Report

The title of the issue should start with Defect: followed by a
succinct title.

OpenCoarrays Version: <!-- caf --version or ./install.sh --version -->
2.0.0
Fortran Compiler:
GNU 7.2.0
C compiler used for building lib:
GNU 7.2.0
Installation method:
install.sh
Output of uname -a:
Linux obst25.zeuthen.desy.de 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 04:11:40 CST 2018 x86_64 x86_64 x86_64 GNU/Linux
MPI library being used:
mvapich2 2.2
Machine architecture and number of physical cores:
x86_64, 16 cores
Version of CMake:
cmake 3.9.2 from OpenHPC

Observed Behavior
the build finishes, but there are linking problems when trying to build the tests
Expected Behavior
tests should build and execute fine
Steps to Reproduce

install CentOS 7.4
add OpenHPC repository
build with the attached spec file with the --define mpi_family\ mvapich2 switch

Attached is the build log:
build.log.txt
And the rpm SPEC file:
opencoarrays.spec.txt
The output of caf -w is
caf wraps /opt/ohpc/pub/compiler/gcc/7.2.0/bin/gfortran
and caf -s is:
/opt/ohpc/pub/compiler/gcc/7.2.0/bin/gfortran -I/builddir/build/BUILD/OpenCoarrays-2.0.0/prerequisites/builds/opencoarrays/2.0.0/include/OpenCoarrays-2.0.0_GNU-7.2.0 -fcoarray=lib -Wl,-rpath -Wl,/opt/ohpc/pub/mpi/mvapich2-gnu7/2.2/lib -Wl,--enable-new-dtags ${@} /builddir/build/BUILD/OpenCoarrays-2.0.0/prerequisites/builds/opencoarrays/2.0.0/lib64/libcaf_mpi.a /opt/ohpc/pub/mpi/mvapich2-gnu7/2.2/lib/libmpifort.so /opt/ohpc/pub/mpi/mvapich2-gnu7/2.2/lib/libmpi.so

OK, I have researched this a bit, mvapich2 2.2 seems to be too old and doesn't have this binding yet. Maybe a configure check should be added for this?

@LaHaine Feel free to submit a pull request with the suggested configure request.  Given other commitments, I don't think anyone else will do so.  For now, I'll close this issue now that you have determined the cause.


TypeError: 'ariadne_jwt'

thats the error I am getting.

Provide more info of project setup and error traceback

I found a way to resolve it. I had messed up the setup.


Update index.md

Added brief intro to Web Accessibility for a background to the practical guide on implementation.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi,
Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details

@RandellDawson Kindly give further information on what I did wrong, please. That will help me make quality PRs in the future. Thanks in anticipation.

You put a check mark by My pull request has a descriptive title (not a vague title like Update index.md), but yet your title is Update index.md.  Give a better description of what your PR does.


WIP - Recreate NetworkAssertions on operator resuming operations

Updates the operator logic to upsert CronJobs,  Jobs and ConfigMaps on NetworkAssertion creation, as well as operator resumption (e.g. after an upgrade).
To address #110

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.541%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
303

Relevant Lines:
331

💛  - Coveralls


"clang 8 is required, but it's not installed"

I followed this site.　https://carla.readthedocs.io/en/0.9.6/how_to_build_on_linux/
However, I got the following message in the "make launch" section of Build CARLA.
"clang 8 is required, but it's not installed.
Util/BuildTools/Linux.mk:143: recipe for target 'setup' failed
make: ***[setup] Error 1"
Ubuntu version 18.04.5 LTS
Unreal Engine 4.22
However i can't install clang 8 because i don't know ubuntu well
please help what can i do?

However i can't install clang 8 because i don't know ubuntu well

Hopefully this doesn't come across as too blunt, because it isn't my intentions to be rude...  One likely shouldn't go down the path of compiling CARLA from source without a working knowledge of Debian-like linux distributions (e.g. Ubuntu) and sudo/root access to deploy dependencies.  Attempting to use a different version of clang (or UE for that matter) than the one supported by the version of CARLA you are using will lead you into problems like in Issue #3246 , which are much worse than the learning curve of Ubuntu's package management system apt.
There are vendor supplied binaries and a docker container if your Linux environment doesn't support said binaries (e.g. glibc version mismatches) that will allow you to avoid compiling from source.
Also, the version of clang supported by carla 0.9.6 is clang 7, not clang 8.  The documentation linked is for CARLA 0.9.6.  Are you using the right tag/release of the CARLA source and/or the right documentation's version?  If you are using CARLA 0.9.9.x, the build instructions are here and show you how to deploy clang-8 in Ubuntu 18.04.

I really need carla0.9.6.
I currently have nvidia440 and cuda10.1.243 in my system. Because this is within the recommendation of carla0.9.6, I do not think that there is not a problem especially...(By the way, the reason why nvidia is 440 is nvidia, I thought to specify 418 at first and install it, but because my PC does not boot Ubuntu like this site
https://itectec.com/ubuntu/ubuntu-problems-with-booting-the-system/
, I use 440  by $sudo ubuntu-drivers autoinstall   )
I think the Ubuntu kernel is fine too, but I still get the same clang error as before.
By the way, unreal engine 4.22 starts with no problem, and during the build of carla. It goes to /Update.sh with no problem.
I describe the result of nvidia-smi as follows. Is there any solution to build carla 0.9.6? Please help me out.
atusi@atusi-G3-3500:~/carla$ uname -rsv
Linux 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC 2020
atusi@atusi-G3-3500:~/carla$ nvidia-smi
Sat Sep  5 17:40:49 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.100      Driver Version: 440.100      CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 166...  Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   52C    P8     5W /  N/A |    243MiB /  5944MiB |      4%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1425      G   /usr/lib/xorg/Xorg                           108MiB |
|    0      1599      G   /usr/bin/gnome-shell                         131MiB |
+-----------------------------------------------------------------------------+

https://mail.google.com/mail/u/1?ui=2&ik=7fcc80d93b&attid=0.1&permmsgid=msg-a:r5938779272112668039&view=att&disp=safe&realattid=f_keph73060

It looked like I had an $sudo apt update between
$sudo apt-get install build-essential clang-7 lld-7 g++-7 cmake ninja-build libvulkan1 python python-pip python-dev python3-dev python3-pip libpng16-dev libtiff5-dev libjpeg-dev tzdata sed curl unzip autoconf libtool rsync
and
$pip2 install --user setuptools
, is it possible that this is causing the above error?

+@bernatx I know it's a busy time, but could you provide some help?

As qhaas sais, are you using the right tag/release of the CARLA source and/or the right documentation version?
It seems that you are trying to compile a latest version of CARLA (which needs clang 8) instead of the CARLA 0.9.6 that you need. Please, download the source for the TAG 0.9.6
The message about clang 8 is required only shows when compiling for CARLA 0.9.9.x and UE 4.24

HI ,if you has install llvm@8 [clang-8] ,maybe the install location is not the same the make launch  script : carla/Util/BuildTools/Setup.sh,you need to change the script the clang-8 location as you specify .
example :
##原来的
command -v /usr/bin/clang++-8 >/dev/null 2>&1 || {
echo >&2 "clang 8 is required, but it's not installed.";
exit 1;
}
CXX_TAG=c8
export CC=/usr/bin/clang-8
export CXX=/usr/bin/clang++-8

#以实际位置为准
command -v /usr/local/opt/llvm@8/bin/clang++ >/dev/null 2>&1 || {
echo >&2 "clang 8 is required, but it's not installed.";
exit 1;
}
CXX_TAG=c8
export CC=/usr/local/opt/llvm@8/bin/clang-8
export CXX=/usr/local/opt/llvm@8/bin/clang++

I had to do sudo apt-get install clang in ubuntu 20.04 to make it work


'package:flutter/src/services/text_input.dart': Failed assertion: line 929 pos 12: 'attached': is not true.

从图片一变为图片二时，就会报错【'package:flutter/src/services/text_input.dart': Failed assertion: line 929 pos 12: 'attached': is not true.】。图片一中是自定义的[PopupRoute],点击空白处后自动消失，消失后变为图片二时就报错了。

Hi @liubaoxinggo
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Trap signals rather than killing processes

We were debugging rogue processes and didn't realize the package had a fix for the issue already. However, we believe the more "native" solution here is to leverage Watch::shouldContinue with Laravel's built-in trap for signal trapping.
This simplifies the code and doesn't run another shell command.
BTW we have been using spatie/laravel-signal-aware-command and found that it did not work as expected with signal trapping, and found the native solution works more reliably, as seen in this solution.

Very nice, thank you!

For me this doesn't work. After making some changes in a project and killing horizon I get this log:
$ sail artisan horizon:watch

   INFO  Starting Horizon and will restart it when any files change...

Horizon started successfully.
   INFO  Change detected! Restarting horizon...

Horizon started successfully.
   INFO  Change detected! Restarting horizon...

Horizon started successfully.
   INFO  Change detected! Restarting horizon...

Horizon started successfully.
^CShutting down...
Shutting down...
Shutting down...
Shutting down...

Also in a Horizon dashboard I can see that after each change new worker is started.

I have double check 1.0.4 version - all worker processes between reloads seems to be killed normally.
My environment:

Mac M1
Laravel Sail 1.25.0
Laravel 10.23.1
Horizon 5.21.0

@joelvh could you have a look?

Hi @sdapkus @freekmurze,
It appears that this is a bug that was already present. This PR addressed signal trapping, but didn't account for the signal forwarding piece that the previous process killing was addressing.
At some point, we generalized this watcher command to watch any process we want, and we fixed it in our version of the command. FWIW, I wasn't aware that it was something that was a pre-existing bug here as well.
The fix in #22 should do the trick. @sdapkus if you could please verify. Thanks!

We're also experiencing this when running Horizon inside a container: https://github.com/spatie/laravel-horizon-watcher/issues. Has anyone found a workaround? We've got a remote team and our app has a lot of services, so running Horizon outside of our Docker development environment isn't an option unfortunately.


Fixes bug where colormaps would be unordered

When generating a smart_colormap, if vmin is positive, zeropoint become negative. This cascades into generating the new cmap from a list containing the following values:
[0, <0, 1]
This list being unordered causes an exception when trying to save the figure:
File "/opt/anaconda21/lib/python2.7/site-packages/matplotlib/colors.py", line 731, in _init
self.N, self._segmentdata['red'], self._gamma)
File "/opt/anaconda21/lib/python2.7/site-packages/matplotlib/colors.py", line 471, in makeMappingArray
"data mapping points must have x in increasing order")
ValueError: data mapping points must have x in increasing order
This commit just changes zeropoint to it's absolute value, ensuring that it is contained between 0 and 1

Thanks!


Coral TPU pcie/M.2 issues on Debian 12 0 - AMD am4 build

Description
Hi, I'm on Debian 12, tried with a kernel 6.8 install, plus proxmox 8 with kernel 6.8.x and now I'm on Debian 12 again (another fresh install), on kernal 6.1.0-21-amd64. I have followed your steps to build and install this version of gasket-dkms and from the basic checks, things seem ok on the host, but I cannot get the TPUs to work in/with anything.
When I perform a "dmesg | grep -i apex", I get the below:
dmesg | grep -i apex
[ 16.471161] apex 0000:08:00.0: enabling device (0000 -> 0002)
[ 16.474447] apex 0000:08:00.0: Couldn't initialize interrupts: -22
[ 16.476806] apex 0000:09:00.0: enabling device (0000 -> 0002)
[ 16.480201] apex 0000:09:00.0: Couldn't initialize interrupts: -22
[ 16.482306] apex 0000:0a:00.0: enabling device (0000 -> 0002)
[ 16.488254] apex 0000:0a:00.0: Couldn't initialize interrupts: -22
[ 21.504640] apex 0000:09:00.0: Apex performance not throttled due to temperature
[ 21.504639] apex 0000:0a:00.0: Apex performance not throttled due to temperature
[ 21.504657] apex 0000:08:00.0: Apex performance not throttled due to temperature
[ 164.884046] apex 0000:0a:00.0: Couldn't reinit interrupts: -22
[ 164.885596] apex 0000:08:00.0: Couldn't reinit interrupts: -22
[ 164.889985] apex 0000:09:00.0: Couldn't reinit interrupts: -22
[ 196.858032] apex 0000:0a:00.0: Couldn't reinit interrupts: -22
[ 196.861839] apex 0000:08:00.0: Couldn't reinit interrupts: -22
[ 196.866137] apex 0000:09:00.0: Couldn't reinit interrupts: -22
[ 228.844407] apex 0000:0a:00.0: Couldn't reinit interrupts: -22
[ 228.848057] apex 0000:08:00.0: Couldn't reinit interrupts: -22
[ 228.852692] apex 0000:09:00.0: Couldn't reinit interrupts: -22
[ 260.899907] apex 0000:0a:00.0: Couldn't reinit interrupts: -22
[ 260.903764] apex 0000:08:00.0: Couldn't reinit interrupts: -22
[ 260.908369] apex 0000:09:00.0: Couldn't reinit interrupts: -22
ls -l /dev/apex*
crw-rw---- 1 root apex 120, 0 May 26 09:50 /dev/apex_0
crw-rw---- 1 root apex 120, 1 May 26 09:50 /dev/apex_1
crw-rw---- 1 root apex 120, 2 May 26 09:50 /dev/apex_2
lspci -nn | grep 089a
08:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]
09:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]
0a:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]
lsmod | grep apex
apex 28672 0
gasket 126976 1 apex
apt list apex
Listing... Done
golang-github-apex-log-dev/stable 1.1.1-3 all
apt list gasket
Listing... Error!
E: input:0-26: error: Expected pattern
gasket-dkms_1.0-18_all.deb
^^^^^^^^^^^^^^^^^^^^^^^^^^
frigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors
I have the same symptoms with this gasket-dkms build as I had with a previous one, except the permission denied errors are gone from the dmesg output now. Still unable to clear the "Couldn't initialise interrupts: -22" error, which I assume is part of the issue? Any help would be greatly appreciated as I have been fighting with these Coral TPUs for 1 week now.
...Also please advise if this is the wrong place to ask and I will move my post to wherever can be suggested.
Click to expand!
Issue Type
Support
Operating System
Linux
Coral Device
M.2 Accelerator with dual Edge TPU
Other Devices
No response
Programming Language
No response
Relevant Log Output
Hi, I'm on Debian 12, tried with a kernel 6.8 install, plus proxmox 8 with kernel 6.8.x and now I'm on Debian 12 again (another fresh install), on kernal 6.1.0-21-amd64. I have followed your steps to build and install this version of gasket-dkms and from the basic checks, things seem ok on the host, but I cannot get the TPUs to work in/with anything.

When I perform a "dmesg | grep -i apex", I get the below:

dmesg | grep -i apex
[ 16.471161] apex 0000:08:00.0: enabling device (0000 -> 0002)
[ 16.474447] apex 0000:08:00.0: Couldn't initialize interrupts: -22
[ 16.476806] apex 0000:09:00.0: enabling device (0000 -> 0002)
[ 16.480201] apex 0000:09:00.0: Couldn't initialize interrupts: -22
[ 16.482306] apex 0000:0a:00.0: enabling device (0000 -> 0002)
[ 16.488254] apex 0000:0a:00.0: Couldn't initialize interrupts: -22
[ 21.504640] apex 0000:09:00.0: Apex performance not throttled due to temperature
[ 21.504639] apex 0000:0a:00.0: Apex performance not throttled due to temperature
[ 21.504657] apex 0000:08:00.0: Apex performance not throttled due to temperature
[ 164.884046] apex 0000:0a:00.0: Couldn't reinit interrupts: -22
[ 164.885596] apex 0000:08:00.0: Couldn't reinit interrupts: -22
[ 164.889985] apex 0000:09:00.0: Couldn't reinit interrupts: -22
[ 196.858032] apex 0000:0a:00.0: Couldn't reinit interrupts: -22
[ 196.861839] apex 0000:08:00.0: Couldn't reinit interrupts: -22
[ 196.866137] apex 0000:09:00.0: Couldn't reinit interrupts: -22
[ 228.844407] apex 0000:0a:00.0: Couldn't reinit interrupts: -22
[ 228.848057] apex 0000:08:00.0: Couldn't reinit interrupts: -22
[ 228.852692] apex 0000:09:00.0: Couldn't reinit interrupts: -22
[ 260.899907] apex 0000:0a:00.0: Couldn't reinit interrupts: -22
[ 260.903764] apex 0000:08:00.0: Couldn't reinit interrupts: -22
[ 260.908369] apex 0000:09:00.0: Couldn't reinit interrupts: -22

ls -l /dev/apex*
crw-rw---- 1 root apex 120, 0 May 26 09:50 /dev/apex_0
crw-rw---- 1 root apex 120, 1 May 26 09:50 /dev/apex_1
crw-rw---- 1 root apex 120, 2 May 26 09:50 /dev/apex_2

lspci -nn | grep 089a
08:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]
09:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]
0a:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]

lsmod | grep apex
apex 28672 0
gasket 126976 1 apex

apt list apex
Listing... Done
golang-github-apex-log-dev/stable 1.1.1-3 all

apt list gasket
Listing... Error!
E: input:0-26: error: Expected pattern
gasket-dkms_1.0-18_all.deb
^^^^^^^^^^^^^^^^^^^^^^^^^^

frigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors

Hi,
I solved similar issue by doing this :
echo 1 > /sys/bus/pci/devices/0000:08:00.0/remove
echo 1 > /sys/bus/pci/rescan


[Adaptive Cards] [Is there any way to make multilingual adaptive card?]

[Your detailed feedback here]
I am utilizing rendering SDK. (Android, Java script, iOS)
I want to use multilingual adaptive card, but rendering SDK doesn't support multilingual adaptive card.
I think it is because a data json doesn't work in rendering SDK.
Is there any other way to provide multilingual?
Or do you have a plan to support data json in rendering SDK?

URL: https://adaptivecards.io/explorer/

You can use templating to get almost all of the way there (depending on your scenario) if you control the end-to-end solution. If not, we don't currently support localization but definitely should.

@jonmill If I use templating to support multilingual function, Is there any way to provide templating for android and ios? As I know, there is no templating SDK for android and ios. Is there any code to match and support templating in android and ios?

@jonmill Thanks for reply. Is there any sample code for support template in Android and iOS? Please provide if there is anything I can refer to for API development.

Mobile templating support is on our roadmap but not currently supported. Sorry about that, we know it is painful and hopefully we'll be able to provide support there soon.


[css/modules] composes fails when using multiple selectors

Describe the bug
composes does not work if you use multiple class selectors in the declaration that defines composes
Input code
.root-class {
    background-color: red;
}

.chain-1,
.chain-2 {
    composes: root-class;
}

.chain-1 {
    color: blue;
}

.chain-2 {
    color: green;
}

Config
No response
Playground link
No response
SWC Info output
No response
Expected behavior
{
  "root-class": [
    {
      "type": "local",
      "name": "__local__root-class"
    }
  ],
  "chain-1": [
    {
      "type": "local",
      "name": "__local__chain-1"
    },
    {
      "type": "local",
      "name": "__local__root-class"
    }
  ],
  "chain-2": [
    {
      "type": "local",
      "name": "__local__chain-2"
    },
    {
      "type": "local",
      "name": "__local__root-class"
    }
  ]
}

Actual behavior
{
  "root-class": [
    {
      "type": "local",
      "name": "__local__root-class"
    }
  ],
  "chain-1": [
    {
      "type": "local",
      "name": "__local__chain-1"
    },
  ],
  "chain-2": [
    {
      "type": "local",
      "name": "__local__chain-2"
    },
  ]
}

Version
main
Additional context
No response

failing test case added in https://github.com/swc-project/swc/pull/7949


CrashLoopBackoff on nginx-ingress-controller

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Create a cluster using RKE and either k8s version 1.13.12-rancher1-1 or 1.14.10-rancher1-0

Result:
After cluster appears active, see nginx-ingress-controller is stuck in Updating state. Logs show:
W0528 21:24:23.304871 6 flags.go:221] SSL certificate chain completion is disabled (--enable-ssl-chain-completion=false)

nginx version: openresty/<IP_ADDRESS>

W0528 21:24:23.313991 6 client_config.go:541] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.

I0528 21:24:23.314208 6 main.go:183] Creating API client for https://x.x.x.x:443

I0528 21:24:23.339979 6 main.go:227] Running in Kubernetes cluster version v1.13 (v1.13.12) - git (clean) commit a8b52209ee172232b6db7a6e0ce2adc77458829f - platform linux/amd64

I0528 21:24:23.342788 6 main.go:91] Validated ingress-nginx/default-http-backend as the default backend.

F0528 21:24:23.488016 6 ssl.go:379] unexpected error storing fake SSL Cert: could not create PEM certificate file /etc/ingress-controller/ssl/default-fake-certificate.pem: open /etc/ingress-controller/ssl/default-fake-certificate.pem: permission denied

Other details that may be helpful:

These failing versions use nginx-ingress-controller tag nginx-0.25.1-rancher1
Deploying a cluster using k8s version v1.15.12-rancher1-1 succeeds, which uses nginx-ingress-controller tag nginx-0.32.0-rancher1

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.2.13-rc1
Installation option (single install/HA): single

The bug still exists on v2.2.13-rc2, the same behavior in 1.13.12-rancher1-1 or 1.14.10-rancher1-0 cluster

Tested with v2.2.13-rc3.
Ingress controller -rancher/nginx-ingress-controller:nginx-0.25.1-rancher1 comes up successfully for both k8s versiona 1.13.12-rancher1-1  and 1.14.10-rancher1


pass performance param

According to API updates
https://dune.com/docs/api/api-reference/execute-query-id/

I have read the CLA Document and I hereby sign the CLA

@bh2smith

Passed "performance" param to init, cleaned up some mess with that param passing through
Implemented "latest result" endpoint (api doc)

So, if everything is ok, let's merge. And would be nice if you can push the new version to pypi so I can switch from custom git installation to pip.

So, if everything is ok, let's merge.

You wanna add some actual tests here? Or do you plan to follow up with some?

Release published: https://github.com/cowprotocol/dune-client/releases/tag/v1.1.1
Should be on pypi within the next few minutes.


Client-side pageviews

Hi, it doesn't appear that the capturePageViews config property actually results in page views being tracked on client-side navigations using the router.beforeEach hook in posthog.client.ts
Any idea why this would be? I've tried both not setting the config in nuxt.config as well as explicitly setting the value to true. For our site, we appear to get intiial SSR loads tracking, but not client-side routes thereafter.
Thanks for your help

Good catch, thanks! Should be fixed in the new release

Confirm fixed and working in our prod env. Thank you for the quick fix


AMBARI-23046. Remove unsecure dependencies from Ambari Groovy Client (amagyar)

What changes were proposed in this pull request?
same as #435 but for different branch
(Please fill in changes proposed in this fix)
#435

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/921/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/928/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/939/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/945/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/950/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/963/
Test FAILed.
Test FAILured.

groovy client was removed


copy of github.com/shankarapailoor/moonshine/trace2syz

for code review purposes
@shankarapailoor

@shankarapailoor I've left some comments.
The thing is pretty large, can it be split further into some logical parts? I don't yet understand whole code, but perhaps parsing strace output into some intermediate representation and then building syzkaller program from that representation. Will be much easier to understand and review that way.
Also I wonder if we can simplify the intermediate representation. For example, lower everything just to 3 types: pointer, scalar, array. I.e. lower all expressions to just a scalar right away, lower structs and arrays to just array, etc.

Thanks for the comments Dmitry. I apologize for the bad code overall :).

I don't yet understand whole code, but perhaps parsing strace output into some intermediate representation and then building syzkaller program from that representation.

I'm assuming you mean we should make this component 1 package within the current tool and not as a separate tool? If so, then I can do that.
I think the IR could be simplified and I will work on that.

I'm assuming you mean we should make this component 1 package within the current tool and not as a separate tool? If so, then I can do that.

Yes, just factor part of the logic into separate package with a clear interface.

This is now committed in another PR


Make use of vm_error in transaction receipts

Two blockchain PRs were recently merged that add more information about failed contract deploy transactions to the receipt. It would be great if the explorer could take this info and display it. (It may be the case that this field is already used and this new data will just show up, I haven't checked)

https://github.com/stacks-network/stacks-blockchain/pull/3593
https://github.com/stacks-network/stacks-blockchain/pull/3587

Note that these changes are not live in the released stacks-node yet, so this data will not be showing up yet. I just wanted to let you know it was coming soon.

Thanks, Brice, for the heads up. 🙏 We'll take a look at it when the API is ready

@matt It seems you may have been involved with this based on your comment https://github.com/stacks-network/stacks-core/pull/3587#issuecomment-1446355057
Is the API already using and sharing these more descriptive errors?


Remove/kill button

There was no objection from staff so this will be considered, I will allow a little longer to make sure there are still no objections.

Three people have objected to this change and we are now discussing how their concerns can be addressed.


请问 8x SR 需要多大的显存？目前 16G 的卡会 OOM

same problem
how to fix this problem

so far, i just load all of the model, the vram consumed 22Gb

How did you manage to launch it with 22GB vram consumption? I tried it with 24GB GPU but ran into OOM

How did you manage to launch it with 22GB vram consumption? I tried it with 24GB GPU but ran into OOM

Have you solved this problem? I ran into OOM too by using 24GB GPU

i use this model for daily upscaling work, and VRAM cost is around 27.47 GB, i will considering optimize this model later


feat: Refactor the dark-light theme from material ui to Tailwind CSS

Proposal:

We currently use the themes with Material Ui
Import Example:

 import { alpha, createTheme, lighten, darken } from "@mui/material";

[ ] Remove the Material UI Theme
[ ] Create the theme with the Tailwind

#9
Attention
This task should be pushed to the Next.js refactoring branch #16

At the moment it doesn't make sense for the project


The CTRL+WIN shortcut does not restore the W11 taskbar context menu

Not a critical issue, but it means that if Shell breaks (some config errors require Explorer restarts), the taskbar context menu is not accessible.

Have you tried the latest build?
This issue has been improved if Shell fails.  But the win+ctrl key issue will be fixed.

This issue has been fixed try this build
RIGHT-CLICK or SHEIFT + F10 and
CTRL + WIN Restore the default context menu of the taskbar.
CTRL  Re-apply shell settings.

I tested this; it appears to work mostly, however:

Using CTRL does not restore Shell's custom menu on the taskbar
Using CTRL in File Explorer does restore all Shell functionality as expected, except
Sometimes, the taskbar freezes for a period of time before the menu works again
I could crash explorer.exe by holding CTRL and spam-right-clicking File Explorer, then tried to right-click the taskbar.


Not able to install 1.0.1 on Nano S

I tried to update/install the new 1.0.1 on an Nano S
Ledger Live shows that has been successfully installed on the Device. But its not shown in the Device Menu.
Also when im closing/reopen Ledger Live, i able to install the App again.
No Error Message or something.

Tried with Ledger Live on Windows + Android, same behavior
	{
		"type": "cmd.START",
		"data": {
			"appOp": {
				"type": "install",
				"name": "Passwords"
			},
			"targetId": 823132164,
			"app": {
				"id": 7842,
				"name": "Passwords",
				"version": "1.0.1",
				"description": "",
				"dateModified": "2021-01-04T13:22:13.338795Z",
				"icon": "passwords",
				"authorName": null,
				"supportURL": null,
				"contactURL": null,
				"sourceURL": null,
				"compatibleWallets": [

				],
				"hash": "4344e7fc2fbb7ae696a9a2dafd3d171549ecbd6f56ffcf96b0ed9578ef2ede85",
				"perso": "perso_11",
				"firmware": "nanos/1.6.1-2/pwmgr/app_1.0.1",
				"firmware_key": "nanos/1.6.1-2/pwmgr/app_1.0.1_key",
				"delete": "nanos/1.6.1-2/pwmgr/app_1.0.1_del",
				"delete_key": "nanos/1.6.1-2/pwmgr/app_1.0.1_del_key",
				"dependencies": [

				],
				"bytes": 34824,
				"warning": null,
				"indexOfMarketCap": -1,
				"isDevTools": true
			},
			"deviceId": ""
		},
		"level": "info",
		"message": "CMD appOpExec.send()",
		"pname": "renderer",
		"timestamp": "2021-01-05T02:29:54.137Z"
    },,,
`

I just tried and had no issue, both on nano X/S.
There are some issues with the Ledger Live Manager, sometimes it instantly installs an app (but it actually doesn't), there's investigations on that. For the time being, keep trying until it works :unamused:

I just tried and had no issue, both on nano X/S.
There are some issues with the Ledger Live Manager, sometimes it instantly installs an app (but it actually doesn't), there's investigations on that. For the time being, keep trying until it works :unamused:


[Bug]: Ollama Host URL is outdated

What happened?
http://localhost:11434 does not work anymore
What was the expected functionality?
Needs to be http://<IP_ADDRESS>:11434 instead. Standard URL should be updated
Describe your environment
MacOS, Node 14.0.0, etc.
Relevant log output
No response
Relevant screenshots
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Closed. Is some IPV6 issue.


how to run

some demo, so I can figure it out what's doing

It’s not an application; the repo documents the open release of Carnegie Hall’s performance history data, and it’s structure and creation. Is there something specific you were trying to do? Perhaps take a look at the README, and then open a new issue with a specific problem or task you were hoping to accomplish.


[SUGGESTION] Use overcommit to manage git hooks and add git pre-hook to format the code.

In order to solve issues #493 and #471, I've added overcommit to manage git hooks and added a formatting pre-commit hook.
Overcommit is a tool to manage git hooks: https://github.com/brigade/overcommit
It depends on ruby and it is easy to install.
I've added a pre-commit script that checks if clang-format exists: if it doesn't exist, the tool will not let the contributor commit the changes.
If clang-format exists it will format the code and add the formatted code to current commit.
What do you think about?

Formatting changes where not added to commit.

Could you trigger a new check on travis build #784.7?

Codecov Report

Merging #495 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #495      +/-   ##
==========================================
+ Coverage   69.44%   69.46%   +0.01%
==========================================
  Files          49       49
  Lines        6854     6854
==========================================
+ Hits         4760     4761       +1
+ Misses       2094     2093       -1

Impacted Files
Coverage Δ

src/common/reactor.cc
80.48% <0%> (+0.4%)
:arrow_up:

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 43bdf4e...bf0ee55. Read the comment docs.


I can't get the mangarr backend container to work

Hello,
I tried to install mangarr but the mangarr backed container doesn't work.
I'm attaching my docker compose file and logs, can you help me?
I'm not a developer but I'd like to install it and use it to give you feedback 😊
docker-compose.txt
_mangarr.backend_logs.txt

It seems like it is unable to find the mongodb container which is kind of odd as it should be able to find it through the host name.
Are you using a tool like portainer? It isn't a great solution but you could try to find the mangarr.db container's ip address and fill that in as the value for the MONGO__HOST environment variable.
Another thing worth noting is that I'm currently doing a pretty hefty rewrite which will combine the frontend and backend into one, but of course feel free to try out the current version and leave feedback, that is very much appreciated :)

Thanks for your reply.
I'll wait for the project rewrite to install it because I really believe in the project.
I suggest you separate the extensions on a repository external to the application to avoid being in a situation like the Tachiyomi app...
I'll be happy to give you feedback once mangarr is installed :)

Thanks for the suggestion! I am indeed planning on separating it to avoid exactly that :)

@xavimaa I've published the combined version and have updated the example docker-compose.yml in the root of the repo. Feel free to try it!

Hi,
Thanks for your return.
I just tried setting the IP address to the MONGO__HOST environment variable but I got errors.

I actually think it comes from my configuration with Portainer. I will try to resolve this problem this weekend :)
_mangarr.stack_logs.txt

You should remove the http:// from MONGO__HOST. The actual connection string for connecting to the db will be turned into mongodb://username:password@host:port, so if your host starts with http:// then it'll be incorrect!

I've just tried it but I'm getting the same errors :/

Can you show your config and logs?

Hi! Thanks again for your help!
I think I know where the problem comes from.
I have this error with mongo: WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!
The Pentium J5040 cpu on my not-so-old NAS doesn't seem to support AVX instructions.
If you have a solution I'd love to hear from you :)
_mangarr.db_logs20240130.txt
_mangarr.stack_logs20240130.txt
docker-compose.txt

Hm. I can't guarantee that it'll work, but you could try changing the image tag from the mongodb container in your docker-compose file
from
image: mongo

to
image: mongo:4

I've just tried it, there are no more errors with mango in version 4 but I still get errors with mangarr.
Is it possible to offer an alternative database system in the future?
_mangarr.stack_logs20240131.txt

Is it possible to offer an alternative database system in the future?

It isn't to plan to support that, for now at least.

I've just tried it, there are no more errors with mango in version 4 but I still get errors with mangarr.

I suspect that the ip address you have filled in isn't correct, one thing I would recommend based on your last docker-compose, is replace the ip address for MONGO__HOST to mangarr.db
If you run into the same problem with the cache then you should change the value for REDIS__HOST to mangarr.cache


selection animation, detect tags automatically by delimiter, etc.

code style fixes, configured to work with SwiftLint;
animation of tag selection;
base class changed from UIView to UISCrollView and added maxHeight parameter - if tags height more than this value scrolling will appear;
detect automatically tags by specified delimiter + bool value to show/hide delimiter;
fixed sample application (need to be improved in the future);

@krezzoid Thank you for this incredible contribution! I'll take a look and I'll leave a review shortly.

@krezzoid Unfortunately, the test suite is failing:
❌  /Users/vagrant/git/WSTagsFieldTests/WSTagsFieldTests.swift:62:53: 'tagViews' is inaccessible due to 'fileprivate' protection level
        XCTAssert(tagsField.tags.count == tagsField.tagViews.count)

Could you take a look please?

@rafaeljegundo done ;)
btw, please take a look tests code coverage report - here is a lot of missed functions

@krezzoid Thanks! Yes, test coverage is pretty low :(

base class changed from UIView to UIScrollView and added maxHeight parameter - if tags height more than this value scrolling will appear;

@krezzoid UIScrollView is nice but I know that some users prefer to see all tags at once by extending the height. Maybe this should be an option: automatically increase/decrease the intrinsic height. What are your thoughts about it?

take a look:
open var maxHeight: CGFloat = CGFloat.infinity
this means that view will try to increase self size infinitely - for users who don't want to have scrolling


[occm]OpenStack endpoints can not be reinitialized automatically

/kind bug
What happened:
When the occm initializes OpenStack endpoint before OpenStack Service is ready, the endpoint may be initialized failed. But after the Service is ready,  occm can not reinitialize the endpoint automatically, which lead call API failed.
What you expected to happen:
The occm can have a mechanism to reinitialize endpoints when the Service status updates.
How to reproduce it:

Install occm
Install OpenStack Service
Call Openstack Service API

Anything else we need to know?:
None
Environment:

occm version: 1.25.5
OpenStack version: Walley
Others:

@dulek @kayrus @zetaab Hi, can you give some advice about this problem? thks.

@YuShangbin Hi, thanks for the issue. Unfortunately I don't understand the problem description.
What does "OpenStack Service is ready" mean? There is an endpoint in the token catalog, but the service doesn't respond?

call API failed

can you provide an example?
In any case, this issue seems to relate more to Gophercloud than to OCCM.
￼
￼
￼
￼
￼

@kayrus  For example, install occm and call LB API before install OpenStack Octavia Service, there is no LB endpoint in the catalog，occm will initialize LB client failed and then call LB API failed. Even install  Octavia Service later, occm can not intialize LB client again, so still call LB API failed.

If there is no LB endpoint, the OCCM must fail and exit. K8s must restart the failed pod until the catalog service endpoint is available. Let me know if this is not true.

The occm will fail and pass, but not exit.

@kayrus Thanks for your reply! If we need check if all OpenStack services in occm have this problem, and give a common resolution?


11.2.0-beta1 - XAML compiler error when using binding in style setter

Describe the bug
Using Avalonia v11.2.0-beta1 I get a compiler error AVLN1000 Avalonia: String '' was not recognized as a valid Boolean when using a binding as a style setter value.
This used to work in v11.1.3.
To Reproduce
Add style as shown below
        <Style Selector="Border.Test">
            <Setter Property="IsVisible">
                <Setter.Value>
                    <MultiBinding Converter="{x:Static BoolConverters.And}">
                        <Binding Path="Test"></Binding>
                        <Binding Path="Test1"></Binding>
                    </MultiBinding>
                </Setter.Value>
            </Setter>
        </Style>

Expected behavior
No compiler error should be thrown, binding should work
Avalonia version
11.2.0-beta1
OS
No response
Additional context
No response

This issue was introduced by PR #16153.
Possible ways to solve it can be:

Trim textValue before invoke XamlTransformHelpers.TryGetCorrectlyTypedValue at this line
Replace Boolean.Parse with Boolean.TryParse at this line of XamlX
Implement XamlAstTrivia and ingnore when xml:space is undefinited or default

my favorite is option 3 but it's probably the longest


Change the description editor for announcement to an activity feed editor that supports hashtag and mention.

Closing this as we will be replacing the current editor with a block editor.


Mac user

Hi, is there a mac version of this program please?

its python can be used anywhere
its a script just install python and requirements and use it

its python can be used anywhere
its a script just install python and requirements and use it

This is a python script, use the python intepreter


fix(@angular/cli): Use appropriate packageManager for linking

When creating a new project using the --link-cli option, the
linking command was hard-coded to use npm link @angular/cli.
This commit replicates the behaviour of npm-install where the
package manager is obtained from the global config and is then
used for linking.

I had some issues with the previous PR so I opened a new one (based on a separate branch)

I have refactored based on the latest commit.


Getting error in installation

can't install the requirements.txt file. That's all the error I'm getting --
error: subprocess-exited-with-error

  × Building wheel for numpy (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [1246 lines of output]

INFO: CCompilerOpt.cache_flush[817] : write cache to path -> /private/var/folders/rt/3jcw80yd5bbgq7_c89cf2sfr0000gn/T/pip-install-2uo0qkr7/numpy_aa84c7662faa46dd92edf70a8758acf0/build/temp.macosx-10.9-universal2-3.11/ccompiler_opt_cache_clib.py
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for numpy
Failed to build numpy
ERROR: Could not build wheels for numpy, which is required to install pyproject.toml-based projects

This is not related to the project, but rather your local environment. You are using python 3.11 and it seems that numpy might not be ready yet for the version you might be using. I have no issues locally using python 3.10.


'Publish to AWS' Failing - 'Unable to determine deploy tool version, no output was detected'

Describe the bug
After successfully connecting AWS Explorer to AWS using IAM credentials, the 'Publish to AWS' action results in an error with no obvious solution.
To Reproduce

Install latest AWS Toolkit version
Project is net7.0
AWS credentials are working and AWS explorer is populated with data

Expected behavior

'Publish to AWS' should open publish dialogue

Screenshots

Toolkit Logs
The logs show the following:
2023-10-16 13:04:30,999 [27] DEBUG Amazon.AWSToolkit.ToolkitFactory - Finished Registering Toolkit Plugins in the AWS Explorer...
2023-10-16 13:04:31,015 [1] DEBUG Amazon.AWSToolkit.VisualStudio.Lambda.LambdaTesterEventListener - Initializing Lambda Tester event listener
2023-10-16 13:04:31,031 [1] INFO  Amazon.AWSToolkit.ToolkitFactory - ToolkitFactory initialized
2023-10-16 13:04:31,031 [27] INFO  Amazon.AWSToolkit.ToolkitFactory - ToolkitFactory SignalShellInitializationComplete
2023-10-16 13:04:31,031 [26] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - AWSToolkitPackage InitializeAsync complete
2023-10-16 13:04:31,031 [11] INFO  Amazon.AWSToolkit.Utility - Running log cleanup
2023-10-16 13:04:31,358 [15] DEBUG Amazon.AWSToolkit.Telemetry.TelemetryService - Telemetry service enabled
2023-10-16 13:04:50,598 [42] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 8 event(s)
2023-10-16 13:04:51,123 [1] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - Received __VSSPROPID2.VSSPROPID_MainWindowVisibility property change, new value True
2023-10-16 13:04:51,123 [1] DEBUG Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - Toolkit considers VS to be initialized now
2023-10-16 13:04:53,401 [1] DEBUG Amazon.AWSToolkit.VisualStudio.Lambda.LambdaTesterEventListener - Registering Debugger events
2023-10-16 13:04:53,409 [1] DEBUG Amazon.AWSToolkit.VisualStudio.Lambda.LambdaTesterUtilities - Configuring Solution with Lambda Tester
2023-10-16 13:04:54,257 [1] ERROR Amazon.AWSToolkit.VisualStudio.Lambda.LambdaTesterUtilities - Error configuring Lambda Tester on project. FileName: , FullName: , UniqueName:
System.Exception: Unable to determine project FileName
at Amazon.AWSToolkit.VisualStudio.Lambda.LambdaTesterUtilities.d__2.MoveNext()
2023-10-16 13:04:54,265 [9] DEBUG Amazon.AWSToolkit.VisualStudio.Lambda.LambdaTesterUtilities - Finished configuring Solution with Lambda Tester
2023-10-16 13:05:06,044 [1] ERROR Amazon.AWSToolkit.Publish.Package.PublishToAws - Failed to open the Publish document
Amazon.AWSToolkit.Publish.DeployToolException: Unable to determine deploy tool version, no output was detected.
at Amazon.AWSToolkit.Publish.Install.GetCurrentCliVersion.ParseVersionFromCliOutput(String output)
at Amazon.AWSToolkit.Publish.Install.GetCurrentCliVersion.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Install.DeployCliInstaller.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Install.DeployCliInstaller.d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Install.DeployCliInstaller.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Install.DeployCli.d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Install.DeployCli.<>c__DisplayClass5_0.<g__Install|0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Telemetry.TelemetryLoggerExtensionMethods.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Install.DeployCli.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Install.DeployCli.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Package.PublishToAwsPackage.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Package.PublishToAws.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Package.PublishToAws.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Package.PublishToAws.<>c__DisplayClass7_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Amazon.AWSToolkit.Publish.Models.PublishDialogStepProcessor.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Package.PublishToAws.d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Package.PublishToAws.<>c__DisplayClass15_0.<g__Show|0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Telemetry.TelemetryLoggerExtensionMethods.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Package.PublishToAws.d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Package.PublishToAws.d__7.MoveNext()
Development System (please complete the following information):

Windows Version: 10.0.19045 Build 19045
Visual Studio Version: 17.7.4
AWS Toolkit for Visual Studio Version: <IP_ADDRESS>

I just updated Visual Studio from Version 117.7.5 and now 'Publish to AWS' is working. Seems like it may have been a VS bug.


fix: optimize BRC-20 activity count by ticker

Use tx_count from deploys table

:tada: This PR is included in version 2.1.1-beta.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Concepts + Anti-Scraping

Restructure Anti-scraping section
Move 3 concepts lessons into Anti-scraping
Migrate 2 Notion pages into Anti-scraping
Migrate 2 Notion pages into Concepts

View preview here


PWA and Dynamic Templates

Are there any special considerations (or examples) when it comes to using lit-html templates in the context of a PWA using Workbox? When using a index.html with only a root node that is populated dynamically at runtime with injected templates the typical SPA pattern no longer applies.
I suppose template functions in JS modules can just be cached by Workbox and used. Seems the only thing different is that now we use lit-html template functions instead of HTML pages or bloated framework components.
https://developers.google.com/web/tools/workbox

There should be no problem with templates and workbox. Workbox doesn't cache individual functions, it caches files.


Changed URL to label instead of clickable link

For Issue #65. Added color to differentiate from hyperlink.

thank you..


Fixed "VMs" relationship label on host summary screen

Reverted textual_vms method to build label & links in the same method, as human_attribute_name method on https://github.com/ManageIQ/manageiq/blob/master/app/helpers/textual_summary_helper.rb#L19 was causing incorrect label to be displayed.
https://bugzilla.redhat.com/show_bug.cgi?id=1270400
@matthewd  @dclarizio please review
before:

after:

FYI, we didn't need to go back quite that far -- there's an option to only override the label.
... though ultimately, I guess we should teach human_attribute_name better, so we don't have to avoid it.


Grammar and Phrasing Improvements in Inputs Section

Hello, my name is Isha Prajapati.
I noticed some small grammar and phrasing issues in the Inputs section of our documentation. Here are the changes I'd like to make:
Current: "How many random colors you want to be shown?"
Proposed: "How many random colors do you want to be shown?"
Current: "Select your desired start & end colors for the gradient"
Proposed: "Select your desired start & end colors for the gradient."
Current: "With how much time interval (in milliseconds) you want to change the colors randomly?"
Proposed: "With what time interval (in milliseconds) do you want to change the colors randomly?"
Current: "What type of view you want to choose (conic, linear or radial)?"
Proposed: "What type of view do you want to choose (conic, linear, or radial)?"
Current: "Countdown timer (in seconds)"
Proposed: "Set the countdown timer (in seconds)."

I'm eager to contribute under GSSOC'24 and would like to request the assignment of this task.
Thank you!

I've submitted a new pull request with the changes I've made. Please take a look and review it.
" Resolved Issues in the Inputs Section #1 "
Thank you!

I've submitted a new pull request with the changes I've made. Please take a look and review it. " Resolved Issues in the Inputs Section #1 " Thank you!

@Coding-whiz
Can you guide him @ishap11 ? She has sent a pull request in her forked repository.

Hi,
If it isn't urgent may I look into this after 10pm today?I am quite busy
right now.
Do let me know if it is urgent.
On Fri, 7 Jun 2024, 03:20 Sanu Kumar, @.***> wrote:

I've submitted a new pull request with the changes I've made. Please take
a look and review it. " Resolved Issues in the Inputs Section #1
https://github.com/sk66641/Random-Disco-Light-Simulator/issues/1 "
Thank you!
@Coding-whiz https://github.com/Coding-whiz
Can you guide him @ishap11 https://github.com/ishap11 ? She has sent a
pull request in her forked repository.
—
Reply to this email directly, view it on GitHub
https://github.com/sk66641/Random-Disco-Light-Simulator/issues/164#issuecomment-2153461644,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWOM42HQFUXWVZ6WWYW4ZPDZGDKQZAVCNFSM6AAAAABI2PEHFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJTGQ3DCNRUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi, If it isn't urgent may I look into this after 10pm today?I am quite busy right now. Do let me know if it is urgent.

ok

@ishap11
To know more about creating a pull request, you can checkout Learn.md

Thanks! I’ll check out the Learn.md file.

Hello @sk66641 and @Coding-whiz,
I noticed that the pull request for the README enhancements was closed but not merged. Could you please provide some feedback on what needs to be improved or why it wasn't merged?
I am eager to learn and make the necessary changes to contribute effectively.
Thank you for your guidance and support!

@ishap11
you have again created a PR in your forked repository! So, how can i merge it.

Thank you for reopening the issue. I've created a PR in the main repository for your review. Please let me know if any changes are needed.


Update com.sparkjava:spark-core to 2.7.2 or later

Due to security issues, com.sparkjava:spark-core should be updated to 2.7.2 or later.

closed with #34


remove spy-der strict version

In the original settings, spy-der  would be restored to an older version during installation, so I updated this pull request.

Thanks. LGTM.


Remove redundant export_alembic method.

Brief description
export_alembic method is not used anywhere anymore.

looks good to me based on the code as the function isn't applied into any scripts in the plugins folder.
Also tested with the code, it doesn't break anything too.

Was a bit confused since I thought we're definitely using a method from lib to export the alembics, but apparently the one used is called extract_alembic. So export_alembic should definitely be removed.

For what it's worth, the _get_mel_global() function in lib also appears to be unused?


Doc: minor records.config cleaning

Removes Fuzz options that left in ATS 7
Fixes parsing of proxy.config.hostdb.round_robin_max_count

[approve ci autest]

This seems to have already been back ported to 8.0.x. Bad Bryan! :)

The real commit hash is: 63c05aec6c7eb51a1e8c6c963af88ae10bb604c3


fix(dashboard): calculate lru_evicted_watermark_time_diff_ms in promsql

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

calculate the diff between current watermark and evicted watermark in promsql instead of RW.

Close #12293

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.


update lcobucci/jwt dependency to ^4.0

Could you put both major versions? We probably support both :) .

Could you put both major versions? We probably support both :) .

Happy to do so.

Happy to do so.

Ah, I just realized you did this PR on acmephp/core! Sorry, but could you open it on https://github.com/acmephp/acmephp ? This repository is a read-only subtree split.

Ah, I just realized you did this PR on acmephp/core! Sorry, but could you open it on https://github.com/acmephp/acmephp ? This repository is a read-only subtree split.

Thanks @tgalopin -- new PR located at https://github.com/acmephp/acmephp/pull/224

Thanks @tgalopin -- new PR located at https://github.com/acmephp/acmephp/pull/224


redesigned icon, provided svg icon(not yet implemented)

I just thought the squared off icon looked kind of ugly, so I made a rounded one as an svg and png. Currently, only the png is implemented, but the svg is now also located in the assets/ folder.

You could possibly provide the icons by placing them in a folder like /usr/share/pixmaps and then updating the deezer-enhanced.desktop file with the matching icon (i.e round, square, or any other formfactor you like).

I am now implementing a new checkbox in the settings page to use the rounded icon, but I can't figure out where the text for the entries and descriptions is styled, so it currently looks like this:

Also, would any modifications to the install be necessary to also provide the round icon (to /usr/shar/icons/hicolor/XxX/apps)?

I was thinking of implementing this feature in the install script only as otherwise you need to ask for sudo privileges, which doesn't seem nice. Also, it's unnecessary to store multiple icons, if you only use one set anyways. But you may know better than me, I'm not much of an icons user.
Changing the desktop file means, that the icon in the title bar (not sure) will stay the same, as well as the tray icon. Which you may, or may not be interested in changing, otherwise I think it's good solution.
Yes, I think it's necessary to provide icons to /usr/shar/icons/hicolor/XxX/apps but I'm not 100 % sure, so see for yourself.

Also, if you anyways decide to implement this into the settings, do not worry about all the labels and so on, I can later implement it myself once rest of the functionality is fine.

Don't worry about the conflicts, I can resolve them myself later, just moved a few files.

I think I have a finalized version now, I work around needing root access by copying the dektop file to .local/share/applications and wget the round icon to .local/share/icons/... if needed. If the user wants to change icons, I simply update deezer-enhanced.desktop using sed.
I added sed and wget as dependencies in the PKGBUILD files, if dependencies need to be specified in any other places, than that still needs to be done.
Apart from that, I hope I accounted for most scenarios (at least the ones I could test).

Hey, this solution looks really crazy, I'll still have to consider how most apps do it and whether there isn't any better, cleaner solution that slipped our minds. Nevertheless, hopefully this feature will get merged one way or the other by the end of this week.

Alright, so after taking a closer look onto how exactly does it work and testing it myself, I don't think this is something we really wanna do, also it looks like a nightmare to debug. Most apps just provide some default icon and that's it, I would prefer to stick to this and leave the icon as it is.
On the other hand, the app uses tray and the tray icon can't be switched as easily as the desktop icon, that means the priority should be to use the desktop icon as tray icon, which honestly I'm not sure whether electron supports.
Sadly, all of this means I will have to close this PR, although I'm open to creating a new repo that would contain alternative icons and an install script if that's suitable.

Nevermind, once again I was wrong! You can now easily change the tray icon, it's located in /opt/Deezer Enhanced/resources/assets/icon.png which is not the best location, but it works. Check out the dev branch.


XML Feed is not parsed

Cool website ! Just found out that  https://christopheradams.io/feed.xml

can you say more?

Yes, sorry :) I think the feed is served properly but there is no XML parser so you end up with a markdown feed, which is not valid XML (see the pic).

Adding this file to the main rep will give you a valid XML for syndication https://github.com/clemsos/clemsos.github.io/blob/master/feed.xml

The feed is generated automatically by the jekyll-feed gem. It adds a stylesheet https://christopheradams.io/feed.xslt.xml which makes the feed look that way (at least in Chrome). The XML is valid.

arf ! sorry for the noise :) I didn't know about any XLST parsing in the browser... thought it was supposed to display plain XML and it was Mardown. Anyway, cool wesbite ! cheers

Thanks!


Is this great tool currently executable?

This tool is exactly what I need. Especially as it allows custom TMS services as a map.
Unfortunately it doesn't seem to work anymore. I tried to run it on Windows 10 with Docker but I always get the following error message.
2024-05-30 19:05:47,080 -- Reading GPX file /videos/GX010054.gpx 2024-05-30 19:05:47,084 -- Cleaning GPX file /videos/GX010054.gpx 2024-05-30 19:05:47,088 -- Duration /videos/GX010054.gpx : 0:00:10.260000 2024-05-30 19:05:47,088 -- Concatenating all GPX files Traceback (most recent call last):   File "/src/gopro-map-sync/gpxmapmovie", line 351, in <module>     main()   File "/src/gopro-map-sync/gpxmapmovie", line 321, in main     if arg.startswith('--') and pass_args[0] and not pass_args[0].startswith('--'): IndexError: list index out of range
Camera is GoPro 9 Black with latest firmware.
Is there still a chance to get the tool running?

Investigating.

@4tler, can you show me the exact and full command line that you ran to get this error?

2024-05-30 21:30:23,634 -- Reading GPX file /videos/GX010053.gpx
2024-05-30 21:30:23,701 -- Cleaning GPX file /videos/GX010053.gpx
2024-05-30 21:30:23,999 -- Duration /videos/GX010053.gpx : 0:13:11.810000
2024-05-30 21:30:23,999 -- Concatenating all GPX files
Traceback (most recent call last):
  File "/src/gopro-map-sync/gpxmapmovie", line 351, in <module>
    main()
  File "/src/gopro-map-sync/gpxmapmovie", line 321, in main
    if arg.startswith('--') and pass_args[0] and not pass_args[0].startswith('--'):
IndexError: list index out of range```

The first thing I'm wondering is why you're getting that error on line 321 when this line of code actually near line 360. Are you running the latest version of the code, @4tler?

Also, looking at your command line, there seems to be an info that shouldn't be there?

I use the docker image under windows with the help of docker dektop. The image is as described here in Git: thomergil/gpxmapmovie:latest

Perhaps you meant --debug info and you removed the --debug but not the info?

ok, i got this with the right command:
docker run --mount="type=bind,source=C:/Users/David/Downloads/videos,target=/videos/" thomergil/gpxmapmovie  --input=/videos/GX010053.MP4 --output=/videos/GX010053.mp4 --debug info
2024-05-30 21:46:15,256 -- Cleaning GPX file /videos/GX010053.gpx
2024-05-30 21:46:15,543 -- Duration /videos/GX010053.gpx : 0:13:11.810000
2024-05-30 21:46:15,543 -- Concatenating all GPX files
2024-05-30 21:46:15,606 -- java -jar /src/gpx-animator-1.6/build/libs/gpx-animator-1.6.0-all.jar --output=/videos/GX010053.mp4 --debug info --input /tmp/tmpdqfwbtfz --total-time 791770
21:46:16.055 [main] ERROR app.gpx_animator.Main - unrecognised option '--output=/videos/GX010053.mp4'
run program with --help option to print help```

Documentation tells you to leave out the = :)

thats true ... here the right comand if someone will need it someday:
docker run --mount="type=bind,source=C:/Users/David/Downloads/videos,target=/videos/" thomergil/gpxmapmovie  --input /videos/GX010053.MP4 --output /videos/GX010053_map.MP4
Thank you very much for the support.

Excellent. I will improve the output of the command to make it more clear what the problem is.

I will be working intensively with the tool over the next few days. If I have any additions for the readme, I can add them if that's ok. Maybe there will also be a small Windows HowTo.


Search not in the Center

Describe the bug
Search bar is not in the middle of screen and move to the left when hiding the title
Steps To Reproduce
Steps to reproduce the behavior:
1.settings
2.remove title
Expected behavior
for the search bar to be in the cetner
Screenshots

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings):0.30.2
PHP Version:7.2.24
Hosting Method (Nginx/Apache/Docker): Nginx

Additional context
I have custom banner image and custom title

Thanks for raising @Zyzto.
I've just committed 4f96cd91648a4f50aa691d7c26c1fd09f66838e6 which should keep the search bar centered until it's pressured to move out by right or left elements. This will be part of the next feature release.


nginx-controller chart should support dnsPolicy

I figure this is a simple change, and I found it necessary today.
Pod dnsPolicy is not defined in the Deployment/Daemonset templates, so they default to ClusterFirst. As per k8s docs, Pods running with hostNetwork: true need to specify dnsPolicy: ClusterFirstWithHostNet if they wish to use the cluster internal DNS. Otherwise, the containers won't be able to resolve service and pod names inside the cluster.
In my case, I'm using a slightly modified nginx.tmpl to configure nginx's log_format. I need to send access_logs to a Graylog service. Graylog pods and services are also inside Kubernetes, so my nginx instances need to resolve the service name to reach them.
The modification to the chart is quite simple:
values.yaml
  # Optionally use this DNS Policy if you have 'hostNetwork: true'
  # Without this, pods running with host network access will not be able to resolve names in K8S' internal DNS
  #dnsPolicy: ClusterFirstWithHostNet

controller-deployment.yaml and controller-daemonset.yaml
spec:
  template:
    spec:
      dnsPolicy: {{ .Values.controller.dnsPolicy | default "ClusterFirst" }}

Hope this can make it to a future release.
Kind regards.

PR approved. Closing this issue.


Use more precise parse-backticks selectors on isSingleFile

Fix #3385
This is caused by
https://github.com/sindresorhus/refined-github/blob/a82f849bd4a745542642b9453c12a6ec18c381aa/source/features/parse-backticks.tsx#L31
After fixing:

To prevent possible problems, I updated another selector which uses .repository-content .js-details-container as well.

🤦♂ Am I clicking too hard? #3391


ORC-231 Configurable capability to overwrite the file if it exists.

Added a boolean flag to configure the overwrite behavior. This change is backward compatible as the default value of the flag is false.

I undid the inadvertent change to the import lines. Please configure your IDE to not introduce wildcard imports for this project.


Create a script to build, test and publish the NodeJS client

To make RedisLess easily testable by any NodeJS developer, it would be useful to have a script to build, test and deploy the NodeJS client. Any suggestion is appreciated.

Stumbled upon this: https://dev.to/kennethlarsen/how-to-distribute-a-rust-binary-on-npm-75n

use this CI template to publish binary releases for Linux, macOS and Windows
install.js looks something like:

let exec = require('child_process').exec;

exec('curl -LSfs https://japaric.github.io/trust/install.sh | \
sh -s -- --git qovery/redisless', (error, stdout, stderr) => {
  console.log(stderr);
});

node install.js

Is this close enough to what you had in mind?

I don't think we need something like that. We already have everything we need. We just need to spend some time to automatically build and publish on NPM with Github actions. I will probably spend some time on this task once I have finished what I am working on - RedisLess cluster support


Report coverage from cypress tests

FUP of https://github.com/opendatahub-io/elyra/pull/89

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 86.68%. Comparing base (37b0487) to head (3583a28).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #92      +/-   ##
==========================================
+ Coverage   85.63%   86.68%   +1.04%
==========================================
  Files          90       84       -6
  Lines       14784    14290     -494
  Branches      103        0     -103
==========================================
- Hits        12661    12387     -274
+ Misses       2123     1903     -220

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Is there a reason why there are functional code changes as part of this PR for the code coverage reports addition? :thinking:

Yeah, for me it's a code change that should not be part of that PR or at least not the same commit :grinning:

I liked that it was a self-test for the coverage reporting.

technically... GH doesn't have to be around in the future, sooo... and for us who aren't used to go to GH for this kind of changes... anyway, yeah... we don't need to be that much strict, I agree... we're not flying to Mars anyway...


Fixed crashes with newest Symfony

Fix of issue #27

Hey @imerzlyakov, can you merge this PR ASAP! thanks


CB-11170 EDH integration to measure how many customers used Data Hub repair

CB-11170 EDH integration to measure how many customers used Data Hub repair

New flows are introduced for flow chain init and flow chain finish
To identify the repair start / finish steps, the repair flowchain is extended with these new flows
The type of the flow chains will follow the following pattern flowchain1/flowchain2/flowchain3/flow in the flowlog table
ClusterUseCaseMapper will make decision about the mapping based on the root flowchain
report will be sent about repair flows
Distrox upgrade will be reported as an upgrade report and a separated repair report

Retest this please


react-native-wheel-picker出现这个Unexpected reserved type number

import PropTypes from 'prop-types';
try

这是引用的第三包里面源码编译时报的错，无法修改源码

已经有添加了

react-native 外部是多少

"react": "16.8.6",
"react-native": "0.59.0",
"react-native-loading-spinner-overlay": "^1.0.1",
"react-native-picker": "^4.3.7",
"react-native-root-toast": "^3.1.2",
"react-native-scrollable-tab-view": "0.10.0",
"react-native-tab-navigator": "^0.3.4",
"react-native-wheel-picker": "^1.2.0",
"react-navigation": "2.11.2",
"react-navigation-redux-helpers": "^2.0.8",
"react-redux": "^5.1.0",
"redux": "^4.0.1",
"redux-actions": "^2.6.3",
"redux-logger": "^3.0.6",
"redux-thunk": "^2.3.0",
"rxjs": "^6.3.3"
react-native -v
react-native-cli: 2.0.1

\tuyasmart-home>react-native -v
react-native-cli: 2.0.1
react-native: 0.59.0

try

I changed picker. You're trying


feature: 'stable' git tag for cloning

Did you check the docs?

[X] I have read all the lazy docs

Is your feature request related to a problem? Please describe.
If we simply clone using the provided instructions in the readme/docs we will get HEAD, which may be in a broken state (thinking of the issue the other day with the cache bug that broke some things for a couple hours - thanks for fixing things so quickly btw!).
Describe the solution you'd like
I have my config.defaults.version = "*" but this won't apply on first git clone of the lazy.nvim repo. Something like this by default might be better, for the bootstrapping part:
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    'git',
    'clone',
    '--filter=blob:none',
    '--single-branch',
   '--branch=stable',
    'https://github.com/folke/lazy.nvim.git',
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

Or however you want to do it!
Describe alternatives you've considered
Added config.defaults.version = "*" but this isn't applied on first clone (when lazy isn't installed). I could manually add --branch to my clone but I'd have to specify exact version and it's not always going to point to the latest release.
Additional context
Nothing else, thanks for the great work and incredibly fast fixes!

That's a good point.

See the install instructions for the new bootstrap code that now always points to stable: https://github.com/folke/lazy.nvim/tree/stable#-installation


How to overwrite a Module?

Love this repo, I believe using these tools provide a far superior approach to writing easily manageable tests.
In exploring a simple way of setting up unit and e2e tests, I'm hoping to load in my main AppModule (with all of it's modules which include logging, sdk interfaces, axios api interfaces, ect) and then overwrite the ones specific to the test suite.  Was hoping there was a way to simply overwrite an entire module (as opposed to a service).  I'm not quite sure how to interpret the README and the source code on how to accomplish this.
Here is an example:
Replace TypeOrmModule with Testing configuration TypeOrmModule
I'de like to initialize an application instance in my test suite using the ApplicationInstanceBuilder, then pass in a custom NestApplicationBuilder class.  This class contains the definitions for modules I would like to potentially overwrite.  In this case, I have a TypeORM in-memory configuration which let's my tests run against a fresh copy of the database without needing to mock data or use a database/container.
Here is my main application module:
import { Module, CacheModule, Logger } from '@nestjs/common'
import { GraphQLModule } from '@nestjs/graphql'
import { TypeOrmModule } from '@nestjs/typeorm'
import { ApolloFederationDriver, ApolloFederationDriverConfig } from '@nestjs/apollo'
import { dotenvLoader, TypedConfigModule } from 'nest-typed-config'
import { Config } from '_common/config'
import { GQL_API_A_Module, GQL_API_B_Module, GQL_API_A_Module, GQL_API_B_Module } from "_common/modules"
import { Module, CacheModule, Logger } from '@nestjs/common'
import DataSource, { InjectedTypeOrmModuleOptions } from './ormconfig'

@Module({
  imports: [
    TypedConfigModule.forRoot({ isGlobal: true, schema: Config, load: dotenvLoader()}),
    TypeOrmModule.forRoot(InjectedTypeOrmModuleOptions), // <-- Using Real Database configs normally
    GraphQLModule.forRootAsync<ApolloFederationDriverConfig>({
      driver: ApolloFederationDriver,
      inject: [Config],
      useFactory: graphQLModuleInitFactory
    }),
    CacheModule.register({ isGlobal: true }),
    REST_API_A_Module,
    REST_API_B_Module,
    GQL_API_A_Module,
    GQL_API_B_Module,
    UsersModule
  ],
  controllers: [],
  providers: [Logger]
})
export class AppModule {}

The above is the module that gets used in creating the Nest App in main.ts await NestFactory.create(AppModule) when running the API in real environments.
Now, I have made a utility, TestNestApplicationBuilder, which is to be using in my tests to define any customizations I need to make to the application in the jest testing before configurations.. here is what I have done so far per the README typeORM configuration example:
import { NestApplicationBuilder, ITestModuleBuilder } from '@jbiskur/nestjs-test-utilities'
import { TypeOrmModule } from '@nestjs/typeorm'
import TestingDataSource, { InjectedTypeOrmModuleOptions } from '../src/testingOrmconfig'

export default class TestNestApplicationBuilder extends NestApplicationBuilder {
  withMemoryTypeORMConnection(): this {
    this.withTestModule((builder: ITestModuleBuilder) =>
      builder.withModule(
        TypeOrmModule.forRootAsync({
          useFactory: () => InjectedTypeOrmModuleOptions,
          dataSourceFactory: async () => TestingDataSource // <- `pg-mem` TypeORM instance
        })
      )
    )
    return this
  }
}

And I interface with it in my .spec.ts tests like so:
import { ApplicationInstance, ApplicationInstanceBuilder } from '@jbiskur/nestjs-test-utilities'
import { AppModule } from 'app.module'
import TestNestApplicationBuilder from '../../test/TestNestApplicationBuilder'
import { UsersService } from './users/users.service'

describe('Users', () => {
  let usersService
  beforeEach(async () => {
    const built = await new ApplicationInstanceBuilder(
      new TestNestApplicationBuilder()
        .withTestModule((builder) => builder.withModule(AppModule))
        .withMemoryTypeORMConnection()
    ).build()
    const module = built.instance
    const usersService = module.get<UsersService>(UsersService)
  })
})

The Problem
Here, we have a withMemoryTypeORMConnection which will insert my in-memory TypeORM module into the testing app instance.. and it works fine.  However, it collides with the real TypeORM module in AppModule.
======================
So my question is, how do I use withOverrideProvider to overwrite the AppModule's TypeOrmModule with my Testing TypeOrmModule?  Would greatly appreciate the help

Hi, thanks for the interest in the repo :) I have looked at the testing module to find a way to override a module. I think I have found a way to do that (I only tested with simple modules, not dynamic, but if it uses metadata the same as simple modules, it should work).
I added a new release v3.12.1 that has this overrideModule method in the module builder (added it to the readme, but I will include the snippet here).
//...
        app = await new NestApplicationBuilder()
        .withTestModule((builder) => builder.withModule(TestModuleA))
         overrideModule(TestModuleA, ModuleToOverride, MockedModule)
        .build();
//...

Hope this helps :)

@jbiskur absolutely amazing.  Thank you 100%
Here is how I changed my code for those who read this:
TestNestApplicationBuilder.ts
import { NestApplicationBuilder, ITestModuleBuilder } from '@jbiskur/nestjs-test-utilities'
import { TypeOrmModule } from '@nestjs/typeorm'
import TestingDataSource, { InjectedTypeOrmModuleOptions } from '../src/testingOrmconfig'
import { AppModule } from '../src/app.module'

export default class TestNestApplicationBuilder extends NestApplicationBuilder {
  constructor() {
    super()
    this.withTestModule((builder) => builder.withModule(AppModule)) <-- always inject AppModule
  }
  withMemoryTypeORMConnection(): this {
    this.overrideModule(
      AppModule,
      TypeOrmModule,
      TypeOrmModule.forRootAsync({
        useFactory: () => InjectedTypeOrmModuleOptions,
        dataSourceFactory: async () => TestingDataSource()
      })
    )
    return this
  }
}

and then in my test:
import { ApplicationInstance, ApplicationInstanceBuilder } from '@jbiskur/nestjs-test-utilities'
import TestNestApplicationBuilder from '../../test/TestNestApplicationBuilder'
import { UsersService } from './users/users.service'

describe('Users', () => {
  let usersService
  beforeEach(async () => {
    const built = await new ApplicationInstanceBuilder(
      new TestNestApplicationBuilder().withMemoryTypeORMConnection()
    ).build()
    const module = built.instance
    const usersService = module.get<UsersService>(UsersService)
  })
})

I think this is a super clean approach.. Thanks for implementing this 🚀

@jbuskur actually.. I don't think the DynamicModules work with the new overrideModule.. I must have missed the false success from a patch job I made in my app when breaking things...
Here is what I discovered:
In module.builder.js:
overrideModule(testModule, target, nestModule) {
    const index = this.imports.findIndex((m) => {
        return m["name"] === (_.isString(testModule) ? testModule : testModule.name);
    });
    if (index > -1) {
        const module = this.imports[index];
        const imports = Reflect.getMetadata("imports", module);
        console.log(imports); // <-- HERE_A
        const targetIndex = imports.findIndex((m) => {
           console.log(m, m["name"], target.name); // <-- HERE_B
           return m["name"] === target.name
        });
        if (targetIndex > -1) {
            Reflect.defineMetadata("imports", [...imports.slice(0, targetIndex), nestModule, ...imports.slice(targetIndex + 1)], module);
        }
        console.log(targetIndex, this.imports[targetIndex]); <-- HERE_C
    }
    return this;
}

I added a few lines for debugging and noticed that for all of the modules that I have .forRoot or .forRootAsync.. or .register -- the module name property doesn't exist, so the targetIndex is -1
Per the AppConfig in the example I pasted above.. the output at log HERE_A looks like this:
[
  {
    global: true,
    module: [class TypedConfigModule],
    providers: [ [Object] ],
    exports: [ [Object] ]
  },
  { module: [class TypeOrmModule], imports: [ [Object] ] },
  {
    module: [class GraphQLModule] { logger: [Logger] },
    imports: undefined,
    providers: [ [Object], [Object], [Object] ]
  },
  {
    global: true,
    module: [class CacheModule extends InternalModuleClass],
    providers: [ [Object] ]
  },
  [class REST_API_A_Module],
  [class REST_API_B_Module],
  [class GQL_API_A_Module],
  [class GQL_API_B_Module],
  [class UsersModule]
]

Without digging too deep.. looks like the class modules have names, but not the others.  I'm going to poke around inside these modules to see if there is a neat way to loop through the inner module property of the dynamic modules to get a handle on the name property

Yea - looks like this change does it:
const targetIndex = imports.findIndex((m) => {
  if (typeof m === "function") {
    return m["name"] === target.name
  } else if (typeof m === "object") {
    const innerModule = m.module
    return innerModule["name"] === target.name
  } else {
    // NOT SUPPORTED
    return false
  }
});

I'll make an MR -- would appreciate an 👁 or 👀  when you have some time!

Well, it works but it doesn't work.. I'm wondering if there is something deeper within the module that isn't getting overwritten?  I'm getting an error that I have duplicates in my Schema which is an error message I would get if I tried to add two TypeOrmModules with the same entities

Awesome, thanks for your contribution 😎

@jbiskur do you mind publishing a new version to registry?  Getting ready for a release of this into my service, would like to point to your package

@bneigher, yea, I released a new version. Sorry about the delay :)


OCL12AdapterPass

This is a port of the OpenCL 1.2 adapter pass from the AMD HSAIL compiler.
The pass is invoked by the FE before linking with the builtins library. The library only contains opencl 2.0 builtins. Pass creates a body for each encountered opencl 1.2 builtin that wraps around the according opencl 2.0 builtin call.

Mistakenly created