HDFS-15168: ABFS enhancement to translate AAD to Linux identities.

ABFS driver enhancement - Allow customizable translation from AAD SPNs and security groups to Linux user and group
Integration Test results - East US2:
Tests run: 1283, Failures: 0, Errors: 0, Skipped: 404

@steveloughran I'd mess up with the previous PR-1858 while fixing the review comment which got auto closed. Created new PR as i want to follow the contributor git commit process. Please review.
CC: @virajith

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
19m  8s
trunk passed

+1 :green_heart:
compile
0m 32s
trunk passed

+1 :green_heart:
checkstyle
0m 25s
trunk passed

+1 :green_heart:
mvnsite
0m 35s
trunk passed

+1 :green_heart:
shadedclient
14m 59s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 27s
trunk passed

+0 :ok:
spotbugs
0m 54s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 52s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 29s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

-0 :warning:
checkstyle
0m 16s
hadoop-tools/hadoop-azure: The patch generated 4 new + 1 unchanged - 0 fixed = 5 total (was 1)

+1 :green_heart:
mvnsite
0m 28s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 48s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 22s
the patch passed

+1 :green_heart:
findbugs
0m 55s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 22s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

57m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1978

JIRA Issue
HDFS-15168

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 2a0849be385c 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 453771f

Default Java
Private Build-1.8.0_252-8u252-b09-1~16.04-b09

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/1/artifact/out/diff-checkstyle-hadoop-tools_hadoop-azure.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/1/testReport/

Max. process+thread count
413 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 31s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
18m 51s
trunk passed

+1 :green_heart:
compile
0m 31s
trunk passed

+1 :green_heart:
checkstyle
0m 25s
trunk passed

+1 :green_heart:
mvnsite
0m 35s
trunk passed

+1 :green_heart:
shadedclient
14m 52s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 27s
trunk passed

+0 :ok:
spotbugs
0m 52s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 49s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 27s
the patch passed

+1 :green_heart:
compile
0m 24s
the patch passed

+1 :green_heart:
javac
0m 24s
the patch passed

-0 :warning:
checkstyle
0m 17s
hadoop-tools/hadoop-azure: The patch generated 4 new + 1 unchanged - 0 fixed = 5 total (was 1)

+1 :green_heart:
mvnsite
0m 27s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 43s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 24s
the patch passed

+1 :green_heart:
findbugs
0m 54s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 22s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

56m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1978

JIRA Issue
HDFS-15168

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux f5bcc5a5f26e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 5e0eda5d5f6

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/2/artifact/out/diff-checkstyle-hadoop-tools_hadoop-azure.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/2/testReport/

Max. process+thread count
414 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/2/console

versions
git=2.17.1 maven=3.6.0 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@steveloughran Thanks on review this PR, addressed below review comments:

Trailing "."
Import ordering
Formatting of ternary operator
Changing to debug statement
Use of "#" as comment

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
19m  5s
trunk passed

+1 :green_heart:
compile
0m 31s
trunk passed

+1 :green_heart:
checkstyle
0m 24s
trunk passed

+1 :green_heart:
mvnsite
0m 34s
trunk passed

+1 :green_heart:
shadedclient
14m 35s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 29s
trunk passed

+0 :ok:
spotbugs
0m 53s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 50s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 28s
the patch passed

+1 :green_heart:
compile
0m 24s
the patch passed

+1 :green_heart:
javac
0m 24s
the patch passed

-0 :warning:
checkstyle
0m 17s
hadoop-tools/hadoop-azure: The patch generated 4 new + 1 unchanged - 0 fixed = 5 total (was 1)

+1 :green_heart:
mvnsite
0m 27s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 31s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 24s
the patch passed

+1 :green_heart:
findbugs
0m 56s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 25s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

56m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1978

JIRA Issue
HDFS-15168

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 9377aff02bd2 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 1983eea62de

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/4/artifact/out/diff-checkstyle-hadoop-tools_hadoop-azure.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/4/testReport/

Max. process+thread count
454 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1978/4/console

versions
git=2.17.1 maven=3.6.0 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Thanks for reviewing this @steveloughran! Merging this PR based on Steve's lgtm above!
Thanks for working on this @amarnathkarthik


Added: { } surroundingPairs for markdown

