Localized string not found

I've implemented LiveChat in ios. when I'm going to upload an attachment then got options from where we can upload an attachment. There are showing "localized string not found" on camera and gallery options. like following attachment.

Hi @rupeshmishra90 could you please provide more details on how did you integrate the widget? What are the languages supported by your app? On this screen there are two languages mixed together which is odd. I tested that on our end and the widget in an app supporting Spanish (if I'm not mistaken) language looks like this. All the options are properly translated.

Hi @rupeshmishra90 could you please provide more details on how did you integrate the widget? What are the languages supported by your app? On this screen there are two languages mixed together which is odd. I tested that on our end and the widget in an app supporting Spanish (if I'm not mistaken) language looks like this. All the options are properly translated.

I'm using spanish and english in my application. I' facing issue in case of spanish

Please provide me solution.

@rupeshmishra90 could you please provide a minimal example reproducing this issue? It works perfectly fine on our end.

@rupeshmishra90 could you please provide a minimal example reproducing this issue? It works perfectly fine on our end.

Using following reference to use
https://developers.livechat.com/docs/getting-started/installing-livechat/ios-widget/

Example-Swift.zip

check this

I've put strings key value but not reflected
"Browse" = "Vistazo";

Please provide a solution we are struck on it

@rupeshmishra90 the problem starts with this method Bundle.swizzleLocalization() when you will comment out this part the image selection UI starts working as expected. However I feel like this is not your real issue. You just want to see the entire chat widget translated to Spanish, am I correct?

Yes, I want to see the entire chat widget translated to Spanish

@rupeshmishra90 you can set the widget language in the agent app settings. Please let me know if that solves your problem.

Can we set multiple language from here?

I have a doubt if there are two users and one using english language and other using spanish then which language we have to set here.

@rupeshmishra90 the dynamic language setting is not currently supported in our widget. Please file a separate ticket with a feature request so we will be able to proceed further.

Closing as clarified.

Hi, I'm facing localized string not found issue in chat page
I have used 3 languages in my App
Added strings in localised file like below
"Photo Library" = "Photo Library";
"Choose Files" = "Choose Files";

"Choose Files" = "Photothèque";
"Choose Files"= "Choisir des fichiers";

"Photo Library" = "फोटो लाइब्रेरी";
"Choose Files" = "फ़ाइलें चुनें";

PFA, please anyone help me
Thanks in advance

Hi,
Is this chat support any third party or created by you.
If it's a third party then please ask them to take title from your side.
On Wed, 5 Jan 2022, 7:29 pm Prabakaran M, @.***> wrote:

Hi, I'm facing localized string not found issue in chat page
I have used 3 languages in my App
Added strings in localised file like below
"Photo Library" = "Photo Library";
"Choose Files" = "Choose Files";
"Choose Files" = "Photothèque";
"Choose Files"= "Choisir des fichiers";
"Photo Library" = "फोटो लाइब्रेरी";
"Choose Files" = "फ़ाइलें चुनें";
PFA, please anyone help me
Thanks in advance
[image: Simulator Screen Shot - iPhone 12 - 2022-01-05 at 15 32 49]
https://user-images.githubusercontent.com/44673016/148228831-f7abc664-3ca9-4be8-8339-3cf8121bedd7.png
—
Reply to this email directly, view it on GitHub
https://github.com/livechat/chat-window-ios/issues/68#issuecomment-1005708771,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGF7WHPKCCCXAZJZJDETZRDUURFEXANCNFSM4QJKONWA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @rupeshmishra90 , Can you please let me know what is the issue there, then how to fix it
For me still this issue is open

Hi @kamil-szostakowski I'm facing that localised string not found issue, how to solve this?

You need to ask with livechat team.
They said that you need to create two channels like one for English and
second for other language and redirect accordingly.
On Tue, 18 Jan 2022, 10:30 am Prabakaran M, @.***>
wrote:

Hi @kamil-szostakowski https://github.com/kamil-szostakowski I'm facing
that localised string not found issue, how to solve this?
—
Reply to this email directly, view it on GitHub
https://github.com/livechat/chat-window-ios/issues/68#issuecomment-1015072091,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGF7WHOASMYXOZYS42F7A3DUWTXWNANCNFSM4QJKONWA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Okay @rupeshmishra90
Any options to show English only, is this possible
I mean if I changed English to French in my App Chat page will show only English

You can change to create Chanel with lagenge French
On Tue, 18 Jan 2022, 2:57 pm Prabakaran M, @.***> wrote:

Okay @rupeshmishra90 https://github.com/rupeshmishra90
Any options to show English only, is this possible
I mean if I changed English to French in my App Chat page will show only
English
—
Reply to this email directly, view it on GitHub
https://github.com/livechat/chat-window-ios/issues/68#issuecomment-1015222982,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGF7WHP6SF6UYISW2543FQLUWUW7TANCNFSM4QJKONWA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Okay, in Chat admin panel right?

Yes, that's right.
On Tue, 18 Jan 2022, 3:40 pm Prabakaran M, @.***> wrote:

Okay, in Chat admin panel right?
—
Reply to this email directly, view it on GitHub
https://github.com/livechat/chat-window-ios/issues/68#issuecomment-1015259057,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGF7WHLQJFWTJ5ETLAUF5KDUWU4CBANCNFSM4QJKONWA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

I have removed other language strings from my App, added English text alone like below, but still I'm facing same issue
// ---- Live Chat Bot -----//
"PHOTO_LIBRARY" = "Photo Library";
"Choose Files" = "Choose Files";

@rupeshmishra90 I have shared my source code please check below link
https://we.tl/t-keQwcehToc


Add debugLogging field to flagSourceConfiguration

Add a bool field to the FlagSourceConfguration CRD to control the addition of the --debug flag to the injected sidecar

Good idea.

I would like to tackle this ticket

surely, thank you!

Insights from discussion between me and @toddbaert, afterwards also with @thisthat and @bacherfl  :
Adding this new field for flag enabling is an awesome idea. Additional to that, we discussed the possibility to also add an additional field for direct argument passing to the injected sidecar.
We agreed that the best approach would be to have a list of "strong" flags (like debugLogging) which will have their place in the CRD spec and can be enabled/disabled via this parameter, but additionally introduce a rawSidecarArgs field for the flexibility of adding needed flags. This field can be very useful for development reasons/debugging or adding some advanced flags from the users.
We are open for any additional suggestions/concerns from the community!

introduce a rawSidecarArgs field

I think this is a good idea. 👍

Just for my understanding, is the idea to use rawSidecarArgs to pass any random side-car (flagd) accepted flag ?

Just for my understanding, is the idea to use rawSidecarArgs to pass any random side-car (flagd) accepted flag ?

Exactly, a good use case would be a need to debug some issues and enable advanced logging in flagD. Therefore there is no need to adapt the OF operator, the developer/user can pass these parameters via FlagSourceConfiguration. I think we use the same approach already with provider arguments in FlagSourceConfiguration CRD.


How to use Iceberg to operate lakefs

How to use Iceberg to operate lakefs like work with hadoop?

Hi @winyluo !
There is an open issue of Iceberg documentation which is currently in progress.
Please refer to #3451

Hi @winyluo! Please see the updates on https://github.com/treeverse/lakeFS/issues/3451#issuecomment-1230482658.
We will be happy to learn more about your use case. How would you like to see lakeFS working with Iceberg? any feature request will be appreciated.

Apart from existing docs as mentioned above and #4360, we are now in motion to implement Iceberg directly in lakeFS.  Current design is #5825.
So closing, but this train is arriving!


Ability to compile to wasm/wasi

ability to compile the tools to wasm/wasi if possible.  It currently fails for E0554.

Would you like to contribute this feature? I'm very open to prs.

Ok will do. not an expert in rust but I can give it a try.  It may not be possible if the issue is with one of the dependencies which I think is the case.  If the library uses any socket/network, it can't be compiled to wasi.  I can at least collect the information.


Add a possibility to tag the Wiki Updater commit

Azure DevOps Extension you are using
Wiki Updater
Where are you running it?

Azure DevOps Service (VSTS)

Version of Extension/Task

Latest public

Expected behaviour and actual behaviour
The Wiki Updater task is at the end of my release pipeline.
I tag my repositories (git version tag)
There is currently inconsistency in my tags and changelog update. Given the fact that the last commit comes from Wiki Updater tasks.
My request is, to add the possibility for a lightweight tag in this task. Something like:
GitWikiFuntions.ts L136+
if (tagRepo) {
 await git.addTag(tagname);
 await git.pushTags();
}

Let me know your thoughs
Note: I tried some other extensions but they tag artifacts, which finds the last commit for tagging (which is prior the Wiki Updater tasks). So that did not solve my issue.

Seems a reasonable enhancement, I have put it on the backlog. I am not sure when I will get to it, but always happy to consider PRs

I had a bit of time, so added the feature. It is released in 1.7.5. It is basically the logic you suggested with  the wiring to manifest.


Changed bitmap back to image

Because there is a file type called bitmap and this will get confusing later on

Thank You!


A bug in macro placement increases the time spent in cts phase

Describe the bug
The bug that was fixed by #4704 caused a huge increase of time spent in cts stage on ariane133 design. Before the bug, the cts took about 15 minutes (on my local computer). Then it increased even to 5h (measured on https://github.com/The-OpenROAD-Project/OpenROAD/commit/200ff70dc0247482a47db794c3d036ef903d58a7). After #4704 it was back to normal ( 13:17 on https://github.com/The-OpenROAD-Project/OpenROAD/commit/ca905ef938aa034def65cfbe2e1d977945b178a0). Now, after #4768, the problem occurs again.
Expected Behavior
I expected that the cts phase takes similar amount of time as before the bug.
Environment
Git commit: fa563246a82355a196feea4d0986a522769f3432
kernel: Linux 5.10.0-28-amd64
os: Debian GNU/Linux 12 (bookworm)
cmake version 3.25.1
-- The CXX compiler identification is GNU 12.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- OpenROAD version: v2.0-12514-gfa563246a
-- System name: Linux
-- Compiler: GNU 12.2.0
-- Build type: RELEASE
-- Install prefix: /usr/local
-- C++ Standard: 17
-- C++ Standard Required: ON
-- C++ Extensions: OFF
-- The C compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found Python: /usr/bin/python3 (found version "3.11.2") found components: Interpreter
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Performing Test C_COMPILER_SUPPORTS__-Wall
-- Performing Test C_COMPILER_SUPPORTS__-Wall - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wall
-- Performing Test CXX_COMPILER_SUPPORTS__-Wall - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-array-bounds
-- Performing Test C_COMPILER_SUPPORTS__-Wno-array-bounds - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-array-bounds
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-array-bounds - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-nonnull
-- Performing Test C_COMPILER_SUPPORTS__-Wno-nonnull - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-nonnull
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-nonnull - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-maybe-uninitialized
-- Performing Test C_COMPILER_SUPPORTS__-Wno-maybe-uninitialized - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-maybe-uninitialized
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-maybe-uninitialized - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format-overflow
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format-overflow - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format-overflow
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format-overflow - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-variable
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-variable - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-variable
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-variable - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-function
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-function - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-function
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-function - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-write-strings
-- Performing Test C_COMPILER_SUPPORTS__-Wno-write-strings - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-write-strings
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-write-strings - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-sign-compare
-- Performing Test C_COMPILER_SUPPORTS__-Wno-sign-compare - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-sign-compare
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-sign-compare - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-deprecated
-- Performing Test C_COMPILER_SUPPORTS__-Wno-deprecated - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-deprecated
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-deprecated - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-c++11-narrowing
-- Performing Test C_COMPILER_SUPPORTS__-Wno-c++11-narrowing - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-c++11-narrowing
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-c++11-narrowing - Failed
-- Performing Test C_COMPILER_SUPPORTS__-Wno-register
-- Performing Test C_COMPILER_SUPPORTS__-Wno-register - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-register
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-register - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format - SucCMake Error at src/CMakeLists.txt:242 (find_package):
  By not providing "Findspdlog.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "spdlog", but
  CMake did not find one.

  Could not find a package configuration file provided by "spdlog" with any
  of the following names:

    spdlogConfig.cmake
    spdlog-config.cmake

  Add the installation prefix of "spdlog" to CMAKE_PREFIX_PATH or set
  "spdlog_DIR" to a directory containing one of the above files.  If "spdlog"
  provides a separate development package or SDK, be sure it has been
  installed.

cess
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal
-- Performing Test C_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal - Failed
-- Performing Test C_COMPILER_SUPPORTS__-fpermissive
-- Performing Test C_COMPILER_SUPPORTS__-fpermissive - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-fpermissive
-- Performing Test CXX_COMPILER_SUPPORTS__-fpermissive - Success
-- Performing Test C_COMPILER_SUPPORTS__-x
-- Performing Test C_COMPILER_SUPPORTS__-x - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-x
-- Performing Test CXX_COMPILER_SUPPORTS__-x - Failed
-- Performing Test C_COMPILER_SUPPORTS__c++
-- Performing Test C_COMPILER_SUPPORTS__c++ - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__c++
-- Performing Test CXX_COMPILER_SUPPORTS__c++ - Failed
-- Performing Test C_COMPILER_SUPPORTS__-std=c++17
-- Performing Test C_COMPILER_SUPPORTS__-std=c++17 - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-std=c++17
-- Performing Test CXX_COMPILER_SUPPORTS__-std=c++17 - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-but-set-variable
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-but-set-variable - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-but-set-variable
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-but-set-variable - Success
-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
-- TCL header: /usr/include/tcl/tcl.h
-- TCL readline library: /usr/lib/x86_64-linux-gnu/libtclreadline.so
-- TCL readline header: /usr/include/x86_64-linux-gnu
-- Found SWIG: /usr/bin/swig4.0 (found suitable version "4.1.0", minimum required is "4.0")
-- Using SWIG >= 4.1.0 -flatstaticmethod flag for python
-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.81.0/BoostConfig.cmake (found version "1.81.0")
-- boost: 1.81.0
-- Found Python3: /usr/include/python3.11 (found version "3.11.2") found components: Development Development.Module Development.Embed
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.13")
-- Configuring incomplete, errors occurred!

To Reproduce
In OpenROAD-flow-scripts/flow directory:
make DESIGN_CONFIG=./designs/nangate45/ariane133/config.mk clean_cts cts
Relevant log output
No response
Screenshots
No response
Additional Context
I noticed the error in openroad-env.log. I don't have it when I run cmake. Anyway, I suspect that it is not relevant in this issue.

Ok, thanks for the information.


Use of hard-coded passwords and HTTP without TLS

Greetings,
I am a security researcher, who is looking for security smells in Puppet scripts.
I noticed instances of hard-coded passwords, which are against the best practices
recommended by Common Weakness Enumeration (CWE) [https://cwe.mitre.org/data/definitions/259.html] and also by other security practitioners.
I suggest use of hiera to mitigate this smell. Feedback is welcome.
Pull request: https://github.com/aeolusproject/aeolus-configure/pull/31

Greetings,
I am a security researcher, who is looking for security smells in Puppet scripts. I found instances where the HTTP protocol is used instead of HTTPS (HTTP with TLS). According to the Common Weakness Enumeration organization this is a security weakness (https://cwe.mitre.org/data/definitions/319.html).  I was wondering why HTTP is used? Is it because of lack of tool support?
I am trying to find out if developers are forced to adopt bad practices due to lack of tool support when it comes to the HTTPS protocol. Maybe it is due to dependency on a resource that uses HTTP?
Any feedback is appreciated.
Source: https://github.com/aeolusproject/aeolus-configure/blob/master/recipes/aeolus/manifests/iwhd.pp (Line#60)


app:rating="3.1"   only show three star ?

@andansky Yes. This is intended. The view is rounding values with precision 0.5 as there are half stars. So if you put value more than 3.25 and less than 3.75 you'll get 3 full and 1 half start for instance.


Add PdfLoader

This pull request introduces a new PdfLoader class to the project. The PdfLoader class is responsible for loading PDF documents and converting them into a list of Document objects. This is achieved by using the Apache PDFBox library to read the PDF file and extract the text.

Closing this and will create a new one as wrong account was used


add 《Designing Data-Intensive Application》Chinese translate

add 《Designing Data-Intensive Application》Chinese translate

This is an unofficial translation of a non-free book (there is an official translation, too: https://item.jd.com/12437624.html). If we are to list it, we should include the name of the original author, the name of the translator, and a label indicating it is an independent translation.

I guess this PR should be closed.
As it is neither a free book nor official translation.


Implement best practices for efk-stack-app app

Coming from here.
The goal of this issue is to have the App eventually adhere to standard cloud-native best-practices. The points below are to be considered non-exhaustive. Feel free to add some that make sense and remove some that don't. If this issue does not make sense (e.g. is a duplicate or covers a deprecated app) please close it.
Expected outcome:

[ ] the app has properly set PDBs (as percentages)
[ ] the app can scale horizontally based on Custom Metrics (if it makes sense)
[ ] the app runs with more than 1 replica by default (if it needs HA)
[ ] the app does not use emptyDir volumes if not strictly necessary

@TheoBrigitte EFK is deprecated, closing


[AdvancedSearch] Regression - Scope should be optionnal in ListSummary

Current behaviour
When the scope is not define we got an exception in _getScopeLabel of ListSummary
return selectedScope.label || this.props.scope;

In the previous version, it was working so it's a regression.
Expected behaviour
Please correct this component to have an optionnal scope or tell us how to fix that.


docs(v2): Fix Gatsby theme name for docs site - Docz

Wrong name - Docz not Dokz.

tha,nks, good catch, actually Dokz also exist 🤪


Add make image params

add make image params
Signed-off-by: Montos<EMAIL_ADDRESS>What type of PR is this?
What this PR does / why we need it:
The local branch has some git conflicts, so redo the pr.
It is currently signed off. But I don't quite understand the WHAT= clusternet-agent make image that I said earlier? Does it mean to increase the what parameter in front of make? Currently my approach is make image clusternet-agent。Is that what I understand?
Which issue(s) this PR fixes:

Fixes #392
Special notes for your reviewer:

Would you please to make this PR works like WHAT=clusternet-hub make images? Thanks.

Sorry, can I export an environment variable here before executing make? It is not clear how to do WHAT=clusternet-hub make images

Would you please to make this PR works like WHAT=clusternet-hub make images? Thanks.

Sorry, can I export an environment variable here before executing make? It is not clear how to do WHAT=clusternet-hub make images

I've created a new PR #424, where your commits are cherry-picked. The credits still go to you.

@MentosL Your commits are cherry-picked into #424.
Close this PR.


Serve openapi.yaml file as documentation page

We should serve our openapi.yaml document as separate page using https://github.com/swagger-api/swagger-ui or https://github.com/Redocly/redoc
AC:

serve on /openapi (or another like /docs, we should discuss name of that path) the openapi.yaml spec

Before contribution please start discussion to clarify implementation and your questions/problems :)
This problem is involved in the OpenForce event. Please don't contribute if you are not participating in this event. If the problem is not solved at the end of the event, feel free to contribute :)

we are using OpenAPI 3.1.0, and it seems Redocly has basic support for it. I'm most familiar with swagger-ui but it doesn't seem to fully support 3.1.0 yet: https://github.com/swagger-api/swagger-ui/issues/5891.
@magicmatatjahu and @smoya what do you think is the best choice here?

@BOLT04 I also more familiar with swagger-ui and it has an excellent support for testing that spec (by test it functionality) but I think that we should go with redocly. As I remember it also support "test it" and have a nicer UX and styling. Of course if you wanna handle that I can help you :)
I found also that nice middleware that we can reuse :) https://github.com/AungMyoKyaw/redoc-express#readme

then let's go with redocly 👍, we can always contribute to the project if we need support on something the library doesn't yet support 😃

@BOLT04 Could we make it as part of the OpenForce event or do you wanna contribute it? More info https://github.com/asyncapi/website/pull/599

yessss let's make it a part of the OpenForce event 👍. New contributors are always welcome 😃

Hi , I would like to work on this issue as part of the openforce event.

As per previous comments, I plan to implement it using redocly and will be creating a display using the openapi.yaml file which will serve as documentation. Regarding the path would you like for me to create a folder named docs and create a index.html file(which will contain the intergration with redocly) inside it?

@everly-gif You can handle that.

As per previous comments, I plan to implement it using redocly and will be creating a display using the openapi.yaml file which will serve as documentation. Regarding the path would you like for me to create a folder named docs and create a index.html file(which will contain the intergration with redocly) inside it?

But that page should be visible on the server side, so you need to have handle that by some static-serve lib or something like that. Please check some open source libs which integrate redoc in express like this one https://github.com/AungMyoKyaw/redoc-express#readme :)

Hi @magicmatatjahu I'm looking into https://github.com/AungMyoKyaw/redoc-express#readme  could you tell me where would it be appropriate for me to add the code. I believe I should be editing app.ts right? I'm quite new to typescript but am familiar with node and express.

@everly-gif You should create controller in the https://github.com/asyncapi/server-api/tree/master/src/controllers folder as docs.controller.ts. You can make it similar to the validation.controller.ts and then connect it to the app in https://github.com/asyncapi/server-api/blob/master/src/server.ts#L13 :)

Implemented by https://github.com/asyncapi/server-api/commit/0d4a4188f480ef8b9012500206b4e269bf1eb92e


Help with SUI Upgrade on Windows

Hi.
I've been using SUI for around a year now (it's fantastic!), but in order to streamline the upgrade process for our team I want to use npm.  So far I have done:
npm install semantic-ui
gulp build

and have a working installation which I have customised for our needs to build to different output folders.
However, I have recently tried to upgrade from version 2.1.4 to 2.1.5 and I'm not sure things are working for me as they should.  I did:
npm update

from within the semantic-ui folder where I originally did the install.  This runs through fine and when I check the semantic version number in the node_modules\semantic-ui folder I see 2.1.5 so that's great.  The problem is that this version is not mirrored in the semantic-ui installation directory because the semantic.json file in there still reads 2.1.4.  I tried doing:
npm install

from inside the semantic-ui installation folder but I get a load of errors relating to a missing package.json file.  I appreciate that the package.json file is sitting in the node_modules/semantic-ui folder and not in the semantic-ui install folder and that is why npm is reporting an error so I assume what I have attempted here is wrong.
I have read all of the documentation on installs/upgrades here:
http://learnsemantic.com/guide/expert.html#running-installer
but they aren't clear on what to do in my specific case to ensure that semantic.json shows the correct version telling me that my installation is running the latest version.
Could someone give me a hand understanding what I am doing wrong and what I need to do to upgrade cleanly please?
Many thanks.

In my case running npm update didn't update semantic ui, my package.json still contained  "semantic-ui": "^2.1.4".
So I tried npm install<EMAIL_ADDRESS>which worked fine.
After switching into semantic/ and gulp build I got the latest semantic ui version running.
Hope this helps :)

