Update AsyncServiceClientCredentials to take HttpRequest

There are auth schemes that require more information than just the service url. Example is the HMAC-SHA256 that the Azure Application Configuration team requires for their service. This requires us to construct a string from HttpHeaders in addition to the service url.
Pulling changes from: https://github.com/Azure/autorest-clientruntime-for-java/pull/593/

Can one of the admins verify this patch?

LGTM

Just one question, the changes in .editorconfig, is it expected?

@anuchandy Yes. I realised that because they were at the bottom, they were only applying to [*.md] files. I can create another PR for this if you want.

@conniey thanks for clarifying, that is a separate commit, so fine with having it in this PR. Between, it will be good to add small description about it in the PR description, just the way you did for Credential + HttpRequest. Just for future ref.


Feature Request: Disable the "/" hotkey (which access the address bar) in certain websites

Feature Requested
Every time I am typing, I keep accidentally access the address bar when I pressed the "/" key.
I would like this option to be disabled when I'm in certain websites for example Google Sheets, or when I'm in Google Docs.
So that I don't have to use my mouse to get back on the line I'm typing on.
Relevant Screenshot
https://github.com/user-attachments/assets/6ffdb719-6c94-4d7e-9412-82c68c948206
Checklist

[X] The feature would be useful to more users than just me.

I think there is already an option in the Search tab of the settings page called "Disable / to search when on these sites", but it never worked for me. Perhaps this should be tagged as a bug instead of a feature request.

Supported in 0.9.13


Run validation script

Transferred from https://github.com/AntelopeIO/leap/issues/1431 original author bhazzard

This is the entire run from genesis to current on latest Leap v5

depends on  https://github.com/eosnetworkfoundation/engineering/issues/77

currently in progress, will take several days

Currently ~65% complete


fixed container name for shipwright-webhook

Changes

Fixed container name for shipwright-webhook from shp-build-webhook  to shipwright-build-webhook
Fixes #1648

Submitter Checklist

[ ] Includes tests if functionality changed/was added
[ ] Includes docs if changes are user-facing
[x] Set a kind label on this PR
[x] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
NONE

I had not seen that issue before. But question. Changing the container name. That would only be for future Shipwright Build releases. In Operator, is that fixable through other means or given its version is "connected" toa Shipwright Build version, it would also not help?

/approve
@SaschaSchwarze0 So this would have an impact on the operator, but not in the way you would expect. We have operator logic that modifies the deployed image based on an environment variable. We pattern match the container name to the environment variable - changing the container name means we need to update the env var name.
I'm OK with this - it brings consistency to those environment variables. This is a minor change that can be addressed once this PR merges and we update the operator with the next nightly release manifest.


Error on video upload: Incomplete response received from application

After selecting the file to upload and completion of the upload the browser returns an error screen with the Incomplete response message.

Closing this issue as I now feel that it is resolved.


[SMALLFIX] Decrease netty packet size in tests.

If we keep it at 64KB, read requests end up reading 64KB * 16 max packets in flight = 1 MB of data. This leads to weird behavior when checking for Alluxio caching, since even reading 1 byte will lead to 1MB being read, which could potentially be the entire block. It does make some tests slower so we will need to make sure to increase the packet size when necessary.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18092/Failed Tests: 6org.alluxio:alluxio-tests: 6alluxio.client.RemoteReadIntegrationTest.remoteReadLock[0]alluxio.client.RemoteReadIntegrationTest.readTest5[0]alluxio.client.RemoteReadIntegrationTest.readTest6[0]alluxio.client.RemoteReadIntegrationTest.remoteReadLock[1]alluxio.client.RemoteReadIntegrationTest.readTest5[1]alluxio.client.RemoteReadIntegrationTest.readTest6[1]
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18094/Failed Tests: 1org.alluxio:alluxio-core-common: 1alluxio.util.io.BufferUtilsTest.equalIncreasingByteArray
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18099/
Test PASSed.

Merged build finished. Test PASSed.


Incorrect upload URL when self hosting

Greetings,
So this is my first S3 integration like this so please bear with me because I've been thrown straight into an ocean.
I'm getting CORS errors when trying to upload something despite the public access being fully enabled in my Amazon S3 Bucket settings.
Also the URL that throws CORS errors doesn't seem to be correct, it's https://bucket_name.s3.eu-north-1.amazonaws.com//bucket_name, why is that so?
Why bucket_name occurs twice in the URL and why when it's used for the second time there are double slashes before it?
Here is my env structure:
Postgres
POSTGRES_PRISMA_URL='postgres://user_name@localhost:5432/user_name'
POSTGRES_URL_NON_POOLING='postgres://user_name@localhost:5432/user_name' # Direct Connection
S3 compatible object storage e.g. AWS
S3_ENDPOINT='s3.eu-north-1.amazonaws.com'
S3_ACCESS_KEY='access_key'
S3_SECRET_KEY='secret_access_key'
PUBLIC_S3_BUCKET='bucket_name'
Vercel specific, but can be easily replaced.
VERCEL_URL='http://localhost:3000'
PUBLIC_ENV='development' # preview/production
Only used for cron jobs that run using Github Actions.
API_SECRET_KEY=''
Thank you in advance.

Hi there,
actually, I had a fair amount of trouble with settings S3 us well. I just checked and noticed that I even added some comment in https://github.com/stophecom/sharrr-svelte/blob/main/src/lib/s3.ts - but I don't recall the exact problem.
Maybe it relates to https://github.com/anacronw/multer-s3/issues/192 ?
As for the CORS issue. Maybe you have some custom config on Amazon? https://docs.aws.amazon.com/AmazonS3/latest/userguide/cors.html
In my setup I use another S3 provider so I can't really help with that I'm afraid.
Hope that helps at least a bit.
Best
Chris


WIP: #6664 fixes for server side external io api

this will contain necessary fixes in order server side part of external io api to work properly.

i am just started, this is not ready to be merged yet, it's work in progress as suggested by prefix in PR name.
looks like in peer.c a lot of io done directly and not using api from transport.c


python code cannot find the namespace declared in qsharp code

I'm a new comer. I failed to run the hello world with python.
from HelloWorld import SayHello
ModuleNotFoundError: No module named 'HelloWorld'
It seems the python code cannot find the namespace declared in qsharp code.
I am using vs code, how can I fix it? Thank you!

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

ID: d7575d10-c405-8e24-3487-008d2338b756
Version Independent ID: 030f289f-4280-def3-598b-615883282486
Content: Create a Quantum Random Number Generator - Microsoft Quantum
Content Source: articles/quickstarts/qrng.md
Product: quantum
GitHub Login: @bromeg
Microsoft Alias<EMAIL_ADDRESS>

Hi @zhizeng8, did you install the QDK for Python?
Installation link: https://docs.microsoft.com/en-us/quantum/install-guide/pyinstall

Hi @zhizeng8, did you install the QDK for Python?
Installation link: https://docs.microsoft.com/en-us/quantum/install-guide/pyinstall

I have installed QDK, is (QDK) different from (QDK for python)? Thank you! @geduardo

I can run Q# command line applications successfully and import qsharp in .py successfully. The only problem is from HelloWorld import SayHello. Thank you! @geduardo

