[BUG] OrderbyDocumentQueryTest initialization intermittently times out in CI environments

See this failure, for example.
Error message
Method com.azure.cosmos.rx.OrderbyDocumentQueryTest.before_OrderbyDocumentQueryTest() didn't finish within the time-out 60000

Stack trace
org.testng.internal.thread.ThreadTimeoutException: Method com.azure.cosmos.rx.OrderbyDocumentQueryTest.before_OrderbyDocumentQueryTest() didn't finish within the time-out 60000
at java.base@11.0.5/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.indexOf(ScheduledThreadPoolExecutor.java:1024)
at java.base@11.0.5/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.remove(ScheduledThreadPoolExecutor.java:1048)
at java.base@11.0.5/java.util.concurrent.ThreadPoolExecutor.remove(ThreadPoolExecutor.java:1751)
at java.base@11.0.5/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.cancel(ScheduledThreadPoolExecutor.java:293)
at app//reactor.core.scheduler.SchedulerTask.dispose(SchedulerTask.java:126)
at app//reactor.core.publisher.MonoDelay$MonoDelayRunnable.cancel(MonoDelay.java:135)
at app//reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionOtherSubscriber.cancel(FluxDelaySubscription.java:100)
at app//reactor.core.publisher.MonoSingle$SingleSubscriber.cancel(MonoSingle.java:101)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drainLoop(Operators.java:2013)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drain(Operators.java:1982)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.cancel(Operators.java:1794)
at app//reactor.core.publisher.Operators$DeferredSubscription.cancel(Operators.java:1430)
at app//reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionOtherSubscriber.cancel(FluxDelaySubscription.java:101)
at app//reactor.core.publisher.MonoSingle$SingleSubscriber.cancel(MonoSingle.java:101)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drainLoop(Operators.java:2013)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drain(Operators.java:1982)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.cancel(Operators.java:1794)
at app//reactor.core.publisher.Operators$DeferredSubscription.cancel(Operators.java:1430)
at app//reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionOtherSubscriber.cancel(FluxDelaySubscription.java:101)
at app//reactor.core.publisher.MonoSingle$SingleSubscriber.cancel(MonoSingle.java:101)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drainLoop(Operators.java:2013)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drain(Operators.java:1982)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.cancel(Operators.java:1794)
at app//reactor.core.publisher.Operators$DeferredSubscription.cancel(Operators.java:1430)
at app//reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionOtherSubscriber.cancel(FluxDelaySubscription.java:101)
at app//reactor.core.publisher.MonoSingle$SingleSubscriber.cancel(MonoSingle.java:101)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drainLoop(Operators.java:2013)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drain(Operators.java:1982)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.cancel(Operators.java:1794)
at app//reactor.core.publisher.Operators$DeferredSubscription.cancel(Operators.java:1430)
at app//reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionOtherSubscriber.cancel(FluxDelaySubscription.java:101)
at app//reactor.core.publisher.MonoSingle$SingleSubscriber.cancel(MonoSingle.java:101)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drainLoop(Operators.java:2013)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.drain(Operators.java:1982)
at app//reactor.core.publisher.Operators$MultiSubscriptionSubscriber.cancel(Operators.java:1794)
at app//reactor.core.publisher.Operators$DeferredSubscription.cancel(Operators.java:1430)
at app//reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionOtherSubscriber.cancel(FluxDelaySubscription.java:101)
at app//reactor.core.publisher.MonoSingle$SingleSubscriber.cancel

This has been fixed on v4.


Error when executing pixi shell ("The current system has a mismatching virtual package...")

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
$ pixi --version

pixi 0.28.0

$ pixi init test-project
$ cd test-project
$ pixi shell

  × The current system has a mismatching virtual package. The project requires '__glibc' to be at
  │ least version '2.28' but the system has version '2.26'

Issue description
I face the error mentioned above every time I create a new project and try to execute pixi shell within it. To solve this, I need to add the following to my pixi.toml file (based on the solution provided here):
[system-requirements]
libc = { family="glibc", version="2.26" }

My setup is straightforward, with my $HOME/.config/pixi/config.toml only containing the following:
default-channels = ["conda-forge", "bioconda"]

I am running Amazon Linux release 2 (Karoo).
Expected behavior
pixi shell should start a new shell in the project's environment.

We have a solution in mind that is high on the list of things we need to solve. I acknowledge that this is not a comfortable way to use pixi. The solution is explained here: https://github.com/prefix-dev/pixi/issues/346#issuecomment-2094906047.
Closing this as a duplicate. Thanks for writing down your current work around for future issue searchers.


Further fixes to bug report templates

A few more fixes to things I messed up in my git hackery

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Closing in favor of #24597


⚠ Jenkins Plugins Artifactory has degraded performance

In 7c9fc04, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1310 ms

Resolved: Jenkins Plugins Artifactory performance has improved in dd6f570 after 12 minutes.


Shell: Combining here string & line continuation breaks bash highlighting

Describe the bug
Bash script highlighting completely breaks for the rest of the file if you use a here string in combination with line continuation:
#!/usr/bin/env bash

# this works (here string)
ssh \
    "foo@bar" \
    "/usr/bin/bash" -sl <<< 'echo "test"'

# this doesn't (here string + line continuation)
ssh \
    "foo@bar" \
    "/usr/bin/bash" -sl <<< \
    'echo "test"'

echo 'now highlighting is completely broken and does not recover for the rest of the file'

Expected behaviour
Here string syntax is recognized and highlighted correctly even when followed by a line continuation.
Additional notes
I read the comment in https://github.com/github-linguist/linguist/blob/master/vendor/README.md, but it's impossible to report this bug in the grammar upstream, since that repository is now archived and unmaintained: https://github.com/atom/language-shellscript

Unfortunately, the only options are to find a new grammar that doesn't experience this issue or fork the current grammar and fix it yourself and then open a PR to change grammars.


support using D1 not also R2

Are you willing to create a library using D1 instead of R2?
D1 can be used without registering a credit card and completely eliminate the possibility of being charged a fee.
https://blog.cloudflare.com/building-d1-a-global-database/

I understand that deployment may become more complex, but why are we not using listeners provided by services like Supabase or Firebase in the first place? They offer generous free tiers and enable real-time connectivity.


Add DBKangaroo 1.0.5

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

yeah, the url in file is correct.

@KevinLaMS


Tzur issue jira template

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: elad-da:white_check_mark: tzurielweisberg:x: Ron GolanRon Golan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Linker Error finding Swift Support Libraries

Prerequisites
Start with a react-native app (not ejected Expo)
Expected Behavior
Build and run
Current Behavior
Linker error:
ld: warning: Could not find auto-linked library 'swiftFoundation'
ld: warning: Could not find auto-linked library 'swiftDarwin'
ld: warning: Could not find auto-linked library 'swiftCoreFoundation'
ld: warning: Could not find auto-linked library 'swiftCore'
ld: warning: Could not find auto-linked library 'swiftCoreGraphics'
ld: warning: Could not find auto-linked library 'swiftObjectiveC'
ld: warning: Could not find auto-linked library 'swiftDispatch'
ld: warning: Could not find auto-linked library 'swiftSwiftOnoneSupport'
Undefined symbols for architecture arm64:
Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Install react-native-ble-plx using yarn add
react-native link
Build-and-Run in Xcode

Context
The fix is to add a single empty swift file to your main app.  This will trigger Xcode to link in Swift and create a bridging header.
We should update the README to include this simple step

Oh my, I'm sorry, the README already says that and I skimmed over it.  So sorry!
(feels embarrased)

Following this solution worked for me
https://stackoverflow.com/a/56187043/9241085

@myckhel That solution worked for me as well. Thanks!

@paddlefish The fix you suggested worked when I experience the issue integrating opentok-react-native


Add Regions to info_image

Now that tugboat supports API 2.0 (thanks!), reporting additional image info can help scripts use tugboat to automate creation of images from snapshots. We added Min Disk Size last October. Now, I'm proposing we add Regions too, since a valid region must be known to successfully build a droplet from an snapshot.
Regions are reported in a comma-separated list:
Name:             Redmine on 14.04
ID:               12438838
Distribution:     Ubuntu
Min Disk Size:    20GB
Regions:          nyc1,ams1,sfo1,nyc2,ams2,sgp1,lon1,nyc3,ams3,fra1

I considered sorting the list, but decided against it, since, while I couldn't find documentation of the significance of the ordering of regions returned by the API, the sequence mirrors the sequence on the website for creating droplets, suggesting the regions may be in order of preference.
FYI – I'm not a Ruby programmer, so apologies if I've missed something. I did ensure bundle exec rspec tests are all passing, so hopefully this simple feature suggestion will be acceptable & easy to merge.

Hi @bmamlin, thanks for your contribution :+1:
I'll see if I can get this released in a 2.2.0 version by EOD 26th Jan. If I've not, ping me to remind me! :smile:


Adding ability to use PFX files

Instead of extending ClientSSLSecurity to handle keys, certs, etc plus pfx keys, I have instead opted to create a new class specifically to use pfx files.

I like this strategy.  Can you add support for passwords?  I feel that may need to be an optional 3rd param.

I like this strategy. Can you add support for passwords? I feel that may need to be an optional 3rd param.

Sure thing

Oops, failing for older versions of node, will fix

Ok @jsdevel,  I have added in passphrase support for you, tests are also now passing.

Pretty close @tomgco !  Once the last minor comments are addressed we'll merge.

Pretty close @tomgco ! Once the last minor comments are addressed we'll merge.

Thanks, just adding these changes now.

Ok, @jsdevel should be all working now and up to scratch.
Want me to rebase my commits into one, or is it good as they are?

Thanks a lot for your time and effort @tomgco :+1:
Please rebase and squash your commits into a single one as stated in our Guidelines on Submitting a Pull Request in order to get your PR merged :smiley:

We are all rebased and should be ready to go, thanks @herom and @jsdevel!

Thanks a ton @tomgco - it's people like you who make this library so awesome :smiley:

