text:
[Request Feature]

1.while idle or while using ASF bot can answer anyone who ask (auto message)
2.auto unlock the achievement with available games when PowerUser:master request maybe via private chat !unlockachievement

Out of the scope of ASF as a program.

not out of scope he just does not want to waste time on that


text:
FreeBSD support

My acquaintance reported current PicoGW does not work on FreeBSD.
It may be caused by the arp library I am using does not support FreeBSD.
I will check later and report here.
The log:
/usr/home/myname/PicoGW/node_modules/arped/lib/fetchers/ARP.js:25
throw new Error('Not Implemented');
^
Error: Not Implemented
at GenericARP.fetch (/usr/home/myname/PicoGW/node_modules/arped/lib/fetchers/ARP.js:25:19)
at Arped.table (/usr/home/myname/PicoGW/node_modules/arped/lib/index.js:45:36)
at chkArpTable [as _repeat] (/usr/home/myname/PicoGW/v1/plugins/admin/ipv4.js:85:22)
at wrapper [as _onTimeout] (timers.js:276:11)
at Timer.listOnTimeout (timers.js:93:15)

ARP management improved. PicoGW now works on Windows, MacOS, and Termux (Android app).
FreeBSD may be worth trying.

New picogw works on FreeBSD.
http://lifedesign.tech/2018/02/freebsd-picogw/

source: gharchive/issue

repo: KAIT-HEMS/PicoGW

license: mit

license_type: permissive

license_source: bigquery


text:
Bug: rerunning friends production command

I'm using the nmssm_devs branches of CROWN and CROWN-TauAnalysis and the main branch of KingMaker.
During the run of ntuple production and afterwards first run of friend production everything is fine. Example commands are:
law run ProduceSamples --analysis tau --config nmssm_config --sample-list nmssm_samples.txt --shifts None --production-tag 01_2024_nmssm_nominal_v5 --workers 40 --scopes mt,tt

and for friends
law run ProduceFriends --analysis tau --config nmssm_config --friend-config nmssm_fake_factors --sample-list nmssm_samples.txt --shifts None --friend-name fake_factors_v1 --production-tag 01_2024_nmssm_nominal_v5 --workers 40 --scopes mt,tt

The bug occurs if I try to run the same ProduceFriends command again. I'm certain that all job finished successfully and produced the friend root files. So the expectation would be in the second run nothing should happen.
But for each sample one single job is always resubmitted. Example for a diboson sample
15:55:17: all: 8, pending: 0 (+0), running: 0 (+0), finished: 7 (+7), retry: 1 (+1), failed: 0 (+0) - WW_TuneCP5_13TeV-pythia8_RunIISummer20UL18NanoAODv9-106X (Analysis: tau FriendConfig: nmssm_fake_factors Tag: 01_2024_nmssm_nominal_v5)
1 failed job(s) in task CROWNFriends_KingMaker____tau_3bc4820171:
    job: 2, branches: [1], id: dummy_job_id, status: retry, code: 0, error: unknown job id, log: None

It's not dependent on the number of all jobs for a sample, but I found that if I process friends for only one channel this is not happening and with 3 channel ("et","mt","tt") always 2 jobs are resubmitted.

Fixed with #32

authors: harrypuuter nshadskiy

repo: KIT-CMS/KingMaker

license: MIT

license_source: github-api


text:
🛑 KMHARS Main Fiber Line is down

In 585448b, KMHARS Main Fiber Line (het09022amj.sn.mynetname.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KMHARS Main Fiber Line is back up in 0919244 after 3 hours, 32 minutes.

repo: KMHARS/uptime


text:
いいところ診断の結果に優しさを追加したい

以下の結果を追加したい
'{userName}のいいところは優しさです。あなたの優しい雰囲気や立ち振る舞いに多くの人が癒やされています。'

これから対応します。

fe7ebdc で対応されました。

repo: KPLOVEPeach/assessment


text:
Create HarderSolarSystem-generic.netkan

This should be the last of my Harder Solar System config sets, for the foreseeable future at least.

Does this work with Kopernicus v0.5.2 ?

Yes, it's been tested with it.

That was what I wanted to hear :)
Merging

thanks!

source: gharchive/pull-request

repo: KSP-CKAN/NetKAN


text:
Create scikit learn tutorial_PT-BR.Rmd

First commit in the process of transalation of this material to brazilian portuguese.

The process of translation are

The scikit learn tutorial are translated to brazilian portuguese

That is my pleasure, Kacawi!!

repo: Kacawi/datacamp-community


text:
🛑 nHentai API is down