@zhizeng8, your .qs file must be in the same folder as the .py file. If that still doesn't work, can you share the contents your .qs file?

namespace HelloWorld {
open Microsoft.Quantum.Intrinsic;
open Microsoft.Quantum.Canon;
operation SayHello() : Unit {
    Message("Hello from quantum world!");
}

}

Can you confirm that the .py and .qs files are located in the same folder? Can you copy/paste the output you get when running python?
You can also try running python -c "import qsharp; qsharp.reload()" from the folder with your .py and .qs files, if you have recently upgraded to a new version.
Also, so we know what versions you have installed, can you run pip show qsharp and dotnet iqsharp --version and report the output?

.py and .qs files are located in the same folder.
Traceback (most recent call last):
File "/Users/zengzhi/VscodeProjects/HelloQuantum/hello_world.py", line 3, in
from HelloWorld import SayHello
ModuleNotFoundError: No module named 'HelloWorld'
Name: qsharp
Version: 0.11.2006.403
Summary: Python client for Q#, a domain-specific quantum programming language
Home-page: https://github.com/microsoft/iqsharp
Author: Microsoft
Author-email: None
License: UNKNOWN
Location: /Library/anaconda3/lib/python3.7/site-packages
Requires: jupyter-client
Required-by: qdk
iqsharp: 0.11.2006.403
Jupyter Core: 1.3.60623.0
.NET Runtime: .NETCoreApp,Version=v3.1

Can you ensure that the .qs file is saved? Try closing and re-opening it from the same folder to ensure that it has the correct contents?

Yes, it is saved.

Can you please run the following Python script to see whether the Python code is correctly finding your Q# operation?
import qsharp
qsharp.reload()
print(qsharp.get_available_operations())

You should see:
['HelloWorld.SayHello']

It returns:
['Qrng.SampleQuantumRandomNumberGenerator', 'Qrng.SampleRandomNumber', 'Qrng.SampleRandomNumberInRange']

It finally works after I delete the Program.qs file.

Thank you very much!

😆 I was in midst of typing a long potential thought/suggestion, and it's comforting to hear it wasn't that. Happy you got it working!

I see! This is an interesting issue caused by the fact that you have multiple .qs files, and your other .qs file must have contained an @EntryPoint() operation, which was causing this operation in the other file to be invisible to Python. I can reproduce this as well. I will open an issue in the https://github.com/microsoft/iqsharp repo for this. Thank you for reporting, and I'm glad you got it working!


[Urgent] Cuda synchronize problem

Hi @HantingChen
I am trying to use cuda version for speeding up, but it shows that the time of cuda threads synchronization is much much longer than computation.
Could you please tell me how u handle this problem?

I'm sorry that the cuda code was written by my colleague and I'm not familiar with cuda.


[Enhancement] Take container into consideration when initiating concurrency

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

There are many ways to set cpu limitation of a container, taking docker for example

--cpu-period: affect cpu.cfs_period_us
--cpu-quota: affect cpu.cfs_quota_us
--cpu-rt-period: affect cpu.rt_period_us
--cpu-rt-runtime: affect cpu.rt_runtime_us
--cpus: affect both cpu.cfs_period_us and cpu.cfs_quota_us
--cpuset-cpus: set cpu affinity

Now, for cpu limitation, we only respect cpu.cfs_period_us and cpu.cfs_quota_us and cpuset.cpus. And real time scheduler configs(cpu.rt_period_us, cpu.rt_runtime_us) will be ignored when calculating relative core number
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

@Mergifyio rebase

run starrocks_admit_test

If the docker container runs with the specific cpuset-cpus, should we consider it by sched_getaffinity, or does the CPU bandwidth control already consider cpuset-cpus?
sudo docker run --cpuset-cpus="0-10" ...

run starrocks_admit_test

run starrocks_admit_test

run starrocks_be_unittest

run starrocks_admit_test

run starrocks_admit_test

@Mergifyio backport branch-2.5


May need to redo several cards to "respect action order"

AKA make sure there is not excessive stuff being done in a cards use function that is instant and not an action.

huh


Add more ErrorCode variants

It's possible that those were omitted for a reason (ie. they can't actually propagate). Please just disregard if that's the case.

👍


How to surport django 3.0?

Modify "load staticfiles" to "load static" in file:"browse.html".

Commit already have been merged but a new version was not released yet.

This has been fixed in the meantime.


Allow specifying port and databases for bbr when not using bosh links

Since bosh create-env still does not support using links, I would like to propose the following changes to the bbr job. To allow us to switch to the postgres bbr job, for bucc.
Original issue: https://github.com/cloudfoundry/postgres-release/issues/26

@valeriap have added a test, it compiles but I'm unable to run test in my current environment. Apparently the test suite does not support bosh with uaa auth...
Has CI for PR branches been enabled? Asking because not having to setup a new bosh environment would save me some time.

@rkoster Thanks for updating the test suite.
The CI for PR is not enabled yet and we have a story in the backlog to support bosh with uaa.
I've run the suite with the PR and the following typo was found:
diff --git a/jobs/bbr-postgres-db/templates/config.sh.erb b/jobs/bbr-postgres-db/templates/config.sh.erb
index 3665c29..291ec52 100755
--- a/jobs/bbr-postgres-db/templates/config.sh.erb
+++ b/jobs/bbr-postgres-db/templates/config.sh.erb
@@ -18,7 +18,7 @@ if_link("database") do |data|
   end

   port = data.p("databases.port")
-  databases = data.p("databases.database")
+  databases = data.p("databases.databases")
 end

  %>

With this typo fixed the suite has run fine.

Thanks, have fixed the typo


Custom metrics doc doesn't mention assign method

URL(s) with the issue:
https://www.tensorflow.org/guide/keras/train_and_evaluate#custom_metrics
Description of issue (what needs changing):
First small issue:  reset_states is deprecated, il should be reset_state. Furthermore, this method is not required when creating a custom metrics.
Second issue:
The doc shows an example with assign_add when updating the metrics. However, it may not fit users need.
For example, let's consider I want to compute a Peak Signal to Noise Ratio metric (a kind of logarithmic MSE). If I follow the doc, I would write something like this:
import tensorflow as tf
from tensorflow import keras
import math

class PSNR(keras.metrics.Metric):
    """
    Peak Signal to Noise Ratio metric
    """
    def __init__(self, name='PSNR', **kwargs):
        super().__init__(name, **kwargs)
        self.psnr = self.add_weight(name='PSNR', initializer='zeros')

    def update_state(self, y_true, y_pred, sample_weight=None):
        y_pred, y_true = tf.cast(y_pred, tf.float32), tf.cast(y_true, tf.float32)
        mse = tf.reduce_mean(keras.metrics.mean_squared_error(y_true, y_pred))
        psnr = 10.0 * tf.divide(tf.math.log(tf.divide(10000**2, mse)), math.log(10))

        self.psnr.assign_add(psnr)

    def result(self):
        return self.psnr

As a high level API user, I am not familiar with tf.Variable methods. Thus, I used assign_add like in the documentation instead of assign because I had no clue assign existed. And it took me some time to figure why my metric was so high and increasing so fast...
Clear description
I think an exemple with assign would benefit some users who would need to implement a metric that is not a sum
Correct links
Yes
Parameters defined
Yes
Returns defined
Yes
Raises listed and defined
Yes
Usage example
Yes
Request visuals, if applicable
No
Submit a pull request?
don't know

