param with '~'(tilda) gets encoded as '~~' by $urlMatcherFactory.format

As the title describes:
Tested with angularjs 1.5.8 and ui.router 1.0.0.beta3
See
https://plnkr.co/edit/00Ffv7TqsRh3vrfa4ZO5?p=preview

Thanks for the plunker.
This is a known issue.  Hopefully we can address it in a future release.  For now, you can declare your parameter as any type and it will not specially encode slashes/tildes.
  const url = '/url?{param:any}'

https://plnkr.co/edit/zlUprCzPYxVqX6rLWiGg?p=preview

For more details about why this occurs, see #2598


Fixed coverage badge.

Used wrong branch specifier.

Coverage remained the same at 96.029% when pulling 51525b22e76e537408cead99ef8b1fb499f8b61a on bd82-patch-1 into 16f0fa82941231f8d983ec77dd350a07821427bd on master.

Coverage remained the same at 96.029% when pulling f7c17ea03e311feded6baca5740e31a94560b412 on bd82-patch-1 into b16c93aaa4431420160fdb8bdcd85f2d7de239dd on master.


Organization Users' emails

Are we supposed to see all the organization users with their emails in the organization page?
See this organization https://www.codabench.org/profiles/organization/6/

We do not want users email to be public


Error message pulls focus out of problems view

Background: I had a tslint error reported in a file that I deleted. The error still showed up in the problems view.

Focus on an entry in the problems view in a file that still exists. This can be done by clicking into the problems view or using the keyboard
Use arrow keys to move between problems
Notice that as you move between them, an editor previews the area with the problem but the focus remains in the problem view
Use the arrow keys to move to a problem for a file that does not exist.

Expected: If an error message appears, it will return focus to the problems view
Actual: An error message appears (Unable to open 'filename', file not found), but then focus moves to the editor in the location of the last valid problem.

Looks like it is already fixed


X.com icon used for any domain that has x in it

Hey! Just wanted to say thanks for keeping this library maintained all this time, it's been very helpful over the years 🙏
What is happening
With the recent v6 release and addition of the x.com support - any domain that has x in it is now treated as x.com.
E.g. if you use https://tlx.dev it will be marked with x.com's icon and not with a generic link icon.
I looked at the code and it seems like the issue comes primarily from the fact that the generator doesn't utilize tlds in the search, so it results in a regex like this being constructed
(?:https?:\/\/(?:[a-z0-9-])?)?(x)[.]

Which would match anything with an x

What is the desired result
It feels like the matcher should also include the tld so then it will not grab unrelated websites like that.

@orels1 Thank you for the kind words. The issue has been addressed in v6.4.0


fix typer version

closes #2984

As discussed on discord, i believe this is a poetry issue rather than a problem with typer 0.12 and reflex itself


Azure OpenAI Support

We are considering to make your software available for our junior developers to help them to improve their coding skills.
Therefore, I have been exploring the different GPT integrations that are available. I am particularly interested in using Azure Open AI for this projects, but I have not been able to find any information on whether your software supports it or if there are any plans to do so in the future.
Could you please let me know if there are any plans to support Azure Open AI? If not, are there any workarounds that I could use to integrate it into my projects?
Thank you for your help.

Hi @jimmylevell, we certainly will support other Large Language Models and endpoints in the future. Thank you for letting us know that you are interested in integrating Azure Open AI. If possible, we would appreciate it if you could provide some sample code examples and using scenarios for using Azure OpenAI API to help us with the integration.

@EasonC13 Here is a proposed solution to make the extension compatible with Azure OpenAI:

Implement a configuration option to make the OpenAI library base URL configurable. This will allow users to easily specify their own Azure OpenAI deployment URL. You can refer to the configuration.ts file in the GitHub repository to identify the relevant code section that needs modification.

Update the readme file to provide instructions for users who want to use their own Azure OpenAI deployment. Suggest deploying a proxy that can convert OpenAI API calls to Azure API calls. You can mention a specific project, such as azure-openai-proxy, which I have personally used to successfully convert OpenAI calls to Azure calls.

By implementing these changes, users will have the flexibility to utilize their own Azure OpenAI deployment with the extension. This solution promotes compatibility and allows users to seamlessly integrate Azure OpenAI functionality into their workflows.

@hdiabi-via Thank you for your suggestion. Will do it when I have time.

@hdiabi-via @jimmylevell
I had updated it in this commit https://github.com/GPTutor/gptutor-extension/commit/dfc3291afb0d1d66dd19923c6a9afc7d287dc6b4
Hope you can try it by Setting -> Set Model Parameters -> Base Path

Let me know if it work or not, so I can close this issue.


Allow user defined CustomJS callbacks to be applied

