Add blood, coffee, and weather tables

Some of these might be wrong, I tested it with a couple dozen players. I'm also not a fan of the big if/else chain for converting to strings, but I'm not sure of a better way to do it.


Update host.docker.internal and related after network change

Forgive if this has been reported / discussed / documented somewhere, but I couldn't find it.
Is your feature request related to a problem? Please describe.
When changing networks, for example disconnecting my laptop from the docking, should update the host.docker.internal ip mapping and possibly other entries like those in /etc/resolv.conf
Currently when undocking, my laptop switches to WiFi, which is to be expected. But WSL2 (or docker for win) isn't aware of this or reacting to it. So everything relying on host.docker.internal for connectivity to the windows host will fail.
(i.e. an MSSQL database server).
Describe the solution you'd like
Ideally the network change gets picked up so the DNS / host entry for host.docker.internal gets updated.
Describe alternatives you've considered
Document this usecase by explaining the steps needed to get host.docker.internal working again.
What worked for me today is wsl --shutdown. Sounds easy afterwards, but if you don't know how this works under the hood it can take you a lot of time to find out.
At first I tried:

closing/opening Ubuntu WSL2
restarting docker for desktop

Those are not working, it seems you really need to shutdown wsl to get it to regenerate the correct ip mapping.
Additional context
I am observing that the ip in /etc/resolv.conf is always different from what host.docker.internal is resolving to. Connecting to host.docker.internal from WSL2 works. The ip from /etc/resolv.conf can be pinged, but windows programs/services are not listening to it it seems, even though they're bound to <IP_ADDRESS>.
valentijn@LAP0125:~$ cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver <IP_ADDRESS>

valentijn@LAP0125:~$ telnet <IP_ADDRESS> 3306
Trying <IP_ADDRESS>...

valentijn@LAP0125:~$ telnet host.docker.internal 3306
Trying <IP_ADDRESS>...
Connected to host.docker.internal.
Escape character is '^]'.

/dupe #4285

@therealkenc not sure if it is a duplicate. Might be the same root cause, but for me DNS works fine. foreverything It's just the host entry for host.docker.internal is not updated, not even after restart of docker or ubuntu.

@valentijnscholten , you seem to be getting host.docker.internal from either a static hosts entry or from the DNS.  This host name appears an artificial entry configured by a docker host for its guest containers,
https://docs.docker.com/desktop/networking/
WSL2 is not a Docker container but a Linux co-guest to a hypervisor (small super-kernel) that started both the Windows and the Linux kernel at the system startup.
Perhaps you want to have the laptop's Windows guest "currently live" ethernet address available in your WSL2 Linux guest (and I understand some of the Windows's ethernet addresses are the ones linked to the physical network interfaces just because Microsoft sets up the hypervisor and the Windows kernel this way).  I can see that a virtual WSL2 ethernet address is exposed as a DNS server address in /etc/resolv.conf (but this may miss changes in your physical configurations).  If that is not good enough, then, perhaps, using the WSL2 mount of /mnt/c/Windows/System32/ipconfig.exe and its stdin/stdout/stderr "interop" could help automate polling for the current address.  Pushing the current address could also be made possible with a manual Windows Task Scheduler task that listens for a particular network change eventID and launches a script.


Docker Compose Project isolation within a single buildkite job ID

Hello!
We're running a Docker Compose Plugin powered build for a large rails app. The build is split up via knapsack across dozens of machines.
Everything works great when there is one buildkite agent running on each machine. However each machine has multiple CPUs so we would like to get more parallelism by running multiple buildkite agents. When there is more than one agent on each machine the knapsack build steps fail, while other build steps that are unique per job ID succeed.
Looking at the code it looks like docker_compose_project_name is based on the buildkite job ID which seems right.
https://github.com/buildkite-plugins/docker-compose-buildkite-plugin/blob/07607ad023752fc409b0a2dd5af7feafb265271a/lib/shared.bash#L83
I see that is assigned to the container name, but do not see anything that sets the --project flag. Not sure if that is a problem or not.
We're continuing along with one agent per machine for now, but eager to ramp paralellism up to save costs if there are any tips I'm missing.

Hi @woodhull! sorry for the long delay in responding.
I reviewed and even back when you reported the issue the run_docker_compose function that was used everywhere to run stuff added the -p option:
https://github.com/buildkite-plugins/docker-compose-buildkite-plugin/blob/07607ad023752fc409b0a2dd5af7feafb265271a/lib/shared.bash#L186
If your builds were failing there was obviously something else going on, but we would need more information to further troubleshoot it. Is this still a concern of yours?


Breaking change in ASA 2.12.0

The new release of ASA v2.12.0 fixes a significant bug related to a non-identity transform for the AR Session Origin.
The WLT-ASA shim contains workarounds for the bug. Those workarounds will need to be disabled for version >= v2.12.0.
(The fix needs to be verified again, but has been previously verified with a preview ASA build. Many thanks to the ASA team!!!)
If I remember correctly, the bug only affects HoloLens.

Having gotten advance notice from the ASA team about this fix coming out (Yay ASA team!), I had put some defines in around version 2.12.0.
I've tested them out, and both the ASA bug fix and the WLT conditional compilation for the workarounds seem to be good.
Please let me know if you run into issues moving to latest ASA version!


Specify file encoding

If not specified, Python uses system default, which for Windows is not "utf-8".

Thanks!


[FEAT] Make boto3 dependency optional

What is the problem? Please describe.
boto3 (and botocore) are only used in sentinelhub/download/aws_client.py. This is not a feature many people need. boto3 and all its dependencies are relatively large (~50MB) and annoying to manage as dependencies, since they update so frequently. It would be great if they were made into optinoal dependencies.
Here's the solution
Use setuptools extra_requires to make them an extra, so one can install sentinelhub[aws] if one needs them.
Alternatives
Just remove the dependency and tell users to install boto3 if they want that module to work.
Additional context
n/a

Thanks for raising this, it is actually something we plan to do in the near future. The idea is to reorganize the content of the package and management of its dependencies. The AWS functionalities of the package will probably become available under the sentinelhub[aws] extension, as you suggested.
Furthermore, we are thinking about having an even more lightweight version of the package so that it could be used as a dependency of SentinelHub QGIS plugin. It is not yet completely clear what would be the best solution for that.

Solved in the newly released version 3.5.0.


feat: api returns 201 created and location header for post requests

see also https://stackoverflow.com/a/19895769/424243
ref #2

Coverage remained the same at 100.0% when pulling afed09c1466437730726b9bfa271d8627f2a992c on Pindar:2-created into 84053de4f8c485386adaf7f751e4fd77327cb6d5 on sebelga:master.

Coverage remained the same at 100.0% when pulling dce0567b80cf9cf705f9827976394afd978c8291 on Pindar:2-created into 84053de4f8c485386adaf7f751e4fd77327cb6d5 on sebelga:master.

Coverage remained the same at 100.0% when pulling dce0567b80cf9cf705f9827976394afd978c8291 on Pindar:2-created into 84053de4f8c485386adaf7f751e4fd77327cb6d5 on sebelga:master.

Coverage remained the same at 100.0% when pulling dce0567b80cf9cf705f9827976394afd978c8291 on Pindar:2-created into 84053de4f8c485386adaf7f751e4fd77327cb6d5 on sebelga:master.


test-ci

Description
PR test to take numbers from GitHub Actions to compare against https://github.com/prettier/eslint-config-prettier/pull/195#issuecomment-939274425

Closing PR since I asume we are done with all the tests


View Engine transfer to Ivy support