@nicolasnn ,
We see that the issue template has not been filled, could you please do so as it helps us analyse the issue.Thanks!

Edited

@tilakrayal @sanatmpa1 i would like to work on this issue. Could you guide me regarding the same?

Will take your issue one by one as follow.

You are right reset_states has been depreciated, instead you can use reset_state as mentioned in the warning, I can help you with creating PR for thew same.

Subclassing metric will resolve many of the complex scenarios =, whereas other methods will be having certain limitations. You can still use the simplest method to define custom metric as you have mentioned. You can also look into this article where he has explained multiple ways to define custom metrics.

assign_add to update the metrics was used specific to the training example shown in the document, however, as per your requirement you can use any of the state ops mentioned here.


The Tutorial Screen Flashes When A TimeLine Starts

The problem
Describe the bug
Version:Dialogic2-alpha-13
If I make the program wait a second before I start a tiemline the tutorial screen always flashes first.
The tutorial screen, I mean this one:

To Reproduce

Make two characters with different name
Make a timeline and for every character prepare some dialogues
Make two simple Mark2D nodes in the main game scene
Before start the timeline, create a timer to wait for 1 second.
Start the timeline and register characters to Mark2D nodes, respectively.
Then run the game

My code is like this:

Screenshots

System (please complete the following information):

OS: MACOS 14.2.1
Godot Version: 4.2.1 stable
Dialogic Version: 2.0-alpha-13

@FakerDomain could you try this again with the current main branch? A bunch of changes to the textbubble layout have been made, so it would be useful to know whether this is still a problem or not. Thank you very much!

@FakerDomain could you try this again with the current main branch? A bunch of changes to the textbubble layout have been made, so it would be useful to know whether this is still a problem or not. Thank you very much!

Sorry for replying so late, I have tried the main branch, and it seems that problem shows no more. I really appreciate your help!!~


Version Switches Do Not All Work: /ed, /edh, /edo

This is a great utility and solves a good handful of problems when launching the game.
However, the version swtcthes do not seem to work as intended. Here is what happens. I am running the 0.71 version of MinEdLauncher. I am running the game through Steam, with the following  basic command line parameters in 'Properties | General | Launch Options':
cmd /c "MinEdLauncher.exe %command% /autorun /autoquit"
When I run this with the /ed switch, it runs base Elite Dangerous, neither Horizons nor Odyssey, as expected
But when I run this with the /edh switch, it runs Odyssey.
And when I run this with the /edo switch, it fails: the CMD box appears then autoquits.
I attach separate log files that result from using the /edh and /edo switch.
I am sure it's something I am missing. Please advise any changes I need to make. And thank you for your work on this.
min-ed-launcher (for edh switch).log
min-ed-launcher (for edo switch).log

Does your settings file have any values for filterOverrides? It should come with { "sku": "FORC-FDEV-DO-1000", "filter": "edo" } if you've never run the launcher before. If it's not there, try adding it.

Thank you for the quick response. I am not sure of the syntax to use for the insertion you suggested in the setting.json file. [I am not familiar with this particular language format.] I did have a settings file. Here is the text it contained:
{
"apiUri": "https://api.zaonce.net",
"watchForCrashes": false,
"language": null,
"restart": {
"enabled": false,
"shutdownTimeout": 3
},
"autoUpdate": true,
"maxConcurrentDownloads": 4,
"forceUpdate": "",
"processes": []
}
Here is the way that I have inserted the text:
{
"apiUri": "https://api.zaonce.net",
"watchForCrashes": false,
"language": null,
"restart": {
"enabled": false,
"shutdownTimeout": 3
},
"autoUpdate": true,
"maxConcurrentDownloads": 4,
"forceUpdate": "",
"processes": [],
"filteroverrides": {
"sku": "FORC-FDEV-DO-1000",
"filter": "edo"
}
}
With this edit, the game runs, but even with the "/edh" switch, it still runs Odyssey. And with the "/edo" switch, it will not run the game at all.
Let me know what I might try to run Horizons using the Min-Ed-Launcher. I attach the current version of the setting.json file, and the log file that results from using this file and the '/edh' switch.
Thank you for your support.
min-ed-launcher (with filteroverrides in settings).log
settings.json.txt

That was close. Just missing two brackets.
{
    "apiUri": "https://api.zaonce.net",
    "watchForCrashes": false,
    "language": null,
    "autoUpdate": true,
    "maxConcurrentDownloads": 4,
    "forceUpdate": "",
    "processes": [],
    "filterOverrides": [
        { "sku": "FORC-FDEV-DO-1000", "filter": "edo" }
    ],
    "additionalProducts": []
}

For future reference, you can find a sample settings file in the readme.md file at the bottom of the settings section.

Got it. I will test it out this evening when I return from work and let you
know the result.
On Mon, Sep 26, 2022 at 2:29 PM Chris @.***> wrote:

That was close. Just missing two brackets.
{
"apiUri": "https://api.zaonce.net",
"watchForCrashes": false,
"language": null,
"autoUpdate": true,
"maxConcurrentDownloads": 4,
"forceUpdate": "",
"processes": [],
"filterOverrides": [
{ "sku": "FORC-FDEV-DO-1000", "filter": "edo" }
],
"additionalProducts": []
}
For future reference, you can find a sample settings file in the readme.md
file at the bottom of the settings section.
—
Reply to this email directly, view it on GitHub
https://github.com/rfvgyhn/min-ed-launcher/issues/62#issuecomment-1258443448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWU2F766HYJVFIEP2YY32F3WAHTSFANCNFSM6AAAAAAQVOOT5A
.
You are receiving this because you authored the thread.Message ID:
@.***>

I was finally able to make those revisions and it works!  /edh starts Horizons; /edo starts Odyssey. I have successfully created separate shortcuts that run off of my Steam installation. Thank you for the help.
I have a separate account for Odyssey through Epic; and I may have a question about how to set up separate shortcuts to run Odyssey or Horizons off of my Epic account. But I will post a separate issue for that. This issue can be closed.
Again, thank you.


Add curl scratch binary and introduce docker healthcheck

Add curl scratch binary and introduce docker healthcheck
Updated buildx.Dockerfile

I think it would be better to add a --healthcheck flag to the CLI, which just makes a HTTP request to /health and exits with 0 or 1, depending on the response.
No need to include all of curl for this.

@pduchnovsky just noticed you've closed this PR. So are you working on a non-curl PR like I suggested? Or what's the reason?

@jonasgeiler I closed the PR because I no longer use the whoami container, and as a result, my interest in the project has shifted. Wishing you all the best with it!


[mui-system][material-ui][Grid v2] Stabilize API

What's the problem?
The Grid v2 component is marked as unstable. With the addition of the Pigment Grid, a stable no-runtime alternative with the same API, we should mark the Grid v2 as stable.
Also, with three separate grid components, I worry it might get confusing to know which one to choose for users
Solution
Stabilize Grid v2 and deprecate Grid, making Grid v2 the option for runtime Grid.
Search keywords: gridv2 unstable grid