Thanks a ton @tomgco - it's people like you who make this library so awesome :smiley:

+1

@tomgco Actually tests are failing over at TravisCI because client-password.pfx has expired and therefore the test "ClientSSLSecurityPFX should be usable in a request" (see here) throws an error.
Since you introduced this valuable extension and provided the files for testing would it be possible for you to add a valid file so that the tests are passing? Thanks a lot :+1:

@tomgco can you re-generate the pfx files with a really long expire time or upload the command you used to create them?

It would be nice if we scripted these with bash or something.

@jsdevel Hi, sorry about this, I haven’t got the scripts on hand at the moment but should be able to upload a script and a new cert come the weekend.

@tomgco :+1:
@jsdevel should we restart all tests on currently open PRs and merge them since you've commented out the currently invalid test?

should be able to upload a script and a new cert come the weekend.

Thanks @tomgco!  That would be great :smile:

should we restart all tests on currently open PRs and merge them since you've commented out the currently invalid test?

I think we'll need to call for a rebase first, otherwise the restart will continue to fail with the test uncommented.  But yes, we should notify other PR authors.


[Snyk] Security upgrade golang from 1.22.5-bookworm to 1.22.7-bookworm

Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

build/Dockerfile

We recommend upgrading to golang:1.22.7-bookworm, as this image has only 89 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Integer Overflow or Wraparound SNYK-DEBIAN12-EXPAT-7855502
  571

Integer Overflow or Wraparound SNYK-DEBIAN12-EXPAT-7855503
  571

XML External Entity (XXE) Injection SNYK-DEBIAN12-EXPAT-7855507
  571

Out-of-bounds Read SNYK-DEBIAN12-CURL-7575306
  514

Out-of-bounds Read SNYK-DEBIAN12-CURL-7575306
  514

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 XML External Entity (XXE) Injection

Already updated #201


custom containment like jquery

Hello
how to do droppable over custom many droppable divs from source
is there any better tutorial guide of this module,  step by step actually I want to learn how you did this
Thanks,

there is a containment option available, check out the docs.


Lab06 -- Low Hanging Fruit

Lab06 submission for elswenson and andrewtran1995.

In accordance with Professor Conrad's new lab06 turn in instructions, please make a new pull request into the branch with your username.  Thanks!


Wishlist: use real literals instead of the current fractional permission inductive

It would be much nicer to write pts_to r #0.5R v than pts_to r #(half_perm full_perm) v.

This is now the case!


AWS Backup 'everything' S3 Failing job

Expected Behavior
AWS Backup job 'everything' should complete successfully each night.
Actual Behavior
Backup resources with resource type 'S3' are currently failing with an 'access denied' error:
Access denied
Your backup job failed as AWS Backup does not have permission to describe resource arn:aws:s3:::{env}-production20220617125755072300000001. Please review your IAM policies to ensure AWS Backup can protect your resources.

Steps to Reproduce the Problem
run the 'everything' backup job in AWS Backup.
Version
latest
Modules
Backup
Account
All

AWSBackupServiceRolePolicyForS3Backup added as per https://github.com/ministryofjustice/modernisation-platform-terraform-baselines/pull/388

Modernisation Platform bumped to version 6.4.0 as per the above PR.
https://github.com/ministryofjustice/modernisation-platform/pull/6187 has now been merged into Main on MP. I check the backup in the morning to confirm that they have successfully run.

S3 Backups are now running successfully without the access denied error, I am therefore closing this ticket.


Add advanced material to Gapminder-R-Intro

[ ] Cross tabulation
[ ] Aggregation (with for loop)
[ ] apply()
[ ] Melt and dcast
[x] DC ecology on ddply
[ ] Tapply() vs ddply()
[ ] Tidyr, dplyr

dplyr: http://www.datacarpentry.org/R-ecology-lesson/04-dplyr.html

Also, demonstration of how assignment operators differ in R.
head(within(gapminder, foo = log10(gdpPercap))) # Breaks
head(within(gapminder, foo <- log10(gdpPercap))) # Works

Also:
mean(x = 1:10)
x

mean(x <- 1:10)
x


[Doc] Updated installation instructions

Update of the installation instructions for Ubuntu 18.10+ as per #84.

That is a risk, yes, but as long as Pattypan stays locked with OpenJFX 8 max and given that Debian-based distributions (and apparently Fedora also) still ship OpenJDK 8 and 11, but will only provide OpenJFX for the latter, then there is no good solution for this.
@yarl talked to me about rewriting the whole tool in (node)JS, that would solve the problem but in the meantime, I think the workaround can benefit to Linux users.


Windows CI: test-unit on pkg\plugins

Signed-off-by: John Howard<EMAIL_ADDRESS>Fixes up the failing unit tests for the WindowsTP4 context for pkg\plugins. It moves the unix:// socket specific test "TestLocalSocket" to a unix file. It also annotates where more work needs to be done in the future. However, this does at least mean that we are closer to turning off the "ignore test-unit failures on WindowsTP4" flag.
Previously failing chunk of output:
00:04:43.532 --- FAIL: TestLocalSocket (0.00s)
00:04:43.532 	discovery_test.go:44: listen unix C:\Windows\TEMP\docker-test763715871\echo.sock: socket: An address incompatible with the requested protocol was used.
00:04:43.532 FAIL
00:04:43.532 coverage: 34.6% of statements
00:04:43.532 FAIL	github.com/docker/docker/pkg/plugins	1.067s

Job: Docker-PRs FAILED:

---
---> Making bundle: validate-gofmt (in bundles/1.11.0-dev/validate-gofmt)
Congratulations!  All Go source files are properly formatted.

---> Making bundle: validate-lint (in bundles/1.11.0-dev/validate-lint)
Errors from golint:
pkg/plugins/discovery_test_unix.go:13:1: comment on exported function TestLocalSocket should be of the form "TestLocalSocket ..."

Please fix the above errors. You can test via "golint" and commit the result.

Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs] $ /bin/sh -xe /tmp/hudson3182780647624608556.sh
+ set +x

---

Job: Docker-PRs-experimental FAILED:

---
---> Making bundle: validate-gofmt (in bundles/1.11.0-dev/validate-gofmt)
Congratulations!  All Go source files are properly formatted.

---> Making bundle: validate-lint (in bundles/1.11.0-dev/validate-lint)
Errors from golint:
pkg/plugins/discovery_test_unix.go:13:1: comment on exported function TestLocalSocket should be of the form "TestLocalSocket ..."

Please fix the above errors. You can test via "golint" and commit the result.

Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-experimental] $ /bin/sh -xe /tmp/hudson5174449498060581730.sh
+ set +x

---

Job: Docker-PRs-userns FAILED:

---
 ---> f9158d6fd655
Step 49 : COPY . /go/src/github.com/docker/docker
 ---> b963a7e32d86
Removing intermediate container a2612dc075fb
Successfully built b963a7e32d86

---> Making bundle: binary (in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15: undefined: setup
pkg/plugins/discovery_test_unix.go:51: undefined: fmt in fmt.Sprintf
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-userns] $ /bin/sh -xe /tmp/hudson7741412886625654945.sh
+ set +x

---

Job: Docker-PRs-experimental FAILED:

---
fault-seccomp)

---> Making bundle: validate-gofmt (in bundles/1.11.0-dev/validate-gofmt)
Congratulations!  All Go source files are properly formatted.

---> Making bundle: validate-lint (in bundles/1.11.0-dev/validate-lint)
Errors from golint:
pkg/plugins/discovery_test_unix.go:13:1: exported function TestLocalSocket should have comment or be unexported

Please fix the above errors. You can test via "golint" and commit the result.

Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-experimental] $ /bin/sh -xe /tmp/hudson5774010780065544460.sh
+ set +x

---

Job: Docker-PRs FAILED:

---
fault-seccomp)

---> Making bundle: validate-gofmt (in bundles/1.11.0-dev/validate-gofmt)
Congratulations!  All Go source files are properly formatted.

---> Making bundle: validate-lint (in bundles/1.11.0-dev/validate-lint)
Errors from golint:
pkg/plugins/discovery_test_unix.go:13:1: exported function TestLocalSocket should have comment or be unexported

Please fix the above errors. You can test via "golint" and commit the result.

Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs] $ /bin/sh -xe /tmp/hudson6117997767298544660.sh
+ set +x

---

Job: Docker-PRs-userns FAILED:

---
 ---> 8a92e4cb792d
Step 49 : COPY . /go/src/github.com/docker/docker
 ---> 1642a19f5851
Removing intermediate container 516ce484053d
Successfully built 1642a19f5851

---> Making bundle: binary (in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15: undefined: setup
pkg/plugins/discovery_test_unix.go:51: undefined: fmt in fmt.Sprintf
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-userns] $ /bin/sh -xe /tmp/hudson3767659972222514309.sh
+ set +x

---

Job: Docker-PRs-gccgo FAILED:

---
 be
# officially supported.
#
# Try this instead: make all
#

---> Making bundle: gccgo (in bundles/1.11.0-dev/gccgo)
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15:24: error: reference to undefined name 'setup'
  tmpdir, unregister := setup(t)
                        ^
pkg/plugins/discovery_test_unix.go:51:11: error: unexpected reference to package
   addr := fmt.Sprintf("unix://%s", c)
           ^
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-gccgo] $ /bin/sh -xe /tmp/hudson129357482376204975.sh
+ set +x

---

Job: Docker-PRs-Win2Lin FAILED:

---
(in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15: undefined: setup
pkg/plugins/discovery_test_unix.go:51: undefined: fmt in fmt.Sprintf
---
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson2451725031993907883.sh
+ set +x

---

Job: Docker-PRs FAILED:

---
fault-seccomp)

---> Making bundle: validate-gofmt (in bundles/1.11.0-dev/validate-gofmt)
Congratulations!  All Go source files are properly formatted.

---> Making bundle: validate-lint (in bundles/1.11.0-dev/validate-lint)
Errors from golint:
pkg/plugins/discovery_test_unix.go:13:1: exported function TestLocalSocket should have comment or be unexported

