Add double parentheses and braces variants

This small PR adds paren.l.double, paren.r.double, brace.l.double and brace.r.double.
I did not add double variants for shell because there are two of them, and I'm unsure which one to choose:

U+27EC ⟬ MATHEMATICAL LEFT WHITE TORTOISE SHELL BRACKET and U+27ED ⟭ MATHEMATICAL RIGHT WHITE TORTOISE SHELL BRACKET, from Miscellaneous Mathematical Symbols-A, or
U+3018 〘 LEFT WHITE TORTOISE SHELL BRACKET and U+3019 〙 RIGHT WHITE TORTOISE SHELL BRACKET, from CJK Symbols and Punctuation.

Note that Unicode also defines two main regular tortoise shell variants (shell currently uses the second one):

U+2772 ❲ LIGHT LEFT TORTOISE SHELL BRACKET ORNAMENT and U+2773 ❳ LIGHT RIGHT TORTOISE SHELL BRACKET ORNAMENT in the "Dingbats" block, and
U+3014 〔 LEFT TORTOISE SHELL BRACKET and U+3015 〕 RIGHT TORTOISE SHELL BRACKET in the "CJK Symbols and Punctuation" block.

I think we should use the codepoints from Miscellaneous Mathematical Symbols-A and Dingbats rather than CJK symbols (meaning we should also change shell.l and shell.r) because they seem to be more appropriate for use as math symbols.
As a comparison, here is how those characters render in the webapp (the first line is text mode, and the other two lines are in math mode):

Source code
#set align(center)

#let tortoise = symbol(
  ("dingbats.l", "❲"),
  ("dingbats.r", "❳"),
  ("math.l.double", "⟬"),
  ("math.r.double", "⟭"),
  ("cjk.l", "〔"),
  ("cjk.r", "〕"),
  ("cjk.l.double", "〘"),
  ("cjk.r.double", "〙"),
)

#tortoise.dingbats.l
Dingbats
#tortoise.dingbats.r
and
#tortoise.cjk.l
CJK
#tortoise.cjk.r

$
  tortoise.dingbats.l
  "Dingbats"
  tortoise.dingbats.r
  +
  tortoise.cjk.l
  "CJK"
  tortoise.cjk.r
$

$
  tortoise.math.l.double
  "Mathematical"
  tortoise.math.r.double
  +
  tortoise.cjk.l.double
  "CJK"
  tortoise.cjk.r.double
$

A good reference here is the symbol list for LaTeX
http://mirrors.ctan.org/macros/unicodetex/latex/unicode-math/unimath-symbols.pdf

Thanks! This list uses dingbats codepoints for regular shells, and mathematical codepoints for double shells. I'll update shell and add variants accordingly.


About the training method of the training model you provided and the training dataset

Hi, thank you for your job. I test the trained model you provided but the result did not look very good. In which way was the model you provided to train?
（1）Train without annotated data
（2）Train with annotated data
And how large is the training dataset used by your model?
Looking forward for your answer.
Thank you.

4 years later and still no answer


failed to lock apt

I'm trying to use this role in my playbook. I'm getting a failure with apt. Do I need to be using sudo:yes at the playbook level? Thanks!
TASK: [angstwad.docker_ubuntu | Install (or update) docker package] ***********
<x.x.x.x> REMOTE_MODULE apt name=lxc-docker state=present
<x.x.x.x> REMOTE_MODULE apt name=lxc-docker state=present
failed: [x.x.x.x] => {"failed": true}
msg: Failed to lock apt for exclusive operation
failed: [x.x.x.x] => {"failed": true}
msg: Failed to lock apt for exclusive operation

FATAL: all hosts have already failed -- aborting

Yes, you'll need to escalate privileges to root using become, sudo, or su.

Thanks @angstwad. Wasn't sure how to do that on a role include, but learned you can do
  roles:
    - { role: angstwad.docker_ubuntu, sudo: yes}

Thanks for the awesome role!


issue - 680 add if execute

add if execute around warnings in macros/cross_db_utils/deprecated/xdb_deprecation_warning.sql
This is my first contribution so if anything is missing please lmk
resolves #
ISSUE- 680
This is a:

[ ] documentation update
[ x ] bug fix with no breaking changes
[ ] new functionality
[ ] a breaking change

All pull requests from community contributors should target the main branch (default).
Description & motivation
Making these changes to not get unnecessary warnings
Checklist

[  x ] This code is associated with an Issue which has been triaged and accepted for development.
[   ] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[ ] Postgres
[ ] Redshift
[ ] Snowflake
This change is unrelated to the warehouse being used so we should be good.

[ x ] I followed guidelines to ensure that my changes will work on "non-core" adapters by:

[ ] dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
[ ] using the limit_zero() macro in place of the literal string: limit 0
[ ] using dbt.type_* macros instead of explicit datatypes (e.g. dbt.type_timestamp() instead of TIMESTAMP

[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[ ] I have added an entry to CHANGELOG.md

@pratikchavandev did you approach not end up working to fix the deprecation warning?


When it's not a player's turn, they cannot move any pieces.

5fe7ab1
restricted the movement of pieces by the non-operating player


Hiding Slicer Header Title

Screenshot

Description
I am not able to hide the chart-title on the slicer using CSS. I would like to do this since the chart-label is there and it would be repetitive to have both

We are not likely to further invest in FilterBox as Dashboard native filter is available(behind a feature flag), and this is not an issue in native filter :) @JosephTheuri

Thanks for this, very helpful

Perhaps then we should have the native filter available by default....


Add tests on Python 3.11

This also re-enables tests on Python 3.8 and Python 3.9

This depends on https://github.com/tensorflow/tensorflow/issues/58032 being fixed

Tensorflow 2.12.0 has wheels for Python 3.11. This is now dependent on fixing https://github.com/brainglobe/cellfinder-core/issues/103 first

Closing this due to restructuring. Issue is tracked in https://github.com/brainglobe/cellfinder-core/issues/230 and will be transferred to https://github.com/brainglobe/cellfinder


[branch-2.9][broker] Full-support set ssl provider, ciphers and protocols

Motivation
Cherry https://github.com/apache/pulsar/pull/14569 to 2.9
Documentation

[x] no-need-doc

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks


Pointing setup.py to the new repo

LGTM

LGTM.
Sorry about this. I tested with pip install but I guess there was something wrong with my environment that made it work.


Gallery images in lighbox too small

Guys, any reason for lightbox gallery images in "New World" theme to be so small on mobile, they are like tiny...
I've uploaded several images 1920x1080 and 1080x1350 which are normal on desktop resolutions but tiny on mobile.
How can I increase the size?

You are talking about the MW.gallery right?
I have noticed the same using that.
I changed my template to use an alternative JQuery gallery where I could customize the size.

Exactly! Could you share or tell me how to change to achieve that please?

I'm using Magnific Popup as a plugin in my template.
Download it, put it in your template and add the following to the following files:
header.php
  <link rel="stylesheet" type="text/css" href="<?php print template_url(); ?>assets/plugins/magnific-popup/magnific-popup.css" />

footer.php

Now you have to change the templates of your picture module to use this instead of the mw.gallery
# Some code precedes this

 # Make sure to add the class js-popup-gallery on a container of the links to the images
      <?php $count = 0;
      foreach ($data as $item): ?> # this code will loop through your images and execute the following for each image:
          <a href="<?php print thumbnail($item['filename'], 1200); ?>" class="pictures picture-<?php print $item['id'];?>"> # Link to the large image
            <img src="<?php print thumbnail($item['filename'], 920); ?>" class="d-block" alt="<?php print $item['image_options']['title']; ?>"> # the smaller image that gets shown on the page (not the gallery)

       <?php endif; ?>

Thanks @RogerAntonio, it's not working for me on "New World" theme which already has magnific popup files in theme assets and that got me confused.
I simply don't have time to pursue this, if you're interested in paid customization please send me a message..

Thanks @RogerAntonio, it's not working for me on "New World" theme which already has magnific popup files in theme assets and that got me confused.
I simply don't have time to pursue this, if you're interested in paid customization please send me a message..
Unfortunatly, I don't really mess with other themes. I have spent a lot of time on my own theme which I'm providing to my customers as a template option, it will keep updating with new layouts and options over time.
My own website was built with it. English translation is in progress so it's only in Dutch right now.


Editorial issues cont'd

Breaking out remaining issues from #245

Line no
Type
Suggestion

84
Clarification
DID (and VC definitions) do not link to w3c specs. This is likely intentional but could be confusing as the audience will have a mix of understanding of the specs / context. Should we refer to the specs as informative? Do we need to clarify definitions are broader?

137, 187
Clarification
"Presentation Definitions are objects that articulate what proofs a Verifier requires." > "...what ^claims/credentials^ and proofs"

Recommendation from previous WG call (line 84)

agreed, plus consider case-by-case where/how things are used
search "ref:" for ease of finding

closed #332


Did changes in validation.py

Closes:#1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

tried changing validation again


Start-PodeStaticServer failing

Describe the Bug
Start-PodeStaticServer is failing to start without being given parameters. It is not using a default set. Setting
[CmdletBinding(DefaultParameterSetName)]

In the function makes powershell fall back to unassigned.
Looking through the code I was unable to determine the intended design of the HTTPS parameter set:
        [Parameter(ParameterSetName='Https')]
        [string]
        $Certificate = $null,

        [Parameter(ParameterSetName='Https')]
        [string]
        $CertificatePassword = $null,

        [Parameter(ParameterSetName='Https')]
        [Parameter()]
        [X509Certificate]
        $X509Certificate = $null,

They default to $null, but then that would fail. It seems like it should default to  -selfsigned when no parameters are specified for https.
if ($Https) {
            if ($null -eq $X509Certificate) {
                Add-PodeEndpoint -Address $Address -Port $Port -Protocol Https -Certificate $Certificate -CertificatePassword $CertificatePassword
            }
            else {
                Add-PodeEndpoint -Address $Address -Port $Port -Protocol Https -X509Certificate $X509Certificate
            }
        }

Ha! It's actually because $CertificateKey has a completely wrong ParameterSetName 😂 (should be Https as well)
To be honest, the whole parameter set could go, doesn't look like it's really needed. And I like the idea of if just -Https is defined it defaults to -SelfSigned.

Removed the parameter set completely, and now if no certificate details are supplied with -Https it defaults to -SelfSigned.


Enhance error message info to be more actionable  when flow fails at any stage

**Is your feature request related to a problem? Understanding of log message in OpenLane log
I am running one of sample design in openlane. Its got failed at routing stage. But there is no clear information why its stopped. Same project i ran using OpenRoad flow scripts its failed and gave info as default placement density is .55 and expected PL_DENSITY is 0.6. or modify core area.
Describe the solution you'd like
If project fails means display Error number and possible workaround to fix this issue. Like above increase core area or placement density value.
 This image captured from OpenRoad flow command log.
 This logs captured from OpenLane flow.
Both run failed due to placement density and core area. But error info was clear in OpenRoad scripts, not in OpenLane flow scripts. So if you had this enhancement in OLFS its helpful to user to understand the root cause quickly.

These two appear to be two distinct failures in two different parts of the flow. I don’t see what’s actionable here.

@donn
I start my design with OpenLane and tool calculating core size on its own based on number of cells. OL calculated  core size is 0 0 940 950. But its failed with below message
Error 0: order_wires failed
Notice 0: error, net 26404, shorts to another term
Notice 0: wire point<PHONE_NUMBER>00)
Notice 0: clknet_leaf_256_wb_clk_i
Refer my previous issue #497
So from OpenLane I got core area, used this value in OpenRoad flow its stopped with Error message and suggesting to re-floorplan or increase PL density.
Again I re-floorplan with  0 0 960 980 I able generate GDSII. Even OpenLane has able to pass this Error 0: order_wires failed, and GDSII file got generated.
So from above OpenLane Error message order_wires failed no where pointing to re-floorplan our design. But openroad does pointing to use re-floorplan.
So this is what my suggestion to do an enhancement in the Openlane scripts to print such user understandable error info.
As I did comparison with both flow I got this information. If people using only OpenLane will post GitHub issue for everything.

