Error in partition list refresh

DBeaver 7.1.3

In SQL Editor
CREATE TABLE table_sec (
id int4 NOT NULL,
expa int4 NOT NULL DEFAULT 0
) PARTITION BY list (expa);

Open table table_sec  parameters, empty partition list

In SQL Editor. Create partition.
CREATE TABLE parti_1 PARTITION OF table_sec FOR VALUES IN (1);

In table table_sec  parameters window i click on refresh button

partition list still empty

Only after i close table table_sec  parameters window and click on refresh in object tree and open table table_sec  parameters window again, i had seen my partition in a partition list

thanks for the bug report

Hello, @detkliff,
Unfortunately, we can't really do much here - in PostgreSQL table partitions are tables too, so in order to see changes we need to refresh parent schema itself to reflect the changes made in it, but this may decrease performance drastically (because no one wants to refresh full schema when you only wanted to refresh a single table). You still can refresh schema manually.

Hello, @detkliff,
Unfortunately, we can't really do much here - in PostgreSQL table partitions are tables too, so in order to see changes we need to refresh parent schema itself to reflect the changes made in it, but this may decrease performance drastically (because no one wants to refresh full schema when you only wanted to refresh a single table). You still can refresh schema manually.

this could be done with a special setting, for example, I am ready to put up with the loss of performance