Please fix the above errors. You can test via "golint" and commit the result.

Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs] $ /bin/sh -xe /tmp/hudson7540651350061942565.sh
+ set +x

---

Job: Docker-PRs-experimental FAILED:

---
fault-seccomp)

---> Making bundle: validate-gofmt (in bundles/1.11.0-dev/validate-gofmt)
Congratulations!  All Go source files are properly formatted.

---> Making bundle: validate-lint (in bundles/1.11.0-dev/validate-lint)
Errors from golint:
pkg/plugins/discovery_test_unix.go:13:1: exported function TestLocalSocket should have comment or be unexported

Please fix the above errors. You can test via "golint" and commit the result.

Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-experimental] $ /bin/sh -xe /tmp/hudson8043801209311699110.sh
+ set +x

---

Job: Docker-PRs-gccgo FAILED:

---
 be
# officially supported.
#
# Try this instead: make all
#

---> Making bundle: gccgo (in bundles/1.11.0-dev/gccgo)
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15:24: error: reference to undefined name 'setup'
  tmpdir, unregister := setup(t)
                        ^
pkg/plugins/discovery_test_unix.go:51:11: error: unexpected reference to package
   addr := fmt.Sprintf("unix://%s", c)
           ^
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-gccgo] $ /bin/sh -xe /tmp/hudson5603263953707491118.sh
+ set +x

---

Job: Docker-PRs-userns FAILED:

---
 ---> 49dfe757fd14
Step 49 : COPY . /go/src/github.com/docker/docker
 ---> 770d8a1a528b
Removing intermediate container f93ed6334a38
Successfully built 770d8a1a528b

---> Making bundle: binary (in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15: undefined: Setup
pkg/plugins/discovery_test_unix.go:51: undefined: fmt in fmt.Sprintf
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-userns] $ /bin/sh -xe /tmp/hudson2820295050436749536.sh
+ set +x

---

Job: Docker-PRs-Win2Lin FAILED:

---
(in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15: undefined: setup
pkg/plugins/discovery_test_unix.go:51: undefined: fmt in fmt.Sprintf
---
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson5203218971774439376.sh
+ set +x

---

Job: Docker-PRs-gccgo FAILED:

---
 be
# officially supported.
#
# Try this instead: make all
#

---> Making bundle: gccgo (in bundles/1.11.0-dev/gccgo)
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15:24: error: reference to undefined name 'Setup'
  tmpdir, unregister := Setup(t)
                        ^
pkg/plugins/discovery_test_unix.go:51:11: error: unexpected reference to package
   addr := fmt.Sprintf("unix://%s", c)
           ^
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-gccgo] $ /bin/sh -xe /tmp/hudson337313262746345270.sh
+ set +x

---

Job: Docker-PRs FAILED:

---
 of statements
ok  	github.com/docker/docker/pkg/parsers/kernel	0.003s	coverage: 56.8% of statements
ok  	github.com/docker/docker/pkg/parsers/operatingsystem	0.004s	coverage: 90.0% of statements
ok  	github.com/docker/docker/pkg/pidfile	0.005s	coverage: 57.1% of statements
?   	github.com/docker/docker/pkg/platform	[no test files]
# github.com/docker/docker/pkg/plugins
pkg/plugins/discover_unix_test.go:51: undefined: fmt in fmt.Sprintf
pkg/plugins/discovery_test.go:76: undefined: setup
FAIL	github.com/docker/docker/pkg/plugins [build failed]
ok  	github.com/docker/docker/pkg/plugins/pluginrpc-gen	0.006s	coverage: 50.4% of statements
?   	github.com/docker/docker/pkg/plugins/pluginrpc-gen/fixtures	[no test files]
ok  	github.com/docker/docker/pkg/pools	0.007s	coverage: 87.9% of statements
ok  	github.com/docker/docker/pkg/progress	0.003s	coverage: 79.2% of statements
?   	github.com/docker/docker/pkg/promise	[no test files]
ok  	github.com/docker/docker/pkg/proxy	0.005s	coverage: 81.1% of statements
ok  	github.com/docker/dock
---

Job: Docker-PRs-experimental FAILED:

---
 of statements
ok  	github.com/docker/docker/pkg/parsers/kernel	0.003s	coverage: 56.8% of statements
ok  	github.com/docker/docker/pkg/parsers/operatingsystem	0.003s	coverage: 90.0% of statements
ok  	github.com/docker/docker/pkg/pidfile	0.002s	coverage: 57.1% of statements
?   	github.com/docker/docker/pkg/platform	[no test files]
# github.com/docker/docker/pkg/plugins
pkg/plugins/discover_unix_test.go:51: undefined: fmt in fmt.Sprintf
pkg/plugins/discovery_test.go:76: undefined: setup
FAIL	github.com/docker/docker/pkg/plugins [build failed]
ok  	github.com/docker/docker/pkg/plugins/pluginrpc-gen	0.015s	coverage: 50.4% of statements
?   	github.com/docker/docker/pkg/plugins/pluginrpc-gen/fixtures	[no test files]
ok  	github.com/docker/docker/pkg/pools	0.003s	coverage: 87.9% of statements
ok  	github.com/docker/docker/pkg/progress	0.002s	coverage: 79.2% of statements
?   	github.com/docker/docker/pkg/promise	[no test files]
ok  	github.com/docker/docker/pkg/proxy	0.009s	coverage: 78.3% of statements
ok  	github.com/docker/dock
---

Job: Docker-PRs-gccgo FAILED:

---
46s
ok  	github.com/docker/docker/pkg/parsers/operatingsystem	0.049s
ok  	github.com/docker/docker/pkg/pidfile	0.042s
?   	github.com/docker/docker/pkg/platform	[no test files]
# github.com/docker/docker/pkg/plugins
pkg/plugins/discover_unix_test.go:51:11: error: reference to undefined name 'fmt'
   addr := fmt.Sprintf("unix://%s", c)
           ^
pkg/plugins/discovery_test.go:76:24: error: reference to undefined name 'setup'
  tmpdir, unregister := setup(t)
                        ^
FAIL	github.com/docker/docker/pkg/plugins [build failed]
ok  	github.com/docker/docker/pkg/plugins/pluginrpc-gen	0.047s
?   	github.com/docker/docker/pkg/plugins/pluginrpc-gen/fixtures	[no test files]
ok  	github.com/docker/docker/pkg/pools	0.047s
ok  	github.com/docker/docker/pkg/progress	0.045s
?   	github.com/docker/docker/pkg/promise	[no test files]
ok  	github.com/docker/docker/pkg/proxy	0.049s
ok  	github.com/docker/docker/pkg/pubsub	1.216s
ok  	github.com/docker/docker/pkg/random	0.044s
?   	github.com/docker/docker/pkg/reexec	[no test
---

Job: Docker-PRs-gccgo FAILED:

---
d/names-generator	[no test files]
ok  	github.com/docker/docker/pkg/parsers	0.039s
ok  	github.com/docker/docker/pkg/parsers/kernel	0.045s
ok  	github.com/docker/docker/pkg/parsers/operatingsystem	0.043s
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test.go:76:24: error: reference to undefined name 'setup'
  tmpdir, unregister := setup(t)
                        ^
ok  	github.com/docker/docker/pkg/pidfile	0.046s
?   	github.com/docker/docker/pkg/platform	[no test files]
FAIL	github.com/docker/docker/pkg/plugins [build failed]
ok  	github.com/docker/docker/pkg/plugins/pluginrpc-gen	0.048s
?   	github.com/docker/docker/pkg/plugins/pluginrpc-gen/fixtures	[no test files]
ok  	github.com/docker/docker/pkg/pools	0.047s
ok  	github.com/docker/docker/pkg/progress	0.046s
?   	github.com/docker/docker/pkg/promise	[no test files]
ok  	github.com/docker/docker/pkg/proxy	0.051s
ok  	github.com/docker/docker/pkg/pubsub	1.221s
ok  	github.com/docker/docker/pkg/random	0.041s
?   	github.com/docker/docker/pkg/reexec	[no test
---

Job: Docker-PRs FAILED:

---
s]
ok  	github.com/docker/docker/pkg/parsers	0.003s	coverage: 100.0% of statements
ok  	github.com/docker/docker/pkg/parsers/kernel	0.004s	coverage: 56.8% of statements
ok  	github.com/docker/docker/pkg/parsers/operatingsystem	0.003s	coverage: 90.0% of statements
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test.go:76: undefined: setup
ok  	github.com/docker/docker/pkg/pidfile	0.003s	coverage: 57.1% of statements
?   	github.com/docker/docker/pkg/platform	[no test files]
FAIL	github.com/docker/docker/pkg/plugins [build failed]
ok  	github.com/docker/docker/pkg/plugins/pluginrpc-gen	0.005s	coverage: 50.4% of statements
?   	github.com/docker/docker/pkg/plugins/pluginrpc-gen/fixtures	[no test files]
ok  	github.com/docker/docker/pkg/pools	0.003s	coverage: 87.9% of statements
ok  	github.com/docker/docker/pkg/progress	0.003s	coverage: 79.2% of statements
?   	github.com/docker/docker/pkg/promise	[no test files]
ok  	github.com/docker/docker/pkg/proxy	0.004s	coverage: 75.5% of statements
ok  	github.com/docker/dock
---

Job: Docker-PRs-experimental FAILED:

---
s]
ok  	github.com/docker/docker/pkg/parsers	0.003s	coverage: 100.0% of statements
ok  	github.com/docker/docker/pkg/parsers/kernel	0.003s	coverage: 56.8% of statements
ok  	github.com/docker/docker/pkg/parsers/operatingsystem	0.003s	coverage: 90.0% of statements
ok  	github.com/docker/docker/pkg/pidfile	0.003s	coverage: 57.1% of statements
?   	github.com/docker/docker/pkg/platform	[no test files]
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test.go:76: undefined: setup
FAIL	github.com/docker/docker/pkg/plugins [build failed]
ok  	github.com/docker/docker/pkg/plugins/pluginrpc-gen	0.014s	coverage: 50.4% of statements
?   	github.com/docker/docker/pkg/plugins/pluginrpc-gen/fixtures	[no test files]
ok  	github.com/docker/docker/pkg/pools	0.010s	coverage: 87.9% of statements
ok  	github.com/docker/docker/pkg/progress	0.003s	coverage: 79.2% of statements
?   	github.com/docker/docker/pkg/promise	[no test files]
ok  	github.com/docker/docker/pkg/proxy	0.008s	coverage: 78.3% of statements
ok  	github.com/docker/dock
---