Fantastic!  Thanks, that did it!


Non base-10 logarithms

Hey really cool library @terkel!
How would one alter your logarithm function so that a second (optional) parameter could be passed that specified the base?

@bcooke Really sorry for my late response 🙇
Thank you for your feedback!


(chore/blockchain_adresses) Implemented Blockchain provider. Implemen…

…ted exchange blockchain address component. Implemented organization blockchain address.

 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.Arkadiusz seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Retrospective shading correction based on entropy minimization

Implement approach of Likar et al. or something similar.
Also implement simpler/faster approaches:

Using top-hat filters: white, black
Smoothing with Gaussian with huge kernels

Accomplished by 3cd571623ba18da8e27e39554ec73d020ea1515d.


Update call to New-AzureRmADApplication to use correct parameters for…

… certificate authentication.  Also updated starting and ending dates in call to makecert.

@rickrain,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@rickrain : Thanks for your contribution to the Azure documentation! The author, @adhurwit, has been notified to review your proposed change.

#sign-off


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Codecov Report

Merging #365 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #365   +/-   ##
=======================================
  Coverage   83.33%   83.33%
=======================================
  Files           1        1
  Lines           6        6
=======================================
  Hits            5        5
  Misses          1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c8aaf40...6e27c27. Read the comment docs.

