text:
Api changes

My proposed changes to the safetyNet API.
Changing the types of safetyNetItem from: situationControl, relaxation, pet, other
to: friends, sport, pet, other, music, personality

Just as a comment, please use meaningful commit messages, so that the other students can easily get what the changes are about. Thanks!
Sorry! Will look out for that in the future. I changed the PR description to properly explain what I changed.

Perhaps I missed out on some of the design discussions but although situationcontrol and relaxation are motivators they can still be part of the safetynet right?

By the proposed change, only the items listed in the enumeration could be part of the safetynet (there is still the other option).

I merged this with the new structure of the specification. @JonahBalshai @redstarmy I ended up inserting all mentioned options within the enum. If you agreed on reducing the number of possible items, feel free to remove unnecessary fields again.

Thanks a lot! I think maybe we'll merge two fields according to the discussion I had on mattermost. Should I create a new PR for that or can I just do it by myself?

I merged this with the new structure of the specification. @JonahBalshai @redstarmy I ended up inserting all mentioned options within the enum. If you agreed on reducing the number of possible items, feel free to remove unnecessary fields again.

Thanks a lot! I think maybe we'll merge two fields according to the discussion I had on mattermost. Should I create a new PR for that or can I just do it by myself?

Please create a PR, so all frontend teams can agree on you proposed merge (or any other changes). @kopfsachen-dev/backend really does not care about what is stored in the safety net :)

I merged this with the new structure of the specification. @JonahBalshai @redstarmy I ended up inserting all mentioned options within the enum. If you agreed on reducing the number of possible items, feel free to remove unnecessary fields again.

Thanks a lot! I think maybe we'll merge two fields according to the discussion I had on mattermost. Should I create a new PR for that or can I just do it by myself?

Please create a PR, so all frontend teams can agree on you proposed merge (or any other changes). @kopfsachen-dev/backend really does not care about what is stored in the safety net :)

Will do :)

authors: JonahBalshai jgraeger

repo: kopfsachen-dev/api


text:
Document stackable tilemap

https://docs.korge.org/views/tile-maps/

Documented here: https://docs.korge.org/views/tile-maps/

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
feat: add deploy script to install the required operators and resources on OpenShift

This PR adds deploy.sh inside hack/openshift. The script makes it easy to debug and maintain the required steps for Korrel8r to work.
This doesn't change the way initially implemented steps were present in Makefile

@vprashar2929 this looks like a  nice improvement, thanks! I agree in this case the Makefile targets are too complex, a script is better. Also I like the use of Templates.  I need to test it a bit, I'll ask questions here if I have any, and merge if all is well.

Sure no worries Alan.😊 Feel free to test it out and let me know if I missed something

source: gharchive/pull-request


text:
feat: add core-dns

What type of PR is this?

/kind feature
What does this PR do?

Which issue(s) does this PR fix?

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

/lgtm
/approve

authors: OrangeBao duanmengkk

repo: kosmos-io/kosmos


text:
Widget can't be destroyed

We are using bdp in a SPA, and need to destroy the whole widget (including both dom and events) when the outer component is destroyed. Unfortunately I don't find such a method. Is it possible to add one? Thanks!

hey @shijistar ,
thank you for the suggestion. I added destroy() method to new version 2.1.3

authors: koss-lebedev shijistar

repo: koss-lebedev/bootstrap-duration-picker

license: mit

license_source: bigquery


text:
Having more than 100 results from a "search"

Hi,
I'm trying to gather all the results around a specific topic, I cannot get more than 100 results.
Can it be changed ?
Cheers

@ellitosprint
Let me quote @kotartemiy :
"100 links per search are the max capacity. The only way to increase your results is to make it day-by-day. So, 100 links per day are your maximum capacity".
This is a Google constraint.

make a function that returns the searches and then call it in a for loop. It'll be 100*(whatever number you decide to put in the for loop)

authors: AlexYurkin OpulentOnyx ellitosprint

repo: kotartemiy/pygooglenews


text:
Cannot run program ruff-lsp - is not a valid Win32 application

Describe the bug
I don't get ruff linter hints in PyCharm 2024.1.1.
I'm running PyCharm 2024.1.1 + ruff-pycharm-plugin 0.0.33 on Windows 11 but my python project is inside WSL.
I've also installed ruff and ruff-lsp inside WSL. I can't get linter hints in my IDE. On the lower right of the IDE under "Language Services" I see "{} Ruff" with a red exclamation mark. It says "Ruff | Termianted". When I check the log it says CreateProcess error=193, %1 is not a valid Win32 application.
2024-05-22 11:49:09,031 [  18080] SEVERE - #c.i.d.PerformanceWatcherImpl - PyCharm 2024.1.1  Build #PY-241.15989.155
2024-05-22 11:49:09,031 [  18080] SEVERE - #c.i.d.PerformanceWatcherImpl - JDK: 17.0.10; VM: OpenJDK 64-Bit Server VM; Vendor: JetBrains s.r.o.
2024-05-22 11:49:09,031 [  18080] SEVERE - #c.i.d.PerformanceWatcherImpl - OS: Windows 11
2024-05-22 11:49:09,031 [  18080] SEVERE - #c.i.d.PerformanceWatcherImpl - Last Action:
2024-05-22 11:49:09,103 [  18152]   INFO - #c.i.u.i.UnindexedFilesScanner - Scanning of fs2d-analytics uses 19 scanning threads
2024-05-22 11:49:09,244 [  18293]   INFO - #c.i.d.u.SqlDialects - SQL dialects initialized in 54 ms
2024-05-22 11:49:09,264 [  18313]   INFO - #c.i.w.i.i.EntitiesOrphanageImpl - Update orphanage. 0 modules added
2024-05-22 11:49:09,264 [  18313]   INFO - #c.i.w.i.i.WorkspaceModelImpl - Project model updated to version 3 in 0 ms: Sync global entities with project: fs2d-analytics
2024-05-22 11:49:09,264 [  18313]   INFO - #c.i.w.i.i.GlobalWorkspaceModel - Global model updated to version 2 in 0 ms: Sync global entities with state
2024-05-22 11:49:09,415 [  18464]   INFO - #c.i.p.l.i.LspServerImpl - RuffLspServerDescriptor@fs2d-analytics(Initializing;0): Starting LSP server
2024-05-22 11:49:09,425 [  18474]   INFO - #c.i.p.l.a.LspServerDescriptor - RuffLspServerDescriptor@fs2d-analytics: starting LSP server: \\wsl.localhost\Ubuntu-20.04\home\michael\.pyenv\shims\ruff-lsp []
2024-05-22 11:49:09,435 [  18484]   WARN - #c.i.p.l.i.LspServerImpl - RuffLspServerDescriptor@fs2d-analytics(Initializing;0): Failed to start LSP server
com.intellij.execution.process.ProcessNotCreatedException: Cannot run program "\\wsl.localhost\Ubuntu-20.04\home\michael\.pyenv\shims\ruff-lsp": CreateProcess error=193, %1 is not a valid Win32 application
	at com.intellij.execution.configurations.GeneralCommandLine.createProcess(GeneralCommandLine.java:367)
	at com.intellij.execution.process.OSProcessHandler.startProcess(OSProcessHandler.java:86)
	at com.intellij.execution.process.OSProcessHandler.<init>(OSProcessHandler.java:46)
	at com.intellij.platform.lsp.api.LspServerDescriptor$startServerProcess$1.<init>(LspServerDescriptor.kt:98)
	at com.intellij.platform.lsp.api.LspServerDescriptor.startServerProcess(LspServerDescriptor.kt:98)
	at com.intellij.platform.lsp.impl.connector.Lsp4jServerConnectorStdio.<init>(Lsp4jServerConnectorStdio.kt:17)
	at com.intellij.platform.lsp.impl.LspServerImpl.F(LspServerImpl.kt:318)
	at com.intellij.platform.lsp.impl.LspServerImpl.F(LspServerImpl.kt:298)
	at com.intellij.openapi.application.impl.RwLockHolder$executeOnPooledThread$1.run(RwLockHolder.kt:154)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
	at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.io.IOException: Cannot run program "\\wsl.localhost\Ubuntu-20.04\home\michael\.pyenv\shims\ruff-lsp": CreateProcess error=193, %1 is not a valid Win32 application
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
	at com.intellij.execution.configurations.GeneralCommandLine.createProcess(GeneralCommandLine.java:491)
	at com.intellij.execution.configurations.GeneralCommandLine.startProcess(GeneralCommandLine.java:464)
	at com.intellij.execution.configurations.GeneralCommandLine.createProcess(GeneralCommandLine.java:357)
	... 17 more
Caused by: java.io.IOException: CreateProcess error=193, %1 is not a valid Win32 application
	at java.base/java.lang.ProcessImpl.create(Native Method)
	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:499)
	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:158)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
	... 21 more
2024-05-22 11:49:09,435 [  18484]   INFO - #c.i.p.l.i.LspServerImpl - RuffLspServerDescriptor@fs2d-analytics(Initializing;0): Stopping LSP server unexpectedly
2024-05-22 11:49:09,445 [  18494]   INFO - #c.i.u.i.IndexingReasonExplanationLogger - Scanner has updated file workspace.xml with appliers: [SingleIndexValueApplier{indexId=filetypes, inputId=1279, fileInfo='workspace.xml(id=1279)'}] and removers: [];
2024-05-22 11:49:09,507 [  18556]   INFO - #c.i.o.v.i.p.NewMappings - VCS Root: [Git] - [<Project>]
2024-05-22 11:49:09,517 [  18566]   INFO - #com.maddyhome.idea.vim.handler.EditorHandlersChainLogger - Esc handlers chain:
com.maddyhome.idea.vim.handler.VimEscLoggerHandler

