Possible CSS issue, the layout does not match one on the tutorial

I've followed the setup procedure for manually using bootstrap datepicker 3 and it has worked but the layout looks worse than the one on the tutorial, the calendar css looks not to have work and it looks to be pixelated. It's not possible to upload an image so I've added one to my public stream so any developer can have a preview and advice https://plus.google.com/+SamuelMuiruri/posts/EwFXg4cqhxz

you have missing css or it's being overridden

I looked at the code I hadn't included the datetimepicket css


ARROW-15901: [C++] Support custom output field names in Substrait

See https://issues.apache.org/jira/browse/ARROW-15901 . Tests will be added after agreement on the approach is reached.

Not sure what to do about the unsuccessful checks; they don't seem to be related to the change. What is the next step?

Sorry for not noticing this originally.  Feel free to ping someone in the future after a few days.
As for the PR, I think this is part of the solution but I think we also want to handle the case where the last node in the declaration is not a project node.  And we will want to have a plan in place for round-trip.  A simple solution would be to just add a project node onto the end (if one is not there already) but that would mean our plan wouldn't round-trip cleanly.
Another approach could be to add a vector of names to ConsumingSinkNodeOptions.  The sink node could then take the output schema from its input, swap out the names, and pass that on to the consumer.  This should round-trip nicely.
Thoughts?

As for the PR, I think this is part of the solution but I think we also want to handle the case where the last node in the declaration is not a project node. And we will want to have a plan in place for round-trip. A simple solution would be to just add a project node onto the end (if one is not there already) but that would mean our plan wouldn't round-trip cleanly.

Agreed, this would not round-trip cleanly. While this could be fixed by creating a special projection-node, which could be removed when going back the round-trip, that seems even less elegant.

Another approach could be to add a vector of names to ConsumingSinkNodeOptions. The sink node could then take the output schema from its input, swap out the names, and pass that on to the consumer. This should round-trip nicely.

Yes, sounds like this should work and round-trip nicely. I'll look into implementing it. One thing to keep in mind here is that in the future we may want to use other sink nodes (e.g., "write" rather than "consuming_sink") in Substrait, so I think it makes sense to factor out the names into a reusable options class (to be included as a member in ConsumingsinkNodeOptions) and the schema-renaming operation for it into a reusable function.

Another approach could be to add a vector of names to ConsumingSinkNodeOptions. The sink node could then take the output schema from its input, swap out the names, and pass that on to the consumer. This should round-trip nicely.

@westonpace, I looked into it a bit and it appears to run into an issue - the schema is not available to ConsumingSinkNode. Instead, ConsumingSinkNode passes a (schema-less) ExecBatch to a SinkNodeConsumer; it is SinkNodeConsumer which is expected to already have been initialized with a schema, like in TableSinkNodeConsumer, and use it to obtain a RecordBatch. Perhaps a reasonable solution would be to extend ConsumerFactory to accept a names parameter? Despite this being a backwards-incompatible change, presumably the Arrow-Substrait code is still in flex so this would be OK.

The Arrow-Substrait code is definitely in flex.  Nothing has been released externally via any binidings so I wouldn't worry about any backwards incompatible changes.
That being said, I think SinkNodeConsumer has an Init method which receives a schema.  This is called by ConsumingSinkNode in ConsumingSinkNode::StartProducing.  At that point (StartProducing) the ConsumingSinkNode should have access to the schema (it's the output schema of the node's single input).
Instead of passing that schema directly it should modify the schema with the names that it gets from its options.  So the act of assigning names to an existing schema would happen in ConsumingSinkNode::StartProducing.

You're right, I needed to rebase to pick up this Init function. I'll commit shortly.

This is just a dummy comment to move this into the "reviewed" state. Please click re-request review when you're ready for me to take another look.

Hmm, I don't see such a button. You can review. For some reason, the code in my last couple of commits builds OK in my environment but failed in the checks, so I committed a fix that hopefully would resolve this.

I don't think the rebase went through correctly (right now GH is showing ~1200 files changed) so I can't review at the moment.  The re-request review button should be way up in the top-right corner.

To keep things clean, I'm replacing this PR with https://github.com/apache/arrow/pull/13069 .


Gridcoin Finance still shows up in "list projects" and "list explainmagnitude".

When doing a list projects, Gridcoin Finance still shows up even though it's no longer in the NN:
"Project" : "gridcoin finance",
Gridcoin Finance also shows up when doing a list explainmanitude:
"4" : "0c130640a79aab9f1eaed36277bc51fc,gridcoin finance,26500,222666.67,1320,441.35,38012.5,450.98,",
Not sure if this would affect the amount each project receives to pay out.

Strange.. I'll send this issue to RTMoney for further investigation.

I blacklisted it yesterday, it should be gone now.


2-stage translation with Ssnpm

In section 3.5, the spec says
When running with virtualization in VS/VU mode with vsatp.MODE = Bare, this means that those two bits may be subject to pointer masking, depending on hgatp.MODE and senvcfg.PMM.

Should this not say "either henvcfg.PMM (for VS) or senvcfg.PMM (for VU)"?

Yes, that's correct – I will add clarification to the text. I will leave this issue open until then.

This should be addressed as of 567bbd0.


Support for writing DTLS 1.3 unified header

Moving suggested changes here: https://github.com/fwh-dc/oqs-openssl/pull/3


Use Swagger to generate rest docs

Resulting documentation example is attached. We can change the styling to other handlebars templates. Currently only the job master is annotated, but eventually the maven build will generate a rest doc for each of our modules which have rest apis.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3641/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3662/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3666/
Test PASSed.

related to this PR, we currently hardcode the following rest doc endpoints in the sidebar HTML:
                        Master REST API
                        Worker REST API
                        Proxy REST API

but i noticed here you generated the rest endpoints for job. @ZacBlanco we may have to make the set of rest doc links configurable per version :/

All I have to say to that is UGH. We'll definitely need to add a bit of logic for the docs to make sure that job/ endpoints are only displayed on the proper versions

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3712/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3713/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3714/
Test PASSed.

I'm okay leaving the strapdown dependency for now. If we ever want to update the docs in the future, it shouldn't be terribly hard to replace.

alluxio-bot, merge this please


updating for encrypted websockets and system user service

Great job on the socketChat... I reviewed alot of them, and you had one of the top performers. I read on form somewhere you were looking to get encryption working. So figured I'd see what I can do. I added ability for TLS, as well as a systemd service install. Hopefully you find the install.sh useful too... merge or denied, hopefully all around the code to get you started is helpful.
The code should allow for simple http/https operation simply presence or absence of certs.

Hey @joshebosh, it seems that I missed your PR for some reason so I apologize. From what I understood, you're creating a user on the server and creating a system service that handles encryption using self-specified certificates. What advantage does this have over client-side encryption?
Also, is there a reason this script is Debian-specific? I would imagine it would work in any UNIX based environment.
Anyway, this is awesome work. Thank you for your contribution!

By the way, I'm going to test your script and play around with it before merging just so I can get a better understanding of how everything works 😄


Location filterform uses non-unique field name

Environment

Nautobot version (Docker tag too if applicable): 2.0.0-beta.2
Python version: 3.10
Database platform, version: psql
Middleware(s):

Steps to Reproduce

Create locations with duplicate names: Region1->Site1, Region2->Site1 (Two "sites" with the same name but different regions)
Create a device in R1->S1 and another device in R2->S1
Navigate to Device ListView
Filter based on location named Site1

Expected Behavior
I expected to be able to filter devices belonging to a particular location named Site1

Observed Behavior
I saw all devices belonging to any location named Site1
This is probably an issue beyond the Device ListView, that is just where I observed the behavior. Filters should use a to_field_name that is unique, but it appears that location filters are using name which is not unique.

From Slack, looks like an oversight in https://github.com/nautobot/nautobot/issues/2662
Fixing:

https://github.com/nautobot/nautobot/blob/next/nautobot/dcim/form_mixins.py#L60-L65
https://github.com/nautobot/nautobot/blob/next/nautobot/dcim/filters/mixins.py#L67-L71

should do the trick?

Additional unexpected behavior transforms filtering of parent locations into the parent name and the name of all descendants in the tree (as opposed to the actual descendants in the tree). For example, having the following Location Tree:
Region 1
  Site 1
Region 2
  Site 1
  Site 2

and using the filter {"location": ["Region 2"]}
Would result in location__name__in=["Region 2", "Site 1", "Site 2"]
I would expect this to be location__in=[<LocationRegion1>,<LocationSite1>,<LocationSite2>]

Related: #2875

Likely the change we will make for both #4207 and #4279 is to change the UI behavior so that all NaturalKeyOrPKMultipleChoiceFilter in the UI switch their behavior to preferring the pk over the name when making a selection and updating the URL query params.


wrong Terraform provider version

Purpose
the version of the terraform provider was wrong, leading to errors while trying to pull from the registry
Pull Request Type
What kind of change does this Pull Request introduce?
[x] Bugfix
[ ] Feature
[ ] Documentation content changes
[ ] Other... Please describe:

@rui1610 you´re welcome! I also saw your changes regarding the version in the development section, but the PR was already created 😄


set_active_gateway is not concurrency safe

https://github.com/fedimint/fedimint/blob/11339763400401b5394e726b05bf6decc031283e/modules/fedimint-ln-client/src/lib.rs#L866-L888
if called concurrently, second one would panic on database commit

cc @dpc

The only reason I'm on the git blame there is because I shuffled this code around.
Though I recognize this code and was already SMH looking at it before. Smells like globals to me, so I don't like it.
The immediate solution would be to wrap it into autocommit.
But possibly the whole thing could be scrapped and the caller could do it's job and track and pass the gateway it wants to use or something? Again - I'm not sure, I don't know that code very well.

Yeah I don't think this code was ever designed with concurrency in mind. Long term I'd like to remove the concept of "active" gateway altogether and replace it with something smarter (like policies based on fees or reliability).
Even wrapping in an autocommit is a bit weird, it essentially means that the first call to set_active_gateway is overwritten, which might not be expected. commit_tx here should probably be propagated up so that the caller can properly handle it.

Seems today we only use this api in test cases where we to pre-activate a specific gateway before asserting some behavior

On master we can already optionally specify the gateway for a payment, this should become the standard way of doing it, getting rid of the active gateway concept. Otherwise it's also impossible to show users a reliable fee preview for outgoing payments since the active GW may change in the meantime.

Some discussion about "active gateway" here https://github.com/fedimint/fedimint/issues/3844


Dataset recipes