Job: Docker-PRs-Win2Lin FAILED:

---
(in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/pkg/plugins
pkg/plugins/discovery_test_unix.go:15: undefined: Setup
pkg/plugins/discovery_test_unix.go:51: undefined: fmt in fmt.Sprintf
---
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson8359319644680871542.sh
+ set +x

---

Jenkins, Gordon and Leeroy are just completely out of sync on this PR. Closing and will open a duplicate PR which hopefully doesn't have the same issues.

Job: Docker-PRs-Win2Lin FAILED:

---
         125.1 MB
busybox             latest              d9551b4026f0        9 weeks ago         1.113 MB
hello-world         frozen              690ed74de00f        4 months ago        960 B
emptyfs             latest              11f64303f0f7        2 years ago         0 B

-----------------------------------------------
Windows CI Timeout Detection - End of debugging
-----------------------------------------------

c:\scripts>exit 0
POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson1636699447996602741.sh
+ set +x

---

Job: Docker-PRs-WoW-TP4 FAILED:

---
	      56	docker-1.11.0-dev.exe.md5
  0%
100%
	    New File  		      88	docker-1.11.0-dev.exe.sha256
  0%
100%
	    New File  		  27.1 m	docker.exe
  0.0%
  3.6%
  7.3%
 11.0%
 14.7%
 18.3%
 22.0%
 25.7%
 29.4%
 33.0%
 36.7%
 40.4%
 44.1%
 47.8%
 51.4%
 55.1%
 58.8%
 62.5%
 66.1%
 69.8%
 73.5%
 77.2%
 80.9%
 84.5%
 88.2%
 91.9%
 95.6%
 99.2%
100%

------------------------------------------------------------------------------

               Total    Copied   Skipped  Mismatch    FAILED    Extras
    Dirs :         1         0         1         0         0         0
   Files :         4         4         0         0         0         0
   Bytes :   54.38 m   54.38 m         0         0         0         0
   Times :   0:00:00   0:00:00                       0:00:00   0:00:00

   Speed :           966547288 Bytes/sec.
   Speed :           55306.279 MegaBytes/min.
   Ended : Thursday, February 11, 2016 2:44:57 AM

+ ec=0
+ set +x
INFO: Linking the built binary to /d/CI/CI-05f8c
---


Don't run backup & update credentials tests in the cluster

/ct

/ct

/ct

/cluster-test

/cluster-test

cluster-test

trigger action

add new comment


I found a bug at uibPopover directive  about popover-popup-close-delay

It seems that the popover control where hide  delayed when I set popover-popup-close-delay="xxx" , but actually it hides directly
When I looked at the source code,I found  some code may cause problem at line 4709 in function hide
ttScope.isOpen = false;

it makes the code at line 4727 doesn't work1
transitionTimeout = $timeout(removeTooltip, ttScope.popupCloseDelay);

I'm Chinese, please ignore my poor English

These line numbers do not help at all - can you please post a simple reproduction on Plunker .

I'm sorry for my careless, this bug has already been fixed before  v0.14.3


Unclear about creation of CRDs after upgrade

I just upgraded from 0.6 to 0.8, and I noticed a new CustomResourceDefinition for deletebackuprequests.ark.heptio.com is now required.
It's not clear in the changelog if I need to create the new CRD as part of the upgrade.
Also, it would be nice if there was a "sanity check" action that I could run after an upgrade to make sure all necessary k8s resources exist, and cloud provider API access is still working as expected.

Thanks for the quick response!
I appreciate that Ark is still very new, but a common upgrade procedure should be documented, and/or release specific upgrade steps should be added to the changelog for each release.
re: ark server ...
I think this command namespace should be reserved for running the actual ark daemon. The help text says "Run the ark server", which tells me that ark server foo should not be run from my workstation while administrating the cluster. Perhaps consider another namespace for server/daemon administration tasks.
re: ark server install
It's a bit off-topic, but this seems this is a perfect use-case for Helm. Unless I'm unaware of some limitation that's preventing the Ark team from using it, I don't understand the advantage of this.
re: ark server verify
Yes, this would be great- but I think it should be under a different command namespace. Perhaps ark admin or ark config.

I appreciate that Ark is still very new, but a common upgrade procedure should be documented, and/or release specific upgrade steps should be added to the changelog for each release.

We'll do our best prior to GA. Post-GA, we will most definitely include upgrade steps with each release.

Perhaps consider another namespace for server/daemon administration tasks.

Noted.

It's a bit off-topic, but this seems this is a perfect use-case for Helm. Unless I'm unaware of some limitation that's preventing the Ark team from using it, I don't understand the advantage of re-implementing Helm.

I appreciate your comment, but it's also important to note that not everyone uses Helm (I haven't, for instance). Helm also has, at least in its current form, some potential security gotchas (see https://engineering.bitnami.com/articles/helm-security.html, https://github.com/kubernetes/helm/issues/1442).
I don't think there's any harm in having an ark install method + a Helm chart, though. And once the next generation of Helm is released (where there won't be a server-side Tiller component any more), we can look at deprecating Ark's install command.
There is an open PR to add a chart for Ark to the charts repo. We'll do our best to ensure it continues to function as we release new versions of Ark.


python312Packages.mitmproxy: relax passlib

Fixes #355902

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

x86_64-linux

:white_check_mark: 8 packages built:

mitmproxy (python312Packages.mitmproxy)
mitmproxy.dist (python312Packages.mitmproxy.dist)
mitmproxy2swagger
mitmproxy2swagger.dist
python311Packages.mitmproxy
python311Packages.mitmproxy.dist
wapiti
wapiti.dist

@ofborg build python312Packages.mitmproxy

This is broken in 24.11. Should it be backported?


Porting Artificial Intelligence A Modern Approach

Might be worth checking out:
http://aimacode.github.io/aima-javascript/
And more specifically this year's work:
https://regalhotpocket.github.io/Aimacode/Chapter5/index.html
http://code.sgo.to/2018/03/05/explorables-design-patterns.html
http://code.sgo.to/2018/03/05/google-summer-of-code.html

@samuelgoto  Thank you for these links (to writing of yours), but I am not sure what you mean. As far as I see, it is NOT an issue (a bug report or feature request).


Option: PLAY , NEW GAME AND SOUND ON

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
I thinks this option should be like buttons or there should be some margin in between. It's somehow confusing me that this is a text.

Describe the solution you'd like
We can change these option into buttons or we can add some margin so that they appears more clear and nice.
Select program in which you are contributing
GSSoC'24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

@Durgesh4993 I want to contribute and i can fix this issue, if you want. please assign me this issue under GSSOC'24

Hey @MahawarHemlata I can do this with an efficient code. Please assign me this issue under GSSOC'24

Hi, I would like to work on this issue, please can you assign this to me.

@Anou25 Please raise any other issue,  i'll assign you
If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created seprate chennals for all projects...
Thank you :)

thanks @Durgesh4993

please assign me this issue ..I will fix button UI..


Updated inferno package versions to 1.3.1 stable

Inferno 1.3.1 stable was finally released today.
This PR updates the styletron-inferno package versions of inferno to 1.3.1.

Once this is merged, could you please publish to npm? I would really appreciate being able to use this in my projects :)

Nice! I was just about to do this :)
FWIW I think 1.3.1 satisfies ^1.3.0-rc.3 so you should still be able to use this...

Thanks a million for publishing really appreciate it :)

Published new version of docs as well (with styletron-inferno): http://styletron.js.org/

Saw that, thank you!


net: pkt: Allow inserting NULL data

If the data parameter in net_pkt_insert() is NULL, then just
insert amount of data but clear the area instead of copying.
Signed-off-by: Jukka Rissanen<EMAIL_ADDRESS>

What's the usecases for this? Is it worth to patch this func for 1-2 code-users?

What would be the use case for this?

What would be the use case for this?

If user wants to insert a some "space" into a net_buf, but does not really care about the values, currently he is forced to allocate a local variable and pass that to net_pkt_insert(). This PR avoids the variable allocation phase. And if the length of the buffer is variable (not known at compile time), then the local variable trick does not work, in which case a new function would be needed to be created. This fixes the issue by simple NULL check in the net_pkt_insert().

New version which clarifies the function prototype documentation.

@tbursztyka Are you ok with this one?


Ability to hide part of the relations

Is your feature request related to a problem? Please describe.
We have a labelling task involving to create a consequent amount of relations between labels. We end up having really messy samples with arrows crossing all over, which makes it really hard to isolate them, making the reviewing process somehow painful...
Unfortunately it's only possible to hide all of the relations and not just some of them.
Describe the solution you'd like
It would be really cool if one could hide relations one by one (like labels) or hide all relations coming out of a given label (pointing towards that label).
Thanks for the cool stuff! 🎉

Thank you for your feature request!
Also you can use region "eye" icon to hide a region + relation.


AraDICE task config file

The AraDICE task and associated config files are based on the following paper.
https://arxiv.org/abs/2409.11404

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: firojalam:x: baselmousiYou have signed the CLA already but the status is still pending? Let us recheck it.

@baberabb @lintangsutawika,
Can you please consider merging the pull request?
Thanks

@firojalam LGTM! One last thing: could you add an entry to lm_eval/tasks/README.md explaining the task in one sentence like all the other tasks? Thanks!

@baberabb, thanks.
Added task information as advised.

