Study autoloaded

Changes to support a study flag to mark as automatically loaded. In general, it should always be false, once we support autoloading we will use this flag.

Codecov Report

Merging #3046 (a23d701) into dev (5a308ea) will decrease coverage by 0.00%.
The diff coverage is 93.75%.

@@            Coverage Diff             @@
##              dev    #3046      +/-   ##
==========================================
- Coverage   95.03%   95.02%   -0.01%
==========================================
  Files          74       74
  Lines       14284    14279       -5
==========================================
- Hits        13575    13569       -6
- Misses        709      710       +1

Impacted Files
Coverage Δ

qiita_db/metadata_template/prep_template.py
99.06% <ø> (+1.03%)
:arrow_up:

qiita_db/test/test_commands.py
95.09% <ø> (ø)

qiita_db/test/test_util.py
99.70% <ø> (ø)

qiita_db/util.py
91.57% <ø> (ø)

qiita_db/processing_job.py
73.80% <68.75%> (-0.04%)
:arrow_down:

qiita_db/__init__.py
100.00% <100.00%> (ø)

qiita_db/analysis.py
96.80% <100.00%> (-0.01%)
:arrow_down:

qiita_db/handlers/artifact.py
97.43% <100.00%> (ø)

qiita_db/handlers/prep_template.py
94.73% <100.00%> (+0.14%)
:arrow_up:

qiita_db/handlers/tests/test_artifact.py
97.61% <100.00%> (+0.03%)
:arrow_up:

... and 9 more

Continue to review full report at Codecov.

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

Thank you for review; that's a good question! I don't think we should display it but it will be good to limit functionality for those studies we didn't submit ...

Yes, I think I was thinking mostly in terms of a meta-analysis to easily check for systematic effects.


about result

thanks for your code. but when i run ,i cant got same result as you say mae=62.3,at epoch 353.

can you give me some advice.
all code not change expect the path of data.

I have run the code for about ten times. In my memory, the mae can be less than 100 at ~10th epoch. Just now I run the code again and get the following result:

May be you can try again.  I can't find any other possibility for now.
Good luck!
If you find the reason , please inform me, thank you.

thanks for your code. but when i run ,i cant got same result as you say mae=62.3,at epoch 353.

can you give me some advice.
all code not change expect the path of data.

I have run the code for about ten times. In my memory, the mae can be less than 100 at ~10th epoch. Just now I run the code again and get the following result:

May be you can try again. I can't find any other possibility for now.
Good luck!
If you find the reason , please inform me, thank you.

thanks for your code. but when i run ,i cant got same result as you say mae=62.3,at epoch 353.

can you give me some advice.
all code not change expect the path of data.

Did you solve the problem? I also tried the code but I could only get large MAE as you did. Would you mind sharing your solutions if you fix it?

@yanfangfangfang @ElaineXiaoke  I think maybe the problem is at the generation of density map. You can check the data_preparation/k_nearest_gaussian_kernel.py to generate the correct density map. I think it will work.

in  the code of data_preparation/k_nearest_gaussian_kernel.py.   'gt' don't definie before ,maybe there should be   'points'

Hey!
Just putting this here, it might be related.
Thanks for this, I am using it for a custom dataset, and seems to be working with some small issues. I can achieve nice results. I would like to point out 2 things though. First in the line below, an integer is divided by another one.
https://github.com/CommissarMa/Context-Aware_Crowd_Counting-pytorch/blob/07f86a5d03664b87812557c429df1835cb2e3124/my_dataset.py#L35
Now in Python 2.7 this will yield another integer, so in our case 0 or 1, but most likely 0. So if someone is using 2.7 then changing to 3.x could solve this, Or change 255 to 255.0 (I recommend the latter). I also got awful results before doing so.
The second thing is for the validation part. In the dataset enumerator you are doing a random flip if I am not mistaken.
https://github.com/CommissarMa/Context-Aware_Crowd_Counting-pytorch/blob/07f86a5d03664b87812557c429df1835cb2e3124/my_dataset.py#L43
I assume this is for data augmentation. Which is nice and helps the training procedure, but not very fortunate during validation in my opinion. It is just a suggestion, it would be better to not flip any image, or flip all, or validate on both normal and flipped images, or basically any option is good, which does not involve randomness for validation. Although if one considers the possibility to compare results to other methods then most likely the "no flipping" version is the most desirable, to help to ensure that the results are evaluated on the same set.

very thanks for your advices. and i run code with python 2.7  there should be  /255.0.

@csonde You are right. I will fix them. Thank you.

Hi @yanfangfangfang , have you finally achieved the MAE (62.3) which was proposed in the paper for Shanghai Part A ? As I can only get about 66 even after 1000 epochs. Many thanks.

Hi @yanfangfangfang , have you finally achieved the MAE (62.3) which was proposed in the paper for Shanghai Part A ? As I can only get about 66 even after 1000 epochs. Many thanks.

no i just got the same result as you, i can't found my problem. but i use the pre-model of code author can reach the MAE(about 62). if you fix, please concat ,thank you very much.

Hi @yanfangfangfang , have you finally achieved the MAE (62.3) which was proposed in the paper for Shanghai Part A ? As I can only get about 66 even after 1000 epochs. Many thanks.

no i just got the same result as you, i can't found my problem. but i use the pre-model of code author can reach the MAE(about 62). if you fix, please concat ,thank you very much.

Thank you for your prompt reply, I will update it if I reach the MAE.

I have the same problem that mae=66,Have you fix it?

Hi @yanfangfangfang , have you finally achieved the MAE (62.3) which was proposed in the paper for Shanghai Part A ? As I can only get about 66 even after 1000 epochs. Many thanks.

no i just got the same result as you, i can't found my problem. but i use the pre-model of code author can reach the MAE(about 62). if you fix, please concat ,thank you very much.

Thank you for your prompt reply, I will update it if I reach the MAE.

I have the same problem that mae=66,Have you fix it?


WIP: Add ADR for removal of Smartdown

This documents our decision to remove Smartdown from the Smart Answers project.
See Documenting Architecture Decisions1 for some background of ADRs.
See presentation/adr-0012 and backdrop/adr-0013 for examples of ADR use
within GDS.

I plan to revisit this but I'd appreciate any feedback you might have, @floehopper.

I'll come back to this again, but here are a couple of quick initial poorly-expressed thoughts while I think of them:

The state of many of the Ruby Smart Answers would've made it hard to convert them to Smartdown without extensive refactoring.
Adding new features to Smartdown would generally have needed extensions to the grammar and hence the parser. I think the cost of adding new features to Smartdown would've been relatively high, especially considering that Ruby Smart Answers already had all the functionality we needed (apart from multiple questions-per-page).

Thanks, @floehopper. I've now incorporated your comments. Feel free to suggest any other amendments.
 Are there any obvious gaps in the document?

I've only had time to skim this, but i'd want to give some proper feedback before merging, so could you hold off a bit? Mostly reflecting the initial aims of Smartdown (eg, publishable/workflowable representation).

Mostly reflecting the initial aims of Smartdown (eg, publishable/workflowable representation).

@dsingleton: Would this not be more appropriate in a separate ADR, possibly in the Smartdown repo?

I've spoken to @dsingleton and we've agreed that documenting Smartdown should be in a separate ADR. I'm going to rebase this on master in preparation for getting it merged.

@floehopper: Is there anything else you want to add to this or can I merge it?

I think you should go ahead and merge it. I think what you have is pretty comprehensive and we can always add stuff later.

I'm happy to write up an ADR 0 for the addition of Smartdown (could you add a card to the trello and put my face on it? ta).
I've got a couple of small suggestions before merging. I'll add them now.

Added some comments about clarifying the intent of the ADR, it's good, but feels a bit focused on what and less of the why, which is the important bit to preserve.

I'm happy to write up an ADR 0 for the addition of Smartdown (could you add a card to the trello and put my face on it? ta).

Done - https://trello.com/c/4QGJGBGQ/130-add-architecture-decision-record-adr-about-smartdown

@dsingleton: Thanks for the feedback! I've attempted to address it in the more recent commits and would appreciate you taking another look when you have a minute.

I've merged this in 968867b4eca8cde37fea9562a54c6eb130f7eec2. Any further discussion can happen as a new pull request.
I manually merged it (rather than rebasing on master and force-pushing to this branch) in order to retain the discussion in here.

:+1:


App 761: New Github v2 renderers

Utils method to encodeURL is now public;
Metadata parser supports multiple items (list) and the root item can have fields too and not only objects.

Can one of the admins verify this patch?


opl3bankeditor, opn2bankeditor: init

Motivation for this change
A small cross-platform editors of the OPL3 and OPN2 FM banks of different formats
Useful for opl/opn synthesizers brought via separate PR
https://github.com/NixOS/nixpkgs/pull/53659
Project page https://github.com/Wohlstand/OPL3BankEditor
https://github.com/Wohlstand/OPN2BankEditor
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build opl3bankeditor opl2bankeditor

@etu Fixed, thank you!

@GrahamcOfBorg build opl3bankeditor opl2bankeditor

@gnidorah Thanks! :-)

@etu Thank you!


How do you respond to static HTML?