In 0c737bf, nHentai API (https://nh.usui.moe) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nHentai API is back up in f5a770c.

repo: Kadantte/candy-up


text:
Issue #59: Implement script/contract for random number generator

Closes #59
Create a contract RandomNumberGeneratorContract and it's tests.
The contract has 4 examples of how to generate random numbers:

get_random_number_with_block_data
get_random_number_with_keccak256
get_random_number_with_user_entropy
get_random_number_with_vrf & receive_random_words

The first 3 methods has an input that applies a bit of entropy to "ensure" randomness but are not recommended since such randomness is not verifiable.
The last method uses the Pragma VRF functionality to get the number. the get_random_number_with_vrf request a random number and the receive_random_words is the function used as callback by the VRF contract to return the random number.
I'm attentive to any correction/question🚀🚀

@jorgezerpa please send an image of your tests results to validate all of them are passing and it is working as expected 🫡

@coxmars Hello! I do it super fast🏃🏃

.tools-versions file added.
Here's the image:  of tests:

.tools-versions file added. Here's the image: of tests:

Awesome job sir, I will review it 🫡

@danielcdz Ready both changes sir!

authors: coxmars jorgezerpa

repo: KaizeNodeLabs/stark-cairo-nodes


text:
useLoader

Hi, I would like to make a PR with a fix for the useLoader attribute, which is a boolean that is later used as a conditional for the buildIndicator/circleprogressloader. How can I contribute to this repo so that other people may be able to use this in their flutter projects?

I am also expecting this feature.

This has been solved now
Thank you


text:
Adding aria tags

Hi,
I don't see any way to add aria tags to the <input/> element.
I need to add tags like:
aria-required
aria-describedby
aria-invalid
Is there a workaround?
Or should I make a PR for it?

Hi @hepiyellow  unfortunately there is no work around so please create a PR for that.

solved in v.2.3.11

authors: KarimMokhtar hepiyellow

repo: KarimMokhtar/react-drag-drop-files


text:
Add content to help page

This can be done after the advisory board meeting.
Content

Brief tutorial
FAQ

How do I contribute data?

Contact info for more questions

Tasks

Create directory and files for page in src/scenes/Help

src/scenes/Help/Help.js
src/scenes/Help/Helps.scss

Add to navigation in src/components/Header/Header.js
Import and add to router in src/index.js

What did you have in mind for the tutorial? Should I provide a specific example? I could add an example similar to what I presented for the demo, and use screenshots of the web pages to demonstrate it.

Yes, similar content to the presentation last week for the advisory board would work well. This would work well as screen shots.
When you make the screen shots, it may be helpful to zoom in with your browser so the text size is larger.
There's many browser plugins that make it easy to take screenshots. Example:
https://chrome.google.com/webstore/detail/nimbus-screenshot-screen/bpconcjcammlapcogcnnelfmaeghhagj?hl=en

done

FAQs still need to be added. I created a new issue for this (#204).

authors: jonrkarr yosefdroth


text:
Invisible activity is always created on background

When asking for permissions, the invisible activity is always created, this might cause some issues if Dexter is called from the onCreate or onResume methods of your own activity (as it will force another call to onCreate & onResume once the inner activity is dismissed). We should only create the inner Activity iff ActivityCompat.requestPermissions is going to be called.
For calling checkSelfPermission we should use the provided application context.

Duplicated #47

repo: Karumi/Dexter


text:
5.10.5 Uses compose on projects without it (cannot find symbol)

Expected behaviour
Should be able to assemble tests without depending on compose manually
Actual behaviour
/home/chris/git/.../OmegaInfoScreenActivityTest.java:53: error: cannot find symbol
androidx.compose.ui.test.SemanticsNodeInteraction node, @org.jetbrains.annotations.Nullable()
^
symbol:   class SemanticsNodeInteraction
location: package androidx.compose.ui.test/home/chris/git/.../OmegaInfoScreenActivityTest.java:59: error: cannot find symbol
androidx.compose.ui.test.junit4.ComposeTestRule rule, @org.jetbrains.annotations.Nullable()
^
symbol:   class ComposeTestRule
location: package androidx.compose.ui.test.junit4
Steps to reproduce
Gradle 7.0.2
ASG 4.2.1
Kotlin 1.5.10
Shot 5.10.5
@RunWith(AndroidJUnit4::class)
class OmegaInfoScreenActivityTest : ScreenshotTest {
}

Version of the library
Shot 5.10.5

Hey @chrisjenx could you please share your shot configuration? The plugin adds compose as a transitive dependency but it should be working on projects without compose installed. Actually, the sample projects in this repository show the plugin is working. Did you change something in your Shot config? Did you exclude compose dependencies?

Honestly not sure why it failed before, I upgraded again and now it works, guessing there was some caching issues...

I'm facing currently the same issue.
When I have the same Test dependencies, as in the sample project, all works good (except I can't set up Dagger injection for test.)
When I add
kaptAndroidTest("com.google.dagger:dagger-compiler:$daggerVersion")
and run tests, I get:
symbol:   class SemanticsNodeInteraction
  location: package androidx.compose.ui.test/Users/.../ProfileLegendFragmentTest.java:50: error: cannot find symbol
    androidx.compose.ui.test.junit4.ComposeTestRule rule, @org.jetbrains.annotations.Nullable()
                                   ^
  symbol:   class ComposeTestRule
  location: package androidx.compose.ui.test.junit4[WARN] Incremental annotation processing requested, but support is disabled because the following processors are not incremental: android.databinding.annotationprocessor.ProcessDataBinding (DYNAMIC).

Could you provide any info, please, how can I work around this?

@lyydikoi I had the same error. I will be able to fix it added ....
androidTestImplementation "androidx.compose.ui:ui-test-junit4:1.0.0-beta03"
@pedrovgs is it possible that the plugin doesn't add the compose as a transitive dependency?

@josehector Shot adds ` implementation "androidx.compose.ui:ui-test-junit4:1.0.0-beta03"`` as a transitive dependency. If you check the sample projects it should work out of the box.

authors: chrisjenx josehector lyydikoi pedrovgs

repo: Karumi/Shot


text:
Only listen to keyboard events on div, and add indicator for it.

Fairly straightforward changes to only listen to wrapping div. The more complicated part of this is adding a keyboard-indicator to show whether the glift box currently has focus.
I wasn't sure of the best way to pass this.statusBar object into the initKeybindingListener.  This feels a little janky, let me know how you'd like it.
Screenshots on http://localhost:9080/htmltests/GameViewerTester.html
Keyboard shortcuts active:

Keyboard shortcuts not active:

Also I really like the wikimedia keyboard asset more, but I couldn't figure out how to get the string representation to work?

  // From Wikimedia: https://commons.wikimedia.org/wiki/File:Keyboard-icon_Wikipedians.svg
  'keyboard-indicator-wikimedia': {
    string: "M43.614,63.057c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h57.662 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H43.614z M106.031,63.057c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h14.85 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H106.031z M24.146,63.057c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h14.85 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H24.146z M54.132,52.677c0,0-0.647,0-0.647,0.647v5.624c0,0,0,0.648,0.647,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H54.132z M43.752,52.677c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.647-0.647-0.647H43.752z M24.146,52.677c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h14.85 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H24.146z M64.512,52.677c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.647-0.647-0.647H64.512z M74.892,52.677c0,0-0.647,0-0.647,0.647v5.624c0,0,0,0.648,0.647,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H74.892z M85.271,52.677c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.647-0.647-0.647H85.271z M95.651,52.677c0,0-0.647,0-0.647,0.647v5.624c0,0,0,0.648,0.647,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H95.651z M106.031,52.677c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h14.989 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.647-0.647-0.647H106.031z M49.519,42.297c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H49.519z M39.139,42.297c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H39.139z M24.146,42.297c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h10.237 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H24.146z M59.898,42.297c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H59.898z M70.278,42.297c0,0-0.647,0-0.647,0.647v5.624c0,0,0,0.648,0.647,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H70.278z M80.658,42.297c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.647-0.647-0.647H80.658z M91.038,42.297c0,0-0.647,0-0.647,0.647v5.624c0,0,0,0.648,0.647,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H91.038z M101.418,42.297c0,0-0.648,0-0.648,0.647v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.647-0.647-0.647H101.418z M111.798,42.297c0,0-0.647,0-0.647,0.647v5.624c0,0,0,0.648,0.647,0.648h9.222 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.647-0.648-0.647H111.798z M74.635,31.916c0,0-0.647,0-0.647,0.648v5.624c0,0,0,0.648,0.647,0.648h5.625 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.648-0.647-0.648H74.635z M64.537,31.916c0,0-0.647,0-0.647,0.648v5.624c0,0,0,0.648,0.647,0.648h5.625 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.648-0.647-0.648H64.537z M54.439,31.916c0,0-0.648,0-0.648,0.648v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.648-0.647-0.648H54.439z M44.342,31.916c0,0-0.648,0-0.648,0.648v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.648-0.647-0.648H44.342z M34.244,31.916c0,0-0.648,0-0.648,0.648v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.648-0.648-0.648H34.244z M24.146,31.916c0,0-0.648,0-0.648,0.648v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.648-0.648-0.648H24.146z M84.733,31.916c0,0-0.647,0-0.647,0.648v5.624c0,0,0,0.648,0.647,0.648h5.624 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.648-0.648-0.648H84.733z M94.832,31.916c0,0-0.648,0-0.648,0.648v5.624c0,0,0,0.648,0.648,0.648h5.623 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.648-0.648-0.648H94.832z M104.93,31.916c0,0-0.648,0-0.648,0.648v5.624c0,0,0,0.648,0.648,0.648h5.623 c0,0,0.648,0,0.648-0.648v-5.624c0,0,0-0.648-0.648-0.648H104.93z M115.027,31.916c0,0-0.648,0-0.648,0.648v5.624c0,0,0,0.648,0.648,0.648h5.624 c0,0,0.647,0,0.647-0.648v-5.624c0,0,0-0.648-0.647-0.648H115.027z",
    bbox: {"x":16.472,"y":24.500999999999998,"x2":128.693,"y2":77.39099999999999,"width":112.221,"height":52.88999999999999}
  },

It ends up looking fuzzy, and the code above doesn't have the keyboard outline.  When I include the keyboard outline:
# prefix `string`: with
'M19.712,24.501c0,0-3.24,0-3.24,3.24v46.41 c0,0,0,3.24,3.24,3.24h105.741c0,0,3.24,0,3.24-3.24v-46.41c0,0,0-3.24-3.24-3.24H19.712z'

It just turns into a filled box on the statusBar--- i imagine b/c the actual svg draws it as a line, not as a fill.  Oh well.  Documenting incase an SVG enthusiast wants something to do.

And now that we have a keyboard indicator, we make a click on it show the list of shortcuts to solve https://github.com/Kashomon/glift/issues/112 for @amj

I haven't forgotten about this -- I'm still thinking about the design. Thanks for the patch. I'll get back to you in a bit.

Of course, let me know if there's anything I can do.

authors: Kashomon pconerly

repo: Kashomon/glift


text:
Power (^) doesn't support decimals.

Power of 2, 3, etc. will work, but anything like 1.7 or 0.5 will do nothing. This means that sqrt() is actually not working.
I have mostly fixed this, but not quite. I can get decimals of 0.5 to work, 0.5, 1.5, etc. will work. Anything like 0.6 or 0.4 will not however.

Another issue with power is that it doesn't support negative powers. The solution is just to divide instead of multiply in the power function, but I'd like to fix this issue before fixing negative powers.

This issue has been fixed. The entire loop has been replaced with first^power, second*power.
I tried this solution before, but it was giving incorrect results and I tossed it.
Turns out its correct, but the way I handle numbers was a problem that wasn't run into before.
Before I believed something like {2.5, 1.3} (2.5 * 10^1.3) just needed to be floored to {2.5, 1} and the answer would be correct. This was never a problem because second was never getting decimals.
This new power solution however would give second with a decimal. And because I was just flooring it out, first was wrong and so I thought it was wrong.
Turns out if you want to get rid of the decimal in second, you multiply first by 10^(second % 1). second % 1 will give us just the decimal of second. 25.532 % 1 = 0.532.
This is the code that uses the above
	first = tonumber(first)

	if second % 1 > 0 then
		first *= 10^(second % 1)
	end

	second = math.floor(second)

This will fix the number correctly (second having decimals is mathematically fine, but the module was built around not allowing it).

repo: KdudeDev/InfiniteMath


text:
Implemented a to_fits() method

I've added a to_fits() method to KeplerLightCurve. I have made it a general method of LightCurve and had KeplerLightCurve implement it with additional header keywords for instrument, detector and mission. I've also added some unit tests and a tutorial for how to write out a fits file.

Codecov Report

Merging #147 into master will decrease coverage by 0.08%.
The diff coverage is 89.58%.

@@            Coverage Diff             @@
##           master     #147      +/-   ##
==========================================
- Coverage   92.32%   92.24%   -0.09%
==========================================
  Files          17       17
  Lines        2189     2282      +93
==========================================
+ Hits         2021     2105      +84
- Misses        168      177       +9

Impacted Files
Coverage Δ

lightkurve/lightcurvefile.py
95% <100%> (+0.17%)
:arrow_up:

lightkurve/tests/test_lightcurve.py
97.82% <100%> (+0.13%)
:arrow_up:

lightkurve/targetpixelfile.py
89.02% <100%> (+0.02%)
:arrow_up:

lightkurve/lightcurve.py
91.36% <86.48%> (-0.81%)
:arrow_down:

Continue to review full report at Codecov.

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

@mirca what do you think of this PR?

This looks great to me 👍 ! I wonder if at some point we would like to have a FITSFactory class, but let's not worry about that in this PR; food for thought.

authors: christinahedges codecov-io mirca

repo: KeplerGO/lightkurve


text:
Incorrect keycaptures

Description
Some keybinding seem to be not working with neovide and some have wrong effects.
Problems:

Switching between panes in xmonad inputs text to neovide (when switching back to neovide pane whilst in insert mode). Text entered: <D-2><D-1>. The switching is done with Super+nr so I supposed neovide captures these key presses whilst terminal does not. <D-2> is switching to pane 2 and  is switching back to pane where neovide is eg pane 1.
Ctrl+Shift+V paste from system keyboard seems to be not working. It only enters ^ or V (it cycles between them eg pressing compo 2 times in a row becomes ^V)
After switching panes (the issue above) exiting insert mode with Esc duplicates line n times. The amount of times seems to be different every time but I suspect it is dependent on amount of time Esc held down. NB: I have CAPS and ESC swapped wit setxkbmap, so I am pressing CAPS on physical keyboard. It happens in a way that first Esc press does nothing and second press duplicates. It might be that this gets solved if the issue above is solved...

Screenshots

Line 1 is me switching between panes when in insert mode.
Line 2 is me trying to paste with Ctrl+Shift+V in insert mode and then exit inset mode.
Next I wrote aaa, then switched between panes and then tried to exit insert mode causing this repetition.
Desktop:

Please run neovide --log and paste the results here:
neovide --log
Ignored client type property: "methods"
Ignored client type property: "attributes"

Additional context
I noticed the repetition bug didn't happen when running neovide from terminal, but it does when I run it from dmenu. Pretty sure it's not a issue with dmenu / xmonad as everything works fine in terminal nvim.
Also I have en keyboard map

Issue 1 is fixed in main. Please test it
Issue 2 is not a bug. Terminal nvim displays the same behavior. I believe this is a feature of your terminal emulator and is out of scope
Issue 3 I thiiink may be a subset of the issue 1. Can you try main?
If these aren't fixed please reopen this issue.

authors: Kethku kilpkonn

repo: Kethku/neovide


text:
Add a wiki: Satisfactory

Link to origin wiki: https://satisfactory.fandom.com
Link to destination (independent) wiki: https://satisfactory.wiki.gg

Added in v3.3.0. Thanks for the submission!

authors: KevinPayravi rgooler

repo: KevinPayravi/indie-wiki-buddy


text:
Remove redundant assignment

Seems to be a small typo

Thanks, but that is needed for self to be initialized before setting it for real 🙃

Huh? I don't understand? Where is self needed?

Ah, for getting context. I'm passing context as a parameter instead in my local branch because it gave me some trouble as an EnvironmentObject
https://github.com/KeyboardKit/KeyboardKit/issues/321

Yeah, I don't like this way of having to init with fake data to then be able to setup the real value. I'd like to find a way around it :)

Btw, if you pass the context around as a parameter, how do you set it up for the view to update when things in the context changes?

authors: danielsaidi digitalheir

repo: KeyboardKit/KeyboardKit


text:
added translations for locale de_DE

Hey, we've update German translations, i.e. de_DE.

Many thanks, change merged!

Great, thanks for the extension! Best, Matthias
On 23 September 2015 at 13:54, Vojta Grec notifications@github.com wrote:

Many thanks, change merged!
—
Reply to this email directly or view it on GitHub
https://github.com/Keyup/Magento-MassShipment/pull/2#issuecomment-142577474
.

authors: both-interact vojtagrec

repo: Keyup/Magento-MassShipment


text:
Setting the SUPERUSER_REALM makes admin access unusable

Describe the bug
When setting the SUPERUSER_REALM environment variable, it is not possible to login to the administrative view.
To Reproduce

Set up a container without the SUPERUSER_REALM environment variable, and verify its working.
(optional) Create a second realm in the admin panel, you want to use for administrative purposes, e.g. an 'api' for automating PI using their rest API.
Setting the env variable SUPERUSER_REALM=['administrator','api']  and restart the container
When logging in with an user in the admin realm, the user doesn't have the admin UI anymore, but only the user UI.

Also trying "['administrator','api']" or \['administrator','api'\] hasn't helped.
As a dirty hack: If you set SUPERUSER_REALM = ['administrator','api'] by hand in the /etc/privacyidea/pi.cfg file inside the container, it works.
Expected behavior
Login with a user in the admin realm still works and you have a working admin realm, for which e.g. in the policy section of the configuration tab, you could select in admin policies the realm 'api'.
Environments (please complete the following information):

OS: Debian 12 hosting the Container
Browser: Firefox 115ESR
PI version or image tag v3.9-patch1
Database postgresql

Additional context
I think, the problem lies in the rootfs/opt/templates/pi-config.template in line 15 as the environ to my knowledge returns strings and the default value is an list.

@camelusferus thank you for reporting the issue and sorry for the late response. I'll check on this.

@camelusferus please verify if the latest release fix the issue.

@mr-ssd I am sorry, but all builds from today on the docker hub wont even start in my environment.
All result/errors I got from a docker-compose setup with the tag v3.9.1-d1.1.0. If I dont set a SUPERUSER_REALM, the pi_cfg script crashes on the trimming of quotes on the default values a list:
privacyidea_1  | Traceback (most recent call last):
privacyidea_1  |   File "/opt/privacyidea/bin/pi-manage", line 113, in <module>
privacyidea_1  |     app = create_app(config_name='production', silent=SILENT)
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/privacyidea/app.py", line 133, in create_app
privacyidea_1  |     app.config.from_pyfile(config_file, silent=True)
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/flask/config.py", line 132, in from_pyfile
privacyidea_1  |     exec(compile(config_file.read(), filename, "exec"), d.__dict__)
privacyidea_1  |   File "/etc/privacyidea/pi.cfg", line 22, in <module>
privacyidea_1  |     if SUPERUSER_REALM.startswith(delimiter) and SUPERUSER_REALM.endswith(delimiter):
privacyidea_1  | AttributeError: 'list' object has no attribute 'startswith'

When I set a list of SUPERUSER_REALM's, the pi-manage script crashes, by a typo in then sqlalchemy URL:
privacyidea_1  | Traceback (most recent call last):
privacyidea_1  |   File "/opt/privacyidea/bin/pi-manage", line 1739, in <module>
privacyidea_1  |     manager.run()
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/flask_script/__init__.py", line 417, in run
privacyidea_1  |     result = self.handle(argv[0], argv[1:])
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/flask_script/__init__.py", line 386, in handle
privacyidea_1  |     res = handle(*args, **config)
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/flask_script/commands.py", line 216, in __call__
privacyidea_1  |     return self.run(*args, **kwargs)
privacyidea_1  |   File "/opt/privacyidea/bin/pi-manage", line 589, in create_tables
privacyidea_1  |     print(db)
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/flask_sqlalchemy/__init__.py", line 1115, in __repr__
privacyidea_1  |     self.engine.url if self.app or current_app else None
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/flask_sqlalchemy/__init__.py", line 998, in engine
privacyidea_1  |     return self.get_engine()
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/flask_sqlalchemy/__init__.py", line 1017, in get_engine
privacyidea_1  |     return connector.get_engine()
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/flask_sqlalchemy/__init__.py", line 592, in get_engine
privacyidea_1  |     sa_url = make_url(uri)
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/sqlalchemy/engine/url.py", line 738, in make_url
privacyidea_1  |     return _parse_url(name_or_url)
privacyidea_1  |   File "/opt/privacyidea/lib/python3.8/site-packages/sqlalchemy/engine/url.py", line 799, in _parse_url
privacyidea_1  |     raise exc.ArgumentError(
privacyidea_1  | sqlalchemy.exc.ArgumentError: Could not parse SQLAlchemy URL from string '=postgresql+psycopg2://DB_USER_REDACTED:DB_PW_REDACTED@DB_HOST_REDACTED:5432/DB_NAME_REDACTED'

@camelusferus could please share your docker-compose you we can test it on the same environment? Meanwhile, if you have an idea to fix it that is also welcome.

@camelusferus thank you for the PR and please consider starring ⭐ to help it reach more people and get more feedback like this.

authors: camelusferus mr-ssd

repo: Khalibre/privacyidea-docker


text:
Widehat

Great work....it will be great to have this working (don't ask me how) ...
\widehat{asdfghjklmnbvcxz}
Suki

closing as duplicate of https://github.com/Khan/KaTeX/issues/407.

authors: Sukii kevinbarabash

repo: Khan/KaTeX


text:
Fix texcmp issues related to bit depth and kerning

Ensure bit depth 8
Print affected file if PNG failed to read (e.g. due to wrong bit depth)
Disable running Kern test case through TeX as doing so fails

Changes look good.  Were some of the PNGs being output with 16 bits per channel?

Using my local TexLive 2016 I indeed saw some 16 bps files. Don't remember which ones.

authors: gagern kevinbarabash


text:
Astc metrics tests

Updates tests for compare-psnr and compare-ssim to include ASTC as well.

@MarkCallow please review and merge this.

These were in previous PR #33 that are already merged.

Ahhh! Sorry I forgot that.

authors: MarkCallow abbaswasim wasimabbas-arm

repo: KhronosGroup/KTX-Software-CTS


text:
spirv-val does not validate that OpPhi instructions start the block correctly.

The check that an OpPhi is at the start of the basic block that it is contained in is not correct.
Here is an example that it gets it wrong:
               OpCapability Shader
          %1 = OpExtInstImport "GLSL.std.450"
               OpMemoryModel Logical GLSL450
               OpEntryPoint Fragment %2 "main"
               OpExecutionMode %2 OriginUpperLeft
               OpSource GLSL 400
          %3 = OpString "t.frag"
       %void = OpTypeVoid
          %5 = OpTypeFunction %void
        %int = OpTypeInt 32 1
      %int_0 = OpConstant %int 0
       %bool = OpTypeBool
       %true = OpConstantTrue %bool
      %int_1 = OpConstant %int 1
          %2 = OpFunction %void None %5
         %11 = OpLabel
               OpSelectionMerge %12 None
               OpBranchConditional %true %13 %12
         %13 = OpLabel
               OpBranch %12
         %12 = OpLabel
         %14 = OpUndef %int
               OpLine %3 1 1
         %15 = OpPhi %int %int_0 %11 %int_1 %13
               OpReturn
               OpFunctionEnd

ValidateAdjacency is only check the immediately previous instruction to an OpPhi. This check should be reworked.

Rebased and pushed into master as f0aa6f4e3a57d428725ef91b7005bb4371d78155

authors: alan-baker jaebaek s-perron

repo: KhronosGroup/SPIRV-Tools


text:
build: Update to header 1.2.195

Update known-good
Generate source

CI Vulkan-Tools build queued with queue ID 47178.

CI Vulkan-Tools build # 535 running.

authors: ci-tester-lunarg mikes-lunarg

repo: KhronosGroup/Vulkan-Tools


text:
Research possibility to speed up import of KHR_materials_specular

Import of glTFs using the KHR_materials_specular extension is rather slow.
The zip available from https://www.dropbox.com/s/fg0bpd3yy7tnoc0/KHR_materials_specular_slowness.zip?dl=0 contains two GLBs, one with and one without KHR_materials_specular (each ~300MB).

file without KHR_materials_specular: 10.34s
file with KHR_materials_specular      : 48.55s

I guess this is expected due to the need to create in memory textures etc.
Still, it would be great if the import speed could be optimized if possible.
Specs:

Blender 3.6 - c7fc78b81ec
Windows 11 Pro
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz   2.21 GHz
32.0 GB RAM

Blender 4.0 beta has now a totally new specular model, where conversion is no more needed.
So this bug/perf request is no more relevant.
Closing

authors: julienduroure timknip

repo: KhronosGroup/glTF-Blender-IO


text:
Some appearance can be improve.

Problems
On the title A-Levels is not the same as the choices below.

Minor capital letter mistake.

There are some duplicate faculty which there are no context of why the score is not the same since it's the same faculty and criteria.

There is a blank space between 00 and 01 which I don't know if it's intentional.

I can confirm that the extra duplicate faculties are not intended. I will also be fixing the grammatical mistakes as well. As for the time wheel I will have @BioB3 look into it.

Can you provide some information on what browser, browser version, and OS you are currently using?

The blank space between 00 and 01 is browser-based since we use datetime-local input. The control's UI varies from browser to browser (provided below), in some browsers with no support, the input field is just a text input. So this is intentional.
Microsoft Edge Version 131.0.2903.63

Mozilla Firefox Version 132.0.2

I suspected that the duplicate faculty can be because of KU has different Engineering faculties in different campus, as we doesn't separated faculties by campus.  One potential way to fix this is just locked it to Bang Khen campus but I will discuss this with the team first.

authors: BioB3 Jangsoodlor KhunakornP SariyaP

repo: KhunakornP/A-plus-management


text:
Is it suit for other translation model like "Helsinki-NLP / opus-mt-en-de"?

Is it suit for other translation model like "Helsinki-NLP / opus-mt-en-de"?

sorry, it only supports T5 architecture.


text:
🛑 FSDH INT is down

In 8cf862a, FSDH INT (https://fsdh-portal-app-int.azurewebsites.net/register) was down:

HTTP code: 503
Response time: 2771 ms

Resolved: FSDH INT is back up in 54ba4fd after 8 minutes.

repo: KingBain/proto-datahub-uptime


text:
🛑 FSDH INT is down

In 7938393, FSDH INT (https://fsdh-portal-app-int.azurewebsites.net/register) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FSDH INT is back up in 856e67e after 22 minutes.


text:
🛑 FSDH INT is down

In ed03f97, FSDH INT (https://fsdh-portal-app-int.azurewebsites.net/register) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FSDH INT is back up in c98ba39 after 33 minutes.


text:
set Playwright actionTimeout to 15 seconds

Playwright global config change to prevent exceedingly long timeouts when certain actions fail
e.g. button click

Or maybe we need to figure out why these tests need so long?

I'm afraid this change won't address those particular issues yet.  This will only tweak the test execution so that tests fail faster - (so I dont have to wait too long when rerunning builds).
Currently, actionTimeout is not specified, when a test fails on a particular action
e.g. clicking a button that is not ready to be clicked.
It will fallback to the test timeout (2 minutes)
I've also pushed some changes to:

enable the html report, this will give insight into which tests are slow.
enable screenshot on failure - for some reason the canvas does not render the lines in tracefiles.  Hoping the screenshot will capture the state of the canvas on failure

Okay, well I'm not sure exactly what's happening, but these 4 are consistently failing on this branch

So they must be related right, I've tried re-running the tests to make sure it's not a fluke.

some progress, I'm getting a different failure now after my most recent commit.  The most recent failure is on my list to fix.
  1) [webkit] › flow-tests.spec.ts:4165:7 › Sketch tests › Can delete most of a sketch and the line tool will still work

    Error: Timed out 10000ms waiting for expect(locator).toBeVisible()

    Locator: locator('[data-message-type="execution-done"]').last()
    Expected: visible
    Received: <element(s) not found>
    Call log:
      - expect.toBeVisible with timeout 10000ms
      - waiting for locator('[data-message-type="execution-done"]').last()

       at test-utils.ts:49

      47 |
      48 | async function expectCmdLog(page: Page, locatorStr: string, timeout = 5000) {
    > 49 |   await expect(page.locator(locatorStr).last()).toBeVisible({ timeout })
         |                                                 ^
      50 | }
      51 |
      52 | async function waitForDefaultPlanesToBeVisible(page: Page) {

        at expectCmdLog (/Users/runner/work/modeling-app/modeling-app/e2e/playwright/test-utils.ts:49:49)
        at Object.expectCmdLog (/Users/runner/work/modeling-app/modeling-app/e2e/playwright/test-utils.ts:254:7)
        at /Users/runner/work/modeling-app/modeling-app/e2e/playwright/flow-tests.spec.ts:4200:13

I'll work on that first

Oh cool!
I think the failing macos playwright tests are related seeing some errors like TimeoutError: page.waitForEvent: Timeout 15000ms exceeded while waiting for event "console"
15000ms makes me think it's this. Should we increase the timeout? or increase it just for these tests?

I've extended the timeout for this particular call:
https://github.com/KittyCAD/modeling-app/pull/3115/commits/53fb96519de58d37cf6fbfaec1bbee0dea4e2171

https://github.com/KittyCAD/modeling-app/pull/3115#issuecomment-2257178830
^ these failures are longer occuring

authors: Irev-Dev ryanrosello-og

repo: KittyCAD/modeling-app


text:
Cut release v0.26.1

What's Changed

Disable rotate on start new sketch (#4287)
Stop propagation of camera clicks after drags (#4257)
Rename Sketch.value to Sketch.paths (#4272)
Fix engine connection break when starting onboarding from a fresh install (#4263)
Support negative start and end in ranges (#4249)
Remove setInterval implementations from camera controls (#4255)
Fix job name for printers (#4234)
Buffer file writes, because writing to file after every keypress has bad consequences (#4242)

Full Changelog: https://github.com/KittyCAD/modeling-app/compare/v0.26.0...v0.26.1

[ ] coredump will open github issue with stuff populated (from home and project page) there are different ways to trigger it as well (! button at top, bug at bottom, mod + shift + .)
[ ] running app.{app,exe} path/to/file opens the kcl file (all oses)
[ ] running app.{app,exe} path/to/dir opens the directory and any kcl file in it or creates a main.kcl if empty (all oses)
[ ] If someone at the office, test you can hit make from the app and it works
[ ] Test updating versions works
[ ] until we have a performance test, sanity check that time to open file directly from command line is not shit
[ ] Electron tests: ensure we can open files that in tauri we would not be able to #3455
[ ] Electron test: upgrading app should not cause user to have to auth again #3469
[ ] Electron: logging in and authing works #3465
[ ] double click to open files from finder opens new window each time (mac/windows)
[ ] export from the app works and opens a file picker ux (needs to be manual since we override for playwright)
[ ] Ensure that a loading toast appears when testing the auto-updater, saying the download has begun
[ ] Token.txt should work #4038

Linux cleared
Manual Tasks

[x] Mash keyboard in the code editor
[x] https://github.com/KittyCAD/modeling-app/issues/3373
[x] coredump will open github issue with stuff populated (from home and project page) there are different ways to trigger it as well (! button at top, bug at bottom, mod + shift + .)
[x] running app.{app,exe} path/to/file opens the kcl file (all oses)
[x] running app.{app,exe} path/to/dir opens the directory and any kcl file in it or creates a main.kcl if empty (all oses)
[ ] If someone at the office, test you can hit make from the app and it works
[x] Test updating versions works
[x] until we have a performance test, sanity check that time to open file directly from command line is not shit
[x] https://github.com/KittyCAD/modeling-app/issues/3455
[x] https://github.com/KittyCAD/modeling-app/issues/3469
[x] https://github.com/KittyCAD/modeling-app/issues/3465
[ ] double click to open files from finder opens new window each time (mac/windows)
[x] export from the app works and opens a file picker ux (needs to be manual since we override for playwright)
[x] Ensure that a loading toast appears when testing the auto-updater, saying the download has begun
[x] https://github.com/KittyCAD/modeling-app/issues/4038

Updater test on Mac passed after reverting #4270  and updating the release branch.


text:
Modal closes and reopens in Android when an input is selected/tapped

Summary
We have created a login form on a modal using this library. Only in Android, modal closes and reopens as soon as user selects/taps any of the available inputs on the form.
Description
I was wondering if anyone has had issues with interacting with the modal in Android. We have created a login form on a modal using this library. It works perfect across all browsers on desktop/iOS, but unfortunately we've faced an issue in Android. Pretty much any device any browser on Android. Our login form has logo, some text, an email address input, a password input, remember email checkbox, forgot password? link, and login button.
In Android, modal opens successfully. But as soon as user clicks/taps the email address / password input, the modal closes and opens again. And this happens over and over again. As a result user cannot enter anything into the inputs.
I wish I could share a link where this is happening. Unfortunately for legal reasons cannot share. But I have included the code to the modal at below.
I would greatly appreciate a help on this.
I did a lot of research and was responsible for finding a great library to handle modals on our projects. I picked this library because it is reliable, accessible, small, fast with great documentation and support on github.
Thank you

            <button class="dialog-close" type="button" data-a11y-dialog-hide aria-label="Close dialog">
                ×
            </button>

<sj:message key="Log In"/>

            <form id="test-login-form" name="test-login-form" method="post">
                <fieldset class="screen-reader-fieldset">
                    <legend></legend>

                        Email address
                        <input id="login-email" class="d-input" autocomplete="username" required="required" type="email" />

                        Password

                            <input id="login-password" class="d-input" type="password" autocomplete="current-password" required="required" name="login-password" value="" />
                            <button class="show-hide-password masked" title="Click to show your password" aria-label="Click to show your password" type="button">

                            </button>

                </fieldset>

                        <input class="login-remember-username-checkbox" type="checkbox" name="login-remember-username" id="login-remember-username" />

                            <sj:message key="Remember Email"/>

                    <button id="forgot-password" class="btn-link" type="button" ><sj:message key="Forgot Password?"/></button>

                    <button id="login-button" class="login-button btn btn-primary" type="submit">Log In</button>

            </form>

Forgot Password

Check your email.

Hello Kitty!
Thank you for your prompt response. Exactly! I couldn't reproduce it on an Android phone either using the official demo for for a11y-dialog!
Thanks again for the help.

Hello again. :)
So I put your code on a CodeSandbox. I instantiated the dialog with JavaScript, since you don’t use the data-a11y-dialog attribute on the dialog — I assume you do the same.
I tried on my Android phone (Pixel 5, Android 12, Firefox) and things seem to work as expected. I can open the dialog, focus the fields, type things in, close the dialog. I unfortunately cannot reproduce the problem you described. :(
So I guess there is something more in your setup that’s causing this to happen. It could be a number of things unfortunately, so pretty hard to track without having a reproducible test case. Ideally you can create a version on CodeSandbox that comes close to what you have in production, CSS and JavaScript included. And then I’ll be happy to spend more time on it. Sorry I couldn‘t figure out so far!

Thank you very much for the time you put into this. I would definitely do that and will update you.

Please do! I hope we can figure it out. :)

Finally, I was able to figure out what’s causing the issue. The root cause was not definitely from the A11y-Dialog library but it was something that impacted modal behavior.
In my example the Login Component (The modal and the link to the modal) is initially in the header. And there is an event listener for window.resize, that if the screen gets below 600 width, it moves the component to the main.
It seems that on Android, the soft keyboard changes the visual viewport and triggers the resize event and as a result it made the modal to refresh. In other words On Android the problem was that it was doing this repositioning everytime the window resizes. I guess most browsers don't perform the action because the element already was there but Android devices actually reloaded the code everytime the keyboard was presented.
I created this CodeSandbox if you'd like to explore.
Thanks again for your help on this.

Hello Tahmoores!
I recall reading something about the keyboard triggering resize events on Android, but I would have not been able to make the connection with our bug. Very nice find! I would argue there is therefore nothing to fix on a11y-dialog itself?
Ideally you maintain the position of the dialog so it doesn’t move around the DOM based on the viewport size? Or you keep track of its status so you persist it once moved (for instance, if it was open before moving, you keep it open after).
Cheers!

authors: KittyGiraudel tmazhari


text:
Update package and resource references

from IBM-Swift to Kitura

@fouadhatem Looks like one of the unit tests is failing due to the architecture text changing for Linux.  ("x86_64-unknown-linux-gnu" to/from "x86_64-unknown-linux").  Do you want to take a hand at updating the unit test to address this?
 /home/travis/build/Kitura/FileKit/Tests/FileKitTests/FileKitTests.swift:20: error: FileKitTests.testExecutablePathResolution : XCTAssertEqual failed: ("["FileKit", ".build", "x86_64-unknown-linux-gnu", "debug"]") is not equal to ("["FileKit", ".build", "x86_64-unknown-linux", "debug"]") -

repo: Kitura/FileKit


text:
Following gettings started steps in README gives me to "NO SSH connection to target" error

I've tried having a working Meterpreter reverse_tcp shell open in parallel to Backdoorme too, but it doesn't help neither.
So currently this program is unusable, sadly (or readme is incomplete).
Thanks!

The readme is only about getting Backdoorme ready. It still requires a target to backdoor, without it, no connection can be made.

Yes: I said I have a linux/x64/meterpreter/reverse_tcp session open and working.

Just having a meterpreter session isn't enough - does the target have SSH open?
It'd be an interesting next step to have this working over meterpreter.

Um, no, it hadn't SSH open. Ok, then.
Thanks!

repo: Kkevsterrr/backdoorme


text:
Neue Firmware  , Problem mit Auslesen

Die neue Firmware STC8-2022-218 hat laut https://secondlifestorage.com/index.php?threads/limiter-inverter-with-rs485-load-setting.7631/post-82148 Probleme mit den Statusmeldungen

du kannst das ja selber testen mit usb rs485 schick die 24 und 7 *0 bytes  und schau ob was kommt
wann nicht , pech gehabt
versuch ein anderes rs485 modul und einen nativen esp12

Ich habe auf zwei Soyos diese Firmware und beide melden dem ESP die DC Werte zurück.

@B230FK Sind es Soyos mit oder ohne Display (WiFi Dongle)?

authors: B230FK KlausLi helgeschneider syssi

repo: KlausLi/Esp-Soyosource-Controller


text:
Support retirement of unpooled tokenized carbon

e.g. TCO2, C3T should be able to be retired directly rather than just pool token

This is resolved in the V2 Infinity Diamond. Both RetireC3C3TFacet and RetireToucanTCO2Facet accomplish this for C3 and Toucan

repo: KlimaDAO/klimadao-solidity


text:
Migrate domain and apply redirects

[ ] In DNS settings remove the vercel deployment and point the url at wix

In wix or in DNS we need to assign redirects:

[x] Redirects from klimadao.finance to carbonmark:

klimadao.finance/retirements/[address] -> carbonmark.com/retirements/[address]
klimadao.finance/retirements/[address]/[retirement_index] -> carbonmark.com/retirements/[address]/[retirement_index]
klimadao.finance/pledge/[address] -> carbonmark.com/users/[address]
klimadao.finance/infinity -> carbonmark.com

[ ] Internal redirects

blog/[id] -> /page/[id]

@Atmosfearful

Confirmed all those redirects, aligned.

This can proceed when #1720 is closed

@Atmosfearful
this redirect klimadao.finance/pledge/[address] -> carbonmark.com/users/[address]
should be klimadao.finance/pledge/[address] -> carbonmark.com/retirements/[address]

All redirects should be working now.
https://klimadao.finance/pledge/atmosfearful.klima
https://klimadao.finance/retirements/atmosfearful.klima
https://klimadao.finance/retirements/atmosfearful.klima/2
https://klimadao.finance/infinity
https://www.klimadao.finance/blog/public-goods-for-the-good-of-the-planet

repo: KlimaDAO/klimadao


text:
Angular 2 Support

Do you guys already have an official plan for supporting Angular 2?  I'm planning to work on integrating this on an Angular 2 project.

Hi @bangonkali Angular 2 isn't on our roadmap at the current time. However, we can assist with any questions you may have during your integration.

Another vote for Angular support for the File Explorer.

@jenkinshouse noted! I'll bring it up internally.

authors: bangonkali jenkinshouse vinodc

repo: Kloudless/file-explorer


text:
Update core to use dotnet

Update core to use dotnet, but I'm not sure is it correct, please check it.

Thanks! I will get to this in the next few weeks - seems that at least the appveyor build has to be reconfigured to support this change.

@Knagis Done.

The modified build does not execute the unit tests. Note that there are 4 failing tests right now on master.
Also I'm guessing that you discovered that appveyor does not yet support .NET Core builds natively - perhaps there is a ticket or issue registered somewhere that you could reference in the build script so that in the future it can be revisited to perhaps switch to native build instead of the external download.

No answer from the PR author 😦

authors: Jeffiy Knagis


text:
Integrate plugins with Gradle composite build in Stack

https://docs.gradle.org/current/userguide/composite_builds.html

Duplicate #13.

repo: Knotx/knotx-gradle-plugins


text:
Add a website regarding the online driving license in Nepal

Pull Request: Adding New Governmental Website for Driving Licenses
Description
This pull request proposes the addition of a new government website related to driving licenses to the repository.
Changes Made

Added the new government website details to the repository:

Name: Transport Management Office, Driving License, Thulobharyang.
URL: http://thulobharyanglicense.bagamati.gov.np/
Description: The Transport Management Office, Driving License, Thulobharyang, is responsible for new driving license issuance, including additional categories, as well as license renewal and verification. It also oversees trial examination centers, ensuring high-quality testing standards.

Added the new governmental website details to apply for the online driving license.

Name: "Online Driving License System"
URL:  "https://applydl.dotm.gov.np/"
"Description": "The Online Driving License System is a web application providing services related to driving license registration and operation. It is a part of the Transport Management Information System (TMIS) developed by the Department of Transport Management (DoTM)."

Please review this pull request and consider merging it into the main project repository. If any further adjustments are needed or if you have any feedback, please let us know. Thank you for your consideration.

Thank you for your contribution @purnasth!

authors: purnasth thenishantsapkota

repo: Know-Nepal/government-websites


text:
Audiokommentare are following up one another

using Audiokommentar under chrome:

first audio comment is saved, shown and can be played
if button "verwerfen" is used and on retaking another audio comment, both of them are stringed together and played one after the other
the same is happening with all the audio comments recorded in one session
if I leave the session and login again, I start from the beginning

Fixed with #521 ... will be included in next release

Related to #500

Fixed with 0.9.42 release
@TaSpatzHfM this should be resolved now, you can go ahead and retest

repo: KoALa-MHF/koala-app


text:
Duplicating a routine can make routines have the same name

Project Builder prevents routines from having identical names by disabling the Back button in the Routine Builder screen if the routine is given the same name as another routine. But identical names can still be achieved by duplicating a routine.
Steps to reproduce:

Add a new routine.
Duplicate the routine.
Duplicate the same routine again.

Sometimes editing a routine with a non-unique name disables the Back button and highlights the name, and sometimes it doesn't.
On my machine the automatic filenames for copies are "name (copy 1)", "name (copy 2)", "name (copy 3)", etc. The same idea could be used for a fix.

c0c209a

I can still get it to make non-unique names.

Add routine (routine 1).
Duplicate routine 1 (routine 2).
Duplicate routine 1 (routine 3).
Delete routine 2.
Duplicate routine 1 (routine 4).
Duplicate routine 1 (routine 5).

Routines 3 and 5 will have the same name: "New Routine (Copy 1)"

authors: KoBeWi svetogam

repo: KoBeWi/Godot-Project-Builds


text:
Add dangerzone buttons and make button texts more intuitive

When hovering on buttons like Delete company

Looks good!

authors: FredrikAugust HakonHesselberg

repo: Kodeworks/liquidator


text:
Added support for new Philips Hue Outdoor Motion Sensor

Added support for the new Philips Hue Outdoor Motion Sensor

Thanks!

authors: Koenkk jonnycastaway

repo: Koenkk/zigbee-shepherd-converters


text:
LUMBER SPV server connection

@Lumberscout while testing LUMBER lite mode it appears that the electrum server is down

Issue resolved, closing

repo: KomodoPlatform/Agama


text:
Add 3.x upstream fields

Adds new upstream fields for 3.x.
Fix #734.
Requires a new go-kong release that includes https://github.com/Kong/go-kong/pull/200. Currently using a main hash.

Codecov Report

Merging #735 (6a98daa) into main (ec25b16) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #735   +/-   ##
=======================================
  Coverage   43.05%   43.05%
=======================================
  Files          74       74
  Lines        9016     9016
=======================================
  Hits         3882     3882
  Misses       4763     4763
  Partials      371      371

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter rainest

repo: Kong/deck


text:
grpc gateway decoding

structured URL args and timestamp transcoding

It appears to be for v2.6.x but I don't see a plugin version update. Was the plugin code updated?

Kong/kong#7538
Kong/kong#7564

If so why no version update.

this plugin has been imported into the main repo, and now it's released with the rest of Kong I'm not sure if we'll keep counting version numbers for them.

@HCloward Will not be merging this PR for the 2.6 release - we'll address this doc change in the coming 2.6.1 patch coming up.

This is now fixed in the release for 2.6 paving the way for this doc.

We are fixing this PR

authors: PaulFischer-Kong javierguerragiraldez


text:
fix(kic): correct curl --resolve option

Description
The --resolve option for curl only accepts an argument in the form {SOURCE IP}:{SOURCE PORT}:{TARGET IP}; a target port cannot be specified. The option --connect-to should be used instead as this can also accept a target port.
Additionally, if users have followed the KIC deployment instructions for minikube, the PROXY_IP variable will contain a URL including a scheme (e.g. http://127.0.0.1:12345); the scheme should be stripped from the variable before being passed to curl to avoid a parsing error.
Testing instructions
Netlify link:
https://deploy-preview-5772--kongdocs.netlify.app/
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

@mheap could you please let me know your preference between  --connect-to and --resolve option with curl.

Hi @steveatkonghq . I noticed that the issue you mentioned about Minikube deployment has been addressed in #5844. Before I validate the commands in the rest of the guides please let me know if they would still hold good.

@Rajakavitha1 Thanks, I'm happy that this PR has been addressed in #5844. I'm in favour of sticking with --resolve providing that the documentation is using this correctly, as it's in more common usage and more closely aligned to the intent of the command (overriding a local DNS resolution).

Hi @steveatkonghq . I noticed that the issue you mentioned about Minikube deployment has been addressed in #5844. Before I validate the commands in the rest of the guides please let me know if they would still hold good.

@Rajakavitha1 Thanks, I'm happy that this PR has been addressed in #5844. FWIW I'm in favour of sticking with --resolve providing that the documentation is using this correctly, as it's in more common usage and more closely aligned to the intent of the command (overriding a local DNS resolution).

Thank you @steveatkonghq  can we close this PR and yes, we will ensure that the usage is consistent across the documentation.

Closing this PR for now. Please feel free to reopen if any other issue needs to be addressed.


text:
feat: support setting custom headers

Currently to set request headers HTTPClientWithHeaders is used to configure an http.Client that injects headers on each request via a custom Transport. This is problematic when there is a desire to reuse the underlying http.Client. This PR adds support for capturing the desired headers when creating the Kong Client and then Do sets the headers.
If users are OK with a customized http.Client then they can continue using NewClient with HTTPClientWithHeaders. If they wish to share the underlying http.Client then they can use the new function NewClientWithHeaders.

Codecov Report
Attention: Patch coverage is 90.90909% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 59.49%. Comparing base (241dbb8) to head (31e1846).

Files
Patch %
Lines

kong/client.go
80.00%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #430      +/-   ##
==========================================
+ Coverage   59.32%   59.49%   +0.16%
==========================================
  Files          69       69
  Lines        4219     4241      +22
==========================================
+ Hits         2503     2523      +20
- Misses       1134     1135       +1
- Partials      582      583       +1

Flag
Coverage Δ

2.1
36.97% <45.45%> (+0.04%)
:arrow_up:

2.2
50.22% <90.90%> (+0.21%)
:arrow_up:

2.3
50.88% <90.90%> (+0.20%)
:arrow_up:

2.4
50.93% <90.90%> (+0.20%)
:arrow_up:

2.5
50.93% <90.90%> (+0.20%)
:arrow_up:

2.6
50.93% <90.90%> (+0.20%)
:arrow_up:

2.7
52.62% <90.90%> (+0.19%)
:arrow_up:

2.8
52.62% <90.90%> (+0.19%)
:arrow_up:

3.0
56.70% <90.90%> (+0.17%)
:arrow_up:

3.1
58.40% <90.90%> (+0.16%)
:arrow_up:

3.2
58.45% <90.90%> (+0.16%)
:arrow_up:

3.3
58.45% <90.90%> (+0.16%)
:arrow_up:

3.4
58.78% <90.90%> (+0.16%)
:arrow_up:

community
42.77% <45.45%> (+0.01%)
:arrow_up:

enterprise
58.02% <86.36%> (+0.14%)
:arrow_up:

integration
59.49% <90.90%> (+0.16%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

I would like to do something like this:
httpClient := &http.Client{
  // some configuration
}

for _, o := range konnectOrgs {
  headers := codeToGetAuthHeader(o)
  kongClient := kong.HTTPClientWithHeaders(baseURL, httpClient, headers)

  // Now manage some entities with kongClient
}

That is a simplified example, but I basically want a long lived http client object that I can reuse across kong clients as well as other HTTP based clients. I can't do this today since HTTPClientWithHeaders modifies the Transport. Another way to think of it is that I want custom headers tied to the kong client and not the http client.

Gotcha, what's the motivation for reusing the client for non-Kong requests? What's lost if you need to build the other clients separately
Sharing the http.Client for other purposes isn't something we really intended here--the go-kong client should be an opinionated collection of settings that are common across all requests to a particular Kong cluster.
We do expose the http.Client as an input but it's not clear why we do so instead of always building the client on behalf of the downstream application. My best guess is that we just didn't do a good job of refactoring delineation of responsibilities when we broke go-kong out into a library. If anything we'd want to make it more opinionated about the Transport configuration going forward.

authors: codecov-commenter rainest szesch

repo: Kong/go-kong


text:
updates README

closes https://github.com/Kong/httpsnippet/issues/249
So, since quite a lot has happened, it was time to overhaul the README.  Hopefully it reads much simpler now, and if not hopefully the newly added quickstart sections span that gap.
Preview it here: https://github.com/dimitropoulos/httpsnippet/blob/redo-readme/README.md

@erunion please take a gander if you could

repo: Kong/httpsnippet


text:
Error message in Insomnia Designer when importing OpenAPI JSON FileShort issue title

Describe the bug
I can't import a Json OpenApi file.
To Reproduce
Hello,
I have an OpenApi Json file that generate an error when I try to import it in Insomnia Designer.
This file can be opened in Swgger Editor and this editor does not report any problem.
Here is the error message I have when I try to import the json file :
`
Import Failed
TypeError:
result.summary[models_WEBPACK_IMPORTED_MODULE_11_.workspace.type]
Import failed
Cannot read property 'type' of undefined
`
For confidentiality reasons I cannot publish this JSON file here but I can send it to you by email.
Expected behavior
The file should be imported.
Desktop (please complete the following information):

Windows 10 Professional Version 10.0.18363 Number 18363
Installation via your website
App Version [e.g. v7.0.3]

Hi @hervehobbes! If you toggle devtools, do you see any errors in the console?
That is unfortunately a fairly generic error (it's on the radar to improve the error output) - to help diagnose, could you please flick an email through to support@insomnia.rest with that specification and I or someone from the team will take a look. ☺

Hello,
Thank you very much for your answer.
Here is the error message I have from the console:
[ErrorModal] Cannot read property 'type' of undefined
And:
[ga] Event Modals, Show, ErrorModal
Ok for the email, it is going to be send now.
Bye

To summarize, the following case is not handled by the openapi3 importer. I'll update the issue title to reflect this. 😄
openapi: '3.0.2'
info:
  title: Endpoint Security
  version: '1.2'
servers:
  - url: https://api.server.test/v1

components:
  securitySchemes:
    Basic:
      type: http
      scheme: basic

paths:
  /none/basic:
    get:
      security:
        - {}		# causes failure
        - Basic: []
      responses:
        '200':
          description: OK

Hello,
Thank you for your help ans answer.
I have a route that can be used with and without authentication, that's why
it is written like that.
Thanks again and bye,
Hervé
Le jeu. 14 mai 2020 à 01:58, Opender Singh notifications@github.com a
écrit :

To summarize, the following case is not handled by the openapi3 importer.
I'll update the issue title to reflect this. 😄
openapi: '3.0.2'
info:
title: Endpoint Security
version: '1.2'
servers:

url: https://api.server.test/v1

components:
securitySchemes:
Basic:

  type: http

  scheme: basic

paths:
/none/basic:
get:

  security:

    - {}		# causes failure

    - Basic: []

  responses:

    '200':

      description: OK

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Kong/insomnia/issues/2167#issuecomment-628307081, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA4VM6DW7M462U6JL7LKGTRRMX3LANCNFSM4M7PHM6A
.

authors: develohpanda hervehobbes

repo: Kong/insomnia


text:
HAWK Authentication uses wrong content type for graphql requests

Expected Behavior
Authentication process should pass on server.
Insomnia should use content-type header for payload hash computation
Actual Behavior
Authentication process fails due to wrong content type used by insomnia for hash computation
Reproduction Steps

Make a GraphQL Request with HAWK Authentication
Obviously it will use by default content-type: application/json in headers section
Send a request
Authentication fails even though HAWK's auth id and key are correct

I've debugged it in dev tools and turned out that insomnia ignores content-type header and uses body.mimeType instead which will be application/graphql in case of graphql requests.
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
You're using @hapi/hawkbut this is no longer maintained. You should upgrade to hawk
I wanted to fix it on my own but apparently this part of code is nor available in this repository?
Insomnia Version
2022.3.0
What operating system are you using?
macOS
Operating System Version
OSX 12.4
Installation method
insomnia.rest
Last Known Working Insomnia version
No response

Hi @wookieb, thank you for reporting this!
Any chance you can share some public working example of HAWK Auth + GraphQL that we can use to test this out?

Hi @filfreire  - I will later today.

Here you go. Details in readme https://github.com/wookieb/insomnia-issue-4855

authors: filfreire wookieb


text:
some kong node not use latest target when update upstream's target use admin api

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
2.2.1
Current Behavior
When I update upstream's target use admin api , some kong node use old target for proxy request.After 30-40 mins ,all kong node use the new target.
I use postgress.During that time (30-40mins) the postgress net work I/O raise about 10 times.
Expected Behavior
When I update target using admin api,after db_update_frequency seconds all the kong node use the new target to proxy request.
Steps To Reproduce
No response
Anything else?
No response

Hi @vaxilicaihouxian! Is it possible to update Kong? There were several balancer fixes and new features since 2.2, this seems one of the bugs fixed.

i'm afraid i can't.i found that may be the lag of the target update events handling.

As Kong 2.2 is an old version, I'm closing this issue. If the same behavior is found with a recent one, please feel free to open a new issue.

authors: locao vaxilicaihouxian

repo: Kong/kong


text:
key-auth option to let backend handle HTTP 401

Summary
Sometimes we would like to see/handle unauthorized requests at the service behind kong. Return our own responses via the service for unauthorized requests. Currently there is no way to pass back unauthorized requests since key-auth always returns its own 401 prematurely (in some cases).
This change is also handy if kong is not the source of record for api keys since individual consumers can be defined in kong that need to be rate-limited transparently without affecting other users.
Full changelog

New config.allow_unauthorized config option

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

how would this be different from using the anonymous user?

Good question! I guess I just didn't understand the anonymous user could be used like that. But now that I re-read the docs it seems to say it right there. Thanks!

authors: CLAassistant Tieske mkhpalm


text:
Include OpenShift cluster version in the telemetry

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
Currently, it's not possible to tell what OpenShift cluster versions KIC is running on in the wild. We would like to know it in order to broaden our context on the usage of KIC with OpenShift that is needed to make a proper decision on support policy for OpenShift.
Proposed Solution

Spin up an OpenShift cluster and ensure that the reported cluster version is not distinguishable indeed.
Find out how we can detect the OpenShift cluster version in runtime (oc CLI, ClusterVersion custom resource, node names heuristics?)
Implement the most appealing heuristic and report OpenShift version field in the telemetry

Additional information
Initial investigation of the existing telemetry data has shown that the telemetry does include a Kubernetes cluster version which is not special in any sense for OpenShift clusters. Probably some dedicated heuristic is going to be needed to detect the OpenShift version.
Acceptance Criteria

[ ] As a KIC developer, based on the telemetry data I can tell what OpenShift cluster versions KIC is being run on

ClusterVersion CRD is worth looking into. Probably we could read it/watch it and inspect its status.desired field.

I didn't know about the library we have for telemetry (that we don't use in KIC yet). I think it might be worth considering incorporating OpenShift detection in there and using the library.

I didn't know about the library we have for telemetry (that we don't use in KIC yet). I think it might be worth considering incorporating OpenShift detection in there and using the library.

That's evidently a miscommunication on my end. But nevertheless putting it in a library is one thing, implementing is another. If we figure out how to detect said version I'll happily help to incorporate that into the library and use it in KIC

tl;dr there are some things that should provide the correct version with high confidence, but we don't currently have permissions to them and I think we should avoid adding new permissions if possible. There's something we do have access to already that looks like it will provide the OpenShift version, but with less confidence. Do we want to go ahead and use the latter?
ClusterVersion is what the oc CLI uses to print the OpenShift version: https://github.com/openshift/oc/blob/bdc5bb5b66e06e77e05ed3290c15ebfff61fa23f/pkg/cli/version/version.go#L138C51-L146
However we would not normally have access to them, and OpenShift also seems weirdly cagey about granting access to them. Using a non-admin user to run oc -v9 version will indeed show
I0615 17:01:44.652805   30665 request.go:1171] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"clusterversions.config.openshift.io \"version\" is forbidden: User \"developer\" cannot get resource \"clusterversions\" in API group \"config.openshift.io\" at the cluster scope","reason":"Forbidden","details":{"name":"version","group":"config.openshift.io","kind":"clusterversions"},"code":403}
I0615 17:01:44.653172   30665 version.go:143] OpenShift Version not found (must be logged in to cluster as admin): clusterversions.config.openshift.io "version" is forbidden: User "developer" cannot get resource "clusterversions" in API group "config.openshift.io" at the cluster scope

shift.yaml.txt is a kubectl get all -A -oyaml dump of all (well, most, since "all" isn't actually all) resources on a fresh 4.13 install. I also reviewed CRDs (not included in all), but it doesn't look like they're an option:
17:08:57-0700 esenin $ kubectl get crd -oyaml | grep -C4 4.13
                      enum:
                      - None
                      - v4.11
                      - v4.12
                      - v4.13
                      - vCurrent
                      type: string
                  type: object
                channel:

Several replication controllers (Deployments and similar) do have a release.openshift.io/version annotation, but we don't currently have permission to those. We do have access to Pods (though I forget exactly why--they don't seem like something we should need access to, at least outside our own namespace) already, and the various built-in operators have information that we can probably use:
17:19:10-0700 esenin $ kubectl get po -n openshift-apiserver-operator -ojson | jq .items[0].spec.containers[0].env
[
  {
    "name": "IMAGE",
    "value": "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ef9f729c0a5759a573009d0009cfe878fe4415b7bf6311aeda1cf3478df8d517"
  },
  {
    "name": "OPERATOR_IMAGE",
    "value": "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0e4653a8f77aa893fe69bacb94d1f83e76756d51e75000d25c7e946dbdc1a533"
  },
  {
    "name": "OPERATOR_IMAGE_VERSION",
    "value": "4.13.0"
  },
  {
    "name": "OPERAND_IMAGE_VERSION",
    "value": "4.13.0"
  },
  {
    "name": "KUBE_APISERVER_OPERATOR_IMAGE",
    "value": "quay.io/crcont/openshift-crc-cluster-kube-apiserver-operator@sha256:31118a93da9b01f37280b37276ec2396002f21945c54532254376d37c148e605"
  }
]

The OpenShift operators look like they all consistently use the same version as the OpenShift version they're bundled with, so that OPERATOR_IMAGE_VERSION variable is an option. That's only based on review of the actual values though--I don't have any guarantee that the versions matching is always the case, though it seems reasonable to expect that it is.

https://github.com/Kong/kubernetes-telemetry/pull/168 and https://github.com/Kong/kubernetes-ingress-controller/pull/4211 work to ascertain the cluster version on 4.13, which is the current version CRC installs.
My  choice of operator to probe was a best-guess about things that are likely to be consistent across versions. The API server is important and the associated operator has been around for ~4y: https://github.com/openshift/cluster-openshift-apiserver-operator
Attempting to try and confirm signal viability across older versions, but tools for deploying older versions of OpenShift locally appear to be quite bitrotten (especially as far as docs go), so a bit poking around in the dark to see what works.

authors: czeslavo pmalek rainest

repo: Kong/kubernetes-ingress-controller


text:
Release v2.12.3

Release Type
patch
For major/minor releases Create release/<MAJOR>.<MINOR>.x Branch

[ ] Create the release/<MAJOR>.<MINOR>.x branch at the place where you want to branch of off main

For all releases Create prepare-release/x.y.z Branch

[x] Ensure that you have up to date copy of main: git checkout main; git pull or a targeted release branch e.g. release/2.7.x: git checkout release/2.7.x; git pull
[x] Create the prepare-release branch for the version (e.g. prepare-release/2.7.1): git branch -m prepare-release/2.7.1
[x] Review carefully CHANGELOG.md. Manually reorder entries for relevance, common topic, adjust description, etc. - make it clear and easy to follow for users. Optionally headline notable changes (emojis are allowed). Double-check that dates are correct, that link anchors point to the correct header, and that you've included a link to the GitHub compare link at the end. If there were any RC releases before this version, fold their changes into the final release entry.
[x] Resolve all licensing issues that FOSSA has detected. Go to Issues tab in FOSSA's KIC project and resolve every issue, inspecting if it's a false positive or not. ignored.go script should be useful to look for issues that have been already resolved and reappeared due to version changes.
[x] Update ignored.json following instructions in README.
[x] Retrieve the latest license report from FOSSA and save it to LICENSES (go to Reports tab in FOSSA's KIC project, select 'plain text' format, tick 'direct dependencies' and download it).
[x] Ensure base manifest versions use the new version (config/image/enterprise/kustomization.yaml and config/image/oss/kustomization.yaml) and update manifest files: make manifests
[x] Push the branch up to the remote: git push --set-upstream origin prepare-release/x.y.z

For all releases Create a Release Pull Request

[x] Check the latest E2E nightly test run to confirm that E2E tests are succeeding. If you are backporting features into a non-main branch, run a targeted E2E job against that branch or use ci/run-e2e label on the PR preparing the release.
[ ] Open a PR from your branch to main. Set a backport release/X.Y.Z label.
[x] If this is a patch release, ensure that the release branch (e.g. release/2.9.x) compared against the latest patch for this minor release (e.g. v2.9.0) includes the expected changes that the release should include (e.g. by checking https://github.com/kong/kubernetes-ingress-controller/compare/v2.9.0..release/2.9.x).
[x] Once the PR is merged (the prepare-release/x.y.z branch will get automatically removed), approve and merge the automatic backport PR and initiate a release job on the main branch for major or minor release, for patch use the release branch. Your tag must use vX.Y.Z format. Set latest to true if this is be the latest release. That should be the case if a new major.minor release is done or a patch release is done on the latest minor version.
[x] CI will validate the requested version, build and push an image, and run tests against the image before finally creating a tag and publishing a release. If tests fail, CI will push the image but not the tag or release. Investigate the failure, correct it as needed, and start a new release job.
[ ] The release workflow (.github/workflows/release.yaml) will update the latest branch - if the released version was set to be latest - to the just released tag.

For major/minor releases only Update Release documents

[x] Trigger release_docs workflow. Note that you will need to update the new version's navigation manifest (e.g. for 2.7 to use the new files (CRDs and CLI arguments references) after.
[ ] Ensure a draft PR is created in docs.konghq.com repository.
[ ] If you are adding a new CRD, add a new description file under app/_includes/md/kic/crd-ref/. This is a brief description injected into the CRD reference page.
[ ] Update articles in the new version as needed.
[ ] Update reference/version-compatibility.md to include the new versions (make sure you capture any new Kubernetes/Istio versions that have been tested)
[ ] Copy app/_data/docs_nav_kic_OLDVERSION.yml to app/_data/docs_nav_kic_NEWVERSION.yml and update the release field to NEWVERSION. Add entries for any new articles.
[ ] Make sure that app/_data/docs_nav_kic_NEWVERSION.yml links to the latest generated custom-resources-X.X.X.md.
[ ] Add a section to app/_data/kong_versions.yml for your version.
[ ] Add entries in support policy documents: app/_includes/md/support-policy.md and app/_src/kubernetes-ingress-controller/support-policy.md.
[ ] Mark the PR ready for review.
[ ] Inform and ping the @Kong/team-k8s via slack of impending release with a link to the release PR.
[ ] Ensure that KGO works with the released version of KIC. Update and release it if needed.

Conformance tests report
Trigger for released version CI workflow Generate Kubernetes Gateway API conformance tests report, verify artifact and submit it to https://github.com/kubernetes-sigs/gateway-api/tree/main/conformance/reports. It's still in experimental phase. Update the KIC version in the README's Gateway API conformance badge.
Release Troubleshooting
The Release Troubleshooting guide covers strategies for dealing with a release that has failed.

blocked by:

#5241
#5252

When I tried to run the e2e test, I encountered the same situation as https://github.com/Kong/kubernetes-ingress-controller/issues/5313

Let's backport https://github.com/Kong/kubernetes-ingress-controller/pull/5327 to v2.12.x

[ ] https://github.com/Kong/docs.konghq.com/pull/6685


text:
Is there any plans to use 2.0 version in Kong?

As I understand version 2.0 of lua-resty-healthcheck uses shared dict to create health checker timer in only one worker process(system wide timer). The previous version 1.6.2 creates dedicated health checker timer per worker process. In some cases, this causing too much stress on upstream services when we run large number of kong pods.
Is there any plan kong to upgrade the version 2.0 to make use of kong node level timers?

Hi @surenraju-careem
Thank you for this remark! We do not plan to include the changes introduced 2.0.0 into kong, mainly because in kong we stopped using lua-resty-worker-events. Apart from that there were other breaking changes introduced to this library that made it painfully difficult to bump the version up in kong.
Therefore we decided to discard 2.0.0 from future development and promote 1.6.3 as the new master and 3.0.0 release since it was there where the main development happened.
When it comes to the issue you're experiencing - it sounds like those changes might be introduced to the next 3.x version - but I'd need other folks to confirm.  @bungle , @Tieske - do you think we could optimize the health checker to not cause too much stress on upstreams in the same manner we optimized it for 2.0.0?

Health-checks were always synchronized across the workers (only 1 worker would execute a specific check). This still required a timer for each healthcheck in each worker though. Problems occured when too many upstreams were created, causing systems to run out of timers.
This has been refactored to use way less timers. I don't know the exact details, but the problem was solved. Maybe @locao can shed some light on that.

authors: Tieske nowNick surenraju-careem

repo: Kong/lua-resty-healthcheck


text:
Better Workbench Management Compatibility

What mod would you like to see compatibility with?
Better Workbench Management
Is there a bug in the mod when it's enabled with this other mod?
Reported by Madman666 on Steam Workshop:

when present, makes it so that when organs finish growing and are taken out of vats, the bill count doesn't go down, so even if you wanted to grow it once - it ll keep growing same limb over and over again.

Are there errors in the debug log? If so, when do they occur?
Unknown

Bug confirmed.

This is actually a bug in regular QEE that is more visible when this mod is enabled. Better Workbench Management changes the default output location to Drop On Floor. The last patch adding bills to the Organ Vat has a bug where the RepeatCount does not decrementing properly when output location is 'Drop On Floor'. Will be fixed next patch.

repo: KongMD-Steam/QuestionableEthicsEnhanced


text:
Upgrade UI - Buy token

Field:

Account selector
Amount
Token selector
Service selector

Flow:

If is account ALL:

Account selector: allow to select any account

If is not account ALL:

Account selector: readonly

If in token group screen:

Token selector: allow to select any supported token (predefined list) base on value of Account selector

If in token detail list screen:

Disable buy icon if the token not in the supported list
Token selector: readonly

When user press next button, process to the corresponding service page .

todo:

Component:
[x]  Service selector
UI:
[x] Buy token layout
Logic:
[x] Implement the flow mention above

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-build-0.8.1-1678083121116.zip
Please check issue

[ ] Show substrate address when buy the default token
Actual: Show substrate address when buy the default token
Expected: Show the network's address when buy the token

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-build-0.8.1-1679019764378.zip

[ ] Still enable Buy button when selected token is not native token

Version test:

[ ] Display incorrect list token

Actual: Show token of the network which is not integrated to SubWallet (BNB - Binance)
Expected: Show token:

Network is connected
Supported buy token on Transak

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-build-0.8.1-1679666144073.zip
Validation passed for cases:

Buy with Substrate account (Specific mode, all account mode)
Buy with EVM account (Specific mode, all account mode)
Buy with a token which not supported token
Buy with a service which not supported yet

repo: Koniverse/SubWallet-Extension


text:
Unified account - Review and update for Ledger account

Describe the task
Review and update for Ledger account

[x] Regarding account overwrite scenarios when connecting, including:
+ legacy <-> legacy: allow overwriting
+ legacy <-> generic: allow overwriting
-> Unable to perform, showing an error that an account from another legacy app with the same address already exists.

[x] Unable to select the Ledger account in the Earning section

[x] Handle the case of duplicate account names when connecting with different devices.

[x]  Update logic block transaction action according to the new interface.

[x] Still show Polkadot Ledger Legacy account when receive token that not supported by Ledger account

Expect: Do not show Polkadot legacy account

Version test : https://drive.google.com/file/d/1EYCD87_fFS1wJSv92ciRZs5F3d9cfc0E/view?usp=sharing

[ ] All account mode, in case the wallet only has a TON account and a legacy ledger account
Actual : Don't fillter chains, tokens for Receive, Send fund, Swap, Buy features

Expect : Fillter chains, tokens for Receive, Send fund, Swap, Buy features

[ ] When perform XCM on send fund feature
Actual : Block XCM with Legacy app : Polkadot, Statemint, Statemine, Kusama

Expect : Don't block XCM with Polkadot, Statemint, Statemine, Kusama app

Version test : https://drive.google.com/file/d/1nuWeryGaUd1jg8ZQaiz_IvndgZsLpV_f/view?usp=sharing

[ ] Don't show popup Unsupported network when get the network address that has not been updated at runtime
Expect : Update code from issue #3463


text:
Update web-runner v1.1.29

Describe the task
Update web-runner v1.1.29

Details: https://github.com/Koniverse/SubWallet-Extension/releases

Version test: 16:35 03/01/2023
Device test: IP 11
Validation passed in case:

Remove some RPC on Polkadot and Kusama (https://github.com/Koniverse/SubWallet-Extension/issues/2425)

repo: Koniverse/SubWallet-Mobile


text:
Vejledning i install

I vejledingen til 1.3.0 på github, bør der stå at det er et condavindue som skal åbnes og ikke blot en commando-promt.
Der er et ”git clone” for meget i kommandoen:
git clone git clone https://github.com/Kortforsyningen/FIRE.git
Brugeren bør opdatere conda til ver 4.11.0 med flg. kommando:
conda update -n base -c defaults conda”
Vedr. 1.3.1  er dette godt eller skidtsvar efter at have kørt: git checkout fire-1.3.1
Previous HEAD position was 760a933 Merge pull request #516 from xidus/1.3
HEAD is now at 4fca6e3 Merge pull request #531 from Kortforsyningen/backport-530-to-1.3

I vejledingen til 1.3.0 på github, bør der stå at det er et condavindue som skal åbnes og ikke blot en commando-promt.

Det står der vel også?

Og så vidt jeg kan se er der også kun en enkelt runde git clone. Det må næsten være et andet sted du har kigget, så hvor er du stødt på de problemer? Jeg læser her https://kortforsyningen.github.io/FIRE/installation.html#fire

Vedr. 1.3.1 er dette godt eller skidtsvar efter at have kørt:

Det er godt svar, men det er uforståeligt for det utrænede øje. Af samme grund bliver du senere i processen bedt om at tjekke versionen med fire --version. Det er nemmere at forstå.

@kbevers  sagde:

Det må næsten være et andet sted du har kigget

Jeg tror det er teksten her @mrlarshole refererer til

Ja, det er det da nok. Det er også rodet at det står der frem for at henvise til eksisterende materiale.

Joacims mail fra 9/12 2021 siger: FIRE 1.3.1 kan installeres på følgende måde, der forudsætter, at man har fulgt vejledningen til installation af FIRE 1.3.0, som kom i sidste uge:
https://github.com/Kortforsyningen/FIRE/releases/tag/fire-1.3.0
Det er her der er dobbeltkonfekt.

Et hurtigt spørgsmål:
Jeg kan skifte mellem test og prod database bare ved at skiftet teksten test til prod i den øverste linje inifilen:?
[general]
default_connection = test

Undertrykker jeg .ini med --db options prod|test?

@mrlarshole

Undertrykker jeg .ini med --db options prod|test?

Ja. Hvis du sætter --db=test fx så er du sikker på at du bruger testdatabasen. Hvis du ikke angiver noget så bruges det du har sat som default_connection i fire.ini.

Jeg har rettet installationsvejledningen under release 1.3.0 til så de værste fejl og mangler er kommet i orden. Jeg tror fremadrettet vi bare skal henvise til websiden, så undgår vi nok lignende fejl.

authors: busstoptaktik kbevers mrlarshole

repo: Kortforsyningen/FIRE


text:
Support for Android App Icons?

Hello,
I am using this plugin in IOS apps and it is great. Today i wanted to use it in my Android app but as far as i see it does not support Android yet?
Best

Sorry - this plugin is built for iOS apps only right now 👍

authors: KrauseFx ergunkocak

repo: KrauseFx/fastlane-plugin-appicon


text:
Disable HTML Generation?

Hello,
Is there a way to disable the HTML generation when the screenshot process completes?
Thanks,
Kevin

That's not possible, but you can use
SNAPSHOT_SKIP_OPEN_SUMMARY=1 snapshot

to not automatically open the file and use fastlane to automatically delete the HTML file.

Perfect, thank you!

:+1:

authors: KrauseFx kevinstueber

repo: KrauseFx/snapshot


text:
🛑 Sebastian VmW is down

In 8feb023, Sebastian VmW (https://verkaufenmitwerten.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sebastian VmW is back up in c779bd8 after 8 minutes.

repo: KrisKodira/uptime-monitor


text:
Django sending Internal Server Error mails for health check endpoint

After upgrading our Django app (Django 2.0.9 -> 2.1.3, Python 3.6 -> 3.7, django-health-check 3.5.1 -> 3.8.0) we're sometimes getting Internal Server Error mails from Django triggered by the health check endpoint. Unfortunately these mails do not contain a stack trace or any other information that is helpful in determining what's going on, which is why I'm opening this issue.
We're running our app on Kubernetes, and it is configured to periodically call the health check endpoint to verify that the app is still alive. There are django-health-check checks configured for db (PostgreSQL) and cache (memcached).
The first part of the error mail is as follows:
Internal Server Error: /healthz

Report at /healthz
Internal Server Error: /healthz

Request Method: GET
Request URL: http://10.244.2.193:8000/healthz
Django Version: 2.1.3
Python Executable: /usr/local/bin/python
Python Version: 3.7.1
Python Path: ['/srv', '/usr/local/bin', '/usr/local/lib/python37.zip', '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/site-packages']
Server time: vr, 9 Nov 2018 19:14:47 +0100
Installed Applications:
(...
 'health_check',
 'health_check.db',
 'health_check.cache',
...)

Do you happen to have any idea what could be causing these internal server errors?

Hi @praseodym thanks for reaching out. I'd love to help you, but must admit this isn't much to go about. Do you happen to use a service like sentry to monitor server errors or do you have some kind of logs? You must have a service in place, that is calling your health check endpoint. Does that service have any more information? I we can figure this out somehow.
Best
-Joe

We have logging enabled, but there is nothing in there related to the failing health check -- the error mail is all we have at this time. Do you have suggestions on how we can obtain more logging?

Hi @praseodym I did an update on a production app yesterday to Django 2.1 and I can now reproduce the error. Also on sentry I don't see the full stack trace. I will investigate this further and let you know when I have more information.

Ok, so I don't know what they changed in 2.1 but the message you are seeing is emitted by the django.requests logger, seealso: https://docs.djangoproject.com/en/2.1/topics/logging/#django-request
It will log all 5xx responses, but doesn't have any information about the error.
What you can do is simply silence the logger in your logging config or filter the email.
If you want to get the proper message from Django health check, you should double check that you have the email handler setup for the health-check logger.
If you don't know what I am talking about I recommend reading into https://docs.djangoproject.com/en/2.1/topics/logging/
Feel free to ask more questions should you have any.

@codingjoe Would you mind explaining a little bit more what you mean with health-check logger? Sorry to say but I didn't get your point :/

Hi @GitRon sure, it'd be my pleasure.
By the health-check-logger, I mean the name of the logger. In Django you can configure the handlers for each logger or other behavior via the LOGGING setting.
In this particular case you want to add:
LOGGING = {
    # ...
    'loggers': {
        # ...
        'health-check': {
            'handlers': ['console'],
            'level': 'WARNING',
            'propagate': True,
        }
}

See also Django's documentation on logging for more information:
https://docs.djangoproject.com/en/stable/topics/logging/

@codingjoe Oh, thats what you mean! Alright, now I get it!
The question is: Even though my healthchecks work perfectly fine I get tons of those errors:

[2019-06-18 07:56:21,017] log: ERROR - Internal Server Error: /healthcheck/
[2019-06-18 08:29:11,008] backends: ERROR - unavailable: Cache key does not match
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/health_check/backends.py", line 30, in run_check
self.check_status()
File "/usr/local/lib/python3.6/site-packages/health_check/cache/backends.py", line 14, in check_status
raise ServiceUnavailable("Cache key does not match")

Any ideas what I can do about it? It started when I integrated memcached and as I said before, everything works as expected.
Thanks!

Hi @GitRon interesting. You get those error logs, but the status endpoint responds with a 200 response? Did you mark the cache check as a critical_service?

Hi @codingjoe
nope, just included the three healthchecks in my installed apps. Thats it.
Thx
Ron

Ok, I double-checked, and it seems your endpoint does respond with a 500 response as it should:

django.request.log_response:228 Internal Server Error: /healthz

How do you check the response type? Do you use some kind of up time bot, if so which one?

Acutally I just see this in my container all the time. Maybe there is some internal function of k8s testing the container and in this case memcached or so is not working. But I dont get more info except that I see the error all the time.

@GitRon if you see the error, there must be something wrong with your cache setup.

@codingjoe Thanks for the info. Maybe I need to ask around our DevOps guys...

@GitRon sorry for coming back to this, but could you please tell me if you guys found a solution for the Cache key does not match issue? on my dev server, everything is fine, but I'm getting this on AWS and I don't manage to solve it... Cheers!

@cbernet Sorry to tell you but I think we ditched the healthchecks for this case.

@carderm that probably means, that your cache isn't setup correctly. What cache backend do you use and would you mind sharing your production cache config (please do not post any secret keys)?

authors: GitRon cbernet codingjoe praseodym

repo: KristianOellegaard/django-health-check


text:
Health Check for Redis

This adds support for a health check for Redis.
More or less the same as the health check for RabbitMQ.
It currently uses the celery_broker_url from Django settings. This could be changed to broker_url that RabbitMQ uses, if wanted.

@ingvaldlorentzen thanks for the contribution. I think a Redis health-check would be great. That being said I see multiple places where Redis can be used in Django. I for one, use it for caching, not as a result backend for celery. So either we change implementation, or we change the naming a little to reflect, that it's monitoring the result backend.
Please also drop the commented out lines ;)
Thanks!
Joe

Codecov Report

Merging #225 into master will decrease coverage by 1.13%.
The diff coverage is 58.06%.

@@            Coverage Diff             @@
##           master     #225      +/-   ##
==========================================
- Coverage   75.52%   74.39%   -1.14%
==========================================
  Files          32       35       +3
  Lines         380      410      +30
==========================================
+ Hits          287      305      +18
- Misses         93      105      +12

Impacted Files
Coverage Δ

health_check/contrib/rabbitmq/backends.py
80% <0%> (ø)
:arrow_up:

health_check/contrib/redis/apps.py
0% <0%> (ø)

health_check/contrib/redis/__init__.py
100% <100%> (ø)

health_check/contrib/redis/backends.py
77.27% <77.27%> (ø)

Continue to review full report at Codecov.

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

Hi,
Thanks for the feedback!
I changed the Redis URL from CELERY_BROKER_URL to simply REDIS_URL. Also updated the variables in the health check to reflect this change.
I think REDIS_URL  is a nice generic way to do this, and if a project doesn't use REDIS_URL, it's easy and hopefully understandable to add to the settings variables for the health check.
Removed the commented code, sorry about that, it was a slip-up.
I'll add info on the Redis health check to the documentation if you think this looks alright.

Ingvald

Edit: I see some checks are failing here. I'm not super familiar with codecov, if you have any feedback on how I should proceed to fix this I would be super thankful!
If not, I'll see if I can get a team member to help me out on Monday.

I tried to create the tests for most things now that @ingvaldlorentzen has refactored over to use redis.
I haven't used pytest before, so please give me a heads up if I need to correct something.
test_redis_conn_ok could probably be rewritten to catch the log message as you requested, but I'd have to look more into that in two weeks when I'm back from vacation.

Released in 3.11.0 🎉

authors: JonasKs codecov-io codingjoe ingvaldlorentzen