With #151, FastAI.jl is getting high-level interfaces for searching datasets (finddatasets) and loading datasets into task-specific data containers (loaddataset). There is also a new DatasetRecipe that encapsulates configuration for loading a data container and the block information from a path. These recipes can be registered with a dataset so that they can be found using the above high-level functions.
The fastai dataset colletion comes with quite a lot of datasets, so only a few have recipes yet. This issue tracks the progress on adding recipes to all the datasets. Contributions of recipe types and recipe configs for datasets are welcome.
See src/datasets/recipes.jl for example recipe implementations and src/datasets/fastairegistry for how recipes are registered. listdatasources() gives you a list of all dataset sources and datasetpath(name) downloads them and returns the download folder.
Progress
For datasets that can be used for multiple tasks, they are listed below. Otherwise a checked dataset that at least one recipe is already implemented.

[x] CUB_200_2011
[ ] bedroom (not sure how the folders are layed out)
[x] caltech_101
[x] cifar10
[x] cifar100
[ ] food-101
[x] imagenette-160
[x] imagenette-320
[x] imagenette
[x] imagenette2-160
[x] imagenette2-320
[x] imagenette2
[x] imagewang-160
[x] imagewang-320
[x] imagewang
[x] imagewoof-160
[x] imagewoof-320
[x] imagewoof
[x] imagewoof2-160
[x] imagewoof2-320
[x] imagewoof2
[x] mnist_png
[x] mnist_var_size_tiny
[ ] oxford-102-flowers
[ ] oxford-iiit-pet
[ ] stanford-cars
[ ] ag_news_csv
[ ] amazon_review_full_csv
[ ] amazon_review_polarity_csv
[ ] dbpedia_csv
[ ] giga-fren
[ ] imdb
[ ] sogou_news_csv
[ ] wikitext-103
[ ] wikitext-2
[ ] yahoo_answers_csv
[ ] yelp_review_full_csv
[ ] yelp_review_polarity_csv
[ ] biwi_head_pose
[x] camvid
[ ] pascal-voc
[ ] pascal_2007

[x] multi-label image classification ((Image{2}, LabelMulti))
[ ] object detection

[ ] pascal_2012
[ ] siim_small
[ ] skin-lesion
[ ] tcga-small
[x] adult_sample
[ ] biwi_sample
[x] camvid_tiny
[ ] dogscats
[ ] human_numbers
[ ] imdb_sample
[x] mnist_sample
[x] mnist_tiny
[ ] movie_lens_sample
[ ] planet_sample
[ ] planet_tiny
[ ] coco_sample
[ ] coco-train2017
[ ] coco-val2017
[ ] coco-test2017
[ ] coco-unlabeled2017
[ ] coco-image_info_test2017
[ ] coco-image_info_unlabeled2017
[ ] coco-annotations_trainval2017
[ ] coco-stuff_annotations_trainval2017
[ ] coco-panoptic_annotations_trainval2017

Do you think we can pull some or all of this into MLDatasets.jl? Obviously some parts like the block API won't be applicable, but it would be nice to expose the registry functionality, for example.

It might be worth also looking at DataSets.jl announced at JuliaCon.

Do you think we can pull some or all of this into MLDatasets.jl? Obviously some parts like the block API won't be applicable, but it would be nice to expose the registry functionality, for example.

At some point, all the dataset functionality should me merged down to MLDatasets.jl and MLDataPattern.jl.
The registry itself is pretty barebones; if you take away the functionality related to blocks, then you could replace it with a Dict{String, Vector{DatasetRecipe}} that maps a list of recipes to a dataset.

At some point we'll have to think about iterable datasets and at that point some rearchitecting DataSets.jl could be useful. It should also not be too hard to add iterable support to DataLoaders.jl.
For now I want to provide a useful core of offline datasets here in FastAI.jl with this simple approach. Rearchitecting should probably flow into the efforts in MLDatasets.jl (or perhaps a DLDatasets.jl if everything will be deprecated anyway?). I'll give a larger reply in https://github.com/JuliaML/MLDatasets.jl/issues/73 later

Hey, I'd like to work on this issue. Since this issue is labeled good first issue I believe I can help. Can you please specify to me what has to be done still cause I see the list above hasn't been updated?

Hey! The list above is uptodate. The easiest thing to get started with should be adding recipes for the csv datasets and registering some TableDatasetRecipes.

Next I want to add recipes for dbpedia_csv, ag_news_csv. They all are in CSV format. But the labels were in separate files and the indexes of these labels are used in the actual CSV files. In that case, I think it is better to replace the label indices with the actual labels in the recipe code itself and then wrap it with TableClassificationRecipe? Are there any ideas to do this?

Might need a new recipe type that wraps TableRecipe, but can't say without looking at the folder structure

fastai-dbpedia_csv/
└── dbpedia_csv
     ├── classes.txt
     ├── readme.txt
     ├── test.csv
     └── train.csv
This is the folder structure for both datasets (dbpedia_csv, ag_news_csv).

Might need a new recipe type that wraps TableRecipe, but can't say without looking at the folder structure

Is it necessary to make a new recipe for datasets that have folder structures similar to the one above? Or is it possible to tweak the existing ones to get the job done?

I think in this case it may be possible to create a new recipe that wraps TableRecipe (which loads the table) and then reads in the labels and converts label indices to label strings. I don't have the bandwidth to look into this in more detail currently, though.

I think in this case it may be possible to create a new recipe that wraps TableRecipe (which loads the table) and then reads in the labels and converts label indices to label strings.

I'll work on this.

After the community meet, I explored fastAI, MLutils and couple of other libraries and tried to understand the codebase specifically . Would love to get started with adding a dataset , can you please specify which one of the above would be a good one to get started into , also I believe the list above isnt updated

The CSV files of dbpedia_csv and ag_news_csv have no headers. The current implementation of loadrecipe for TableDatasetRecipe in Tabular/recipes.jl ignores this and is causing trouble in implementing recipes for both mentioned datasets.  Is there any workaround?
The point is, I want to apply for GSOC for FastAI on implementing textual models. I hope that this addition of dataset recipes will increase the chance of my application getting accepted (As discussed in the previous community call).


ES Module build

This adds an ES module build into dist/preact.esm.js as described here. Closes #670

Coverage remained the same at 100.0% when pulling 9d14988bc18a5da8605108bdba10140cfdae19a0 on matthewp:es1 into c4f3fb0e4c18bd502b9084a11149749fa6a08c9b on developit:master.

😍😍

Hoping to be able to merge this and get a release out in the next couple of days. Sorry for the delay, life stuff taking priority for a little bit!  Anyone else able to review is much appreciated.

No worries, thanks!

Coverage remained the same at 100.0% when pulling 1ffd3b791b28ba77b94e582a71c0dc8eb2769eae on matthewp:es1 into c4f3fb0e4c18bd502b9084a11149749fa6a08c9b on developit:master.

I was just about to PR this myself -- looking forward to it!

Me too! I should have time to get this merged after Google I/O.

Would this need also a module entry in package.json to allow it to be detected by bundlers?
https://github.com/rollup/rollup/wiki/pkg.module

indeed!

Coverage remained the same at 100.0% when pulling 6ca5a7e1807d94854949df3c13abff1bb48e9200 on matthewp:es1 into b80bec35354273187b0bc998c1c870da00bf212b on developit:master.

What should "module" point to? I'll update the PR with that if it will help move this along. Anything else needed?

What should "module" point to?

dist/preact.esm.js I believe

Added the field.

Coverage remained the same at 100.0% when pulling d3407b89144a54848a60a2d086c9def1225992c1 on matthewp:es1 into b80bec35354273187b0bc998c1c870da00bf212b on developit:master.

+1, would love to have this. I have some tooling in my build pipeline that needs the "module" field.
While it's no longer required in Node's proposed ESM support plan, it's still the current standard for denoting an ESM entrypoint.