In a markdown file, when we select some text and hit {, we expect to surround the text with {}. No one would like a single {. See more details at https://github.com/yzhang-gh/vscode-markdown/pull/452

There is one more problem. When the user hit a <, most time the user expects a less than symbol instead of a html tag, what do you think?
Our markdown extension would like to override the auto closing pair <> in a math block, is it possible?

Duplicate of https://github.com/microsoft/vscode/issues/74046. See that issue for why I'm not in favor of introducing this.
If you want braces to be auto closed, your extension should be able to contribute new autoclosing pairs that override the standard vs code ones


nat.tf boot disk image is out of date

The current nat.tf configuration currently includes:
boot_disk {
    initialize_params {
      image = "debian-cloud/debian-8"
      size  = 10
    }

It looks like the debian-8 image family is now deprecated and causes the deploy script to fail with * google_compute_instance.nat: Error resolving image name 'debian-gnu/linux-8': Could not find image or family debian-gnu/linux-8.
I think this should be updated to debian-cloud/debian-9.

https://github.com/cf-platform-eng/gcp-pcf-quickstart/commit/e928689faceea4c1c0f0d9368b7482485a59208d


only upload to pypi when the commit time is within last 24 hrs

Use the timestamp of the commit on which the workflow is run, and see if it is within 24 hrs. If it is, then we go ahead and upload. Otherwise, we should have already uploaded it in the last run, so do nothing.

thanks.


Make record.save no-op

As we allow data modifications only inside of TX there is no need to force users to manually call save.

As experience shows users often forget to call save and that leads to puzzling results.

Closed in favour of new implementation


Fix PLAYWRIGHT_DRIVER_URL example

cf. https://github.com/dgtlmoon/changedetection.io/discussions/587

@ginkel thanks a lot for this, it helps everyone :)


Mindustry is missing zenity dependency

Describe the bug
A clear and concise description of what the bug is.
Steps To Reproduce
Steps to reproduce the behavior:

nix-shell -p mindustry
in main menu go to settings then game data
click Export save

Additional context
[nix-shell:~/nixpkgs]$ mindustry
[I] Initialized Discord rich presence.
[I] [Core] Initialized SDL v2.30.3
[I] [Audio] Initialized SoLoud 202111 using MiniAudio at 44100hz / 900 samples / 2 channels
[I] [GL] Version: OpenGL 4.6.0 / AMD / AMD Radeon Graphics (radeonsi, renoir, LLVM 17.0.6, DRM 3.54, 6.6.36)
[I] [GL] Max texture size: 16384
[I] [GL] Using OpenGL 2 context.
[I] [JAVA] Version: 17.0.11
[I] [RAM] Available: 3.7 GB
[I] [Mindustry] Version: 146
[I] Total time to load: 2176ms
[I] Fetching community servers at https://raw.githubusercontent.com/Anuken/Mindustry/master/servers_v7.json
[I] Fetched 83 community servers.
[E] java.lang.RuntimeException: java.io.IOException: Cannot run program "zenity": error=2, No such file or directory
	at arc.util.OS.exec(OS.java:101)
	at arc.util.OS.exec(OS.java:107)
	at mindustry.core.Platform.lambda$showZenity$6(Platform.java:174)
	at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.io.IOException: Cannot run program "zenity": error=2, No such file or directory
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
	at java.base/java.lang.Runtime.exec(Runtime.java:594)
	at java.base/java.lang.Runtime.exec(Runtime.java:453)
	at arc.util.OS.exec(OS.java:82)
	... 3 more
Caused by: java.io.IOException: error=2, No such file or directory
	at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:314)
	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
	... 7 more

[W] zenity not found, using non-native file dialog. Consider installing `zenity` for native file dialogs.

Notify maintainers
@chkno @fgaz @thekostins

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.36, NixOS, 24.11 (Vicuna), 24.11.20240703.9f4128e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.4`
 - channels(root): `"nixos-23.05"`
 - channels(sigmanificient): `""`
 - nixpkgs: `/nix/store/dk2rpyb6ndvfbf19bkb2plcz5y3k8i5v-source`

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

i'll try to add zenity to deps as zenity exist in nixpkgs, gimme some time..

did https://github.com/NixOS/nixpkgs/pull/332917, now we wait..

Fortunately zenity is optional, so at least it wasn't totally broken, it just didn't use system dialogs

zenity not found, using non-native file dialog. Consider installing `zenity` for native file dialogs.


Inconsistent Discovering of Devices.

I am running Test.js with inconsistent results. I have 4 computers that I can run and discover devices almost every time. These are all Windows 7 pro 64 bit machines using BCM20702A0  Bluetooth adapter.
I have two computers that will only discover a device 1 out 10 times or worse.
1 computer is a Windows 7 pro 64 bit and the other computer is Windows 10. Both are using the same BCM20702A0  Bluetooth adapter.
Any ideas on how to trouble shoot the 2 computers or fix the issue?
Thanks.

Does increasing the scan time help?
It sounds like a hardware issue. Bad hardware? Something with the antenna? The easiest solution is probably to switch to a USB Bluetooth adapter.


Do not call finalise script from the build part, as it needs external services like a database.

For magento 2, similar to the one for drupal 8 in #103

@andytson-inviqa happy to merge?


Add ability to define fn as async, also allow for macros in traits and impls

As described above, I'd like to add async support and macro support. My use case is that I'd like to use codegen w/ async fns, in addition to using the #[async_trait] macro [1]
Ergonomically I don't love using r#macro in the code, but I also don't like avoiding using a good name just cuz its reserved. Thoughts on that, or thoughts on other parts of the code would be appreciated. Thx!
[1] https://github.com/dtolnay/async-trait

I don't have time to maintain this crate anymore. I would be happy to hand it off to whoever. Sorry :(

Merged into release 0.1.3


License Violation in ptpstatus.sh  (debian-main branch)

The License described in this file is problematic for usage with ansible.
https://github.com/seapath/ansible/blob/debian-main/src/debian/ptpstatus/ptpstatus.sh

Thanks @dknueppe for reporting it.
Indeed the file clearly mentioned "Any reproduction without written permission is prohibited by law.".
The license is clearly not open-source.
@insatomcat could you please remove this file immediately ?


Email provider. Which one?

Loops?
Resend?
Enveloop?
Postmark?

Plunk??

https://saasprices.net/emails?emails=25000


tfrecord

I want to train from tfrecords, can you give some advice about how to modify this code, thank you very much!

Sorry, I don't know. I make this code from keras, it support generator better.


Output Object.assign problem

Hi,
I'm having a problem when rendering objects. When I try to render an object I get unwanted properties in the rendered output i.e. "Object.assign {" (See example below)

I do not know if this is intentional or a bug.
Also, would it be possible to turn off the object preview if it has subitems?
Thanks in advance,
Regards,
Mo Binni

Ref: https://github.com/mohsen1/json-formatter-js/pull/36 - fixes issue


Redundant AppExit event checking in ScheduleRunnerPlugin

Bevy version
0.11
Description
While looking through Bevy's source code, I noticed that the ScheduleRunnerPlugin is checking for AppExitEvents twice in the main loop - once immediately before calling App.update() and once immediately after. Meanwhile, the main loop of the WinitPlugin only does this check once in the main loop, a bit after calling App.update().
As the WinitPlugin is only checking for AppExit events once per loop, I believe that means the extra check in ScheduleRunnerPlugin is redundant and unneccessary (Or if it somehow is necessary, it's completely undocumented). The secondary check was added in this commit, if it's any help.

Let's get a PR open for this and do some testing? This definitely looks redundant to me.


Javascript / mocha: Not a test file

My tests files are not recognized when running any of the commands (:TestNearest, :TestFile, etc.). They all report 'Not a test file'. My test files are in the 'test' directory. The :Mocha command itself does work.

Do your test files satisfy the regex tests?/.*\.(js|coffee)$? This is what test.vim currently uses for recognizing the test files for Mocha. Open the test file in the buffer, and check if
:echo expand('%') =~ '\vtests?/.*\.(js|coffee)$'

returns 1. If it returns zero, then something is strange (because this regex recognizes any .js/.coffee file in the test/ directory).

It returns 0.
My directory structure is basically like this, the Node convention:
/lib
--code.js
/test
--index.js

I open vim in the root, then open test/index.js.

I cannot seem to reproduce, for me the following works:
mkdir myproject
cd myproject
mkdir test
touch test/index.js
vim test/index.js
:TestFile

Strange... I also did exactly the same thing you did. Still 'Not a test file'.

Are you using the latest version of vim-test?

Yes, I cloned the repo. It's weird that the regex returns 0, since that should be unrelated to the plugin.

You're right, that is unrelated. Could you try testing the regex without the .vimrc or any plugins, starting up Vim with vim -u NONE test/index.js?

It returns 1. I guess I have some conflicting plugins or settings.

It turns out that the following setting broke the regex: set autochdir

Ah, yeah, this definitely breaks vim-test, because it has to know in which folder are your files located.

I'm a big fan of autochdir, but would still like to use vim-test. Is it possible to test against the full file path?

The thing is, test.vim relies on the fact that your working directory is the root of your project. This way it knows whether a file is a test file or production file. If I would expand the file path to the full pathname, then I wouldn't know which is the actual subfolder of the project test/, and it could theoretically happen that your project is located in a test/ folder (although I know, very unlikely).
This is also how it knows where to find things like node_modules or other files in other testing frameworks, in order to do some smart decisions. That means that for every file test.vim would have to traverse up the file hierarchy until it finds a wanted file or until it reaches the root directory of your disk. This sounds very inefficient to me, and would complicate code in each place I check something in the filesystem.

Not sure if it could be leveraged here, but I use the Project Root plugin ( https://github.com/dbakker/vim-projectroot ) in order to run some commands (like grepping, etc) from the root of any project.
Another option would be to allow for customizing the test -- in the project I'm currently working on, all test files end with _test.js, which would be easy to match if an appropriate property were exposed.

I agree with your latter suggestion, the users indeed should be able to change the test file regexes, I opened a separate issue for it. I will fix it sometime in the next two weeks.


feat: insert window check into preloader for Node execution

Description
Closes #15369
Allows for skipping the preloader in non-browser environments.
Additional context
I'm struggling a bit to create a minimal test case, though I'm unfamiliar with how & when the preloader gets injected. If anyone has any ideas, I'd love to hear them. Somehow we run into this in the linked feature request but I'm unable to minimally reproduce.

What is the purpose of this pull request?

[ ] Bug fix
[X] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines, especially the Pull Request Guidelines.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Update the corresponding documentation if needed.
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

We discussed this in today's team meeting and decided to keep the patch in userland for now, sorry again for pushing for the PR before Christian. More context at https://github.com/vitejs/vite/issues/15369#issuecomment-1884538980


add match statistic

Hey thanks for the contribution.
Do you think we should support the other possible options for the match statistic. I checked out the man page quickly:
  statistic
       This module matches packets based on some statistic condition.  It supports two distinct modes settable with the --mode option.

       Supported options:

       --mode mode
              Set the matching mode of the matching rule, supported modes are random and nth.

       [!] --probability p
              Set the probability for a packet to be randomly matched. It only works with the random mode. p must be within 0.0 and 1.0. The supported granularity is in 1/2147483648th increments.

       [!] --every n
              Match one packet every nth packet. It works only with the nth mode (see also the --packet option).

       --packet p
              Set the initial counter value (0 <= p <= n-1, default 0) for the nth mode.

I think we should also support --every and --packet flag.
Or are these flags never returned by iptables -S and "translated" to a probability?

done, thx for the hint.

Why did you remove the negated mode flag but not the packat flag?

@leonnicolas sorry, i was beside myself yesterday, maybe side effect of vaccination.

Great @cgroschupp Thank you very much!


IPv6 examples: replace ace:cab:deca with fd00:cab:deca

Currently, the IPv6 documentation examples use the range ace:cab:deca::/48. My understanding is that IPv6 ranges in Virtual Networks should use a private, and not globally routable address space. The a::/3 address range is currently unallocated/reserved, but may eventually become globally routable.
Unique Local Addresses in IPv6 are similar to IPv4 private address ranges, and use the fc00::/7 address range.
Updating the documentation makes it clear to users that a Unique Local Address range is required for Virtual Networks.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: jlaundry sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@jlaundry : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#reassign: EricTheRed999

@EricTheRed999 Could you review this pull request? Thanks.

@kumudd @twooley @EricTheRed999 - Could one of you review this PR from February? Thanks.

I was also noticing this was rather odd. It should also be changed in the portal, which defaults to the abc... address.

@EricTheRed999 (notification refresh)

@kumudd Could you make a call on this PR? EricTheRed999 is no longer in GitHub as a Microsoft-linked account.

@ramandhillon84 Please can you review and approve for sign-off. Thanks!

The article has been updated, and the line of code that's revised in this pull request is no longer in the same context. We'll close the PR. If the issue the PR is intended to address is outstanding, please open a new pull request using the current version of the article. Thanks.

@ktoliver did the portal's default also get fixed?

Hi @fdr - I don't work with the content team and I don't have any details. If just appears that we wouldn't be able to merge in this pull request based on the current version of the file, so I closed it for that reason. You can see what's currently in master by viewing specific files in GitHub: https://github.com/MicrosoftDocs/azure-docs. I'm sorry that I can't be more helpful.

Alright, I'll give it a quick look and maybe use the uservoice feedback link if it's still weird. Thanks.

Hi everyone, I want to update this documentation to use RFC3849 space (2001:DB8::/32) in these examples instead of what is proposed here. Could we close this PR, and take the changes offline instead?

@ktoliver I appreciate that you don't manage the content directly, but I'd like to raise that the documentation is now inconsistent and still references ace:cab:deca in places, such as the screenshot azure/virtual-network/media/virtual-network-ipv4-ipv6-dual-stack-powershell/dual-stack-application-summary.png. I won't be raising another PR.
@fdr spoiler alert: the Azure UI still defaults to ace:cab:deca 😥
@ramandhillon84 The point that I was trying to raise with this PR was that the UI and documentation is extremely confusing as to what one should configure, and what sensible values would be. As this is 2020 and example code will be copy+pasta'd into production 99% of the time, the working examples should be reasonable, and ULA space fits this use case exactly.
For that reason, I believe fd00:cab:deca::/48 is the best example to use. But, 2001:db8::/32 is still better than ace:cab:deca.

Have a good day. 😊

Thanks for the detailed reply @jlaundry, really appreciate it.
Although I'm a bit late here, but I'm trying to get all the documentation as well as UI to change defaults and not offer this random range. My proposal was based on the RFC describing the IPv6 range to be used for documentation.
But I do see your point about whatever is documented will be used in PROD most of the time. I'll edit those and use ULA instead to update the example docs at the very least.
Will work with the Portal folks to correct this as well.

Awesome, thanks @ramandhillon84!

Sorry @ramandhillon84 one last thing - when you talk to the portal team, please get them to randomise the prefix in line with RFC4193 - it's a small thing, but maybe it'll prevent an issue for someone trying to route between two VNETs one day.

That's actually a bigger change, as it involves a bit of IP Address Management and Networking Control plane changes.
We do have that on our radar, but not sure if we'll be able to get it it fairly soon. My first priority is to get rid of current range though :)

@jlaundry I actually filed another bug with a screenshot about that. https://feedback.azure.com/forums/217313-networking/suggestions/42009079-default-ipv6-subnet-in-portal-should-use-fd00-8
I'm not sure why at least subnet randomization would involve control plane changes, unless for some reason Azure can't handle Vnets having a wide dispersion in address spaces across the customer base. It's definitely the 99/1 as far as avoiding peering clashes.

Any update on this change?

For folks that come across this thread, it took us a while, but we have updated the portal so that the default IPv6 address space is within FD00, and we're doing address space randomization. The change is slowly deploying to everyone -- If you don't yet see the change you can use preview.portal.azure.com to get the updated experience.

[heart]         Ramandeep Singh Dhillon reacted to your message:

From: Richard Rundle @.>
Sent: Monday, July 24, 2023 10:10:58 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Ramandeep Singh Dhillon @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] IPv6 examples: replace ace:cab:deca with fd00:cab:deca (#46099)
For folks that come across this thread, it took us a while, but we have updated the portal so that the default IPv6 address space is within FD00, and we're doing address space randomization. The change is slowly deploying to everyone -- If you don't yet see the change you can use preview.portal.azure.com to get the updated experience.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/46099#issuecomment-1648694148, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKEU5BSGSQ2ARCPA7NVRBBDXR3XHFANCNFSM4KGMHLFA.
You are receiving this because you were mentioned.Message ID: @.***>


Add link to 29

Since 29 will only be published on Jun 8 at 10:00 UTC, I could not add the link just yet.
This should be caught up on once 29 has been published.

https://github.com/creativecreatorormaybenot/funvas/blob/4ad5819f1932bdd7be1fe437f3fc223af2f2dbef/funvas_tweets/lib/src/29.dart#L11

Closed in #99.


Update routerlicious dependencies to use any binary blob on FirstSummary.

Description
Once the FRS server has been updated, we will need to start consuming the new base64 Blob on first summary. This PR does the client update.
Support upload of any binary content of the blob during the initial summary upload at routerlicious driver. · Issue #15969 · microsoft/FluidFramework (github.com)

@NicholasCouri sorry for the dumb questions... do you know if FRS has already picked up the server changes? And this change will require client consumers to upgrade their server bits too, right? If so, add a changeset which will end up the release notes.

@NicholasCouri Also can you add links to the relevant PRs that made the preceding changes? That will be really helpful for the commit if we need to trace the changes altogether.

@NicholasCouri Also can you add links to the relevant PRs that made the preceding changes? That will be really helpful for the commit if we need to trace the changes altogether.

Done! Added to the description.

@NicholasCouri Also can you add links to the relevant PRs that made the preceding changes? That will be really helpful for the commit if we need to trace the changes altogether.

Done.

[celebrate]     Nicholas Couri reacted to your message:

From: Tyler Butler @.>
Sent: Wednesday, August 2, 2023 6:04:31 PM
To: microsoft/FluidFramework @.>
Cc: Nicholas Couri @.>; Mention @.>
Subject: Re: [microsoft/FluidFramework] Update routerlicious dependencies to use any binary blob on FirstSummary. (PR #16648)
Merged #16648https://github.com/microsoft/FluidFramework/pull/16648 into next.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/FluidFramework/pull/16648#event-9990960947, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGIMYCBCXDG5L47FOK7B4C3XTKJC7ANCNFSM6AAAAAA3ALZHAM.
You are receiving this because you were mentioned.Message ID: @.***>


[SR-15699] Support for Range<String.Index> in addition to Range

Previous ID
SR-15699

Radar
None

Original Reporter
daltonclaybrook (JIRA User)

Type
New Feature

Additional Detail from JIRA

Votes
0

Component/s
Swift-Markdown

Labels
New Feature

Assignee
None

Priority
Medium

md5: 32b021f1b425577d805c274b1171647c

Issue Description:
Today, when you ask a Markup instance for its `range`, you get an instance of `Range<SourceLocation>`. These bounds contain line and column numbers, but they do not contain the absolute index within the source string. This index would be useful for doing operations on the source string, such as using the String range subscript function to obtain a substring. I think either a new field should be added to Markup called `indexRange` (etc) that returns a `Range<String.Index>`, or a field should be added to `SourceLocation` called `absoluteIndex: String.Index` (etc) so that a `Range<String.Index>` can be derived.

Seconded! This would open up a lot of possibilities!


Not all OpenAI calls are displayed on the OpenAI Dashboard

Description
3/4 calls are correctly being tracked to the given model. One of my calls (get_final_answer() in my repo is not being captured in any of the queries.
Steps to Reproduce

See GitHub repo at https://github.com/Trolann/ParkingSucks
Observe src/completion_manager/answer_chains.py
See the call for get_final_answer()

The prompt/call is not being shown in the logs or number of calls:

Expected Behavior
The get_final_answer call is correctly shown on the OpenAI Dashboard
Relevant Logs / Console output
See screenshots and account 3912204
Your Environment
Docker python:3.9 (bullseye). Docker file provided at repo link.
Additional context
I've tried adjusting how the chat() object is called from LangChain, moving the final answer to go before the others, initializing monitor in different files (at one point was initializing it 3 times) and checked for logic errors.

Closing this. It appears the method isn't being captured as a background task for some reason.


Update to latest version

Hey @justandras
Thanks for your PR 🙂
I've configured the Github repo now to automatically stay up-to-date with upstream changes, so manual syncs will luckily not be needed anymore


New version: Sandboxie.Plus version 1.14.6

Pull request has been created with WinGet Releaser :rocket:
Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run

/azp run


Install CA Certificates after installing OpenJDK

Fixes a ca-certificates-java bug where installing OpenJDK does not install Java SSL certificates.
Closes #26
Connects WikiWatershed/model-my-watershed#2167
Testing

Follow the testing instructions in the README, make sure molecule tests pass.
It also may be worthwhile to test this on WikiWatershed/model-my-watershed#2167. To do so, apply this diff to your MMW branch, and re-provision the worker VM:

diff --git a/deployment/ansible/roles.yml b/deployment/ansible/roles.yml
index 714c97a8..73ca45ca 100644
--- a/deployment/ansible/roles.yml
+++ b/deployment/ansible/roles.yml
@@ -44,7 +44,10 @@
   version: 0.1.0
 - src: azavea.beaver
   version: 1.0.1
-- src: azavea.java
-  version: 0.5.0
+
+- name: azavea.java
+  src: git+https://github.com/azavea/ansible-java.git
+  version: origin/feature/tnation/install-cacerts
+
 - src: azavea.docker
   version: 1.0.2
diff --git a/vagrant/ansible_galaxy_helper.rb b/vagrant/ansible_galaxy_helper.rb
index 6e14f858..ad95257d 100644
--- a/vagrant/ansible_galaxy_helper.rb
+++ b/vagrant/ansible_galaxy_helper.rb
@@ -18,7 +18,7 @@ module AnsibleGalaxyHelper
     ansible_roles_spec = File.join(ansible_directory, "roles.yml")

     YAML.load_file(ansible_roles_spec).each do |role|
-      role_name = role["src"]
+      role_name = role["name"] ? role["name"] : role["src"]
       role_version = role["version"]
       role_path = File.join(ansible_directory, "roles", role_name)
       galaxy_metadata = galaxy_install_info(role_path)

Trying this out in MMW now


Refactor gensim.doctest to work for gensim 4.0.0 and up

Hello!
Pull Request Overview

Update gensim.doctest allowing us to remove the <4.0.0 version lock of gensim.

Details
See https://github.com/nltk/nltk/issues/2913#issuecomment-993305846 for a short discussion on gensim. It is currently locked to gensim < 4.0.0, and we'll want to start supporting newer versions. However, in 4.0.0, gensim made some changes in syntax, meaning that you either support before 4.0.0, or after 4.0.0.
This is us moving to the latter.
Beyond this PR
Lastly, I would like to propose the following, which is not included in this PR:
Let's deprecate gensim from pip-req.txt. gensim is not used anywhere in the codebase, except for this doctest, so we should remove it from pip-req.txt, and keep it only in requirements-ci.txt/requirements-test.txt. I have some other issues with these files at the moment, which I've brought up before in #2881:

Perhaps we can merge requirements-test.txt and requirements-ci.txt. They're both for testing, and are already very similar.
It somewhat bothers me that pip-req.txt and requirements-ci.txt/requirements-test.txt don't have the same naming structure. Perhaps we can change this? (To be honest, I don't remember ever seeing a pip-req.txt file before NLTK - I only encounter requirements.txt)

cc: @purificant This PR might be relevant for you and your work to help with #2913.

Tom Aarsen

requirements-ci.txt was created as a clean slate for CI when moving to GitHub Actions, since then this has become our primary CI pipeline, we could definitely clean up other requirement files and consolidate. :+1:

Amazing work @tomaarsen, thank you for doing this. One step closer to py 3.10

I've decided it's best to remove the unused gensim dependency as it might mess with people who wish to use specific gensim versions alongside NLTK, and there is no need to potentially introduce unnecessary version conflict.


drop ruby 2.1 and add ruby 2.3 to ruby versions in travis config

Signed-off-by: Dane Jensen<EMAIL_ADDRESS>

This was already addressed as part of another commit. Closing.


Read me file refers to older dataflex version

In the README.md file it is stated that

You need a DataFlex Studio 19.0 or later.

The help file under Wha's new for DFRefactor 2024.0 states this:

The only DataFlex Studio version supported are the latest two. At current that means DataFlex 2023 and 2024. That doesn't mean that the program can't be used for projects/workspaces on earlier DataFlex versions. All this means is that one of the last two DataFlex Studio's needs to be installed to compile and run these refactoring programs.

The README.md file should be changed to reflect the new requirements.

Good point. Fixed!

Wow that was fast!


Popups cannot be dismissed by default

Reproducer.
package me.dominaezzz.chitchat

import androidx.compose.desktop.Window
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.material.*
import androidx.compose.runtime.mutableStateOf
import androidx.compose.runtime.remember
import androidx.compose.runtime.getValue
import androidx.compose.runtime.setValue
import androidx.compose.ui.Alignment
import androidx.compose.ui.Modifier
import androidx.compose.ui.unit.IntSize
import androidx.compose.ui.unit.dp
import androidx.compose.ui.window.Popup

fun main() {
	Window(title = "Popup Example", size = IntSize(300, 300)) {
		var showPopup by remember { mutableStateOf(false) }

		MaterialTheme {
			TextButton(onClick = { showPopup = true }) {
				Text("Show popup")
			}

			if (showPopup) {
				Popup(Alignment.Center, onDismissRequest = { showPopup = false }) {
					Card(modifier = Modifier.fillMaxSize(0.7f), elevation = 20.dp) {
						Text("This is supposed to be loads of Lorem Ipsum but I'm lazy.")
					}
				}
			}
		}
	}
}

Clicking outside of the popup doesn't call onDismissRequest.

You need to add isFocusable = true to your Popup

Ah thanks! Wasn't expecting the argument to enable that.
Although, I think it should be isFocusable = onDismissRequest != null internally, there's probably a reason for it.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


[SONARMSBRU-183] Amended targets to merge SonarLint ruleset with any …

…existing ruleset

LGTM

Update: the merge code doesn't work correctly for relative ruleset paths. I'm looking at a fix for this now.

@bgavrilMS tested the basic functionality, so I'll check this in as-is. There is an outstanding issue that relative ruleset paths aren't handled correctly.


Add a way to cancel a connection attempt

When you try to connect to a remote pi, if the information is not correct or node is down or not reachable, then the UI is effectively blocked and you have to kill the app and start again.
What we should try and do is:

not disable the cancel button when the connection attempt is started (or add another button - but "cancel" seems the obvious text for such another button)
when the user hits the cancel button (or ESCAPE key?) send a request to cancel the connection attempt
if there is no direct mechanism to cancel a connection attempt using the Iroh/TCP connection primities then the subscription will have to implement a timeout, or check for a cancel request periodically or some such async cancel mechanism.
the connection attempt would stop, and the dialog would go back to previous state with the data still present and cancel button would go back to it's previous function of closing the dialog.

If during a connection attempt, the dialog is closed using some other mechanism (such as ESCAPE key) then catch that and also cancel the connection attempt in background, and close the dialog as the user expects.


Shouldn't UniformGridLayout.MaximumRowsOrColumns be a DependencyProperty

The UniformGridLayout.MaximumRowsOrColumns is a normal property. Shouldn't this be a DependencyProperty so it can support databinding?

Sorry, my mistake. I just assumed it wasn't a DP because I got a strange Error when databinding it to the Length of an array. This problem is not associated with the UniformGridLayout. You get this message also on a TextBlock.Text property.
<TextBlock Text="{x:Bind Columns.Length}" />

The Columns property is an Array of integers.
private int[] Columns = new int[5];

I'm not sure why this 'Derived classes must provide an implementation' goes off. There are many workarounds which I could use. For instance adding an extra ColumnLength property like below.
private int ColumnsLength => Columns.Length;

You can close the issue. Sorry for not investigating it enough before I created it.


Allow organizations to set limits on invite link access

Currently VS Live Share allows anyone with an invite link to sign in and join a collaboration session. The invite link identifier is only valid while collaboration session is active (so time is a factor), is large, and non-guessable which increases the overall security of the approach. However, while this is convenient and reduces friction for guests some organizations may want to lock down to specific individuals instead.
Organizations should be able to establish a set of users in a Live Share “account” and set minimum invite link access at one of the following levels:

Anonymous access (if supported, see #3)
Anyone with the link
Anyone in the account
Specific groups

Organizations should be able to change these settings at any time and have this update any existing links automatically.

Hi All, I am a PM on the VS Live Share team and we are starting to look at this feature more.  If you are interested in it please shoot me an email @ JOEMEL at Microsoft.com

Just wondering if there had been progress on this? I am trying to get my Azure AD admin to enable this when logged in via work account (Office365) however they are concerned that the session link could be shared externally (on purpose) breaking out security policy. If admins could set a minimum level (in our case, internal users only) this would enable us to start using the extension.

@joemellin : My company is using Visual Studio for almost everything. As our process are partially have to comply to external regulations security is of major concern. Being able to centrally define a closed user group (e.g. for the companies domain) is a key feature for us.

@fubaduba @joemellin  Just stumbled across the vsls-contrib/gatekeeper extension which adds capabilities for further restrict who can you share with which seems awesome!
The collaborators are from Microsoft, so wondering what's the chance of folding that code into the live share?

For Visual Studio, we announced enterprise policies. To learn more, see the following links:

https://devblogs.microsoft.com/visualstudio/ls-policies/
https://learn.microsoft.com/en-us/visualstudio/liveshare/use/policies-visual-studio

Currently, we are not able to support policies in VS Code due to https://github.com/microsoft/vscode/issues/147756 and https://github.com/microsoft/vscode/issues/151948. When VS Code supports policies, Live Share can re-visit adding these.
Based on the above, I am going to close this issue. However, rest assured that we love your input. If you have a use-case for additional VS policies outside of what is currently available, please provide feedback at https://learn.microsoft.com/en-us/visualstudio/liveshare/use/policies-visual-studio#contact-us.


⚠ Guya.moe Proxied has degraded performance

In 69d93e5, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 21440 ms

Resolved: Guya.moe Proxied performance has improved in e0f5ed3 after 34 minutes.


Application plan in airflow is broken

When I apply some changes in multiple models, the application plan is broken. Some expected tasks are missing and the tasks are not in the correct order. This affects the correctness of the data.
I haven't managed to create a small reproduction of this, but I've met it multiple times across 0.101 and 0.104 versions.
Here I changed all my models' types to be incremental by partition instead of date (new model kind supporting bq).
The DAG is wrong. Most of the models are missing snapshots and task dependency is wrong.

In the chat @izeigerman mentioned he suspected the sensor. I met the same problem again, tried multiple times planning prod getting the same weird behavior repeatedly. I changed the DAG leaving out the external sensor and it worked.
I still don't know if this is incidental, but it may help track the issue down.
Also, nobody else has this issue apart from me :P so that would be another reason to suspect the sensor.

Actually I can confirm it.
While the DAG was running, I changed the dag python file to re-add the sensor and the DAG got messed up (pic 1).
Removing again the sensor fixed the dag (pic 2). That's the exact same DAG in the middle of its run.


FPT_RPL.1/Rollback App note 61

Does in that case immutable firmware not exist possibility during secure sequence of factory modes that there is made switch to phase mutable firmware so that then this goal rollback detection can be achieved? I thought that exactly out of this reason secure verified state sequences as in case of AVB would have been introduce?! Am I wrong or is missing here s.th. in explanation maybe?

I'm not sure I understand the question exactly, but factory modes, which implies during production, are out of scope for the evaluation as they are not the final product as it exists "in market". I don't see any value in what would seem like jury-rigging the requirement to include factory provisioning so all DSC TOEs can meet the requirement since the factory isn't part of the evaluation (since this isn't EAL4).
Does anyone have a different understanding of this question?

From Veronika:
I wanted to express my doubts about immutable firmware expression because of given set of possible Factory related tools ( apps) that are even most of times preinstalled on device for some certain factory like purpose that conducts rollback of given important device own components. I also wanted to highlight that these kind of preloaded parts should be taken into account here independently of EAL level. So it was not meant to bring in here whole FR issue. Maybe and hopefully this explains it?!

While I won't argue that newer doesn't always equal better, the entire point of this requirement is to make sure that an attacker cannot load an older version with a known vulnerability onto the DSC. Allowing the downgrade based on an authorization would seem to then bring in a lot of questions about what that authorization would look like (since it would seem to be different than the normal authorizations we have now). I'm not ready at this point to create new requirements to allow that, though if someone wants to propose something I'm happy to look at it, but this doesn't seem like a high priority to me.
If the manufacturer is going to create old versions that may be vulnerable and send them out, well I don't know that there is much we could do about it since this is a point in time evaluation with not a huge amount of life cycle review. Again, that would seem out of scope for here unless we are going to raise the EAL to something higher to bring in expectations about development/release processes. That also would seem a larger project than what we are trying to do now (maybe a good one, but it hasn't been the plan to this point).
As a possible short term change, I would just remove the first sentence about immutable firmware.
I propose to put this in for a v3 review that could include more discussion about possible tools that may be available but locked on the device.

I'm okay with removing the first sentence in the app note.  It's not necessary to add different methods of authorization for rollbacks to the v3 parking lot.  I don't think the commenter asked for this capability.

Closing at this point based on the pull request referencing this as a new issue for v3.


[Feature] Dynamic import

Dynamic import cannot be used when targeting ECMAScript 2015 modules

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
[x] 4.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[x] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Not a bug
Expected behavior:

Dynamic import should works
Steps to reproduce:

Add a dynamic import or pass a page through navParams
 let url = "";
    let PorrraMlke = import('.././perguntasFactory/dispineia/fraca/fraca').then(stringHelpers => {
      stringHelpers.reverse('Hello World');
    });

Related code:
 let url = "";
    let PorrraMlke = import('.././perguntasFactory/dispineia/fraca/fraca').then(stringHelpers => {
      stringHelpers.reverse('Hello World');
    });

A sample application via GitHub
None
Plunker (http://plnkr.co/edit/cpeRJs?p=preview)
-->
insert short code snippets here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here

Thanks for any support or help!

Guys sorry for opening this, I've found the solution.
import the asset at page, then set it as attribute as following:
_logoutPage:any ;
constructor ....
    this._logoutPage = LogoutPage;

then pass the page as navParams ()
this.navController.push(PAGE_X, {new_page: this._logoutPage} );


Customizing chromium

Hi, how are you?

I saw your article and you're a good chromium developer.
I want to customize chromium.
Can you do that?


Remove Join Condition Push CBO Rule since it was causing infinite cos…

…t based optimization for certain queries

cc @randerzander

This is resolved! Thanks all!


Slight Java spec updates

remove httpLogDetailLevel and add new API
Interfaces should not start with 'I'
Maven artifact IDs must follow similar naming structure and include group in name

@bterlson @johanste @KrzysztofCwalina Could I please get a +1 from one of you kind folk. Thanks.


Plugin Commands

TOGGLE_SELF_SERVER_GROUP
How would I go about making a server group toggle on/off using a hotkey?

https://github.com/thorwe/CrossTalk/wiki/Plugin-Commands

The My Server would be what?

and if I want to assign a usergroup to myself, the serveradmin would be the usergroup name?

yes and yes and My Server is the server name

and how do I install this now?

What?


Replace deprecated DropwizardAppRule

As per Dropwizard documentation:

Deprecated since Dropwizard 2.0.0. Please migrate to JUnit 5 and io.dropwizard.testing.junit5.DropwizardAppExtension.

JUnit4 -> JUnit5 migration guide: https://howtodoinjava.com/junit5/junit-5-vs-junit-4/

The current version of Powermock (used in a couple of test classes for mocking) lacks support for JUnit5: https://github.com/powermock/powermock/issues/830


[all Juno apps] fix index.js file with async await to be able to catch errors

This is for all Juno apps in the Juno monorepo, as well as the greenhouse apps in the greenhouse and greenhouse-extensions repos.
see example from the clusters app, which it was already changed:
// export mount and unmount functions with async import
export const mount = async (container, options = {}) => {
  await import("./App").then((App) => {
    mount.root = createRoot(container)
    mount.root.render(React.createElement(App.default, options?.props))
  })
}

It is still up-to-date

outdated


⚠ PrivateHD has degraded performance

In b476261, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1541 ms

Resolved: PrivateHD performance has improved in 83ed718.


⚠ Secret Website 3 has degraded performance

In af21540, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2794 ms

Resolved: Secret Website 3 performance has improved in 8ee4c24.


text stroke channels

Fixes #467.
(It’d be nice to consolidate this code somehow, but I don’t think that needs to block this PR.)

Thank you for adding a test! I’d like our examples to try to be representative of good visualizations and best practices (for some minimal definition of “good” and “best”); people will inevitably use them to learn and as starting points for exploration. I couldn’t think of a “good” use of the text stroke channel, so I removed it from the test, but maybe it’d be worth adding as a unit test?


find-psresource [ 3.0.0-beta10] not listing all modules with artifactory repository

Running find-psresource has strange behaviour when the NUGET repository is hosted in Artifactory
Our repository, 'powershelf', has 760 artifacts over 53 unique modules. I can list all of them with version 2.2.5
With powershellget beta, I only see 4
PS 5.1 with PowerShellGet 2.2.5:
ps:\> (find-module -repository powershelf -Credential $creds).count

53

PS 7.1.0-rc.1 with PowerShellGet 3.0.0-beta10:
ps:\> (Find-PSResource -Repository powershelf -Credential $creds).count
4

When I search for a specific module not listed within the generic find, I get my module just fine.
Additional odd behavior, when Publishing with the publish-psresource, I can not find it by name, only with no name specified, or a * specified for the name. This resolves after about 30 minutes, may be a caching issue

Thanks @adrian-andersson we havent finished the wildcard implementation for v3 nuget feeds (like artifactory) so this likely what is causing the issue. We are interested that 4 made it through--it would be interesting to know if there is some commonality between those 4 that are returned....we have a few theories as to what may be happening (it may only be hitting the first layer of the repository index) but this would help us diagnose the issue...thanks!

Hi @SydneyhSmith I did a comparison and noted that find-psresource command is returning the first 4 modules in alphabetical order, and I can get the same result with find-module -repository powershelf -Credential $creds|sort-object -Property name |select-object -first 4
Happy to close and revisit this at a later date

Thanks @adrian-andersson we still plan to address this

Hi @adrian-andersson, is this still an issue with the latest previews?

Thanks @StevenBucher98
Seems in this beta, with Find-PSResource -name is now a mandatory param. Wildcards don't seem to work with Artifactory repositories with nuget feeds v2 or v3 though. As a result, Unable to 100% verify this is resolved. It works for psgallery though.
Wildcards on artifactory feeds is a pretty big mess. Example using my artifactory repo (Powershelf) and comparing to PSGallery:
Wildcards are clearly not working. It might be an artifactory limitation so I will keep experimenting
`
get-module powershellget
ModuleType Version    PreRelease Name                                ExportedCommands

Binary     3.0.12     beta       PowerShellGet                       {Find-PSResource, Get-PSResource, Get-PSResourceR…
ps:> find-module -Repository PSGallery -Name carb*
Version              Name                                Repository           Description

2.11.0               Carbon                              PSGallery            Carbon is a PowerShell module for automating the configuration Windows 7, 8, 2008, and 2012 and automation the installation and configuration of Windows appl…
1.0.0                Carbon.Core                         PSGallery            Functions that make doing things in PowerShell a little easier. We think these should be part of PowerShell itself. Core functions that are used by other Car…
2.2.0                Carbon.Cryptography                 PSGallery            Makes encrypting and decrypting strings and other security work easy.
1.0.0                Carbon.Windows.Installer            PSGallery            The Carbon.Windows.Installer module is a Windows-only module that has functions for reading and installing Windows MSI…
ps:> find-psresource -Repository powershelf -Name carb* -Credential $creds
ps:> find-psresource -Repository powershelf -Name carbon -Credential $creds
Name   Version Prerelease Repository Description

Carbon <IP_ADDRESS>            powershelf Carbon is a PowerShell module for automating the configuration Windows 7, 8, 2008, and 2012 and automation the installation and configuration of Windows applications, websites, and services. It can …
ps:> find-psresource -Repository powershelf -Name * -Credential $creds
Name   Version Prerelease Repository Description

Carbon <IP_ADDRESS>            powershelf Carbon is a PowerShell module for automating the configuration Windows 7, 8, 2008, and 2012 and automation the installation and configuration of Windows applications, websites, and services. It can …
ps:> find-psresource -Repository powershelf -Name psrapid -Credential $creds
Name    Version Prerelease Repository Description

psrapid <IP_ADDRESS>            powershelf A PowerShell API Framework
ps:> find-psresource -Repository powershelf -Name psrap* -Credential $creds
`

Hi,
I confirm that this issue is still happening on 3.0.16-beta16 with Find-PSResource and Artifactory using wildcard.
> Find-PSResource -Name * -Repository Test -Verbose
VERBOSE: Searching in repository Test
VERBOSE: No packages found in repository: Test.

> Find-PSResource -Name PwshCore -Repository Test -Verbose
VERBOSE: Searching in repository Test

Name     Version Prerelease Repository Description
----     ------- ---------- ---------- -----------
PwshCore <IP_ADDRESS>            Test       PowerShell wrapper for Rest API

This situation is a blocker for moving onto version 3.0 at the moment. Is there any way to contribute to your testing?

I can confirm that this is also an issue for GitLab package registries at least as current as v15.2.2-ee.

I'm seeing the same for nuget feeds under Nexus OSS 3.38 configured as PS repositories.

@aproposts @indented-automation could you let us know the url for your registries?

Sorry for the slow reply, I saw the reply then got busy and forgot.
https://gitlab-internal.domain.com/api/v4/projects/135/packages/nuget/index.json
No packages are returned when using wildcards, but can be found if the exact name is given.

@anamnavi we should test this with your changes in #1144

Find all was not supported for v3 repositories because many have upstreams which could have expensive unintended consequences, additionally there was not native api support so we prioritized getting base features working before adding the customization logic for v3 support. We can special case for artifactory (and other repos) and plan to do this-- just need to finish up a few other bugs first 😄

Would love to know from folks on this issue if you expect upstream sources to be picked up in a find all call?

Hi @SydneyhSmith I have switched roles/companies, no longer have access to Artifactory to test, sorry!.

FWIW, I can get a (partial) list of modules from a GitHub Repo iff I specify the Name with one or more letters followed by a wildcard. For example:
Find-PSResource -Repository MyRepo -Name A*
I'm running PowerShell v7.3.8. Below are my package management-related versions:
Microsoft.PowerShell.PSResourceGet    1.0.0
Microsoft.PowerShell.SecretStore      1.0.6
PackageManagement                     1.4.4
Microsoft.PowerShell.SecretManagement 1.1.2
PowerShellGet                         3.0.22  beta22

Over a year later meanwhile with AzureDevops Artifact feed, using latest release (1.0.6) of PSResourceGet, can't use any wildcards at all using v3 endpoint:
>Find-PSResource -Repository CustomFeedv3 -Name * -Credential $RepoCred
Find-PSResource: Find all is not supported for the V3 server protocol repository 'PFMLCustomFeedv3'

[...]
Find with Name containing wildcards is not supported for the V3 server protocol...

However, registering a PSResource repo w/ v2 at least allows a partial wildcard:
Find-PSResource -Repository CustomFeedv2 -Name M*
for instance works, assuming "MyFirstModule" or whatever exists.


Vampirika/moam orb

Added Moam new ability - orb of annihilation.
Changed Moam attack type missle-splash to accomodate AoE.

@vampirika Oops I forgot that your branches are on a fork so I can't push straight to them. Could you fix the merge conflict?

@vampirika Oops I forgot that your branches are on a fork so I can't push straight to them. Could you fix the merge conflict?

Think I've resolved the conflicts there.


Update sbt-scalajs-crossproject to 1.1.0

Updates org.portable-scala:sbt-scalajs-crossproject from 1.0.0 to 1.1.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.0.0).
You might want to review and update them manually.
core/src/main/scala/io/chrisdavenport/epimetheus/CollectorRegistry.scala

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.portable-scala", artifactId = "sbt-scalajs-crossproject" } ]

labels: sbt-plugin-update, semver-minor, old-version-remains

Superseded by #289.


Include groupId in maventest

Executing tests in a maven reactor solution of mine fails if -pl argument does not specify groupId, ie
-pl groupId:artifactId.
If groupdId is not specified, the tests fail with [ERROR] Could not find the selected project in the reactor... . Including the groupId causes the test to correctly run.
Sorry, I couldn't find any discussion about this.

@andrewwillette Hello!
Could you explain how to reproduce this issue?

@GiuseppeMP sorry, it's been a long time since I've worked on maven solutions such as what brought this up. I'm going to close this issue.
The problem arose from a complex module structure I don't have on my machine anymore (enterprise software of former employer).


Update TCP to SpringBoot/SpringCloud 2.0.x

set default output content-type in post-processors
replace config. properties inheritance by composition
Resolves missing documentation generation

Resolves #4

@artembilan thanks for the reminder! I've updated the authors and dates docs and mentioned the .
fyi, first I thought that those changes are "cosmetic" and i don't have to add my name to the authors list.


TM1py Time Series Forecasting Question

Hi Marius,  I got the sample Jupyter Notebook, just wondering how to get the retail cube and time series view to learn how TM1py works by running the codes in the sample.  If retail cube does not exist in any of the sample database with TM1 installation, I can create it myself, just want to know whether there is another tm1py example that creates this cube and view, there are many examples in master sample folder, thank you

Hi @slu18,
sorry for the extremely late reply. for the time series forecasting use case, I recommend you check out the Cubike sample.
we provide a help article and a script to set up your environment with all required dimensions and cubes.
https://github.com/cubewise-code/tm1py-samples/tree/master/Samples/Cubike
https://code.cubewise.com/blog/data-science-with-tm1-planning-analytics
Cheers
Marius


add fixture 'eurolite/led-fe-1500'

add fixture 'eurolite/led-fe-1500'
update register.json

Thank you @Fxedel!

Export files validity
(Output of test script tests/github/exports-valid.js.)
Test the exported files of selected fixtures against the plugins' export tests.
You can run a plugin's export tests by executing:
$ node cli/run-export-test.js -p <plugin name> <fixtures>
Fixture eurolite/led-fe-1500 changed in this PR

d-light

attributes-correctness

:white_check_mark: eurolite/led-fe-1500-9ch.xml

ecue
ofl
qlcplus

xsd-schema-conformity

:white_check_mark: Eurolite-LED-FE-1500.qxf


fix greatest/least function non-vectorized processing to ignore null argument types

Description
Fixes a flaw in greatest and least functions non-vectorized expression processing to ignore null valued arguments for determining the output type. For example, given an expression like least(1.0, 1, null), the getOutputType method correctly chooses DOUBLE as the output type, however during non-vectorized processing, we incorrectly consider it, which ends up with the default STRING output type, resulting in incorrectly using the STRING comparator instead of the double comparator as expected. This can cause odd effects and incorrect results because values like 1.0 and 1 are considered distinct when using the string comparator, while the same when using a numeric comparator.
The added tests fail without the changes in this PR.
This PR has:

[x] been self-reviewed.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[x] been tested in a test Druid cluster.

I think it would be great to have consistency check testcase which ensures that from now on the contract that least should behave the same in non-vectorized mode and in vectorized mode .... (or that's already there with some trick I've missed?)
I understand that this patch fixes a consistency issue - but I'm a bit confused to see that it will be allowed to have DOUBLE typed null for the least function; shouldn't others like + also follow the same principle?
for example: with the proposed changes the following testLeast1() will pass; however testAdd will not.
  @Test
  public void testLeast1()
  {
    ObjectBinding a = new SingleInputBindings(ExpressionType.DOUBLE);
    ExpressionType t1 = Parser.parse("least(1.0 , 2.0)", ExprMacroTable.nil()).eval(a).type();
    ExpressionType t2 = Parser.parse("least(1.0 , null)", ExprMacroTable.nil()).eval(a).type();
    assertEquals(t1, t2);
  }

  @Test
  public void testAdd()
  {
    ObjectBinding a = new SingleInputBindings(ExpressionType.DOUBLE);
    ExpressionType t1 = Parser.parse("1.0 + 2.0", ExprMacroTable.nil()).eval(a).type();
    ExpressionType t2 = Parser.parse("1.0 + null", ExprMacroTable.nil()).eval(a).type();
    assertEquals(t1, t2);
  }

is that okay? couldn't the same happen for + ?

I think it would be great to have consistency check testcase which ensures that from now on the contract that least should behave the same in non-vectorized mode and in vectorized mode .... (or that's already there with some trick I've missed?)

Technically neither of these functions are vectorized yet and just rely on the fallback stuff introduced in #16366. There are such tests that fit this purpose, but none of the fallback stuff has been added here https://github.com/apache/druid/blob/master/processing/src/test/java/org/apache/druid/math/expr/VectorExprSanityTest.java https://github.com/apache/druid/blob/master/sql/src/test/java/org/apache/druid/sql/calcite/SqlVectorizedExpressionSanityTest.java because its basically like.. all the functions i guess.

I understand that this patch fixes a consistency issue - but I'm a bit confused to see that it will be allowed to have DOUBLE typed null for the least function; shouldn't others like + also follow the same principle?

So, the greatest and least functions do not follow the same behavior as math operations, for whatever reason a null argument does not result in the output of the function being null the same way add does. See comment in https://github.com/apache/druid/blob/master/processing/src/main/java/org/apache/druid/math/expr/Function.java#L635.
The reason the output type is double in your first test is because the result is 1.0, while the reason it is string in the second one is a sort of legacy behavior of non-vectorized expressions where the output type of null values is STRING. Generally, when dealing with ExprEval, the type is ignored if the value is null because it isn't trusted. Vectorized expressions on the other hand will create a 'null' vector of whatever the inferred output type of the expression is, so that addition example when vectorized has an output type of double, with null value vectors.

one more question: is it true that a null will always be of type STRING?

Null constants always will be currently, while null values from columns will be whatever column type they came from (e.g. long column make ExprEval with ExpressionType.LONG with null values). The exception to from columns is in cases where we have no type information and are using expressions, which discover the types on the fly with ExprEval.bestEffortOf, in which case they also will be string like constants.


Wrong measurement after 10min on ESP8266EX + Arduino 2.2.1 w/ example getDistance

Using the getDistance.ino example and a ESP8266EX board (Wemos D1 R1), i get wrong measures after ~10min.
Sensor is placed on a horizontal dark surface, and reads 56 to 57mm steady - which is approximate to the real distance.
After about 10 to 12 minutes, distance jumps to meters without any change to distance or environment.
This behavior is consistent and reverts after board power off/power on.
Example calibration data:

After running sensor calibration and adjusting que sketch:

After further 10min without resetting the board, measures will tend to go down at an exponential decay of 2 to 3mm per measure, but will stabilize at ~2.5x the effective distance.
If i move the sensor to 100mm, it'll display  ~230mm distance.

Loop function needs a tof.sleep(); and tof.wakeup(); between readings with a non blocking loop.
Then it's fine.


Health System and some other minor changes

See Title
There will be merge conflicts, I will deal with them tomorrow (25/07) and I would appreciate some help.

The merge conflicts gave me a headache


PATH env variable doesn't reflect profile config when install/upgrade

I …

[x] am reporting a bug others will be able to reproduce and not asking a question.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
I tried to update two brew installed extensions for PHP70 and PHP71 (blackfire.io) in order to use them with my MAMP setup.
What happened (include command output)
brew refuses to read my .bashrc, .bash_profile, .zshrc and .profile file which all configure the PATH variable as follows
export PATH="/Applications/MAMP/bin/php/php7.0.30/bin:$PATH"

if I run brew upgrade it fails to do so with
==> Upgrading blackfireio/blackfire/blackfire-php56 --without-homebrew-php
Error: Version of PHP (71) in $PATH does not support this extension
       version (56). Consider installing blackfire-php-71 with the `--without-homebrew-php` flag.

and also stops the upgrade of other tools (the chain breaks, brew stops).
NOTE: I know that 7.0 is still not 7.1 nor 5.6 … but still: the error should be Version of PHP (70) in $PATH does not … … instead it's using the builtin macOS php (7.1)
I expect it to use this one:
 ~/ php --version
PHP 7.0.30 (cli) (built: Jul 17 2018 11:19:27) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
 ~/ which php
/Applications/MAMP/bin/php/php7.0.30/bin/php

What you expected to happen
brew should use my custom $PATH config, instead it ignores it when upgrading. Running brew with IRB shows the correct path value in HOMEBREW_PATH but not in PATH:
 ~/ brew irb
==> Interactive Homebrew Shell
Example commands available with: brew irb --examples
irb(main):001:0> ENV
=> {
"HOMEBREW_PROCESSOR"=>"Intel",
"HOMEBREW_DEV_CMD_RUN"=>"1",
"HOMEBREW_USER_AGENT"=>"Homebrew/1.7.1 (Macintosh; Intel Mac OS X 10.13.6)",
"HOMEBREW_AUTO_UPDATE_CHECKED"=>"1",
"HOMEBREW_COMMAND_DEPTH"=>"1",
"HOMEBREW_LIBRARY"=>"/usr/local/Homebrew/Library",
"HOMEBREW_TEMP"=>"/private/tmp",
"TERM"=>"xterm-256color",
"SHELL"=>"/bin/zsh",
"HOMEBREW_BOTTLE_DOMAIN"=>"https://homebrew.bintray.com",
"HOMEBREW_OS_VERSION"=>"macOS 10.13.6",
"HOMEBREW_REPOSITORY"=>"/usr/local/Homebrew", "HOMEBREW_SYSTEM_TEMP"=>"/private/tmp",
"HOMEBREW_RUBY_PATH"=>"/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/current/bin/ruby",
"HOMEBREW_GIT_CONFIG_FILE"=>"/usr/local/Homebrew/.git/config",
"LC_ALL"=>"en_US.UTF-8",
"HOMEBREW_RUBY_WARNINGS"=>"-W0", "HOMEBREW_PATH"=>"/Applications/MAMP/bin/php/php7.0.30/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin:/Users/rico/.rvm/gems/ruby-1.9.3-p392/bin:/Users/rico/.rvm/gems/ruby-1.9.3-p392@global/bin:/Users/rico/.rvm/rubies/ruby-1.9.3-p392/bin:/Users/rico/.rvm/bin:/Users/rico/bin:/Users/rico/.wp-cli/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/Applications/MAMP/Library/bin",
"USER"=>"riconeitzel",
"SSH_AUTH_SOCK"=>"/private/tmp/com.apple.launchd.1ZjMagFCKA/Listeners",
"HOMEBREW_ANALYTICS_USER_UUID"=>"1795C617-8A68-48DB-9958-1BD5BDE31FD0",
"HOMEBREW_CACHE"=>"/Users/riconeitzel/Library/Caches/Homebrew",
"HOMEBREW_USER_AGENT_CURL"=>"Homebrew/1.7.1 (Macintosh; Intel Mac OS X 10.13.6) curl/7.54.0",
"PATH"=>"/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Homebrew/Library/Homebrew/shims/scm",
"PWD"=>"/Users/riconeitzel",
"HOMEBREW_BREW_FILE"=>"/usr/local/bin/brew",
"HOMEBREW_MACOS_VERSION"=>"10.13.6",
"HOMEBREW_ANALYTICS_ID"=>"UA-76679469-1",
"HOMEBREW_PRODUCT"=>"Homebrew",
"SHLVL"=>"0", "HOME"=>"/Users/riconeitzel",
"HOMEBREW_PREFIX"=>"/usr/local",
"HOMEBREW_BOTTLE_DEFAULT_DOMAIN"=>"https://homebrew.bintray.com",
"LOGNAME"=>"riconeitzel", "HOMEBREW_VERSION"=>"1.7.1",
"HOMEBREW_CELLAR"=>"/usr/local/Cellar", "HOMEBREW_CURL"=>"curl",
"HOMEBREW_SYSTEM"=>"Macintosh", "__CF_USER_TEXT_ENCODING"=>"0x1F5:0:0",
"LINES"=>"67", "COLUMNS"=>"136"
}
irb(main):004:0> quit

brew doctor
 ~/ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
  /Applications/MAMP/bin/php/php7.0.30/bin/php-config
  /Applications/MAMP/Library/bin/sablot-config
  /Applications/MAMP/Library/bin/pkg-config
  /Applications/MAMP/Library/bin/MagickCore-config
  /Applications/MAMP/Library/bin/MagickWand-config
  /Applications/MAMP/Library/bin/yaz-config
  /Applications/MAMP/Library/bin/python2-config
  /Applications/MAMP/Library/bin/icu-config
  /Applications/MAMP/Library/bin/freetype-config
  /Applications/MAMP/Library/bin/xslt-config
  /Applications/MAMP/Library/bin/libpng16-config
  /Applications/MAMP/Library/bin/python2.7-config
  /Applications/MAMP/Library/bin/Magick++-config
  /Applications/MAMP/Library/bin/libpng-config
  /Applications/MAMP/Library/bin/xml2-config
  /Applications/MAMP/Library/bin/x86_64-apple-darwin13.4.0-pkg-config
  /Applications/MAMP/Library/bin/python-config
  /Applications/MAMP/Library/bin/libmcrypt-config
  /Applications/MAMP/Library/bin/curl-config
  /Applications/MAMP/Library/bin/Wand-config
  /Applications/MAMP/Library/bin/Magick-config
  /Applications/MAMP/Library/bin/pcre2-config
  /Applications/MAMP/Library/bin/pcre-config

brew config
 ~/ brew config
HOMEBREW_VERSION: 1.7.1
ORIGIN: https://github.com/Homebrew/brew
HEAD: d6a245c05110c240e680da594c2cc6038998b82e
Last commit: 2 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 3b1efb5c318e46fc5fb7d812b9171140711734af
Core tap last commit: 3 days ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
CPU: octa-core 64-bit skylake
Homebrew Ruby: 2.3.7 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby
Clang: 10.0 build 1000
Git: 2.17.0 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: N/A
macOS: 10.13.6-x86_64
CLT: <IP_ADDRESS>.1.1527767617
Xcode: N/A
XQuartz: N/A

$PATH variable
 ~/ brew --env
HOMEBREW_CC: clang
HOMEBREW_CXX: clang++
MAKEFLAGS: -j8
CMAKE_PREFIX_PATH: /usr/local
CMAKE_INCLUDE_PATH: /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/libxml2:/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/OpenGL.framework/Versions/Current/Headers
CMAKE_LIBRARY_PATH: /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/OpenGL.framework/Versions/Current/Libraries
PKG_CONFIG_LIBDIR: /usr/lib/pkgconfig:/usr/local/Homebrew/Library/Homebrew/os/mac/pkgconfig/10.13
HOMEBREW_SDKROOT: /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk
ACLOCAL_PATH: /usr/local/share/aclocal
PATH: /usr/local/Homebrew/Library/Homebrew/shims/mac/super:/usr/bin:/bin:/usr/sbin:/sbin

Here you can see the PATH env var. It's impossible to change its value.

Setting the PATH must be done in the formula in a requirement if you wish to add a non Homebrew path.


the last step!!!!!

i have this problem!!!!
[www.facebook.com.netroyano.tk] acme: Error 400 - urn:acme:error:dns - DNS problem: NXDOMAIN looking up A for www.facebook.com.xxxx.tk
Error Detail:
Validation for www.facebook.com.xxxx.tk:80
Resolved to:
Used:

And the final messenge say:
Timeout during connect (likely firewall problem)

@netroyano  Likely Firewall Problem, means literally that Let'sEncrypt can't access port 80 on your host. If you are running Evilginx2 on a server behind NAT, you'll need to port forward port 80. But I recommend you to get some cheap VPS on DigitalOcean or Amazon AWS.
If you are facing this issue on VPS, check your firewall rules and allow 80 IN connections.


 But there's a new problem in engine simulator: UNRESOLVED REFERENCE.

I have the same problem but I'm not sure if it's to do with version or something else.


Hi friend, can you provide "SolarSystem-3D/resource/textures/" archive file to my email<EMAIL_ADDRESS>

Hello and thank you for your nice project, can you provide "resource/textures/" archive file to my email.
<EMAIL_ADDRESS>

@bilaizi, sent.


[vcpkg] Update the minimum version of vcpkg

Since microsoft/vcpkg and microsoft/vcpkg-tool are synchronized to update x-download related content, update to 2021-05-05 (contains x-download) version to avoid being unable to find this command:
E:\Lib\vcpkg>vcpkg install sundials --triplet x64-windows
Computing installation plan...
The following packages will be built and installed:
    sundials[core]:x64-windows -> 5.7.0#1
Detecting compiler hash for triplet x64-windows...
Could not locate cached archive: C:\Users\ch6535\AppData\Local\vcpkg\archives\df\df61b63fc4d86a443bbedaa77be748372df4bfe
c.zip
Starting package 1/1: sundials:x64-windows
Building package sundials[core]:x64-windows...
-- Downloading https://github.com/LLNL/sundials/archive/73c280cd55ca2b42019c8a9aa54af10e41e27b9d.tar.gz -> LLNL-sundials
-73c280cd55ca2b42019c8a9aa54af10e41e27b9d.tar.gz...
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' = off
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] BuiltinRegistry initialized with: ""
[DEBUG] Using vcpkg-root: E:\Lib\vcpkg
[DEBUG] Using installed-root: E:\Lib\vcpkg\installed
[DEBUG] BuiltinRegistry initialized with: ""
[DEBUG] Using buildtrees-root: E:\Lib\vcpkg\buildtrees
[DEBUG] Using downloads-root: E:\Lib\vcpkg\downloads
[DEBUG] Using packages-root: E:\Lib\vcpkg\packages
[DEBUG] Using scripts-root: E:\Lib\vcpkg\scripts
[DEBUG] Using ports-root: E:\Lib\vcpkg\ports
[DEBUG] Using versions-root: E:\Lib\vcpkg\versions
invalid command: x-download

Related: https://github.com/microsoft/vcpkg/pull/13639#discussion_r659941583 https://github.com/microsoft/vcpkg/issues/18353 etc.

/azp run

Waiting for https://github.com/microsoft/vcpkg/pull/18812 merge.

Closed for rollup PR #18838

@strega-nil-ms  I suggest to merge this PR quickly since many user have this issue.


t.maximizeWindow with firefox:headless casues testcafe to hang

What is your Scenario?
use t.maximize window on all browsers - or error cleanly and not hang.

What is your public website URL? (or attach your complete example)
https://www.immersivelabs.com
What is your TestCafe test code?
/* eslint-disable no-console */
import { Selector } from "testcafe";
fixture("Broken test")
.page(https://www.immersivelabs.com/)
.beforeEach(async (t) => {
console.log("hello");
await t.maximizeWindow();
});
test.meta("testFeature", "badTest").meta("role", "smoke")(
"Test to demo firefox issue",
async (t) => {
const demo = Selector("a[href='/demo/']");
await t.expect(demo.exists).ok("Get a demo exists");
}
);
Your complete configuration file
{
"src": "./testcafe/tests/**/*.ts",
"videoPath": "results/videos",
"testExecutionTimeout": 5000
}
Your complete test report
PS C:\Users\user\CODE\testcafe> testcafe firefox:headless  --test-meta testFeature=badTest
Using locally installed version of TestCafe.
The "filter" option from the configuration file will be ignored.
Running tests in:

Firefox 95.0 / Windows 10

Broken test
hello
Screenshots
impossible due to hang
Steps to Reproduce
just run testcafe firefox:headless  --test-meta testFeature=badTest with the test and config above
TestCafe version
1.18.1
Node.js version
14.16.1
Command-line arguments
testcafe firefox:headless  --test-meta testFeature=badTest
Browser name(s) and version(s)
firefox:headless (I have also tried firefox, chrome, chrome:headless and edge:headless)
Platform(s) and version(s)
windows, and testcafe docker image linux
Other
we have ffmpeg installed for videos as per webpage.
Its the combination of video and firefox:headless that causes the hang

Thank you for your report. I reproduced the issue. We will research it and update this thread once we have any news.


Initial Implemention of list primitive

@kuujo
I am going to merge this and will complete some of the functions like insert, iterate, etc in a separate PR because I should think about them a little bit more.  I also used Lua scripting for CheckAndSet  counter primitive function.


Publish SGP4 to WAPM

Publish the sgp4 package for satellite propagation to WAPM (prod, not dev).

This has been published to WAPM :rocket:


withdrawing tellor issue

I bought a few tellor a couple days before the delist and now I am having trouble withdrawing them.  Using chrome, metamask and a ledger I can log into my dex account fine.  When I go to the balances tab I can see my tellor. When I click withdraw the pop screen shows the amount and both the quantity and the withdraw button have a red circle with a line through them.    The number to withdraw cannot be altered and if I click withdraw the transaction fails as soon as I confirm in metamask with the withdrawl request failed please try again message.  I have withdrawn lrc from the dex before and had no issues.

Thanks to whoever made some changes.  The transaction went through today.


Error 503 - Service temporarily unavailable

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug
I have configured NPM in the correct way when it comes to port & traffic forwarding. When I use a domain with no traffic, it works well with no issue. When I use a domain with a lot of traffic on it (700-800 clients simultaneously), I get Error 503. I am using the same domain directly without passing to the proxy, and it is working perfectly fine. When I use Proxy and I keep refreshing the website, 1/4 of times works, 3/4 of times gives error 503. I use this to hide the IP of the streaming server.
""I have checked the logs and I am getting:
183#183: *127384 connect() failed (111: Connection r
efused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: <IP_ADDRESS>:8080,
upstream: "xx.xx.xxx.xx:8080", bytes from/to client:0/0, bytes from/to upstre
am:0/0""
Is there any way I can increase the load that it can handle? I want to set it to have no limits on traffic handling. Is there any way to do so?
Nginx Proxy Manager Version

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Operating System

Additional context

+1

2024/11/13 16:35:55 [error] 170#170: *2 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://<IP_ADDRESS>:3000/", host: "117.xx.xx.xxx:8888", referrer: "http://117.xx.xxx.xx:8888/"

2024/11/13 16：35：55 [错误] 170#170：2 connect（） 失败（111：连接被拒绝）连接到上游时，客户端：xx.2x.x9.x7，服务器：nginxproxymanager，请求：“GET /api/ HTTP/1.1”，上游：“http://<IP_ADDRESS>:3000/”，主机：“117.xx.xx.xxx:8888”，引用站点：“http://117.xx.xxx.xx:8888/"

Checked the reason: Part of it is an issue with the IP range. It's more appropriate to change it to the way of using environment variables.

The bug has been reproduced. The reason is that the mapping path in Docker is too long. It can be fixed by shortening the path a bit.
#start：docker compose -f docker-compose-nginx-proxy-manager.yml up -d
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - "/root/docker-data/npm/data:/data"
      - "/root/docker-data/npm/letsencrypt:/etc/letsencrypt"


Throw an API error when deleting namespace in termination

Errors from API server should be from the api/errors package in order to get a proper Status response.
Fixing a bug in namespace registry where this rule was not respected.
/cc @smarterclayton

LGTM [merge]

[merge] in wrong repository... try the green button ;-)