On hold: https://github.com/mui/material-ui/pull/42742

hmm I saw component being built in pigment-css, which I didn't expect.
I thought those component will be part of base-ui, and that material-ui & joy-ui will use them or reexport them if needed.

I prefer making Grid v2 stable in v6 (without renaming the name) and deprecating the Grid v1.
I think it's the right time to get rid of the Grid v1 because the v2 is using gap by default thanks to @DiegoAndai. It's much better and I think the community will like it.

I prefer making Grid v2 stable in v6 (without renaming the name) and deprecating the Grid v1.
For the docs, I think we can swap so /material-ui/react-grid presents the new Grid and /material-ui/react-deprecated-grid presents Grid v1.

I agree, this approach makes sense 👍🏼

Is #42000 about the same issue?

Is #42000 about the same issue?

Yes, I'm closing it.


[Feature] Offers Gradle support when compiling

Description
This PR brings the ability to use Gradle as a build tool, for those who are more familiar / used to Gradle
The following features are offered:

A new key in repo.json config that indicates if that repo is supposed to be compiled with Gradle or Maven
A test that tests the functionality of Gradle building
A README.md reform that includes Gradle in it
Most important of all, compiles using Gradle shell script in the addon repo

Reason
As a follow up PR for https://github.com/Slimefun/Addon-Template/pull/5 so it works in the future when one is using Gradle based template

Oh wow, gaving this support Gradle would be very awesome, thanks a lot!
Though bare with me please, I'll be honest and tell you that this is gonna take a long time to review.
I currently got 56 Pull Requests and 65 Issues in my back log and it is gonna take some time till I get to this. And the reviewing itself may also take quite a while since it is a relatively huge PR.
But thanks a lot for making these changes!

No problem, but please notify me for any issues in the code
As I am still kinda learning JS and Java, it would be great if you could point out anything that could be optimized!

I'm thinking of switching to Gradle on a few projects, this looks promising 👀


Add support for MSG200, MLS610, MSS620

When trying to setup the integration, I can retrieve the key, but I keep getting stuck in a loop asking to login. I assume it’s because none of the meross devices I own are currently supported.
hopefully support can be added for  MSG200, garage door opener
MLS610, desk lamp
MSS620, outdoor smart plug

Hello @danielsza,
The devices, even when not supported, should pass the configuration phase since feature identification is done later in code.
If anything is wrong with feature/device recognition this should result in 'incomplete' devices i.e. no entities or misbehaving ones, but the configuration phase would pass anyway since it only checks for basic protocol handling.
The 'loop' is either because the key is wrong or because of a bug in meross_lan config flow handling.
This is what should happen supposing your device is already paired with Meross app and HA prompted you after discovery:

initial configuration panel reports:
key mode: cloud retrieve
device key: empty
when you hit SUBMIT it shows you the cloud login form. After entering valid credentials this form closes and reports back to the main config form with the 'device key' filled with your secret key
when you SUBMIT again, meross_lan checks the key is really correct for the actual device and, if it fails, it brings you to the cloud login form again

So, if you see the 'cloud retrieved key' in place and still you get to the cloud login form, I guess the device is either unpaired or paired to a different meross account.
Could be it ?
To check if the key is correct and avoid the cloud login form you can select 'key mode' = 'user set'. This way no cloud login form or check would happen but the device key you provide must be correct else you'd be stuck again.
If the device is still unpaired you could try set the 'device key' to empty and 'key mode' to 'Hack mode' and see if it pass the configuration phase but this way, even if configuration could pass, the device behaviour would be rather unpredictable (maybe working for some time maybe not at all, random unavailability..and so on)

I double checked the login info, it looks like at some point I had a typo in my email address, and my password manager had both saved.
I was trying to use the incorrect login. Since it did return a key I assumed it was the correct login.
I was able to add all 3 of my devices, and they do seem to correctly add the devices.

On Apr 8, 2022, at 03:22, krahabb @.***> wrote:

Hello @danielsza,
The devices, even when not supported, should pass the configuration phase since feature identification is done later in code.
If anything is wrong with feature/device recognition this should result in 'incomplete' devices i.e. no entities or misbehaving ones, but the configuration phase would pass anyway since it only checks for basic protocol handling.
The 'loop' is either because the key is wrong or because of a bug in meross_lan config flow handling.
This is what should happen supposing your device is already paired with Meross app and HA prompted you after discovery:
initial configuration panel reports:
key mode: cloud retrieve
device key: empty
when you hit SUBMIT it shows you the cloud login form. After entering valid credentials this form closes and reports back to the main config form with the 'device key' filled with your secret key
when you SUBMIT again, meross_lan checks the key is really correct for the actual device and, if it fails, it brings you to the cloud login form again
So, if you see the 'cloud retrieved key' in place and still you get to the cloud login form, I guess the device is either unpaired or paired to a different meross account.
Could be it ?
To check if the key is correct and avoid the cloud login form you can select 'key mode' = 'user set'. This way no cloud login form or check would happen but the device key you provide must be correct else you'd be stuck again.
If the device is still unpaired you could try set the 'device key' to empty and 'key mode' to 'Hack mode' and see if it pass the configuration phase but this way, even if configuration could pass, the device behaviour would be rather unpredictable (maybe working for some time maybe not at all, random unavailability..and so on)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

It is possible that the meross api doesnt report an error when login informations are wrong or (most likely) that you just retrieved informations from a different login than intended
Good this was 'not' an issue ;)


Fix 9604 - sort out upgrade problems

This PR creates a new chart for CRDs.  The CRDs can either be helm templated, or manually applied via kubectl.  This should work for the helm upgrade case and will definitely work for helm template in upgrade modes.
This PR enforces a two-step workflow across all releases independent of the installation model.  One tradeoff is that helm template no longer generates one manifest from the istio.yaml chart.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: sdake
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sdake: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sdake: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sdake: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sdake: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sdake: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-integ-k8s-tests

prow/istio-presubmit.sh
6336b8a5f3dd7b90f5dd38774b73a18170e8d88c
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Pre-GPU Hack Cleanup: Complete hook-in of proj_maxwellian_on_basis and porting to GPUs

proj_maxwellian_on_basis from lab moments (M0, M1i, and M2) is completed and tested on the CPU. Need to:

Complete and test proj_maxwellian_on_basis from plasma frame moments (n, u, T)
Hook-in proj_maxwellian_on_basis to app as a means of specifying the initial conditions (this hook-in will also serve as an example of how to deploy proj_maxwellian_on_basis for other parts of the code such as BGK collisions and neutral interactions)
Port proj_maxwellian_on_basis to GPUs.
Extend proj_maxwellian_on_basis to special relativity and create proj_maxwell_juttner_on_basis. Note: this requires special functions and is only (reasonably) defined in one momentum dimension and three momentum dimensions (fractional MacDonald functions are possible but to my knowledge are not implemented in standard math libraries and likely not worth the trouble here).

This functionality has existed in at least some form for awhile, but I am officially closing this issue especially now with the recent PR: https://github.com/ammarhakim/gkylzero/pull/328
that unifies the relativistic and non-relativistic "Maxwellian" (or in a more formally correct parlance the local thermodynamic equilibrium, LTE) distribution projection on CPUs and GPUs.

