".well-known" URL returns 404

Hi there. I'm using Django 1.10 and I've created a static app from www.example.com/.well-known to ~/public_html such that if I put a file (say test.html) in ~/public_html and browse to www.example.com/.well-known/test.html it renders properly.
But when I run
$ letsencrypt_webfaction --account_email<EMAIL_ADDRESS>--domains example.com,www.example.com --public /home/username/public_html/
I get 404 errors that it couldn't find www.example.com/.well-known/acme-challenge/some-hash
When I look in ~/public_html, there's nothing in there. Do you have any suggestions?

Did you use ls -a to see hidden files and folders?

Gah. When I was looking for a fixed I forgot to check for closed issues (which are filtered by default). I'm probably having exactly the same issue everyone else did. I've got a different cert installed which will last me the year. Thanks for your help (and sorry for wasting your time :()


Error in installation instructions inside Readme.md

There is a mistake in the installation instructions in the readme. The readme states:

Installation
npm i slide-up-down

The command is wrong. The actual package name is vue-slide-up-down, so the instructions should be:

Installation
npm i vue-slide-up-down

Fixed in 1.4.1! <3


Updated demo code

Cleaned up code and made sure it worked
Fixed Controller to use Configuration.php
Added MDR lookup example

@envisean This is ready for code review, all functional testing went well.


Fix error swallowing

This PR fixes a bug where command errors are swallowed when leaving the alternate terminal screen was successful. The bug was introduced here.

Thanks!


Fix UnicodeEncodeError when creating responses

flask_ask uses xml.etree to find out if the response contains SSML. Because xml.etree internally only works on byte strings it raises an error if the implicit encoding to ascii doesn't work. To avoid that unicode strings are encoded to utf-8 before parsing with xml.etree

Thank you Tobias. I appreciate this P.R. very much. However, for a while now, I think it makes sense to do away with the etree dependency and XML checks altogether and just always return the response as an SSML response (i.e. always wrap responses in .
That is how Amazon's official SDK for NodeJS works for all ask/tell responses:
https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs/blob/master/lib/alexa.js#L266
and reprompts:
https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs/blob/master/lib/alexa.js#L271
Is that something you'd be interested in helping with? Reason I ask is because before I merge any P.R.s, I always run them through all the samples in the samples dir and that takes about an hour. I'd rather not do it here since I'm going to throw that code out altogether anyway.

Thanks for the quick reaction.  I'd be interested in helping. But maybe it would be better to make it explicit? Add a parameter responseType by default set to 'PlainText' and has to be set to 'SSML' if you want to use SSML. Otherwise what happens if you want to explicitly use SSML. Will it be doublewrapped?

The idea is to do away with PlainText responses entirely and always wrap the speech in <speak></speak> tags and not give an explicit option. All responses should just be returned as SSML responses by default.  PlainText responses are superfluous.
Basically,
def _output_speech(speech):
    try:
        xmldoc = ElementTree.fromstring(speech)
        if xmldoc.tag == 'speak':
            return {'type': 'SSML', 'ssml': speech}
    except ElementTree.ParseError as e:
        pass
    return {'type': 'PlainText', 'text': speech}

would better be
def _output_speech(speech):
    return {'type': 'SSML', 'ssml': speech}

If you take a look at this function from Amazon,
https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs/blob/master/lib/alexa.js#L375
You'll see it's the only way their SDK generates speech of any sort.

Hmm... Sorry - that would break templates, so is not a good idea right now. I have to think about this. If I can't think of something soon, I'll test and merge your PR

Does it make sense to create a test suite to lessen the burden of integrating changes?

Am 15.01.2017 um 18:57 schrieb John Wheeler<EMAIL_ADDRESS>Hmm... Sorry - that would break templates, so is not a good idea right now. I have to think about this. If I can't think of something soon, I'll test and merge your PR
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/johnwheeler/flask-ask/pull/81#issuecomment-272711694, or mute the thread https://github.com/notifications/unsubscribe-auth/AAgUvWGRP1twmIEypGdv9aXjIM4mpWiJks5rSl4FgaJpZM4Lj8cz.

Absolutely. Now that people are starting to contribute to the project, it would be very helpful. I'm just lazy. :)

The echo and echo dot are still invite only in Germany. I believe you will see more and more people during this year :)

Am 15.01.2017 um 19:15 schrieb John Wheeler<EMAIL_ADDRESS>Absolutely. Now that people are starting to contribute to the project, it would be very helpful. I'm just lazy. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/johnwheeler/flask-ask/pull/81#issuecomment-272712774, or mute the thread https://github.com/notifications/unsubscribe-auth/AAgUvXacu0KJAi615Fba4PhprKOPuKc-ks5rSmItgaJpZM4Lj8cz.


Add ability to route based on "addr"

My scenario is (probably common), I deployed Redis in an AWS with master and read-only replicas across multiple AZs (traffic is 99% read). I would like if possible to redirect the majority of the reads to read-only replicas in the same AZ to avoid cross AZ network traffic ($$$).
Initial thought was to support a custom "router" a func that allows user to sort nodes in the order of priorities (I will do it based on address most likely, maybe it is not possible).
Do you have a solution for this? Does anyone solved this issue?
PS: "RouteByLatency" may be good, but the problem is that if updateLatency will give a bad latency (for different reasons) initially I will end-up never going to the same AZ. A solution may be to run periodically updateLatency.

I've improved RouteByLatency in https://github.com/go-redis/redis/pull/1484:

latency should be more accurate by properly calculating mean and inserting random pauses between probes
latency should be updated when Cluster state changes

Hopefully that is enough.


Capture metadata for NIH life sciences projects

The national institutes of health provides a Project API that allows us to attach extensive metadata to a dataset by linking it to the NIH grant / project.
We can use https://api.reporter.nih.gov/ for this. A TUI should be invoked if a user executes the --nih option, for example
Froster archive --nih

now implemented:
https://github.com/dirkpetersen/froster/commit/ea5faa36349a7a2f213900d47aadc0eef6406f70


Project discontinued?

Hello,
I have seen no progress on this for several month, is it discontinued? We planned to use this in production, are there any alternatives or will it get picked up again?
Thanks

Would also like to know the status of this project. Most of the issues still open have been open for months with no end in sight.
A specific issue we are facing is the expansion of volumes after they've been provisioned. StorageOS and other volume drivers are handling this fine, but the VMWare Storage For Docker team has closed out all of the old issues relating to this.
https://github.com/vmware/vsphere-storage-for-docker/issues/1876

+1 what's the status of this project?

There is no active development happening for this driver, nor is planned in the near future.  We have shifted our efforts to Kubernetes solutions.
Volume expansion support is being planned for kubernetes driver.

Should this be compatible vith vmware 6.7?
We recently updated to 6.7 now I get errors like
May 13 09:28:45 dca.tek.fi dockerd[336]: time="2019-05-13T09:28:45.361945009Z" level=error msg="fatal task error" error="VolumeDriver.Mount: Device not found" module="node/agent/taskmanager" node.id=pd9mvqohram9ewygqyyjiui27 service.id=7t1obs5rmin23hpvcgdb0nyq3 task.id=m7qsr5x0z05viyqqnu3nnig7q
Still docker volume info returns correct info.

So there is actually no good solution for Docker Swarm users if this project is scrapped.


merge index.html edits from master

Hey @w3cj, I'm not sure if we accept PRs directly to the gh-pages branch, I think this may be handled separately, @rhys-vdw do you know?

Yeah, wasn't sure the process for getting changes into gh-pages. I checked, and the changes were merged in another commit, I'll close this. Thanks!


[python-package] add plot tree

#171

Hi @wxchan, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Graphviz are not executables on Travis, so there is no way to test it. I just put an empty function with a skip message there to notice others.

Here is an example how the plot tree looks like in examples/python-guide/plot_example.py.

Wow, this looks good!
Is it easy to show a feature name instead of the index?

@guolinke finished.
@henry0312 feature name is saved in Dataset, not in Booster now. We can investigate how to use feature name instead of index after this pr.

feature name is saved in Dataset, not in Booster now.

I see...🤔

@wxchan I think we can add feature names to booster as well.
Actually inside boosting class has feature_names

I use feature_name in dump_model for now. @guolinke @henry0312

seems good :)

@chivee I think it's better to use squash and merge commit to merge PR like @guolinke.

It seems the merge of this PR add many additional commit log in master branch.
I will force update the master branch now.
@wxchan  can you re-create this PR again ?

@henry0312, I was assuming GitHub using squash and merge as a default option.

@guolinke , please using reset soft rather than 'hard  mode' as possible


Upstart documentation failing

I have gone through the steps outlined in section Set up Mattermost Server.
When I get to step 9 and run the command sudo start mattermost, it fails with error message:
[sudo] password for ubuntu:
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
The machine is running Ubuntu 16.04.1 x64 (a DigitalOcean droplet).

I think you're using Ubuntu 14.04 instructions on Ubuntu 16.04,
Could you try the steps here: http://forum.mattermost.org/t/ubuntu-16-04-support/2406
16.04 instructions are being drafted by the community to be added to the official docs, we'd highly appreciate any feedback you have posted to the forum--whether it worked or it didn't.

Thanks @it33, I was able to get over the hurdle by properly installing Upstart. I will add more comments in the forum.

Excellent, thanks for your help!


Everytime I try opening it says this

You have an N edition of Windows installed. See this article: https://support.microsoft.com/en-us/topic/media-feature-pack-list-for-windows-n-editions-c1c6fffa-d052-8338-7a79-a4bb980a700a


Gooey with pythonw

Would be nice to allow a user to just double click on a script and open the script with pythonw so without any dos console on windows.
However it seems that Gooey is in a endless loop, when started with a double click and pythonw.

This works on my machine : )
Can you provide an example where it is not working? Try the demo code below (Remove the .txt extension). It should fire right up on double click.
widget_demo2.pyw.txt