Will there be an update for the view engine transfer to ivy?
Generating browser application bundles (phase: setup)...Processing legacy "View Engine" libraries:
- @datorama/akita-ng-effects [es2015/esm2015] (https://github.com/datorama/akita)
Encourage the library authors to publish an Ivy distribution.

No. This library is deprecated. Use https://github.com/ngneat/effects

@NetanelBasal Can it be used with akita?

Yes


Sluggish performance on larger project

Very interesting new approach Zach, thanks for working on this!
I tried it with a larger project I'm working on. I see a number of performance issues:

on startup, it takes 20+ seconds to load what appears to be the project tree (firefox offers to kill the script)
editing a clojure file with 1000 lines is slow (>2 second delay for some keystrokes)

The repl by contrast seems fine so I suspect it's a javascript-side issue.

I'm seeing these issues on both Chrome and Firefox

Could you try version 1.3.0 in your project and let me know if you notice any improvement?

Closing, but feel free to let me know if it's still an issue with the latest version (currently 1.3.2).


Enable cppad on Windows

Thanks to https://github.com/microsoft/vcpkg/pull/12560 installing cppad on windows becomes simple. This PR introduces the support to cppad on Windows.
Related issues #75

Now everything is working. I'm reorganizing the commits.


[Backwards compatible] Migrate cloudflare_load_balancer to autogen docs

Migrate cloudflare_load_balancer docs to use the autogen process rather than templating, as documented here.
While migrating, I learned that the object session_affinity_attributes was being represented with a TypeMap, which does not have support for defining specific keys. As a result, descriptions of any of its keys were discarded when running make docs. In other to document this object properly, I refactored it to a TypeSet, which is a breaking change. I used TypeSet rather than a TypeList (of length 1) since the order of keys does not matter, but happy to refactor it if TypeList is more appropriate.
To preview the documentation changes, copy the file docs/resources/load_balancer.md and paste it into the Terraform doc preview. To see the difference with the current docs, the current docs can be found here.
Other changes include:

Improved the written descriptions to align more with the API docs (and fixed typos).
Improved the formatting of the descriptions (formatting property values and linking to other property Markdown anchors).
Added a terraform import example.
Moved all schema-related structs into schema_cloudflare_load_balancer.go.
Avoided reusing common schema.Elem definitions between LB rule overrides and main definitions. They were made separate as there are minor differences between some of the LB rule overrides and the main definitions, such as session_affinity_attributes not supporting the property drain_duration when it is a rule override. In addition, validation may be slightly different for rule overrides. The descriptions for all rule overrides are in the form See (), such as See session_affinity_attributes.

Open questions

I noticed that the main load balancer schema definitions include fallback_pool_id and default_pool_ids properties, which correspond to the API definitions fallback_pool and default_pools. The LB rule overrides for these are named fallback_pool and default_pools, which is a bit inconsistent. Since we are already introducing a breaking change, would it make sense to rename both occurrences to the same name? Are there any other breaking change improvements we can think of that might be nice to make now?
We have properties pop_pools/country_pools/region_pools, all which share a common sub-property pool_ids. As a result, when trying to create a Markdown anchor link to pools_ids, like so — [pool_ids](#pool_ids) — it will link to the first pool_ids definition, every time. Do you know if it is possible to tell Terraform to create an anchor so that we can link to a particular definition? (Of course, we can just change the autogenerated Markdown, but this is not a great solution).

Future work / Thoughts

I noticed that some of the properties have Computed: true, which aren't really computed and caused some confusion for me. Also, we can't set default values when Computed: true. For instance, ttl has this set, which prevents us from setting Default: 30. steering_policy also has it set and I believe this is because the API will return either "off" or "geo" when given an empty string. I still don't fully understand why Computed is needed in some of these places.
I tried to maintain some level of consistency between the main schema definitions and rule override definitions, but there were a few places I was afraid to touch, thinking there might be a possible corner case. For instance, the rule overrides fallback_pool and default_pools do not have any validation.

Acceptance tests pass
TESTARGS='-run "^TestAccCloudflareLoadBalancer_*" -count 1 -parallel 1' make testacc
TF_ACC=1 go test $(go list ./...) -v -run "^TestAccCloudflareLoadBalancer_*" -count 1 -parallel 1 -timeout 120m -parallel 1
?       github.com/cloudflare/terraform-provider-cloudflare     [no test files]
=== RUN   TestAccCloudflareLoadBalancerMonitor_Import
=== PAUSE TestAccCloudflareLoadBalancerMonitor_Import
=== RUN   TestAccCloudflareLoadBalancerPool_Import
=== PAUSE TestAccCloudflareLoadBalancerPool_Import
=== RUN   TestAccCloudflareLoadBalancer_Import
=== PAUSE TestAccCloudflareLoadBalancer_Import
=== RUN   TestAccCloudflareLoadBalancerMonitor_Basic
--- PASS: TestAccCloudflareLoadBalancerMonitor_Basic (3.92s)
=== RUN   TestAccCloudflareLoadBalancerMonitor_FullySpecified
--- PASS: TestAccCloudflareLoadBalancerMonitor_FullySpecified (10.49s)
=== RUN   TestAccCloudflareLoadBalancerMonitor_EmptyExpectedBody
--- PASS: TestAccCloudflareLoadBalancerMonitor_EmptyExpectedBody (4.10s)
=== RUN   TestAccCloudflareLoadBalancerMonitor_TcpFullySpecified
--- PASS: TestAccCloudflareLoadBalancerMonitor_TcpFullySpecified (5.07s)
=== RUN   TestAccCloudflareLoadBalancerMonitor_PremiumTypes
--- PASS: TestAccCloudflareLoadBalancerMonitor_PremiumTypes (7.36s)
=== RUN   TestAccCloudflareLoadBalancerMonitor_NoRequired
--- PASS: TestAccCloudflareLoadBalancerMonitor_NoRequired (2.28s)
=== RUN   TestAccCloudflareLoadBalancerMonitor_Update
--- PASS: TestAccCloudflareLoadBalancerMonitor_Update (5.50s)
=== RUN   TestAccCloudflareLoadBalancerMonitor_CreateAfterManualDestroy
--- PASS: TestAccCloudflareLoadBalancerMonitor_CreateAfterManualDestroy (5.72s)
=== RUN   TestAccCloudflareLoadBalancerMonitor_ChangingHeadersCauseReplacement
--- PASS: TestAccCloudflareLoadBalancerMonitor_ChangingHeadersCauseReplacement (5.26s)
=== RUN   TestAccCloudflareLoadBalancerPool_Basic
=== PAUSE TestAccCloudflareLoadBalancerPool_Basic
=== RUN   TestAccCloudflareLoadBalancerPool_FullySpecified
=== PAUSE TestAccCloudflareLoadBalancerPool_FullySpecified
=== RUN   TestAccCloudflareLoadBalancerPool_CreateAfterManualDestroy
=== PAUSE TestAccCloudflareLoadBalancerPool_CreateAfterManualDestroy
=== RUN   TestAccCloudflareLoadBalancer_Basic
=== PAUSE TestAccCloudflareLoadBalancer_Basic
=== RUN   TestAccCloudflareLoadBalancer_SessionAffinity
=== PAUSE TestAccCloudflareLoadBalancer_SessionAffinity
=== RUN   TestAccCloudflareLoadBalancer_AdaptiveRouting
=== PAUSE TestAccCloudflareLoadBalancer_AdaptiveRouting
=== RUN   TestAccCloudflareLoadBalancer_LocationStrategy
=== PAUSE TestAccCloudflareLoadBalancer_LocationStrategy
=== RUN   TestAccCloudflareLoadBalancer_RandomSteering
=== PAUSE TestAccCloudflareLoadBalancer_RandomSteering
=== RUN   TestAccCloudflareLoadBalancer_GeoBalanced
=== PAUSE TestAccCloudflareLoadBalancer_GeoBalanced
=== RUN   TestAccCloudflareLoadBalancer_ProximityBalanced
=== PAUSE TestAccCloudflareLoadBalancer_ProximityBalanced
=== RUN   TestAccCloudflareLoadBalancer_Rules
=== PAUSE TestAccCloudflareLoadBalancer_Rules
=== RUN   TestAccCloudflareLoadBalancer_DuplicatePool
=== PAUSE TestAccCloudflareLoadBalancer_DuplicatePool
=== RUN   TestAccCloudflareLoadBalancer_Update
=== PAUSE TestAccCloudflareLoadBalancer_Update
=== RUN   TestAccCloudflareLoadBalancer_CreateAfterManualDestroy
=== PAUSE TestAccCloudflareLoadBalancer_CreateAfterManualDestroy
=== CONT  TestAccCloudflareLoadBalancerMonitor_Import
--- PASS: TestAccCloudflareLoadBalancerMonitor_Import (3.72s)
=== CONT  TestAccCloudflareLoadBalancer_LocationStrategy
--- PASS: TestAccCloudflareLoadBalancer_LocationStrategy (5.62s)
=== CONT  TestAccCloudflareLoadBalancer_CreateAfterManualDestroy
--- PASS: TestAccCloudflareLoadBalancer_CreateAfterManualDestroy (8.08s)
=== CONT  TestAccCloudflareLoadBalancer_Update
--- PASS: TestAccCloudflareLoadBalancer_Update (7.38s)
=== CONT  TestAccCloudflareLoadBalancer_DuplicatePool
--- PASS: TestAccCloudflareLoadBalancer_DuplicatePool (3.06s)
=== CONT  TestAccCloudflareLoadBalancer_Rules
--- PASS: TestAccCloudflareLoadBalancer_Rules (5.21s)
=== CONT  TestAccCloudflareLoadBalancer_ProximityBalanced
--- PASS: TestAccCloudflareLoadBalancer_ProximityBalanced (5.36s)
=== CONT  TestAccCloudflareLoadBalancer_GeoBalanced
--- PASS: TestAccCloudflareLoadBalancer_GeoBalanced (5.76s)
=== CONT  TestAccCloudflareLoadBalancer_RandomSteering
--- PASS: TestAccCloudflareLoadBalancer_RandomSteering (6.18s)
=== CONT  TestAccCloudflareLoadBalancerPool_CreateAfterManualDestroy
--- PASS: TestAccCloudflareLoadBalancerPool_CreateAfterManualDestroy (5.83s)
=== CONT  TestAccCloudflareLoadBalancer_AdaptiveRouting
--- PASS: TestAccCloudflareLoadBalancer_AdaptiveRouting (5.33s)
=== CONT  TestAccCloudflareLoadBalancer_SessionAffinity
--- PASS: TestAccCloudflareLoadBalancer_SessionAffinity (12.39s)
=== CONT  TestAccCloudflareLoadBalancer_Basic
--- PASS: TestAccCloudflareLoadBalancer_Basic (5.23s)
=== CONT  TestAccCloudflareLoadBalancerPool_Basic
--- PASS: TestAccCloudflareLoadBalancerPool_Basic (4.01s)
=== CONT  TestAccCloudflareLoadBalancerPool_FullySpecified
--- PASS: TestAccCloudflareLoadBalancerPool_FullySpecified (4.02s)
=== CONT  TestAccCloudflareLoadBalancer_Import
--- PASS: TestAccCloudflareLoadBalancer_Import (5.72s)
=== CONT  TestAccCloudflareLoadBalancerPool_Import
--- PASS: TestAccCloudflareLoadBalancerPool_Import (4.26s)
PASS
ok      github.com/cloudflare/terraform-provider-cloudflare/internal/provider   147.055s

This schema still needs lots of more love, but hopefully these changes put it back on the right track!

thanks for this massive effort @tc80 👏 i'm very much in favour of getting this to a more consistent state however, we can't do big breaking changes like this outside of next major version bump (tracking 4.x in #1646). what i would suggest is for now, to put two PRs together. one that has all the backwards compatible changes in it to merge immediately and a second with all the breaking changes that we can track for 4.x. i'll have to schedule some time soon to start on putting the 4.x release together and iron out a bunch of the changes mentioned in #1646. the breaking changes will also need to provide a schema migration to try and automatically help out operators as much as possible with their migration to 4.x when it comes (TypeMap => TypeSet, field renames, etc).

I noticed that the main load balancer schema definitions include fallback_pool_id and default_pool_ids properties, which correspond to the API definitions fallback_pool and default_pools. The LB rule overrides for these are named fallback_pool and default_pools, which is a bit inconsistent. Since we are already introducing a breaking change, would it make sense to rename both occurrences to the same name? Are there any other breaking change improvements we can think of that might be nice to make now?

none that come to mind (other than adding account_id to other specific LB resources) but this is a good call out.

We have properties pop_pools/country_pools/region_pools, all which share a common sub-property pool_ids. As a result, when trying to create a Markdown anchor link to pools_ids, like so — pool_ids — it will link to the first pool_ids definition, every time. Do you know if it is possible to tell Terraform to create an anchor so that we can link to a particular definition? (Of course, we can just change the autogenerated Markdown, but this is not a great solution).

none to my knowledge. the automatic documentation uses the nested level as part of the anchor however, that doesn't seem to extend to the properties of the nested schema. this might be something we can suggest/PR to the upstream documentation tool, terraform-plugin-docs. i couldn't find an open issue for this one.

I still don't fully understand why Computed is needed in some of these places.

from the docs:

Computed is often used to represent values that are not user configurable or can not be known at time of terraform plan or apply, such as date of creation or a service specific UUID. Computed can be combined with other attributes to achieve specific behaviors, and can be used as output for interpolation into other resources

i think it was likely that because we defined the default in the API instead, we opted to have these listed as Computed in the schema to allow the API to provide the default when one wasn't provided. it's entirely possible, this is wrong too 😄

Thanks for all the feedback @jacobbednarz! Really appreciate it 🙏
You are also super prompt at responding!! 🥇
I amended the commit so that it is backwards compatible (and naturally reverted all changes to the test file). I will open a new PR once this merges with the breaking change to refactor TypeMap => TypeSet.
Since session_affinity_attributes is a TypeMap, I just shoved all the definitions of its sub-properties into it, like so:

thanks for understanding. unfortunately, TypeMap is still a thorn in our side and we're slowly moving everything off it since 2.x due to issues like this in the internals.
that's a good workaround for the session_affinity_attributes. i was going to say, if you don't have any better approaches, we could use a custom template (in `templates/resources/load_balancer.md.tmpl) that looks like this and append those descriptions to the bottom to link to.
---
page_title: "{{.Name}} {{.Type}} - {{.RenderedProviderName}}"
subcategory: ""
description: |-
{{ .Description | plainmarkdown | trimspace | prefixlines "  " }}
---

# {{.Name}} ({{.Type}})

{{ .Description | trimspace }}

## Example Usage

{{ tffile (printf "%s%s%s" "examples/resources/" .Name "/resource.tf") }}

{{ .SchemaMarkdown | trimspace }}

### Nested schema for `session_affinity_attributes`

Optional:

- `secure` (String) Configures the SameSite attribute on session affinity cookie. Value Auto will be translated to Lax or None depending if Always Use HTTPS is enabled. Note: when using value None, then you can not set [secure="Never"](https://registry.terraform.io/tools/doc-preview#secure). Available values: `Auto`, `Lax`, `None`, `Strict`.
- ...

## Import

Import is supported using the following syntax:

{{ codefile "shell" (printf "%s%s%s" "examples/resources/" .Name "/import.sh") }}

then in your session_affinity_attributes link to #nested-schema-for-session_affinity_attributes. then once this breaking change happens, remove the custom template and you'll be 100% autogen then.
i'll take a final pass over this tomorrow but it's looking good! thanks again.

Thanks for the idea! I didn't realize custom templates could be used like so.
To be honest, I would prefer avoiding the custom template if we can and keeping the documentation in the same place. However, if you feel strongly I have no problem making that change 😄

Never mind go for it my dude 😆

i just whipped in the custom template for you to take a look and let me know what you think. it keeps the same feel, etc so it blends in a bit better than all in a single attribute but let me know your thoughts. it's just as easy to revert!

Sweet, let's keep it. Thanks for pushing that up!
When we merge this I will open another PR to do the breaking change and revert this custom template 😄

Got to be careful with the Available Values!

Pushed one more commit to update the documentation (make docs).

Thanks for catching that! 🙏

thanks a bunch @tc80! this is awesome!


Recursive event folder not searching through subfolders for events?

Thank you for developing this very helpful plugin.
I installed v0.6.1 with the "recursive event folders" setting turned on.
I then added an 'events' folder for default location of events that are created by clicking on the calendar. I also added another calendar to the top level of my vault (/), hoping that Full Calendar will search through all subfolders for events, and show all the notes with relevant frontmatter in the vault (e.g., notes that I've "upgraded into events"). This doesn't work, however.

To resolve the issue, I had to restart Obsidian.


#2 - TypeError:: isAllowed type hint string no allowed Nette\Security\IAuthorizator::ALL

Please fix tests too - Tests\Integration\Classes\Authorizator::isAllowed($resource, string $privilege): bool

Hi, I fixed test, but I don't know why tests are failing.

Travis check is failing for all arachne packages at the moment because there is new version of phony but no compatible version of phony-phpunit (I'm checking if all dependencies are up to date using composer outdated --direct). @ezzatron will probably release a new version soon, see https://github.com/eloquent/phony-phpunit/issues/1 for details.
Anyway that's completely unrelated so I'll merge this now. Thank you!


Workspace TypeScript version not detected for nested folders (i.e monorepo)

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.68.0
OS Version: Darwin arm64 21.5.0

Steps to Reproduce:

Open two folders in your workspace (don't open parent folder)
run npm init and npm i typescript@latest inside the first folder
create a nested folder in the second folder and inside it run npm init and npm i typescript@latest inside the first folder
Open a typescript file anywhere in vscode
Now try to "Select typescript version"
Only the typescript version from the first folder will appear in the dropdown

Expected behaviour:

The nested typescript installation should appear in the options as well
Just like it would if the folders weren't nested:

This used to work in older version of VSCode, I'm pretty sure

Also, configuring the typescript.tsdk inside settings.json doesn't help because:
This setting cannot be applied in this workspace. It will be applied when you open the containing workspace folder directly.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Unable to make OCSP responder listen on IPv6, still broken in 3.4?

I see a couple others complaining about this years ago, but is it now expected to work in 3.4?  The documentation certainly says that it does...I've demonstrated that all the desired functionality is working with IPv4.  Now just trying to move to IPv6.
I've tried the "-port" option like this: "-port [2604:b641:1504:3103::bebe]:8888", but that yields:
ocsp: Can't parse "[2604:b641:1504:3103::bebe]:8888" as a number

I've tried the "-url" option like this: "-url http://[2604:b641:1504:3103::bebe]:8888", and that happily starts listening on the IPv4 loopback instead of giving an error message!
Just wondering if this works for others using version 3.4 + IPv6

Duplicate of #16204


API subscription expired

Not a bug of the plugin BUT
after the trial month I get the error
API subscription expired. Please renew the API subscription at Tuya IoT Platform
and all devices stop responding in homekit although they are still visible.
I remember seeing the option for 6 month renewal but I cannot find it on Tuya IOT platform any more.
Has anyone found a solution for this?

I'm not sure where to submit trial request too, but @ipa64 succeed.
https://github.com/0x5e/homebridge-tuya-platform/issues/14#issuecomment-1296375297

Thx.
I found it in the mean time, very obscure.
In any case; when the API subscription is expired, the plugin stops working.
Making this remark for documentation purposes, I understand this is out of your field of influence.
Thank you for the effort you put in this plugin though.

OK I will update a much detailed message and document later after I extend the trail month.  Nowhere in all these installation guides is it mentioned that the tool no longer works after a month because a trial period has expired, which you then have to renew manually.
Of course, you could just take the subscription plan ... the cheapest version ONLY costs $25,000 anyway. We've all just shaken it out of our hands.
I only noticed this rubbish with the trial period today when I was sitting in a freezing cold flat because none of my heaters were switched on -> Subscription expired.
I wish there was another tool that worked with my Wi-Fi radiators and Homekit so that I wouldn't have to deal with this mess every month.

@hattabatatta You can extend 6 months at once, not every month. Of course the price is unresonable for individual users, but there's nothing I can do with the public API and SDK.
Lan protocol is private and not published, you can find the local plugins with reverse engineering, but may not working on all firmwares.

Yes, I saw the possibility of extending it by 6 months.
But that doesn't make the whole thing any less absurd imho.
I have already considered reverse engineering the apps of the providers, but unfortunately I only have iOS and dealing with it is a horror for me as a pure .NET developer :D

Yes, "extending every 6 months" is the tuya company's decision, I can do nothing with that.
I'm able to implement the lan protocol but I'm not allowed to do this, I think.
You can search "tuya local" keywords on github.

Don't worry I didn't mean it as an accusation ;)
I'll see if I want to read up on the subject and then possibly create my own solution.

The lan solution would be a possibility maybe, but you need to obtain the local key for the device first and I think that is only possible through the api? Which would mean that communication can be done locally, but you need a way of getting to the local key.

Yes I agree :) @hattabatatta
Yes localkey can only get from api, but it won't changed unless the device got removed/unpaired. @PrimaveraNL

This is true, but when you would want to add a new device, you need a key for that.
Unless you set it up and then do not expand your smart home, you will need an account with Tuya after the trial period.
BTW I got my whole realm working again after the subscription was renewed. There is no info on what the policy is after a 6 month trial.

I think the first-time trial period won't get removed, so there's always a way to get the keys, create an new account is free, just cost time.
But the extend period policy indeed has the possibility to change, it depends.

I have extended my IoT core for 6 months. However, the error continues.
[TuyaOpenAPI] API subscription expired. Please renew the API subscription at Tuya IoT Platform.
Fetching home list failed. code=28841002, msg=No permissions. Your subscription to cloud development plan has expired.

How long does it take to reconnect? Quite inconvenient.

The subscription needs to be 'reviewed', I think it took about 1,5 days in my case.
Maybe over the weekend it will take longer?

Review approved, deadline extended.
But it cannot make API request.

Review approved, deadline extended.
But it cannot make API request.

From your description seems like a cloud side bug, please submit a ticket in the tuya platform.

https://github.com/tuya/tuya-homebridge/issues/321

After submitting the ticket, my issue was resolved.
thx

This whole Tuya platform seems like classic Chinese junk - super cheap poorly made hardware, 3rd rate connection platform that we have to work around because they want to spy on the data, not let us control it locally. I know my "social credit score" will drop for saying that but I don't really care.

@0x5e, thanks for sharing your perspective on the privacy. It's encouraging to hear. Do we need anything other than the free IoT Core subscription? I ask because when I log into my Homebridge Service API tab on the IoT Platform, I see these services enabled:

IoT Core
Smart Home Basic Service
Device Status Notification
Industry Basic Service

Are those last three included in the IoT Core? And, if not, are they free?
Thanks.

@githubnavigator  It's written on https://github.com/0x5e/homebridge-tuya-platform#configuration, it depends on what type of device you have. they are all free, but need to extend trial every 6 month :(


Translate tutorials/kubernetes-basics/expose/expose-intro/ in Japanese

This is a...

[x]  Feature Request
[ ]  Bug Report

Problem:
No tutorials/kubernetes-basics/expose/expose-intro/ in Japanese.
Proposed Solution:
Translate tutorials/kubernetes-basics/expose/expose-intro/ in Japanese.
Copy from en content and Update content/ja/docs/tutorials/kubernetes-basics/expose/expose-intro.html.
Page to Update:
https://kubernetes.io/ja/tutorials/kubernetes-basics/expose/expose-intro/

#12074

/close


Review and standardize how we normalize code sent to the interactive window

pythonFiles/normalizeSelection.py seems to be a carry-over from the python extension split and is only used in some cases for normalizing code sent to the IW - specifically when executing a selection, but not when executing the contents of a cell.
If we do want to continue using the code here, perhaps we should also use it for cell execution as well. Otherwise, perhaps we can remove the duplication between python and jupyter extensions

cc @DonJayamanne


Implement the interface for the external domain-specific models

Now the integration with external model is copmlicated because a lot of manual operations should be done.

Add new operation ("custom_model") to FEDOT. It will save the domain-specific model output (e.g. NEMO forecast) at fit stage and return in at predict stage. The real integration with NEMO is not required now, but the train/test separation should be supported;
Build the example with hybrid chain (ML models + NEMO);

Implemented as data_source


[wip] Add grunt, linting, enable in travis-ci and make pass

Add linting and enable travis-ci for grunt + lint both the es5 and es6 files; make files pass.

Eh,  apologies, I am not sure why my 'amends' were added as new commits. Please, when reviewing, look only at the last commit.

@mooeypoo thanks for the patches! The es6 support is awesome, and I have been using it heavily elsewhere, and stabilizing tests would be good.
Most of the Kartohterian code is indented with spaces, and uses much more compact spacing. Refactoring all of it just for the sake of refactoring seems wrong, esp considering that MW-style spacing is very rare.
Another thing - we should probably switch all let to const - unless something is changing. Especially this applies to the const util = require('util'); stile declarations (and we should probably make them one per line.
Thanks!

Don't worry about the multiple patches - most of github PRs are like that, and you keep adding to them (instead of rebasing - which is a really horrible practice because it looses history). Once you are done, simply remove the WIP tag from the title, and when we merge, all patches will be squashed into one.

Yeah, I used the general "mediawiki" styles just out of habit; I can probably change the linter from tabs to spaces (though I must admit, I'm of the 'tabs are superior' crowd, but I don't actually mind ;) and I can also change the 'let' statements to 'const'. I was trying to avoid mixing the linting changes with more substantive changes to make review easier, but 'let -> const' change is probably best to do now anyways.
I'll submit the followup soon. Thanks!

Thanks!!  I am an avid spaces, not tabs person - at least that's what my 29 years of dev tells me (I'm soo not pulling a rank on this one!!! :D ) -- and it seems github's user survey backs me up on that ;) https://ukupat.github.io/tabs-or-spaces/  But even more importantly, it seems that those who use space earn more ;)  https://stackoverflow.blog/2017/06/15/developers-use-spaces-make-money-use-tabs/   </religious war>
Perhaps we should set up a kartotherian-lint style - similar to  https://www.npmjs.com/package/eslint-config-airbnb --  called eslint-config-kartotherian ?

Well, most code writing software today can just switch tabs with spaces for you, so I guess practically speaking it doesn't matter much anymore, but the "earning more" fact should sway me here... I shall consider switching to the dark side...
As for the rest of the style rules, I do admit that the MW-style brainwashing worked on me well; I think that spaces within brackets and parentheses make the code more readable and I use that standard even in my personal projects (in fact, I sometimes use it in PHP! don't tell anyone) -- so while I think we should stick to that, I can suffer in silence </emotional blackmail>
Seriously, though, we could create a specific kartotherian rule set, it would make it much easier to then go and continue implementing those in the other kartotherian repos.
Do you have a base set you want to start from, or rules you want to use? If we come up with a standard, I can edit this PR for it, and when we agree on how it looks/feels I can continue to implement in the rest of the repos for consistency.

LOL :)
Turns out I already have it - https://github.com/kartotherian/eslint-config-kartotherian
It might be slightly outdated and may need to be updated.
Basic settings:   indent 2spaces, must have semicolon, no unused vars, use single quotes or backticks (no double quotes), use === instead of ==, no trailing comma, must have newline at the end, no space after function name before '('.   Basically similar to the airbnb preset, but I would prefer to set up kartohterian-wide one.

I might be missing something, but I don't see the file with the actual rules in that package...?

@mooeypoo you are right, I forgot to check it in. I guess it was never really used - I started playing with it but it was never complete. I just checked it in.

@nyurik is the eslint-config-kartotherian published in npm? When I tried to add it as a package, I'm getting:
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/eslint-config-kartotherian
I can alternatively "just" use the base .eslintrc file that's in that package in each individual repo for now, but I want to verify and see what you want to do for consistency.

It probably isn't. Can you try using / polishing it with one repo, and once its ready, we can push it to npm?   I wouldn't want to maintain a copy of the same file in 20 repos :)

Actually never mind, I just published it, will make things easier :)

@nyurik, I had to add "eslint-config-airbnb-base" to the dev dependencies in this repo, because of https://github.com/kartotherian/eslint-config-kartotherian/pull/2 -- can you merge the eslint-config-kartotherian pull request and re-publish the npm package? Then I can update the dependencies in the PR to not need the airbnb-base dependency itself.

@mooeypoo I revised it a bit more, and removed most of the per-lib customizations.  I think other libs should do similar.  Also, I removed the test file - it was unrelated to this module - I think it was a leftover from the node template.


Influx line format, enum metrics string send as field

Influx line format, enum metrics string we want to send as field and not as tag.
The field name should have a suffix "_str" on the normal metric name.

This is merged in #395 and #391.


Variant needs move constructors

Variant without move constructors causes lots of copying. Attributes are one of the biggest offenders here. Serializable drags registered attributes through Variant. As a result multiple copies may be performed during (de)serialization.

It was implemented recently


ExhibitionDB data model

Create an ER diagram of the ExhibitionDB data model using PlantUML
https://plantuml.com/ie-diagram

ER diagram created and referenced in README


Issue #2985: Add object ids by default in uhdm output

Issue #2985: Add object ids by default in uhdm output
Also, fixed the regression script update logic to fix line-endings for Windows.
NOTE: PR includes PR 723 from UHDM

Codecov Report

Merging #2988 (6234f6b) into master (2323361) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2988   +/-   ##
=======================================
  Coverage   27.40%   27.40%
=======================================
  Files          99       99
  Lines       32759    32759
=======================================
  Hits         8979     8979
  Misses      23780    23780

Continue to review full report at Codecov.

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

This PR and https://github.com/chipsalliance/UHDM/pull/723 do not add-up in functionality.
I reverted https://github.com/chipsalliance/UHDM/pull/723 until there is more evidence that vpiParent info is visible in the visitor.

@alaindargelas Targeted change. Will reintroduce the vpiParent change as a separate PR.

Actually, this was a bad idea. I'm working on a change in UHDM elaboration, the IDs changes makes the diffs unreadable.


Check mikz/miser

Hi!
I would consider joining effort by porting my bank scrapers from https://github.com/mikz/miser
But I took very different approach, using real browser and capybara instead of doing all that hand.
Would you consider it as a optional dependency?

Wow, that's awesome! We weren't aware about your work with miser.
We prefer finding real APIs to inreact with, but we're ok with web scrappers too. In fact the implementation we have for Bankinter (done by @ismaGNU) uses Nokogiri for scrapping their site.
I think we should definitely join efforts.
Right now, and after trying multiple options, we're using mechanize for HTTP requests, which has an API similar to capybara. Before porting your scrapers, do you think could it be possible to rewrite them with mechanize instead of capybara? To avoid adding additional dependencies.
Also, have you tried to find APIs for banc_sabadell and evo_banco? Check out the slides of the talk we did in Madrid.rb which explains how to do it (video will be out soon):
I'm really excited to see this happening :clap:!

@javiercr yeah I tried using mechanize, but there is just too much javascript that I didn't want to bother with it.
What about having the banks as separate gems which can have own dependencies?
I'm all for discovering real APIs and I already tried. Not sure which one of them, but I think eve_banco was really weird and I could not get anything, but sabadell was pretty fine.
Also I have this prototype branch https://github.com/mikz/miser/pull/2 that is a website, but encrypts your credentials by master secret, so you can host it on heroku. But that all can be extension to bank scrap.
Will check the APIs and get back to you in few days.

Hi, I am glad to hear about miser, It is music for our ears.
Like @javiercr says, could you try to avoid using capybara? I have tried capybara before but It has strong dependencies. Actually, you need a xserver and real browser to begin with, that was my reason to move on to http requests and html parsers.
I understand if you don´t want to migrate, It is tedious. But, if you want, I could help you with the migrations, I think I can get an evo bank account to try.
IMO, splitting banks into gems its not a good idea. The goal of this gem is to unify. It´s a same that dependencies could not be optional.
Anyway, thanks for taking the time to consider the migration. Let us know what are your improvement checking the APIs.

@mikz is that JS all mandatory? @ismaGNU had to run some JS and used execjs gem for that, but I understand that in some case we could need a full browser.
Splitting into multiple gems is an option (as long as we keep a main gem that would be a dependency for all the individual gems), but we went for the single gem approach following the model used by ActiveMerchant, which I think it makes easier for newcomers to write new adapters for other banks. Our idea was to add a script that could generate a boilerplate adapter, with the proper class and the methods that need to be implemented in order to be compatible with the bank_scrap's API. @ferblape @raulmarcosl what do you think about this?
Regarding the site app, @raulmarcosl was working in another gem that would be something very similar, a web app for display bank_scrap data in a nice format (with charts and all of that).

@javiercr No idea if it is mandatory. Probably it could be replaced by execjs. But I just found easier to run capybara.
The drivers are really simple: https://github.com/mikz/miser/blob/master/lib/miser/driver/banc_sabadell.rb and https://github.com/mikz/miser/blob/master/lib/miser/driver/evo_banco.rb.
After trying firefox, chrome, capybara-webkit the easiest one is poltergeist which is wrapper of phantomjs.
Installing phantomjs is fairly easy, but still it is a dependency.
I would not consider porting current drivers to non-browser stack, but if their API proves hackable, I'd make a driver.
I understand the desire to unify the ecosystem and agree. However, some drivers require more things than others, for example the ING requires rmagic? What if I can't install it? Rmagic has issues on different ruby version etc etc etc. For someone it might be just easier drop statically linked phantomjs.
Having all dependencies in the main gem, is a bad idea imo. But you can still have all the drivers in one repo, and just split it to gems. Almost every major ruby project in the end splits to subgems. I understand it is more maintenance, but  when it is in one repo, it is not that bad.
Looking forward our collaboration guys!

You're right about rmagick, we tried to avoid it when hacking ING but it was the easier solution for hacking the virtual keyboard (we needed image processing).
I use phantomjs in a daily basis (for Rails integration testing), and it is cool but IMHO is a bit slow until it fires up. However I must admit I haven't tried it outside Rails apps, so I'm not sure if that lack of speeds comes actually from phantomjs / poltergeist.  How much long does it takes for fetching bank transactions with your current implementation?
In other words, in my opinion for implementing bank adapters here is the order of preference:
 Real APIs > Simple Web scrappers > Web scrappers that require full browsers with JS enabled
Do you know any other gem that uses a multi gem approach besides Rails? So we can research about their approach.

Sabadell takes about 10 second to get list of recent transactions. Evo looks broken now, because they changed the website.
Definitely agree on the order. I made miser because I wanted to get report how much I spent every day to my mailbox. So I went simple and dirty.
Just from top of my head: Rspec went through split in 2.x. Compass now splits cli and core. Cucumber in 2.0 is split. Capybara drivers are splitted. Github's peek. Pry and its extensions. NewRelic's contrib. Some of them are governed by different people and some of them by the same.
I think that properly designed driver system would allow people to have best of the both worlds. For example if the driver is good and you have a contributor that has that account, you'll pull it in if the author agrees.

We'll check out those projects.
If we finally decide to stick to the one single gem approach, I'd suggest using [http://nofail.de/2010/11/gem-best-practice/](this approach) for optional dependencies:
# require optional dependency
begin
  require 'rmagick'
rescue LoadError
  puts "ING needs rmagick to be installed, please 'gem install rmagick'"
end

I don't have a strong opinion about splitting. I like the idea of keeping things smaller, but the examples mentioned have a lot of lines of code, much more than bank_scrap right now, so it was justified.
Given that there are no tests right now, I'd keep things unified with the begin/rescue approach when requiring gems. But, of course, it's just an opinion.

Speaking of tests, I was investigating how to add tests for miser and found one decent solution.
Using VCR with https://www.relishapp.com/vcr/vcr/docs/configuration/filter-sensitive-data as a base + some rake task to do a cleanup. But for API tests it does not make much sense, so I'd settle with webmock.
I'd definitely write tests when porting my drivers, so which tools you prefer? Minitest/rspec?

Thanks for the input @ferblape!
@mikz why do you think VCR doesn't make sense for API tests? I was thinking about using it but I didn't know it had support for filtering sensitive data, I'll give it a try.
Regarding rspec vs minitest, I'd prefer rspec.
Sorry about the off topic, but me and @raulmarcosl we've been thinking about setting up a Slack channel to discuss the project. Check out this blog post and let me know if you like the idea.

@javiercr because you want to spec the API client, so you want to have the requests and responses in the test. You probably want to make some 'fake' calls, so for example you don't have to login every time.
Also if you want to set up expectations, you need to have some values. Those values would change if different people would run the tests (unless you want to share an account with them).
Regardin Slack, I welcome the idea. It has IRC gateway, so it is fine for me :) But freenode would also work.

@mikz, raul created an Slack channel, click on the Slack badge in the Readme and let's talk about this. :D


Add test_post_with_variables and update test_duplicate_keys method get

Added a missing post test method with variables and made a valid get method test_duplicate_keys

Not fix run


Changing the Applies to section to say SQL 2022

This function/DMV is related to Query Store Hints functionality that's available in SQL 2022 (https://learn.microsoft.com/en-us/sql/relational-databases/performance/query-store-hints?view=sql-server-ver16), but the article says it applies to all supported versions. I got some questions about it recently, so I thought to update the doc.

@rwestMSFT
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

@rwestMSFT, unless you are confident that this is exactly correct, we should merge these changes to the private repo for validation and staging. Can you do that, or do you need assistance? Thanks.

@rwestMSFT, please respond in a comment and then sign off again.
#hold-off


Question: Is it possible to upload a file using a FunctionMonkey function?

I don't mean through BlobStorage, just wanted to get that out there.
I need a function that will receive a CSV file and other metadata which can be processed on the server and saved to a database
I have created a function which accepts a File with Content-Type of multipart/form-data but the value of File is always null
I am using Postman to post to the function, just to test things. My function looks like this:
    public class ImportCandidatesCommand : ICommand<IActionResult>
    {
        public string CenterId { get; set; }
        public object File { get; set; }
    }

    public class ImportCandidatesCommandHandler : CommandHandler, ICommandHandler<ImportCandidatesCommand, IActionResult>
    {
        public ImportCandidatesCommandHandler(CosmonautClient cosmonautClient, ILogger logger) : base(cosmonautClient, logger)
        {
        }

        public Task<IActionResult> ExecuteAsync(ImportCandidatesCommand command, IActionResult previousResult)
        {
            // do something with the file
        }
    }

This sort of got answered in this issue


Launch gitlab-runner service without requiring UI login session

Move the gitlab-runner service to a launchd service so we don't have to log in

This might actually not be feasible, because you can't even run gitlab-runner start from an ssh session because it will error out as follows: FATAL: Failed to start gitlab-runner: "launchctl" failed: exit status 112, Could not find domain for port (Aqua).

Closing - I don't think this is feasible


Improve change status

In GitLab by @froura on Jul 17, 2024, 15:03
Hi @ltenorio I have a suggestion for what could be a (small) improvement in the GUI.
Coming from the old version, I found the option with the colors (without the "desplegable") a much more visual option to get the commands to change the job status. Could it be possible to keep this format in the new version?
Here 2 screenshots about what I mean:

Thanks! :smile:

In GitLab by @ltenorio on Jul 17, 2024, 15:15
Hello @froura! Thanks for the feedback. Sure, now that I see colors can help users to identify the correct status they want.
Maybe we can keep the desplegable (bc now the list of statuses is bigger) but add the colors in the options like is shown in the select option of the graph view like this:

WDYT?

In GitLab by @ltenorio on Jul 18, 2024, 11:56
mentioned in commit 780a75a94c10e1e57522c89bee8b8e60aae292e9

In GitLab by @froura on Jul 17, 2024, 15:30
Hi @ltenorio !
Even though I prefer still the option without desplegable (a bit picky, but it is one click less), I see that it may not be recommended given the bigger number of statuses.
This option with the colors would be a good compromise!
Thanks for taking care of it.
Francesc


The schema for stac-item.json does not reflect the change in 0.5.0 release

To validate the Item JSON created with "Link as a Dictionary" (https://github.com/radiantearth/stac-spec/releases/tag/v0.5.0) it is necessary to have the following change in stac-item.json. It appears that the master branch has not received this change.
"links": { "type": "array" }
to
"links": { "type": "object" }

I believe this is fixed in 0.5.1 or 0.5.2 (and was part of why I issued that release). Can't go back to 0.5.0 and change it there, unfortunately.


Creating a Supervisord for RTD

I can access RTD if I use ./checkouts/readthedocs.org/manage.py runserver <IP_ADDRESS>:8000  However, if I reboot the server, I'll need to run this command again.  How can I have RTD start on boot-up?
Bigger picture, I'd like to use the VMs ip address when accessing this page because URLs like http://my_libarary.ip_address:8000

Gunicorn or another server works. This is an infrastructure decision that isn't related to RTD though, closing as it isn't an issue with RTD.

As someone who knows nothing about running a python web app (I use apache/php) can you point me to where I can find some info about howto use Gunicorn with RTD?


ExcludeFromCodeCoverage ignore above properties

Description
When excluding a propety from code coverage using de ExcludeFromCodeCoverage attribute this is ignored in the coverage result.
Repro steps
Example code:
public sealed class Euro : ICurrencyDefinition
{
	private const string currencyCode = "EUR";

	[ExcludeFromCodeCoverage]
	public string CurrencyCode
	{
		get
		{
			return currencyCode;
		}
	}

	[ExcludeFromCodeCoverage]
	public string Name
	{
		get { return "Euro"; }
	}

	[ExcludeFromCodeCoverage]
	public int NumberOfDecimals => 2;
}

All the above situations are marked as missing test coverage.
Expected behavior
The properties are marked as covered.
Actual behavior
The properties are not marked as missing code coverage.
Known workarounds
Exclude the whole class from code coverage.
Related information

coverlet.msbuild Version: 2.3.1
Visual Studio Version: Visual Studio Professional 2017 (15.8.7 and 15.9.0 Preview 3)
Microsoft Test Execution Command Line Tool Version: 15.8.0

close for dup


Move to IBM github presence?

I propose we move this to http://github.com/IBM/node-odbc

One of the requests that wankdanker had when I took it over was that we didn't move it under the IBM organization GitHub, as it might turn off those who don't use IBM products or are connecting from non-IBM systems and/or to non-IBM databases.
Now, the actual code ownership doesn't change if it moves over there, since my work is all property of IBM, but hosting it in more "neutral" territory was the initial hope. Willing to keep entertain the idea, but I just want to make sure people will still be willing to contribute and test if it moves to the organization GitHub

That's a reasonable argument for keeping this in a more neutral territory. Closing this issue


Proposal's title count hotfix

What does this PR?
It shows the correct number of votes in the proposal's  title.
Bug
As you can see in the video attached below.  When user try to gets the votes by just changing the page, it is working fine.
But when user search any thing and then change the page, it shows the wrong count. I debugged the issue and then correct it.
https://user-images.githubusercontent.com/106739598/216985934-d639e0da-708d-4337-9814-9b7723f0ec93.mp4
Steps to reproduce

Open any proposal and change the page and see the number of votes on the title.
Search any user name and then change the page and jump into the last page. It will show the correct count on that proposal.
You can take help from the attached video.

Screenshot / Video
https://user-images.githubusercontent.com/106739598/216985958-1d225082-23cc-4975-a719-6c4844491e00.mp4

@MTSaeed good find, one more fix... don't show 0+ when no data is fetched yet. Just keep Votes on .... without numbers only after fetch is success we can show 1000+ or numbers, makes sense?

@MTSaeed good find, one more fix... don't show 0+ when no data is fetched yet. Just keep Votes on .... without numbers only after fetch is success we can show 1000+ or numbers, makes sense?

https://user-images.githubusercontent.com/106739598/217168134-6a4b5b28-aabe-4d07-9cd4-c0754b9f92bb.mp4


don't attempt to make 'make clean' work on old checkouts

It's just not worth the extra complication in the Makefile, and the code for it was actually broken.
Also, outdent comment so it doesn't get splattered onto the console.
Fixes #2188.

You'll need to rebase to get tests to pass


WIP: Add southbound API to pass notification to RackHD (refer to ODR682)

This is the PR to support https://github.com/RackHD/on-http/pull/377
Still needs to be done:

Add unit test

DO NOT MERGE untill I remove the WIP flag.

*** BUILD #1274 ***
Test Name: Base Job Subscriptions should clean up subscriptions for every subscriber helper method
Error Details: Object #<EventsProtocol> has no method 'subscribeTaskNotification'
Stack Trace: TypeError: Object #<EventsProtocol> has no method 'subscribeTaskNotification'
    at InnerMockJob._subscribeTaskNotification (lib/jobs/base-job.js:9:10828)
    at spec/lib/jobs/base-job-spec.js:222:35
    at node_modules/lodash/index.js:3073:15
    at baseForOwn (node_modules/lodash/index.js:2046:14)
    at node_modules/lodash/index.js:3043:18
    at Function.<anonymous> (node_modules/lodash/index.js:3346:13)
    at Context.<anonymous> (spec/lib/jobs/base-job-spec.js:212:15)

Test Name: Install OS Job should set up message subscribers
Error Details: expected _subscribeHttpResponse to have been called at least once, but it was never called
Stack Trace: AssertionError: expected _subscribeHttpResponse to have been called at least once, but it was never called

Test Name: Install OS Job should finish job if http response has expected completionUri
Error Details: expected _subscribeHttpResponse to have been called exactly once, but it was called 0 times
Stack Trace: AssertionError: expected _subscribeHttpResponse to have been called exactly once, but it was called 0 times
    at spec/lib/jobs/install-os-job-spec.js:150:55
    at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:507:31)
    at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:581:18)
    at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:697:14)
    at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
    at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)

Test Name: Install OS Job should not finish job if http response has bad http statusCode
Error Details: expected _subscribeHttpResponse to have been called exactly once, but it was called 0 times
Stack Trace: AssertionError: expected _subscribeHttpResponse to have been called exactly once, but it was called 0 times
    at spec/lib/jobs/install-os-job-spec.js:166:55
    at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:507:31)
    at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:581:18)
    at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:697:14)
    at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
    at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)

Test Name: Install OS Job should not finish job if http response has no expected completionUri
Error Details: expected _subscribeHttpResponse to have been called exactly once, but it was called 0 times
Stack Trace: AssertionError: expected _subscribeHttpResponse to have been called exactly once, but it was called 0 times
    at spec/lib/jobs/install-os-job-spec.js:181:55
    at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:507:31)
    at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:581:18)
    at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:697:14)
    at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
    at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)

Test Name: test_nodes_discovery
Error Details: timeout waiting for task discovery
-------------------- >> begin captured logging << --------------------
urllib3.connectionpool: INFO: Starting new HTTP connection (1): localhost
tests.api.v1_1.nodes_tests: INFO: Wait start time: 2016-07-20 06:07:20.424084
amqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']
amqp: DEBUG: Open OK!
kombu: INFO: Starting AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>
amqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']
amqp: DEBUG: Open OK!
kombu.mixins: INFO: Connected to amqp://guest:**@<IP_ADDRESS>:9091//
amqp: DEBUG: using channel_id: 1
amqp: DEBUG: Channel open
tests.api.v1_1.nodes_tests: INFO: Graph.SKU.Discovery - target: 578f4d66c50c0b2a088bfa55, status: succeeded, route: bd1fb8a1-e38e-445c-bc1d-a465db06b41b, duration: 0:01:32.023687
tests.api.v1_1.nodes_tests: INFO: Graph.SKU.Discovery - target: 578f4d6bc50c0b2a088bfa5c, status: succeeded, route: 3fd0dc9c-6604-42a4-844a-56d7b83ae863, duration: 0:01:36.700402
modules.worker: ERROR: subtask timeout after 1200 seconds, (id=discovery), stopping..
kombu: INFO: Stopping AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>
modules.worker: INFO: stopping subtask for discovery
amqp: DEBUG: Closed channel #1
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/v1_1/nodes_tests.py", line 122, in test_nodes_discovery
    message='timeout waiting for task {0}'.format(self.__task.id))
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 67, in assert_false
    raise ASSERTION_ERROR(message)
"timeout waiting for task discovery\n-------------------- >> begin captured logging << --------------------\nurllib3.connectionpool: INFO: Starting new HTTP connection (1): localhost\ntests.api.v1_1.nodes_tests: INFO: Wait start time: 2016-07-20 06:07:20.424084\namqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']\namqp: DEBUG: Open OK!\nkombu: INFO: Starting AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>\namqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']\namqp: DEBUG: Open OK!\nkombu.mixins: INFO: Connected to amqp://guest:**@<IP_ADDRESS>:9091//\namqp: DEBUG: using channel_id: 1\namqp: DEBUG: Channel open\ntests.api.v1_1.nodes_tests: INFO: Graph.SKU.Discovery - target: 578f4d66c50c0b2a088bfa55, status: succeeded, route: bd1fb8a1-e38e-445c-bc1d-a465db06b41b, duration: 0:01:32.023687\ntests.api.v1_1.nodes_tests: INFO: Graph.SKU.Discovery - target: 578f4d6bc50c0b2a088bfa5c, status: succeeded, route: 3fd0dc9c-6604-42a4-844a-56d7b83ae863, duration: 0:01:36.700402\nmodules.worker: ERROR: subtask timeout after 1200 seconds, (id=discovery), stopping..\nkombu: INFO: Stopping AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>\nmodules.worker: INFO: stopping subtask for discovery\namqp: DEBUG: Closed channel #1\n--------------------- >> end captured logging << ---------------------"

Test Name: teardown
Error Details: 'X-Auth-Token'
-------------------- >> begin captured logging << --------------------
modules.redfish_auth: INFO: auth already disabled.
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/redfish_1_0/session_service_tests.py", line 38, in teardown
    Auth.disable()
  File "/home/jenkins/workspace/on-tasks/RackHD/test/modules/redfish_auth.py", line 67, in disable
    del config.api_client.default_headers['X-Auth-Token']
"'X-Auth-Token'\n-------------------- >> begin captured logging << --------------------\nmodules.redfish_auth: INFO: auth already disabled.\n--------------------- >> end captured logging << ---------------------"

Test Name: teardown
Error Details: 'X-Auth-Token'
-------------------- >> begin captured logging << --------------------
modules.redfish_auth: INFO: auth already disabled.
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/redfish_1_0/account_service_tests.py", line 38, in teardown
    Auth.disable()
  File "/home/jenkins/workspace/on-tasks/RackHD/test/modules/redfish_auth.py", line 67, in disable
    del config.api_client.default_headers['X-Auth-Token']
"'X-Auth-Token'\n-------------------- >> begin captured logging << --------------------\nmodules.redfish_auth: INFO: auth already disabled.\n--------------------- >> end captured logging << ---------------------"

Test Name: pollers_data_get
Error Details: Condition was True.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/v2_0/pollers_tests.py", line 158, in pollers_data_get
    assert_false(poller.get('lastFinished', False))
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 67, in assert_false
    raise ASSERTION_ERROR(message)
AssertionError: Condition was True.

@tannoa2 This is the notification API that you want.

Looks great to me

*** BUILD #1284 ***
Test Name: Base Job Subscriptions should clean up subscriptions for every subscriber helper method
Error Details: Object #<EventsProtocol> has no method 'subscribeTaskNotification'
Stack Trace: TypeError: Object #<EventsProtocol> has no method 'subscribeTaskNotification'
    at InnerMockJob._subscribeTaskNotification (lib/jobs/base-job.js:9:10828)
    at spec/lib/jobs/base-job-spec.js:222:35
    at node_modules/lodash/index.js:3073:15
    at baseForOwn (node_modules/lodash/index.js:2046:14)
    at node_modules/lodash/index.js:3043:18
    at Function.<anonymous> (node_modules/lodash/index.js:3346:13)
    at Context.<anonymous> (spec/lib/jobs/base-job-spec.js:212:15)

Test Name: Install OS Job should finish job if http response has expected completionUri
Error Details: expected _done to have been called exactly once, but it was called twice     _done() at /home/jenkins/workspace/on-tasks/build/lib/jobs/install-os.js:9:11718     _done(TypeError: Object #<EventsProtocol> has no method 'subscribeTaskNotification') at /home/jenkins/workspace/on-tasks/build/lib/jobs/install-os.js:9:12721
Stack Trace: AssertionError: expected _done to have been called exactly once, but it was called twice
    _done() at lib/jobs/install-os.js:9:11718
    _done(TypeError: Object #<EventsProtocol> has no method 'subscribeTaskNotification') at lib/jobs/install-os.js:9:12721
    at spec/lib/jobs/install-os-job-spec.js:151:39
    at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:507:31)
    at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:581:18)
    at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:697:14)
    at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
    at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)

Test Name: Install OS Job should not finish job if http response has bad http statusCode
Error Details: expected _done to not have been called
Stack Trace: AssertionError: expected _done to not have been called

Test Name: Install OS Job should not finish job if http response has no expected completionUri
Error Details: expected _done to not have been called
Stack Trace: AssertionError: expected _done to not have been called

Please change the wait-completion-uri job as well: https://github.com/RackHD/on-tasks/blob/master/lib/jobs/wait-completion-uri.js#L57

*** BUILD #1291 ***
Test Name: Base Job Subscriptions should clean up subscriptions for every subscriber helper method
Error Details: Object #<EventsProtocol> has no method 'subscribeTaskNotification'
Stack Trace: TypeError: Object #<EventsProtocol> has no method 'subscribeTaskNotification'
    at InnerMockJob._subscribeTaskNotification (lib/jobs/base-job.js:9:10835)
    at spec/lib/jobs/base-job-spec.js:222:35
    at node_modules/lodash/index.js:3073:15
    at baseForOwn (node_modules/lodash/index.js:2046:14)
    at node_modules/lodash/index.js:3043:18
    at Function.<anonymous> (node_modules/lodash/index.js:3346:13)
    at Context.<anonymous> (spec/lib/jobs/base-job-spec.js:212:15)

Test Name: Install OS Job should finish job if http response has expected completionUri
Error Details: expected _done to have been called exactly once, but it was called twice     _done() at /home/jenkins/workspace/on-tasks/build/lib/jobs/install-os.js:9:11718     _done(TypeError: Object #<EventsProtocol> has no method 'subscribeTaskNotification') at /home/jenkins/workspace/on-tasks/build/lib/jobs/install-os.js:9:12593
Stack Trace: AssertionError: expected _done to have been called exactly once, but it was called twice
    _done() at lib/jobs/install-os.js:9:11718
    _done(TypeError: Object #<EventsProtocol> has no method 'subscribeTaskNotification') at lib/jobs/install-os.js:9:12593
    at spec/lib/jobs/install-os-job-spec.js:151:39
    at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:507:31)
    at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:581:18)
    at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:697:14)
    at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
    at Async.drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)

Test Name: Install OS Job should not finish job if http response has bad http statusCode
Error Details: expected _done to not have been called
Stack Trace: AssertionError: expected _done to not have been called

Test Name: Install OS Job should not finish job if http response has no expected completionUri
Error Details: expected _done to not have been called
Stack Trace: AssertionError: expected _done to not have been called

*** BUILD #1315 ***
Test Name: Base Job Subscriptions should clean up subscriptions for every subscriber helper method
Error Details: Object #<EventsProtocol> has no method 'subscribeTaskNotification'
Stack Trace: TypeError: Object #<EventsProtocol> has no method 'subscribeTaskNotification'
    at InnerMockJob._subscribeTaskNotification (lib/jobs/base-job.js:9:10835)
    at spec/lib/jobs/base-job-spec.js:222:35
    at node_modules/lodash/index.js:3073:15
    at baseForOwn (node_modules/lodash/index.js:2046:14)
    at node_modules/lodash/index.js:3043:18
    at Function.<anonymous> (node_modules/lodash/index.js:3346:13)
    at Context.<anonymous> (spec/lib/jobs/base-job-spec.js:212:15)

Test Name: test_nodes_discovery
Error Details: timeout waiting for task discovery
-------------------- >> begin captured logging << --------------------
urllib3.connectionpool: INFO: Starting new HTTP connection (1): localhost
tests.api.v1_1.nodes_tests: INFO: Wait start time: 2016-07-28 03:37:17.417145
amqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']
amqp: DEBUG: Open OK!
kombu: INFO: Starting AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>
amqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']
amqp: DEBUG: Open OK!
kombu.mixins: INFO: Connected to amqp://guest:**@<IP_ADDRESS>:9091//
amqp: DEBUG: using channel_id: 1
amqp: DEBUG: Channel open
modules.worker: ERROR: subtask timeout after 1200 seconds, (id=discovery), stopping..
kombu: INFO: Stopping AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>
modules.worker: INFO: stopping subtask for discovery
amqp: DEBUG: Closed channel #1
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/v1_1/nodes_tests.py", line 122, in test_nodes_discovery
    message='timeout waiting for task {0}'.format(self.__task.id))
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 67, in assert_false
    raise ASSERTION_ERROR(message)
"timeout waiting for task discovery\n-------------------- >> begin captured logging << --------------------\nurllib3.connectionpool: INFO: Starting new HTTP connection (1): localhost\ntests.api.v1_1.nodes_tests: INFO: Wait start time: 2016-07-28 03:37:17.417145\namqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']\namqp: DEBUG: Open OK!\nkombu: INFO: Starting AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>\namqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']\namqp: DEBUG: Open OK!\nkombu.mixins: INFO: Connected to amqp://guest:**@<IP_ADDRESS>:9091//\namqp: DEBUG: using channel_id: 1\namqp: DEBUG: Channel open\nmodules.worker: ERROR: subtask timeout after 1200 seconds, (id=discovery), stopping..\nkombu: INFO: Stopping AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>\nmodules.worker: INFO: stopping subtask for discovery\namqp: DEBUG: Closed channel #1\n--------------------- >> end captured logging << ---------------------"

Test Name: teardown
Error Details: 'X-Auth-Token'
-------------------- >> begin captured logging << --------------------
modules.redfish_auth: INFO: auth already disabled.
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/redfish_1_0/session_service_tests.py", line 38, in teardown
    Auth.disable()
  File "/home/jenkins/workspace/on-tasks/RackHD/test/modules/redfish_auth.py", line 67, in disable
    del config.api_client.default_headers['X-Auth-Token']
"'X-Auth-Token'\n-------------------- >> begin captured logging << --------------------\nmodules.redfish_auth: INFO: auth already disabled.\n--------------------- >> end captured logging << ---------------------"

Test Name: teardown
Error Details: 'X-Auth-Token'
-------------------- >> begin captured logging << --------------------
modules.redfish_auth: INFO: auth already disabled.
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/redfish_1_0/account_service_tests.py", line 38, in teardown
    Auth.disable()
  File "/home/jenkins/workspace/on-tasks/RackHD/test/modules/redfish_auth.py", line 67, in disable
    del config.api_client.default_headers['X-Auth-Token']
"'X-Auth-Token'\n-------------------- >> begin captured logging << --------------------\nmodules.redfish_auth: INFO: auth already disabled.\n--------------------- >> end captured logging << ---------------------"

Test Name: test_nodes_discovery
Error Details: timeout waiting for task discovery
-------------------- >> begin captured logging << --------------------
tests.api.v2_0.nodes_tests: INFO: Wait start time: 2016-07-28 03:57:34.691653
amqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']
amqp: DEBUG: Open OK!
kombu: INFO: Starting AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>
amqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']
amqp: DEBUG: Open OK!
kombu.mixins: INFO: Connected to amqp://guest:**@<IP_ADDRESS>:9091//
amqp: DEBUG: using channel_id: 1
amqp: DEBUG: Channel open
modules.worker: ERROR: subtask timeout after 1200 seconds, (id=discovery), stopping..
kombu: INFO: Stopping AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>
modules.worker: INFO: stopping subtask for discovery
amqp: DEBUG: Closed channel #1
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/v2_0/nodes_tests.py", line 125, in test_nodes_discovery
    message='timeout waiting for task {0}'.format(self.__task.id))
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 67, in assert_false
    raise ASSERTION_ERROR(message)
"timeout waiting for task discovery\n-------------------- >> begin captured logging << --------------------\ntests.api.v2_0.nodes_tests: INFO: Wait start time: 2016-07-28 03:57:34.691653\namqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']\namqp: DEBUG: Open OK!\nkombu: INFO: Starting AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>\namqp: DEBUG: Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2013 GoPivotal, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'platform': u'Erlang/OTP', u'version': u'3.2.4'}, mechanisms: [u'AMQPLAIN', u'PLAIN'], locales: [u'en_US']\namqp: DEBUG: Open OK!\nkombu.mixins: INFO: Connected to amqp://guest:**@<IP_ADDRESS>:9091//\namqp: DEBUG: using channel_id: 1\namqp: DEBUG: Channel open\nmodules.worker: ERROR: subtask timeout after 1200 seconds, (id=discovery), stopping..\nkombu: INFO: Stopping AMQP worker <unbound Queue graph.finished -> <unbound Exchange on.events(topic)> -> graph.finished.*>\nmodules.worker: INFO: stopping subtask for discovery\namqp: DEBUG: Closed channel #1\n--------------------- >> end captured logging << ---------------------"

Test Name: test_tags_del
Error Details: local variable 'updated_tags' referenced before assignment
-------------------- >> begin captured logging << --------------------
tests.api.v2_0.tags_tests: INFO: Deleting tag that was created in Testing POST:/api/2.0/tags/
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-tasks/RackHD/test/tests/api/v2_0/tags_tests.py", line 116, in test_tags_del
    assert_equal([],updated_tags, message='Tags were not deleted successfully')
"local variable 'updated_tags' referenced before assignment\n-------------------- >> begin captured logging << --------------------\ntests.api.v2_0.tags_tests: INFO: Deleting tag that was created in Testing POST:/api/2.0/tags/ \n--------------------- >> end captured logging << ---------------------"

Remove WIP flag.

:+1:

:+1:

jenkins: test this please


Add tests for init command

bors r+

Codecov Report

Merging #29 into master will increase coverage by 3.62%.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           master     #29      +/-   ##
=========================================
+ Coverage    1.45%   5.07%   +3.62%
=========================================
  Files          22      22
  Lines        2614    2621       +7
  Branches     1303    1310       +7
=========================================
+ Hits           38     133      +95
+ Misses       2518    2220     -298
- Partials       58     268     +210

Impacted Files
Coverage Δ

src/commands/init.rs
26.31% <0.00%> (+26.31%)
:arrow_up:

src/commands/new.rs
0.00% <0.00%> (ø)

src/commands/open.rs
0.00% <0.00%> (ø)

src/commands/test.rs
0.00% <0.00%> (ø)

src/commands/login.rs
0.00% <0.00%> (ø)

src/commands/submit.rs
0.00% <0.00%> (ø)

src/commands/participate.rs
0.00% <0.00%> (ø)

src/commands/watch_submissions.rs
0.00% <0.00%> (ø)

src/commands/retrieve_testcases.rs
0.00% <0.00%> (ø)

src/commands/migrate_cargo_atcoder.rs
0.00% <0.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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

bors r+

bors r+


Navigation: View Experiences

@jhlink I have made the changes in all files. Could you take a look at them?

@jhlink I think I've resolved the merge conflicts. Is it good to merge now?

@anoura12 I'll take a look later today!

PR is good. Merging.


JSON templates lookup fails except when building

What version of Hugo are you using (hugo version)?

$ hugo version
Hugo Static Site Generator v0.73.0/extended linux/amd64 BuildDate: unknown

I have two sections, Projects and Universities, where I want Hugo to generate JSON and HTML outputs. The JSON for Universities works perfectly, but the JSON file for Projects is using the template for University.
I made a post about it here: https://discourse.gohugo.io/t/json-output-uses-the-wrong-template/27284
Upon further investigation, the lookup order works when running yarn build but not when running watch or preview.
 Looking at your project, you have a list.json.json and then in the other section a list.json... Without discussing the sensibility of it all, it looks to me like list.outputFormat.mediaType is more specific than the other even if it's in a different section.

Even if I name all the files to list.json.json, yarn start does not build my projects index.json properly. yarn build does. Why does it not work consistently?


feat: add options param to query#runStream

[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

@AVaksman could you please explain the motivation of this PR and more about the changes?

@AVaksman could you please explain the motivation of this PR and more about the changes?

Sure
query.runStream() delegates to request.runQueryStream() and typescript users don't have an ability to pass options
export interface RunQueryOptions {
  consistency?: 'strong' | 'eventual';
  gaxOptions?: CallOptions;
  wrapNumbers?: boolean | IntegerTypeCastOptions;
}

in particular the wrapNumbers value, leaving the user no way to handle out of bounds integers.

Ah, gothca. Thanks! I just had a small change request, but LGTM.


Automatically maintain collapsed range code indentation if line is moved

If I push a collapsed range line using tab, the collapsed lines do not move along it. I would like it to maintain the indentation itself.

You have to select the collapsed line up to the next line.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


real_idx

Surelog issue: https://github.com/chipsalliance/Surelog/issues/2325

New surelog issue: https://github.com/chipsalliance/Surelog/issues/2553

I don't see this issue (locally) anymore, lets wait for sv-tests to update yosys-uhdm-plugin-integration repository to confirm it is also working in CI.

Issue fixed: https://chipsalliance.github.io/sv-tests-results/?v=uhdmverilator+6.12+real_idx


[#6019] Remove redundant project dependencies from AI Recognizers

Fixes # 6019

Note: The same dependency structure was corroborated for JavaScript and Python. Only JavaScript has the similar case as DotNet, whereas Python doesn't.

Description
This PR removes redundant dependencies for Dialogs.Adaptive, AI.Orchestrator and AI.QnA.
Specific Changes

Dialogs.Adaptive

Removed AdaptiveExpressions dependency reference from <ProjectReference/> and <PackageReference/>.

AI.Orchestrator

Removed Microsoft.Bot.Builder.Dialogs dependency reference from <ProjectReference/>.

AI.QnA

Removed AdaptiveExpressions and Microsoft.Bot.Builder dependencies' references from <ProjectReference/> and <PackageReference/>.

Testing
The following image shows the CI pipeline running successfully after the changes.

Promoted https://github.com/microsoft/botbuilder-dotnet/pull/6067