Coverage remained the same at 83.333% when pulling 6e27c27c013c31108a76ff1781ecd9a8aba4d4bc on template-sync-1 into c8aaf40212b92fab3dba8d0bcc7a0a563eae545a on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Video showing black screen on Ios while playing

Current Behavior
Sometimes when playing videos in Ios a black screen is being shown while the video is playing. So we can hear the audio but
see black screen instead of the video(See the bug reproduction video attached). The video is being loaded from AWS. The integration code is
import ReactPlayer from 'react-player';

<ReactPlayer
        config={{
          file: {
            forceVideo: true,
            attributes: {
              poster: 'Some external image URL',
              preload: 'metadata',
            },
          },
        }}
        playsinline
        playing={true}
        width='100vw'
        url={`Some external video URL`}
      />

Environment

URL attempting to play: https://app.starnewsmobile.com/creator-channel/5
Browser: Safari
Operating system: Ios 17

https://github.com/cookpete/react-player/assets/30544850/338b24f2-ad27-41e9-87b8-115ba859d4e2

I see same behavior. If you exit the video and play again it works fine. I've verified this is issue with IOS 17. Works fine with 16.5

I've just stumbled across this issue whilst researching a very similar issue I'm having in my own react application (which uses the native video controls when running in Safari on iOS). So even though I'm not using react-player I thought this information might be helpful...
For me it seems to occur only when:

