iScroll with jquery+jquery mobile

Running iScroll 4.1.9 with jQuery und jQuery Mobile gives some weird behaviour on mobile phones (tested with HTC Flyer, iPhone 4G and iPod touch). When a page was already visited (is present in Dom) and i navigate back to it, it jumps a little down and the i can't scroll to the top of the page.
Example: https://github.com/h-andreas/iscroll-jumpy
Download, navigate to page1.html, scroll down, click "next", scroll down again and click "next" again. It will navigate back to page1 and a moment later scroll/jump down.

I have the exact same issue. I have a page that scrolls nicely (A). When i click on a button and go to another page(B) and press the back button on the other page (B), the initial page (A) shows correctly, but after a split second the page scrolls down completely.
The weird thing is, when going back from page A to the page that came before that, and going back again to page A, everything is fine again.
Furthermore, when th glitch happens and the page seems to scoll all the way down. This is only visually, or so it appears. iScroll still works, but thinks i'm at the top of the page. So visually i'm at the bottom of the page, but since iScroll thinks i'm at the top, i can scroll even further down...
I've tried resetting the classes on the page, tried resetting iScroll everytime i show the page, have tried to refresh iScroll and programatically scroll to the top, but nothing seems to work.
Working on phonegap 0.9.6, jQueryMobile 1.0 RC2, iScroll 4.1.9 (and 4.1.8, both have the same issue).

Hello Andreas, thanks for your reply!
When i set those settings, the iScroll becomes very jittery and doesn't scroll fluently at all. When going to page B and back, the same thing happens as before (page jumps to bottom, scrolling is messed up) but now i can fix this by scrolling all the way down (far beyond the bottom of the content). It seems to reset iScroll in some way. After that, i can scroll normally again, albeit very jittery.
Although it helped somewhat, still not really a solution i'm afraid


Proper function input

Users should have the option to change in between JavaScript input (like it is now) and our custom input, which would work with what normally would be considered a function on paper.

i.e. remove the need for Math, among other things

This is almost complete; we just need the option to switch to javascript (maybe?)

No. We'll have Python scripting that has nothing to do with the function strings.


[How to use]

Platforms
Web
Description
How to fix the size of the crop frame and not drag the crop frame
My code
No response
Try do it
No response

i can't get it

any more info about your issue?


Multiple anchors handled wrong in YAML syntax check

Bug description
If multiple anchors are used in the compose file, the YAML syntax checks doesn't recognize "<<" as a special key.
Expected behavior
Multiple anchors could be used correctly
Portainer Logs
There is an error in the yaml syntax: YAMLSemanticError: Map keys must be unique; "<<" is repeated
Steps to reproduce the issue:
Use a simple config like below
version: "3"

x-temp-a: &one
  restart: always

x-temp-b: &two
  networks:
    - network

services:
  service-a:
    image: nginx
    <<: *one
    <<: *two

Technical details:

Portainer version: 2.9.0

If I deploy the stack with the second anchor replaced by the actually values, I could then later successfully revert that change in the editor, so that it correctly uses the multiple anchors. So somehow the check in the editor is different, than the initial one

Closing this one as a duplicate of https://github.com/portainer/portainer/issues/5660


Feature: [searh filter] [date range] make default field view more intuitive

By default date range field show just empty string.
I think that more intuitive will be show text "From" to "To" as in example:

May be also will be more clear if data range will be splitted to 2 fields: From / To like in example from other site:

I also agree that the empty date range filter to get the calendar view is obscure from an user PoV.


Display latest sync time for pull mirrors on the repo page

Fixes #25168

Could you provide a screenshot?

Screenshots:

Updated time maybe zero.


Error in Extensions in Google Chrome

I am executing this project on Windows platform and executed the steps as mentioned on your main page. but while testing the phishing attack on any new website, I am seeing this below error:
Error handling response: Error: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'http://localhost/Malicious-Web-Content-Detection-Using-Machine-Learning/clientServer.php'.
Context
popup.html
Stack Trace
popup.js:13 (anonymous function)

Can you please fill up the Bug report template so that I get more details about the problem?

Hello Mr. Naik,
I am attaching the screenshot of the error. I followed the steps mentioned on your GITHUB README.md file, currently, I am working on Windows platform with python 2.7 and all the latest dependencies are as per your requirement. When I went into detail for the errors in the extension, I found the error as mentioned in the Capture1 int he attachments.
Thanking you.With regards,Jigar Makwana
On Sunday, 28 April, 2019, 10:24:11 pm GMT-7, Rohit Naik<EMAIL_ADDRESS>wrote:

Can you please fill up the Bug report template so that I get more details about the problem?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Jigar, I cannot see any screenshot attached here.

Hello Rohit,
I am attaching the errors again for your reference:
Thanking you.
With regards,Jigar Makwana
On Wednesday, 1 May, 2019, 11:14:13 pm GMT-7, Rohit Naik<EMAIL_ADDRESS>wrote:

Hi Jigar, I cannot see any screenshot attached here.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi please check if you can see the screenshot yourself in this issue.
For your reference, this is how you attach images to issues - https://help.github.com/en/articles/file-attachments-on-issues-and-pull-requests

Hi Jigar,
I just tested the most updated version of the code by following the steps from the README and I am unable to recreate this error. Please do a git pull and test again.
If still there is an error, I would suggest taking a look at this link.
If you still need help, please fill up the following bug report template so that I can recreate this issue and take it from there -
**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - Browser [e.g. stock browser, safari]
 - Version [e.g. 22]

**Additional context**
Add any other context about the problem here.

Closing the issue for now as I am not able to see any issue with the updated code.

@Jigar6591  i am also facing the same issue did u find the solution to it ? if yes please help me out ! thankou @Jigar6591  and @philomathic-guy


Make EndpointRegistry extends Map<NormalizedEndpointUri, Endpoint>

Change the CamelContext.getEndpointRegistry() to return an EndpointRegistry<NormalizedEndpointUri> instead of an EndpointRegistry<? extends ValueHolder<String>>.
This is a small incompatible change.

You can add a note about this API change in the Camel 4.7 upgrade page

You likely need to update code at places like
camel-rest/src/main/java/org/apache/camel/component/rest/DefaultRestRegistry.java

You can do a
cd components
git grep getEndpointRegistry

this PR needs to fix in the components as commented above

this PR needs to fix in the components as commented above

In theory yes, in practice, no component is affected.  The reason is that the K generic type in the EnpointRegistry is only used on keySet() and entrySet() methods, which are not used, and components, when they need to access the registry do so without using an intermediate variable which could cause a cast compilation error.
I'm actually wondering if that parameter is needed at all, and while we're changing this method, it may be simpler to just make EndpointRegistry non parameterised and extends Map<NormalizedEndpointUri, Endpoint>. @davsclaus thoughts ?

this PR needs to fix in the components as commented above

In theory yes, in practice, no component is affected. The reason is that the K generic type in the EnpointRegistry is only used on keySet() and entrySet() methods, which are not used, and components, when they need to access the registry do so without using an intermediate variable which could cause a cast compilation error.
I'm actually wondering if that parameter is needed at all, and while we're changing this method, it may be simpler to just make EndpointRegistry non parameterised and extends Map<NormalizedEndpointUri, Endpoint>. @davsclaus thoughts ?

Yes that is better as we dont need other kind of parameters at all

org.apache.camel.issues.RecipientListUseOriginalMessageEndpointExceptionIssueTest.testRecipientListUseOriginalMessageIssue
1.822s
FAILURE

org.apache.camel.builder.xml.XPathTest.testXPathSplitConcurrent
1.763s
FAILURE


Can template be used in the default note name?

Hi, thanks for this amazing extension! I downloaded Raycast just for your extension 🤣
I wonder if I can use some basic templates, like {{time}}, in the default note name, prefix for append, etc.? The use case is that I use this extension to quick capture things that I don't want to spend time naming them, yet I still want to log the time.

Hi @zcysxy,
thank you so much for the nice feedback 🔥
Right now templates are not supported. However you could use the Obsidian Plugin Templater. It can automatically rename new notes based on a template that you store in a folder in your vault.
For people not very familiar with Templater or plugins in general it might be a good idea to support some basic templates and I would love to implement those in the Create Note command and the default name, prefix for append, etc.
These are the ones I could think of:

{{time}}
{{date}}
{{month}}
{{day}}
{{zettelkastenID}}

Do you have any more suggestions for templates? Maybe even templates for the content of the note?

Hi @marcjulianschwarz, thanks for the reply. I use Templater and it would be great if the new note creation triggers Templater. However, on my end, the new notes created by the extension will not trigger Templater.
And for extension built-in templates, I think your comment is very thorough; I have nothing to add for now : )

Hi @zcysxy,
I just found out that Templater will only be triggered if Obsidian is running. That's not ideal, maybe I can create a feature request at Templater to not only listen for note creation but additionally listening for new files (e.g. on startup). This could however create problems with templates where you use the current time.
Will let you know when the suggested templates are available.

Got it working, added the mentioned templates in my local repo.
The feature will be released with the next update.

Works like a charm! Thank you!


Adding ThrowChecker to detect usage of throw

Adding a ThrowChecker, similar to the WhileChecker and ReturnChecker.
The PR should include the necessary tests and xml definitions.
sbt test passes locally.
Let me know if anything is missing.
For context, this is related to my issue over on the sbt-scalastyle repo: https://github.com/beautiful-scala/sbt-scalastyle/issues
Basically, it doesn't seem to be possible to reliably identify throw tokens with a regular expression.

Hi @mwz. Thanks for getting to this so quickly. Any idea when it will land in a release?

I want to sort out any outstanding dependency updates while I'm at it and will release afterwards. Hopefully tonight.

I want to sort out any outstanding dependency updates while I'm at it and will release afterwards. Hopefully tonight.

Great. FWIW, I noticed while working on my branch that scalafmt introduces a ton of changes. Touching ~30 files, probably more. We also saw this internally when updating from a 1.x version of scalafmt to the most recent. That was also prompted by scala-steward automatic updates. Rather than having a multi-thousand line commit attributed to whomever happened to run scalafmt, we just decided to stick with the older version.

Rather than having a multi-thousand line commit attributed to whomever happened to run scalafmt, we just decided to stick with the older version.