same with this script :-(
seems to be in an endless loop. I fill in some details, click "Start" an the widget says,
the code is running. At the same time a new widget pops up, with the "Settings" again.

Please supply a code sample that reproduces the issue


Issue: Guild.delete() deprecated

Summary
It's technically not a bug, but the delete() method can no longer be used as Discord no longer allows giving bots guild ownership
Reproduction Steps

Create Guild
Invite bots
Right click bot (no give ownership option)
invite an alt account
Right click alt account (You will see the give ownership option)

Minimal Reproducible Code
-

Expected Results
An existing "give ownership" option for bots
Actual Results
No Give ownership option
Intents

System Information

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.

Additional Context
probably should have just brought it up in bikeshedding but eh... whatever.

Bot's can create guilds and would gain guild ownership in the process.


want to add logo to login page

Want to add clickable logo to login and sign up form as well.
Kindly assign it to me.
HAPPY HACKING

I would like to contribute to this issue.

hello,
I can easily solve this issue
@ishitakapoor26 please assign this issue to me asap

@ishitakapoor26 Kindly assign the issue raised to me

There is no need of adding logo to the login page.
Please raise another issue to work on!
Good luck!


About preprocess

Hello, thank you for your code. I still want to know what preprocessing you have done to the data? Because when running with my data, the result is not ideal. I would like to know if this is because of the difference in preprocessing or the data is too different?

the result is not ideal. I would like to know if this is because of the difference in preprocessing or the data is t

Hi, Actually, we didn't do special preprocessing. Maybe your problem is different. You can add my WeChat (You can Email me to obtain my wechat<EMAIL_ADDRESS>for real-time communication.


🐛 FIX: Add formatting for definition/field/apidoc lists

closes #158
The CSS for the API doc components is taken from the RTD theme CSS, which I converted to SCSS here: https://gist.github.com/chrisjsewell/0f414e6c13e714f9cf70c36f20efaafa
There can possibly be some "pruning" of unneeded elements?
As noted in the scss, field list should be a different format, but that format is a little tricky (see https://github.com/pandas-dev/pydata-sphinx-theme/issues/193) and not widely used, so I think tackle that in a separate issue/PR
@pradyunsg I also added nitpick mode (to check for missing refs) to the nox sphinx-build commands

Ok merge this and make a release, because I need it for myst-parser


reintroducing truncated gradient BPTT

truncated_gradient was removed from keras. it is supported in Theano.
when you have very long sequences and you want a long memory, truncating the gradient in BPTT can be essential to performance.
@fchollet expressed in several places that this can be done using the stateful rnn. however after working on it for the last week, i find this quite non-trivial. splitting the data to short sequences introduces many edge cases, and with sequences of varying length you have to implement the fit and evaluate loops yourself to control the state reset (see also https://github.com/fchollet/keras/issues/4185 )

How do you propose getting it into Keras code base? I'm very curious! Totally agree that stateful RNNs require a lot of fiddling.

I am curious that why truncated_gradient is removed.

please reopen. this is still an issue. i missed the stale tag.

Has any progress been made on how to do the truncate_gradients thing in keras? I do not get how to do it with stateful mode, and it seems there should be some simple option like theano has (truncate_gradient in the scan function). Would appreciate any help on this!

looking forward to the solution too


Weird empty package

I found a weird broken package under available packages. It has no name, version, author, description, or source URL. (The source button has the cursor default and it gets TypeError: Error processing argument -1. via open_url when clicked.)

@1j01 Thanks for the report.
The problem is that the code that builds the list ('cache') of plugin metadata is treating the script sub-directory as a plugin.

👍


Fix word regex for snake case with numbers

In the token cursorless_target_v1, the v1 is treated as two words instead of one.

I'm not sure we actually want this. For example if you generate a range of numbers on multiple targets being able to select that number so you can increment, decrement, reverse could be really useful.


ElasticSearch with cluster name and ports

Description
Fix errors  in elasticSearch related with the connection ports and uris.
Added cluster name function.
Reviewer
@arinconstrio
Test
Passed

API tests passed and very general and ES specific GUI tests passed


Current in Copper Coil

hohlzylinder_cu_frequenzabhaengig_approx.py
Why not 200mA?

Probably due to B not actually being measured, but its representative voltage.


config: support online change gc worker config

What have you changed?
This pr is part of online config change.
This pr add support for online change gc worker config by using VersionTrack to listen the update of config, this pr also make the Debugger using the same way to change io limit.
What is the type of the changes?

New feature (a change which adds functionality)

How is the PR tested?

[ ] Unit test
[x] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No

/run-all-tests

LGTM, please resolve conflicts.

/run-unit-test

/run-all-tests

/run-unit-test

/run-unit-test


Highlight phone numbers, email addresses, etc.

When sending messages, I noticed that Riot doesn't make phone numbers clickable. Is it possible to leverage Linkify to make this possible?
It would make a life a lot simpler when sending contact information to other Riot users if they could just click on the specific parts of the message with the details (similar to how if you receive an SMS with a phone number in it, it automatically highlights it like a link and opens up the dialer if you press on it)

Validated in 0.6.10-dev (639650f)


set_query, set_encoded_query incorrect for empty string

When called with an empty string, setting the query actually clears it:
https://github.com/CPPAlliance/url/blob/afb91bc384168ed912e991ae436b8e8bbbde7d89/include/boost/url/impl/url_base.ipp#L1629

The javadoc is correct:
        is thrown. When this function returns,
        @ref has_query will return `true`.

but the behavior of the function does not match.


Custom Pagination CSS

Can i config the CSS for pagination ? like active class etc.
And how if i want to show not only active page ?
Maybe like some config at this component
https://www.npmjs.com/package/react-js-pagination
Thanks.

We are working on it, we will release it soon.

Hi,
We have implemented new type of pagination like you want in new release(1.3.0) please see documentation.
Also please let us know if you have any problem in same

Hi @ashvin27, thanks for the new update.
i just try it and works good, but i found some issue.
i set next & previous at pagination, language config but doesn't work. the default is always left and right arrow.
this is my config
language: {
  pagination: {
    previous: "Previous",
    next: "Next"
  }
}

i think the problem is at lib/ADPagniation.js
tags.push(_react2.default.createElement(
  Item,
  {
    key: "p0",
    className: props.isFirst ? "disabled " : "",
    onClick: props.previousPage },
  "\u25C4"
));

.
.
.

tags.push(_react2.default.createElement(
  Item,
  {
    key: "n0",
    className: props.isLast ? "disabled " : "",
    onClick: props.nextPage },
  "\u25BA"
));

that code still use "\u25C4" & "\u25BA", unicode for black left & right pointing pointer

Hi @freyandhy Thanks for the update.
We will fix it then update.

Fixed in version 1.5.0


Swagger generator incorrectly generates wrong client name for an operation group that has 'operation' in its name.

<Copied from https://github.com/Azure/azure-sdk-for-net/issues/22156>
In the swagger specification for the service, there is an operation group named FarmOperations:
https://github.com/Azure/azure-rest-api-specs/blob/683e3f4849ee1d84629d0d0fa17789e80a9cee08/specification/agfood/data-plane/Microsoft.AgFoodPlatform/preview/2021-03-31-preview/agfood.json#L3156
Since we generate a client per operation group, we would expect that this would create a client type named FarmOperationsClient but instead we generated a client named simply FarmClient:
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/agrifood/Azure.Verticals.AgriFood.Farming/src/Generated/FarmClient.cs#L17
Suspect the issue here is that "Operations" is a pretty special term and it's getting "cleaned" somewhere in our pipeline.

Hi @pallavit it is a behavior by design and have existed for a long time: https://github.com/Azure/autorest.csharp/blob/8698fe440049c0adfe370c6286db9f248ea0d7e0/src/AutoRest.CSharp/Common/Output/Builders/ClientBuilder.cs#L67
We use this ClientBuilder.GetClientPrefix to build the name of a client, such as: https://github.com/Azure/autorest.csharp/blob/8698fe440049c0adfe370c6286db9f248ea0d7e0/src/AutoRest.CSharp/LowLevel/Output/DpgOutputLibraryBuilder.cs#L296
Therefore the Operations suffix will be trimmed off.
For now, the behavior is by-design, but since our principal for generated code has changed recently because of the non-branding stuff and typespec, this might need to be discussed again, therefore feel free to start an official channel internally to discuss this.


README.md in 8.6 docker-compose folder is empty

Today, we found that the readme in the 8.6 folder is empty, which caused confusion with the new --profiles argument that was needed to be included with 8.6 (which previously was not required in 8.5 or earlier).

At what stage did we introduce profile argument?
Was this ever discussed?


Error/warning on Apple Silicon

I am seeing the following on my terminal when I run the container:
! frontend The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s
Everything is working, but I guess it is due to a platform mismatch and this warning/error could be gracefully handled.

oh good point, i should also build containers for arm, thanks :)

closing for #90


issue on window 10：python main.py Failed to load clip model,please help to check this issue and tell me how to solve it, thank you

Traceback (most recent call last):
File "D:\ProgramFiles\Local-File-Organizer\main.py", line 106, in
main()
File "D:\ProgramFiles\Local-File-Organizer\main.py", line 26, in main
initialize_models()
File "D:\ProgramFiles\Local-File-Organizer\data_processing.py", line 23, in initialize_models
image_inference = NexaVLMInference(
^^^^^^^^^^^^^^^^^
File "D:\ProgramFiles\miniconda3\Lib\site-packages\nexa\gguf\nexa_inference_vlm.py", line 142, in init
self._load_model()
File "D:\ProgramFiles\miniconda3\Lib\site-packages\nexa\utils.py", line 155, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "D:\ProgramFiles\miniconda3\Lib\site-packages\nexa\gguf\nexa_inference_vlm.py", line 155, in _load_model
self.projector_handler(
File "D:\ProgramFiles\miniconda3\Lib\site-packages\nexa\gguf\llama\llama_chat_format.py", line 2718, in init
raise ValueError(f"Failed to load clip model: {clip_model_path}")

It seems like the issue you're encountering may be due to missing dependencies, incorrect model paths, or a version mismatch in your Python environment.

verify that all required libraries are installed and compatible by checking your Python version:python --version

use nexa list to verify model paths and ensure the CLIP model is correctly referenced.

check version conflicts between libraries like PyTorch can cause issues. Make sure you're using compatible versions by checking and updating them.

If the problem persists, consider submitting an issue to the Nexa SDK GitHub repository for further assistance: SDK issue. The developers are usually quick to respond.

@QiuYannnn 兄弟有微信没，给个微信行不

You can try
pip uninstall nexaai
and then,
pip instal nexaai
It should be SDK problem about Window, please leave the question in Nexa SDK Issue Tab


Add timeout option

Separate from but based on the old PR regarding this feature: https://github.com/cjoudrey/gluahttp/pull/20

Thanks!


PHP: complete some todo

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

One or more commits are not associated with a GitHub user. The email used in the Git commit must match a verified email address in a GitHub user profile. For more information, please see https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/

Regards,
CLA GitHub bot

@ZhouyihaiDing Hi, please review the pr, thanks a lot.

Interop Cloud-to-Prod Tests (internal CI) - #15231


it is a good job,can you share the visualization code？ thank you!

Hi, you can use this tool: https://github.com/gxywy/rl-plotter


Arbitrary variables support

Environment

Python version:  3.5.3
Peering Manager version:  master

Proposed Functionality

Support for various types of arbitrary variables:
-- community type
-- integer type
-- string type
-- etc..

To be efficient with screen realestate, potentially move community and routing policy under the "Variables" umbrella.  ie:  A Routing Policies entry now be a policy type variable.  A Communities entry would become community type variable.

Allowing arbitrary variables could allow a routing policy to be constructed on a session using different defined variables, or even free-hand.
See very rudimentary visual representation attached.

External Dependencies

Maybe we could add some kind of configuration_context field that could be then used in templating (just an idea I had, that needed to be written not to be forgotten).

I think this would be a good option to have. Would also setup to prep for generation of routing policies by peering-manager.

I'd love to see this as well, as I have per-peer routing policies that reference their ASN, but I don't want to configure Peering Manager with all the individual policy names for each peer (and have to assign them on a per-peer basis as well)

I'd like to know if you feel this is addressed in 7f4e1f5 or if we need to go further to close the issue.

This ties into #505, happy to have some feedback in that thread!

Closing it as it seems resolved.


Stuck at "Github Dorks in process"

hi, the scan always gets stuck at Github Dorks in process. It has been here for about 20mins
Steps to reproduce the behavior:

docker pull six2dez/reconftw:main
docker run -it --rm -v "${PWD}/OutputFolder/":'/reconftw/Recon/' six2dez/reconftw:main -d example.com -a

OS: Debian GNU/Linux 11 (bullseye) x86_64

Version 2.3.2

The time taken by this technique depends on the target, the number of GitHub tokens provided, your network.... being slow does not mean it is not working, sorry


Append to, rather than overwrite, $layout.svelte

Is it possible to just add import "./global.css" to $layout.svelte, instead of overwriting it?
Why?
I went through Svelte Kit docs & followed along. Then at the end, I ran npx svelte-add tailwindcss --jit in this project and thought it broke the site. Turns out the adder overwrote my $layout.svelte, instead of just adding import "./global.css" to it.
People might want to run the command at a later stage of their project.

People might want to run the command at a later stage of their project.
I very much so do not want to support this.

Otherwise, supporting appending to $layout.svelte is a needed missing feature so this adder can be used in conjunction with the Bulma adder that does the same thing.

Hmm It's a bit limiting to not be able to run it successfully except in the first few moments. Maybe the underlying project adder is built on doesn't support this well.
But two options:
1.) If it can run an arbitrary JS file:
const str = fs.readFileSync('path/to/$layout.svelte', 'utf8');

// if doesn't already exist, add it.
if (!str.match(`import .*global\.css`)) {
 str = str.replace('<script>','<script>\n  import "../global.css";')
}

fs.writeFileSync('path/to/$layout.svelte', str, 'utf8');

(Untested, but the match and replace are tested.)
2.) Or ansible is a much more bulletproof underlying project, that is idempotent (won't mess things up if it was run previously), can do things like only add a line to a file if that particular line doesn't yet exist, etc. Only downside is that it would require users to run brew install ansible before using any adder.

Seems at the very least a well behaved utility should warn the user before overwriting existing files!

Closed by https://github.com/svelte-add/postcss/commit/fb1a7f277e8df2aac5166bc03880484c5cd2376b


Update creating_a_organization_quota_definition.html

Thanks for contributing to cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:

An explanation of the use cases your change solves

[ ] I have viewed signed and have submitted the Contributor License Agreement

[ ] I have made this pull request to the master branch

[ ] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests on bosh lite

Hey @abbyachau,
Thanks for submitting the update. Everything looks good, but one thing is that the non_basic_services_allowed field in SpaceQuota determines whether a space (not organization) can have these non-free services. An org can have non_basic_services but we also want to be more restrictive in regards to spaces in that org.
It would be great if you could make the updates!
Thanks,
CAPI Community - @michaelxupiv

Oops. You're right. We've updated the PR. Better?
Thanks!

@shalako & @abbyachau ,
All looks good. Merged!
Thanks,
CAPI Community - @michaelxupiv


fix: sidebar spill in safari

remove z-index from sidebar CSS
Fixes #549. I haven't seen any negative consequences, but I do not really know why that z-index was there.

this is currently active on: https://publish.1042.ch/

This is not working. I keep looking for a solution.

ok the new version work, but is visually unpleasant, you can't ease into unsetting the z-index.

Yeah, I see it sorta works. I think there is likely a better solution though. I'll look into it more

I just relearned about ::after, this is much nicer.


GridView filter row is always positioned in the thead element

What steps will reproduce the problem?
GridView->$filterPosition = self::FILTER_POS_BODY;
This variable is set to tbody as default. No matter of it's value - the filter row is always added to the thead element.
What is the expected result?
The filter row has to be positioned as the $filterPosition property is.
What do you get instead?
The filter row is always added to the is always added to the thead element.
Additional info
renderTableHeader() -> elseif ($this->filterPosition === self::FILTER_POS_BODY) {$content .= $this->renderFilters();}
code should be moved to the renderTableBody() method of the GridView class.
Same case is for the footer function-method.

Q
A

Yii version
2.0.8

PHP version
5.6.8

Operating system
Windows

This variable is set to tbody as default. No matter of it's value - the filter row is always added to the thead element.

This is expected: see the description for the filter position constants:
- [[FILTER_POS_HEADER]]: the filters will be displayed on top of each column's header cell.
- [[FILTER_POS_BODY]]: the filters will be displayed right below each column's header cell.
- [[FILTER_POS_FOOTER]]: the filters will be displayed below each column's footer cell.

If you choose FILTER_POS_HEADER filter appears at the top row of thead, if FILTER_POS_BODY - at the bottom of thead if FILTER_POS_FOOTER - at the footer.

Thank you Paul,
I have override GridView class. Functions renderTableHeader(), renderTableBody(). All works fine now.
I'm not sure if I understand exactly the configurations, so I've wrote mine.
Regards
Hristo Hristov


Add the ability to the CLI to post process returned metadata and extract image to a local media file

Resolves #214
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

ok to test

/ok to test

Updates and typo fix look good!


Getting Certificate Invalid Error

On running the npm start command and opening the local host url (https://<IP_ADDRESS>:8080/). I am getting below error.

Yes, this is expected. If you want to avoid these certificate errors you will need to create your own certificate (cert.key and cert.pem) and put them on the ca folder.
Some browsers let you bypass these certificate errors.

@shubham1079 Could you please consider Close this issue, as @dlouvton has confirmed this is expected behavior, and no further actions/works is required at this time. Warm regards.

Bump @shubham1079

Hi @estrudels @dlouvton , thank you for the update on this. I have no further questions and this issue can be closed. For some reason i am not able to view the close issue button. May be @dlouvton can close this one.

Hi @dlouvton @estrudels thank you for update on this. I have no further questions, closing the issue.


Increased Lightbox component zIndex

Hello, currently it is lower than material-ui AppBar component's zIndex (1100).

Thanks @newsiberian!
This will get some people out of trouble until we find a solution theming


add react-scripts as zero conf build tool with jest test support

This PR replaces local webpack and babel config for a zero conf build tool react-scripts
There are several advantages as well as disadvantages over using a zero conf build tool.
The main advantages are:

you dont need to be a webpack expert
configs are up to date by a huge community and new features are on its way for upcoming 2.0 release (css modules, vendor chunks etc)
less dependencies to keep track of

The disadvantages might be:

you might get less understanding of how your app is bundled

This build tool was very fast to introduce in this project just as a "try it before you buy it", its up to the maintainer if you want it. Clone the branch and give it a go.
Resolves #31 #32 #33  and also adds jest for testing, I added one smoke test for demo purpose you can run npm test to give it a shot. I can add more smoke tests if this PR is considered acceptable.
Following javascript features is supported:
Exponentiation Operator (ES2016).
Async/await (ES2017).
Object Rest/Spread Properties (stage 3 proposal).
Dynamic import() (stage 3 proposal)
Class Fields and Static Properties (part of stage 3 proposal).
Following pollyfills are included:
Object.assign() via object-assign.
Promise via promise.
fetch() via whatwg-fetch.
Debugging via editor is possible:
https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#debugging-in-the-editor
Adding environment variables is easy and can be overridden locally:
https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#debugging-in-the-editor
Now you can develop locally with production backend without chaning code, just local configuration:
Just create .env.development.local and put in REACT_APP_MISSION_CONTROL_HOST=https://ctrl.missions.io
Build dir is now build instead of dist
Static assets in public dir will be compiled without hashnames, assets and images in src dir will use hashnames which means you can have far future expire headers on /static dir because only files changed will be recompiled when running npm run build
Remember to disable cache headers for html file and service-worker.js
Related Issue
#31 #32 #33

Hey @andriijas
Thanks for the awesome PR. I wanted to take the time to go over it properly, and have already looked at it three times so far.
I have actually originally started building missions by using Create React App (as I did on any other React project I started recently), only to later scrap it and start over with my own configurable build system (as I did every other time I tried Create React App).
I have always found that it creates a great place to start, and gives you plenty of of goodies for free... but the minute you want to do anything differently, configure it slightly differently, use something they did not think off, or anything that is different from the rigidly structured, opaque package that is Create React App then you are in for a rough time.
I think the fact that you couldn't use the workbox plugin and had to hard code its functionality instead is one example of that, as was the need to rename the output directory (though that one is minor).
What do you think? Am I overlooking some basic truths of Create React App? That's entirely possible.

I think you should keep what you have then :) In some projects I stick with cra, sometimes i wrap it with https://github.com/timarney/react-app-rewired when i need to extend it.

Interesting, I haven't heard of rewired yet.
I see though that it still takes the approach of requiring rewire-specific plugins for the overrides you want to use. Has that been limiting? Have you found yourself missing out on some things?


Make a GitHub page out of Curation Guide

This guide https://docs.google.com/document/d/1i8EzoWiQH8932hSI5gor64IQ9ozRucw7tBfvZfeQUFc/edit#heading=h.hf9b8vu4h5z1 needs to be turned into a GitHub page instead of being a Google doc

https://github.com/SFDO-Community-Sprints/sprintys-community-resources/wiki/Volunteer-Curator-Guide

This can be updated once the submission form is updated


TRX file cannot be correctly located in VsTest 16.7 in Azure DevOps Pipeline

Description
Starting today, the VsTest 16.7.0 is available in Azure DevOps pipeline. We got an error message at the end of the VsTest step that it clamied TRX was not found when publishing the test.
It appears the VsTest was looking for trx file in \agent\_work\_temp\TestResults while it was actually saved to $(Common.TestResultsDirectory)
We were using VsTest 16.6.1 with the same pipeline this past Sunday without problem.
Script
Here is the part of our yml pipeline file:

- task: VisualStudioTestPlatformInstaller@1
  displayName: 'VsTest Platform Installer'
  inputs:
    versionSelector: latestStable

# To avoid vstest execution error, we need to split tests into group by framework version.
- task: VSTest@2
  displayName: 'VsTest - testAssemblies - .Net Framework'
  inputs:
    testSelector: 'testAssemblies'
    testAssemblyVer2: |
      **\MyApp.UnitTest.dll
      !**\obj\**
    searchFolder: '$(System.DefaultWorkingDirectory)'
    vsTestVersion: 'toolsInstaller'
    codeCoverageEnabled: true
    pathtoCustomTestAdapters: '$(System.DefaultWorkingDirectory)/test/UnitTests/MyApp.UnitTest'
    otherConsoleOptions: '/ResultsDirectory:$(Common.TestResultsDirectory)'

Log
Here is the log output:
**************** Starting test execution *********************
C:\agent\_work\_tool\VsTest\16.7.0\x64\tools\net451\Common7\IDE\Extensions\TestPlatform\vstest.console.exe "@C:\agent\_work\_temp\tb3bjofmr20.tmp"
Microsoft (R) Test Execution Command Line Tool Version 16.7.0
Copyright (c) Microsoft Corporation.  All rights reserved.
vstest.console.exe "C:\agent\_work\31\s\test\UnitTests\MyApp.UnitTest\bin\x86\Release\MyApp.UnitTest.dll"
/Settings:"C:\agent\_work\_temp\5k2prh3hdf4.tmp.runsettings"
/Logger:"trx"
/TestAdapterPath:"C:\agent\_work\31\s\test\UnitTests\MyApp.UnitTest"
/ResultsDirectory:C:\agent\_work\31\TestResults
Starting test execution, please wait...
Microsoft (R) Coverage Collection Tool Version 16.0.30319.200

Copyright (c) Microsoft Corporation.  All rights reserved.

Results File: C:\agent\_work\31\TestResults\CMMMM038$_CMMMM038_2020-08-07_14_38_13.trx
Attachments:
  C:\agent\_work\31\TestResults\c52bfe34-15a7-4762-bbff-fbba29cac278\CMMMM038$_CMMMM038 2020-08-07 14_38_06.coverage
Test Run Successful.
Total tests: 5
     Passed: 5
 Total time: 9.0765 Seconds
Vstest.console.exe exited with code 0.
**************** Completed test execution *********************
Test results files:
##[error]Error occurred while publishing test results : MS.VS.TestService.VstestConsoleAdapter.NoTrxFoundException: No trx files found in the specified test results directory C:\agent\_work\_temp\TestResults.
##[error]Skipping marking test run as complete as test run id 0 is invalid.
Completed TestExecution Model...
##[warning]Vstest failed with error. Check logs for failures. There might be failed tests.
##[error]Error: The process 'C:\agent\_work\_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\2.170.1\Modules\DTAExecutionHost.exe' failed with exit code 1
##[error]Vstest failed with error. Check logs for failures. There might be failed tests.
Finishing: VsTest - testAssemblies - .Net Framework

Here is the log output for VsTest 16.7.0 installation
==============================================================================
Task         : Visual Studio test platform installer
Description  : Acquire the test platform from nuget.org or the tool cache. Satisfies the ‘vstest’ demand and can be used for running tests and collecting diagnostic data using the Visual Studio Test task.
Version      : 1.151.3
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/tool/vstest-platform-tool-installer
==============================================================================
Starting VsTest platform tools installer task.
==============================================================================
Looking for the latest stable version of the Microsoft.Testplatform.
C:\agent\_work\_tasks\VisualStudioTestPlatformInstaller_2c65196a-54fd-4a02-9be8-d9d1837b7111\1.151.3\nuget.exe list packageid:Microsoft.TestPlatform -NonInteractive -Source https://api.nuget.org/v3/index.json
Microsoft.TestPlatform 16.7.0
C:\agent\_work\_tasks\VisualStudioTestPlatformInstaller_2c65196a-54fd-4a02-9be8-d9d1837b7111\1.151.3\nuget.exe install Microsoft.TestPlatform -Version 16.7.0 -Source https://api.nuget.org/v3/index.json -OutputDirectory C:\agent\_work\_temp\VsTest -NoCache -DirectDownload -NonInteractive
Feeds used:
  https://api.nuget.org/v3/index.json

Attempting to gather dependency information for package 'Microsoft.TestPlatform.16.7.0' with respect to project 'C:\agent\_work\_temp\VsTest', targeting 'Any,Version=v0.0'
Gathering dependency information took 1.26 sec
Attempting to resolve dependencies for package 'Microsoft.TestPlatform.16.7.0' with DependencyBehavior 'Lowest'
Resolving dependency information took 0 ms
Resolving actions to install package 'Microsoft.TestPlatform.16.7.0'
Resolved actions to install package 'Microsoft.TestPlatform.16.7.0'
Retrieving package 'Microsoft.TestPlatform 16.7.0' from 'nuget.org'.
  GET https://api.nuget.org/v3-flatcontainer/microsoft.testplatform/16.7.0/microsoft.testplatform.16.7.0.nupkg
  OK https://api.nuget.org/v3-flatcontainer/microsoft.testplatform/16.7.0/microsoft.testplatform.16.7.0.nupkg 51ms
Adding package 'Microsoft.TestPlatform.16.7.0' to folder 'C:\agent\_work\_temp\VsTest'
Added package 'Microsoft.TestPlatform.16.7.0' to folder 'C:\agent\_work\_temp\VsTest'
Successfully installed 'Microsoft.TestPlatform 16.7.0' to C:\agent\_work\_temp\VsTest
Executing nuget actions took 7.53 sec
Caching tool: VsTest 16.7.0 x64
VsTest will use the Test Platform package found in C:\agent\_work\_tool\VsTest\16.7.0\x64

We were using VsTest 16.6.1 without problem before today.
Environment
The agent is running at Windows 10 1803

@aDisplayName Are you able to access this result file Results File: C:\agent\_work\31\TestResults\CMMMM038$_CMMMM038_2020-08-07_14_38_13.trx? As I know ,we have not done any changes related to TestResults directory in 16.7.0. We will try to look into it.

@aDisplayName I tested using VsTest 16.7.0 with specifying ResultsDirectory and it worked fine.

So, in your case trx file was saved to /ResultsDirectory:C:\agent\_work\31\TestResults as you specify it as argument, but AzDo were looking at it in $(Common.TestResultsDirectory) which has value C:\agent\_work\_temp\TestResults, that why it failed to find it there.
And this MS.VS.TestService.VstestConsoleAdapter.NoTrxFoundException: No trx files found in the specified test results directory looks like a AzDo exception. Maybe @ShreyasRmsft can also help us.
@aDisplayName  Could you also provide runsettings file?

Thanks @Sanan07

@aDisplayName Are you able to access this result file Results File: C:\agent\_work\31\TestResults\CMMMM038$_CMMMM038_2020-08-07_14_38_13.trx? As I know ,we have not done any changes related to TestResults directory in 16.7.0. We will try to look into it.

Yes, the trx, coverage, and the raw data were all under C:\agent_work\31 folder.
There is nonthing under C:\agent_work_temp\TestResults folder.

@aDisplayName I tested using VsTest 16.7.0 with specifying ResultsDirectory and it worked fine.

So, in your case trx file was saved to /ResultsDirectory:C:\agent\_work\31\TestResults as you specify it as argument, but AzDo were looking at it in $(Common.TestResultsDirectory) which has value C:\agent\_work\_temp\TestResults, that why it failed to find it there.
And this MS.VS.TestService.VstestConsoleAdapter.NoTrxFoundException: No trx files found in the specified test results directory looks like a AzDo exception. Maybe @ShreyasRmsft can also help us.
@aDisplayName Could you also provide runsettings file?

The only runsettings was the one generated by VsTest task. I've attached the full log here.
21.log
Also, the azure agent version is 2.165.0

@Sanan07 , I agree with you. It seems VsConsole.exe did complete with exit code 0. And indeed it was the DTAExecutionHost.exe which exited with error code 1

@aDisplayName Please look at this https://github.com/microsoft/azure-pipelines-tasks/issues/11526 and https://developercommunity.visualstudio.com/content/problem/756960/21574modulesdtaexecutionhostexe-failed-with-exit-c.html
As I understood by default AzDo writes results in temp folder, but you can overwrite it. But in your case it still looks at temp folder, instead of looking at the folder which you specify as an argument. Try to run again an agent and see if you get the same behaviour.

@Sanan07  But the only thing between pass and fail is the change from VsTest 16.6.1 to 16.7.0.
Actually I tried with 16.6.1 today after we had problem with 16.7.0, and the tasks passed without any glitch. Back to 16.7.0, failed again. Same build agent.

@aDisplayName Could you please provide installation logs for VsTest 16.6.1 as you provided in your post for 16.7.0?
As you may see above 16.7.0 was installed inside work\temp folder, probably that is why it tries to reach trx log file from there :
Adding package 'Microsoft.TestPlatform.16.7.0' to folder 'C:\agent\_work\_temp\VsTest' Added package 'Microsoft.TestPlatform.16.7.0' to folder 'C:\agent\_work\_temp\VsTest' Successfully installed 'Microsoft.TestPlatform 16.7.0' to C:\agent\_work\_temp\VsTest Executing nuget actions took 7.53 sec Caching tool: VsTest 16.7.0 x64 VsTest will use the Test Platform package found in C:\agent\_work\_tool\VsTest\16.7.0\x64

@Sanan07 as far as I know, every azure task is installed under _work_temp

I am able to reproduce the problem with the following azure pipeline script.
Azure Host Agent: windows-latest
Task Version:
Downloading task: UseDotNet (2.171.0)
Downloading task: PowerShell (2.170.1)
Downloading task: VisualStudioTestPlatformInstaller (1.151.3)
Downloading task: VSTest (2.170.1)
Downloading task: PublishTestResults (2.171.0)
Using vstest 16.6.1
When using vstest 16.6.1, all task completed without problem
trigger: none

pool:
  vmImage: 'windows-latest'

workspace:
  clean: all

steps:
- task: UseDotNet@2
  displayName: 'Use .NET Core sdk 3.1.302'
  inputs:
    version: 3.1.302

- powershell: |
    Set-Location $(System.DefaultWorkingDirectory)
    dotnet new mstest -o MyApp.UnitTest
    dotnet build MyApp.UnitTest/MyApp.UnitTest.csproj -o output

- task: VisualStudioTestPlatformInstaller@1
  displayName: 'VsTest Platform Installer'
  inputs:
    packageFeedSelector: 'nugetOrg'
    versionSelector: 'specificVersion'
    testPlatformVersion: '16.6.1'

- task: VSTest@2
  displayName: 'VsTest - testAssemblies - .Net Framework'
  inputs:
    testSelector: 'testAssemblies'
    testAssemblyVer2: |
      **/MyApp.UnitTest.dll
    searchFolder: '$(System.DefaultWorkingDirectory)/output'
    vsTestVersion: 'toolsInstaller'
    codeCoverageEnabled: true
    pathtoCustomTestAdapters: '$(System.DefaultWorkingDirectory)/output'
    otherConsoleOptions: '/ResultsDirectory:$(Common.TestResultsDirectory)'

- task: PublishTestResults@2
  displayName: 'Publish Test Results'
  inputs:
   testResultsFormat: 'VSTest'
   testResultsFiles: '$(Common.TestResultsDirectory)/**/*.trx'

Using vstest 16.7.0
When using vstest 16.7.0, the vstest task failed when publishing the test result.

trigger: none

pool:
  vmImage: 'windows-latest'

workspace:
  clean: all

steps:
- task: UseDotNet@2
  displayName: 'Use .NET Core sdk 3.1.302'
  inputs:
    version: 3.1.302

- powershell: |
    Set-Location $(System.DefaultWorkingDirectory)
    dotnet new mstest -o MyApp.UnitTest
    dotnet build MyApp.UnitTest/MyApp.UnitTest.csproj -o output

- task: VisualStudioTestPlatformInstaller@1
  displayName: 'VsTest Platform Installer'
  inputs:
    packageFeedSelector: 'nugetOrg'
    versionSelector: 'specificVersion'
    testPlatformVersion: '16.7.0'

# To avoid vstest execution error, we need to split tests into group by framework version.
- task: VSTest@2
  displayName: 'VsTest - testAssemblies - .Net Framework'
  inputs:
    testSelector: 'testAssemblies'
    testAssemblyVer2: |
      **/MyApp.UnitTest.dll
    searchFolder: '$(System.DefaultWorkingDirectory)/output'
    vsTestVersion: 'toolsInstaller'
    codeCoverageEnabled: true
    pathtoCustomTestAdapters: '$(System.DefaultWorkingDirectory)/output'
    otherConsoleOptions: '/ResultsDirectory:$(Common.TestResultsDirectory)'

- task: PublishTestResults@2
  displayName: 'Publish Test Results'
  inputs:
   testResultsFormat: 'VSTest'
   testResultsFiles: '$(Common.TestResultsDirectory)/**/*.trx'

Here is the build agent information
2020-08-08T03:14:52.4713503Z ##[section]Starting: Initialize job
2020-08-08T03:14:52.4715025Z Agent name: 'Hosted Agent'
2020-08-08T03:14:52.4715363Z Agent machine name: 'fv-az674'
2020-08-08T03:14:52.4715579Z Current agent version: '2.173.0'
2020-08-08T03:14:52.4767213Z ##[group]Operating System
2020-08-08T03:14:52.4767497Z Microsoft Windows Server 2019
2020-08-08T03:14:52.4767652Z 10.0.17763
2020-08-08T03:14:52.4767782Z Datacenter
2020-08-08T03:14:52.4767933Z ##[endgroup]
2020-08-08T03:14:52.4768088Z ##[group]Virtual Environment
2020-08-08T03:14:52.4768270Z Environment: windows-2019
2020-08-08T03:14:52.4768443Z Version: 20200802.1
2020-08-08T03:14:52.4768749Z Included Software: https://github.com/actions/virtual-environments/blob/win19/20200802.1/images/win/Windows2019-Readme.md
2020-08-08T03:14:52.4769028Z ##[endgroup]
2020-08-08T03:14:52.4769869Z Current image version: '20200802.1'
2020-08-08T03:14:52.4775867Z Agent running as: 'VssAdministrator'
2020-08-08T03:14:52.4815061Z Prepare build directory.
2020-08-08T03:14:52.5078768Z Set build variables.
2020-08-08T03:14:52.5112160Z Download all required tasks.
2020-08-08T03:14:52.5225718Z Downloading task: UseDotNet (2.171.0)
2020-08-08T03:14:54.5404379Z Downloading task: PowerShell (2.170.1)
2020-08-08T03:14:54.8021028Z Downloading task: VisualStudioTestPlatformInstaller (1.151.3)
2020-08-08T03:14:55.1260638Z Downloading task: VSTest (2.170.1)
2020-08-08T03:14:56.7509719Z Downloading task: PublishTestResults (2.171.0)
2020-08-08T03:14:57.5531780Z Checking job knob settings.
2020-08-08T03:14:57.5540533Z    Knob: AgentToolsDirectory = C:/hostedtoolcache/windows Source: ${AGENT_TOOLSDIRECTORY}
2020-08-08T03:14:57.5541884Z    Knob: AgentPerflog = c:\vsts\perflog Source: ${VSTS_AGENT_PERFLOG}
2020-08-08T03:14:57.5542896Z Finished checking job knob settings.
2020-08-08T03:14:57.5868290Z Start tracking orphan processes.
2020-08-08T03:14:57.5921876Z ##[section]Finishing: Initialize job

@aDisplayName Could you run the agent with v16.7 but without this property otherConsoleOptions: '/ResultsDirectory:$(Common.TestResultsDirectory)' and see if AzDo can successfully get the trx file.
As from logs, again it looks like vstest completed successfully, but issue occurs when AzDo trying got fetch trx log file.
@ShreyasRmsft Could you please look at the issue?

@aDisplayName Could you run the agent with v16.7 but without this property otherConsoleOptions: '/ResultsDirectory:$(Common.TestResultsDirectory)' and see if AzDo can successfully get the trx file.

The answer is "Yes" that removing the /ResultsDirectory setting solved the problem. But that is not the solution we can take.
The long story of why we have to use '/ResultsDirectory:$(Common.TestResultsDirectory)':

In our production build pipeline, we have multiple test projects, and we use SonarQube to calculate the overall test coverage.
Some of those unit test projects are targetting .NET Framework, while the rest are targetting .NET Core.
We had problem to run all tests within one VsTest tasks due to the difference of target framework, so we splitted them into two VsTest tasks targetting different framework.
Without setting /ResultsDirectory to $(Common.TestResultsDirectory), the test result in temp folder from the first VsTest task will be cleared out by second VsTest task, which would then prevent SonarQube to collect both test coverage results for SonarQube Code Analysis task.
The solution we've found, is to add '/ResultsDirectory:$(Common.TestResultsDirectory)' option to both VsTest tasks, so that the test results will be preserved after each test run, and be available for following SonarQube code run analysis task to consume.

That is the reason why we have to have /ResultsDirectory option set as it is shown in the sample code.


Modify bar labels in Go Term vs Gene Count

Right now the populationAnnotationCount is shown, although the Y-axis is the number of genes (matches).
Could we show the number of genes in the label, and instead have the percentage of the matches in the populationAnnotationCount in parentheses?
As an example, if we have a GO-term with 5 matches and 82 populationAnnotationCount, the label for that bar should be:

5 (6.1%)

Yes that looks good.  Or we could have a toggle for the Y-axis between actual number and proportion?  If we show proportion we could add another bar next to each bar for the proportion in the background population.

We see that now on hover of bars like this:

Sorry if I was unclear. By label I mean the text on top of the bars.
So basically move the amount of matches with the percentage in parentheses, that is now in the on-hover tooltip to be the label for the bars instead.
We also need some more space to the top as the labels get cropped. If you want to test with this list, it's called PL FlyTF_REDfly_TFs and part of flymine.


"Halve damage" and "P5 health" settings require restarting the game

This seems to be a common problem since I've seen a few people asking about the same thing. After installing GodSeekerPlus and toggling the halve damage and p5 health settings, the damage and hp values don't apply in the HoG, until you restart the game once. After that, they seem to work (unless you uninstall and reinstall the mod again). Obviously not a big issue but it's confusing to people who don't know restarting works.

I cannot reproduce this on my side, toggling them takes effect immediately without needing a restart.
There are cases when Scarab forget to update dependencies (Satchel, Osmi & HKMirror), try uninstall-reinstall in Scarab first.
If the problem persist, you can post your ModLog.txt here for more debug information

Hmm interesting, the settings take effect immediately now for me too. The reason I posted was because I've helped at least two other runners with this problem before, and I used to have this issue earlier as well. Maybe it was the dependencies that weren't updated. Thanks for your helps and sorry for the trouble!


(gdk): ca-central-1 not supported

Feature Description
Making a feature request based off this RePost suggestion:
https://repost.aws/questions/QUe_mJGGF6ScSvyoj0uLixLQ/aws-io-t-pub-sub-sdk-workshop-gdk-tool-fails-in-ca-central-1
I am not the repost thread creator, just someone with the same issue.
Use Case
I used gdk-cli in a publishing pipeline that needs to publish to the canada region.
Proposed Solution
As suggested in repost - add ca-central-1 to the schema.

[ ] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

Hey @gearoid-moore,
Thanks for reaching out and bringing this up. We are working on getting this fixed and will be available on our next patch release 1.2.1 which should be completed in the next couple of days.
Cheers,
Nelson

@gearoid-moore we just released v1.2.1 which will accept the ca-central-1 region. Closing this issue


Tutorial component

to #469
plus small fixes

Also fixes #450 but with comment - see original issue.

thanks :+1:


Jinja2==3.1.0 breaks build workflow

We use
https://github.com/pytorch/vision/blob/56fb0bf5796ac374d4e353032e418236cd73c554/docs/requirements.txt#L5
Internally, they only restrict Jinja2>=2.3. Jinja2==3.1.0, which was released about an hour ago, removes
from jinja2 import environmentfilter

This however is imported by sphinx==3.5.4. Never versions of sphinx have a safeguard .
This trips our CI docs workflow. See this run for an example.

The fix #5674 was quick way to get CI green again. In the long run, I agree, we should move to sphinx >= 4. But that is already tracked in the issue you mentioned.


Set MapDisplay topic durability to transient local

Related to #400
I think it would be better if this were replaced with a property so that publishers with different durability still work. I've left a TODO in case we want to merge this as-is and revisit later. This quick fix is also more easily back-ported to Dashing and/or Crystal.

Closing in favor of https://github.com/ros2/rviz/pull/409


Basic framework for E2E testing of submariner, including one example

The framework is based on the work done in kubefed and kubernetes around E2E, and it's based in ginkgo.

Ok, I have updated the patch following your comments. I still need to add support to target multiple clusters. I can do that as a follow up, or just add another patch on top of this.

Ok, I hope this version looks good enough.
I have updated the load config to allow for non-flattened config files too, also.. the inability to load the configuration at some points stops the whole E2E tests with a non-recoverable error. Otherwise we get lots of failing tests, which, does not make sense, since the issue is not the functionalities being broken, but a bad CI environment/config.


Allocatebug

Fix bug and optionally let allocate methods pre-fill buffers.

Is there anything blocking this PR? I'm affected by the regression on output_buffer_allocate, as its result no longer works with process_into_buffer as intended. I wouldn't mind helping.

Also, output_frames_max does not return a correct upper frames bound at least for the FftFixedIn resampler when nbr_chunks_ready > 1. This happened on v0.13 too, but previously the buffer was just reallocated, which means that relying on the return value of output_buffer_allocate/output_frames_max to avoid allocations has never been effective, but that is now exacerbated due to the latest changes.

I thought it was ready and I was planning to release it as soon as I had some free time. But if there is an issue with output_frames_max then there is still work to do.
Can you open a new issue for that, with a simple example for how to trigger the problem?

Sure, I can try to cobble together a reproduction case! Thank you for your effort in maintaining this library by the way :smile:


Reimplement/rethink "analyze" task

Currently analyze task makes very little sense, is confusing and produces non-deterministic and counterintuitive results.
If you have unit tests, cram tests and integration tests and don't specify analyze as a top-level task, analyze still runs but only analyzes unit tests ignoring cram and integration tests. If analyze is specified as a top-level task then analyze runs after all the tests.
If the coverage, for example, is combined for unit and integration tests, and then checked for 100% combined coverage, then running pyb publish will fail because analyze, not being explicitly invoked, runs after unit tests only, where as the same code with pyb analyze publish will pass all the tests.
I would propose either:

Getting rid of analyze altogether and performing all necessary checks in verify making it a responsibility of individual plugins to bind to that verify task and performing aggregate analysis for all tasks executed by the reactor.
Replacing analyze with analyze_sources, analyze_unit_tests, analyze_integration_tests etc making it the responsibility of those plugins individually.
Something else

@mriehl thoughts?

I like being able to differentiate between check for functional defects and check for warts and potential bugs / style issues. But you're right that it's confusing... I think 2. would be too low level.
The issue I see with 1. is that I won't be able to have a customizable execution order for unit tests / linters. Say I only want to unit test if flake8 has no complaints (or the other way around). Then clearly those need to be separate tasks.
Maybe another possibility is having publish (the default task out of the box) depend on analyze and analyze depend on verify? This is what I usually want (no point in getting "line too long" errors when my tests are red) but this would make it difficult to get it working the other way around.

Well, there are two approaches:

fail fast and report
test everything, collect all the errors, fail and report

Another thing to consider is maybe we will simply remove analyze, unit and integration test and coverage default tasks once I'm done with #188. Then each plugin individually adds either analyze_xxx task or adds to a common analyze task.
Do we want to have flexibility to either fail-on-error and fail-on-end, like Maven does?

I think we should always fail fast because most things (like upload or integration tests) don't make sense when the build is failed.
Getting rid of analyze and verify with #188 sounds good - this would give us flexibility to either call the top-level tasks that flak8 etc reverse-depend on, or set a custom order with default_task.
Right now we can't run "just flake8" since the analyze namespace is cluttered by many plugins.

@mriehl I naturally meant fail-on-end before result-generating tasks such as publish, install or upload.
Alternative would also be add an attribute to "@task(fault_tolerant=False)" and add it to publishers, which would make publishers etc intolerant of previous failures while the other tasks can proceed.
I need to sleep on this :smile:


app:processReleaseGoogleServices FAILED

Build/Submit details page URL
https://expo.dev/accounts/bradydowling/projects/journal-buddy/builds/f160f4ff-b4c8-4b75-b71b-7e6140bd34e1
Summary
This seems like a very similar issue as what was opened here for expo-cli.
Source Map Upload Report

  Scripts

    ~/index.android.bundle (sourcemap at index.android.bundle.map, debug id 232d3e87-d40d-49e9-99d7-0de9bdd7f1eb)

  Source Maps

    ~/index.android.bundle.map (debug id 232d3e87-d40d-49e9-99d7-0de9bdd7f1eb)

> Task :app:checkReleaseAarMetadata

> Task<EMAIL_ADDRESS>
Sentry Logger [info]: Reading source map from /home/expo/workingdir/build/android/app/build/generated/sourcemaps/react/release/index.android.bundle.map

Sentry Logger [info]: Saving modules to /home/expo/workingdir/build/android/app/src/main/assets/modules.json

Sentry Logger [info]: Resolving modules from paths /home/expo/workingdir/build/node_modules

Sentry Logger [info]: Modules collected and saved to: /home/expo/workingdir/build/android/app/src/main/assets/modules.json

> Task :app:generateReleaseResValues

> Task :app:processReleaseGoogleServices FAILED

Parsing json file: /home/expo/workingdir/build/android/app/google-services.json

> Task :app:createBundleReleaseJsAndAssets_SentryUploadCleanUp SKIPPED

FAILURE: Build failed with an exception.

* What went wrong:

Execution failed for task ':app:processReleaseGoogleServices'.

> Missing project_info object

* Try:

> Run with --stacktrace option to get the stack trace.

> Run with --info or --debug option to get more log output.

> Run with --scan to get full insights.

> Get more help at https://help.gradle.org/.

The suggestion there was:

Even though you're not uploading your staging app to Google Play Store you have to use another google-services.json generated specifically for your staging app :) This file contains the package name of your app so when you use the production json file the package names don't match hence you get the error from you first message.

When I go to make a new google-services.json file it requires me to either:

Use a different package name
User a different keystore

From this response it's unclear whether the path forward is to use a different package name or to generate a new keystore. It seems like the package name would have to stay the same (because I'm not making a new app, just a new env/profile) but the answer doesn't mention anything about the keystore.
What is the path forward here?
Managed or bare?
Managed
Environment
npx expo-env-info:
  expo-env-info 1.2.0 environment info:
    System:
      OS: macOS 13.4.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 22.2.0 - /opt/homebrew/bin/node
      Yarn: 1.22.22 - /opt/homebrew/bin/yarn
      npm: 10.7.0 - /opt/homebrew/bin/npm
    Managers:
      CocoaPods: 1.15.2 - /opt/homebrew/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
    IDEs:
      Android Studio: 2023.2 AI-232.10300.40.2321.11567975
      Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
    npmPackages:
      @expo/webpack-config: ~19.0.1 => 19.0.1
      expo: ~50.0.19 => 50.0.19
      react: 18.2.0 => 18.2.0
      react-dom: 18.2.0 => 18.2.0
      react-native: 0.73.6 => 0.73.6
      react-native-web: ~0.19.6 => 0.19.9
    npmGlobalPackages:
      eas-cli: 10.0.2
    Expo Workflow: managed

npx expo-doctor:
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✖ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK

Detailed check results:

(node:9053) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
The following packages should be updated for best compatibility with the installed expo version:
<EMAIL_ADDRESS>- expected version: ~0.27.8
Your project may not work correctly until you install the correct versions of the packages.
Found outdated dependencies
Advice: Use 'npx expo install --check' to review and upgrade your dependencies.

One or more checks failed, indicating possible issues with the project.

Error output
No response
Reproducible demo or steps to reproduce from a blank project

Implement Sign in with Google (using Supabase)
Create a google-services.json file
Deploy it to a preview build

I've tried creating a new Google services json file and conditionally using that based on an environment variable and a ternary in my app.config.ts file but it still doesn't work. I'm at a loss here. Here are two other more recent build attempts: one here and a second where I switched my default keystore.

Seems like this was a result of me having an improperly formatted google-services.json file. I'm using Supabase so I need to figure out how to get that file or create it (since I'm not using Firebase).

The actual issue here was that I thought I needed a google-services.json file but with Supabase I did not need it at all. Instead what I needed to do was:

Create the Oauth Credentials in the Google console
Add the clientId from that credential into the Supabase console under Google > Authorized Client IDs
Remove the android.googleServicesFile field from my app.config.ts file


We don't want lin / log option on Size - picker

That means, for size: always use "lin" with the square root scale for circle area.

Why not? If a measure is logarithmic (like income?) you'd want it to be log, no?

@jheeffer agree. but doing is probably easier than trying to convince Ola that it's useful

Not agree because log scale on size is a nice possibility
Agree because it's a very advanced one and you have  to be aware what you're doing.
I removed it and we move on
Just so you know, allowed scales is part of hook configuration and can be super easily configured from either vizabi or tools page


Patch release request

Is this a bug report?
No

There was recently (early May) a merged PR to work around an issue with users behind NPM proxies/mirrors (https://github.com/facebookincubator/create-react-app/pull/2147/files)
There has not been a release since this PR was merged. Would I be able to request a patch release? This is blocking at the moment for our team - we have very strict internet access rules, and are unable to update our NPM proxy software.
It would be a life saver :)

I'll try to get a patch out within a few days. Currently working on batching a few other changes together for it.

This is all good now following the release of react-scripts - cheers!


Implementing Datatables

Closes #113

Thanks, works wonderfully! ...as soon as I remembered to run npm install that is. :-)