LVS reports:
net count difference = 0
device count difference = 0
unmatched nets = 0
unmatched devices = 0
unmatched pins = 29
property failures = 0
Total errors = 29


Prefer importlib.metadata over pkg_resources if available

Let's not use pkg_resources and avoid a DeprecationWarning if importlib.metadata is available.
Fixes https://github.com/getsentry/sentry-python/issues/2048

If distributions() yields the same stuff as pkg_resources.working_set this looks good and can be merged.

@antonpirker It does with one difference: distributions() keeps the capitalization, working_set makes everything lowercase, e.g.:
# distributions()
MarkupSafe 2.1.2
matplotlib-inline 0.1.6
mock 5.0.2
packaging 23.1
parso 0.8.3
pexpect 4.8.0
pickleshare 0.7.5
pip 23.1.2
platformdirs 3.5.0
pluggy 0.13.1
prompt-toolkit 3.0.38
ptyprocess 0.7.0
pure-eval 0.2.2
py 1.11.0
Pygments 2.15.1

# working_set
markupsafe 2.1.2
matplotlib-inline 0.1.6
mock 5.0.2
packaging 23.1
parso 0.8.3
pexpect 4.8.0
pickleshare 0.7.5
pip 23.1.2
platformdirs 3.5.0
pluggy 0.13.1
prompt-toolkit 3.0.38
ptyprocess 0.7.0
pure-eval 0.2.2
py 1.11.0
pygments 2.15.1

Do you see this creating issues anywhere? I grepped for where we actually use the modules and it seems like we attach them to the event and check them here but elsewhere we seem to be using sys.modules instead.

@sentrivana could you please add a test for testing _generate_installed_modules?

@antonpirker Changed the PR a bit and added a test, could you please skim over to see if it still looks ok to you?


factor_returns should shift returns by one day

The format in alphalens is: signal_t <> return_(t+T). In words, the signal on day t is linked to the returns of that asset on day t+T (e.g. 1). factor_returns computes the return series of that signal by multiplying signal_t * return_(t+T) and giving that timestamp t. However, I'm arguing it should be timestamp t+T because only then is the return actually realized.

I understand your point but I don't believe it's a bug, I would call it  is a convention: the returns are reported at the timestamp at which the transaction happens (when the factor is traded, and new long or short positions are entered). To know when the return is actually realized we have to add to this timestamp the timedelta corresponding to the period for which the returns are computed for (1 hour, 1 day etc.) The function that computes the cumulative returns behaves consistently with this convention, It doesn't seem to be buggy.
Of course we can change this convention is we like, but I believe this decision has a historical reason. The main Alphalens use case is to analyze factors computed at market open and the daily returns are better shown on the same day the factor is traded because the returns accumulate during the trading day. Reporting the returns the following day, when the returns are actually realized would seem strange. If the common scenario was to analyze factors computed just before market close, I believe a different convention would have been chosen.

I see what you're saying but I don't think that convention makes sense. Why would that be the way to think about factor returns? I suppose the question is where this is used but do you agree that for generating pyfolio returns it should definitely be shifted?

Ah right, the problem is passing the factor returns to pyfolio. I understand there are special cases (analysis of a daily factor computed at market open and 1 day period) where you would like to pass the factor returns to pyfolio untouched but in Alphalens there is some computation  happening on factor returns to make them suitable for pyfolio.
Since the factor returns properties can vary  (period length, frequency, overlapping or not, time at which they are computed) and since pyfolio wants daily returns only, Alphalens computes the following transformation:

computes the cumulative returns from the factor returns
resamples the cumulative returns at 1 day frequency
finally computes daily returns from 1 day  cumulative returns, which can be safely passed to pyfolio.

So you can call performance.create_pyfolio_input which does all that for you or:
# compute cumulative returns
cumrets = perf.cumulative_returns(factor_returns[period], period)
# resample at 1 day frequency
cumrets = cumrets.resample('1D').last().dropna()
# cumulative to daily returns
returns = cumrets.pct_change().fillna(0)

Bottom line, if you still want to change the convention I am fine with that (it might be more intuitive) but I don't believe is a good idea to pass factor returns directly to pyfolio since Alphalens can take care of the details required to adapt them.

The more I think about this the more I believe you are right, the current convention is really counter-intuitive: factor returns should use the timestamp at which they are realized. Still I don't believe there are bugs (at least not obvious ones) as the code seems to handle the factor returns correctly.
I'll have a look if I can fix the factor returns timestamps without breaking the code :)

@twiecki I had a look at the code and it's not that easy to change the behavior of factor_returns. What about adding an argument to performance.factor_returns like this:
realized_ts: bool, optional
   By default the returns use the timestamps of the factor values for which they are computed for.
   If `realized_ts` is True the returns will use the timestamps at which the returns are actually realized
   (Suggestions for a better description  are welcome :) )

What makes it not easy to change? The rest of the code-base relying on this way of setting the dt?