I really am hoping to get this into 8.2, sorry for the horrible delay everyone :(

so... finally merged!

Yay!


Create rchain coop flyer template

Please make the issue SMART: Specific, Measurable, Achievable, Realistic, Timely.
Measure of Completion:
Suggested Budget:
See CONTRIBUTING.md for details on budget and reward process.

i thought i would shake the tree assuming there had to already be one of these? if not, do we have a location with all of the design requirements, colors, etc?

Something like this (and I apologize if I missed this info somewhere else) https://www.ethereum.org/brand

ah ha! here is the info in case anyone comes across this and is looking. i think what is in there is good enough to move on. https://github.com/rchain/Members/tree/master/style_guide_assets
am closing this out.


Add custom index.html file for balancer example

This is great.  I think it would be great if you had a custom index.html used which would provide the IP# of the backend webserver it loads.  This way it can visually show which of the backend webserver it loaded.
I noticed in one of your other examples you did something like this; but doing it for this example would be the best.
Didn't realize this wouldn't display for the deployments-balancer folder specifically

Sounds reasonable! Thanks for the suggestion.

Looking back on this; for this particular example I have the user using curl -Is http://<IP_ADDRESS>/ and checking the cookie value to see which app server is serving the request. Since this example is early in the book and meant to mostly show how to drop a server out of the rotation—and since later examples do (as you mention) have more advanced 'app' functionality that displays the IP—I'm going to leave the example as is for now.


add debug calls?

would it make sense to sprinkle the code with debug calls? personally, i would find this helpful for debugging.

This is a good idea. The needle library uses the debug package for a similar purpose.
https://www.npmjs.com/package/debug
I've used the DEBUG=needle flag before to get more dump the request/responses to the console but it doesn't include everything.
Do we want to follow that approach?

yes. i think the main missing pieces from needle are the body of the request and of the response. needle also includes too much information generally (though sometimes the extra info helps). finally, if a program is using needle for more than one purpose, having the ability to log just our requests is helpful.
e.g. too much info, and yet too little:
  needle Got response 200 { 'x-backside-transport': 'OK OK',
  connection: 'close',
  'transfer-encoding': 'chunked',
  server: 'nginx',
  date: 'Tue, 26 Jun 2018 11:53:38 GMT',
  'content-type': 'application/json',
  'x-request-id': '...',
  'access-control-allow-origin': '*',
  'access-control-allow-headers': 'Authorization, Content-Type',
  ibm_cloud_functions: 'OpenWhisk',
  'x-global-transaction-id': '...',
  'set-cookie':
   [ 'DPJSESSIONID=PBC5YS:...; Path=/; Domain=.openwhisk.ng.bluemix.net; Secure; HttpOnly' ] }

LGTM, do you want to open a PR around this?

yes, i'll try to get something in the next few days


Fix typos

There are so many typos.
This PR fixes that.

Thank you. Big problem here is that we get no grammar correction on .jade files :/

Well Done Sir!  Thank you much. Gratefully accepted.


Rework the enter verification code step

Trello card
Trello-2902
Context
This step doesn't perform all that well and we see roughly 1/5 users drop off/don't successfully enter their verification code and progress to the next step.
In an effort to tackle this we are making the copy clearer/reworking the layout of the step (this will bring it inline with the GiT website transactions).
Changes proposed in this pull request

Rework the enter verification code step

Guidance to review
The Cypress tests will need to be updated when this is shipped.

Looks good to me
@SaimaBodiat Do you want to have a quick look at this given that you oversaw the same change to our other funnels?

looks good to me


Problem of integration krakend with keycloak

Hello. I have keycloak bitnami chart and krakend deployed in in k8s.  Also I have a test api, and I want being authenticated before access it.  I'm able to get valid jwt token from keycloak, but when  I'm trying to access my api  through krakend, it returns 401 error
Any help is really appreciated.
Software versions:
keycloak: 16.1.1
crakend: 2.0.4
my config file:
{
  "$schema": "https://www.krakend.io/schema/v3.json",
  "version": 3,
  "timeout": "3000ms",
  "cache_ttl": "300s",
  "output_encoding": "json",
  "port": 8080,
  "endpoints": [
      {
          "endpoint": "/mock/parents/{id}",
          "method": "GET",
          "input_headers": [
             "Authorization"
           ],
          "extra_config": {
              "auth/validator": {
                  "alg": "RS256",
                  "jwk-url": "http://keycloak-headless:8080/auth/realms/master/protocol/openid-connect/certs",
                  "disable_jwk_security": true,
                  "roles_key_is_nested": true,
                  "roles_key": "realm_access.roles",
                  "roles": ["test-app-parent"],
                  "operation_debug": true
              }
          },
          "output_encoding": "json",
          "concurrent_calls": 1,
          "backend": [
              {
                  "url_pattern": "/parents/{id}",
                  "encoding": "json",
                  "sd": "static",
                  "extra_config": {},
                  "host": [
                    "http://testapp-service:8400"
                  ],
                  "disable_host_sanitize": false,
                  "blacklist": [
                      "super_secret_field"
                  ]
              },
              {
                  "url_pattern": "/siblings/{id}",
                  "encoding": "json",
                  "sd": "static",
                  "extra_config": {},
                  "host": [
                      "http://testapp-service:8400"
                  ],
                  "blacklist": [
                      "sibling_id"
                  ],
                  "group": "extra_info",
                  "disable_host_sanitize": false
              },
              {
                  "url_pattern": "/parents/{id}/children",
                  "encoding": "json",
                  "sd": "static",
                  "extra_config": {},
                  "host": [
                      "http://testapp-service:8400"
                  ],
                  "disable_host_sanitize": false,
                  "mapping": {
                      "content": "cars"
                  },
                  "whitelist": [
                      "content"
                  ]
              }
          ]
      },
      {
          "endpoint": "/mock/bogus-new-api/{path}",
          "method": "GET",
          "extra_config": {
              "auth/validator": {
                  "alg": "RS256",
                  "jwk-url": "http://keycloak-headless:8080/auth/realms/master/protocol/openid-connect/certs",
                  "disable_jwk_security": true
              },
              "github.com/devopsfaith/krakend/proxy": {
                  "static": {
                      "data": {
                          "new_field_a": 123,
                          "new_field_b": [
                              "arr1",
                              "arr2"
                          ],
                          "new_field_c": {
                              "obj": "obj1"
                          }
                      },
                      "strategy": "always"
                  }
              }
          },
          "output_encoding": "json",
          "concurrent_calls": 1,
          "backend": [
              {
                  "url_pattern": "/not-finished-yet",
                  "encoding": "json",
                  "sd": "static",
                  "extra_config": {},
                  "host": [
                      "nothing-here"
                  ],
                  "disable_host_sanitize": false
              }
          ]
      }
  ]
 }  ```

Commands, I'm using to start  krakend:
kubectl apply -f krakend.yml

There are following logs:
KRAKEND ERROR: [ENDPOINT: /mock/parents/:id][JWTValidator] Unable to validate the token: Get "": unsupported protocol scheme ""
[GIN] 2022/05/12 - 11:15:07 | 401 |     368.798µs |       <IP_ADDRESS> | GET      "/mock/parents/8f01e84c-6bdf-4cc0-bf5f-566698d30277"

Hi @ugene77 ,
It looks like you have migrated from a KrakenD 1.x to a KrakenD 2.0 but you have not replaced jwk-url by jwk_url. You also have blacklist which is not currently allowed (use deny) instead.
You can find problems like this in the future by running krakend check -dtc krakend.json --lint


Adds Support of Spring MVC Framework

Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

Hey @head-thrash, thanks for your patience -- I'm going to try to review this in the next few days, my schedule has been pretty hectic recently.

So, first, this looks really solid. The main priority for me is to maintain maintainability, and having tests is really solid.

It would be good to have a few more round-trip tests exercising stuff like empty lists, mixed valid and invalid parameters for lists, application/x-www-form-urlencoded, multipart/form-data, at the very least.

Running the existing tests yields some unexpected discrepancy:

2020-02-02 23:11:30.741  WARN 78782 --- [g-BaselineSpecs] .w.s.m.s.DefaultHandlerExceptionResolver : Resolved [org.springframework.web.bind.MissingServletRequestParameterException: Required List parameter 'status' is not present]

I'd expect that to be a 4xx error, but it seems as though your NoContent was returned successfully.

Again, for the DateTimeSpecs, it seems as though there is a lot of debug output:

MockHttpServletRequest:
      HTTP Method = POST
      Request URI = /foo
       Parameters = {long=[1]}
          Headers = [Content-Type:"application/json;charset=UTF-8"]
             Body = 42
    Session Attrs = {}

Handler:
             Type = alias.server.springMvc.foo.FooResource
           Method = alias.server.springMvc.foo.FooResource#doFoo(Optional, Optional)

Async:
    Async started = false
     Async result = null

Resolved Exception:
             Type = null

ModelAndView:
        View name = null
             View = null
            Model = null

FlashMap:
       Attributes = null

MockHttpServletResponse:
           Status = 201
    Error message = null
          Headers = [Content-Type:"application/json"]
     Content type = application/json
             Body = 42
    Forwarded URL = null
   Redirected URL = null
          Cookies = []

MockHttpServletRequest:
      HTTP Method = GET
      Request URI = /foo
       Parameters = {dateTime=[2020-02-02T23:11:30.430-08:00], optionalDateTime=[2020-02-02T23:11:30.430-08:00], date=[2020-02-02], optionalDate=[2020-02-02]}
          Headers = [Content-Type:"application/json;charset=UTF-8"]
             Body = null
    Session Attrs = {}

Handler:
             Type = dateTime.server.springMvc.dateTime.DateTimeResource
           Method = dateTime.server.springMvc.dateTime.DateTimeResource#getSomething(OffsetDateTime, Optional, LocalDate, Optional)

Async:
    Async started = false
     Async result = null

Resolved Exception:
             Type = null

ModelAndView:
        View name = null
             View = null
            Model = null

FlashMap:
       Attributes = null

MockHttpServletResponse:
           Status = 204
    Error message = null
          Headers = []
     Content type = null
             Body =
    Forwarded URL = null
   Redirected URL = null
          Cookies = []

It would be good to reduce some of this noise.

My apologies for this taking so long to actually review. The code looked fine, but I was unfamiliar with Spring Boot and Spring MVC, so I wanted to try it out before giving the final OK on it.
https://github.com/blast-hardcheese/guardrail-spring-mvc-playground/ was all that was required in the end, but actually carving out the time turned out to be the hard part.
Thanks for your effort and patience, @head-thrash.


Error when parsing watch.html, maybe YouTube made a change

Describe the bug
Error when parsing watch.html, maybe YouTube made a change.
Please report this issue with the "1693081603912-watch.html" file on https://github.com/distubejs/ytdl-core/issues.
Debug File
1693081603912-watch.html
Environment

@distube/ytdl-core version: 4.11.17
Node.js version: 18.6.0
Operating system: Ubuntu 22.04.2 LTS

Found it was something to do with sending a cookie as part of the request headers as removing this seems to fix it.


Cannot update the name of a vm

If I execute the below code it throws an error (latest netbox 2.9.4) . I think this worked in 2.8
netbox = pynetbox.api(url, token=api)
nb_vm  = netbox.virtualization.virtual_machines.get(name="test")
nb_vm.name = "test2"
try:
  nb_vm.save()
except pynetbox.RequestError as e:
  print(e.error)

output:
{"detail":"Method "PATCH" not allowed."}

did an update issue resolved


Add language switcher

Have a look at the dev branch which adds support for i18n.

Would be super useful to have one ! :+1:

As hugo-agency-theme is mostly in maintenance mode and no new features will be added.
We created Syna as a more flexible iteration of this theme.
Syna is working on multi language support tracked in issue https://github.com/okkur/syna/issues/14.


Client Not Stopping

When the client is not the last user and the client leaves, the communicator stop and screen share dispose is not called. Thus both are running even though the window is closed.
@bruise-88 @ragedjavelin kindly fix this issue.

#142


Scrolling beyond viewport in Firefox

Issue Summary
Potentially related to #8664, when scrolling in Firefox (all extensions disabled) on the page editor, when you reach the bottom of the page, if you keep scrolling the viewport keeps getting bigger, letting you scroll forever. If you scroll back up, the height is reset correctly.

Steps to Reproduce

Be in Firefox
Edit a page
Scroll down to the bottom, and then keep scrolling. Most noticeable when using an un-ratcheted scroll wheel.

Technical details

Python version: N/A
Django version: N/A.
Wagtail version: Confirmed on 4.1, 4.2 and 5.0.
Browser version: Firefox 114 / 115 on Linux.

I'd say this is a duplicate of https://github.com/wagtail/wagtail/issues/8664

Yeah I agree, the screenshot in the issue is from pre-4.0 but I think it's the same problem discussed further there. Closing as duplicate.


Incorrect traceback lineno

When I use kola runner on Linux, the traceback lineno fails to initialize during Lexer creating.
In Linux
$kola: #version
0.1.0b4
$kola: #err
Traceback (most recent call last):
...
File "", line 2, in
kola.exception.KoiLangCommandError: [2] command 'err' not found
While in Windows, all lineno in  frame here should be 1.

The problem has been fixed in 0.1.0b5


(AzureCXP) fixes MicrosoftDocs/azure-docs#59903

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


[QHC-833] Improving/Feedback for Transpilation

TODOs for this PR:

[x] Put optimize flag, for actual optional optimizations (& Improve optimize word use in methods names)
[x] Make Transpilation/compile only for single circuits (unify code standard across qililab)
[x] Make Transpilation efficient, by not constructing the Circuit class so many times, between methods
[x] Pass a transpilation kwargs instead of so many args in platform/qililab's execute(...)
[x] Cover/change test for all of this.

You will see two empty methods, in this next PR I will fill them:
bunch_drag_gates(...), delete_gates_with_no_amplitude(...)

The documentation after this PR looks like:


Fixing Minion SegmentGenerationAndPush task to support any PinotFS override

Description
Current issue:
When using the Pinot Minion SegmentGenerationAndPush task, Minions always tries to use the existing PinotFS created by Minion servers. This means if the minion server created an S3 PinotFS for its own usage, no other minion tasks can create a new S3PinotFS with their own AWS S3 credentials.
After the change:
Always create temporary PinotFS based on the input and output PinotFS configs for Minion task: SegmentGenerationAndPush.
If no input/output fs configs, then fallback to default PinotFS
Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)

[ ] Yes (Please label as backward-incompat, and complete the section below on Release Notes)

Does this PR fix a zero-downtime upgrade introduced earlier?

[ ] Yes (Please label this as backward-incompat, and complete the section below on Release Notes)

Does this PR otherwise need attention when creating release notes? Things to consider:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

[ ] Yes (Please label this PR as release-notes and complete the section on Release Notes)

Release Notes
If you have tagged this as either backward-incompat or release-notes,
you MUST add text here that you would like to see appear in release notes of the
next release.
If you have a series of commits adding or enabling a feature, then
add this section only in final commit that marks the feature completed.
Refer to earlier release notes to see examples of text
Documentation
If you have introduced a new feature or configuration, please add it to the documentation as well.
See https://docs.pinot.apache.org/developers/developers-and-contributors/update-document

Codecov Report

Merging #6744 (8cc731e) into master (98faf2b) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

:exclamation: Current head 8cc731e differs from pull request most recent head 8377385. Consider uploading reports for the commit 8377385 to get more accurate results

@@             Coverage Diff              @@
##             master    #6744      +/-   ##
============================================
- Coverage     73.75%   73.75%   -0.01%
  Complexity       12       12
============================================
  Files          1407     1407
  Lines         68455    68459       +4
  Branches       9896     9896
============================================
  Hits          50489    50489
+ Misses        14681    14674       -7
- Partials       3285     3296      +11

Flag
Coverage Δ
Complexity Δ

integration
42.91% <0.00%> (-0.07%)
0.00 <0.00> (ø)

unittests
66.04% <0.00%> (-0.02%)
0.00 <0.00> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


pull request for e2e test at 01/15/2017 23:56:13

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Scan retries for blobs that no longer exist

Description of the bug
If an end user uploads a data elements and triggers a file scan, but deleted the file before the scan is completed, the dataElement will be retried 5 times without luck.
Should be able to identify that blob no longer exists and stop execution.
A bit of an edge case, but it can happen and result in an unnecessary loard on the system. Should be handled when time allows.
Steps To Reproduce

Disable filescan function
Upload file to an app with filescan enabled
Delete file
Enable filescan function
See error i filescan function logs

Additional Information
No response

Not prioritized as it doesn't happen often enough to be a serious issue.


377 version param

Feature or Bugfix

Feature

Detail
version.json in repo root contains information about version. This json-string is uploaded to SSM parameter /dataall/{env}/versin. Also this file is copied to frontend folder and version number is displayed near "dataall" header
Relates
-
Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)? NA

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization? NA

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features? NA

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users?NA

Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

As long, as @dlpzx required simple way to store version info, I made it as obvious as possible.
Version info is updated only in one file - version.json
We will both have ssm-param for that and static file in the front.
What can be different?
We can introduce another API route (smth like /metadata) to fetch version from backend and display at the frontend.
In this case it will be 100% the same at front and back, but maybe in future we want to have different versions for front and back? Also, I decided not to make another API section just for one version-param.

Left a minor comment - otherwise code looks good and a very much needed enhancement 🙌
To finish up testing and push through by Monday:
Deployed to AWS (Internet Facing)

[ ] CICD Successful
[ ] Version present in login logo + webpage

Deployed to AWS (VPC Facing)

[ ] CICD Successful
[ ] Version present in login logo + webpage

Deployed Local

[ ] Logo present in webpage

Now version is tooltip


Properly scale canvas on higher resolution displays

Fixes the issue where canvas was way too large on higher resolution displays.

Looks good.


Can't import Module

Thanks for taking the time to share this, been looking for this exact library!
Can't seem to get the module to import though, and i've tried alot of different paths...
"Error while processing route: route1.index" "Could not find module ember-cli-fullpagejs-view/view/fullpage-js-view" "requireModule@http://localhost:4200/assets/vendor.js:67:1

Hmm that's weird.
I am using the following lines in the Bitzik full page view:
import Ember from 'ember';

import FullpageJsView from 'ember-cli-fullpagejs-view/view/fullpage-js-view';

export default FullpageJsView.extend({
  fullpageOptions: {
    ....
  }
  }
});

Also make sure that you are using the last version of ember-cli-fullpagejs-view, I had messed up the Brocolli management in the previews versions.

Yea, i'm using the last version, and imported it exactly that way.. using ember-cli 0.1.5; ember 1.8.1; and did ran that code from views/application.js.
is there another command to run on install besides 'npm i ember-cli-fullpagejs-view'?

I am using ember-cli 0.1.12.
I don't remember at which point in Ember-cli 's development the recommended way to install addon became: ember install:addon ember-cli-fullpagejs-view
I don't know if the bower dependency will be installed automatically if you simply run npm i ember-cli-fullpagejs-view. But that shouldn't be the reason of this error in any case.
Is your code available somewhere?

Hi @e-karma
I checked and ember install:addon was introduced in ember 0.1.5 so you should probably try to install it that way :smile:
Keep me updated!

yea, they've changed things quite a bit.  I just ran a new project and tried installing that way and get this.. both with and w/o the 'npm i....' in advance.
Path or pattern "bower_components/fullpage.js/jquery.fullPage.js" did not match any files
Error: Path or pattern "bower_components/fullpage.js/jquery.fullPage.js" did not match any files

ok that's an issue I understand :)
You can try to run bower install and see if it works.
Else it would seem that 1the bower dependencies of my addon aren't carried over to the project that install it...
I'll have to check that
meanwhile you can just type ember install:bower fullpagejs and it should work !
I hope so at least

ok, I wiggled with the bower commands/ files n it appears to be working.. I'm going to spend some more time with it later this evening and may try to rework the addon to be seamless w/ new settings (if I get lucky).  I'll keep you posted and thanks for all the help + sharing this!

No problem !

@e-karma I updated the addon to make sure that the bower dependency is installed!


Noto Nastaliq Urdu 3.001

This PR fixes the following open issues:

Swap gaf anchors; fixes googlefonts/noto-fonts#1587
Change toothless seen rules; fixes googlefonts/noto-fonts#1786
Use inverted-v sukun in Kashmiri; fixes googlefonts/noto-fonts#2111
Raise LamIni.low anchors, don't use LamIni.low in I/F pairs; fixes googlefonts/noto-fonts#2181
Make Tah2DotsEnclNS more chonky; fixes googlefonts/noto-fonts#1988
Be more conservative about lam-lam-hah ligature; fixes googlefonts/noto-fonts#1588
Change diacritic placement in FDFD; fixes googlefonts/noto-fonts#1262

It also encodes more missing glyphs (0615, 06A7, 06A8, 06BD, 069B, 069C), fixes a few kerning regressions, and makes the version strings consistent (in 3.000, the nameID record 5 version was still 2.001. Oops.)

@simoncozens any chance we could address the following issues too?  That would finally provide us with a serviceable font for Kashmiri.
https://github.com/googlefonts/noto-fonts/issues/2219
https://github.com/googlefonts/noto-fonts/issues/2220

Sorry, missed those as they were untagged. I'll work on them.


Improve device status page

Attempted to make the device status page clearer for users, and to include more explicitly the VPN Only and Heartbeat Only statuses.
Moved images to end of document, as they don't seem to be very useful, other than an example.
Change-type: patch
Signed-off-by: Scott Lowe<EMAIL_ADDRESS>

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@vipulgupta2048 This didn't get merged - are there changes required? or can we merge it?

Hey @srlowe I was under the impression that this was being taken to a product call before the merge on it + @20k-ultra opened a PR to solve a similar issue with #1880 so it might be helpful to cherry-pick his changes in yours if they help provide more context to the users. Let me know when you are done, will do final review and merge

@balena-ci rebase

Hey @20k-ultra do check this out when we have a chance and we can get it out there

@balena-ci rebase

@balena-ci rebase


How to handle element not found exception

Hi @juliemr @wlingke
Is there a way in Protractor to handle element not found exception, similar to what we can do in Java version of Selenium webdriver?
Thanks,
Mohit

Hi @Droogans
I could find the custom Exception error handler code in the astrolabe. could you please add it over here in the comment.

https://github.com/stuplum/astrolabe/blob/963eb5001d7d3ce019a6ed66cec62ba2bb0d316b/lib/astrolabe/base.js#L45
It simply hooks up to the exceptions npm module, which contains more information. Or, you can take a look at the example that uses this.exception on Astrolabe's readme.
However, keep in mind that the tutorial referenced above is very stale. I would not recommend making too many custom exceptions. Sometimes it's useful for invalid situations in your business logic, but overall, throw new Error() works just as well, without the extra dependency.
At some point I might redo it, since vanilla ES6 in node 6+ makes Astrolabe obsolete (it's just a fancy way to make very uniform looking es6 classes, with some URL convenience functions that are easy to reproduce). If I were to rewrite it today, it would be using at least protractor 4.0, with typescript featured prominently. That might make more sense once typescript releases 2.0.


Ayoub

Hello my friend!
 @ayoub222
I think you forgot to remove the GIT origin to point to your own repository. This PR will change the initial setup of the project.
I created a tutorial about how to setup the project, please take a look: https://www.youtube.com/watch?v=soaG3GNSxJY
Hence I will close it.


Document Acceptance Criteria for Random Beacon v2

The document stores User Acceptance Criteria for Random Beacon v2
feature. It will be used to gain common understanding of how Random
Beacon v2 should act and will be utilised during the acceptance testing
of the feature.

@Piotr's comments addressed, ready for another round of reviews.

UACs list updated after recent changes to the Random Bacon v2. Ready for another round of reviews.

@tomaszslabon, I applied your propositions, also updated a couple more of parameters.


Laggy update of patient count and staff count in lsward.

At this point i believe this is a featureflaw and is subject to feature freeze


Unable to create a chef vault secret from a recipe

Hello,
I am trying to run create a chef vault secret from a recipe. I get a permission denied. I have tried different things including giving specific update permissions to the node/client on that specific databag but to no avail.
Here is the complete stacktrace and error: https://gist.github.com/chirag-jog/1aebe628bd6ddcf1c91c

The problem isn't access to the data bag, it's access to reading the public key of the user in order to encrypt the secret.
[2015-05-05T19:49:25+00:00] DEBUG: Initiating GET to https://api.opscode.com/organizations/rm_001/users/chiragjog
...
[2015-05-05T19:49:25+00:00] DEBUG: HTTP 1.1 403 Forbidden

For support with the chef_vault_secret helper, you should open an issue against that cookbook (which was written by Chef, not by Nordstrom).
Try doing the equivalent create from the node using knife vault create from the node - if that fails with permission denied, I expect the helper will fail as well.

Hi,
Thanks for responding.
I tried doing the same via the chef-vault gem and it still fails.
chef:recipe > item = ChefVault::Item.new("test", "test_data_item")
=> data_bag_item["test", "test_data_item", {"id"=>"test_data_item"}]
chef:recipe > item.raw_data = ({'id'=>'item', 'aa'=>'bb'})
=> {"id"=>"item", "aa"=>"bb"}
chef:recipe > item.admins(node.name)
WARNING: ubuntu14.clogeny.dev not found in users, trying clients.
=> ["ubuntu14.clogeny.dev"]
chef:recipe > item.save()
Net::HTTPServerException: 403 "Forbidden"
from /opt/chef/embedded/lib/ruby/2.1.0/net/http/response.rb:119:in error!' from /opt/chef/embedded/apps/chef/lib/chef/http.rb:145:in request'
from /opt/chef/embedded/apps/chef/lib/chef/http.rb:126:in post' from /opt/chef/embedded/apps/chef/lib/chef/data_bag.rb:159:in create'
from
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-vault-2.5.0/lib/chef-vault/item_keys.rb:81:in
rescue in save' from /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-vault-2.5.0/lib/chef-vault/item_keys.rb:75:in save'
from
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-vault-2.5.0/lib/chef-vault/item.rb:168:in
`save'
from (irb#1):21
chef:recipe >
How do i get the client to create a secret via the recipe?
--
Regards,
[image: Clogeny logo square]
Chirag Jog
VP - Engineering,
Clogeny Technologies Pvt. Ltd.
(India) +91-9766619440 | (US) +1-408-598-1792
Skype: chirag.jog
http://www.clogeny.com
[image<EMAIL_ADDRESS>https://www.linkedin.com/company/clogeny  [image:
<EMAIL_ADDRESS>https://www.facebook.com/pages/Clogeny-Technologies-Pvt-Limited/151746528245744
[image<EMAIL_ADDRESS>https://twitter.com/clogeny
On Tue, May 5, 2015 at 5:18 PM, James FitzGibbon<EMAIL_ADDRESS>wrote:

The problem isn't access to the data bag, it's access to reading the
public key of the user in order to encrypt the secret.
[2015-05-05T19:49:25+00:00] DEBUG: Initiating GET to https://api.opscode.com/organizations/rm_001/users/chiragjog
...
[2015-05-05T19:49:25+00:00] DEBUG: HTTP 1.1 403 Forbidden
For support with the chef_vault_secret helper, you should open an issue
against that cookbook https://github.com/opscode-cookbooks/chef-vault
(which was written by Chef, not by Nordstrom).
Try doing the equivalent create from the node using knife vault create
from the node - if that fails with permission denied, I expect the helper
will fail as well.
—
Reply to this email directly or view it on GitHub
https://github.com/Nordstrom/chef-vault/issues/154#issuecomment-99225807
.

This isn't really a problem with chef-vault itself: you are trying to change an object on your Chef server that you don't have permission to access.  From what you pasted, I can't even tell what you were trying to access when you received a 403 response.
Generally speaking, nodes cannot read client objects other than their own.  In order to create or update a vault, you need to be able to read the public keys of all clients (nodes and users) who you want to decrypt it, and you need to be able to write to the data bag item and the side-along _keys data bag item.  If any of those things cannot be accessed, then you won't be able to create the vault.
In the gist you posted, your problem is that the machine trying to create the vault can't read the public key of chiragjog.  I expect that you can't use knife client show chiragjog from that node either.
Until all those permissions are fixed, you won't be able to do what you're trying to.  But this is an issue with how your org's permissions are set up, not with chef-vault.

Yes, makes sense. I had to explicitly give the client permissions to create
data bags or given it admin permissions (incase of open source chef) and
now it works.
Thanks for the help!
--
Regards,
[image: Clogeny logo square]
Chirag Jog
VP - Engineering,
Clogeny Technologies Pvt. Ltd.
(India) +91-9766619440 | (US) +1-408-598-1792
Skype: chirag.jog
http://www.clogeny.com
[image<EMAIL_ADDRESS>https://www.linkedin.com/company/clogeny  [image:
<EMAIL_ADDRESS>https://www.facebook.com/pages/Clogeny-Technologies-Pvt-Limited/151746528245744
[image<EMAIL_ADDRESS>https://twitter.com/clogeny
On Wed, May 6, 2015 at 4:30 PM, James FitzGibbon<EMAIL_ADDRESS>wrote:

This isn't really a problem with chef-vault itself: you are trying to
change an object on your Chef server that you don't have permission to
access. From what you pasted, I can't even tell what you were trying to
access when you received a 403 response.
Generally speaking, nodes cannot read client objects other than their own.
In order to create or update a vault, you need to be able to read the
public keys of all clients (nodes and users) who you want to decrypt it,
and you need to be able to write to the data bag item and the side-along
_keys data bag item. If any of those things cannot be accessed, then you
won't be able to create the vault.
In the gist you posted, your problem is that the machine trying to create
the vault can't read the public key of chiragjog. I expect that you can't
use knife client show chiragjog from that node either.
Until all those permissions are fixed, you won't be able to do what you're
trying to. But this is an issue with how your org's permissions are set up,
not with chef-vault.
—
Reply to this email directly or view it on GitHub
https://github.com/Nordstrom/chef-vault/issues/154#issuecomment-99598642
.


Queulat does not seem to install

Description

Our composer.json contains a requirement for felipelavinz/queulat.
Under the repositories section, we have configured a fork of the queulat package.
For some reason, the queulat dependency does not seem to be installing, since the felipelavinz directory is empty after running composer install.
Reproduction

run composer install
look in the felipelavinz/directory
observe there are no files
look for a creativecommons/queulat/ directory (from VCS)
observe that the creativecommons/queulat project does not seem to have been cloned

Expectation

The queulat dependency would install correctly either from

felipelavinz/queulat or
creativecommons/queulat

Additional context

Regardless of whether we decide to deprecate Queulat (#69) it would be useful if the dependency would install correctly.

@hugosolar does the composer.json file seem to be configured correctly from your perspective?

@brylie as far as I remember, we make a fork of Queulat since the original repo does not have a release yet, that's why creativecommons/queulat should be the repo to use on composer. I don't remember having any particular issues by installing creativecommon-base I can take a look in a minute

OK, thanks @hugosolar
For context, I'm using our [Docker-based development environment](https://github.com/creativecommons/creativecommons-base/tree/main/development to run WordPress with the creativecommons-base theme. There is a line in the docker-compose.yml that creates a volume to link the repository root with the wp-content/themes/creativecommons-base/ directory inside the image.
https://github.com/creativecommons/creativecommons-base/blob/1ca33ae3525fa7d789148e1030dd69ecfaaf5d0e/development/docker-compose.yml#L13
The Docker volume would preserve the file structure, including the vendor/directory as a sub-directory of wp-content/themes/creativecommons-base. Is that where vendor/ is expected to be found?

yes, and then you need to use that path to vendor/autoload.php on mu-plugin/Queulat.php
take a look at this : https://github.com/felipelavinz/queulat#loading-queulat-as-mu-plugin


SA1026 codefix bug

intput:
public class Foo
{
    public void Bar()
    {
        var ints = new
            [] { 1, 2, 3 };
    }
}

output:
public class Foo
{
    public void Bar()
    {
        var ints = new            [] { 1, 2, 3 };
    }
}

expected:
public class Foo
{
    public void Bar()
    {
        var ints = new[] { 1, 2, 3 };
    }
}

grabbed

:question: Can you include the expected output as well?

done


Add a test which reproduces the original crash that is fixed by #23984

Internal issue b/166232206 for more context.
This is a clean up for the original verification for the fix in #23984 that is mentioned in https://github.com/grpc/grpc/pull/23984#issuecomment-682246191.
This repro's the original crash at ~75-100% in opt and tsan builds, with the fix removed.
The main thing this makes use of is the new mechanism to inject mocked values for target initial window size calculations. Achieving the desired flow control settings behavior is very tricky to do, otherwise. The mock API here is good enough for this test's purpose, but I'm open to other ideas.

How long does this test take to run?

How long does this test take to run?

From what I've seen, the opt/linux/epollex config runs in around 5 seconds and the tsan/poll build runs in around 20 seconds, so other builds/platforms should I think be somewhere in between.
Some results from manually invoked RBE runs:
bazel --bazelrc=tools/remote_build/manual.bazelrc test --config=opt //test/core/transport/chttp2:remove_stream_from_stalled_lists_test@poller=epollex --runs_per_test=10

...

//test/core/transport/chttp2:remove_stream_from_stalled_lists_test@poller=epollex PASSED in 6.6s
  Stats over 10 runs: max = 6.6s, min = 4.6s, avg = 5.1s, dev = 0.5s

bazel --bazelrc=tools/remote_build/manual.bazelrc test --config=tsan //test/core/transport/chttp2:remove_stream_from_stalled_lists_test@poller=poll --runs_per_test=10

...

//test/core/transport/chttp2:remove_stream_from_stalled_lists_test@poller=poll PASSED in 24.7s
  Stats over 10 runs: max = 24.7s, min = 19.7s, avg = 23.1s, dev = 1.3s

We can perhaps actually reduce the runtime of the test e.g. by halving the number of threads used, though.
For example, with the fix for the original issue removed, running the opt/epollex configuration on linux for 100 runs actually yields me ~80 failures both with 128 client threads and 64 client threads.
With 64 threads, TSAN runtime seems brought down to ~13 seconds: Stats over 10 runs: max = 13.8s, min = 11.9s, avg = 13.3s, dev = 0.5s

@yashykt I've lowered the number of threads to 64, which decreases the runtime but still repro's well enough

A heads up, I hit a macos flake in this test:
I0829 15:04:45.926330000<PHONE_NUMBER>29216 subchannel.cc:1126]           New connected subchannel at 0x7fc7e5320530 for subchannel 0x7fc7e521fce0
I0829 15:04:45.926433000<PHONE_NUMBER>38944 subchannel.cc:1126]           New connected subchannel at 0x7fc7e53214d0 for subchannel 0x7fc7e4620040
I0829 15:04:45.926465000<PHONE_NUMBER>02368 subchannel.cc:1126]           New connected subchannel at 0x7fc7e512bd30 for subchannel 0x7fc7e461e970
D0829 15:04:46.994763000<PHONE_NUMBER>50272 remove_stream_from_stalled_lists_test.cc:323] All RPCs completed!
E0829 15:04:46.994915000<PHONE_NUMBER>50272 server.cc:830]                assertion failed: listeners_destroyed_ == listeners_.size()

*******************************
Caught signal SIGABRT
  no backtrace

2020-08-29 15:04:46,996 FAILED: cmake/build/remove_stream_from_stalled_lists_test --gtest_filter=Pollers.TestReadabilityNotificationsDontGetStrandedOnOneCq  GRPC_POLL_STRATEGY=poll [ret=-6, pid=37762, time=1.2sec]

... which I'm looking into

The server shutdown flake mentioned above should be fixed now.
Ran 2000 iterations in opt for each of poll (previously flakey), epoll1, and epollex, and they are all passing.

squashed down commits


UnixMode + UnixStat.Mode

Summary of the new feature / enhancement
Please add:

the ability to display access rights in octal notation.
displaying  SGID, SUID and sticky bit in UnixMode

Proposed technical implementation details (optional)
For example:
Get-Item ./1.ps1

    Directory: /home/user/Desktop

UnixMode      Octal  User   Group      LastWriteTime       Size Name
--------      -----  ----   -----      -------------       ---- ----
-rw-r--r-T     1644  user    user   11.01.2022 22:34        579 1.ps1

And the question -- where can I see the enum of unix access rights? Like this:
[flags()] enum access
{
    ExecuteAll   = 1
    WriteAll     = 2
    ReadAll      = 4
    ExecuteGroup = 8
    WriteGroup   = 16
    ReadGroup    = 32
    ExecuteOwner = 64
    WriteOwner   = 128
    ReadOwner    = 256
    StickyBit    = 512
    SGID         = 1024
    SUID         = 2048
  #              = 4096    # ???
    SymLink      = 8192    # And character special file ???
    Directory    = 16384
    File         = 32768
}

get-typedata system.io.fileinfo | % members
shows that Mode, ModeWithoutHardLink, VersionInfo, BaseName, Target, LinkType, NameString, LengthString, LastWriteTimeString are added from the types information for fileinfo objects and  (on linux)
get-typedata system.io.fileSysteminfo | % members
shows types information adds script properties for 'UnixMode, User, Group, Size' to fileSysteminfo objects
The script in UnixMode checks for the presence of UnixStat and  uses its .GetModeString Method to return the Unix mode as a formatted string.  (User, Group and Size also use UnixStat)
if I do something like  $d = Get-Item ./PowerShell
$d.GetFiles  returns items without UnixStat members, (which is what the types info suggests) but $d | gci returns items with UnixStat - which implies it is added by Get-Item  / Get-ChildItem . It looks to be a "helper" designed to hide all the internals you want - exposing them doesn't seem to be a very difficult thing to do but I haven't searched for the code that does the work.

Thank you. But I don't understand where can I look for System.Enum (like System.IO.FileAttributes) of linux access rights? In order to use net-methods (they are faster then scripts and no need to assemble my own bike) For example:
(gi ./Desktop/).UnixStat.Mode   # 16877
(gi ./Desktop/).UnixMode        # drwxr-xr-x

16877 is:
d_rwx_r-x_r-x

d: 16384  # Directory

r: 256    # owner can read
w: 128    # owner can write
x: 64     # owner can execute

r: 32     # group can read
w: 0      # group can not write
x: 8      # group can execute

r: 4      # other can read
w: 0      # other can not write
x: 1      # other can execute

16384 + 256 + 128 + 64 + 32 + 8 + 4 + 1 = 16877

P/Invoke read Unix stat struct and mode_t field of the struct is the mode you ask. You can find more info in https://man7.org/linux/man-pages/man0/sys_stat.h.0p.html

From where UnixStat.Mode does get values? Is this an enum or not?

From where UnixStat.Mode does get values? Is this an enum or not?

It copies mode_t from stat struct. It is int - see reference to docs above.

I wanted to do it the right way, I did it as always, with the help of crutches (/usr/bin/stat).

You can also look https://github.com/PowerShell/PowerShell-Native where Unix P/Invokes implemented.

1 powershell is currently not perfect
2 You can judge the SGID, SUID, sticky attributes by the following commands:
(Get-Item './smy Matrix Digital Rain.ps1').Unixstat.IsSetUid
(Get-Item './smy Matrix Digital Rain.ps1').Unixstat.IsSetGid
(Get-Item './smy Matrix Digital Rain.ps1').Unixstat.IsSticky
3 You can get the string with the following commands and calculate it yourself:
(Get-Item './smy Matrix Digital Rain.ps1').UnixMode[-3]
r

3 You can get the string with the following commands and calculate it yourself

The variant, thanks. Just I don't want to parse strings to get result. Kind of this:
& {
 -join ('drwxr-xr-x' -replace '[ldc]' `
                     -replace '-','0' `
                     -replace 'r','4' `
                     -replace 'w','2' `
                     -replace 'x','1' `
                     -split '(?<=...)(?=(?:...)+$)' |
           Foreach-Object { [Linq.Enumerable]::Sum([int[]][string[]][char[]] $_) }
       )
 }

# 755

I noticed that if SUID and SGID are in the file at the same time, then UnixStat.IsSetUid and UnixStat.IsSetGuid both show False but each of them must show True.

A shorter conversion :-)
 [convert]::ToString([convert]::ToInt32(('drwxr-xr-x' -replace '[rwx]','1' -replace "[^1]","0"),2),8)

Thanks to all.


Integrate tesla driven adapter to handle http request and form data

[ ] Config for form data
[ ] Refactor connection process use case (remove Mint calls)
[ ] Test (logger - timeout)


Fix inconsistency when user specifies weights_save_path

Background
Currently, when the user specifies weights_save_path we have inconsistent behavior as to the path where we actually save the checkpoints.
If we have no loggers, we save to weights_save_path/checkpoints (line 587)
If we have one logger, we save to weights_save_path/name/version/checkpoints
If we have multiple loggers, we save to weights_save_path/name1_name2/version1_version2/checkpoints
https://github.com/PyTorchLightning/pytorch-lightning/blob/2360049744667c21a532a2cb7bee290e002a9698/pytorch_lightning/callbacks/model_checkpoint.py#L572-L587
Proposed refactor
Let's always use the path weights_save_path/checkpoints , like we do for the case when there is no Logger: https://github.com/PyTorchLightning/pytorch-lightning/blob/5df519572f78ae5e23b0aab18fcbda06df7ff8dd/pytorch_lightning/callbacks/model_checkpoint.py#L607
Motivation

It doesn't make sense to store the checkpoints under a path containing the loggers' names and versions, because we are not writing to the logger at all. We are writing to the weights_save_path provided by the user.
For the user it is a strange experience that he/she provides a weights_save_path, but depending on whether there is a logger or not, the path gets changed
The concatenation of the logger names and versions has an awkward look to it and should be fixed. It is a relic of the deprecated LoggerCollection.

Why should we do this even though weights_save_path has been deprecated?

It is the right experience for the user
It will clean up a particularly confusing part of the code and make it much easier to understand
It will make implementation of https://github.com/PyTorchLightning/pytorch-lightning/issues/12177 and https://github.com/PyTorchLightning/pytorch-lightning/issues/12028 a lot simpler

cc @awaelchli @edward-io @borda @ananthsub @rohitgr7 @kamil-kaczmarek @Raalsky @Blaizzy @ninginthecloud

Updated the title and description

It probably makes sense to do this for long term.
As usual, I will jump in to give a small history lecture 🤣
weights_save_path was previously used to save mainly two things:

a special checkpoint when interrupting training with e.g. the Ctrl+C signal
a special checkpoint when receiving a SLURM interrupt signal

(1) got replaced by fault-tolerant training and (2) is currently being changed to use default_root_dir.
If I remember correctly, the motivation behind using weights_save_path also in the ModelCheckpoint was for convenience, in that you had to only change a trainer arg instead of instantiating a ModelCheckpoint with a custom dir_path.


Fix incorrect Params.Behaviour.data/2 typespec

After I updated params in our project, I got new Dialyzer warnings:
web/controllers/queue_controller.ex:1: The inferred return type of data/2 ({'error',_} | {'ok',#{'__struct__'=>atom(), atom()=>_}}) has nothing in common with #{'__struct__'=>atom(), atom()=>_}, which is the expected return type for the callback of 'Elixir.Params.Behaviour' behaviour

The only file that uses Params.Behaviour is Params.Schema, so I changed callback spec. With this change Dialyzer warnings are gone.

@vic ping :)

@take-five  pong!
Sure I'm merging this and will release a new minor version. Thanks!


Fixing bug in ops.substring

If min_dist is equal to 0 (i.e. the first coordinate) then the loop immediately breaks.
This means that internal coordinates are skipped because only (start_point.x, start_point.y) and (end_point.x, end_point.y) are written to the new vertex_list.
By changing the less than to a less-than-equal sign the loop behaves as intended.

Fixes #659

Coverage remained the same at 81.152% when pulling 0fe1027d0a49b69aae24591268acf4bf6f7fd9ae on shongololo:patch-1 into fc12a113f2c234ec76f4935d1a94d0b134cc91fb on Toblerity:master.

Coverage remained the same at 81.152% when pulling 0fe1027d0a49b69aae24591268acf4bf6f7fd9ae on shongololo:patch-1 into fc12a113f2c234ec76f4935d1a94d0b134cc91fb on Toblerity:master.

Coverage remained the same at 81.152% when pulling 0fe1027d0a49b69aae24591268acf4bf6f7fd9ae on shongololo:patch-1 into fc12a113f2c234ec76f4935d1a94d0b134cc91fb on Toblerity:master.

Coverage remained the same at 81.152% when pulling 0fe1027d0a49b69aae24591268acf4bf6f7fd9ae on shongololo:patch-1 into fc12a113f2c234ec76f4935d1a94d0b134cc91fb on Toblerity:master.

Coverage remained the same at 81.152% when pulling 0fe1027d0a49b69aae24591268acf4bf6f7fd9ae on shongololo:patch-1 into fc12a113f2c234ec76f4935d1a94d0b134cc91fb on Toblerity:master.

Coverage remained the same at 81.152% when pulling 0fe1027d0a49b69aae24591268acf4bf6f7fd9ae on shongololo:patch-1 into fc12a113f2c234ec76f4935d1a94d0b134cc91fb on Toblerity:master.

Coverage remained the same at 81.152% when pulling 0fe1027d0a49b69aae24591268acf4bf6f7fd9ae on shongololo:patch-1 into fc12a113f2c234ec76f4935d1a94d0b134cc91fb on Toblerity:master.

@shongololo I see what you mean. Can you add a test to tests/test_substring.py to confirm the fix? Something like this after 70 should suffice.
    @unittest.skipIf(geos_version < (3, 2, 0), 'GEOS 3.2.0 required')
    def test_return_substring_min_dist-zero(self):
        """Confirm fix of #658"""
        self.assertTrue(substring(self.line2, 0.0, 7.0).equals(LineString(([3.0, 0.0], [3.0, 6.0], [4.0, 6.0]))))


Unicode problem

Same error issue #29, when doing add:
dockutil --add "/System/Applications/Music.app" --label "Música" --after "Fotos"
Result:
Traceback (most recent call last):
  File "/usr/local/bin/dockutil", line 669, in <module>
    main()
  File "/usr/local/bin/dockutil", line 371, in main
    commitPlist(pl, plist_path, restart_dock)
  File "/usr/local/bin/dockutil", line 658, in commitPlist
    writePlist(pl, plist_path)
  File "/usr/local/bin/dockutil", line 388, in writePlist
    plistlib.writePlist(pl, plist_import_path)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 94, in writePlist
    writer.writeValue(rootObject)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 252, in writeValue
    self.writeDict(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 281, in writeDict
    self.writeValue(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 258, in writeValue
    self.writeArray(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 287, in writeArray
    self.writeValue(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 252, in writeValue
    self.writeDict(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 281, in writeDict
    self.writeValue(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 252, in writeValue
    self.writeDict(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 281, in writeDict
    self.writeValue(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 239, in writeValue
    self.simpleElement("string", value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 172, in simpleElement
    value = _escapeAndEncode(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 222, in _escapeAndEncode
    return text.encode("utf-8")             # encode as UTF-8
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1: ordinal not in range(128)

version: 2.0.5

Still having issues with unicode as well, e.g. with German localisation with Munki's 'Managed Software Center.app'; while adding works fine (as the English name) trying to find or remove the icon (once the localised string is recognised by the Dock) does not:
dockutil --find 'Geführte Softwareaktualisierung' or
dockutil --find 'Gefu<0308>hrte Softwareaktualisierung'
results in
item Geführte Softwareaktualisierung was not found in /Users/user/Library/Preferences/com.apple.dock.plist
and
dockutil --remove 'Geführte Softwareaktualisierung'
throws a
/usr/local/bin/dockutil:317: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
  if pl[section][item_offset]['tile-data']['file-label'] == find_label:
Geführte Softwareaktualisierung was not found in /Users/user/Library/Preferences/com.apple.dock.plist

@kcrawford same problem here. German Umlauts are not working in labels.
Ü ü
Ä ä
Ö ä
Can you fix this, please?

I think this is working properly in dockutil 3. Please retest in dockutil 3.

Tested and confirmed to work in macOS 12.2.1, including the formerly failing --find thank you!!1!

Thanks for testing!  Closing this issue.


Fix issue #133

Fix compose:down not dealing with dependencies correctly.

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

I'm not overly familiar with the code but this seems to work for the use case in the bug report.
Hopefully the fix is as simple as it looks but I'm happy to look further if there are any concerns with the proposed fix.

Thanks for the contribution!
Unfortunately I don't think the fix is this simple. The down action (like other "remove" actions) shouldn't run the default "create" action, which is what will happen if the dependencies are added like this. An example is a compose resource that depends on an image. We shouldn't rebuild the image just to compose:down.
I think the problem is that the env resources is not like other resources. It's needed to populate some values so that compose:down is able to run.  This ties into the problem described in #73.
I proposed a workaround in https://github.com/dnephin/dobi/issues/133#issuecomment-402331701
I think the solution might be to declare env dependencies differently, so that they will apply  to all actions.

I did think it must be more difficult than that. Thanks for the extra info though. I will try to understand it in more depth and see what I can come up with.
Do you want me to close this PR and I can comment in the issue (before making any changes) if I find an alternative approach that I think will work and then we can go from there?

I'm fine keeping the PR open. There are so few it's easy to manage.


AttributeError: module 'openai' has no attribute 'Embedding'

🐛 Describe the bug
AttributeError: module 'openai' has no attribute 'Embedding'
Default Google Collab page raises this error.

Thanks for reporting. You can resolve this issue for now by doing pip install openai==0.28.1
Chroma folks are fixing the issue in the meantime: https://github.com/chroma-core/chroma/issues/1340

Yes, it did resole with downgrading openai as you mentioned.
Thanks!


perf: send messages immediately in wss

The stream in wss is buffered.
This change makes it so that we flush the stream immediately after writing to it so that we don't introduce artificially bad ping.

Closing this for now as it doesn't seem to fix the issues.
I will update this PR once I've done more research https://github.com/MirrorNetworking/SimpleWebTransport/pull/25


Safe Locks leaderbaord not sorting correctly.

Due to missing data for some rows, the table for the safe locks leader board does not sort as expected when changing between owned, cracked and wish listed.
Additionally it appears to be defaulting to owned rather then cracked as I expect the default sort should be.

Data fixed, thanks for pointing it out. Sort matches the locks one...


Please add support for PHP 8.0

Sometimes VS Code shows a notification that some ReflectionParameter functionality is deprecated, happening since I upgraded my MacBook to PHP 8.0
ErrorException:
Method ReflectionParameter::getClass() is deprecated in /Users/buismaarten/.vscode/extensions/felixfbecker.php-intellisense-2.3.14/vendor/phpdocumentor/reflection-docblock/src/DocBlock/StandardTagFactory.php:241

Stack trace:
#0 /Users/buismaarten/.vscode/extensions/felixfbecker.php-intellisense-2.3.14/vendor/phpdocumentor/reflection-docblock/src/DocBlock/StandardTagFactory.php(241): {closure}(8192, 'Method Reflecti...', '/Users/buismaar...', 241)
#1 /Users/buismaarten/.vscode/extensions/felixfbecker.php-intellisense-2.3.14/vendor/phpdocumentor/reflection-docblock/src/DocBlock/StandardTagFactory.php(198): phpDocumentor\Reflection\DocBlock\StandardTagFactory->getArgumentsForParametersFromWiring(Array, Array)
#2 /Users/buismaarten/.vscode/extensions/felixfbecker.php-intellisense-2.3.14/vendor/phpdocumentor/reflection-docblock/src/DocBlock/StandardTagFactory.php(122): phpDocumentor\Reflection\DocBlock\StandardTagFactory->createTag('ClientCapabilit...', 'param', Object(phpDo...

https://php.watch/versions/8.0/deprecated-reflectionparameter-methods
ReflectionParamter::getType() is the recommended way to replace the deprecated methods. This method is available in PHP 7.0 and later.
not that I'm forcing people anyone, just wondering if anyone is working on this?

It seems easy to do, just upgrade the phpdocumentor/reflection-docblock package to v5 which supports PHP 8.0. Hopefully the author would merge a pull request or fix it himself after not touching the repostiry for nearly 2.5 years.

change file .vscode/extensions/felixfbecker.php-intellisense-2.3.14/vendor/phpdocumentor/reflection-docblock/src/DocBlock/StandardTagFactory.php line 241 to this code
                //$typeHint = $parameter->getClass() ? $parameter->getClass()->getName() : null;
                try{
                        $type = $parameter->getType();
                        if($type){
                                $name = new \ReflectionClass($parameter->getType()->getName());
                                if($name){
                                        $typeHint = $name->getName();
                                }
                        }
                }catch(Exception $e){
                }


🚀 Major feature request: EEG recordings

Use Case
The app should provide the ability to do EEG recordings for a patient to provide that data for further analysis.
Problem
This feature is currently unsupported by the app (and the Spezi framework ecosystem).
Solution
Two major changes are imposed by these feature:

Integration of the EEG band hardware and the respective SDK
Integration of a EEG measurement flow into the app's UI

Alternatives considered
--
Additional context
Reusable components should be directly integrated or refactored out into standalone modules of the StanfordSpezi framework ecosystem.
Code of Conduct

[X] I agree to follow this project's Code of Conduct and Contributing Guidelines

considered resolved as of #19


Bossbar can be obstructed when there are 6 or more Withers in the area

It would be great if you are able to make the bossbar for the teleport always show up on top despite other bossbars

in WitherEntity.class, the private ServerBossBar bossBar is created using new ServerBossBar...
i see no mention of bossbar manager anywhere in it, so it might not get added to it
overall i have no idea how to actually do this...


Wait cache

This seems really sketchy. From looking at its usage, it's unclear whether i is expected to be an Iterator<Promise<T>> or an AsyncIterator<T>, i.e. whether i.next() returns a Promise<IteratorResult<T>> or an IteratorResult<Promise<T>>.
Or really, waitCache seems to only work as documented (i.e. waiting for multiple things concurrently) when you get back a Promise<IteratorResult<Promise<T>>>, which should not happen with normal AsyncIterator implementations.

@bergus I've struggled with the performance-related issues, but I got it all sorted out in the end:

Here's the final code
Here's the original discussion here
Here's generated documentation

I did look at the final code, but it doesn't seem to be so different so I figured this PR would be the appropriate place to comment (better than the locked StackOverflow question).
I'm not familiar with your library (don't know the details of map and pipeAsync) so I might be missing something, but how does this actually run multiple things concurrently if consumed by a sequential for await loop? Wouldn't you have to call next() multiple times in quick succession even before the previous call (promise) completed?

A sequential for await accounts just for the sequence itself, i.e. Promise<Promise<IteratorResult<T>>>. When you re-map the actual values into promises, using map, for example, then you'd need:
for await (const a of i) {
    await a; // because values themselves are promises
}

that's why we have wait that can resolve those automatically:
const i = pipeAsync([1, 2, 3], map(a => Promise.resolve(a)), wait());

And so waitRace caches those up, and then runs Promise.race on those values.

Ah, so it really needs to be an AsyncIterable<Promise<T>> for the concurrency to take place, AsyncIterable<T> is not enough.
I did not see wait, I had expected map to implicitly take care of that - but I guess then it would at least be mapAsync or something.

I had expected map to implicitly take care of that

Our re-mapping operators, like map and aggregate do not resolve promises, because there are a number of ways they can be resolved, and it would take away the freedom of choosing how they should be resolved.
With our approach you can append wait for one-by-one resolution, you can aggregate into an array and then do Promise.all, or you can do now waitRace to cache them up and race-resolve.

@bergus I have updated map documentation to explain why it does not resolve any promises.


Subdomain not getting picked up

Hi, thanks for this package! When using the Spatie multi-tenancy package, I am having the following issue.
Expected behavior
When I am on a tenant URL, such as http://tenant-one.my-app.test/comment that has the named route comment.index and I try using this.route().current('comment.index'); in a Vue component I should get a result of true.  However, I get false.
Similarly, when I am on the same URL and I try using this.route().current() in a Vue component I would expect to get the named route comment.index as the result.  However, I get undefined, probably due to the above.
Versions

Laravel: 8.12.3
Ziggy: 0.9.4 (composer) and also "ziggy-js": "^0.9.4" (packagist)
"spatie/laravel-multitenancy": 1.6.9

Can you please share the route definition, the relevant section of the output of Ziggy.namedRoutes in your console, and the context you're making those route() calls in? Do you have other routes or uses of Ziggy that are working as expected? Thanks.

Hi @bakerkretzmar - thanks for the quick response.
This is working as expected:  this.route('comment.index', [], false); as it results in creating the route /comment.
My route is:
Route::middleware('tenant')->group(function () {
    Route::middleware('auth')->group(function () {
        Route::resource('comment', CommentController::class)->only([
            'index', 'show',
        ]);
    });

When I try Ziggy.namedRoutes in my console, I get Ziggy is not defined. I also tried console.logging the following from within my Vue component with no luck:
            console.log(Ziggy.namedRoutes);
            console.log(this.Ziggy.namedRoutes);
            console.log(this.route().namedRoutes);
            console.log(this.namedRoutes);

Interesting. My understanding of Route::resource() is that it names routes using the plural, so I would have expected route('comments.index') to work, but not route('comment.index').
Is this.route('comment.index', [], false); inside the template of a Vue component, not a method call or mounted hook or something?
How are you setting this.route? Do you have a global mixin in app.js like Vue.mixin({ methods: { route: route } })?

Hi @bakerkretzmar thanks again for the quick response.  Here are my answers to your questions:

When I run php artisan route:list I see comment.index for the route name.

I have this.route('comment.index', [], false); inside a regular computed property in a .vue file/component:

    computed: {
        getIndexRoute () {
            return this.route('comment.index', [], false);
        },

I am pulling in the package in app.js like this:

import route from 'ziggy';
import { Ziggy } from './ziggy';

require('./bootstrap');

window.Vue = require('vue');

Vue.mixin({
    methods: {
        route: (name, params, absolute) => { return route(name, params, absolute, Ziggy); }
    }
});

Nothing much going on inside ./bootstrap:
window._ = require('lodash');
window.axios = require('axios');
window.axios.defaults.headers.common['X-Requested-With'] = 'XMLHttpRequest';

webpack.mix.js:
const mix = require('laravel-mix');
const path = require('path');

mix
    .webpackConfig({
        resolve: {
            alias: {
                ziggy: path.resolve('vendor/tightenco/ziggy/src/js/route.js')
            }
        }
    })
    .js('resources/js/app.js', 'public/js')
    .extract()
    .postCss('resources/css/app.css', 'public/css', [
        require('postcss-import'),
        require('tailwindcss'),
        require('postcss-nested'),
        require('autoprefixer')
    ]);

if (mix.inProduction()) {
    mix
        .version();
}

and I am not pulling in @routes in Blade anywhere - I actually tried using @routes before installing npm, and unfortunately I was having separate issues with that where it wasn't cooperating with Vue for some reason, so then I started down this road instead as it seemed potentially better anyways to just pull it in via JS instead of blade.

@bryanjamesmiller okay, thanks a lot for these details!
Did you run php artisan ziggy:generate, and the output of that file is in a file called ziggy.js right beside your app.js? namedRoutes should be in there, can you share the value of the comment.index entry in that object?

@bakerkretzmar yes, I had run the artisan command and the resulting file ziggy.js was placed in the same directory as app.js.  Here is the comment.index entry:
["GET","HEAD"],"domain":null},"comment.index":{"uri":"comment","methods":

Okay sorry, can you share more of that file actually? Or at least all the top-level keys like baseDomain and baseUrl, and a couple other routes?
My current best guess is that your routes are only being generated for the "current" tenant at the moment you run the php artisan ziggy:generate command, but I want to look into this more.

        namedRoutes: {"debugbar.openhandler":{"uri":"_debugbar\/open","methods":["GET","HEAD"],"domain":null},"debugbar.clockwork":{"uri":"_debugbar\/clockwork\/{id}","methods":["GET","HEAD"],"domain":null},"debugbar.telescope":{"uri":"_debugbar\/telescope\/{id}","methods":["GET","HEAD"],"domain":null},"debugbar.assets.css":{"uri":"_debugbar\/assets\/stylesheets","methods":["GET","HEAD"],"domain":null},"debugbar.assets.js":{"uri":"_debugbar\/assets\/javascript","methods":["GET","HEAD"],"domain":null},"debugbar.cache.delete":{"uri":"_debugbar\/cache\/{key}\/{tags?}","methods":["DELETE"],"domain":null},"welcome":{"uri":"\/","methods":["GET","HEAD"],"domain":null},"login":{"uri":"login","methods":["GET","HEAD"],"domain":null},"logout":{"uri":"logout","methods":["POST"],"domain":null},"register":{"uri":"register","methods":["GET","HEAD"],"domain":null},"password.request":{"uri":"password\/reset","methods":["GET","HEAD"],"domain":null},"password.email":{"uri":"password\/email","methods":["POST"],"domain":null},"password.reset":{"uri":"password\/reset\/{token}","methods":["GET","HEAD"],"domain":null},"password.update":{"uri":"password\/reset","methods":["POST"],"domain":null},"password.confirm":{"uri":"password\/confirm","methods":["GET","HEAD"],"domain":null},"comment.index":{"uri":"comment","methods":["GET","HEAD"],"domain":null},"comment.show":{"uri":"comment\/{comment}","methods":["GET","HEAD"],"domain":null}},
        baseUrl: 'http://my-app.test/',
        baseProtocol: 'http',
        baseDomain: 'my-app.test',
        basePort: false,
        defaultParameters: []
    };

@davejamesmiller thanks for your patience. Here's the quick fix—update your app.js to this:
Vue.mixin({
    methods: {
        route: (name, params, absolute) => {
            return route(name, params, absolute, {
                ...Ziggy,
                baseUrl: window.location.origin,
                baseDomain: window.location.host,
            });
        }
    }
});

The behaviour you're seeing is being caused by Spatie's multi-tenancy package not playing super nicely with the same part of Ziggy that #334 took issue with—the fact that we use url('/') to determine the base URL for Ziggy's route generation.
The @routes Blade directive works fine for your use case: it gets its base URL late in the current HTTP request when there is already a tenant, so it correctly passes http://tenant-one.my-app.test/ back to Ziggy's Javascript, which works because that is indeed the current window's URL.
The ziggy:generate Artisan command, however, runs without an HTTP request and therefore does not have a tenant set up—its 'URL' is set automatically to the value of APP_URL, which is http://my-app.test, and so later when you try to use it in your app, it doesn't match the current window URL.
The change in #334 means that @routes will actually also stop working for this specific setup in Ziggy v1. I'm not sure how I feel about this... Spatie's multi-tenancy package configures the tenant and sets it in the URL without adjusting the route definition, which took me a while to figure out and get working and feels kinda weird to me. If the tenant was a real route parameter, set up with something like Route::domain('{tenant}.my-app.test')..., none of this would be an issue.
Ignoring the domain when calling route().current(), as suggested in #329, would also solve this issue. I still don't like that being the default behaviour, but now I'm not quite so sure.
Thoughts?

@bakerkretzmar I will try this out shortly, but it makes perfect sense and looks very promising.  Thank you for your help on this!
Regarding the @routes blade directive, while that at first was working for me (before I started using the npm package), I think the problem I was running into had to do with testing a view that was compiled by Vue.  It was a simple "assertSee('some text')" view.  It appeared that phpunit couldn't get past the compiled results of the @routes directive.  However, you have given me what looks like a working path forwards, so I myself will probably not need a solution for that anymore, but just as a heads up if you wanted to know what happened with my attempts at that approach.

@bryanjamesmiller sounds good! That PHPUnit issue is interesting.... do you remember the specifics of the errors you were seeing? I've made similar text/content assertions on views with @routes before without issue, I'm not totally sure about Vue but I'm curious how that could affect it since PHPUnit of course can't execute the JS.


view and edit comfortable json configs

currently we have a plain text editor for working with json files
This is a different approach
https://github.com/PaulSchweizer/qt-json-view
this will need a small refactoring for python-3 and QT5.
We have also to verify if our data is compatible.
That's the documented example. That's promising. We have to look on the boolean syntax. I changed for the example False to None.

in moinmoin the help information is generated automatically from the decriptions in the source
result:
http://moinmo.in/HelpOnConfiguration#Access control lists
source: https://github.com/moinwiki/moin-1.9/blob/master/MoinMoin/config/multiconfig.py#L753
The new editor has to show the meaning of the keys
Also the saved file has only to store changed from default.
On loading a minimum set of changes the editor should also show what can be changed

Realized as part of GSOC2021.


Keep rasa server on

Rasa NLU version (0.7.3):
Used backend / pipeline (spacy):
Operating system (ubuntu 16.04):
Issue:
How to keep rasa server on ?
I need to keep the rasa server on, the moment I log out from my terminal (ubuntu) it closes down.

Thanks
Content of configuration file (if used & relevant):

I'd recommend using docker, but if you need an alternate solution try this SO thread https://stackoverflow.com/questions/24518522/run-python-script-at-startup-in-ubuntu


Screenshots?

Hey mate!
Could you add some screenshots to the README.md? If you haven't by tomorrow i'll give it a shot (:
Thanks!

done!


Offer full support for customized/ non-prod DevOps API URL root

General problem: assuming prod in the devops API (url) vs keeping it simple for the happy path of prod usage.
Idea from a conversation:
There is no way to "spawn" a DBOps object from the general AstraDB. If there were one, then I would tell you:

regular usage would have users "spawn" an Ops from their main AstraDB instance, which would have an .ops() method spawning an AstraDBOps. That method would sound like this:

  def ops(self, dev_ops_url=None):
    if dev_ops_url is None and self.base_url = <production api url>:
        dev_ops_url = <prod OPS url>
   return AstraDBOps(self.api_key, dev_ops_url=dev_ops_url)```

#48 should address this i hope, let me know @hemidactylus


WIP: Tests

Hello @Honny1! Thanks for opening this PR.


User boopathy -> Master

-GDPR
-Root key
-URLSession issue fix
-getAllRelatedList

Completion Handler added

ZCRMModuleRelation metadata vs data changes.
Completion handler to include entity.
getRecords methods args order check.

It should merge with PRE_RELEASE branch before merging with the master branch.