This bug was previously reported in June 2018 (https://github.com/dbeaver/dbeaver/issues/2035#issuecomment-397777792). I honestly can't believe it has been open for the past 6 years with the excuse that "actually refreshing the partition list will be too slow".

What does the "Refresh" button in this screen even do, if it doesn't refresh the table names and list, and the stats have their own button ("Read row count and other expensive properties").

I think the most correct behavior when clicking the Refresh menu item would be to refresh the contents of the selected node (without children). It would also be useful to have an additional menu item like "Refresh with children" to refresh the contents of the selected node and all its children. The first option works quickly, the second one obviously takes longer. It's up to the user to decide.


Unknown option '--devserverPort=9001'

A clear and concise description of what the bug is.
How to reproduce the bug

I start the frontend according to this post.
I passed two parameters:

npm run dev-server -- --devserverPort=9001 --supersetUrl=http://<IP_ADDRESS>:8088

Terminal output error:

><EMAIL_ADDRESS>dev-server
> cross-env NODE_ENV=development BABEL_ENV=development node --max_old_space_size=4096 ./node_modules/webpack-dev-server/bin/webpack-dev-server.js --mode=development "--devserverPort=9001" "--supersetUrl=http://<IP_ADDRESS>:8088"

[webpack-cli] Error: Unknown option '--devserverPort=9001'
[webpack-cli] Run 'webpack --help' to see available commands and options

Expected results
The frontend starts success and the passed parameters take effect.
Actual results
[webpack-cli] Error: Unknown option '--devserverPort=9001'

Environment

superset version: 1.5.1
python version: miniconda  python 3.8.12
node.js version: v16.15.1

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

@wang-valdanito-chao Hi. Some of the content in this article is out of date, so I recommend referring to the official superset documentation. https://github.com/apache/superset/blob/master/CONTRIBUTING.md#webpack-dev-server
# Run the dev server on a non-default port
npm run dev-server -- --port=9001

Closing this since it's likely obsolete after following the provided docs :)


local-gadget: Add trace sni gadget

#893

https://github.com/inspektor-gadget/inspektor-gadget/pull/1103 was merged. @mqasimsarfraz would you mind updating this one please?

@mauriciovasquezbernal thanks for the review. Do you have want to have final look? I updated the PR to address the nits. I will merge this once CI is green.

It's good. It can be merged once CI is green.


Is diff_graph() an implementation of the U-matrix?

Hi Federico,
I looked into the code and the only difference between the U-matrix and your implementation of diff_graph() seems to be that the former takes an average of the distances with its neighbours while diff_graph() just takes the sum. Is diff_graph() an implementation of the U-matrix?

Hello Rohit,
apologies for the late reply.
I believe the original definition of U-matrix requires to add extra "padding" nodes between each pair of nodes colored according to the distance of the neighbors.
This definition is used in SOM Toolbox (a Matlab package for SOM).

Compute and return the unified distance matrix of a SOM.
For example a case of 5x1 -sized map:
m(1) m(2) m(3) m(4) m(5)
where m(i) denotes one map unit. The u-matrix is a 9x1 vector:
u(1) u(1,2) u(2) u(2,3) u(3) u(3,4) u(4) u(4,5) u(5)
where u(i,j) is the distance between map units m(i) and m(j) and u(k) is the mean (or minimum, maximum or median) of the surrounding values, e.g. u(3) = (u(2,3) + u(3,4))/2.

The implementation of diff_graph() is more similar to an alternative, simplified representation of the U-matrix that can be found in some works (see this paper).

The U-Matrix is constructed on top of the map.
Let n be a neuron on the map, NN(n) be the set of immediate neighbors on the map, w(n) the weight vector associated with neuron n, then
U-height(n) = SUM( for m ∈ NN(n)) d(w(n)-w(m)), where d(x,y) is the distance used in the SOM algorithm to construct  the  map.
The  U-Matrix  is  a  display  of  the  U-heights  on  top  of  the  grid  positions  of  the
neurons on the map.

The actual difference (except for a scaling factor which is fixed and dependent on the geometry of the map) boils down to the interpolating nodes. I personally prefer the second implementation because the resulting map is more intuitive for me, it's easier to read and compare with the other maps produced.
There seems to be a scarcity of information on this argument online, but there are a few discussions (like this one) on stack overflow regarding this if you are interested in more details.

Hello Rohit,
if there are no further question I'm going to close this issue.


[ATIP] Add CordovaLauncher/XWalkLauncher support

-add CordovaLauncher/XWalkLauncher support
-add other app launcher support with pkg and activity name
-add TIZEN_USER support for local debug in set_env.sh
UT Result: BDD suites run well

@cicili @yugang please help review. :smile:

LGTM


update entity-search-webapp to 2.7.0

The version of the webapp needs to be updated. see release notes: https://github.com/Senzing/entity-search-web-app/releases/tag/2.7.0

SenzingGo pulls the latest images from a list we publish on Git, if this list isn't up to date yet it won't pull latest version. It's also possible to override the version pulled if you require a specific version/tag. The current list and tags can be seen with SenzingGo.py -il (--imagesList).


Update request: pcloud 1.14.5 → 1.14.6

Package name: pcloud
Latest released version: 1.14.6

Current version on the unstable channel: 1.14.5
Current version on the stable/release channel: 1.14.5

[ ] Checked the nixpkgs pull requests

Notify maintainers
@Patryk27

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

It seems that I was already updated to the latest version (https://github.com/NixOS/nixpkgs/commit/27e96ecbef451500f3b5710c817c2906ddd126d2)

Yeah, I've already updated pcloud a couple of days ago, so it's both in master and nixos-unstable now - if you're using Flakes, try running nix flake update etc. 🙂
I'm closing this issue, but feel free to re-open it if you find any problems with the upgrade.


[Marker.io] buttons are displayed again below the cards when the user scrolls down on the page

Steps to reproduce:

scroll down on the page
notice the buttons below the card tiles again

Actual result:buttons are shown again below the cards
Expected result: they should not see it
https://go.screenpal.com/watch/cZXh11nckE5

Reported by: vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://na13-prezzee.webflow.io/en-us/use-cases
Issue details: Open in Marker.io
Device typedesktopBrowserChrome <IP_ADDRESS>Screen Size1366 x 768OSWindows 10 (10.0.0)Viewport Size1517 x 712Pixel<EMAIL_ADDRESS>
🤖 Marker.io bot - This issue was marked as ✅ Resolved in Marker.io


Style action label on SnackBar

Use case
The designers on my team want a consistent font family for all text within the app.
There is a need to display a SnackBar with an action. Currently, the action label cannot be styled.
Proposal
I should be able to pass a TextStyle to the SnackBarAction to specify what I want that text to look like.

Or better yet, pass a Text widget in as the label so that you are free to style the label and possibly the textScaleFactor

pls reopen it


We should rename all occurrences of the term "Surface" in non-vaapi code

This will be very confusing when/if other backends (like v4l2 backends) come along.
For consistency, we should rename this at the decoder level.
My suggestion is to use the term resource, meaning some backend-specific buffer or data structure consumed during decode, like VASurface, V4L2Request, V4L2Buffer, VkMemory and etc.

That's probably a good idea, agreed. We should probably also define the terminology we use in the online doc.
"Resource" always sounds to me like we are mining ore or something though. How about just "Frame"? A frame is made of memory buffers, has planes, and a given format.

Frame is fine then

Fixed by 06ac7b3c9e5fe3bd06a4f42a8a9ea31a0b808019.


Voice Feedback Alerts and Information

Hi, I want to ask about a suggestion to make Soulissapp more "human".
Will be good to have some voice feedback options using google's TTS to notice things like:
-Tell temperature, humidity or other sensors when we ask on Voice command.
-Tell the state of a T1x when a (on/off/toggle) voice command is sended, something like (light on the bedroom is on)
-Alert on Alarm or Door open command.
Regards

This will be useful to make T5x based rules with Automate.
Regards

+1


chore!: vue considered peerDependency

Release-As: 0.2.1

I'm hoping release-please will publish this version. I don't want to pollute a bunch of extra version numbers try to diagnose :/

Hmm, no release PR this time

Hmm, no release PR this time

https://github.com/cdmoro/bootstrap-vue-3/pull/522 Believe this is why. I think it only had to do with the fact that it was an empty commit causing the action to not run. Are you able to do a manual release to npm?

Thanks!
Would prefer to wait for the next change which triggers release bot, so we can fully test everything.

Thanks!
Would prefer to wait for the next change which triggers release bot, so we can fully test everything.

I can submit some of the finished components to bnav if you'd like

I can submit some of the finished components to bnav if you'd like.

Yes please.
Still not published at https://www.npmjs.com/package/bootstrap-vue-3 :(

I can submit some of the finished components to bnav if you'd like.

Yes please. Still not published at https://www.npmjs.com/package/bootstrap-vue-3 :(

Yes, I noticed that for some reason the if statements on actions are causing them to never run. https://github.com/cdmoro/bootstrap-vue-3/runs/7632822151?check_suite_focus=true . If the next actual commit that changes something doesn't cause them to fire, that means I have an issue I need to work out.

Thanks for looking into it!

Shall I merge https://github.com/cdmoro/bootstrap-vue-3/pull/524 or wait for some other changes?

Shall I merge #524 or wait for some other changes?

It's up to you. I think it could be released primarily to see if the workflow is working properly. But I'm likely to have a few more components done by tomorrow.

Ah, I was referring only to testing the workflows, especially publishing. Will merge now.

It still doesn't publish at https://www.npmjs.com/package/bootstrap-vue-3

I left a question report to their github. A possible fix would be to remove the if statements outright and wait for their response to see if there's a better option.

I'm still waiting on the question I posted, but I realize that since I'm not concerned with the actual status of publishing to npm, rather only the workflow, I believe I can test out and try to figure out a solution on my own repository without bloating and waiting for you to review requests..


Include Wiki link to Heroku deploy in README

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Input data normalization

i see that the MeanShift has been applied to input data as the zero normalization, while the data' values is not in the -1 ~ 1 range.
Could this effect the performance?  have the input image data just been divided by 255.0 (data value in 0 ~ 1 range) as the normalization to train the model and how is the final performance?
thanks for your reply!

have the input image data just been divided by 255.0 (data value in 0 ~ 1 range) as the normalization to train the model and how is the final performance?

FYI.  def np2Tensor(*args, rgb_range=255):.

have the input image data just been divided by 255.0 (data value in 0 ~ 1 range) as the normalization to train the model and how is the final performance?

FYI.  def np2Tensor(*args, rgb_range=255):.


add configuration to use nginx-golang-postgres sample with Docker Dev Environments feature

Add a dedicated Compose file in the .docker directory for Dev Env configuration
Add a new dev-envs stage in backend Dockerfile
Update documentation
small others changes

replace by #275


[D435] Recommended configuration for near-range (< 1m) accuracy

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 14.04

Kernel Version (Linux Only)
4.4.0-103-generic

SDK Version
2.9.0 (current master@2a2446f)

I'm testing out D435 for my use case, and sensor precision using default depth settings is much poorer than expected. The subject is a human face around 0.15m-1m away from the sensor, and the 3D result is invariably a blob with significant dynamic noise. I'd be happy to provide some example scans, but I'll begin the conversation here in case you all have some upfront recommendations.

Hey @jfhamlin , here are a list of parameters that I found effective at manipulating depth resolution at close range. I'm using the D415 camera and not the D435 so things might be slightly different.
In no particular order:
Exposure
Gain
Laser Power
DS neighbor threshold
Estimate mediam decrement
score maximum threshold
depth units
disparity shift
depth clamp max
depth clamp min
I'm currently working on this problem myself so if I find anything revolutionary I'll let you know.
Here is the thread I started about a similar issue
https://github.com/IntelRealSense/librealsense/issues/1171

Hello, did anyone compare near range accuracy of D415 vs D435 with sample pictures?
I'm quite disappointed of my D435 accuracy, when I use 3D view I get strong noise and bad z-accuracy.
From pictures in this page D415 seems to have better quality.
Thanks

[Realsense Customer Engineering Team Comment]
This document will be good for you to tune up your depth quality.
https://realsense.intel.com/wp-content/uploads/sites/63/BKMs-For-Tuning-RealSense_D4xx_Cameras_WP_1.7.pdf

@RealSense-Customer-Engineering thanks! I'm happy to have this issue closed for the time being, unless there are plans to expose better near range presets or more tuning suggestions for close-range use cases.

Though looking back at @dorodnic's results, I still see considerably more depth noise at that range.


Server do not start when the DBMS is PostgreSQL.

Due to missing tables related to the Configuration Store feature [1], the server starts with an exception in the startup logs when the underlying DBMS is PostgreSQL.
[1] https://github.com/wso2/product-is/issues/4499

Please find the issue tracking the root cause for this. A detailed description can also be found there.

cannot be reproduced in the latest pack - 5.8.0-alpha4-Snapshot

But this is reproducible on a WUM updated pack of IS 5.7.0, so what's our solution?
Shouldn't we fix to only activate the feature if relevant tables are present?

@emswbandara , we need to create a task to track that redundant feature enabling disabling blocks should be cleaned up when all table schemas gets  introduced for each database type.

@malithie I have already added this concern in here

There is a bit of confusion related to this issue and information is scattered in multiple git issues.
What's the root cause of this behaviour?
How was this fixed, was it done by having appropriate data source configurations or code fix?
@tharindu-bandara @emswbandara appreciate if you could explain?

@mefarazath , currently the schemas related to all database types have not been added for this feature. Therefore this issue can be reproduced if the relevant table/column is not available. However it is intermittent since the connection that is used to check the column existence will have uncommitted changes when there's a SQLException (due to table unavailability), if another code uses this same connection from the connection pool, to query the database this exception can be thrown. Therefore as a fix for this we have introduced a config to enable/disable this feature.

@emswbandara Thanks you for the explanation. Can you point me to the PR which introduced this fix?
Also if the error occurs due to uncommitted connections, will having  property in datasource configurations be sufficient?

@mefarazath Having the  enabled in the data source configurations resolves this issue.


RFE - Review draft localization into Italian for doc/concepts/cluster-administration

This is a RFE
There is a set of pages under doc/concepts/cluster-administration already localized in Italian but still in draft status.
What would you like to be added
Draft localizations should be reviewed, content should be aligned with the latest English version, and the draft flag should be removed
/language it
/priority backlog

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale


"Something went wrong!" message presented when switching threads when response is still being streamed.

Electron app version - 0.10.0-rc3
Steps to reproduce the problem:

Have multiple chat threads.
From one of the threads, initiate a chat message and even before a response is streamed fully click on another thread.

This results in the following page presented to the user:

https://github.com/user-attachments/assets/ede4238a-7e8a-40d3-bde0-1cf688cfab43

Moving this back into Triage and unassigning myself since I have been given other things to do.

PR: https://github.com/gptscript-ai/desktop/pull/407

The above PR fixed this, but I just tested after merging and it is doing something else weird. Will continue to investigate here.

I believe this is the rest of it: https://github.com/gptscript-ai/desktop/pull/412

Tested with electron build - 54ecc2c
This issue is not seen anymore.
When I quit the thread when response is still being streamed and when I revisit the same thread , I dont see this chat message/response in this thread. Will follow up on this issue separately.


Update introduction-to-adapter-objects.md

enhanced the paragraph

Hi @kvndb thanks for the suggestion, but I think the paragraph is ok as-is.


FriendsHouse class

@cbell108  I cannot get to this class because the code loops back to the beginning after any command. I do not see where you created any objects in the main method besides the scanner. This may be why the code just loops everything in the main method.

package main;
public class Friendshousetest2 {
public static void main (String args[]) {
FriendsHouse.Houseinit();
String[] inputs = {"use","look","visit","check inventory","help"};
//Textgame.main(inputs);
FriendsHouse.HouseMain("name", inputs);
}
}
After testing your code it seems that all functions in this class work except for the "check inventory" option, which never opens.


Make the PrivilegeEditor request a list of privileges from the auth-server for assigning

If the user edits available privileges, they won't have the full list client-side.

Outmoded - this component no longer exists.


Add option to allow self-signed/invalid certificates

Kept it simple. Set the AllowSelfSigned to true before the call to NewConsumer.
oauth.AllowSelfSigned = true

consumer := oauth.NewConsumer(
	ConsumerKey,
	ConsumerSecret,
	oauth.ServiceProvider{},
)

If you have another idea for the implementation, let me know.

Thanks for the patch!
How would you feel about using oauth.NewCustomHttpClientConsumer and passing in the modified HttpClient that way?
Similarly, you could override consumer.HttpClient afterwards (which seems a bit less elegant, but basically similar)
I have an example of the second case here:
https://github.com/mrjones/oauth/blob/ce4e16c43ec593b54ca3568b43ae89fe161f4c9e/examples/jira/jira.go
On the one hand, now we have two users wanting this feature (you and jira.go). So I'm definitely open to the possibility.  On the other hand, the fewer options we can have in the library the better!
Either way: Thanks again!

Matt

The first option is indeed much better, I totally missed it!
Here's how it looks:
tr := &http.Transport{
    TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
}
httpClient := &http.Client{Transport: tr}
consumer := oauth.NewCustomHttpClientConsumer(
    ConsumerKey,
    ConsumerSecret,
    oauth.ServiceProvider{},
    httpClient,
)

My PR has no meaning so I'm closing it, thanks for the directions!


Error while running the exporter

Thank you for writing this awesome exporter. I recently tried upgrading the exporter from 0.2 to 0.5.5 along with the kafka-python to 1.4.7. Although most of the metrics were getting populated well, I got the following error: https://gist.githubusercontent.com/chhetripradeep/d294a90a1ee9871ea41a85cc5fed5566/raw/8c1e1a9957ffab6d5085b3f70c5ad525d1a54eb6/gistfile1.txt
I am running kafka v1.0.0 clusters. Thank you for the help.

Hi @chhetripradeep, Sorry to hear you're having issues.
The error log you linked is a timeout when fetching low-water marks. Do you get similar errors for other things, e.g. high-water marks? Are all fetches failing (i.e. every 10 seconds with the default config), or just occasionally?
I've tried that combination of exporter/kafka-python/kafka locally, and it seems to work fine, with no load at least. It's possibly a legitimate timeout fetching from your Kafka cluster. Are your brokers under significant load? Do you have a large number of topics? Have you changed any timeouts using the --consumer-config flag?

Hi @braedon , thank you for the quick reply.

Do you get similar errors for other things, e.g. high-water marks?
I don't see the errors while collecting high-water marks or any other metrics.

Are all fetches failing (i.e. every 10 seconds with the default config), or just occasionally?
Its failing for fetching lowwatermark metrics for few partitions of a topic eg: https://gist.githubusercontent.com/chhetripradeep/92303ddfba789c797b5de36c8fcac319/raw/064e4ed89483aa73d33f5a2bb80a35ddd66b2526/gistfile1.txt

Are your brokers under significant load?
Probably this is the reason.

Do you have a large number of topics?
I have around 20 topics with topics having around partitions ranging from 16 to 150 partitions.

Have you changed any timeouts using the --consumer-config flag?
Let me try changing this timeout flag

Thank you for the help Braedon. I will update the thread with the changes.

Hi @braedon I tried updating the timeout to 20 seconds but still it fails.

@chhetripradeep Which timeout did you set - there's a few haha.
Digging into the code a bit more, it looks like the timeout is occurring when sending (b'x') on the "wakeup" socket, not on a connection to Kafka. I guess the send buffer must be filling up somehow when processing the large response from Kafka.
The setting to control this timeout is wakeup_timeout_ms, which you can set in the config file with the key wakeup.timeout.ms. Can you try setting it to 20 seconds - it's 3 seconds by default.

Hi @braedon haha i set up consumer.timeout.ms timeout. nice catch. let me try doing that and see if the error stops. thanks a lot for your continuous help :)

Hi @braedon looks like there is no consumer config variable named wakeup_timeout_ms I think that config variable is defined by python kafka client only.

Ugg, I was hoping we'd be able to set it via the config file anyway - all those settings get passed to the KafkaConsumer, and through to the underlying KafkaClient - but it looks like KafkaConsumer validates the settings, and doesn't know about KafkaClient's wakeup_timeout_ms.
Looks like there isn't any way to pass settings KafkaConsumer doesn't know about to the underlying KafkaClient, so we'll need to construct a client ourself manually.
I've thrown together a quick branch - https://github.com/braedon/prometheus-kafka-consumer-group-exporter/pull/39 - can you try testing that code, or do you need a pypi/docker release?

Sorry @braedon for late response. I was on vacation. I will try the branch and let you know. Thanks for continuous support. Really very appreciated.

Hi @braedon i just tried your fix but looks like those timeouts are still happening - https://gist.githubusercontent.com/chhetripradeep/70246f8e17289b319747d3db4aa4f31d/raw/d5e504adabf8bed82d41c6ca6211cfae7c2d30c6/gistfile1.txt

Darn, I wonder if the client can't consume anything from the send buffer once it gets full, preventing it from clearing, even with a long timeout... Not sure.
I think I'll have to try and replicate it locally, and do some debugging.

Hello @braedon  Can you think of any workaround for this issue. If you can guide with some pointers to look at, it will be great.

Hi @chhetripradeep, I haven't been able to replicate the issue you're seeing locally. Even with 25k partitions on a single node, and significant read and write load, the exporter is still able to run with no issues. There's a bunch factors that make my tests different to your case - exporter on the same computer, single Kafka node, etc. - but I'm rather limited in what I can set up for testing currently.
As a possible workaround, you could try increasing the refresh interval for topic/high-water/low-water info, using the --topic-interval/--high-water-interval/--low-water-interval options, to see if spacing requests out more helps.
Beyond that, you could try debugging the kafka-python code yourself - particularly looking at what's happening with the wakeup socket. e.g. is it actually timing out because it's filling up with too many wakeup requests (if so, what exactly is generating them), or is something else causing the timeout.
You could try and replicate it with a simplified script that makes the same calls to kafka-python, but eliminates the rest of the exporter. If you can replicate it there, you could try raising an issue with kafka-python.

Closing as I couldn't replicate the issue, and it's been quite a while. If anyone else is running into the same issue, please re-open.


cryfs: 0.10.2 -> 0.11.1

Motivation for this change
Package update.
Upstream now provides a way to use dependencies from nixpkgs ;
except for cryptopp and googletest.
Vendored cryptopp is v8.6.0 in cryfs 0.11.1
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Just opening this for review after Christmas holidays. :)
Ping @midchildan for testing on a Darwin platform.
Could you maybe retest locally running the tests? Supposedly all tests using fuse are disabled so maybe they can succeed even on Darwin.