Appsource not supporting SendEvent note needs more clarity and reasoning

[Enter feedback here]
The note on the Send Event on AppSource is not supported is quite an issue for ISV's wishing to be good Microsoft partners, is this due to the AppSource team limiting the manifest sets and is going to be fixed in time?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9e12d688-9620-e8f2-871d-922ec98008b5
Version Independent ID: a8b409f3-44f7-97e5-d722-cbf04edc0653
Content: On-send feature for Outlook add-ins - Office Add-ins
Content Source: docs/outlook/outlook-on-send-addins.md
Product: outlook
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

As of now, we have blocked the on-send add-ins on store due to Security reasons. However, We are working on an enhancement that will unblock it. Its in our backlog

As of now, we have blocked the on-send add-ins on store due to Security reasons. However, We are working on an enhancement that will unblock it. Its in our backlog

Thanks for the feedback is there a specific reason from a security standpoint as surely if side loading is possible defeats and or creates an observational concern for our clients if deemed a security reason..

Store listing of add-ins allows end users to find and install the add-ins. Currently our security policies don’t allow wide distribution of add-in’s that are invoked automatically from store. On-Sends is one example of that. We currently do not have provisions/control to inform end users about such add-in capabilities at the time of add-in installation or updates.

Having said that, we are in the process of making updates on this. We are working towards making block on send like add-in’s available on store