A number of feature requests we have accumulated ask for fairly specific functionality which would really best be served by an easy way of setting up CustomJS callbacks on bokeh models (e.g. see https://github.com/ioam/holoviews/issues/1114). I'd therefore suggest we expose some way of setting up CustomJS callbacks that allow for all kinds of complex interactivity.

Whatever approach we take, I think HoloViews should only ever deal with CustomJS bokeh objects. That would help make it clear this is bokeh's functionality we are supporting and not some JS particular to holoviews.


Multiple closing tags added

When I type my closing tag it adds a bunch of extra tags afterwards. Any ideas?
Link to the HTML file in question
This also happens with the Tag addon: https://github.com/uzyn/tag/issues/24

This is usually caused by less-than-slash being activated more than once,
try uninstall, close atom, open atom then reinstall. If the problem
persists let me know
On Tue., 11 Apr. 2017, 8:34 am James Nisbet<EMAIL_ADDRESS>wrote:

[image: 2017-04-11_10h31_37]
https://cloud.githubusercontent.com/assets/30508/24885360/21c419d4-1ea2-11e7-93a5-c1a62b3bf231.png
When I type my closing tag it adds a bunch of extra tags afterwards. Any
ideas?
Link to the HTML file in question
https://gist.github.com/Bandit/086a75409760566654ea47b19d24ec5f
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mrhanlon/less-than-slash/issues/47, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AHazr4LaoRiVoRMImrcZyy2f6sFhuqHmks5ruq6MgaJpZM4M5Z75
.

That fixed it. What would cause it to be activated more than once? Multiple Atom windows open?

I thought I fixed it ages ago but apparently not, it usually happens when you disable and re-enable the plugin, or if you update. Something must be wrong with our deactivation handlers.

Interesting. I installed this addon for the first time today after uninstalling Tag thinking it was faulty. Maybe it was an un-deactivated Tag instance causing the issues?

Just installed tag and played with the enable/disable toggle. Their package
is not deactivating properly and causing the multiple closing tags.
On Tue., 11 Apr. 2017, 9:04 am James Nisbet<EMAIL_ADDRESS>wrote:
Interesting. I installed this addon for the first time today after
uninstalling Tag https://atom.io/packages/tag thinking it was faulty.
Maybe it was an un-deactivated Tag instance causing the issues?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mrhanlon/less-than-slash/issues/47#issuecomment-293103716,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHazr6gMoslp7xzyvpdD4IuFcwBMsZ3fks5rurWOgaJpZM4M5Z75
.

This workaround does not seem to work for me permanently. The extra tags always come back.


Marginalia annotation not working with persp-switch-to-buffer*

I am using selectrum for completion. Since perspective generates a list as a candidate list for completing-read, when using persp-switch-to-buffer* marginalia's annotations don't work.  According to https://github.com/minad/marginalia/issues/48 :

buffer completion category the problem should be fixed and you will get the usual marginalia buffer annotations which work for switch-to-buffer!

Though I have not clue what this means.

I gave it a shot. Can you try the https://github.com/nex3/perspective-el/tree/add-metadata-to-persp-switcher branch?

sweet, thanx alot. This seems to work. I'll open a new issue if I run into anything else related to this.

Patch merged into master and should reach MELPA in a couple of hours.

For reference for anyone looking for a solution with consult
     (consult-customize consult--source-buffer :hidden t :default nil)

     (defvar consult--source-perspective
       (list :name     "Perspective"
             :narrow   ?s
             :category 'buffer
             :state    #'consult--buffer-state
             :default  t
             :items    #'persp-get-buffer-names))

     (push consult--source-perspective consult-buffer-sources)


🔍 Use the same verification for other wordlist-related commands

Currently, when loading a wordlist, a verification process first checks if it's applicable to be a wordlist. However, these functions:

restore()
stack()
merge_delete()

don't support such validation yet. This can be easily implemented by adapting the algorithm from load_wordlist() to work with the methods mentioned above.

Implemented!


Formatting tweaks and minor spelling fixes

@adbertram : Thanks for your contribution! The author, @tylerleonhardt, has been notified to review your proposed change.

@adbertram : Thanks for your contribution! The author, @tylerleonhardt, has been notified to review your proposed change.

#sign-off

@GitHubber17 : Thanks for your contribution! The author, @tylerleonhardt, has been notified to review your proposed change.

@adbertram - Thank you for your contribution. Our style is to use sentence case for headings. I made a few adjustments to your suggested changes. Thanks!


Any plans to implement landscape mode for tabs?

Per the following react-native-scrollable-tab-view commit: https://github.com/skv-headless/react-native-scrollable-tab-view/commit/d8cbf1def7a6b3affd1a1cf87693b53065f1c5fe

+1

Landscape mode is not something very high on our priority list right now.


Make sure tests are run with full error reporting

This is also done in all symfony components. It makes sure that tests report all errors and warnings including strict ones.
Often this is not the case otherwise (because it's not part of the php defaults). The other advantage is that it makes tests more equal in PHP 5 and PHP 7. PHP  7 removed strict errors and changed them to warnings or notices. So in PHP 7 those errors might cause failures but they do not cause failures in PHP 5 when strict is ignored.

@nicolas-grekas what do you think?

:+1:

I wonder how this interacts with https://github.com/symfony/symfony-standard/blob/2.8/app/autoload.php#L6 that is part of the bootstrapping?

@Tobion I think this line should be specific to entry points (app.php, app_dev.php and console) and not the autoloader :confused:

@nicolas-grekas do you agree with this PR? And shouldn't we add symfony/phpunit-bridge to the require-dev section as well?

LGTM Yes. Adjoint the bridge is a good idea although not strictly required since it looks like that no deprecations are triggered for now

I just tested it with phpunit and the php config is executed before AND after the bootstrap file. So the error_reporting is -1 when calling autoload and is reset to -1 after it by phpunit. But it is not set for each test. This is strange behavior by phpunit. But at the end it doesn't really matter to us. There is no difference if error reporting is -1 or -1 & ~E_USER_DEPRECATED if you use the phpunit bridge.
So this is good to be merged.

For the phpunit-bridge I created #884

Thank you @Tobion.


Create IconButton

High quality scalable icon buttons can help the application look more professional.
I’ve tried using background images on the normal Button, but normal images do not scale well to arbitrary sizes and the raster images look odd.
we should be able to make a proper icon button if we draw the icon using canvas instructions. Consider creating a SVG reader that can convert SVGs into canvas instructions. We could use this reader to support SVG icon images.

Closed with #9.


x/tools/gopls: bad error state after editing

What did you do?
Created a file and typed a bunch of code. After saving, gopls correctly added an import to net/http.
What did you expect to see?
No errors.
What did you see instead?
However, it still displays a marker for the error undeclared name: http, and on the wrong line.

This kind of thing happens fairly commonly (and I just restart gopls), but in this case it was a brand new file, so the section of log starts at the initial opening of the file, so hopefully this has all relevant log messages to diagnose the problem.
Log
gopls.log.gz
Build info
golang.org/x/tools/gopls v0.3.4
    golang.org/x/tools/gopls@(devel)
<EMAIL_ADDRESS>h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
<EMAIL_ADDRESS>h1:Kpca3qRNrduNnOQeazBd0ysaKrUJiIuISHxogkT9RPQ=
<EMAIL_ADDRESS>h1:WG0RUwxtNT4qqaXX3DPA8zHFNm/D9xaBpxzHt1WcA/E=
<EMAIL_ADDRESS>h1:8gQV6CLnAEikrhgkHFbMAEhagSSnXWGV915qUMm9mrU=
<EMAIL_ADDRESS>=> ../
<EMAIL_ADDRESS>h1:/atklqdjdhuosWIl6AIbOeHJjicWYPqR9bpxqxYG2pA=
<EMAIL_ADDRESS>h1:sXmLre5bzIR6ypkjXCDI3jHPssRhc8KD/Ome589sc3U=
<EMAIL_ADDRESS>h1:KaMb5GLhlcSX+e+qhbRJODnUUBvlw01jt4yrjFIHAuA=

Go info
go version go1.14 darwin/amd64

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/alex/Library/Caches/go-build"
GOENV="/Users/alex/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY="github.com/t11e/*"
GONOSUMDB="github.com/t11e/*"
GOOS="darwin"
GOPATH="/Users/alex/.go"
GOPRIVATE="github.com/t11e/*"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/opt/go/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/opt/go/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/qs/wpmg19r12_9_nz7pvvs2_82r0000gn/T/go-build683361864=/tmp/go-build -gno-record-gcc-switches -fno-common"

Thank you for the report and the log!
A few quick thoughts / questions:

Is the client.go file the only file in the package?
I noticed in the log is that none of the textDocument/codeAction requests have a non-empty response (code actions are used for import organization), but the "net/http" import does get added. If you can remember - did you add net/http by accepting a completion or do you have any other VS Code extensions installed that might be adding this import?
The main issue seems to begin after the didChange to add import "net/http". We seem to try to reload the package command-line-arguments, which is a placeholder package path for an ad-hoc package (a package that is outside of GOPATH or a Go module).

[Info  - 8:37:28 PM] 2020/03/20 20:37:28 go/packages.Load
	snapshot = 1975
	query = [command-line-arguments]
	packages = 1
[Trace - 20:37:28.546 PM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/03/20 20:37:28 go/packages.Load\n\tsnapshot = 1975\n\tpackage = command-line-arguments\n\tfiles = []"}

[Info  - 8:37:28 PM] 2020/03/20 20:37:28 go/packages.Load
	snapshot = 1975
	package = command-line-arguments
	files = []
2020/03/20 20:37:28 diagnose: could not generate diagnostics for go.mod file: command-line-arguments has no metadata

It seems you are using modules - are you opening VS Code at the root of your module or a subdirectory? It seems like we're treating your package as an ad-hoc package.
Something we can definitely do is make sure that we don't try to reload packages with the path command-line-arguments as that is always wrong.

Is the client.go file the only file in the package?

Yes

... did you add net/http by accepting a completion or do you have any other VS Code extensions installed that might be adding this import?

I typed *http.Client and hit "save" to let the formatter kick in. No other extensions.

It seems you are using modules - are you opening VS Code at the root of your module or a subdirectory?

Root, though it's a workspace with multiple folders.

I typed *http.Client and hit "save" to let the formatter kick in. No other extensions.

Hm, based on the log that doesn't seem to be the case. Would you mind sharing a log where you follow that same workflow just so that I can confirm if things are working properly?

Root, though it's a workspace with multiple folders.

Thanks for the confirmation. It sounds like gopls may not be loading your workspace correctly. Would you mind sharing the logs starting from the very beginning of the gopls instance when you open that workspace?

I am actually able to reproduce the bug consistently, doing exactly what I described:

Create a new folder client.
Create an empty file called client.go.
Type:

package client

type Client struct {
  hc *http.Client
}

Hit Save.

Here's a gopls log from doing the above, and nothing else: gopls.log.gz.

Thanks for attaching the log! It's helped me notice a few deficiencies in the way we log for multi-project workspaces, so I will mail a change to address some of them soon.
Another question about your workspace - it seems like only one go.mod workspace was detected by gopls, but it sounds like you expect there to be 2 - is that correct?
Also, are you able to reproduce this if you only open that project instead of your multi-project workspace?

but it sounds like you expect there to be 2 - is that correct?

Yes.

Also, are you able to reproduce this if you only open that project instead of your multi-project workspace?

No.

I am also able to reproduce the bug if I have only one project in the workspace. So it's not related to the other project in the workspace that also has a go.mod file.

Thanks! I've mailed the above changes to address some of the immediate issues I noticed from the logs, so I will ask you to try again after those are merged.
If you'd like to try one more thing in the meantime, could you create a repro log with a single-project workspace? It might make it a bit easier for me to parse your log. If not, totally fine to wait until after those changes are merged. Thanks for your help on this!

These changes are now merged, and you can try them out by updating to gopls at master (GO111MODULE=ON go get golang.org/x/tools/gopls@master golang.org/x/tools@master). Please let me know if these fixes addressed the problem, and if not, please attach new logs. Thanks for your patience!

Thanks! Unfortunately, no difference. Here's a log.
I will get you a log from a single-project workspace.

Uh, I don't know what happened. After reloading the VSCode window (Developer: Reload window) a few times, I am no longer able to reproduce in the same workspace. I definitely upgraded before. Will do some more experimenting.

Reloaded the window, and am once again able to reproduce it, even in a workspace that contains just the one Go project: gopls.log.gz. I'm no longer not able to reproduce it.

By the way, I'm installing from source: git reset --hard origin/master && go install .. Installing via go get doesn't work for me:
$ GO111MODULE=on go get golang.org/x/tools/gopls@master
go: downloading golang.org/x/tools/gopls v0.1.8-0.20200324201824-1fc30e1f4ccc
go: golang.org/x/tools/gopls master => v0.1.8-0.20200324201824-1fc30e1f4ccc
go: downloading golang.org/x/tools v0.0.0-20191130070609-6e064ea0cf2d
# golang.org/x/tools/gopls/internal/hooks
.go/pkg/mod/golang.org/x/tools/gopls@v0.1.8-0.20200324201824-1fc30e1f4ccc/internal/hooks/hooks.go:19:9: options.URLRegexp undefined (type *source.Options has no field or method URLRegexp)

Thanks for the log! I am now able to reproduce this issue myself. I'll aim to have a fix soon.
By the way, some of the error messages in your logs (no matching versions for query "latest") would likely stop if you added your project to your GOPRIVATE environment variable. Also, the command to get gopls from master is GO111MODULE=ON go get golang.org/x/tools/gopls@master golang.org/x/tools@master.

Super, thank you.

your GOPRIVATE environment variable

Good catch, I didn't realize that!

GO111MODULE=ON go get golang.org/x/tools/gopls@master golang.org/x/tools@master

Oh, I didn't realize it took multiple arguments. For global installs, it maybe resolves them together as if they were in the same go.mod/go.sum?


Update CCDL logos

Context
We have a new logo
Problem or idea
There are two spots where the logo is:
- Landing page:
We should replace the ALSF and CCDL logo with the CCDL x ALSF logo

Footer
We should replace this with the main logo. ( we can technically use the shorthand here but based on the layout, (i.e., the height of ALSF logo, it's best to use the main one)

Solution or next step

Also have to update the figures to have the new logos. Github doesn't let me attach svgs, will slack you.


New GitHub Pages Site

The current github pages site serves as the core documentation endpoint for the project. With #189 we are moving the documentation into the repository. We will need to recreate the site so it serves more as an introduction to the library than a fully fleshed out technical documentation site.
We will need to answer the following before proceeding:

Is there a designer who is willing to come up with a new layout / color scheme for the site? If anyone is/knows someone who might want to do this please comment on the ticket!
What do we want to communicate and how should the site be laid out? A simple single page? Perhaps more?

Anyone who is interested in taking this on will have me as their partner moving forward, don't be afraid to get your hands dirty :)

For point 2, single page would be fine given the number of chart types Epoch currently has. It should contain similar breakdown of the current gh-page information, with the addition of dedicated API documentations to complement to offer another way to find usage examples.


Add tooltip of alert name

Version: master 2.2 (12/14/18)
What kind of request is this:
Enhancement
Request:
There are currently no tooltips for alert names. Some alert names (even our defaults) have names too long so they cannot fit in the UI.
I propose that we add tooltips so that you can at least hover over the names for a bit to see the full name.
Example screenshot:

Current workaround requires you to edit the alert just so you can see the full name of the alert.

@n313893254 is it possible to tweak the tooltip so that the little arrow points to the center of the name column rather than the middle of the resulting tooltip text? See this screenshot for example. The little triangle pointing downwards is too far to the right. Or would it be better if I open a separate issue for this?

Version: master 2.2 (12/20/18)
Confirmed enhancement. The tooltip will now appear for any alert. A separate issue will be created regarding my comment about how the small arrow under the tooltip is not pointing to the right area. Issue is: #17203


update schema to fix errors with clickhouse 23.9

https://github.com/ClickHouse/ClickHouse/blob/master/CHANGELOG.md#improvement
Clickhouse on version 23.9 updated information_schema.tables.table_type  from Enum8 to String

Do I get right now that version 23.9 will be required now as the minimum version?

No, it will be backward compatible. Enum8 can be compared against Integers and Strings, while Strings can only be compared against Strings.
I updated the query to use string in the WHERE clause, it should work with the older versions and the newer one.

Tested it on 23.3, it breaks compatibility. Let's try to honor the 1-year support period of the LTS (up to 2024-03)
2023-11-27T10:17:16.679-0500 ERRO (sink-sql) new db loader: load psql table: retrieving table and schema: code: 53, message: Cannot convert string BASE TABLE to type UInt8: while executing 'FUNCTION equals(multiIf(is_temporary, 4, like(engine, '%View'), 2, like(engine, 'System%'), 5, equals(has_own_data, 0), 3, 1) : 19, 'BASE TABLE' : 14) -> equals(multiIf(is_temporary, 4, like(engine, '%View'), 2, like(engine, 'System%'), 5, equals(has_own_data, 0), 3, 1), 'BASE TABLE') UInt8 : 20'


[openssl-1.0.1m] After successful TLSv1.0 negotiation in  SSLv23 mode, openssl fails to send the data in one ssl_write() API call.

Version: openssl-1.0.1m
System: CentOS 6.5 (64-bit and 32-bit)
Environment: Lync Server 2010 and an openssl client.
After successful TLSv1.0 negotiation the client is not able to send the data to Lync Server 2010 with ssl_write() API.  The data reach the server if I usessl_write() API 2 times with the same data.
openssl context has been initiated using sslv23 method.
But in openssl-1.0.1g  with method sslv3 it works fine for SSL. Is their any specific configuration necessary or is that not related to openssl?

It's unclear from the description what the problem is. Please raise such question on the openssl-users email list. Details here https://mta.openssl.org.


ref.json: "ref valid, maxItems ignored" test question

Hi! On my way to my own draft-6 validator implementation in C++ I'm currently running the draft-4 test cases. My test suite throws a difference to the expected result for the "ref valid, maxItems ignored" test case in ref.json:
"schema": {
    "definitions": {
      "reffed": {
           "type": "array"
      }
    },
    "properties": {
         "foo": {
             "$ref": "#/definitions/reffed",
             "maxItems": 2
         }
    }
}

"data": { "foo": [ 1, 2, 3 ] }
My understanding is that the test case should be invalid because of the maxItems keyword.
Am I wrong or is the test case wrong?
Thanks a lot!

@Clemens-U The object with {"$ref":...} isn't a schema (because it's a reference), so you wouldn't process the "maxItems" property in it.

I see. Thanks a lot for your answer. I'm currently combining the schema context. So this is easy to fix for me. I guess I need to update my JSON schema analyzer also in the regard...


Encountered error while generating package metadata

How to fix the error below
 × python setup.py egg_info did not run successfully.
...
pkg_resources/_vendor/packaging/requirements.py", line 9, in <module>
× Encountered error while generating package metadata.
╰─> See above for output.

when running "pip install -r requirements/requirements.txt"? Thanks

It says "See above for output." because the relevant error details are above. Can you edit your post to include them?

Closing due to inactivity.
You have frequently opened issues with insufficient documentation and then abandoned them. Please stop doing so. If you do not have the ability or willingness to respond to questions, please refrain from leaving issues in the future.


is there a .min version available?

Nope. I see no need for it either. Minification should be done on your complete application bundle, not the individual library files so the minifiers can easily remove dead code and minimize code more efficiently.

I think it doesn't hurt to have ready to go .min version.
What if, I don't have to deal with build system.

I would assume that you want to minify the code for performance reasons. And without a build system you can't really bundle it, so that would mean that your application would require a minimal of 2 HTTP requests. 1 for your application code and 1 for this library. It would be a faster to bundle the app code and library in 1 file, unminified than it would be to load the library minified and your application code minified. So that doesn't make any sense in time performance gain or time invested.
But if you're feeling strongly about it, i'll be more than happy to accept a pull request which adds and generates a minified build when we publish a new release.


Patch release 1.10.6

Description
Merging fixes into release branch first:
https://github.com/dapr/dapr/pull/6277
https://github.com/dapr/dapr/pull/6270
Issue reference
Fixes https://github.com/dapr/dapr/issues/6268
Fixes https://github.com/dapr/go-sdk/issues/390
Fixes https://github.com/dapr/components-contrib/issues/2786
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

I am working on the release notes.

I am working on the release notes.

Done.

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

It does not work. It seems to be some incompatibility with the master version.

Dapr E2E test
🔗 Link to Action run
Commit ref: 5fb0406
❌ Infrastructure deployment failed
Cluster	Resource group name	Azure region
Linux	Dapr-E2E-dapre2eddaa08ba22l	westus3
Windows	Dapr-E2E-dapre2eddaa08ba22w	westus3
Linux/arm64	Dapr-E2E-dapre2eddaa08ba22la	eastus
Please check the logs for details on the failure.
❌ Build failed for linux/arm64
Please check the logs for details on the error.
❌ Build failed for linux/amd64
Please check the logs for details on the error.
❌ Build failed for windows/amd64
Please check the logs for details on the error.

first the k8s version that this is trying to deploy is no longer available. That is why infra deployment fails.


the trait bound ** is not satisfied problems - conflict

Hello.
I just need to get UUID from Postgres and serialize with serde. My Cargo.toml:
[dependencies]
serde="1.0.2"
serde_derive="*"
bincode="*"

[dependencies.uuid]
version = "0.5.0"
features = ["serde"] //allows Serialize

[dependencies.postgres]
version = "*"
features = ["with-uuid"] //allows ToSQL

version=0.5.0 let me to download new version of UUID and Serialize works for UUID (0.4.0 not), but postgres-shared wants 0.4.0.
cargo tree
├── postgres v0.14.1
│   ├── bufstream v0.1.3
│   ├── fallible-iterator v0.1.3
│   ├── log v0.3.7 (*)
│   ├── postgres-protocol v0.2.2
│   │   ├── byteorder v1.0.0 (*)
│   │   ├── fallible-iterator v0.1.3 (*)
│   │   ├── md5 v0.3.4
│   │   └── memchr v1.0.1
│   │       └── libc v0.2.22 (*)
│   └── postgres-shared v0.2.1
│       ├── fallible-iterator v0.1.3 (*)
│       ├── hex v0.2.0
│       ├── phf v0.7.21
│       │   └── phf_shared v0.7.21
│       │       └── siphasher v0.2.2
│       ├── postgres-protocol v0.2.2 (*)
│       └── uuid v0.4.0 (*)
├── serde v1.0.2 (*)
├── serde_derive v1.0.2
│   ├── quote v0.3.15
│   ├── serde_derive_internals v0.15.0
│   │   ├── syn v0.11.11
│   │   │   ├── quote v0.3.15 (*)
│   │   │   ├── synom v0.11.3
│   │   │   │   └── unicode-xid v0.0.4
│   │   │   └── unicode-xid v0.0.4 (*)
│   │   └── synom v0.11.3 (*)
│   └── syn v0.11.11 (*)
└── uuid v0.5.0
    └── serde v1.0.2 (*)

So where are 2 versions of uuid and i get error
the trait bound `uuid::Uuid: postgres::types::FromSql` is not satisfied

How rust will compile this? It think that where are 2 different separated structs UUID? How about shared methods and same memory?
How to resolve this conflict? I edited Cargo.toml of postgres-shared in cargo cache and later cargo clean, but It uses 0.4.0 again.

It looks like there's two versions of uuid being used? You may need to use uuid 0.4.0 temporarily instead of 0.5.0 in your application

But 0.4.0
Ok
[dependencies.uuid]
version = "0.4.0"
features = ["serde"]

error[E0277]: the trait bound `uuid::Uuid: serde::Serialize` is not satisfied
  --> src/db/users.rs:20:10
   |
20 | #[derive(Serialize, Deserialize, Debug)]
   |          ^^^^^^^^^ the trait `serde::Serialize` is not implemented for `uuid::Uuid`
   |
   = note: required by `serde::ser::SerializeStruct::serialize_field`

error[E0277]: the trait bound `uuid::Uuid: serde::Deserialize<'_>` is not satisfied
  --> src/db/users.rs:20:21
   |
20 | #[derive(Serialize, Deserialize, Debug)]
   |                     ^^^^^^^^^^^ the trait `serde::Deserialize<'_>` is not implemented for `uuid::Uuid`
   |
   = note: required by `serde::de::SeqAccess::next_element`

wonderful! And what next?

Is that because two versions of serde are in use? Maybe 1.0 and 0.9?

I think yes
├── bincode v0.8.0
│   ├── byteorder v1.0.0
│   ├── num-traits v0.1.37
│   └── serde v1.0.2
├── cdrs v1.0.0-beta.9
│   ├── byteorder v0.5.3
│   ├── log v0.3.7
│   ├── lz4-compress v0.1.1
│   │   ├── byteorder v0.5.3 (*)
│   │   └── quick-error v1.2.0
│   ├── r2d2 v0.7.2
│   │   ├── antidote v1.0.0
│   │   ├── log v0.3.7 (*)
│   │   └── scheduled-thread-pool v0.1.0
│   │       └── antidote v1.0.0 (*)
│   ├── rand v0.3.15
│   │   └── libc v0.2.22
│   ├── snap v0.1.2
│   │   ├── byteorder v0.5.3 (*)
│   │   └── lazy_static v0.2.8
│   ├── time v0.1.37
│   │   └── libc v0.2.22 (*)
│   └── uuid v0.4.0
│       └── serde v0.9.15

[dependencies]
serde="1.0.2"
serde_derive="*"
bincode="*"
redis = "*"
cdrs = "1.0.0-beta.9"

[dependencies.uuid]
version = "0.4.0"
features = ["serde"]

[dependencies.postgres]
version = "*"
features = ["with-uuid"]

But I want use newest of packages.
repo:https://github.com/TrionProg/server_master some wast exists.

How to change version of dependence in multiple crates?
Seriously I need use 5 databases and each crate wants different versions of uuid or other common crates. Where is eternal race of versions and I am sure that authors wont change version of their crate if version of dependence have been updated. Okey I can download sources, write something like xxx = { path = "../xxx" }, but this is not solution and how I can publish crates in this case?. Where should be tool how to align versions of crates, or rust should use not 2 versions of UUID but merge them.

@TrionProg you're running into a problem here where the versions are not matching up, and to get things to work you'll need them to match up. One of your dependencies is postgres, which currently uses uuid 0.4. You'll need to use uuid 0.4 in that case. The uuid 0.4 crate depends on serde 0.9, so you'll need to use serde 0.9 in that case.

It will not break if I will use newer version 99%. This is my own risk and necessity. But I need read uuid from postgres and write to cassandra/mongo etc. And what version I should use? 5 versions of uuid, serde etc? This versions will never matchup! And how I need convert uuid 0.4.0 to 0.5.0 and 0.5.2 ? And let's rememdeb the main question, this issue have been started, - It won't compile.
Select what is better?!

https://github.com/rust-lang-nursery/uuid/issues/87#issue-227534773
or
https://github.com/rust-lang-nursery/uuid/issues/87#issuecomment-300585778
If I will write 0.4.0 everywhere it also wont compile. Why I need limit myself if some 1 year old library want 0.1.0 ?
Good luck!

But seriously I think rust should implement methods for UUID of 0.4.0 for postgres(it want's 0.4.0) , and 0.5.0 for 'other library'(it need 0.5.0), but if I use 0.5.0, I can not access methods of 0.4.0, but postgres may give some implementations of it's traits for 0.5.0 - To read from it and 'other library' it's own traits to write to 'other library' . Currently it does not compile. I will write 3 examples tomorrow.

Hello. Ok. let's continue.
just 2 files:
main.src
#[macro_use]
extern crate serde_derive;
extern crate bincode;
extern crate serde;

extern crate uuid;
extern crate redis;
extern crate cdrs;
extern crate postgres;

pub use uuid::Uuid;
use redis::Commands;
use cdrs::query::QueryBuilder;
use cdrs::types::IntoRustByName;

#[derive(Serialize, Deserialize, Debug)]
pub struct Data{
    s:String,
    pub id:Uuid,
}

fn main() {
    let client = redis::Client::open("redis://<IP_ADDRESS>/").unwrap();
    let con = client.get_connection().unwrap();

    let bin_data:Option<Vec<u8>> = con.get("45545").unwrap();

    let data=match bin_data {
        Some( bin_data ) => {
            //we use bincode to get data from redis
            let d:Data=bincode::deserialize(&bin_data).unwrap();
            d
        },
        None => {
            Data{
                s:"nothing".to_string(),
                id:Uuid::parse_str("936DA01F9ABD4d9d80C702AF85C822A8").unwrap(),//and we can parse uuid as string or generate
            }
        },
    };

    //we use postgresql
    let tls_mode = postgres::TlsMode::None;
    let postgresql_connection = postgres::Connection::connect("postgresql://postgresql_user@localhost/users",tls_mode).unwrap();

    let insert_result=postgresql_connection.execute(
        "INSERT INTO users (id) VALUES ($1)",
        &[&data.id]
    ).unwrap();

    //We use cassandra
    let cassandra_address="<IP_ADDRESS>:9042";
    let cassandra_transport = cdrs::transport::TransportTcp::new(cassandra_address).unwrap();
    let cassandra_client = cdrs::client::CDRS::new(cassandra_transport, cdrs::authenticators::NoneAuthenticator);
    let mut cassandra_session = cassandra_client.start(cdrs::compression::Compression::None).unwrap();

    let cassandra_querry=QueryBuilder::new(format!("SELECT content from files WHERE id = {};",&data.id)).finalize();
}

and Cargo.toml
[package]
name = "vpe"
version = "0.1.0"
authors = ["trionprog<EMAIL_ADDRESS>
[dependencies]
serde="0.9.15" #not 1.0.4
serde_derive="0.9.15" #not 1.0.4. This is really difficult to investigate what version of serde it wants
bincode="0.7.0" #not 0.8.0. This is really difficult to investigate what version of serde it wants
redis = "0.8.0" #it does not use uuid
cdrs = "1.0.0-rc.1" #it wants uuid 0.4.0

[dependencies.uuid]
version = "0.4.0" #of course I want use 0.5.0, but you advice.
features = ["serde"]

[dependencies.postgres]
version ="0.14.1" #this works good. because it wants 0.4.0, but sometimes it does not works because Cargo.toml of postgres-shared has >=0.4
#On my Laptop it does not works =)
#error : the trait `postgres::types::ToSql` is not implemented for `uuid::Uuid`

#try this
#path = "../rust-postgres/postgres" #rust-postgres/postgres-shared/ uses 0.5.0 for example. And it wont compile.
#I should use old verion of postgres because cdrs wants 0.4.0? I can not use new protocols, fixes of bugs etc because cdrs wants 0.4.0?
#Do you understand what you say?! Nothing personal, but seriously this is the absurd. This problem MUST be fixed. Because after 3 years
#cargo will be trash of conflicting versions of crates. I hope you understand me.
#error : the trait `postgres::types::ToSql` is not implemented for `uuid::Uuid`
#because it implements 0.5.0, not 0.4.0. see file https://github.com/sfackler/rust-postgres/blob/master/postgres-shared/src/types/uuid.rs
features = ["with-uuid"] #implement postgres::types::ToSql for uuid::Uuid

I think, rust should works this way:
C is common data type(uuid). It has no difference in memory structure
A is crate what wants C 0.4.0. A has method to read C from A
B is crate what wants C 0.5.0. B has method to write C to B
main.rs is code of user

If A has code that uses C 0.4.0, it will execute code of impls for C 0.4.0.
But A can implement traits for C 0.5.0 to use C 0.5.0 in main.rs and to send to B(read C from A and send C to B)
If B has code that uses C 0.5.0, it will execute code of impls for C 0.5.0.
But B can implement traits for C 0.4.0 to allow A use UUID from B(read C from A and send C to B)
Main.rs manipulate with version of C, what Cargo.toml use. It may be 0.5.0 or more, but then A implements for C 0.5.0 and B implements for C 0.5.0, that is why user can read C from A and write C to B.

Curently A implements traits for C 0.4.0 and B for C 0.5.0, but C from main.rs can not be 0.4.0 and 0.5.0 at the same time, but it must be readed from A and writen to B. This is the problem.
repo:
https://github.com/TrionProg/vpe

@TrionProg I think the problem here is that everything just needs to agree on versions of uuid, it's just not possible to have some on 0.4 and some on 0.5 when types are shared across crates. The repo you linked builds, though, is there still a problem with it?

I think the problem here is that everything just needs to agree on versions of uuid, it's just not possible to have some on 0.4 and some on 0.5 when types are shared across crates.
And it must be fixed in the future =)

The repo you linked builds, though, is there still a problem with it?
read Cargo.toml and above(this repo is copy of code above):
#try this
#path = "../rust-postgres/postgres"
Then it wont build because postgres wants 0.5.0. Here is some text for you =)

@TrionProg so to be clear, I think very little of this has to do with the uuid crate itself, it's basically entirely about crate graph resolution in Cargo. Along those lines you may be interested in https://github.com/rust-lang/rfcs/pull/1977.
I also found that this diff got your project compiling: https://gist.github.com/alexcrichton/9b068da8426cd1b37008003548187c63

Yes. UUID is just example of common problematic crate.
Wow. I can not belive that It can works =) Very strange. What have you edited in Cargo.toml or you edited Cargo.lock directly? I see, where are some changes around serde, but I do not know how serde works, so I can not understand.
Hm I think, some impl may be marked by keyword extern, and then they will implement traites to all versions of C in the project, which has same memory structure. But memory structure may be changed, then we can not implement code of old version to new, then user must have way how to import both versions like use postgres::postgres_shared::UUID as OldUUID; and convert by himself.
do not forget that postgres has .toml like https://github.com/sfackler/rust-postgres/blob/master/Cargo.toml.
I think, you've understood me and you(rustc/cargo developers) will fix this in the future.

I just updated the Cargo.toml and ran cargo update. Cargo's graph resolution is nondeterministic so we may have gotten two different versions (both valid, just different lock files). I believe this error is primarily related to https://github.com/rust-lang/rfcs/pull/1977, so I'm going to close in favor of that RFC


4.22.0内置DNS解析速度巨慢，无论结果是好是坏

你正在使用哪个版本的 V2Ray？
4.22.0

你看到的不正常的现象是什么？
内置DNS服务器解析速度巨慢，无论结果是好是坏

你期待看到的正确表现是怎样的？
DNS解析完秒回

请附上你的配置

客户端配置:
{
	"inbounds": [
		{
			"tag": "dns-in",
			"protocol": "dokodemo-door",
			"port": 8053,
			"settings": {
				"address": "<IP_ADDRESS>",
				"port": 53,
				"network": "udp,tcp"
			}
		},
		{
			"tag": "dns-in2",
			"protocol": "dokodemo-door",
			"port": 8054,
			"settings": {
				"address": "<IP_ADDRESS>",
				"port": 53,
				"network": "udp,tcp"
			}
		}
	],
	"outbounds": [
		{
			"tag": "direct",
			"protocol": "freedom"
		},
		{
			"tag": "dns-fwd",
			"protocol": "dns"
		}
	],
	"dns": {
		"servers": [
			"<IP_ADDRESS>",
			"<IP_ADDRESS>"
		],
		"tag": "dns-direct"
	},
	"routing": {
		"rules": [
			{
				"type": "field",
				"inboundTag": [
					"dns-in"
				],
				"outboundTag": "dns-fwd"
			}
		]
	}
}

相同的配置，不能复现你的场景

可以打开DEBUG模式看看日志
"log": {
        "loglevel": "debug"
}

相同的配置，不能复现你的场景

可以打开DEBUG模式看看日志
"log": {
        "loglevel": "debug"
}

下面是执行了一次nslookup输出的日志：
2020/01/01 13:05:13 [Debug] [67397894] v2ray.com/core/proxy/dokodemo: processing connection from: <IP_ADDRESS>:60931
2020/01/01 13:05:13 [Info] [67397894] v2ray.com/core/app/dispatcher: taking detour [dns-fwd] for [udp:<IP_ADDRESS>:53]
2020/01/01 13:05:13 [Info] [67397894] v2ray.com/core/proxy/dns: handling DNS traffic to udp:<IP_ADDRESS>:53
2020/01/01 13:05:13 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 querying DNS for: www.baidu.com.
2020/01/01 13:05:13 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 querying DNS for: www.baidu.com.
2020/01/01 13:05:13 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:<IP_ADDRESS>:53
2020/01/01 13:05:13 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/01/01 13:05:13 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:<IP_ADDRESS>:53
2020/01/01 13:05:13 [Info] v2ray.com/core/app/dispatcher: default route for udp:<IP_ADDRESS>:53
2020/01/01 13:05:13 [Info] v2ray.com/core/proxy/freedom: opening connection to udp:<IP_ADDRESS>:53
2020/01/01 13:05:13 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: www.baidu.com. TypeAAAA -> [] 21.9408ms
2020/01/01 13:05:13 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 updating IP records for domain:www.baidu.com.
2020/01/01 13:05:13 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: www.baidu.com. TypeA -> [<IP_ADDRESS> <IP_ADDRESS>] 21.9408ms
2020/01/01 13:05:13 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 updating IP records for domain:www.baidu.com.
2020/01/01 13:05:16 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 querying DNS for: www.baidu.com.
2020/01/01 13:05:16 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:<IP_ADDRESS>:53
2020/01/01 13:05:16 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: www.baidu.com. TypeAAAA -> [] 22.9393ms
2020/01/01 13:05:16 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 updating IP records for domain:www.baidu.com.
2020/01/01 13:05:17 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain www.baidu.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/01/01 13:05:17 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 querying DNS for: www.baidu.com.
2020/01/01 13:05:17 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:<IP_ADDRESS>:53
2020/01/01 13:05:17 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/01/01 13:05:17 [Info] v2ray.com/core/app/dispatcher: default route for udp:<IP_ADDRESS>:53
2020/01/01 13:05:17 [Info] v2ray.com/core/proxy/freedom: opening connection to udp:<IP_ADDRESS>:53
2020/01/01 13:05:17 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: www.baidu.com. TypeAAAA -> [] 16.9546ms
2020/01/01 13:05:17 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 updating IP records for domain:www.baidu.com.
2020/01/01 13:05:20 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain www.baidu.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/01/01 13:05:20 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 querying DNS for: www.baidu.com.
2020/01/01 13:05:20 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:<IP_ADDRESS>:53
2020/01/01 13:05:20 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: www.baidu.com. TypeAAAA -> [] 15.9572ms
2020/01/01 13:05:20 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 updating IP records for domain:www.baidu.com.
2020/01/01 13:05:21 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain www.baidu.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/01/01 13:05:21 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/01/01 13:05:21 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2020/01/01 13:05:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain www.baidu.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/01/01 13:05:25 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/01/01 13:05:25 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe

发现问题了，如果一个域名AAAA记录为空，那么会查询4次AAAA记录导致解析巨慢。
如果一个域名A记录，AAAA记录都有，那么会瞬间返回。
nslookup www.qq.com <IP_ADDRESS>#8053
2020/01/01 05:17:18 [Debug] [1109122690] v2ray.com/core/proxy/dokodemo: processing connection from: <IP_ADDRESS>:60217
2020/01/01 05:17:18 [Info] [1109122690] v2ray.com/core/app/dispatcher: taking detour [dns-fwd] for [udp:<IP_ADDRESS>:53]
2020/01/01 05:17:18 [Info] [1109122690] v2ray.com/core/proxy/dns: handling DNS traffic to udp:<IP_ADDRESS>:53
2020/01/01 05:17:18 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 querying DNS for: www.qq.com.
2020/01/01 05:17:18 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:<IP_ADDRESS>:53
2020/01/01 05:17:18 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/01/01 05:17:18 [Info] v2ray.com/core/app/dispatcher: default route for udp:<IP_ADDRESS>:53
2020/01/01 05:17:18 [Info] v2ray.com/core/proxy/freedom: opening connection to udp:<IP_ADDRESS>:53
2020/01/01 05:17:18 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 querying DNS for: www.qq.com.
2020/01/01 05:17:18 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:<IP_ADDRESS>:53
2020/01/01 05:17:18 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: www.qq.com. TypeA -> [<IP_ADDRESS> <IP_ADDRESS>] 18.36848ms
2020/01/01 05:17:18 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 updating IP records for domain:www.qq.com.
2020/01/01 05:17:18 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: www.qq.com. TypeAAAA -> [[240e:e1:a900:10::15]] 18.52224ms
2020/01/01 05:17:18 [Debug] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 updating IP records for domain:www.qq.com.
2020/01/01 05:17:26 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/01/01 05:17:26 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe

试试这个看能解决吗
v2ray.exe.zip

试试这个看能解决吗
v2ray.exe.zip

这个解决了，不再解析超时了

好的，稍后会发一个新版本

可恶啊 你发现的那个问题ok了 我发现的那个问题依然老样子.
所以咱果然不是一个问题呢.


Sass preprocessor creates .css file with content-type text/html

Hi guys,
I've installed the sass-chokidar as explained in readme file. All scss files are compiled in to one App.css file and then I import it in the html file with
<link href="/src/App.css" rel="stylesheet" type="text/css">
The classes in the file is not beeing rendered in the browser and when I inspect it in the network inspector, I can se that it has a content-type of "text/html". Can anyone help me where to add a content-type to the App.css file?
Thanks
Kasper

@cubanpete could you post a link to the project, some piece of code that would recreate the error, or some screenshots of the configuration and errors

@cubanpete content type is configured in web server mime types. For example in nginx https://www.nginx.com/resources/wiki/start/topics/examples/full/#mime-types

@cubanpete Try importing from index.jsx (as it described in docs) instead of adding it into index.html. It will also work with hot reloading of css this way.

The solution here is what @JLarky advises; please import this in JavaScript (index.js) instead of HTML.


Less I/O

description

[x] removing hard dependencies on IO, replaced with MonadIO m => m,
and also added bracketObserveX which does not depend on MonadCatch m
this was necessary to make benchmarking in cardano-ledger work.

checklist

[x] compiles (cabal new-clean; cabal new-build)
[x] tests run successfully (cabal new-test)
[ ] documentation added and created (cd docs; nix-shell --run make)
[x] link to an issue
[ ] link to an epic
[x] add estimate points
[x] add milestone (the same as the linked issue)

bors r+

bors try

bors r+

bors r+

bors r+

bors r+

bors r-


BCR Launch: Ensure rules_nodejs/rules_js works with BCR

I think we are tracking this in https://github.com/aspect-build/rules_js/issues/63


BC Theme applied consistently

Splash Screen / Loading Icon
Home Screen

take out bifold logo from home screen
notifications

Contacts screen
Scan Screen
Credentials List Screen

Lower Priority

Settings Screen

The first step in this I think is going to be to go through the app and apply the Aries Style Guide that Kim created. We need to have more control over theme rather than just black, white, and green. The colours used in the base bifold need to be compatible with the colours in the BC Theme.


feat!: remove pydantic v1 shims

Home Assistant has migrated to pydantic 2 which
is the only reason we kept around v1 support
https://github.com/home-assistant/core/pull/131963

Summary by CodeRabbit

New Features

Introduced a new utility function assert_equal_dump for enhanced object comparison in tests.

Bug Fixes

Updated import statements for ValidationError to utilize the latest version from Pydantic, ensuring consistent error handling across tests.

Chores

Updated CI workflow to focus on Pydantic version 2 and refined permissions for release jobs.
Added new dependency pydantic-extra-types to project configuration.
Enhanced initialization of optional attributes across various classes to default to None.
Updated various import statements to reflect changes in the Pydantic library structure.

Private attribute values; models with different values of private attributes are no longer equal.

Will use the profiler lru cache service to check the cache and change it if it’s needed.

2024-12-11 02:30:55.938 CRITICAL (SyncWorker_1) [homeassistant.components.profiler] Cache stats for lru_cache <function extract_type_shape at 0x7f39aa902e80> at /usr/local/lib/python3.13/site-packages/uiprotect/data/types.py: CacheInfo(hits=1175914, misses=352191, maxsize=128, currsize=128)
LRU is too small and we should use the type

Changed to the type
hit rate is great now
2024-12-11 02:35:31.667 CRITICAL (SyncWorker_10) [homeassistant.components.profiler] Cache stats for lru_cache <function extract_type_shape at 0x7f83afbc36a0> at /usr/local/lib/python3.13/site-packages/uiprotect/data/types.py: CacheInfo(hits=31304, misses=159, maxsize=512, currsize=159)


conf: disable local latch by default

Signed-off-by: Shuaipeng Yu<EMAIL_ADDRESS>

The default value in roles/tidb/vars/default.yml is true.

PTAL @liubo0127


Code Review Standards for External Contributors

This PR proposes a set of code review standards to be followed when external contributors submit pull requests to FuelLabs repositories. The aim of this PR is to provide a reference point for external contributors to follow.
Currently, I have the maximum line limit set at 500, and that 2 internal contributors need to approve the PR. Happy to workshop these numbers.

Yeah good point that's definitely something worth mentioning in this document. I'll add that in now. Thanks!

I have no objections to what's here -- like it so far. Will give it some time to get some more eyes on it.

No objections on my side, looks good so far.

I'm liking this so far! No objections


Update weaver-cats to 0.7.8

Updates com.disneystreaming:weaver-cats from 0.7.7 to 0.7.8.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.disneystreaming", artifactId = "weaver-cats" } ]

labels: test-library-update, early-semver-minor, semver-spec-patch

Superseded by #302.


Provide automated tests

Autotesting is the key in open-sourced project, people can not worry about if their pull request will break the app or not. They will already know the answer.

In first time I recommend this simple way: react-testing-library

Well, I can provide some help, but before issue should be split in test types: ui, api, etc. Also, we need determ where test files should be located: near test subject or tests should have their own directrory

Contact me via Telegram if you want to discuss issue.

Well, I can provide some help, but before issue should be split in test types: ui, api, etc.

There should be only one test category - the React code. We don't need to test API because it is external and UI is tested on multiple devices, so I always know if the layout is wrong before publishing a version.

Also, we need determ where test files should be located: near test subject or tests should have their own directrory

I prefer having a separate tests/ folder and have the same structure, as files in the main src/ folder.
I want to test some obvious issues, like props to some components (this issue could've been covered by tests https://github.com/jarvis394/habra/issues/121). But, anyways, writing tests is always a tedious job and such small project doesn't even need them because I have Sentry collecting errors. Every day I just check logs and, if I have an error, I fix it.

So, looks like you don't need tests. Fine, I'll find another issue. Pretty impressed by the app and really wanna help and contribute

yup, thanks in advance!


[bug]: Regression in 2.3.0 on MPS -- Python crashing and new errors on smaller sizes

Is there an existing issue for this?

[X] I have searched the existing issues

OS
macOS
GPU
mps
VRAM
64GB
What happened?
I have a new M2 Max (38 core) MacBook Pro running MacOS 13.2. In Invoke 2.2.5, there is a known crashing issue for image generations at 1024x1024 on Apple Silicon systems ("total bytes of NDArray > 2**32"), but otherwise I was able to generate at up to 1536x1536 (I haven't tested larger than this). Invoke 2.3.0 has a significant regression, though, and will not generate anything larger than 704x704 with SD 1.5 or 768x768 with SD-2.1-768. I tested in 2.3.0-rc7, but verified that the final release shows the same behavior.
Using the SD 1.5 model, generations from 512x512 to 704x704 finish correctly and perhaps slightly faster than in Invoke 2.2.5. However, with 2.3.0 the generation sizes 768x768 and 832x832 now cause Python to crash with the NDArray error written into the Terminal:
AppleInternal/Library/BuildRoots/c651a45f-806e-11ed-a221-7ef33c48bc85/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShaders/MPSCore/Types/MPSNDArray.mm:724: failed assertion `[MPSNDArray initWithDevice:descriptor:] Error: total bytes of NDArray > 2**32'
Between 832x832 and 1216x1216, Python instead crashes with a different error written to Terminal. I have not seen anyone report this error before (and note that it replaces the known error previously reported at 1024x1024):
AppleInternal/Library/BuildRoots/c651a45f-806e-11ed-a221-7ef33c48bc85/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShaders/MPSCore/Types/MPSNDArray.mm:705: failed assertion `[MPSNDArray initWithDevice:descriptor:] Error: product of dimension sizes > 2**31'
Further, at 1280x1280 and above (all the way to 2048x2048), Python stops crashing and instead there is a nonfatal error printed to Terminal with no generation. It consists of a long traceback ending in:
File "/Applications/Stable Diffusion/invokeai/.venv/lib/python3.10/site-packages/diffusers/models/cross_attention.py", line 189, in get_attention_scores
torch.empty(query.shape[0], query.shape[1], key.shape[1], dtype=query.dtype, device=query.device),
RuntimeError: Invalid buffer size: 39.06 GB
The reported buffer size depends on the requested image resolution, ranging from the above 39.06 GB at 1280x1280 up to 256.00GB at 2048x2048.
Using the SD 2.1-768 model, the behavior is a little different. This model outputs correctly up to 768x768, but produces the NDArray error from 832x832 to 960x960 and the dimension sizes error from 1024x1024 to 1408x1408. At 1472x1472 and above I get the nonfatal buffer size error, with listed buffer sizes ranging from 42.70 GB to 160.00 GB.
Please help to restore the generation functionality on MPS. Thanks!
Screenshots
No response
Additional context
No response
Contact Details
No response

I also reported this as #2444
as workaround don't use diffuser models for now

Thanks. I saw that bug report, but you didn’t report the product of dimension sizes crash or the buffer size error.On Feb 11, 2023, at 11:15 AM, Ivano Coltellacci @.***> wrote:
I also reported this as #2444
as workaround don't use diffuser models for now
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

@Adreitz can you confirm also this issue ? #2603

Thanks, I’ll check later today when I’m at home.On Feb 11, 2023, at 11:35 AM, Ivano Coltellacci @.***> wrote:
@Adreitz can you confirm also this issue ? #2603
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

The issue is still being experienced with the latest release. see #2444

Yes, I'm still experiencing this issue.

Update: v. 2.3.2-post1 exhibits exactly the same behavior with the SD1.5 model as I described above. I haven't checked SD2.1, but I expect it to also be the same as with 2.3.0.

@i3oc9i I just updated to the MacOS 13.3 public beta (v.4). I am seeing NO MORE CRASHING, including at 1024x1024. However, I am seeing greatly increased memory use. It got a bit better once I updated to the new torch/torchaudio/torchvision releases, but I'm still getting 10.7GB used during a 512x512 generation and over 55GB used at 1024x1024. Can you confirm?

@Adreitz I will prefer to not upgrade to MacOS 13.3 public beta, because I use Mac for work too, and I have other software that may break. Anyway is quite a good news, I will confirm as soon as the official 13.3 will be available, probably next month.
Anyway I updated to the new torch/torchaudio/torchvision releases and that only not solve the issue.

@Adreitz I confirm issue is solved with official Ventura 13.3, see comment
https://github.com/invoke-ai/InvokeAI/issues/2444#issuecomment-1485891105

@i3oc9i Thanks for the response. Can you confirm increased memory use by Python, or is it just my computer? That has taken over the crashes as the reason that I cannot generate at larger image sizes.

@Adreitz Im not able to be precise about memory usage, because I did non monitor exactly before the update, the general feeling is not,  maybe there is some increase but I have 128G so I don't get any memory pressure

Closing as resolved with MacOS 13.3 update. May open a new issue regarding high memory use.


Different permission & other Bugfixes, DevEx Improvement, Adjusted Current Timezone logic

This issue with the mutiple executions of the scheduled task is here again @Swiizyy :/

Hm but only in dev?


[ERROR-166] Course id not found!

Hi @r0oth3x49 , i also encountered "Course id not found" issue. I tried the URL with /learn/v4/*. Can you please advise on what should I do?

hey @mariesheilag , First of all a bit confuse about date it 29-June-2019 here. are you here from paste :rofl:

which method you used to authenticate?

email/pass or cookies based?


Add "destroy()" to stream$Stream

I'm getting this error in my project.
Error:(124, 5) property destroy. Property not found in stream$Writable
Let me fix it.
https://nodejs.org/api/stream.html#stream_writable_destroy_error

mixed

Sure, I force pushed to mine. Sorry, I didn't understand the next one.

It also looks like the object itself (stream$Stream).

fixing

@mrkev Done. Glad if you check this again.


typing.Type and type handled differently in nested NamedTuple

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
I noticed when we updated to v2.9(.0 and.1) that a particular nested model we have in one of our codebases started causing an error of the form:
pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for _tuplegetter(0, 'Alias for field number 0'). Set `arbitrary_types_allowed=True` in the model_config to ignore this error or implement `__get_pydantic_core_schema__` on your type to fully support it.

The model itself has many attributes but I narrowed it down to an attribute which is a NamedTuple, itself having an attribute of type type, and with a little more fiddling uncovered something that is really strange.
We use from __future__ import annotations in the module this type is defined in, and just importing that appears to cause this error when instantiating the model. Two things (well, three) resolve the error:

don't import __future__ -> it works as before with the type annotation
still import __future__, but use typing.Type rather than type in the annotation
the third is to use arbitrary_types_allowed=True like the error says, but this wasn't required before

I honestly have no idea whether this is a pydantic issue or not, but it definitely only happens on 2.9.x
Example Code
from __future__ import annotations # see below

import typing

from pydantic import BaseModel

class MyTuple(typing.NamedTuple):
    # type:typing.Type # this works
    type:type # this doesn't, but does if you don't import __future__

class MyModel(BaseModel):
    # model_config = ConfigDict(arbitrary_types_allowed=True) # Adding this makes both work, but wasn't required before
    tuple: MyTuple

def test_types():
    MyModel(tuple=MyTuple(type=int))

Python, Pydantic & OS Version
pydantic version: 2.9.1
        pydantic-core version: 2.23.3
          pydantic-core build: profile=release pgo=false
                 install path: /Users/xxx/.venv/lib/python3.11/site-packages/pydantic
               python version: 3.11.9 (main, Apr  2 2024, 08:25:04) [Clang 15.0.0 (clang-15<IP_ADDRESS>)]
                     platform: macOS-14.6.1-arm64-arm-64bit
             related packages: typing_extensions-4.12.2
                       commit: unknown

You are hitting a limitation of the runtime type checking logic of Pydantic.
When analyzing the MyTuple class, Pydantic will try to evaluate forward annotations, such as type: 'type'.
To do so, we use the typing._eval_type function, by passing the forward annotation and the namespaces. Here is a canonical example:
MyType = int

class SomeClass:
    MyType = str

    field: 'MyType'

typing._eval_type(
    typing.ForwardRef(SomeClass.__annotations__['field']),
    globals(),  # module globals {"MyType": int, ...}
    vars(SomeClass),  # `SomeClass` locals  {"MyType": str}
)
#> str

In your case, the locals of MyTuple are a bit different: the NamedTuple class dynamically add some members. In particular, attribute getters are being added for each type. When calling typing._eval_type, the module globals will contain the builtin type, but vars(MyTuple) will take priority and will contain the attribute getter named 'type'.
This was unexpectedly working before 2.9 as we changed how namespaces are fetched.

In general, it is recommended to avoid having the same field names and types. As a workaround, you can import Type from typing.

Thanks @Viicos! THat's super interesting, I had a suspicion we might have had an accidentally working configuration before.
It's easy enough for me to work around. Should I close this issue, or is there any possible mitigation (even with a clearer error message, if possible) for this edge case?


text change of crop to save

🚨🚨🚨🚨🚨 THIS LIBRARY IS NOT MAINTAINED, PLEASE READ THIS 🚨🚨🚨🚨🚨 #838
To avoid your issues, please use the latest updated library: https://github.com/CanHub/Android-Image-Cropper
100% kotlin
All bugs fixes
active community


Determine whether collection properties should be settable on input models

Problem

Customers are hitting problems initializing collection read-only properties on input models.
.NET guidelines say not to make collection properties settable, and there is C# syntax for collection read-only properties, but customers aren’t finding this.
Should we let collection properties on input and round-trip models be get/set?

This issue tracks making a decision regarding what to do in DPG, whether to make collection properties settable or not on input and round-trip models.

We made the decision to keep collection properties read-only for now.  It's possible we will revisit this prior to DPG 2.0 GA, based on what we learn during that time.
The primary reason is that once we make collections settable, any type of collection can be assigned.  If we wanted to use special collection types, e.g. to track changes made to collections, we wouldn't be able to do this reliably.
We plan to work toward improving the customer experience in other ways in the interim, and evaluate whether these interventions mitigate the issue.


Modified redirect_uri comparison method in authorization flow, and others

modified redirect_uri comparison method in authorization flow
added parsing client credentials from request body in token flow
added renewing refresh token when refreshing access token
added removeByRefreshToken method for revoking token in refreshing flow
implemented test methods accordingly and fixed some typo

Hi Dawoon, the RFC (http://tools.ietf.org/html/rfc6749#page-10) indicate to the refresh_token flow, the new refresh_token is optional. Can you add a configuration attribute?

Hi Dawoon sorry,I add more, for redirect_uri the RFC defines that redirect_uri must no have fragment component, and must retain query parameters (specially the state parameter to do the security check by the client).
So, is good correcting the comparison redirect_uri, but we going to open other issues.
Can you add the checking for fragments on redirect_uri and open a new issue for retaining query parameters?

Hi Pablo, thanks for the comments! I was able to learn more about the OAuth 2.0 :)
I've added things you mentioned and tested with both test code and my hand.
However, it seems that the query parameters are retained correctly as it is now. I tested authorization flow with adding "state" parameter, and it was retained correctly through out the flow.

Hi
Thank you for your contribution guys, going to merge it as soon as i get to my laptop (in 1 day i hope)


Fixed 'credential' typo in name of detection & missing filter macro

Fixed a typo in the name & updated the Known False Positives.

Hi @drewchurch : Thanks for the PR. I created a duplicate PR https://github.com/splunk/security_content/pull/1196 since this current one is failing out CI. Minor Update in the filter macro.
Thanks again for submitting a fix


What is the default value for 'Mode' ?

If I don't specify 'Mode', what default value is used...All or Indexed? This doc should define the default. In particular, many built-in policies don't specify mode, so we really need to know.

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

ID: d956852a-d98e-c022-d6f2-c2910afe6e93
Version Independent ID: 8107b348-d2b4-214e-2b18-bf813f1fe1e8
Content: Azure Policy definition structure
Content Source: articles/azure-policy/policy-definition.md
Service: azure-policy
GitHub Login: @bandersmsft
Microsoft Alias: banders

@jtuliani We appreciate you bringing this to our attention. Your feedback has been shared with the content owner for further review.

@jtuliani we're looking this for you.
#in-process

If "mode" is null it is treated the same as if it was "mode"="indexed".  I will update the docs to reflect this.

@jtuliani The update that Chris made to the article is live. Hope that helps.
#please-close

@jtuliani Closing this thread as resolved. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Export User in index.js

The reason for this change is that in some cases during startup of an app, the asynchronous nature of the userManager's getUser function interferes with possible API requests depending on the user to be loaded. In order to synchronously load a user it is necessary to have access to the User in this library to use the synchronous User.fromStorageString(storageKey) function when using either local or session storage.
See this issue for details.

To follow up on this, the reason for the PR is to provide a way to use a synchronous loading mechanism for user data that might be present in local or session storage. Even when local or session storage is used, the promise returned by getUser always causes a delay between call and result. During startup of an app (no matter if using ReactJS / Redux or any other library or framework) this can lead to unexpected behavior.
In the example provided in the issue I've linked, the startup finishes and an API request gets dispatched which requires the user to be present. Only after the dispatch the promise of getUser is resolved. I understand that the reason for the asynchronous nature of getUser is to allow for additional storage mechanisms besides local and session storage, but I'd like to see a 'fallback' synchronous option.
My idea with exporting the User is to allow a User object to be created synchronously like this:
import { User } from 'oidc-client';

const user = User.fromStorageString(sessionStorage.get('myStorageKey'));

This is currently not possible because the user isn't exported.
My questions regarding this method are:

Is there another (synchronous) way to get a User object from either local or session storage?
Is there something happening in the background that links the User object to a userManager instance? Or does the userManager reliably check storage for this info so that no duplicate User objects are created?
Is there a way to reliably retrieve the storage key without having to hardcode it?

Thanks in advance!

I've not had time to really look at this, but my first reaction is that something's wrong with the API design if you have to do this sort of thing.

Sadly I don't have access to the code that causes the problem in the linked issue. My first reaction was the same. I would just like to offer a solution for my users that could solve a problem I don't know enough about :).
It is conceivable however that problems could be caused by this. For a little background:
My library consists of redux-middleware, which is conceptually equivalent to OWIN middleware. Instead of HTTP requests however, the redux pipeline handles UI or background actions. But it is entirely synchronous in nature. My middleware handles the user data and calls the userManager's getUser function to check on the user data. It triggers a login attempt if the user has been expired. Since the nature of getUser is asynchronous, this goes against the nature of the middleware and could cause the reported issue, meaning a second action relying on the user data is dispatched before getUser has been resolved.
Sadly I cannot change the nature of the middleware, this is why I wish for a synchronous option to retrieve the User object.

I've investigated further and was able to resolve the issue so this is no longer needed. Sorry for the inconvenience.

What was the solution?

The user who reported the issue sent me a fork reproducing it. In React / Redux, UI components can also dispatch actions through the redux pipeline when loaded and his component required the user to be present and was always loaded - no matter what. A simple check had to be made to not load that component when the user is not present or expired.
 A little learning experience for me :-)
Thanks for your time!


Added defer koan

few examples for defer operator

I like this idea. @zhikiri do you think you can get a few more contributors to advocate for your additional tests?

@cdarwin unfortunately I can't :( I'm a new guy in Go community

ok, no worries. I will put some more time and thought into this and get back to you. Thanks!

bump.

I dig it.  Thanks, @zhikiri !


Not possible to pass  credentials (username,pwd) with file based MQ-JNDI

Version of Gatling being used: 2.3.0
I do have a JMS scenario against a IBM MQ using a file based MQ-JNDI in conjunction with a bindingsfile containing all required infomation about my MQ objects (e. g. Hostname, Channel etc.)
From a security perspective, of course IBM does not allow to have values for username/password in the bindingsfile which is just a plain text file.
So when starting the scenario, the connection attempt is being desclined.
I'd expect the JNDI lookup to pass values for username/pwd while establishng the ConnectionFactory like so:
QueueConnectionFactory qcf = (QueueConnectionFactory) ctx.lookup("myQCF");
QueueConnection qc = qcf.createQueueConnection(userID, password);

This is my scenario:
import io.gatling.core.Predef._
import io.gatling.core.structure.ScenarioBuilder
import io.gatling.jms.Predef._
import io.gatling.jms.protocol.JmsProtocolBuilderBase.connectionFactoryName

import scala.concurrent.duration._

class GPRSForwarderTest extends Simulation {

  val JNDI_CONTEXT = "com.sun.jndi.fscontext.RefFSContextFactory"

  val DEFAULT_QCF_NAME = "GPRSF"

  val message254 = "00001100E033102C20EBB51CC1C036EFFFF00010002323802000200FE05001400000000FFFFFFFF01FFFFFFFFFFFFFFFFFFFFF10F37298C"

  val jmsConfig = connectionFactoryName(DEFAULT_QCF_NAME)
    .url("file:///Users/brandsheide/Documents")
    .credentials("mqm", "mqm")
    .contextFactory(JNDI_CONTEXT)
    .listenerCount(1)
    .usePersistentDeliveryMode

    println("filepath = " + jmsConfig)

  val scn = scenario("Load testing GPRS InboundQueue").repeat(1) {
    exec(jms("F&F testing").send
      .queue("COMPANY.GPRS_MESSAGES.QUEUE")
      .textMessage(message254)
    )
  }

Apparently the values being passed with .credentials("mqm","mqm")are being ingored.
As of now the only way to run load tests against IBM MQ is to deactivate authentication (?)

In Gatling 2.3, connecting to queues is anonymous by default. This feature is being dropped in Gatling 3 and connecting will always use provided credentials if present.

@slandelle thanks, when is Gatling 3.0 goint to be released? And If I'd like to fix this on my instance of v. 2.3 I'll just have to
anonymousConnect: Boolean = true to false instead?
Or, another way, set def disableAnonymousConnect = copy(anonymousConnect = false) to true - compilele - and invoke the scenario again? Thanks for  your support.

when is Gatling 3.0 going to be released?
Hopefully first RC in July.

disableAnonymousConnect

Connect is never anonymous in Gatling 3, and AFAIK, there's no reason to make this behavior configurable.


Return undefined instead of Dict.empty from Page.getInheritedPageProp for non-existent properties to prevent possible future bugs

This is something that I noticed while working on PR #8126, which is (more) fallout from PR #6065.
In general, it's actually not correct to return Dict.empty as the default value for non-existent properties. Please note that a prior PR, see https://github.com/mozilla/pdf.js/pull/5957#issuecomment-103112698, asked for that behaviour but I don't think that's right.
Obviously for properties that are (or should) be Dicts it makes sense, however certain properties can be e.g. Strings or Arrays instead. In the latter case, returning Dict.empty is just plain wrong, and it's quite fascinating that this hasn't caused any errors in practice. (The existing validation in the various getters has actually saved us here.)
Also, when looking at this code again, it seemed unnecessary to duplicate the MAX_LOOP_COUNT check since we could just return immediately instead.

/botio test

Looks good. Thank you for the fix!


Why i can't see any benefit of implementing Redis to my api?

Description
Redis is known for its speed, and popular applications like Instagram rely on Redis for optimal performance. However, when I integrated Redis into my API, I observed that it only marginally improved the response time. Initially, my regular API, which uses MongoDB, responded with an average of 302ms. After implementing Redis, the response time decreased to an average of 298ms.
Now, I'm seeking guidance on the proper implementation of Redis in my Node.js API. Could you please provide some advice on how to achieve optimal utilization of Redis within my API?
(async () => {
  await redisClient.connect();
})();

redisClient.on('connect', () => console.log('::> Redis Client Connected'));
redisClient.on('error', (err) => console.log('<:: Redis Client Error', err));

router.get('/posts', async (req, res) => {
  try {
    const numBuckets = 10;
    const cacheTTL = 60;
    const bucketIndex = Math.floor(Math.random() * numBuckets);
    const cacheKey = `posts:${bucketIndex}:${req.query.page || 1}`;
    const cachedData = await redisClient.json.get(cacheKey, '$');
    if (cachedData) {
      console.log('Data fetched from Redis cache');
      return res.json(cachedData);
    }
    const limit = 30
    const page = Number(req.query.page) || 1;
    const skip = (page - 1) * limit;
    const result = await User.aggregate([
      { $project: { _id: 0, username: 1, profileImg: 1, posts: 1 } },
      { $unwind: '$posts' },
      { $project: { postImage: '$posts.post', date: '$posts.date', username: 1, profileImg: 1 } },
      { $sort: { [bucketIndex % 2 === 0 ? 'date' : 'postImage']: bucketIndex % 2 === 0 ? -1 : 1 } },
      { $skip: skip },
      { $limit: limit },
    ]);
    await Promise.all([
      redisClient.json.set(cacheKey, '$', result),
      redisClient.expire(cacheKey, cacheTTL)
    ]);
    console.log('Data fetched from MongoDB and cached in Redis');
    res.json(result);
  } catch (err) {
    console.error(err);
    res.status(500).json({ message: 'Internal server error' });
  }
});

Node.js Version
v20
Redis Server Version
Redis Labs
Node Redis Version
4.6.7
Platform
MacOS
Logs
No response

One issue i see is, for every GET api call, you are generating a cacheKey based on random bucketIndex and hence i don't think your code reaches to this point at any time
if (cachedData) {
      console.log('Data fetched from Redis cache');
      return res.json(cachedData);
 }

In addition to @avinashkrishna613 valid point, your TTL value probably is too low for the number of requests that you get for each "bucket".


Update HelperConfigTest once zend-view refactor is complete

The HelperConfigTest test case is marked incomplete currently due to the fact that Zend\View\Navigation\PluginManager is not updated to the latest zend-servicemanager changes. Once it has been, we can address this test case.

I think the test should be refactored then for not depend of the external implementation.

The point of the test is to determine how it configures the view helper
manager; it's an integration test.
On Oct 29, 2015 2:25 PM, "Maks3w"<EMAIL_ADDRESS>wrote:

I think the test should be refactored then for not depend of the external
implementation.
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/zend-navigation/issues/6#issuecomment-152294032
.

This repository has been closed and moved to laminas/laminas-navigation; a new issue has been opened at https://github.com/laminas/laminas-navigation/issues/4.


Improve installation instructions

Hi Johannes @jo-mueller ,
there are some discussion on image.sc suggesting that the installation instructions for napari-stress should be improved. Manon Valet suggests this:
conda create -n napari-stress-open3d -c conda-forge -c open3d-admin python=3.9 open3d
conda activate napari-stress-open3d
conda install -c conda-forge napari
pip install napari-stress

If you take this proposal over, please thank her in the next release notes.
Thanks!
Best,
Robert

Hi @haesleinhuepf ,
thanks for creating this issue. I'm not sure whether Manon's solution actually solves the problem - the code she used to install napari-stress has correctly installed the plugin - with the exception of widgets that actually use pygeodesics. It's odd though, that the installation throws an error and at the same time installs napari-stress correctly.
But I agree, there should be a sort of FAQ section on the documentation page to collect this sort of things.

She installs open3d via conda; I think this makes a big difference compared to the current installation instructions.

Rachna confirmed that the solution described on image.sc fixed this so I'd close this issue.


1657389 Add descriptions for SEO (series of related PRs)

Add descriptions for SEO
For anyone that GitHub notifies, this is for 1657389.
You're welcome but not required, according to KhairunJ's guidance, to review these proposed meta descriptions. I'll leave this PR open for 48 hours and address any feedback. After that, we'll sign off for merge. Thanks!
Please keep in mind our 100-160 char length for descriptions.
Fixes #1657389

@BillWagner - We're not fixing other things for these SEO items, so I won't fix the table title suggestion. Our team has addressed all the new suggestions in the Azure repo. I don't know whether we'll be tasked to look at dotnet.
FYI - there's another writer working on this task with me named Jason. I don't know whether he's reached out to you yet.


[Suggestion] Mirror docker image on dockerhub (for IPv6 download support)

I just learned the hard way after setting up my vps for 20 minutes that ghcr.io still does not support ipv6. I have read people worked around this by also providing docker images via dockerhub as it supports IPv6.
I think it would be nice to have this so systems without ipv4 can still download the image.

Nice suggestion!
I'll add docker hub support.

Done ✅
Now image is available in docker hub: https://hub.docker.com/r/mliezun/caddy-snake
Also updated readme so that users are aware where they can get the image from. Both ghcr and docker hub.
Can you try it out and see if this resolves the problem that you were having?

Yes, with only ipv6 access docker pull does work with the image from docker hub. Thanks for the quick resolve!


Travel advice govspeak

It's easier to just look at this commit: https://github.com/alphagov/govuk-content-schemas/commit/bd238599c60a77e4f0bc9dd5b4b3ef8cab8c991d (the other just rebuilds the schemas)
This change is made more complicated by the fact
that the schema differs between backend and
frontend.
By the time the content reaches the front-end, the
‘text/html’ content type is inlined. Therefore, we
need to generate slightly different schemas to
cater for this.
https://trello.com/c/L6gBHNFN/471-make-travel-advice-publisher-send-both-govspeak-and-html-to-the-publishing-api

Looks good to me, I assume the build failure is known seeing as it's about travel-advice-publisher anyway :+1:

Yes, the build is dependent on the application PR merge.


Changing size?

I really like your plugin - thanks for the work. Also the ease animation would look great to be implemented.
I wondered how I can easily change the size of the counter without changing all 1000 css defaults.
Thanks in advance

Hi
I know its nearly a year old, but here is the manual solution (its really not '1000 css defaults'):
.flip-clock-wrapper ul {width: 40px;height: 78px;margin: 0 2px;}
.flip-clock-wrapper ul li {line-height: 78px;}
.flip-clock-wrapper ul li a div div.inn {border-radius: 3px;font-size: 50px;}
.flip-clock-wrapper ul li a div.down {border-bottom-left-radius: 3px; border-bottom-right-radius: 3px;}
.flip-clock-wrapper ul li a div.up:after {top: 38px;height: 2px;}
the '.flip-clock-wrapper ul' properties represent each digit's containing box.
the line-height of '.flip-clock-wrapper ul li' should match the height of '.flip-clock-wrapper ul'.
the actual number inside the box is represented by '.flip-clock-wrapper ul li a div div.inn' so I have adjusted the font size here.
ive reduced the border radius' of '.flip-clock-wrapper ul li a div div.inn' and '.flip-clock-wrapper ul li a div.down' for aesthetics.
'.flip-clock-wrapper ul li a div.up:after' represents the line between the top and bottom parts of the flip. Its 'top' property has to be the height of '.flip-clock-wrapper ul' divided by 2 minus its own height divided by 2 [(78/2) - (2/2) = 38].
hope this helps

@Jawaad Thanks for explaining this it helped :)

@Jawaad You are the best, thank you!
I even shrink it more and added a few more line to adjust the positions of the dots:
/* Adjust the position of the top's dot /
.flip-clock-dot.top {
top: 10px;
}
/ Adjust the position of the bottom's dot /
.flip-clock-dot.bottom {
bottom: 0;
top: 25px;
}
/ Adjust the size of both dots /
.flip-clock-dot{
width: 7px;
height: 7px;
}
/ Adjust the space between the wrappers */
.flip-clock-divider {
width: 17px;
height: 45px;
}

Thanks @Jawaad and @Hillelman! I put it together into a less source, that allows sizing by parameters:
http://jsfiddle.net/fd3600yv/

Thanks @j0hj0h ! I added it to my project, and it worked like a charm.

Glad to hear that @jeepnet

Thanks for this!!!

And another thank you for this.

Hi All,
Just to keep the discussion clean I am locking this. The project has moved past this solution already. And an even better solution will be available in v1.
Thanks for the support!


meant to be a public repo?

was surprised to see this as a public repo - not sure if it matters, but wanted to ask
i see this in the readme description:

Spoton internal Helm charts repository.

@asiegman @fcooper-spoton

Helm charts are by design public things. This is mostly an accident of language.  The chart isn't useful to anyone outside of SpotOn, not even a little bit.
Feel free to make a PR.


SD XL (pony) dreambooth on colab?

Hey Ben,
Love your work.    I'm using realDream_sdxlPony13.safetensors these days and I'd like to be able to fine tune it.  All the finetuning I've done so far is with sd1.5 files and your google colab dreambooth notebook won't work for that, right?  I tried working with your paperspace notebook, but I just keep getting stuck because I don't use paperspace.  I'd really rather stick with google colab just because I am so familiar with the in's and out's of it.    This did not go well!  Here is my proposition.  Would you be willing to take a commission to create a google colab dreambooth notebook that can handle the sdxl pony checkpoint?  I want to fine tune (not LoRA).  I would pay $250 up front if you (a) would write this and then (b) do a little tech support if I can't get it to work easily.  Interested?

you can write me at<EMAIL_ADDRESS>if you would prefer to discuss privately


Fixes #1023 - Load exceptions in user resolvers are not reported

Put try...catch around require.resolve() (not require())

Coverage increased (+0.02%) to 96.248% when pulling 8778d7c38fa17d005a6269980483f9e1430e716f on patrick-steele-idem:issue-1023 into 91cfd6d873953a98f9e75680bf19ee3e25f974c4 on benmosher:master.


Game crashes on startup on Linux

Geode Issue

[X] I confirm that this crash is NOT related to a mod but directly to Geode Loader itself.

Platform
Windows
Geode Version
v3.8.1
Mods Installed
== Installed Mods ==
x | [v1.4.12] alphalaneous.happy_textures
x | [v1.1.12] b1rtek.gddlintegration
x | [v1.0.7] cdc.level_thumbnails
x | [v1.2.1] cvolton.misc_bugfixes
x | [v0.3.2] flafy.autonong
x | [v2.11.0] fleym.nongd
x | [v1.9.0] geode.custom-keybinds
x | [v3.8.1] geode.loader
x | [v1.14.1] geode.node-ids
x | [v1.6.1] geode.texture-loader
x | [v1.0.0-beta.44] minemaker0430.gddp_integration
x | [v1.2.2] syzzi.click_between_frames
x | [v1.1.0] thesillydoggo.comment_emojis
x | [v1.6.10] thesillydoggo.qolmod
x | [v1.3.0] ziegenhainy.xxlify
Steps to Reproduce

Open the game using Wine version 9.18.
During the "verifying loader resources" phase, the game will crash.

Crash Report
https://pastebin.com/4wvC7Tik
Additional Information
The game worked fine yesterday, opened it today and now it crashes on the "verifying loader resources" phase. I removed all of the mods and tried opening it, but the exact same thing happened. Tried deleting my save files to see if that was the issue, but that also doesnt fix the problem. Uninstalled and installed geode again, same issue (even though the vanilla game does work without geode). Tried deleting the wineprefix, same thing.

alright so i tried running it using Proton through Lutris instead of wine and then it worked fine. so i guess it is an issue with wine itself or with the Arch Linux version of wine. I still think this should be investigated since the vanilla game works fine with wine, so its a geode issue.

this should've been fixed a few commits ago, can you try the nightly build? see if it works fine there

yep. works fine using the nightly build and wine 9.16. closing this now