I've been struggling to keep up with the changes to scalafmt. The new defaults seem sensible though, so I don't really mind reformatting the entire codebase as long as it's consistent. There's been a bunch of bugfixes too, so imo it's good to update to the latest version. I think you might be able to tweak some of the new settings to get it closer to the old behaviour.

I think you might be able to tweak some of the new settings to get it closer to the old behaviour.

I tried for about four hours without success. So if you're fine reformatting the code then I'd just do that.
Thanks again for the quick work and for maintaining this project!

No problem, v1.5.0 is out.


download reference files using command lines tools

Download the SILVA seed and rrnDB files using commands tools rather than using a browser, to ensure the ability to update the software in the future.

d3778cd closes issue


Example code does not work?

Hey, i am getting this
> go build .
github.com/go-gl/gl/v3.2-core/gl
github.com/golang-ui/nuklear/nk
# github.com/golang-ui/nuklear/nk
cgo-dwarf-inference:1:17: error: expected '{' before ')' token

was checking the nk-example.

The same happens to me:
build example:
...
go: downloading github.com/getlantern/systray v1.2.2
go: downloading github.com/golang-ui/nuklear v0.0.0-20231115163627-2440a671efc5
...
go: downloading github.com/go-gl/gl v0.0.0-20231021071112-07e5d0ea2e71
go: downloading github.com/go-gl/glfw v0.0.0-20240506104042-037f3cc74f2a
...
# github.com/getlantern/systray
# [pkg-config --cflags  -- ayatana-appindicator3-0.1]
...
# github.com/go-gl/glfw/v3.2/glfw
...
# github.com/golang-ui/nuklear/nk
cgo-dwarf-inference:1:17: error: expected '{' before ')' token
2024/07/16 15:18:55 Failed to cross compile package: exit status 1.

import go example:
import (
	"github.com/go-gl/gl/v3.2-core/gl"
	"github.com/go-gl/glfw/v3.2/glfw"
	"github.com/golang-ui/nuklear/nk"
)

Getting this exact error as well from my own code just by having the inclusion. My go.mod looks like:
module test/nktest

go 1.22.5

require (
	github.com/golang-ui/nuklear v0.0.0-20231115163627-2440a671efc5
	github.com/veandco/go-sdl2 v0.4.40
)

require (
	github.com/go-gl/gl v0.0.0-20231021071112-07e5d0ea2e71 // indirect
	github.com/go-gl/glfw v0.0.0-20240506104042-037f3cc74f2a // indirect
	github.com/xlab/android-go v0.0.0-20221106204035-3cc54d5032fa // indirect
)

Tried indirects as well, same result.

SDL2 example doesn't work either. It seems like the functions are based on some older nuklear api version, the arguments provided in the examples doesn't match the current api.

Probably I see the same error.
% go build ./nk
# github.com/go-gl/glfw/v3.2/glfw
In file included from ../../go/pkg/mod/github.com/go-gl/glfw@v0.0.0-20240506104042-037f3cc74f2a/v3.2/glfw/c_glfw_darwin.go:8:
../../go/pkg/mod/github.com/go-gl/glfw@v0.0.0-20240506104042-037f3cc74f2a/v3.2/glfw/glfw/src/cocoa_window.m:989:9: warning: multiple methods named 'center' found [-Wobjc-multiple-method-names]
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSCollectionViewCompositionalLayout.h:602:19: note: using
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:417:1: note: also found
# github.com/golang-ui/nuklear/nk
cgo-dwarf-inference:1:17: error: expected identifier or '{'
__typeof__(enum ) *__cgo__0;
                ^
cgo-dwarf-inference:1:28: error: expected ')'
__typeof__(enum ) *__cgo__0;
                           ^
cgo-dwarf-inference:1:11: note: to match this '('
__typeof__(enum ) *__cgo__0;
          ^
2 errors generated.

My environment is like this:
% go version
go version go1.23.2 darwin/arm64

% fastfetch
                     ..'          hajimehoshi@Hajimes-MacBook-Pro
                 ,xNMM.           -------------------------------
               .OMMMMo            OS: macOS 15.0.1 arm64
               lMM"               Host: MacBook Pro (14-inch, Nov 2023, Three Thunderbolt 4 ports)
     .;loddo:.  .olloddol;.       Kernel: 24.0.0
   cKMMMMMMMMMMNWMMMMMMMMMM0:     Uptime: 9 days, 14 hours, 12 mins
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.     Packages: 148 (brew), 2 (brew-cask)
 XMMMMMMMMMMMMMMMMMMMMMMMX.       Shell: zsh 5.9
;MMMMMMMMMMMMMMMMMMMMMMMM:        Display (Color LCD): 3600x2338 @ 120Hz (as 1800x1169) [Built-in]
:MMMMMMMMMMMMMMMMMMMMMMMM:        DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX.       WM: Quartz Compositor
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.     WM Theme: Multicolor (Light)
 'XMMMMMMMMMMMMMMMMMMMMMMMMMMk    Font: .AppleSystemUIFont [System], Helvetica [User]
  'XMMMMMMMMMMMMMMMMMMMMMMMMK.    Cursor: Fill - Black, Outline - White (32px)
    kMMMMMMMMMMMMMMMMMMMMMMd      Terminal: tmux 3.3a
     ;KMMMMMMMWXXWMMMMMMMk.       CPU: Apple M3 Pro (12) @ 4.06 GHz
       "cooc*"    "*coo'"         GPU: Apple M3 Pro (18) [Integrated]
                                  Memory: 15.12 GiB / 18.00 GiB (84%)
                                  Swap: 15.35 GiB / 16.00 GiB (96%)
                                  Disk (/): 320.35 GiB / 926.35 GiB (35%) - apfs [Read-only]
                                  Local IP (en0): <IP_ADDRESS>/24 *
                                  Battery: 80% [AC connected]
                                  Power Adapter: 96W USB-C Power Adapter
                                  Locale: C

I guess c-for-go failed to treat enums correctly:
// NkInputKey function as declared in nk/nuklear.h:837
func NkInputKey(arg0 *Context, arg1 C.enum_, down Bool) {
	carg0, carg0AllocMap := (*C.struct_nk_context)(unsafe.Pointer(arg0)), cgoAllocsUnknown
	carg1, carg1AllocMap := (C.enum_)(arg1), cgoAllocsUnknown
	cdown, cdownAllocMap := (C.nk_bool)(down), cgoAllocsUnknown
	C.nk_input_key(carg0, carg1, cdown)
	runtime.KeepAlive(cdownAllocMap)
	runtime.KeepAlive(carg1AllocMap)
	runtime.KeepAlive(carg0AllocMap)
}

https://github.com/xlab/c-for-go/issues/174

One of the necessary change is
diff --git a/nk.yml b/nk.yml
index 237576e..bebea9b 100644
--- a/nk.yml
+++ b/nk.yml
@@ -70,6 +70,7 @@ TRANSLATOR:
       - {transform: export}
     const:
       - {action: accept, from: "(?i)^nk_"}
+      - {action: replace, from: "(?i)^nk_bool", to: "BoolType"}
       - {action: replace, from: "(?i)^nk_", to: _}

       - {action: ignore, from: _INT8}
       -

Even with the PR https://github.com/xlab/c-for-go/pull/176 and the above patch, I have not succeeded to compile this yet:
% go build ./nk
# github.com/golang-ui/nuklear/nk
nk/etc.go:26:26: cannot use content (variable of type string) as *byte value in argument to NkTexteditPaste
nk/impl_glfw_common.go:40:9: not enough return values
        have (string)
        want (string, error)
nk/impl_glfw_common.go:111:26: cannot use keyPressed(win, glfw.KeyDelete) (value of type int32) as Bool value in argument to NkInputKey
nk/impl_glfw_common.go:112:28: cannot use keyPressed(win, glfw.KeyEnter) (value of type int32) as Bool value in argument to NkInputKey
nk/impl_glfw_common.go:113:28: cannot use keyPressed(win, glfw.KeyKPEnter) (value of type int32) as Bool value in argument to NkInputKey
nk/impl_glfw_common.go:114:26: cannot use keyPressed(win, glfw.KeyTab) (value of type int32) as Bool value in argument to NkInputKey
nk/impl_glfw_common.go:115:32: cannot use keyPressed(win, glfw.KeyBackspace) (value of type int32) as Bool value in argument to NkInputKey
nk/impl_glfw_common.go:116:25: cannot use keyPressed(win, glfw.KeyUp) (value of type int32) as Bool value in argument to NkInputKey
nk/impl_glfw_common.go:117:27: cannot use keyPressed(win, glfw.KeyDown) (value of type int32) as Bool value in argument to NkInputKey
nk/impl_glfw_common.go:118:32: cannot use keyPressed(win, glfw.KeyHome) (value of type int32) as Bool value in argument to NkInputKey
nk/impl_glfw_common.go:118:32: too many errors


adding github action to unittest python

Adding a new github action to unittest the Python using pytest
Fixes #1

I was expecting to be able to "Approve" the workflow, and so test it but the butting does not appear 🤔
Any suggestion for how to test it?

@pberkes - Have you enabled actions in the repository setting page? The actions/workflow worked on my fork https://github.com/sculley/empirical_copula/actions/runs/3210718863 when I submit a push, it should also trigger when there is a push request.
Regarding approval, did you want to have a manual approval to trigger the workflow? I assumed you would want the test job/workflow to trigger automatically but can look into adding a manual trigger.

It's activated, but the first contribution to a public repository requires manual approval, which is somehow missing. I can see that it worked in your fork, and the changes look good, so I'll merge. Thank you!


FEAT: Refactor Upgrade functions, stick to the Cosmos Hub, etc way

Refactor the Upgrade handler's functions using folders, each folder for a different upgrade. Cosmos Hub (and others) style for SDK v0.50
As reference:

https://github.com/cosmos/gaia/tree/release/v20.x/app/upgrades
https://github.com/cosmos/gaia/tree/release/v19.2.x/app/upgrades

Not necessary by the moment


knife rehash breaks subcommands that have a super-class