@manauref I thought I showed that projection at Gauss-Lobatto nodes is not the same as eval_on_nodes.


Improve perf of noise texture gen in lens and ssao

Use raw texture with a buffer of pixels instead of dynamic texture to render one pixel at a time using canvas.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14300/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14300/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14300/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14300/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14300/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14300/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14300/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14300/merge#BCU1XR#0


suppress gcc warnings about ARM ABI change

This adds the compiler flag -Wno-psabi when building with GCC. This suppresses warnings about an ABI change starting with GCC 10 in C++17 mode on ARM64 that is not relevant, since we always build with the same version of GCC (>10).

/azp run


tt.where does not support divergent types between true_value and false_value

Steps to reproduce
To reproduce the issue, follow the tt.where's docstring but make this replacement:
- m["Paris value"] = tt.where(l["City"] == "Paris", m["Value.SUM"], 0)
+ m["Paris value"] = tt.where(l["City"] == "Paris", m["Value.SUM"], "0")

This will result in a casting error in the java stack. This behavior is against Python's dynamic typing which would have no problem playing with numbers and strings.
Actual Result
Error stacktrace stating a ClassCastException between Number and String
Expected Result
City
London         "0"
Paris         8.00
Environment
Not relevant

After next release, the documentation of tt.where will mention that the two measures must have the same type among :
Numerical
Boolean
Object


Feature Request: Open resource in browser (Azure Portal)

This is autogenerated. Please review and update as needed.
Describe the bug
It would be nice if I am working on a specific azure resource to be able to ask the az-cli to open it in my browser so I can explore/change its settings
Command Name
``
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
``

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.17.1

Additional Context

Please describe the detailed info including CLI commands if this issue is related to Azure CLI.

Please describe the detailed info including CLI commands if this issue is related to Azure CLI.


Adjudicator Dashboard Wireframe - 1st iteration

https://www.figma.com/file/nhOquOVmWD1P3BxEY0KIh5/CCBC-Intake?node-id=198%3A1032 Here is the wireframes for the analyst view, based on the feature map on MIRO.
@marcellmueller @BryanGK  Would someone be able to do a technical feasibility review?

@marcellmueller and @BryanGK , any thoughts here?

@eazeredo It has been resolved during our sprint meeting, I will update the card accordingly.


⚠ Everything Hub has degraded performance

In 89aee00, Everything Hub (https://hub.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 3723 ms

Resolved: Everything Hub performance has improved in 78756f1 after 14 minutes.


hasNotch() return false on Blackview A30

Bug report
hasNotch() return false on Blackview A30

Environment info
"react-native-device-info": "^5.6.1"

react-native info output:
DeviceInfo.hasNotch();
false

Library version: 5.6.1
Summary
The device isn't listed in devicesWithNotch
I found that some others Blackview models have the notch, like BV9600(all versions), please add them too

PRs happily accepted - hasNotch additions are 100% community driven

@pebehb could you attach DeviceInfo.getBrand() and DeviceInfo.getModel() for your device?

@pebehb could you attach DeviceInfo.getBrand() and DeviceInfo.getModel() for your device?

getBrand: "Blackview", getModel: "A30"

you can see the 5.6.4 release for a patch link showing exactly how to PR them


Adds a Rsync recipe, basis for performing repository-related tasks locally

Rsync recipe
Installing
// deploy.php

require 'vendor/deployphp/recipes/recipes/rsync.php';

Configuration options

rsync_excludes (optional): accepts a array with files/dirs to be excluded from sending to server
rsync_user (optional): accepts a string with username to server
rsync_local_release_dir (optional): accepts a string with dirname where temporary repository cloning should take place before being sent to server

// deploy.php

set('rsync_excludes', [
    '.git',
    'deployer_release',
    'releases',
    'deploy.php',
]);

set('rsync_user', 'server_user');

set('rsync_local_release_dir', '/tmp');

Tasks

deploy:local_release Creates local release directory
deploy:update_code overrides standard deploy:update_code to update code locally instead of remotelly
deploy:rsync perorms rsync from local release to remote

Suggested Usage
This recipe performs all repository-related tasks locally, so the best way to use it, would be to use this instead of common.php recipe.
For using composer or other tools, You'd need to override deploy:vendors task and plug it in deploy chain.

Hey, nice recipe!
I have only a couple: current convention for configuration variables is that a recipe uses only one keyword, which is the same name as the recipe itself. The other is that you should not provide a default user.
Configuration (example)
+set('rsync', [
    'excludes' => [
        '.git',
        'deployer_release',
        'releases',
        'deploy.php',
    ],
    'user' => 'server_user',
    'local_release_dir' => '/tmp'
]);

User (example)
if (!get('rsync.user')) {
    throw new \RuntimeException("You need to specify a rsync.user");
}

Thanks for suggestions! Changes are applied in new commit, however, now without specifying username instead of bailing out, we should try to connect without username, as sometimes this is acceptable (whether usernames are configured in ssh config or are same on destination host as on source).

Great! Cool recipe! :beer:

Does this recipe works then you trying to deploy multiple servers in parallel?

Wait a bit before merging that. I have some very nice additions piled up.
technically it SHOULD work... however we have process when we rsync our dev
code to per-dev pre-staging environment, then code goes to repo, then goes
to stating and then goes to one final production. I don't really know how
would this work in parallel, bacause I never had parallels deploy scenario.
2015-06-11 12:46 GMT+02:00 Anton Medvedev<EMAIL_ADDRESS>
Does this recipe works then you trying to deploy multiple servers in
parallel?
—
Reply to this email directly or view it on GitHub
https://github.com/deployphp/recipes/pull/10#issuecomment-111083051.

--
Pozdrawiam,
Hubert Kowalski

@johnny-bit try to deploy it on one server to different deploy_path and run with dep deploy -p.

It seems that it SHOULD work, but parallel deploy in my environment simply
hangs. I even provisioned different hosts to be able to use multiple hosts
and to no avail. It properly synces to multiple hosts in multiple
locations, but I can't get parallel deploy to work. It's either about my
fresh php5.6 or that I don't have suggested modules (i try to have on dev
host only that what's available on staging & production)
2015-06-11 13:53 GMT+02:00 Anton Medvedev<EMAIL_ADDRESS>
@johnny-bit https://github.com/johnny-bit try to deploy it on one
server to different deploy_path and run with dep deploy -p.
—
Reply to this email directly or view it on GitHub
https://github.com/deployphp/recipes/pull/10#issuecomment-111103620.

--
Pozdrawiam,
Hubert Kowalski

Okayy - last commit is rather big, but allows great flexibility when it comes to rsync. Now deploys should be multiple-host-safe with pararell deployments being probably ok.

Nice work! :) Awesome!

So to sum up recent commit:

Fixed documentation as @gordalina suggested
recipe now only exposes one task: rsync

However in making this change I needed to make some decisions due to some time constraints today. Usually there are only one server and one source that would be constant... but what if for one server You'd depoly to /var/www and second to /var/www/vhosts/client_id/site_name/httpdocs/app? What if say with one command You'd want to deploy to one server from devel dir but to second server from locally built release? so I added 2 env vars: rsync_src and rsync_dest that can deal with it.
Now @elfet and @gordalina - how do You like it?