The following change is needed to compile the vendored cyptopp with Clang:
diff --git a/pkgs/tools/filesystems/cryfs/default.nix b/pkgs/tools/filesystems/cryfs/default.nix
index 446f18661dc..5b927284c49 100644
--- a/pkgs/tools/filesystems/cryfs/default.nix
+++ b/pkgs/tools/filesystems/cryfs/default.nix
@@ -1,6 +1,7 @@
 { lib, stdenv, fetchFromGitHub
 , cmake, pkg-config, python3
 , boost, curl, fuse, openssl, range-v3, spdlog
+, llvmPackages
 # cryptopp and gtest on standby - using the vendored ones for now
 # see https://github.com/cryfs/cryfs/issues/369
 }:
@@ -40,7 +41,11 @@ stdenv.mkDerivation rec {

   strictDeps = true;

-  buildInputs = [ boost curl fuse openssl range-v3 spdlog ];
+  buildInputs = [ boost curl fuse openssl range-v3 spdlog ]
+    ++ lib.optionals stdenv.cc.isClang [
+      # needed to build the vendored cryptopp
+      llvmPackages.openmp
+    ];

   #checkInputs = [ gtest ];

Unfortunately I'm seeing a regression in Boost that's preventing cryfs from compiling on Darwin. Boost is applying the namespace operator (::) on sigemptyset and other signal related functions, which are actually implemented as preprocessor macros on Darwin  and therefore not namespaced.
In file included from /tmp/nix-build-cryfs-0.11.1.drv-1/source/src/cpp-utils/process/subprocess.cpp:6:
In file included from include/boost/process.hpp:24:
In file included from include/boost/process/async_system.hpp:22:
In file included from include/boost/process/child.hpp:21:
In file included from include/boost/process/detail/child_decl.hpp:30:
include/boost/process/detail/posix/wait_for_exit.hpp:60:7: error: expected unqualified-id
    ::sigemptyset(&sigset);
      ^

A bit of searching led me to boostorg/process#55 and #144610. It seems that using a newer version of Boost fixes the problem, so I updated the above patch to use pkgs.boost17x instead. After applying the patch, cryfs now builds and the tests pass too.

I've confirmed that creating/mounting/reading/writing encrypted directories work as intended on Darwin.

Thanks for those tests. I just pushed an update using boost17x by default on all platforms and re-enabling the check phase on Darwing.

I should've mentioned this, but the check phase  can't be enabled for Darwin on Hydra because it requires a full installation of macFUSE. Nixpkgs only includes a compile time stub for libfuse. Here's  a bit of additional context if you're interested.
With Darwin, the check phase for FUSE packages needs to be run locally.

I see on staging-next:
error: anonymous function at /nix/store/j5fhw348rsazaxad115xmf1bf683fdsg-source/pkgs/tools/filesystems/cryfs/default.nix:1:1 called with unexpected argument 'boost'

@GrahamcOfBorg eval

Fixed on staging-next in a38c345989a936ffaa66fe80235719af4f04e246

However this still regresses on staging-next
https://hydra.nixos.org/build/162001566
I suppose this might need to be included in https://github.com/NixOS/nixpkgs/issues/151469 now


Fixed bulkOverwriteApplicationCommands

bulkOverwriteApplicationCommands wasn't sending any commands in the payload
Will add a bit more documentation to make it clearer what the function does and also bit more testing (initial testing shows that it works so that's cool)

Is it still draft yet?

just gotta test it with global commands and then it should be finished

Tested quite extensively, seems to work correctly

Alright.


Amazon.com does not seem to work in the built app (Mac)

Homework

[ x] I looked at nativefier --help and https://github.com/nativefier/nativefier/blob/master/API.md
[ x] I checked the Troubleshooting section of the README.
[ x] I searched existing issues, open & closed. Yes, my bug is new.
[ x] I'm using the latest version available at https://github.com/nativefier/nativefier/releases

Bug description
The top section of Amazon's web page does not display properly in the final built app. It looks like the top section is broken.
Steps to reproduce
nativefier --name 'Amazon' --icon '/path/amazon.icns' 'https://smile.amazon.de/' '/path/FinalApp' --inject '/path/site.css' --title-bar-style 'hiddenInset' --tray --bookmarks-menu '/path/amazon.json' --disable-dev-tools --fast-quit --quiet --lang de-DE
Expected behavior
After the error-free build process, I expected the app to display the page error-free.
Actual behavior
The build process of the app runs flawlessly, yet the Amazon page in the app window looks broken.
Debug info
Context

Nativefier: (47.2.0)
Node.js: ( ?)
Npm: (8.9.0)
OS: (macOS 12.5 Beta (21G5027d))
Is it a regression? If yes, what's the last working / first broken version? Maybe version 47.0
Additional context: -

Why are you adding extra css? May this be the issue?

I have removed the CSS code from the build process. After that the header of the app was ok again.
After I added the CSS code unchanged but again to the build process, the header area of Amazon in the app is still ok.
No idea where the problem was now.


Allow uploading patch from the UI

Description
https://github.com/orgs/community/discussions/146387
It would be nice to allow patches via web interface, how phabricator handles it: a text area where we past the stuff.
Example URLs
https://www.jesusamieiro.com/applying-patches-with-git-and-curl-or-wget/

Why would they send a patch via email? Creating a patch requires them to have the whole repo checked out. What's stopping them from opening a proper PR?

PRs and MRs are relatively new concepts.

Probably time they learn them, I'm not interested in supporting workflows from the 90s in 2025

Also not possible via API, the commit would lose all metadata: https://stackoverflow.com/questions/43769489/how-to-create-a-commit-from-a-diff-or-patch-using-githubs-api

Linus doesn't use GitHub.com. When he gets an email, he applies the patch file via command line. Instead of switching to GitHub.com to apply the patch, switch to the terminal and use pbpaste | git apply


No PixelShuffle used

Hi, were do you use the pixelshuffle operator? Cant find it

https://github.com/pmh9960/iColoriT/blob/8a02415aea6f6cc144650b47f38e58476f4e2a0f/engine.py#L66
This is the pixelshffle operator.


[DO NOT MERGE] Check GPU CI for security issue

GPU workflow did not get triggered - which is good. Unclear why that happened in #1409

Curiously, the workflow run links to https://github.com/AcademySoftwareFoundation/OpenColorIO/commit/70d541843ac66e117011d31c4b3c73a163cf0662

and GitHub even says that this commit does not belong to any branch in this repo:

There was a force-push, but in the branch of the fork

I don't see anything in the PR feed that the base branch was changed or the like, but I would not expect a workflow run in any case. Very peculiar.


Added addons prop to customize the available options in menu

Fixes #57

Removed undo and redo options from the fixed menu.
Removed video embed option from slash menu (file Embed.js not deleted).
Converted the following options as defaultOptions:  font size, font color, bold, italics, underline, strike through, link, bulleted list and numbered list. These are always available.
Converted the following options as addons: hightlight, emoji, code-block, block-quote, and image-upload. These are shown in the menu if the user provides the correct prop.
Added documentation for addons.

@amaldinesh7 _a please have a look.

@amaldinesh7 _a please have a look at the changes.

LGTM. Nice work 👍 @AbhayVAshokan


Enable support for Laravel 10

The title describes everything ;)

@lepikhinb Any chance you can take a look at this?

@lepikhinb +1

as a temporary solution:
composer require based/laravel-typescript:dev-master


Custom Sun Color and Custom Moon Texture not working properly in my mod.

It doesn't color the sun green at all, it colors the moon instead, and it doesn't show the moon texture either.
yesterday the custom sky texture didn't work, only in owerworld. I use World Renderer 1.8.2 but in the latest release not working too.
I Insert a video link, to template what doesnt work.
https://imgur.com/a/Nz5ZqcS

Set a texture of the sun and return a logical true on the sky event.


Do not retract versions in future

Hello there.
Thanks for this package, but, please, in future do not retract any versions as such action breaks pipelines for projects using the package and creates a negative impression about it.

Hello @vbuberen,
Thank you for your feedback. We did not plan on making that change. Unfortunately, there was an issue with the versioning. The latest version was supposed to be 0.3.X, which caused the updates to the package to not reflect as the latest.
We appreciate your time in bringing this issue to our attention, and please know that your feedback has been taken seriously.


Navigation tree collapse if page link's anchor is unicode text.

Sphinx with recommonmark does not use unicode text header as page link's anchor, just ignore them. If the header is written by unicode text only, anchor is empty like "http://example.com/foo.html#". So I use unicode_ids extension to generate unicode anchor text from header.
In that case, navigation to 3rd or below level get fall back to top level content and toc tree collapsed, because sphinx_rtd_theme try to find URI escaped anchor and fail.
Change theme.js from
var anchor = encodeURI(window.location.hash);
to
var anchor = window.location.hash;
worked for me. Is this acceptable change?

@agjohnson you are the javascript guy

var anchor = window.location.hash;

Sorry, that worked only with Edge and IE.
This may be just a workaround, but the code below works with Edge, IE, Chrome.
var anchor = decodeURI(window.location.hash);

Yes, I think that decodeURI is more correct than encodeURI. For the test string ёђѓєѕіїјљњћќўџабвг, the value of window.location.hash is:

Firefox: %D1%91%D1%92%D1%93%D1%94%D1%95%D1%96%D1%97%D1%98%D1%99%D1%9A%D1%9B%D1%9C%D1%9E%D1%9F%D0%B0%D0%B1%D0%B2%D0%B3

Chromium: ёђѓєѕіїјљњћќўџабвг

With encodeURI(window.location.hash):

Firefox: %25D1%2591%25D1%2592%25D1%2593%25D1%2594%25D1%2595%25D1%2596%25D1%2597%25D1%2598%25D1%2599%25D1%259A%25D1%259B%25D1%259C%25D1%259E%25D1%259F%25D0%25B0%25D0%25B1%25D0%25B2%25D0%25B3

Chromium: %D1%91%D1%92%D1%93%D1%94%D1%95%D1%96%D1%97%D1%98%D1%99%D1%9A%D1%9B%D1%9C%D1%9E%D1%9F%D0%B0%D0%B1%D0%B2%D0%B3

In other words, in Firefox it gets encoded twice. The alternative is to find a more cross-platform alternative to window.location.hash but decodeURI seems to work in the meantime.

@jessetan

@0giso can you check if PR #615 solves this for you?

@jessetan I am not sure #615 can fix or not this problem, but I created test case to reproduce the issue.
https://github.com/0giso/testcase_for_sphinx_rtd_theme_issue495
It use sphinx_rtd_theme installed by pip.

Thanks for the testcase. Can you explain the need for the unicode_ids extension? If I remove it, the TOC works correctly.
#615 does not influence the behavior you reported and is no longer necessary because Fx now behaves identical to Chrome.

I need unicode_ids extension for non-English markdown document because if I don't use it, sphinx with recommonmark ignore non-English character in section title, then section hyper link url ends with '#' (no url fragment appended).
I updated the test case as below to show unicode_ids necessity.

Disable unicode_ids
Section headers are translated from English to Japanese, Thai, or Korean.

Thank you.


ory proxy exposes duplicate cors headers when already configured upstream

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] I have joined the Ory Community Slack.
[X] I am signed up to the Ory Security Patch Newsletter.