Description
In #4090 a special-case was added to handle ChefFS specifically, rather than fixing the general case. This leaves all other plugins that use a similar pattern broken after knife rehash is called.
Chef Version
Chef Development Kit Version: 2.4.17
chef-client version: 13.6.4
Platform Version
Linux/OSX
Replication Case
See #4089 #4090 and https://github.com/pdf/knife-attribute/issues/4
Stacktrace
/home/user/.chefdk/gem/ruby/2.4.0/gems/knife-attribute-1.1.0/lib/knife-attribute/node/get.rb:4:in `<class:NodeAttributeGet>': uninitialized constant KnifeAttribute::Node::Helpers (NameError)
        from /home/user/.chefdk/gem/ruby/2.4.0/gems/knife-attribute-1.1.0/lib/knife-attribute/node/get.rb:3:in `<module:Node>'
        from /home/user/.chefdk/gem/ruby/2.4.0/gems/knife-attribute-1.1.0/lib/knife-attribute/node/get.rb:2:in `<module:KnifeAttribute>'
        from /home/user/.chefdk/gem/ruby/2.4.0/gems/knife-attribute-1.1.0/lib/knife-attribute/node/get.rb:1:in `<top (required)>'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/lib/chef/knife/core/hashed_command_loader.rb:80:in `load'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/lib/chef/knife/core/hashed_command_loader.rb:80:in `block in load_command'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/lib/chef/knife/core/hashed_command_loader.rb:78:in `each'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/lib/chef/knife/core/hashed_command_loader.rb:78:in `load_command'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/lib/chef/knife/core/subcommand_loader.rb:109:in `command_class_from'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/lib/chef/knife.rb:153:in `subcommand_class_from'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/lib/chef/knife.rb:214:in `run'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/lib/chef/application/knife.rb:156:in `run'
        from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4/bin/knife:25:in `<top (required)>'
        from /usr/bin/knife:255:in `load'
        from /usr/bin/knife:255:in `<main>'

I encountered something similar and I found that adding e.g. require knife-attribute/node/helpers to the plugin file seems to get the constant included.  That might work for your example here.


matter How many Endpoints can theoretically be added dynamically in the official bridge-app example? (CON-1286)

I want to use the official briage-app example to implement many dynamic Endpoints, but after adding 16, the following error appears. What should I modify?
I (2033) chip[DL]: Added device Channel1 to dynamic endpoint 4 (index=0)
I (2043) chip[DL]: Added device Channel2 to dynamic endpoint 5 (index=1)
I (2053) chip[DL]: Added device Channel3 to dynamic endpoint 6 (index=2)
I (2053) chip[DL]: Added device Channel4 to dynamic endpoint 7 (index=3)
I (2063) chip[DL]: Added device Channel5 to dynamic endpoint 8 (index=4)
I (2073) chip[DL]: Added device Channel6 to dynamic endpoint 9 (index=5)
I (2073) chip[DL]: Added device Channel7 to dynamic endpoint 10 (index=6)
I (2083) chip[DL]: Added device Channel8 to dynamic endpoint 11 (index=7)
I (2093) chip[DL]: Added device Channel9 to dynamic endpoint 12 (index=8)
I (2103) chip[DL]: Added device Channel10 to dynamic endpoint 13 (index=9)
I (2103) chip[DL]: Added device Channel11 to dynamic endpoint 14 (index=10)
I (2113) chip[DL]: Added device Channel12 to dynamic endpoint 15 (index=11)
I (2123) chip[DL]: Added device Channel13 to dynamic endpoint 16 (index=12)
I (2133) chip[DL]: Added device Channel14 to dynamic endpoint 17 (index=13)
I (2143) chip[DL]: Added device Channel15 to dynamic endpoint 18 (index=14)
I (2143) chip[DL]: Added device Channel16 to dynamic endpoint 19 (index=15)
I (2153) chip[DL]: Failed to add device Channel17 to dynamic endpoint 20 with error 137
I (2163) chip[DL]: Failed to add device Channel18 to dynamic endpoint 20 with error 137
I (2173) chip[DL]: Failed to add device Channel19 to dynamic endpoint 20 with error 137
I (2183) chip[DL]: Failed to add device Channel20 to dynamic endpoint 20 with error 137
I (2183) chip[DL]: Failed to add device Channel21 to dynamic endpoint 20 with error 137
I (2193) chip[DL]: Failed to add device Channel22 to dynamic endpoint 20 with error 137
I (2203) chip[DL]: Failed to add device Channel23 to dynamic endpoint 20 with error 137

bridge-app is configured with 16 dynamic endpoints hence you are seeing this error, Please check https://github.com/project-chip/connectedhomeip/blob/master/examples/bridge-app/esp32/CMakeLists.txt#L32 and change -DCHIP_DEVICE_CONFIG_DYNAMIC_ENDPOINT_COUNT=16 to the number that you'd like to configure

Thank


database query to user table on each request

Unless of course we are missing something obvious, we are getting the database hit for getting the request.user on each access to a view which is not using the user at all because of the deault jwt authentication class. I assume we will have to write our own base authentication class If we need the authentication but not the user object every time?
'DEFAULT_AUTHENTICATION_CLASSES': (
'rest_framework_jwt.authentication.JSONWebTokenAuthentication'

I am also considering to fix this situation on my app. I don't know how I will fix.
But before that, I wonder whether checking the user account again is really necessary proccess or not.
Is it needed for security or other reason?

@Blquinn, Is there a built in way in Django to do this? I thought one could selectively load fields from the DB but what if we don't want to hit the DB at all...got a minute for some quick code (doesn't have to work)?

You can check out the related code authenticate_credentials() in rest_framework_jwt/authentication.py.
The reason for hitting DB in this code is to verify the user's activeness.
I could avoid it by writing my own authentication code like below.
After applied this code, I added more code to check the acviceness of user when he log in.
Hope it helps.
settings.py:
'DEFAULT_AUTHENTICATION_CLASSES': (
'user_manager.MyJSONWebTokenAuthentication.MyJSONWebTokenAuthentication',
# 'rest_framework.authentication.BasicAuthentication',
),
MyJSONWebTokenAuthentication.py:
from rest_framework import exceptions
from rest_framework_jwt.authentication import JSONWebTokenAuthentication
from rest_framework_jwt.settings import api_settings
jwt_get_username_from_payload = api_settings.JWT_PAYLOAD_GET_USERNAME_HANDLER
class MyJSONWebTokenAuthentication(JSONWebTokenAuthentication):
def authenticate_credentials(self, payload):
    username = jwt_get_username_from_payload(payload)

    if not username:
        msg = ('Invalid payload.')
        raise exceptions.AuthenticationFailed(msg)

    return username

@hwh7 pretty much summed it up, you have to write a custom auth class for sure.
In my project, I needed to integrate JWT with an existing code base, so I wanted to get an actual user object (my AUTH_USER_MODEL) with a bunch of deferred fields as you said.
Here's my auth class. It is kinda hacky and not necessarily functional.
# -*- coding: utf-8 -*-

from __future__ import unicode_literals, print_function, absolute_import, division

from uuid import UUID
from itertools import chain

from rest_framework_jwt.authentication import JSONWebTokenAuthentication
from rest_framework_jwt.settings import api_settings
from rest_framework import exceptions
from django.contrib.auth import get_user_model
from django.utils.translation import ugettext as _

# Maps user attribute names -> payload variable names
PAYLOAD_FIELD_MAP = {
    'id': 'user_id',
    'username': 'username',
}

User = get_user_model()

class JWTAuth(JSONWebTokenAuthentication):

    def get_deferred_fields(self):
        # I got this from Django's docs on how to get all non-relational field names.
        all_fields = set(chain.from_iterable(
            (field.name, field.attname) if hasattr(field, 'attname') else (field.name,)
            for field in User._meta.get_fields()
            # For complete backwards compatibility, you may want to exclude
            # GenericForeignKey from the results.
            if not (field.many_to_one and field.related_model is None)
        ))
        payload_fields = set(PAYLOAD_FIELD_MAP.keys())
        return all_fields.difference(payload_fields)

    def create_user_from_payload(self, payload):
        try:
            kwargs = {k: payload[v] for k, v in PAYLOAD_FIELD_MAP.items()}
        except KeyError:
            msg = _('Invalid payload.')
            raise exceptions.AuthenticationFailed(msg)

        user = User(**kwargs)
        deferred_fields = self.get_deferred_fields()
        for f in deferred_fields:
            try:
                delattr(user, f)
            except AttributeError:
                pass
        # Not sure if the following is necessary/ a good idea.
        user._state.adding = False
        user._state.db = 'default'
        return user

    def authenticate_credentials(self, payload):
        """
        Returns an active user that matches the payload's user id and email.
        """
        user_id = payload.get('user_id')
        if not user_id:
            msg = _('Invalid payload.')
            raise exceptions.AuthenticationFailed(msg)
        # I use UUID, not necessary if you don't
        try:
            payload['user_id'] = UUID(user_id)
        except ValueError:
            msg = _('Invalid payload.')
            raise exceptions.AuthenticationFailed(msg)

        user = self.create_user_from_payload(payload)

        return user

I didn't end up using this in production code, because it will cause your code to do a round trip to the database, per attribute that isn't in your user model. Therefore, you would want to always call User.refresh_from_db() before accessing more than one non-relational attribute in a a given request. I didn't want to take the risk of missing any refreshes and therefore destroying my database.
In order to avoid tons of round trips I experimented with the following code that I added to my user model:
    def __init__(self, *args, **kwargs):
        super(User, self).__init__(*args, **kwargs)
        self._refreshed = False

    def __getattr__(self, item):
        if not self._refreshed and item not in PAYLOAD_FIELD_MAP.keys():
            self.refresh_from_db(fields=self.get_deferred_fields())
            self._refreshed = True

        return super(User, self).__getattr__(self, item)

This would have to effect of refreshing the whole user model when an unavailable field is accessed, eliminating the change for unwanted round trips. Unfortunately this didn't really work because I was seeing a bunch of round trips getting user fields when I logged my SQL. I do, however, think this would be a nice solution, if it could be made to work.
If I was starting a new project, I would probably use a similar approach, but not return the actual user model with deferred fields, but rather have a plaid JWTUser object that gets passed. It would then have a method to get the full user, when needed.
So, it needs work, but I think there's potential. Let me know if you decide to work on it and your thoughts.

Do you want to fix this issue in the level of django-rest-framework-jwt or by using custom auth class?
authenticate() should returns User object as it is defined in the django doc. If we wanna to fix in the level of django-rest-framework-jwt, I think we should follow it.