Expected behavior
I want to get linter hints in my IDE.
Screenshots

Environments (please complete the following information):

IDE: PyCharm 2024.1.1
OS: Windows 11 with WSL
Ruff Version 0.0.33
Plugin version [e.g. 0.3.11 ]

Additional context
Add any other context about the problem here.

@michaelmaschinenf
I'm sorry for the late action.
I have released the fixed version as 0.0.36
https://plugins.jetbrains.com/plugin/20574-ruff/versions/stable/597308

authors: koxudaxi michaelmaschinenf

repo: koxudaxi/ruff-pycharm-plugin


text:
Translation and Rotate

Hi, I have some question about Translation and Rotate in data_loader.py.
https://github.com/koyeongmin/PINet_new/blob/fead6baf0210a11444bf02d8fda7b3a33cec8e8c/TuSimple/data_loader.py#L384
Why don't you process target_h when you translate and rotate the image in case that target_h is out of [0, y_size-1]?

Because y_size is height of input image, It will occur error if we make some value at that point.

Probably I didn't make myself clear to you. When you translate and rotate the image, why don't you translate and rotate the target_h that is y coordinates of lane keypoints? In your code, you only translate and rotate target_lanes that is x coordinates of lane keypoints.

authors: JiayiLy koyeongmin


text:
Note amfora is in maintenance mode

I noted in READEME.dm that amfora is in maintenance mode. Fixes #169

@Solomon1732 Thanks for the PR 🎉


text:
fix [heartbeat_interval] sec wait after boot in worker command

Summary
After boot the started worker would spend the amount of seconds defined by the heartbeat_interval not dequeuing any jobs but continuously looping through the following loop in a high cpu cycle fashion:
eval { $self->_work until $self->{finished} && !keys %{$self->{jobs}}; 1 }
With a default heartbeat_interval value of 5 minutes for the worker command this can be a long time.
The reason for this behaviour was that CLOCK_MONOTONIC on linux systems seems to use boot time as reference so that this condition never evaluated true for the time of one heartbeat_interval:
$worker->register and $self->{last_heartbeat} = steady_time
if ($self->{last_heartbeat} + $status->{heartbeat_interval}) < steady_time;
The fix sets the initial value for "last_heartbeat" to a negated heartbeat_interval so the worker can register immediately.

On my OpenSuse 42.2 VM with 4.4.27 Kernel a call to steady_time results in a syscall of clock_gettime(CLOCK_MONOTONIC...) which gives the uptime of the system in seconds.
The issue only affects the first few seconds after a full system reboot. (when steady_time is smaller than the first heartbeat_interval)

Oh, now i get it.

Thanks, applied.

authors: kraih rgci

repo: kraih/minion


text:
Fix two test names to match the test result

Found two tests that had inverted names, as if there was a copy and paste and later the test was inverted or something.

Thanks, applied.

authors: andk kraih

repo: kraih/mojo


text:
Power User Mode

Upon first start of the application there has to be a choice: Are you a power users?
Like are you are cryptocurrency expert who knows his way around, or are you fairly new to crypto.
Based on the answer you are given access to multiple additional settings that you might not have access to otherswise.
For instance:
24 words seed phrases;
Multisignature;
Passphrase;
and more.

I can't find the eddit button so:
Ofcourse one can change this in the settings at later date.
So a user who gains experience over time can change the settings or a user who clicked Power User and made a mistake doing so can revert it back.

repo: krakenfx/wallet


text:
Question: How to destroy/teardown

In a React environment, imagine this:

Component is mounted, xcomponent is then set up, iframe loaded, event listeners attached etc
The component is unmounted (because we no longer want to show the xcomponent)
Component is mounted again. Now we're getting the error:

Request listener already exists for xcomponent_delegate_mystuff on domain * for specified window

I'm enclosing the xcomponent supplied react component in my own component so I can do stuff on componentWillUnmount, but how to tear down the correct way? I've searched the source code but didn't find any obvious reasons.

So let me understand -- when the component is mounted, you're calling xcomponent.create again?
xcomponent comes with good support for tearing down a component that's been rendered, not so much for tearing down the component definition -- the assumption is xcomponent.create() is only called once per page per component.
I'd like to understand this use-case a bit better though.

I am calling xcomponet.create() once per component but I got Request listener already exists for xcomponent_delegate_calendar_modal on domain * for specified window also

@raphaelcosta weird -- since that listener should only be set up on xcomponent.create.

Could you share a stack trace for that error?