Ory Network Project
https://goofy-dewdney-rri0sodzzj.projects.oryapis.cojm
Describe the bug
We have a use-case to use the ory proxy auxiliary function to proxy our dev environment locally along with the ory session handler. This enables frontend developers to work on the UI while being authenticated correctly.
The issue arises when upstream services already handle CORS headers for you. The proxy will add it's own CORS headers as part of the proxy middleware, which results in duplicate headers, causing CORS to fail in the browser. The only solution right now was to fork and patch the cli with the following patch.
diff --git a/cmd/cloudx/proxy/proxy.go b/cmd/cloudx/proxy/proxy.go
index a5c9f82..cb57b43 100644
--- a/cmd/cloudx/proxy/proxy.go
+++ b/cmd/cloudx/proxy/proxy.go
@@ -223,6 +223,12 @@ func run(cmd *cobra.Command, conf *config, version string, name string) error {
 			return body, nil
 		}),
 		proxy.WithRespMiddleware(func(resp *http.Response, config *proxy.HostConfig, body []byte) ([]byte, error) {
+
+			// Remove a duplicate Access Control header
+			resp.Header.Del("Access-Control-Allow-Origin")
+			// Remove a duplicate Access Allow Credentuals header
+			resp.Header.Del("Access-Control-Allow-Credentials")
+
 			l, err := resp.Location()
 			if err == nil {
 				// Redirect to main page if path is the default ui welcome page.
@@ -239,17 +245,16 @@ func run(cmd *cobra.Command, conf *config, version string, name string) error {
 		return nil
 	}

-	var originFunc func(r *http.Request, origin string) bool
-	if conf.isDev {
-		originFunc = func(r *http.Request, origin string) bool {
-			return true
-		}
+	originFunc := func(r *http.Request, origin string) bool {
+		return true
 	}

+	corsOrigins := []string{"http://localhost:3000", "http://localhost:4000"}
+
 	proto := "http"
 	addr := fmt.Sprintf(":%d", conf.port)
 	ch := cors.New(cors.Options{
-		AllowedOrigins:         conf.corsOrigins,
+		AllowedOrigins:         corsOrigins,
 		AllowOriginRequestFunc: originFunc,
 		AllowedMethods:         corsx.CORSDefaultAllowedMethods,
 		AllowedHeaders:         append(corsx.CORSRequestHeadersSafelist, corsx.CORSRequestHeadersExtended...),

Reproducing the bug

Have an upstream service that handles CORS headers;
Run the ory proxy: ory proxy --dev --project goofy-dewdney-rri0sodzzj $upstream
Access the login url: http://localhost:4000/.ory/self-service/login/browser?return_to=http://localhost:3000
Login

This will result in you getting redirected to http://localhost:3000/, which will fetch an api endpoint through the proxy. The response of the proxied request will contain duplicate CORS headers, leading to CORS failure in the browser.
Relevant log output
No response
Relevant configuration
No response
Version
Version:    v0.3.4 Git Hash:   654e4987a7c0a6111988dccb158541329ec36c9f Build Time: 2024-02-10T10:29:21Z
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Binary
Additional Context
No response

Hey - awesome find! Would you mind creating a PR for this? :) Looks like you already have the diff :)

I am running into the same problem for ory tunnel, what is the current state of this issue?

Didn't have time to fix this unfortunately, but you should be able to apply the patch locally (assuming things didn't change much) and build the binaries. Otherwise a PR fix would be ideal for the maintainers.

I disabled CORS for my Ory project using the Ory CLI and that fixed my problem
ory patch project <your-project-id> \
  --replace '/cors_public/enabled=false' \


Frost list 1.0

This is a #major# change.
CHANGELOG

Removed small/medium/large detail level support.
Updated  to use ember-block-slot. for multiple yield sections.
Updated  user interface, now user need pass the path of custom list-item component to frost-list as positional param insetead of directly invoking the component.
Updated  Css to serve new template layout.
Added  list expand/collapse control.
Added  frost-sort intergration support.
Fixed  content shifting when item get selected.

Changes Unknown when pulling 798754b4b927af8ac2633ec89ea4674a75413871 on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling dde5ff2306e051eae848c397db06f7e69308ebad on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 97054718c7fd7b4217769e38abaa8b5027d7ed8b on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 8908bf426ec0020db8e8c17a22577db777eea429 on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 04eff40aeb3f25c2700f3ff88ee3865d279a9a20 on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 829c0bd739e70f1b2086bb7b045eb158775d3e37 on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 829c0bd739e70f1b2086bb7b045eb158775d3e37 on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 7e6c579affe31e3f9871b910e205cac0f5297daa on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 0ee53b0db2e1b762860442f3531c40f83cf9374e on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 25a11712ae233389bdbbbcae232a393907ce7cba on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling 25a11712ae233389bdbbbcae232a393907ce7cba on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling bf6375843cf9b13ca1e5cf7600d9d0190215a29e on quincyle:refect-list into ** on ciena-frost:master**.

Changes Unknown when pulling bf6375843cf9b13ca1e5cf7600d9d0190215a29e on quincyle:refect-list into ** on ciena-frost:master**.


Link to documentation in the README is broken

As per the title -- the link to documentation on this page https://github.com/ably-labs/scalable-serverless-editable-chat-demo/tree/main/chat-web-app/store doesn't resolve (for me)

I've just tried this link in Incognito mode and it seems to work fine. Can you provide me more details of how you are trying to access it so I can reproduce the scenario? @stichbury


Go: Use new retry mechanism

This commit accompanies https://github.com/googleapis/gax-go/pull/36 .
It updates the client library generation to use the new retry mechanism.
A notable change:
defaultCallOptions and its friends now lookup the appropriate CallOption
in a map. This has two advantages:

We should now initialize fewer anonymous functions.
This is nice but does not greatly matter.
In the YAML config, the names are normally in snake case.
The previous implementation converts it into camel.
We can get rid of this dance completely by just making the names
opague strings.

Current coverage is 82.03% (diff: 78.57%)

Merging #434 into master will increase coverage by 0.01%

@@             master       #434   diff @@
==========================================
  Files           195        195
  Lines          7299       7307     +8
  Methods           0          0
  Messages          0          0
  Branches        964        963     -1
==========================================
+ Hits           5986       5994     +8
  Misses         1032       1032
  Partials        281        281

Powered by Codecov. Last update 15c6b8e...c236c1d

@jmuk PTAL

LGTM


Fixed documentation by removing obsolete reference.

Python 3.11 has removed support for @asyncio.coroutine and with it removed the documentation references for asyncio.iscoroutinefunction() such that the intersphinx reference is unavailable.
The implementation of asyncio.iscoroutinefunction() still exists, however:
https://github.com/python/cpython/blob/a1092f62492a3fcd6195bea94eccf8d5a300acb1/Lib/asyncio/coroutines.py#L21-L24
It looks as though it will be removed in the future:
https://github.com/python/cpython/issues/94912
As we still need to support Python < 3.11 where @asyncio.coroutine may be used we will likely need to vendor this until Python 3.11 is the minimum supported version when inspect.iscoroutinefunction() can be used directly instead. That will likely not be required until 3.12 though.

Found in https://github.com/django/django/actions/runs/3347024592/jobs/5544547813


[stable/prometheus-operator] How to set config reloader containers resources?

Describe the bug
There's no way to set the resources for sidecar containers such as alertmanager's config reloader, prometheus's rules configmap reloader and config reloader.
Version of Helm and Kubernetes:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.7-gke.19", GitCommit:"bebe882824db5431820e3d59851c8fb52cb41675", GitTreeState:"clean", BuildDate:"2019-07-26T00:09:47Z", GoVersion:"go1.11.5b4", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
stable/prometheus-operator
What happened:
What you expected to happen:
I need to set the values for the resources of the sidecar containers. But there's no place in values.yaml to do that.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

@vsliouniaev Is there a way to set the resources for these containers?


[HUDI-5046] Support all the hive sync options for flink sql

Change Logs
Make the hive sync options compatible with HiveSyncConfig, before this patch, only option with shortcut key works.
Impact
Flink SQL hive sync options.
Risk level (write none, low medium or high below)
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

The modified test is passed and the failed tests are not related, would merge it soon ~


Update the Release Planner ADO state to use "Complete" instead of "Finished

The reason that the Release Planner ADO state uses "Finished" was to keep the terminology consistent between the Release Planner and ADO.  Since the Release Planner UI uses the term "Complete", the Release Planner state should be changed to use "Complete".

[ ] Update automation to use "Complete" for the state of the Release Plan ADO work item.
[ ] Update all existing work items with a state of "Finished" to the state of "Complete".  If this can't be done via automation, then we can export a query and make the update, then import work items.
[ ] Once all of the existing release plan states are changed from "Finished to Complete", we can remove the "Finished" state from the Release Plan ADO template.

@ladonnaq Curious, what is the problem with the word Finished? I understand that it will be good to be consistent, but given other priorities, I don't think this will happen in Dt


Standardize testing environments of flutter_tools dependencies

Instead of using our own machines and deleting stuff to reproduce states of missing dependencies to test things like #9580, create an official process to test on unified initial environments.
Something lightweight like Docker is ideal. Then we can have different images for each development environment combinations. Definitely seems possible for Android SDK https://hub.docker.com/r/runmymind/docker-android-sdk/~/dockerfile/. There's even a flutter image  https://hub.docker.com/r/brianegan/flutter/. Not sure how easy it is to get xcode running in docker though.
Otherwise we can create images of OS X in virtualbox

Seems only possible to create linux based images in docker. Can't test the macosx paths there.

Seems like the simplest way (to simulate mac) is to take a mac, install https://my.vmware.com/web/vmware/details?downloadGroup=FUS-857&productId=527&rPId=16242. Then it has an option to create a guest VM instance from the host machine's own recovery partition. Seems like a good way to test since we can snapshot various conditions.
cc @cbracken cause I think you're testing stuff

@xster -- edited your comment to prettify the download link for VMWare Fusion.

Is this a dup of #8963?

Hi @xster
I see there's an open issue addressing the case you described.
Please follow up on that issue,
I'm closing the current one as duplicate.
If you disagree please write in the comments
and I will reopen it.
Thank you


Keep turtle in same position when switching direction

The turtle has to be rotated from a central x,y origin. Look for examples on how this may be achieved.

Check the following https://stackoverflow.com/questions/60357251/rotating-image-on-canvas-around-the-center-of-the-image


(HTTP code 404) no such image - no such image: springci/spring-boot-ci-image:latest: No such image: springci/spring-boot-ci-image:latest

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

click on create

Have the same problems with some images


Getting Argument of type 'ChatOpenAI' is not assignable to parameter of type 'BaseLLM'. when trying to pass ChatOpenAI to RetrievalQAChain or ConversationalRetrievalQAChain

fromLLM method of RetrievalQAChain or ConversationalRetrievalQAChain expects an llm but when you pass it an instance of ChatOpenAI
instead of OpenAI, you'll get the following type error
Argument of type 'ChatOpenAI' is not assignable to parameter of type 'BaseLLM'.
 Property '_generateUncached' is missing in type 'ChatOpenAI' but required in type 'BaseLLM'.ts(2345)

code to reproduce:
import { OpenAI } from "langchain/llms/openai";
import { ConversationalRetrievalQAChain } from "langchain/chains";
import { HNSWLib } from "langchain/vectorstores/hnswlib";
import { OpenAIEmbeddings } from "langchain/embeddings/openai";
import { RecursiveCharacterTextSplitter } from "langchain/text_splitter";
import * as fs from "fs";

export const run = async () => {
 /* Initialize the LLM to use to answer the question */
 const model = new ChatOpenAI(
   {
     modelName: "gpt-3.5-turbo"
   }
 );
 /* Load in the file we want to do question answering over */
 const text = fs.readFileSync("state_of_the_union.txt", "utf8");
 /* Split the text into chunks */
 const textSplitter = new RecursiveCharacterTextSplitter({ chunkSize: 1000 });
 const docs = await textSplitter.createDocuments([text]);
 /* Create the vectorstore */
 const vectorStore = await HNSWLib.fromDocuments(docs, new OpenAIEmbeddings());
 /* Create the chain */
 const chain = ConversationalRetrievalQAChain.fromLLM(
   model,
   vectorStore.asRetriever()
 );
 /* Ask it a question */
 const question = "What did the president say about Justice Breyer?";
 const res = await chain.call({ question, chat_history: [] });
 console.log(res);
 /* Ask it a follow up question */
 const chatHistory = question + res.text;
 const followUpRes = await chain.call({
   question: "Was that nice?",
   chat_history: chatHistory,
 });
 console.log(followUpRes);
};

The error will be gone if you replace:
const model = new ChatOpenAI(
    {
      modelName: "gpt-3.5-turbo"
    }
  );

with
  const model = new OpenAI({});

Expected behavior:
I should be able to use Chat models (e.g. gpt-3.5) with ConversationalRetrievalQAChain

@aamir1995
Hello! What version of Langchain do you use?
I tried to reproduce it with your code, but I got the result below.
 npx ts-node src/service/issue_1162.ts
{
  text: 'The president honored Justice Stephen Breyer for his service to the country and mentioned that he is a retired Justice of the United States Supreme Court and an Army veteran.'
}
{
  text: 'The president thanked Justice Breyer for his service to the country.'
}

The difference is that mine just passed OpenAI API KEY to the field directly.
And I am using the latest one.

Upgrading the package from 0.0.67 > 0.0.72 fixed the issue.
Thanks for the quick reply :100:

Great! Enjoy!


schema is not exportable and importable

I created a schema in graphqldesigner . Then  created code. later I wanted to add a new table and a column in old table. Since the schema is lost if i access the  http://localhost:4100/  again (with no option to export and import scehma) , I have to change things manually which I was trying to avoid. Any suggetsion

While I'm sure it'd be nigh impossible to make the tool import what it exports, surely it wouldn't be too hard to serialize the current state of the app into JSON, and let users import/export that state?


A page for the CSS url() function is needed

Request type

[X] New documentation
[ ] Correction or update

Details
There is currently a  page but no CSS url() function page.
Related issues
If this request relates to other issues in Bugzilla or GitHub, please provide links:
Once created, add url() instead of  to the See Also of

[ ] - 'background-image' - https://developer.mozilla.org/en-US/docs/Web/CSS/background-image
[ ] -'border-image' - https://developer.mozilla.org/en-US/docs/Web/CSS/border-image
[ ] -'list-style-image' - https://developer.mozilla.org/en-US/docs/Web/CSS/list-style-image
[ ] -'content' - https://developer.mozilla.org/en-US/docs/Web/CSS/content
[ ] -cursor - https://developer.mozilla.org/en-US/docs/Web/CSS/cursor
[ ] -border-image(-source) - https://developer.mozilla.org/en-US/docs/Web/CSS/border-image-source
[ ] - @counter-style/symbol - https://developer.mozilla.org/en-US/docs/Web/CSS/@counter-style/symbols

Acceptance Criteria:
All check boxes checked.

Page at https://developer.mozilla.org/en-US/docs/Web/CSS/url()
still have to do examples at top and links.


Update user-reaching references to Census in R API doc-strings

Update any use or reference to "Cell Census" in the R doc-strings of methods that can reached by the user, i.e. all doc strings of classes/methods/functions labelled with the @export decorator e.g. this
Use or references may include the following and must be changed to corresponding match:
Any references to "Cell Census" should be modified accordingly to the new feature name "Census":
Non-code redaction

CZ CELLxGENE Discover Cell Census --> CZ CELLxGENE Discover Census
Cell Census --> Census

All other code related if and when it appears:

CellCensus --> cellxgene.census (R package)
cell_census --> cellxgene_census (Python package)
cell-census --> cellxgene-census (Python package)

With this pattern in mind any other reference must be changed accordingly.

Completed #344


Fix missing CSP exception in NC16

The CSP exception URL requires host and path.
host is either given by settings or by gethostname() and path only from settings a /

Now every case should work, tested with multiple environments.
Only the host and / is required, not the full path so we can add a / just to be sure, it doesn't matter if there's already one.

The CSP exception URL requires host and path

That's wrong. The path is not required, see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#Sources
Also adding the web server host is useless, because therefore you should use the reserved 'self'. Maybe I have some applications activated which add self to csp and therefore I can't reproduce your issue. Will try it asap and report back.
Nonetheless thanks for your time and effort.

Nextcloud creates different csp for Chrome and Firefox. I created a pr #71, which adds self also on FF. Would be awesome if you could test it @criegerde @MinIsMin

fixed in 3665c399baf9dcf69ad4c492f887f4043b857f29


router-view/ router-link cannot work

Version
4.0.0-rc.6
Reproduction link
http://none
Steps to reproduce
start run script
What is expected?
router-view/ router-link  normal
What is actually happening?
const RouterView = RouterViewImpl;
// warn against deprecated usage with  &
// due to functional component being no longer eager in Vue 3
function warnDeprecatedUsage() {
const instance = vue.getCurrentInstance();
const parentName = instance.parent && instance.parent.type.name;
.....
TypeError: Cannot read property 'parent' of null

const RouterLinkImpl =
.....
setup(props, { slots, attrs }) {
const link = vue.reactive(useLink(props));
const { options } = vue.inject(routerKey);
Cannot destructure property 'options' of 'vue.inject(...)' as it is undefined.

I can't check anything without a repro: https://new-issue.vuejs.org/?repo=vuejs/vue-router-next#why-repro


[iOS] TextInput .focus() does not work when editable is false initially

[x] I have reviewed the documentation
[x] I have searched existing issues
[x] I am using the latest React Native version

Environment
Environment:
OS: macOS Sierra 10.12.6
Node: 9.10.1
Yarn: 1.5.1
npm: 5.6.0
Watchman: 4.7.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 3.0 AI-171.4443003
Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.1 => 0.55.1
Steps to Reproduce

https://snack.expo.io/@riwu/textinput-focus
import React, { Component } from 'react';
import { Button, View, TextInput, Text } from 'react-native';

export default class App extends Component {
  state = {
    editable: false,
  };
  render() {
    return (
      <View style={{marginTop: 100}}>
        <Button
          title="Focus"
          onPress={() => {
            this.setState({ editable: true });
            this.ref.focus();
          }}
        />
        <TextInput
          ref={ref => {
            this.ref = ref;
          }}
          opacity={this.state.editable ? 1 : 0}
          editable={this.state.editable}
        />
        <Text>Position below text input</Text>
      </View>
    );
  }
}

Expected Behavior
On clicking "Focus", the input should be focused (on Android this works).
Actual Behavior
On iOS, input did not get focused.

setState is asynchronous, move your focus call into a callback and you'll get your intended behavior.
this.setState({ editable: true }, ()=>{
    this.ref.focus();
});

@lfkwtz

calling .focus() on uneditable TextInput works on Android, so the inconsistency should probably be fixed unless it's an OS limitation rather than implementation difference.
even if this is intended, pressing the "Focus" button second time should work since editable will be true by then.

Also in the actual app, the state that determines the editable prop is stored in Redux, so I'd have to execute the .focus() in componentDidUpdate or change my action from  (...) => ({...}) to
(...) => dispatch => {
  dispatch({...});
  return Promise.resolve(); // not very elegant
}

This also delays the display of keyboard until the component re-renders, though that might be a better behaviour as the user will not be able to input text until then.

Is it not clear that this is a bug report? There's no reason why pressing the "Focus" twice wouldn't trigger the keyboard input.

This is a bug. I cannot get onFocus to work if my TextInput has editable={false} property.


Local code generation depending on remote module doesn't work right

Describe the bug
I'm working with a local proto directory that depends on googleapis/googleapis remote module. When I import the remote type, the local generated code doesn't use remote deps. The generated code is as follows:
import { proto3 } from "@bufbuild/protobuf";
import { Operation } from "../../../google/longrunning/operations_pb.js";

The Operation type should be imported from remote deps, but instead it's importing from local files which doesn't exsit.
My buf.yaml is as follows:
version: v1
deps:
  - buf.build/googleapis/googleapis
breaking:
  use:
    - FILE
lint:
  use:
    - DEFAULT

My buf.gen.yaml is:
# buf.gen.yaml
version: v1
managed:
  enabled: true
  go_package_prefix:
    except:
      - buf.build/googleapis/googleapis
plugins:
  # Go
  - plugin: buf.build/protocolbuffers/go
    out: gen/go
    opt:
      - paths=source_relative
  - plugin: buf.build/bufbuild/connect-go
    out: gen/go
    opt:
      - paths=source_relative

  # JS
  - plugin: buf.build/bufbuild/es
    out: gen/js
  - plugin: buf.build/bufbuild/connect-es
    out: gen/js
  - plugin: buf.build/bufbuild/connect-query
    out: gen/js

Hey @coobeet, buf does not generate code for dependencies, unless you specify the --include-imports flag. For Go, you don't notice because the googleapis/googleapis proto files set a go_package option that points to pregenerated code.
The workaround is to use two buf.gen.yaml files, and run the JS one with buf generate --template buf.gen.js.yaml --include-imports.
For more context, see https://github.com/bufbuild/connect-es/issues/262 and https://github.com/bufbuild/protobuf-es/issues/457.


fix: 🐞 fix check for existence errors/warnings

fix check for existence errors/warnings
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] UI changes have been reviewed
[ ] No UI review needed

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 2.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error installing @mui/utils

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
run:
npm i @mui/utils
Error:
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>Current behavior 😯
No package found in npm repository
Expected behavior 🤔
Correct inport of mui
Context 🔦
The error happens installing the package directly, but using other mui libraries that depends on it
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

I can't reproduce it. Perhaps there was a temporary issue with npm?
The 5.14.9 version shows up correctly on npm: https://www.npmjs.com/package/@mui/utils?activeTab=versions
Could you try again?

The problem was present for some hours and now is disappeared, I don't understand if there are some issue on the repository. Anyway, now it works correctly. Thank you


Adding mspec test runner

Adding a bozo test runner that will execute tests built using MSpec

Hey @mjo-zopa,
Thanks for opening this pull-request! There's just a thing or two more that you need to do before we can consider it for bozo-scripts:

should always include a youtrack issue
should be signed off by a non committing developer

As soon as you do that, we'll consider your submission right away!
Thanks!
Note: For a full list of issue filing guidelines, please refer to the bozo-scripts issue filing guidelines.


datastore: document use of local development server

The documentation for gcd only gives examples for Java and Python, both of which are configured automagically via environment variables. I tried writing:
http, err := cloud.DialHTTP(context.Background(), cloud.WithEndpoint("localhost:8080"))

But that gave the error:
google.DefaultTokenSource: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.

That page doesn't discuss local debugging at all.

Need to double check, but I think Python/Java use DATASTORE_HOST and DATASTORE_DATASET for auto configuration

I'm developing an application that facilitates both Google App Engine (Managed VM, Go) and Google Compute Engine (Go) and accesses Datastore from both sides.
This works fine in production, although I am struggling a bit to get a nice testing and fiddling setup to run. It might be the case that this is just because of the apparent lack of documentation, so I will explain what we are trying here. If this is off topic, I would appreciate if you could direct me to the correct issue tracker/mailing list/whatever. Thank you.
When trying to let my code for Compute Engine connect to the local Datastore instance (started by gcloud preview app run ... or maybe also gcd.sh) I run into problems because I am not sure how to redirect requests to the local instance. I looked up cloud.DialHTTP, which says "Most developers should call the relevant NewClient method for the target service rather than invoking DialHTTP directly." so I looked further and found datastore/example_test.go which calls datastore.NewClient which is missing from the current version. I also found this answer on StackOverflow which talks about writing my own wrapper and accessing a gcd.sh Datastore instance. It is more than a year old now, so it would be great to have confirmation this before wasting time trying it out. @proppy?

I set up datastore emulator (following instructions here https://cloud.google.com/datastore/docs/tools/datastore-emulator).
Started emulator with:
$ gcloud beta emulators datastore start --no-legacy

Set the following environment variables (exactly as documented):
$ export DATASTORE_DATASET=my-project-id
$ export DATASTORE_EMULATOR_HOST_PATH=localhost:8128/datastore
$ export DATASTORE_HOST=http://localhost:8128
$ export DATASTORE_EMULATOR_HOST=localhost:8128
$ export DATASTORE_PROJECT_ID=my-project-id

My sample code hits the emulator and works exactly as expected.
Sample code:
package main

import (
	"fmt"
	"log"

	"cloud.google.com/go/datastore"
	"golang.org/x/net/context"
)

type Person struct {
	Name     string
	Engineer bool
}

func main() {
	ctx := context.Background()

	client, err := datastore.NewClient(ctx, "my-project-id")
	if err != nil {
		log.Fatalf("failed to make client: %s", err)
	}

	anne := Person{
		Name:     "Annie",
		Engineer: true,
	}

	key := datastore.NewKey(ctx, "Person", "",<PHONE_NUMBER>352832, nil)
	if _, err := client.Put(ctx, key, &anne); err != nil {
		log.Fatalf("failed to put: %s", err)
	}

	anne = Person{}
	if err = client.Get(ctx, key, &anne); err != nil {
		log.Fatalf("failed to get: %s", err)
	}

	fmt.Printf("%#v\n", anne)
}

Output:
$ go run datastore.go
main.Person{Name:"Annie", Engineer:true}

Corresponding emulator log:
[datastore] INFO: Adding handler(s) to newly registered Channel.
[datastore] Sep 12, 2016 2:46:28 PM io.gapi.emulators.netty.HttpVersionRoutingHandler channelRead
[datastore] INFO: Detected HTTP/2 connection.
[datastore] Sep 12, 2016 2:46:47 PM com.google.appengine.api.datastore.dev.LocalDatastoreService$11 run
[datastore] INFO: Time to persist datastore: 1 ms

Am I missing something?
What needs to be documented?

/cc @rakyll

I guess the expectation is that the client should run against the devappserver (at localhost:8080), the developers simply don't know they need to run the emulator to use this client.
Can we document how to start the emulator in the datastore godoc somewhere or just give a link to https://cloud.google.com/datastore/docs/tools/datastore-emulator?
I think once the emulator is out of beta, this will be more seamless. But for now, docs would be good to have.

Got it! Ok, will do.

It looks as though we are using @okdave 's personal github key for interactions between Gerrit and Github. Can we create a bot user for this instead? Esp. considering that Dave will be moving teams at some point.
/cc @broady @rakyll @jba @zombiezen

Filed #369

Sorry for 'abusing' this thread, but I'd like to ask @adams-sarah: the reason you manually set the key in datastore.NewKey(ctx, "Person", "",<PHONE_NUMBER>352832, nil) is because the emulator cannot automatically generate a key?
When I try to run datastore.NewKey(ctx, "Person", "", 0, nil) or datastore.NewIncompleteKey(ctx, "Person", nil) then I get the error: failed to get: rpc error: code = 3 desc = Key path element must not be incomplete: [Person: ]

@cyxg for a Key to be valid, it must have either a name or an ID. So when Put-ing a new entity, you may want to do something like:
key := datastore.NewKey(ctx, "Person", "Annie", 0, nil)

See godoc here for more examples and documentation: https://godoc.org/cloud.google.com/go/datastore

I apologize, I think this may actually be a bug.
Made an issue you can track: https://github.com/GoogleCloudPlatform/google-cloud-go/issues/411
I'll work on this tomorrow.

@cyxg ok major blunders here on my part. My apologies, I am fairly new to this project.
You can 100% Put with an incomplete key, i misspoke. The issue with the above code is on the Get.
client.Put returns both a complete key and an error. In my example code above, I ignore the new key.
The Put code should read:
key := datastore.NewKey(ctx, "Person", "",<PHONE_NUMBER>352832, nil)
key, err = client.Put(ctx, key, &anne)
if err != nil {
    log.Fatalf("failed to put: %s", err)
}

// and then use the updated Key (which now has an ID) in the Get, not the old incomplete key.

So sorry about the confusion. Please let me know if you run into any other issues.

Hi @adams-sarah, thanks a lot for the response (and sorry for my slow response) :)!
Upon further digging I also saw that the code did successfully Put with NewIncompleteKey using your code, but I became (and still am) super confused when the keys generated end up being incrementing digits since I could've sworn it was supposed to be a very long randomly generated number.. I can also see it's documented (https://cloud.google.com/appengine/docs/go/datastore/entities) that default policy should generate a number with 16 random digits, whereas the legacy policy should generate in the way I experience it now.. but what confuses me is the fact that I start the emulator using --no-legacy flag (gcloud beta emulators datastore start --no-legacy), yet all the ID's generated appear to be using the legacy policy..
Anyway, it's not the end of the world since it's working, I just find it rather confusing :)


Patching debug logging calls and debug print statements

As titled,
This PR patches all calls to logging.basicConfig and orphan print statements used for debugging purposes.

@kc611 thank you for the patch! @sklam thank you for the review!


onExtHostInitialized is not defined

I noticed with the upgrade that onExtHostInitialized is not there anymore, is there an alternative function that we can use for this?

Now you just need to wait for the service initialization

Okay, great, thanks for the info!


Enabled bicep in pipelines

Change

Update module tests to work with bicep
Refactored several modules to work with tests
Refactored pipeline actions to work with bicep
Added bicep cli installation
Added conditional template spec publishing workaround
Fixed some bicep template issues
Switched pipeline login to native action

NOTE: This requires an update of the current credentials

Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update (Wiki)

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (readme)
[x] I did format my code

@MrMCake , do you think it's worth parameterizing the 'deploymentScope', making it more targeted. Thus, reducing lines 123-145?


Code Improvemnt: documentOrigin and popupWindowOrigin are calculated wrong

In line 680 you do the following (see source at https://github.com/sahat/satellizer/blob/master/satellizer.js#L680-L681 ):
var documentOrigin = document.location.host + ':' + document.location.port,
                popupWindowOrigin = popup.popupWindow.location.host + ':' + popup.popupWindow.location.port;

In JavaScript document.location.host already contains the port, so doing something like
var documentOrigin = document.location.host + ':' + document.location.port;

will have a weird result, i.e. "localhost:8181:8181". Instead you should use
var documentOrigin = document.location.host,
    popupWindowOrigin = popup.popupWindow.location.host;

This also makes sure that you don't have a tailing ":" without a port...

Thanks, this was actually submitted as a PR a while back. This is a case of two "wrongs" make 1 "right", because in the end it still worked.


How to setup multiple servers / nodes under one network with ssl?

I have 2 servers running under same network and I made ssl work with this configuration
http {
    ssl_certificate "/etc/nginx/ssl/cert.pem";
    ssl_certificate_key "/etc/nginx/ssl/key.pem";
    ssl_session_cache shared:SSL:1m;
    ssl_session_timeout  10m;
    gzip on;
    gzip_types text/plain text/css application/javascript application/xml application/json;
    gzip_proxied any;
    gzip_comp_level 5;
    gzip_min_length 1k;
    server_tokens  off;
    client_max_body_size 0;

    server {
        listen 80;
        listen [::]:80;
        server_name domainhere;

        return 302 https://$server_name$request_uri;
    }

    server {
        listen <IP_ADDRESS>:443 ;
        listen [::1]:443 ;
        server_name localhost;
        gzip off;
        location / {
            proxy_pass http://localhost:24444;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header REMOTE-HOST $remote_addr;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            add_header X-Cache $upstream_cache_status;
            expires -1;
        }
    }

    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
        server_name domainhere;

        location ~ (^/socket.io/)|(^/upload/)|(^/download/) {
            proxy_pass http://localhost:24444 ;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header REMOTE-HOST $remote_addr;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
        add_header X-Cache $upstream_cache_status;
            expires -1;
        }
        location / {
            proxy_pass http://localhost:23333 ;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header REMOTE-HOST $remote_addr;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            add_header X-Cache $upstream_cache_status;
            expires -1;
        }
    }

}

Now everything is working for the server #1, but what would i do to make the other server work. The current port for that other server is 24445 and I tried reverse proxying it to 8443 but it doesnt work.
Also I paid support on your  page but i cant log into the group because QQ is chinese only and creating account on it is almost impossible. Could we have a telegram group for supporters? I want to test the new versions on english not chinese website. Thanks!

Update i set up 2 panels one on one machine with port 443 and one on the other with port 8443
both are ssl and both are working in ssl daemons and everything but i cant add both daemons to a single panel.

it makes no sense

The web side of MCSM does not support handshakes with the daemon side that is not the root directory. You can backend different daemons to different ports.

Wdym backend different daemons to different ports, they are running on two different ports?

How would I go around to connect another machine as another daemon to my panel then?

The problem now is that filling in host:port/path on the web side will cause the program to be unable to correctly resolve the host and port, and the path cannot be included in communication.
You need to reverse proxy different daemons to the root directories of different ports.

And how do i do that?

My suggestion is to allocate an independent port for each daemon.

But i have one is hosted on 24444 and the other on 24445 thats not the issue. I can't get the panel to recognize the one thats on 24445 --> 8443. Its ssl and it works in the browser i have the image above but the web ui doesnt see it

How do i make the panel recognize the second machine? wss://domain:8443 works in browser and shows up as daemon but panel reports it as offline

Is your router's port forwarding loopback disabled?

I sent the picture above, its accessible. My router doesn't have that option at all, its simply porforwarded as it should be

If anyone has an idea on how to figure this out it would be great

It may be because you are using an intranet IP. Please do not use IPs such as 192.168.X.X.

We use $ip1 to refer to the internal ip of the one that works well(i mean, the main server, referred to as machine1).
Use $ip2 to refer to the ip of another one(referred to as machine2).
Use $domain to refer to your domain.

Let's check some details first

[x] For both machine, panel works on port 23333 and daemon works on port 24444.
[x] For machine1, you have setup nginx.
[x] You can use ip1[:443] and ip2[:443] to connect to each panel.
[x] You want to proxy the daemon on machine2 to ip1:8443.
[x] You can connect to http://ip2:23333 (no ssl).

Here we go
Add a server block in the nginx config of machine1, don't forget to fill your real ip2 and $domain:
server {
        listen 8443 ssl http2;
        listen [::]:8443 ssl http2;
        server_name $domain;

        location / {
            proxy_pass http://$ip2:23333 ;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header REMOTE-HOST $remote_addr;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            add_header X-Cache $upstream_cache_status;
            expires -1;
        }
    }

Then try to open https://$domain:8443 to check if the proxy works well.
If yes, add a daemon on the panel on machine1, ip wss://$domain, port 8443. Check if this works.
By the way
By the way, i wonder how did you proxy the backend to /#/service.
I'm not native English speaker. Forgive my grammar mistakes.

we haven't had a telegram group yep. but we do have a discord channel: https://discord.com/invite/9UgPGDFH

He is already in the Discord channel and the issue has been resolved


Improve member count.

The action counts github_membership and github_repository_collaborator in the tf file as members.
However, If a user starts writing the GitHub account management in a different way in the tf file, the action will not be counted correctly.
Therefore, I have improved the action to count members from terraform plan results.

Codecov Report

Merging #45 (8e0709b) into main (1077d0e) will decrease coverage by 0.38%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #45      +/-   ##
==========================================
- Coverage   96.80%   96.42%   -0.38%
==========================================
  Files          10        8       -2
  Lines         250      224      -26
==========================================
- Hits          242      216      -26
  Misses          8        8

Flag
Coverage Δ

unittests
96.42% <100.00%> (-0.38%)
:arrow_down:

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

Impacted Files
Coverage Δ

lib/check_members_action.rb
87.23% <100.00%> (ø)

lib/config_validator.rb
91.30% <100.00%> (ø)

lib/terraform_reader.rb
100.00% <100.00%> (ø)

spec/config_validator_spec.rb
100.00% <100.00%> (ø)

spec/terraform_reader_spec.rb
100.00% <100.00%> (ø)

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


Ships Landing Without Opening Bay

Ships that land and drop off NPCs such as the Va'ruun, Ecliptic and Starborn do not open their bays and drop off NPCs. This also causes a lock on the quest Groundpounder as the enemies that are dropped off during the invasion do not exit the ship to progress the quest.

Details
Quest ID: MS01
Stage number: 1000
Game Version
1.7.29
New Game
No
Reproduction Steps
Land on any planet and wait for a ship to land and the bay does not open. The ship simply lands and does not open and does not take off. The ship that spawns in the Vulture;s Roost was inaccessible due to this bug. Starborn ships and NPC ships related to random landings on planets and ships related do the Wanted perk just land and do not do anything. This causes a lock on the Groundpounder quest as the enemies do not spawn.

There is a mod out that should fix this issue:
https://www.nexusmods.com/starfield/mods/5668

This is related to https://github.com/Starfield-Community-Patch/Starfield-Community-Patch/issues/221 and has been fixed by Bethesda.


option handling robustness

Currently, option handling allows multiple specifications of options and arguments, as well as requiring optind be set to 0 before calling getopt long.
Roll getopt into our own callback option handling that enhances error reporting as well.
Take care of #197 and #216 while doing this.

Won't Fix


problematic command line

Hi,
I'm having an issue with the command npx fixpack || true in package.json/scripts.
I'm getting the error:
✖ Initializing sharec
TypeError: Cannot read property 'split' of undefined
    at /test/node_modules/sharec-schema/lib/helpers/commandsToMap.js:36:58
    at Array.reduce (<anonymous>)
    at commandsToMap (/test/node_modules/sharec-schema/lib/helpers/commandsToMap.js:22:30)
    at commandAtom (/test/node_modules/sharec-schema/lib/atoms/command.js:61:41)
    at /test/node_modules/sharec-schema/lib/actions/compose.js:46:9
    at /test/node_modules/sharec-schema/lib/actions/compose.js:83:65
    at /test/node_modules/sharec-schema/lib/actions/compose.js:46:9
    at Object.<anonymous> (/test/node_modules/sharec-schema/lib/actions/compose.js:82:69)
    at Object.processor (/test/node_modules/lodash/_createFlow.js:71:31)
    at /test/node_modules/sharec/src/steps/mergeConfigs.js:78:39

I've look at commandsToMap, it's splitting the command into subcommands and arguments. But why?
PS: I have to add || true because fixpack in return 1 even when it has successfully fixed the package.json

We should to process commands as data structures, where command is a key and arguments are members, but at the same time, we can have multiple members with the same key.
It needs for cases, when current state is npx eslint && npx stylelint and upcoming one is npx eslint --fix && npx stylelint. We should merge each command member correctly.
As I see here, we should handle this case in commandsToMap and thats would be enough to fix the problem.

Are you working on that? Or can I make a PR to fix it?

Thank you for your PR! :)


Translation problems

I translated everything in /peo/views/*html to the German language when I run the command docker-compose up -d the page is online and everything works without problems, but it is still in the Chinese language.
Please help me to solve this problem.
Thank you

There are still some Chinese text in go files, so you can translate the Chinese text strings into German then build your own docker image with the Dockerfile, change the image in docker-compose.yml and use docker-compose up -d command.
Soon i will add translation modules thus every one can easily use their language, thanks for your comment.

Thanks for the answer, since I'm not an expert to be able to do it all, can you give me a little more detail on how to do it, if you can write me a few commands, I really like your system

Working Tanko You


You can pay for invoices you create

pay self invoice is normal function .
sendPaymentV2's grpc-parameter AllowSelfPayment default value is false, SelfPayment is disable default.

"invoice you create"?
the invoice is create by oblnd-addInvoice grpc-api?
the invoice is create by by our coud server for you?    this type invoice is coud server's invoice. and  "invoice.dest" is server's pubkey,not your pubkey .

dest is the pubkey of the payment proxy node, and it is impossible to determine whether the invoice was created by itself.

now app's all invoice id  created  by  coud server. this type invoice  is server's invoice.
if app want to disable pay to  this type invoice ,app can:
1)when app receive the invoice ceated by server, app can  record the invoice's paymentHash exist in a app local storage .
2)next time , when pay some invoice, check if the invoice's paymentHash  is in local storage, if true app stop payment Invoke

There is a situation:

After creating the invoice, save the hash and then uninstall the app.

After reinstalling the app, the check is invalid, so the previous invoice can also be paid again.

After creating the invoice, save the hash and then uninstall the app.

After reinstalling the app, the check is invalid, so the previous invoice can also be paid again.
it 's a stupid situation.

when  uninstall app,  walletdb is gone ,  all Channel is gone, all local invoices gone, all local trancation record gone.
after reinstalling the app, the walletdb is all most new:without any channel, without any invoices;   the invoice before uninstall will have no relation with you, and who give the old invoice.
after reinstalling  ,if you need receive new payment ,make cloud server create new invoice for you .


Use ListItem in blueprint tree UI

What
This PR back-ports ListItem into the blueprint tree UI. This includes multiple fixes and additions to ListItem itself.
Note that this PR strictly replicates the current behaviour, which has several issues:

containers look inactive although they are active
hidden elements look inactive although they are active
cannot unhide one children of a hidden group
hiding a container doesn't dim its children
more generally, it would be nice to improve the visual distinction between containers, space views, data group and data item (i.e. if you know what a space view vs. data group is, you'll find them, but the tree UI does very little to actually teach that distinction)

Fixes:

#3044
#2946
#2855

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

There is some rather annoying flickering going on:

There is some rather annoying flickering going on:

I can reproduce on all 3 major browsers but not on native 🤔


Copied mapcubed module from ehsteve's sunpy PR

Copied mapcubed module from ehsteve's sunpy PR so we can start work with it while the PR is being finished and merged into sunpy.

@DanRyanIrish can you please merge this so I can start working on SJIMapSequence

@abit2, yes I'll merge this today.  However, I would advise when working on SJIMapSequence to, as much as is possible, develop an abstract API to minimise how dependent we are on the specifics of MapCubed.  In light of the disagreements in riot last week, it is possible that we may want to use something other than MapCubed in the future if a better data cube object is developed in sunpy or astropy etc.  MapCubed is also bound to change before and after it is merged in sunpy.  So an abstract API will help minimise additional work for SJIMapSequence in the long run.

I maintain this was not the right way to go...

@Cadair, what do you suggest that we can use now to start developing API?

From my limited knowledge of the data I think that sunpy/cube is a closer fit to what you need.

So what's the point of MapCubed then?  As far as I know there isn't anything inherently different between AIA images and SJI images.  They are directly focused images of the Sun in EUV/UV.  Why would IRIS SJI need something inherently different than AIA?

So what's the point of MapCubed then?

I am not really sure on this you would have to ask @ehsteve. As written MapCubed is a collection of 2D headers and one contiguous 3D array.

Why would IRIS SJI need something inherently different than AIA?

AIA images are a collection of 2D images and metadata, whereas SJI is one 3D array and a singular 3D header. sunpy/cube was written specifically to address the case of a 3D (or more) array with a single corresponding header.
Again, all of this is as MapCubed is currently implemented. Although, I don't see the point in re-implementing something that looks a lot like sunpy/cube.

OK.  Thanks for the summary @Cadair.  You have a good point.


ext_proc: remove exception throw in ext_proc configuration parsing code

Description
This PR refactors the exception throwing logic in the ext_proc filter to use absl::Status returns instead of throwing exceptions.
Fixes #37046

Commit Message: ext_proc: remove exception throw in ext_proc configuration parsing code
Additional Description: This change makes the error handling in ext_proc more consistent with other parts of the codebase by using Status returns instead of exceptions. The validation logic remains unchanged.
Risk Level: Low
Testing:

Added new Unit Tests around config validation
Existing unit tests modified to verify status returns
Integration tests remain unchanged as external behavior is the same

Docs Changes: N/A
Release Notes: N/A

/assgin @mattklein123 @yanavlasov

/assign @mattklein123 @yanavlasov

/assign @jmarantz @alyssawilk

HI, @alyssawilk , thanks for reviewing this PR.
Could you please clarify what's the eventual goal about Envoy exception throwing?  Are we supposed not to throw exception during filter passing configuration, but has to return a not-ok absl::Status if configuration parsing failed here: https://github.com/envoyproxy/envoy/blob/77e0bfc20090ad1e636e20d2060ae562780fd98e/source/extensions/filters/http/ext_proc/config.cc#L14.
If that's the case, then this PR is not achieving the goal yet.

/wait

so the goal is to remove exceptions from core Envoy. Envoy will always support exceptions (and have try-catch) so folks downstream don't need to rewrite filters.  That said, Envoy does not support exceptions on the data plane and the exception removal project has found a non-trivial number of (uncaught) exceptions on the data plane, so the fewer exceptions Envoy has and the farther up the stack they are, the less likely uncaught data plane exceptions will be to end up being reintroduced.
I think if we get to the point that all of core Envoy has no exceptions it behooves google to remove exceptions from extensions we use, just so we don't need to use them at all, but that project is not staffed or planned.

Thanks @alyssawilk for the clarification.
HI, @agrawroh ,
I think it should be easy to surface the absl::status and return here:
https://github.com/envoyproxy/envoy/blob/5a241d32cc89ce9aa492a5820707fd584547d843/source/extensions/filters/http/ext_proc/config.cc#L13
,  if the ext_proc configuration is wrong.
What you can do is that instead of checking the configuration in the c'tor of FilterConfig here: https://github.com/envoyproxy/envoy/blob/5a241d32cc89ce9aa492a5820707fd584547d843/source/extensions/filters/http/ext_proc/ext_proc.cc#L265,  you can move that configuration check out to here: https://github.com/envoyproxy/envoy/blob/5a241d32cc89ce9aa492a5820707fd584547d843/source/extensions/filters/http/ext_proc/config.cc#L22, i.e, before the c'tor of FilterConfig.
That way, you can easily return a an absl::status for this function: ExternalProcessingFilterConfig::createFilterFactoryFromProtoTyped() if configuration check failed.
You can also move below checks to the same place:
https://github.com/envoyproxy/envoy/blob/5a241d32cc89ce9aa492a5820707fd584547d843/source/extensions/filters/http/ext_proc/ext_proc.cc#L266
https://github.com/envoyproxy/envoy/blob/5a241d32cc89ce9aa492a5820707fd584547d843/source/extensions/filters/http/ext_proc/ext_proc.cc#L61
This way, we can make the ext_proc filter code free of throwing any exception.

/retest

I don't know how this got 5 assignees but seems overkill.  As this is pure extension code removing all but tyxia who is codeowner and can approve and merge extension code.  @tyxia you can add me back in if you prefer a second pass review

@agrawroh Thanks for your good work!
Only one thing left is that we should call verifyFilterConfig() here:
https://github.com/envoyproxy/envoy/blob/64036b42e1581df185d02858d0e5d48b8aaaef97/source/extensions/filters/http/ext_proc/config.cc#L60, and if the configuration is bad, throw an exception to keep the existing behavior.  It's a little bit unfortunate createFilterFactoryFromProtoWithServerContextTyped() does not support return an absl::status, and it's caller chain does not throw exception, so ext_proc should throw it here if configuration is bad.  Please add a unit test case to cover this code change as well.

LGTM


Edit Numbers Shown on One Page

Show 10 results on one page.

Solved by the issue Pagination 10 for ALL Pages #321