If  trying to response to static HTML, double quotation marks at the beginning and the end it has also been output.
Please tell me how to respond correct static HTML.
val getIndex: Endpoint[String] = get("index.html") {
   io.finch.Output.Payload[String](value = "
Hello
", charset = Some("utf-8"), contentType = Some("text/html"))
}

Response is
"
Hello
"

Solved.
val getIndex: Endpoint[String] = get("index.html") {
   val text = "
Hello
"
   val buf = com.twitter.io.Buf.Utf8(text)
   io.finch.Output.Payload[String](value = buf, charset = Some("utf-8"), contentType = Some("text/html"))
}


Dockerfile for Shotover

Example of how to use, assuming your config and topology file are in the home dir:
docker run -t -v /home/conor:/config shotover-proxy --help
docker run -t -v /home/conor:/config shotover-proxy -t config/top1.yaml -c config/config.yaml
I've registered a "shotover" user on Dockerhub and will also integrate publishing our releases in this PR.

I've tested the workflow on this repo: https://github.com/conorbros/hot-restart-proxy
Published results can be seen here: https://hub.docker.com/repository/docker/conorbros/hot-restart-proxy


Make login id non-case sensitive

Several users (mostly SW) having difficulty because they are entering their email with capital letters and unable to log in. Is it possible to remove the condition of case-sensitivity for log-in?

Note for future development:
The password matching code is part of Keystone.  If we want to handle this outside of a Keystone update, I'd recommend the following:

determine how to decrypt the passwords using the bcrypt library
write a script to update every user record in the system, decrypting the password, converting it to lowercase, then resaving it to the record
update the account code to convert newly submitted passwords to lowercase (handles saving through the website)
update all user models with a presave hook to convert all passwords to lowercase (handles saving through the model)
update the login functionality to convert the password to lowercase before submitting to log in the user

captured in 338.


Add option to disable Swiftclick on a per element basis

Is is possible to do this? I am using the Flickity carousel by Metafizzy and this conflicts.
Feature request?

Yes, in fact this is something I've been thinking about adding, as the same behaviour is exhibited when using Google Maps, and other libraries that implement their own touch-to-click event conversion.
My only reservation is that this addition could bloat the code-base. I'll look into it when I have some spare time.

@mrmartineau This has now been implemented in release 1.2.0 (1686eb1).
Also published to npm :smile:

Yes! :+1: :100:


Home Assistant 2024.1 warnings

Version of the custom_component

Latest.
Configuration

N/A

Describe the bug
Warnings from HA.
Not the only custom component with these.
Debug log

2024-01-05 21:20:03.055 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPBackLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 1> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.055 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPMoodLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 17> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.061 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPBackLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 1> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.061 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPMoodLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 17> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.064 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPBackLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 1> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.064 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPMoodLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 17> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.171 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPBackLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 1> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.171 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPMoodLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 17> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.187 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPBackLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 1> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.187 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPMoodLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 17> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.574 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPBackLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 1> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-01-05 21:20:03.574 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.openhasp.light.HASPMoodLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 17> and color modes, please create a bug report at https://github.com/HASwitchPlate/openHASP-custom-component/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

Same issue here.
The logs suggest mentioning the following page: https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

These warnings are now fixed in Pre-Release 0.7.2. Please help test it before release by redownloading this version of the Custom Component in HACS.

After updating to version 0.7.2, the component stopped working
2024-03-06 01:16:48.142 ERROR (MainThread) [homeassistant.components.script] Script with object id 'plate04_timer_popup' could not be validated and has been disabled: template value should be a string for dictionary value @ data['sequence'][0]['data']. Got {'keyword': 'jsonl', 'parameters': '{"page":0,"id":150,"obj":"obj","x":85,"y":90,"w":310,"h":340,"radius":15,"click":true,"border_side":0,"bg_color":"#0B61A4"} {"page":0,"id":151,"parentid":150,"obj":"label","x":10,"y":10,"w":48,"h":50,"click":false,"text":"{{ entity_icon }}","text_color":"#FFF","text_font":48} {"page":0,"id":152,"parentid":150,"obj":"label","x":0,"y":18,"h":30,"w":320,"align":"center","text_color":"#fff","text_font": 24,"text":"{{ entity_name }}"} {"page":0,"id":153,"parenti...
2024-03-06 01:17:39.519 ERROR (MainThread) [homeassistant.components.light] Platform openhasp does not generate unique IDs. ID 3030f973b8d4., already exists - ignoring light.plate04_light_2
2024-03-06 01:17:39.521 ERROR (MainThread) [homeassistant.components.light] Platform openhasp does not generate unique IDs. ID 3030f973b8d4.[ already exists - ignoring light.plate04_light
2024-03-06 01:17:39.521 ERROR (MainThread) [homeassistant.components.light] Platform openhasp does not generate unique IDs. ID 3030f973b8d4.] already exists - ignoring light.plate04_light_3
2024-03-06 01:17:39.527 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up openhasp platform for binary_sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 344, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/openhasp/binary_sensor.py", line 42, in async_setup_entry
for gpio in entry.data[CONF_INPUT][device_class]
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
TypeError: string indices must be integers, not 'str'
2024-03-06 01:17:39.670 ERROR (MainThread) [homeassistant.util.logging] Exception in lwt_message_received when handling msg on 'hasp/plate04/LWT': 'online'
Traceback (most recent call last):
File "/config/custom_components/openhasp/init.py", line 475, in lwt_message_received
await self.refresh()
File "/config/custom_components/openhasp/init.py", line 630, in refresh
await self.async_change_page(self._page)
File "/config/custom_components/openhasp/init.py", line 564, in async_change_page
if page <= 0 or page > num_pages:
^^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'int' and 'str'

Thanks for you report. We've updated the discovery and published a new pre-release of 0.7.2. That should fix the problem.

Can this issue be closed now?


如何加载本地已下载的权重？how to load locally downloaded weights？

如何加载本地已下载的权重，由于防火墙无法访问huggingface，我通过VPN下载了权重，如何在代码中进行加载？
Due to the firewall, I cannot access Hugging Face directly. I used a VPN to download the weights. How can I load them in the code?

Create a directory weights and put the weight into it.

By the way, you can set --captioner none to avoid downloading LLaVA or RAM from hugging face.

Wow! This is great!


Update networks.json

@aicgi almost same issues as here:
https://github.com/noxonsu/unifactory/pull/186
And again I don't see the reason to add just a testnet.


chore: release 0.3.1

:robot: I have created a release *beep* *boop*
0.3.1 (2021-11-19)
Bug Fixes

client: unknown command "version" for "trdl" (702a7f0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/trdl/releases/tag/v0.3.1 :sunflower:


PatternStates not working as expected

If i add a pattern state by e.g. add @progress to one pattern, every other pattern that includes a pattern or is included by an other pattern get that state.
So adding state "progress" to a pattern, lets say "base-button", all my other patterns that have includes are on progress. Even if they don't include base-button.
In the docs http://patternlab.io/docs/pattern-states.html is can see there is some kind of state inheritance but this can not be the expected behaviour.
Live example:

This pattern have no state suffix in filename, Child-pattern ist complete BUT the pattern ist set to in-review because some other pattern is set to in-review.
I used the node-edition earlier where states are working like a charm.
Any ideas?

Same Problem here!

Same issue too.

@EvanLovely Is this something you've seen in your recent work touching the pattern states feature?

Fixed in https://github.com/pattern-lab/patternlab-php-core/pull/139 and released in core v2.8.4


fix: update code coverage script and prevent similar problems in the future

Summary of changes

Changes introduced in this pull request:

Fix errors in code coverage script.
Run a small version of the code coverage script in PRs when they're out of draft.

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

While I appreciate the quick review, there is more work to do in this PR before it is ready. :)

@LesnyRumcajs Need a re-review before this can be merged.


Adding helm chart to deploy provisioner

Closes: https://github.com/kubernetes-incubator/external-storage/issues/487
This PR adds an alternative method of deploying local volume provisioner by using HELM chart.  Chart.yaml is just a description of the chart, values.yaml contains variables and its values which the user can change, and templates/provisioner.yaml is the template.
by running:
helm template privisioner

from local-volume/provisioner/deployment/kubernetes/helm folder, provisioner's confgmap and daemon set will be generated based on values provided in values.yaml.

/assign @msau42

@sbezverk - can you please add a small README.md? You can probably start with simply the content in the description of this PR.
You could potentially include some examples of generated content or include generated content with _generated in the filename in the PR.

I'm thinking it may also be good to include it as part of the main readme

@msau42 @ianchakeres thanks for your suggestions , I was also thinking about a small section in the doc about this feature. @msau42  Could you point me in the doc where would it make more sense to add.  Also I need to cover helm installation, well it is very simple but still people needs to know how to get it.

You can replace the bootstrapper section here:
https://github.com/kubernetes-incubator/external-storage/tree/master/local-volume#option-1-bootstrapping-the-external-static-provisioner

/lgtm
Thanks so much for doing this!


Envoy Rate Limit: Enable stage setting matching.

Update documentation to reflect new behaviour.
getApplicableRateLimit() returns all rate limits for default stage settings, a set of rate limits for a specific stage setting or an empty vector if there are no rate limits or a stage setting that doesn't exist.

@lyft/network-team


Add a better timedelta?

Should there be a 'better' class to wrap timedelta?
pro:

allows for a better named class, like Duration
allows for friendlier API
allows implementing 'fuzzy' durations like year or month

con:

timedelta is fine. It doesn't have pitfalls like datetime. Wrapping in another class adds complexity

One idea I've been thinking of, is having two classes:

Duration for exact durations. Can be measured absolutely in seconds, hours, etc. Cannot handle months, years because the duration of these depends on the context (i.e. months and years have different number of days). Perhaps even days can be disallowed, since it can be confusing whether you mean "exactly 24 hours" or "the same time the next day" (which can often be 23 or 25 hours later due to DST)

d = Duration(hours=34, seconds=1)

# addition/subtraction should work as expected
UTCDateTime.now() + d

# directly convert to common units
d.as_hours()
d.as_minutes()

# arithmetic between other Durations
d + Duration(hours=2)

# but NOT supported
Duration(months=3)  # NOT supported

FuzzyDuration for durations that involve more 'human' durations that don't have an exact interpretation in hours/seconds.

f = FuzzyDuration(year=1)

# addition/subtraction should work as expected
UTCDateTime.now() + f

f.as_hours()  # NOT supported

# can addition be supported in all cases...I wonder...
f + FuzzyDuration(months=3)

Speaking of timedelta, it would be nice to be able to use seconds() and microseconds() in addition to days(), hours(), and minutes().
(And if you think it doesn't fit in here, I'll be happy to open a separate issue and reference this one.)

@kseistrup agree, I always thought it weird that timedelta exposed the underlying fields (days, seconds, milliseconds). I consider that almost 'implementation details'. I'd much rather have an opaque duration with in_seconds(), in_microseconds(), in_days(), etc.

Here is a survey of how other languages and standards call the concepts of "fuzzy" and "exact" durations:

"fuzzy" duration
"exact" duration

Python

timedelta

C# (NodaTime)
Period
Duration

Rust (chrono)

Duration

JS (Temporal)
Duration

Haskell

Duration

Java
Period
Duration

ISO8601
Period

I Could be wrong but... I would like simplification over a ton of classes...
I mean, we all know a month has a relative duration. It depends on the context.
But the truth is that Duration(months=1) will never mean or result into nothing if not used with a datetime.
I mean this is not fuzzy: datetime(2023,1,1) + Duration(month=1) even when Duration(month=1) is in fact fuzzy.
In other means, Duration(month=1) has no "result" until it's arithmetically used with a date/datetime.
But either way maybe some assumptions are needed.

Thanks for the feedback 👍 , you're not the only one remarking about 'too many classes'.
A proposal to "class overload" here: a .add and .subtract method, so you don't even need to interact with duration classes if you don't want to. This is basically what pendulum and arrow do. What do you think?
my_event.add(month=1)

I prefer using operators (+ , -) but either way it's ok.
A good time delta implementation is what's keeping me from dropping python-dateutil.

I prefer using operators (+ , -) but either way it's ok.

Here's a thought: we could expose the units as months(), days(), hours(), etc.
Arithmetic would then automatically create the right classes:
my_event + months(3)  # always works
fuzzy_duration = years(1) - weeks(7) + hours(4)
exact_duration = hours(2.5) + seconds(30)

fuzzy_duration.in_seconds()  # not allowed. Only known relative to a DateTime
exact_duration.in_seconds()  # allowed

Giving it a second thought:

Using months, days, etc.... adds complication as well. Maybe going back to duration: Duration(months=1) is easier (to the user!).
Like:

fuzzy_duration = Duration(years=1) - Duration(weeks=7) + Duration(hours=4)
exact_duration = Duration(hours=2.5) + Duration(seconds=30)

It should not be possible to specify Duration(month=1, day=1) because can lead to ambiguos results. The operation is not commutative as adding a month and then adding a day can have a different value than adding a day and then a month. Unless some operator precedence is set which I think complicates all a lot..
One way or another should be Duration(month=1) or Month(1) not duration(month=1) or month(1)

Using months, days, etc.... adds complication as well. Maybe going back to duration: Duration(months=1) is easier (to the user!). As you will end up again with a lot of different clases.

You can have the benefits of both (fewer classes + less verbosity) if you do:
def months(i):
    return Duration(months=i)

def days(i):
    return Duration(days=i)

One way or another should be Duration(month=1) or Month(1) not duration(month=1) or month(1)

Yeah, I didn't make clear that month is a function; that's why I had them lowercased. Indeed classes should be properly cased 😄

[...] The operation is not commutative as adding a month and then adding a day can have a different value than adding a day and then a month.

It's mathematical properties like this that I'd ideally like to express in different types. I took a first stab at it, you can see the docs for this dev version here. What do you think?

Unless some operator precedence is set which I think complicates all a lot..

Note this isn't such a crazy idea. Established libraries in other languages and RFC 5545 perform these operations from biggest (year) to smallest (day and ) unit.

Ok ok! Sorry I thought month() was a class constructor returning a month instance.
I will read the docs dev version and look into RFC 5545 🤯 didn’t know that this exists.

RFC 5545 🤯 didn’t know that this exists.

It's quite a read. Have a look at NodaTime or JS temporal for ideas on what a duration API can look like


Create Runbook

As an SRE, I should be able to refer to a runbook for general system and service overview, operational procedure reference, FAQs, points of contact, support and other critical account info, diagrams, and other information necessary to easily and effectively support the product.
Acceptance Criteria

[ ] A document created and available offline

Going to be tying some new documentation process for this, hopefully we can cover this story with documentation outputs from other stories currently in progress. Another good example is 18F/cg-site#457.


Using POS tagger on existing tokens

I've got a large amount of text that's already been tokenised into lists of strings by an external process.
Is there any way to pass that through Spacy's part of speech tagger? I can see that it can be called on a Doc object, but I can't see any way of creating that other than from using an English object's call method on a string.

Hey,
The docs should be clearer on this. You want:

tokens = nlp.tokenizer.tokens_from_list(token_strings)
nlp.tagger(tokens)

If you want to apply preset tags, use:

nlp.tagger.tag_from_strings(tokens, tag_strs)

The doc.from_array method is also useful for loading annotations.

Thanks for that, knowing I can create tokens from a list of strings should help with a few things.
Is there anything else I need to do in order to initialise the tagger by the way? I'm currently getting None when using your code above, e.g.:
import spacy.en
NLP = spacy.en.English()

sent = 'This is a sentence .'
words = sent.split()
tokens = NLP.tokenizer.tokens_from_list(words)
print('Tokens:', tokens)
tags = NLP.tagger(tokens)
print('Tags:', tags)

outputs:
Tokens: This is a sentence .
Tags: None

The tagger, parser and NER all modify the tokens object in place. The design is optimized to use the annotations via the Doc, Token and Span objects, so that it's easy to hop between the different representations. This also allows us to store everything efficiently, and handle string<->integer encodings.
To get a list of strings do:
[token.tag_ for token in doc]
This produces the PTB-style tags like VBZ, VBD, etc. You can instead get the Google universal tags, at token.pos_. The integer encoded versions are at token.tag and token.pos, without the trailing underscore.

Ah, thanks again, that works perfectly.


Publication link not given on the SCoRe Lab Website

This is an issue with the actual scorelab website, not the Webiu project codebase
On the scorelab website https://scorelab.org/ under the publication section on the home page, we have a publication titled 'Smart mobile payment system' which does not take to the actual publication published instead it redirects to the publications page https://scorelab.org/publications/ as shown -

I believe this is an issue with the link-prop passed to that particular publication item and updating the link prop to the correct one will resolve this issue

I would request mentors @charithccmc and @wdevon99 to please look into this :)

I can fix this. Can you provide the correct link which is to be replaced?

I can fix this. Can you provide the correct link which is to be replaced?

It's not an issue with the current project, it's an issue in production props which we don't have access to

I would request mentors @charithccmc and @wdevon99 to please look into this :)