Add help message to freeze.py

I usually run python freeze.py --help to remind myself of how it works..... but instead it creates a environment.py---help.yml file

Whoop!


Rename SynchronizedIterator to SynchronizedAdvancer

Because SynchronizedIterator is not an iterator in a C++-sense, we should rename it to something else. We thought about SynchronizedAdvancer, seeing that it already has the advance() method.

Can't this simply be e.g. SynchronizedTraversal? I mean that is at least valid and existing word.

advancer is a valid word, too. See dictionary records for advancer, for example ;) And I must say that I like advancer. It makes it clearer to me what the class does than anything else, to be honest.

https://www.oxfordlearnersdictionaries.com/spellcheck/english/?q=advancer
https://dictionary.cambridge.org/dictionary/english/advancer
I rest my case.

Nah, who would believe Oxford or Cambridge dictionaries these days, anyway? I believe in GNU version of the Collaborative International Dictionary of English :joy:


fix(ocpi-2.2.1): Add Content-Type header on requests (if needed), on all responses & fixed headers case sensitivity

Change notes
Only for ocpi 2.2.1

Content-Type: application/json header is now added on requests if the body is not null
Content-Type: application/json header is now added on all responses
Headers are not case sensitive anymore. It means that X-Request-ID and X-Correlation-ID are properly propagated in responses even if the case does not match. Note: Authorization header was working because it also accepted authorization

