Added L337 support

Added L337 Support

long time coming but can you please fix merge conflicts and we will try and get this merged

See #62, both fixes there


Adding support for NVIDIA NIMs as embeddings provider

Description
Added NvidiaEmbeddingsProvider.
Checklist

[x] The base branch of this PR is dev, rather than main
[x] The relevant docs, if any, have been updated or created

Perfectly done, thanks for the contribution!


Remove mentions of paid support

Pull request checklist
Use the following template to make sure your PR fits the Teku documentation standard.
Before creating the PR
Make sure that:

[x] You've read the contribution guidelines.
[x] You've previewed your changes locally.

Describe the change
Removes mention of paid support from footer.

Issue fixed
Fixes #403
Fixes #402

Impacted parts

For content changes:

[x] Documentation content
[ ] Documentation page organization

For tool changes:

[ ] CircleCI workflow
[ ] Build and QA tools (for example lint or vale)
[x] MkDocs templates
[ ] MkDocs configuration
[ ] Python dependencies
[ ] Node dependencies and JavaScript
[ ] Read the Docs configuration
[ ] GitHub integration

After creating your PR and tests have finished
Make sure that:

[x] You've fixed any issues raised by the tests.
[x] You've previewed your changes on Read the Docs
and added a preview link.

Preview
https://pegasys-teku--404.com.readthedocs.build/en/404/

@NicolasMassart may be best placed to review this. We still have the following in footer.html, and I'm not sure if that needs to be deleted/updated as well:
{% if config.extra.support.paid %}       Questions or feedback? You can obtain paid professional support by {{config.extra.support.company}} at {{config.extra.support.email}}


Add support to skip action notifications when executed under workflow context

This pull request resolves https://github.com/StackStorm/st2/issues/5221

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

Thanks for the contribution.
The bug fix / change looks good to me overall, I just had some questions / comments as far as tests and action-chain workflows go.

For some reason after merging this, those new tests are failing for me locally with this error - https://gist.github.com/Kami/52543866f5400e29537f00911654bfe1.
No idea (yet) why it happens locally, but not on CI. I likely won't have time to dig in before the weekend.

OK, I see the issue - https://github.com/StackStorm/st2/pull/5227/files#diff-c86e8df3fb95a5e1b0806ce20a77ee1a92f721e933a1d230e5a302b1ebb10873R210.
This function needs some more love. Right now it will return as soon as execution has 1 or more children, but from the code that's not actually what we want - we want to wait for 2 children. So the code needs to be changed to handle that better otherwise it will be prone to timing / race conditions.
I will push a fix shortly.

Here we go - 5856fa482.
I confirmed that with this change, the tests now consistently pass locally.

Here we go - 5856fa4.
I confirmed that with this change, the tests now consistently pass locally.

Thanks for fixing the test case 👍


Request support for door sensor MC400D

Log Message

Please paste logs here
Cette erreur provient d'une intégration personnalisée

Logger: custom_components.tuya_local.config_flow
Source: custom_components/tuya_local/config_flow.py:216
Integration: Tuya Local (documentation, issues)
First occurred: 17 février 2024 à 07:38:34 (7 occurrences)
Last logged: 10:53:17

Connection test failed with <class 'Exception'> Unable to find device on network (specify IP address)

Information about DPS mappings

