Expand Testing Guides to include Cypress

Currently, our testing guide page states the following:

Testing helps you write and maintain working Astro code. Astro supports many popular tools for unit tests, component tests, and end-to-end tests including Jest, Mocha, Jasmine, Cypress and Playwright.

However, the page only has a mention for how to integrate Playwright into E2E testing for Astro apps.
It would be awesome to see similar content for Cypress, since it's explicitly mentioned as well.

Yes! We would love to have more testing info expanded to incorporate different testing platforms!
This page was created in response to a community submission specifically to document their own Playwright setup. I built up a fuller page "around it" prepared to add/accept more testing information, so absolutely, our community can consider this page "Open For PR Business"  🚀

@sarah11918 I will take care of this guide, feel free to assign the issue to me

@bandantonio Done! Happy to answer any questions here or in the docs channel, but I think our initial discussion shows we're on the same page. So, looking forward to see what you come up with!  🙌


Is flash-attn still necessary?

Using the latest depo I encounter the error:
  File "D:\PythonProjects\genmoai-smol\src\mochi_preview\dit\joint_model\asymm_models_joint.py", line 8, in <module>
    from flash_attn import flash_attn_varlen_qkvpacked_func
ModuleNotFoundError: No module named 'flash_attn'

If I install flash-attn wheels (Windows, Python 3.10) from author's HuggingFace and run inference I see
    import flash_attn_2_cuda as flash_attn_cuda
ImportError: DLL load failed while importing flash_attn_2_cuda: The specified procedure could not be found

Not anymore! Pull the latest release and follow the instructions in the README.


S3 Blobstore Client does not follow 301 MOVED PERMANENTLY responses

Amazon recently moved one of our S3 buckets from US Standard to Oregon without notifying us and just left a lot of 301 redirects in place of the files that were once there. This makes the blob syncing part of creating a release fail now with this error:
$ bosh create release --force
/var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/blobstore_client/lib/blobstore_client/simple_blobstore_client.rb:43:in `get_file': Could not fetch object, 301/ (Bosh::Blobstore::BlobstoreError)
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/blobstore_client/lib/blobstore_client/s3_blobstore_client.rb:88:in `get_file'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/blobstore_client/lib/blobstore_client/base.rb:50:in `get'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/blobstore_client/lib/blobstore_client/sha1_verifiable_blobstore_client.rb:19:in `get'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/blobstore_client/lib/blobstore_client/retryable_blobstore_client.rb:19:in `block in get'
	from /var/vcap/store/gems/2.0.0p353/deploy/gems/bosh_common-1.5.0.pre.1244/lib/common/retryable.rb:21:in `block in retryer'
	from /var/vcap/store/gems/2.0.0p353/deploy/gems/bosh_common-1.5.0.pre.1244/lib/common/retryable.rb:19:in `loop'
	from /var/vcap/store/gems/2.0.0p353/deploy/gems/bosh_common-1.5.0.pre.1244/lib/common/retryable.rb:19:in `retryer'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/blobstore_client/lib/blobstore_client/retryable_blobstore_client.rb:18:in `get'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/blob_manager.rb:295:in `download_blob'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/blob_manager.rb:230:in `block in process_index'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/blob_manager.rb:211:in `each_pair'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/blob_manager.rb:211:in `process_index'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/blob_manager.rb:155:in `sync'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/commands/release.rb:350:in `dirty_blob_check'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/commands/release.rb:300:in `create_from_spec'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/commands/release.rb:48:in `create'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/command_handler.rb:57:in `run'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/runner.rb:59:in `run'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/lib/cli/runner.rb:18:in `run'
	from /var/vcap/store/gems/2.0.0p353/deploy/bundler/gems/bosh-1e760331719a/bosh_cli/bin/bosh:7:in `<top (required)>'
	from /var/vcap/store/gems/2.0.0p353/deploy/bin/bosh:23:in `load'
	from /var/vcap/store/gems/2.0.0p353/deploy/bin/bosh:23:in `<main>'

We're going to be moving the bucket back to the original region but it would be nice if the BOSH blobstore client understood redirect status codes and handled them with the correct semantics.

@cppforlife, is this likely fixed since the s3cli merge in https://github.com/cloudfoundry/bosh/commit/01c6ab0ea96f162ffb82dfb8eb38379b5c8d95fc / since stable-3232?

Buildpacks team just got bitten by this. We consider it a bug.
If following redirects automatically will not be supported behaviour, it would be super duper helpful to get something other than an inscrutable stacktrace.
For example, something like
Looked for blob name-of-binary in us-east-1, but was redirected to us-west-2. BOSH will not follow redirects.

Closing - this should no longer be an issue with the go client used by director and new bosh-cli.


Broken colors after upgrade VS to 16.3.4

Hi,
After upgrading vs to 16.3.4, the colors in the text editor are broken. Disabling this extension fixs the problem.

I'm not sure what caused the problem now, because the problem emerged again somehow with this extension disabled.

I'm see odd behavior in syntax highlighting in the text editor as well. Seems like lately the updates have been a bit jarring introducing behavior changes that come and go.


Running LLaVA_OneVision_Tutorials.ipynb reports an ValueError: Unknown vision tower: google/siglip-so400m-patch14-384

ValueError                                Traceback (most recent call last)
 in <cell line: 5>()