@hwh7 My only concern with adding it to the library would be that users need to understand that you will be doing a ton of round trips for the user's properties unless you refresh. It's pretty counter productive towards the goal of this issue if we're causing more round trips for people. That said, maybe it could be included with the library, but not used by default.

Absolutely @Blquinn, it should be an optional extra but is really needed for those of us that don't want the db to be hit to check user 'activeness'.
It definitely shouldn't be the default


Time to change logo again?

See https://blog.golang.org/go-brand
:wink:

I think a protest in the form of extensively keep using the Gopher everywhere is appropriate.

I think a protest in the form of extensively keep using the Gopher everywhere is appropriate.

The gopher is not changing, and the logo has barely changed. This is the old logo, the new one is just a cleaned up version and a document that provides a design language for the pending website and blog redesign.


Added pseudo R-squared metrics to evaluation

Many papers/researchers report pseudo R-squared metrics for case/control traits, such as the Nagelkerke R2 for binary traits. It may be useful to add implementation for this (and other related metrics) in eval.metrics module.
Here are a set of tasks to do:

[x] Add implementation for the Nagelkerke R2
[x] Add implementation for the Cox & Snell R2
[x] Add implementation for the McFadden R2

Here's a reference that may useful for the implementation: https://web.pdx.edu/~newsomj/cdaclass/ho_logistic.pdf

Done in v0.1


📁Docs: Usage page examples need updated

The usage page examples need updated to support the new builder api.

Fixed!


Remove runtime config from exported ledger.

Explain your changes:

Remove the mainnet runtime configuration from exported ledger.

Explain how you tested your changes:

CI

Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[x] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? List them

Closes #15076

!ci-build-me

Merged these changes into #15109


Support authenticated plugin repositories in plugin dependencies

Is your feature request related to a problem? Please describe.
Right now it is impossible to depend on a plugin that is available behind authorised plugin repository
Describe the solution you'd like
Option to add authorisation header that would be copied to requests "as-is" without any changes.
Describe alternatives you've considered
Right now you are able to depend on a plugin that is pre-downloaded on disk but it is annoying

IntelliJ Platform Gradle Plugin 2.0 uses Gradle repositories, which can be customized. It's possible to involve all auth options described in Gradle docs: https://docs.gradle.org/current/userguide/declaring_repositories.html#sec:authentication_schemes


Fixes problem with multiple card forms on the page

When there were multiple card forms on the page at the same time, it was
rendering the template multiple times in each container. This change
sets the container to be only child elements of the form, so that the
correct number of renders happen in the form.

Thank you for your PR!
The container shouldn't have to be a child element of the form, so I'm not sure I want to merge this in. I could be open to adding a data element to the container that marks that it's already rendered, if you'd be up to make that change!


No missing attribute error by mypy

mypy does not warn missing attribute when inheriting BaseModel.
from pydantic import BaseModel

class A:
    x: int

class B(BaseModel):
    x: int

A().y
B(x=1).y

main.py:9: error: "A" has no attribute "y"

Can I check missing attribute for B().y?

Thanks for the question.
I would guess this is because BaseModel implements __getattr__ so mypy can't easily work out whether B().y would raise an AttributeError.
Not really much we can do about this I'm afraid.

I see... Thanks for your reply!


[Survey selector] Show progress spinner while survey loads

SurveySelectorViewModel.activateSurvey navigates to the home screen without waiting for the survey to load. Instead, some a loading spinner should be shown while the survey and LOIs are loading.
@vittorino For recommended UXD.
@shobhitagarwal1612 PTAL for eng?

Can be shown as modal dialog.


feat: rise kit WebView

Basic WebView support in Rise Kit
Playground in controls example loads the Rise Tools home page:

Nice! Add WebView reference here: https://github.com/rise-tools/rise-tools/blob/fd67dda6b1da21904753f59e965611f8ed009d5e/packages/kitchen-sink/tsconfig.json and to the top-level tsconfig.build.json and I think build issues should go away!

Great job Eric!


Issues/305 show current newsletter

Description / Motivation
Highlights newsletter that is currently viewed.
Fixes #305
How Has This Been Tested?
Local and Vercel
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update (non-breaking change; modified files are limited to the /data directory or other markdown files)

Checklist:

[X] I have read the Contributing guide.
[X] My code/comments/docs fully adhere to the Code of Conduct.
[X] My change is a code change.
[ ] My change is a documentation change and there are NO other updates required.
[ ] My change has new or updated images which are stored in the /public/images folder that need to be migrated to Sitecore DAM

📝 Changed routes:

…sletter/[year]/[month]

(view full size)