Migration guide
If you manually added Content-Type header & normalized headers in your Transport implementation, you can remove it.
Otherwise, you do not need to update anything. All the changes are included in the lib.
Notes
For versions 2.1.1 and 2.1.1 Gireve, two issues have been open:

https://github.com/IZIVIA/ocpi-toolkit/issues/12
https://github.com/IZIVIA/ocpi-toolkit/issues/13

I will also add an option to specify explicitely the X-Request-ID and X-Correlation-ID. It will be useful to test that these headers are properly propagated.

It is now possible to define how X-Request-ID and X-Correlation-ID are generated. Two methods were added to TransportClient interface. By default, the behaviour stays the same, it generates a random UUID.
I also greatly improved Credentials tests by checking every request / response done during the process. This mecanisme can be reused in integration tests for anything else.


Update workflow-in-sharepoint-server.md

corrected a typo

@asgr86 - thank you! Much appreciated!


Remove CVE check from minimal collection

JIRA: HACBS-2281

Looking in https://issues.redhat.com/browse/HACBS-2190 I'm not sure this is what we want, so move to draft until we can discuss it.

Replaced (sort of) by https://github.com/enterprise-contract/config/pull/1 .


Docker compose

Added support for both fig and the new docker-compose. It is looking for docker-compose existance and then falling back to fig.