addRequestListener@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:101108:116
listen@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:103216:68
value@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:103476:34
Component@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:103439:117
create@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:102001:45
render@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98170:53
measureLifeCyclePerf@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:23808:15
_renderValidatedComponentWithoutOwnerOrContext@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24528:46
_renderValidatedComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24555:79
performInitialMount@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24095:56
mountComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:23991:41
mountComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:16552:50
updateChildren@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:23563:66
_reconcilerUpdateChildren@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:23094:47
_updateChildren@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:23198:57
updateChildren@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:23185:28
_updateDOMChildren@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:20434:27
updateComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:20252:29
receiveComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:20214:26
receiveComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:16631:39
_updateRenderedComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24487:40
_performComponentUpdate@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24457:35
updateComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24378:36
receiveComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24280:26
receiveComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:16631:39
_updateRenderedComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24487:40
_performComponentUpdate@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24457:35
updateComponent@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24378:36
performUpdateIfNecessary@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:24294:28
performUpdateIfNecessary@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:16663:47
runBatchedUpdates@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:16252:46
perform@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:17546:25
perform@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:17546:25
flushBatchedUpdates@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:16274:27
flushBatchedUpdates@[native code]
closeAll@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:17612:30
perform@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:17559:25
enqueueUpdate@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:16302:37
enqueueUpdate@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:25707:30
enqueueSetState@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:25892:19
setState@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:10546:32
_onChange@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:90350:19
_onChange@[native code]
emit@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:31954:15
updateAndEmitChange@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:34082:15
http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:34274:39
_invokeCallback@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:31483:25
dispatch@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:31459:30
openModal@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:31741:39
modal@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98083:37
modal@[native code]
bound modal@[native code]
bound bound modal@[native code]
bound bound bound modal@[native code]
bound bound bound bound modal@[native code]
http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98517:89
dispatch@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98528:20
then@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98538:55
http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:103019:104
http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98517:89
dispatch@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98528:20
then@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98538:55
http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:101268:45
trycatch@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98428:24
SyncPromise@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98490:26
deNodeify@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:101264:36
http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98517:89
dispatch@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98528:20
then@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98538:55
http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:102857:34
receiveMessage@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:102786:60
messageListener@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:102805:28
http://localhost:4000/js/xcomponent.js:4704:159
receiveMessage@http://localhost:4000/js/xcomponent.js:4601:59
messageListener@http://localhost:4000/js/xcomponent.js:4620:27
	(anonymous function) (application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:98460)```

I do see a create call there:
create@http://localhost:3000/assets/v3/application-49050ad020c8fa96d5dc862c32729b8e8e833a39b82a7c0b6e9822e4d2215d15.js:102001:45
At what point in your code are you calling create()? could you share some code?

Also FWIW, I should really add an earlier error for multiple creates with the same tag name...

I am creating inside a render method, it's possible to call everytime component mount? I am using that to render dynamic tag names

Yeah, that's the problem then. The expectation is you call create() at load time with a unique tag name, then render() when you're ready to render.
Does that not work for you? Out of interest, why do you need dynamic tag names?

I am trying to use xcomponent to build a platform for apps, like Trello power ups.
We will have multiple apps initialized, so 2 apps could have 2 modals with iframe at same time.

Sure -- but could you not create the component once, for this use case, and render it twice?

Yes, I will do that. My current scenario is when user open Modal(iframe), closes and try to open again.
Thanks for you help @bluepnume

Also @emiloberg sounds like you may be doing something similar. Interested to know if there's a reason you can't call create() once at the top level, then render() when you're ready to display

I guess I should clarify this in the docs. create() is analogous to React's createClass() (which I'm assuming you'd only ever call once per component you want to create) and render() is analogous to calling render() in React, or dropping a component into a jsx template.

Yes, I didn't get that. Thanks for clarifying that for me.

authors: bluepnume emiloberg raphaelcosta

repo: krakenjs/xcomponent


text:
Add beaver logs

We should use beaver-logger to instrument xcomponent, and allow people to pass in their own beaver back-end url, for example:
let FooComponent = xcomponent.create({
    ...
    logUrl: 'http://foo.com/api/log'
});

Mostly done, but still need to figure out how to separate this out so it's more of a dependency injection, since:
a) it's only a soft dependency
b) other apps might also include beaver-logger and don't want to load it twice.
Right now just mooting window.$logger...


text:
Use RUN instead of ADD

Using ADD automatically invalidates the cache of subsequent command in the docker build, even if the version has not changed.
I recommend using RUN with curl so that the cache is only invalidated when the version in the URL actually changes.
https://docs.docker.com/engine/reference/builder/#add

Thanks for your suggestion; however, I'd rather not implement this change.
I've explained in https://github.com/krallin/tini/issues/103 if you'd like to check this out.
Cheers,

I completely understand the desire to make README instructions work by default for the broadest possible audience and having curl installed is an extra step. That said, most people have to figure out how to install some software in their docker image, so it doesn't feel like a big leap to me to ask them to install curl. Fair enough if you disagree, this is your project and thank you for making something so useful.

RUN is a much superior approach when build performance and a minimal number of layers are desirable (in fact, that's often how I install Tini myself when I use it in production) .

Given the fact that you agree the documented approach isn't ideal for production, how would you feel about adding a separate section/note at the bottom of the readme that discusses the ADD cache footgun and has a single example with using RUN curl... (instead of changing it everywhere like I did in this PR)?

authors: krallin nicksnyder

repo: krallin/tini


text:
supplemented by information to lessons №19

Добавлена дополнительная информация, про автообновление страниц без перезапуска сервера.

Спасибо за предложение, про это уже написано в 22 уроке. https://github.com/krdprog/rubyschool-notes/blob/81ad7b4ce59f1f27e741cc7be5504138aad9fd4f/one-by-one/lesson-22.md
В уроке эта тема поднималась.

authors: dionixs krdprog

repo: krdprog/rubyschool-notes

license: Unlicense


text:
Spray Coater pushed out of keybinds bar

While you add in new content, some others that are in the game got pushed out of the keybinds. it will be nice by default you moved the Spray Coating to somewhere else, let say gathering.

Do you mean you build bar?

You have rebind build bar for a reason. You can rebind it yourself.

Please check this mod readme. You already have it installed. https://dsp.thunderstore.io/package/kremnev8/RebindBuildBar/

Do you mean you build bar?

Yes, hotbar key is what i ment.

Unfortunately I can't place everything by default, as there is not enough space in there. As such I won't be doing this. RebindBuild bar covers this issue perfectly.


text:
Using with view in layout

Hi @krimin-killr21
Currently we can directly use MaterialScrollBar directly from Java. But it takes the flexibility, so can you create a some view like com.packagename.MaterialScrollBar which would be really cool & flexible to move in layout hierarchy.
Let me know what you think about it.

@AkshayChordiya Do you mean directly in xml-layout files? Look at new version 8. Maybe this issue could be closed.

authors: AkshayChordiya Rainer-Lang


text:
[feature]: what about adding a maxMatchSize option?

When searching in a large object, there may be too many results.
Adding a maxMatchSize option would reduce the perform issue by early returns.

It wouldn't make a huge difference without re-architecting some things. Ultimately you need to score all of the entries to find out the top entries, and that's where all the performance critical work is.

Agreed, @heyimalex.

It wouldn't make a huge difference without re-architecting some things. Ultimately you need to score all of the entries to find out the top entries, and that's where all the performance critical work is.

It may not need to score all of the entries, just to find a limit number of the result that meets the threshold(early returns, left the rest unvisited).
I've found the limit option on code, but it's not used.
https://github.com/krisk/Fuse/blob/fe1ff83645a55b6ea9f9488893a32495c132529f/src/index.js#L100-L102

@dabuside You're right that it'd be possible, but how often would it be used? The vast majority of people want the best matches, not the first x matches that crossed the threshold.
That code you linked runs after scoring.

@dabuside You're right that it'd be possible, but how often would it be used? The vast majority of people want the best matches, not the first x matches that crossed the threshold.
That code you linked runs after scoring.

oops. You're right.

authors: dabuside heyimalex krisk

repo: krisk/Fuse


text:
Make the async APIs thread-safe and fix the indexes they report

I put the fixes in the same PR because they target the same region of code, but let me know if you'd like to review them separately.

Thanks for the quick review @krisk! I optimized this a little further in https://github.com/krisk/fuse-swift/pull/43 if you like.

repo: krisk/fuse-swift


text:
Chrome V46 Tooltip Browser Crash

Hi,
It seems that there is a issue with custom tooltips which causes latest version of chrome to crash (V48 DEV suffers same issue).
When custom tooltips are disabled and highlight is used, everything works except for Linw With Focus chart which  uses custom tooltips by default.
Bug can be reproduced by using  more than 50 data points in.
http://krispo.github.io/angular-nvd3/#/lineWithFocusChart

can you please create a crash demo?

It seems that issue has been partially fixed in latest release. The problem was occuring when you had custom tooltips with more then 100 data points.  New problem is that custom tooltips are not working on line charts,  (interactive:true,guideline:false), but are working on multibar charts :(

nvd3 warning: tooltips has been deprecated.  use chart.tooltip.enabled() instead

authors: krispo rubenmendoza vhanescu


text:
Replace illegal characters for file names

This PR fixes file names replacing illegal characters.
E.g. it is impossible to create "GitHub (GitHub:OperKH).png" file in my case - it creates empty "GitHub (GitHub" file instead

Thanks! I tweaked it slightly.

authors: OperKH krissrex

repo: krissrex/google-authenticator-exporter


text:
Locale/vary support

Is it possible to generate different versions of an asset based on a vary configuration, such as "vary by locale."
{% javascripts 'js/dict.twig' vary='locale' output='js/{locale}/dict.js' %}...{% endjavascripts %}

I'm also looking for this feature. What is your conclusion here?

authors: kriswallsmith schmittjoh

repo: kriswallsmith/assetic


text:
Unified fetchOrder, is it possible?

fetchOrder was implemented for chbtc on #74. I was trying to implement it for liqui, poloniex and bittrex, but there's nothing like "getOrder" on poloniex, so I don't think it's possible without ugly "workarounds", like emulating it using "returnOpenOrders", "returnOrderTrades" and/or "returnTradeHistory". This might be the same for some other exchanges, I'm not sure.
I'm just wondering if it would be worth it to make fetchOrder part of the unified API, what do you think?

Yes, we have plans to unify the fetchOrder. Your help will be much appreciated as well (with those exchanges that you can handle without a big pain). We will update you on this, and, in the meantime, if you don't mind, I'm closing this issue as a duplicate of https://github.com/kroitor/ccxt/issues/71 ?

Sure! I missed that one, sorry.

authors: Nilotaviano kroitor

repo: kroitor/ccxt


text:
[System Tests] why is our test impl validating if alias exists when deleting the KEK

I appreciate this is just moved code, but why is our test impl validating this? Shouldn't we just forward it to the backend and let it decide? As currently we aren't actually testing against what the real KMS's systems will do when asked to delete an unknown alias.
Originally posted by @SamBarker in https://github.com/kroxylicious/kroxylicious/pull/1367#discussion_r1687171645

Currently we have some functionality included in the deleteKek method in the TestKekManager implementations that would not allow us to test the behavior of the KMS in case of an intended error, such as deleting a non-exisiting alias/keyId.
So we could think about moving that functionality to the test behavior instead having it inside the framework.

repo: kroxylicious/kroxylicious


text:
Automate attaching binary distribution to GitHub release

Currently we build and release the libs wlto maven central, and then tag the commit as vX.Y.Z and create a matching GitHub release.
Now that we can create binary distributions we should attach the tarball and zip to the release. Then we could point users towards the GitHub release to download it.
This would involve running another maven command with the dist profile and then I'm guessing some gh commands to attach the binaries after creating the release.

Triaged 16/08/23

@robobario was this done for 0.3.0? Or should it be moved to 0.4.0?

@robobario was this done for 0.3.0? Or should it be moved to 0.4.0?

Please move to 0.4.0, I don't see any distributions attached to 0.3.0 so assume this hasn't been touched

fixed by #776

authors: gracegrimwood robobario tombentley


text:
Provide an example about how to build a rocket project to wasm?

Using krustlet to run a HTTP server.
If an application using rocket as HTTP framework and diesel as ORM, how to build it to wasm?

Hi, @fanux.
Currently, you are unable to compile a program that uses networking sockets to WebAssembly — this includes HTTP servers.
See https://github.com/WebAssembly/WASI/pull/312 and https://radu-matei.com/blog/towards-sockets-networking-wasi/ for a write-up of the status for the networking APIs in WASI.
The workaround for writing HTTP handlers in WebAssembly is by using Wagi (or something like it) — https://github.com/deislabs/wagi, where the underlying runtime handles the actual HTTP listener and server, and passes the request data to a WebAssembly module.
You can use it today with Krustlet by following  — https://github.com/deislabs/krustlet-wagi-provider
Closing now, as there isn't anything we can do on the Krustlet side, but feel free to reopen if you think there is something we can improve here.
Thanks!

Hi, @fanux.
Currently, you are unable to compile a program that uses networking sockets to WebAssembly — this includes HTTP servers.
See https://github.com/WebAssembly/WASI/pull/312 and https://radu-matei.com/blog/towards-sockets-networking-wasi/ for a write-up of the status for the networking APIs in WASI.
The workaround for writing HTTP handlers in WebAssembly is by using Wagi (or something like it) — https://github.com/deislabs/wagi, where the underlying runtime handles the actual HTTP listener and server, and passes the request data to a WebAssembly module.
You can use it today with Krustlet by following  — https://github.com/deislabs/krustlet-wagi-provider
Closing now, as there isn't anything we can do on the Krustlet side, but feel free to reopen if you think there is something we can improve here.
Thanks!

We might use Dapr with wasi-experimental-http to work around with this model for networking interface like this article https://www.alibabacloud.com/blog/webassembly-%2B-dapr-%3D-next-generation-cloud-native-runtime_598222 too

authors: fanux radu-matei thangchung

repo: krustlet/krustlet


text:
sourcery failed to build swift templates with Xcode 9 beta / Swift 4

I tried just building the included templates with Sourcery, and this is the output:
Scanning sources...
Found "extension Encodable" of type for which there is no original type declaration information.
Found "extension Decodable" of type for which there is no original type declaration information.
Found "extension NSLock" of type for which there is no original type declaration information.
Found "extension NSRecursiveLock" of type for which there is no original type declaration information.
Found "extension UIStoryboard" of type for which there is no original type declaration information.
Found "extension UIViewController" of type for which there is no original type declaration information.
Found "extension URL" of type for which there is no original type declaration information.
Found "extension BaseMappable" of type for which there is no original type declaration information.
Found "extension Data" of type for which there is no original type declaration information.
Found "extension Dictionary" of type for which there is no original type declaration information.
Found "extension RealmSwift.List" of type for which there is no original type declaration information.
Found 151 types.
Loading templates...
Loaded 7 templates.
Generating code...
Rendering template Templates/AutoCases.stencil
error: Unknown type AutoCases, should be used with `based`
Skipping EsiMobile/Generated/AutoCases.generated.swift as it is empty.
Rendering template Templates/AutoEquatable.stencil
error: Unknown type AutoEquatable, should be used with `based`
error: Unknown type AutoEquatable, should be used with `based`
Rendering template Templates/AutoHashable.stencil
error: Unknown type AutoHashable, should be used with `based`
error: Unknown type AutoHashable, should be used with `based`
Rendering template Templates/AutoLenses.stencil
error: Unknown type AutoLenses, should be used with `based`
Rendering template Templates/AutoMockable.stencil
Rendering template Templates/Decorator.swifttemplate
/usr/bin/rsync "-av" "/usr/local/bin/Sourcery.app/Contents/Frameworks/SourceryRuntime.framework" "/var/folders/q7/pr0h22nd4cdgb2f6zrx7sg_w0000gn/T"
/usr/bin/swiftc "/var/folders/q7/pr0h22nd4cdgb2f6zrx7sg_w0000gn/T/Sourcery.build/main.swift" "-suppress-warnings" "-Onone" "-module-name" "main" "-target" "x86_64-apple-macosx10.10" "-F" "/var/folders/q7/pr0h22nd4cdgb2f6zrx7sg_w0000gn/T" "-o" "/var/folders/q7/pr0h22nd4cdgb2f6zrx7sg_w0000gn/T/Sourcery.build/bin"
error: /var/folders/q7/pr0h22nd4cdgb2f6zrx7sg_w0000gn/T/Sourcery.build/main.swift:2:8: error: module compiled with Swift 3.1 cannot be imported in Swift 4.0: /var/folders/q7/pr0h22nd4cdgb2f6zrx7sg_w0000gn/T/SourceryRuntime.framework/Modules/SourceryRuntime.swiftmodule/x86_64.swiftmodule
import SourceryRuntime

When I remove Decorator.swifttemplate, everything works fine.
Unfortunately if I try building sourcery in Xcode 9, I get compilation errors:
SWXMLHash.XMLIndexer:72:22: error: invalid redeclaration of 'Element'
    public typealias Element = SWXMLHash.XMLIndexer
                     ^
/Users/kshaikh/Github/Sourcery/Pods/SWXMLHash/Source/SWXMLHash.swift:457:10: note: 'Element' previously declared here
    case Element(XMLElement)

Hey @kashifshaikh thanks for submitting an issue, we will take a look soon on the Xcode 9 compilation issues 😄

This is expected. Sourcery 0.7 is still built with Xcode 8, thus it is build with Swift 3.1. The same about SourceryRuntime framework which is used internally by the tool and by Swift templates. That's why it can not be used with Xcode 9 and Swift 4. To solve that we will either need to provide a version built with Xcode 9 (we can do that and attach it to the release, will create a separate issue for that) or you need to build from sources, or not use swift templates.
P.S. if you don't use all the templates bundled with Sourcery release - don't provide its Templates folder as source of templates, specify individual templates that you need to avoid unneded code generation.

authors: Antondomashnev ilyapuchka kashifshaikh

repo: krzysztofzablocki/Sourcery


text:
[Question] Is it possible to generate inline code AND generate the AutoEquatable/AutoHashable implementations from the generated properties in one go?

Let's say I have a stencil template:
{% for type in types.all %}
{% if type|annotated:"AutoGenerateProperties" %}
// sourcery:inline:auto:{{ type.name }}.AutoGenerateProperties
{% for var in type.storedVariables %}
    {{ type.accessLevel }} {% if var.isMutable %}var{% else %}let{% endif %} {{ var.name }}: {{ var.typeName }}
{% endfor %}
// sourcery:end
{% endif %}
{% endfor %}

I have a Fruit protocol annotated for sourcery
protocol Fruit {
    // sourcery: defaultValue: = "Apple"
    var name: String { get set }

    // sourcery: defaultValue: = "Red"
    var color: String { get set }

    // sourcery: skipEquality, skipHashing
    var size: CGSize: { get set }
}

and I have an Apple struct with no implementation yet:
// sourcery: AutoGenerateProperties,AutoEquatable,AutoHashable
struct Apple: Fruit{
}

When I run sourcery,  the inline code generation works BUT the AutoEquatable and AutoHashable implementations for Apple are empty.
So, what I currently do is:

Run sourcery
Delete  // sourcery:inline:auto:{{ type.name }}.AutoGenerateProperties, // sourcery:end, and the AutoGenerateProperties annotation from Apple
Run sourcery again

The AutoEquatable and AutoHashable implementations are correctly generated in the second sourcery call.
Is there any way to do the inline code generation and AutoEquatable/AutoHashable generation in one sourcery command?

this is a bit surprising, the fact you use inline in one template should not break other templates, I assume you use our bundled Equality / Hashing templates (that don't have anything inlined) ?

Yes I am using the AutoEquatable and AutoHashable from https://github.com/krzysztofzablocki/Sourcery/tree/master/Templates/Templates

does the issue happen if you don't use :auto and just regular inline with manual markers?

It still happens.
I removed the generated lines and left only this on Apple:
// sourcery: AutoGenerateProperties,AutoEquatable,AutoHashable
struct Apple: Fruit{
// sourcery:inline:Apple.AutoGenerateProperties
// sourcery:end
}

Ran sourcery. It created the variables in my Apple.swift file but AutoEqutable.generated.swift has:
public func == (lhs: Apple, rhs: Apple) -> Bool {
    return true
}

AutoHashable.generated.swift has:
// MARK: - Apple AutoHashable
extension Apple: Hashable {
    public func hash(into hasher: inout Hasher) {
    }
}

I've changed the template to:
{% for type in types.all %}
{% if type|annotated:"AutoGenerateProperties" %}
// sourcery:inline:{{ type.name }}.AutoGenerateProperties
{% for var in type.allVariables %}
    {{ type.accessLevel }} {% if var.isMutable %}var{% else %}let{% endif %} {{ var.name }}: {{ var.typeName }}
{% endfor %}
// sourcery:end
{% endif %}
{% endfor %}

but your Apple type doesn't have any variables, so what else would you expect to be generated?

I see. So let's say the Fruit protocol has all the necessary Equatable and Hashable properties and I rewrite how AutoEquatable and AutoHashable work, it would be possible since those templates would make Sourcery read the properties from the Fruit protocol instead?

Yeah it works. Sorry about that 😅. I didn't think about the AutoEquatable and AutoHashable templates

authors: hooliooo krzysztofzablocki


text:
Remove warning when scene type is default type

When the user not set any specific type for ViewController on the storyboard it raise a warning.
I proposed to do the save treatment for casting that it already does for returntype.

looks good. thanks!

repo: krzyzanowskim/Natalie


text:
Update README.md

Fix typo :-)

Thanks!

authors: marcelm richelbilderbeek

repo: ksahlin/strobealign


text:
Add handling for artifacts with classifiers

The v0.2.0 plugin is unable to download artifacts with a Maven classifier specified with:
compile 'group:name:version:classifier'

This error is print for that artifact:

"ERROR: Could not find dependency: ${target}"

The correct place to find the file is:
.../modules-2/files-2.1/group/artifact/version/hash/artifact-version-classifier.ext
This change adds support for handling these classifiers. Please let me know if this is the correct fix, and thanks for publishing this plugin.

Coverage remained the same at 100.0% when pulling 27c79077a1c6ac3c2dd517c0570160875d7b4d7f on benhylau:classifier into 013e7a67470fe7ed5524af95f315cb9b2482c43f on ksoichiro:master.

@ksoichiro ping

@benhylau Thank you for your PR, and sorry for my late reply.
I found that one of the Gradle API, org.gradle.api.artifacts.ResolvedArtifact interface
has getClassifier() method, and maybe we should use this interface to handle artifacts correctly, I think.
But anyway, your fix seems enough to solve this issue.
Thank you!

Yea I first looked at that interface in ResolvedArtifact, but it's been a while and I can't remember why I couldn't use it. I vaguely remember it had something to do with AndroidDependency being a custom class. Thanks for merging!

authors: benhylau coveralls ksoichiro

repo: ksoichiro/gradle-eclipse-aar-plugin


text:
XRv9K: Target device not reloaded.

Condoor reports ‘Target device not reloaded’ but all the hosts reloaded successfully.
2017-04-17 12:55:45,395 [   DEBUG] condoor.fsm:run(152): RELOAD Start
2017-04-17 12:56:38,365 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=2,STATE=0
2017-04-17 12:56:38,400 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=3,STATE=0
2017-04-17 12:56:38,400 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=4,STATE=0
2017-04-17 13:00:38,090 [   DEBUG] condoor.fsm:run(176): E=6,S=0,T=600,RT=239.69
2017-04-17 13:00:38,091 [   DEBUG] condoor.fsm:run(185): A=None
2017-04-17 13:00:38,091 [   DEBUG] condoor.fsm:run(193): NS=6,NT=600
2017-04-17 13:00:38,092 [   DEBUG] condoor.fsm:run(176): E=7,S=6,T=600,RT=0.00
2017-04-17 13:00:38,092 [   DEBUG] condoor.fsm:call_action(23): A=Send text line to the controller.
2017-04-17 13:00:38,394 [   DEBUG] condoor.fsm:run(193): NS=7,NT=300
2017-04-17 13:05:38,392 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:10:38,384 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:15:38,375 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:20:38,368 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:25:38,361 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:30:38,355 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:35:38,346 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:40:38,350 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:45:38,340 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:50:38,329 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 13:55:38,320 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 14:00:38,314 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 14:05:38,306 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 14:10:38,295 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 14:15:38,286 [ WARNING] condoor.fsm:run(196): Unknown transition: EVENT=11,STATE=7
2017-04-17 14:15:38,286 [   ERROR] condoor.fsm:run(207): FSM looped. Exiting
2017-04-17 14:15:38,288 [   ERROR] condoor.connection:emit_message(471): Target device not reloaded.
2017-04-17 14:15:38,325 [   DEBUG] condoor.device:disconnect(187): Disconnecting: telnet://cisco@172.28.98.211:8041
2017-04-17 14:15:38,325 [   DEBUG] condoor.protocols.telnet:disconnect(150): TELNETCONSOLE disconnect
2017-04-17 14:15:38,626 [   DEBUG] condoor.controller:disconnect(96): Disconnecting the sessions
2017-04-17 14:15:38,729 [   DEBUG] condoor.controller:disconnect(99): Disconnected

Fixed

authors: jamesjwei kstaniek

repo: kstaniek/condoor


text:
CPU 占用率过高

机型:iPhone 5C
系统:iOS 10.2
截图

切换视频播放CPU 基本飙到了 100%+

看下这个内存泄漏是不是缓存框架或者播放器导致的

看下这个内存泄漏是不是缓存框架或者播放器导致的


text:
How to get the ordered elements  manually?

I insert dom into gridly dom and call method gridly, but it did not trigger callback.How do I deal with it?
BTW, can I change some grid's position with code?

these are my dirty hack to solve problems above

repo: ksylvest/jquery-gridly


text:
[수정] API v1을 모두 v2로 교체

배경
일부 기능에 남아있던 API v1을 모두 v2로 교체했습니다. 서버 측에서 v1 API를 교체해 달라는 요청이 오래 전부터 있었는데, 여러 사정으로 인해 이제야 교체할 수 있었습니다.
여담으로 API v2에서는 api key 등의 신기술이 적용될 예정이라고 합니다. (출처: 4/27 회의록)
변경사항

테스트용 json 파일 및 테스트 코드도 수정했습니다.

https://github.com/ku-ring/KU-Ring-Android/commit/115f4752ac5e71bbb01481fc0599a575b6e90f2c: v2용 default response를 DefaultV2Response라는 이름으로 정의했습니다. v1을 모두 제거한 후 DefaultResponse로 이름을 변경할 예정입니다. (아래 커밋 참고)
https://github.com/ku-ring/KU-Ring-Android/commit/90f505048c6734b52b363a30f25f3c9ea34fd22d, https://github.com/ku-ring/KU-Ring-Android/commit/b2e43a11ce9f30aad2ad1448d2afb7a9b64b6229: 피드백 API를 교체했습니다.
https://github.com/ku-ring/KU-Ring-Android/commit/9e5e594de3015a4d0357f6c9fcd6cc2b5da73117, https://github.com/ku-ring/KU-Ring-Android/commit/bd335d681fcc6333d5f232b7ccc4707da49b0caa: 공지 API를 교체했습니다.
https://github.com/ku-ring/KU-Ring-Android/commit/8578bcdec68b0dd5ebf91944a11739b80bb92f12, https://github.com/ku-ring/KU-Ring-Android/commit/4874c614cd3315e58c9a92471b03781012cdfc07: 구독한 학과 리스트 API를 교체했습니다.
https://github.com/ku-ring/KU-Ring-Android/commit/075513d9f85830359f3f59a4946fd5241ef3542e, https://github.com/ku-ring/KU-Ring-Android/commit/89a1fc3dd35b56d202104c4fcfa8d4b13b0e10c5, https://github.com/ku-ring/KU-Ring-Android/commit/68810d30d43f2e49eae4a59ac5f02a355bb61f98: 학과 구독 API를 교체했습니다.
https://github.com/ku-ring/KU-Ring-Android/commit/d3ca1c9a9f7b29f53a789c138bd760064fa41c12, https://github.com/ku-ring/KU-Ring-Android/commit/404fded4145ddf87177bd08da73e35b680d2d908: v1용 default response를 제거하고, DefaultV2Response의 이름을 DefaultResponse로 수정했습니다.

release도 테스트 완료된 코드입니다~

repo: ku-ring/KU-Ring-Android


text:
Beat Saber search only searches for artist names

And it even includes the artist name twice in the search. I found this quite useful, because you can see if an artist has Beat Saber songs IN GENERAL. But as it is now - with this issue, you can't see (at a glance) if a specific song is available.
I kind of wish you could set whether the search should only filter by artist name or also by song name
Thank you for this extension by the way, otherwise it is very useful! <3

+1


text:
In UI jobs graph tab, show indication of sub-pipeline invocation.

In UI jobs graph tab, show indication of sub-pipeline invocation, with link to the sub-pipeline graph itself.

Duplicate
kube-HPC/hkube#750

authors: NassiHarel golanha

repo: kube-HPC/hkube


text:
[Bug]: Traefik keeps restarting all the time

Description
I have created a new cluster recently and deployed a couple of web services there along with TLS for each one of them. And finally I put the Hetzner LB behind CloudFlare. And that's when I started getting 525 SSL Handshake Error from CloudFlare. Investigation led me to traefik pod logs which shows that traefik is being restarted quite a lot and I can't seem to understart a true reason behind it.

kubectl describe -n traefik pod traefik-75fd586479-vsgvx

  Type     Reason     Age                   From     Message
  ----     ------     ----                  ----     -------
  Warning  Unhealthy  58m (x69 over 9h)     kubelet  Readiness probe failed: Get "http://10.42.3.14:9000/ping": dial tcp 10.42.3.14:9000: connect: connection refused
  Warning  Unhealthy  3m10s (x114 over 9h)  kubelet  Liveness probe failed: Get "http://10.42.3.14:9000/ping": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy  3m8s (x301 over 9h)   kubelet  Readiness probe failed: Get "http://10.42.3.14:9000/ping": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

kubectl get pods -n traefik -o wide

NAME                       READY   STATUS    RESTARTS         AGE     IP              NODE                          NOMINATED NODE   READINESS GATES
traefik-75fd586479-cbrkt   1/1     Running   0                3m29s   10.42.102.249   k3s-worker-17440953fcddcf01   <none>           <none>
traefik-75fd586479-k5b5j   1/1     Running   0                3m29s   10.42.102.250   k3s-worker-17440953fcddcf01   <none>           <none>
traefik-75fd586479-mf4wq   1/1     Running   0                3m29s   10.42.131.7     k3s-workload-amd64-xbl        <none>           <none>
traefik-75fd586479-vsgvx   1/1     Running   37 (2m33s ago)   10h     10.42.3.14      k3s-worker-71de43e0505e4dc5   <none>           <none>

Then I execute this command in terminal again after a couple of minutes
NAME                       READY   STATUS    RESTARTS         AGE   IP           NODE                          NOMINATED NODE   READINESS GATES
traefik-75fd586479-vsgvx   1/1     Running   37 (5m39s ago)   10h   10.42.3.14   k3s-worker-71de43e0505e4dc5   <none>           <none>

For some reason, traefik jumps from node to node.
Then I looked into traefik logs and here what it shows

kubectl logs -n traefik traefik-75fd586479-vsgvx --previous

Traefik logs
kubectl logs -n traefik traefik-75fd586479-vsgvx --previous
2024-10-11T16:30:57Z INF Traefik version 3.1.5 built on 2024-10-02T12:49:07Z version=3.1.5
2024-10-11T16:30:57Z INF
Stats collection is disabled.
Help us improve Traefik by turning this feature on :)
More details on: https://doc.traefik.io/traefik/contributing/data-collection/

2024-10-11T16:30:57Z INF Enabling ProxyProtocol for trusted IPs [127.0.0.1/32 10.0.0.0/8] entryPointName=web
2024-10-11T16:30:57Z INF Enabling ProxyProtocol for trusted IPs [127.0.0.1/32 10.0.0.0/8] entryPointName=websecure
2024-10-11T16:30:57Z INF Starting provider aggregator aggregator.ProviderAggregator
2024-10-11T16:30:57Z INF Starting provider *traefik.Provider
2024-10-11T16:30:57Z INF Starting provider *ingress.Provider
2024-10-11T16:30:57Z INF ingress label selector is: "" providerName=kubernetes
2024-10-11T16:30:57Z INF Creating in-cluster Provider client providerName=kubernetes
2024-10-11T16:30:57Z INF Starting provider *crd.Provider
2024-10-11T16:30:57Z INF label selector is: "" providerName=kubernetescrd
2024-10-11T16:30:57Z INF Creating in-cluster Provider client providerName=kubernetescrd
2024-10-11T16:30:57Z INF Starting provider *acme.ChallengeTLSALPN
2024-10-11T16:31:09Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:41942: read: connection reset by peer"
2024-10-11T16:31:13Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:42482: read: connection reset by peer"
2024-10-11T16:31:17Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:2956: read: connection reset by peer"
2024-10-11T16:31:20Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:35264: read: connection reset by peer"
2024-10-11T16:31:22Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:6725: read: connection reset by peer"
2024-10-11T16:31:26Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:11449: read: connection reset by peer"
2024-10-11T16:31:28Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:60139: read: connection reset by peer"
2024-10-11T16:31:30Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:26146: read: connection reset by peer"
2024-10-11T16:31:48Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:64538: read: connection reset by peer"
2024-10-11T16:31:50Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:62160: read: connection reset by peer"
2024-10-11T16:31:54Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:59993: read: connection reset by peer"
2024-10-11T16:31:58Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:22806: read: connection reset by peer"
2024-10-11T16:32:03Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:19873: read: connection reset by peer"
2024-10-11T16:32:17Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:40547: read: connection reset by peer"
2024-10-11T16:32:43Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:38871: read: connection reset by peer"
2024-10-11T16:32:50Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:45781: read: connection reset by peer"
2024-10-11T16:32:52Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:12022: read: connection reset by peer"
2024-10-11T16:32:54Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:17638: read: connection reset by peer"
2024-10-11T16:33:07Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:1189: read: connection reset by peer"
2024-10-11T16:33:24Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:43642: read: connection reset by peer"
2024-10-11T16:33:39Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:54101: read: connection reset by peer"
2024-10-11T16:33:41Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:60014: read: connection reset by peer"
2024-10-11T16:33:47Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:21735: read: connection reset by peer"
2024-10-11T16:34:18Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:4936: read: connection reset by peer"
2024-10-11T16:34:35Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:17052: read: connection reset by peer"
2024-10-11T16:34:47Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:9700: read: connection reset by peer"
2024-10-11T16:34:54Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:43955: read: connection reset by peer"
2024-10-11T16:35:11Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:56010: read: connection reset by peer"
2024-10-11T16:35:17Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:46808: read: connection reset by peer"
2024-10-11T16:35:24Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:56341: read: connection reset by peer"
2024-10-11T16:35:28Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:37627: read: connection reset by peer"
2024-10-11T16:35:35Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:23782: read: connection reset by peer"
2024-10-11T16:35:45Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:58842: read: connection reset by peer"
2024-10-11T16:35:52Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:29932: read: connection reset by peer"
2024-10-11T16:35:56Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:21478: read: connection reset by peer"
2024-10-11T16:36:00Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:18906: read: connection reset by peer"
2024-10-11T16:36:04Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:56715: read: connection reset by peer"
2024-10-11T16:36:05Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:41407: read: connection reset by peer"
2024-10-11T16:36:11Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:2593: read: connection reset by peer"
2024-10-11T16:36:13Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:48587: read: connection reset by peer"
2024-10-11T16:36:19Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:12493: read: connection reset by peer"
2024-10-11T16:36:20Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:55890: read: connection reset by peer"
2024-10-11T16:36:22Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:4663: read: connection reset by peer"
2024-10-11T16:36:24Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:59695: read: connection reset by peer"
2024-10-11T16:36:26Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:23891: read: connection reset by peer"
2024-10-11T16:36:28Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:51389: read: connection reset by peer"
2024-10-11T16:36:30Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:4682: read: connection reset by peer"
2024-10-11T16:36:32Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:54670: read: connection reset by peer"
2024-10-11T16:36:34Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:49066: read: connection reset by peer"
2024-10-11T16:36:35Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:31648: read: connection reset by peer"
2024-10-11T16:36:37Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:42948: read: connection reset by peer"
2024-10-11T16:36:39Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:3393: read: connection reset by peer"
2024-10-11T16:36:41Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:29542: read: connection reset by peer"
2024-10-11T16:36:43Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:47006: read: connection reset by peer"
2024-10-11T16:36:45Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:59415: read: connection reset by peer"
2024-10-11T16:36:47Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:46032: read: connection reset by peer"
2024-10-11T16:36:49Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:10751: read: connection reset by peer"
2024-10-11T16:36:50Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:8004: read: connection reset by peer"
2024-10-11T16:36:52Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:1877: read: connection reset by peer"
2024-10-11T16:36:54Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:57597: read: connection reset by peer"
2024-10-11T16:36:56Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:17810: read: connection reset by peer"
2024-10-11T16:36:58Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:60498: read: connection reset by peer"
2024-10-11T16:37:00Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:49148: read: connection reset by peer"
2024-10-11T16:37:02Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:30491: read: connection reset by peer"
2024-10-11T16:37:04Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:9393: read: connection reset by peer"
2024-10-11T16:37:05Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:13296: read: connection reset by peer"
2024-10-11T16:37:07Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:53422: read: connection reset by peer"
2024-10-11T16:37:09Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:37960: read: connection reset by peer"
2024-10-11T16:37:11Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:17739: read: connection reset by peer"
2024-10-11T16:37:13Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:11345: read: connection reset by peer"
2024-10-11T16:37:15Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:30884: read: connection reset by peer"
2024-10-11T16:37:17Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:43100: read: connection reset by peer"
2024-10-11T16:37:19Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:57897: read: connection reset by peer"
2024-10-11T16:37:20Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:17745: read: connection reset by peer"
2024-10-11T16:37:22Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:1079: read: connection reset by peer"
2024-10-11T16:37:24Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:11605: read: connection reset by peer"
2024-10-11T16:37:26Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:22391: read: connection reset by peer"
2024-10-11T16:37:28Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:30293: read: connection reset by peer"
2024-10-11T16:37:30Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:13250: read: connection reset by peer"
2024-10-11T16:37:32Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:7965: read: connection reset by peer"
2024-10-11T16:37:34Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:54181: read: connection reset by peer"
2024-10-11T16:37:35Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:16583: read: connection reset by peer"
2024-10-11T16:37:37Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:53389: read: connection reset by peer"
2024-10-11T16:37:39Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:30789: read: connection reset by peer"
2024-10-11T16:37:41Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:54004: read: connection reset by peer"
2024-10-11T16:37:43Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:33763: read: connection reset by peer"
2024-10-11T16:37:45Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:40997: read: connection reset by peer"
2024-10-11T16:37:47Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:64525: read: connection reset by peer"
2024-10-11T16:37:49Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:36071: read: connection reset by peer"
2024-10-11T16:37:50Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:12668: read: connection reset by peer"
2024-10-11T16:37:52Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:10462: read: connection reset by peer"
2024-10-11T16:37:54Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:18195: read: connection reset by peer"
2024-10-11T16:37:56Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:29207: read: connection reset by peer"
2024-10-11T16:37:58Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:19648: read: connection reset by peer"
2024-10-11T16:38:00Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:54209: read: connection reset by peer"
2024-10-11T16:38:02Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:29710: read: connection reset by peer"
2024-10-11T16:38:04Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:51228: read: connection reset by peer"
2024-10-11T16:38:05Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:44994: read: connection reset by peer"
2024-10-11T16:38:07Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:51831: read: connection reset by peer"
2024-10-11T16:38:09Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:54868: read: connection reset by peer"
2024-10-11T16:38:11Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:15643: read: connection reset by peer"
2024-10-11T16:38:13Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:4027: read: connection reset by peer"
2024-10-11T16:38:15Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:44883: read: connection reset by peer"
2024-10-11T16:38:17Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:64669: read: connection reset by peer"
2024-10-11T16:38:19Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:46981: read: connection reset by peer"
2024-10-11T16:38:20Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:44315: read: connection reset by peer"
2024-10-11T16:38:22Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:9132: read: connection reset by peer"
2024-10-11T16:38:24Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:31548: read: connection reset by peer"
2024-10-11T16:38:26Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:37932: read: connection reset by peer"
2024-10-11T16:38:28Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:10387: read: connection reset by peer"
2024-10-11T16:38:30Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:39554: read: connection reset by peer"
2024-10-11T16:38:32Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:14257: read: connection reset by peer"
2024-10-11T16:38:34Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:40483: read: connection reset by peer"
2024-10-11T16:38:35Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:30745: read: connection reset by peer"
2024-10-11T16:38:37Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:41608: read: connection reset by peer"
2024-10-11T16:38:39Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:64420: read: connection reset by peer"
2024-10-11T16:38:41Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:32593: read: connection reset by peer"
2024-10-11T16:38:43Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:53297: read: connection reset by peer"
2024-10-11T16:38:45Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:51223: read: connection reset by peer"
2024-10-11T16:38:47Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:1576: read: connection reset by peer"
2024-10-11T16:38:49Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:23271: read: connection reset by peer"
2024-10-11T16:38:50Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:18630: read: connection reset by peer"
2024-10-11T16:38:52Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:58694: read: connection reset by peer"
2024-10-11T16:38:54Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:35423: read: connection reset by peer"
2024-10-11T16:38:56Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:59727: read: connection reset by peer"
2024-10-11T16:38:58Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:55791: read: connection reset by peer"
2024-10-11T16:39:00Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:39101: read: connection reset by peer"
2024-10-11T16:39:02Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:23349: read: connection reset by peer"
2024-10-11T16:39:04Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:56860: read: connection reset by peer"
2024-10-11T16:39:05Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:59433: read: connection reset by peer"
2024-10-11T16:39:07Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:54419: read: connection reset by peer"
2024-10-11T16:39:09Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:3194: read: connection reset by peer"
2024-10-11T16:39:11Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:47675: read: connection reset by peer"
2024-10-11T16:39:13Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:21305: read: connection reset by peer"
2024-10-11T16:39:15Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:46435: read: connection reset by peer"
2024-10-11T16:39:17Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.130.0:26238: read: connection reset by peer"
2024-10-11T16:39:19Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:65219: read: connection reset by peer"
2024-10-11T16:39:20Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:63080: read: connection reset by peer"
2024-10-11T16:39:22Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:21911: read: connection reset by peer"
2024-10-11T16:39:24Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.130.0:14581: read: connection reset by peer"
2024-10-11T16:39:26Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:16629: read: connection reset by peer"
2024-10-11T16:39:28Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:47622: read: connection reset by peer"
2024-10-11T16:39:30Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:16943: read: connection reset by peer"
2024-10-11T16:39:34Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:18603: read: connection reset by peer"
2024-10-11T16:39:35Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:24521: read: connection reset by peer"
2024-10-11T16:39:37Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:33371: read: connection reset by peer"
2024-10-11T16:39:38Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:14758: read: connection reset by peer"
2024-10-11T16:39:40Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:37225: read: connection reset by peer"
2024-10-11T16:39:43Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:19001: read: connection reset by peer"
2024-10-11T16:39:45Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:18821: read: connection reset by peer"
2024-10-11T16:39:48Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:25361: read: connection reset by peer"
2024-10-11T16:39:50Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:48834: read: connection reset by peer"
2024-10-11T16:39:53Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:17658: read: connection reset by peer"
2024-10-11T16:39:55Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:28881: read: connection reset by peer"
2024-10-11T16:39:58Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:31312: read: connection reset by peer"
2024-10-11T16:40:00Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:21971: read: connection reset by peer"
2024-10-11T16:40:03Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:44184: read: connection reset by peer"
2024-10-11T16:40:05Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:15407: read: connection reset by peer"
2024-10-11T16:40:08Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.131.0:52434: read: connection reset by peer"
2024-10-11T16:40:10Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.3.1:25737: read: connection reset by peer"
2024-10-11T16:40:13Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8000->10.42.102.0:29679: read: connection reset by peer"
2024-10-11T16:40:14Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:46834: read: connection reset by peer"
2024-10-11T16:40:16Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:8303: read: connection reset by peer"
2024-10-11T16:40:19Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:46922: read: connection reset by peer"
2024-10-11T16:40:21Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:63431: read: connection reset by peer"
2024-10-11T16:40:24Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:36068: read: connection reset by peer"
2024-10-11T16:40:26Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:55451: read: connection reset by peer"
2024-10-11T16:40:29Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:57147: read: connection reset by peer"
2024-10-11T16:40:31Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:37188: read: connection reset by peer"
2024-10-11T16:40:34Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:32515: read: connection reset by peer"
2024-10-11T16:40:36Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:48865: read: connection reset by peer"
2024-10-11T16:40:39Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:26165: read: connection reset by peer"
2024-10-11T16:40:41Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:10806: read: connection reset by peer"
2024-10-11T16:40:44Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:49117: read: connection reset by peer"
2024-10-11T16:40:46Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:26946: read: connection reset by peer"
2024-10-11T16:40:49Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.102.0:17212: read: connection reset by peer"
2024-10-11T16:41:04Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.3.1:65230: read: connection reset by peer"
2024-10-11T16:41:17Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:8443->10.42.131.0:18003: read: connection reset by peer"
2024-10-11T16:41:22Z INF I have to go...
2024-10-11T16:41:52Z INF Stopping server gracefully

It just shuts down gracefuly and that's it. So I kept monitoring it and sometimes I get additional errors use of closed network connection:
2024-10-11T15:57:29Z INF I have to go...
2024-10-11T15:57:35Z INF Stopping server gracefully
2024-10-11T15:57:36Z ERR error="accept tcp [::]:9100: use of closed network connection" entryPointName=metrics
2024-10-11T15:57:42Z ERR error="accept tcp [::]:9000: use of closed network connection" entryPointName=traefik
2024-10-11T15:57:42Z ERR error="accept tcp [::]:8443: use of closed network connection" entryPointName=websecure
2024-10-11T15:57:48Z ERR Error while Peeking first byte error="read tcp 10.42.3.14:9000->10.42.3.1:50102: use of closed network connection"
2024-10-11T15:57:42Z ERR error="accept tcp [::]:8000: use of closed network connection" entryPointName=web
2024-10-11T15:58:16Z INF Shutting down
2024-10-11T15:58:16Z INF Server stopped

I thought maybe this could happen because I have 0 agent_nodepools nodes, only autoscaled ones, where I already deployed high traffic web apps that could easily consume a lof of CPU and RAM. I've added a new node to the agent just to make sure, and traefik pod did occupy that spare node, yet restarted again.

I'm completely out of ideas at this point. Traefik is not crashing, it just keeps restarting. Traefik docs says that the stop signal comes from above.
Kube.tf file
locals {
  hcloud_token = "xxxxxxxxxxx"
}

module "kube-hetzner" {
  providers = {
    hcloud = hcloud
  }
  hcloud_token = var.hcloud_token != "" ? var.hcloud_token : local.hcloud_token
  source = "kube-hetzner/kube-hetzner/hcloud"
  ssh_public_key = file("~/.ssh/id_ed25519.pub")
  ssh_private_key = file("~/.ssh/id_ed25519")
  network_region = "eu-central"
  control_plane_nodepools = [
    {
      name        = "control-plane-fsn1",
      server_type = "cax11",
      location    = "fsn1",
      labels      = ["k8s"],
      taints      = [],
      count       = 1,
      swap_size   = "2G"
    },
    {
      name        = "control-plane-nbg1",
      server_type = "cax11",
      location    = "nbg1",
      labels      = ["k8s"],
      taints      = [],
      count       = 1,
      swap_size   = "2G"
    },
    {
      name        = "control-plane-hel1",
      server_type = "cax11",
      location    = "hel1",
      labels      = ["k8s"],
      taints      = [],
      count       = 1,
      swap_size   = "2G"
    }
  ]

  agent_nodepools = [
    {
      name        = "workload-amd64"
      server_type = "cpx11"
      location    = "fsn1"
      labels      = []
      taints      = []
      kubelet_args = [
        "kube-reserved=cpu=50m,memory=300Mi,ephemeral-storage=1Gi",
        "system-reserved=cpu=250m,memory=300Mi"
      ]
      count     = 1
      swap_size = "2G"
    }
  ]
  load_balancer_type     = "lb11"
  load_balancer_location = "fsn1"
  autoscaler_nodepools = [
    {
      name        = "worker"
      server_type = "cpx21"
      location    = "fsn1"
      min_nodes   = 1
      max_nodes   = 10
      taints      = []
      kubelet_args = [
        "kube-reserved=cpu=250m,memory=1000Mi,ephemeral-storage=1Gi",
        "system-reserved=cpu=250m,memory=200Mi"
      ]
    }
  ]
  system_upgrade_use_drain = true
  extra_firewall_rules = [
    {
      description     = "Allow Outbound TCP MySQL Requests"
      direction       = "out"
      protocol        = "tcp"
      port            = "29867"
      source_ips      = []
      destination_ips = ["78.46.253.145"]
    },
    {
      description     = "Allow Outbound UDP MySQL Requests"
      direction       = "out"
      protocol        = "udp"
      port            = "29867"
      source_ips      = []
      destination_ips = ["78.46.253.145"]
    },
    {
      description     = "Allow Outbound TCP Redis Requests"
      direction       = "out"
      protocol        = "tcp"
      port            = "19321"
      source_ips      = []
      destination_ips = ["91.107.211.207"]
    },
    {
      description     = "Allow Outbound UDP Redis Requests"
      direction       = "out"
      protocol        = "udp"
      port            = "19321"
      source_ips      = []
      destination_ips = ["91.107.211.207"]
    }
  ]
  dns_servers = [
    "1.1.1.1",
    "8.8.8.8",
    "2606:4700:4700::1111",
  ]
}

provider "hcloud" {
  token = var.hcloud_token != "" ? var.hcloud_token : local.hcloud_token
}

terraform {
  required_version = ">= 1.5.0"
  required_providers {
    hcloud = {
      source  = "hetznercloud/hcloud"
      version = ">= 1.43.0"
    }
  }
}

output "kubeconfig" {
  value     = module.kube-hetzner.kubeconfig
  sensitive = true
}

variable "hcloud_token" {
  sensitive = true
  default   = ""
}

Screenshots
No response
Platform
Linux

It appears that setting ingress_replica_count to 3 solves the issue. From the comment above that option

The default 0 means autoselecting based on number of agent nodes (1 node = 1 replica, 2 nodes = 2 replicas, 3+ nodes = 3 replicas)

And I had 0 agent nodes, but 2-4 autoscaled nodes. Probably a single pod with traefik couldn't handle the amount of traffic apps on my cluster were getting, though kubectl top showed that it's nearly idle. I tried using Lens to see live CPU load, but it just couldn't get the metrics.
I am going to leave this issue open until it's confirmed to be a misconfiguration on my side and not an actual bug.

@abriginets Could have been the case indeed. The pod was not healthy or ready. Happy it's working now!

authors: abriginets mysticaltech


text:
test/e2e: Ensure the test artifacts base directory exists before running e2e suite

Update the main_test entrypoint function and ensure that we can stat the
base test artifact directory before we start running any of the e2e test
handler functions.
We're currently seeing instances of CI runs where this directory doesn't exist
for whatever reason, and we log these kinds of errors to a file, which won't exist
if the directory doesn't exist, instead of stdout like t.Logf(...).

/close

repo: kube-reporting/metering-operator


text:
update to use kubeapps/dashboard

removes prerender and ratesvc

@prydonius Can you quickly explain the removing part ?

Yes, sorry. Ratesvc is for starring/commenting which is only needed in the Hub. Prerender is for prerendering (surprise) the Angular app so that search engines can index the Hub. This isn't needed on-premise.

authors: ngtuna prydonius

repo: kubeapps/manifest


text:
kubearmor automatic stopped watchalerts problem

Bug Report

Unexpected behavior
karmor logs
local port to be used for port forwarding kubearmor-relay-6fddb8865b-bh2fk: 32813
Created a gRPC client (localhost:32813)
Checked the liveness of the gRPC server
Started to watch alerts
== Alert / 2023-07-26 11:45:49.815282 ==
ClusterName: default
HostName: ip-192-168-65-235
NamespaceName: nginx
PodName: nginx-deployment-68f7f96974-9dz8m
Labels: app=nginx
ContainerName: nginx
ContainerID: 20575b9e764f40001c080a96c135f3e75f8545c8fa7b802cc1ae6dac47f97501
ContainerImage: docker.io/library/nginx:latest@sha256:08bc36ad52474e528cc1ea3426b5e3f4bad8a130318e3140d6cfe29c8892c7ef
Type: MatchedPolicy
PolicyName: ksp-group-1-proc-path-block
Severity: 1
Source: /usr/bin/bash
Resource: /usr/bin/apt update
Operation: Process
Action: Block
Data: syscall=SYS_EXECVE
Enforcer: BPFLSM
Result: Permission denied
HostPID: 24617
HostPPID: 24568
Owner: map[Name:nginx-deployment Namespace:nginx Ref:Deployment]
PID: 69
PPID: 63
ParentProcessName: /usr/bin/bash
ProcessName: /usr/bin/apt
releasing grpc client
Stopped WatchAlerts
Screenshots
If applicable, add screenshots to help explain your problem.

This usually happens due to connection breakages experienced by internal port-forwarding done by karmor logs command.
Note that karmor logs is not a solution to be used for long-standing logs/telemetry/alerts pull. The right thing to do would be to either stream the logs to elf, prometheus etc. Check this for ref.

repo: kubearmor/KubeArmor


text:
wrapper functions required

Implement of the following wrapper functions is currently required to attach any ebpf program:

getprogram()
attachkprobe()
traceprint()

@Ankurk99 I'll work on it asap.

I noticed that TracePrint() is no longer in the libbpfgo.go codebase. It was moved to helpers module and named TracePipeListen() https://github.com/aquasecurity/libbpfgo/blob/391db9565ae877caa14423f5999b6847ef085ad5/helpers/tracelisten.go#L15-L33.
@Ankurk99 Is TracePipeListen() really necessary at this moment? If not, as we're building the KA libbpf as 1:1 to kernel libbpf, I would like to defer its implementation into a sub-module to be created.

Ah sure, we can do it's implementation later.

@Ankurk99, be my guest to test the changes. It would be grand if you could create the tests/progs.go and tests/progs.bpf.c and raise a PR with them.

repo: kubearmor/libbpf


text:
fix: recovery operation name repeat

What type of PR is this?
/kind bug

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

/cc @zhuzhenfan

/lgtm

/approve

authors: Metrora x893675 zhuzhenfan

repo: kubeclipper-labs/kubeclipper


text:
Refactor downloader

Fix not loading on worker node when adding plugins, and optimize code for download + load mirror of plugins
Signed-off-by: zhuzhenfan 981189503@qq.com

What type of PR is this?
/kind bug

What this PR does / why we need it:
reopen issue #356: Fix not loading on worker node when adding plugins, and optimize code for download + load mirror of plugins
Which issue(s) this PR fixes:

Fixes #356
Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

@x893675 @Metrora

/lgtm
/approve

/cherrypick master

repo: kubeclipper/kubeclipper


text:
Invalid value: "v2beta1": must appear in spec.versions

Hi, I'm trying to install KubeFlow Training Operator 1.6.0 on an AWS cluster.
Below is the command I used for installation:
kubectl apply -k "github.com/kubeflow/training-operator/manifests/overlays/standalone?ref=v1.6.0"
I got the following output:
namespace/kubeflow created
customresourcedefinition.apiextensions.k8s.io/mxjobs.kubeflow.org created
customresourcedefinition.apiextensions.k8s.io/paddlejobs.kubeflow.org created
customresourcedefinition.apiextensions.k8s.io/pytorchjobs.kubeflow.org created
customresourcedefinition.apiextensions.k8s.io/tfjobs.kubeflow.org created
customresourcedefinition.apiextensions.k8s.io/xgboostjobs.kubeflow.org created
serviceaccount/training-operator created
clusterrole.rbac.authorization.k8s.io/training-operator created
clusterrolebinding.rbac.authorization.k8s.io/training-operator created
service/training-operator created
deployment.apps/training-operator created
The CustomResourceDefinition "mpijobs.kubeflow.org" is invalid: status.storedVersions[0]: Invalid value: "v2beta1": must appear in spec.versions

It seems like there is something wrong this version, but I've no idea what it means and how to debug it. Any insights here would be helpful!

You can not install both MPIJob v1 and v2beta1 crds to the cluster. If you installed a CRD MPIJob v2beta1 (mpi-operator), you need to remove the below line:
https://github.com/kubeflow/training-operator/blob/a4c0cec561a4bfe478720f1a102f305ed656071b/manifests/base/crds/kustomization.yaml#L8
Or you can use the kustomize delete patch:
$patch: delete
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: mpijobs.kubeflow.org

@tenzen-y Thank for pointing that out!
Another quick question I have is: I have 1 head node and 2 worker nodes. Which nodes should I install KubeFlow Training Operator and MPI Operator on?

@tenzen-y Thank for pointing that out! Another quick question I have is: I have 1 head node and 2 worker nodes. Which nodes should I install KubeFlow Training Operator and MPI Operator on?

Those operators don't mind where they are run. So you can install that operator on any node.

However, you need to set the below parameters to the training-operator when you install both the training-operator and the mpi-operator to the same cluster:
https://github.com/kubeflow/training-operator/issues/1777#issuecomment-1480720233
By the above configuration, MPIJob v1 is disabled in the cluster, and then you can use only MPIJob v2beta1.

authors: Wenhan-Tan tenzen-y

repo: kubeflow/training-operator


text:
[SDK] Fix Failed condition in wait Job API

We should check if Failed is not in expected_conditions set. We need to add more unit tests for our SDK. I will create issues for it.
/assign @kubeflow/wg-training-leads @droctothorpe

Pull Request Test Coverage Report for Build 9856249929
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 35.398%

Files with Coverage Reduction
New Missed Lines
%

pkg/controller.v1/mpi/mpijob.go
1
91.06%

Totals

Change from base Build 9675519469:
-0.008%

Covered Lines:
4377

Relevant Lines:
12365

💛  - Coveralls

RuntimeError

Sure, done

authors: andreyvelich coveralls


text:
'@org_golang_x_sys//unix:go_default_library%linux_amd64_msan%cgo_cxx_lib' does not have mandatory providers: 'cc'.

ERROR: /root/.cache/bazel/_bazel_root/47ca83421d4eade77cfa488519355325/external/org_golang_x_sys/unix/BUILD.bazel:3:1: in libs attribute of _cgo_collect_info rule @org_golang_x_sys//unix:go_default_library%linux_amd64_msan%cgo_info: '@org_golang_x_sys//unix:go_default_library%linux_amd64_msan%cgo_cxx_lib' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'go_library_macro', the error might have been caused by the macro implementation in /root/.cache/bazel/_bazel_root/47ca83421d4eade77cfa488519355325/external/io_bazel_rules_go/go/private/rules/cgo.bzl:694:16

This is not the right place to ask for help, please reach out to the maintainers of the distribution you are using.
/close

authors: thesuperzapper wanvincent

repo: kubeflow/website


text:
Update installation instructions for IKS

Update IKS deployment instructions to 1.3.1
Signed-off-by: Yihong Wang yh.wang@ibm.com

/cc @Tomcli

/lgtm
/approve

/approve

authors: Tomcli yhwang


text:
Update aws related documents for 0.4 release

Try tutorials using AWS EKS and notice several documentation are outdated and need to update.

This change is

@sarahmaddox  Most of the changes are not specific to v0.4, only change is I change tf-serving aws prototype from tf-serving-aws to tf-serving-deployment-aws.
This change has been merge into kubeflow/kubeflow master today. https://github.com/kubeflow/kubeflow/pull/2097
Since kubeflow team is working on v0.4 release cut, I think corresponding website change can be merge into master and cut the release branch together with kubeflow main repo.

You're right. :)
/ok-to-test
/approve

authors: Jeffwan sarahmaddox


text:
ecmp route doesn't update after gatwayNode is notReady

Steps to Reproduce the Problem

create a subnet (100.90.8.0/24) whose gatewayType is centralized and gatewayNode is node1, node2, where ip of node1 is 100.20.0.8 and
ip of node2 is 100.20.0.9.
create a pod (named pod1) with this subnet. Then ping www.baidu.com in pod1, which will succeed.
remove node ip from the main gatewayNode, like 100.20.0.8, and check ping baidu.com again, which will failed.

node status:
kubectl get no -o wide
NAME         STATUS                        ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION                CONTAINER-RUNTIME
100.20.0.7   Ready                         node     14d   v1.17.3   100.20.0.7    <none>        CentOS Linux 7 (Core)   3.10.0-1062.9.1.el7.x86_64    docker://18.9.9
100.20.0.8   NotReady,SchedulingDisabled   node     14d   v1.17.3   100.20.0.8    <none>        CentOS Linux 7 (Core)   3.10.0-1062.9.1.el7.x86_64    docker://18.9.9
100.20.0.9   Ready,SchedulingDisabled      node     13d   v1.17.3   100.20.0.9    <none>        CentOS Linux 7 (Core)   3.10.0-1062.9.1.el7.x86_64    docker://18.9.9

route in ovn-cluster:
kubectl ko nbctl lr-route-list ovn-cluster
IPv4 Routes
               100.20.0.7               100.64.0.11 dst-ip
               100.20.0.8               100.64.0.12 dst-ip
               100.20.0.9               100.64.0.13 dst-ip
            100.90.8.0/24               100.64.0.12 src-ip
            100.90.8.0/24               100.64.0.13 src-ip

https://github.com/kubeovn/kube-ovn/pull/924

authors: hongzhen-ma realksj

repo: kubeovn/kube-ovn


text:
Become Kubernetes conformance certified for 1.13 and 1.14

We should check can we become a Kubernetes conformance certified for 1.13 once we go open source and if yes we should see what's need and can we start the process.

I extended this issue to 1.14 as well.

/assign
/lifecycle active

We've become conformance certificed for Kubernetes 1.14, but we need to repeat the process for 1.13 and 1.15 (once it's out).

/close

repo: kubermatic/kubeone