You'd depoly to /var/www and second to /var/www/vhosts/client_id/site_name/httpdocs/app? What if say with one command You'd want to deploy to one server from devel dir but to second server from locally built release? so I added 2 env vars: rsync_src and rsync_dest that can deal with it.

Common recipe based on env var deploy_path, and you should use it too.

Ummm... No.
deploy_path fails short.
Reasons:

deploy_path is for example /var/www/vhosts/site. However since we're doing releasey stuff, actuall content is in /var/www/vhosts/site/current. Well, that's a symlink, so it's actually in /var/www/vhosts/site/releases/[release_date]. If we were to rsync stuff using delete flag, then actual conent would go in /var/www/vhost/site but due to delete flag so popular with rsync, current and releases would vanish. So You'd need to use release_path
We're doing al releasey stuff locally, for dev previews. But using convention we're specyfing deploy_path to be actual path to what we're syncing. Since there's no releasey stuff going on on remote, using previous release_path would yeld incorrect path for rsync. So... Need to use deploy_path.
Say you'd need to rsync some misc files after deploy, but with nice rsync capabilities and you're DevOps spec. Files You're syncing are relative to deploy_path but are not kept in versioning system, maybe they're sensitive (happened couple times to me when deploying domain-registrar stuff). So neither deploy_path nor release_path are okay in this case. Actually maybe You could use {{deploy_path}}/../../secure/devops/{{server.host}}/ and set it as rsync_dest and be done with it?

You see: I'm all for that super nice and super nifty flexibility. That way You can allow anybody using this recipe to have one command rsync tool that can do anything normal rsync can without having to specify advanced magic every time.
Look at it this way: Due to way of how I set it, it's most flexible rsync tool that would allow anybody to take advantage of rsync in any way they could come up with :smile_cat:

Correct, what about using just release_path? :) Do not try to cover 100% usage on rsync =)
User can implement this it self. But having deploy:update_code which using rsync will be nice :+1:
@gordalina ?

Well: my point is exactly not covering 100% possible usage, but instead
allow user to implement everything rather easily :) Using release_path
might be ok, but it would mess bot non-deployment workflow and
deployment-relative workflow :)
Trade-offs everywhere, but I personally really hate situation when I need
to create tremendous workaround just because creator hardcoded something
instead of allowing config.
Thoughts @gordalina ?

Looks good to me! I kinda like that it is flexible enough to do other rsync stuff, not only the repository itself.
@elfet do you have any other issues?

I've split config & environment variables. How does it look now?

@elfet do you have any concerns about this, or can it be merged?

Everything look cool! Lets merge it!
PS we a need some page on deployer.org with info about this recipes with docs.

@elfet that's on #8 but I haven't had the time for that, maybe @johnny-bit is interested in doing that?


fullscreen triangle optimization

Seems using only one fullscreen triangle would have some performance gains. Does it also apply to our situation?
Learn more: https://github.com/mrdoob/three.js/pull/21358

This is a great recommendation for the minimal renderer! For the three.js plugin, I don't think it'd make sense because people might want to be able to include their shaders w/ other geometry, but in this context it fits really well.
We were hoping to add mouse controls to the minimal renderer at some point to have similar functionality to OrbitControlls in Three.js. Not sure if switching this to a full-screen triangle rules out that option, but I guess you can always make virtual camera controls within the shader. What are your thoughts @PWhiddy

That's sounds interesting, glad to know it. I also have a similar idea during reading the targets/threeJS and targets/minimalRenderer solution. If it may be difficult to integrate them in the future, feel free to close this PR. Thanks!

This seems like a fine change to me!
Tests seemed to pass fine, @TomHsiao1260 did you also check the rendering looks the same?
Quickest way to check is if you run yarn/npm test locally, some images will be rendered to the folder test/out. If those look normal happy to merge :)

Hi, after comparing them, they're mostly the same except for two of them may be different because of noise. Not sure if this is normal. Here's the different:
looper.png

rotateBoxes.png

That looks fine to me, I'm guessing they just show up different because they are animated with time and the page loads/screenshot happens at slightly different times on each run.
Thanks!


Double dashes sent from source protocols are modified to contian only one single dash when received in matrix