For multiple-choice tasks the default prompt format is <doc_to_text><target_delimiter><doc_to_choice> for each choice in doc_to_choice, where the default target_delimiter=" "
Some tasks failing a check where doc_to_choice starts with a space and target delimiter is also a space. Just wanted to confirm if that is the your expected format.

@baberabb , We did have a fix. Can you please check? Thanks

Hi @baberabb , sorry that this is taking time.
We fixed the formatting issue. Can you please check if it is fine now?
Thanks

@baberabb , can you please advise whether we need to do anything? Looks like it is still failing. We do not find any issue on the local test.

@baberabb , can you please advise whether we need to do anything? Looks like it is still failing. We do not find any issue on the local test.

Sorry, the failing test is unreleated. Looks good to merge! Thanks for the PR.


Filer doesn't list directories correctly

dc1-r1/weed volume -max=20 -dataCenter="DC1" -rack="Rack 1" -dir=./dc1-r1/ -port=8081 &
dc1-r2/weed volume -max=20 -dataCenter="DC1" -rack="Rack 2" -dir=./dc1-r2/ -port=8082 &
dc1-r3/weed volume -max=20 -dataCenter="DC1" -rack="Rack 3" -dir=./dc1-r3/ -port=8083 &
dc1-r12/weed volume -max=20 -dataCenter="DC1" -rack="Rack1.2" -dir=./dc1-r12/ -port=8084 &
dc2-r1/weed volume -max=20 -dataCenter="DC2" -rack="Rack 2.1" -dir=./dc2-r1/ -port=8085 &
master2/weed master -mdir=./master2 -peers=localhost:9334 &
master/weed master -mdir=./master -port=9334 &
filer/weed filer -mdir=.
These are my commands to run a cluster of servers .
Topology :
DC1 - Rack 1 + Rack 2 + Rack 3 + Rack 1 + Filer
DC2 - Rack 2.1
Each DC1 is set on different servers
On Windows Server 2008, this is the output when I tried to upload file
{"Directory":"/","Files":[{"name":"test","fid":"33,9e6009c49e"}],"Subdirectories":null}
** To a not exist directory :
{"Directory":"/test/","Files":[{"name":"test","fid":"33,9e6009c49e"}],"Subdirectories":null}
Everything seems work fine on Ubuntu 14.04, since it doesn't show the file that doesn't exist in the current directory
{"Directory":"/","Files":null,"Subdirectories":[{"Name":"test","Id":1}]}
{"Directory":"/test/","Files":[{"name":"examples.desktop","fid":"12,100190d200a658"}],"Subdirectories":null}

There is a bug fixed similar to this.

I currently cannot find the workaround that you said that was fixed here. My only options now is to use Ubuntu Server instead

@chrislusf :
Hi , This is the nearest explanation that I can find here but no solution provided
https://groups.google.com/forum/#!searchin/seaweedfs/filer/seaweedfs/wL1bCeQQ6F0/B6e2u1vpGGwJ

One thing that I also notice is the dir.LOG in Windows Server is never updated
I have tried upload 2 files with same name to different directory , but seems that the file is overwrite.
I think this was supposed to be the "flat namespace" without directory listing ?
I am using Embedded LevelDB for Filer Server.


azd github workflows for multiple environments (dev, qa, prod)

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I'm using azd up to provision the infra and deploy the app backend. It works fine locally.

I need to deploy it using azd to different environments (dev, qa, prod) using github workflows (classic CI\CD process)
I need some guidance on how to go about it, as the documentation is not clear on support for multiple environments.
Some basic questions: How do i configure my DEV and QA environment variables in different subscriptions? I see AZURE_SUBSCIRPTION_ID, how does each environment map to a different subscription?

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows and Linux

azd version?

azd version 1.10.1 (commit 31409a33266fb4a5fdbb644bc83988e725d6c7c9)

Versions

Mention any other details that might be useful
After a very successful client demo, they are looking to have this on their next environments QA and then PROD. Appreciate the help!

Thanks! We'll be in touch soon.

@vhvb1989 Does azd have general guidance about doing this, given this isn't a sample specific request?

there's some conversation going on around this here: https://github.com/Azure/azure-dev/issues/2373
Nothing planed for the short term yet


WIP: Build on MacOS.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
With this change build.sh manfests/1.1.0/opensarch-1.1.0.yml works up until k-nn, which is #737.
Current scripts for OpenSearch hard-code linux when they see -a x64. Our options are:

This change. Quick but dirty.
Reuse -a (or replace it) and change it from "architecture" to "target", so -a x64 to -a darwin-x64 and -a linux-x64.
Add another option for passing on system, e.g. -m darwin.
Remove system and arch options and use current platform in the build scripts.

Thoughts? /cc:@peternied @bbarani
Issues Resolved
Part of #38
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Reversing my stance after read up on those issues and quickly synced offline - Yup we need to support building on the mac, we have gaps around docker images and we will need to mitigate those so we can support top down building for linux, mac and windows.

Current scripts for OpenSearch hard-code linux when they see -a x64. Our options are:

This change. Quick but dirty.
Reuse -a (or replace it) and change it from "architecture" to "target", so -a x64 to -a darwin-x64 and -a linux-x64.
Add another option for passing on system, e.g. -m darwin.
Remove system and arch options and use current platform in the build scripts.

In order of preference

Not blocking contributions is important, so I would weight this highly, however if we have cycles #3 is preferred

I think is this a good north star, it allows for flexibility in systems where we have common behavior or to diverge intelligently.  Might require a lot of param plumbing

Not a fan because it conflates architecture and platform into a single parameter, this will get merged/unmerged and when we have a noarch/multi-arch target it goes off the rails.

This defers the problem into the internals of the build system, which could work, but I feel like this would lead to some components building for arm, arm64, aarch64, etc.. if we have to take their word for it it means we can have deviation in terminology which doesn't make as much sense when we will be creating a distribution that should have a single platform/architecture associated with it.


How to caught the bower install error in shell

Output of bower -v && npm -v && node -v:
(paste your output here)

Additional environment details (proxy, private registry, etc.):
Steps to reproduce the issue:

Describe the results you received:
Describe the results you expected:
Additional information:
I want to catch the bower install error, but seems that I cannot test it with
if [ bower install -q ] as it always returns false

sorry, not enough details to reproduce it, bower works fine for me


Can you require that a specific flag is used?

I saw this in the README:
 Positional Variables:
    testPositionalA - (Required) Test positional A does some things with a positional value. (default: defaultValue)
    testPositionalB - Test positional B does some less than serious things with a positional value.

and when reviewing the GoDoc page for this package I saw that positional arguments can optionally be required, but didn't spot that feature when configuring flags.
Is there an easy way to determine when a flag has been provided? Would you perhaps define a "default" instance of a configuration type to compare against the configuration type that is modified by flaggy.Parse()?

For flags, you can easily just check the value after calling flaggy.Parse().  If the value is set to something other than the default, then the caller supplied it.  If it was the default value (set by you or the language), then it was not used.
As for subcommands, you can check the Used property:
if subcommandA.Used { print("subcommand A used") }
Positional commands have a requirement parameter because leaving out positionals can cause the variables being input to shift, which is much harder to validate against.

For flags, you can easily just check the value after calling flaggy.Parse(). If the value is set to something other than the default, then the caller supplied it. If it was the default value (set by you or the language), then it was not used.

Thanks for confirming I was on the right path. I've included a response to this issue I was about to submit when I noticed your reply. The package might be overkill for the purposes of determining whether a flag was passed, but seems to be useful for my learning/prototype work.

As for subcommands, you can check the Used property:
if subcommandA.Used { print("subcommand A used") }
Positional commands have a requirement parameter because leaving out positionals can cause the variables being input to shift, which is much harder to validate against.

Ah, OK. That makes sense. Thanks for taking the time to explain all of this.

My original response:

Follow-up to my earlier post: I came across this package which allows you to diff structures for changes. This could be used against a "stock" copy of the config struct and a copy of the config struct (potentially) updated by flaggy.Parse().


Fix return value of sleep()

Actual
sleep 1
#=> #<Object:xxxxxxxx>    # Other thing like `Empty` returns. It changes every time you run

Expected
Object#sleep and Object#sleep_ms should return an Integer.
sleep 1
#=> 1

sleep 2
#=> 2

sleep 1.5
#=> 1
# (See the *note below)

sleep_ms 10
#=> 10

(*note) In this case whose argument is a Float should also return an Integer instead of a Float. See https://docs.ruby-lang.org/ja/latest/method/Kernel/m/sleep.html
To be precise, in CRuby, sleep 1.5 randomly returns 1 or 2 depending on the actual runtime situation.
But I think mruby/c can simply return a rounded value as the example code shows.

PicoIRB needs this spec otherwise SEGV occasionally happens.

Thank you.


Make all Render overrides sealed

What does the pull request do?
This is needed because at some point we might want to change the way built-in primitives are rasterized
Fixed issues
Fixes #10066

You can test this PR using the following package version. 11.0.999-cibuild0029850-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0029858-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

Same problem here, I have custom controls that inherit from Border and now they're dead...

