[Feature]: Add markdown support to Title card

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Is your feature request related to a problem?
Would it be possible to add basic Markdown support to the Title card?
It would be helpful if select text could be in bold or italicised etc.
Describe the solution you'd like

For example I have this welcome message on my main Dashboard that displays in the morning. It would be helpful if I could bold or italicise select words and phrases so that the key information is more easily distinguishable at a glance.
With markdown support I would be be able to style the text in my template using **bold** and *italics* like this:
{% if is_state("binary_sensor.is_it_morning", "on") %} {% set ignore = ["unknown", "unavailable"] %} {% if states("sensor.openweathermap_forecast_precipitation_probability") not in ignore and states("sensor.good_morning_weather_helper") not in ignore and states("sensor.good_morning_forecast_temp_helper") not in ignore %} {% set wet_weather = ("exceptional", "thunder and lightning", "rainy with thunder and lightning", "heavy rain", "rain showers", "snow and rain showers") %} {% set forecast_temp = states("sensor.good_morning_forecast_temp_helper") %} {% set weather_desc = states("sensor.good_morning_weather_helper") %} {% if states("sensor.good_morning_weather_helper") in wet_weather %}The weather today will be **{{ weather_desc }},** the probability of rain is {{ states("sensor.openweathermap_forecast_precipitation_probability") }}%, **don't forget an umbrella.**{% else %}The weather today will be **{{ weather_desc }}.**{% endif %} {% if is_number(forecast_temp) %}The forecast temperature is **{{ forecast_temp }}°C.**{% endif %} {% endif %}
  {% if is_state("binary_sensor.quote_of_the_day", "on") %}
{{ state_attr("binary_sensor.quote_of_the_day", "quotation") }}
*- {{ state_attr("binary_sensor.quote_of_the_day", "who_said_it") }}*
  {% endif %}
{% endif %}

Similar to the Markdown card: https://www.home-assistant.io/dashboards/markdown/

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

This looks like a great idea for secondary and primary info for all cards (if possible), at least for the card template
For example:
type: custom:mushroom-template-card
entity: update.home_assistant_core_update
icon: mdi:home-assistant
icon_color: blue
multiline_secondary: true
primary: Home Assistant Core
secondary: >-
  {%- set version = {"installed":
  state_attr('update.home_assistant_core_update', 'installed_version') |
  version, "latest": state_attr('update.home_assistant_core_update',
  'latest_version') | version, "skipped":
  state_attr('update.home_assistant_core_update', 'skipped_version') | version }
  -%}

  Installed: **{{ version.installed }}**

  {% if version.latest != version.installed
    or version.skipped != 'None' and version.latest != version.skipped
  -%}
    Update available: **{{ '~~'+version.latest+'~~' if version.skipped
    != 'None' and version.latest == version.skipped else version.latest
    }}** {{ '*skipped*' if version.skipped != 'None' and version.latest
    == version.skipped }}
  {%- else -%}
    *No updates*
  {%- endif %}

This card could look like this


Instagram still blocks accounts

As the title indicates, instagram blocks my account when I try to grab a user's followers list with 10k+ items, it stops at around 4.5k. I tried putting a 4-second sleep timer in between iterations under get_users method, but no luck. I also couldn't continue the list from where it stopped by setting next_max_id to (number of followers grabber/12).
Do you have any suggestions?

I tried this, but encountered the same issue . Got blocked after iteration 765.

Will try grabbing the next_max_id from where it stopped and then use it with different account. Will reply in the thread if any success. Cause if I try to use proxy or change user-agent that wont work as mentioned in this  issue

@gitgudscrap After getting blocked from 2 accounts. Finally I tried testing it manually. Turns out that even if I keep scrolling the followers list on Instagram manually, it will still block after 4k followers. Have posted the screenshots below. Furthermore, I'm changing the repo description and removing the "prevents from getting blocked" clause.
You can close the issue now.
Results for manual testing.


Replace GetString with GetTextReader for Data / Metadata

Same idea as #248

Valuable for metadata as well? 💭


Rename and refactor convolution and pooling operators.

We've decided to rename existing convolution and pooling methods to something more approachable and discoverable, following precedents in other frameworks.

[ ] Change method Tensor.convolved2D(withFilter:strides:padding:) to a top-level function named conv2D(_:filter:strides:padding:), taking the original self as a first argument.
[ ] Change method Tensor.convolved3D(withFilter:strides:padding:) to a top-level function named conv3D(_:filter:strides:padding:), taking the original self as a first argument.
[ ] Change method Tensor.maxPooled2D(kernelSize:strides:padding:) to a top-level function named maxPool2D(_:filterSize:strides:padding:), taking the original self as a first argument.
[ ] Change method Tensor.maxPooled3D(kernelSize:strides:padding:) to a top-level function named maxPool3D(_:filterSize:strides:padding:), taking the original self as a first argument.
[ ] Change method Tensor.avgPooled2D(kernelSize:strides:padding:) to a top-level function named avgPool2D(_:filterSize:strides:padding:), taking the original self as a first argument.
[ ] Change method Tensor.avgPooled3D(kernelSize:strides:padding:) to a top-level function named avgPool3D(_:filterSize:strides:padding:), taking the original self as a first argument.

Note:

The new names we recommend are precisely described above. Further naming discussions are absolutely welcome, but will be preferable if delayed until July/August. These new names will make it into Swift for TensorFlow version 0.4.
These methods' derivatives (VJPs) will need to be changed to top-level functions as well.

I'll get to work on this, will post updates! =)

Than you @QuantumTCode!

@rxwei why not just add aliases?

@rxwei why not just add aliases?

We never intended to keep names like convolved2D, maxPooled2D or avgPooled2D around. It's an artifact from early days of Swift for TensorFlow development. Since the project is very young, we would like to be able to improve and iterate quickly without baggage, and thus are not developing for user-facing backwards compatibility.

Also, I think there is a lot of discussions to be had around naming conventions though.

Yep, you are right!

Thank you @QuantumTCode!


Typo in walkthrough

Extra "be" here: "They can be also be used for more detailed mapping of many features you might normally map as points."
https://github.com/openstreetmap/iD/blob/3440b5523c857e2c71be7c7829283530fe4274c7/data/core.yaml#L880
A pokemon go player raised this on reddit so good that someone is paying attention to the walkthrough 😛

Thanks for reporting!  This is a bug that makes me happy.  👏

The same issue is also in these files: https://github.com/openstreetmap/iD/blob/3440b5523c857e2c71be7c7829283530fe4274c7/dist/locales/en.json
https://github.com/openstreetmap/iD/blob/add1bac3f2e5e1bfa7f2eff422cb56fda4347ee3/dist/locales/en-GB.json
(I also came here after reading that PokemonGo thread :) )

I am working on this.

I have finished this task and submitted a pull request.

This was done #4620


Current bower package has no js code

After updating to the latest in my bower.json and installing, I got 404 errors looking for the headroom js files.
I checked the headroom folder in bower_components, and sure enough there is no src folder in there, nor any javascript files at all.  I needed to roll back to the older version I had in my repo.

See the README for latest installation instructions. See various issues if you wish to see the reasoning behind the change

Do you mean bower install https://npmcdn.com/headroom.js/bower.zip --save?
Because that didn't work either.

@smlombardi , i've found that i needed to delete the resulting bower directory (e.g.: bower_components/headroom.js/) and then running the bower install command you noted (the readme one) works and you get the .js files (like dist/headroom.js) there.


A crash log

Hi,
I used the MacOS 10.14 and the Xcode 10. After installing the swift for tensorflow, I got a very long crash log.
crashlog.txt

This is a bug in Xcode and/or LLDB. We recommend using Swift Jupyter for development because it's more stable.

All right. thanks for your reply. 👍


Install by Melpa?

I like this theme, but can it be installed by melpa? That would be nice. Thanks!

I have a pull request in melpa for it, and have got feedback. I’m just kinda busy to deal with it right now. Will do that “soon”. 😅

Done. It’s named “flucui-themes”.


add fuzz test for cert requests with vault issuer

Adds a fuzz test that tests certificate requests with the Vault issuer.
The fuzzer randomizes selected fields in the request and the issuer. Sometimes it will choose correct values and sometimes it will choose incorrect ones.
The fuzzer could be expanded by e.g. adding more objects or randomizing more fields, but it would be good to see how this runs on OSS-Fuzz first.

Pull Request Motivation

Kind
/kind feature

Release Note

NONE

/ok-to-test

@AdamKorcz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name	Commit	Details	Required	Rerun command
pull-cert-manager-master-make-verify	825f385 link	true	/test pull-cert-manager-master-make-verify
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

@AdamKorcz can you fix the linter failure?

/kind feature


update Windows dependency

pywin32 moved to GitHub and now ships binary wheels itself.
https://github.com/mhammond/pywin32
https://pypi.org/project/pywin32/#files

good catch, thanks for the update


daydream: switch to v1.130.0

Fixes build issue with ARCcore: https://github.com/gearvrf/GearVRf-Demos/pull/598
GearVRf-DCO-1.0-Signed-off-by: Mihail Marinov<EMAIL_ADDRESS>

I am still facing that Dex issue with ARCore demo.

Please make sure you git clean -fdx all repos first. I even ran the arcode demo with daydream.

@liaxim,
I have done that  git clean -fdx and reverted my commit "Workaround to Dex issue" to test with this PR.
I may be doing something wrong but I am still facing the dex issue :(

Ok, it works! Thank you.

Planning to merge on Tuesday.
No new problems found. There are some elements missing from gvr-immersivepedia (main menu quads) and gvr-accessibility (piedestal) when using Daydream. It has been happening with v120. Have been looking into it.


Use resolvo instead of libsolv_c

Currently rattler-server uses libsolv-c with some tricks to cache the .solv files. It would be cool if we could make use of resolvo, the new Rust based implementation of a SAT solver.

To get started with this, one would change the line to:
rattler_solve = { version = "0.16.2", default-features = false, features = ["resolvo"] }


Adds chocolatey on windows section to readme

Hi, I've created a choco package and will maintain it moving forward. I would like to add a hint to the readme for all the Windows users of ksonnet. I've also created a Zapier Zap to automatically update the choco package on every release created in ksonnet/ksonnet.

Hello,
Thanks for this package. Would you mind if the ksonnet team took this over? We'd hook it into our build pipeline and would not require the Zapier integration?

Hi, this would even be better. How would you like to do this? Do you want to create a repo and I'll hand over the package to you? I need to check how I can transfer ownership of the chocolatey package to you. I guess you'd have to create a chocolatey account first?

This item is still open. We are currently working out our 0.12 release and will revisit afterwards.

ksonnet will be discontinued, so I think this issue can be closed.


Order items manually

Hi,
I miss a option to order items manually on menu, it is possible?

Currently this is not possible but it could be. I could add some sorting directive where in the JSON you specify a number and then it sorts based off that number.
Example:
"MenuItemNumber": "8"
Would  anyone else be interested in this feature?

We also have #117 which is sorting based on the order listed in the JSON file. Which method would you prefer?

I prefer order JSON file, because I don't use ssh/config file

If shuttle built the menu based on the order in the JSON file would that be adequate?

Yes! that's be perfect...

Okay, Thanks for the update!

Any progress on this? Would be great to have the order based on the order in the JSON file.

@nathanreid No progress yet. I hope to have it in the next release I dont have a timeline for you.

#117 is asking for the same feature. Cleaning up the issues area. Closing this and using #117 as the main for this request.


Review recent PRs and prepare for 0.0.2

Ok, it has been a while since release and there's a number of patches that have been incorporated into spoon. We need to review the changes (since many conflicted, and I did my best to resolve them) and prepare to do a 0.0.2 release.
All pull requests have been incorporated at this point. There's now support for more posix_spawn actions on UNIX (only) and support for the equivalent function _spawnv* on Windows.
Among the things that need review:

We need some tests at least for the basic functionality.
errno checking/handling had to be rejiggered a bit when I added Windows support; unsure if it's ok.
Windows support: I could not test, so I'm unsure if I merged everything properly.

Anything else?
Pinging @wmeissner, @danielcavanagh, @evilrich directly since they have contributed (and if you'd like commit access, I have no problem with that).

Circling back to @boutil's suggestions: I believe libc@4454035 was covered by e90c6e32114d5791d0b9d1fb02f69f8f5f92c683 and libc@9eceb36 was covered by b90c9936a378fdc59bf837b291c90fcf6f2aa14c.

Calling this done as of 0.0.5.


WebAssembly Backend

WASM backend

Compiles with Coq 8.11 / 8.12
Switches to separate extraction
WASM PoC, but functional
Need to better integrate testing / runtime
Left as draft PR for now

Replaced by #147


rename Tracks.tail_width to Tracks.width

🧰 Task
A Tracks.head_length API was added to the tracks layer by @JoOkuma in #3168. @andy-sweet noted in #4688 that Tracks.tail_width is now a bit of a misnomer as it adjusts the width of both the head and the tail.
We should probably deprecate Tracks.tail_width in favour of Tracks.width

👍 from me. I'll point out that this might eventually go under tracks.style.width if we unify all visual attributes for all layers under style.


fix: provide right response when there are failures in multi select changeset mode

When a change set request fails due to an error in processing one of it's parts, we exit the scenario and don't execute the remaining parts of the change set.
We correct the behaviour to return a single error on change set failure.
The function handlePart is refactored into:

ChangeSet case:
getChangeSetResponse
    getPartRequest
    get412ErrorInfo*
    getPartResponse
    getCombined412ErrorResponse
Isolated case:
getPartRequest
getPartResponse

We shall use the pull request https://github.com/SAP/open-ux-odata/pull/869 for this change.


Receiving prompt in log: "Configuration of Pirate Weather sensor in YAML is deprecated and can be safely removed" but has already been removed from configuration.yaml.

Message in the log:
2023-02-03 13:54:02.118 WARNING (MainThread) [custom_components.pirateweather.sensor] Configuration of Pirate Weather sensor in YAML is deprecated Your existing configuration has been imported into the UI automatically and can be safely removed from your configuration.yaml file
...but there's no longer anything pertaining to Pirate Weather in my configuration.yaml file. Could the info be elsewhere?

Thanks for using this integration and opening this issue, since that is definitely not the expected behavior! I just tested the most recent version on my end and I'm not seeing these warnings once they're removed, so definitely something strange going on here. Just as a sanity check, can you verify that there's not a rogue sensor block somewhere in either your configuration or sensor.yaml, and that you've restarted core?

Sure enough -- there was code in sensors.yaml. I thought I'd used VSCode to search all of my yaml files/folders... Anyway, thanks!


named services is a breaking change and should have been a major version

Describe the bug
Our automation scripts do the following

pip install cumulusci
cci service connect github --username $GITHUB_USERNAME --token $GITHUB_TOKEN --email<EMAIL_ADDRESS>
That worked yesterday, but now fails with

Error: Missing argument 'SERVICE_NAME'.

I appreciate the functionality provided by this change, but it is a breaking change. The existing, default behavior should have been preserved. Or at least some warning should have appeared in this version, as if this feature was being deprecated.
Context
Please include the following information at minimum.

cci version 3.33.0
python 3.9.4
macOS 10.14.6

@avisser Apologies for the breaking change in a minor version -- I was forgetting that this command is also used in CI scripts in this fashion.
You can fix the error by adjusting the command to specify a name for the service: e.g. cci service connect github github.com --username $GITHUB_USERNAME --token $GITHUB_TOKEN --email<EMAIL_ADDRESS>You can use another name instead of github.com. The first github service that you connect will be used by default.

@avisser fwiw, we are going to change this so that the service name is optional, and try to get that released later today.
Generally we try hard to avoid breaking changes like this, and I think we are usually pretty successful, but obviously this one slipped through. Pinning to a specific version is the way to avoid surprises -- perhaps you can pin 3.33 but then revisit periodically to update (with a CI build to verify the new version before merging the update to the pin).

@avisser We just released cumulusci 3.33.1 which restores the ability to run cci service connect without specifying a service name (it will use the name "default")


Multi-level resources with static JSON file

I want to create the following endpoints
/items/:userId/ -> returns all items for a given user
/items/:userId/item/:itemId -> returns a single item for the user if it exists
How would the static data in the JSON file look like if it is possible?  I couldn't figure out if something like this is possible from the README.
I want to avoid using a module - as it would mean refactoring a lot of existing code.

You can access items for the user by id through a filter.
{
  "users": [
    {
      "id": 1,
      "name": "Sir John Franklin"
    }
  ],
  "items": [
    {
      "id": 1,
      "userId": 1,
      "ship": "HMS Erebus"
    },
    {
      "id": 2,
      "userId": 1,
      "ship": "HMS Terror"
    }
  ]
}

/users/1/items/1 yields a 404 error but /users/1/items/?id=2 yields:
[
  {
    "id": 2,
    "userId": 1,
    "ship": "HMS Terror"
  }
]

So you can apply the advice in https://github.com/typicode/json-server/issues/72 and use a filter to achieve the same result as you might expect from /items/:userId/item/:itemId (albeit enclosed in an array)

Hi @cuongluu8 are you happy with this answer? Can you close the ticket?

And how about this? I want to visit /user/1/data, but only got empty object {}.
{
  user: [
    {
      id: 1,
      data: [/*...lots of data item...*/]
  ]
}

Ok, I found the right way for /user/1/data like this:
{
  user: [
    {id: 1}
  ],
  data: [/*...lots of data item...*/]
}


sgml-common: new formula

If sgml-common is a dependency of formulae in core, it should be added to core.

I think the point is to have Linux-only formulae here even if something depends on them from the core, no?

At least, on the main page we have
Linux-only formulae that are not dependencies of core formulae

:)

oh! not I missed that

It's so that if the version of a dependency is bumped, its dependents are tested for linkage breakage. Currently that test is done only for dependents in the same repo. Cross-repo deps are not tested for linkage breakage.


chore: refresh dependencies to update to latest versions

What does this PR do?
fix cve in rollup
Screenshot / video of UI

What issues does this PR fix or reference?
https://github.com/rollup/rollup/security/advisories/GHSA-gcx4-mw62-g8wm
How to test this PR?

rebased


Clean up log stream output

Use append instead of appendLine since the log stream data already has line breaks
Fixes https://github.com/Microsoft/vscode-azurefunctions/issues/1089 where the functions log stream sometimes displays duplicate information. As far as I can tell the 'data' comes in on a per-line basis with a timestamp, so I'm pretty confident this logic only removes duplicate lines. Y'all think I need to be more careful in case the data comes in smaller chunks?

Closing this one for now. Duplicate data is annoying, but not as bad as accidentally hiding non-duplicate data IMO. I want to be more careful about this


Data type in C

Description 📜
I have briefly defined the fundamentals data type in C using numerous example along with code syntax.
Fixes # 1295

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[ ] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[ x ] I follow Contributing Guidelines & Code of conduct of this project.
[ x ] I have performed a self-review of my own code or work.
[ x ] I have commented my code, particularly in hard-to-understand areas.
[ x ] My changes generates no new warnings.
[ x ] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

96 files changed😲???
Shreya plz fetch all the changes from the "girlscript/C_CPP" to your local machine and then make a PR.

Okay
On Thu, 23 Sep, 2021, 2:13 PM Deepak Verma, @.***>
wrote:

96 files changed😲???
Shreya plz fetch all the changes from the "girlscript/C_CPP" to your local
machine and then make a PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/girlscript/winter-of-contributing/pull/2094#issuecomment-925615790,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUIXTR3YSTRL3B5N4QIDYOLUDLSEZANCNFSM5ESYEVLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

is it done??

is it okay now??
On Thu, 23 Sept 2021 at 15:13, Ruhi Chaudhary @.***>
wrote:

Okay
On Thu, 23 Sep, 2021, 2:13 PM Deepak Verma, @.***>
wrote:

96 files changed😲???
Shreya plz fetch all the changes from the "girlscript/C_CPP" to your
local machine and then make a PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/girlscript/winter-of-contributing/pull/2094#issuecomment-925615790,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUIXTR3YSTRL3B5N4QIDYOLUDLSEZANCNFSM5ESYEVLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@shreyarai05 close this PR and then fetch all the changes from girlscript/CPP then make a PR

Closing this PR. Please fetch the updated repo and make the new PR. Here is a video explaining the workflow.


[CosmosDB] Fixing gaps in the new apiVersion

This PR moves privateEndpoint related specs from preview API to latest stable API. This is done because the feature is GA'ed since March and we wanted to make the specs available consistently.
This PR also edits readmes to incorporate the new apiVersion.
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run

Hi @MehaKaushik please resolve the CI failures.
And recent changes might break autorest generation, for your information, the following is the error messages:
01:26:18.077 cmderr 	[main.go] FATAL: swagger-document/compose - FAILED
01:26:18.077 cmderr 	[main.go] FATAL: Error: '$.definitions.ErrorResponse.properties.code.description' has incompatible values (---
01:26:18.078 cmderr 	[main.go] Error code.
01:26:18.078 cmderr 	[main.go] , ---
01:26:18.078 cmderr 	[main.go] The error code.
01:26:18.078 cmderr 	[main.go] ).
01:26:18.078 cmderr 	[main.go] Failure during batch task - {"tag":"package-2020-09"} -- Error: '$.definitions.ErrorResponse.properties.code.description' has incompatible values (---
01:26:18.078 cmderr 	[main.go] Error code.
01:26:18.078 cmderr 	[main.go] , ---
01:26:18.082 cmderr 	[main.go] The error code.
01:26:18.082 cmderr 	[main.go] )..
01:26:18.083 cmdout 	[main.go] Process() cancelled due to exception : '$.definitions.ErrorResponse.properties.code.description' has incompatible values (---
01:26:18.083 cmdout 	[main.go] Error code.
01:26:18.083 cmdout 	[main.go] , ---
01:26:18.083 cmdout 	[main.go] The error code.
01:26:18.083 cmdout 	[main.go] ).
01:26:18.084 cmderr 	[main.go]   Error: '$.definitions.ErrorResponse.properties.code.description' has incompatible values (---
01:26:18.084 cmderr 	[main.go] Error code.
01:26:18.084 cmderr 	[main.go] , ---
01:26:18.085 cmderr 	[main.go] The error code.
01:26:18.085 cmderr 	[main.go] ).

ErrorResponse might be defined in multiple swagger files but do not have the same properties

Hi @ArcturusZhang regarding these breaking changes here(https://github.com/Azure/azure-rest-api-specs/pull/11609/checks?check_run_id=1420566034)
In apiVersion 2020-04-01 privateEndpointConnextion.json and privateLinkResources.json files were referenced from the preview apiVersion 2019-08-01-preview. When we created 2020-09-01 swagger specs we used OpenAPIHub to copy the 2020-04-01 specs. This resulted in the copying of privateEndpoint related properties.
Now, in this PR I am adding the JSON files by copying them from 2019-08-01. I would have expected the property definitions to look exactly the same but there are few differences. The correct definitions are the ones that I am introducing in this PR.
Can we get a breaking change exception?

Hi @MehaKaushik please resolve the CI failures.
And recent changes might break autorest generation, for your information, the following is the error messages:
01:26:18.077 cmderr 	[main.go] FATAL: swagger-document/compose - FAILED
01:26:18.077 cmderr 	[main.go] FATAL: Error: '$.definitions.ErrorResponse.properties.code.description' has incompatible values (---
01:26:18.078 cmderr 	[main.go] Error code.
01:26:18.078 cmderr 	[main.go] , ---
01:26:18.078 cmderr 	[main.go] The error code.
01:26:18.078 cmderr 	[main.go] ).
01:26:18.078 cmderr 	[main.go] Failure during batch task - {"tag":"package-2020-09"} -- Error: '$.definitions.ErrorResponse.properties.code.description' has incompatible values (---
01:26:18.078 cmderr 	[main.go] Error code.
01:26:18.078 cmderr 	[main.go] , ---
01:26:18.082 cmderr 	[main.go] The error code.
01:26:18.082 cmderr 	[main.go] )..
01:26:18.083 cmdout 	[main.go] Process() cancelled due to exception : '$.definitions.ErrorResponse.properties.code.description' has incompatible values (---
01:26:18.083 cmdout 	[main.go] Error code.
01:26:18.083 cmdout 	[main.go] , ---
01:26:18.083 cmdout 	[main.go] The error code.
01:26:18.083 cmdout 	[main.go] ).
01:26:18.084 cmderr 	[main.go]   Error: '$.definitions.ErrorResponse.properties.code.description' has incompatible values (---
01:26:18.084 cmderr 	[main.go] Error code.
01:26:18.084 cmderr 	[main.go] , ---
01:26:18.085 cmderr 	[main.go] The error code.
01:26:18.085 cmderr 	[main.go] ).

ErrorResponse might be defined in multiple swagger files but do not have the same properties

I removed the redundant ErroResponse, yet this error is still showing up. Can you help identify the root cause.

/azp run

You are modifying an existing stable API version, which is considered a breaking change. (See https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md#versioning for details.) You should either request a breaking change approval (instructions in the link) or introduce this functionality in a new API version.

Because of the breaking changes, I am abandoning this PR. We will add GA PrivateEndpoint APIs in the next apiVersion.


suggestion about removing libdatachannel as a submodule

Hi paullouisageneau,
How do you think about removing libdatachannel as a submodule from this repository? A person using libdatachannel and datachannel-wasm together can add both of them as submodules and then add an if statement in their cmake code. As datachannel-wasm is a partial implementation of libdatachannel for wasm without actual code dependency, I think this can make this repository lighter! Versioning can be done by adding a line to the readme file or by adding a Version file.
This improvement would become visible when working with a forked version of libdatachannel with datachannel-wasm. Currently, this leads to having two copies of libdatachannel since there is a forked one and another one inside datachannel-wasm.
And thanks for your continuing work!

I like datachannel-wasm being platform agnostic, however I admit it could be more practical to separate libdatachannel. It doesn't make integration a lot more difficult.

Thanks for being so acceptive to suggestions. I think since you have Convergence as an excellent example for people on how to use the wasm part of datachannel-wasm and libdatachannel together, removing as submodule won't hurt that much in this direction, but I also understand if you prefer the other direction since its just a submodule that can be ignored without having side effects more than allocating some disk space.


RUM-1520 Add all Logs Feature integration tests

What does this PR do?
Add integration tests covering all the Logs Feature apis
Motivation
Reliability, reliability, reliability

Codecov Report

Merging #1769 (8da8d33) into develop (bece8a1) will increase coverage by 0.05%.
Report is 14 commits behind head on develop.
The diff coverage is n/a.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1769      +/-   ##
===========================================
+ Coverage    83.34%   83.39%   +0.05%
===========================================
  Files          468      468
  Lines        16304    16309       +5
  Branches      2431     2432       +1
===========================================
+ Hits         13587    13600      +13
+ Misses        2050     2038      -12
- Partials       667      671       +4

see 27 files with indirect coverage changes


[AAD Support] Support AAD and new user & group schema

Coverage decreased (-2.9%) to 50.344% when pulling e09eacdbeb88dec3c9d5daa1db8552e29037b7f6 on authndev into fb025c0941aac3f48fb65be739c609f61870493c on master.


feat: reuse logical planner in influxdb_iox

Which issue does this PR close?
Closes #724
Rationale for this change
Reust logical planner in influxdb_iox.
See detail

What changes are included in this PR?
See title.

Are there any user-facing changes?
None.

How does this change test
Test by ut.

Codecov Report

Merging #730 (5a46aee) into main (8837aa6) will decrease coverage by 0.24%.
The diff coverage is 4.10%.

:exclamation: Current head 5a46aee differs from pull request most recent head ff85e0b. Consider uploading reports for the commit ff85e0b to get more accurate results

@@            Coverage Diff             @@
##             main     #730      +/-   ##
==========================================
- Coverage   68.26%   68.02%   -0.24%
==========================================
  Files         288      286       -2
  Lines       45335    44714     -621
==========================================
- Hits        30946    30417     -529
+ Misses      14389    14297      -92

Impacted Files
Coverage Δ

sql/src/frontend.rs
0.00% <0.00%> (ø)

sql/src/influxql/mod.rs
0.00% <ø> (ø)

sql/src/influxql/planner.rs
0.00% <0.00%> (ø)

sql/src/influxql/provider.rs
0.00% <0.00%> (ø)

sql/src/planner.rs
91.91% <0.00%> (-0.11%)
:arrow_down:

sql/src/tests.rs
89.28% <100.00%> (-4.52%)
:arrow_down:

... and 15 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@Rachelint  I'm OK with this PR. Let's wait for suggestions from @jiacai2050.


Getting started application doesn't work quite right.

MyApp2.zip

Hi,
The string values for the users display as raw strings in the welcome.html page.  Most likely, I have done something wrong, but I would appreciate it if you would point it out to me.
Thank you.

I think I know what this. It's a common mistake...perhaps it's even wrong in our docs. But, in ES 2015 and TypeScript, string templates need to be enclosed in back ticks, not quotes.
get fullName() {
  return `${firstName} ${lastName}`;
}

Let me know if that fixes it.

Hi Rob,
It has been improved, though it doesn’t behave consistently in safari, chrome, or firefox.  I am now getting the picture below.  Can you tell me what I have to do for the alert?
I am also getting warnings in the WebStorm editor.  It says that the submit needs to be static and the get fullName is unused.
-Denis

On Jan 29, 2016, at 3:33 PM, Rob Eisenberg<EMAIL_ADDRESS>wrote:
Let me know if that fixes it.
—
Reply to this email directly or view it on GitHub https://github.com/aurelia/skeleton-navigation/issues/280#issuecomment-176956417.

Show my your full code from the js and html files.

Unfortunately the

`export class Welcome {
heading = 'Welcome to Aurelia!';
firstName = 'John';
lastName = 'Doe';
get fullName() {
return ${this.firstName} ${this.lastName};
}
submit() {
alert('Welcome, ${this.fullName}!');
}
}`

I fixed it for you. You can use three backticks for large code blocks on github. You can also follow the backticks with "html" or "javascript" to get the correct highlighting.

Also, you need to use the backticks in the submit button as well for the alert message.

Other than that, I don't see anything wrong. Can you tell me what errors you are seeing?

WebStorm could be confused because you are using ES 2016 class field instances.

@EisenbergEffect latest Webstorm supports ES 2016 class field.
@denismp set ECMAScript 6 as the JavaScript version in WebStorm’s Preferences (Languages & Frameworks | JavaScript).

Runtime error from chrome:
INFO [aurelia] Aurelia Started
aurelia-logging-console.js:38 DEBUG [templating] importing resources for http://<IP_ADDRESS>:8080/src/app.html ["bootstrap/css/bootstrap.css", "font-awesome/css/font-awesome.css"]
aurelia-logging-console.js:38 DEBUG [templating] importing resources for http://<IP_ADDRESS>:8080/src/welcome.html []
aurelia-binding.js:2032 Uncaught Error: submit is not a function
WEB storm is giving me warnings for the welcome.html for “submit trigger now allowed here” and “attribute bind is not allowed here.”

On Jan 29, 2016, at 4:08 PM, Rob Eisenberg<EMAIL_ADDRESS>wrote:
Other than that, I don't see anything wrong. Can you tell me what errors you are seeing?
—
Reply to this email directly or view it on GitHub https://github.com/aurelia/skeleton-navigation/issues/280#issuecomment-176969988.

The web storm errors on the html are bogus errors. That is spec-compliant html...web storm just doesn't realize it. The real error is "submit is not a function". Can you check to see if you have any compiler errors? You might also want to run gulp clean and then gulp build

I have already set WEBstorm for ecma6.
gulp clean
[16:18:05] No gulpfile found
Deniss-IMAC:MyApp2 denisputnam$ which gulp
/usr/local/bin/gulp
Deniss-IMAC:MyApp2 denisputnam$
How do I create the gulp file?

Ok, you are using the beginner kit. Gotcha. There is no gulp for that. Please zip up your project and attach it here. Let me take a look.

@EisenbergEffect the zip is in the first comment of this issues

MyApp2.zip
Here is the latest version.

Okay, I removed the --optional 'es7.classProperties", "es7.decorators'  from the file filter and that seems to have corrected the problem.
Boy that was ugly.
The config.js file has this in it:
System.config({
  defaultJSExtensions: true,
  transpiler: "babel",
  babelOptions: {
    "optional": [
      "es7.decorators",
      "es7.classProperties"
    ]
  },

Ok...so was there a bug in our starter kit? I'm not quite following what the issue was.

Originally I was having a problem with the @inject annotation.  Then someone suggested that I use the --optional 'es7.classProperties", "s7.decorators’, which ended up placing the transpiler entry in the config.js file (I think), which then created the problem that I posted.
I think that the WEBstorm editor then populated the config.js file with the transpiler/babelOptions (don’t hold me to that though), and then the problem showed up.  After I edited the file filter options by taking out the —optional args it corrected the problem.
I think the beginners kit needs have the transpiler entry in it, so that kit compiles properly.  Of course, this is only a guess.
-Denis

On Jan 29, 2016, at 5:24 PM, Rob Eisenberg<EMAIL_ADDRESS>wrote:
Ok...so was there a bug in our starter kit? I'm not quite following what the issue was.
—
Reply to this email directly or view it on GitHub https://github.com/aurelia/skeleton-navigation/issues/280#issuecomment-176997186.


[CT-1474] [Feature] Let users add fields to strucutred logs

Is this your first time submitting a feature request?
No, I have made other feature requests.

[x] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
At the moment, structured logs have a predefined set of JSON properties (docs).
I would like to to be able to add fields to the structured logs to consume in downstream systems.
This ask was inspired by the query-comment marco. By customizing the macro, I can "log" exactly the details I need, removing info I don't need and adding info I do need.
Describe alternatives you've considered
Here's my work-around to augment logs with additional data.
Instead of consuming logs as they are generated to stdout, I write the logs to file. Then I execute a Python script that adds data from manifest.json into the logs file (by data.node_info.unique_id in logs) and then re-emits the logs.
Who will this benefit?
Use-case: add node tags to the data.node_info property in logs. By tagging a node with team ownership, the log consumer can alert different teams based on the failures.
Example:
{"level": "error", "data": { "node_info": {"tags": ["finance_team"], ...}, ...}, ...}

The consumer would see the "level": "error" and prepare to alert. Then the consumer would see that the node is tagged with "finance_team", so instead of sending a general alert, a more narrow, finance alert is sent.
Are you interested in contributing this feature?
Yes, I could help if we are interested in the feature.
Anything else?
No response

@tmastny Thanks for opening! & long time no see :)
First off, you have good timing. We're doing work on structured logging right now, and one piece of it is ensuring that the node_info dict is available on as many relevant events as possible (at parity with the old logging system: https://github.com/dbt-labs/dbt-core/issues/6222).
Two thoughts:

I don't think we should put the full node object (manifest entry) on every single node-related. The motivation for node_info is, this should be enough information to answer 80-90% of real-ish-time questions you could ask about dbt models running right now. For everything else, including retrospective / longitudinal analysis, a join to the full manifest entry feels appropriate.
I don't think we'll be able to support this in the same sort of totally flexible mechanism as the query_comment macro. We're doing a lot of work to make our events/log messages strongly typed, and that requires us to be able to say in advance the exact structure of their contents.

Proposal
So: What do you think about using the meta field for this? That is: always meta, and only meta.
The big idea with meta is:

it's a dictionary that can contain whatever key-value pairs you want
it has no functional purpose within dbt — you put things in there, and they show up
it's for metadata! and logs are metadata :)

Not too dissimilar from the ability to annotate all log events with env/run-level metadata (https://github.com/dbt-labs/dbt-core/issues/5228). It's explicit, and it's explicitly not used for any actual dbt core functionality.
How is meta different from tags? Well... tags are a teensy bit more special, and originally designed for node selection. (You can use config.meta.key:value now for node selection, too, but that's not its original intent.) I'd vote for one or the other, and my vote goes to meta.
Implementation
As far as implementing this, I think it could be a fairly simple change in two places. First, the proto type:
https://github.com/dbt-labs/dbt-core/blob/6c76137da4e72bbcad6e7789a78c31f1bf5cffac/core/dbt/events/types.proto#L27-L37
Adding something like: map<string, string> adapter_response = 9;
And then the Python code to use it:
https://github.com/dbt-labs/dbt-core/blob/6c76137da4e72bbcad6e7789a78c31f1bf5cffac/core/dbt/contracts/graph/parsed.py#L186-L203
Adding something like: "meta": getattr(self, "path", {}),


[GHSA-6rh5-23hx-j452] Improper Authorization in Jenkins Core

Updates

Affected products
Source code location

Comments
Add source code location related to CVE-2019-1003003.

Hi @sunSUNQ, source code location is an optional field, so please don't be concerned if a missing source code location is the only item you find!
However, this advisory was missing 2.150.2 as a patched product, so I adjusted the vulnerable version ranges accordingly. I also replaced http://www.securityfocus.com/bid/106680, which is currently a dead link, with an archived copy of the page.


[Feature][Kafka] Add debezium_record_table_filter and fix error

Purpose of this pull request
This add new feature to filter debezium data when use kafka read debezium_json format data.

Does this PR introduce any user-facing change?
no

How was this patch tested?
add new test.

Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist
Add ci label in label-scope-conf
Add e2e testcase in seatunnel-e2e
Update connector plugin_config

[ ] Update the release-note.

cc @hailin0


Dropbox Fails to Mount - Authorization Page Failed to Load

I'm attempting to use the File System for Dropbox Chrome OS extension. I am having trouble setting it up, as I continue to get this message:
Dropbox failed to mount...
Authorization page failed to load

I had this problem a week ago, but it seems to have been fixed! Try again and report back?

I am currently experiencing this issue. Tried uninstall and reinstall.

Same for me.

I am having the same issue as well.  It works for a Chromebook that I already had it set up months ago but my new one will give me this error when trying to mount Dropbox through the "Files" app.  Any ideas?

Also happening for me on a new Acer Chromebook 315. Used to work fine on my older one but this new one flashes the login page briefly, then it closes and displays the failure message with "Authorization page could not be loaded." as per mccyclone above.
I'm running Chrome OS 79.0.3945.86 (Official Build) (64 bit)
Could this be linked to the latest version of Chrome OS as it wasn't happening on the earlier version my other Chromebook was running when I first ran the Dropbox File System app?

Mine is happening on my new Acer Chromebook 715 that I purchased last week.
Matt Herman

From: Falcon124<EMAIL_ADDRESS>Sent: Friday, December 20, 2019 9:15:09 PM
To: yoichiro/chromeos-filesystem-dropbox<EMAIL_ADDRESS>Cc: mherman95<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [yoichiro/chromeos-filesystem-dropbox] Dropbox Fails to Mount - Authorization Page Failed to Load (#99)
Also happening for me on a new Acer Chromebook 315. Used to work fine on my older one but this new one flashes the login page briefly, then it closes and displays the failure message with "Authorization page could not be loaded." as per mccyclone above.
I'm running Chrome OS 79.0.3945.86 (Official Build) (64 bit)
Could this be linked to the latest version of Chrome OS as it wasn't happening on the earlier version my other Chromebook was running when I first ran the Dropbox File System app?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/yoichiro/chromeos-filesystem-dropbox/issues/99?email_source=notifications&email_token=AOC3FMHR6W6465Z5LFLON4TQZWC33A5CNFSM4FED7PYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHOT3JI#issuecomment-568147365, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOC3FMCXFCDRI4GX36EECM3QZWC33ANCNFSM4FED7PYA.

I've got the same problem on my Samsung Chromebook.  I did a factory reset (Powerwash) and re-initialized it and still the same error.  The problem seems to be widespread as I found quite a few references to it when I searched online.  I'm running Chrome 79.0.3945.86 as of 12/23/19
Somebody has to know where this error message is generated...

My Samsung Chromebook still has it working weirdly enough. It must be an issue the developer has. Hopefully they can resolve it quickly as it is a very helpful tool.
Matt Herman

From: Robert Cowan<EMAIL_ADDRESS>Sent: Monday, December 23, 2019 6:31:19 AM
To: yoichiro/chromeos-filesystem-dropbox<EMAIL_ADDRESS>Cc: mherman95<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [yoichiro/chromeos-filesystem-dropbox] Dropbox Fails to Mount - Authorization Page Failed to Load (#99)
I've got the same problem on my Samsung Chromebook. I did a factory reset (Powerwash) and re-initialized it and still the same error. The problem seems to be widespread as I found quite a few references to it when I searched online. I'm running Chrome 79.0.3945.86 as of 12/23/19
Somebody has to know where this error message is generated...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/yoichiro/chromeos-filesystem-dropbox/issues/99?email_source=notifications&email_token=AOC3FMEHLJIKS2DIGVFNNLTQ2CVRPA5CNFSM4FED7PYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHRA4KI#issuecomment-568462889, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOC3FMAEJT3BODFXD3RHXWLQ2CVRPANCNFSM4FED7PYA.

Facing the same issue on my new ASUS Chromebook C425. Version 79.0.3945.86 (Official Build) (64-bit)

Duplicated #120. Close this issue, and I treat this issue on the #120. Thank you for the reporting!


Improve previews documentation

After having tested prismic previews with the plugin I came up with some ideas to improve the documentation. Hope you will agree with this, I'm also open to changes/suggestions!
A summary of what I changed:

remove the previews.md which seems to be the old version, to avoid any confusion
added a part to handle the unpublished document, as I felt it was missing in the new guide (I mostly reused what you wrote in the old guide)
changed the "merge with prismic data" part, by introducing a helper example which I feel would be more convenient to use since then we only need to add 1 line to the template component
added a limitations section to warn people about what work and not with the previews currently, again to avoid confusion and waste of time

This is great! Thanks for the updates. I'll read through the changes and put some notes down if necessary.
I have some ideas of how we can make the whole preview system easier by providing a withPreview HOC, similar to gatsby-source-prismic-graphql, that basically does what the existing preview guide implements. I'll open a separate issue to discuss.

Looks good! Thanks for bringing in the unpublished previews docs and removing the old file.

RFP posted here: https://github.com/angeloashmore/gatsby-source-prismic/issues/223


Suggest to use flag after a sub-command

Hi @kbknapp,
I saw that  https://github.com/kbknapp/clap-rs/issues/927 was mentored, so I'd like to give it a try.
Here is a first attempt. The message is simpler than what to suggest in the issue, because I could not find out how to print this part from did_you_mean_flag_suffix:
        myapp --foo bar
              ^^^^^

By the way, I splitted did_you_mean_suffix into did_you_mean_flag_suffix and did_you_mean_value_suffix, is that ok?

This change is

Coverage increased (+0.06%) to 91.985% when pulling 4e0ae66034502a79dfcb40abd2afd52c80908329 on little-dude:flag into 49f9dc166a20483643e6e08606b2956ee5e8521d on kbknapp:master.

Wow @little-dude looks like you're on a roll! Great work! I'm re-building the AppVeyor build to see if it was just a fluke.

I'd suggest: imp(Suggestions): suggests to use flag after subcommand when applicable and tests(Suggestions): update tests for subcommand suggestions

Coverage increased (+0.06%) to 91.985% when pulling e8518cf07d0fadc712986da7427bc2d294e5cfa1 on little-dude:flag into a6c6e8152920b8183d4384623707e32a2c559f7a on kbknapp:master.


Patch-1

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[ ] I have read the application guidelines.
[ ] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[ ] The software delivered for this grant will be released under an open-source license specified in the application.
[ ] The initial PR contains only one commit (squash and force-push if needed).
[ ] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: juliusjulyp:x: Asante-ntiroYou have signed the CLA already but the status is still pending? Let us recheck it.

Hello David Hawig,,
My name is Muchiri and we would like to continue with our grant procedure
under the web3 foundation and build for Polkadot community and ecosystem in
Africa. We were experiencing some few financial issues with our projects
but we have rallied past them and we are ready to continue building our
project and community. Kindly help us get back and we will do our best to
deliver.
with regards,
Muchiri Elkanah,
CEO Jua Labs
On Tue, May 9, 2023 at 4:03 PM David Hawig @.***> wrote:

I'm closing the application due to inactivity. Let me know if I should
reopen it.
—
Reply to this email directly, view it on GitHub
https://github.com/w3f/Grants-Program/pull/1680#issuecomment-1540085614,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKB3JDSBGHDFWYTC42AHJ3XFI6CTANCNFSM6AAAAAAXD6LPDM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for pinging me here. I suggest that you open a new PR. But keep in mind that we don't fund ecosystems or community-focused projects via our grants program. If this is your main goal, you might want to take a look at the treasury instead: https://github.com/w3f/Grants-Program#treasury


fix(scaffolder): update annotator action readme

Resolves:
Addresses the comments on the PR  https://github.com/janus-idp/backstage-plugins/pull/1567

@debsmita1 I was just wondering, is the getCurrentTimestamp utility function necessary?
You should be able to achieve the same thing by using the following instead?
const time = `${dateObj.toLocaleDateString()}, ${dateObj.toLocaleTimeString('en-US')}`

This is mainly to address the fact that the current tests for that utility function being brittle and compares the output of toLocaleDateString (which can be formatted differently depending on the platform it's run) with a hard-coded date.

for context:

with my change: https://productionresultssa2.blob.core.windows.net/actions-results/37472355-c409-468d-81af-fe2176f[…]&sr=b&st=2024-05-28T22%3A47%3A33Z&sv=2021-12-02

2024-05-28T21:52:34.6648360Z     Expected: "2021-05-12, 07:03:18 AM"
2024-05-28T21:52:34.6648891Z     Received: "5/12/2021, 07:03:18 AM"

but without it I had the opposite failure locally

A yarn prettier:fix needs to be run as well

@debsmita1 I was just wondering, is the getCurrentTimestamp utility function necessary?
You should be able to achieve the same thing by using the following instead?
const time = `${dateObj.toLocaleDateString()}, ${dateObj.toLocaleTimeString('en-US')}`

This is mainly to address the fact that the current tests for that utility function are brittle and compares the output of toLocaleDateString (which can be formatted differently depending on the platform it's run on) with a hard-coded date.

Thank you for catching this, I should have converted the expected date string to localeDateString. Strangely, the CI didn't catch this earlier

/approve


Feature tileo/rebased raster flow issues

I merged it and put this on a test environment.  Back to @apercas for some testing since I couldn't make it work.


Bug fix: Return zero if there is no directed path from treatment to outcome

Added a check for directed path from treatment to outcome
If no such path exists, estimator is not called. Effect is zero by definition.

I just checked that this implementation fixes the previous bug.
However, should methods like CausalEstimate.get_standard_error handle the missing estimator or should this be handled downstream by the user?

Handling downstream by user should be fine for now. Since the standard error will tell the user "self.estimator not found", which is essentially the same exception we would raise if we handle it in get_standard_error.


Styled components breaking in page reload on vercel prod

What is Happening ?
A strange bug is happening when I acess my React SPA application, when running it on localhost, the components there are styled with SC works like a charm, but when building it and delivering it to vercel, when refreshing the page (or pressing f5) some specific componentes lose all of his styles, inputs and buttons to exact.
What I've tried

Disabling speedy mode (I'm using create-react-app so i tried putting it on my env in local AND the vercel env variables)
Changing webpack GENERATE_SOURCEMAP config
Renaming the global css file written with "createGlobalStyle" function
Downgrading Styled components version respectively to 5.3.0 and 5.2.3

None of the above worked
Expected Behavior
When refreshing the page regardless of the content on it, it should keep the styles on components such as buttons and inputs
Actual Behavior
The styles on buttons and inputs (specifically for some reason) are losing all styles and turning into plain html on page refresh
I can't really bring any code in this situation and is difficult to reproduce the bug since he only appears when pushing the app to production via Vercel, but I do can bring the version of the main tools
React - v18.0.1
Styled-components - v5.3.6
Radix primitives - v1.0.0 (Some of them are at 1.1.2, like radix-select)
Edit: We've noticed that most of the components breaking are inside of a radix modal, maybe there are incompatibilities ?
I would be thankfull of any help in this issue

@carlosdarwed if you're using nextjs 13 there is a known issue with the setup on their end when bundling for production. I'd recommend using nextjs 12 in the meantime and following their documentation for setting up styled-components when using the "pages" directory. You can see the setup in our sandbox project: https://github.com/styled-components/styled-components/blob/main/packages/sandbox/pages/_document.tsx


python3Packages: format with nixfmt

Description of changes
People have started reformatting individual packages with nixfmt, so a treewide change should get rid of that review churn.
Also, we're at an ideal point to sneak in a reformat, when we consider backports from master to release.
If this causes rebuilds, we'll need to identify those and postpone.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 313628 run on x86_64-linux 1

4 packages built:

python311Packages.waitress-django
python311Packages.waitress-django.dist
python312Packages.waitress-django
python312Packages.waitress-django.dist

The @NixOS/nix-formatting team wasn't planning on doing any large reformats just yet, because the formatter isn't stable yet, but it is indeed a good time for it.
The team will try to make a decision on this in time and merge it if ready.

:thinking:
diff --git a/pkgs/development/python-modules/waitress-django/default.nix b/pkgs/development/python-modules/waitress-django/default.nix
index fad82f4952ce..925f37df7487 100644
--- a/pkgs/development/python-modules/waitress-django/default.nix
+++ b/pkgs/development/python-modules/waitress-django/default.nix
@@ -1,4 +1,9 @@
-{ lib, buildPythonPackage, django, waitress }:
+{
+  lib,
+  buildPythonPackage,
+  django,
+  waitress,
+}:

 buildPythonPackage {
   pname = "waitress-django";
@@ -6,7 +11,10 @@ buildPythonPackage {
   format = "setuptools";

   src = ./.;
-  pythonPath = [ django waitress ];
+  pythonPath = [
+    django
+    waitress
+  ];
   doCheck = false;

   meta = with lib; {

The default.nix becomes part of the src = ./., which causes the package rebuild.
I don't think this is really worth fixing.

https://github.com/NixOS/nixpkgs/issues/301014

A concrete but minor problem is that because https://github.com/NixOS/nixfmt/pull/201 isn't merged yet (and more cases could exist), not all empty lines are preserved as the RFC specified. So formatting with the current version "loses" a bit of information

That kind of information loss doesn't sound too concerning to me. What I'm more concerned is, is the amount of churn. Have you seen the number of conflicting files? So the reformat is actually already happening.

For the record:
Changes like this should be scheduled in advance, especially during ZHF. Now, we have probably over a 100 merge conflicts in open PRs (not all ZHF-related, though) on your hands which could have been easily avoided.

@piegamesde In our team processes we document that non-trivial decisions need to be done by at least two team members, please honor that.
And indeed the RFC documents that formatting should happen before the branch-off, this wasn't honored either.
It's definitely not great to have this much churn though, I wasn't aware of this, I wish the formatting team was pinged more for that.

And indeed the RFC documents that formatting should happen before the branch-off, this wasn't honored either.

Why are you saying this wasn't honored? It was merged 4 minutes before the start of the branch-off meeting. I was even clearing it up with Weija on the call.

Ah sorry! I wasn't aware of that, and didn't properly check it myself (just compared the time of the branch-off announcement against the merge time of this PR).
I guess it doesn't make sense for this to be reverted at this point. Personally I don't have a lot of time to help with that now, I was expecting this to be done only at the next release.

The strategy to rebase conflicting changes is:

run nixfmt-rfc-style on your changes
git commit --amend
git rebase origin/master

Running the reformat first will reduce the chance for conflicts significantly.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/formatting-team-meeting-2024-05-28/46126/1


fix(ngMocks.findInstance): works without fixture #2311

closes #2311

v13.5.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


Feature/Move get_or_create logic into the QuerySet

This PR deprecates the get_or_create classmethod and advocates using the traditional django approach of objects.get_or_create instead.
The goal of this is to keep the Estimator, and DataSet logic focuses on the data model, and not the manager or queryset operations.
Additionally,

Fix a bug with a double save on the file.save()
Add support for objects.update_or_create(..)
Add support for objects.filter(..)
Add support for Estimator.objects methods to accept the estimator kwarg and compute and use the hash for retrieval
Add support for DataSet.objects methods to accept the data  kwarg and compute and use the hash for retrieval

Coverage increased (+0.7%) to 95.146% when pulling<PHONE_NUMBER>282a2d2f95d6a60e5bea9f5735d571 on feature/improve_tests into 1e1f10922b497f53f2bf34b2cc3d4f8d2cf09a96 on master.

Coverage increased (+0.7%) to 95.146% when pulling<PHONE_NUMBER>282a2d2f95d6a60e5bea9f5735d571 on feature/improve_tests into 1e1f10922b497f53f2bf34b2cc3d4f8d2cf09a96 on master.

Coverage increased (+1.2%) to 95.631% when pulling 38aed128179b3c326ac787de1e3adb484db470db on feature/improve_tests into 1e1f10922b497f53f2bf34b2cc3d4f8d2cf09a96 on master.

Coverage increased (+1.2%) to 95.631% when pulling b9fa56690bcda1c01aa0c3ec5604b98975743ee9 on feature/improve_tests into 1e1f10922b497f53f2bf34b2cc3d4f8d2cf09a96 on master.

Coverage increased (+1.2%) to 95.631% when pulling 1c1addc7e4e916d4b6a9b04bf40a8e8ac41668e0 on feature/improve_tests into 1e1f10922b497f53f2bf34b2cc3d4f8d2cf09a96 on master.

Coverage increased (+1.2%) to 95.631% when pulling 1c1addc7e4e916d4b6a9b04bf40a8e8ac41668e0 on feature/improve_tests into 1e1f10922b497f53f2bf34b2cc3d4f8d2cf09a96 on master.


react-native 0.64 build error

Issue Description
I upgraded to React-Native 0.64.0 from 0.63.4 and started getting this error on android when I run install debug, it was working before I upgraded.
> Task :react-native-camera-kit:compileDebugKotlin FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.7/userguide/command_line_interface.html#sec:command_line_warnings
414 actionable tasks: 414 executed
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
e: /Users/aprilmintacpineda/projects/my-app/node_modules/react-native-camera-kit/android/src/main/java/com/rncamerakit/RNCameraKitModule.kt: (36, 33): Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type UIManagerModule?

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-camera-kit:compileDebugKotlin'.
> Compilation error. See log for more details

I was able to build and run successfully on iOS.
Steps to Reproduce / Code Snippets / Screenshots
N/A

Environment

React Native Navigation version: N/A
React Native version: N/A
Platform(s) (iOS, Android, or both?): Android
Device info (Simulator/Device? OS version? Debug/Release?): Device, Debug and might also be Release

Hey @aprilmintacpineda, do you have Kotlin installed in your Android project? https://github.com/teslamotors/react-native-camera-kit/blob/master/docs/kotlin.md

Hi @aarongrider, yes, I've followed that, it used to work when I was using 0.63.4, I got that error when I upgraded to 0.64.0 following the diffs in the upgrade guide

/node_modules/react-native-camera-kit/android/src/main/java/com/rncamerakit/RNCameraKitModule.kt: (36, 33): Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type UIManagerModule?

FAILURE: Build failed with an exception.

That's an extra information to help you with debugging @aarongrider

I'm facing the same issue on<EMAIL_ADDRESS>

https://github.com/teslamotors/react-native-camera-kit/pull/385

@lBroth thanks! Seems not deployed yet though...

As a workaround you can install the package directly from this merge commit (3208896c569b2ab79db1e292129de47de5d2af99) like so in your package.json:
"react-native-camera-kit": "github:teslamotors/react-native-camera-kit#320889",
I can confirm this works with React Native 0.64 & 0.64.1. Although ideally, we'd see this released as a new version asap.

Refer to this docs: https://github.com/DibyajyotiMishra/react-native-camera-kit/blob/master/docs/kotlin.md
OR
This thread: https://github.com/teslamotors/react-native-camera-kit/issues/434


plotting tests to sorting_optimization branch

This is a quick fix for Spaghetti_plot and plot2D_cut will polish it today.


python3Packages.pytorch: 1.9.0 -> 1.10.2; python3Packages.torchvision: 0.11.2 -> 0.11.3

Motivation for this change
Noticed these were out of date.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Only new failure nixpkgs-review gave me on nixos x86_64:
builder for '/nix/store/mk59iysx4vikawl4jw1nk268jw0rl27v-python3.9-boxx-0.9.9.drv' failed with exit code 1; last 10 log lines:
      switch_backend(rcParams["backend"])
    File "/nix/store/rr9mlvqwjzfd88xfrpcwfvc3y8wqmzln-python3.9-matplotlib-3.5.1/lib/python3.9/site-packages/matplotlib/pyplot.py", line 275, in switch_backend
      raise ImportError(
  ImportError: Cannot load backend 'TkAgg' which requires the 'tk' interactive framework, as 'headless' is currently running

  ----------------------------------------------------------------------
  Ran 1 test in 0.000s

  FAILED (errors=1)

Though I note that prior to this, boxx is just failing to find any tests
----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK

On x86_64-linux I see:
running install tests
Matplotlib created a temporary config/cache directory at /build/matplotlib-sntfeqm6 because the default path (/homeless-shelter/.config/matplotlib) is not a writable directory; it is highly recommended to set the MPLCONFIGDIR environment variable to a writable directory, in particular to speed up the import of Matplotlib and to better support multiprocessing.

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK

Yes ditto, I just didn't include the that message in my paste

I was surprised because you said in https://github.com/NixOS/nixpkgs/pull/158185#issuecomment-1030894467 that with this update you see the tests erroring out. But I see tests are still not found even after this update.

Result of nixpkgs-review pr 158185 run on x86_64-darwin 1

27 packages marked as broken and skipped:

python39Packages.boxx
python39Packages.bpycv
python39Packages.einops
python39Packages.elegy
python39Packages.ignite
python39Packages.pyro-ppl
python39Packages.pytorch
python39Packages.pytorch-lightning
python39Packages.pytorch-metric-learning
python39Packages.pytorchWithoutCuda
python39Packages.pywick
python39Packages.qiskit
python39Packages.qiskit-machine-learning
python39Packages.rising
python39Packages.shap
python39Packages.skorch
python39Packages.slicer
python39Packages.spacy-transformers
python39Packages.stanza
python39Packages.tensorboardx
python39Packages.test-tube
python39Packages.torchgpipe
python39Packages.torchinfo
python39Packages.torchvision
python39Packages.treex
python39Packages.zcs
tts


Implement priors in prior transformation

Move priors to actual prior transformation function for dynesty sampling. will need to think harder about how to make this compatible with the MCMC based approach.

partially addressed in https://github.com/wbalmer/backtrack/commit/662095c20dc71bf39397408ad559b3f9ecb65d1f ,
unsure if this implementation of the Bailer-Jones prior is appropriate / the implementation itself is correct. Using the functional form in Nielsen 2017, e.g.
$p(\pi)=\pi^{-4} e^{-1/(\pi L)}$

but still unsure if the prior transform itself, lines
L_d = 1.35e3 # length scale value from astraatmadja+ 2016   L = (1/L_d)*1000   par = plx_pdf(par, L)
produce the proper prior space.

the transformation from unit cube to prior space requires the PPF (percent-point function) not the PDF 🤦 as I mistakenly read. The PPF is the inverse of the CDF of our PDF (lol)
$CDF = \Gamma(3, \frac{1}{\pi L} L^3$
$PPF = \Gamma^{-1}(3, \frac{\pi}{L^3})/L$
which is now implemented in backtrack.utils.py as
plx_ppf = lambda x,L : gammainccinv(3, (x/(L**3)))/L

using from scipy.special import gammainccinv
Since we have the factor of $L^3$ within the inverse gamma, we have to scale the unit cube from [0,1) to [0, $L^3$), which is $\sim0.40644$.

now implemented in d17cfb9

I had been following Nielsen et al 2017, but as @gotten mentions, I can't quite track down exactly how this is normalized or where the factors of $\pi$ are coming from. If we go back to the source, Bailer-Jones for DR2 and DR3 has an updated analytic prior expression (a Generalized Gamma Distribution) with a few more parameters, $\alpha$, $\beta$, and L. In particular, Bailer-Jones+ 21 gives
$$\frac{1}{\Gamma(\frac{\beta+1}{\alpha})}\frac{\alpha}{L^{\beta+1} r^\beta e^{-(r/L)^\alpha}$$
and for the EDSD (e.g. their DR2 prior) they give $\alpha=1$, $\beta=2$ whereas for eDR3 they fit for $(\alpha, \beta)$for each HEALpixel.
@gotten has already done a bit of the math to create the CDF and PPF out of this updated function, but we will also need to nearest neighbor the parameters, which for eDR3 can be found here. This might mean we downgrade our gaia call to DR2 or eDR3 to maintain consistency with the prior, while sacrificing a bit of precision? Since the typical uncertainty on our direct imaging astrometry is large comparatively, I think this is reasonable.
I will update soon, after breakfast.

so, for a PDF given by Eq 3 of Bailer-Jones+21, we have the CDF:
$$CDF(r) = \gamma(\frac{\beta+1}{\alpha}, (r/L)^\alpha)$$
and the PPF:
$$PPF(r) = L*\gamma^{-1}(\frac{\beta+1}{\alpha}, r)^{1/\alpha} $$
which we can call from scipy.special import gammaincinv
and when given $\alpha=1$, $\beta=2, L=1.35e3$ and cast into units of mas looks like:

this is now implemented as a prior transform function in backtrack.utils.py
def transform_gengamm(x, L=1.35e3, alpha=1, beta=2):
    return L*(gammaincinv((beta+1)/alpha,x)**(1/alpha))

as of 854ad13.
next commit will include the query of Bailer-Jones+21 healpix table of fit alphas, betas, and Ls for a given target.

commit 9f8d3c0 now includes a query of the fit alpha, beta, and L parameter for a given gaia source_id. tested on HD 131399 Ab, which produced reasonable results. closing this issue for now.


Hide Artifacts: Email Hiding Rules

Hide Artifacts: Email Hiding Rules
https://attack.mitre.org/techniques/T1564/008/

Probably the TTP could be simulated as following:
$olFolders = "Microsoft.Office.Interop.Outlool.OlDefaultFolders" -as [type]
$olRuleType = "Microsoft.Office.Interop.Outlook.OlRuleType" -as [type]
$outlook = New-Object -ComObject outlook.application
$namespace = $Outlook.GetNameSpace("mapi")

#Rule name
$rules = $outlook.session.DefaultStore.GetRules()
$rule = $rules.Create("T1564.008", $olRuleType::OlRuleReceive)

#process emails comes from specific address.
$FromCondition = $rule.Conditions.From
$FromCondition.Enabled = $true
$FromCondition.Recipients.Add("<EMAIL_TEST>")
$FromCondition.Recipients.ResolveAll()

#Apply condition on specific keywords in Subject
$SubjectCondition = $Rule.Conditions.Subject
$SubjectCondition.Enabled = $true
$SubjectCondition.Text = @('malware','suspicious','phish','hack','hacked')

#Action to be done (delete email)
$ForwardRuleAction = $Rule.Actions.Delete
$ForwardRuleAction.Enabled = $true

#Save the rule
$rules.Save()

To be executed in powershell


Add back option to have small 3-d axis in corner

@PennyQ - you worked on this in https://github.com/vispy/vispy/pull/1125, so shall I assign this to you here? This should go in common/vispy_widget.py and with an option similar to the one to turn on/off the coordinate grid in common/viewer_options.py.

@astrofrog Ok, I already had one available for the dev Vispy. So we will wait for the new release of Vispy or just implement it?

@PennyQ - ah, does the code require changes available in dev vispy? If so, it's fine to wait for a new release.

@astrofrog I tested the code (put here for convenience https://raw.githubusercontent.com/PennyQ/vispy/f3fa22dc87bc2d5c34d1b19c0180bb78781632a4/examples/basics/scene/volume.py) and I found the axis works well for my current version of Vispy (old one) now, so maybe we could implement it into Glue? I could do that if you like :)

@PennyQ - that would be great!

See https://github.com/glue-viz/glue-3d-viewer/pull/91


Trigger staging bundle release for 0.19.4

Issue #, if available:
Description of changes:
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/lgtm

/approve


What is DevOps, Kubernetes and Docker ?

Research what DevOps, Kubernetes and Docker are, and then install Kubesphere on your own local machine and verify that it works.

I researched what DevOps, Kubernetes and Docker are and confirmed that Kubesphere was installed and running on the host machine.


Battery Control for SOLAX Hybrid G4

Hi,
The new feature Battery control is a very good feature.
For solax inverters, the only parameter that can be changed is the battery output A power that can be limited.
Is it possible during fast charging or smart grid to limit the output power of the battery and return it normally to the end of charging or back to a normal mode?
This parameter can be modified with a value defined in the configuration for example? (and not updated all the time, because according to the returns the eprom has a predetermined maximum write capacity)
Thanks

Yes please provide all technical details like Modbus registers, documentation, command flow examples, ...

Command flow is just when charging at full speed or smart grid (full speed too).
Change battery_discharge_max_current to 5 or 10A (it's better if i can change it in yaml for exemple)
Charge at fast mode
When stop charging (vehicle disconnected or fully charged) or mode change the battery_discharge_max_current is restored (can be a setting in yaml too)
For modbus register :
https://gbc-solino.cz/wp-content/uploads/2022/07/Hybrid-X1X3-G4-ModbusTCPRTU-V3.21-English_0622-public-version.pdf
It's 0x0091 "Battery_DischargeMaxCurrent", recommended 25 A and can be 0 to 30A
Say if you need more information.

Looks these two registers may fit the requirements:

First is the inverter mode for backup or other. (So no)
The second is for force charge the battery with the grid.
So I don't think this is useful for discharge control of the battery.

Please no guessing. Did you try it?
Switching to backup mode should stop discharging the battery.

I'm not guessing for backup and self use mode, I'm always on backup mode.
Backup mode just keeps a minimum soc more important (can be set) of the battery and when no solar power, inverter keep eps active, in self use mode if battery is at or less min soc (and no solar power ) the inverter is on standby and don't backup if grid lost.
So if you are in manual mode with no force charge and discharge, the inverter go to standby (I think because no backup mode) and don't go to eps mode when grid is lost.

Ok I have re read and i don't know why I think this.
(Or it's another setting like hot standby setting)

Can someone confirm https://github.com/evcc-io/evcc/issues/11227#issuecomment-1868543284?

Bitte mal testen

@andig getting an decoding error on starting, please have a look.
I did not change anything in the config. It does not work since the last update:
FATAL 2024/01/01 13:59:27 cannot create meter 'battery': cannot create meter 'template': cannot create meter 'custom': battery mode: 1 error(s) decoding:

error decoding 'Timeout': time: invalid duration ""

meters:
...
- type: template
  template: solax
  id: 1
  device: /dev/ttyUSB0
  baudrate: 19200
  comset: 8N1
  usage: battery
  modbus: rs485serial
  name: battery

I have tested the battery control activation and i have a error  in EVCC :
Request failed with status code 400: API request failed http://XXXXXXXXX:7070/api/batterydischargecontrol/true
And in network tab, the response is :
{"error":"modbus: exception '4' (server device failure), function '6'"}

@ioniks could you please tun
evcc meter --log error,modbus:trace --battery-mode hold --battery-mode-wait 30s
Thanks!

On 4. Jan 2024, at 11:56, ioniks @.***> wrote:
I have tested the battery control activation and i have a error in EVCC :
Request failed with status code 400: API request failed http://XXXXXXXXX:7070/api/batterydischargecontrol/true
And in network tab, the response is :
{"error":"modbus: exception '4' (server device failure), function '6'"}
—
Reply to this email directly, view it on GitHub https://github.com/evcc-io/evcc/issues/11227#issuecomment-1876899849, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABND365WLPGBGEOT4Z5WFTYM2DG3AVCNFSM6AAAAABBBNE6TGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWHA4TSOBUHE.
You are receiving this because you were mentioned.

@andig  is there interessed for other users with Solax Hybrid WR´s?  could you need more informations?

@andig
Can i set this mode in Yaml ? (i have docker version of evcc)

It's unclear to me if Solax works. If not we'll need an issue with relevant details.

@andig
I have set in yaml
log: debug
levels:
  modbus: trace

This is the log when i set the battery control to On, same API error and nothing in log for modbus
[lp-1  ] DEBUG 2024/01/04 12:28:34 charge power: 0W
[site  ] DEBUG 2024/01/04 12:28:34 pv power: 2108W
[site  ] DEBUG 2024/01/04 12:28:35 battery soc: 46%
[site  ] DEBUG 2024/01/04 12:28:35 battery power: -1560W
[site  ] DEBUG 2024/01/04 12:28:35 grid power: -0W
[site  ] DEBUG 2024/01/04 12:28:35 battery has priority at soc 46% (< 95%)
[site  ] DEBUG 2024/01/04 12:28:35 site power: 150W
[lp-1  ] DEBUG 2024/01/04 12:28:35 charge total import: 3428.009kWh
[lp-1  ] DEBUG 2024/01/04 12:28:35 charger status: A
[site  ] DEBUG 2024/01/04 12:28:44 set battery discharge control: true
[site  ] DEBUG 2024/01/04 12:28:49 ----
[lp-1  ] DEBUG 2024/01/04 12:28:49 charge power: 0W
[site  ] DEBUG 2024/01/04 12:28:50 pv power: 2008W
[site  ] DEBUG 2024/01/04 12:28:50 battery soc: 46%
[site  ] DEBUG 2024/01/04 12:28:50 battery power: -1438W
[site  ] DEBUG 2024/01/04 12:28:50 grid power: -0W
[site  ] DEBUG 2024/01/04 12:28:50 battery has priority at soc 46% (< 95%)
[site  ] DEBUG 2024/01/04 12:28:50 site power: 150W
[lp-1  ] DEBUG 2024/01/04 12:28:50 charge total import: 3428.009kWh
[lp-1  ] DEBUG 2024/01/04 12:28:50 charger status: A
[site  ] DEBUG 2024/01/04 12:29:04 ----

Run on command line:
evcc meter --log error,modbus:trace --battery-mode hold --battery-mode-wait 30s

evcc meter --log error,modbus:trace --battery-mode hold --battery-mode-wait 30s
[main  ] INFO 2024/01/04 13:09:25 evcc 0.123.5
[main  ] INFO 2024/01/04 13:09:25 using config file: /etc/evcc.yaml
[modbus] TRACE 2024/01/04 13:10:55 modbus: send 00 01 00 00 00 06 01 06 00 1f 00 02
[modbus] TRACE 2024/01/04 13:10:57 modbus: recv 00 01 00 00 00 03 01 86 04
[main  ] FATAL 2024/01/04 13:10:57 set battery mode: modbus: exception '4' (server device failure), function '6'

In Home Assistant when i set Manual mode (with solax modbus plugin) it revert to Backup mode (my previous mode), and when i set it in Solax app, it works (but when it's set Stop charge and discharge, it continue charging ...)

In Home Assistant when i set Manual mode (with solax modbus plugin) it revert to Backup mode (my previous mode), and when i set it in Solax app, it works (but when it's set Stop charge and discharge, it continue charging ...)

I have no idea what that means. Zero.
That said: if anyone has a problem with Solax please open new issue with required information.

evcc meter --log error,modbus:trace --battery-mode hold --battery-mode-wait 30s
[main  ] INFO 2024/01/04 12:14:22 evcc 0.123.5
[main  ] INFO 2024/01/04 12:14:22 using config file: /etc/evcc.yaml
[modbus] TRACE 2024/01/04 12:15:22 modbus: send 00 01 00 00 00 06 01 06 00 1f 00 02
[main  ] FATAL 2024/01/04 12:15:22 set battery mode: read tcp <IP_ADDRESS>:35484-><IP_ADDRESS>:502: read: connection reset by peer

ich setze mal die Ausgabe aus meinem system ein..

TCP Connection weg- ob/was das mit einem potentiellen Modbusproblem zu tun hat ist unklar.


add cterm support

this will set ctermfg as well to support terminal vim that doesn't support guifg

could you rebase ?

Since I'm not an advanced git user, is what I did is what I should do?

run git rebase master from your branch, fix the conflicts, then git add . && git rebase --continue, then git push -f

Thanks!

still conflicts sorry i merged the mint PR before :/

sure! the problem is now resolved
sorry for the late response :(

thanks :)


updated source code

this fork is like 30 commits behind

@BemboLikePizza erm... pull?

@BemboLikePizza  pull this please!!!!!!!!!!!!!!!!!!!!!!!!!

i forgot to explain why i wanted you to pull this so bad but for some reason every single vsdave fork defaulted to be a fork of your fork because the original repo was privated for 3.5

what
El jue, 26 de ene. de 2023 12:59 p. m., Mayo78 @.***>
escribió:

@BemboLikePizza https://github.com/BemboLikePizza erm... pull?
—
Reply to this email directly, view it on GitHub
https://github.com/BemboLikePizza/VsDave/pull/1#issuecomment-1405226791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVLFYAHTLNIDHG4BQSNFZZDWUKNNZANCNFSM6AAAAAAUGNSGPM
.
You are receiving this because you were mentioned.Message ID:
@.***>

this repository of code, which was a fork of the dave and bambi repository, was made into a normal repository instead of a fork because the original dave and bambi repository from moldygh was privatized for the next dave and bambi update, and every previous fork of the original dave and bambi was made into a fork of this repository

Interesting.
El lun, 6 feb 2023 a la(s) 21:26, Mayo78 @.***)
escribió:

this repository of code, which was a fork of the dave and bambi
repository, was made into a normal repository instead of a fork because the
original dave and bambi repository from moldygh was privatized for the next
dave and bambi update, and every previous fork of the original dave and
bambi was made into a fork of this repository
—
Reply to this email directly, view it on GitHub
https://github.com/BemboLikePizza/VsDave/pull/1#issuecomment-1419985585,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVLFYAD635F3GJIIK2MHBCLWWGJCXANCNFSM6AAAAAAUGNSGPM
.
You are receiving this because you were mentioned.Message ID:
@.***>

wym about pull
El jue, 26 ene 2023 a la(s) 12:59, Mayo78 @.***)
escribió:

@BemboLikePizza https://github.com/BemboLikePizza erm... pull?
—
Reply to this email directly, view it on GitHub
https://github.com/BemboLikePizza/VsDave/pull/1#issuecomment-1405226791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVLFYAHTLNIDHG4BQSNFZZDWUKNNZANCNFSM6AAAAAAUGNSGPM
.
You are receiving this because you were mentioned.Message ID:
@.***>


[BUG] in LibffmConverter docstrings

Description

fix https://github.com/microsoft/recommenders/issues/1577
Related Issues

Checklist:

[ ] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[ ] I have updated the documentation accordingly.
[ ] This PR is being made to staging branch and not to main branch.

Codecov Report

Merging #1589 (9cf8d82) into staging (7013f0d) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           staging    #1589      +/-   ##
===========================================
+ Coverage    61.88%   61.90%   +0.01%
===========================================
  Files           84       84
  Lines         8458     8462       +4
===========================================
+ Hits          5234     5238       +4
  Misses        3224     3224

Flag
Coverage Δ

pr-gate
61.90% <100.00%> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

recommenders/datasets/pandas_df_utils.py
94.89% <ø> (ø)

recommenders/models/rbm/rbm.py
73.66% <100.00%> (+0.47%)
:arrow_up:

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 45195d3...9cf8d82. Read the comment docs.

FYI @anargyri


protobuf/coreapi: lowercase sid in JSON encoding

Is there any good reason for that change ?

Is there any good reason for that change ?

Yes, if we don't lowercase the SID in json encoding, it'll stay as uppercase where all the other fields are lowercased which is not convenient. Also there is no reason to keep SID uppercase in json format, we may also have it as sID since it consists of two words but it kinda doesn't look good.

Hum I guess you are talking about the display in the detail command. That's the only place I see we use json. In that case I might be ok but I don't want to introduce a special flag.
If it's for consistency which is great it has to be consistent on the api level and this implies some other modifications and so maybe a lot of modifications for a small problem

@mesg-foundation/core
We need to have both lowercase and first letter uppercase style.
For now, both are SID and that's weird.
I suggest to go with "sid" everywhere and "Sid" in go struct when sid need to be public.

I'm ok to have everything lowercase but it's weird to have in the api SID with json name sid.
I would simply do:
string sid = 12


Trigger event when you append to a blob.

Is it possible to trigger an event when you append to a blob? I only see the event "eventType": "Microsoft.Storage.BlobCreated". This event does not seem to trigger when I append to a blob.
/Andreas

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b250ca39-0ba3-20dc-179b-c5a0d80fba9f
Version Independent ID: 5f1d000e-c731-4b98-8eb7-55836829ca47
Content: Send Blob storage events to web endpoint - portal
Content Source: articles/event-grid/blob-event-quickstart-portal.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

Hi @Tottmar - Thank you for your question. Presently, there isn't such a trigger on the "Blob Update" event. Please review this thread where the Event Grid team has weighed on this scenario recently and consider upvoting an existing feature request on Azure UserVoice.

@Tottmar We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


My bug report

Steps to reproduce
Run the attached script.
It uses the disk serial number obtained using Get-Disk or Get-PhysicalDisk and tries to use the output to obtain the disks that match the serial number using Get-Disk or Get-PhysicalDisk
This does not work as the output from Get-Disk contains leading spaces which are not present using Get-PhysicalDisk
E,g.
Disk Number: [1] Serial:[            S1E35PF2] (Using Get-Disk)
Disk Number: [1] Serial:[S1E35PF2] (Using Get-PhysicalDisk

Expected behavior
Using the output from either method should be usable in the other to obtain the appropriate disk output.
See the TXT file in the zip and how the output differs and is confusing
I think the documentation may also need addressing as it seems to differ from reality if I am looking at the correct page see the online version link shown using "get-help Get-PhysicalDisk"

# Actual behavior
The request to find disks with a particular serial number using the output from either sometimes returns an error and other times the result is empty.

Using Get-Disk:
`Disk Number: [1] Serial :[            S1E35PF2] (From Get-Disk using Get-Disk)
Disk Number: [1] Serial :[] (From Get-Disk using Get-PhysicalDisk)`

Using Get-PhysicalDisk:
Get-Disk: S:\Test\GetDiskExample.ps1:27
Line |
  27 |  … ng Get-Disk)' -f $item, (Get-Disk -SerialNumber $SerialNumber).Serial …
     |                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | No MSFT_Disk objects found with property 'SerialNumber' equal to 'S1E35PF2'.  Verify the value of the
     | property and retry.

Disk Number: [1] Serial :[] (From Get-PhysicalDisk using Get-Disk)
Disk Number: [1] Serial :[S1E35PF2] (From Get-PhysicalDisk using Get-PhysicalDisk)

Both methods should work in the same way and the "Number" property should be available using Get-PhysicalDisk

Environment data

Name                           Value

PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
GetDiskExample.zip

These cmdlets is not in the repository. Please use Windows 10 Feedback tool or UserVoice site.