I can fix this. Can you provide the correct link which is to be replaced?

It's not an issue with the current project, it's an issue in production props which we don't have access to

Okay, Thank you!!


drivers: spi_nrfx: Fix NRFX_ASSERT crash when sck pin is set to no-connect

Fixes a bug in nrf spi driver when CONFIG_WS2812_STRIP_SPI is used to drive a WS2812 strip NRFX_ASSERT() is triggered.
SPI is used for accurate timings and is widely supported for driving these types of LED's. To save on pin count there is only the need for MOSI to be physically connected to the output buffer.

twister-build-prep / prep_pr pipeline failed with
Error: The process '/usr/bin/git' failed with exit code 128
Error: Error: failed to run script step: command terminated with non-zero exit code: Error executing in Docker Container: 1
Error: Process completed with exit code 1.
Error: Executing the custom container implementation failed. Please contact your self hosted runner administrator.

I don't believe this is related to my PR. Might need to re-run later if the CI server is down

I retriggered it


inference

hello, how to test the trained model??

I used
$ ipython3 nbconvert --to script similar_image_retrieval.ipynb
to convert similar_image_retrieval.ipynb to a .py script, it's working fine


Use fewer<EMAIL_ADDRESS>traits in examples, build HAL without default features in CI

This branch turned into a bit of a grab bag of changes, and nothing too exciting here, but the gist is:

Build esp-hal package in CI without the default features enabled

Big asterisk here, the rt and vectored features are currently still required, see #1371

Cleaned up some warnings which appeared without either embedded-hal or embedded-hal-02 traits
Small miscellaneous changes/cleanup

Ahh it's because the CI jobs changed, and we need to explicitly configure the CI job names in the repo settings. Really annoying, I don't feel like dealing with it right now so will fix it tomorrow.


Replace Bootstrap's text-center

https://trello.com/c/FTWCbdsp/91-replace-bootstraps-text-center-class-with-a-custom-class
Updated main.scss file to replace Bootstrap's text-center.

1. Can we remove the `important!` property? I know Bootstrap uses it, but I'd rather avoid it.

2. Let's remove the `.text-center` rule altogether from `bootstrap.css` to prevent any confusion.

I will get started on those changes. I didn't even think about removing .text-center from bootstrap.


not building bzip2 on linux

bzip2 sublibrary (in src/bzip2 folder) isn't compiling on Linux when running make. I'm use StormLib as a static library in my project and that gives me a compiling error when I'm trying to build my project with static libstorm.a
/usr/local/lib/libstorm.a(SCompression.cpp.o): In function Compress_BZIP2(void*, int*, void*, int, int*, int)': SCompression.cpp:(.text+0x7cb): undefined reference to BZ2_bzCompressInit'
SCompression.cpp:(.text+0x814): undefined reference to BZ2_bzCompress' SCompression.cpp:(.text+0x831): undefined reference to BZ2_bzCompressEnd'
/usr/local/lib/libstorm.a(SCompression.cpp.o): In function Decompress_BZIP2(void*, int*, void*, int)': SCompression.cpp:(.text+0x888): undefined reference to BZ2_bzDecompressInit'
SCompression.cpp:(.text+0x8be): undefined reference to BZ2_bzDecompress' SCompression.cpp:(.text+0x8db): undefined reference to BZ2_bzDecompressEnd'
I made a workaround by adding ${ZLIB_BZIP2_FILES} in CMakeLists.txt, line 286.