Describe the bug
I bridge matrix, telegram, irc, mattermost and xmpp which is working in all combinations. Today we had an user sending a link where the url contained a double dash. Which was relayed as a single dash in the resulting formatted body on matrix side. We noticed that because the link on matrix side was invalid in the first place. I could reproduce that with regular text as well, but hence that is no klickable link it hadn't hardly ever be noticed by us before:
{
  "content": {
    "body": "[X@telegram] --",
    "format": "org.matrix.custom.html",
    "formatted_body": "[X@telegram] –",
    "msgtype": "m.text"
  }

To Reproduce

Bridge telegram, xmpp, irc, mattermost and matrix
Send amessage containing a double dash

Expected behavior

in matrix, you will see a message that contains the double dashes in both the formatted body, as well as in the unformatted body.

Screenshots/debug logs
Matterbridge log entry (with the essential content):
[0766] DEBUG gateway:      => Sending config.Message{Text:"http://bla--blubb.de", Channel:"12345", Username:"X", UserID:"12334566898", Avatar:"", Account:"telegram.foobar", Event:"", Protocol:"telegram", Gateway:"foobar", ParentID:"", Timestamp:time.Time{wall:0xbf7f0260626765d3, ext:766545225763, loc:(*time.Location)(0x55957af0cfc0)}, ID:"14100", Extra:map[string][]interface {}{}} from telegram.foobar (12345) to matrix.foobar (#foobarchat:matrix.org)
[0766] DEBUG matrix:       => Receiving config.Message{Text:"http://bla--blubb.de", Channel:"#foobarchat:matrix.org", Username:"[X@telegram] ", UserID:"12334566898", Avatar:"", Account:"telegram.foobar", Event:"", Protocol:"telegram", Gateway:"foobar", ParentID:"", Timestamp:time.Time{wall:0xbf7f0260626765d3, ext:766545225763, loc:(*time.Location)(0x55957af0cfc0)}, ID:"", Extra:map[string][]interface {}{}}
[0766] DEBUG matrix:       Channel #foobarchat:matrix.org maps to channel id !abcdefgh:matrix.org
[0767] DEBUG gateway:      mID matrix.foobar: $TK1jTFV6EHroKM9AwDBNPCzhram1GHwu06U6y-J3nYo
[0767] DEBUG matrix:       == Receiving event: &gomatrix.Event{StateKey:(*string)(nil), Sender:"@foobarchat:matrix.org", Type:"m.room.message", Timestamp:1578865153667, ID:"$TK1jTFV6EHroKM9AwDBNPCzhram1GHwu06U6y-J3nYo", RoomID:"!abcdefgh:matrix.org", Content:map[string]interface {}{"body":"[X@telegram] http://bla--blubb.de", "format":"org.matrix.custom.html", "formatted_body":"[X@telegram] http://bla–blubb.de", "msgtype":"m.text"}, Redacts:"", Unsigned:map[string]interface {}{"age":909, "transaction_id":"go1578865153625906564"}}

Environment (please complete the following information):

OS: host is debian, using official docker image 42wim/matterbridge:latest (the version you made for #969)
Matterbridge version: version: 1.16.4-dev 31dd538c

Additional context,
[general]
<EMAIL_ADDRESS>MediaServerDownload="https://myurl.eu/"
RemoteNickFormat="[{NICK}@{PROTOCOL}] "
#OPTIONAL (default 1000000 (1 megabyte))
MediaDownloadSize=100000000

[irc]
    [irc.freenode]
    Server="irc.freenode.net:6667"
    Nick="schraddelblinkundbuntChat"
    MessageSplit=true
    Charset="utf-8"

[mattermost]
    [mattermost.schraddelblinkundbunt]
    Server="chat.schraddelblinkundbunt.de"
    Team="schraddelblinkundbunt"
    Token="foobarbaz"
    PrefixMessagesWithNick=true

[xmpp]
    [xmpp.schraddelblinkundbunt]
    Server="jabber.schraddelblinkundbunt.de"
<EMAIL_ADDRESS>    Password="foobarbaz"
    Muc="conference.jabber.schraddelblinkundbunt.de"
    Nick="schraddelblinkundbuntChat"

[telegram]
    [telegram.schraddelblinkundbunt]
    Token="foobarbaz:foobarbaz"
    UseFirstName=true

[matrix]
    [matrix.schraddelblinkundbunt]
    Server="https://matrix.org"
    Login="schraddelblinkundbuntchat"
    Password="foobarbaz"
    NoHomeServerSuffix=true

[[gateway]]
name="schraddelblinkundbunt"
enable=true
    [[gateway.inout]]
    account="irc.freenode"
    channel="#schraddelblinkundbunt"

    [[gateway.inout]]
    account="mattermost.schraddelblinkundbunt"
    channel="foobarbaz"

    [[gateway.inout]]
    account="xmpp.schraddelblinkundbunt"
    channel="foobarbaz"

    [[gateway.inout]]
    account="telegram.schraddelblinkundbunt"
    channel="-1234567889"

    [[gateway.inout]]
    account="matrix.schraddelblinkundbunt"
    channel="#schraddelblinkundbuntchat:matrix.org"

[[gateway]]
name="foobarbaz"
enable=true
    [[gateway.inout]]
    account="mattermost.schraddelblinkundbunt"
    channel="foobarbaz"

    [[gateway.inout]]
    account="xmpp.schraddelblinkundbunt"
    channel="foobarbaz"

    [[gateway.inout]]
    account="telegram.schraddelblinkundbunt"
    channel="-928320948309585"

[[gateway]]
name="foobarbaz"
enable=true
    [[gateway.inout]]
    account="xmpp.schraddelblinkundbunt"
    channel="foobarbaz"

    [[gateway.inout]]
    account="telegram.schraddelblinkundbunt"
    channel="-09328402947"

    [[gateway.inout]]
    account="matrix.schraddelblinkundbunt"
    channel="#foobarbaz:matrix.org"

Related to #924

Hasn't that been fixed long ago?

Related to #989 and fixed in master in a few minutes.


Data interface for querying is not available anymore in 0.8.5

I've just upgraded InfluxDB from 0.8.2 to 0.8.5, and when I enter InfluxDB administration ui on port 8083, there is no item available in the "Interfaces" menu, so I cannot access the data interface to run my InfluxDB queries.
In InfluxDB v0.8.2, I could go to the InfluxDB query data interface by selecting "Default" in the "Interfaces" menu.
I tried to investigate this issue with the firefox developer tools, and when I log in, the "/interfaces" url is requested but returns error 400 "Bad request", as you can see in the following screenshot:

If I try to open this "/interfaces" url in a new tab, I get: "open interfaces: no such file or directory"

@JulienChampseix using 0.8.8 I wondering if I am not having the same issue? I cannot access the web interface from a remote server or any other influx ports remotely? Was trying to pus graphite data into port 2003. The web interface works great local but all off the ports for influxdb seem closed? I wrote some testing code to try and connect to server ports. Port 80 is open however none of the ports are open for influx. Sorry if I should of posted to another thread.

@mkarquette that sounds like an issue with your setup. Make sure you have the ports open.

Paul I think you are correct I a missing a concept here about influxdb.
all of the other ports appear open as iptables off etc.
also here is a little test script I ran from another server to check.
def checkPort (hostIn, portIn):
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
result = sock.connect_ex((hostIn,portIn))
if result == 0:
print "Port is open"
else:
print "Port is not open"
checkPort("<IP_ADDRESS>", 8083)
checkPort("<IP_ADDRESS>", 8086)
checkPort("<IP_ADDRESS>", 80)
checkPort("<IP_ADDRESS>", 443)
output is
Port is not open
Port is not open
Port is open
Port is open
Process finished with exit code 0
here is info from config.toml
bind-address = "<IP_ADDRESS>"
[admin]
port   = 8083
[api]
port     = 8086
note if I shutdown influx. with
server influxdb stop
then
I run a test server I wrote on the same server as influxdb using the same ports the ports accept connections fine.
so it must be something I am missing in the config.toml setup? Note --  I had to config the etc/hosts and hostname on this server so this server doesn't show up in dns. Also the host name will have a local domain ext.

also I should get into the support group and stop posting to this thread as well!!!


Active Links for education

More information here:
https://discourse.gohugo.io/t/difficulty-making-active-links/10452/4
Purpose
Allow links in the education section

The name of an institution is text, not Markdown. However, I have opened #1094 to consider adding more flexibility, such as a url field.


Governance is Contrary to Bitcoin's Purpose

Bitcoin's purpose is to resist change—its design relies on a decentralized, consensus-driven resistance to alterations, which helps ensure its robustness and security. Any attempts to organize governance, whether through stakeholder hierarchies or formalized processes, inherently risk undermining this very resilience. By establishing governance structures, power consolidates, making Bitcoin more vulnerable to centralization and censorship.
Bitcoin is designed to minimize trust through incentive alignment, ensuring the system is both resilient and hard to change. Introducing formal governance reintroduces trust and decision-making power to human actors, which inherently increases opportunities for coercion and corruption—opposing Bitcoin’s core principle of minimizing trusted intermediaries.
The equilibrium that Bitcoin maintains emerges because changes require overwhelming consensus, which maximizes the cost of any alteration. Formalized governance mechanisms lower this cost by concentrating decision-making, making it easier for well-resourced actors to influence or capture the system. Maintaining decentralized equilibrium, where actors are disincentivized to make arbitrary changes, is key to maintaining robustness.
In Bitcoin, distinguishing between a beneficial change, a naive speculative risk, and a malicious intent is often impossible. What seems like an improvement to one stakeholder could appear as a threat to another, particularly when differing incentives are at play. Introducing more governance only amplifies these subjective disagreements, turning the process into a power struggle. Instead of naturally filtering out bad ideas through decentralized consensus, formal governance introduces a mechanism that can be captured, directed, and ultimately wielded for control.
BCAP’s treatment of governance risks missing Bitcoin's core philosophy—that more governance implies more opportunities for centralization, coercion, and censorship. Bitcoin thrives on minimizing trust and resisting organized control, and efforts to formalize governance contradict these foundational principles.
 Be appropriately humble about this power.

I agree with your view but need help seeing how it applies to BCAP. It is a
non-goal of BCAP to be bitcoin's governance or to be prescriptive about
consensus changes. The only use of the term "governance" is explicitly
saying bitcoin doesn't have governance. Namely, "Bitcoin consensus change
is not achieved through formal governance but through a complex interplay
of actions and reactions among stakeholders"
Can you point out specific areas where BCAP strays from this and risks the
point you're making?
On Thu, Nov 7, 2024 at 2:46 PM John Carvalho @.***>
wrote:

Bitcoin's purpose is to resist change—its design relies on a
decentralized, consensus-driven resistance to alterations, which helps
ensure its robustness and security. Any attempts to organize governance,
whether through stakeholder hierarchies or formalized processes, inherently
risk undermining this very resilience. By establishing governance
structures, power consolidates, making Bitcoin more vulnerable to
centralization and censorship.
Bitcoin is designed to minimize trust through incentive alignment,
ensuring the system is both resilient and hard to change. Introducing
formal governance reintroduces trust and decision-making power to human
actors, which inherently increases opportunities for coercion and
corruption—opposing Bitcoin’s core principle of minimizing trusted
intermediaries.
The equilibrium that Bitcoin maintains emerges because changes require
overwhelming consensus, which maximizes the cost of any alteration.
Formalized governance mechanisms lower this cost by concentrating
decision-making, making it easier for well-resourced actors to influence or
capture the system. Maintaining decentralized equilibrium, where actors are
disincentivized to make arbitrary changes, is key to maintaining robustness.
In Bitcoin, distinguishing between a beneficial change, a naive
speculative risk, and a malicious intent is often impossible. What seems
like an improvement to one stakeholder could appear as a threat to another,
particularly when differing incentives are at play. Introducing more
governance only amplifies these subjective disagreements, turning the
process into a power struggle. Instead of naturally filtering out bad ideas
through decentralized consensus, formal governance introduces a mechanism
that can be captured, directed, and ultimately wielded for control.
BCAP’s treatment of governance risks missing Bitcoin's core
philosophy—that more governance implies more opportunities for
centralization, coercion, and censorship. Bitcoin thrives on minimizing
trust and resisting organized control, and efforts to formalize governance
contradict these foundational principles.
 Be appropriately humble about this power.
—
Reply to this email directly, view it on GitHub
https://github.com/bitcoin-cap/bcap/issues/26, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACPUA4SOXUIY7A3YIDBCSDZ7PUSTAVCNFSM6AAAAABRMIAQECVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY2DEMZYGAZDGMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

All speculative changes to Bitcoin require governance; they are an oppressive abuse of user trust.
I fundamentally disagree with the naive concepts of "building consensus", convenient appeals to "game theory", and all speculative complexity, and feel such perspectives are ignored, which, to me, says a lot about motives.
To me, BCAP presents as an attempt to codify the system through a biased set of narratives, ultimately serving a purpose of templating that can be referenced in arguments for changes to Bitcoin.
My ideal, responsible version of this document would be starkly more conservative, cautionary, and using only accepted economic and network dynamic concepts.
I know most of the people involved meant well, but the conservative rational views required for this are missing, and people like Eric Voskuil should have been leading/consulting on this.

"speculative changes"

What makes a change speculative? Or rather, what is a non-speculative change?

"more conservative"

Can you point out examples of where BCAP is too progressive or aggressive?

"more cautionary"

The one future scenario soft fork is dedicated to being cautionary. It describes how we could wind up with a fragile network as a cautionary tale to avoid it. Where and how would you suggest more caution?

"using only accepted economic and network dynamic concepts"

Which accepted economic and network dynamic concepts would you like to see added?

"speculative changes"

What makes a change speculative? Or rather, what is a non-speculative change?

"more conservative"

Can you point out examples of where BCAP is too progressive or aggressive?

"more cautionary"

The one future scenario soft fork is dedicated to being cautionary. It describes how we could wind up with a fragile network as a cautionary tale to avoid it. Where and how would you suggest more caution?

"using only accepted economic and network dynamic concepts"

Which accepted economic and network dynamic concepts would you like to see added?

A speculative change is the kind based on (imaginary) game theory and "incentive-compatibility" or other non-data-driven excuses for change. Such changes attempt to predict the future with loose undefined/theoretical models, and often obnoxious degrees of complexity that we could have no hope of assessing second-order effects of.
The opposite could be a "substantiated" change, or "evidence-based" or such, where an overwhelming amount of research and data is shown to prove the demand, appropriateness, and fitness for a specific change. Non-speculative changes should be responses to evident problems that threaten core functionality, rather than a desire to iterate or experiment.

Can you point out examples of where BCAP is too progressive or aggressive?

Maybe start with the entire framing that defaults to entertaining new features instead of questioning if they should exist at all. (Try feeding all my comments into AI and having it review the doc, I'm not going to make pull requests here.)

The one future scenario soft fork is dedicated to being cautionary. It describes how we could wind up with a fragile network as a cautionary tale to avoid it. Where and how would you suggest more caution?

Caution isn’t about one chapter of concern; it’s about every step having a presumption of resistance, and every proposal being an attack on consensus. BCAP could be explicit about this.

Which accepted economic and network dynamic concepts would you like to see added?

I'm not an expert in either, so I might suggest finding some; I just know enough from Cryptoeconomics and other Systems experience to see that there is a higher academic and axiomatic way to approach these topics. You at least have many actual game theory concepts that could be specified and presented as proofs. You at least have Cryptoeconomics and the author willing to respond to questions.

I agree BCAP should not be framed in a way that suggests changing bitcoin is the default. However, I don't agree that it is framed that way. I am sure there are specific wordings we could change to improve, but I don't see any of them suggested in this issue. Don't see anything actionable so will close.


Mobile Navigation Cleanup

Before launch, we need to make sure the mobile navigation is finished and cleaned up
Fixing spacing issues like this

Fixing my initial range UI (we can do a lot better)

There are type errors showing up for bus navigation on mobile


[Feat] : Auth Slice

Description
Auth slice for state Management

@MAVRICK-1 Please assign me under GSSOC24

#40 Please review the PR!


Moved to a more structured hierarchy

With this structure every exception thrown by the key value store is marked with a specific interface.
Use case:
try {
    // extract values from a DBAL storage
} catch (\Doctrine\KeyValueStore\Exception\NotFoundException $e) {
    // data not found
} catch (\Doctrine\KeyValueStore\Storage\Exception\Exception $e) {
    // generic storage-level exception
} catch (\Doctrine\KeyValueStore\Exception\RuntimeException $e) {
    // EntityManager or UnitOfWork runtime exception (extends \RuntimeException)
} catch (\Doctrine\KeyValueStore\Exception\Exception $e) {
    // EntityManager or UnitOfWork exception (extends \Exception)
} catch (\Doctrine\KeyValueStore\Exception $e) {
    // generic key value store exception
} catch (\Exception $e) {
    // generic exception
}

This is a RFC with the basic structure only, later I'll add message methods (following this article) and tests.

ping @Ocramius @beberlei