Yes. Throughout Alphalens code the returns are aligned to the factor index, exactly as it happens with the forward returns in factor_data:
           -------------------------------------------------------------------
                      |       | 1D  | 5D  | 10D  |factor|group|factor_quantile
           -------------------------------------------------------------------
               date   | asset |     |     |      |      |     |
           -------------------------------------------------------------------
                      | AAPL  | 0.09|-0.01|-0.079|  0.5 |  G1 |      3
                      --------------------------------------------------------
                      | BA    | 0.02| 0.06| 0.020| -1.1 |  G2 |      5
                      --------------------------------------------------------
           2014-01-01 | CMG   | 0.03| 0.09| 0.036|  1.7 |  G2 |      1
                      --------------------------------------------------------
                      | DAL   |-0.02|-0.06|-0.029| -0.1 |  G3 |      5
                      --------------------------------------------------------
                      | LULU  |-0.03| 0.05|-0.009|  2.7 |  G1 |      2
                      --------------------------------------------------------
    """

Isn't there a difference between forward-returns (which need to be tied to the signal dt) and factor returns (which we plan to change to tie to the return dt)? Or does factor_returns get used in other parts there as well?

The latter, factor_returns does  get used in other parts of the code.

I see. Yes, then we should probably add a kwarg realized_ts.

@twiecki I had a look at the code in detail and I realized it is not even possible to add the realized_ts flag.  perf.factor_returns function computes the returns for all periods in factor_data and, since each period has a different realized time for the same factor time, it would not be possible to store the factor returns for all periods in the same index. At least, it wouldn't be clean.
By the way, this also explain the choice of using the factor index as the factor return index instead of the return realized timestamps.

Right, each period would need to be shifted by that period length. That would definitely jumble up the periods but I don't see a problem with that per se. Say we have 1D and 5D signal, we would shift the returns by 1 and 5 days, respectively. That's exactly how it would look if you would actually trade that signal.

But what about a 3h and 1D signal? How could you combine them with the same index?

@twiecki can we close this? I believe we should create a  new API if we need something that cannot be achieved with the current  perf.factor_returns implementation. Due to the reasons in this thread we cannot  change the function behaviour.


Fix DE numerical ordinal matching

The numerical ordinal matching rule in DE is too broad. An ordinal like "1." may not be proceeded or followed by numbers.

Added negative lookbehind - avoids matching the first "1." in "1.1" as an ordinal.
Added negative lookahead - avoids matching the second "1." in "1.1. as an ordinal

I suspect this might affect the generated classifiers.
Can you run:
stack build :duckling-regen-exe && stack exec duckling-regen-exe

and amend the generated files to the pull request?

Sorry, thought that this would be generated on the fly

No worries, I'd be nice for it to be somehow handled by the build system, but we haven't found a nice way to do that yet.

Merging, thank you!


Defender AV licensing for 2012 servers

[Enter feedback here]
It would be good to add something about Defender AV also being included with the license. Defender AV is only built into 2012 Server Core and Server 2016/2019.
https://www.microsoftvolumelicensing.com/Downloader.aspx?documenttype=PT&lang=English on Page 32 we can read:
"3.3 System Center Endpoint Protection Use with Azure Security Center or Microsoft Defender Advanced Threat Protection for Servers
Customer may use System Center Endpoint Protection to manage Virtual OSEs it is protecting using the Standard tier of Azure Security Center or Microsoft Defender Advanced Threat Protection for Servers. The System Center License Terms, as amended here, govern that use. Managed Virtual OSEs can be running on shared or dedicated Servers. Customer is not required to acquire and assign System Center Licenses for this limited use."

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

ID: 8432d9d8-e414-acf4-9287-ebbafab23c7e
Version Independent ID: 9eb184bd-e66d-6b1b-6b86-509ebe70bd3e
Content: Azure Defender for servers - the benefits and features
Content Source: articles/security-center/defender-for-servers-introduction.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@razmipatel
Thanks for your feedback! We will investigate and update as appropriate.

Thanks! It's mentioned in the article that they have an integrated license, but I made a pull request to link to the licensing agreement page.  https://github.com/MicrosoftDocs/azure-docs-pr/pull/135269
If you feel that more should be added feel free to make an additional pull request to the article.


fix: Updated Discovery.launch example with xrn:firebolt:application-type

:tada: This PR is included in version 0.18.0-next.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


⚠ ClamAV has degraded performance

In 463d9ce, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 176 ms

Resolved: ClamAV performance has improved in 59e6c3f.


Redix Sort Implementation in C++

Description
The full imlementation and logic in Redix Sort
Domain
Competitive Programming
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


Add poetry to manage dependencies, etc.

We can use it to manage package dependencies and add other tasks, e.g., testing for documentation, linting, code formatting, etc.

Add poetry as a dependency manager and make third party packages optional (if I'm not wrong one can install optional dependencies as group in poetry)
Add poetry build and deploy the GH workflows
Add testing, linting and formatting as poetry tasks
Add type checking as poetry task


Upgrade Quarkus Amazon services to 1.3.1

@zbendhiba please can you rebase.

@zbendhiba please can you rebase.

I just did :)


Minor typo fixes

The motivation for this change is to fix a number of typos to improve readability.

Good fixes, thank you!


Addition of three 404 Notfound templates

Title: Addition of three 404 Notfound templates
Fixes: #36
Description: This PR is regarding the addition of three 404 Notfound templates. Initially, I am adding three templates named NotfoundA,NotfoundB and NotfoundC.
ScreenShot:
Template1 - NotfoundA
Light mode

Dark mode

Template2 - NotfoundB
Light mode

Dark mode

Template2 - NotfoundC
Light mode

Dark mode

As you can see, I had added the three Notfound templates.

This fixes #36  Request.

why are these not merged? Is this not maintained?


Should this page include "TargetFramework" property?

[Enter feedback here]
I am trying hard to to find all the built-in parameters that I can use in a .csproj file for MsBuild.
The best page I found is this one, and I wonder why it doesn't include the very famous '$(TargetFramework)' property?
So, if TargetFramework is missed, could you please add it to this page, or if it doesn't belong here, could you please point me to the page that includes it?
Thank you so much.
Cheers,
Sia

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

ID: 9dbdd881-dc08-3ff7-d7f4-f9fa9373ea9b
Version Independent ID: 23ee268e-c6fa-9420-3a8d-a52f81104da7
Content: Common MSBuild Project Properties - MSBuild
Content Source: docs/msbuild/common-msbuild-project-properties.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @ghogen
Microsoft Alias: ghogen

Thanks for the issue report. The TargetFramework property is documented here, along with a few other properties that apply to SDK projects:
https://docs.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props
It could well be added to this page, perhaps along with others in that category.

Thank you so much for the update.
Regards,
Siavash Mortazavi
From: Gordon @.>
Sent: Wednesday, July 28, 2021 13:46
To: @.>
Cc: @.>; @.>
Subject: Re: [MicrosoftDocs/visualstudio-docs] Should this page include "TargetFramework" property? (#6902)
Thanks for the issue report. The TargetFramework property is documented here, along with a few other properties that apply to SDK projects:
https://docs.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props
It could well be added to this page, perhaps along with others in that category.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/visualstudio-docs/issues/6902#issuecomment-888609816, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB2AJP3MOZNORMPNJ4ZLTETT2BUCBANCNFSM5BC2ILMA.


iterate empty query

fix #129

We don't need detail::key_equal_encoded after this PR. Should I remove it?
return key_equal_encoded(plain_key, encoded_key);

is equivalent to
return plain_key == pct_encoded_view(encoded_key);

yeah remove it if necessary but put a comment on the equality line explaining the intent and make sure there's tests. Merge this PR when you feel it is ready.


CORE_ASSET.core_exchange_rate.is_null() == true

Please be aware.

Is there any bug being caused by this?
Is there any concrete suggestion of what should be done about this?

I think the resolution is to add a line to the doc comment explaining what the semantics should be when core_exchange_rate.is_null() and under what circumstances it should occur, then audit that the evaluators enforce these circumstances for asset CRUD.

No bug has been found except in my developing branch. CER is needed for percentage based transfer fee feature to calculate the value of a transfer. All assets created or updated in bitshares 2.0 have valid CERs. All assets except core asset inherited from bitshares 0.x have null CERs, they can't apply percentage fee unless set a valid CER. So I encountered this issue here when trying to apply percentage fee to core asset.
In asset_update_operation, CER is validated thus is_null()==false. However CER of core asset is invalid and it will never be updated. So I think it's ok to leave it as is, and be careful. Or fix it.

I discovered you can register new assets with null CER as well, see #579


[WIP] VIZ/EDU: how to analyze the forward model with PCA

Here I have some small example to investigate the effective dimensions in the lead field.
The script with its comments should be self-explanatory.
But, overall, I am a bit surprised about the relatively small number of dimensions.
Any feedback for improving the computation approach and correctness would be highly welcome.
cc @larsoner @agramfort @SherazKhan etc.
Here is the output:

yes but why not keeping all channels? if you add redundant channels it
won't increase the rank

So you’re saying that resulting differences in the svd spectra not simply
reflect higher resolution through added sensors but true intrinsic
resolution?
The 99% cumulative variance explained dimensions are about 50, 25 and 18
for grad, mag, eeg if you take all sensors within each sensor type.
On Wed 21 Nov 2018 at 16:36, Alexandre Gramfort<EMAIL_ADDRESS>wrote:

yes but why not keeping all channels? if you add redundant channels it
won't increase the rank
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/5736#issuecomment-440708451,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fiq5dJLOsMr3nhvE3H2gensVE7iQYks5uxXL4gaJpZM4Ys_1r
.

yes

@agramfort I removed subsampling and updated the comments a bit. I'd eventually like to add some more plots for exploring topographic patterns and visiting the effective rank by source label, but this can also be another PR.

maybe @LauriParkkonen or @mshamalainen have an opinion or a ref for the best way to display this.  I am sure this has been done before.

@dengemann are you up for polishing this for MRG? If not I'd say let's close and someone can resurrect if they are interested in the issue


Error when trying to delete a service

Context, see the "nastest1" repository on the Moehaha Cockpit: https://moehaha.barcelona.aydo.com/cockpit/Repo?repo=nastest1
When trying to delete vm1 get the error shown in the screenshot:

A delete tries to do an uninstall then it deletes the service instance file.
The problem comes from AYS itself. If a service has not been properly installed in the first place when trying to do the uninstall action, most of the time the action will fail too and show the error like the one here.

Good that we understand what is wrong...
But we really need the "Delete" action to work even if the installation failed.
I filed a feature request for this: #142

OK. I'll expose the ays destroy command in the portal so we can clean a repo even if some services are faulty.

@zaibon is this something you can fix today? I really need to clean-up the demo environment, and don't want to delete all repositories


feat(ricardian-contracts): add validator node agreement

resolves #4
Add Validator node agreement to ricardian clauses
Notes and considerations
This PR takes dev branch as head changes and compile clauses and contract as the Ricardian Contract Specification.
The base structure followed to construct the clauses specificaction were ricardian-spec and EOSIO/eosio.contracts

@leisterfrancisco I dont think we need to add the abi and wasm files to this repo , just the clauses is fine


relative URLs don't work in image_tag

Let's say I'm in some nested subdirectory:
/category
  /things
    index.html
    /images
      screenshot.png

If I add this to index.html:
= image_tag "images/screenshot.png"

I would expect a link to /category/things/images/screenshot.png. I swear this used to work. But in v4, I get /images/images/screenshot.png.

Converted to a pull with patch.


TN-3140 Catch second submission of a known QNR dyad in the act

as per TN-3140, need to prevent duplicate QNRs, that is, ones that match on visit, a function of (questionnaire_bank_id, qb_iteration), and instrument for a given patient.
given the complexity of source data - interventions including AE submitting such QNRs, don't raise but rather log the error to trigger a notification.

Complicated reproduction, as this is trying to capture an unexpected situation.
Done on eproms-test:

complete all questionnaires for a patient.
use SQL to move one of the submitted responses out of the way - i.e. assign a different subject_id temporarily
hit the /timeline&purge=true for user to update status
return to AE to take the questionnaire moved out of the way in step 2
BEFORE submitting from AE, reverse the move in step 2
submit from AE, and note in the logs:

 {"written_at": "2023-03-10T03:34:54.078Z", "written_ts":<PHONE_NUMBER>078849000, "msg": "Second submission for an existing QNR dyad received. Patient: 4089, QNR 4017", "type": "log", "logger": "flask.app", "thread": "MainThread", "level": "ERROR", "module": "questionnaire_response", "line_no": 198, "correlation_id": "859510f0-bef4-11ed-8731-0242ac130008"}


Clicking on notification does nothing useful

Describe the bug

Clicking on an "Items synced" notification from Maestral causes a Dock icon for Maestral to appear, but nothing else (seemingly) happens.
To Reproduce

Enable notifications for Maestral
Wait for Maestral to sync something to PC
Receive notification from Notification Center
Click on notification

Expected behaviour

Maybe open a folder with said synced items? Maybe see what official client does in a similar use case.
System:

Maestral version: 1.5.2
OS: [e.g. Ubuntu] macOS 10.15.7

Additional context

I don't know what an action should be, but right now it's pointless. Unclear why a Dock icon appears either, since no preferences window, nor any other Maestral window, is open at that point. Hope this is clear, and not a dupe of some earlier bug. Thanks.

In case of a single synced file or folder, clicking on the notification will open a new Finder window showing that item. In case of multiple synced items, there is currently no action at all (as you have discovered). It could potentially make sense to open all containing folders if multiple items are synced, though I am not sure how much the added value would be.

@SamSchott thanks. Opening multiple folders is indeed pointless, if not annoying. Perhaps a single notification per item, but that could pollute the notification centre in no time.
Still, the Dock icon should not appear if the app has no windows to show.

Still, the Dock icon should not appear if the app has no windows to show.

Fair point.
Also note that currently you will need to click the "Show" button of the notification to reveal the item, not just the notification itself. This could probably also be changed as clicking anywhere on the notification is often an intuitive action.


snazzy-info-window failed the build

Issue description
Hello! When I connected snazzy-info-window - build failed.
All folders and files are at their places.
http://prntscr.com/goeisp
Here is part of the log:
angular2 & angular-google-maps version
"angular/core": "4.4.3",
"agm/core": "1.0.0-beta.1",
"agm/snazzy-info-window": "1.0.0-beta.1",
Other information
ERROR in ./node_modules//directives/snazzy-info-window.js
Module not found: Error: Can't resolve 'snazzy-info-window' in 'D:\WorkSpace\improver\browser\node_modules@agm\snazzy-info-window\directives'
resolve 'snazzy-info-window' in 'D:\WorkSpace\improver\browser\node_modules@agm\snazzy-info-window\directives'
Parsed request is a module
using description file<EMAIL_ADDRESS>(relative path: ./directives)
Field 'browser' doesn't contain a valid alias configuration
after using description file<EMAIL_ADDRESS>(relative path: ./directives)
resolve as module
D:\WorkSpace\improver\browser\node_modules@agm\snazzy-info-window\directives\node_modules doesn't exist or is not a directory
D:\WorkSpace\improver\browser\node_modules@agm\snazzy-info-window\node_modules doesn't exist or is not a directory
D:\WorkSpace\improver\browser\node_modules@agm\node_modules doesn't exist or is not a directory
D:\WorkSpace\improver\browser\node_modules\node_modules doesn't exist or is not a directory
D:\WorkSpace\improver\node_modules doesn't exist or is not a directory

Did you install the package snazzy-info-window?

Yes of course. On screenshot you can see package inside node_modules

The screenshot points to @agm/snazzy-info-window. That package has a peer dep of snazzy-info-window, which you seem to be missing.

Thank you very much guys! =)

In conclusion:
Its not very clear that "snazzy-info-window" must be installed separately.
I think it would be better if this "snazzy-info-window" was a piece "@agm/snazzy-info-window".
Any "@agm/snazzy-info-window" way its cant be used as standalone, so why it doesn't have dependence to snazzy-info-window?
Or at last add some notes about it (Get started)
Thank your for help!
Best regards!

@Halynsky I can't speak for the author's reasons, but I can guess that it was handled that way so you could update dependency of snazzy-info-window on your own instead of waiting for a patch of the wrapper which will just bump up the dep versions.


fix: don't focus on composer when open right modal

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/26489
PROPOSAL: https://github.com/Expensify/App/issues/26489#issuecomment-1703141465
Tests

Open ND and log in with any account
Open any chat
Input @ character and verify that mention suggestions appears
Tap + button before the composer and tap outside of the menu
Verify that suggestions appears again
Tap + button again and tap any menu except Add attachment
Verify that suggestion list doesn't appear for a brief moment before modal is opened
Close modal
Verify that suggestion list appears again

[x] Verify that no errors appear in the JS console

Offline tests

Open ND and log in with any account
Open any chat
Input @ character and verify that mention suggestions appears
Tap + button before the composer and tap outside of the menu
Verify that suggestions appears again
Tap + button again and tap any menu except Add attachment
Verify that suggestion list doesn't appear for a brief moment before modal is opened
Close modal
Verify that suggestion list appears again

QA Steps

Open ND and log in with any account
Open any chat
Input @ character and verify that mention suggestions appears
Tap + button before the composer and tap outside of the menu
Verify that suggestions appears again
Tap + button again and tap any menu except Add attachment
Verify that suggestion list doesn't appear for a brief moment before modal is opened
Close modal
Verify that suggestion list appears again

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/126839717/7b9d2a1e-4275-49f8-ac9e-cd387f56bf54

Mobile Web - Chrome
https://github.com/Expensify/App/assets/126839717/206204ab-c3d9-46cd-8c97-f939004beca1

Mobile Web - Safari
https://github.com/Expensify/App/assets/126839717/b7afea8f-c397-47ae-a3f9-3c1a66cf0c1b

Desktop
https://github.com/Expensify/App/assets/126839717/27aa8224-d723-41fb-bbb1-6465baa0c32d

iOS
https://github.com/Expensify/App/assets/126839717/3ec08f34-b9e7-4f99-b257-b0100b7874b4

Android
https://github.com/Expensify/App/assets/126839717/407e8101-3cb6-4a34-ac84-a911c034c901

@s-alves10 The PR is slightly different than the approved solution. Please comment on each new section that was added explaining the need for it.

@s-alves10 The PR is slightly different than the approved solution. Please comment on each new section that was added explaining the need for it.

I added some comments.
Suggestions, SuggestionEmojis, and SuggestionMentions have a new method: restoreSuggestions. This is created for restoring the previous suggestions.
We calculate the suggestions in onSelectionChange, but this is not called when gets refocused if there is no selection change. In this case, I restored the previous suggestions.

@s77rt
Please take a look again

Added some comments on the previous review comments

@s77rt
If you think we should limit the scope of the PR in the issue, please let me know.
We don't need restoreSuggestions in that case. I'll remove them

@s-alves10 Yes, let's please limit the PR to the bugs that are linked in the issue. If a bug is found and it's a regression we should fix it, but if it's on staging/main already it's better to report it in Slack otherwise we would be working out a new solution instead of going forward with the approved one (with the exception of some bugs where the solution is straightforward).

@s77rt
I removed all unrelated code. Please check again

@youssef-lr
Please take a look

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/youssef-lr in version: 1.3.69-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.69-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/youssef-lr in version: 1.3.70-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 1.3.70-8 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


az network nsg rule create

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az network nsg rule create
Errors:
The command failed with an unexpected error. Here is the traceback:
Expect <class 'str'>, got {'additional_properties': {}, 'id': '/subscriptions/25d76115-c785-433c-8cd5-99fceda2914d/resourceGroups/rg-mol-prd-vnet-001/providers/Microsoft.Network/applicationSecurityGroups/asg-mol-prd-rds-001', 'name': None, 'type': None, 'location': None, 'tags': None, 'etag': None, 'resource_guid': None, 'provisioning_state': None} (<class 'azure.mgmt.network.v2022_01_01.models._models_py3.ApplicationSecurityGroup'>
Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/network/custom.py", line 5358, in create_nsg_rule
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_command.py", line 145, in __call__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/network/aaz/latest/network/nsg/rule/_create.py", line 40, in _handler
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_command.py", line 149, in _handler
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_command_ctx.py", line 31, in __init__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_field_value.py", line 80, in __setitem__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_field_type.py", line 382, in process_data
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_field_value.py", line 369, in __setitem__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_field_type.py", line 219, in process_data
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_field_value.py", line 80, in __setitem__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_field_type.py", line 43, in process_data
AssertionError: Expect <class 'str'>, got {'additional_properties': {}, 'id': '/subscriptions/25d76115-c785-433c-8cd5-99fceda2914d/resourceGroups/rg-mol-prd-vnet-001/providers/Microsoft.Network/applicationSecurityGroups/asg-mol-prd-rds-001', 'name': None, 'type': None, 'location': None, 'tags': None, 'etag': None, 'resource_guid': None, 'provisioning_state': None} (<class 'azure.mgmt.network.v2022_01_01.models._models_py3.ApplicationSecurityGroup'>

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az network nsg rule create -g {} --nsg-name {} --name {} --priority {} --direction {} --source-asgs {} {} {} --destination-asgs {} --destination-port-ranges {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} --access {} --protocol {}

Expected Behavior
Environment Summary
Windows-10-10.0.22621-SP0
Python 3.10.8
Installer: MSI

azure-cli 2.43.0

Additional Context

It's duplicate with https://github.com/Azure/azure-cli/issues/24853 and will be fixed in Azure CLI 2.44.0.


How can I add my custom grafana dashboard?

I am trying to add a new dashboard to the below helm chart
https://github.com/helm/charts/tree/master/stable/prometheus-operator
I am having all my dashboards in .json files. Could you please help me out I can I edit my values.yaml in such a way that everytime I install prometheus-operator I will have my dashboard imported.
P.S I know I have to create a configmap and there is some setting I need to modify in values.yaml. But could some please help me out the the best way to do this?

I can comment on this. There are a couple of ways to inject Grafana dashboards, but here's the general flow:

Make sure you have a dashboardProvider configured. This is actually part of the Grafana chart that comes bundled with the Prometheus operator Helm chart:

grafana:
  dashboardProviders:
    dashboardproviders.yaml:
      apiVersion: 1
      providers:
      - name: 'myprovider'
        orgId: 1
        folder: ''
        type: file
        disableDeletion: true
        editable: false
        options:
          path: /var/lib/grafana/dashboards/myprovider

Once you have your provider (named myprovider in this case), you can add dashboards one of the followings ways:

Via the official Grafana website:
grafana:
  dashboards:
    myprovider:
      nginx-ingress-controller:
        datasource: Prometheus
        gnetId: 9614
        revision: 1

Via raw JSON:
grafana:
  dashboards:
    myprovider:
      some-custom-chart:
        json: |
          {
            "annotations": {
              "list": [
                {
                  "builtIn": 1,
                  "datasource": "Prometheus",
                  "enable": true,
                  "hide": true,
                  "iconColor": "rgba(0, 211, 255, 1)",
                  "name": "Annotations & Alerts",
                  "type": "dashboard"
                }
              ]
            }
<.....>

Those are the two basic methods, but the Grafana chart has other methods (see here: https://github.com/helm/charts/blob/master/stable/grafana/values.yaml#L345-L360)

The Prometheus Operator itself is completely out of scope for Grafana these days. Please open Grafana related and kube-prometheus specific question over in that repo: https://github.com/coreos/kube-prometheus/
As I can see some Helm related things in the comments above you might want to discuss in the helm repository.
Closing because this discussion is happening in an unrelated repository.


Replace nullable_visit by NullableVisitor

This introduces the NullableVisitor from CPython's pegen.

This is part of the former PR #85.
I was able to run the test-suite locally, using pipenv and python38.
Generally, should we not upgrade to latest python310 with all pegen development?

@phorward please don't force push after an approval because it forces us to dismiss the review and review again everything :)

Hello @pablogsal, I hope you're doing well.
Can you please take another review and maybe merge on this pull request? I've started to work on a pull request setting-up on this one, to successively transfer all overrides from the CPython version of pegen to the stand-alone project. It is important for me to have the stand-alone pegen in similar code-base as the CPython version, to start with further developments on it.
I would like to share my vision of pegen in some kind, if interested, as it may become a universal PEG-like parser generator not only limited to Python. Please contact me, or provide a way to share ideas.

@phorward Thanks for the PR and sorry for taking so long on this. We've been very busy with other things and this fell further down in our list of to-dos.
If you want to start a discussion on ideas you have for the project, an issue would be the best way forward. Please open one, and I'd be happy to get a conversation going there.

@phorward Thanks for the PR and sorry for taking so long on this. We've been very busy with other things and this fell further down in our list of to-dos.

No problem, thanks for merging. Can you please check the GitHub action job that is currently pending, so that the merge becomes complete?

If you want to start a discussion on ideas you have for the project, an issue would be the best way forward. Please open one, and I'd be happy to get a conversation going there.

Ok thanks. I wrote some ideas down on a vision for pegen in my fork anypeg, but I think it'll be the best to divide it into separate issues to easier maintain and focus on.


How to set Workstation for AuthIdentity

In some case, may need  Workstation for negotiate, is there any interface for it.

@RickSKy do you know if there's a way to do it in the original Windows SSPI API? We've started adding a few extended credential/context attributes not supported in Windows SSPI, but we always try to find the "portable" way to do it first.

I found that cntlm has Workstation param  Configuration hints.

we can also find workstation in  Python's ntlm lib https://pypi.org/project/ntlm-auth/

There is no API for it now, but we might add one for it

Hi @RRRadicalEdward! Is it on your roadmap for this month?

@CBenoit Yeah. I will do it after making the changes in FreeRDP that Richard has requested.

Excellent!


Folder structure for packages and Java

Haven't tried to build yet, but I was struck that some of the java code for aa and LocalServer isn't organized along the usual package conventions, though the code itself does have package statements. E.g. in AaTool.java

Do you mean that,
com.google.startupos.tools.reviewer.aa.AaTool
is in folder tools/reviewer/aa instead of java/com/google/startupos/tools/reviewer/aa and tests in javatests/com/google/startupos/tools/reviewer/aa?

Yes, that's what I meant.

Right, so we've actually had some discussions on that, here:
https://github.com/google/startup-os/issues/30
The idea is that Bazel is a multi-language built tool, so if a repo has multiple projects, and say some project has java, scala, c++, python and proto (quite conceivable), it's confusing to have each in a separate root folder, i.e:
java/com/google/startupos/tools/reviewer/aa
javatests/com/google/startupos/tools/reviewer/aa
and then similarly,
<language>/com/google/startupos/tools/reviewer/aa
<language>tests/com/google/startupos/tools/reviewer/aa
for every language.
So the idea is that we organize folders based on projects, and keep project-related files together.

 Set create_timestamp to local machine time when creating a new Diff. New proto field should be added for that.

How do we move forward with this issue?

My personal opinion:
It is not confusing to put separate language files in separate roots. In fact, it's the opposite. It helps keep things organized and makes it easier to find the code. google3 and most multi-language github projects I've seen do this.
That said, I don't know enough about bazel to have a strong, informed opinion here. But I do think most Java developers will find the existing layout confusing.

I'm not sure what you mean by a root here. google3 certainly does separate java, C++, etc. into separate directory structures and google3/java follows java conventions on package organization. In this case google/startup-os is the equivalent of google3.


minor language re-edit

Thanks for the PR, but I failed to see the motivation behind these changes. The language may be improved, but the original text was also fine and readable, IMHO.

See. But there is error in picture pointers2.png. Hope that picture will be re-designed.

Honestly I don't see any error in the figure. There is only one way to construct the program since B is the type who holds weak_ptr:
#include <memory>
#include <iostream>

struct A;
struct B;

struct A {
    std::shared_ptr<B> pointer;
    ~A() {
        std::cout << "A 被销毁" << std::endl;
    }
};
struct B {
    std::weak_ptr<A> pointer;
    ~B() {
        std::cout << "B 被销毁" << std::endl;
    }
};
int main() {
    auto a = std::make_shared<A>();
    auto b = std::make_shared<B>();
    a->pointer = b;
    b->pointer = a;
}

The output of this program is:
A 被销毁
B 被销毁

It's about the destruction order of local variables within main():
auto a = ...
auto b = ...
...
// destruction of b
// destruction of a
// return;

So, in the picture,  shared_ptr b should disapear first, followed by a.
see C++ local variable destruction order

By the way, "重写" and "重载" looks similar but should be distinguished between.

compare the two code snippets:

b destruct first
b destruct first

compare the two code snippets:

a destruct first
b destruct first

I appreciate that you are trying to contribute, however, note that the rule of destruction should also respect the reference counting. The output of the previous code example already represents the order of destruction. Your example is invalid as it is incomparable to the original example because your example involved different variable scopes.

NOT "destruction order of  A,B instances", but "destruction order of local variables a,b".

I will not respond to the issue any more. Thanks for your patience.

By the way, "重写" and "重载" looks similar in Chinese character but should be distinguished for the different concepts they hold.

I do not think the Chinese-translated terminology matters much here. Apparently, we use override for the terminology, and to my knowledge, it was often translated "重载".

NOT "destruction order of A,B instances", but "destruction order of local variables a,b".

I will not respond to the issue any more. Thanks for your patience.

I keep failing to see what you are trying to argue here. a and b are pointers referring to the actual object instance. The following program will not execute the destructors.
#include <memory>
#include <iostream>

struct A;
struct B;

struct A {
    std::shared_ptr<B> pointer;
    ~A() {
        std::cout << "A 被销毁" << std::endl;
    }
};
struct B {
    std::weak_ptr<A> pointer;
    ~B() {
        std::cout << "B 被销毁" << std::endl;
    }
};
int main() {
    A *a;
    B *b;
}

The stack overflow link you referred to was a stack object, which is different from our context here. In our case, it does not matter to remove a or b first in the picture. Thanks for raising the discussion.

Leaving all results here.
destruction order

a destruct first

executing this code snippet results in:
A 被销毁
1
B 被销毁

b destruct first

executing this code snippet results in:
1
A 被销毁
B 被销毁

"重载"
try Googling for "overload vs override", search with Baidu for "重载 和 重写"

"overload vs override in c++" from stackoverflow

Overloading generally means that you have two or more functions in the same scope having the same name.
Overriding is something completely different.

"重载 和 重写"

Last words. You are writing a BOOK, not blogs or C++ learning notes.

I believe I have made a clear point in https://github.com/changkun/modern-cpp-tutorial/pull/254#issuecomment-1265657610, and your response missed that.
I don't care which Chinese translation of override and overload is; as I said, it is a matter of education. As long as I am the author, I decide what terminology to use for describing a semantic. It is sound as long as it stays consistent in the book. Please adapt yourself to the author if your prior knowledge does not match. Otherwise, you have the right to choose what book to read. I'll stop continuing this discussion. Thanks.


Remove "Ionic", replace by "Cordova"

This is not Ionic specific, no need to call it this way.

"Just" changed the order so Cordova always comes first, still mention Ionic as it is just more popular.


Make challenge link in changeset description mandatory

I would like to make it mandatory to have the link to the MapRoulette challenge in the changeset description.
Right now this is optional.
Ideally I would like #225 to be done first to minimize the payload, but I don't consider that as mandatory.

Will it also be possible to view the person who created the maproulette thing without logging in to maproulette?
Strictly speaking, telling someone to do something via maproulette is an example of organised editing so that https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines should be followed.  Some organisers do follow this (for example https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/Expedia , which is related to this issue).
Someone should be able to click through from an OpenStreetMap changeset to get to be able to message the person who "organised" it, which in this case is the OSM user who created the challenge, without having to log into an external system.

Strictly speaking, telling someone to do something via maproulette is an example of organised editing

This depends on the relationship between the organizer and those who make the edits, not on the tool used.

Someone should be able to click through from an OpenStreetMap changeset to get to be able to message the person who "organised" it, which in this case is the OSM user who created the challenge, without having to log into an external system.

MapRoulette uses OSM OAuth for authentication so there is a 1:1 relationship between MapRoulette usernames and OSM ones.
We display the name of the MapRoulette user with every Challenge even if you're not signed in:

With that information, you can message the user on OSM.
Now, we can make it easier by adding a link to compose a new OSM message like we do on the Task screen:

Is that something you think would be helpful for those who really don't want to sign in to MapRoulette using their OSM account?

A note unrelated to the comment above: I don't think there is a way to prevent mappers from modifying the changeset comment to remove the link, so this is not a guarantee that the link between a changeset and the MapRoulette challenge will exist on the OSM side, but I believe it's as close as we can reasonably get.

See also #1899 for the issue raised above, following discussion here

What I stated above is not technically correct -- the default project created when a user first registers themselves with MapRoulette is called [OSM user display name]'s Project but a) this name can be changed and b) users can create additional projects with names that don't include their OSM user display name.

Discussing with @jschwarz2030 this is how we will implement:

MapRoulette Challenge link (if implemented, shortened #225) will always be included in the changeset comment if and only if the challenge is discoverable at the time the mapper works on the task
There will be a server configuration flag to override this behavior but maproulette.org will not have this flag set.
The switch in the Challenge wizard to enable / disable adding the URL to the changeset comment will be removed.

Note that mappers can still always edit the changeset comment before committing the edit to OSM, so there can never be a guarantee that the linkage between an OSM changeset and a MR task exists - unless we use changeset tags instead?


Make all request timeouts configurable and clear

What problem are you trying to solve?
We have a couple of ways to set request timeouts at the moment.
STREAM_READING_TIMEOUT_ENV an env variable, DEFAULT_STREAM_READING_TIMEOUT a constant, DEFAULT_REQUEST_TIMEOUT another constant, and --request-timeout a cli argument.

Having these different sources can potentially conflict and be confusing to debug.
Timeouts that use only the constants are not configurable

What's your suggested solution?
We should add request_timeout field to the EndpointConfig class. This way, every endpoint can specify a custom timeout, falling back to a default if not set.
The EndpointConfig class has too many responsibilities being both a representation of a config from endpoints.yml and a http request controller. We should split it up into Endpoint and EndpointConfig so that the request handling is in the Endpoint class and the config parsing and handling is in the the EndpointConfig class.
This way all timeouts can be set in the Endpoint instance and it can be used for EVERY outgoing request. If this is done we will not longer be importing DEFAULT_REQUEST_TIMEOUT in many places across the app.
Examples (if relevant)
No response
Is anything blocking this from being implemented? (if relevant)
No response
Definition of Done

all requests are made from an instance of Endpoint
EndpointConfig includes request_timeout field and this is parsed from that endpoint's block in endpoints.yml
All unused timeout constants are deleted
the --request-timeout flag is removed

Thanks for submitting this feature request 🚀 @s-elsharkawy will get back to you about it soon! ✨


feat(makeServerFetchye): adding run method to response

We have been experimenting with using fetchye across our tenancy, and have run into an interesting case where we want to be able to use both the data, and the reload run methods as part of our module thunk methods. Currently we get both the data object and the run method into our components via the useFetchye hook, we then pass these into our redux thunks as parameters. However this method is clumsy and starts to get heavy when the example includes more than one source of data (we managed to get up to 3x in one case), or when thunks begin to chain calls.
This change is to export the run method, so both the two interfaces to Fetchye expose the same API to the client. This would allow us to re-use the underlying makeOneServerFetchye methods not only in our loadModuleData functions, but in redux thunks to load / get / reload data without getting stuck in parameter hell.
Since we have started this change the oneFetchye method was added to fetchye-one-app which compliments our change allowing engineers to just dispatch their fetchye requests in their thunk.
What we have today
const onPrimaryTravelerSaveThunk = ({
  contactInfo, // fetchye run and data are renamed and passed as a param to the thunk
  reloadContactInfo,
}) => async (dispatch, getState) => {
  const state = getState();
  await dispatch(setFormSubmitted(true));

  if (hasFormChanged(contactInfo, state)) {
    dispatch(setIsSaving());
    try {
      await dispatch(postUpdatesThunk());
      await dispatch(setSaveSuccessful());
    } catch (error) {
      await dispatch(setErrorSaving());
    } finally {
      reloadContactInfo();
    }
  }
  dispatch(setFormSubmitted(false));
};

What we would like to be able to do
const onPrimaryTravelerSaveThunk = () => async (dispatch, getState) => {
  const state = getState();
  await dispatch(setFormSubmitted(true));

  const {
    data: contactInfo,
    run: reloadContactInfo,
  } = await dispatch(loadContactInfo());  // by accessing data directly from fetchye via a thunk. we can remove the parameters

  if (hasFormChanged(contactInfo, state)) {
    dispatch(setIsSaving());
    try {
      await dispatch(postUpdatesThunk());
      await dispatch(setSaveSuccessful());
    } catch (error) {
      await dispatch(setErrorSaving());
    } finally {
      reloadContactInfo();
    }
  }
  dispatch(setFormSubmitted(false));
};

Here is how we access the exported data, errors and run response within a thunk context via our loadContactInfo function
export const loadContactInfo = ({
  isCompanion,
  companionId,
}) => async (dispatch, getState) => {
  const { data: profileId } = await dispatch(loadProfileId);
  const { data: secToken } = await dispatch(loadSecToken);
  return dispatch(oneFetchye(
    getContactInfoUrl(profileId, isCompanion, companionId)(getState()),
    {
      headers: generateHeaders(secToken),
      credentials: 'include',
    }
  ));
};

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


Par unseq/unseq adding

1. Add policies:
unsequenced_task_policy;
unsequenced_task_policy_shim;
unsequenced_policy;
unsequenced_policy_shim;
parallel_unsequenced_task_policy;
parallel_unsequenced_task_policy_shim;
parallel_unsequenced_policy;
parallel_unsequenced_policy_shim;

  Add tests for unseq/par_unseq in rotate.cpp

2. Add implementations for new policies to handle local exceptions
  Add tests in rotate.cpp to test if that works

Fixes #5492

Have no idea why some commits come over from my own hpx repository.
For creating this PR today(5.16), I only add the two latest commits from my local workstation.
(Looks like those unrelated commits are not interfering with existing files anyway)

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)+InfoPropertyBeforeAfterHPX Datetime2022-02-09T15:45:06+00:002022-05-16T20:30:18+00:00HPX Commita68196882e3e093ba44367f6675f538d613c9aa3cd53b41befda6b0591e7ce0b856c1906d95d1b46Hostnamenid00729nid00026EnvfileClusternamedaintdaintDatetime2022-02-09T17:03:21.440240+01:002022-05-16T22:49:41.904586+02:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPX Datetime2021-11-11T08:14:57+00:002022-05-16T20:30:18+00:00HPX Commit96a2e4bd1c76207dea8d5302784962c927882406cd53b41befda6b0591e7ce0b856c1906d95d1b46Hostnamenid00006nid00026EnvfileClusternamedaintdaintDatetime2021-11-11T09:28:13.071121+01:002022-05-16T22:49:58.933072+02:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)-(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)=(=)InfoPropertyBeforeAfterHPX Datetime2021-11-10T19:14:21+00:002022-05-16T20:30:18+00:00HPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01acd53b41befda6b0591e7ce0b856c1906d95d1b46Hostnamenid00120nid00026EnvfileClusternamedaintdaintDatetime2021-11-10T20:28:18.266961+01:002022-05-16T22:50:14.111250+02:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Have no idea why some commits (7 days ago, 21days ago) come over from my own hpx repository.

You might want to rebase onto master, that should get rid of all superfluous commits.

@msimberg the clang-apex-builder on Daint reports a strange error claiming that there is a version control header in one of the files, even if it isn't in the file in the repository. I'm stumped - would you have any ideas?

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Commita68196882e3e093ba44367f6675f538d613c9aa3044a4b3b0eb1fab7c923e56f2724d6ceaed06e33HPX Datetime2022-02-09T15:45:06+00:002022-06-10T15:10:17+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2022-02-09T17:03:21.440240+01:002022-06-10T17:28:06.274826+02:00ClusternamedaintdaintEnvfileHostnamenid00729nid00495ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch+InfoPropertyBeforeAfterHPX Commit96a2e4bd1c76207dea8d5302784962c927882406044a4b3b0eb1fab7c923e56f2724d6ceaed06e33HPX Datetime2021-11-11T08:14:57+00:002022-06-10T15:10:17+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-11-11T09:28:13.071121+01:002022-06-10T17:28:23.098633+02:00ClusternamedaintdaintEnvfileHostnamenid00006nid00495ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)-(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)=InfoPropertyBeforeAfterHPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a044a4b3b0eb1fab7c923e56f2724d6ceaed06e33HPX Datetime2021-11-10T19:14:21+00:002022-06-10T15:10:17+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-11-10T20:28:18.266961+01:002022-06-10T17:28:38.559775+02:00ClusternamedaintdaintEnvfileHostnamenid00120nid00495Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

The HIP builder failures are caused by configuration issues on Rostam. We will fix those separately

bors merge


round does not check for empty values.

Coordinate rounding throws an error when trying to round a coordinate that is undefined.

Actually just a but in limit.  Returning an empty value, instead of passing pack the Coordinate.


Error in Google maps for flutter in gestureRecognizers in google_map.dart

Steps to Reproduce

I'm trying to use the plugin: https://github.com/flutter/plugins/tree/master/packages/google_maps_flutter
When I'm trying to run the example provided: https://github.com/flutter/plugins/blob/master/packages/google_maps_flutter/example/lib/map_ui.dart
I got the error:

Error: The argument type 'dart.core::Set' can't be assigned to the parameter type
in
final Set<Factory> gestureRecognizers;
in google_map.dart
Logs

X:\_flutter_sdk>flutter doctor -v
[√] Flutter (Channel beta, v0.9.4, on Microsoft Windows [VersiÃ³n 10.0.17134.345], locale es-ES)
    • Flutter version 0.9.4 at X:\_flutter_sdk
    • Framework revision f37c235c32 (4 weeks ago), 2018-09-25 17:45:40 -0400
    • Engine revision 74625aed32
    • Dart version 2.1.0-dev.5.0.flutter-a2eb050044

[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at x:\_android_sdk\
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • ANDROID_HOME = x:\_android_sdk\
    • Java binary at: X:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[√] Android Studio (version 3.2)
    • Android Studio at X:\Program Files\Android\Android Studio
    • Flutter plugin version 29.1.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[√] IntelliJ IDEA Ultimate Edition (version 2018.1)
    • IntelliJ at W:\Program Files\JetBrains\IntelliJ IDEA 2018.1.2
    • Flutter plugin version 28.0.2
    • Dart plugin version 181.4668.60

[√] Connected devices (1 available)
    • Android SDK built for x86 64 • emulator-5554 • android-x64 • Android 8.0.0 (API 26) (emulator)

• No issues found!

log_error.txt
main.dart.txt

Can you please try flutter channel master and check if you can still reproduce?

Hi
Please find below the error I got trying to do flutter channel master in my computer:
Thank you.
X:_flutter_sdk>flutter channel master
Switching to flutter channel 'master'...
git: error: The following untracked working tree files would be overwritten by checkout:
git:    dev/integration_tests/ios_host_app/Flutter/.gitkeep
git:    examples/flutter_gallery/test/demo/material/expansion_panels_demo_test.dart
git:    packages/flutter/lib/src/material/color_scheme.dart
git:    packages/flutter/lib/src/material/material_button.dart
git:    packages/flutter/lib/src/material/text_theme.dart
git:    packages/flutter/test/material/switch_list_tile_test.dart
git:    packages/flutter/test/material/text_theme_test.dart
git:    packages/flutter/test/material/theme_defaults_test.dart
git:    packages/flutter/test/painting/binding_test.dart
git:    packages/flutter_driver/lib/src/common/fuchsia_compat.dart
git:    packages/flutter_localizations/lib/src/l10n/material_km.arb
git:    packages/flutter_localizations/lib/src/l10n/material_mn.arb
git:    packages/flutter_tools/templates/app/.gitignore.tmpl
git:    packages/flutter_tools/templates/app/.metadata.tmpl
git:    packages/flutter_tools/templates/app/README.md.tmpl
git:    packages/flutter_tools/templates/app/android-java.tmpl/app/build.gradle.tmpl
git:    packages/flutter_tools/templates/app/android-java.tmpl/app/src/main/java/androidIdentifier/MainActivity.java.tmpl
git:    packages/flutter_tools/templates/app/android-java.tmpl/build.gradle
git:    packages/flutter_tools/templates/app/android-kotlin.tmpl/app/build.gradle.tmpl
git:    packages/flutter_tools/templates/app/android-kotlin.tmpl/app/src/main/kotlin/androidIdentifier/MainActivity.kt.tmpl
git:    packages/flutter_tools/templates/app/android-kotlin.tmpl/build.gradle
git:    packages/flutter_tools/templates/app/android.tmpl/app/src/main/AndroidManifest.xml.tmpl
git:    packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/drawable/launch_background.xml
git:    packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-hdpi/ic_launcher.png
git:    packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-mdpi/ic_launcher.png
git:    packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-xhdpi/ic_launcher.png
git:    packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-xxhdpi/ic_launcher.png
git:    packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-xxxhdpi/ic_launcher.png
git:    packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/values/styles.xml
git:    packages/flutter_tools/templates/app/android.tmpl/gradle.properties
git:    packages/flutter_tools/templates/app/android.tmpl/gradle/wrapper/gradle-wrapper.properties
git:    packages/flutter_tools/templates/app/android.tmpl/settings.gradle
git:    packages/flutter_tools/templates/app/ios-objc.tmpl/Runner.xcodeproj/project.pbxproj.tmpl
git:    packages/flutter_tools/templates/app/ios-objc.tmpl/Runner/AppDelegate.h
git:    packages/flutter_tools/templates/app/ios-objc.tmpl/Runner/AppDelegate.m
git:    packages/flutter_tools/templates/app/ios-objc.tmpl/Runner/main.m
git:    packages/flutter_tools/templates/app/ios-swift.tmpl/Runner.xcodeproj/project.pbxproj.tmpl
git:    packages/flutter_tools/templates/app/ios-swift.tmpl/Runner/AppDelegate.swift
git:    packages/flutter_tools/templates/app/ios-swift.tmpl/Runner/Runner-Bridging-Header.h
git:    packages/flutter_tools/templates/app/ios.tmpl/Flutter/AppFrameworkInfo.plist
git:    packages/flutter_tools/templates/app/ios.tmpl/Flutter/Debug.xcconfig
git:    packages/flutter_tools/templates/app/ios.tmpl/Flutter/Release.xcconfig
git:    packages/flutter_tools/templates/app/ios.tmpl/Runner.xcodeproj/project.xcworkspace/contents.xcworkspacedata
git:    packages/flutter_tools/templates/app/ios.tmpl/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme
git:    packages/flutter_tools/templates/app/ios.tmpl/Runner.xcworkspace/contents.xcworkspacedata
git:    packages/flutter_tools/templates/app/ios.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/Contents.json
git<EMAIL_ADDRESS>git<EMAIL_ADDRESS>git<EMAIL_ADDRESS>git<EMAIL_ADDRESS>git:    packages/flutter_t
git: Aborting
Switching channels failed with error code 1.

Use
git clean -xfd
git stash save --keep-index
git stash drop
git pull

in the Flutter install directory.

Merging with #23253


Thunar

It's the file manager for Xfce desktop environment
Icon name: org.xfce.thunar
Original icon:

Duplicate of #9


I want to ask：How can I make my own data set?---thanks

How can I make my own COCOA data set?
i see the :http://openaccess.thecvf.com/content_cvpr_2017/papers/Zhu_Semantic_Amodal_Segmentation_CVPR_2017_paper.pdf.
but the tools do not open-source.

Try https://github.com/wkentaro/labelme

想请问一下，在labelme中标注的时候，应该对哪些部分进行标注呢，分为几类呢，比如说：标注需要去遮挡的目标和目标中被遮挡的部分。
万分感谢

Sorry, this repo does not involve how to annotate an amodal dataset. I cannot provide any suggestions since we did not try it.

How can I make my own COCOA data set?
i see the :http://openaccess.thecvf.com/content_cvpr_2017/papers/Zhu_Semantic_Amodal_Segmentation_CVPR_2017_paper.pdf.
but the tools do not open-source.

Hello! I would like to ask you some questions. Have you successfully made your own data set? But the tool is not open source. Have you found the tool? Thank you.

How can I make my own COCOA data set?
i see the :http://openaccess.thecvf.com/content_cvpr_2017/papers/Zhu_Semantic_Amodal_Segmentation_CVPR_2017_paper.pdf.
but the tools do not open-source.

Hello! I would like to ask you some questions. Have you successfully made your own data set? But the tool is not open source. Have you found the tool? Thank you.

I have the same question, Have you found the tool?Thank you.


WIP: [9.x] Adding a "unixtime" Eloquant type and cast

This PR adds the $table->unixTime(); migration table method and "unixtime" cast to Models.

This doesn't break any existing features. $table->timestamps();, "datetime", "timestamp", etc. still behave as they did.
MySQL (and by extension, MariaDB) does not yet support >2038-01-19 03:14:07 UTC, and it is slowly but increasingly becoming a problem. Many developers have resorted to using BIGINT and writing their own casts (including myself) to store datetimes beyond 2038.
This PR adds a convenient migration table method and an Eloquent cast to make this easier out-of-the-box.

Isn't the timestamp cast already a unix timestamp cast?

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

For anyone who finds this, you can just add this to your Models to make them send and accept unix timestamps to and from the database:
protected $dateFormat = 'U';

(this is what happens when you don't read the docs)


update the owner files

[skip ci]
What does does this PR do / why we need it:
This PR removes the following people from approvers and reviewers list as they are in different teams now.

maysunfaisal
johnmcollier
GeekArthur
amitkrout
elsony

Also removes cdrage as he is going on leave.
Which issue(s) this PR fixes:
No issue
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

[ ] I have read the test guidelines

How to test changes / Special notes to the reviewer:

/retest

/approve


Match default chunksize in docstring to actual default set in code

[ ] Closes #11253
[ ] Tests added / passed
[ ] Passes pre-commit run --all-files

The last pre-commit didn't pass, even on a clean clone I get several errors in numpy_compat.py - I guess this is known?

Can one of the admins verify this patch?
Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.

thx!


fix: add depends on to igw on public subnets

without this, during a destroy, terraform tries and fails to destroy the
igw very early on. this fixes that minor efficiency problem

:tada: This PR is included in version 1.1.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: