HTMLEditorExtender image upload

Similar to https://github.com/DevExpress/AjaxControlToolkit/issues/43
The AJAX Control Toolkit \16.11
The installation method  NuGet package
Minimal steps to reproduce the bug
Created a minimal web site, 1 page, dropped the HtmlEditorExtender on it. Attached it to a text control.
Added the full Toolbar suite, including the image upload.
Added the entry in web.config
<handlers>
<add name="AjaxFileUploadHandler" verb="*" path="AjaxFileUploadHandler.axd" type="AjaxControlToolkit.AjaxFileUploadHandler, AjaxControlToolkit"/>
</handlers>
in the code-behind (c#) Added an event handler for ImageUploadComplete
ran the page, F12'd the browser diagnostic, tried to add an image.
It never got as far as the c# event - got client error.
Console window says:
HTTP404: NOT FOUND - The server has not found anything matching the requested URI (Uniform Resource Identifier).
(XHR)POST - http://localhost/AjaxFileUploadHandler.axd?contextKey={DA8BEDC8-B952-4d5d-8CC2-59FE922E2923}&controlID=HtmlEditorExtender1_ajaxFileUpload&fileId=0D5BC50A-7072-01F0-9AE0-84BF1D1D27C2&fileName=crash_test_dummy.jpg&chunked=false&firstChunk=true
SCRIPT5022: error raising upload complete event and start new upload
ScriptResource.axd (1468,21)
Since it seems to be looking for the handler to be installed in the default web site, I did that,
tried again
HTTP500: SERVER ERROR - The server encountered an unexpected condition that prevented it from fulfilling the request.
(XHR)POST - http://localhost/AjaxFileUploadHandler.axd?contextKey={DA8BEDC8-B952-4d5d-8CC2-59FE922E2923}&controlID=HtmlEditorExtender1_ajaxFileUpload&fileId=EC3088A9-8133-7BAD-D315-BEB9C32DBAAC&fileName=Crown.jpg&chunked=false&firstChunk=true
SCRIPT5022: error raising upload complete event and start new upload
ScriptResource.axd (1468,21)
I also tried adding  a path to the entry in web.config

Browser(s) used Edge, IE11, Firefox
Dev machine Windows 10 Pro, Visual Studio 2015
A site deployment method

[ ] VS development web-server,
[ ] IIS

Also gave the IIS AppPool\DefaultAppPool user full control on C:\Windows\Temp, as suggested in various places.
TestHTMLEditorExtender.zip

(By the way requiring a change of permissions on the temp folder is not a good idea when the site is running in a shared host / Azure)

Merged with #168
Please download the AppVeyor CI master branch artifacts or apply a workaround described here: https://github.com/DevExpress/AjaxControlToolkit/issues/168#issuecomment-236840248


Feature - Command to access contents of History buffer

So, I can see the history for the current powershell session with the Get-History commandlet, however, there is no way to see the history that PSReadline has read in from its history file.  It would be nice if either Get-History could be updated to include the contents of my PSReadline history file, or add a new command to access the PSReadline history queue (Get-PSReadlineHistory or some such).

I would use this for my Invoke-FuzzyHistory command.  Right now Invoke-FuzzyHistory reads directly from beginning of the the history file.  If I had the ability to read directly from PSReadLine, it would be trivial to start reading history backwards.

New api added in  b2c0474.


Question: Best way to obtain second derivative of interpolations

I've just started using this package and so far it's all been going very well, but I'm curious if there's a recommended way to obtain the second derivative of the Chebyshev interpolations.
Taking the first derivative is (as noted on the homepage here) about twice as fast using chebgradient than using ForwardDiff, but I've been getting the second derivative using ForwardDiff.derivative.(x->stack(chebgradient.(fu,x))[2,:],x) which seems clunky and makes me wonder if there's a better way.
Thanks!

You could use TaylorDiff.jl, which is similar to ForwardDiff.jl but is optimized to be faster for higher derivatives.
To do even better, you'd need something like the FastChebInterp.Jevaluate function (which computes the Jacobian, i.e. the first derivative), but for the 2nd derivative.   (This gets more expensive in higher dimensions, where it is a rank-3 tensor.)

Thanks for the reply! I'll look at TaylorDiff.jl and if I can get my head around the Jevaluate function I might try to implement a 2nd derivative equivalent.


Yubikey 5 NFC is not recognized when using USB NFC reader on Linux

Yubico Authenticator version: 5.0.5
Operating system and version: Windows 10 x64 / Android 9 - Lineage 16 / Linux 5.4.124-1-MANJARO
YubiKey model and version: Yubikey 5 NFC / Fidesmo Card 2.0
Bug description summary: Yubikey is not recognized when using USB NFC reader on Linux

Rationale: I want to use my Yubikey 5 NFC via NFC on all my devices.
I did some differential testing, for results see below.
Steps to reproduce

Use a USB NFC reader such as a SCM SCL3711
Configure a Yubikey 5 NFC as OTP device using the Yubikey manager application.
Configure a Fisdesmo Card 2.0 as OTP device using the Fidesmo mobile app.
Interface the devices using the Yubico Authentificator software via the USB NFC reader (Windows & Linux) or the mobile phones integrated NFC chip.

Expected result
All three operating systems are able to interface both hardware devices (key and card) and are able to read and write OTP entries.
Actual results
Windows:

USB NFC reader is recognized and installed as a scl3711 reader & NFC device smartcard reader. (Driver: SCM Microsystems - 25.07.2013 - <IP_ADDRESS> / SCardSvr)
Yubico Authentificator (exe version) is configured to use a custom CCID filter: SCM Microsystems SCL3711 reader & NFC device 0
:heavy_check_mark: The Yubikey 5  NFC is recognized via NFC in the app and able to function correctly
:heavy_check_mark: The Fidesmo Card 2.0 is recognized via NFC in the app (as Yubikey NEO) and able to function correctly

Android:

Yubico Authentificator configuration is unchanged from stock
:heavy_check_mark: The Yubikey 5  NFC is recognized via NFC in the app and able to function correctly
:heavy_check_mark: The Fidesmo Card 2.0 is recognized via NFC in the app and able to function correctly

Linux:

USB NFC reader is recognized and installed as a SCM Microsystems, Inc. SCL3711-NFC&RW. (Driver: usbfs / opensc / pcscd)
Yubico Authentificator is configured to use a custom CCID filter: SCL3711 Reader and NFC Device 00 00
:x: The Yubikey 5  NFC is recognized via NFC in the app, but OTP entries to NOT display rendering it unusable

However: Connection via direct physical USB works if no CCID filter is used

:heavy_check_mark: The Fidesmo Card 2.0 is recognized via NFC in the app (as Yubikey NEO) and able to function correctly

Other info
The following are the pcsc_scan reports from Linux for various configurations.

:heavy_check_mark: Yubikey 5 via physical USB
0: Yubico YubiKey OTP+FIDO+CCID 00 00
1: SCL3711 Reader and NFC Device 00 00

Sun Jul 11 11:03:59 2021
 Reader 0: Yubico YubiKey OTP+FIDO+CCID 00 00
  Event number: 18
  Card state: Card inserted,
  ATR: 3B FD 13 00 00 81 31 FE 15 80 73 C0 21 C0 57 59 75 62 69 4B 65 79 40

ATR: 3B FD 13 00 00 81 31 FE 15 80 73 C0 21 C0 57 59 75 62 69 4B 65 79 40
+ TS = 3B --> Direct Convention
+ T0 = FD, Y(1): 1111, K: 13 (historical bytes)
  TA(1) = 13 --> Fi=372, Di=4, 93 cycles/ETU
    43010 bits/s at 4 MHz, fMax for Fi = 5 MHz => 53763 bits/s
  TB(1) = 00 --> VPP is not electrically connected
  TC(1) = 00 --> Extra guard time: 0
  TD(1) = 81 --> Y(i+1) = 1000, Protocol T = 1
-----
  TD(2) = 31 --> Y(i+1) = 0011, Protocol T = 1
-----
  TA(3) = FE --> IFSC: 254
  TB(3) = 15 --> Block Waiting Integer: 1 - Character Waiting Integer: 5
+ Historical bytes: 80 73 C0 21 C0 57 59 75 62 69 4B 65 79
  Category indicator byte: 80 (compact TLV data object)
    Tag: 7, len: 3 (card capabilities)
      Selection methods: C0
        - DF selection by full DF name
        - DF selection by partial DF name
      Data coding byte: 21
        - Behaviour of write functions: proprietary
        - Value 'FF' for the first byte of BER-TLV tag fields: invalid
        - Data unit in quartets: 2
      Command chaining, length fields and logical channels: C0
        - Command chaining
        - Extended Lc and Le fields
        - Logical channel number assignment: No logical channel
        - Maximum number of logical channels: 1
    Tag: 5, len: 7 (card issuer's data)
      Card issuer data: 59 75 62 69 4B 65 79
+ TCK = 40 (correct checksum)

Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
3B FD 13 00 00 81 31 FE 15 80 73 C0 21 C0 57 59 75 62 69 4B 65 79 40
	Yubico YubiKey 5 NFC (PKI)
	https://www.yubico.com/product/yubikey-5-nfc
 Reader 1: SCL3711 Reader and NFC Device 00 00
  Event number: 0
  Card state: Card removed,

:x: Yubikey 5 via NFC USB reader
0: Yubico YubiKey OTP+FIDO+CCID 00 00
1: SCL3711 Reader and NFC Device 00 00

Sun Jul 11 11:05:31 2021
 Reader 0: Yubico YubiKey OTP+FIDO+CCID 00 00
  Event number: 0
  Card state: Status unavailable,
 Reader 1: SCL3711 Reader and NFC Device 00 00
  Event number: 11
  Card state: Card inserted,
  ATR: 3B 8D 80 01 80 73 C0 21 C0 57 59 75 62 69 4B 65 79 F9

ATR: 3B 8D 80 01 80 73 C0 21 C0 57 59 75 62 69 4B 65 79 F9
+ TS = 3B --> Direct Convention
+ T0 = 8D, Y(1): 1000, K: 13 (historical bytes)
  TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0
-----
  TD(2) = 01 --> Y(i+1) = 0000, Protocol T = 1
-----
+ Historical bytes: 80 73 C0 21 C0 57 59 75 62 69 4B 65 79
  Category indicator byte: 80 (compact TLV data object)
    Tag: 7, len: 3 (card capabilities)
      Selection methods: C0
        - DF selection by full DF name
        - DF selection by partial DF name
      Data coding byte: 21
        - Behaviour of write functions: proprietary
        - Value 'FF' for the first byte of BER-TLV tag fields: invalid
        - Data unit in quartets: 2
      Command chaining, length fields and logical channels: C0
        - Command chaining
        - Extended Lc and Le fields
        - Logical channel number assignment: No logical channel
        - Maximum number of logical channels: 1
    Tag: 5, len: 7 (card issuer's data)
      Card issuer data: 59 75 62 69 4B 65 79
+ TCK = F9 (correct checksum)

Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
3B 8D 80 01 80 73 C0 21 C0 57 59 75 62 69 4B 65 79 F9
	Yubikey 5 NFC (via NFC) (Other)
	https://www.yubico.com/product/yubikey-5-nfc/#yubikey-5-nfc

:heavy_check_mark: Fidesmo Card 2.0 via NFC USB reader
0: Yubico YubiKey OTP+FIDO+CCID 00 00
1: SCL3711 Reader and NFC Device 00 00

Sun Jul 11 11:08:45 2021
 Reader 0: Yubico YubiKey OTP+FIDO+CCID 00 00
  Event number: 0
  Card state: Status unavailable,
 Reader 1: SCL3711 Reader and NFC Device 00 00
  Event number: 23
  Card state: Card inserted,
  ATR: 3B 80 80 01 01

ATR: 3B 80 80 01 01
+ TS = 3B --> Direct Convention
+ T0 = 80, Y(1): 1000, K: 0 (historical bytes)
  TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0
-----
  TD(2) = 01 --> Y(i+1) = 0000, Protocol T = 1
-----
+ Historical bytes:
+ TCK = 01 (correct checksum)

Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
3B 80 80 01 01
	ISO 14443 Type B without historical bytes
	Electronic Passport
	Spanish passport (2012)
	Canadian Passport
	Venez_Prox

As you can see, the physical USB Yubikey is recognized as Yubico YubiKey 5 NFC (PKI), while the Yubikey via USB NFC reader ist recognized as Yubikey 5 NFC (via NFC) (Other).
I understand if this issue is low-priority for you due to the specific hard- and software configuration. However I would be willing to fix is myself if you could point me to the corresponding places in the codebase. Or maybe the issue lies within my Linux configuration - please advise.
Thank you for any help.
Edit: Clarification - Yubikey 5 NFC is indeed recognized, but OTP entries do not display.

Related: #664

I configured a second Yubikey 5 NFC with only one (1) OTP entry, just like I did with the Fidesmo card 2.0. Turns out, now it works. This leads me to believe that there is some kind of limit on the amount of OTP entries that can be transmitted via the USB NFC reader.

I tested another NFC reader: a "SCL011 Contactless Reader" marketed as a personal ID reader for the citizens of Germany.
This device and its drive don't appear to have this strange "number of OTP entries" limitation, everything works as expected.
In conclusion, this problem does not seem to be related to the Yubikey software at all, but rather to the Linux driver of a specific device. I will report the problem to PCSClite, where I think the problem could be fixed maybe.
This issue is now void, however I'll leave it online if anyone else stumble upon this in the future.


Update README.md Remove https://pipedream.com/@pravin/http-api-for-la…

…test-wuhan-coronavirus-data-2019-ncov-p_G6CLVM/
Page not found

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single com

Thank you.


ObjectSerializer opens SplFileObject with write-only permissions

The ObjectSerializer opens the SplFileObject instance with write-only permissions. This makes doing any further operations on the file very difficult and usually requires re-opening the SplFileObject with a new instance.
If would be beneficial is the new instance of SplFileObject was changed from (ObjectSerializer:265):
$deserialized = new \SplFileObject($filename, "w");

to
$deserialized = new \SplFileObject($filename, "w+");

Making it capable of rewinding and reading from the same SplFileObject instance.

@trickeyone Thanks for bring this our attention, we will review this internally and make the change is we deem necessary. Until then please try reopening the file with a new instance for other operations.
Sorry for the inconvenience.


Use UUID on trackable_id

Would it be possible to choose uuid instead of id ?

Sure, i just need to make the migrations customizable. Will add it in the next release.

@elbaylot released on v1.2.0

Thanks @mateusjunges


Training on a custom dataset

Hello, I was reading the training instructions (and the prepare dataset scripts) and I don't understand how you'd create and use custom datasets with this model.

@korakoe
you can skip lhotse download and lhotse prepare, but you must prepare the lhoste manifests files like https://github.com/lhotse-speech/lhotse/blob/master/lhotse/recipes/libritts.py#L84
more examples: https://github.com/lhotse-speech/lhotse/tree/master/lhotse/recipes

@lifeiteng this was very much helpfull. Thanks for it!!

Is this used for transcribing? You can just use whisper to transcribe most languages. Then convert it into hdf5 file and texts and feed it via dynamic batch samppler


not nil error value, when return nil value of type, which implements error

Please answer these questions before submitting your issue. Thanks!
What did you do?
While working on json-rpc communication, I've stumbled upon interesting situation. Lets assume following types
type Err struct {
        Code int
        Message string
}

func (e *Err) Error() string {
        return fmt.Sprintf("code=%d desc=%s", e.Code, e.Message)
}

type Response struct {
        Result int
        Error  *Err `json:"omitempty"`
}

Now, if I want to deserialize json {"Result":101} into Response and return Error field as error (because Error implements error), I got error which is not nil but is <nil> when printed.
Full code on Go Playground: https://play.golang.org/p/f9afzE69t7
What did you expect to see?

Error field to be nil
When return Error field as error I expect error to be nil also

What did you see instead?

Error field is nil
When return Error field as error, error is not nil but is <nil> when printed

System details
go version go1.8 linux/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/user/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build491112895=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
GOROOT/bin/go version: go version go1.8 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.8 X:framepointer
uname -sr: Linux 4.4.0-31-generic
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Ubuntu EGLIBC 2.19-0ubuntu6.9) stable release version 2.19, by Roland McGrath et al.
gdb --version: GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1

For questions about Go, see https://golang.org/wiki/Questions
In this case you should look at: https://golang.org/doc/faq#nil_error


Add matplotlib unit registry and rcParams context manager

Summary

Fixes #494
Added context manager to avoid pandas-profiling permanently change the global context of matplotlib. The context manager modifies and rolls back  matplotlib.rcParams and matplotlib.inits.Registry. Every plotting function is decorated with the context manager.
Refactored mplstyle file into a python dictionary

It would be grateful if someone spend time to review this patch and let me know if there's any possible issues with this patch or other suggestions.

Noticed using context manager is not thread safe. Looking for other workaround.

I think current patch is okay. Found that thread pool is used to run describe_1d, calculating statistics from pandas series. The visualization functions are currently run in a single thread. If you still think it can be a problem in the future, please let me know.

Thanks for this workaround. Not experiencing side effects on the matplotlib rcparams will be much appreciated by users.
I've got two points we should consider before merging:

In this implementation the params are set and restored at every plotting call. I'd like to know how much overhead this adds. If it's not neglectible, we might add the context manager elsewhere. For instance, when the report is rendered.
Seaborn is currently not a dependency in any of the releases. If we can, i'd like to avoid making it mandatory. The fact that it is present in the develop branch is somewhat misleading, as it's not expected to be in the next release.

Hi, thanks for your review. I've done a naive profiling using examples/bank_marketing_data/banking_data.py. Based on this commit, total overhead of manage_matplotlib_context was 0.062 second, while executing to_file method of ProfileReport took total 14.2507 second. Average overhead of calling this function was 0.00081 second. I think it's acceptable overhead. If you think this isn't acceptable or this experiment is insufficient, please let me know.


Accented letters

Apologies if this has been suggested or implemented but i couldnt see/find it. Would it be possible to add accents like à é etc to the app? It would make it easier to type in multipule languages without needing to load different languages.

This is not possible.
T9 keyboards always type digits, then convert the digit sequence to the words in the selected language. Hence, to type a word in a different language, you must have it loaded.

What about in abc mode?  I've had bar phones that did it where they would put the accented characters after the number.  (Preferably as an option, so if someone doesn't use the accented characters at all they wouldn't need to scroll through them after pressing one too many times)

Sorry, this is out of the question. If you need to type in another language, just switch to that language.

I understand that you can add the language without loading the dictionary (and switch to this language when needed), I don't know if it works for your case.

Absolutely. If you just need to type one character in a different language, by only enabling the language and using its ABC mode.


Move to the rust-lang org

As https://github.com/rust-lang/rust/pull/58623 has landed we should probably move this to the rust-lang org. If you add me or @pietroalbini as admins to this repo, we can do this move (I think you need to have admin on rust-lang to move a crate there)

You can't add people as administrators to personal projects: you have to transfer the repo to an org owner's account, and then the org owner can transfer the repo to the org.

Oh, damn. Uh, in that case please transfer to one of us, I guess?

Done, thanks!

The libs team (and various bot teams) have access, lmk if perms need to be tweaked


Issue with the comic list when going back from a comic

When going back from a comic to the comic list, the app doesn't show the list near the comic I was reading (for example 1518) but close to the first one (it's around 100).
So I have to go back to the top and search for my comic.
But once I've done that and if I go back again, it shows the right place in the list.
But if I close the app(not just quitting it), and do this again, the issue is here again.
Not sure if I'm clear enough ^^

I'll look into that!

And it seems the more I go down in the seen comics(1504), the more it goes up when I go back to the comic list (114 now).

After some test, it seems to be keeping the position but in the wrong order. I'm at the 120 comics from the top and it put me at the 120 comics from the beginning when I go back to the list view

Thanks for your detailed description, should be fixed in the next update!

No problem, happy to help


swagger.json 404 Not found.

I have done my best to follow the instructions set forth in the wiki, but I get no startup errors and I get a 404 when attempting to access /swagger.json
Here is my spring config:
<!--  Which URL have you tried?

I use Apache CXF JaxRS.  I have tried http://localhost:9095/swagger.json   and I have tried http://localhost:9095/api/swagger.json.
I have tried updating my config to:
	<bean id="swaggerResource" class="io.swagger.jaxrs.listing.ApiListingResource"/>

    <bean id="beanConfig" class="io.swagger.jaxrs.config.BeanConfig">
        <property name="title" value="Disney Key Management Service"/>
        <property name="version" value="0.0.1" />
        <property name="schemes" value="http" />
        <property name="host" value="${env.kmsService.baseUrl:http://localhost:9095/api}" />
        <property name="basePath" value="/api"/>
        <property name="resourcePackage" value="com.foo.tss.kms"/>
        <property name="scan" value="true"/>
    </bean>
	<!-- End Swager -->

	<bean id="amazonKMSKeystore" class="com.foo.tss.kms.logic.AmazonKMSKeystore"/>

	<bean id="kmsServiceBean" class="com.disney.tss.kms.api.KeysService">
		<constructor-arg index="0" value="${env.authzClientId.attributeName:AUTHZ_CLIENT_ID}"/>
		<constructor-arg index="1" ref="amazonKMSKeystore"/>
	</bean>
	<bean id="statusServiceBean" class="com.foo.tss.kms.api.StatusService"/>

	<jaxrs:server id="kmsService" address="/">
		<jaxrs:providers>
			<bean class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider"/>
			<bean class="com.foo.tss.kms.exceptions.JsonMappingExceptionMapper"/>
			<bean class="io.swagger.jaxrs.listing.SwaggerSerializers"/>
		</jaxrs:providers>
		<jaxrs:serviceBeans>
			<ref bean="swaggerResource"/>
			<ref bean="statusServiceBean"/>
			<ref bean="kmsServiceBean"/>
		</jaxrs:serviceBeans>
	</jaxrs:server>

The /api/swagger.json gives a no such method found 500 error and the /swagger.json gives 404 not found error.

Well, the wiki doesn't really cover CXF so there isn't much to follow. I don't know CXF well enough to tell whether that configuration should work or not.
As a first step, I'd ask you to take a look at the CXF sample and see if you spot any major differences.

Already looked at that.  The CXF sample doesn't really follow good idioms in that it does not use the schema appropriate to CXF but uses raw bean definitions instead.
So for example in the sample we have:
<bean class="org.apache.cxf.jaxrs.JAXRSServerFactoryBean" init-method="create">
    <property name="address" value="/" />
    <property name="serviceBeans">
      <list>
        <ref bean="userResource" />
        <ref bean="petResource" />
        <ref bean="petStoreResource" />

        <ref bean="swaggerResource" />
      </list>
    </property>
    <property name="providers">
      <list>
        <ref bean="jsonProvider" />
        <ref bean="swaggerWriter" />
        <ref bean="exceptionMapper" />

        <!-- required for writing swagger classes -->
        <!-- <ref bean="resourceWriter" />
        <ref bean="apiWriter" /> -->
      </list>
    </property>
  </bean>

My spring config uses the jaxrs:server tag provided by the: http://cxf.apache.org/schemas/jaxrs.xsd schema.  That should not fundamentally change things however.  And as an additional data point all of this sort of worked when I was using the:  com.wordnik.swagger.jaxrs.listing.ApiListingResourceJSON in the jaxrs:serviceBeans section and: com.wordnik.swagger.jaxrs.listing.ResourceListingProvider, com.wordnik.swagger.jaxrs.listing.ApiDeclarationProvider in the jaxrs:providers section.
Migrating to the stuff in this project doesn't seem to enable things to work correctly.

I figured it out the magic path is http://localhost:9095/api/swagger
That works.  By the way for some reason Swagger thinks that the HttpServeletRequest is something that it should be placing in the API documentation.  It shouldn't.

swagger-core just scans your code. If have an operation that accepts HttpServletRequest as an input, you'd need to explicitly tell it to ignore it using @ApiParam(hidden=true).

hidden does not seem to be well documented but sure enough, it works, thanks.

It's documented in the javadocs, but sure. Please reopen if needed.


[BUG] : MENU not responsive

Describe the bug
MENU Button is not working Properly  like its suppose to
Screenshots

@Debshibraj123 Here you go 🚀

@PritamSarbajna I guess the problem was not fixed, I am working on a fix can you please assign me to it?

yeah sure @Domenez25

@PritamSarbajna @athar-ansari,  I have finished the work that was assigned to me and you can check on pull #119


stm32/rcc: move rcc logic from ipcc

This moves the bulk of the rcc configuration out of the ipcc module, and also frontloads clock computation.

This time, the HIL failure is not my fault.


Customisable MuiInputLabel required text

An asterisk (*) is hard-coded to required fields. I think we should allow users to customise the asterisk or remove it if they want to.
https://github.com/callemall/material-ui/blob/fb3a42f421d9a00cbc31e69e06e5e30c7b1998fc/src/Form/FormLabel.js#L125-L127

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Be able to pass in a requiredText: Node to be displayed instead of the hard-coded asterisk, or false to completely remove it.
Current Behavior

There is no way to override the asterisk at the moment.
Steps to Reproduce (for bugs)

Not a bug
Context

For some forms that all fields are required, I'd like to display a label somewhere (All fields are required) and remove all the asterisks in each TextField.
The form looks cleaner without those.
Your Environment

Tech
Version

Material-UI
1.0.0-beta.9

React
15.4.1

browser
Chrome

etc

You can already remove the asterisk by setting the required property to false on the input label. Then if you want to customize it, you can directly use the children property.

@oliviertassinari what if I want to set required to true (i.e. to utilise browser form validation)?
Also, my validation logic is also based on that required prop.

The TextField is made of different components. You can have the required property set to true for the input but to false for the label.

@oliviertassinari How can I customize requiredText (*)  and its color?

@sudhanshudeshmukh By targeting the style of the FormHelperText component.

I mean how can we change requiredtext for all component when we set required:true for those in material ui

@sudhanshudeshmukh  you can customize it within TextField  just by using & to reference selectors
textField : {
   "& label": {         // for label
     color: "#fccf5d"
   },
"& label span": {    // for asterisk
     color: "green"
   }}

Here is the working codesandbox: Textfield Asterisk CSS Override

@oliviertassinari don't you think we should add some props to override this css within textField?

@sakhisheikh What do you have in mind?

It could be nice to be able to change the asterisk to adhere to the newest UX recommendation: https://www.nngroup.com/articles/required-fields/

@waker-lna Could you expand on this? What do you mean by change?


[API] endpoints to manage user/org/repo avatars

GET, SET, DELETE endpoints are needed
to simplify I would propose:
user

GET /users/{username}/avatar -> return raw image
PUT /users/{username}/avatar -> return status 204 (add img within request body)
DELETE /users/{username}/avatar -> return status 204 (rm and use default avatar)

org

GET /orgs/{org}/avatar -> return raw image
PUT /orgs/{org}/avatar -> return status 204 (add img within request body)
DELETE /orgs/{org}/avatar -> return status 204 (rm and use default avatar)

repo

GET /repos/{owner}/{repo}/avatar -> return raw image
PUT /repos/{owner}/{repo}/avatar -> return status 204 (add img within request body)
DELETE /repos/{owner}/{repo}/avatar -> return status 204 (rm and use default avatar)

ref: https://codeberg.org/gitnex/GitNex/issues/552

I would say that this issue depends upon #17123 to be implemented the easiest.

Mostly implemented by #25369

Get, and I think we only have the ability to set own user avatar, not for another user


Add limit of before php 5.4

Add limit of before php 5.4 - so that the package does not install on systems that don't require it

see https://github.com/symfony/polyfill-php56/pull/1


Compilation fails on recent versions of Odin

With Odin compiled on the most recent git commit in master, compiling any of the examples will give me these two errors:
D:/Code/Odin/shared/odin-binding-generator/bindgen/c-parser-evaluate.odin(172:9) Assignment count mismatch '1' = '2'
D:/Code/Odin/shared/odin-binding-generator/bindgen/c-parser-evaluate.odin(176:9) Assignment count mismatch '1' = '2'

Compiling and running with the tagged v0.12.0 of Odin works without any issues.
Platform Win10.

Apparently API for strconv.parse_f64 changed. Do you know in what extent?
I won't update until new officially tagged version.

In https://github.com/odin-lang/Odin/commit/190932935c3f6e4398934ec766214b61adc1bbca#diff-f161bde54e8dd2ecc624cf8b2743f600 and https://github.com/odin-lang/Odin/commit/704ee9f8510cdaa75fe207316957efb70e8269de#diff-f161bde54e8dd2ecc624cf8b2743f600 the signatures strconv.parse_* changed to return a pair of values. It is now -> (value: f64, ok: bool). Updating odin-binding-generator to support that will be easy, but we will loose compatibility with older versions of Odin. As it is still in version "0", it is OK for us.


add complex support in solve

I added support for complex dtype in solve.
Also, I moved the get_handle calls from _solve to solve because it took to much time for the batched case.
I still need to push some tests.

Thank you for the contribution.  The test code for cupy.solve is in cupy/tests/cupy_tests/linalg_tests/test_solve.py.
While the test does not exclude complex dtypes, it only generates real inputs!


Add more fields to LiteUser

Currently API enpoints /v0/me, /v0/user/[username], /v0/user/by-id/[id], and /v0/users only return the following fields:
id, createdTime, name, username, url, avatarUrl?, bio?, website?, twitterHandle?, discordHandle?,
balance, totalDeposits, profitCached { daily, weekly, monthly, allTime }

This Pull requests adds 8 more fields to the returned LiteUser object:
 isBot, isCore, isChecked, isBannedFromPosting?, userDeleted?,
 followerCountCached, currentBettingStreak?, lastBetTime?

Where isBot, isCore, isChecked are checked against the BOT_USERNAMES, CORE_USERNAMES, CHECK_USERNAMES constants from common/envs/constants.ts and the rest of the fields are taken from the User object.
I'm open for discussion if isCore and isChecked is the best naming choice. Perhaps they're better be renamed to isAdmin and/or isTrustworthy in the LiteUser object, to avoid confusion.

Nice! This is hopefully helpful to the api users, can you change isCore to isAdmin and isChecked to isTrustworthy like you mention? I think that will be a better UX for the median api user.

Also, has anyone asked for more fields on liteuser or is this just something you think would be useful?

Also, has anyone asked for more fields on liteuser or is this just something you think would be useful?

Primarily I've asked for this, and I also think it would be useful for others. 🙂
For example, some users create quite a number of markets regarding other user's streaks, like: Will 5 or more people, with streaks of 150 or more, comment in this market?, and it's currently difficult if not impossible to verify a persons streak (the person can just photoshop their screenshot, and there's some streakForgiveness logic going on under the hood which would be difficult to reproduce on a local machine). A similar thing is happening with the followers count.
This PR should help in both of those use-cases.
Also lastBetTime should help those, who implement API scripts that rely on other users betting activity.

Okay this seems reasonable, but I also don't understand why we return only a lite user at the user/by-id/[id] endpoint. I'd figure we use lite-user when you could potentially get a lot of users, and a full user when you request one via id.

I just changed the api so that /user/by-id/[id] returns the full user object

I also don't understand why we return only a lite user at the user/by-id/[id] endpoint. I'd figure we use lite-user when you could potentially get a lot of users, and a full user when you request one via id.

I've checked, and /api/v0/me actually calls getcurrentuser which returns full User.

I just changed the api so that /user/by-id/[id] returns the full user object

Are you sure that it's ok to make referredByUserId public information?

yup, will only help people audit the referrals totals if anything.


Update README.md: Tuple to Array

fixes #1805
Update zod enum option property documentation to better match reality. And fix typo in example code.

I'm going to close this for now. You are more than welcome to see if someone else will merge it for you. But I just don't think this is needed.


feat(Monad): add more funs

Can you add test cases for these functions? In principle, adding new functions requires adding test cases.

test added @EMQ-YangM


python311Packages.bentoml: 1.1.7 -> 1.1.9

Description of changes
https://github.com/bentoml/BentoML/releases
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@natsukium good catch! Sorry for the typo.


0.3.0 is not available on npm

0.3.0 is not available on npm. It looks like the latest version available on npm is 0.2.4

Oops, I forgot to publish - it's there now!


Add the reliability module to the pole vulnerability simulation

The reliability module needs to be added to the pole vulnerability simulation.
In addition, the pole status is currently coming back to OK after only 1 hour and that appears to be the incorrect value.

@aivanova5, please confirm whether this is ok now.


Fixed id links

Added the id links from the Repo's front page to the <h3> header tags in the library. Very strange why only the Library page has this problem. If it breaks something then sorry.

at least it's not boring anymore


Extend image proxy to work with cover art

Fixes

Closes #76
Description
This PR adds endpoints to generate thumbnails for album art associated with audio sets
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@obulat the image proxy we use for scaling has caching functionality built-in, although we have not configured it in the dev environment. The documentation covers most caching setups so it should not pose significant difficulty.


sidebar-mini state should be persistent

Currently when the sidebar is minimized (sidebar-mini) and the page is refreshed, the sidebar's state will not be restored, which means the sidebar is expanded again.
For persistance basically we just need an LSO or even a cookie to store the current state and restore it after a page was reload.
What do you think?

You need to do that on the server side. Refer to #315.

As @YasserHassan said, this is a back-end issue. Doing that in the front-end would cause unwanted transitions to occur during reload. Thanks!


Lettuce trusts the first sentinel's response to who the master is.

I'm not sure if this is a bug in Lettuce or in Redis/Sentinel or just a weird quirk.
Our setup is master with two slaves, and a sentinel on each machine, (i.e. M1+S1,R2+S2,R3+S3), all Redis 4.0.2 connected via Lettuce 4.4.3 snapshot.
We encountered a situation whereby Lettuce was connecting to a slave (R2) even when ReadFrom was set to MASTER, then issuing a setex and failing because it was connected to a readonly slave.
From what I could tell, M1,R2,R3,S1,S3 all agreed on the master being M1, but because the URI happened to be redis-sentinel://S2,S1,S3/0##redis-cluster and Lettuce only asks the first in the list, it was asking S2 sentinel who the master was, and getting the incorrect reply of R2.
(In case it's relevant, running SENTINEL master redis-cluster was reporting flags of "s_down,master" on that node - possibly a previous failover didn't fully cleanup.)
Moving the master's sentinel IP to be first in the URI solved the problem, and repairing the config on S2 allowed either order to work.
Should Lettuce keep checking sentinels until it has a quorum agreement on which node is the master?
Or is this entirely the job of Redis/Sentinel, and there's a bug there which allowed the incorrect sentinel config to persist?

Thanks for reporting the issue. There are a couple of things in there, let me untangle:

Lettuce attempts to connect to all sentinels in the order they get returned by RedisURI.getSentinels(). The mentioned method takes the first URI but really, sentinels are within the URI. The method is a bit unfortunate because it suggests the possibility of having multiple Sentinel URIs passed through Iterable.
The actual Sentinel connect happens in RedisClient.connectSentinel(…).
Lettuce doesn't check in Sentinel Master/Slave mode for the server's role. It obtains topology details from Sentinel and assumes details are in sync. Connecting in Master/Slave mode without Sentinel lets Lettuce figure out the currently connected server role and the topology from INFO command. Lettuce trusts Sentinel – if it wouldn't then we would have much bigger issues.

Changing how Lettuce connects to a Redis master isn't something we should change. Adding a quorum check increases the time until you're able to use the connection. Asking more than one machine causes actually more issues than contributing to be a cure:

What if there is never a quorum
What if a node is down and cannot report its state

I see it entirely as part of Sentinel's responsibility to report the correct topology. We read masters and slaves from Sentinel, as your client is running probably on a different machine, it might have a different network view (connectivity). If Sentinel reports a master is down, but you're still able to connect, then something's not right about that state. We could deny establishing a connection, but that would effectively prevent you from using Redis whereas we don't know how your application is going to interact with Redis.
Does this make sense?

Thanks for the clarification, that does all make sense.
On the connection startup front, I've found another oddity where I can't see what's going on.
In short, the problem is Lettuce is connecting to master but also the slaves, and in particular to R3 which is a slave with priority 0 - it's purpose is a witness server, and the application shouldn't connect to it.
<IP_ADDRESS> = M1/S1 , <IP_ADDRESS> = R2 , <IP_ADDRESS> = R3
Filtered logs:

20:59:23 DEBUG RedisClient:784 - Connecting to Redis Sentinel, address: /<IP_ADDRESS>:16379
20:59:23 DEBUG RedisClient:287 - Connecting to Redis at /<IP_ADDRESS>:16379
20:59:23 DEBUG RedisClient:312 - Connecting to Redis at /<IP_ADDRESS>:16379: Success
20:59:24 DEBUG RedisClient:287 - Connecting to Redis at /<IP_ADDRESS>:6379
20:59:24 DEBUG RedisClient:312 - Connecting to Redis at /<IP_ADDRESS>:6379: Success
20:59:24 DEBUG RedisClient:287 - Connecting to Redis at /<IP_ADDRESS>:6379
20:59:24 DEBUG RedisClient:287 - Connecting to Redis at /<IP_ADDRESS>:6379
20:59:24 DEBUG RedisClient:312 - Connecting to Redis at /<IP_ADDRESS>:6379: Success
20:59:24 DEBUG RedisClient:312 - Connecting to Redis at /<IP_ADDRESS>:6379: Success
20:59:24 DEBUG RedisClient:287 - Connecting to Redis at /<IP_ADDRESS>:16379
20:59:24 DEBUG RedisClient:312 - Connecting to Redis at /<IP_ADDRESS>:16379: Success
20:59:24 DEBUG RedisClient:287 - Connecting to Redis at /<IP_ADDRESS>:16379
20:59:25 DEBUG RedisClient:312 - Connecting to Redis at /<IP_ADDRESS>:16379: Success
20:59:25 DEBUG RedisClient:287 - Connecting to Redis at /<IP_ADDRESS>:6379
20:59:25 DEBUG RedisClient:312 - Connecting to Redis at /<IP_ADDRESS>:6379: Success

Behind the firewall, the R3 connection attempt causes a timeout...
java.util.concurrent.CompletionException: com.lambdaworks.io.netty.channel.ConnectTimeoutException: connection timed out: /<IP_ADDRESS>:6379
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
	at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:593)
	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
	at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
	at com.lambdaworks.redis.AbstractRedisClient.lambda$initializeChannelAsync$1(AbstractRedisClient.java:305)
	at com.lambdaworks.io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:507)
	at com.lambdaworks.io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:500)
	at com.lambdaworks.io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:479)
	at com.lambdaworks.io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:420)
	at com.lambdaworks.io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:122)
	at com.lambdaworks.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:269)
	at com.lambdaworks.io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)
	at com.lambdaworks.io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120)
	at com.lambdaworks.io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
	at com.lambdaworks.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
	at com.lambdaworks.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463)
	at com.lambdaworks.io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at com.lambdaworks.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.lambdaworks.io.netty.channel.ConnectTimeoutException: connection timed out: /<IP_ADDRESS>:6379
	at com.lambdaworks.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:267)
	... 8 more

I'm not following where/why the slaves are being called, but I'm hoping there's a way to stop the connection to R3, since the timeout delay adds to the application startup time.
Thanks.

That's a different issue. In short: Lettuce connects to all known nodes to verify connectivity and to get a response time (PING) for nearest node reads.
Closing this ticket as there is nothing left to do here.


Breaking typo in CurlClient

ErrorException in CurlClient.php line 43: Use of undefined constant body - assumed 'body

Thanks for reporting @Robarelli. This has been fixed in v1.0.3.


Width of the popover is restricted to the width of the parent.(parent grid).

Hi
I am using Bootstrap Version:  v3.3.4, I am calling bootstrap popover via angular custom popover.
When the target is inside the bootstrap grid structure the width of the popover is restricted to the width of the grid . Kindly help me to solve this issue. Please find the screen sort for my html structure

Please upgrade to Bootstrap v3.3.6
Please post an example JS Bin or JS Fiddle that doesn't use Angular (we cannot provide help with third-party lobs such as Angular)
Have you tried setting the data-container="body" option?

Thanks for your response it is working after replacing data-container='body'


Register Application with Azure AD failed for aad application named with "animial-rescue" already existed

Met with this error in this step. The reason is AAD app named with "animal-rescue" is already existed. We use another name for the AAD app and unblock this issue eventually.

Thanks, @qingc. Would these updated instructions prevent others from running into the same issue?

Thanks, @qingc. Would these updated instructions prevent others from running into the same issue?

Yes, that's much better. Thank you! @maly7


⚠ Bofrost.de has degraded performance

In dd94b17, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1288 ms

Resolved: Bofrost.de performance has improved in 0b8c3fd after 8 minutes.


Error Debug Log

[01-10-2015 23:22] System.NullReferenceException: Object reference not set to an instance of an object.
at POEApi.Model.Map..ctor(Item item)
at POEApi.Model.ItemFactory.Get(Item item)
[01-10-2015 23:22] ItemFactory unable to instanciate type : Tropical Island Map
[01-10-2015 23:22] Error downloading stash for Standard, exception details: System.Exception: ItemFactory unable to instanciate type : Tropical Island Map
at POEApi.Model.ItemFactory.Get(Item item)
at System.Linq.Enumerable.WhereSelectListIterator2.MoveNext()    at System.Collections.Generic.List1..ctor(IEnumerable1 collection)    at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)
at POEApi.Model.Stash..ctor(Stash proxy)
at POEApi.Model.POEModel.GetStash(Int32 index, String league, Boolean forceRefresh)
at POEApi.Model.POEModel.getAllTabs(String league, Stash stash)
at POEApi.Model.POEModel.GetStash(String league, String accountName)
[01-10-2015 23:22] System.Exception: Downloading stash for Standard, details logged to DebugInfo.log, please open a ticket at
https://github.com/Stickymaddness/Procurement/issues
at POEApi.Model.POEModel.GetStash(String league, String accountName)
at Procurement.ViewModel.LoginWindowViewModel.LoadStashItems(Character character)
at Procurement.ViewModel.LoginWindowViewModel.d__6.MoveNext()
at System.Collections.Generic.List1..ctor(IEnumerable1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass2.b__1()
at System.Threading.Tasks.Task.Execute()

The new version of Procurement is out, which fixes this issue: https://github.com/Stickymaddness/Procurement/releases/tag/1.9.6
Unfortunately until GGG decide to support the dev community, these type of issues will continue to happen as it is out of our hands. http://i.imgur.com/yrPtajM.jpg


Add gRPC proxy

Motivation
gRPC+Protobuf has a number of advantages compared to websockets + JSON
Protobuf:

Static data structures: data validation, better tooling, etc...
More compact (binary format) : esp. the payload can be sent raw instead of Base64-encoded.
More efficient encoding: no need to encode/decode to Base64
(NB: Protobuf could also be used over websocket)

gRPC:

No preliminary handshake like in Websocket. Also websocket needs to open TCP connexions twice (once for the handshake, once for the stream).
Built on HTTP/2 so streams are multiplexed: lower overhead if the client opens a large number of concurrent streams.
Pull-based flow-control model: although it's possible to handle backpressure in websockets by using the TCP congestion mechanism, few implementations actually do it.

This PR is WIP for discussion and early feedback. Topics that still need to be covered:

[ ] Clean up
[x] Add license headers
[x] Add authentication
[ ] Test authentication
[ ] Stats / monitoring
[ ] Unit/Integration Tests
[ ] Reader endpoint
[ ] Admin I/F
[ ] Separate/standalone mode
[x] Use Protobuf for metadata ? gRPC's Metadata can be string or binary. It would probably be better to encode the stream parameters in Protobuf and pass it in a binary Metadata field
[ ] Make the proxy reactive with e2e back-pressure? eg: In produce mode, backpressure is currently done by dropping the message and answering with a ProducerQueueIsFullError exception. It would probably be better to use a dedicated thread pool and a producer queue configured as blockIfQueueFull(true) then propagate the pressure to the gRPC driver. On the server-side, gRPC would not accept new messages if the producer queue is full. See reactive-grpc for a library to bind gRPC and reactive-streams which would make all this easier.

Fix #271

About authentication, I see that for websockets it's done 2 ways:

with a servlet filter when embedded in the broker
in the websocket handler (checkAuth())

It even looks like authentication is done twice when embedded in the broker: once with the filter, once in the handler !
Shouldn't it be done only once in the filter ?
Then about authorization, the filter already gets the role and puts it in AuthenticationFilter-role so the handlers could get it from there.
WDYT ?

run integration tests

CI failure is due to docker hub issue : https://github.com/docker/hub-feedback/issues/1693

@cbornet sorry for getting back to this late. in general I like this grpc proxy. however since it is a new feature, would you mind writing up a PIP for this feature? when this feature is approved and merged, we can use that PIP for writing documentation for this feature.
You can find example PIPs here: - https://github.com/apache/pulsar/wiki
You can write is in your own gist. I will move your gist to the pulsar wiki when it is available.

@cbornet is there work pending for this ?

Guys, please keep it moving forward.

Hi @cbornet, I just wonder what if one gRPC Server Crashes. Will the messages already sent to clients but not acked be delivered again?

Yes, they'll be redelivered

@cbornet Can this PR be closed?

Yes. I still think a gRPC proxy is of interest. But now we could do it as a protocol handler or a proxy extension.


Add C/C++ Implementation Of Exponential Search

Add the needful here and submit a PR,
https://github.com/MadhavBahlMD/OOPS/tree/master/Search/Exponential_Search
Also, do add the algorithm and explanation in Corresponding README + snippet of code
Format for README
Exponential Seaerch
Some Details
Algorithm
Algorithm
Explanation
Explanation
C/C++ Code
Code Here

PR format:

[x] About
[x] Algorithm
[x] Explanation
[x] Code Snippets
[ ] Screenshots as example


Fix #328 checkout to wrong folder using submodules

refs #328: It works for me now.

To be honest: no :(  It's seems for me, that Intellij doesn't support git submodules (see https://youtrack.jetbrains.com/issue/IDEA-64024). So Jetbrains's multi roots and git's submodules are similar but different. I recommend that I rewrite my commit to use it as a special but prefered case. Do you agree?


[Snyk] Security upgrade com.amazonaws:aws-java-sdk-core from 1.12.239 to 1.12.708

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

jobs/pacman-tenable-enricher/pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity
Reachability

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1009829
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1047324
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1052449
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1052450
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1054588
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056414
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056416
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056417
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056418
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056419
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056420
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056421
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056424
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056425
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056426
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1056427
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-1061931
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-174736
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

525/1000  Why? Has a fix available, CVSS 7.5
Denial of Service (DoS) SNYK-JAVA-COMFASTERXMLJACKSONCORE-2421244
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

520/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Denial of Service (DoS) SNYK-JAVA-COMFASTERXMLJACKSONCORE-3038424
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

670/1000  Why? Proof of Concept exploit, Is reachable, Has a fix available, CVSS 5.9
Denial of Service (DoS) SNYK-JAVA-COMFASTERXMLJACKSONCORE-3038426
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
Reachable

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-31507
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-31573
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-32043
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-32044
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-32111
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

520/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-450207
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

705/1000  Why? Mature exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-450917
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Mature
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-455617
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-467014
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

675/1000  Why? Mature exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-467015
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Mature
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-467016
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-469674
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-469676
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-471943
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-472980
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-540500
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-548451
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-559094
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-559106
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-560762
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-560766
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-561362
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-561373
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

630/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-561585
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-561586
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-561587
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-564887
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-564888
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-570625
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-572300
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-572314
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-572316
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

555/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-6056407
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

780/1000  Why? Proof of Concept exploit, Is reachable, Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-608664
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
Proof of Concept
Reachable

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72445
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72446
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72447
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72448
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72449
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72450
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72451
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72882
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72883
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

563/1000  Why? Has a fix available, CVSS 8.1
Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-72884
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

485/1000  Why? Is reachable, Has a fix available, CVSS 3.7
Information Exposure SNYK-JAVA-COMMONSCODEC-561518
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
Reachable

415/1000  Why? Has a fix available, CVSS 5.3
Improper Input Validation SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-1048058
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
No Path Found

565/1000  Why? Is reachable, Has a fix available, CVSS 5.3
Directory Traversal SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-31517
com.amazonaws:aws-java-sdk-core:  1.12.239 -> 1.12.708
No
No Known Exploit
Reachable

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Deserialization of Untrusted Data
🦉 Denial of Service (DoS)
🦉 Improper Input Validation
🦉 More lessons are available in Snyk Learn

Checkmarx One – Scan Summary & Details – 7cef7ff8-38bd-4fd1-a238-839d9f88b318
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-34034
Maven-org.springframework.security:spring-security-web-5.0.7.RELEASE
Vulnerable Package

CVE-2023-34034
Maven-org.springframework.security:spring-security-config-5.0.7.RELEASE
Vulnerable Package

CVE-2023-52428
Maven-com.nimbusds:nimbus-jose-jwt-9.8.1
Vulnerable Package

CVE-2023-6481
Maven-ch.qos.logback:logback-core-1.3.5
Vulnerable Package

CVE-2023-6481
Maven-ch.qos.logback:logback-core-1.2.9
Vulnerable Package

CVE-2023-6481
Maven-ch.qos.logback:logback-core-1.2.3
Vulnerable Package

CVE-2023-6481
Maven-ch.qos.logback:logback-core-1.2.11
Vulnerable Package

CVE-2023-6481
Maven-ch.qos.logback:logback-core-1.1.11
Vulnerable Package

CVE-2024-22243
Maven-org.springframework:spring-web-5.0.8.RELEASE
Vulnerable Package

CVE-2024-22257
Maven-org.springframework.security:spring-security-core-5.0.7.RELEASE
Vulnerable Package

CVE-2024-22259
Maven-org.springframework:spring-web-5.0.8.RELEASE
Vulnerable Package

CVE-2024-22262
Maven-org.springframework:spring-web-5.0.8.RELEASE
Vulnerable Package

CVE-2024-23672
Maven-org.apache.tomcat.embed:tomcat-embed-core-8.5.32
Vulnerable Package

CVE-2024-23672
Maven-org.apache.tomcat.embed:tomcat-embed-websocket-8.5.32
Vulnerable Package

CVE-2024-24549
Maven-org.apache.tomcat.embed:tomcat-embed-core-8.5.32
Vulnerable Package

CVE-2024-29180
Npm-webpack-dev-middleware-5.3.0
Vulnerable Package

Missing User Instruction
/dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 2
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Passwords And Secrets - Generic Password
/mysql-check.yaml: 10
Query to find passwords and secrets in infrastructure code.

Add Instead of Copy
/dockerfile: 10
Using ADD to load external installation scripts could lead to an evil web server leveraging this and loading a malicious script.

Add Instead of Copy
/Dockerfile: 10
Using ADD to load external installation scripts could lead to an evil web server leveraging this and loading a malicious script.

CVE-2023-33202
Maven-org.bouncycastle:bcprov-jdk15on-1.67
Vulnerable Package

CVE-2023-33202
Maven-org.bouncycastle:bcprov-jdk15on-1.56
Vulnerable Package

CVE-2024-29025
Maven-io.netty:netty-codec-http-4.1.79.Final
Vulnerable Package

CVE-2024-29025
Maven-io.netty:netty-codec-http-4.1.77.Final
Vulnerable Package

CVE-2024-29025
Maven-io.netty:netty-codec-http-4.1.27.Final
Vulnerable Package

CVE-2024-29025
Maven-io.netty:netty-codec-http-4.1.32.Final
Vulnerable Package

Image Version Not Explicit
/dockerfile: 1
Always tag the version of an image explicitly

Image Version Not Explicit
/Dockerfile: 2
Always tag the version of an image explicitly

Pip install Keeping Cached Packages
/dockerfile: 4
When installing packages with pip, the '--no-cache-dir' flag should be set to make Docker images smaller

Pip install Keeping Cached Packages
/Dockerfile: 4
When installing packages with pip, the '--no-cache-dir' flag should be set to make Docker images smaller

Pip install Keeping Cached Packages
/dockerfile: 3
When installing packages with pip, the '--no-cache-dir' flag should be set to make Docker images smaller

Pip install Keeping Cached Packages
/dockerfile: 10
When installing packages with pip, the '--no-cache-dir' flag should be set to make Docker images smaller

RUN Instruction Using 'cd' Instead of WORKDIR
/dockerfile: 4
When using RUN command 'cd' should only be used for full path. For relative path make use of WORKDIR command instead.

Unpinned Actions Full Length Commit SHA
/codeQl.yaml: 50
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/codeQl.yaml: 65
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/codeQl.yaml: 84
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Package Version in Apk Add
/dockerfile: 10
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Apk Add
/dockerfile: 1
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Apk Add
/Dockerfile: 4
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Apk Add
/dockerfile: 3
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Pip Install
/dockerfile: 10
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Pip Install
/dockerfile: 4
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Pip Install
/dockerfile: 3
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Pip Install
/Dockerfile: 4
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Healthcheck Instruction Missing
/dockerfile: 1
Ensure that HEALTHCHECK is being used. The HEALTHCHECK instruction tells Docker how to test a container to check that it is still working

Healthcheck Instruction Missing
/dockerfile: 1
Ensure that HEALTHCHECK is being used. The HEALTHCHECK instruction tells Docker how to test a container to check that it is still working

Healthcheck Instruction Missing
/dockerfile: 1
Ensure that HEALTHCHECK is being used. The HEALTHCHECK instruction tells Docker how to test a container to check that it is still working

Healthcheck Instruction Missing
/Dockerfile: 2
Ensure that HEALTHCHECK is being used. The HEALTHCHECK instruction tells Docker how to test a container to check that it is still working

IAM Access Analyzer Not Enabled
/CloudFormation.yaml: 2
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

MAINTAINER Instruction Being Used
/dockerfile: 2
The MAINTAINER instruction sets the Author field of the generated images. The LABEL instruction is a much more flexible version of this and you sho...

MAINTAINER Instruction Being Used
/Dockerfile: 3
The MAINTAINER instruction sets the Author field of the generated images. The LABEL instruction is a much more flexible version of this and you sho...

Multiple RUN, ADD, COPY, Instructions Listed
/dockerfile: 144
Multiple commands (RUN, COPY, ADD) should be grouped in order to reduce the number of layers.

Fixed Issues

Severity
Issue
Source File / Package

CVE-2022-38900
Npm-decode-uri-component-0.2.2


Audio Spaces Positive Interoperability Tracker

app
Nip-53
NIP-52
B
C
D:
E:
comment

Nests
✅
.
.

Cornychat
?
✅
?

Hivetalk
?
?
?

Initial objective is to make cornychat and nests rooms mutually discoverable, and joinable

@alltheseas how about https://hivetalk.org?  We'd also like to do this. We are an audio AND Video AND Screenshare space.

Never heard of hivetalk - is it nostr based?
Yes, love to have all audio "rooms" apps interoperable

This will be a monumental failure.

why?

Well, these things were never built to be compatible, and I am pretty sure they are not interested in being compatible. My understanding was always that Nests was built to be a public conversation with a few guests and a ton of silent listeners, while Hivetalk is just a closed group chat room, and they use completely different technology choices because of that. Also I believe the CornyChat guy has explicitly denied any interest in being compatible with anything else.
Nests also has never detailed how their thing works, although it can be inferred in theory, but I tried to make a desktop client for and couldn't get some things. @v0l said they're changing some things and working on a NIP, which would be the first step towards getting any interoperability.
In a way I think CornyChat and HiveTalk are not really "Nostr clients", they're more like normal apps, like Jitsi or GoogleMeet competitors, that happen to use Nostr identities, which is good.

Have you actually talked to the Devs of each?

@fiatjaf what would be needed to make HiveTalk a Nostr client?

Have you actually talked to the Devs of each?

Not really. Did I say anything very stupid?

what would be needed to make HiveTalk a Nostr client?

It depends on how you define a Nostr client. After posting my comment above I saw that Derek Ross was questioning the clientness of CornyChat, but after that now I think it isn't fruitful to be too strict about the definition of "client". What I had in mind though was a program that followed an open standard described somewhere (be it on a NIP or elsewhere) and that was ready (and willing) to be interoperable with other programs that also implemented the same standard.
In my understanding CornyChat and Hivetalk are not such things, they are just webapps that connect to a hardcoded server and allow people to chat in closed groups, and I don't think they should be trying to be more than that actually, because we don't need censorship-resistance, discovery or any of the other Nostr features for the audio-meeting-room use case. In my mind to have such calls it would suffice for groups to coordinate over Nostr to use some third-party service like Jitsi or whatever, have their audio call, then go back. If Hivetalk and CornyChat have built-in Nostr identities that makes the experience better, but I don't see any way to go further.
Now about Nests I think it benefits from being a more standardized Nostr subprotocol because, similarly to NIP-53 video livestreams, it is made for public broadcasts, therefore it benefits from Nostr's core features.

@fiatjaf no, of course not. Nice to officially meet you btw. I was just curious as I know how hard the dev for HiveTalk works on this product. I would hate for any dev to feel defeated and give up on a passion project. I appreciate the additional context you provided.

Today I learned NIP-53 exists, and nests uses this, whereas cornychat uses NIP-52 calendar events.
Dont give up hope just yet @fiatjaf

Have you actually talked to the Devs of each?

Not really. Did I say anything very stupid?.

You did. The “CornyChat dev” does support interoperability with other nostr platforms. He explicitly goes out of his way to be as interoperable as possible, displays live activities from other platforms if published properly, and links users to other platforms to encourage interoperability and multi platform usage.
Take some time to read his outline here.
https://cornychat.com/datatypes
While not all interoperable priorities have been completely implemented, he is only one guy working when he has the time to better nostr.

Also I believe the CornyChat guy has explicitly denied any interest in being compatible with anything else.

FWIW, I am "the CornyChat guy", and I'm for open standards and interoperability and compatibility wherever its possible and makes sense from a UX standpoint.  It should be very easy for people to find me seeing as the home page of the application links to my profile. If you have any questions/comments/concerns/ideas, you can reach out directly.
Corny Chat is built on open source work, forked from Jam Systems, and integrates several NIPS and kinds of nostr to enrich the product. Similarly, HiveTalk also is built on existing open source, forked from MiroTalk SFU.  From a user standpoint, initial integrations benefit greatly by use of common identities, user profiles, zap support etc.  Going beyond that adds more noticeable value
Corny Chat implements all or part of NIP-1 (basic protocol), NIP-2 (follow list), NIP-5 (nostr addresses),  NIP-7 (browser extension), NIP-9 (event deletions), NIP-10 (use of e and p tags), NIP-19 (bech32 encoding), NIP-24 (extra metadata fields), NIP-38 (statuses), NIP-40 (expirations), NIP-47 (wallet connect), NIP-51 (lists), NIP-52 (scheduling), NIP-53 (live activities), NIP-57 (zaps), NIP-58 (badges), NIP-65 (relay list metadata), NIP-75 (zap goals), NIP-81 (relationships).

we don't need censorship-resistance, discovery or any of the other Nostr features for the audio-meeting-room use case.

I'm going to respectfully disagree here.  Censorship resistance may not be a primary goal, but we shouldn't be actively fighting against that either, which is something that key nostr influencers (a.k.a nostrati) are doing. I implore them to stop the negative actions they are taking which harms communities as a whole.
Likewise on discovery, we need more discovery, not gatekeepers.  Trying to funnel everything into singular clients is a huge mistake.  Corny Chat contributes to this discovery as the NIP-53 events from other apps such as Nostr Nests, Zap Stream, and forks of Corny Chat will show on the Corny Chat homepage, just like Zap Stream shows events from others.

but I don't see any way to go further

That's the beauty of open standards. You don't need to have an all encompassing vision.  Other developers will build the applications that users make use of every day.
Corny Chat will continue to be enhanced and with respect to NIP-53 interoperability, the road map does include finding some means to provide a merged HLS stream so users accessing the live activity in apps like Amethyst will be able to listen.

Thanks Vic for all you do!

Fiat Gayf should take a line out of the book of Satoshi and just disappear.

app Nip-53 NIP-52 B C D: E: comment
Nests	✅	.	.
Cornychat	?	✅	?
Hivetalk	?	?	?

app Nip-53 NIP-52 B C D: E: comment
Nests	✅	.	.
Cornychat	?	✅	?
Hivetalk	?	?	?

I updated your table for you based on Vic’s above reply. Not sure about hivetalk and nostr nests support, surely they support some of these nips as well…

App
Nip-53
Nip-52
Nip-47
Nip-57
Nip-75
Nip-2
Nip-5
Nip-7
Nip-9
Nip-10
Nip-19
Nip-24
Nip-38
Nip-40
Nip-51
Nip-58
Nip-65
Nip-81

Nostrnests
✅
?
?
?
?
?
?
?
?
?
?

Thanks for the detailed response @Nostr-Tortuga. My objective with this nostrability tracker was to check if its possible for cornychat and nests rooms to be mutually discoverable, and joinable.
A non-objective is to make sure each app follows the same NIPs.
I will take the information you provided on cornychat, and add it to the respective NIP tracker.
Gracias.

It would seem the answer is that mutually discoverable is certainly possible.
Mutually joinable seems to depend on how one defines “join.” If by join you mean can listen from outside, then certainly possible. If by join one means can speak to participants from within the other, doubtful.
But what can certainly happen is each platform can include links within the live activities and the apps can redirect users to the other platform to “join”for speaking purposes. Corny chat uses live activities to redirect users to zap.stream content already.


Error unmarshalling deployment transaction for block event: proto: protos.ChaincodeDeploymentSpec: wiretype end group for non-group

I get the following error after a deploy transaction on all 4 peer.But the docker container comes up successfully .
Note: I have consensus set to obcpbft classic , security is turned on and privacy is turned on .
00:15:03.163 [consensus/obcpbft] processNewView -> INFO 055 Replica 0 ignoring new-view from 3, v:3: we are active in view 3
00:15:05.991 [container] newDockerClient -> INFO 056 Creating VM with endpoint: unix:///var/run/docker.sock
00:15:06.322 [ledger] sendProducerBlockEvent -> ERRO 057 Error unmarshalling deployment transaction for block event: proto: protos.ChaincodeDeploymentSpec: wiretype end group for non-group

what could be the cause of this ?

please provide complete logs from all peers

@corecode  I have attached below the logs on all 4 peers . Thanks.
deploy3.txt
deploy4.txt
deploy1.txt
deploy2.txt

@clydedacruz : this error occurs during event generation and is not related to consensus.  Should affect only event listeners.

@muralisrini do you understand how this happens?  I had a brief browse through the code, but couldn't figure out the flow of the message.

@clydedacruz, #1204 seems a duplication of this. Shall we close this issue because the discussion is now on #1204?

@adecaro  sure you can close it .


Able to access minio

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
No
Describe the solution you'd like
A clear and concise description of what you want to happen.
Able to access minio using port forward
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
I would like to access minio service that comes with epinio. Currently with port-forward minio will not let you login due to invalid ssl

What are you hoping to do with the data in minio? These buckets aren't supposed to be used for other workloads

What are you hoping to do with the data in minio? These buckets aren't supposed to be used for other workloads

The disk usage keeps growing until K8s couldn't garbage collect. After uninstalling Epinio everything is back to normal.
So, we suspect it's Minio.

Ok, then I think we should address that issue directly and improve our garbage collection. Would you mind if I edited the name of this ticket to reflect that?
@gitricko We are looking at s3gw in #1876

@Lodimup Would you mind deleting a bunch of apps the next time you run into this to see if it resolves the issue naturally? If so, it could be that #1646 is the culprit and too much is being uploaded on each push.

Restarting the cluster make the total usage go down a bit. Not sure if related. Uninstalling/Reinstalling epinio resolved the issue.
thanks for good work!

We really love Epinio. The spec was T2.Large, 2vcpu 8gb ram. about 4 apps.

We really love Epinio. The spec was T2.Large, 2vcpu 8gb ram. about 4 apps.

For us, we use the stock epinio with minio and registry as part of the install. Instability start to grows (timeout from registry) when we have lots of deployments. For minio, it is fairly stable. We are able to run 11 apps with 7 backing services on a C5.large 32g ram 16cpu in dockerize k3s


Bugfix/withdraw check

There is only one change from MatchMakerV3 to V4
-> ensure that the match is not already finished when you withdrawFromMatch. Otherwise it would count as an escape.
The change can be found in line 193
 matches[matchId].phase < Phase.GameOver

Very good finding, will upgrade contract asap.


More accurate work with internal exceptions

FIxes #253

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

Project coverage is 44.39%. Comparing base (988318e) to head (10b4395).

Files
Patch %
Lines

core/src/main/java/tech/ydb/core/Status.java
54.16%
4 Missing and 7 partials :warning:

...src/main/java/tech/ydb/table/impl/BaseSession.java
0.00%
4 Missing :warning:

...ain/java/tech/ydb/core/impl/BaseGrpcTransport.java
0.00%
3 Missing :warning:

core/src/main/java/tech/ydb/core/Result.java
66.66%
1 Missing and 1 partial :warning:

...src/main/java/tech/ydb/query/impl/SessionImpl.java
50.00%
2 Missing :warning:

...n/java/tech/ydb/coordination/impl/SessionImpl.java
0.00%
1 Missing :warning:

.../java/tech/ydb/coordination/impl/SessionState.java
0.00%
1 Missing :warning:

...c/main/java/tech/ydb/coordination/impl/Stream.java
0.00%
1 Missing :warning:

...ain/java/tech/ydb/coordination/impl/StreamMsg.java
66.66%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #275      +/-   ##
============================================
- Coverage     44.43%   44.39%   -0.04%
- Complexity     1568     1571       +3
============================================
  Files           297      297
  Lines         11502    11505       +3
  Branches       1121     1124       +3
============================================
- Hits           5111     5108       -3
- Misses         5987     5988       +1
- Partials        404      409       +5

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


Implements DreamMetaObjectIcon, Width(), Height()

See #141
This is some messy 3am coding, opening as a draft to make my life easier.

Probably good to review.


Live Rust: log show error  decode expected value

First , Thank you this project
Environment
VM

1 CPUs
1 GB

binancefutures toml
# Testnet: wss://fstream.binancefuture.com/ws
# Mainnet: wss://fstream.binance.com/ws
# Private: wss://fstream-auth.binance.com/ws
# Low-Latency Market Maker: wss://fstream-mm.binance.com/ws
stream_url = "wss://fstream.binance.com/ws"

# Testnet: https://testnet.binancefuture.com
# Mainnet: https://fapi.binance.com
# Low-Latency Market Maker: https://fapi-mm.binance.com
api_url = "https://fapi.binance.com"

order_prefix = "test"
api_key = "****"
secret = "****"

After I run connector and use live grid, the logs of strategy shows as follows, symbol: 1000shibusdt:

the  logs of connector, seems in ordermanager:

I cannot see anything trade on Binance App
I searched the error text,  seems the logic run to here:

and the root cause maybe in submit_order return error:

I don't encounter any issues, at least on the testnet. Could you check if the issue persists there?