:+1: looks good to me.


check node before prefetching

follow-up #298

I really really really really don't like the four nested if statements but Rust won't me chain if let and if <expr> together.

@adiprerepa: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
a9c0e55609f88c9da0a29b60187c71a67f7b4cc6
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


(RE-9732) Use artifactory instead of nexus (4.4.x branch)

Previously would send releases and snapshots to nexus, we want to ship these to artifactory instead.
Tested and shipped to artifactory

Test PASSed

CLA signed by all contributors.


Add a notebook on opening a remote zarr dataset

After many weeks of experiments in the background and a flurry of ideas and patches (https://github.com/climet-eu/lab/compare/7846b575c3c03821fef52c4264663f65e769254d...086f285d98977a74a6fca4da3bad5a44115f9362), aiohttp and fsspec now work sufficiently well in the lab to support opening remote zarr datasets :D
This PR adds a short notebook showcasing this functionality with a ~32TB example dataset

@SF-N Opening a remote Zarr datasets (here hosted on S3 but we're accessing it via HTTP) now works!
Do you have any suggestions as to what else should go into this notebook, aside form the standard titles and short explanations?

Thanks a lot, this is great.
For now, I don't think there is a lot to add to the notebook.
Depending on the data, it might be necessary to use earthkit.data.from_source to load the data instead of xarray.open_dataset (see the hplp_experiment branch for an example).
But I would postpone this to when we are working on the target datasets from IFS, EC-earth and ICON.

So far I’m a bit sceptical of earthkit’s from source, as it seems to mostly rely on downloading the datasets. Obviously we cannot do this in the online lab (we have a few MB of cache there, so any GB or TB dataset must be accessed remotely). There are good existing solutions, some format-specific (e.g. for NetCDF), some more general (using fsspec with zarr or h5netcdf). I think we should support those general options first and perhaps you can suggest to the earthkit team to add fsspec as another source (which then brings additional sources like remote http or s3 in for free) / to add an already-opened xarray as a source.

I've also made progress on loading the dataset with s3fs (see https://gist.github.com/juntyr/8b73265b2eeb766eba7075295d3cafbf), which I'll add to this notebook once it fully works (though it is much slower than going through HTTP directly right now)

@SF-N I've also experimented with supporting GRIB at https://gist.github.com/juntyr/14b3f80c58a39624641f9021450e5f28, but it seem like earthkit.data only supports streams (and not random-access file-like objects) for now.
I've opened https://github.com/ecmwf/earthkit-data/issues/467 for this.

I've given up a bit on native support for NetCDF through netCDF4 (trying to make the libcurl dependency work has eaten far too much of my brain) or h5netcdf (which seems to not support large datasets).
However, I've managed to get everything to work using kerchunk! We can now load a ~19GB NetCDF file in the online lab:
https://gist.github.com/juntyr/23c2df3b3e20ac351591b99d70e19ca8

I've also tried to get it to work with GRIB files, but unfortunately merging different messages doesn't fully work yet in kerchunk (tracked in https://github.com/fsspec/kerchunk/issues/358 and https://github.com/fsspec/kerchunk/issues/150).
@SF-N perhaps you could reach out to the cfgrib or eccodes-python teams after your holiday to look at these kerchunk issues and see if they could help with a fix - being able to load larger remote GRIB files would be very valuable for the community.
My not-fully working example (the hybrid dimension is 1 instead of 10) is here:
https://gist.github.com/juntyr/9ebda19683691956700adacd12c4f806

The combined and documented notebook is now at https://gist.github.com/juntyr/a89175eb60a80150dc17bf553cd2e2d7.
I'll wait for sympy to be available in the lab before updating and merging this PR.


Segmentation fault when negative values is set to terminal size

Description
Set negative values to contour.yml
# Determines the initial terminal sice in characters.
  terminal_size:
    columns: -130
      lines: 30

and see the crash.

It also happens if the value is not set at all. I tried to use the YAML map merging syntax to ease out my config file and just "inherit" most of the settings, and either it's not supported by the YAML parser we use, or something other goes wrong.

After years and years and years of trying not to do that, I finally did fix it. :)


Update to TypeScript 4.3 and require use of new override keyword

TypeScript 4.3 has been out for about 3 months now, so we really ought to move up before we fall too far behind.
It turns out there have not been many breaking changes since 4.1, and all the new compiler errors I hit moving up seemed genuinely helpful.  As always, the last two versions of TypeScript include a number of useful improvements and new features, so be sure to check out the full release notes for TS 4.2 and TS 4.3!
The biggest change that I'm hoping to take advantage of in TS 4.3 is the new override keyword.  This has the potential to catch a lot of mistakes at compile-time, and I believe we should make its use mandatory (via the noImplicitOverride tsconfig option).
While we're staying up-to-date with TypeScript, we are (for the moment) still stuck on older versions of two other key tools in our toolchain (api-extractor and typedoc).  Fortunately, I was able to use pnpm hooks to force those tools to use TypeScript 4.3 as well - so we can start using override/noImplicitOverride today!
Finally, since I added override in a few thousand places, I've gone thru and explicitly called out everywhere I had to react to a compiler warning in review comments, just make sure they don't get lost among the diff noise.

D:\vsts_b\2\s\core\geometry\src\test\geometry3d\Angle.test.ts(904,18): error use-isnan : Use the isNaN function to compare with NaN.
D:\vsts_b\2\s\core\geometry\src\test\geometry3d\Angle.test.ts(905,18): error use-isnan : Use the isNaN function to compare with NaN.
D:\vsts_b\2\s\core\geometry\src\test\geometry3d\Angle.test.ts(906,18): error use-isnan : Use the isNaN function to compare with NaN.

Probably should just delete these - we're not testing the browser.

FYI, now that all comments are resolved I plan on bypassing the review requirements and merging this once all build pipelines succeed (to avoid chasing down 20+ required reviewers).
If you have any issues with this change (or just want me to wait for your review), speak now or forever hold your peace!
CC: @ramanujam-raman @kabentley @ColinKerr @EarlinLutz @khanaffan  @grigasp  @RBBentley @swbsi @swwilson-bsi


"sudo startunity" the chroot update dosen't work

Hi, I just updated my ubuntu to 14.04. I think I made a little mistake at the work through.
This is the massage I get with "sudo startunity":
chronos@localhost / $ sudo startunity
Entering /mnt/stateful_partition/crouton/chroots/precise...
Unknown username "whoopsie" in message bus configuration file
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension GLX
[dix] Could not init font path element /usr/share/fonts/X11/misc, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
/usr/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
Running exit commands...
/usr/bin/xinit: connection to X server lost
waiting for X server to shut down
Unmounting /mnt/stateful_partition/crouton/chroots/precise...
After that, I tried to run an update:
chronos@localhost / $ sudo sh ~/Downloads/crouton -n precise -u
Downloading latest crouton installer...
######################################################################## 100.0%
/usr/local/chroots/precise already exists; updating it...
Preparing chroot environment...
unity target does not work in xephyr in trusty due to missing egl support.
And this is the log for the croutonversion
chronos@localhost / $ sudo enter-chroot -n precise croutonversion
Entering /mnt/stateful_partition/crouton/chroots/precise...
A chroot setup script still exists inside the chroot.
The chroot may not be fully set up.
However, it appears the setup script is invalid.
Removing the chroot setup script. You may want to update your chroot again.
Unknown username "whoopsie" in message bus configuration file
crouton: version 1-20141226162305~master:21db8947
release: precise
architecture: armhf
targets: unity
host: version 6457.68.0 (Official Build) beta-channel nyan_big
Unmounting /mnt/stateful_partition/crouton/chroots/precise...
what can I do to get around that problem?

Yeah, upgrading was a mistake if you want to keep using Unity.  Either make a new precise chroot if you want to go back to unity, or do the following to switch to another DE (such as xfce):
sudo enter-chroot -u root sed -i 's/unity/xfce/' /etc/crouton/targets
sudo sh ~/Downloads/crouton -n precise -u


Flutter doesn´t create the system directories

Steps to reproduce
Well, it all started when creating a Flutter project after updating to version 3.27 of the framework. When initializing a project, whether with Android Studio or the CLI, all the components are created normally, but when opening the directory, none of the target system directories appear.
And when running "flutter create ." to rebuild the project, it only initializes and attaches the web project to the root of the base Flutter project.
Expected results
As a result, it should present all the directories for the systems to be developed (even Android Studio allows selecting the target systems), yet it still doesn't create any of them.
Actual results
As a result, it should present all the directories for the systems to be developed (even Android Studio allows selecting the target systems), yet it still doesn't create any of them.
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

@bryandelgado99
Can you provide more details about system directories with visuals or elaborate when you say the tool isn't creating system directories as compared to previous stable ?


Add script to run after bootstrap in userdata

Description
What problem are you trying to solve?
Sometimes I need to perform a specific action after executing bootstrap.sh.
But now we can only put custom userdata before running bootstrap.sh.
It would be nice to have a setting like customAfterUserData.
How important is this feature to you?
After bootstrap.sh is executed, I need to run "systemctl restart runtime.slice".

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What are you trying to run after the boostrap.sh script? What can't be handled through adding it at the end of your userData?

This looks like a duplicate of #3915. Do you mind adding a +1 to that issue and than any additional context that you want to share for your use-case?

Closing as a duplicate.


ClientID & ClientSecret not created in 1st Tutorial of mission - Set Up Integration Suite Trial

Tutorial URL: https://developers.sap.com/tutorials/cp-starter-integration-cpi-design-iflow.html
Step 8, point 2.
In the Username and Password field, enter the clientid and clientsecret that you copied from the service key that you created when you provisioned the SAP Cloud Platform Integration tenant.
The "SAP Cloud Platform Integration tenant" tutorial has been replaced by "Set Up Integration Suite Trial" (https://developers.sap.com/tutorials/cp-starter-isuite-onboard-subscribe.html) which does not include a step to generate the clientid and clientsecret required in the Postman transaction.

Hi,
Having added the step to create the ClientID & ClientSecret given in the old "SAP Cloud Platform Integration tenant" tutorial the final Step 8 works correctly. Please update "SAP Cloud Platform Integration tenant" tutorial to include this step.
Kind regards, Andrew

Hi Andrew,
Thanks for your advice.
We have considered this feedback and incorporated in the tutorial.
You can see the changes shortly.
Regards,
Vikram Kulkarni

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Adds January 2021 API version

Description
Adds support for using the latest API version.

I've updated the register.ts as well and signed the CLA. I've also update the appropriate changelogs, thought not 100% sure if I did it right. Please let me know if I need to change or update something.

I've updated the register.ts as well and signed the CLA. I've also update the appropriate changelogs, thought not 100% sure if I did it right. Please let me know if I need to change or update something.

Fixed by #2001


Adds specialization constant to computeheadless

I noticed that you had the comment in headless.comp for the computeheadless project, and as such I added specialization constants and removed the comment about said specialization constants

Thx for the PR!


"RTL" and "LTR" support at runtime

hello, first you'r doing great guys. great ui libarary for twcss
i read the docs about RTL support and it shows that we need to use "rtl: true" and put dir='rtl' to root element and the theme will be rtl.
the problem is if i change dir to dir="ltr" things will get broken.. is that mean that daisy ui support "one" dir that should be declared before build time and i cant change it during run time to LTR ?

Duplicate of https://github.com/saadeghi/daisyui/issues/193
Let me know if you have any questions

Having 2 different CSS files for RTL and LTR is the most efficient solution for any CSS library as long as we're using left and right for paddings, margins, positions, etc. Because they all should be reversed in a RTL page and if we include both styles in one file, all our users should load unused style to their browsers because users either use RTL or LTR almost for ever. It's not something people switch between regularly.
Here's and example that creates 2 CSS files for LTR and RTL it switch CSS files using Alpine.js.
This example is made a year ago and dependencies are old but you get the idea:
https://github.com/saadeghi/daisyui-bidirectional-builds
Let me know if you have any questions.


ENH: scipy.signal - Addition of CSD, coherence; Enhancement of welch

This is a new PR for adding Cross Spectral Density computations to scipy.signal. The previous PR (#4468), extended the existing welch algorithm for the CSD, but then I found that matplotlib.malb has an existing, much faster, version that uses strided arrays for efficiency.
I have adapted the matplotlib.mlab code for use in scipy.signal. This required rewriting welch to use the same underlying stride algorithm.
Some reworking of the matplotlib code was needed to make functions work for
multidimensional arrays, as the current scipy.signal.welch function allows.
Things were also adjusted to keep the same welch API.
Advantages of this code change include:

A speedup of about 8x in welch
A speedup of about 6x in csd compared to extending the current
algorithm to cover the cross spectral density.
Straightforward extensibility to add spectrogram functionality

There are probably still rough edges, but this seems to be working. Some
tests are included. (Known test failure : test_complex_32 in
test_spectral.TestWelch; effectively correct, but the tolerances are too
tight.)

The private functions _stride_repeat, _stride_windows and _apply_window are used exactly once, contain unnecessary checks (input validation should be done at the beginning of the public functions) and large docstrings that make the code hard to read. The actual functionality is only a couple of lines. I suggest to either remove these functions and simply add a comment inline about what as_strided is doing in each case, or at least strip them down to the minimum needed.

@e-q nice, timings look very promising. It would be good to add a benchmark for each function that is sped up here. This should be quite straightforward, see https://github.com/scipy/scipy/pull/4621 for an example

Thanks for the feedback! I've cleaned things up a bit; I suppose I wasn't critical enough of the original code's structure.
Benchmarking sounds like a great idea. Oddly enough, these functions are now slightly slower than their matplotlib ancestors... I'll get to the bottom of it.

Thanks, changes all look good - now this PR is pretty clean and easy (or easier) to review.

Good catches @ewmoore! Cleaning up that unnecessary work won an almost 10% speed boost.
Indeed, the empty input cases are probably not so common, but I wouldn't want to cause any regression. To this end, I shuffled things around a bit to return the correctly broadcast shape for the CSD when only one input is empty, but can otherwise be broadcast (and tests for that case). Hopefully my implementation isn't too clunky...
I.e. csd(np.empty((10,10,3)), np.zeros((10,0,1)), axis=1) returns a shape of (10,0,3)

I've written some simple benchmarks for welch and csd, that just run the functions on random arrays about a million items long. Comparing the new welch to the master branch on my machine:
BENCHMARK                                    BEFORE      AFTER     FACTOR
signal.CalculateWindowedFFT.time_welch       785.73ms    66.92ms   0.085169206x

The latest commit failed because np.squeeze doesn't take the axis kwarg in 1.6.2...

Is https://github.com/matplotlib/matplotlib/issues/4324 anyhow relevant? (I've no idea; have just noticed that MPL issue, and this PR seems to use some code from roughly the same part of MPL...)

@ev-br Good catch!

The welch function in scipy 0.15 has the same bug that matplotlib/matplotlib#4324 describes, as can be found by running the same example code shown there, just with the appropriate call structure:
f, P = sig.welch(u, nperseg=u.size, fs=1/dt, window=sig.boxcar(u.size), detrend=None, noverlap=0, scaling='density', return_onesided=True)
This means that the existing unit tests for welch, and the tests for CSD that I derived from them, that involve odd numbered fft segments will have to be changed as well.

@tacaswell you did https://github.com/matplotlib/matplotlib/pull/4326, could you have a look on https://github.com/e-q/scipy/commit/853a4e20ad67472361fca3b177d7a7d7b959a24d please?
Just to be clear: I don't have an opinion about this PR (apart from noticing that the speedup looks nice), and I'll defer to @rgommers and @ewmoore for a review / decision on it.

Any suggestions what should still be worked on here? I'm eager to hear any additional feedback!

@e-q a basic example with a plot in an Examples section in the docstrings of the new functions would be a nice bonus.
I'll play with this PR a little now; it seems to be in pretty good shape.

@ewmoore do you still want/need to review the algorithm changes in more detail, or is this good to go from your POV?

Its probably fine. I'll have some time this weekend to look if you could
give another day or two.
On Thu, Apr 30, 2015 at 4:23 PM, Ralf Gommers<EMAIL_ADDRESS>wrote:

@ewmoore https://github.com/ewmoore do you still want/need to review
the algorithm changes in more detail, or is this good to go from your POV?
—
Reply to this email directly or view it on GitHub
https://github.com/scipy/scipy/pull/4682#issuecomment-97955425.

The only thing I see is that I don't think the comment and reference to Bartlett's method really belongs anywhere but in welch.

Rebased, to take #4766 into account.

Nevermind, I must have been looking at an old version.  This looks good to me.

LGTM too. Checked the benchmark, runs and for welch is indeed 8x faster than on current master. So in it goes. Thanks @e-q !

Ack, should I have squashed the commits first?

It's fine like this. It's a pretty large PR that went through some changes; 17 commits is large-ish but not completely ridiculous.

@e-q Thanks for this PR, it is a nice addition to scipy.
One quibble (and sorry to get here late with this):  In the description of the fs argument, it should not say that the units are Hz.  Nothing in the code requires the units to be Hz, so saying that is confusing.  (E.g. if I have sunspot data that was recorded monthly, do I really have to convert my sample rate to Hz?)


Fixed preview url paths

What is the change?
Modified HTML+CSS folder path
Related issue?
closes: #321
How was it tested?
I tested it locally, it works fine.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelineswhile contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Have you tested the code before submission?
[x] Have you formatted your code ? (You can use any html,css beautifier)
[x] My changes generates no new warnings.
[x] I'm Diversion2k23 contributor.
[x] I have commented my code, particularly in hard-to-understand areas.

The issue isn't resolved yet it seems. Check the deploy preview !