Commit 4b5ffecdaf40c6a469fb8ad5b23b2ae51928374d (https://developer-portal-2pukl12dz-sitecoretechnicalmarketing.vercel.app).

Update that specific newsletter entry:


Increase coverage on otel/app/defaultconfig and otel/app/defaultcomponents

Which problem is this PR solving?

Increasing coverage for #2514

Short description of the changes

Added the ability to test the factory returned by CreateDefaultConfig()
Added the ability to test otelconfigs
Refactored Merge() to remove an untested line
Increased coverage on defaultscomponents/defaults

jaeger/cmd/opentelemetry/app/defaultconfig (master)$ go test -cover
PASS
coverage: 81.9% of statements
ok  	github.com/jaegertracing/jaeger/cmd/opentelemetry/app/defaultconfig	0.153s

jaeger/cmd/opentelemetry/app/defaultconfig (otel-coverage)$ go test -cover
PASS
coverage: 98.8% of statements

jaeger/cmd/opentelemetry/app/defaultcomponents (master)$ go test -cover
PASS
coverage: 84.6% of statements

jaeger/cmd/opentelemetry/app/defaultcomponents (otel-coverage)$ go test -cover
PASS
coverage: 100.0% of statements

The modified test panics when running locally.

Apologies.  Forgot the config file you noticed above.  It's now been pushed and I believe tests should pass.


Source Code I want to compile into exe?

What is your question?
How do i compile source code? Because i try but it doesnt work. I just started so i have no experience

Read the compiling instructions ig


Openfeign integration not picking requests

I am using both your nice library and the Jaeger spring integration. The Jaeger Spring integration picks up the calls to my Spring service, but does not print send any trace of the resulting Openfeign calls generated by that same service.
In my build gradle I have imported both libraries :
    compile 'io.opentracing.contrib:opentracing-spring-cloud-starter'
    compile 'io.opentracing.contrib:opentracing-spring-jaeger-cloud-starter'

I have a Spring controller that and I have a feign configured class that eventually gets called by a request to that same controller
@RestController
@RequestMapping(value = "/saved-items", produces = APPLICATION_JSON_UTF8_VALUE)
public class SaveForLaterController {

@FeignClient(name = "atg-savedforlater", url = "myurl")
public interface SavedForLaterRestClient {

And I get a query on Jaeger from the Spring mvc side, but not the resulting span from the Feign client side

Am I missing some configuration ? Do I need to explicitly declare the tracer implementation maybe ?

How are you using the feign client? Are you injecting it as a bean? This module https://github.com/opentracing-contrib/java-spring-cloud/blob/master/instrument-starters/opentracing-spring-cloud-feign-starter/src/test/java/io/opentracing/contrib/spring/cloud/feign/FeignTest.java#L97 has tests for feign client. Could you please debug and see whether the Feign auto configurations are enabled and used?

My issue was something specific to my project, closing


A little help for a React newbie..

Does anyone have a fork of this repository that has boilerplate authentication? I like the setup of this project but I've never done authentication with react before, and I'm kind of under the gun. Any help would be appreciated!

I based my code on these guidelines, it worked pretty well (written by Auth0, you may like their products, too):
https://auth0.com/blog/adding-authentication-to-your-react-flux-app/


Support to GPU info connected to computer

Was wondering if it could also gather info on connected devices  to the Computer
like GPUs

You can run the command Get-SystemInfo -Video


Roadrunner to Unreal import

CARLA version: 0.9.14
Platform/OS: Windows
Problem you have experienced:
Hello, I have problem with importing custom map from Roadrunner to Unreal Engine. Although I defined the routes in Roadrunner, after import to Unreal RoutePlanner items are generated weirdly. What should I change to improve this? Thanks

I faced the same problem, did you solve this problem?


ci: release zip archives with binaries

Is the goal to have the chmod +x already set?

Is the goal to have the chmod +x already set?

Yes, it was to prevent this: https://github.com/edgelaboratories/stacks/commit/90c34973789e82ca39f71508e6e1b9b0bb3bbe06#diff-c694712443a5d8a50164ee843d39c90ce2ff46be63d29b535c0c2761fea80edbR65-R67


Question: How to get a Version string manually

I would like to use refreshVersions to set the ktlint version in the ktlint-gradle-plugin:
ktlint {
    version.set("0.36.0") // "_" is not accepted here
    ...
}

Is there some refreshVersions mechanism to pull the Version and use it here or is it ok to use something like project.properties[...]
ktlint {
    val ktlintVersion = project.properties["com.pinterest:ktlint:_"]
    version.set("$ktlintVersion")
    ...
}

The problem with that is that refreshVersions Task removes that version every time it's ran.
Would be nice to know how to handle the not so ordinary cases of dependencies!
Other than that, Greate Plugin!!! It really cleaned up our Project a lot!

Analogical use cases:

Vaadin version for (any) Vaadin plugin
versions for replace by processResouces task in some sort of deployment descriptors ( OSGI/Docker etc)

this is probably going to break but currently works:
import de.fayard.versions.internal.InternalRefreshVersionsApi
import de.fayard.versions.internal.getVersionProperties

@UseExperimental(InternalRefreshVersionsApi::class)
val versionsMap =  getVersionProperties()
versionsMap.forEach { (key, value) ->
    logger.lifecycle("$key : $value")
}

for this to work there needs to be some dependency on what you want to grab though.. otherwise refreshDependencies task will wipe it
maybe you can define a new configuration to gradle that does nothing
@miikeat for you that this code should do the trick:
import de.fayard.versions.internal.InternalRefreshVersionsApi
import de.fayard.versions.internal.getVersionProperties

configurations {
    create("fake")
}

dependencies {
  add("fake", "com.pinterest:ktlint:_")
}

@UseExperimental(InternalRefreshVersionsApi::class)
val versionsMap =  getVersionProperties()

logger.lifecycle("ktlint: ${versionsMap["version.com.pinterest..ktlint"]}")

PS for a nicer key (version.ktlint).. use this rule:
com.pinterest:ktlint:*
              ^^^^^^

could refreshVersions register a no-op configuration automatically?
could this be exposed via a extension ? then it would be possible to call refreshVersions.getVersion("version.jooq") for example

@NikkyAI Thanks! That looks great!
How can I add a custom rules? That would be handy for couple of other dependencies too!

@NikkyAI Thanks
@jmfayard It would be nice to have Public API for that.

Having a public API for that: I appended it to my priority list here: https://github.com/jmfayard/refreshVersions/projects/4#card-38206665
I hope I'll get the time to do it this year.
Thanks @NikkyAI for helping other users!

Hello, the version 0.10.0 added the versionFor function. I hope you like it!


Coordinates on each square should not work in Coordinate trainer

https://lichess.org/training/coordinate
... unless Show coordinates is selected

Also the text of the coordinates is wrong :*(

Fixed in v2.3.62


Can SDL2 be made the highest priority Clipboard provider?

Issue #5792 has shown that on Linux there can be a problem with the clipboard provider of the DE framework under certain circumstances (Wayland in this case). Also, the clipboard provider gtk3 is not accessible in a virtual environment, and the necessary Python bindings aren't easily installable. This was fixed with 1a20a3a.
However, it's probably be better to have SDL2 as the highest priority clipboard provider instead, because that is a core requirement. We would have to make sure that this is completely reliable on all platforms beforehand.
Additionally, only xclip and xsel are Cutbuffer providers at the moment, which seems to enable selection + middle click copy/paste on Linux. We would need to determine, either:

Is that a possibility with SDL2 as well?
Is it desirable to have support for that out of the box, or should it rather be something optional instead?

Note: this seems to work with Xorg and XWayland (which is how Kivy currently runs), but is probably not supported with a native Wayland client anyway. Likewise, xclip & xsel might stop working under Wayland altogether (needs to be tested).

Seems like a good idea to me. However I've had multiple generations of Debian where the sdl2 clipboard provider just straight up does not work at all (in Kivy, I didn't test it separately). I've also seen this reported by a few other users since sdl2 was added, not sure about their distros. If anyone has run into this / done research etc, please share.

Is that a possibility with SDL2 as well?

I doubt it; cut buffers are X specific and obsolete, ref this link

X10 had these things called ``Cut Buffers'' that were a more limited and wasteful predecessor to selections. They are obsolete; don't use them. Some applications (like xterm) still have legacy support for them, but ignore that. [...]

Cut Buffers: | Obsolete. Never, ever, ever use them. Ever.

@bionoid Do you know or remember what versions those are/were. Would be good to have a list of potentially problematic systems for doing some testing (I haven't yet tried to do any of those anywhere).
That's some good info on that page, thanks. I guess what I meant was having support for the Primary clipboard on Linux (selection + MMB). I don't really know why they're called Cutbuffer providers in Kivy. Sounds like that's not a necessity for that.
However, haven't found anything in the SDL2 project yet which would indicate they support that. The clipboard interface there semes to be pretty simple ([1] [2] [3]).

Cutbuffer is causing critical error messages when the Linux system doesn't have xclip and xsel installed:
2024-07-10 11:22:52 [1,301ms] [CRITICAL] [kivy] Cutbuffer: Unable to find any valuable Cutbuffer provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
xclip - FileNotFoundError: [Errno 2] No such file or directory: 'xclip'
  File ".../python/.venv/lib/python3.10/site-packages/kivy/core/__init__.py", line 59, in core_select_lib
    mod = importlib.__import__(name='{2}.{0}.{1}'.format(
  File "<frozen importlib._bootstrap>", line 1129, in __import__
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File ".../python/.venv/lib/python3.10/site-packages/kivy/core/clipboard/clipboard_xclip.py", line 17, in <module>
    p = subprocess.Popen(['xclip', '-version'], stdout=subprocess.PIPE,
  File "/usr/lib/python3.10/subprocess.py", line 971, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)

xsel - FileNotFoundError: [Errno 2] No such file or directory: 'xsel'
  File ".../python/.venv/lib/python3.10/site-packages/kivy/core/__init__.py", line 59, in core_select_lib
    mod = importlib.__import__(name='{2}.{0}.{1}'.format(
  File "<frozen importlib._bootstrap>", line 1129, in __import__
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File ".../python/.venv/lib/python3.10/site-packages/kivy/core/clipboard/clipboard_xsel.py", line 16, in <module>
    p = subprocess.Popen(['xsel'], stdout=subprocess.PIPE)
  File "/usr/lib/python3.10/subprocess.py", line 971, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)

We don't really need the clipboard / cutbuffer, which I believe is not a rare case. Could you make a change to the log level so that the above message is not critical but just a warning?


Capella mainnet release 23.1.1

Release web3signer with mainnet config for Capella. Requires updating Teku to the latest release once available with mainnet config changes.

Blocked waiting latest teku release


Following the docs for kind+Eirini result in a non working cluster

Describe the bug
Follow the docs there:
https://kubecf.io/docs/tutorials/deploy-kind/
(take this PR into account: https://github.com/cloudfoundry-incubator/kubecf-docs/pull/37)
When all pods are up and running, try to push an app (e.g. https://github.com/scf-samples/dizzylizard)
After staging is done, the app pods don't start. They fail with Error: ErrImagePull
Events:
  Type     Reason     Age                   From                           Message
  ----     ------     ----                  ----                           -------
  Normal   Scheduled  <unknown>                                            Successfully assigned eirini/dizzy-default-0b5c24131a-3 to kubecf-control-plane
  Normal   Pulling    23m (x4 over 24m)     kubelet, kubecf-control-plane  Pulling image "<IP_ADDRESS>:31666/cloudfoundry/1056bd51-07bd-4e84-9a2c-f907e68d73b4:362379573001a18c2b4671ae9fbeb9ba17be290e"
  Warning  Failed     23m (x4 over 24m)     kubelet, kubecf-control-plane  Failed to pull image "<IP_ADDRESS>:31666/cloudfoundry/1056bd51-07bd-4e84-9a2c-f907e68d73b4:362379573001a18c2b4671ae9fbeb9ba17be290e": rpc error: code = Unknown desc = failed to pull and unpack image "<IP_ADDRESS>:31666/cloudfoundry/1056bd51-07bd-4e84-9a2c-f907e68d73b4:362379573001a18c2b4671ae9fbeb9ba17be290e": failed to resolve reference "<IP_ADDRESS>:31666/cloudfoundry/1056bd51-07bd-4e84-9a2c-f907e68d73b4:362379573001a18c2b4671ae9fbeb9ba17be290e": unexpected status code [manifests<PHONE_NUMBER>01a18c2b4671ae9fbeb9ba17be290e]: 400 Bad Request
  Warning  Failed     23m (x4 over 24m)     kubelet, kubecf-control-plane  Error: ErrImagePull
  Warning  Failed     9m58s (x64 over 24m)  kubelet, kubecf-control-plane  Error: ImagePullBackOff
  Normal   BackOff    4m57s (x86 over 24m)  kubelet, kubecf-control-plane  Back-off pulling image "<IP_ADDRESS>:31666/cloudfoundry/1056bd51-07bd-4e84-9a2c-f907e68d73b4:362379573001a18c2b4671ae9fbeb9ba17be290e"

To Reproduce
See above
Expected behavior
The application pod should be up and running
Environment
kubecf v2.6.1 on kind v0.9.0 go1.15.2 linux/amd64
Additional context
Add any other context about the problem here.

I hit this same issue, kubecf v2.6.1 on kind v0.9.0 go1.13 linux/amd64. Was wondering if it had something do to with the cert instructions. The command does succeed but differs from that at the bottom of https://kubecf.io/docs/tutorials/deploy-k3s (cert location is from a bits-service-ssl secret rather than the node's system). Could be a red herring, kind vs k3s, but thought it worth mentioning.

I replaced the opi image in the eirini pod with jimmykarily/opi which is an image I built using the same code but disabling the code that deletes the staging job after it's done (more here: https://github.com/cloudfoundry-incubator/kubecf/issues/1323#issuecomment-692530753). It seems that the uploader init container never succeeds:

┌────────────────────────────────────────────────────────────────────── Containers(eirini/dizzylizard-default-6cmpb)[3] ──────────────────────────────────────────────────────────────────────┐
│ NAME↑                    PF     IMAGE                                                            READY      STATE          INIT           RESTARTS PROBES(L:R)      PORTS      AGE          │
│ opi-task-downloader      ●      registry.suse.com/cap-staging/recipe-downloader:1.8.0-24.56      true       Completed      true                  0 off:off                     5m27s        │
│ opi-task-executor        ●      registry.suse.com/cap-staging/recipe-executor:1.8.0-24.56        true       Completed      true                  0 off:off                     5m27s        │
│ opi-task-uploader        ●      registry.suse.com/cap-staging/recipe-uploader:1.8.0-24.56        false      Completed      false                 0 off:off                     5m27s        │
│
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘                                                                                │

but it doesn't print an error either.

Can't tell for sure if the staging container worked or not. What I do see though is an error in the singleton blobstore pod:
~/dizzylizard (master)*$ kubectl  logs -n kubecf singleton-blobstore-0  -c blobstore-nginx
nginx: [alert] could not open error log file: open() "/var/vcap/packages/nginx_webdav/logs/error.log" failed (13: Permission denied)

execing in the pod shows that the nginx process is started by user vcap but that dir is owned by root. Not sure if it's relevant to the failed staging but something to look at for sure (may have to do with changes in the stemcell).
Also this may be relevant:
https://github.com/cloudfoundry-incubator/kubecf/commit/31dc889eaf7b71b02e396d59f959275f9927756b#diff-6cef92220d2f63c1a73bbbeca21e2d1a7c08d210fbf109a08ee08bae91e723a1

I tried deploying v2.6.1 using the make targets in kubecf:
$ git checkout v2.6.1
$ make kind-start
$ make all

and after all pods are up and running, pushing the example app (dizzylizard) works. So, I realized it must have something to do with how kind is setup, because make kind-start is doing some preparation to the cluster, other than simply calling kind create cluster: https://github.com/cloudfoundry-incubator/kubecf/blob/master/scripts/kind-start.sh
To verify, I created a fresh cluster with make kind-start and then I followed the docs to deploy kubecf like in the description (thus the only difference to the reproduction steps was the way I created the kind cluster). Pushing the app works in this case.
So it seems that something in what make kind-start is doing, is necessary to make things work. We need to find out what that is and document that in the documentation page.

ok new data: Simply using ``` kind create cluster     --image "kindest/node:v1.17.5" and then following the docs makes it work. The problem is with the k8s version. The make target is pulling 1.17.5 while the command from the docs simply pulls latest (which doesn't work). Is 1.19 already supported by kubecf @viovanov ? If not then I will simply update the docs to use a supported version (preferably  1.17.5 which is known to work).


eve-ng 5.0.1-13

EVE-NG v5.0.1-13 Community Edition
First export attempt on CHR 6.49.6 (existing configured CHR) indicates starting export but no prompt is given and does not complete. When trying to export same CHR on second attempt error is given - ERROR: "Failed to lock the lab (60061)."

Same here with 6.48.6LT

Same here with 6.48.6LT

Is the problem for 6.48.6LT is for the same version EVE-NG v5.0.1-13 Community Edition ?
This both reported issues are related to export function ?
How the configuration was apply

Manually added configuration
CHR apply it on first boot
problem happen when configuration was edited and export action fail
OR
CHR without configuration
Manually configured CHR
export function fail ?

Regards

I found the problem,
I sure ros admin user password was set!
I will update the README with more information about the problem.
The short story: I order to export/import config the script (and I think this is valid for all eve-ng vm/os's ) script use telnet (console connection to the ros), however when password is set script cannot login in order to export/import
For now please DO NOT set admin password, if you config the vm via console and see "new password" just press "ctl+c" or via windbox just ignore prompt for new password, also do not se password via import script!
The story is more complicated and is not related to the script !
How this can be solve is more related to eve-en - PHP code ..
As I say, I will update the README with more details.

README notes are  update


.

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

Project coverage is 45.45%. Comparing base (1bee594) to head (1e26167).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #24   +/-   ##
=======================================
  Coverage   45.45%   45.45%
=======================================
  Files          13       13
  Lines          44       44
=======================================
  Hits           20       20
  Misses         24       24

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


review / refactor tests/constants.py

This looks to me currently a bit overengeenered.  On github also each worker creates anyway a new tmp dir.
Is there any case on local development where we need a second information about the state of the git repository?
try:
    import git
except ImportError:
    SHA = ""
else:
    path = os.path.dirname(os.path.realpath(__file__))
    repo = git.Repo(path, search_parent_directories=True)
    logging.debug(path)
    try:
        # this is for local development important to get a fresh named tmpdir
        SHA = repo.head.object.hexsha[0:10]
    except (ValueError, BrokenPipeError) as ex:
        logging.debug("Unknown Problem: %s", ex)
        # mounted dir in docker container and owner is not root
        SHA = ""

ROOT_FS = TempFS(identifier=f"msui{SHA}")

Catch specific exceptions instead of general ValueError and BrokenPipeError. Consider git.exc.InvalidGitRepositoryError

Can I work on this issue?

Welcome @YashaswiniTB I assigned it to you.

This looks to me currently a bit overengeenered. On github also each worker creates anyway a new tmp dir. Is there any case on local development where we need a second information about the state of the git repository?
try:
    import git
except ImportError:
    SHA = ""
else:
    path = os.path.dirname(os.path.realpath(__file__))
    repo = git.Repo(path, search_parent_directories=True)
    logging.debug(path)
    try:
        # this is for local development important to get a fresh named tmpdir
        SHA = repo.head.object.hexsha[0:10]
    except (ValueError, BrokenPipeError) as ex:
        logging.debug("Unknown Problem: %s", ex)
        # mounted dir in docker container and owner is not root
        SHA = ""

ROOT_FS = TempFS(identifier=f"msui{SHA}")

pls try this
import os
import tempfile
import logging
def get_git_sha():
try:
from git import Repo
except ImportError:
logging.debug("GitPython not installed, skipping SHA retrieval")
return ""
try:
    path = os.path.dirname(os.path.realpath(__file__))
    repo = Repo(path, search_parent_directories=True)
    sha = repo.head.object.hexsha[:10]
    logging.debug(f"Git SHA: {sha}")
    return sha
except Exception as ex:
    logging.debug(f"Failed to get Git SHA: {ex}")
    return ""

Use a unique identifier for the temporary filesystem
unique_id = f"msui{get_git_sha()}"
ROOT_FS = tempfile.mkdtemp(prefix=unique_id)

This looks to me currently a bit overengeenered. On github also each worker creates anyway a new tmp dir. Is there any case on local development where we need a second information about the state of the git repository?
try:
    import git
except ImportError:
    SHA = ""
else:
    path = os.path.dirname(os.path.realpath(__file__))
    repo = git.Repo(path, search_parent_directories=True)
    logging.debug(path)
    try:
        # this is for local development important to get a fresh named tmpdir
        SHA = repo.head.object.hexsha[0:10]
    except (ValueError, BrokenPipeError) as ex:
        logging.debug("Unknown Problem: %s", ex)
        # mounted dir in docker container and owner is not root
        SHA = ""

ROOT_FS = TempFS(identifier=f"msui{SHA}")

The SHA is being used as an identifier for the TempFS, presumably to create unique and consistent temporary filesystems during local development.
However, as you pointed out, in many environments (like GitHub Actions), a new temporary directory is created for each run anyway, making this extra identifier potentially unnecessary.
For local development, having the SHA in the identifier could potentially help in tracking changes across different commits or branches, but this benefit might be minimal in most cases.
The current implementation has error handling for cases where the git repository information can't be retrieved, falling back to an empty string for the SHA.
import os
import tempfile
import logging
def get_git_sha():
try:
from git import Repo
except ImportError:
logging.debug("GitPython not installed, skipping SHA retrieval")
return ""
try:
    path = os.path.dirname(os.path.realpath(__file__))
    repo = Repo(path, search_parent_directories=True)
    sha = repo.head.object.hexsha[:10]
    logging.debug(f"Git SHA: {sha}")
    return sha
except Exception as ex:
    logging.debug(f"Failed to get Git SHA: {ex}")
    return ""

Use a unique identifier for the temporary filesystem
unique_id = f"msui{get_git_sha()}"
ROOT_FS = tempfile.mkdtemp(prefix=unique_id)


docs: need examples for how to build with archive data

from db api
from storage .json files
with nextjs, with streamlit, etc

For inspiration, I think should look in the direction of Supabase's docs. They have these "quick starts" for each language

https://supabase.com/docs/guides/getting-started
Would also be powerful to have a Glitch/CodePen/JSFiddle. Like so people can open it in their browser and see how to access the data, and play with the code to display like, the tweet that has the fewest word, the tweet that has the longest word, whatever you want to explore
(that would help onramp people who are still deciding whether it's worth cloning/contributing/learning how to use the API)


How use in windows?

my code:
async def main():
    client = Client(
        api_id=API_ID,
        api_hash=API_HASH,
        library_path='./lib',
        phone_number=PHONE_NUMBER
    )

    async with client:
        me = await client.api.get_me()
        logging.info(f"Successfully logged in as {me.json()}")
if __name__ == '__main__':
    logging.basicConfig(level=logging.INFO)
    asyncio.run(main())

error:
FileNotFoundError: Could not find module 'D:\Desktop\tg_use_wls\lib' (or one of its dependencies). Try using the full path with constructor syntax.

You should provide path to tdlib binary, not to directory containing it. For example
client = Client(..., library_path="./lib/tdlib.dll")

You should provide path to tdlib binary, not to directory containing it. For example
client = Client(..., library_path="./lib/tdlib.dll")

I don't have tdlib.dll at my td installer dir.

You have to build a binary yourself. This library provides binaries only for MacOS and Linux.
Please follow build instructions for Windows by TDLib: https://tdlib.github.io/td/build.html?language=Python


Update README.md

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Pranita Dane


Figure out how to handle the result of governance moderation

Options:

Fork the Cosmos Governance module, adding a new proposal type for content moderation. Add events to signal the result of governance votes, so rewards can be paid out (or slashed). Furthermore, the post and upvotes have to be either deleted or flagged, or curation has to resume, accounting for the moderation delay.
See if just a text proposal is enough, but if its possible to hook into the results to do the redistribution.

Fork the Cosmos Governance module, adding a new proposal type for content moderation. Add events to signal the result of governance votes, so rewards can be paid out (or slashed). Furthermore, the post and upvotes have to be either deleted or flagged, or curation has to resume, accounting for the moderation delay.

+1, I think it makes sense to fork it.

Closing until there's a data layer.


Modify AstroPredictor to accept an in-memory checkpoint.

This is in support of rail_deepdisc issue 9

This work was done before the config refactor was merged to main. Rebasing has proven difficult. I've moved the important changed to PR #84. Closing this one.


enhanced tags

What does this PR?
Where should the reviewer start?
Steps to reproduce
Issue number
https://github.com/esteemapp/esteem-mobile/issues/569
Screenshots/Video

tags are not showing on android @ue

@ue fixed


luci-app-attendedsysupgrade: lua code for acl.d

re add lua code to handle content of acl.d/. This should enable users to
use the luci-app without having the full snapshot luci installed, e.g.
trying the app from 17.01.2
Signed-off-by: Paul Spooren<EMAIL_ADDRESS>

@jow- ping


use flash-attn via xformers

fixes https://github.com/vllm-project/vllm/issues/485#issuecomment-1693821853

Hi @tmm1 thanks for letting us know the performance issue and submitting the PR.
While using FA2 might improve the performance, we have concerns in using it because it does not support 1) attention bias like ALiBi, V100 GPUs, FP32 data type, and head_size 256 (which is used for GPT-J). So, to use FA2, I believe we should make a fallback option to xformers cutlass backend.

So, to use FA2, I believe we should make a fallback option to xformers cutlass backend.

thanks @WoosukKwon, I updated the PR to allow xformers to fallback

So, to use FA2, I believe we should make a fallback option to xformers cutlass backend.

thanks @WoosukKwon, I updated the PR to allow xformers to fallback
cc @danthe3rd

Hi @tmm1 , I am very interested in your PR. I see the PR does not allow xformers to fallback.

Hi, xformers maintainer here
The way it's setup in this PR allows xformers to decide which backend to use - this is also what we recommend. It will use by default Flashv2 if available, but will fallback to cutlass if it's not available (eg if using a custom bias, fp32 or v100).

Hi @danthe3rd , thanks for your explanation. I just wonder why xformers.ops.memory_efficient_attention_forward does not been used in the decoding stage? The API has used in the prefill stage in vLLM.  Hand-written kernel may have lower perf than xformers if we are not an expert of CUDA.

At the moment, memory_efficient_attention is optimized the training mostly. We have a backend for inference, but it's not fully optimized for all cases, but we're working on it :)

At the moment, memory_efficient_attention is optimized the training mostly - which is similar to the prefilling stage in terms of problem sizes. We have a backend for next token decoding, but it's not fully optimized for all cases, but we're working on it :)

Thanks a lot. So it makes sense that most llm inference framworks has hand-written cuda kernel for fused attention impl.

For allow xformers to pick the best available implementation, I don't quite understand this change, so how should I use flash?


Add pool description/name editting

[ ] Update pool name
[ ] Update pool description

Currently the only way to do this would be via the admin panel...


Generalized Notary Client External Signer/HSM Interface

I'm new to TUF and notary but I'm familiar with the corporate software signing operations at the company where I work. We use a network-based HSM solution for signing that handles our large organization problems - problems like corporate access control and authorization of signing requests,  ability to do signing requests from data center VMs that don't have accessible usb ports, etc. etc.
As we investigated signing for docker images we've found the most important private keys are stored on the notary client machine or a local yubikey.  Neither of these solutions satisfies the signing needs of a large organization like ours.  I looked through other notary issues and I am excited to see several folks talking about extending the keystore/HSM support on the client. However, unless I'm mistaken (which is entirely possible), it appears the writers of these issues propose to modify notary client to work with their specific HSM and/or their specific PKCS#11 interface package.   This is all good, but takes notary down a (never ending?) path of supporting all sort of different variants of HSMs and HSM interfaces inside the client.  Might it be better to have one external interface for all this?
So, what I'm proposing here is a generalized "external keystore" plugin solution -- some sort of proper interface/API where any interested party could write a plugin to teach the notary client to interact with their specific HSM/keystore needs -- such that the code that interfaces with that keystore/HSM would be outside notary.   The interface wouldn't be PKCS11 or KMIP or MS-CAPI -- instead it would be a notary defined plugin interface anyone could write a plugin to for whatever local or remote HSM/keystore they need accessible from the notary client.   With such an API in place, the notary client would instantly have a compatibility story for interacting with any local or remote keystore/HSM/HSM system without having to muck with notary itself.
Thoughts?  After writing all this I found the trustmanager remoteks grpc interface, but that seems to be solving a different problem.   Could it be used/extended/adapted for this purpose?

Hmm, I think the hope was that PKCS11 was standard enough to be supported by the devices people use, and that the current work on restructuring that would make it easier to use with other devices. What APIs are you interested in supporting? I have had recent interest in better HSM integration just yesterday, so interested in this area.

PKCS#11 is fine for communicating with local HSM hardware.  However, with the advent of this cool thing called the network, commercial enterprise-level HSMs systems aren't typically local to the machine that needs the signing done.  Those sorts of systems will typically want KMIP.     Then there's folks like me that have to interact with highly customized systems.  I will be coding to a RESTful API for HSM access.   The point is, there's a whole world here.  I'm trying to think strategically and get the complications of every HSM protocol and environment out of the notary client -- create a higher level API and let the community take care of it.   That's why I used words like "plugin" in the write-up above.    What's the easiest way to have an interface out of the notary client and into a 3rd party provided local app that handles all the specifics of their HSM/keystore setup?  That's what's needed.

@dbilling if you're planning for a RESTful API, you might instead want to look at the GRPC based remote signer interface we've already defined: https://github.com/theupdateframework/notary/tree/master/trustmanager/remoteks
I apologize that I never really got around to writing up docs for it. I'll look into that over the upcoming labor day weekend.

Actually, I'm looking at that again and it's more about key escrow. It implements the trustmanager.Storage interface. I'd intended but I guess never got round to implementing a similar GRPC interface for the trustmanager.KeyStore interface. In that instance the concrete underlying struct that implemented the PrivateKey interface would make additional GRPC calls when its Sign method was called.
I feel like the code for that may be sitting in a stale PR and never got merged due to lacking priority. I'll see if I can dig it up

Hi @endophage, I'm a GRPC newbie, but this all sounds super interesting and I'd be quite happy to learn and use GRPC for my interoperability case if that's how you experts want to handle the "how do we let others plugin their network-based HSM" problem for the notary client.   It does look from your second post like the current support for GPRC solves a different issue and is not quite enough to handle the keystore case, if I read all that correctly.  Let me know what you need from me... I'd be happy to reorganize/repurpose this issue for that support, close this one and open another, and/or help in anyway necessary make this happen...

GRPC is ultimately implemented over HTTP2. I see it as providing 2 key advantages over designing and building a RESTful API directly:

Clear definition of the available "routes" in the .proto file.
Compilation of client and server libraries in many languages, making integrations faster and more consistent.

The current state is not that GRPC itself solves a different problem it's that we haven't yet defined the GRPC interface and integrated it into notary for your specific use case (and we did intend to support your use case at some point).
This issue hasn't gotten too long so I'm happy to keep this as the issue for defining the remote signing interface. Any existing code would likely be in this PR and there would be a distinct proto file defining the remote signer interface. As I'm not seeing that proto file I'm pretty sure there's no existing code.

Sounds like we have a good plan on how to solve the problem, but there's no existing work/stale PR for this specific grpc use case.   @endophage, is this something you'd prefer to code up or would you rather I put together a contribution?

@dbilling to keep it focussed, why don't you start by proposing a .proto definition for the GRPC interface that would back a remote instance of the KeyStore. The GRPC interface would necessarily also implement the PrivateKey interface.
I'd anticipate GetKey would essentially be a quick lookup on the KeyID and would return a pseudo-PrivateKey that holds the KeyID and passes through calls to Sign to the GRPC service.

@endophage @justincormack,  I've taken a look at this and I have a proposal grpc .proto to share...what's your preferred method for starting a discussion/getting feedback on the .proto file?    Along the way, I've come up with  the following questions:

In truly secure environments, HSMs generate key pairs and never expose the private key at all.  Can the current trustmanager.KeyStore interface handles this case? If not, do you have a suggested solution to the problem where public key/pseudo private key needs to get into the notary client from the HSM but the private key material never leaves the HSM, ever.  My idea is
Does notary require a one-to-one mapping between a keyinfo (GUN/role) and a key pair?  or can multiple GUNs share the same key?  GetKeyInfo() seems to imply that each key pair is tied uniquely to one GUN/role, but the rest of the interface seems to specifically allow for multiple GUNs to share a key.
What key types/signature types need to be supported over the grpc interface?  obviously the most important is ecdsa/ecdsa, but if other key types/sig types are necessary across this interface pls let me know the list.
Similar to above, within ecdsa, should the interface support different curves?
A Somewhat related question:  I can't figure out how someone would move trust data between notary servers without resigning.  The use case here for docker is:   a docker image is posted to docker.io (registry A) and signed by "Author".    Some consumer of this image ("Joe") wants a copy of the image in a different registry (registry B).  In the docker world, he'd do a pull from A, tag for B, and a push to B.  However, Joe wants to keep the original trust data intact (he wants the unmodified image in registry B to still be signed by "Author", not by "Joe".   Is this possible?  Such a feature that allows for trust replication will be critical when trust pinning is finally arrives in docker.

@dbilling We generally use PR's for any type of code review, even early stage proposals. Regarding your other questions:

KeyStore can't handle this today. I'd suggest creating a new interface something like KeyGenerator and having the concrete HSM KeyStore implementation define that method. The Create method on CryptoService could then iterate the KeyStores attached to the CryptoService and do a type check to see if any of them implement KeyGenerator, falling back to its current behaviour if none of them do.
The tight coupling of keys to guns is for the most part unintentional tech debt. It seemed like a better idea 3 years ago than it turned out to be. There are some security benefits in not re-using keys, but it also means most users have to juggle a lot of keys, which comes with its own set of security downsides. I'd want the input of the other maintainers, but I'd be more than OK with starting to unwind the coupling.
I'd want to see at least one RSA 4096 based scheme supported in addition to ECDSA.
Possibly making point 3. moot, is it possible to make the interface indifferent to the algorithm?
The CLI doesn't really make it possible today (in this case there's definitely some code in a PR somewhere), but a bit of curl and bash can absolutely do it. If you pull the current trust data from one server and upload those files as a multi-file upload to the other under the same name, it'll work fine. The issue we've historically run into with Docker itself is that image names and registry locations are tightly coupled. I think there has been some progress on that front in Docker but I don't have anything specific to point to (maybe @justincormack can help there?).

Yes we definitely want to be able to support interfaces that can't expose private keys.
Agree with David, starting to change this would be good.
RSA 4096, ed25519, ECDSA p256 cover most cases (although there are still two padding schemes for RSA that are common).
Support for different curves in ECDSA is not commonly used. While it would be nice to make the interface indifferent, I think there are HSMs that require the format to be specified so we probably need a list.
We are trying to fix the naming issue with Docker, and are planning more work towards this, as it is a problem. There is some mirroring configuration support at present but it needs extending to support authentication better, and further extensions to decouple naming, but we want to resolve this soon as it is very limiting.

I should have been more clear re. 1. We already support not exposing private keys for signing. It's only the creation that needs to be updated. The existing Yubikey code returns a type that implements the PrivateKey interface but can't actually return the private key bytes. It simply allows you to call Sign which passes through to the Yubikey's signing functionality.

@dbilling - thanks for this PR and your work - controlling and auditing access to key material is super-important in cloud automation scenarios. Looking forward to see this PR get merged.
I am interested in this since this can be used to use cloud key vault (Azure Keyvault) to store notary signing keys to satisfy security and compliance requirements when using Docker Content Trust. Would be great to have reference implementation of remote keystore server.

Hi @alukan -  Thank you for the encouragement.  I am motivated to continue to move this toward a merge.  In regards to your reference implementation question, The trustmanager/grpckeystore/client_test.go file does contain the all the framework necessary for building a matching server in go, although it also contains code to test code intermingled in.   This week I'm going to update the PR to add a test or two and hopefully see if I can get the attention of the admins.

hey @dbilling, any updates on your progress?

Hi, Any updates on this ?


Making custom_pip_install.sh Windows friendly.

Towards #1123.

Now that pip uses a wheel cache by default, could we find a way to drop the use of custom_pip_install.sh altogether, a la https://github.com/travis-ci/travis-ci/issues/1531?
The Travis caching docs suggest that the following might work:
cache:
  directories:
    - wheel_house

I've thought about that a lot :grinning: However, I wanted to vet that this does what our current setup does and don't want to use the cycles and I wrap up some of these other pending things.
I'm not sure what's causing the error, it doesn't fail on my Ubuntu or Windows machines. I think it's the use of $* in ./custom_pip_install.sh $*

@tseaver Bump

Though this black magic is neat, it's much better to just remove the file: #1350


fix(aws-s3): hotfix for AWS S3 endpoint

yarn build
yarn run v1.22.19
$ npm run build:types && npm run build:js

<EMAIL_ADDRESS>build:types
tsc

src/util/functions.ts:168:37 - error TS2339: Property 'endpoint' does not exist on type '{ region: string; access_key_id: string; secret_key: string; defaultBucketName: string; }'.
168           endpoint: config?.aws_s3?.endpoint || undefined,
~~~~~~~~
src/util/functions.ts:169:43 - error TS2339: Property 'forcePathStyle' does not exist on type '{ region: string; access_key_id: string; secret_key: string; defaultBucketName: string; }'.
169           forcePathStyle: config?.aws_s3?.forcePathStyle || undefined,
~~~~~~~~~~~~~~
Found 2 errors in the same file, starting at: src/util/functions.ts:168
error Command failed with exit code 1.

Hello, could you keep your pull request (PR) with only the AWS hotfix? The sharp fix can be done in a separate PR, but I will correct it directly in the library since it's an issue there.


Performance issues

Querying a lot of rows has a severe performance impact on the gui client :( On postgres (tried with redshift), the app just froze after querying 100k rows. I think it's a different issue to #129.

Would be awesome don't have this performance issues anymore. Last time I debugged that, the main problem was the process of converting data to plain objects from the lazy load objects coming from IPC call in the main process.
Unfortunately, we need to do that because redux states depend on plain objects to handle changes in the app state. Without that hack, the app as getting some pretty messed up state problems.
But I have never seen other people describing this kind of issue in other projects. Probably there is a way to solve that.


Do you like to see Dingo\Api\Routing\Route.php extends from \Illuminate\Routing\Route.php?

Dingo Route.php does similar routing handling like Illuminate core. I think it's better to go closer to the core as possible as we can.
What do you think?
I was able to solve all these errors popped with Laravel 5.5.
   …/laravel/app    master   docker exec -it laravel_web_1 php artisan api:routes
+----------------------------------+----------+------+---------+---------+-----------+------------+----------+------------+
| Host                             | Method   | URI  | Name    | Action  | Protected | Version(s) | Scope(s) | Rate Limit |
+----------------------------------+----------+------+---------+---------+-----------+------------+----------+------------+
| api.laravel.thilangapitigala.dev | GET|HEAD | user | profile | Closure | No        | v1         |          |            |
+----------------------------------+----------+------+---------+---------+-----------+------------+----------+------------+
Need to test against a full application.

This sounds good to me.


Non Fatal error when any of the three "EvtxECmd, RECmd, and SQLECmd" folders do not exist if there is a file to update.

Hi Andrew,
Just noticed the following errors after trying to update:

Details
* Files to download: 1
* F:\Triage\KAPE\Modules\bin\ZimmermanTools\net6 does not exist. Creating...
VERBOSE: GET with 0-byte payload
VERBOSE: received 82580608-byte response of content type application/zip
* Downloaded EZViewer.zip (Size: 82,580,608) (net 6)

* Saving downloaded version information to F:\Triage\KAPE\Modules\bin\ZimmermanTools\!!!RemoteFileDetails.csv

[2022/04/20 05:20:44] | Copying EvtxECmd, RECmd, and SQLECmd and all associated ancillary files to F:\Triage\KAPE\Modules\bin
Copy-Item: F:\Triage\KAPE\KAPE-EZToolsAncillaryUpdater.ps1:374
Line |
 374 |          Copy-Item -Path $folder -Destination $kapeModulesBin -Recurse …
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot find path 'F:\Triage\KAPE\Modules\bin\ZimmermanTools\net6\EvtxECmd' because it does not exist.

Copy-Item: F:\Triage\KAPE\KAPE-EZToolsAncillaryUpdater.ps1:374
Line |
 374 |          Copy-Item -Path $folder -Destination $kapeModulesBin -Recurse …
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot find path 'F:\Triage\KAPE\Modules\bin\ZimmermanTools\net6\RECmd' because it does not exist.

Copy-Item: F:\Triage\KAPE\KAPE-EZToolsAncillaryUpdater.ps1:374
Line |
 374 |          Copy-Item -Path $folder -Destination $kapeModulesBin -Recurse …
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot find path 'F:\Triage\KAPE\Modules\bin\ZimmermanTools\net6\SQLECmd' because it does not exist.

[2022/04/20 05:20:44] | Copied EvtxECmd, RECmd, and SQLECmd and all associated ancillary files to F:\Triage\KAPE\Modules\bin successfully
[2022/04/20 05:20:44] | Copying remaining EZ Tools binaries to F:\Triage\KAPE\Modules\bin

I think we need an if statement to determine if we are expecting to update these folders, if not than skip.
Let me know if you would like me to submit a pull request and I can fix it up.
Thank you

Please go ahead and do a PR!


WMS ID 5521: Setting Up Active Data Guard For On-Premises, fixed some issues

Add here your WMS ID
5521
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[ ] All filenames are lower case (including folders, images, files, etc.)
[ ] Filenames are descriptive
[ ] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[ ] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[ ] Image references in markdown contain an alternate text

Is test markdown used in the main workshop project?

Yes. It's the name of the lab, not really for test.
Madhusudhan Rao @.***> 于2022年12月5日周一 12:29写道：

Is test markdown used in the main workshop project?
[image: image]
https://user-images.githubusercontent.com/70625227/205549646-79c35133-b5eb-418e-bc64-271dfc0e5334.png
—
Reply to this email directly, view it on GitHub
https://github.com/oracle-livelabs/pts/pull/54#issuecomment-1336737819,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOCNSQQEFKLMEKH4V2YVASDWLVVRFANCNFSM6AAAAAASTJDI6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>


Service Bus Extension v5 - host.json - sessionHandlerOptions

The v5 host.json settings sections says:

When you set the isSessionsEnabled property or attribute on the trigger to true, the sessionHandlerOptions is honored

But there is no sessionHandlerOptions section shown. Either the text is wrong or the example+table - which is it?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0440205f-adcc-0fc5-3adb-db4dbe1d1292
Version Independent ID: 14ad1300-590c-8102-6887-366078e1882a
Content: Azure Service Bus bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-service-bus.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@fowl2 Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@fowl2 This section talks about the host.json setting and the property table will only show the configuration that is applicable only to host.json setting
As the section mentions that isSessionsEnabled can be used as an attribute or property on the trigger (not to the host.json setting) as documented here.

When you set the isSessionsEnabled property or attribute on the trigger to true, the sessionHandlerOptions is honored.

@MayankBargali-MSFT thanks for the reply! I'm still not 100% on how to specify these settings - if they are not available via host.json, what code do we need?


This is just a fact of life, as the document will load too fast before Publisher Interface can connect up. Need to update the documentation to mention this situation


feat: Support Athena query prepared statements & Athena parameterized queries

Feature or Bugfix

Feature

Detail

Support Athena query prepared statements
Support Athena parameterized queries
Using parameterized queries

Relates

#2325

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: ab54de68f686a7372b6ad0e8696650a691965a7a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: ab54de68f686a7372b6ad0e8696650a691965a7a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 5ad88ff22d3cb38d704107f39782790f72c2a41d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 5ad88ff22d3cb38d704107f39782790f72c2a41d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 26b3fc72f98791d78fe123a5f427050159bf18c3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: bc2c3cf17dda9d27342724f168ce017830d0f94f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 5ef44fa493a590155dc92ac6dd8f3d4f5b7f4f13
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 3ed18e0556cd4715ecf4336cc80bb8bfc8635702
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 3ed18e0556cd4715ecf4336cc80bb8bfc8635702
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 3ed18e0556cd4715ecf4336cc80bb8bfc8635702
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: d7b182c1297618475a8ece16e5f04f2a0d48c8bb
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: d7b182c1297618475a8ece16e5f04f2a0d48c8bb
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: a00f63c6776b5bb9c481e740a3992104a72e07ef
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: a00f63c6776b5bb9c481e740a3992104a72e07ef
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: a00f63c6776b5bb9c481e740a3992104a72e07ef
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 12162f98eff629bdbe3be11f8aacab6872d9cfd9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 12162f98eff629bdbe3be11f8aacab6872d9cfd9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: bd32da9479f75e552b251ca308e14506161207d4
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: bd32da9479f75e552b251ca308e14506161207d4
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: d02b0d562d7dcadaf86a59c77c25c0f250b8e219
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Big endian support for arrays

Handling of big="" tag for arrays

Please amend your commit with the "-s" option so the DCO is approved.
Very quality change, thanks for your contribution!


added my githubID in the member's list

This change is

/assign @theadactyl

Thanks @Gaurang10 can you point to some of your PRs?

This is first time I am trying to contribute to an open source project.

That's great. Have you seen our contributor guide?
https://www.kubeflow.org/docs/about/contributing/#joining-the-kubeflow-github-org
We generally ask you to submit a couple of PRs first before joining the GitHub org.

Oh.. I missed it. Let me try to find some issues to raise PR. Thanks.

Thank you. I'll close this PR for now. Feel free to reopen later on after submitting some PRs.