the video has a poster image set
the user taps the webkit 'play' control (i.e. it doesn't occur if they tap anywhere else on the <video> element)
the playsinline attribute is NOT set

Frustratingly I can't replicate the issue outside of my application - either in a pure HTML5 video or in a React app that renders a <video> element.
But I am wondering if it's something that's been caused by a recent iOS update as it seems unlikely that it hasn't been noticed & reported before (this application has hundreds of thousands of users).
Oh, in my app it also works fine if you exit the video then play again.
I also noticed that if I switch to picture-in-picture it plays back fine.

@amitava82 a colleague with an iPhone still running iOS 16.4.1 just tested and couldn't replicate the issue so yeah I think something is broken in mobile safari.
Also note that in @hhovakimyan 's config playsinline is set but in the screen recording it looks to be opening in the full screen player

Hello!
I had a similar issue with Safari and Chrome in my app on iOS 17. However, I noticed that the video works as expected when the poster attribute is removed.
I hope this helps someone.


Documentation

It would be nice to properly document PyOS and keep it updated, maybe in the GitHub wiki.

#3 not needed as it is fundamentally the same as this issue.

Closed by #19.


Remove trailing slash from requests

e.g. when using
this.setEndpoint('users/' + userId + '/preferences');

the uikit will prepend a slash / at the end such that the request goes to [...]/preferences/ instead of [...]/preferences. This is unnecessary and leads to, should the user decide to do so, /preferences/?someQueryParm=foo which destroys the query parameter

Why does it destroy the query parameter? Isn't the example just a valid URL?

Isn't the example just a valid URL?

Good point, it is, and the query parameter works.
Still i would enjoy not having it added automatically since its confusing


License?

Would be nice to know.

Thanks for asking. I added the zlib license. It's permissive, so whatever your use case, you shouldn't have any troubles.

He'll yeha!


Take Notes for Discriminability

Simulation Notes
Figure Notes

overall comment: paper content is pretty all over the place and not very cohesive; probably needs a 100% rewrite; the figures need to get in place before we start improving the language in the paper more I think

F test for ICC/I2C2

2 sample simulation. n subjects; 2 scans per subject. pipeline 1 adds more variance. scaled identity for pipeline 1.

figure 1 is simulation figure, left panel is simulation drawing, middle is distance matrix, right is rdfs for linear simulation. figure 2 is like current but updated simulations, right show distribution figure 3 is power curves as a function of n for 1d and 100d, figure 4 is the current figure 3 redone to be pretty/right.
for 1d case:
generate 6 simulations
generate power curves as a function of nsamples
generate for 10d case as well wrt discr and I2C2

add line for mean discriminability to histogram

update radial sims to appropriately handle measure for added noise

incorporate ndmg revision comments


I can't install it using "pkg install" (Termux).

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
The Wiki page states that it's possible to install "yt-dlp" to Termux using this command:
pkg install -U "yt-dlp[default]".
But it says that there is no such package:

Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

No, the wiki says something else:
pip install -U "yt-dlp[default]

Oh, sorry then.
But it was a little bit difficult to notice (but probably it's just me):

I think it won't hurt adding some note like "hence pip" or IDK


feat: use pems in wasm client api

Description
Makes the tomb-wasm client use PEM formatted strings in place of CrytpoKeys or CryptoKeyPairs

Not sure if this is the proper time to merge. this would block incorporating newer changes into the banyan-core frontend until the passing of keys back and form between js and wasm is refactored


Behaviour of popover-is-open is unpredictable

Hi all,
i have a little question about popover-is-open. If i have a popover with popover-is-open="some_model" and in popover i have button to set this model to false, then i can close popover by click on it. But if i set same handler to button, which actually has popover, then popover is opening despite the fact that some_model is set to false. See example and environment on plunkr: http://plnkr.co/edit/qKJeh5qCUq6qBsqosphf?p=preview
So how can i implement next functionality: i want to open popover when and only when some expression returns true (for example, i have a download modal dialog to save file and i want to show popover with warning only if size of file is greater than some limit)?
Thank you!

Questions of this nature should be asked on Stackoverflow, please read the FAQ section: Need Help?
The popover is responding to the button click due to the default 'click' trigger that is added.  To use the *is-open attribute exclusively, you need to set the popover-trigger="none" as documented in the tooltip Triggers section.

@RobJacobs Stackoverflow didn't help me.
Thank you, your solution helped!

@BParnikel, @RobJacobs meant you should follow the instructions we post on how to ask for help and post your question on StackOverflow.  The issues forum is for bugs, not support requests.

I have found a related problem but I'm not sure if I should create a new issue for that.
Here is a Plunker example:
http://plnkr.co/edit/ZwQgKgMoQI7MOLNtM8Yl
Essentially, if you have set popup-delay and the value of a property bound to popover-is-open has been changed to false, then after the delay time passes popover thinks that it should be open because that's what the property was before the delay.
I think, if using popup-delay, popover should check the popover-is-open property once more after the delay timeout has passed to avoid showing popover based on out-of-date value of popover-is-open.


[Feat] Add a Translation Tool (all language) ✨

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I want to add a Translation Tool(all language) properly.
@Luson045 PA please assign me this task.

Use Case
..
Benefits
..
Priority
High
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

checkout , footer , it already exists. @Subhajit-2023-44

@Subhajit-2023-44  don't spam

@Subhajit-2023-44 don't spam

what ??


[opt-remark] When looking for debug_value users, look modulo RC Identity preserving users.

A key concept in late ARC optimization is "RC Identity". In short, a result of
an instruction is rc-identical to an operand of the instruction if one can
safely move a retain (release) from before the instruction on the result to one
after on the operand without changing the program semantics. This creates a
simple model where one can work on equivalence classes of rc-identical values
(using a dominating definition generally as the representative) and thus
optimize/pair retain, release.
When preparing for late ARC optimization, the optimizer will normalize aggregate
ARC operations (retain_value, release_value) into singular strong_retain,
strong_release operations on leaf types of the aggregate that are
non-trivial. As an example, a retain_value on a KlassPair would be canonicalized
into two strong_retain, one for the lhs and one for the rhs. When this is done,
the optimizer generally just creates new struct_extract at the point where the
retain is. In such a case, we may have that the debug_value for the underlying
type is actually on a reformed aggregate whose underlying parts we are
retaining:
bb0(%0 : $Builtin.NativeObject):
  strong_retain %0
  %1 = struct $Array(%0 : $Builtin.NativeObject, ...)
  debug_value %1 : $Array, ...

By looking through RC identical uses, we can handle a large subset of these
cases without much effort: ones were there is a single owning pointer like Array.
To handle more complex cases we would have to calculate an inverse access path needed to get
back to our value and somehow deal with all of the complexity therein (I am sure
we can do it I just haven't thought through all of the details).
The only interesting behavior that this results in is that when we emit
diagnostics, we just use the rc-identical transitive use debug_value's name
without a projection path. This is because the source location associated with
that debug_value is with a separate value that is rc-identical to the actual
value that we visited during our opt-remark traversal up the def-use
graph. Consider the following example below, noting the comments that show in
the SIL itself what I attempted to explain above.
struct KlassPair {
  var lhs: Klass
  var rhs: Klass
}

struct StateWithOwningPointer {
  var state: TrivialState
  var owningPtr: Klass
}

sil @theFunction : $@convention(thin) () -> () {
bb0:
  %0 = apply %getKlassPair() : $@convention(thin) () -> @owned KlassPair
  // This debug_value's name can be combined...
  debug_value %0 : $KlassPair, name "myPair"
  // ... with the access path from the struct_extract here...
  %1 = struct_extract %0 : $KlassPair, #KlassPair.lhs
  // ... to emit a nice diagnostic that 'myPair.lhs' is being retained.
  strong_retain %1 : $Klass

  // In contrast in the case below, we rely on looking through rc-identity uses
  // to find the debug_value. In this case, the source info associated with the
  // debug_value (%2) is no longer associated with the underlying access path we
  // have been tracking upwards (%1 is in our access path list). Instead, we
  // know that the debug_value is rc-identical to whatever value we were
  // originally tracking up (%1) and thus the correct identifier to use is the
  // direct name of the identifier alone (without access path) since that source
  // identifier must be some value in the source that by itself is rc-identical
  // to whatever is being manipulated. Thus if we were to emit the access path
  // here for na rc-identical use we would get "myAdditionalState.owningPtr"
  // which is misleading since ArrayWrapperWithMoreState does not have a field
  // named 'owningPtr', its subfield array does. That being said since
  // rc-identity means a retain_value on the value with the debug_value upon it
  // is equivalent to the access path value we found by walking up the def-use
  // graph from our strong_retain's operand.
  %0a = apply %getStateWithOwningPointer() : $@convention(thin) () -> @owned StateWithOwningPointer
  %1 = struct_extract %0a : $StateWithOwningPointer, #StateWithOwningPointer.owningPtr
  strong_retain %1 : $Klass
  %2 = struct $Array(%0 : $Builtin.NativeObject, ...)
  %3 = struct $ArrayWrapperWithMoreState(%2 : $Array, %moreState : MoreState)
  debug_value %2 : $ArrayWrapperWithMoreState, name "myAdditionalState"
}

@atrick @adrian-prantl this is actually adding something new and not just moving stuff around.

@swift-ci smoke test


Unrouteable messages are always sent to a DLQ

On my cluster I have a broker, a trigger, and an event producer, but the trigger is currently unable to resolve its sink. The behavior I see is that the broker's DLQ is filling up with these undeliverable messages, despite there not being any DLQ configured on the Broker or the Trigger. This seems like a bad situation, since nobody is going to read from this cluster either and it will eventually consume all of the cluster's resources (I think!).
It only seems to happen in this unrouteable-trigger situation, if I delete the trigger then the messages are dropped on the floor.

Creating a trigger with a subscriber uri of https://dev.null repros this

Turns out this is because we always create a DLQ internally in Rabbit, even if we don't have anything configured. This seems bad, since it will mean undeliverable message will fill up our Rabbit cluster, rather than being discarded as per the eventing contract

Ah, I was going to point to the broker spec, but it sounds like this is internal to Rabbit...
https://github.com/knative/specs/blob/main/specs/eventing/control-plane.md#broker
If no delivery options are set on a Trigger, the Broker's delivery options should be used.

I think this might be related to #448, maybe the intention of this design was to work around the lack of mutability in RabbitMQ. Once you declare a queue, you can't change where its dead letter exchange points to, so one option is to preemptively declare resources you don't yet need so that you can allow the user to update the Knative broker/trigger without needing to recreate the backing RMQ resources.


Annotations should always invoke the constructor

@jacob314 suggests that annotations should always invoke the constructor:
From https://github.com/dart-lang/sdk/issues/26322#issuecomment-231226953:

This is a general issue with annotations in Dart2JS and Dart. I think the most user friendly solution is to have
@AnyAnnotation
be syntactic sugar for
@AnyAnnotation()
if AnyAnnotation is a class.
This is consistent with how some other languages handle annotations, makes the code users write more terse, and avoids these entirely confusing compile errors altogether.

Duplicate of #13582.


New Service: Add azure file service support

Azure Files offers fully managed file shares in the cloud that are accessible via the industry standard Server Message Block (SMB) protocol, Network File System (NFS) protocol, and Azure Files REST API. Azure file shares can be mounted concurrently by cloud or on-premises deployments. SMB Azure file shares are accessible from Windows, Linux, and macOS clients. NFS Azure file shares are accessible from Linux clients. Additionally, SMB Azure file shares can be cached on Windows servers with Azure File Sync for fast access near where the data is being used.
https://learn.microsoft.com/en-us/rest/api/storageservices/file-service-rest-api

Can I have a try?

Can I have a try?

Of course! Have fun😜


Remove 'stable' from the list of reserved version names

Yea, I felt a little silly when I went to test the "mark as stable" workflow -- the whole reason for doing this! -- and realized it would't work :)


Exclude JDK8 javax/management/MBeanServer/OldMBeanServerTest.java

Exclude JDK8 javax/management/MBeanServer/OldMBeanServerTest.java
Cherry-pick

https://github.com/adoptium/aqa-tests/pull/5826

Signed-off-by: Jason Feng<EMAIL_ADDRESS>

Thanks @smlambert


feat: add goreleaser config for brew and docker

@StewartJingga can you verify it once, locally it worked fine. Also it will be a better idea to update the name and email id in commit author for brews with yours as I will not have the access to the repo and the release will fail later when initiated by ci.

@StewartJingga @GrayFlash Build is failing on main for this. Dockerfile issue.

Oh sorry I missed it during review.
@GrayFlash we need the goreleaser action with --snapshot flag to build the binary on build workflow.

@StewartJingga @ravisuhag  missed that part, working on goreleaser-config branch temporarily, will create PR once it successfully gets triggered there.


Value not saved when two zero values in the same stem are inserted

Failing code
   use tempfile::tempdir;
        let temp_dir = tempdir().unwrap();

        let db = MemoryDb::new();
        let mut trie = Trie::new(TestConfig::new(db));

        let tree_key_version: [u8; 32] = [
            121, 85, 7, 198, 131, 230, 143, 90, 165, 129, 173, 81, 186, 89, 19, 191, 13, 107, 197,
            120, 243, 229, 224, 183, 72, 25, 6, 8, 210, 159, 31, 0,
        ];

        let tree_key_nonce: [u8; 32] = [
            121, 85, 7, 198, 131, 230, 143, 90, 165, 129, 173, 81, 186, 89, 19, 191, 13, 107, 197,
            120, 243, 229, 224, 183, 72, 25, 6, 8, 210, 159, 31, 2,
        ];

        let value_0: [u8; 32] = [
            0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
            0, 0, 0,
        ];

        trie.insert_single(tree_key_version, value_0);
        trie.insert_single(tree_key_nonce, value_0);
        let val = trie.get(tree_key_nonce).unwrap();

The problem of finding tree_key_nonce, only happens when tree_key_version is in the same stem and is also set to 0. ie if we change tree_key_version to be in another stem, tree_key_nonce can be found

This has been fixed in commit d17213c8be38e490aa7dcaa86167a33bc6bcd764


matrix-hookshot: 3.2.0 -> 4.0.0

Description of changes
https://github.com/matrix-org/matrix-hookshot/releases/tag/4.0.0
Includes bump of matrix-sdk-crypto-nodejs.

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)
[ ] 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/)
23.05 Release Notes (or backporting 22.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

[x] Fits CONTRIBUTING.md.

Can you include changelog links in the commits?

This breaks matrix-appservice-slack currently. Will look into fixing it, but I fear we will have to carry multiple versions of matrix-sdk-crypto-nodejs.

Couldn't find a way to fix this instead of carrying multiple versions. Deployed this to my server, matrix-appservice-slack and matrix-hookshot still work.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2232

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/963


Prevent multiple date time allocations

DateTime.SpecifyKind will return a new DateTime instance.
Creating new DateTime instance for Epoch,
Adding Milliseconds creates a new DateTime Instance

Now only one instance is created (apart from the one time static hit)

ported to 2.x and 5.x


Incompatibility with Minimap

There is a weird conflict with Minimap (https://www.nexusmods.com/skyrimspecialedition/mods/49490) where toggling the minimap on and off changes the FOV with Improved Camera installed. This wasn't an issue with the old Improved Camera.

Sorry for the late response on this. No doubt the MiniMap mod has its own FOV settings if they do not match what you have with Improved Camera that will result in what you are experiencing. We have a check in place for if the MapMenu is displayed and if so it turns off.


First pass at integration test docs

Assumes https://github.com/envoyproxy/envoy/pull/1901 is checked in
Fixes https://github.com/envoyproxy/envoy/issues/1922

Thanks this is super awesome. One other doc thought: Talk about the case where the user wants to have an additional upstream for use in async API calls (Lua, ratelimit, xDS, etc.)? It took me a bit of digging on how to set this up.
Also, what is your guidance on when to add new top level test fixtures vs. modify existing ones. Is that worth calling out?


Unnecessary GuidGenerator calls for custom delegates in authored types

Describe the bug
We're emitting some GuidGenerator calls when using custom delegates in authored components:

Pretty sure we could just literally hardcoded that same GUID we added on the ABI type for the delegate instead?
To Reproduce

public sealed unsafe partial class HelloWorldEffect
{
    public event MyEventHandler Foo;
}

public delegate void MyEventHandler(object sender, string args);

Expected behavior
We should probably emit that IID in a static readonly field, and then reference it wherever needed.
Version Info
2.0.5-prerelease.240203.7

This is probably getting optimized by IIDOptimizer today, but I agree we can move this to a readonly static field.

If that's the case I think we should probably also fix #1478? Because otherwise IIDOptimizer will break in libraries, and if you just opt-out, then that path will not be optimized by it. I mean I agree here we can just update the code writer, but this just makes me think that in general, the IIDOptimizer should also run on authored libraries then? 🤔


Exposed scanned image duration to iOS SDK

There was no way to reduce scanned image duration to 0 seconds, so there was always a flash of the card numbers on the screen. We had a client request that the numbers are never shown in that manner, so I exposed that value to the SDK.
There was some inconsistency in code formatting, so apologies for those modifications. I ended up using the following settings for my changes:
Tab width: 2 spaces
Indent width: 2 spaces
✓ Automatically trim trailing whitespace
✓ Including whitespace-only lines

Thanks. This seems reasonable, and the implementation is definitely straightforward. I've not thought much about iOS in a while, though; @dgoldman-ebay what do you think?
I appreciate the whitespace cleanup. However, I'd like to keep it separate from the functional changes. I pulled it in as https://github.com/card-io/card.io-iOS-source/commit/6732275; thanks! This means you'll need to rebase these changes, for which I apologize...but the resulting commit should be much cleaner. If you would, please take this opportunity to also squash your three commits into one. Please also revert the changes to  .gitmodules and icc.xcodeproj/project.pbxproj. (If you don't know how to do these things, just let me know and I can help.)

I'll wait until @ClaudeSutterlin has a chance to follow @josharian's requests, and then do a nice and picky review. :smiley_cat:

@josharian @dgoldman-ebay Thanks folks, I was being a little bit careless. I'll sort those issues out.
Regarding my change to .gitmodules though, I was getting a permission denied issue when trying to pull down the submodules per your instructions. After I updated the path to how you see it here, I was able to sync them.

@ClaudeSutterlin regard .gitmodules, it's tricky -- some folks don't have github/ssh playing together nicely, but others don't have a credential cache set up, so https is frustrating for them. I'd prefer to leave it as ssh instead of https, although I'm open to compelling arguments to the contrary. In the meantime, the best suggestion I have (which is not great) is to use insteadOf: https://coderwall.com/p/sitezg/force-git-to-clone-with-https-instead-of-git-urls.


Auto Update Feature

Description
I think having webcord auto update like the offical discord app does would be nice instead of having to download a new version each time, i'd be more than happy to help with this idea.
Suggestions
No response
Alternatives
No response
Additional Context
No response

I mean, Discord kinda doesn't update as well (at least on Linux), only a modules that it installs during update but the client stays intact.
As of Windows and macOS, Electron supports auto-updating these, but I guess in case of Windows my hate over Squirrel format won't make it happen (I'm not sure if NSIS supports auto-updates over Electron) and AFAIK macOS has also required the binary signing for auto-updates to be supported, so yeah… this is kinda problematic right now.
Also as of Linux, I thought of setting up the OBS (OpenSuse Build System) in order to have some kind of CI to automatically build the binaries for multiple Linux distros. But right now I have no clue how to set it up, so it is still uncertain when and if that'll happen.

I have this inplace for my own app:

I could modify it for your purpose and have it handle appimages and other stuff, and it can be contained in the update.ts file for the main logic.

Was not aware appimages could do that


Error messages not very useful

Exceptions are intercepted and passed into Result.errorMessages. This makes it very hard to get the error and deliver meaningful messages to the user.
Example:
This is the Error message delivered after the user has denied access and we try to modify the calendar -
[599] Device calendar plugin ran into an issue. Platform specific exception [401], with message :"The user has not allowed this application to modify their calendar(s)", has been thrown
It comes in the form of a String which is useless if we want to deliver a meaningful message to the user.
It would be nice to be able to tell the user if they want to use the feature they need to allow permission and how to do that etc, but with the exception being parsed how it is this is very difficult.
If we get the untouched PlatformException we can check the code and deliver a message to the user based on that or in some cases just forward the message.

You can use errorCode from ResultError class to display specific error messages for specific error code.


[1.3] The implementation of the Device Energy Management Mode is required

Reproduction steps
Executed the below mentioned command to put DUT into a commissionable state
./chip-all-clusters-app
Once DUT reach the commissionable state sent below mentioned command on TH.
./chip-tool pairing onnetwork 1 20202021
After the successful commissioning, I attempted to validate the Device Energy Management Mode Cluster, but it is not implemented in chip-tool
Bug prevalence
Whenever I do
GitHub hash of the SDK that was being used
09f014cebf114980e6174277d8d45f301f77679f
Platform
raspi
Platform Version(s)
1.3
Anything else?
Chip-tool has to be implement for below mentioned Attribute:

[ ] SupportedModes
[ ]  CurrentMode
[ ]  StartUpMode
[ ]  OnMode
[ ]  ClusterRevision
[ ]  FeatureMap
[ ]  AttributeList
[ ]  AcceptedCommandList
[ ]  GeneratedCommandList

Spec References:

https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/app_clusters/Mode_DeviceEnergyManagement.adoc#5-attributes

Test Plan References:

https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/mode_device_energy_management.adoc

See PR #31506


Update prometheus fetcher for so11y

Document how to set up so11y for cluster
Add label filter to aggregate metrics from dedicated labels.
Update self.yaml
Add UI template for so11y.


update New-NetFirewallRule.md

https://github.com/MicrosoftDocs/windows-powershell-docs/issues/2377

Dear @JohanFreelancer9,
kindly do the copy editor review for this PR.
Dear @e0i, for your information
Thank you

Docs Build status updates of commit 05dd0cb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3355fb2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit eeba1cf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 09a8747:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit bfbd2be:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2f504df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 12fb1a7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 474a539:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5ed10dc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2012r2-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2019-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Dear @JohanFreelancer9 ,
can you please have another look? I applied recommendations from other contributors and also fixed the same error on Set-NetFirewallRule article.
Thank you!

Docs Build status updates of commit bc6c921:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2012r2-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2019-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 474a539:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2012r2-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2019-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@MaratMussabekov - looks good.

Docs Build status updates of commit dde9fa3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2012r2-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2019-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/netsecurity/Set-NetFirewallRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add mutate for List properties

CheckedList is a list implementation that delegates to a provided add method (in this case, the user's overridden addFoo method) to perform element validation and insertion into a random-access backing list.
This PR is part of issue #6.

ok, I added a comment, and then just merged it. Ah well. Follow-up if you think worthwhile.


Why CURRENT-OFFSET NOT change when AutoCommit disabled?

Versions

Sarama
Kafka
Go

2.6.2
1.1.0
1.2

Problem Description

use the example of [consumer group|https://github.com/Shopify/sarama/tree/master/examples/consumergroup]

Disable the AutoCommit by this
config.Consumer.Offsets.AutoCommit.Enable = false

Show status via ./kafka-consumer-groups.sh  --describe --group XX  --bootstrap-server XX
TOPIC      PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG           CONSUMER-ID

Why CURRENT-OFFSET  never changed? It will change when AutoCommit enabled.

because you are not be able to Commit manually,
#1570

Dupe of #1570


地圖頁面

當地圖拉遠時，所有標示擠在一起。也許 (https://www.ioa.tw/Develop/GoogleMaps-Marker-Clustering.html)可以解，找時間待研究。

Hi,Teacher,
This issue was already closed,does it mean that this direction is not suggested to be processing and researching?

Hi,Teacher, This issue was already closed,does it mean that this direction is not suggested to be processing and researching?

這個問題已經解決了，請在近端運行這個專案，就可以看到效果
舊版版本沒有辦法直接更動

我先把議題重新打開，請確認完成，再把它關閉

哇！真的完成了耶！昨晚我在近端run yarn serve時不知為何還出現一堆bug...
好快啊，真神奇！


LIVE-2895 Osmosis staking on LLM

📝 Description
It's all in the title :slightly_smiling_face:
Osmosis currently is only send/receive on LLM, this PR add support for all the staking flows, which are the same as for Cosmos.
❓ Context

Impacted projects: ledger-live-mobile
Linked resource(s): https://ledgerhq.atlassian.net/browse/LIVE-2895

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach

:information_source: Currently targeted at the release branch because it contains mandatory changes for this feature.


Updated README for new inputs

Current dependencies on/for this PR:

main

PR #254

PR #255   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: tKhQ5RjOPcnJZi7fRjsG


Closes #16 library now checks if visible

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[ ] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[ ] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[ ] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[ ] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[ ] Update to all relevant roxygen headers and examples.
[ ] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[ ] Address any updates needed for vignettes and/or templates
[ ] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[ ] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[ ] Address or fix all lintr warnings and errors - lintr::lint_package()
[ ] Run R CMD check locally and address all errors and warnings - devtools::check()
[ ] Link the issue so that it closes after successful merging.
[ ] Address all merge conflicts and resolve appropriately.
[ ] Pat yourself on the back for a job well done! Much love to your accomplishment!

@mstackhouse FYI,  base::libary()has to be evaluated prior to resetting autos to keep autos at the top of the search path.  So I just check if return is visible and added a conditional return


"Update import from ..." quick fix doesn't trigger on mouse click

Type: Bug

Click the blue light bulb
Click the "Update import from ..."  Can you please try putting together a small example project that demonstrates this problem

Did some debugging, this issue triggers when code fix menu item is overlapping with CodeLens. For example in a JavaScript file:
module.exports = { a: 1 } // Invoke code fix menu on `module`, add/remove empty lines below to make some menu item overlapping with CodeLens below

// enable `"javascript.referencesCodeLens.enabled": true`, there will be a CodeLens here
function foo() {

}

https://user-images.githubusercontent.com/1330321/210427910-675dc999-2232-490e-922f-32ffabb0cc07.mp4

Hey @mjbvz, this issue might need further attention.
@yume-chan, you can help us out by closing this issue if the problem no longer exists, or adding more information.

@mjbvz Please try again using the new repro step above. It's still reproducible in latest insiders version.

Thank you @yume-chan! I can repo now
@alexdima I believe the root cause is that our editor mouse handlers don't know about context views. In this instance, clicking in the action widget fires mouseDown here:
https://insiders.vscode.dev/github/microsoft/vscode/blob/main/src/vs/editor/browser/controller/mouseHandler.ts#L305
This code ends up thinking that the user has clicked on an MouseTargetType.CONTENT_VIEW_ZONE element, which suppresses the mousedown event.
Can you provide some suggestions on how to fix this? I tried adding a new PartFingerprint.ContextView enum value but then realized the context view service can't use PartFingerprint because it lives in base

I could reproduce the same with Ballerina vscode extension as depicted below.

When I select an item from the context menu on a code lens it selects the public token as depicted above(triggers a mouseDown  event). This prevents the selected item (code action) from executing. However,  if I selected the same somewhere else (not on code lens) it does not trigger such a event and the  code action executes fine.

I see. The root problem is that we add a foreign dom node to the editor dom node via direct DOM APIs and that is unexpected to the mouse handling logic. The foreign dom nodes added to the editor have so far been added via API (content widgets, overlay widgets, etc.).


vault fails to start during build

This is an intermittent problem during builds:
NOTIFIED: [vault | restart vault] *********************************************
failed: [resching-do-control-02] => {"changed": true, "cmd": ["systemctl", "restart", "vault"], "delta": "0:00:02.370250", "end": "2015-12-17 14:17:20.983720", "rc": 1, "start": "2015-12-17 14:17:18.613470",
"warnings": []}
stderr: Job for vault.service failed because the control process exited with error code. See "systemctl status vault.service" and "journalctl -xe" for details.

FATAL: all hosts have already failed -- aborting

But, the vault service is successfully running after the fact:
● vault.service - vault
   Loaded: loaded (/usr/lib/systemd/system/vault.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2015-12-17 14:17:42 UTC; 12min ago
  Process: 24735 ExecStartPost=/bin/bash -c [ -f /etc/vault/vault.unseal ] && /etc/vault/vault.unseal (code=exited, status=0/SUCCESS)
 Main PID: 24734 (vault)
   Memory: 41.0M
   CGroup: /system.slice/vault.service
           └─24734 /usr/bin/vault server -config=/etc/vault/vault.config

Dec 17 14:17:42 resching-do-control-02 bash[24735]: Unseal Progress: 0
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Sealed: false
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Key Shares: 5
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Key Threshold: 3
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Unseal Progress: 0
Dec 17 14:17:42 resching-do-control-02 systemd[1]: Started vault.
Dec 17 14:18:05 resching-do-control-02 vault[24734]: 2015/12/17 14:18:05 [INFO] core: acquired lock, enabling active operation
Dec 17 14:18:05 resching-do-control-02 vault[24734]: 2015/12/17 14:18:05 [INFO] core: post-unseal setup starting
Dec 17 14:18:05 resching-do-control-02 vault[24734]: 2015/12/17 14:18:05 [INFO] rollback: starting rollback manager
Dec 17 14:18:05 resching-do-control-02 vault[24734]: 2015/12/17 14:18:05 [INFO] core: post-unseal setup complete

Logs show that the first attempt to start the vault service failed, interrupting the build:
Dec 17 14:17:13 resching-do-control-02 systemd[1]: Starting vault...
Dec 17 14:17:13 resching-do-control-02 systemd[1]: Started vault.
Dec 17 14:17:15 resching-do-control-02 vault[24564]: ==> Vault server configuration:
Dec 17 14:17:15 resching-do-control-02 vault[24564]: Log Level: info
Dec 17 14:17:15 resching-do-control-02 vault[24564]: Backend: consul (HA available)
Dec 17 14:17:15 resching-do-control-02 vault[24564]: Listener 1: tcp (addr: "<IP_ADDRESS>:8200", tls: "enabled")
Dec 17 14:17:15 resching-do-control-02 vault[24564]: ==> Vault server started! Log data will stream in below:
Dec 17 14:17:15 resching-do-control-02 vault[24564]: 2015/12/17 14:17:15 http: TLS handshake error from <IP_ADDRESS>:55250: EOF
Dec 17 14:17:16 resching-do-control-02 vault[24564]: 2015/12/17 14:17:16 [INFO] core: security barrier initialized
Dec 17 14:17:16 resching-do-control-02 vault[24564]: 2015/12/17 14:17:16 [INFO] core: post-unseal setup starting
Dec 17 14:17:16 resching-do-control-02 vault[24564]: 2015/12/17 14:17:16 [INFO] rollback: starting rollback manager
Dec 17 14:17:16 resching-do-control-02 vault[24564]: 2015/12/17 14:17:16 [INFO] core: post-unseal setup complete
Dec 17 14:17:16 resching-do-control-02 vault[24564]: 2015/12/17 14:17:16 [INFO] core: root token generated
Dec 17 14:17:16 resching-do-control-02 vault[24564]: 2015/12/17 14:17:16 [INFO] core: pre-seal teardown starting
Dec 17 14:17:16 resching-do-control-02 vault[24564]: 2015/12/17 14:17:16 [INFO] rollback: stopping rollback manager
Dec 17 14:17:16 resching-do-control-02 vault[24564]: 2015/12/17 14:17:16 [INFO] core: pre-seal teardown complete
Dec 17 14:17:18 resching-do-control-02 systemd[1]: Stopping vault...
Dec 17 14:17:18 resching-do-control-02 systemd[1]: vault.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 17 14:17:18 resching-do-control-02 systemd[1]: Unit vault.service entered failed state.
Dec 17 14:17:18 resching-do-control-02 systemd[1]: vault.service failed.
Dec 17 14:17:18 resching-do-control-02 systemd[1]: Starting vault...
Dec 17 14:17:19 resching-do-control-02 vault[24654]: ==> Vault server configuration:
Dec 17 14:17:19 resching-do-control-02 vault[24654]: Log Level: info
Dec 17 14:17:19 resching-do-control-02 vault[24654]: Backend: consul (HA available)
Dec 17 14:17:19 resching-do-control-02 vault[24654]: Listener 1: tcp (addr: "<IP_ADDRESS>:8200", tls: "enabled")
Dec 17 14:17:19 resching-do-control-02 vault[24654]: ==> Vault server started! Log data will stream in below:
Dec 17 14:17:19 resching-do-control-02 bash[24655]: Sealed: true
Dec 17 14:17:19 resching-do-control-02 bash[24655]: Key Shares: 5
Dec 17 14:17:19 resching-do-control-02 bash[24655]: Key Threshold: 3
Dec 17 14:17:19 resching-do-control-02 bash[24655]: Unseal Progress: 1
Dec 17 14:17:19 resching-do-control-02 bash[24655]: Sealed: true
Dec 17 14:17:19 resching-do-control-02 bash[24655]: Key Shares: 5
Dec 17 14:17:19 resching-do-control-02 bash[24655]: Key Threshold: 3
Dec 17 14:17:19 resching-do-control-02 bash[24655]: Unseal Progress: 2
Dec 17 14:17:20 resching-do-control-02 vault[24654]: 2015/12/17 14:17:20 [INFO] core: vault is unsealed
Dec 17 14:17:20 resching-do-control-02 vault[24654]: 2015/12/17 14:17:20 [INFO] core: entering standby mode
Dec 17 14:17:20 resching-do-control-02 bash[24655]: Sealed: false
Dec 17 14:17:20 resching-do-control-02 bash[24655]: Key Shares: 5
Dec 17 14:17:20 resching-do-control-02 bash[24655]: Key Threshold: 3
Dec 17 14:17:20 resching-do-control-02 bash[24655]: Unseal Progress: 0
Dec 17 14:17:20 resching-do-control-02 vault[24654]: 2015/12/17 14:17:20 [INFO] core: acquired lock, enabling active operation
Dec 17 14:17:20 resching-do-control-02 vault[24654]: 2015/12/17 14:17:20 [INFO] core: post-unseal setup starting
Dec 17 14:17:20 resching-do-control-02 vault[24654]: 2015/12/17 14:17:20 [INFO] rollback: starting rollback manager
Dec 17 14:17:20 resching-do-control-02 vault[24654]: 2015/12/17 14:17:20 [INFO] core: post-unseal setup complete
Dec 17 14:17:20 resching-do-control-02 systemd[1]: vault.service start-post operation timed out. Stopping.
Dec 17 14:17:20 resching-do-control-02 systemd[1]: vault.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 17 14:17:20 resching-do-control-02 systemd[1]: Failed to start vault.
Dec 17 14:17:20 resching-do-control-02 systemd[1]: Unit vault.service entered failed state.
Dec 17 14:17:20 resching-do-control-02 systemd[1]: vault.service failed.
Dec 17 14:17:41 resching-do-control-02 systemd[1]: vault.service holdoff time over, scheduling restart.
Dec 17 14:17:41 resching-do-control-02 systemd[1]: Starting vault...
Dec 17 14:17:41 resching-do-control-02 bash[24735]: Error attempting unseal: Put https://<IP_ADDRESS>:8200/v1/sys/unseal: dial tcp <IP_ADDRESS>:8200: connection refused
Dec 17 14:17:41 resching-do-control-02 vault[24734]: ==> Vault server configuration:
Dec 17 14:17:41 resching-do-control-02 vault[24734]: Log Level: info
Dec 17 14:17:41 resching-do-control-02 vault[24734]: Backend: consul (HA available)
Dec 17 14:17:41 resching-do-control-02 vault[24734]: Listener 1: tcp (addr: "<IP_ADDRESS>:8200", tls: "enabled")
Dec 17 14:17:41 resching-do-control-02 vault[24734]: ==> Vault server started! Log data will stream in below:
Dec 17 14:17:41 resching-do-control-02 bash[24735]: Sealed: true
Dec 17 14:17:41 resching-do-control-02 bash[24735]: Key Shares: 5
Dec 17 14:17:41 resching-do-control-02 bash[24735]: Key Threshold: 3
Dec 17 14:17:41 resching-do-control-02 bash[24735]: Unseal Progress: 1
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Sealed: true
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Key Shares: 5
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Key Threshold: 3
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Unseal Progress: 2
Dec 17 14:17:42 resching-do-control-02 vault[24734]: 2015/12/17 14:17:42 [INFO] core: vault is unsealed
Dec 17 14:17:42 resching-do-control-02 vault[24734]: 2015/12/17 14:17:42 [INFO] core: entering standby mode
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Sealed: false
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Key Shares: 5
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Key Threshold: 3
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Unseal Progress: 0
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Sealed: false
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Key Shares: 5
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Key Threshold: 3
Dec 17 14:17:42 resching-do-control-02 bash[24735]: Unseal Progress: 0
Dec 17 14:17:42 resching-do-control-02 systemd[1]: Started vault.
Dec 17 14:18:05 resching-do-control-02 vault[24734]: 2015/12/17 14:18:05 [INFO] core: acquired lock, enabling active operation
Dec 17 14:18:05 resching-do-control-02 vault[24734]: 2015/12/17 14:18:05 [INFO] core: post-unseal setup starting
Dec 17 14:18:05 resching-do-control-02 vault[24734]: 2015/12/17 14:18:05 [INFO] rollback: starting rollback manager
Dec 17 14:18:05 resching-do-control-02 vault[24734]: 2015/12/17 14:18:05 [INFO] core: post-unseal setup complete

this issue was related to the latest centos release and is resolved by running upgrade_packages.yml prior to deployment as documented in the getting started guide.see #927.


fix(tfconfig): hide managedFields in default tfconfig

Description

Hide the verbose managedFields diff when server-side-apply is enabled.
Related issues

Special notes for your reviewer:

Codecov Report
Patch and project coverage have no change.

Comparison is base (067458b) 37.74% compared to head (fd6696d) 37.74%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #146   +/-   ##
=======================================
  Coverage   37.74%   37.74%
=======================================
  Files          32       32
  Lines        2559     2559
=======================================
  Hits          966      966
  Misses       1530     1530
  Partials       63       63

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


Unmet peer Dependecies during installation

Am trying to intall the package but i get the following error.

UNMET PEER DEPENDENCY<EMAIL_ADDRESS>
What could be the issue?

In your package.json you have most likely 3.1.1 and you need 3.1.2

I actually didn't have it. thanks


Allow text items in questionnaire

Currently it is not possible to have a validated QuestionnaireResponse for a Questionnaire with a text item:
According to the specification (https://www.hl7.org/fhir/valueset-item-type.html, or the current version http://build.fhir.org/valueset-item-type.html), the answer has to be a valueString. The InstanceValidator does currently not validate such a request and insists that the answer has to be a 'text'.
This patch-set contains two patches with add tests for all item types for both DSTU3 and R4.
The other two patches fix the issue by adapting the value to compare against for DSTU3 and R4.
Unfortunately, at the moment the DSTU3 InstanceValidator is not used when validating the DSTU3 request - the patch in that case is thus a bit speculative.
Furthermore, the patches fix a NPE which I stumbled against when creating the test. Unfortunately, I did forget to record the exact circumstances.

Coverage increased (+0.01%) to 72.927% when pulling 5ca969d5a3cf237ed52a5091cd2c9dc07fb46afb on hdconradi:validate-questionnaire-response-item-type-for-text into 4ef07d27aad07f1db46395b74696d19073005431 on jamesagnew:master.


update grafana and rockset-go-client sdks

Summary

Update grafana and rockset-go-client sdks
Regenerated with grafana create-plugin (everything under .config is generated)
Added simple e2e tests with grafana e2e which is based on cypress
Incremented version to 0.2.0
Moved React components to components folder
Updated apiserver placeholder to point at Rockset api docs which contains current endpoints
Small name refactor:MyVariableQuery to VariableQuery

can you past a screenshot of the query window?

can you past a screenshot of the query window?

Thanks @jhochmuth
@pmenglund here's a screenshot from the e2e test and I made the suggested changes.


Feature matching?

I saw your YouTube video showing face generation with feature matching. Has it been removed in the TensorFlow 1.0 version of this code?

Ah, yes.
Since feature matching is not included in the original DCGAN paper, I changed it so that users can add them yourself.
Please see https://github.com/sugyan/face-generator/blob/4dbfcd3ba8bc166dd85666220461d5dee1a5776e/train.py#L50-L54


RSS feed doesn't include abstract

It only shows the title and note (if any).

Further the links for other citations in the note field are incorrect. E.g. https://quantumpl.github.io/Cross2017 for https://quantumpl.github.io/bib/publication/Cross2021/


Add Option to Remove Empty Line Between Header and Yaml, Add Blockquote Support and Other List Markers to List Item Removal, and Minifier Process Update

Fixes #331
Fixes #219
Changes Made:

Updated build command to make sure that for production it keeps the license comments and banner that states that the js file is generated
Updated heading-blank-lines to allow the user to decide if they want an empty line before the Yaml frontmatter and the first header (the default is to have one)
Updated remove-empty-list-markers to account for nesting in blockquotes or callouts and also added +, #., *, - [ ] and - [x] to the list of empty list markers

I got to try out version 1.4.1. Great to see the changes! One bug:
Before:
* item
*
// [end of file without blank line here]

After: linter adds a blank line, keeps the empty marker, and adds 3 additional blank lines to the end.
* item

*

Could you put in a bug report for this along with the rule that is causing this or your data.json, @yimingli ?


python312Packages.oauthenticator: 17.0.0 -> 17.1.0

Changelog: https://github.com/jupyterhub/oauthenticator/blob/17.1.0/docs/source/reference/changelog.md

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 351015

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.oauthenticator
python311Packages.oauthenticator.dist
python312Packages.oauthenticator
python312Packages.oauthenticator.dist