Please paste the output here.
```{
  "result": {
    "model": "{\"modelId\":\"000003eglo\",\"services\":[{\"actions\":[],\"code\":\"\",\"description\":\"\",\"events\":[],\"name\":\"默认服务\",\"properties\":[{\"abilityId\":1,\"accessMode\":\"ro\",\"code\":\"doorcontact_state\",\"description\":\"\",\"extensions\":{\"attribute\":\"768\"},\"name\":\"门磁状态\",\"typeSpec\":{\"type\":\"bool\",\"typeDefaultValue\":false}},{\"abilityId\":2,\"accessMode\":\"ro\",\"code\":\"battery_percentage\",\"description\":\"\",\"extensions\":{\"attribute\":\"128\"},\"name\":\"电池电量\",\"typeSpec\":{\"max\":100,\"min\":0,\"scale\":0,\"step\":1,\"type\":\"value\",\"typeDefaultValue\":0,\"unit\":\"%\"}}]}]}"
  },
  "success": true,
  "t":<PHONE_NUMBER>459,
  "tid": "c5994be1ce4211eea4757ade033758b0"
}

<!--
If you do not have access to iot.tuya.com, please try to identify as
many DPs as possible, by experimenting with your device.  Please also
note any ranges and scale factors for input numbers, and possible
values and their meanings for any input strings (enums).
-->

# Product ID

<!--
If you have access to the IoT portal, please paste just the product_id
line from API Explorer: "Devices Management" / "Query Device Details in Bulk".
You will also find the local_key in here, please take care not to post that
publicly.  If you do, then re-pairing the device with the mobile app will
refresh the local key.

Alternatively, tools that do local discovery, such as tinytuya, may be able
to show the product id without needing access to the developer portal.

Although this information is optional and not required, it will be
used in future to identify matching devices.
-->
{
  "result": [
    {
      "active_time":<PHONE_NUMBER>,
      "bind_space_id": "6957558",
      "category": "mcs",
      "create_time":<PHONE_NUMBER>,
      "custom_name": "détecteur Bar",
      "icon": "smart/icon/ay1537847617560vAgbw/5526564c1ac295a5a9eeea014fb2d02e.jpg",
      "id": "bfd65e3354a7dc06a62xyp",
      "ip": "<IP_ADDRESS>",
      "is_online": true,
      "lat": "50.7500",
      "local_key": "",
      "lon": "1.7300",
      "model": "MC400D",
      "name": "Contacter le capteur",
      "product_id": "5etnzhfidcmm0ang",
      "product_name": "WIFI门磁",
      "sub": false,
      "time_zone": "+01:00",
      "update_time":<PHONE_NUMBER>,
      "uuid": "28f4450dc9e97e07"
    }
  ],
  "success": true,
  "t":<PHONE_NUMBER>891,
  "tid": "2d0364e2ce4311ee9d7cfe8b4d072f7e"
}

# Information about how the device functions

<!--
If there is a manual or other explanation available online, please
link to it (even if not in English) Otherwise if it is not obvious
what all the functions do, please give a brief description.
-->
Thanks in advance

Is this a battery powered WiFi device?  The log message would suggest that thee device itself is not reliably present on WiFi, which would mean it cannot be supported.

Oops sorry, yes, it's a battery powered device ( door sensor).
Thanks for your answer


Modified apiEndpoint breaks Amplitude Instrumentation Explorer

Expected Behavior
Expect events to be tracked using the new apiEndpoint provided

Current Behavior
No events are shown in the plugin

Possible Solution
Allow JS SDK or Plugin to change apiEndpoint for watching the talks

Steps to Reproduce

init client with a custom apiEndpoint in config
open plugin in chrome to no events

Environment

JS SDK Version: 7.1.0
Installation Method: Yarn
Browser and Version or React Native and Device: Chrome 84 - MacOS Catalina 10.15.6

Thanks for the report, will look into this

@Naismith are you using a custom endpoint or api2.amplitude.com? Version 0.1.2 of the instrumentation explorer should be able to listen to changes, but we can keep this open to consider more generic api endpoints.

@Naismith are you using a custom endpoint or api2.amplitude.com? Version 0.1.2 of the instrumentation explorer should be able to listen to events on api2.amplitude.com, but we can keep this open to consider more generic api endpoints.

I am using a custom endpoint

@jooohhn and @kelvin-lu has there been any progress on this? Just checking in.

Hey @Naismith we're tracking this internally - we're hoping to have updates this week or in the coming week so that the instrumentation explorer can be configured to other endpoints!

Hi @Naismith , are there any updates on this issue? It still doesn't work with the latest version of amplitude-js (8.14.0) and amplitude instrumentation explorer (0.3.3)

Is this SDK working fine with the custom endpoint?
This sounds like an issue for the event explorer, I found that we have a list of api endpoints hard-coded there to listen to with webRequest API. So I don't think custom endpoint is supported with the current event explorer yet, we can probably support custom endpoint with the webRequest API too.


Error  Compiling mockito v0.22.0

error[E0432]: unresolved imports assert_json_diff::Comparison, assert_json_diff::Actual, assert_json_diff::Expected
--> /home/olexiyb/.cargo/registry/src/github.com-1ecc6299db9ec823/mockito-0.22.0/src/lib.rs:527:24
|
527 | use assert_json_diff::{Comparison, assert_json_no_panic, Actual, Expected};
|                        ^^^^^^^^^^                        ^^^^^^  ^^^^^^^^ no Expected in the root
|                        |                                 |
|                        |                                 no Actual in the root
|                        no Comparison in the root
error[E0603]: function assert_json_no_panic is private
--> /home/olexiyb/.cargo/registry/src/github.com-1ecc6299db9ec823/mockito-0.22.0/src/lib.rs:527:36
|
527 | use assert_json_diff::{Comparison, assert_json_no_panic, Actual, Expected};
|                                    ^^^^^^^^^^^^^^^^^^^^ this function is private

thx! :relaxed:


remove flaky flag & disable devicelab tests

Description
With https://github.com/flutter/flutter/pull/72401 submitted, a couple of rows have been run with a success. This PR remove the flaky flag, and skip the devicelab tasks.
Related Issues
https://github.com/flutter/flutter/issues/71615

LGTM! Can you update the migration spreadsheet with this info?

Will do.


Support for PROXY Protocol

Is it possible to accept PROXY Protocol traffic from within the UI?
If I go in and manually edit the files it works, but requesting certs resets the files so it's not really a viable alternative.
https://docs.nginx.com/nginx/admin-guide/load-balancer/using-proxy-protocol/

Lack of proxy protocol is a non-starter.
You can't be running this stuff in a cluster behind a cloud firewall and then not be able to listen with proxy protocol. Without it, the applications lose the IP information from the origin client. Geo-based content becomes impossible.
I'm going to look at the source code to see if this is an easy fix. Seems like a checkbox or toggle is all that would be needed as proxy_protocol is just a single directive that goes with the listener line in NGINX.

Correct yes a simple toggle in the UI would be enough to get this moving, saved to the db table and the backend template just needs to know about that value.
This kind of thing wasn't part of the project's goal. It's generally not expected that people using this for their home gateway would be using a load balancer or HA.

I did some digging through the source code and I can see how to add support for this. There are models to update, etc. But.. you are correct. I also reviewed a few other things and concluded that this is a good system for a home lab, but it can't do things like setup backend streams or sets of target servers for load balancing. And without that, it would be pretty senseless to add proxy protocol because anyone utilizing proxy protocol is most certainly doing so to load balance their services.
I wouldn't mind using this in a homelab environment myself, but the problem is that I usually need to mimic the production environment as closely as possible so that I can see how things will (hopefully) work in the real world.
I think I will still spin this up though and play with it.

I would like to support adding listen ssl proxy_protocol,
Thanks.
like this:
listen                     443 ssl http2 proxy_protocol;

I'm looking forward to adding this option!

Hopefully I'd see this feature get supported soon.
I can think of one instance where support of proxy protocol is great for home settings: Users with two or more WANs.
Personally my old test setup with dual-wan + proxy is like this:

This also works well if you have multiple domains that you want to serve from different machines.
You can use a load balancer that splits the traffic using SNI (so it doesn't need to know about the certificate) and then proxies it on so originating IP data isn't lost.

Hello @jc21
Is there any update is it going to be added?

I'd also really like this, though my use-case is a bit obscure:
My home server is behind a CGNAT, so I use rathole behind an nginx server on a VPS to passthrough the raw TCP stream to my server's NPM instance. This works great, but when I check the logs of anything running on the server (e.g. Authentik), it always shows the local rathole IP instead of the real client IP. Using the PROXY protocol between the VPS and NPM would fix this, assuming the applications read X-Forwarded-For. There are other solutions, but this would definitely be the easiest and most robust one.

Strongly needed, can this feature be included in the development plan

Is this still going to be added? I need proxy protocol support for my setup, really don't want to move off of NPM.

I want to setup https://github.com/stalwartlabs/mail-server in my home environment, and I only have 1 public IP. Therefore, NPM handles all my traffic. But for stalwart mail server, I need the proxy to be able to speak PROXY protocol: https://stalw.art/docs/server/reverse-proxy/proxy-protocol

I want to setup stalwartlabs/mail-server in my home environment, and I only have 1 public IP. Therefore, NPM handles all my traffic. But for stalwart mail server, I need the proxy to be able to speak PROXY protocol: stalw.art/docs/server/reverse-proxy/proxy-protocol

Do you need NPM to proxy all ports explicitly?
I'm running docker-mailserver next to NPM just fine, with the latter listening on 80+443 and the former on all the mail stuff like 25 or 143.
Unless you have things like custom load balancing set up in your NPM config that you want to leverage by setting up a stream module, you shouldn't need NPM as a middle-man on mail ports.

You can theoretically send the smtp imap ports directly to stalwart and only send the port 8080 for the gui via NPM, but then you have to include the certificates I think


Switch to tracing everywhere

Specific Demand
We have a number of crates that are not updated to use tracing and instead still use log + fern/env_logger/simple_logger. The ecosystem seems to have moved to tracing. The CLI specifically needs to be updated, among others.

I imagine the documentation here needs updating too?


Matching service nevin

Has bugs:

When user 1 creates room and user 2 joins the existing room, after that room is closed, user 2 hits the difficulty button and creates a new room, createroom is called twice.

LGTM (except the bugs)


make stuck at "Getting org.scala-sbt sbt 0.13.5 ..."

Simplified output:
"
bin/sbt package
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
Getting org.scala-sbt sbt 0.13.5 ...
"
I guess it is downloading something, so I tried to use proxy for acceleration but it do not works either.
If it is downloading something, is it possible to download it before make？
Full output of make:
"$ make
wget "http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.13.7/sbt-launch.jar" -P bin
--2020-05-30 16:31:03--  http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.13.7/sbt-launch.jar
Resolving repo.typesafe.com (repo.typesafe.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>
Connecting to repo.typesafe.com (repo.typesafe.com)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://dl.bintray.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.13.7/sbt-launch.jar [following]
--2020-05-30 16:31:05--  http://dl.bintray.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.13.7/sbt-launch.jar
Resolving dl.bintray.com (dl.bintray.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to dl.bintray.com (dl.bintray.com)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 302
Location: http://akamai.bintray.com/b4/b407b2a76ad72165f806ac7e7ea09132b951ef53?gda=exp=1590828185~hmac=48f612be861eff248e253b67dd7b1b258db78425e4642b32f06567a9e9152397&response-content-disposition=attachment%3Bfilename%3D%22sbt-launch.jar%22&response-content-type=application%2Foctet-stream&requestInfo=U2FsdGVkX18YHXR7BVjJBbdXYGjAzUainNBCIw9bFfY-AmF7H5An4hqbrM3bpoqpNGBYlMnj32WAtXQ1qE9jeyhLHpdBQYAYjyG9QT4WFqoH5Gwa5XNR-7mk2X7y3Csz_vR5J3kIgqPRwnY4YA-6lAFR5lfT-5vIV7KntyHCDsY [following]
--2020-05-30 16:31:06--  http://akamai.bintray.com/b4/b407b2a76ad72165f806ac7e7ea09132b951ef53?gda=exp=1590828185~hmac=48f612be861eff248e253b67dd7b1b258db78425e4642b32f06567a9e9152397&response-content-disposition=attachment%3Bfilename%3D%22sbt-launch.jar%22&response-content-type=application%2Foctet-stream&requestInfo=U2FsdGVkX18YHXR7BVjJBbdXYGjAzUainNBCIw9bFfY-AmF7H5An4hqbrM3bpoqpNGBYlMnj32WAtXQ1qE9jeyhLHpdBQYAYjyG9QT4WFqoH5Gwa5XNR-7mk2X7y3Csz_vR5J3kIgqPRwnY4YA-6lAFR5lfT-5vIV7KntyHCDsY
Resolving akamai.bintray.com (akamai.bintray.com)... <IP_ADDRESS>
Connecting to akamai.bintray.com (akamai.bintray.com)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1208380 (1.2M) [application/octet-stream]
Saving to: ‘bin/sbt-launch.jar’
sbt-launch.jar              100%[========================================>]   1.15M  16.2KB/s    in 71s
2020-05-30 16:32:18 (16.5 KB/s) - ‘bin/sbt-launch.jar’ saved [1208380/1208380]
bin/sbt package
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
Getting org.scala-sbt sbt 0.13.5 ...
"

I found out that creating ~/.sbt/repositories and assign some ivy and maven mirror can accelerate the downloadings.


Integration Test - Release - 2020/09/25 15:45:21

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#reassign PRMergerTest2

GitHub user PRMergerTest2 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#reassign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#please-close


Reproducing results from paper

In the appendix of their paper, Trager et al. report the IW, RW, and Avg scores on the MIT-States and the UT Zappos dataset using a pretrained and a randomly initialized CLIP ViT-L-14 model (Tables 6 and 7).
They report the following scores. Pretrained encoder (Table 6):

IW
RW
Avg

MIT-States
0.23 ± 0.05
0.43 ± 0.06
0.78 ± 0.13

UT Zappos
0.16 ± 0.04
0.51 ± 0.05
0.58 ± 0.18

Randomly initialized encoder (Table 7):

IW
RW
Avg

MIT-States
0.04 ± 0.02
0.16 ± 0.02
0.10 ± 0.03

UT Zappos
0.10 ± 0.02
0.22 ± 0.04
0.14 ± 0.05

However, when trying to reproduce these results using the example script, we get different results. Pretrained encoder:

IW
RW
Avg

MIT-States
0.06 ± 0.03
0.20 ± 0.06
0.88 ± 0.08

UT Zappos
0.03 ± 0.01
0.26 ± 0.05
0.75 ± 0.12

Randomly initialized encoder (these obviously change with each execution):

IW
RW
Avg

MIT-States
0.02 ± 0.01
0.36 ± 0.03
0.52 ± 0.07

UT Zappos
0.04 ± 0.02
0.38 ± 0.05
0.59 ± 0.10

For the randomly initialized encoder, we do not expect results to be identical but also the overall scale seems to be off. But we would expect the pretrained encoder results to be (at least almost) identical. I also tried using the 🤗 transformers checkpoint which they linked in the paper but got the same results as with OpenCLIP.
The question is where does this difference come from? Is it a bug in the ideal word computation, is it bug in the score computation? Are we using the wrong checkpoint? Are we using the model wrong?

It seems like scores are computed inconsistently in the paper. In the text, it is stated that all scores are computed as the average of squared distances of embedding vectors. However, after some empirical testing, I suspect that they only used squared distances for the Avg score and non-squared distances for the IW and RW scores.
As this behaviour is a bit inconsistent, I want to keep the default behaviour for all scores to use squared distances. For reproducibility, I added a score_mode argument that can be specified when creating an IdealWords instance. You can choose either 'avg_dist' to use non-squared distances everywhere, 'avg_sq_dist' to use squared distances everywhere, or 'paper_repro' to use non-squared distances for IW and RW and squared distances for Avg.
Running our example script with score_mode='paper_repro' now produces results that are reasonably close to the originally reported results:

IW
RW
Avg

MIT-States
0.23 ± 0.05
0.44 ± 0.06
0.78 ± 0.18

UT Zappos
0.16 ± 0.04
0.50 ± 0.05
0.57 ± 0.17


Update part3.md

Following the steps above I spent several hours trying to "Troubleshoot slow Docker swarm performance" as each web server in my stack was taking 'forever' to respond to HTTP requests, but worked just fine when invoked directly. I noticed it was taking almost exactly 30 seconds every time, and when finishing the turorial (thus deploying Redis) I realized that the python apps were waiting for some kind of Redis timeout. After deploying with a working Redis service responses were quick as before.
As somebody new to Docker it would have been good to know that the web app itself (timing out for Redis) was causing the delay not the host system or docker configuration.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks for figuring this out and getting us the feedback! I'm sorry you ran into trouble.


H as M

According to the other issues, this has already been identified, but I guess it's a recurring problem.


Get specs passing when Bundler version is >= 2

2371 examples, 248 failures, 1 pending

Failed examples:

rspec ./spec/bundler/ui/shell_spec.rb:38 # Bundler::UI::Shell#error prints to stdout
rspec ./spec/cache/gems_spec.rb:184 # bundle cache when previously cached adds and removes when gems are updated
rspec './spec/cache/git_spec.rb[2:4]' # bundle cache with git tracks updates
rspec './spec/cache/git_spec.rb[3:4]' # bundle package with git tracks updates
rspec ./spec/cache/platform_spec.rb:45 # bundle cache with multiple platforms ensures that a successful bundle update does not delete gems for other platforms
rspec ./spec/commands/add_spec.rb:88 # bundle add shows error message when version is not formatted correctly
rspec ./spec/commands/add_spec.rb:93 # bundle add shows error message when gem cannot be found
rspec ./spec/commands/add_spec.rb:101 # bundle add shows error message when source cannot be reached
rspec ./spec/commands/binstubs_spec.rb:42 # bundle binstubs <gem> when the gem exists in the lockfile displays an error when used without any gem
rspec ./spec/commands/binstubs_spec.rb:122 # bundle binstubs <gem> when the gem doesn't exist displays an error with correct status
rspec ./spec/commands/check_spec.rb:52 # bundle check prints a generic error if the missing gems are unresolvable
rspec ./spec/commands/check_spec.rb:64 # bundle check prints a generic error if a Gemfile.lock does not exist and a toplevel dependency does not exist
rspec ./spec/commands/check_spec.rb:75 # bundle check prints a generic message if you changed your lockfile
rspec ./spec/commands/check_spec.rb:109 # bundle check ensures that gems are actually installed and not just cached
rspec ./spec/commands/check_spec.rb:189 # bundle check outputs an error when the default Gemfile is not found
rspec ./spec/commands/check_spec.rb:201 # bundle check should not crash when called multiple times on a new machine
rspec ./spec/commands/check_spec.rb:256 # bundle check --path vendor/bundle after installing gems in the default directory returns false
rspec ./spec/commands/check_spec.rb:284 # bundle check when locked shows what is missing with the current Gemfile if it is not satisfied
rspec ./spec/commands/clean_spec.rb:75 # bundle clean removes new version of gem if unused
rspec ./spec/commands/clean_spec.rb:185 # bundle clean removes old git gems
rspec ./spec/commands/clean_spec.rb:277 # bundle clean displays an error when used without --path
rspec ./spec/commands/clean_spec.rb:361 # bundle clean --clean should override the bundle setting on update
rspec ./spec/commands/clean_spec.rb:400 # bundle clean does not clean on bundle update with --path
rspec ./spec/commands/clean_spec.rb:418 # bundle clean does not clean on bundle update when using --system
rspec ./spec/commands/clean_spec.rb:464 # bundle clean when missing permissions returns a helpful error message
rspec ./spec/commands/exec_spec.rb:188 # bundle exec errors nicely when the argument doesn't exist
rspec ./spec/commands/exec_spec.rb:199 # bundle exec errors nicely when the argument is not executable
rspec ./spec/commands/exec_spec.rb:210 # bundle exec errors nicely when no arguments are passed
rspec './spec/commands/exec_spec.rb[1:25:4:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing the executable raises behaves like it runs like a normally executed executable
rspec ./spec/commands/help_spec.rb:80 # bundle help has helpful output when using --help flag for a non-existent command
rspec ./spec/commands/info_spec.rb:21 # bundle info info from specific gem in gemfile given a gem that is not installed prints missing gem error
rspec ./spec/commands/init_spec.rb:4 # bundle init generates a Gemfile
rspec ./spec/commands/init_spec.rb:9 # bundle init prints a message to the user
rspec ./spec/commands/init_spec.rb:25 # bundle init when a Gemfile already exists notifies the user that an existing Gemfile already exists
rspec ./spec/commands/init_spec.rb:34 # bundle init given --gemspec option should generate from an existing gemspec
rspec ./spec/commands/init_spec.rb:55 # bundle init given --gemspec option when gemspec file is invalid notifies the user that specification is invalid
rspec ./spec/commands/init_spec.rb:90 # bundle init when init_gems_rb setting is enabled when gems.rb already exists notifies the user that an existing gems.rb already exists
rspec ./spec/commands/inject_spec.rb:38 # bundle inject with injected gems already in the Gemfile doesn't add existing gems
rspec ./spec/commands/inject_spec.rb:45 # bundle inject incorrect arguments fails when more than 2 arguments are passed
rspec ./spec/commands/inject_spec.rb:102 # bundle inject when frozen doesn't allow Gemfile changes
rspec ./spec/commands/install_spec.rb:14 # bundle install with gem sources the simple case does not make a lockfile if the install fails
rspec ./spec/commands/install_spec.rb:154 # bundle install with gem sources the simple case activates gem correctly according to the resolved gems
rspec ./spec/commands/install_spec.rb:315 # bundle install with gem sources the simple case gracefully handles error when rubygems server is unavailable
rspec ./spec/commands/install_spec.rb:357 # bundle install with gem sources Ruby version in Gemfile.lock and using an unsupported Ruby version prints an error
rspec ./spec/commands/install_spec.rb:443 # bundle install with gem sources when requesting a quiet install via --quiet should be quiet
rspec ./spec/commands/install_spec.rb:463 # bundle install with gem sources when bundle path does not have write access should display a proper message to explain the problem
rspec ./spec/commands/install_spec.rb:480 # bundle install with gem sources when bundle install is executed with unencoded authentication should display a helpful messag explaining how to fix it
rspec ./spec/commands/lock_spec.rb:86 # bundle lock does not fetch remote specs when using the --local option
rspec ./spec/commands/lock_spec.rb:108 # bundle lock errors when updating a missing specific gems using --update
rspec ./spec/commands/lock_spec.rb:195 # bundle lock errors when removing all platforms
rspec ./spec/commands/newgem_spec.rb:786 # bundle gem uncommon gem names fails gracefully with a .
rspec ./spec/commands/newgem_spec.rb:791 # bundle gem uncommon gem names fails gracefully with a ^
rspec ./spec/commands/newgem_spec.rb:796 # bundle gem uncommon gem names fails gracefully with a space
rspec ./spec/commands/newgem_spec.rb:801 # bundle gem uncommon gem names fails gracefully when multiple names are passed
rspec ./spec/commands/newgem_spec.rb:820 # bundle gem #ensure_safe_gem_name with an existing const name should include "Invalid gem name gem"
rspec ./spec/commands/newgem_spec.rb:825 # bundle gem #ensure_safe_gem_name with an existing hyphenated const name should include "Invalid gem name gem-specification"
rspec ./spec/commands/newgem_spec.rb:889 # bundle gem on conflicts with a previously created file should fail gracefully
rspec ./spec/commands/newgem_spec.rb:900 # bundle gem on conflicts with a previously created directory should fail gracefully
rspec ./spec/commands/open_spec.rb:31 # bundle open complains if gem not in bundle
rspec ./spec/commands/open_spec.rb:49 # bundle open suggests alternatives for similar-sounding gems
rspec ./spec/commands/outdated_spec.rb:189 # bundle outdated with --local option uses local cache to return a list of outdated gems
rspec ./spec/commands/outdated_spec.rb:385 # bundle outdated with invalid gem name returns could not find gem name
rspec ./spec/commands/outdated_spec.rb:418 # bundle outdated after bundle install --deployment outputs a helpful message about being in deployment mode
rspec ./spec/commands/package_spec.rb:207 # bundle package with --frozen tries to install with frozen
rspec ./spec/commands/pristine_spec.rb:143 # bundle pristine when passing a list of gems to pristine raises when one of them is not in the lockfile
rspec ./spec/commands/show_spec.rb:47 # bundle show with a standard Gemfile complains if gem not in bundle
rspec ./spec/commands/show_spec.rb:151 # bundle show with an invalid regexp for gem name does not find the gem
rspec ./spec/commands/update_spec.rb:15 # bundle update with no arguments updates the entire bundle
rspec ./spec/commands/update_spec.rb:40 # bundle update when update_requires_all_flag is set errors when passed nothing
rspec ./spec/commands/update_spec.rb:46 # bundle update when update_requires_all_flag is set errors when passed --all and another option
rspec ./spec/commands/update_spec.rb:78 # bundle update with an unknown dependency should inform the user
rspec ./spec/commands/update_spec.rb:82 # bundle update with an unknown dependency should suggest alternatives
rspec ./spec/commands/update_spec.rb:101 # bundle update when a possible resolve requires an older version of a locked gem and only_update_to_newer_versions is set does not go to an older version
rspec ./spec/commands/update_spec.rb:178 # bundle update in a frozen bundle should fail loudly
rspec ./spec/commands/update_spec.rb:187 # bundle update in a frozen bundle should suggest different command when frozen is set globally
rspec ./spec/commands/update_spec.rb:196 # bundle update with --source option should not update gems not included in the source that happen to have the same name
rspec ./spec/commands/update_spec.rb:209 # bundle update with --source option should update gems not included in the source that happen to have the same name
rspec ./spec/commands/update_spec.rb:252 # bundle update when there is a child dependency that is also in the gemfile should not update the child dependencies of a gem that has the same name as the source
rspec ./spec/commands/update_spec.rb:285 # bundle update when there is a child dependency that appears elsewhere in the dependency graph should not update the child dependencies of a gem that has the same name as the source
rspec ./spec/commands/update_spec.rb:343 # bundle update without a Gemfile.lock should not explode
rspec ./spec/commands/update_spec.rb:372 # bundle update when a gem depends on a newer version of bundler should not explode
rspec ./spec/commands/update_spec.rb:377 # bundle update when a gem depends on a newer version of bundler should explain that bundler conflicted
rspec ./spec/commands/update_spec.rb:386 # bundle update shows the previous version of the gem when updated from rubygems source
rspec ./spec/commands/update_spec.rb:405 # bundle update shows error message when Gemfile.lock is not preset and gem is specified
rspec ./spec/commands/update_spec.rb:489 # bundle update --ruby when a different Ruby is being used than has been versioned shows a helpful error message
rspec ./spec/commands/update_spec.rb:568 # bundle update conservative patch and minor options patch preferred update all
rspec ./spec/commands/update_spec.rb:590 # bundle update conservative patch and minor options strict minor preferred
rspec ./spec/commands/update_spec.rb:687 # bundle update conservative error handling raises if too many flags are provided
rspec ./spec/install/allow_offline_install_spec.rb:17 # bundle install with :allow_offline_install with no cached data locally still fails when the network is down
rspec ./spec/install/allow_offline_install_spec.rb:28 # bundle install with :allow_offline_install with cached data locally will install from the compact index
rspec ./spec/install/allow_offline_install_spec.rb:71 # bundle install with :allow_offline_install with cached data locally will install from a cached git repo
rspec ./spec/install/bundler_spec.rb:32 # bundle install with bundler dependencies causes a conflict if explicitly requesting a different version
rspec ./spec/install/bundler_spec.rb:93 # bundle install with bundler dependencies causes a conflict if child dependencies conflict
rspec ./spec/install/bundler_spec.rb:114 # bundle install with bundler dependencies causes a conflict if a child dependency conflicts with the Gemfile
rspec ./spec/install/deploy_spec.rb:11 # install with --deployment or --frozen fails without a lockfile and says that --deployment requires a lock
rspec ./spec/install/deploy_spec.rb:16 # install with --deployment or --frozen fails without a lockfile and says that --frozen requires a lock
rspec ./spec/install/deploy_spec.rb:21 # install with --deployment or --frozen disallows --deployment --system
rspec ./spec/install/deploy_spec.rb:28 # install with --deployment or --frozen disallows --deployment --path --system
rspec ./spec/install/deploy_spec.rb:123 # install with --deployment or --frozen with an existing lockfile explodes with the --deployment flag if you make a change and don't check in the lockfile
rspec ./spec/install/deploy_spec.rb:138 # install with --deployment or --frozen with an existing lockfile can have --frozen set via an environment variable
rspec ./spec/install/deploy_spec.rb:168 # install with --deployment or --frozen with an existing lockfile explodes with the --frozen flag if you make a change and don't check in the lockfile
rspec ./spec/install/deploy_spec.rb:183 # install with --deployment or --frozen with an existing lockfile explodes if you remove a gem and don't check in the lockfile
rspec ./spec/install/deploy_spec.rb:196 # install with --deployment or --frozen with an existing lockfile explodes if you add a source
rspec ./spec/install/deploy_spec.rb:208 # install with --deployment or --frozen with an existing lockfile explodes if you unpin a source
rspec ./spec/install/deploy_spec.rb:228 # install with --deployment or --frozen with an existing lockfile explodes if you unpin a source, leaving it pinned somewhere else
rspec ./spec/install/failure_spec.rb:5 # bundle install installing a gem fails prints out why that gem was being installed
rspec ./spec/install/gemfile/gemspec_spec.rb:57 # bundle install from an existing gemspec should raise if there are no gemspecs available
rspec ./spec/install/gemfile/gemspec_spec.rb:67 # bundle install from an existing gemspec should raise if there are too many gemspecs available
rspec ./spec/install/gemfile/gemspec_spec.rb:259 # bundle install from an existing gemspec in deployment mode when the lockfile was not updated after a change to the gemspec's dependencies reports that installation failed
rspec ./spec/install/gemfile/git_spec.rb:779 # bundle install with git sources handles repos that have been force-pushed
rspec ./spec/install/gemfile/git_spec.rb:804 # bundle install with git sources ignores submodules if :submodule is not passed
rspec ./spec/install/gemfile/git_spec.rb:894 # bundle install with git sources prints a friendly error if a file blocks the git repo
rspec ./spec/install/gemfile/git_spec.rb:76 # bundle install with git sources when floating on master complains if pinned specs don't exist in the git repo
rspec ./spec/install/gemfile/git_spec.rb:86 # bundle install with git sources when floating on master complains with version and platform if pinned specs don't exist in the git repo
rspec ./spec/install/gemfile/git_spec.rb:102 # bundle install with git sources when floating on master complains with multiple versions and platforms if pinned specs don't exist in the git repo
rspec ./spec/install/gemfile/git_spec.rb:276 # bundle install with git sources when specifying a revision does not download random non-head refs
rspec ./spec/install/gemfile/git_spec.rb:492 # bundle install with git sources when specifying local override explodes if given path does not exist on install
rspec ./spec/install/gemfile/git_spec.rb:505 # bundle install with git sources when specifying local override explodes if branch is not given on install
rspec ./spec/install/gemfile/git_spec.rb:534 # bundle install with git sources when specifying local override explodes on different branches on install
rspec ./spec/install/gemfile/git_spec.rb:553 # bundle install with git sources when specifying local override explodes on invalid revision on install
rspec ./spec/install/gemfile/git_spec.rb:997 # bundle install with git sources bundle install after the remote has been updated gives a helpful error message when the remote ref no longer exists
rspec ./spec/install/gemfile/git_spec.rb:1072 # bundle install with git sources gem install hooks complains if the install hook fails
rspec ./spec/install/gemfile/git_spec.rb:1163 # bundle install with git sources with an extension does not prompt to gem install if extension fails
rspec ./spec/install/gemfile/git_spec.rb:1253 # bundle install with git sources without git installed prints a better error message
rspec ./spec/install/gemfile/git_spec.rb:1314 # bundle install with git sources git sources that include credentials that are username and password does not display the password
rspec ./spec/install/gemfile/git_spec.rb:1331 # bundle install with git sources git sources that include credentials that is an oauth token displays the oauth scheme but not the oauth token
rspec ./spec/install/gemfile/groups_spec.rb:207 # bundle install with groups installing --without with gems assigned to a single group errors out when passing a group to with and without
rspec ./spec/install/gemfile/groups_spec.rb:364 # bundle install with groups when locked and installed with --without does not hit the remote a second time
rspec ./spec/install/gemfile/path_spec.rb:49 # bundle install with explicit source paths expands paths raise error with not existing user's home dir
rspec ./spec/install/gemfile/path_spec.rb:144 # bundle install with explicit source paths warns on invalid specs
rspec ./spec/install/gemfile/path_spec.rb:241 # bundle install with explicit source paths raises if there are multiple gemspecs
rspec ./spec/install/gemfile/path_spec.rb:574 # bundle install with explicit source paths gem install hooks complains if the install hook fails
rspec ./spec/install/gemfile/ruby_spec.rb:99 # ruby requirement fails gracefully with malformed requirements
rspec ./spec/install/gemfile/sources_spec.rb:31 # bundle install with gems on multiple sources without source affinity with multiple toplevel sources warns about ambiguous gems, but installs anyway, prioritizing sources last to first
rspec ./spec/install/gemfile/sources_spec.rb:40 # bundle install with gems on multiple sources without source affinity with multiple toplevel sources errors when disable_multisource is set
rspec ./spec/install/gemfile/sources_spec.rb:61 # bundle install with gems on multiple sources without source affinity when different versions of the same gem are in multiple sources warns about ambiguous gems, but installs anyway
rspec ./spec/install/gemfile/sources_spec.rb:227 # bundle install with gems on multiple sources with source affinity with an indirect dependency when the indirect dependency is in a different source and in yet another source installs from the other source and warns about ambiguous gems
rspec ./spec/install/gemfile/sources_spec.rb:285 # bundle install with gems on multiple sources with source affinity with a gem that is only found in the wrong source does not install the gem
rspec ./spec/install/gemfile_spec.rb:59 # bundle install with deprecated features reports that lib is an invalid option
rspec ./spec/install/gems/compact_index_spec.rb:18 # compact index api should URI encode gem names
rspec ./spec/install/gems/compact_index_spec.rb:223 # compact index api times out when Bundler::Fetcher redirects too much
rspec ./spec/install/gems/compact_index_spec.rb:698 # compact index api fails gracefully when the source URI has an invalid scheme
rspec ./spec/install/gems/compact_index_spec.rb:245 # compact index api when --full-index is specified should use the modern index for update
rspec ./spec/install/gems/compact_index_spec.rb:518 # compact index api when using basic authentication strips http basic auth creds when warning about ambiguous sources
rspec ./spec/install/gems/compact_index_spec.rb:587 # compact index api when using basic authentication with authentication details in bundle config shows instructions if auth is not provided for the source
rspec ./spec/install/gems/compact_index_spec.rb:592 # compact index api when using basic authentication with authentication details in bundle config fails if authentication has already been provided, but failed
rspec ./spec/install/gems/compact_index_spec.rb:628 # compact index api when ruby is compiled without openssl explains what to do to get it
rspec ./spec/install/gems/compact_index_spec.rb:710 # compact index api checksum validation raises when the checksum does not match
rspec ./spec/install/gems/compact_index_spec.rb:730 # compact index api checksum validation raises when the checksum is the wrong length
rspec ./spec/install/gems/dependency_api_spec.rb:18 # gemcutter's dependency API should URI encode gem names
rspec ./spec/install/gems/dependency_api_spec.rb:213 # gemcutter's dependency API timeouts when Bundler::Fetcher redirects too much
rspec ./spec/install/gems/dependency_api_spec.rb:235 # gemcutter's dependency API when --full-index is specified should use the modern index for update
rspec ./spec/install/gems/dependency_api_spec.rb:507 # gemcutter's dependency API when using basic authentication strips http basic auth creds when warning about ambiguous sources
rspec ./spec/install/gems/dependency_api_spec.rb:576 # gemcutter's dependency API when using basic authentication with authentication details in bundle config shows instructions if auth is not provided for the source
rspec ./spec/install/gems/dependency_api_spec.rb:581 # gemcutter's dependency API when using basic authentication with authentication details in bundle config fails if authentication has already been provided, but failed
rspec ./spec/install/gems/dependency_api_spec.rb:617 # gemcutter's dependency API when ruby is compiled without openssl explains what to do to get it
rspec ./spec/install/gems/flex_spec.rb:194 # bundle flex_install when Gemfile conflicts with lockfile suggests bundle update when the Gemfile requires different versions than the lock
rspec ./spec/install/gems/flex_spec.rb:233 # bundle flex_install subtler cases does something
rspec ./spec/install/gems/flex_spec.rb:300 # bundle flex_install when a locked child dependency conflicts prints the correct error message
rspec './spec/install/gems/resolving_spec.rb[1:4:2:1:1]' # bundle install with install-time dependencies when a required ruby version allows no gems behaves like ruby version conflicts raises an error during resolution
rspec './spec/install/gems/resolving_spec.rb[1:4:2:2:1:1]' # bundle install with install-time dependencies when a required ruby version allows no gems with a < requirement behaves like ruby version conflicts raises an error during resolution
rspec './spec/install/gems/resolving_spec.rb[1:4:2:3:1:1]' # bundle install with install-time dependencies when a required ruby version allows no gems with a compound requirement behaves like ruby version conflicts raises an error during resolution
rspec ./spec/install/gems/resolving_spec.rb:178 # bundle install with install-time dependencies when a required rubygems version disallows a gem does not try to install those gems
rspec './spec/install/gems/standalone_spec.rb[1:3:1]' # bundle install --standalone with gem that has an invalid gemspec outputs a helpful error message
rspec './spec/install/gems/standalone_spec.rb[2:3:1]' # bundle install --standalone run in a subdirectory with gem that has an invalid gemspec outputs a helpful error message
rspec ./spec/install/gemspecs_spec.rb:75 # bundle install when ruby version is specified in gemspec and gemfile fails and complains about patchlevel on patchlevel mismatch
rspec ./spec/install/gemspecs_spec.rb:92 # bundle install when ruby version is specified in gemspec and gemfile fails and complains about version on version mismatch
rspec ./spec/install/git_spec.rb:17 # bundle install git sources displays the ref of the gem repository when using branch~num as a ref
rspec ./spec/install/path_spec.rb:38 # bundle install with --path disallows --path vendor/bundle --system
rspec ./spec/install/path_spec.rb:167 # bundle install to a file reports the file exists
rspec ./spec/install/post_bundle_message_spec.rb:100 # post bundle message for fresh bundle install with misspelled or non-existent gem name should report a helpful error message
rspec ./spec/install/post_bundle_message_spec.rb:109 # post bundle message for fresh bundle install with misspelled or non-existent gem name should report a helpful error message with reference to cache if available
rspec ./spec/install/post_bundle_message_spec.rb:162 # post bundle message for bundle update without any options
rspec ./spec/install/post_bundle_message_spec.rb:168 # post bundle message for bundle update with --without one group
rspec ./spec/install/post_bundle_message_spec.rb:175 # post bundle message for bundle update with --without two groups
rspec ./spec/install/post_bundle_message_spec.rb:182 # post bundle message for bundle update with --without more groups
rspec ./spec/install/security_policy_spec.rb:24 # policies with unsigned gems will fail when given invalid security policy
rspec ./spec/install/security_policy_spec.rb:29 # policies with unsigned gems will fail with High Security setting due to presence of unsigned gem
rspec ./spec/install/security_policy_spec.rb:35 # policies with unsigned gems will fail with Medium Security setting due to presence of unsigned gem
rspec ./spec/install/security_policy_spec.rb:55 # policies with signed gems and no CA will fail with High Security setting, gem is self-signed
rspec ./spec/install/security_policy_spec.rb:60 # policies with signed gems and no CA will fail with Medium Security setting, gem is self-signed
rspec ./spec/install/yanked_spec.rb:10 # when installing a bundle that includes yanked gems throws an error when the original gem version is yanked
rspec ./spec/install/yanked_spec.rb:33 # when installing a bundle that includes yanked gems throws the original error when only the Gemfile specifies a gem version that doesn't exist
rspec ./spec/install/yanked_spec.rb:45 # when using gem before installing does not suggest the author has yanked the gem
rspec ./spec/lock/lockfile_spec.rb:76 # the lockfile format does not update the lockfile's bundler version if nothing changed during bundle install
rspec ./spec/lock/lockfile_spec.rb:199 # the lockfile format errors if the current is a major version older than lockfile's bundler version
rspec ./spec/lock/lockfile_spec.rb:226 # the lockfile format shows a friendly error when running with a new bundler 2 lockfile
rspec ./spec/lock/lockfile_spec.rb:1112 # the lockfile format raises if two different versions are used
rspec ./spec/lock/lockfile_spec.rb:1123 # the lockfile format raises if two different sources are used
rspec ./spec/lock/lockfile_spec.rb:1260 # the lockfile format raises a helpful error message when the lockfile is missing deps
rspec ./spec/lock/lockfile_spec.rb:1351 # the lockfile format refuses to install if Gemfile.lock contains conflict markers
rspec ./spec/lock/lockfile_spec.rb:1304 # the lockfile format a line ending during updates preserves Gemfile.lock \n line endings
rspec ./spec/lock/lockfile_spec.rb:1312 # the lockfile format a line ending during updates preserves Gemfile.lock \n\r line endings
rspec ./spec/other/cli_dispatch_spec.rb:4 # bundle command names work when given fully
rspec ./spec/other/cli_dispatch_spec.rb:10 # bundle command names work when not ambiguous
rspec ./spec/other/cli_dispatch_spec.rb:16 # bundle command names print a friendly error when ambiguous
rspec ./spec/other/major_deprecation_spec.rb:100 # major deprecations Bundler bundle update warns when no options are given
rspec ./spec/other/platform_spec.rb:311 # bundle platform bundle install doesn't install when the ruby version doesn't match
rspec ./spec/other/platform_spec.rb:323 # bundle platform bundle install doesn't install when engine doesn't match
rspec ./spec/other/platform_spec.rb:335 # bundle platform bundle install doesn't install when engine version doesn't match
rspec ./spec/other/platform_spec.rb:349 # bundle platform bundle install doesn't install when patchlevel doesn't match
rspec ./spec/other/platform_spec.rb:401 # bundle platform bundle check fails when ruby version doesn't match
rspec ./spec/other/platform_spec.rb:418 # bundle platform bundle check fails when engine doesn't match
rspec ./spec/other/platform_spec.rb:454 # bundle platform bundle check fails when patchlevel doesn't match
rspec ./spec/other/platform_spec.rb:483 # bundle platform bundle update updates successfully when the ruby version matches
rspec ./spec/other/platform_spec.rb:499 # bundle platform bundle update updates fine with any engine
rspec ./spec/other/platform_spec.rb:517 # bundle platform bundle update fails when ruby version doesn't match
rspec ./spec/other/platform_spec.rb:533 # bundle platform bundle update fails when ruby engine doesn't match
rspec ./spec/other/platform_spec.rb:549 # bundle platform bundle update fails when ruby engine version doesn't match
rspec ./spec/other/platform_spec.rb:567 # bundle platform bundle update fails when patchlevel doesn't match
rspec ./spec/other/platform_spec.rb:617 # bundle platform bundle show fails if ruby version doesn't match
rspec ./spec/other/platform_spec.rb:629 # bundle platform bundle show fails if engine doesn't match
rspec ./spec/other/platform_spec.rb:641 # bundle platform bundle show fails if engine version doesn't match
rspec ./spec/other/platform_spec.rb:655 # bundle platform bundle show fails when patchlevel doesn't match
rspec ./spec/other/platform_spec.rb:704 # bundle platform bundle cache fails if the ruby version doesn't match
rspec ./spec/other/platform_spec.rb:715 # bundle platform bundle cache fails if the engine doesn't match
rspec ./spec/other/platform_spec.rb:726 # bundle platform bundle cache fails if the engine version doesn't match
rspec ./spec/other/platform_spec.rb:739 # bundle platform bundle cache fails when patchlevel doesn't match
rspec ./spec/other/platform_spec.rb:785 # bundle platform bundle pack fails if the ruby version doesn't match
rspec ./spec/other/platform_spec.rb:796 # bundle platform bundle pack fails if the engine doesn't match
rspec ./spec/other/platform_spec.rb:807 # bundle platform bundle pack fails if the engine version doesn't match
rspec ./spec/other/platform_spec.rb:820 # bundle platform bundle pack fails when patchlevel doesn't match
rspec ./spec/other/platform_spec.rb:957 # bundle platform bundle console fails when ruby version doesn't match
rspec ./spec/other/platform_spec.rb:971 # bundle platform bundle console fails when engine doesn't match
rspec ./spec/other/platform_spec.rb:985 # bundle platform bundle console fails when engine version doesn't match
rspec ./spec/other/platform_spec.rb:1001 # bundle platform bundle console fails when patchlevel doesn't match
rspec ./spec/other/platform_spec.rb:1195 # bundle platform bundle outdated fails when the ruby version doesn't match
rspec ./spec/other/platform_spec.rb:1213 # bundle platform bundle outdated fails when the engine doesn't match
rspec ./spec/other/platform_spec.rb:1231 # bundle platform bundle outdated fails when the engine version doesn't match
rspec ./spec/other/platform_spec.rb:1251 # bundle platform bundle outdated fails when the patchlevel doesn't match
rspec ./spec/other/platform_spec.rb:1271 # bundle platform bundle outdated fails when the patchlevel is a fixnum
rspec ./spec/plugins/command_spec.rb:56 # command plugins raises error on redeclaration of command
rspec ./spec/plugins/install_spec.rb:11 # bundler plugin install shows proper message when gem in not found in the source
rspec ./spec/plugins/install_spec.rb:71 # bundler plugin install malformatted plugin fails when plugins.rb is missing
rspec ./spec/runtime/setup_spec.rb:1017 # Bundler.setup with a gemspec that requires other files error intelligently if the gemspec has a LoadError
rspec ./spec/runtime/with_clean_env_spec.rb:49 # Bundler.with_env helpers Bundler.original_env removes variables that bundler added
rspec './spec/update/gems/post_install_spec.rb[1:1:1:1]' # bundle update when listed gem is updated behaves like a post-install message outputter should display post-install messages for updated gems
rspec './spec/update/gems/post_install_spec.rb[1:1:1:2]' # bundle update when listed gem is updated behaves like a post-install message outputter should not display the post-install message for non-updated gems
rspec './spec/update/gems/post_install_spec.rb[1:1:2:1:1]' # bundle update when listed gem is updated behaves like a config observer when ignore post-install messages for gem is set doesn't display gem's post-install message
rspec './spec/update/gems/post_install_spec.rb[1:1:2:2:1]' # bundle update when listed gem is updated behaves like a config observer when ignore post-install messages for all gems doesn't display any post-install messages
rspec './spec/update/gems/post_install_spec.rb[1:2:1:1]' # bundle update when dependency triggers update behaves like a post-install message outputter should display post-install messages for updated gems
rspec './spec/update/gems/post_install_spec.rb[1:2:1:2]' # bundle update when dependency triggers update behaves like a post-install message outputter should not display the post-install message for non-updated gems
rspec './spec/update/gems/post_install_spec.rb[1:2:2:1:1]' # bundle update when dependency triggers update behaves like a config observer when ignore post-install messages for gem is set doesn't display gem's post-install message
rspec './spec/update/gems/post_install_spec.rb[1:2:2:2:1]' # bundle update when dependency triggers update behaves like a config observer when ignore post-install messages for all gems doesn't display any post-install messages
rspec ./spec/update/git_spec.rb:5 # bundle update git sources floats on a branch when :branch is used
rspec ./spec/update/git_spec.rb:97 # bundle update git sources fetches tags from the remote
rspec ./spec/update/git_spec.rb:180 # bundle update git sources errors with a message when the .git repo is gone
rspec ./spec/update/git_spec.rb:210 # bundle update git sources shows the previous version of the gem

This is now done!


Drag and drop from File Explorer should put full path at cursor location in Windows Terminal

Summary of the new feature/enhancement
Drag and drop of file or folder from File Explorer should behave the same way that it does in conhost.  Conhost will add the text of the full path of the item dropped at the current cursor location.
Proposed technical implementation details (optional)

Ref. #331 for linking purposes.
Thanks!

I'm just wondering if there's any update on when this will be enabled.  I saw that there are issues with capturing path information under WSL, but will this be implemented for cmd.exe and/or PowerShell anytime soon?  Thanks!

@jingyu9575 Maybe opening a new issue?

@SJang1 In today's release, I cannot reproduce the first problem, but the second one is still not fixed. I've opened a new issue #4567.


--password flag in helm repo add seems broken

Hi,
I'm using Chartmuseum as a private helm repo.
But I've used the Basic auth method to secure the API.
When I want to add the repo I use the command :
helm repo add chartmuseum https://mycustom.domain.com --username <username> --password <mypassword>
But I get the following error :
Error: looks like "https://mycustom.domain.com" is not a valid chart repository or cannot be reached: failed to fetch https://mycustom.domain.com/index.yaml : 401 Unauthorized
However, when I omit the --password flag I get prompted for it.
When I then type it it proceed and add the repo correctly.
So I think the --password flag doesn't work as it is supposed to.
Output of helm version:
version.BuildInfo{Version:"v3.6.0", GitCommit:"7f2df6467771a75f5646b7f12afb408590ed1755", GitTreeState:"dirty", GoVersion:"go1.16.4"}

Can you please check again with Helm 3.7.1?

I've updated to 3.7.1 and the problem still occurs when providing --password  flag

Hmm, I just tested with chartmuseum running on localhost with basic auth and --password flag worked for me.
Output of helm version:
version.BuildInfo{Version:"v3.7+unreleased", GitCommit:"b6a04cfbd544f0bbeea449129c1497eec8d99e2b", GitTreeState:"dirty", GoVersion:"go1.16.5"}

Okay. Can you please follow up with chartmuseum? I suspect it has something to do with how you set up your server. If there's something else at play within Helm we can look into that further. Thanks!


Usage in Electron app expects gcc to be installed (macOS)

Describe the bug
On Macs without Xcode command line tools (or gcc) installed, an Electron app using systeminformation (either at main or rendered processes) causes a popup to appear (see screenshot attached)
To Reproduce
Simply use the module in an Electron app:
const si = require('systeminformation');

si.getStaticData().then(data => {
 // some code ...
}).catch(error => console.error(error));

Current Output
Module works fine, data is returned, but launching the electron app causes a popup to appear asking user to install "command line developer tools" in order to use gcc.

If user presses "Not Now" on this dialog, it will appear again (every) next time they launch the app. After removing the systeminformation module from the Electron app, the dialog popup never appears again.
Expected behavior
No confusing dialog popups should appear to the end user.
Environment (please complete the following information):

systeminformation package version: 4.12.2
OS: tested on macOS Sierra or later
Hardware: any Mac (tested on Mac Mini, iMac, Macbook Pro, VMWare VM)
Electron: 5+

@zdol : ahhh yes I see! Will try to fix this ... give me a little time to test it.

@zdol: found a solution, will provide a patch later today. Sorry for the inconvinience ...

That's great @sebhildebrandt. Happy to help!

@zdol: version 4.13.1 just released. can you test it on your side? Regards

@zdol did you had a chance to test the latest version on your side?

@sebhildebrandt I can confirm the popup no longer appears.
Tested on macOS High Sierra with latest Electron.


how to add CR and LF after the declaration node?

how to add CR and LF after the declaration node? can I add a new option to the format_option?
eg.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Types xmlns="http://schemas.openxmlformats.org/package/2006/content-types"> ...

pugixml uses LF for newlines in the output. If you want to use CRLF you can use automatic conversion that fopen/std::ofstream provide, e.g.
std::ofstream out("result.xml");
doc.save(out);

will use CRLF on Windows, since the default output mode for ofstream is text.

pugixml uses LF for newlines in the output. If you want to use CRLF you can use automatic conversion that fopen/std::ofstream provide, e.g.
std::ofstream out("result.xml");
doc.save(out);

will use CRLF on Windows, since the default output mode for ofstream is text.

In this case, I use pugixml to parse the *.xml contained in a Excel file
It turns out that the source string contains "\r\n", but after being modified by pugixml, "\r\n" disappears
Or, can make the pugi::format_raw option preserve the "original format"?
eg.
#include <pugixml.hpp>
#include <iostream>

const unsigned int parse_options = (pugi::parse_default & ~pugi::parse_eol) | pugi::parse_ws_pcdata | pugi::parse_declaration;

int main() {
	pugi::xml_document doc;
	doc.load_string("<?xml version=\"1.0\" encoding=\"UTF - 8\" standalone=\"yes\"?>\r\n<foo bar='baz'><call>hey</call></foo>", parse_options);

	// Output is "<?xml version="1.0" encoding="UTF - 8" standalone="yes"?><foo bar="baz"><call>hey</call></foo>"
	doc.save(std::cout, "", pugi::format_raw);

	// Expected output
	// "<?xml version="1.0" encoding="UTF - 8" standalone="yes"?>\r\n<foo bar="baz"><call>hey</call></foo>"

	std::cout << std::endl;
	return 0;
}

In this case, I use pugixml to parse the *.xml contained in a Excel file
It turns out that the source string contains "\r\n", but after being modified by pugixml, "\r\n" disappears
Or, can make the pugi::format_raw option preserve the "original format"?
eg.
#include <pugixml.hpp>
#include <iostream>

const unsigned int parse_options = (pugi::parse_default & ~pugi::parse_eol) | pugi::parse_ws_pcdata | pugi::parse_declaration;

int main() {
	pugi::xml_document doc;
	doc.load_string("<?xml version=\"1.0\" encoding=\"UTF - 8\" standalone=\"yes\"?>\r\n<foo bar='baz'><call>hey</call></foo>", parse_options);

	// Output is "<?xml version="1.0" encoding="UTF - 8" standalone="yes"?><foo bar="baz"><call>hey</call></foo>"
	doc.save(std::cout, "", pugi::format_raw);

	// Expected output
	// "<?xml version="1.0" encoding="UTF - 8" standalone="yes"?>\r\n<foo bar="baz"><call>hey</call></foo>"

	std::cout << std::endl;
	return 0;
}

If you want to preserve the top-level formatting you need to add parse_fragment option during parsing to store it in pcdata nodes that will be reproduced during printing.

If you want to preserve the top-level formatting you need to add parse_fragment option during parsing to store it in pcdata nodes that will be reproduced during printing.

Now it works. thanks.

Now it works. thanks.


TikaDocumentReader can't read large PDFs

When trying to load a large PDF with TikaDocumentReader, I get this exception:
org.apache.tika.exception.WriteLimitReachedException: Your document contained more than 100000 characters, and so your requested limit has been reached. To receive the full text of the document, increase your limit. (Text up to the limit is however available).

It seems that it is possible to overcome this limit by setting Tika's BodyContentHandler's write limit. Setting it to -1 means no limit. See https://tika.apache.org/1.4/api/org/apache/tika/sax/BodyContentHandler.html#BodyContentHandler(int)
Unfortunately, this setting isn't exposed through TikaDocumentReader, so it can't be set by an application developer using Spring AI. In fact, the BodyContentHandler used in TikaDocumentReader is created directly at https://github.com/spring-projects/spring-ai/blob/main/document-readers/tika-reader/src/main/java/org/springframework/ai/reader/tika/TikaDocumentReader.java#L119 and can't be changed.
Exposing configuration on TikaDocumentReader to set the write limit would address this problem. (And there may be other settings that could/should be exposed for developers to fine-tune how TikaDocumentReader works.)

Okay, I see now that I can construct a TikaDocumentReader with a ContentHandler, for which BodyContentHandler could be given. I'm gonna try that and (assuming it works) will close this issue.

Followup: It does work in that if I give it a BodyContentHandler with a write limit of -1, it succeeds in loading the entire large PDF without failing. But then it fails because it loads the entire PDF into a single Document object (without splitting it up into multiple document nodes) which is too large for sending to the embedding API. It seems that the 100000 character limit was helping avoid an oversized Document problem, while limiting the size of the PDFs that TikaDocumentReader can load.
In light of this new understanding, I'm going to close this issue and think over how to overcome the new problem I've encountered.
(Bear in mind that TikaDocumentReader is much more flexible with regard to PDF formatting than the other PDF document readers and it is also able to read multiple types of documents...not just PDF. So it would be nice if it could handle larger PDF documents better, by splitting them into several document nodes small enough to be sent to the embedding API.)


(add): Adding README.md as my profile name

Description

[X] I have added a folder(Named it as my GitHub user id)
[X] I have added a Readme.md file inside the folder
[X] I understand the GitHub Forking Concept fully

"README.md file is added"


Missing key(s) in state_dict: "text_model.embeddings.position_ids".

Trying to extract a Lycoris with the lycoris_locon_extract script and I get the following error:
Traceback (most recent call last):
  File "C:\AI\kohya_ss\tools\lycoris_locon_extract.py", line 129, in <module>
    main()
  File "C:\AI\kohya_ss\tools\lycoris_locon_extract.py", line 98, in main
    db = load_models_from_stable_diffusion_checkpoint(args.is_v2, args.db_model)
  File "C:\AI\kohya_ss\venv\lib\site-packages\lycoris\kohya\model_utils.py", line 1060, in load_models_from_stable_diffusion_checkpoint
    info = text_model.load_state_dict(converted_text_encoder_checkpoint)
  File "C:\AI\kohya_ss\venv\lib\site-packages\torch\nn\modules\module.py", line 2041, in load_state_dict
    raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for CLIPTextModel:
        Missing key(s) in state_dict: "text_model.embeddings.position_ids".

Was run with: ./venv/Scripts/python.exe "tools\lycoris_locon_extract.py" --device cuda --mode fixed --safetensors
--linear_dim 128 --conv_dim 64 --sparsity 0.98 "C:/AI/models/Stable-diffusion/cyberrealistic_v33
fp32.safetensors" "C:/AI/Training/Lora/Models/FT/Model.safetensors"
"C:/AI/Training/Lora/Models/Lyco/Lycoris Model.safetensors"
(Run via the Kohya GUI by bmaltais).
The finetune has been trained via a different tool (OneTrainer).

its not as simple as that key is also dependent on ancient transformers being used - it doesn't exist in newer transformers and eventually even this repo will need to upgrade.
see https://github.com/kohya-ss/sd-scripts/pull/687#issuecomment-1742139009


Add pg_statistic catalog

This creates a new catalog, pg_statistic, which contains some of the same basic information as stored in the Postgres catalog of the same name: https://www.postgresql.org/docs/9.5/catalog-pg-statistic.html.
The catalog contains a tuple for every column in a table. For now, only columns in actual tables (as opposed to indexes) are tracked. Whenever a table is created or dropped, a corresponding tuple in the pg_statistic catalog is added or removed accordingly.
A new method GetTableStats is added to the DatabaseCatalog class, which pulls statistics from the pg_statistic table. This method returns a TableStats object, so it is somewhat compatible with the existing StatsStorage interface.
However, the new API is not actually used in the codebase anywhere — the users of the StatsStorage API have not yet been updated at this time.
Questions for reviewers:

Is database_catalog.cpp the right location to add functions inserting into, deleting from, and updating the pg_statistic catalog?
Is optimizer/stats_catalog_test.cpp the right place to add a test for this? Maybe it should go under catalog/?
Does an API returning a TableStats object make sense? (Is the TableStats object used immutably, or is it expected that updates to the object will be reflected in the actual storage?)
The code for "find all TupleSlots in pg_statistics matching a table OID" is verbose, and is sort of duplicated in multiple places. How can this be resolved? I've written a helper function in stats_catalog_test for ease of use inside that file, but what about inside database_catalog.cpp? Adding private helper functions to that class for this purpose doesn't seem to fit the type of code in that file.

Closed to reduce Jenkins contention


Add apache-rat-plugin to release profile

Description:
Need to add apache-rat-plugin to release profile to check copyright notices.

Issue is outdated now. Hence, closing the issue.

Issue is outdated now. Hence, closing the issue.


[Network] Add SetBroadcastsEnabled() to Sockets

In Berkeley sockets, the SO_BROADCAST flag is required to perform multicast send operations. Set this flag on or off in a member method SetBroadcastsEnabled().

Added SetBroadcastsEnabled()


Update active-directory-functional-levels.md

make it better understandable

@robinharwood, @Xelu86
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Block requests if page not visible

Is your feature request related to a problem? Please describe.

Cosmos Wallet is requesting a lot in the background. This is consuming data and power. Users would probably prefer to not have this.
Describe the solution you'd like

We can use https://davidwalsh.name/page-visibility in api.js.
This would not submit any request if the page is not active.
Describe alternatives you've considered

Additional context

this is a great idea. additionally, there may be a few places where we are making requests that are not necessary or are redundant.


Replace Express with Koa 2

<EMAIL_ADDRESS>https://github.com/koajs/koa/issues/533

+1

+1

+1

I would wait until v2 is stable (async/await supported by node). It's too complicated now (transformation of old middle-wares...). Also, server transpilation is questionable.

https://github.com/koajs/koa/issues/533

Closing because it will not probably happen in foreseeable future. Express is good enough.


Improve regex test cases by including negative tests for unsupported escape characters in them

There is need to add some test cases that check the validation/acceptance of non ECMAScript regular expressions. In the particular case (see the issue here: https://github.com/JamesNK/Newtonsoft.Json.Schema/issues/34) the software accepts escape characters that are not part of the ECMAScript regular expression definitions.

Adding an additional module to the optional test cases would certainly sound fine to me, any chance you'd mind submitting a PR?
Putting it alongside the existing tests wouldn't work, the spec doesn't require ECMAScript compatibility it just recommends it, and many languages would have difficulty with the requirement and these tests.

I've missed the "recommendation" part. My apologies.
I'll try to put some PR about this. Is this file a good place for this?

A file in /optional/ecmascript-regex.json would be good
On Jul 6, 2016 9:59 AM, "Radoslav Petrov"<EMAIL_ADDRESS>wrote:

I've missed the "recommendation" part. My apologies.
I'll try to put some PR about this. Is this file
https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/develop/tests/draft3/optional/jsregex.json
a good place for this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/json-schema-org/JSON-Schema-Test-Suite/issues/119#issuecomment-230779736,
or mute the thread
https://github.com/notifications/unsubscribe/AAUIXs0eUBYmnOCX55yuA_jMRAakj4dPks5qS7TdgaJpZM4JF3gX
.


[QUERY] How to get barcodes with prebuit-invoice model

Library name and version
Azure.AI.FormRecognizer 4.1.0-beta.1
Query/Question
I'm following the javascript example to get invoice data using the prebuilt-invoice model.
When I tried on Form Recognizer Studio there is an option to enable the detection of barcodes.
With the given example I could not find a way to enable this. My code:
const client = new DocumentAnalysisClient(endpoint, new AzureKeyCredential(key));
const poller = await client.beginAnalyzeDocumentFromUrl("prebuilt-invoice", document);
const {
        documents: [result]
    } = await poller.pollUntilDone();

//poller.getResult().pages[0].barcodes = undefined

I believe I need to pass a parameter to enable the barcode read, any thoughts?
Environment
.NET SDK:
Version:   7.0.202
Commit:    6c74320bc3
OS Name:     Windows
OS Version:  10.0.22621
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\7.0.202\
Host:
Version:      7.0.4
Architecture: x64
Commit:       0a396acafe
.NET SDKs installed:
6.0.401 [C:\Program Files\dotnet\sdk]
7.0.202 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.28 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hello @rvilvert,
The option to enable barcode detection you saw in Form Recognizer Studio is only available in service version 2023-07-31. The SDK version you're using (4.1.0-beta.1) targets service version 2023-02-28-preview, which only supports barcode detection in models prebuilt-read and prebuilt-layout.
SDK version 4.1.0 targeting the latest service version will be released this week. Once it's released, you'll be able to enable barcode detection by doing the following (in the .NET SDK):
var options = new AnalyzeDocumentOptions()
{
    Features = { DocumentAnalysisFeature.Barcodes }
};
var operation = await client.AnalyzeDocumentAsync(WaitUntil.Completed, "prebuilt-invoice", document, options);

Please note that this repository focuses on the .NET SDK. If you have questions about the JavaScript SDK, feel free to open an issue at https://github.com/Azure/azure-sdk-for-js.

Thank you @kinelski


Added additional nonstandard units + tests.

We're working on a recipe parser for a project and we continue to find additional non-standard units. This should be all of them for now, though.

https://github.com/iancanderson/ingreedy/pull/13 added support for cans as a unit


Add enable option to xdebug plugin

This adds an option to selectively enable debug features.
This is an incompatible change. Please do not back port to old versions.

Closing because this is incompatible change and it should be landed on 10-Dev.


SEO - URL issue

Can we have a more SEO friendly URL like:
https://en.wikipedia.org/wiki/Albert_Einstein
instead of:
https://matterwiki.herokuapp.com/#/article/9?_k=myv8vt

UI looks great! I had the same question. The # symbol is kind of odd. I'd love a SEO friendly URL too.

agree

On Sep 8, 2018, at 10:17 AM, sunk818<EMAIL_ADDRESS>wrote:
UI looks great! I had the same question. The # symbol is kind of odd. I'd love a SEO friendly URL too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I found something that could help:
https://stackoverflow.com/questions/16358715/node-js-and-mongoose-seo-friendly-urls

https://cdn0.tnwcdn.com/wp-content/blogs.dir/1/files/2018/09/image1-1.png


Security headers missing

Previously I had to remove the security headers from next.s as it doesn't know how to export those to static files - but perhaps there's a way to enable them on github pages or in the root layout.tsx
https://securityheaders.com/?q=https%3A%2F%2Fclimatetriage.com%2F&followRedirects=on
The past headers can be found in next.config.js still.
CC: @andrew (this is the one I mentioned)

I don't believe you can change the headers in github pages, you'd need to proxy the site through another webserver like cloudflare or nginx.

Moved this to https://github.com/protontypes/climate-triage/issues/20


Compilation quickly slows down with increasing codebase size

This is a followup issue to #4282.
As our Angular2 codebase grows we noticed that the compilation time seems to be increasing non-linearly/exponentially with the code size growth.
In Angular repo we have several modules that we are compiling together and I noticed that simply removing some modules can significantly improve the performance. What's interesting is that it doesn't matter which modules I drop. Any of them can result in improvements more significant the size the removed modules contribute to the overall compilation unit.
To repro with tsc on the angular code base:

check out: https://github.com/IgorMinar/angular/tree/tsc-perf-repro
cd angular
npm install
switch to ES6 target following instructions in #4282 which is even more severely impacted than ES5
time ./node_modules/.bin/tsc -p modules
rm -rf modules/<some_module>
time ./node_modules/.bin/tsc -p modules

You might delete any modules except for the main angular2 module which other modules depend on. All these modules are leaves except for angular2_material which is being depended on by examples module.
Example numbers in ES6 mode (patched tsc v1.5.3 - see #4282 for more info about the patches) :

baseline (all modules) : ~21s (total LoC*=71308)
previous - benchpress:  ~19s (total LoC=66902)
previous - examples:~16s (total LoC=63989)
previous - rtts_assert:  ~16s (total LoC=63251)
previous - benchmarks: ~14s (total LoC=60294)
previous - benchmarks_external: ~14s (total LoC=59675)
previous - angular2_material: ~11s (total LoC=58221)
previous - angular2/test: ~5s (total LoC=31942)

Now interestingly if I remove angular2/test first, slimming the code base significantly I get different numbers:

baseline (all modules) : ~21s (total LoC=71308)
previous - angular2/test: ~7s (total LoC=45029)
previous - benchpress:  ~6.5s (total LoC=40623)
previous - examples:~6s (total LoC=37710)
previous - rtts_assert:  ~6s (total LoC=36972)
previous - benchmarks: ~5.8s (total LoC=34015)
previous - benchmarks_external: ~5.5s (total LoC=33396)
previous - angular2_material: ~5s (total LoC=31942)

This shows that removing the angular2/test folder which contributes significantly to the overall codebase size can speed up the compilation by either 14s or 6s depending on what other modules are we compiling (even though the angular2/test has no dependencies on these other modules (with the exception of the core angular2 module that all of the modules depend on.
My assumption is that since the angular2/test is a leaf, removing it first or last should yield in the same absolute perf improvement, but that's not the case. I'm using this to simulate code-base growth since what we see is that the compilation time is increasing faster than our code base.

I'm using LoC to as a lame approximation of the compilation unit size - if you have a better way to measure this please advise :).

Almost all the extra time is spent in the checker:
With angular2/tests:
Files:             573
Lines:          100440
Nodes:          455418
Identifiers:    147979
Symbols:         72168
Types:           66300
Memory used:   149830K
I/O read:        0.35s
I/O write:       2.83s
Parse time:      1.15s
Bind time:       0.57s
Check time:     17.87s
Emit time:       5.09s
Total time:     24.69s

When you remove tests:
Files:             447
Lines:           74035
Nodes:          311600
Identifiers:    103304
Symbols:         57243
Types:           37664
Memory used:   127146K
I/O read:        0.24s
I/O write:       1.92s
Parse time:      0.86s
Bind time:       0.53s
Check time:      6.29s
Emit time:       2.94s
Total time:     10.61s

Perhaps tellingly there are almost half as many types when compiling without tests. Despite only cutting ~25% LOC, you cut ~50% of the types!

@sheetalkamat can you take a look..

@IgorMinar : I ran this with node and the result was this:
Files:             573
Lines:          100438
Nodes:          455129
Identifiers:    147854
Symbols:         72082
Types:           67959
Memory used:   237189K
I/O read:        0.41s
I/O write:       0.00s
Parse time:      1.14s
Bind time:       0.66s
Check time:     23.41s
Emit time:       0.00s
Total time:     25.20s
Vs without test folder
Files:             447
Lines:           74033
Nodes:          311321
Identifiers:    103181
Symbols:         57157
Types:           36995
Memory used:   171307K
I/O read:        0.38s
I/O write:       0.00s
Parse time:      0.91s
Bind time:       0.53s
Check time:      5.61s
Emit time:       0.00s
Total time:      7.05s
But as @mhegazy suggested me, I ran this with iojs and the result was this indicating this to be node issue.
Files:             573
Lines:          100438
Nodes:          455129
Identifiers:    147854
Symbols:         72082
Types:           67959
Memory used:   280986K
I/O read:        0.36s
I/O write:       0.00s
Parse time:      1.09s
Bind time:       0.58s
Check time:      3.34s
Emit time:       0.00s
Total time:      5.01s
Vs
Files:             447
Lines:           74033
Nodes:          311321
Identifiers:    103181
Symbols:         57157
Types:           36995
Memory used:   173990K
I/O read:        0.25s
I/O write:       0.00s
Parse time:      0.88s
Bind time:       0.44s
Check time:      2.42s
Emit time:       0.00s
Total time:      3.73s

Thanks! I'll try to play with different node versions


Documentation or Sample code for disabled transaction

Issue #655 introduced disabling transaction support.
But there is no sample, no documentation and only a unit test to demonstrate this.
Todo :

add sample in flyway-sample module
add relevant documentation

Hi, is there some small example, anywhere?
Thanks.

Example would be great...

I came across this issue while looking into CREATE INDEX CONCURRENTLY support in Flyway. Can this issue be closed now that Flyway >= 4.1.0 supports autodetection of non-transactional statements?

I've updated the documentation site regarding this. We aim to release it with v6.


Add ability to use nested field as PK for RedisCache

Previously, if you were trying to use nested fields in ksql like that:
connect.redis.kcql=INSERT INTO user.state. SELECT * FROM user.state PK auth.userId, connectionId

You would have met following error:
[2018-07-24 14:25:05,696] ERROR WorkerSinkTask{id=RedisSinkConnector-0} Task threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask)
org.apache.kafka.connect.errors.ConnectException: Exiting WorkerSinkTask due to unrecoverable exception.
        at org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:517)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:288)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:198)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:166)
        at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:170)
        at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:214)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: java.lang.IllegalArgumentException: requirement failed: userId keys are not present in the SinkRecord payload:connected,connectionId,auth

This PR is aimed to add support for using nested fields as primary keys

This change is

@Kanris826 Thanks for the PR, we review it shortly!


indexer: consistent checkpoint age metrics

Description
prev. indexer checkpoint age metrics were IntGauge and validator and FN use mysten_metrics::histogram::Histogram, which is better as it automatically calculate p50, p95 and p99 accurately, instead of in the past for indexer checkpoint age, I had to do quantile_over_time
Test plan
local run and make sure the metrics can pop as expected

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:

Iirc we want to migrate all histograms to be Prometheus ones and avoid using the ones defined in Mysten metrics

@bmwill yes, I did not know that and just replaced the mysten ones with prom ones. will open a separate pr to replace the checkpoint_age on validator and checkpoint to be consistent.


Enhance Error Handling

[x] Add more assertion checks on python end
[x] Error messages on Dart end should be made more concise and clear
[ ] ...

I faced this weird bug, in a DataTable if the number of columns is less than the number of datacells in any row it will grey out whole table without throwing error ( refer to the image attacted )
while if the number of columns is less than number of datacell in rows, it will just not display that cell and display rest of the table, I think this case can be also improved by throwing a warning at terminal about number of datacells being more than columns, or it should just render those cells without a column name.

I found another thing about DataTable, if you accidentally use any other control than DataCell inside of cells list in DataRow, it will grey out everything same as mentioned above.

if you accidentally use any other control than DataCell inside of cells list in DataRow, it will grey out everything same as mentioned above.

What's the behavior you expected?

if you accidentally use any other control than DataCell inside of cells list in DataRow, it will grey out everything same as mentioned above.

What's the behavior you expected?

to throw a error stating that it was supposed to be a DataCell, not just greying out the whole table without any clue


Lambda broken due to: [ERROR] Runtime.ImportModuleError: Unable to import module 'index': urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with OpenSSL 1.0.2k-fips  26 Jan 2017.

Currently getting this error in Cloudwatch Logs with a GET to /serverless_lambda_stage.

[ERROR] Runtime.ImportModuleError: Unable to import module 'index': urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with OpenSSL 1.0.2k-fips  26 Jan 2017. See: https://github.com/urllib3/urllib3/issues/2168

The fix to lock the dependency in https://github.com/lithops-cloud/lithops/issues/1104 works. Need to apply my PR in #9 then do a terraform destroy if already deployed and then another terraform apply and it will accept a POST with the demo JSON body here: https://github.com/aws-samples/aws-sam-terraform-examples/blob/main/serverless_tf_sample/api-lambda-dynamodb-example/events/lambda-input.json
{
    "BookTitle": "My fave book",
    "ReviewScore": "8",
    "ReviewText": "Epic read! Definitely recommended!"
}


Add OLM Bundle Generation Scripts

Fixes #705
Description
This commit adds most of the necessary plumbing for generating OLM artifacts, as well as publishing those artifacts to a container registry.
This takes advantage of theack-generate olm command and operator-sdk generate bundle in order to generate artifacts that should be ready to go into an operator collection like https://github.com/operator-framework/community-operators.
Change Synopsis

install-operator-sdk.sh - This will install install the Operator SDK binary at the current release version (1.6.1) and is modeled after other similar dependency installation scripts.
build-controller-release.sh - This has been updated to include optional logic to both install operator-sdk and use the ack-generate olm command to generate necessary manifest bases to feed a downstream bundle generation. As these are optional, their defaults are set to false.
olm-create-bundle.sh - This will  create an OLM bundle using operator-sdk generate bundle  on disk by leveraging the manifest bases that are created in the previous step.
olm-build-bundle-image.sh - This will create the corresponding container image from the assets on disk (generated in the previous step). This also has optional variables that will add additional labels necessary for Red Hat operator certification.
olm-publish-bundle-image.sh - This will publish the bundle to a configurable container registry.

Sample Execution
I did my testing using the s3-controller as I already had the necessary OLM config handy. I believe I pulled the main branch.
# s3-controller directory/repository
$ git rev-parse HEAD
6980337a5e9b2234d4b7355377ead6ab589d0d5b

I then added my sample s3 OLM configuration file. I will go through and commit these files to their respective repos (assuming that the source repositories are where these need to go).
# s3-controller directory/repository
$ cat s3-olmconfig.yaml
---
annotations:
  capabilityLevel: basic install
  shortDescription: AWS S3 Controller is a Service Controller for Managing AWS S3 Buckets
    in Kubernetes
displayName: AWS Simple Storage Service (S3) for Kubernetes
description: Manage AWS S3 Buckets from within your OpenShift cluster.
  This controller is a component of the [AWS Controller for Kubernetes](https://github.com/aws/aws-controllers-k8s)
  project. This project is currently in **developer preview**.
samples:
- kind: Bucket
  spec: |
    name: "example-bucket-created-by-ack"
- kind: MultipartUpload
  spec: |
    bucket: "example-bucket-created-by-ack"
      key: "some-key"
maintainers:
- name: "The ACK Team"
  email<EMAIL_ADDRESS>
I enable OLM artifact generation using an environment variable and build a controller release (10.0.0 for this test, as I might be a time traveler from the future =D ). The location of the *-olmconfig.yaml is configurable, but I don't need to change it because of where I've placed the file:
# community directory/repository
$ export ACK_GENERATE_OLM=true
$ ./scripts/build-controller-release.sh s3 10.0.0
Building release artifacts for s3-10.0.0
Generating custom resource definitions for s3
Generating RBAC manifests for s3
Generating operator lifecycle manager bundle assets for s3

Double check that our CSV bases have been generated.
# community directory/repository
$ tree ../s3-controller/config/manifests/
../s3-controller/config/manifests/
├── bases
│   └── ack-s3-controller.clusterserviceversion.yaml
└── kustomization.yaml

1 directory, 2 files

From there, I'll need to create the bundle on disk. Note that this section relies on the controller image being set in the deployment manifest, so the script handles updating that based on defaults/environment. It's also possible to customize the bundle version via environment in case it differs from the controller release, but I don't need it here.
# community directory/repository
$ ./scripts/olm-create-bundle.sh s3 10.0.0
Generating bundle version 10.0.0
Generating bundle manifests
Bundle manifests generated successfully in bundle
Generating bundle metadata
Creating bundle.Dockerfile
Creating bundle/metadata/annotations.yaml
Bundle metadata generated successfully
INFO[0000] Found annotations file                        bundle-dir=build/release/s3/olm/bundle container-tool=docker
INFO[0000] Could not find optional dependencies file     bundle-dir=build/release/s3/olm/bundle container-tool=docker
INFO[0000] All validation tests have completed successfully

Assets are generated in the controller source repo in a directory called olm
$ tree ../s3-controller/olm
../s3-controller/olm
├── bundle
│   ├── manifests
│   │   ├── ack-s3-controller.clusterserviceversion.yaml
│   │   ├── ack-s3-metrics-service_v1_service.yaml
│   │   ├── ack-s3-reader_rbac.authorization.k8s.io_v1_role.yaml
│   │   ├── ack-s3-writer_rbac.authorization.k8s.io_v1_role.yaml
│   │   └── s3.services.k8s.aws_buckets.yaml
│   ├── metadata
│   │   └── annotations.yaml
│   └── tests
│       └── scorecard
│           └── config.yaml
└── bundle.Dockerfile

At this point we need to build the bundle image and publish, but the publish script will build it so we'll just use that. The build script allows you to also specify if the RH certification labels should be added to the image. I'm turning it on here, but the default value is false (i.e. don't build the image with the extra labels) I set the docker repository to my own namespace for testing and publish:
export DOCKER_REPOSITORY=quay.io/komish/aws-controllers-k8s
export ADD_RH_CERTIFICATION_LABELS="true"
$ ./scripts/olm-publish-bundle-image.sh s3 10.0.0
building 's3' OLM bundle container image with tag: quay.io/komish/aws-controllers-k8s:s3-bundle-10.0.0

... build output truncated for brevity ...

Pushing 's3' operator lifecycle manager bundle image with tag: s3-bundle-10.0.0
The push refers to repository [quay.io/komish/aws-controllers-k8s]
4319a9b9bb3d: Pushed
1c3775fb3ec9: Pushed
993f51922e08: Pushed
s3-bundle-10.0.0: digest: sha256:d41682d98e2047784d7a24e06983706f658c41950b433853b10222985f5579aa size: 939

Checking the bundle in this case to make sure that it has the necessary labels for certification (here, I'm referring to the top three labels. The rest of the labels are coming from operator-sdk):
$ docker inspect quay.io/komish/aws-controllers-k8s:s3-bundle-10.0.0 | jq .[].Config.Labels
{
  "com.redhat.deliver.backport": "false",
  "com.redhat.delivery.operator.bundle": "true",
  "com.redhat.openshift.versions": "v4.6",
  "operators.operatorframework.io.bundle.channel.default.v1": "alpha",
  "operators.operatorframework.io.bundle.channels.v1": "alpha",
  "operators.operatorframework.io.bundle.manifests.v1": "manifests/",
  "operators.operatorframework.io.bundle.mediatype.v1": "registry+v1",
  "operators.operatorframework.io.bundle.metadata.v1": "metadata/",
  "operators.operatorframework.io.bundle.package.v1": "ack-s3-controller",
  "operators.operatorframework.io.metrics.builder": "operator-sdk-v1.4.0+git",
  "operators.operatorframework.io.metrics.mediatype.v1": "metrics+v1",
  "operators.operatorframework.io.metrics.project_layout": "unknown",
  "operators.operatorframework.io.test.config.v1": "tests/scorecard/",
  "operators.operatorframework.io.test.mediatype.v1": "scorecard+v1"
}

I also pulled the image locally to make sure it has the right assets (i.e. the ones I pushed)
$ docker image save  quay.io/komish/aws-controllers-k8s:s3-bundle-10.0.0 > my-image.tar

$ tar xvf my-image.tar
9ffd953efb5ed2e9c3b63cbe235ea383389b2e480c822cf59b8ec9a459806dc9/
9ffd953efb5ed2e9c3b63cbe235ea383389b2e480c822cf59b8ec9a459806dc9/VERSION
9ffd953efb5ed2e9c3b63cbe235ea383389b2e480c822cf59b8ec9a459806dc9/json
9ffd953efb5ed2e9c3b63cbe235ea383389b2e480c822cf59b8ec9a459806dc9/layer.tar
a2db863c6a4ca59e0c6fb4862e807df698165e86a451e6e6cdbe1520302f16ef/
a2db863c6a4ca59e0c6fb4862e807df698165e86a451e6e6cdbe1520302f16ef/VERSION
a2db863c6a4ca59e0c6fb4862e807df698165e86a451e6e6cdbe1520302f16ef/json
a2db863c6a4ca59e0c6fb4862e807df698165e86a451e6e6cdbe1520302f16ef/layer.tar
f92c158cd01e5c5728b5d9c392749806d44ba4ca7f9d99eabf76d91e1affd14d/
f92c158cd01e5c5728b5d9c392749806d44ba4ca7f9d99eabf76d91e1affd14d/VERSION
f92c158cd01e5c5728b5d9c392749806d44ba4ca7f9d99eabf76d91e1affd14d/json
f92c158cd01e5c5728b5d9c392749806d44ba4ca7f9d99eabf76d91e1affd14d/layer.tar
f9bc836c26f34f90702b1696d9ff1065005e5be259553e641ee22a69b0c8cc3e.json
manifest.json
repositories

$ find . -name layer.tar -exec tar xvf {} \;
tests/
tests/.wh..wh..opq
tests/scorecard/
tests/scorecard/config.yaml
manifests/
manifests/ack-s3-controller.clusterserviceversion.yaml
manifests/ack-s3-metrics-service_v1_service.yaml
manifests/ack-s3-reader_rbac.authorization.k8s.io_v1_role.yaml
manifests/ack-s3-writer_rbac.authorization.k8s.io_v1_role.yaml
manifests/s3.services.k8s.aws_buckets.yaml
metadata/
metadata/.wh..wh..opq
metadata/annotations.yaml

$ tree tests manifests metadata
tests
└── scorecard
    └── config.yaml
manifests
├── ack-s3-controller.clusterserviceversion.yaml
├── ack-s3-metrics-service_v1_service.yaml
├── ack-s3-reader_rbac.authorization.k8s.io_v1_role.yaml
├── ack-s3-writer_rbac.authorization.k8s.io_v1_role.yaml
└── s3.services.k8s.aws_buckets.yaml
metadata
└── annotations.yaml

1 directory, 7 files

Notes

Originally, I had this outputting to the community directory in a build/ folder. I thought I had seen that output location in some existing scripts. That said, I noticed that the helm assets are stored in-repo with the controller source, so I've moved the output to the $SERVICE_CONTROLLER_SOURCE_PATH/olm. Let me know if that needs to change.
I tested against ack-generate built from code-generator v0.0.7 as I see the --template-dirs flag has changed to --templates-dir on main and I didn't want to make changes in other places calling this flag until you were ready to do so.
There are additional labels and configurations that will need to go  into the controller image build scripts that are not included as a part of this PR. I will do further testing and submit a future issue+PR that will optionally add those labels to the controller container image in order to enable Red Hat certification.
I also need to go through and commit OLM configs for each controller to get us started.

[EDIT] Force pushed to squash a commit that just changed permissions on a script to make it executable.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jaypipes Happy to help! Changes have been submitted and responses are also in-line. Let me know if any further changes are required.


Pow 1472

What does this PR do?

Please open a new PR with a description once the feature you're adding is complete.

Sorry this was meant for our forked version


SOAPEngine licence key

how a i can get SOAPEngine licence key.

You can get one here: https://www.prioregroup.com/iphone/soapengine.aspx
I'm not affiliate by any with Priore group. If you prefer to develop the XML parsing yourself you can look at this repo