@gusmanb Definitely agree :(
It ended up being pretty easy for my Border control though. Its a really basic one like what you're mentioning and I got it working... just had to replace Border.Child usage with UserControl.Content.

This is very bad idea.
Avalonia can almost do nothing.

@29654761 it's a bad idea to comment on merged PRs. Open a Discussion with your specific issue und use-case described. If possible, show sample code.


pyproject.toml fixes

running
pip install .
locally gives a large error output; I think we need to update pyproject.toml
Processing /Users/benjaminpope/code/dLux
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [16 lines of output]
      /private/var/folders/q3/wlh9qxyn1nxdm7v7l30qryf00000gn/T/pip-build-env-8th_ts7n/overlay/lib/python3.11/site-packages/setuptools/config/expand.py:134: SetuptoolsWarning: File '/Users/benjaminpope/code/dLux/LICENSE' cannot be found
        return '\n'.join(
      error: Multiple top-level packages discovered in a flat-layout: ['site', 'dLux', 'notebooks'].

      To avoid accidental inclusion of unwanted files or directories,
      setuptools will not proceed with this build.

      If you are trying to create a single distribution with multiple packages
      on purpose, you should not rely on automatic discovery.
      Instead, consider the following options:

      1. set up custom discovery (`find` directive with `include` or `exclude`)
      2. use a `src-layout`
      3. explicitly set `py_modules` or `packages` with a list of names

      To find more information, look for "package discovery" on setuptools docs.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

Fixed with #246


rospilot: 1.5.1-0 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository rospilot to 1.5.1-0:

upstream repository: https://github.com/rospilot/rospilot.git
release repository: https://github.com/rospilot/rospilot-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.6
previous version for package: 1.5.0-0

rospilot
* Fix wlan configuration on Bionic
* Fix Systemd service to work on Melodic
* Contributors: Christopher Berner

(waiting on sync https://discourse.ros.org/t/preparing-for-melodic-sync-2018-09-04/5919)


Cache and user administration

Hi again,
is there any chance to disable caching of parsed webpages? I think that this could save me a lot of disk space.
My second question: Is there any user administration? As far as I can see everybody can query my version of Gigablast. Since it is accessable through the internet some hackers etc. could perform a DDoS attack oder something like that. A login and password needed to search via the API would be helpful...
Thanks

no, it needs them for summary generation etc.
there was some query password at one point, you can add it to 'master passwords' if you want to code it back in.


giving "CSRF Failed: CSRF token missing or incorrect" while using both session and token login

We are using session login in website so user can multiple login and logout in multiple browser (It doesn't throw any error and keep current session while logout from another browser so we are using session login).
we are using token login in mobile application but if we are logged in multiple mobile device its giving "CSRF Failed: CSRF token missing or incorrect" while logout from another mobile device. We are using token login in mobile app because User doesn't  need to re-login in it's own mobile(as any other app does)
I have tried https://github.com/Tivix/django-rest-auth/issues/16 solution and it solves mobile device problem(as mentioned in above)
REST_SESSION_LOGIN = False
But we want to use session login too. so user does not need to re-login while logged out from another device.
We have spend a lot of time for this solution but nothing is work. Please help us!! :)

Have you seen #159?

@LeonardoGentile I used this http://www.soyoucode.com/2011/really-disable-csrf-django solution and it works fine.

@LeonardoGentile Can you explain how to and where to set this url code??. need to add any another url for LoginViewCustom class??. is there different url for session and token authentication? (I used both token and session auth)

I'm using DRF for the web app. Our iOS developer uses it using Swift. It's literally impossible to work when you can't be logged in all the time :)

@sanchig I think my comment is quite clear, what is that you don't understand?
You have to crete a new app (myapp for example) and apply the code mentioned here
Basically you creates a new class view child of LoginView provided by django-rest-auth in order to include an extra authentication_classes field

Yeah I understand that. Although.
>>> from rest_framework.authentication import TokenAuthentication
>>> from rest_auth.registration.views import LoginView
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "d:\Projects\test\venv\lib\site-packages\rest_auth\registration\views.py", line 10, in <module>
    from allauth.account.views import ConfirmEmailView
ImportError: No module named allauth.account.views

It requires installing allauth module.

@andreyshipilov I recommend you read the docs.

@cho-is I recommend you provide useful comments instead.

@andreyshipilov do you have rest_auth.registration in your INSTALLED_APPS?

@cho-is yeah man. Basically I solved this problem temporarily by creating an endpoint for getting an CSRF token.

https://github.com/tomchristie/django-rest-framework/issues/3538#issuecomment-153375679
Tom Christie suggests that the login view should explicitly have no authentication classes.
Is there any chance of having that change implemented?

Try including
REST_FRAMEWORK = {
'DEFAULT_AUTHENTICATION_CLASSES': (
'rest_framework.authentication.TokenAuthentication',
)
}

There should be a better way to solve this. Why isn't this default? There is no reason to have auth classes for public views, and csrf_exempt does nothing for cases if you are not using sessions.

@dudanogueira, first of all - thanks!
In addition, I believe that setting the authentication_classes to be () is enough, and there is no need to use the csrf_exempt

any update? In development phase, I need the browseable api, so I have to use both token and session auth. Though there's an easy workaround, it'll be nice to have an official fix.

Basically, using just that:
'rest_framework.authentication.BasicAuthentication',
'rest_framework.authentication.TokenAuthentication',

works.

Basically, using just that:
'rest_framework.authentication.BasicAuthentication',
'rest_framework.authentication.TokenAuthentication',

works.

I have access to a token authentication and the session browsable API.
Deleted SessionAuthentication and included BasicAuthentication.
Works for me.

Basically, using just that:
'rest_framework.authentication.BasicAuthentication',
'rest_framework.authentication.TokenAuthentication',

works.

This worked for me too.
Deleted the SessionAuthentication and included BasicAuthentication.

if you are doing it from postman try deleting the cookies. It worked for me.

For me adding @api_view(['POST']) worked

`from rest_framework.authentication import SessionAuthentication, BasicAuthentication
class CsrfExemptSessionAuthentication(SessionAuthentication):
def enforce_csrf(self, request):
    return  # To not perform the csrf check previously happening`

Now Replace authentication_classes SessionAuthentication with CsrfExemptSessionAuthentication

if you are doing it from postman try deleting the cookies. It worked for me.

This solution worked for me


Only complete unmanaged branches in the .git/machete editor

So that branches that are already listed in .git/machete aren't suggested (related: #341).

Also, a repeated branch isn't underlined with red squiggles:

Also, a repeated branch isn't underlined with red squiggles:

will be done in a separate issue: https://github.com/VirtusLab/git-machete-intellij-plugin/issues/1195

I am not convinced of this idea. I can imagine a situation when I want to reorganize the branch layout and at first, I am "repeating" a branch name in the new, desired place, and then I remove the primary occurrence of it. Why? E.g. I do not want to forget the branch name that I want to move. In our project, it may not be the case as we have general freedom of choosing branch names, but I think there could be projects with branches feature/2137, feature/2317, feature/2137-2, etc. So once you remove the first entry I may easily mistype it in the new place.
I would appreciate an opinion from someone outside of this project (@radeusgd can you share your feeling about it if you have any?).

☝🏻 huh makes sense indeed... let's put this issue on hold then. #1195 is, however, non-controversial, methinks

I am not convinced of this idea. I can imagine a situation when I want to reorganize the branch layout and at first, I am "repeating" a branch name in the new, desired place, and then I remove the primary occurrence of it. Why? E.g. I do not want to forget the branch name that I want to move. In our project, it may not be the case as we have general freedom of choosing branch names, but I think there could be projects with branches feature/2137, feature/2317, feature/2137-2, etc. So once you remove the first entry I may easily mistype it in the new place.
I would appreciate an opinion from someone outside of this project (@radeusgd can you share your feeling about it if you have any?).

We do have non-trivial issue names (wip/<username>/<issue-shortname>-<issue-id> where <issue-id> is a pretty long de-facto-random number) so it may be hard to remember the suffix - but if autocomplete helps with that it shouldn't be an issue either.
If I'm editing the machete file I'd normally use Ctrl+Shift+<Up/Down arrow> to swap lines and then fix indentation. So I would never remove a branch anyway if I want to keep it - so from my subjective perspective it doesn't really matter too much. I kind of like the fact that not-completing helps avoid writing the same branch twice, but I'm not convinced it changes much really.

cool. Thanks a lot for the extensive answer

Closing then!


external-url not used in RubiconConfiguration

https://github.com/prebid/prebid-server-java/blob/711bfa44c5319d310f61c2f42b3e6ce489022d19/src/main/java/org/prebid/server/spring/config/bidder/RubiconConfiguration.java#L45
Is this on purpose :smile: ? IMHO the externalUrl should be used in the UserSyncer, right?

Yeah, but not each bidder requires it. Rubicon doesn't need redirect url.

I stumbled upon this as I fixed this in our code to make rubicon work :smile:

So... do we have here to do anything?

In our internal fork we add the externalUrl to the UserSyncCreator, depending on your judgement you can keep leave it null here or add it :shrug: :smile:


Feature request: intellisence and error detection for reg files

basic features:

suggest available path inside square brackets
suggest available keys and their default for sections

advanced features:

underline wrong syntax
underline wrong path
underline wrong values and suggest to fix them: use default values instead

May be I will implement it.


Fixes Fate IT race conditions

I merged this to the elasticity branch in 2c8947b90044344fb049a334388aa2fbf46271bb and would appreciate a confirmation there weren't any merge bugs introduced in the conflict resolution. There was a conflict with the FateIT in that branch, but that test appears to not be working in that branch (unrelated to this - it failed before and after the merge in the same way - a NoNode exception).

@ctubbsii I pushed bdf22da852f8f2f5177de1ace95974901e636a7f to remove some redundant code that may have been introduced in 2c8947b90044344fb049a334388aa2fbf46271bb


Need a standard for docstring writing

It's pretty a mess for the moment... And probably write it down in the CONTRIBUTING guide.

When we started writing the library, I asked you about that, and we agreed to use the numpy style for the docstring (https://numpydoc.readthedocs.io/en/latest/format.html).

This should be mentioned in the contributing guide.

PyCharm can be configured to use numpy style in Settings | Tools | Python Integrated Tools | Docstring format | Numpy

But I think that the default reStructuredText syntax has the advantage of being used by Sphinx/ReadTheDocs.
I don't know whether sphinx can be configured for other docstring styles.

Maybe this solves the problem with sphinx: https://github.com/numpy/numpydoc


Missing or empty dependency-check.html

This is related to #325 and possibly to #189 as well. With #189 fixed I thought I'd give 1.3.1 a try but in more cases than not I don't see a valid dependency-check.html. I'm wondering if it's simply a user mistake...
I have a multi-module project and all tests / modifications were done in Maven root.
Command line
mvn org.owasp:dependency-check-maven:1.3.1:aggregate -DlogFile=./dependency-check.log -q works ok. I get a valid target/dependency-check.html.
Running during build
With the above working fine I "Mavenized" the command by adding the following to a profile in the pom.xml:
<build>
<plugin>
  <groupId>org.owasp</groupId>
  <artifactId>dependency-check-maven</artifactId>
  <version>1.3.1</version>
  <executions>
    <execution>
      <goals>
        <goal>aggregate</goal>
      </goals>
    </execution>
  </executions>
</plugin>

This doesn't work, it produces target/dependency-check.ser but no HTML file.
Running during site build
Next I added it to the site build like so:
<plugin>
  <groupId>org.owasp</groupId>
  <artifactId>dependency-check-maven</artifactId>
  <version>1.3.1</version>
  <reportSets>
    <reportSet>
      <reports>
        <report>aggregate</report>
      </reports>
    </reportSet>
  </reportSets>
</plugin>

When I run mvn site I get a 0KB target/site/dependency-check.html but  target/dependency-check.ser seems sufficiently big (6.2KB).

The aggregate goal has known issues with anything beyond site:site (i.e. stage, deploy). We have a plan to resolve this issue - but it will require running the plugin twice. However, you appear to be having issues with just site:site.
Can you provide the mvn -v and the output of mvn site -X?

I just had another thought on why the aggregate goal may be failing for some people. Is there any chance one or more of the modules are skipped during the build (specifically, the last module in the reactor)?
[INFO] Reactor Summary:
[INFO]
[INFO] parent1 ............................................ SUCCESS [ 21.041 s]
[INFO] project1 ........................................... SUCCESS [  8.034 s]
[INFO] project2 ........................................... SUCCESS [  9.684 s]
[INFO] project3 ........................................... SKIPPED

Can you provide the mvn -v

Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T15:51:42+02:00)
Maven home: /Applications/ApacheGroup/Maven-3.2.2
Java version: 1.8.0_11, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_11.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"

and the output of mvn site -X

That'd be 56M of information I can't disclose, sorry. However, I can confirm that none of the ~40 modules was skipped.
I also tried with Maven 3.3.3 but the result is the same. Every module and the root project have a /target/dependency-check.ser.

If you used the check goal you get valid HTML reports in all of the projects - correct? Completely understand that is not ideal when dealing with 40+ modules, just want to confirm there isn't something else going on.

I just confirmed, yes, the check goal produces valid HTML reports.

Thanks for the information.  I am still not entirely sure why it is failing on your installation. Let me describe exactly how the aggregate goal works (currently) and this may give you a clue.
As dependency-check requires the maven perform dependency resolution it only works on a module after the compile phase. As such, the aggregate goal runs the equivelent of the check goal on each child module, when it gets to the last child it will then cycle through all the results of the previous results to build the dependency-check aggregate report. This results in the following:

When the parent pom is processed maven generates a blank dependency-check report
Each child project will have a valid .ser file; this is the serialized data to build the dependency-check report.
If the last module is skipped, the blank aggregate report will not be over-written by the correct aggregate report.
If a plugin is moving the site results, such as site:stage, then when the parent pom is processed a blank dependency-check report is generated and then moved to the staging directory. Once the last child module is processed the correct dependency-check aggregate report is written to the original site directory - but has not been moved to the staging directory.

From your earlier comments I don't think item 4 is causing the issue in your case, but I could be mistaken. I will be reaching out to the maven developer list to see if I am missing something or if they can suggest a different approach.
I have also been considering making the aggregate goal a report-only goal that does not actually run dependency-check. Instead it would entirely rely upon the serialized data file. The downside of this is that you would have to run maven twice to generate the aggregate goal.

I may have just figured out what the problem is - are any of the modules configured to skip the Maven site? Example:
    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
        <maven.compiler.source>1.8</maven.compiler.source>
        <maven.compiler.target>1.8</maven.compiler.target>

       <maven.site.skip>true</maven.site.skip>

    </properties>

I believe this issue has been resolved in the 1.3.5-SNAPSHOT. The patch will be included in the next release. However, issue #325 is still present and will likely have issues for anything beyond site:site (i.e. site:stage or site:deploy may result in blank reports being staged or deployed).

are any of the modules configured to skip the Maven site?

No.

well, that is unfortunate... At least I solved one reason that the report was not being generated...

I am facing the same problem. As my problem is about an open-source project this could help you to trace down the issue:
https://github.com/oasp/oasp4j/issues/401
I therefore I created this PR that is not yet accepted
https://github.com/oasp/oasp4j/pull/404
So to reproduce clone this and generate site:
https://github.com/hohwille/oasp4j

BTW (off topic): You might also like the idea of that open-source project called OASP as it cares a lot about OWASP. See here:
https://github.com/oasp/oasp4j/wiki/guide-security

The aggregation code has been completely re-written in 1.4.3-SNAPSHOT. The fix will be released with the next release.


Exported variable  has or is using private name  from external library

Hey guys not really sure what to do about this. I know this is a duplicate of #6307, but I didn't really want to comment on a closed issue. I can't really use @DanielRosenwasser's solution here because the class is exported from the library. I guess I could extend that class in my code and use that instead. Completely understand the issues with this, I guess I'm just looking for a recommendation and I wanted to report this for other people.
Error:
(4,1): error TS4082: Default export of the module has or is using private name 'Warning'.

My code:
import { optional } from 'rulr';
import { stringValue, mailto, sha1, iri, account } from '../factory';

export default {
  objectType: optional(stringValue),
  name: optional(stringValue),
  mbox: optional(mailto),
  mbox_sha1sum: optional(sha1),
  openid: optional(iri),
  account: optional(account),
};

Rulr's type definitions (generated by the TypeScript compiler):
export declare type Path = string[];
export declare class Warning {
    data: any;
    path: Path;
    constructor(data: any, path: Path);
}
export declare type Rule = (data: any, path: Path) => Warning[];
export declare const optional: (rule: Rule) => Rule;

Actually I can't extend the class, that makes no sense. I'd have to recreate every function in that library haha

Ok as to the rescue haha, I don't think this is great, but it does work.
import { optional, Rule } from 'rulr';
import { stringValue, mailto, sha1, iri, account } from '../factory';

export default {
  objectType: optional(stringValue) as Rule,
  name: optional(stringValue),
  mbox: optional(mailto),
  mbox_sha1sum: optional(sha1),
  openid: optional(iri),
  account: optional(account),
};

I am not able to get this to repro locally using your input file. can you share more context?

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

Hey @mhegazy, no worries, I'd do the same, I'm on holiday for a few more days, I'll get back to this when I'm home :smile:

Ok @mhegazy, what context do you need? 😄

can you share a self-contained sample that reproduces the issue?

Yeah I'll give that a try.

https://github.com/ryansmith94/ts-15947

This is the same issue as https://github.com/Microsoft/TypeScript/issues/9944. The declaration emitter tried to serialize the type of the property foobar, which is Rule, which is an alias to (data: any, path: Path) => Warning[];, it tried to write Warning but that would be invalid, since Warning is not imported.
The emitter does not add imports automatically to avoid divulging implementation details that the user did not intend to expose. https://github.com/Microsoft/TypeScript/issues/9944 tracks relaxing this rule.
To avoid this warning, write an explicit type annotation for the type of your property. something like this would work:
import { optional, Rule } from 'rulr';

export default <{foobar: Rule;}> {
  foobar: optional(() => []),
}

Hey @mhegazy, I did understand that already from other issues I'd found before creating this one, but thank you for the explanation anyway and thanks for referencing the duplicate issue (sorry I didn't find that in my search) 😄 I'll subscribe to that issue going forward.
Thanks for the fix too! 👍


CLOUD-601: integrationtest update to work with the new network abstraction

@biharitomi pls review

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1194/


Predictable Output Order

Minor change to Select-InventoryObject to ensure object output is sorted alphabetically.  Otherwise the output list order is unpredictable and for large inventories makes it harder for the user to find the right item to select.

I haven't tested your changes, but I have seen this behavior as well.
This will make me happy if it fixes the sorting/ordering issue.
+1

It has thus far in my testing of this change.  When performing tests to other changes in Vester, also makes it much easier to enter the same numbers at each prompt and know I'm picking the same inventory objects.

Just over here sitting on this until October 1st. 😃


Upload and programming a Leonardo board fails

I'm not sure if this has been specifically tested, but on OS X, you cannot successfully program/upload to a Leonardo Arduino board. The board works fine with the Arduino IDE, but fails every time using Platformio!
The first issue is that it doesn't sequence the port detection correctly/simply (like Arduino IDE) but you can mostly get around that (by timing the reset of the board to have the port show up and then execute the upload command, but it is very hard and painful).
The second issue is that it fails checksum for some unknown reason.
avrdude: Device signature = 0x1e9587
avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D8
avrdude: safemode: efuse reads as CB
avrdude: reading input file ".pioenvs/leonardo/firmware.hex"
avrdude: writing flash (32156 bytes):

Writing | ################################################## | 100% 2.23s

avrdude: 32156 bytes of flash written
avrdude: verifying flash memory against .pioenvs/leonardo/firmware.hex:
avrdude: load data flash data from input file .pioenvs/leonardo/firmware.hex:
avrdude: input file .pioenvs/leonardo/firmware.hex contains 32156 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.29s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x7000
0x55 != 0xc3
avrdude: verification error; content mismatch

avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D8
avrdude: safemode: efuse reads as CB
avrdude: safemode: Fuses OK (H:CB, E:D8, L:FF)

avrdude done.  Thank you.

scons: *** [upload] Error 1

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26576079-upload-and-programming-a-leonardo-board-fails?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github).

Do you have problem when specify --upload-port option for platformio run command?
P.S: We have this board in our team (@valeros has it). However, he uses it under Windows and doesn't have any problems.

Could you try this new build?
pip install https://github.com/platformio/platformio/archive/feature/issue-287.zip

I merged it to main branch. Use update command above
pip install -U https://github.com/platformio/platformio/archive/develop.zip

Yep. All sorted. Much better upload now. The 2nd issue was due to me hitting the leonardo flash limit. I forgot about the huge 4K boot loader and the program hit the 0x7000 memory limit.

Please upgrade to stable 2.3.2 where this issue is fixed:
platformio upgrade

Thanks.


invalid syntax error when specifying a variable as proxyiv

In the IV setting, when specifying a variable as proxyiv, it produces an invalid syntax error. For instance:
*load example dataset
use "https://github.com/JMSLab/xtevent/blob/main/test/example31.dta?raw=true", clear
xtset i t
xtevent y x, panelvar(i) t(t) policyvar(z) window(3) proxy(zeta) proxyiv(eta)

@Constantino-Carreto-Romero This used to work, maybe some of the changes to the parser broke something? Or is this a bug on the latest published version?
Also, shouldn't this show up when running the test file? Why did we miss it?

@jorpppp I executed it with xtevent 1.0.0 and it showed up the same error. In the test file, all the cases that use a variable as proxyiv, use a collinear variable, so the collinearity error showed first (this expected error is muted in the test file, so it doesn't stop the execution). However, in the test file, there is not an example with a non-collinear variable, so this error doesn't show up when I execute the test file. I found this bug while testing #111

@Constantino-Carreto-Romero Now that #111 is closed, can you take a closer look at this, please?

@jorpppp sure thing, I already started to check it.

@jorpppp  It seems that there are two bugs:

In this block of code, that goes from line 161 to line 175, for a proxyiv that is only numbers (numlist) or numbers and variable names (mixed), we want to include in the local ivnorm all the integers that indicate leads to use as instruments. However, the way it is designed, whenever a variable name is included as an instrument along with some lead orders (i.e., the user specifies a mixed proxyiv), this error message will be shown. This is preventing the user from using a mixed proxyiv. I think the solution is to change the foreach loop, so it loops over a version of proxyiv that doesn't contain variable names. This change doesn't affect subsequent code.
In that block of code, that check is done only for a numlist or a mixed proxyiv. If the user specifies only variable names as proxyiv (i.e., a varlist proxyiv), the local ivnorm stays empty. Then, in the code for the scaling factor, that goes from line 468 to 480, it always requires that the local ivnorm to be non-empty. This is what causes the message error pointed out in https://github.com/JMSLab/xtevent/issues/114#issue-1393094702. In this setting, where the user specified only variable names as proxyiv and thus no lead order is specified, for the scaling factor computation, ¿what coefficient number should be used as a reference? I think in this case, the program should use the coefficients the user indicated through the option norm.

@jorpppp It seems that there are two bugs:

In this block of code, that goes from line 161 to line 175, for a proxyiv that is only numbers (numlist) or numbers and variable names (mixed), we want to include in the local ivnorm all the integers that indicate leads to use as instruments. However, the way it is designed, whenever a variable name is included as an instrument along with some lead orders (i.e., the user specifies a mixed proxyiv), this error message will be shown. This is preventing the user from using a mixed proxyiv. I think the solution is to change the foreach loop, so it loops over a version of proxyiv that doesn't contain variable names. This change doesn't affect subsequent code.
In that block of code, that check is done only for a numlist or a mixed proxyiv. If the user specifies only variable names as proxyiv (i.e., a varlist proxyiv), the local ivnorm stays empty. Then, in the code for the scaling factor, that goes from line 468 to 480, it always requires that the local ivnorm to be non-empty. This is what causes the message error pointed out in invalid syntax error when specifying a variable as proxyiv #114 (comment). In this setting, where the user specified only variable names as proxyiv and thus no lead order is specified, for the scaling factor computation, ¿what coefficient number should be used as a reference?
For the scaling factor computation, the program uses the smallest lead order among the specified lead orders. I think in the case where no lead order is specified, we could make the program use the coefficients the user indicated in the option norm.

Thanks @Constantino-Carreto-Romero. This makes sense. The fix you suggest for the loop sounds good.
The value of ivnorm for the case when no leads are used should be -1.
Can you try to implement the fixes, please?

@jorpppp sure thing, I will start working on implementing it.

In this block of code, that goes from line 161 to line 175, for a proxyiv that is only numbers (numlist) or numbers and variable names (mixed), we want to include in the local ivnorm all the integers that indicate leads to use as instruments. However, the way it is designed, whenever a variable name is included as an instrument along with some lead orders (i.e., the user specifies a mixed proxyiv), this error message will be shown. This is preventing the user from using a mixed proxyiv. I think the solution is to change the foreach loop, so it loops over a version of proxyiv that doesn't contain variable names. This change doesn't affect subsequent code.

I implemented this in https://github.com/JMSLab/xtevent/commit/0fec5c442b1648f17c25df66ea2ec93f00dbca42.

In that block of code, that check is done only for a numlist or a mixed proxyiv. If the user specifies only variable names as proxyiv (i.e., a varlist proxyiv), the local ivnorm stays empty. Then, in the code for the scaling factor, that goes from line 468 to 480, it always requires that the local ivnorm to be non-empty. This is what causes the message error pointed out in invalid syntax error when specifying a variable as proxyiv #114 (comment). In this setting, where the user specified only variable names as proxyiv and thus no lead order is specified, for the scaling factor computation, ¿what coefficient number should be used as a reference?
For the scaling factor computation, the program uses the smallest lead order among the specified lead orders. I think in the case where no lead order is specified, we could make the program use the coefficients the user indicated in the option norm.

It is not possible to set ivnorm to -1 because if the normalized coefficient is norm=-1, the program doesn't compute that coefficient. The coefficient to compute the scaling factor needs to be different from the normalized coefficient. ¿What coefficient shoul we use? Temporarily, in https://github.com/JMSLab/xtevent/commit/adbdb36bfad11b0f857d9a7cdd814f03ab15cb88 I set this coefficient to be equal to norm-1.
While testing this implementation, I also noticed that the change of lead order carried out in this part of the code, only covers the case where proxyiv= norm=-1, but if they are equal to another integer, later an error appears. So in https://github.com/JMSLab/xtevent/commit/adbdb36bfad11b0f857d9a7cdd814f03ab15cb88 I also added some changes to cover those other cases. Tentatively, I added a warning message.
These are some examples check these implementations:
*install the branch version
net install xtevent, from("https://raw.githubusercontent.com/JMSLab/xtevent/issue114_proxyiv_doesnt_allow_varnames") replace

*load example dataset
use "https://github.com/JMSLab/xtevent/blob/main/test/example31.dta?raw=true", clear
xtset i t

*default case
xtevent y x, panelvar(i) t(t) policyvar(z) window(3) proxy(zeta)

*Mixed proxyiv
*This proxyiv type used to generate an error.
xtevent y x, panelvar(i) t(t) policyvar(z) window(3) proxy(zeta) proxyiv(2 3 eta)

*varlist proxyiv
*This proxyiv type used to generate an error.
*since norm = -1, the scaling factor is computed based on coefficient -2
xtevent y x, panelvar(i) t(t) policyvar(z) window(3) proxy(zeta) proxyiv(eta alpha)

*Case when a lead order = normalized coefficient.
* This change was done by the program only for the case: lead order = normalized coefficient = -1.
*But in other cases it generated an error.
*the program changes the lead order and shows a warning message.
xtevent y x, panelvar(i) t(t) policyvar(z) window(3) proxy(zeta) proxyiv(1) norm(-1)
xtevent y x, panelvar(i) t(t) policyvar(z) window(3) proxy(zeta) proxyiv(2) norm(-2)

Thanks @Constantino-Carreto-Romero. In cases when we have external instruments, we should normalize one coefficient per instrumental variable as long as the # of instruments is smaller than the LHS of the window. Can you implement this please?

update: I'm currently working on it

@jorpppp  in https://github.com/JMSLab/xtevent/commit/ddf03f73e81c6ebe97349198cfede59afa232c41 I implemented https://github.com/JMSLab/xtevent/issues/114#issuecomment-1275257341
These are some examples to check the implementation. This is the log file.

Per call:

@Constantino-Carreto-Romero will add an informative message about the normalization in the mixed IV case
@Constantino-Carreto-Romero will check that xteventplot works properly in the examples https://github.com/JMSLab/xtevent/blob/issue114_proxyiv_doesnt_allow_varnames/issue114/examples to check the implementation.do

Also note that we should change the language of the messages following #116

@jorpppp

in https://github.com/JMSLab/xtevent/commit/4255814812e7e65303006e6d337957ed1db232a2 I implemented https://github.com/JMSLab/xtevent/issues/114#issuecomment-1284207892. For the messages in this issue, I considered https://github.com/JMSLab/xtevent/issues/114#issuecomment-1284209751.
In https://github.com/JMSLab/xtevent/commit/a79b0e611568b1b8ce18bf7088c83d4350f43cde there are some examples to check the implementation. This is the log file.
I also checked that xteventplot worked properly. For instance, when executing:

xtevent y x, panelvar(i) t(t) policyvar(z) window(4) proxy(zeta) proxyiv(1 eta zeta)

Since norm equals -1, the first instrument will be changed to lead 2. Then, to normalize two more coefficients due to eta and zeta, the program will choose the coefficients closest to zero from the set of available pre-event coefficients, so it will choose -3 for eta and -4 for zeta. The resulting event study plot is this.

In a79b0e6 there are some examples to check the implementation. This is the log file.

Per call: the implementation looks correct. There are only some examples that need small changes. After that, @Constantino-Carreto-Romero can open the PR

In https://github.com/JMSLab/xtevent/commit/429f9d5487c70026a378e889474da32f7f08f828 I implemented small changes to some examples to check the implementation. I also uploaded the log file. Both of them are placed in the issue folder.
I ran the test file again and checked that xteventplot keeps working properly. For instance, when executing:
xtevent y x, panelvar(i) t(t) policyvar(z) window(4) proxy(zeta) proxyiv(1 eta u)

it produces the following plot, where the ommited coefficients are -1,-2,-3, and -4.