Yo're supposed to use system bzip on linux.
Add -lbzip2 (or whatever the actua flag is, can't remember) to the gcc
command line
On Mon, Mar 16, 2015 at 7:26 PM, Mistranger<EMAIL_ADDRESS>wrote:

bzip2 sublibrary (in src/bzip2 folder) isn't compiling on Linux when
running make. I'm use StormLib as a static library in my project and that
gives me a compiling error when I'm trying to build my project with static
libstorm.a
/usr/local/lib/libstorm.a(SCompression.cpp.o): In function Compress_BZIP2(void*,
int*, void*, int, int*, int)':
SCompression.cpp:(.text+0x7cb): undefined reference toBZ2_bzCompressInit'
SCompression.cpp:(.text+0x814): undefined reference to BZ2_bzCompress'
SCompression.cpp:(.text+0x831): undefined reference toBZ2_bzCompressEnd'
/usr/local/lib/libstorm.a(SCompression.cpp.o): In function Decompress_BZIP2(void*,
int*, void*, int)':
SCompression.cpp:(.text+0x888): undefined reference to
BZ2_bzDecompressInit'
SCompression.cpp:(.text+0x8be): undefined reference to BZ2_bzDecompress'
SCompression.cpp:(.text+0x8db): undefined reference toBZ2_bzDecompressEnd'
I made a workaround by adding ${ZLIB_BZIP2_FILES} in CMakeLists.txt, line
286.
—
Reply to this email directly or view it on GitHub
https://github.com/ladislav-zezula/StormLib/issues/38.

yes, I've built my broject with bzip and everything is ok now


Rename Antennas-Version_1.1.ckan to Antennas-1.1.ckan

I think this will fix the Max KSP version in CKAN, but I'm not entirely sure. That hardcoded version number might throw it out.

As https://github.com/KSP-CKAN/CKAN-meta/pull/860 changing filenames will have no effect.

Passes locally. Merging with my thanks.


Home page is empty

There is no content being displayed on the dashboard other than "Dashboard Page Title" which is kinda useless...

Agreed! I personally go to "Jobs" most of the time, not sure if that view should be the default. Also "Projects" could be a good initial view.
Where do others usually go?

There is little value for individuals or teams to know about every job ( and then some since filters aren't working properly ) packit is performing but as a landing page some statistic information and or overall job page might be useful.
What's the initial scope of the dashboard part of the project?
( is it thought as just somekind of information radiator or configuration platform of some sort? Or only meant for the packit team?  )
What value does it bring to me as a packit consumer to be using it?

@johannbg You are right. It does not look nice. We want to add some statistics/status/charts/... there. Sadly, the dashboard wasn't a high priority in the last months.

What's the initial scope of the dashboard part of the project?

Originally, it was created as a companion to our result pages. I would say a nice view of our database.
It was done as a GSOC project (task description).

What value does it bring to me as a packit consumer to be using it?

You can see what was managed for your (or someone else's) project from one place. Yes, not so interesting for our users.
But nowadays, we (ok, mainly @IceWreck..;) are working on replacing the old result pages and having them incorporated into the dashboard (#73). And that will bring a real benefit to our users.
So the short-term plan (#71):

Have a result page for build/test that can be linked from PR status. (Includes links to copr/koji, logs, installation instructions...)
The pages are linked together (build/srpm/test-run/PR/project) for better browsing.

And long-term:

Basic statistics.
Deployment status and reporting of the problems on our side.
Ideally, incorporate GitHub accounts and project management (e.g. to retrigger the job).

@lachmanfrantisek very good explanation - I'd say that right now the dashboard is really just a dashboard - overview what packit is doing with not many valuable info for users of packit - #73 will change it massively
Once we enable authentication via github and gitlab, the dashboard will start offering tailored info about projects you are working on, though we are definitely a few months away from that. In the meantime, github and gitlab are primary interfaces for packit.

Will packit be limited to the Fedora/RHEL ecosystem or are there any "future" plans to allow it to be integrated with other distributions like (Open)Suse, Debian etc.

We don't have any plans to support other distributions right now - the main reason being that we don't know how those distributions work and no one requested such a thing from us so far.

Not doing so you end up narrowing the packit end users base strictly to RH's own maintainers who are upstream and maintaining their component downstream, which begs the question why packit is not just RH internal tool,

To make some progress on the original issue, let's specify an outcome of this task:

[ ] Provide a suggestion(s) about the possible look of the home page. (static text, links to docs, charts, statistics, last jobs, ...)
[ ] Discuss the plan here and/or with the team.
[ ] Implement the plan.

Closed by #111, introduced links to documentation, GitHub namespace and contributing repository.


Conditional classes like for a navigation bar

I am trying to create an active state for the navigation bar based on the sveltekit docs but it doesn't work with tailwind. Do you have any suggestions?

Check out an example __layout.svelte like this to start from:

	Page a
	Page b

<slot></slot>

I've tested it and it works in both dev and prod without the styles being wrongly removed.


Add Binance Wallet as a new Provider

I've seen a few projects that have "Binance Wallet" as a connector, besides MetaMask and the others.
Might be interesting to add it

Done

Done


Add channel diffing

Some of the NWP channels are accumulations. For example, in the ECMWF data the channels ['dswrf', 'dlwrf', 'sr', 'duvrs'] are all accumulated. This leads to issues in production if the NWP data is more delayed than the model has seen in production since the values get higher and higher throughout the forecast steps.
Therefore we need to apply a diff for this accumulation data.
This merge includes

Add diffing as an option when slicing the NWP data
Add as option in NWP configuration
Use within pvnet pipeline

We needed to switch round the order of spatial and time slicing for this to avoid loading data through dask too early

Add tests

This pull request adds the diff to the time slicing function. This is a slightly complex way of doing things but the simpler way of diffing the data when initially loaded performed very poorly.
e.g. In this simple case the diffed data talkes 5.5 times longer than the non-diffed data. I don't know why the slowdown should be so much. More chunks in the step-wise dimension need to be loaded for each slice but nothing close to 5.5 times more. I wonder if this could be due to more dask overhead and a more complex graph
import xarray as xr
import ocf_blosc2
import numpy as np
import pandas as pd
from datetime import timedelta

ds_ecmwf = xr.open_zarr("/mnt/disks/nwp_rechunk/nwp/ecmwf/UK_v2.zarr")
accum_channels = ['dswrf', 'dlwrf', 'sr', 'duvrs']

# Diff some of the channels and recombine
xr_accum = ds_ecmwf.sel(variable=accum_channels).diff(dim="step", label="lower")
xr_non_accum = (
    ds_ecmwf.sel(variable=[v for v in ds_ecmwf.variable.values if v not in accum_channels])
    .isel(step=slice(0, -1))
)
ds_diffed = xr.concat([xr_accum, xr_non_accum], dim="variable")

def random_sel(ds):
    """Function for testing speed of diffed and non-diffed data"""
    lat0 = np.random.randint(0, len(ds.latitude)-24)
    lon0 = np.random.randint(0, len(ds.longitude)-24)
    step0 = np.random.randint(0, len(ds.step)-16)
    init_time = np.random.randint(0, len(ds.init_time))
    return ds.isel(
        latitude=slice(lat0, 24+lat0),
        longitude=slice(lon0, 24+lon0),
        step=slice(step0, 8+step0),
        init_time=init_time
    ).compute()

%timeit -n 3 -r 3 random_sel(ds_ecmwf)
>> 1.48 s ± 420 ms per loop (mean ± std. dev. of 3 runs, 3 loops each)

%timeit -n 3 -r 3 random_sel(ds_diffed)
>> 8.16 s ± 1.45 s per loop (mean ± std. dev. of 3 runs, 3 loops each)

In the version submitted in this pull request, using the channel diffing (which is optional) causes a slowdown of less than 2x.

#286 does this solve this @dfulu?

#286 does this solve this @dfulu?

Yeh, this closes #286 except for the normalisation part. I'll keep this open for now until I can add that


Fixed branch alias

The purpose of branch aliases is to indicate to Packagist what version the branch is. That is, what release series to expect the next tag on the master branch to be. This allows people to test with @dev stability, and get the correct version of Bugsnag.

Can you explain the use-case that needs this change?
We only ever push to master for a new release which gets immediately tagged, so I'm not sure if this is useful; the latest version of master is always the same as the latest tagged release

The purpose of this is so that composer knows what version the code on that branch will be. If someone asks composer to get the latest versions, not just the latest stable versions, then composer will think the code on this branch represents wip for the next 3.20.x release, which is wrong.
This feature is particularly useful when someone wants to test a minor release series before a first .0 tag has been made, or just wants to get bug fixes before they are tagged.

The purpose of this is so that composer knows what version the code on that branch will be. If someone asks composer to get the latest versions, not just the latest stable versions, then composer will think the code on this branch represents wip for the next 3.20.x release, which is wrong.
This feature is particularly useful when someone wants to test a minor release series before a first .0 tag has been made, or just wants to get bug fixes before they are tagged.


add UT for csi

Codecov Report

Merging #180 (77ef8dc) into main (fbb18e9) will increase coverage by 5.14%.
The diff coverage is 50.00%.

:exclamation: Current head 77ef8dc differs from pull request most recent head 39d634a. Consider uploading reports for the commit 39d634a to get more accurate results

@@            Coverage Diff             @@
##             main     #180      +/-   ##
==========================================
+ Coverage   23.28%   28.42%   +5.14%
==========================================
  Files          38       38
  Lines        6007     5941      -66
==========================================
+ Hits         1399     1689     +290
+ Misses       4438     4039     -399
- Partials      170      213      +43

Flag
Coverage Δ

unittests
28.42% <50.00%> (+5.14%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/controller/allocate_migrate.go
36.66% <ø> (ø)

pkg/csi/controllerserver.go
61.33% <50.00%> (+45.13%)
:arrow_up:

pkg/controller/controller.go
39.87% <0.00%> (-6.55%)
:arrow_down:

pkg/csi/type.go
86.84% <0.00%> (+7.89%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


inconsistent type issue of opx_driver.OPX.qua_program

the member qua_program returns an QUA program but it is used in get_prog() as if it were an actual QUA program instance
The recommended usage pattern is also to replace the method in the instance with a field containing the qua program instance and not with a callable method.
This causes type checking issues showing up in Pylance (VS Code) which complains about overwriting () -> QuaProgram with just QuaProgram, and the result of respecting the type ~hints~ information or as matter of fact leaving the method as-is would cause errors.
My recommendation would be to change this so that qua_program would always be a field created in the constructor and assigned to maybe _default_qua_program which is a @staticmethod.
Original code for context (with added type hints and comment at type error):
    # Empty method that can be replaced by your pulse sequence in the main script
    # This can also be modified so that you can put the sequences here directly...
    def qua_program(self) -> Program:
        """
        Custom QUA program

        :return: QUA program
        """
        with program() as prog:
            pass
        return prog

    # @abstractmethod
    def get_prog(self) -> Program:
        """Get the QUA program from the user"""
        prog = self.qua_program # <--- incorrect type
        return prog

@sherbrooke-equal1 - I guess you're speaking on the opx_driver, right? I do not see any type hinting there in the main branch, are you on a side branch?
@TheoLaudatQM - Do you know?
In any case, get_prog(self) should return a QuaProgram

with added type hints and comment at type error):

i have added the type hints myself to illustrate the problem

Ok, I looked at it again, I was wrong and it does return a Program and not a QuaProgram.
I can't really see the issue... even when I add type hinting, but I'm using PyCharm.
Do you have a link to any VSCode issue about it? or a place that points to the recommended use pattern?
In any case, @TheoLaudatQM - is there any specific reason we went to this implementation of having an abstract method get_prog which points to another method called qua_program? I think that replacing qua_program by a field makes sense.

@sherbrooke-equal1 - Can you please see if PR-190 fixes it?


Health Check limit errors on verifyNoMissingOppPayments

Apex script unhandled exception by user/organization: 0051A00000A83D4/00D80000000dXy4
Visualforce Page: /apex/npsp__STG_SettingsManager
caused by: System.LimitException: npsp:Too many query rows: 50001
Class.npsp.STG_PanelHealthCheck_CTRL.verifyNoMissingOppPayments: line 655, column 1
Class.npsp.STG_PanelHealthCheck_CTRL.runAllDetections: line 184, column 1
Class.npsp.STG_PanelHealthCheck_CTRL.runDetector: line 101, column 1
we need to fix its soql to limit appropriately.

**lurch: add

Tracking W-010291

duplicate of #2022


Policy for access logs

Is your request related to a problem? Please describe.

Describe the solution you'd like.

Describe alternatives you've considered.

Additional context

This issue has been resolved in version 3.10.0 :tada:


Consider variable default values with @skip/@include/@defer

Related to #4784
In the response adapters, we generate lines like this:
if (not(variable("skipIf")).evaluate(customScalarAdapters.adapterContext.variables(), __typename, customScalarAdapters.adapterContext, null)) {
  // Read fields for the fragment
}

but customScalarAdapters.adapterContext.variables() was empty, since it only considered variables that are not optional, or optional and present.
with this approach we include the optionals that are absent and have a default value (booleans only)

Just pushed:

use variable adapters instead of introducing a new variables() method (and use a flag that piggybacks on CustomScalarAdapters.AdapterContext)
revert what was done in #4700 for the case of the normalizer - the new approach works for it too

⚠ Just a reminder that tweaks will be needed to avoid breaking changes when backporting to 3.x


Make getMentorById endpoint a public endpoint

Is your feature request related to a problem? Please describe.
User's who haven't logged in should be able to see the mentor details
Describe the solution you'd like
Update the SecurityConfig file to make the api/mentors/{id} endpoint public
Describe alternatives you've considered
N/A
Additional context
N/A

@Piumal1999 I would like to work on this issue.

Nice! Assigned @pasindur99


Response Templating: Case-Insensitive Headers

This changes adaptedHeaders in RequestTemplateModel.from(..) to TreeMap with CASE_INSENSITIVE_ORDER to ignore case for headers in response templating.
E.g. allows that {{request.headers.X-CorrelationID}} also matches x-correlationid.
Resolves issue https://github.com/tomakehurst/wiremock/issues/1313

Great stuff, thanks!


Make clipped-relu inplace and fix docs for elu

I just noticed that in #2285 I didn't implement the clipped_relu layer as an in place layer, so this PR fixes that.
Also, the documentation for clipped_relu and elu was lying about their in place behavior, so I fixed that, as well.
Sorry for missing it in the first PR... :(

Ha, right.  I didn't notice either :)


[Snyk] Upgrade pixi.js from 6.4.2 to 6.5.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade pixi.js from 6.4.2 to 6.5.1.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 6 versions ahead of your current version.
The recommended version was released a month ago, on 2022-07-24.

Release notes

Package name: pixi.js

6.5.1 - 2022-07-24🔥  Hotfix
Previous release accidentally bundled the core into packages it wasn't suppose to including in ticker, canvas-mesh, canvas-sprite. It is strongly recommended that you update to 6.5.1 if you upgraded (or tried to) 6.5.0.
💾  Download
Development Build:

https://pixijs.download/v6.5.1/pixi.js
https://pixijs.download/v6.5.1/pixi.js.map
https://pixijs.download/v6.5.1/pixi.mjs
https://pixijs.download/v6.5.1/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.1/pixi.min.js
https://pixijs.download/v6.5.1/pixi.min.js.map
https://pixijs.download/v6.5.1/pixi.min.mjs
https://pixijs.download/v6.5.1/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.1/docs/index.html

Changed
v6.5.0...v6.5.1
🐛 Fixed

Hotfix: Make sure core isn't bundled in ticker, canvas-sprite, canvas-mesh (#8527) @ bigtimebuddy

6.5.0 - 2022-07-22 Read more

6.5.0-rc.4 - 2022-07-20🔥 Sorting blocking bug related to @ pixi/assets
💾  Download
Development Build:

https://pixijs.download/v6.5.0-rc.4/pixi.js
https://pixijs.download/v6.5.0-rc.4/pixi.js.map
https://pixijs.download/v6.5.0-rc.4/pixi.mjs
https://pixijs.download/v6.5.0-rc.4/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.0-rc.4/pixi.min.js
https://pixijs.download/v6.5.0-rc.4/pixi.min.js.map
https://pixijs.download/v6.5.0-rc.4/pixi.min.mjs
https://pixijs.download/v6.5.0-rc.4/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.0-rc.4/docs/index.html

Changed
v6.4.2...v6.5.0-rc.4

6.5.0-rc.3 - 2022-07-20🔥 Sorting more blocking bugs related to @ pixi/node
💾  Download
Development Build:

https://pixijs.download/v6.5.0-rc.3/pixi.js
https://pixijs.download/v6.5.0-rc.3/pixi.js.map
https://pixijs.download/v6.5.0-rc.3/pixi.mjs
https://pixijs.download/v6.5.0-rc.3/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.0-rc.3/pixi.min.js
https://pixijs.download/v6.5.0-rc.3/pixi.min.js.map
https://pixijs.download/v6.5.0-rc.3/pixi.min.mjs
https://pixijs.download/v6.5.0-rc.3/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.0-rc.3/docs/index.html

Changed
v6.4.2...v6.5.0-rc.3

6.5.0-rc.2 - 2022-07-15🔥 Hotfix for @ pixi/node
💾  Download
Development Build:

https://pixijs.download/v6.5.0-rc.2/pixi.js
https://pixijs.download/v6.5.0-rc.2/pixi.js.map
https://pixijs.download/v6.5.0-rc.2/pixi.mjs
https://pixijs.download/v6.5.0-rc.2/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.0-rc.2/pixi.min.js
https://pixijs.download/v6.5.0-rc.2/pixi.min.js.map
https://pixijs.download/v6.5.0-rc.2/pixi.min.mjs
https://pixijs.download/v6.5.0-rc.2/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.0-rc.2/docs/index.html

Changed
v6.4.2...v6.5.0-rc.2

6.5.0-rc - 2022-07-14This is a do-no-harm prerelease and to test new packages @ pixi/assets and @ pixi/node.
💾  Download
Development Build:

https://pixijs.download/v6.5.0-rc/pixi.js
https://pixijs.download/v6.5.0-rc/pixi.js.map
https://pixijs.download/v6.5.0-rc/pixi.mjs
https://pixijs.download/v6.5.0-rc/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.0-rc/pixi.min.js
https://pixijs.download/v6.5.0-rc/pixi.min.js.map
https://pixijs.download/v6.5.0-rc/pixi.min.mjs
https://pixijs.download/v6.5.0-rc/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.0-rc/docs/index.html

Changed
v6.4.2...v6.5.0-rc

6.4.2 - 2022-06-02💾  Download
Development Build:

https://pixijs.download/v6.4.2/pixi.js
https://pixijs.download/v6.4.2/pixi.js.map
https://pixijs.download/v6.4.2/pixi.mjs
https://pixijs.download/v6.4.2/pixi.mjs.map

Production Build:

https://pixijs.download/v6.4.2/pixi.min.js
https://pixijs.download/v6.4.2/pixi.min.js.map
https://pixijs.download/v6.4.2/pixi.min.mjs
https://pixijs.download/v6.4.2/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.4.2/docs/index.html

Changed
v6.4.0...v6.4.2
🔥 Hotfix

Fix: Resolves issue where "exports" broke Webpack (#8381) @ zwade

🐛  Fixed

Clarify that the object's mask must be in the subtree of its parent in the docs (#8378) @ lazarljubenovic

    from pixi.js GitHub release notes

Commit messages

Package name: pixi.js

a344b58 v6.5.1
27365ba Hotfix: Make sure core isn't bundled in ticker, canvas-sprite, canvas-mesh (#8527)
63b9f0c v6.5.0
bff5c47 Move VERSION to core instead of bundle (#8520)
1db04bb Fix LoaderResource tests (#8518)
6fc416e Fix app and ismobilejs typings (#8517)
611ca6a v6.5.0-rc.4
c2bcc64 Fix error with assets import path
0027841 v6.5.0-rc.3
380906d FIx extensions for esm modules to .mjs (#8505)
326fa79 Adds exports to package.json in Assets (#8504)
675b7aa Fix Jest not exiting properly when killing the http server (#8513)
b5dd432 Fix bundle ismobilejs (#8506)
559e3df v6.5.0-rc.2
011feab Fixes Node not starting (#8497)
ffa04c3 Fixes ReferenceError: Can't find variable: ImageBitmap (#8499)
d81beda Fix the hello world example for Node bundle (#8495)
b928798 Fix Rollup warning, ignore used node dependencies (#8493)
16005f8 v6.5.0-rc
c0877e0 Chore: Add script to clean types (#8492)
4776c29 Add detection parsers to Assets (#8482)
9c6c295 Chore: Drop add/remove from resolvers/parsers/caches (#8488)
063870f remove add/remove parsers
84096a7 Chore: Eliminate redundant handling code for extensions (#8485)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Closing. No security patches and no new features needed at the moment.


Improvements (configuration and validation)

Description:

Set default in validation
Ordering
Allow the users to set  name for the sensors (analog the other platforms)

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#3121
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: yr
    name: Weather
    monitored_conditions:
      - temperature
      - symbol

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

That's cool. :tada:
Should be probably properly stated in the release notes (and not only "improvments (configuration and validation") so people can get rid of their customize entries for just naming sensors.


Following build instructions: issue with "homepage" handling in build-front.sh ?

Problem description
Hi there,
While trying to build and run the app on my computer, with docker, I encountered the following issue after starting the containers:
when opening the app in my browser, it tries to reach for static files with an additional /static prefix, for example http://localhost/static/font-inter/inter.css instead of just http://localhost/font-inter/inter.css.
Consequently, the browser complains that the MIME type is wrong, and does not display the app.
Analysis
The issue might come from the script build-front.sh which indeed adds a "/static" prefix to the homepage defined inpackage.json.
Is there a good reason for that processing ?
sed -i 's|"homepage".*|"homepage": "/static",|g' package.json

Environment
Ubuntu 20.04

Digging a little the history for another reason, it seems that build-front.sh has been added in commit 23fb96e3 in particular to make the standalone (pyinstaller) version work.
The modifications done in the script are necessary for the fastapi app to serve correctly the static files, but it breaks other kinds of deployment.
The following logic in python app startup are relying on this:
https://github.com/AntaresSimulatorTeam/AntaREST/blob/d6eae5342fd1f731bbc60392428a9e0529e1de32/antarest/main.py#L138-L143

I had the same issue on my development environment.


Don't format Floats as Strings

Previously if the only change in a class was a parameter's data type
from a Float to a String, then the class resource would be marked as
different, but str_diff would return nil causing a Error: undefined method split' for nil:NilClass error here
Fixes #32

Dear stale bot. This is actually a fairly trivial PR that fixes an actual issue. Labeling it wontfix is not helpful IMO.

This looks legit to me. +1

This is a legit fix.

I am waiting for feedback in https://github.com/camptocamp/puppet-catalog-diff/issues/60

@bastelfreak Would you like to merge this one now?

@alexjfisher Migration Done.

@alexjfisher Migration Done.

Yep.  Just noticed.  Didn't want to merge my own PR though.


Upstream Depends updates

PR intention
This updates depends to work with bionic suite distro's ,Should allow gitian descriptors to be updated to use bionic suite and fix compile issues on fontconfig package on bionic suites
Code changes brief
Change references and usages of python to python3
Use https instead of http on package download links
Misc patches for compile issues
Closes #790

Thanks we'll review @akshaynexus !

Thanks for the update. I'll reuse it when updating to the bionic target (in progress).


MAINT: _lib: update Boost Math

Reference issue
gh-18906
What does this implement/fix?
This updates Boost Math to fix the beta part of gh-18906.
Additional information
Locally, I'm still getting the OverflowError, but the comment (removed in this PR) suggests that it should return a value after Boost Math is updated. @WarrenWeckesser do you know why we're still seeing the OverflowError after updating Boost Math here?

Would it make sense to update boost-math separately, and keep this PR only for the stats overflow issue? An up-to-date submodule helps having to guess whether something is fixed already upstream (which is how I arrived at this PR).

I'm fine with that. My reason for updating Boost has usually been that something specific has been fixed upstream, so I tend to test the fix in the update PR. That was the case here, but the issue didn't seem to be fixed.

@mdhaber, could you let us know the fate of this effort? Postponed? Abandoned?

The issue I wanted to fix with this was not fixed by it at the time. I haven't checked since. Anyone is welcome to checkout a more recent commit of the Boost submodule, though.


Minimal config scalafmt

This aims to make the formatting of Scanamo more consistent by using scalafmt.
At present it still requires a manual formatting step.
The config is fairly minimal at the moment with the idea that subsequent pull requests can make incremental changes which can be seen on their own merits.

I don't love all of these changes, but I don't think any of them are heinous enough to sacrifice consistency for.

Is ScalaFmt worth using by default from now on in projects over Scalariform? I thought Scalariform 'just worked'. What are the benefits of ScalaFmt over Scalariform?


Add Y036: check for badly-defined __(a)exit__ methods

Fixes #188

There is one remaining typeshed hit, which I'm not quite sure what to do with:
https://github.com/python/typeshed/blob/ec27c00ca220c501a55e51617117f5b2d60fc06c/stdlib/imp.pyi#L48
The check I've written argues that it should be rewritten:
def __exit__(self, *args: Any) -> Any: ...  # OLD
def __exit__(self, *args: object) -> Any: ...  # NEW

The only thing is, this method is part of a protocol definition. I'm not sure whether it's important to keep it as it is or not. I think it would probably be fine? But also protocols generally need more permissive definitions for argument types. So, I'm not sure.
If we decide not to change that method in typeshed, we have two options:

# noqa it in typeshed.
Add further complexity to this check by special-casing __(a)exit__ methods inside protocol definitions.

The typeshed hit seems buggy. Isn't it saying that for an object to be compatible with that protocol, it must have an exit method that accepts any number of arguments?

Nope. If this PR is merged, any of the following will be accepted as valid __exit__ signatures:
def __exit__(self, *args: object): ...
def __exit__(self, typ: type[BaseException] | None, *args: object): ...
def __exit__(self, typ: type[BaseException] | None, val: BaseException | None, *args: object): ...
def __exit__(self, typ: type[BaseException] | None, val: BaseException | None, tb: TracebackType | None): ...

What won't be accepted is any of these:
def __exit__(self, *args: Any): ...
def __exit__(self, typ: type[BaseException] | None, *args: Any): ...
def __exit__(self, typ: type[BaseException] | None, val: BaseException | None, *args: Any): ...

I get that and it's fine, but *args in a Protocol seems to be broken and a bad idea.

The typeshed hit seems buggy. Isn't it saying that for an object to be compatible with that protocol, it must have an exit method that accepts any number of arguments?

Hah, good point. So the stub is broken anyway.

I get that and it's fine, but *args in a Protocol seems to be broken and a bad idea.

Yeah sorry, I misread your message :)


Update react.md - usage example for IonActionSheet

The icons in buttons were not working. I've done the following changes:

added: import {  } from 'ionicons/icons'
changed: removed quotes from "icon" properties inside "buttons" array
changed: "arrow-dropright-circle" (does not exist in ionicons v5) to "playCircleOutline" (camelCase instead of dashes)

Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[X] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

The icons in buttons were not working in the usage exxample code for React.
What is the new behavior?

Icons working :)

added: import
changed: strings to variables in buttons.icon
changed: arrow icon from ionicons v4 to play icon from v5

Does this introduce a breaking change?

[ ] Yes
[X] No

Thanks for the PR! Please run npm run build in order to compile the API changes.

Thanks @gkaneto, I'll go ahead and fix the build errors and get this merged.


How can I do to have DrawerLayout and BottomNavigationView on the same screen?

The Material Design guidelines suggest to avoid using nav drawer with other primary navigation components - see this doc for more details.


bumps rails to 5.0.5

I rule and have completed some work on Case Manager that's ready for review!
Point release bump of rails to 5.0.5! 🥇
This pull request makes the following changes:

bundle update rails

Very minor point release that fixes some minor misbehaviors, but also gets us away from the mail gem flag vulnerability we've known about for a bit.
@DarthHater or @lomky can I get a signoff?
No issues.

Codecov Report

Merging #1165 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1165   +/-   ##
======================================
  Coverage    95.3%   95.3%
======================================
  Files          52      52
  Lines        1151    1151
======================================
  Hits         1097    1097
  Misses         54      54

Continue to review full report at Codecov.

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

Logs from odd hang for those with deeper rails-fu:

Server boot
try to load localhost:3000
impatiently stop that and try to load localhost:3000/users/sign_in
impatiently stop and hit reload on localhost:3000/users/sign_in
wait
sign in loads, sign in, redirected to dashboard.

Sat Aug 05 08:57:07 [bump-rails]~/.../dcaf_case_management $ rails s
=> Booting Puma
=> Rails 5.0.5 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
[6808] Puma starting in cluster mode...
[6808] * Version 3.8.2 (ruby 2.4.1-p111), codename: Sassy Salamander
[6808] * Min threads: 5, max threads: 5
[6808] * Environment: development
[6808] * Process workers: 3
[6808] * Preloading application
[6808] * Listening on tcp://<IP_ADDRESS>:3000
[6808] Use Ctrl-C to stop
[6808] - Worker 0 (pid: 6839) booted, phase: 0
[6808] - Worker 1 (pid: 6852) booted, phase: 0
[6808] - Worker 2 (pid: 6865) booted, phase: 0
Started GET "/" for <IP_ADDRESS> at 2017-08-05 08:57:53 -0400
MONGODB | Topology type 'unknown' initializing.
MONGODB | Server localhost:27017 initializing.
MONGODB | Topology type 'unknown' changed to type 'single'.
MONGODB | Server description for localhost:27017 changed from 'unknown' to 'standalone'.
MONGODB | There was a change in the members of the 'single' topology.
MONGODB | localhost:27017 | dcaf_case_management_development.insert | STARTED | {"insert"=>"sessions", "documents"=>[{"_id"=>"497fa856314ab10e12c73eb657ea8902", "_data"=><BSON::Binary:0x69965253444320 type=generic data=0x04087b0749221375...>, "updated_at"=>2017-08-05 12:57:53 UTC, "created_at"=>2017-08-05 12:57:53 UTC}], "ordered..."
MONGODB | localhost:27017 | dcaf_case_management_development.insert | SUCCEEDED | 0.001673376s
Started GET "/users/sign_in" for <IP_ADDRESS> at 2017-08-05 08:57:53 -0400
Processing by Devise::SessionsController#new as HTML
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.00047449799999999996s
  Rendering devise/sessions/new.html.erb within layouts/application
  Rendered devise/shared/_links.html.erb (0.9ms)
  Rendered devise/sessions/new.html.erb within layouts/application (21.1ms)
Started GET "/" for <IP_ADDRESS> at 2017-08-05 08:58:56 -0400
MONGODB | Topology type 'unknown' initializing.
MONGODB | Server localhost:27017 initializing.
MONGODB | Topology type 'unknown' changed to type 'single'.
MONGODB | Server description for localhost:27017 changed from 'unknown' to 'standalone'.
MONGODB | There was a change in the members of the 'single' topology.
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.0012506820000000001s
Started GET "/users/sign_in" for <IP_ADDRESS> at 2017-08-05 08:58:56 -0400
Processing by Devise::SessionsController#new as HTML
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.000652519s
  Rendering devise/sessions/new.html.erb within layouts/application
  Rendered devise/shared/_links.html.erb (0.9ms)
  Rendered devise/sessions/new.html.erb within layouts/application (20.4ms)
Started GET "/users/sign_in" for <IP_ADDRESS> at 2017-08-05 08:59:07 -0400
Processing by Devise::SessionsController#new as HTML
MONGODB | Topology type 'unknown' initializing.
MONGODB | Server localhost:27017 initializing.
MONGODB | Topology type 'unknown' changed to type 'single'.
MONGODB | Server description for localhost:27017 changed from 'unknown' to 'standalone'.
MONGODB | There was a change in the members of the 'single' topology.
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.001599895s
  Rendering devise/sessions/new.html.erb within layouts/application
  Rendered devise/shared/_links.html.erb (0.9ms)
  Rendered devise/sessions/new.html.erb within layouts/application (29.7ms)
  Rendered layouts/_messages.html.erb (0.7ms)
Completed 200 OK in 58462ms (Views: 58458.4ms)

MONGODB | localhost:27017 | dcaf_case_management_development.update | STARTED | {"update"=>"sessions", "updates"=>[{"q"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "u"=>{"$set"=>{"_data"=><BSON::Binary:0x69965301169560 type=generic data=0x04087b0749221375...>, "updated_at"=>2017-08-05 12:59:54 UTC}}, "multi"=>false, "upsert"=>f...
MONGODB | localhost:27017 | dcaf_case_management_development.update | SUCCEEDED | 0.000535512s
  Rendered layouts/_messages.html.erb (0.5ms)
  Rendered layouts/_messages.html.erb (0.5ms)
Completed 200 OK in 121451ms (Views: 121438.2ms)

Completed 200 OK in 47476ms (Views: 47464.1ms)

MONGODB | localhost:27017 | dcaf_case_management_development.update | STARTED | {"update"=>"sessions", "updates"=>[{"q"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "u"=>{"$set"=>{"_data"=><BSON::Binary:0x69965270177640 type=generic data=0x04087b0749221375...>, "updated_at"=>2017-08-05 12:59:55 UTC}}, "multi"=>false, "upsert"=>f...
MONGODB | localhost:27017 | dcaf_case_management_development.update | STARTED | {"update"=>"sessions", "updates"=>[{"q"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "u"=>{"$set"=>{"_data"=><BSON::Binary:0x69965267562020 type=generic data=0x04087b0749221375...>, "updated_at"=>2017-08-05 12:59:55 UTC}}, "multi"=>false, "upsert"=>f...
MONGODB | localhost:27017 | dcaf_case_management_development.update | SUCCEEDED | 0.0006218370000000001s
MONGODB | localhost:27017 | dcaf_case_management_development.update | SUCCEEDED | 0.000677612s
Started GET "/images/favicon.ico" for <IP_ADDRESS> at 2017-08-05 08:59:56 -0400

ActionController::RoutingError (No route matches [GET] "/images/favicon.ico"):

actionpack (5.0.5) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
railties (5.0.5) lib/rails/rack/logger.rb:36:in `call_app'
railties (5.0.5) lib/rails/rack/logger.rb:24:in `block in call'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:69:in `block in tagged'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:26:in `tagged'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:69:in `tagged'
railties (5.0.5) lib/rails/rack/logger.rb:24:in `call'
sprockets-rails (3.2.0) lib/sprockets/rails/quiet_assets.rb:13:in `call'
request_store (1.3.2) lib/request_store/middleware.rb:9:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/request_id.rb:24:in `call'
rack (2.0.3) lib/rack/method_override.rb:22:in `call'
rack (2.0.3) lib/rack/runtime.rb:22:in `call'
activesupport (5.0.5) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/executor.rb:12:in `call'
rack (2.0.3) lib/rack/sendfile.rb:111:in `call'
secure_headers (3.6.4) lib/secure_headers/middleware.rb:12:in `call'
railties (5.0.5) lib/rails/engine.rb:522:in `call'
puma (3.8.2) lib/puma/configuration.rb:224:in `call'
puma (3.8.2) lib/puma/server.rb:600:in `handle_request'
puma (3.8.2) lib/puma/server.rb:435:in `process_client'
puma (3.8.2) lib/puma/server.rb:299:in `block in run'
puma (3.8.2) lib/puma/thread_pool.rb:120:in `block in spawn_thread'
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/routing_error.html.erb within rescues/layout
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_trace.html.erb
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_trace.html.erb (1.1ms)
  Rendered collection of /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/routes/_route.html.erb [61 times] (122.2ms)
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/routes/_table.html.erb (3.4ms)
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_request_and_response.html.erb
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.000483045s
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_request_and_response.html.erb (2.9ms)
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/routing_error.html.erb within rescues/layout (168.8ms)
Started POST "/users/sign_in" for <IP_ADDRESS> at 2017-08-05 09:00:54 -0400
Processing by Devise::SessionsController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]", "user"=>{"email"=>"[FILTERED]", "password"=>"[FILTERED]"}, "commit"=>"Sign in"}
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.000580516s
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"users"<EMAIL_ADDRESS>"limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.000646701s
Completed 401 Unauthorized in 139ms

Processing by Devise::SessionsController#new as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]", "user"=>{"email"=>"[FILTERED]", "password"=>"[FILTERED]"}, "commit"=>"Sign in"}
  Rendering devise/sessions/new.html.erb within layouts/application
  Rendered devise/shared/_links.html.erb (0.7ms)
  Rendered devise/sessions/new.html.erb within layouts/application (3.6ms)
  Rendered layouts/_messages.html.erb (0.4ms)
Completed 200 OK in 230ms (Views: 158.4ms)

Started GET "/favicon.ico" for <IP_ADDRESS> at 2017-08-05 09:00:56 -0400

ActionController::RoutingError (No route matches [GET] "/favicon.ico"):

actionpack (5.0.5) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
railties (5.0.5) lib/rails/rack/logger.rb:36:in `call_app'
railties (5.0.5) lib/rails/rack/logger.rb:24:in `block in call'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:69:in `block in tagged'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:26:in `tagged'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:69:in `tagged'
railties (5.0.5) lib/rails/rack/logger.rb:24:in `call'
sprockets-rails (3.2.0) lib/sprockets/rails/quiet_assets.rb:13:in `call'
request_store (1.3.2) lib/request_store/middleware.rb:9:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/request_id.rb:24:in `call'
rack (2.0.3) lib/rack/method_override.rb:22:in `call'
rack (2.0.3) lib/rack/runtime.rb:22:in `call'
activesupport (5.0.5) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/executor.rb:12:in `call'
rack (2.0.3) lib/rack/sendfile.rb:111:in `call'
secure_headers (3.6.4) lib/secure_headers/middleware.rb:12:in `call'
railties (5.0.5) lib/rails/engine.rb:522:in `call'
puma (3.8.2) lib/puma/configuration.rb:224:in `call'
puma (3.8.2) lib/puma/server.rb:600:in `handle_request'
puma (3.8.2) lib/puma/server.rb:435:in `process_client'
puma (3.8.2) lib/puma/server.rb:299:in `block in run'
puma (3.8.2) lib/puma/thread_pool.rb:120:in `block in spawn_thread'
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/routing_error.html.erb within rescues/layout
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_trace.html.erb
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_trace.html.erb (3.4ms)
  Rendered collection of /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/routes/_route.html.erb [61 times] (15.2ms)
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/routes/_table.html.erb (1.4ms)
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_request_and_response.html.erb
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.0007212659999999999s
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_request_and_response.html.erb (2.7ms)
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/routing_error.html.erb within rescues/layout (50.5ms)
Started GET "/favicon.ico" for <IP_ADDRESS> at 2017-08-05 09:00:56 -0400

ActionController::RoutingError (No route matches [GET] "/favicon.ico"):

actionpack (5.0.5) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
railties (5.0.5) lib/rails/rack/logger.rb:36:in `call_app'
railties (5.0.5) lib/rails/rack/logger.rb:24:in `block in call'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:69:in `block in tagged'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:26:in `tagged'
activesupport (5.0.5) lib/active_support/tagged_logging.rb:69:in `tagged'
railties (5.0.5) lib/rails/rack/logger.rb:24:in `call'
sprockets-rails (3.2.0) lib/sprockets/rails/quiet_assets.rb:13:in `call'
request_store (1.3.2) lib/request_store/middleware.rb:9:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/request_id.rb:24:in `call'
rack (2.0.3) lib/rack/method_override.rb:22:in `call'
rack (2.0.3) lib/rack/runtime.rb:22:in `call'
activesupport (5.0.5) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
actionpack (5.0.5) lib/action_dispatch/middleware/executor.rb:12:in `call'
rack (2.0.3) lib/rack/sendfile.rb:111:in `call'
secure_headers (3.6.4) lib/secure_headers/middleware.rb:12:in `call'
railties (5.0.5) lib/rails/engine.rb:522:in `call'
puma (3.8.2) lib/puma/configuration.rb:224:in `call'
puma (3.8.2) lib/puma/server.rb:600:in `handle_request'
puma (3.8.2) lib/puma/server.rb:435:in `process_client'
puma (3.8.2) lib/puma/server.rb:299:in `block in run'
puma (3.8.2) lib/puma/thread_pool.rb:120:in `block in spawn_thread'
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/routing_error.html.erb within rescues/layout
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_trace.html.erb
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_trace.html.erb (1.2ms)
  Rendered collection of /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/routes/_route.html.erb [61 times] (12.5ms)
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/routes/_table.html.erb (0.9ms)
  Rendering /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_request_and_response.html.erb
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.001902353s
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/_request_and_response.html.erb (5.4ms)
  Rendered /home/lomky/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/actionpack-5.0.5/lib/action_dispatch/middleware/templates/rescues/routing_error.html.erb within rescues/layout (44.9ms)
Started POST "/users/sign_in" for <IP_ADDRESS> at 2017-08-05 09:01:04 -0400
Processing by Devise::SessionsController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]", "user"=>{"email"=>"[FILTERED]", "password"=>"[FILTERED]"}, "commit"=>"Sign in"}
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.001037198s
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"users"<EMAIL_ADDRESS>"limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.000853472s
Completed 401 Unauthorized in 82ms

Processing by Devise::SessionsController#new as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]", "user"=>{"email"=>"[FILTERED]", "password"=>"[FILTERED]"}, "commit"=>"Sign in"}
  Rendering devise/sessions/new.html.erb within layouts/application
  Rendered devise/shared/_links.html.erb (0.7ms)
  Rendered devise/sessions/new.html.erb within layouts/application (3.7ms)
  Rendered layouts/_messages.html.erb (0.4ms)
Completed 200 OK in 309ms (Views: 235.0ms)

Started POST "/users/sign_in" for <IP_ADDRESS> at 2017-08-05 09:01:29 -0400
Processing by Devise::SessionsController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]", "user"=>{"email"=>"[FILTERED]", "password"=>"[FILTERED]"}, "commit"=>"Sign in"}
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"sessions", "filter"=>{"_id"=>"497fa856314ab10e12c73eb657ea8902"}, "limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.000846557s
MONGODB | localhost:27017 | dcaf_case_management_development.find | STARTED | {"find"=>"users"<EMAIL_ADDRESS>"limit"=>-1, "sort"=>{"_id"=>1}}
MONGODB | localhost:27017 | dcaf_case_management_development.find | SUCCEEDED | 0.000982188s
MONGODB | localhost:27017 | dcaf_case_management_development.update | STARTED | {"update"=>"users", "updates"=>[{"q"=>{"_id"=>BSON::ObjectId('5985bff7ae611217a27a0ad3')}, "u"=>{"$set"=>{"last_sign_in_at"=>2017-08-05 13:01:30 UTC, "current_sign_in_at"=>2017-08-05 13:01:30 UTC, "last_sign_in_ip"=>"<IP_ADDRESS>", "current_sign_in_ip"=>...
MONGODB | localhost:27017 | dcaf_case_management_development.update | SUCCEEDED | 0.000740338s
Redirected to http://localhost:3000/
Completed 302 Found in 156ms

That's bizarre! But I think the db calls taking a normal amount of time and the
My GUESS is that it's some extreme form of dev environment asset compilation, which rails does behind the scenes. (If you tweak the scss or coffeescript, rails will re-pack and compile it on page reload without you having to do anything.) Usually it doesn't take a full minute though!
A way to test this would be to edit some of the scss and js and reload a page, and compare load times. If it recreates the behavior, it's PROBABLY that in some form, though normally this is like a 5s thing and not a 60s thing.

Merging to squelch a few alerts, but let's keep an eye on this.


Accessible Color Warnings

The pick-a-good-color module will always pick an accessible color, but sometimes the color just doesn't look quite right.
To work around this, #325 enabled app developers to choose their own colors. This PR is a followup that ensures sure the human-provided colors are in fact accessible according to the WCAG guidelines..
When a color's contrast ratio is not high enough, this kind of error is produced:
AssertionError: google-play-music-desktop-player: contrast ratio too low for goodColorOnWhite. Try: #DE2811

cc @MarshallOfSound. I took the liberty of adding custom colors for GPMDP as a test case, based on the icon and the website.
cc @codebytere

This also updates the CONTRIBUTING doc to explain the contrast requirements and link to a site that makes it easy to pick accessible colors.
Also broke the doc up a bit with more headings so we can more easily deep-link to sections in the doc.


[WIP] CCO-388: control-plane-operator: reconcile the CCO (rebased)

Rebased copy of #2794

/close


KAFKA-15471: Allow independently stop KRaft controllers or brokers

KIP-979: Allow independently stop KRaft processes
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks for the PR!  Given that we have no automated test, please add comments documenting the output of appropriate manual tests of this feature.

Thanks for describing the testing.  I just did a test to see what would happen if the config file was specified with a relative path, and it did not work well.  For example:
start broker in config/kraft directory, with relative path to config file
 ../../bin/kafka-server-start.sh broker.properties
broker starts, as expected...

try to stop it from repo top-level directory
bin/kafka-server-stop.sh --process-role=broker
zsh: no such file or directory: bin/kafka-server-stop.sh
If we are supporting relative paths, then we need to fail elegantly and with. reasonable error message if we run the "stop" command from some other directory rather than the one where the node was started.

Hey Ron, thank you for catching that bug. I added a log message to notify the user that the start process and the stop process should be called from the same directory. WDYT?

Thanks for describing the testing. I just did a test to see what would happen if the config file was specified with a relative path, and it did not work well. For example: # start broker in config/kraft directory, with relative path to config file  ../../bin/kafka-server-start.sh broker.properties
broker starts, as expected...

try to stop it from repo top-level directory bin/kafka-server-stop.sh --process-role=broker
sed: : No such file or directory

If we are supporting relative paths, then we need to fail elegantly and with a reasonable error message if we run the "stop" command from some other directory rather than the one where the node was started.

LGTM -- I tested the change manually, and it works.  Thanks for the PR!  And your first KIP!


Add AvramSlugify

Hi @andrewmcodes!
This adds AvramSlugify. It lets you build slugs :)
Also, what do you think about adding me to the repo so I can help out with PRs and such?
Thanks,
Paul

Sent you an invite @paulcsmith!

Woo hoo! Thanks :D
On Mar 30, 2020, 1:12 PM -0400, Andrew Mason<EMAIL_ADDRESS>wrote:

Merged #25 into master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Ensure all functions/classes have proper jsDocs

Need to update jsdocs for :

[ ] Connection.js

[ ] ProgramCall.js

[ ] CommandCall.js

[ ] Deprecated.js


Reserve button within Concert details page should fill all inputs with current concert data

Suggested Changes:

When users navigate to concert and then select one concert, It should be able to go to the reserve section and all fields should be automatically filled for the current or selected concert

From Here:

To Here:

Issue has been solved in https://github.com/Diegogagan2587/Book-a-concert-front-end/pull/94


Feature/3.7 branding

Change graphics for upcoming version. I tried Gimp 3 alpha. As it has non destructive layer filters. Akin to the Photoshop color overlay thing. I couldn't get it to work to mimic this. However now the Gimp version of the image is exportable straight. I just hid the original colored Jaime layer and did a colored version of it.
Also the Gimp version didn't have the bottom shape (in Photoshop terms), it is now made straight with painting tools in Gimp.
I still used Gimp 3 to edit the XCF so it might require a newer Gimp to further edit/open. Gimp 3 should be out shortly anyway, I don't see this as a problem.

I'll eventually squash & merge this then if I remember...


Should create and configure a second readme for the distribution of the library

I wanted to first say thanks for this great tool!
I was wanting to get thoughts on adding a readme to the src directory when initializing a new library, and copying that file over to the dist directory on build (following the same pattern as the package.json). I'm currently doing this as a manual process after I build, and it would be nice to have it automated.

@dbfannin — I think that is a great idea 👍
Are you interested in creating a PR for this? Thanks in advance!

Sure I can do that!

Do you think the route should be to just copy the root readme to the dist directory, or adding a second README to the templates?

To keep it simple, I would just leave one. It would be a responsibility of the user to create two sections within it: One for development and another one for usage! 🤓
BTW, @dbfannin thanks for taking thing one! 👍

@dbfannin — The generators/app/templates/README.MD file should do. It's already being generated in the root of the generated code. Thanks in advance!

Implemented in #85 and released as v10.1.0 👍