3
4 # Load the pre-trained model without passing the vision_tower parameter
----> 5 tokenizer, model, image_processor, max_length = load_pretrained_model(
6     pretrained,
7     None,
5 frames
/usr/local/lib/python3.10/dist-packages/llava/model/multimodal_encoder/builder.py in build_vision_tower(vision_tower_cfg, **kwargs)
13             return CLIPVisionTower(vision_tower, args=vision_tower_cfg, **kwargs)
14
---> 15     raise ValueError(f'Unknown vision tower: {vision_tower}')
ValueError: Unknown vision tower: google/siglip-so400m-patch14-384
Is there any way to solve the Unknown vision tower problem?

`import os
from transformers import AutoModel, logging
Suppress warnings (optional)
logging.set_verbosity_error()
Model identifier
model_name = "google/siglip-so400m-patch14-384"
Check if the model is already cached
cache_dir = "~/.cache/huggingface/hub"  # Default cache directory
model_path = os.path.join(cache_dir, "models--google--siglip-so400m-patch14-384")
if os.path.exists(model_path):
print(f"Model '{model_name}' is already cached at: {model_path}")
else:
print(f"Model '{model_name}' is not cached. Downloading...")
# Download the model
try:
    _ = AutoModel.from_pretrained(model_name)
    print(f"Model '{model_name}' downloaded successfully!")
except Exception as e:
    print(f"Error downloading model '{model_name}': {e}")`


Is ther any chance to  change DeathStartBench into Serverless mode?

Hi there,
I try to modify the services into such a situation that, all services is down untile a request is arrive, and the contianers will auto turn up to deal with the request and go to destory after send the response.
Is ther any useful suggestions? Or some others ideas to make the benchmark more flexable and useful!

I transfered this benchmark to k8s, and Google's serverless platform knative seems base on k8s, you may try it.


api_analysis_exploration: add r3 experiment

This includes propagation of exports, so the summary produced should be fairly comprehensive.
One can analyse a local package to obtain a full summary, or a hosted package, in which case all appropriate versions are analysed and the differences displayed.
It remains to add a README description.

@jonasfj


versions.json not deployed correctly

https://storybook.js.org/versions.json
Should contain the latest versions.json that I uploaded in master, but instead contains the auto-generated one.

Yay!! I just released https://github.com/storybooks/storybook/releases/tag/v4.1.13 containing PR #5675 that references this issue. Upgrade today to try it out!


Js public unjoined teams

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?
-

What's in this Pull Request?
Added a new SPFx web part sample. The web part lists all the Teams the current user is not a member of and offers buttons for joining.

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

thx @LauraKokkarinen, really nice demonstration again on the usage of the Graph APIs. Would you be interested in doing a live demo of this one in the upcoming SPFx community calls? Would be typical setup with 10-15 min coverage on how the web part is implemented. Concentration on the Graph API model etc.


Create release and develop branches

Create release and develop branches and set up GitFlow

User Story:
As a developement team member,
I want to be able to work on new features in a separate branch,
So that my commits can be tested before put into the main branch.
Acceptance criteria:
Given IDE window open
When presss push and select develop branch
Then commits are pushed to the develop branch

User Story:
As a developement team member,
I want to be able publish stable release code in a separate branch,
So that it can be accesed when needed.
Acceptance criteria:
Given Github window opena nd new release created
When create pull request and merge
Then release branch is up to date


not working

I'm using Mattermost Version: 7.10.0 currently self hosted.
I've uploaded your plugin and enabled it but when I upload an mp4, nothing happens.
Everything looks like before.

What can I do and check why it is not working?

Same here, v1.1.1 of this plugin installed on Mattermost v9.0,0 no video player shows up for an uploaded .webm file.
Tried in a channel and tried in a thread.

Thanks for the reports. Since we are still using Mattermost 8.x on our server, I can't repoduce the errors yet. I will have a look at the problem with a Mattermost 9.x version locally in the near future. I suspect Mattermost has made some changes to their frontend API that I need to read up on.

This has nothing to do with v9.x.
It didn't work since 7.10 as in my first post.
8.x didn't work and it still doesn't work with 9.x

@Shadowsith I reseached this problem and fixed it here: https://github.com/Shadowsith/mattermost-plugin-videofile/pull/4
Could you merge it and release a new version with this fix?

@danilvalov thank you for analyzing the error, version 1.1.2 is now released has been tested on a Mattermost v9.5.0 server.


Is this project dead/unmentained? Should I fork?

Is this project completely dead?
There are crucial bugfixes unmerged for a long time.
If it's dead, I would like to fork.
I would like to merge in pull requests, implement mobile mode (maybe ability to send mobile bots to mobile rendered site and desktop bots to desktop render)...

Extension filter also highly needed...

One more feature:
QueryString remover.
Array of query string keys that should be removed from url if they do not influance render output. Should increase cache hit rate.

My updates are here: https://github.com/hheexx/AspNetCore.Rendertron
I will publish to nuget if there is no response for another 2 weeks.


Sort languages list vertically instead of horizontally

This is a pretty small user experience thing, but I think it would be better to sort the list of languages vertically instead of horizontally. This Stack Exchange answer explains why.
TL;DR: it's easier and faster to find stuff when vertically sorted

It seems your TL;DR is unintentionally reversed...

@jaccarmac it is, thanks for pointing that out. I’ve edited it.

Hi, I agree with @IvanFon point and the answer beautifully explains the point. Is anyone working on this ? If we need this I can send a PR for this.
@prathamesh-sonpatki @schneems

Sure go ahead and send the PR 👍


Question about deauther/troubleshooting.md

I have a question regarding the information on the Wiki at deauther/troubleshooting.md
Hello..thanks for the great tool/project.  I appreciate the time and research it must have taken to complete this.
I have a question I do not see an answer for in my research.  If I can see a certain device/wifi object while using the Scan function, how certain am I to be able to send packets that are meaningful?  I check the Attack page and I always see the same thing..namely 24/24  which is what I would expect if I am attacking and meaningful packets are being sent.
I hope I was clear in my question.
Thanks again and keep up the great work.

I'm not sure what you mean with "meaningful packets" but if you find a device you can be sure you're able to send deauth-packets.


ERR! enable Couldn’t find a repo with this slug. Either it doesn’t exist on GitHub, it’s a fork, or private.

┌─[wulfsolter@Wulfs-MBP]-[2015-10-09 00:58 -<PHONE_NUMBER>]-[~/Code/mongo-express] (master)
└─[$]-> greenkeeper -v
2.1.1

┌─[wulfsolter@Wulfs-MBP]-[2015-10-09 00:58 -<PHONE_NUMBER>]-[~/Code/mongo-express] (master)
└─[$]-> git remote -v
origin  git@github.com:andzdroid/mongo-express.git (fetch)
origin  git@github.com:andzdroid/mongo-express.git (push)

┌─[wulfsolter@Wulfs-MBP]-[2015-10-09 00:58 -<PHONE_NUMBER>]-[~/Code/mongo-express] (master)
└─[$]-> greenkeeper enable
🌴  info enable The GitHub slug is: andzdroid/mongo-express
🌴  ERR! enable Couldn’t find a repo with this slug.
🌴  ERR! enable Either it doesn’t exist on GitHub, it’s a fork, or private.

┌─[wulfsolter@Wulfs-MBP]-[2015-10-09 00:58 -<PHONE_NUMBER>]-[~/Code/mongo-express] (master)
└─[$]-> greenkeeper enable --slug andzdroid/mongo-express
🌴  info enable The GitHub slug is: andzdroid/mongo-express
🌴  ERR! enable Couldn’t find a repo with this slug.
🌴  ERR! enable Either it doesn’t exist on GitHub, it’s a fork, or private.

https://github.com/andzdroid/mongo-express is a public repo to which I have write access, and I have tried gk logout && gk login.

Hey @wulfsolter,
thank you for this issue. Do you have admin rights? They're required to enable repos, because we need to create some webhooks for you.
We've just pushed a new version of the CLI that better explains the error you encountered.
Best,
Stephan

Just realized that the repo you're trying to enable is a personal repo of another GitHub user, which unfortunately means you can't enable it for them, because you can't have admin access on it.
Best,
Stephan

Hmm. Greenkeepr worked the first time on this repo as installed by me, made
commits to lock in versions and a few upgrades. On the 30th Sept you sent
me a very kind email of apologies for falsely attributed PRs (
https://github.com/kentcdodds/invoke-filter/pull/7 ), but it hasn't worked
since.
While I am not the creator of this repo, I do have admin ability - to
create and merge PRs.
Closed #48 https://github.com/greenkeeperio/greenkeeper/issues/48.
—
Reply to this email directly or view it on GitHub
https://github.com/greenkeeperio/greenkeeper/issues/48#event-430682515.

Hey @wulfsolter,
we allowed enabling for a short time, because we didn't enforce the required rights. In this case the webhooks enabling failed and we could never sync your package.json content, which is required to send you PRs for all dependencies.
We're working on manual webhooks enabling, so admin rights are no longer required to be granted to us (https://github.com/greenkeeperio/greenkeeper/issues/46), but with that working GitHub would still require this to be done by @andzdroid.
Thanks for understanding
Best,
Stephan
// cc @christophwitzko


LibWeb: Request cursor change, leave tooltip area, and unhover link only when needed

Previously: https://github.com/SerenityOS/serenity/pull/24039

@trflynn89 requesting review.


Support creating indexes with descending ordering.

          I'm not sure whether we've supported it, but we can specify `DESC` order when creating index in postgres (which is often used along with `NULLS FIRST/LAST`). So maybe we should not hard-code an `Asc` here, but use `index_table.pk` instead.

cc @chenzl25
Originally posted by @BugenZhao in https://github.com/risingwavelabs/risingwave/pull/7726#discussion_r1098195637

Creating indexes with descending ordering is basically supported. The remaining part is to support Null First or Null Last. We will use another issue for tracking.


ci: merge staging to master

This is an automatic PR generated by the pipeline CI/CD. This will be automatically fast-forward merged if successful.

Pipeline Attempt on<PHONE_NUMBER> for 07e2cbede755a6e2be13a70e0b1ae3b33939c8f6
https://gitlab.com/MatrixAI/open-source/js-mdns/-/pipelines/1045605062

Pipeline Succeeded on<PHONE_NUMBER> for 07e2cbede755a6e2be13a70e0b1ae3b33939c8f6
https://gitlab.com/MatrixAI/open-source/js-mdns/-/pipelines/1045605062


fix: Regression in generalized ValueDeserializers

This change is necessary if https://github.com/serde-rs/serde/pull/166 is merged. More information in the linked PR.

There were the following issues with your Pull Request

Commit: f69e7b21cee04e25586b9233c4bfcabf426af0c2
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/serde-rs/json

This message was auto-generated by https://gitcop.com

There were the following issues with your Pull Request

Commit: da7ae95a7d0c296dfb41dc2a05cb87d8432d579b

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: c07920f9d39aaae421a80397bdb4b462db71d854

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 45d87f74e7c535e53336af1d2313bb462ad7e513

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: c8cd1b947ff6fe368a3153c208b2e0bf601100db

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: aea44fce0632447611461075605f2a41f6efe3e4

Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/serde-rs/json

This message was auto-generated by https://gitcop.com

There were the following issues with your Pull Request

Commit: 8798f87980e97fcede8bddc3e1cad1bfda2e6d5f

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: fbb7d9ffb83447efe7637c12558ea36e099e8688

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 6e4dcd7050b22bfb2f4271a8ff2bda19d573690a

Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/serde-rs/json

This message was auto-generated by https://gitcop.com

This PR builds and tests successfully against https://github.com/serde-rs/serde/tree/27c933a86548601027fc68bb7daf8082de819c10.

:umbrella: The latest upstream changes (presumably #31) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably c53ce95) made this pull request unmergeable. Please resolve the merge conflicts.

This has actually landed since serde 0.7 was released!


Undefined method change_contents for RubyXL::Cell

Using rubyXL 3.4.2 or 3.4.0 and either ruby 2.6.2 or 2.5.3, this code causes an exception:
require 'rubyXL'
workbook = RubyXL::Workbook.new
worksheet = workbook[0]
worksheet.add_cell 0, 0, 'hi'
worksheet[0][0].change_contents 'there'

The exception is:
NoMethodError (undefined method `change_contents' for #<RubyXL::Cell(0,0): "hi", datatype="str", style_index=0>)

The code works fine in rubyXL 3.3.33. Did the spec change for 3.4.0? (The README.rdoc still specifies the change_contents method.)

README.rdoc also has a new section added explicitly mentioning 3.4.0 and what should you do.


be able to pass undefined or null as mapStateToProps

Hello
I often need to connect only actions to my component. So I write:
@connect(
  ()=>{return{}},
  (dispatch) => {
    return {
      actions: bindActionCreators(informationActions, dispatch)
    };
  }
)

I read in documentation:

[mapStateToProps(state, [ownProps]): stateProps] (Function): If specified, the component will subscribe to Redux store updates. Any time it updates, mapStateToProps will be called. Its result must be a plain object*, and it will be merged into the component’s props. If you omit it, the component will not be subscribed to the Redux store. If ownProps is specified as a second argument, its value will be the props passed to your component, and mapStateToProps will be re-invoked whenever the component receives new props.

"If specified" lets me think we can use connect() without defining mapStateToProps
So I tried:
@connect(null,
  (dispatch) => {
    return {
      actions: bindActionCreators(informationActions, dispatch)
    };
  }
)

But it didn't work. it makes sens to be able to connect actions only, isn't it? Is there a better way than writing  ()=>{return{}}? Otherwise I can try to implement it in React-Redux. Let me know.

Actually it works... a side effect from another connect() triggered my issue. My bad!

Writing looks better () <> {} 😉


parallelize IModelApp.startup

also:

make default Localization be ITwinLocalization rather than empty
remove optional Localization argument for Tool.register (breaking)
fix hypermodeling tests

@bsteinbk I'd say in a separate PR and sounds good. I think with the removal of that setup takes away the main reason to even have those initialize methods on all of the managers which would be fantastic to remove :)

@kabentley I can merge this, it's a mess now that I merged the line endings PR, sorry...

@kabentley I can merge this, it's a mess now that I merged the line endings PR, sorry...

thanks, but i've already started it.

@kabentley ah okay, sounds good. I'll abandon mine then.


resets counter sometimes ignored

Hello everyone, sometimes prometheus handle multiple resets during service restarts, for example on screen you can see one resets on host and 20 resets on other host (one service per host).

Now request counter metrics are:

And finally, in grafana we see huge spike in the service rps (+3 GMT)

Is it bug or why prometheus handle 20 resets on service restart sometimes?
Environment

Prometheus version:

Version 2.12.0
Revision: 43acd0e2e93f9f70c49b2267efa0124f1e759e86
BuildUser: root@7a9dbdbe0cc7
BuildDate: 20190818-13:53:16
GoVersion: go1.12.8

There's insufficient information here to indicate a bug, so I have to presume this is actually a support request.
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Build failed for UI - Linux, Fedora 31

Using the Hygieia/UI/ directory, ran mvn clean package integration-test and got this output:
[INFO] --- frontend-maven-plugin:1.6:install-node-and-npm (install node and npm) @ UI ---
[INFO] Node v6.9.1 is already installed.
[INFO] NPM 5.0.1 is already installed.
[INFO]
[INFO] --- frontend-maven-plugin:1.6:npm (npm install) @ UI ---
[INFO] Running 'npm install --ignore-scripts' in /home/mjaffe/work/DashBoards/Hygieia/UI
[INFO] up to date in 6.525s
[INFO]
[INFO] --- frontend-maven-plugin:1.6:gulp (gulp build) @ UI ---
[INFO] Running 'gulp build' in /home/mjaffe/work/DashBoards/Hygieia/UI
[INFO] [17:00:10] Using gulpfile ~/work/DashBoards/Hygieia/UI/gulpfile.js
[INFO] [17:00:10] Starting 'build'...
[INFO] [17:00:10] Starting 'clean'...
[INFO] [17:00:10] Finished 'clean' after 202 ms
[INFO] [17:00:10] Starting 'assets'...
[INFO] [17:00:10] Starting 'themes'...
[INFO] [17:00:10] Starting 'fonts'...
[INFO] [17:00:10] Starting 'js'...
[INFO] [17:00:10] Starting 'views'...
[INFO] [17:00:10] Starting 'test-data'...
[INFO] [17:00:19] Finished 'themes' after 8.46 s
[INFO] [17:00:19] Finished 'assets' after 8.48 s
[INFO] [17:00:19] Finished 'fonts' after 8.49 s
[INFO] [17:00:19] Finished 'test-data' after 8.62 s
[INFO] [17:00:19] Finished 'views' after 8.74 s
[INFO] [17:00:19] Finished 'js' after 8.79 s
[INFO] [17:00:19] Starting 'html'...
[INFO] [17:00:29] 'html' errored after 9.38 s
[INFO] [17:00:29] RangeError: Maximum call stack size exceeded
[INFO]     at /home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:149:29
[INFO]     at /home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/lodash/lodash.js:4905:15
[INFO]     at baseForOwn (/home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/lodash/lodash.js:2990:24)
[INFO]     at /home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/lodash/lodash.js:4874:18
[INFO]     at Function.forEach (/home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/lodash/lodash.js:9342:14)
[INFO]     at /home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:183:11
[INFO]     at /home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/lodash/lodash.js:4905:15
[INFO]     at baseForOwn (/home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/lodash/lodash.js:2990:24)
[INFO]     at /home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/lodash/lodash.js:4874:18
[INFO]     at Function.forEach (/home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/lodash/lodash.js:9342:14)
[INFO]     at /home/mjaffe/work/DashBoards/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:183:11
[INFO] [17:00:29] 'build' errored after 18 s
[INFO] [17:00:29] Error in plugin 'run-sequence'
[INFO] Message:
[INFO]     An error occured in task 'html'.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 37.711 s
[INFO] Finished at: 2020-01-21T17:00:29-08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:gulp (gulp build) on project UI: Failed to run task: 'gulp build' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]

@Jaff  We are seeing the same issue on Mac also. Did you find any resolution for the same?


Change of Delimiter does not work correct for SQLite

I would create the following two tables in a SQLite Database by using flyway:
CREATE TABLE my_patch_level
  (
    db_id                     INTEGER PRIMARY KEY autoincrement,
    db_level                  NUMBER (3) NOT NULL ,
    db_svn                    VARCHAR2 (35) NOT NULL ,
    db_zp_beginn              DATE NOT NULL ,
    db_zp_ende                DATE
   ) ;
CREATE TABLE adr_verfahren
  (
    vrf_id   INTEGER PRIMARY KEY autoincrement ,
    vrf_knz  VARCHAR2 (3) NOT NULL ,
    vrf_name VARCHAR2 (80) ,
    vrf_zid  NUMBER (12) ,
    vrf_dm   DATE DEFAULT (datetime('now','localtime'))
  ) ;

After executing the script with flyway - there has been created only one table without any exception.
I have debug flyway. The class SQLiteSqlStatementBuilder overrides the method changeDelimiterIfNecessary. In this method flyway checks if it is necessary to change the delimiter. This is useful for database-specific stored procedures or trigger. But in my case - there is no stored procedures or trigger.
Due the column db_zp_beginn (in my first table) the following code assigned the field insideBeginEndBlock to true and the method returns null for the delimiter and flyway puts all the following statemets to the current statement.
Here the code:
    @Override
    protected Delimiter changeDelimiterIfNecessary(String line, Delimiter delimiter) {
        if (line.contains("BEGIN")) {
            insideBeginEndBlock = true;
        }

        if (line.endsWith("END;")) {
            insideBeginEndBlock = false;
        }

        if (insideBeginEndBlock) {
            return null;
        }
        return getDefaultDelimiter();
    }

The condition for setting the field insideBeginEndBlock should be fixed. There could also be a problem if I would insert a text in a column which contains begin or if I have a column such as beginners.

Thanks for researching this! Fixed.


i18n(pt-BR): update guides/typescript.mdx

Changes to match main original file commit 9d4f1c6

Description (required)
Update pt-br/guides/typescript.mdx to match en/guides/typescript.mdx

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Thanks @viniciusdeliz, I can see there are a few missing commits to apply to the translation here, could you take a look and update accordingly? https://github.com/withastro/docs/commits/main/src/content/docs/en/guides/typescript.mdx?since=2023-10-23T20:48:38.000Z

@Yan-Thomas I've just ingested the latest changes and fixed some inconsistencies in the Portuguese version.


undefined reference to `app_main' with native build

esp-test-error-fixed.zip. I added
#[export_name = "app_main"]
extern "C" fn dummy() {}

to get it working.
I have the latest ldproxy (ldproxy-0.2.0).
Seems like the dummy cmake project isn't being includedin the native build?
CC: @N3xed

Having an app_main symbol defined by default is a tricky topic. For one, esp-idf-sys (and its friends like esp-idf-hal, esp-idf-svc) might be pulled in as a dependency in CMake-first/PIO-first projects with a mixed C/Rust codebase, where the app_main symbol might already be defined in C, and the developer might want to leave it like that.
With that said, we do have the means to automatically define an app_main symbol, which does call a Rust main symbol that the user should provide here, however it currently lives in the esp-idf-svc crate, so you should pull a dependency on that.
It works as follows:

If you are building a STD binary crate (typical case for cargo-first builds), the above code gets triggered automatically (because the binstart feature is part of default).
If you are building a library crate (the usual scenario for CMake-first and PIO-first projects), binstart cannot be even used, as it works for binary crates only. Instead, there is a libstart feature but it is not default. It has less features compared to binstart but it still night be useful, but the user should opt-in.

With all of the above said... the questions are:

Shall we move the start.rs code from  esp-idf-svc to esp-idf-sys? Perhaps yes, because even though esp-idf-sys is supposed to model the ESP-IDF unsafe API only, it already does have a few small utilities, and furthermore, it models the building and linking of ESP-IDF builds too, so perhaps start.rs belongs here. Jut like the panic_handler definition is already here. Btw it should also be protected by a feature flag, as the user might want to override it.
Shall we leave the binstart feature enabled by default? Perhaps yes, as this gives more ergonomics to cargo-first projects that do build a binary crate, at the expense of less ergonomics for CMake-first and PIO-first projects that currently cannot use the default feature of esp-idf-sys (currently esp-idf-svc).


chore(rust): Resolve Ignored Tests in Secure Channel

Current behavior
Few tests are ignored in Secure Channel
Proposed changes
This PR tries to resolve the issue which cause these test to fail and being ignored
Closes #8409

Test03 is working fine. So i removed #ignore tag
For run_04_inlet_outlet_separate_processes_secure_channel_via_ockam_orchestrator
Its till failing... The probable issue for this is 1.node.ockam.network:4000 and currently there is no alternative for it. as mentioned here


script responding error - with cloud license server

Exception: Authentication Error: Response code: 401. Please verify ls url or cls id, username and password and try again

We are looking into this issue.

Hey, any updates on this? I'm trying to run the script and I'm getting the same error. Thank you very much

using LS_USERNAME=admin solved my issue when trying to connect to a cloud license server


jamomacore: remove as unmaintained

Motivation for this change
This library is broken since years, upstream has no activity since 2015 for this library
I found one application using it which looks unmaintained also, so removed it too
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Can you rebase this branch on master to fix the eval error?

I am ok to add this software, but:

as the previous was broken since ages, I suppose nobody use it currently
I am not sure what their "release" suffix a19 means, but from other tags I guess alpha, and the fetch phase doesn't work:

From https://github.com/ArashPartow/exprtk
 * [new branch]      master     -> origin/master
fatal: reference is not a tree: d312ba91419c9cb12c8279fd3a19096d39dfcb5e
Unable to checkout d312ba91419c9cb12c8279fd3a19096d39dfcb5e from https://github.com/ArashPartow/exprtk.

I am not sure what their "release" suffix a19 means, but from other tags I guess alpha, and the fetch phase doesn't work:

In that case I think it's best to wait for the 3.0.0 stable

@freezeboy please resolve the merge conflict.

@freezeboy please resolve the merge conflict.

Rebased, i also gave another try to build ossia-score to follow @prusnak's idea but still no success apparently they don't provide all the files in the source tgz.

Rebased, i also gave another try to build ossia-score to follow @prusnak's idea but still no success apparently they don't provide all the files in the source tgz.


How long does it take to process a point cloud

About the timeliness，how long does it take to process a point cloud ?

The test time is different for different platforms, you can run to test it.


Drawing-caused Darkness isn't greyscale when seen with Darkvision

Details:

Pathfinder 2e system
Rules-based Vision on
Scene darkness 0
Drawing darkness 1 (set in lighting tab, with Override and Active toggled)
A light is right outside the door (the tokens are on the inside).

Images:
GM perspective

Creature with darkvision

Creature without darkvision

Creating with darkvision, when the scene darkness is set to 1 (this is correct, and the saturated part is caused by the light)

You have to check the override checkbox of Saturation Level in this situation, otherwise the drawing inherits the saturation level of the scene, which is linked to the scene darkness and is 1 because the darkness level of the scene is 0.


Show list of possible chips by just pressing space

Feature
Feature Request
When seeing possibilities in the drop down of an autocomplete chip make the space key reveal all of the possibilities instead of just the ones that contain a space.
What is the expected behavior?
currently hitting just space shows only...
'need more?'
Because that is the only example chip that has a space in it.
Instead the chip suggestion after hitting space should be...
'stepper',
'expansion-panel',
'markdown',
'highlight',
'loading',
'media',
'chips',
'http',
'json-formatter',
'pipes',
'need more?',
What is the motivation / use case for changing the behavior?
Because we want to display all the possible choices to the user, sometimes they can't remember them, and they end up typing different letters trying to get the right choice to come up.  Space should cause them all to appear.
Did this work in previous versions of Angular / Material?
I don't think so.

All the possibilities are shown now with https://github.com/Teradata/covalent/pull/459 since we replaced the native datalist with md-autocomplete

Ok sounds great.  Any knowledge of a release date on that?

When material releases beta.3 we will release ours since we need to merge this PR first https://github.com/Teradata/covalent/pull/464

Closing this since the new chips a11y has been merged


CC-5576: Use SslContextFactory.Server to disable server-side hostname verification

Jetty recently enabled hostname verification by default, but this
only makes sense for clients. They introduced a new subclass that
should be used in server contexts.

@rayokota I pushed an additional commit that partially reverts 4b0bcc441e8

LGTM for the partial revert


Minor changes preparing for v0.6

Minor changes introduced in order to prepare the package for v0.6:

[x] VERSION < v"0.6" added, since the previous implementation
was failing in juliabox.com with the v0.6-dev kernel,
[x] Relaxed the build matrix in .travis.yml file,
[x] Changed from Array(T, n) to Vector{T}(n) to get rid of the
deprecation warnings, and,
[x] Fixed convert rules in two ways: (1) added map version to the
AbstractArray case to cover for everything, (2) removed the
promote_type section from conversions.

As for the last item above, convert{T,S}(::Type{Poly{T}}, n::S) should
ALWAYS convert to Poly{T}, not to Poly{promote_type(T,S)}.
Closes #100.

This looks good. Thanks


Remove function redundant parameters

sprintf函数中使用了冗余参数heading，从函数的使用意图出发，此参数并不必要

 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.


Problem with positioning

I've got problem with positioning opened select box.
It works bad only on chrome (testen on firefox and IE - works good).

It's angular bootstrap 's dropdown issue - not Yours.


[Models/ImageClassification] For transfer learning, apply @_Freezable property wrapper on all Layer conforming properties

This PR proposes to apply @_Freezable property wrapper on every property of image classification models that conforms to Layer protocol.
One thing I'd like to point out is that in some models like ResNet, VGG, EfficientNet, and others, the property wrapper is applied on the neural blocks instead of the layers contained in those neural blocks because, according to my best knowledge (please correct me if I'm wrong here), it is rare to freeze specific layers in neural blocks during transfer learning.
cc @BradLarson

@googlebot I fixed it.

@googlebot I fixed it.

@googlebot I fixed it.

Hi @rahulbhalley Thank you very much for putting this together. Unfortunately, I think we want to hold off on merging this in. Transfer learning is a really important use case to support well, and something we're actively thinking about carefully. @shadaj will be presenting some of our latest ideas at this Friday's open design meeting. I hope you're able to join in!

Ok.


Upgrade yeoman-generator to version 0.19.1

I've tried to upgrade the generator to the 0.19.1 API as it was using fs directly.
Let me know if there's something wrong.
BTW, I tried to use sinom to spy on the generator.log.error method for testing asserts but it seems to be already wrapped.

@alfonso-presa we should probably also replace calls to this.template() w/ this.fs.copyTmpl() right?

@alfonso-presa
I made a PR to your UpgradeGeneratorVersion branch which includes a couple of extra changes that I think help bring this more in line w/ the way things are supposed to work in yeoman 0.19, but I'll let @SBoudrias weigh in on whether or not I've got it right:
https://github.com/alfonso-presa/generator-karma/pull/1

Included @tomwayson changes and @SBoudrias comments to his PR. Thank you guys.

Added some comments about the code style and a bug I found.

@SBoudrias, thanks for the feedback. They should all be corrected in the last commit.
About the async()... I was expecting this to be necessary for the generator not to trigger the "end" event until the instalations have ended. In the past I've seen the "npm install" running at the same time when using one generator inside another (i.e. generator-angular) causing concurrency issues....is this solved in generator-yeoman 0.19?

It's been solved for a couple versions now. But the deadlocking issue is only in yeoman-generator since 0.18

Ok, thanks! Great to hear it's solved :-). I removed the async call in the last commit, so I guess everything is ok now.

Some new comments, went through the whole thing this time so it should be the last iteration of review comments :)

Minus the code style comments, LGTM2.

Sorry for the delay... here you have the changes.
By the way.. I've seen that when using this inside other generators based in older versions of yeoman-generator (for example generator-angular) it now displays conflict when generator-karma is editing package.json (even if the folder was initially empty).... Is there any way to solve this different than upgrading that generator to 0.19.x?

Looks like using inTmpDir breaks the build in travis due to a failing test. My guess is that in travis it's using the same tmp folder and it's not clearing it before running the tests. This is the failing build:
https://travis-ci.org/yeoman/generator-karma/builds/59006966
Changing back to inDir solved the issue...

Ok... it was my fault. For some reason in travis (probably because it's slower than my machine) it was ending the inTmpDir before it appends the onready event that adds the spy to the log error in the test. I rewrote the test to ensure the onready is attached.
I have already squashed the commits in case you wan't to merge.

Thanks a lot!!

Thank you!


Add formatter option to the VSCode extension

At this point this is an issue for discussing how the formatter can be implemented and how exactly the filter lists and individual rules should be formatted / sorted.
My initial idea is to sort the filter lists so that all rules for a given website were collected together. Something like this:
google.com###banner
||example.org^$domain=google.com
||google.com/test

At the same time we should take comments into account. Maybe allow grouping rules into a single section using special comments.
Anyways, lets discuss.
CC @AdguardTeam/filters-maintainers @maximtop @scripthunter7

We also should consider to keep the formatting in sync with the planned code guidelines: https://github.com/AdguardTeam/CodeGuidelines/issues/16

Not clear how to resolve cases when one comment is related to a group of rules

@maximtop we can provide special rules for that, something like this:
! block start

! block end

If we introduce such rules, perhaps it would make sense to follow the pattern of preprocessor directives:
!#section
rules
!#endsection

IMO, formatter and linter are different things and mixing them together may be confusing.
At the same time, it does not mean that AGLint cannot enforce formatting rules, it can rely on the formatter for that.

My initial idea is to sort the filter lists so that all rules for a given website were collected together.

We use this approach for some sites. In general it is not a good idea to apply it for all rules, because some rules can be applied to many sites, they can have mirrors (not only with different TLD), and they merged into one large rule.

At the same time we should take comments into account. Maybe allow grouping rules into a single section using special comments.

In some cases we are using Comment Anchors to improve file navigation
! SECTION: Cookies - Popular rules
||rule1.com^
||ruleN.com^
! NOTE: Popular rules end ⬆
! !SECTION: Cookies - Popular rules

How it looks:

Automatically creating groups will not improve convenience.
As written above - there may (will) be problems with existing groups, directives and hints.
Previously never felt the need to create a separate group for each site. This may be handy for the hotfixes filter, but not for the main filters.

The problem with the current structure in AdguardFilters is that it's hard to understand where to add a new rule unless you already have lots of experience working with it. I don't think we should take it as an example. Instead of that, let's think what structure would be reasonable to use if we were creating a new list from scratch.

IMO, formatter and linter are different things and mixing them together may be confusing.
At the same time, it does not mean that AGLint cannot enforce formatting rules, it can rely on the formatter for that.

@ameshkov ESLint also drops formatting rules: https://eslint.org/blog/2023/10/deprecating-formatting-rules/


Bug in compiler with as?(Array)

Ok so this isn't causing me any actual problems, but it does say to report bugs in the compiler so here goes:
class AllowedParams
  property raw

  def initialize()
    @raw = {} of Symbol => Array(String) | Array(Float64)	# also works if i remove either of these
  end

  def []?(k)
    @raw[k]?
  end
end

allowed_params = AllowedParams.new

#Works
#puts "#{allowed_params["param1"]?.as?(Array(String))}"

#Nice compiler message about Unhandled Exception
#puts "#{allowed_params["param1"]?.as(Array)}"

#Bug in compiler
puts "#{allowed_params["param1"]?.as?(Array)}"

I'm on:
Crystal 0.34.0 (2020-04-07)
LLVM: 10.0.0
Default target: x86_64-apple-macosx
Thanks for all your work!

The error message for posterity
https://carc.in/#/r/94ic
Module validation failed: Call parameter type does not match function signature!
i32* %value
 %"Array(Float64)"*  %5 = call %String* @"*Array(Float64)@Object#to_s:String"(i32* %value), !dbg !898
Call parameter type does not match function signature!
i32* %value
 %"Array(String)"*  %7 = call %String* @"*Array(String)@Object#to_s:String"(i32* %value), !dbg !898
 (Exception)
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from __crystal_main
  from main
  from __libc_start_main
  from _start
  from ???
Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

Duplicate of #9249?

Duplicate of #9249?

No. The LLVM error message is the same, but that error message is very common.

as? doesn't work as well as as for some reason. I personally avoid it because I now that's true. I don't know why, though.

Reduced:
struct Nil
  def foo
    "Nil"
  end
end

class Gen(T)
  def foo
    "foo"
  end
end

a = Gen(String).new || Gen(Int32).new
a.as?(Gen).foo


feat: fix recurring end date upon deletion

Brief description. What is this change?

Cancel All Following Donations, End Date Still the Same

Implementation description. How did you make this change?

Found maximum date remaining after deletion and updated all objects with the same recurring_donation_id to have this updated date -> found this to be the simplest solution because the frequency makes the ability to just subtract the date to be more difficult /  more code. Sequelize has a nice function for this.
Some error prevention in the sense that you cannot update the end recurring date if the object with that recurring_donation_id no longer exists. I used the count function for this, but am open to quicker / more efficient methods here.
Refactored common test objects to be under a testUtils folder but not sure if I placed correctly (we discussed this in the first recurring deletion backend tickets.
Added one more test for this use case and as a result had to add more objects to the testSchedules object

Steps to test

Create a recurring donation
Try to delete "this and following recurring donation" on of the donations in the middle in time of the beginning to end date. Remember this date. Refresh donation page and make sure it is one day less than the date you remembered.
Can delete the very first item and make sure that no error is thrown (for point 2 under implementation details)

Checklist

[X] My PR name is descriptive and in imperative tense
[X] My commit messages follow conventional commits and are descriptive. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
[X] I have run the appropriate linter(s)
[X] I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR
[X] The appropriate tests if necessary have been written

Also could someone else test - while filming the demo I scheduled a recurring one for 11am - 12pm that repeats daily and one for 12pm - 1pm that repeats daily and if i delete recurring... it actually deletes everything bc both events have the same recurringDonationId?? I have videos of this if need for confirmation.

@Shehryar21
[{"id":"40","donorId":"1","categories":["Dry packaged goods"],"size":"Medium","isPickup":false,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2021-12-15T12:00:00.000Z","endTime":"2021-12-15T13:00:00.000Z","status":"Approved","volunteerNeeded":true,"volunteerTime":"8:00 AM","volunteerIds":[],"frequency":"One time donation","recurringDonationId":"null","recurringDonationEndDate":null,"notes":"these are the notes"},{"id":"43","donorId":"1","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Small","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-01-18T00:00:00.000Z","endTime":"2022-01-18T01:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"One time donation","recurringDonationId":"null","recurringDonationEndDate":null,"notes":""},{"id":"429","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Early Morning (12am - 6am)","startTime":"2022-01-26T08:00:00.000Z","endTime":"2022-01-26T09:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"4","recurringDonationEndDate":"2022-01-31T05:52:14.000Z","notes":""},{"id":"462","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Early Morning (12am - 6am)","startTime":"2022-01-27T08:00:00.000Z","endTime":"2022-01-27T09:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"7","recurringDonationEndDate":"2022-03-31T04:56:52.000Z","notes":""},{"id":"380","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)","Essential items (masks, hand sanitizer, bags)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-01-27T22:00:00.000Z","endTime":"2022-01-27T23:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"1","recurringDonationEndDate":"2022-02-26T03:22:37.000Z","notes":""},{"id":"381","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)","Essential items (masks, hand sanitizer, bags)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-01-28T22:00:00.000Z","endTime":"2022-01-28T23:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"1","recurringDonationEndDate":"2022-02-26T03:22:37.000Z","notes":""},{"id":"382","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)","Essential items (masks, hand sanitizer, bags)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-01-29T22:00:00.000Z","endTime":"2022-01-29T23:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"1","recurringDonationEndDate":"2022-02-26T03:22:37.000Z","notes":""},{"id":"383","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)","Essential items (masks, hand sanitizer, bags)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-01-30T22:00:00.000Z","endTime":"2022-01-30T23:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"1","recurringDonationEndDate":"2022-02-26T03:22:37.000Z","notes":""},{"id":"384","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)","Essential items (masks, hand sanitizer, bags)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-01-31T22:00:00.000Z","endTime":"2022-01-31T23:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"1","recurringDonationEndDate":"2022-02-26T03:22:37.000Z","notes":""},{"id":"385","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)","Essential items (masks, hand sanitizer, bags)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-02-01T22:00:00.000Z","endTime":"2022-02-01T23:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"1","recurringDonationEndDate":"2022-02-26T03:22:37.000Z","notes":""},{"id":"458","donorId":"4","categories":["Non-alcoholic drinks and juices"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Early Morning (12am - 6am)","startTime":"2022-02-04T07:00:00.000Z","endTime":"2022-02-04T08:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"6","recurringDonationEndDate":"2022-02-25T05:55:36.000Z","notes":""},{"id":"420","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-04T12:00:00.000Z","endTime":"2022-02-04T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"3","recurringDonationEndDate":"2022-02-10T12:00:00.000Z","notes":""},{"id":"411","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-02-04T21:00:00.000Z","endTime":"2022-02-04T22:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"2","recurringDonationEndDate":"2022-02-05T21:00:00.000Z","notes":""},{"id":"379","donorId":"4","categories":["Prepared meals","Non-alcoholic drinks and juices"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-02-04T22:00:00.000Z","endTime":"2022-02-04T23:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"One time","recurringDonationId":"null","recurringDonationEndDate":null,"notes":""},{"id":"421","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-05T12:00:00.000Z","endTime":"2022-02-05T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"3","recurringDonationEndDate":"2022-02-10T12:00:00.000Z","notes":""},{"id":"412","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Evening (4pm - 9pm)","startTime":"2022-02-05T21:00:00.000Z","endTime":"2022-02-05T22:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"2","recurringDonationEndDate":"2022-02-05T21:00:00.000Z","notes":""},{"id":"422","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-06T12:00:00.000Z","endTime":"2022-02-06T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"3","recurringDonationEndDate":"2022-02-10T12:00:00.000Z","notes":""},{"id":"603","donorId":"3","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-08T16:00:00.000Z","endTime":"2022-02-08T17:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"624","donorId":"3","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-08T17:00:00.000Z","endTime":"2022-02-08T18:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"557","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Night (9pm - 12am)","startTime":"2022-02-09T04:00:00.000Z","endTime":"2022-02-09T05:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"9","recurringDonationEndDate":"2022-04-01T02:47:18.000Z","notes":""},{"id":"533","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-09T12:00:00.000Z","endTime":"2022-02-09T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"604","donorId":"3","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-09T16:00:00.000Z","endTime":"2022-02-09T17:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"625","donorId":"3","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-09T17:00:00.000Z","endTime":"2022-02-09T18:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"534","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-10T12:00:00.000Z","endTime":"2022-02-10T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"605","donorId":"3","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-10T16:00:00.000Z","endTime":"2022-02-10T17:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"626","donorId":"3","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-10T17:00:00.000Z","endTime":"2022-02-10T18:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"459","donorId":"4","categories":["Non-alcoholic drinks and juices"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Early Morning (12am - 6am)","startTime":"2022-02-11T07:00:00.000Z","endTime":"2022-02-11T08:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"6","recurringDonationEndDate":"2022-02-25T05:55:36.000Z","notes":""},{"id":"535","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-11T12:00:00.000Z","endTime":"2022-02-11T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"606","donorId":"3","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-11T16:00:00.000Z","endTime":"2022-02-11T17:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"627","donorId":"3","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-11T17:00:00.000Z","endTime":"2022-02-11T18:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"536","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-12T12:00:00.000Z","endTime":"2022-02-12T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"607","donorId":"3","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-12T16:00:00.000Z","endTime":"2022-02-12T17:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"628","donorId":"3","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-12T17:00:00.000Z","endTime":"2022-02-12T18:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"537","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-13T12:00:00.000Z","endTime":"2022-02-13T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"608","donorId":"3","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-13T16:00:00.000Z","endTime":"2022-02-13T17:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"629","donorId":"3","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-13T17:00:00.000Z","endTime":"2022-02-13T18:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"538","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-14T12:00:00.000Z","endTime":"2022-02-14T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"609","donorId":"3","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-14T16:00:00.000Z","endTime":"2022-02-14T17:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"630","donorId":"3","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Afternoon (11am - 4pm)","startTime":"2022-02-14T17:00:00.000Z","endTime":"2022-02-14T18:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"10","recurringDonationEndDate":"2022-02-14T17:00:00.000Z","notes":""},{"id":"539","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-15T12:00:00.000Z","endTime":"2022-02-15T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"558","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Night (9pm - 12am)","startTime":"2022-02-16T04:00:00.000Z","endTime":"2022-02-16T05:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"9","recurringDonationEndDate":"2022-04-01T02:47:18.000Z","notes":""},{"id":"540","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-16T12:00:00.000Z","endTime":"2022-02-16T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"541","donorId":"4","categories":["Hygiene products (tampons, pads, soap, etc.)"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Morning (6am - 11am)","startTime":"2022-02-17T12:00:00.000Z","endTime":"2022-02-17T13:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Daily","recurringDonationId":"8","recurringDonationEndDate":"2022-02-17T12:00:00.000Z","notes":""},{"id":"460","donorId":"4","categories":["Non-alcoholic drinks and juices"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Early Morning (12am - 6am)","startTime":"2022-02-18T07:00:00.000Z","endTime":"2022-02-18T08:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"6","recurringDonationEndDate":"2022-02-25T05:55:36.000Z","notes":""},{"id":"559","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Night (9pm - 12am)","startTime":"2022-02-23T04:00:00.000Z","endTime":"2022-02-23T05:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"9","recurringDonationEndDate":"2022-04-01T02:47:18.000Z","notes":""},{"id":"461","donorId":"4","categories":["Non-alcoholic drinks and juices"],"size":"Medium","isPickup":null,"pickupLocation":null,"dayPart":"Early Morning (12am - 6am)","startTime":"2022-02-25T07:00:00.000Z","endTime":"2022-02-25T08:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"6","recurringDonationEndDate":"2022-02-25T05:55:36.000Z","notes":""},{"id":"560","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Night (9pm - 12am)","startTime":"2022-03-02T04:00:00.000Z","endTime":"2022-03-02T05:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"9","recurringDonationEndDate":"2022-04-01T02:47:18.000Z","notes":""},{"id":"561","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Night (9pm - 12am)","startTime":"2022-03-09T04:00:00.000Z","endTime":"2022-03-09T05:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"9","recurringDonationEndDate":"2022-04-01T02:47:18.000Z","notes":""},{"id":"562","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Night (9pm - 12am)","startTime":"2022-03-16T04:00:00.000Z","endTime":"2022-03-16T05:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"9","recurringDonationEndDate":"2022-04-01T02:47:18.000Z","notes":""},{"id":"563","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Night (9pm - 12am)","startTime":"2022-03-23T04:00:00.000Z","endTime":"2022-03-23T05:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"9","recurringDonationEndDate":"2022-04-01T02:47:18.000Z","notes":""},{"id":"564","donorId":"4","categories":["Essential items (masks, hand sanitizer, bags)","Hygiene products (tampons, pads, soap, etc.)"],"size":"Large","isPickup":null,"pickupLocation":null,"dayPart":"Night (9pm - 12am)","startTime":"2022-03-30T04:00:00.000Z","endTime":"2022-03-30T05:00:00.000Z","status":"Approved","volunteerNeeded":false,"volunteerTime":null,"volunteerIds":[],"frequency":"Weekly","recurringDonationId":"9","recurringDonationEndDate":"2022-04-01T02:47:18.000Z","notes":""}]


Editor: Ctrl+Home doesn't work

From<EMAIL_ADDRESS>on 2010-08-11T10:32:18Z
Hello,
CTRL+HOME should go to the first line of the current file.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=284

From pierre.raybaut on 2010-08-17T10:30:54Z
Summary: Editor: Ctrl+Home and Ctrl+End don't work
Status: Accepted
Labels: -Priority-Medium Priority-High

From pierre.raybaut on 2010-08-18T03:24:19Z
Summary: Editor: Ctrl+Home doesn't work

From pierre.raybaut on 2010-08-18T10:21:09Z
Status: Fixed


Missing command to open errors / warnings window

VSCode Version: 1.6.1
OS Version: Windows 10 Anniversary Update

Steps to Reproduce:

Open VSCode
Write some code with syntactical errors (eg. NodeJS)
Notice that the lower-left corner of VSCode indicates more than 0 errors or warnings
If you click the errors/warnings, an Error pane will appear in VSCode
Hit F1 to open the command palette
Search for error
Notice that there is no command in the Command Palette to invoke the errors / warnings window that appears in step 4

Cheers,
Trevor Sullivan
Docker Captain
Microsoft MVP: Cloud & Data Center Management
https://trevorsullivan.net
https://twitter.com/pcgeek86

@pcgeek86 in the command palette search for "Problems". The 'error pane' is called "Problems View" in VS Code.

@weinand might benefit from an alias pertaining to errors and warnings, too.

@sandy081 Shouldn't we just call it Error & Warnings instead of Problems? Also, the action labels are misaligned, since one is prefixed with *View: *

@jrieken Since the panel is called Problems I think it makes sense to called Problems. Errors and Warnings is an alias to assist users looking for errors and warnings

Well, that's my suggestion: We rename the panel to Errors & Warnings. No one talks about "compile problems" but "compile errors"


Add support for min cpu platform

What this PR does / why we need it:
Adds support for setting the minimum CPU platform when creating VMs.
Which issue(s) this PR fixes:
-
Special notes for your reviewer:
-
Release note:

The GCPProviderSpec now supports setting `minCpuPlatform` to configure the minimum CPU platform requested for the VM.

Hmm, right. We can generate the docs in a later PR. Let's not block this change for that
Ah, my bad, I did not realize that. Yup, you're right, fair enough then


stringprep.h

xml/jid.go:13:24: fatal error: stringprep.h: No such file or directory

Make sure you have libidn installed before trying to build jackal.

Works with libidn, but sql not
# mysql -h localhost -D jackal -u jackal -p < mysql.sql
Enter password:
ERROR 1071 (42000) at line 6: Specified key was too long; max key length is 767 bytes

jackal requires MySQL 5.7+ or MariaDB 10.2+


Feature: Allow to create post in draft mode

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other non-breaking change (enhancement, tests, documentation, chore and the like)

And

[x] This Pull Request DOES NOT target the main (production) branch on this repository (if so it must point to a feature branch or to the develop (staging) branch).
[x] I have read the CONTRIBUTING document.
[x] I have added/updated tests to cover my changes.
[x] All new and existing tests passed.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] There are no other open Pull Requests for the same update/change.

Proposed Changes

closes #32

Codecov Report

Merging #66 (654204b) into develop (0f44b29) will decrease coverage by 0.73%.
The diff coverage is 96.62%.

@@              Coverage Diff              @@
##             develop      #66      +/-   ##
=============================================
- Coverage      98.08%   97.34%   -0.74%
- Complexity       237      266      +29
=============================================
  Files             37       39       +2
  Lines            469      527      +58
  Branches          24       32       +8
=============================================
+ Hits             460      513      +53
  Misses             1        1
- Partials           8       13       +5

Impacted Files
Coverage Δ

...nhandler/impl/InvalidArgumentExceptionHandler.java
80.00% <80.00%> (ø)

.../org/wcdevs/blog/core/common/util/StringUtils.java
94.44% <85.71%> (-5.56%)
:arrow_down:

.../wcdevs/blog/core/common/post/PostServiceImpl.java
96.15% <92.30%> (-3.85%)
:arrow_down:

.../wcdevs/blog/core/common/post/PostTransformer.java
98.43% <100.00%> (+0.52%)
:arrow_up:

...va/org/wcdevs/blog/core/persistence/post/Post.java
100.00% <100.00%> (ø)

...org/wcdevs/blog/core/persistence/post/PostDto.java
93.10% <100.00%> (-2.90%)
:arrow_down:

.../wcdevs/blog/core/persistence/post/PostStatus.java
100.00% <100.00%> (ø)

...r/impl/DataIntegrityViolationExceptionHandler.java
96.15% <100.00%> (-3.85%)
:arrow_down:

...org/wcdevs/blog/core/rest/post/PostController.java
100.00% <100.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

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


certain notes won't display

No posts of Hacker News Daily RSS feed are visible:
https://nostrudel.ninja/#/u/npub1cfgtutmzspmge05vaxtk5hk5226dt8waf43jprhdzth0twl39s2qyds4yu/notes
but they are in other clients:
https://snort.social/p/npub1cfgtutmzspmge05vaxtk5hk5226dt8waf43jprhdzth0twl39s2qyds4yu
https://primal.net/profile/npub1cfgtutmzspmge05vaxtk5hk5226dt8waf43jprhdzth0twl39s2qyds4yu
Maybe because of the amount of links in each note?

Its looks like an issue where the client cant find the relays to read from, by default noStrudel reads from these relays https://github.com/hzrd149/nostrudel/blob/master/src/services/client-relays.ts#L13-L19


Publish 1.0.1

@kripken if you have an npm account, i can add permissions for you there too! Publishing as 1.0.1

Thanks! I don't have an npm account yet actually, never gotten around to. I should though...


updated all.json with more information

Resloves #13 Completed all.json with more information

Looks good.


Pedestrian crossings on boulevards rotated wrong

I am trying to import a borough of Montreal currently. It looks like there is a bug for pedestrian crossings on boulevards:

The crossing seems to be rotated 90 degrees. There should be a zebra top right and bottom left and no zebras in the middle.

There are a few things going wrong here. First is related to how sidewalks are mapped in OpenStreetMap -- sometimes as separate ways, sometimes as an attribute of the road (sidewalk=left, right, or both), and often not at all. The A/B Street importer uses the attributes when present and makes guesses based on road type when missing. If this area has separate sidewalks and crossings explicitly mapped, then ideally we would import them.
But even with the current approach of placing a sidewalk on the left/right/both sides of each road segment, the way crosswalks are inferred is very unrealistic. If you imagine rotating either direction around the center of an intersection, every pair of adjacent sidewalks (not counting the ones sharing the same corner) get a crosswalk between them. In situations with split one-way roads like this, this heuristic is quite wrong. So I think dedicating this issue to improving that makes sense.
The final issue is mostly cosmetic, although it can incorrectly cause some vehicle turns to look like they conflict with the crosswalk. The crosswalk geometry is always a straight line between the two sidewalk endpoints. Really it should trace along the shape of the intersection and look more like this:

All of these problems have existed for a while because I haven't found a straightforward way to fix them. https://github.com/dabreegster/abstreet/blob/master/map_model/src/make/walking_turns.rs is the one place that figures out which sidewalks should be connected with a crosswalk, and calculates their exact geometry. There's a disabled v2 method in there that tries to simplify things, but it needs more work and doesn't solve all of the problems. If you have any ideas about how to improve the heuristics for where crosswalks go, I'm all ears!

There are a few things going wrong here. First is related to how sidewalks are mapped in OpenStreetMap -- sometimes as separate ways, sometimes as an attribute of the road (sidewalk=left, right, or both), and often not at all. The A/B Street importer uses the attributes when present and makes guesses based on road type when missing. If this area has separate sidewalks and crossings explicitly mapped, then ideally we would import them.
But even with the current approach of placing a sidewalk on the left/right/both sides of each road segment, the way crosswalks are inferred is very unrealistic. If you imagine rotating either direction around the center of an intersection, every pair of adjacent sidewalks (not counting the ones sharing the same corner) get a crosswalk between them. In situations with split one-way roads like this, this heuristic is quite wrong. So I think dedicating this issue to improving that makes sense.
The final issue is mostly cosmetic, although it can incorrectly cause some vehicle turns to look like they conflict with the crosswalk. The crosswalk geometry is always a straight line between the two sidewalk endpoints. Really it should trace along the shape of the intersection and look more like this:

All of these problems have existed for a while because I haven't found a straightforward way to fix them. https://github.com/dabreegster/abstreet/blob/master/map_model/src/make/walking_turns.rs is the one place that figures out which sidewalks should be connected with a crosswalk, and calculates their exact geometry. There's a disabled v2 method in there that tries to simplify things, but it needs more work and doesn't solve all of the problems. If you have any ideas about how to improve the heuristics for where crosswalks go, I'm all ears!

You are right. Indeed, the sidewalks are not tagged on OSM. Here is this intersection. Nevertheless, the importer did a good job inferring both sidewalks on the East-West street and only outside sidewalks on the North-South street.
I would imagine that having an intersection like
 S|X
S | S
--┼--
S | S
 S|X

, where S is a sidewalk and X no sidewalk. The crosswalks should be produced connecting only sidewalks with the corresponding direction like
 S|X
S╬══S
-║  -
S╬══S
 S|X

You are right. Indeed, the sidewalks are not tagged on OSM. Here is this intersection. Nevertheless, the importer did a good job inferring both sidewalks on the East-West street and only outside sidewalks on the North-South street.
I would imagine that having an intersection like
 S|X
S | S
--┼--
S | S
 S|X

, where S is a sidewalk and X no sidewalk. The crosswalks should be produced connecting only sidewalks with the corresponding direction like
 S|X
S╬══S
-║  -
S╬══S
 S|X

I could see that working!
I revived the old attempt at simplifying crosswalk generation. Other importing steps have become more complicated since I wrote it -- in some cases, the importer will try to merge intersections like the one in your first post. It comes out like this:

The crosswalk geometry looks bad, but the connections are reasonable.
Until it's possible to do the intersection consolidation everywhere and get good results, what I'll attempt is to use the existing crosswalk generation, but make a second pass and filter out the crossings over the short road in the middle of the two intersections. In reality, this is likely one large intersection, without much room to stop in the middle. Having people cross in the middle is very unrealistic.

I could see that working!
I revived the old attempt at simplifying crosswalk generation. Other importing steps have become more complicated since I wrote it -- in some cases, the importer will try to merge intersections like the one in your first post. It comes out like this:

The crosswalk geometry looks bad, but the connections are reasonable.
Until it's possible to do the intersection consolidation everywhere and get good results, what I'll attempt is to use the existing crosswalk generation, but make a second pass and filter out the crossings over the short road in the middle of the two intersections. In reality, this is likely one large intersection, without much room to stop in the middle. Having people cross in the middle is very unrealistic.

And, by the way. I am not sure if you are aware of this (I can create a separate issue).
An alley connected to a road should not allow thru traffic nor produce pedestrian crossings:

I understand that this is not mapped, but it is possible to infer from the tags highway=service, service=alley.

And, by the way. I am not sure if you are aware of this (I can create a separate issue).
An alley connected to a road should not allow thru traffic nor produce pedestrian crossings:

I understand that this is not mapped, but it is possible to infer from the tags highway=service, service=alley.

I'm not sure I understand the alley problem. No through traffic for anyone? At least with alleys I'm familiar with, there are no legal restrictions preventing a vehicle, cyclist, or pedestrian from going through. There are often physical width constraints that make it highly unlikely two vehicles in opposite directions will attempt to go through at the same time. But from the simulation perspective, any movement should be allowed through, but the routing should strongly prefer to not use alleys.
The crosswalk issue is a little different. Pedestrians in A/B Street can only enter the road using crosswalks. It might be reasonable to not generate any crosswalks because of alleys, but then that forces people to walk all the way around the block. There may be some situations where this produces very unrealistically circuitous routes.
It might be time to evaluate divorcing the physical presence of crosswalks in the map model from how pedestrians can cross. There are plenty of situations around the US that I'm familiar with where there isn't a crosswalk on all edges of a 4-way junction, but it's still standard for people to cross, after yielding to traffic. Possibly the distinction we ought to model is who has the right of way -- when there's a physical crosswalk present and ideally mapped in OSM, pedestrians, and otherwise, vehicles on the road.

I'm not sure I understand the alley problem. No through traffic for anyone? At least with alleys I'm familiar with, there are no legal restrictions preventing a vehicle, cyclist, or pedestrian from going through. There are often physical width constraints that make it highly unlikely two vehicles in opposite directions will attempt to go through at the same time. But from the simulation perspective, any movement should be allowed through, but the routing should strongly prefer to not use alleys.
The crosswalk issue is a little different. Pedestrians in A/B Street can only enter the road using crosswalks. It might be reasonable to not generate any crosswalks because of alleys, but then that forces people to walk all the way around the block. There may be some situations where this produces very unrealistically circuitous routes.
It might be time to evaluate divorcing the physical presence of crosswalks in the map model from how pedestrians can cross. There are plenty of situations around the US that I'm familiar with where there isn't a crosswalk on all edges of a 4-way junction, but it's still standard for people to cross, after yielding to traffic. Possibly the distinction we ought to model is who has the right of way -- when there's a physical crosswalk present and ideally mapped in OSM, pedestrians, and otherwise, vehicles on the road.

At least with alleys I'm familiar with, there are no legal restrictions preventing a vehicle, cyclist, or pedestrian from going through.

Sorry, my bad. I did the research, and indeed it is allowed. People just prefer not to do this when there is a lot of traffic.

At least with alleys I'm familiar with, there are no legal restrictions preventing a vehicle, cyclist, or pedestrian from going through.

Sorry, my bad. I did the research, and indeed it is allowed. People just prefer not to do this when there is a lot of traffic.

I'm testing a change to remove crosswalks and stop signs from these short "roads." If all goes well, should have it pushed within an hour. Initial results:

becomes

into

I'm testing a change to remove crosswalks and stop signs from these short "roads." If all goes well, should have it pushed within an hour. Initial results:

becomes

into

Nice @dabreegster! Does this affect traffic flow or just rendering?

Nice @dabreegster! Does this affect traffic flow or just rendering?

Both. Stop signs on those short segments really do cause a 0.5s pause, which can't be helping our gridlock. And extraneous crosswalks mean worse traffic signal heuristics, and maybe people cutting in front of turning vehicles in an unrealistic way.

Both. Stop signs on those short segments really do cause a 0.5s pause, which can't be helping our gridlock. And extraneous crosswalks mean worse traffic signal heuristics, and maybe people cutting in front of turning vehicles in an unrealistic way.

@dmitriy-serdyuk If you re-import with the latest code, the inner crosswalks from your example should disappear -- er... actually, only if that road happens to be under 2 meters. You could try locally editing is_extremely_short in map_model/src/objects/road.rs if not. I'm not sure how to set this threshold without breaking some places. As part of #114, I'd still like to try automatically merging short roads like this, which is an even bigger cleanup than the previous commit.

@dmitriy-serdyuk If you re-import with the latest code, the inner crosswalks from your example should disappear -- er... actually, only if that road happens to be under 2 meters. You could try locally editing is_extremely_short in map_model/src/objects/road.rs if not. I'm not sure how to set this threshold without breaking some places. As part of #114, I'd still like to try automatically merging short roads like this, which is an even bigger cleanup than the previous commit.

It doesn't work very well for my case unfortunately... I had to increase the constant up to 20-30 meters to import this particular intersection. It caused many false positive mergings elsewhere.
I want to try the following heuristic. Merge if

a road is extremely short (say, <2m)
or; a road is short (say, <50m) and its starting and ending nodes belong to ways with the same name

It doesn't work very well for my case unfortunately... I had to increase the constant up to 20-30 meters to import this particular intersection. It caused many false positive mergings elsewhere.
I want to try the following heuristic. Merge if

a road is extremely short (say, <2m)
or; a road is short (say, <50m) and its starting and ending nodes belong to ways with the same name

I've considered explicitly tagging https://wiki.openstreetmap.org/wiki/Proposed_features/junction%3Dintersection in OSM for cases like this, but coming up with the precise rules for this tag is tricky ("so that things render in A/B Street" is of course not a valid definition there), and it often requires splitting the way.
I've been tagging https://wiki.openstreetmap.org/wiki/Tag:dual_carriageway%3Dyes in places like this -- it has a very clear definition and is a more widely-used tagged. I'll try your second heuristic with the name matching or dual_carriageway=yes on both of them. The second is a bit more precise, but would require lots of tagging.

I've considered explicitly tagging https://wiki.openstreetmap.org/wiki/Proposed_features/junction%3Dintersection in OSM for cases like this, but coming up with the precise rules for this tag is tricky ("so that things render in A/B Street" is of course not a valid definition there), and it often requires splitting the way.
I've been tagging https://wiki.openstreetmap.org/wiki/Tag:dual_carriageway%3Dyes in places like this -- it has a very clear definition and is a more widely-used tagged. I'll try your second heuristic with the name matching or dual_carriageway=yes on both of them. The second is a bit more precise, but would require lots of tagging.

Furthermore, the intersecting ways on either end should be oneway=yes. I have a heuristic for finding dual carriageways that's mostly geometric: https://github.com/dabreegster/abstreet/blob/2837808206d0b445ec6d7c8fd0b2441c85584ea9/parking_mapper/src/mapper.rs#L598
You can run this detector using https://dabreegster.github.io/abstreet/side_projects/parking_mapper.html and changing the dropdown on the right. I use this tool to look for possible dual carriageways and then manually tag them in OSM. The detection has false positives, so it still requires a human touch, but it finds many cases quickly.

Furthermore, the intersecting ways on either end should be oneway=yes. I have a heuristic for finding dual carriageways that's mostly geometric: https://github.com/dabreegster/abstreet/blob/2837808206d0b445ec6d7c8fd0b2441c85584ea9/parking_mapper/src/mapper.rs#L598
You can run this detector using https://dabreegster.github.io/abstreet/side_projects/parking_mapper.html and changing the dropdown on the right. I use this tool to look for possible dual carriageways and then manually tag them in OSM. The detection has false positives, so it still requires a human touch, but it finds many cases quickly.

@dmitriy-serdyuk You could try changing the distance thresholds at https://github.com/dabreegster/abstreet/blob/322fb81a9d9cb43392c59de8c6cb6dd1291f19df/map_model/src/make/merge_intersections.rs#L64 and just below. The connects_dual_carriageway heuristic has lots of false positives in my tests so far; I'll keep trying to improve it.
Also, if you're at least mildly invested in getting Montreal imported and high-quality in abst, I can start regularly importing and maintaining it. Just send the polygon boundary you're using if so.

@dmitriy-serdyuk You could try changing the distance thresholds at https://github.com/dabreegster/abstreet/blob/322fb81a9d9cb43392c59de8c6cb6dd1291f19df/map_model/src/make/merge_intersections.rs#L64 and just below. The connects_dual_carriageway heuristic has lots of false positives in my tests so far; I'll keep trying to improve it.
Also, if you're at least mildly invested in getting Montreal imported and high-quality in abst, I can start regularly importing and maintaining it. Just send the polygon boundary you're using if so.

I was checking OSM for Montreal. It is quite low quality: number of lanes, parking, restricted left turns, u-turns, speed limits. It will take some effort to fix OSM before exporting something decent.
How do you choose which area to export? The city is quite big.

I was checking OSM for Montreal. It is quite low quality: number of lanes, parking, restricted left turns, u-turns, speed limits. It will take some effort to fix OSM before exporting something decent.
How do you choose which area to export? The city is quite big.

It will take some effort to fix OSM before exporting something decent.

Definitely. I'm hoping A/B Street can provide motivation to rally OSM communities to mapping those sorts of details. Of course not only abst benefits from this; routing can be more precise, in particular. I personally think tagging for lanes is often low-quality in many areas because it's so hard to visualize the results.

How do you choose which area to export? The city is quite big.

I chop it up into different pieces. Some examples:

As you can see, the pieces don't have to perfectly partition the city; they can have gaps or overlap. Picking the boundaries totally depends on what you're trying to do -- some of the chunks of Seattle were chosen specifically for an experimental Santa game. Others were chosen because I wanted to study the possible effects of some changes to a certain area, so I used my own judgment to figure out what area might be relevant. And it's trial-and-error to tune the resulting file sizes and workaround bugs like #32

It will take some effort to fix OSM before exporting something decent.

Definitely. I'm hoping A/B Street can provide motivation to rally OSM communities to mapping those sorts of details. Of course not only abst benefits from this; routing can be more precise, in particular. I personally think tagging for lanes is often low-quality in many areas because it's so hard to visualize the results.

How do you choose which area to export? The city is quite big.

I chop it up into different pieces. Some examples:

As you can see, the pieces don't have to perfectly partition the city; they can have gaps or overlap. Picking the boundaries totally depends on what you're trying to do -- some of the chunks of Seattle were chosen specifically for an experimental Santa game. Others were chosen because I wanted to study the possible effects of some changes to a certain area, so I used my own judgment to figure out what area might be relevant. And it's trial-and-error to tune the resulting file sizes and workaround bugs like #32

I filed #485 to focus on the crosswalk heuristics, btw

I filed #485 to focus on the crosswalk heuristics, btw