Enable Computer Vision Client to customize endpoint.

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

@DavidLiCIG @felixwa please, review.

@sergey-shandar, no changes on operations/models. Just swagger update so the client can be flexible to customize the base URI.

@sergey-shandar ping... :)

Yes, we are aware that this is a breaking change. :) Please merge.


Switching to httpaf when the lwt supported release is on opam

Httpaf has better performance than cohttp, so it makes sense to switching to it

An another possiblity is h2, which supports http2, which would mean being more "future proof".


Fix problem with removeAccents: true

When removeAccents is true, all accents in the searchable elements are removed. But if you type an accent like "ä" in your search input this value is not modified and the search results are not correct.
Therefore if removeAccents is activated all accents should also be removed from the searchvalue.
Hope this is correct and I didn't overlook something.

Merged to hideseek-mod


Strange wrapping issues

Hi, I am having this problem with bobby & powerline-plain themes for bash-it. As you can see when I cd into a directory or resize terminal, the command prompt gets completely messed up:

Specs:

We recently solved a similar issue and the root cause was a bad value for the locale. The locale was getting set to "C" (ancient, no unicode support). That locale treats every byte as a character. But modern locales like utf8 have 2-byte characters. It doesn't actually have anything to do with Powerline other than the fact that Powerline uses non-breaking spaces for spaces, which are 2 byte unicode characters. It also uses 2-byte unicode characters for the right-facing triangles in the prompt. For every space or triangle in the prompt, it thinks there are 2 characters instead of 1. This causes all of the strange wrapping behavior.
The fix is to make sure your locale is correct.  See what-does-lc-all-c-do for information about LC_ALL. For us, glibc was actually the culprit. For some good info on how glibc uses the locale, see: differences-between-en-us-utf8-and-en-us-utf-8.

Our use model was a bit different since we are running Centos in Docker. Our fix was the following:
In Dockerfile:
-ENV LANG=en_US.UTF-8
+ENV LANG=en_US.utf8
+sed -i 's/UTF-8/utf8/' /etc/yum.conf
Then we ran "locale -a" and "locale" to verify that en_US.utf8 was there. When we used the capital letter form (UTF-8), it was getting set to "C" which caused the bad wrapping.

BTW if glibc is built with the wrong locale, you'll need to rebuild it. For Centos/RH, that means running   "yum reinstall glibc-common" after fixing /etc/yum.conf.


Split overview card units and label

Previously, card hero numbers had units and labels on the same line. This change splits the units and labels onto different lines.
We want to mimic this Azure layout for all cards on all tabs.

Also added units to all hero numbers, where we had (intentionally) omitted them.
Mocks: https://marvelapp.com/1jj511j6/screen/63870434

Codecov Report

Merging #1191 into master will decrease coverage by 0.49%.
The diff coverage is 28.12%.

@@            Coverage Diff            @@
##           master    #1191     +/-   ##
=========================================
- Coverage   75.43%   74.94%   -0.5%
=========================================
  Files         229      229
  Lines        4421     4466     +45
  Branches      836      860     +24
=========================================
+ Hits         3335     3347     +12
- Misses        968     1002     +34
+ Partials      118      117      -1

Impacted Files
Coverage Δ

src/store/azureDashboard/azureDashboardWidgets.ts
100% <ø> (ø)
:arrow_up:

...rts/awsReportSummary/awsReportSummaryAlt.styles.ts
100% <ø> (ø)
:arrow_up:

src/store/ocpDashboard/ocpDashboardWidgets.ts
100% <ø> (ø)
:arrow_up:

src/store/ocpDashboard/ocpDashboardCommon.ts
95.65% <ø> (ø)
:arrow_up:

...ocpReportSummary/ocpReportSummaryDetails.styles.ts
100% <ø> (ø)
:arrow_up:

.../ocpOnCloudDashboard/ocpOnCloudDashboardWidget.tsx
72.6% <ø> (ø)
:arrow_up:

src/store/awsDashboard/awsDashboardWidgets.ts
100% <ø> (ø)
:arrow_up:

...rtSummary/ocpOnCloudReportSummaryDetails.styles.ts
100% <ø> (ø)
:arrow_up:

...azureReportSummary/azureReportSummaryAlt.styles.ts
100% <ø> (ø)
:arrow_up:

...e/ocpOnCloudDashboard/ocpOnCloudDashboardCommon.ts
95.65% <ø> (ø)
:arrow_up:

... and 9 more

Continue to review full report at Codecov.

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


SCCM device discovery and inventory maintenance suggested improvements

SCCM system discovery works very well once you get your non-windows objects out of your discovery OU's so they don't keep getting discovered.
That said, when you are doing lifecycle or rebuild operations in your environment you can end up with a lot of stale records. These are NOT the laptops that go offline for 3 months and then come back...these are systems that have been rebuilt from W7 to W10 or from W10 LTSB to W10 {current release}. Unless sccm cleans itself up vs AD then the objects stay there until the maintenance job clears them out, and you can't have it be aggressive with AD discovered objects separately from inactive objects.
I would suggest that if a system is ADDED by AD System Discovery, it should be REMOVED by the same process when the AD object is removed. This basically means if a system is deleted from AD, and it was added via AD discovery, it will automatically be removed from SCCM when deleted from AD. Or at least the next time system discovery is run, if it's not there, it will be removed.
For workgroup machines, they should have to be manually removed or aged out.
For inactive machines & laptops that go on vacation, the existing maintenance aging jobs are just fine.
Some systems have a concept of "how added" which i observe in this schema as well. Using the "how added" to also "how removed" is what we are asking for here.
This prevents us from having to hack scripts on every site server to remove things that are in SCCM but NOT in AD anymore. Everyone is probably doing this exact same thing.

Thanks @chadparris for taking the time to provide feedback on Configuration Manager! This is an interesting feature idea, and I want to make sure it gets directly into the hands of the engineering team. Fortunately, we've got dedicated channels for that very purpose. :) See the Product feedback section in our docs. I think it’s important that you submit it directly, because that allows you to receive notifications and more closely monitor the progress. I'm closing this issue as there's nothing actionable for docs at this time.


Integrate Tendermint mempool

Resolves #5.

Codecov Report

Merging #34 (2331bb5) into main (e553342) will increase coverage by 6.41%.
The diff coverage is 49.27%.

@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
+ Coverage   43.82%   50.24%   +6.41%
==========================================
  Files           4        6       +2
  Lines         251      412     +161
==========================================
+ Hits          110      207      +97
- Misses        123      172      +49
- Partials       18       33      +15

Impacted Files
Coverage Δ

rpcclient/local.go
27.16% <35.48%> (+20.91%)
:arrow_up:

node/mempool.go
51.61% <51.61%> (ø)

node/node.go
58.82% <65.11%> (ø)

p2p/client.go
72.58% <100.00%> (+0.22%)
: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 e553342...2331bb5. Read the comment docs.

I'm marking this as ready for review. For better visibility I'll create separate PR to remove use of reflect (ref: #38).
Currently I'm working on testing, so more tests will also be submitted in another PRs. Available unit test shows that after BroadcastTx executed against one node, another node receives Tx via full stack (RPC, ABCI/Mempool, P2P).


Algolia search results PAGE not returning any results

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
I enabled algolia search on my site: https://react-uploady.netlify.app
The modal works fine and returns results for existing search terms.
For example:

However, when clicking the "see all results". The search page always shows NO results:

I noticed that when contextualSearch was enabled, I also got no results in the modal. When I set it to false the results started showing.
I think there are values being sent from the page that arent being sent from the modal.
This is the query data from the modal:
{"requests":[{"query":"provider","indexName":"react-uploady","params":"attributesToRetrieve: ["hierarchy.lvl0","hierarchy.lvl1","hierarchy.lvl2","hierarchy.lvl3","hierarchy.lvl4","hierarchy.lvl5","hierarchy.lvl6","content","type","url"]
attributesToSnippet: ["hierarchy.lvl1:10","hierarchy.lvl2:10","hierarchy.lvl3:10","hierarchy.lvl4:10","hierarchy.lvl5:10","hierarchy.lvl6:10","content:10"]
snippetEllipsisText: …
highlightPreTag: <mark>
highlightPostTag: </mark>
hitsPerPage: 20
facetFilters: []"}]}

While this is the query from the page:
{"requests":[{"indexName":"react-uploady","params":"hitsPerPage: 15
advancedSyntax: true
query: provider
page: 0
facets: ["language","docusaurus_tag"]
tagFilters:
facetFilters: [["language:en"],["docusaurus_tag:default","docusaurus_tag:docs-default-current"]]"},{"indexName":"react-uploady","params":"hitsPerPage=1
advancedSyntax: true
query: provider
page: 0
attributesToRetrieve: []
attributesToHighlight: []
attributesToSnippet: []
tagFilters:
analytics: false
clickAnalytics: false
facets: language
facetFilters: [["docusaurus_tag:default","docusaurus_tag:docs-default-current"]]"},{"indexName":"react-uploady","params":"hitsPerPage=1
advancedSyntax: true
query: provider
page: 0
attributesToRetrieve: []
attributesToHighlight: []
attributesToSnippet: []
tagFilters:
analytics: false
clickAnalytics: false
facets: docusaurus_tag
facetFilters: [["language:en"]]"}]}

Steps to reproduce

open https://react-uploady.netlify.app
use search modal to search for ex: "sender"
see results
scroll to bottom and click "see all X results"
see page with no results

Expected behavior
Page should return all results
Actual behavior
no results are shown
Your environment

Public source code: https://github.com/rpldy/react-uploady-docs
Public site URL: https://react-uploady.netlify.app
Docusaurus version used: 2.0.0-beta.15

Reproducible demo
https://react-uploady.netlify.app
Self-service

[ ] I'd be willing to fix this bug myself.

Duplicate of #5084, right?

I noticed that when contextualSearch was enabled, I also got no results in the modal. When I set it to false the results started showing.

That sounds like a distinct issue from the search modal sending incorrect requests, which we are aware of.

thanks @Josh-Cena
Indeed duplicate (GH issue search sucks) and disheartening that its still open

Is there no solution then for the search page yet? Or is the last comment something I can follow?
Yes, the contextualSearch param does seem to break the search. Thats what made me think to look at the params being sent from the search page

/cc @lex111 We may need to revamp the search page, now that you are already working on #6692.
We'll keep it open because of that contextualSearch issue. cc @shortcuts as well, if we can get any input on your side.

you added the search only 2 hours ago

Have you triggered a new crawl since enabling the search?

@slorber Search works in the modal consistently. This also seems to be the same issue reported in #5084
Are you suggesting that for the same term working in modal, not working in page, can be related to crawling?

@slorber Search works in the modal consistently.

You said they do not show if you turn contextualSearch on.
Yes, you have to follow the doc and trigger a crawl or wait 24h. If contextual search doesn't work, then you have a deeper problem because the search page somehow always use contextual search (we'll change that)

Hey,
As @slorber said, the issue is that the search plugin was not enabled before crawling your website, which make contextualSearch unusable.
To solve your issue:

Keep your search plugin enabled
Enable contextualSearch
Start a new crawl from the crawler interface https://crawler.algolia.com/
Enjoy searching from both the modal and the search page :D

because the search page somehow always use contextual search (we'll change that)

It would indeed be nice to make it follow the config value

Okay! In that case, closing as duplicate of #5084. Hope we can get this fixed up soon...

I know this issue is closed as it is a duplicate of #5084, but I wanted to chime in here and say that I am also experiencing the same issues as outlined above.
The modal search will only return results if contextualSearch is set to false.  The /search page does not return any results.
I have tried to debug this issue according to the suggestions from the Discord servers for Algolia DocSearch and Docusaurus, and so far nothing has worked for me.
I am hoping there is a fix soon, thank you.  🙏
@Josh-Cena @shortcuts

Hey @huynhicode,
Are you using your own crawler our the Algolia Crawler?
The contextualSearch option requires a few things to work:

Having docusaurus_tag, version and language in the attributesForFaceting (see Docusaurus v2 config template)
The steps describe in https://github.com/facebook/docusaurus/issues/6693#issuecomment-1041545752

Feel free to provide more infos about your crawler/Algolia app, I'll check if the steps above doesn't help.

thanks @shortcuts and @slorber, I can confirm the steps you described solved the issues. contextual works now on both modal & page 🔥

Thanks @shortcuts, we have this set as the configuration for attributesForFaceting.
Currently, the code exists on a local branch.  I am hesitant to push code that is not working locally, but it seems like the crawler needs to crawl a public URL with the Algolia search code.

@huynhicode you can also trigger a crawl on a deploy preview or staging deployment if you need to reduce the risk
In https://github.com/facebook/docusaurus/pull/6707 I change this behavior for next release: your index should contain correct Algolia metadata in all cases (after a crawl of course) even if your site in production doesn't have the Algolia plugin/config activated. Hopefully this will help reduce this confusion

Thank you @slorber
We will deploy our code to staging to test.  Will reach back out if we encounter further issues.
Appreciate all the help!

We were able to get our modal and /search page working!  🎉
Thanks everyone for your help!  @slorber @shortcuts

I have the same issue. Our search is working in the dialog but not on the full page.
I'm working on a fix here: https://github.com/nhost/nhost/pull/716 and tried to follow the steps in this issue:

enabled contextualSearch (see PR above)
Updated the Algolia crawler config:

  initialIndexSettings: {
    nhost: {
      attributesForFaceting: [
        "type",
        "lang",
        "language",
        "version",
        "docusaurus_tag",
      ],
      attributesToRetrieve: [
        "hierarchy",
        "content",
        "anchor",
        "url",
        "url_without_anchor",
        "type",
      ],

Deplied a preview environment: https://docs-git-docs-algolio-fix-nhost.vercel.app/

Result: Search stopped working in the modal. The full-page search does not work.
Could someone hint me in the right direction to fix this?

Hey @elitan, initialIndexSettings are applied at index creation time, so you might need to delete your index from the Algolia dashboard (https://www.algolia.com/apps/YOUR_APP_ID/dashboard) and restart a crawl, everything should work after this.

Thanks. I got it working. I did some permutation of steps. But in the end, I think these were the steps:

Delete the current index (nhost).
Copied the v2 config from https://docsearch.algolia.com/docs/templates/#docusaurus-v2-template. Updated with appName, apiKey, and index name (nhost).
Re-run crawler (will create the index for me).
Redeployed my Docusaurus site.

The contextualSearch option requires a few things to work:

Having docusaurus_tag, version and language in the attributesForFaceting (see Docusaurus v2 config template)
The steps describe in Algolia search results PAGE not returning any results #6693 (comment)

Feel free to provide more infos about your crawler/Algolia app, I'll check if the steps above doesn't help.

@shortcuts @slorber Oh my goodness, thank you both so much for this fix! I was facing the same issues as the others here and stumbled upon this thread. Both my modal and search page are working now. 🥳

Is the docusaurus v2 template still the one to use nowadays or should the v3 be used?
In any case, tried both. I used the template in Algolia, updated my keys and index name, double checked the tags docusaurus_tag, version and language, restarted an indexing but, nothing worked out.
Even worth, if I enable contextualSearch the all search does not work at all anymore.
Really confuse about what is the correct configuration 🤔.

Finally, I was able to solve it! Even though I followed exactly the steps provided by @elitan in this answer, including deleting the index, using the template v2, reindexing, enabling contextualSearch, and redeploying, the problem persisted.
Eventually, I realized that despite these steps and the presence of the fields in my crawler, the attributesForFaceting configuration in the index was actually not populated correctly (🤷♂). So, I manually added the required fields in the UI and initiated a reindexing, which ultimately resolved the issue.

Is the docusaurus v2 template still the one to use nowadays or should the v3 be used?

I recently asked the Algolia team for the creation of a v3 config, but for now, it's exactly the same as v2. It may start to diverge later.

the attributesForFaceting configuration in the index was actually not populated correctly

That's weird, we definitively this to be populated correctly for our search to work. Worth reporting a bug to the DocSearch team.

Following the comments here was able to get this to work after updating my Crawler to use the v3 config. I applied for the open source program so the crawler was created for me with the wrong config settings.
I updated it based on their site to use the v3 config but still ran into issues. The problem I had was I was initializing the index myself and letting the crawler fill it.
The fix was to let the crawler create the index for me because there are settings it fills only on initial creation. I found that by re-reading thru this issue and found this comment: https://github.com/facebook/docusaurus/issues/6693#issuecomment-1158568333

I use Docusaurus V3.

I used crawler config from here
In docusaurus config I have contextualSearch: true,
In index config in Filtering and Faceting I added Facets docusaurus_tag, edition, lang, language, type and version

Only after step 3 it started working

Yes faced similar issue. I use V3 and my algolia docsearch got approved today. I was first facing issue

Had to use crawler config from v3 template
In docusaurus config I have contextualSearch: true my config
Delete existing index and retrigger crawling
Now both search and modal works perfectly fine.

ignoreCanonicalTo: true in the crawler config is critical else pages were getting ignored.

No search result?
For anyone passing by, if you don't get any Algolia search results:

make sure that your Algolia index has the fields in the screenshot below
If you don't see these fields, then you have an index config problem
You should check your crawler config, make sure it matches the recommended one, and then delete/recreate your index based on the newly updated/fixed crawler config (Algolia team recommendation)

See also: https://github.com/facebook/docusaurus/discussions/10007#discussioncomment-9021352

Thanks @randombeeper
we have recently added some docs here, let me know if this looks good:
https://github.com/facebook/docusaurus/pull/10056
https://docusaurus.io/docs/search#algolia-troubleshooting

Respectfully 🙏 I think that all of the troubleshooting comments here are off the mark.
If I set contextualSearch: false in my docusaurus config file, I expect that to apply to both the search modal and the search page.
Every solution on this page is based on the pretext of  ignoring this error and forcing users to configure their index for use contextual search, as though this is somehow easier than making the search page respect the config settings and send the same request format as the modal.
If the intention is to force all users to configure and use contextual search (even if it is not necessary for their use case), then the contextualSearch option should be removed from the config file and documentation.
If the intention is to allow users to disable contextual search, then the search page should be updated to respect the config file.
It seems that all the advice here is simply a very complicated workaround to what should be a simple solution.
Make the search page respect the contextualSearch config and send the same request that the modal does.

If the intention is to allow users to disable contextual search, then the search page should be updated to respect the config file.

The problem is tracked here: https://github.com/facebook/docusaurus/issues/3805
The only reason the search page does not respect the config is because we maintainers have limited time. Fixing it requires a quite significant refactor of some very old legacy code (pre 2020, not even written by me). And the ROI is limited considering this page is not widely used.
If anyone wants to contribute a fix to the search page, PRs are welcome. Unfortunately I can't make it a priority right now, but we'll come to it someday.

I experienced the same issue today, it was happening on one of my sites. It's kind of weird because my other 3 sites use Algolia DocSearch too and it works smoothly right after initial setup.
@peterpeterparker's solution works fine. I managed to resolve this issue by simply adding the docusaurus_tag under attributesForFaceting. Just it, no additional steps are needed on either Algolia's website or docusaurus config file.

This issue was resolved in a pull request 4 days ago and should be included in the version 3.4 update. What version of Docusaurus do you have?


Referrer policy

Standard: http://www.w3.org/TR/referrer-policy/
Browsers are starting to support Referrer policy through meta tags. Firefox seem to support the new (and preferred) keywords, while Chrome seems to only support the old ones.
Support is also underway in IE. http://dev.modern.ie/platform/status/metareferrer

This is cool, I can remove my HTML helper from Boilerplate. I was going to implement a ASP.NET 5 tag helper for this. I won't if you have plans to do this.

Yes, this has been hanging around for a while, but the HtmlHelper will be included in the next relase.


freerdp/core/gcc: channel name hardening

According to [MS-RDPBCGR <IP_ADDRESS>.4.1 Channel Definition Structure] the channel name must be an 8-byte array containing a null-terminated collection of seven ANSI characters that uniquely identify the channel.
We did not check if the transmitted name was null-terminated which could have the usual severe effects on stability and security since the channel name is used in several functions expecting a null-terminated string (strlen, printf, etc.)

Strange I would have swear that it was not null-terminated on purpose. Is it possible that the specs have changed on this point ?
+1 otherwise

@hardening I don't remember. And regarding null-termination in general the rdp protocol is a real mess with unclear specs and violations by Microsoft's implementations all over the place. However, at least here the specs, headers and implementations seem sane.


add Wroclaw's public schools

@Kisiekx First stage of verification passed, official domain is wroclaw.pl as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Kisiekx This domain doesn't represent a university or college. Apply for a free educational license using the "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
To apply on behalf of City of Wroclaw or State educational authorities, email us at<EMAIL_ADDRESS>We require prior discussion with responsible representatives for large groups of schools.
I have to close this request without merging. Thank you for your understanding.


Can surface loss be understood in following not efficient but simple way?

Thanks for sharing the code.
I very enjoy your nice idea and reading your paper.
But I'm confused about the implementation of surface loss.
In section 2 of the paper, it said "boundary loss in Eq. (5) is the sum of linear functions of the regional softmax probability outputs of the network".
Without regard to the efficiency of the code, can surfaceloss be understood in following way?
# inputs (2D/3D):
    # ground_truth
    # cnn_prediction: softmax output
# outputs: surface_loss

# precompute the level set function
gt_onehot = class2one_hot(ground_truth)
gt_dist = one_hot2dist(gt_onehot)

def surface_loss(CNN_prediction, gt_dist):
    cnn_pred_onehot = class2one_hot(CNN_prediction)
    loss = np.mean(cnn_pred_onehot, gt_dist)
    return loss

Looking forward to your reply.
Best regards,
Edward

Should be np.mean(cnn_pred_onehot * gt_dist) (probs a typo), but yes this looks like a correct simplification of what we do.
The code is a little bit more complex, because we select which classes should be supervised with the surface loss.
one_hot2dist will compute one distance map for each class. For a problem with 4 classes, 0 being the background, maybe you want to compute the surface loss only wrt the distance maps of classes 1, 2 and 3. Or maybe all of them, or maybe only for the class 2.  So self.idc is the list of classes that you should supervise with this loss (self.idc = [1] in the paper experiments as we sticked to binary problems).
Then, I use einsum so I can easily remember the shape of my tensor when I come back after a while (bcwh standing for batch,class,width,height). It will also explode if I feed by accident a tensor with less or more axises than 4, which makes debugging easier.
Let me know if some parts remain difficult to understand.

Hi @HKervadec , thanks for your quick response very much.


There are no explode fonctions form Hatch to List

Hello,
I would like to know if there will be a function that allow netdxf to explode the Hatch entity into a list of lines? Like Lwpolyline
public List<EntityObject> Explode();
BR
Lionel Peeters

Cannot say, you can request a feature but I cannot tell you when or even if I will implement it.

When processing Hatch objects, the internal Pattern is difficult to achieve. I don't know if I will explode Hatch into basic line segments in the future?

@chaoslife I do not know either.

Any news on this? I wish a could draw the hatches patterns as lines.


Add a Fyne GUI option that adds a GameBoy feel

It also recolours pixels to match the original palette
perhaps that should be part of the internal graphics?
Fixes #12

Oops, this had 2 different items in, apologies


Update for podfile

The new version of RN will automatically add ART lib in the pod file when installing @react-native-community/art


upgrade to the latest stable action version

upgrade to the latest stable action version
fix https://github.com/dart-lang/ecosystem/issues/108

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

From the health workflow:
...
Found packages [package:firehose 0.3.22-wip (dir=/home/runner/work/ecosystem/ecosystem/current_repo/pkgs/firehose), package:dart_flutter_team_lints 1.0.0 (dir=/home/runner/work/ecosystem/ecosystem/current_repo/pkgs/dart_flutter_team_lints)] at Directory: '/home/runner/work/ecosystem/ecosystem/current_repo'
The files of interest are []
Found packages [package:firehose 0.3.22-wip (dir=../base_repo/pkgs/firehose), package:dart_flutter_team_lints 1.0.0 (dir=../base_repo/pkgs/dart_flutter_team_lints)] at Directory: '../base_repo/'
The packages of interest are []
...

We might need to adjust the set of files we consider for various checks? I.e., we probably want all dart files checked for copyright headers, but only publishable packages checked for changelog updates.


set dotSize

Hey there.
First of all, thanks for the awesome work !
signature_pad it great !
but today i find a little question about dotSize.  I need let users to set dot,so I get the value from a range,
As we all know ,the value is String ,but I ignore it,when i find in the source code,i understand i Make mistakes,the dot return  a Unexpectedly value.(not waring ,no error ,so i Spend some time to find why)
this.dotSize = opts.dotSize || function () {             return (this.minWidth + this.maxWidth) / 2;         };
maybe it's better
        this.dotSize = opts.dotSize || function () {             return (parseFloat(this.minWidth) + parseFloat(this.maxWidth)) / 2;         };

I need let users to set minWidth,maxWidth ,not dot

First, dotSize is not set at dotSize but at "_strokeWidth";
Finally, you can alter it by the passed in object: see code below:
    var signaturePad = new SignaturePad(document.getElementById('signature-pad'), {
        backgroundColor: 'rgba(255, 255, 255, 255)',
        penColor: 'rgb(0, 0, 0)',
        maxWidth: 20 /* this makes it fatter!!! */
    });


Retry PR for interpreter mismatch on open

For #10926, #10953
The initial interpreter for a kernel spec was not being used for a notebook.

Codecov Report

Merging #10994 into master will decrease coverage by 0.01%.
The diff coverage is 9.09%.

@@            Coverage Diff             @@
##           master   #10994      +/-   ##
==========================================
- Coverage   60.75%   60.73%   -0.02%
==========================================
  Files         583      583
  Lines       31717    31760      +43
  Branches     4518     4532      +14
==========================================
+ Hits        19270    19291      +21
- Misses      11461    11484      +23
+ Partials      986      985       -1

Impacted Files
Coverage Δ

.../datascience/interactive-common/interactiveBase.ts
5.54% <0.00%> (+<0.01%)
:arrow_up:

src/client/datascience/jupyter/jupyterNotebook.ts
4.24% <0.00%> (ø)

...ient/datascience/jupyter/kernels/kernelSwitcher.ts
90.14% <ø> (+1.09%)
:arrow_up:

...ascience/jupyter/liveshare/guestJupyterNotebook.ts
10.29% <ø> (+0.14%)
:arrow_up:

...datascience/jupyter/liveshare/hostJupyterServer.ts
11.47% <0.00%> (ø)

src/client/datascience/types.ts
100.00% <ø> (ø)

...ient/datascience/interactive-ipynb/nativeEditor.ts
11.49% <20.00%> (+0.21%)
:arrow_up:

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-5.89%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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


Empty Collection Contents - Unable to refresh

When UICollectionView is empty or there are a few contents not as many as enough to scroll, CR is unable to refresh.

Set the the collectionView's alwaysBounceVertical property to true

Hi, VasApps.
Thank you for your help.
it works very well.
UICollectionView seems not alwaysBounceVertical in default.
So I set the UICollectionView's alwaysBounceVertical property to true. Then it works to refresh.
Cheers.

Yeah I had that same issue and realized without any items it doesn't bounce unless that property is set. Glad to help!
Cheers!


add metadata auth framework.

Modeled after Max's pull request. Checks authorization of metadata based on either file or dataset.

Need to be updated after #354 gets merged

Will update once that is merged.


Hi team, when I excuted my code, the result's tab wasn't appeared but the message's tab was appeared. So reaason why? And how I could result it.

[Enter feedback here]

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

ID: 0ee54bb6-2c60-0d08-69e1-39022b0a357e
Version Independent ID: 3962c09d-95a0-19d1-dd61-5165355cac07
Content: Use Visual Studio Code to connect and query - Azure SQL Database & SQL Managed Instance
Content Source: azure-sql/database/connect-query-vscode.md
Service: sql-database
Sub-service: connect
GitHub Login: @dzsquared
Microsoft Alias: drskwier

@stephen-kh
Thanks for your feedback! We will investigate and update as appropriate.

In the messages tab - what are the messages you see?
If you were expecting to see rows but got only messages - the messages likely contain an error message.
Are you following a specific tutorial?  The page you linked has these prerequisite steps (https://learn.microsoft.com/en-us/azure/azure-sql/database/connect-query-vscode?view=azuresql#prerequisites) but the database you have connected to does not appear to be the required AdventureWorks sample database.
If the database you're connected to is currently empty, you'll need to start by adding tables/objects.


Explicitly ignore Avalonia samples to build as nugets

The test build showed that nuget packages were generated for the Avalonia samples. This should not happen.
The current configuration for packing is that the Directory.Build.props has it set to false and all projects that need to be packed have IsPackable set to true.
For the Avalonia samples this system apparently failed because it has it's own Directory.Build.props. So, this fix also set IsPackage to false in that file.

I tested this by running the pack command locally.


Implement basic Spark Driver with docs

Including yaml configuration mechanism for Driver (also used to configure tests and to remove SparkTestConfiguration class)


Feature/#359 - Use ruff

https://github.com/Avaiga/taipy/issues/359
TODO:

[ ] Revisit # type: ignore
[ ] Merge with new linter workflows and use ruff instead of other tools
[ ] Re-enable mypy since Ruff is a linter and mypy is a type checker

Approved for gui only and with a few comments


Sqlabugs

Addresses issue #643

LGTM at a glance. But avoid globals as @erikbern  said :)

LGTM except the global variable. Is it easy to fix?

@erikbern  I will move the global variables out. That's a good suggestion.
Let me give you some background around the changes I made. I want to get your advice on making the right fix for the problem I observed.
I saw that even though I had only 2 workers, all the tasks were getting created simultaneously. So if I had, say,  100 sqla.CopyToTable jobs, then that resulted in 100 objects creations and hence 100 connections all at once. After my modifications I was hoping that the two processes would hold the connection throughout the pipeline. But I noticed that the workers keep changing (based on the PID). Is that how it is supposed to work?
Overall I want to modify the create_engine part so that there aren't too many connections being made to the database. Do you have any suggestions for me .

That should not be the case I believe. Luigi should start one task per worker and wait for them to finish. Maybe you job finshes without closing the database connection? You maybe (my mistake) do something asynchronous in your run()?

If you only have two processes then there shouldn't be more than two simultaneous connections.
Note that Luigi might do some forking under the hood (at least between scheduling and execution) so you might end up with a broken connection in some cases. But I'm guessing sqlalchemy will handle the failure and reconnect

Let me try to create a small script to replicate this issue. Let us not merge this thing yet.

@erikbern I have fixed some of the other issues I encountered. I have also removed the globals. Take a look!

@erikbern I am getting some errors after removing the globals. Let me see if I can fix.

Would be good if you can run all your tests twice: one with n_workers=1 and one with n_workers>1 just to make sure it works with more than one process

@erikbern  Where should I use the n_workers? Should it go part of luigi.build() in the tests?

sure, sounds good!

@erikbern I have added tests for the different num workers.

Looks like you're failing pep8 checks, which should be easy to fix!

Still a pep8 issue. You can try it locally using pep8 --ignore E501 luigi test examples bin.

@erikbern I like the os.getpid() idea. How do I get the dict shared across processors?
I will fix the pep issues. I know the PR has been long, but lets get it right! I like that the functionality has improved substantially through this PR.

@erikbern I tried sharing engines using the multiprocessing.Manager().dict(). I get expected string or Unicode object, NoneType found exception. This I think has to do with the fact that the sqlalchemy engines may not be pickleable.

You shouldn't share engines, across processes, you want to make sure they are different.
Note that multiprocessing forks processes so it might be enough to just set SQLAlchemyTarget._engine = None and then create it in def engine. That way you don't have to mess around with multiprocessing or pids.

I have this working on my end. Let me fix the conflicts and do some more testing.
BTW, is there a good place to put a link to a blog post with a tutorial on using the SQLA module?

@erikbern How do I find out if any tasks failed after I do luigi.build([])  in tests?

I think luigi.build will raise an exception if any task fails?

I think luigi.build doesn't throw an exception. I had test cases that were marked as passing. I dug into the logs to discover there were failures.

Yeah looks like it returns whether all tasks succeeded.
We could add a flag to let it raise if something fails?
Otherwise you can use luigi.run which should raise if it fails

@erikbern Thanks for the info.
I have been having issues running the current version of the code in my production environment with MySQL database. I think I have a hunch on the issue I am facing with the current code. I think that when I use static class variables as a means to create_engine, it is possible that when it forks, every process doesn't get a connection of its own. However when I used the module level global variable set to None and then checking that to create an engine, things seem to work fine.
I am not sure if there is a work around. I am not a fan of globals but I don't know how to avoid it.

@erikbern Can you take a look at the latest commit? This removes all the globals.
It is my understanding that the workers are forked after the initial engine creation. So now I check for the pid of the engine with that of the process running the job.

This looks great now, thanks!
 There are 29 at the moment. I can merge when you have rebased!

See #742


no insignificant zeroes in barsBeatsSixteenths

fixes #246

thanks but please make the PR on the 'dev' branch

@tambien my bad!


Game

https://docs.github.com/en/github/site-policy/github-community-guidelines#building-a-strong-community

Game


Wormhole-v1 received WWT token after bridging WETH from Phantom to Metamask

Dear Wormhole Developers!
I tried to bridge WETH (Sollet) from Phantom to Metamask (Ethereum) yesterday and received a worthless WWT token which cant be swapped or used for anything.
Here is the process on the Explorer:
https://explorer.solana.com/tx/2pNjByVfnm6XxxiDCz7yhb5Kvj8NvRYdyih72jJwbrD89GgorM1pJaYEgokWZwKf4XybT54nEoiUQHTvXKK1kh59
Is it possible to bridge it back to Phantom or is it stuck forever?
Thank You!
Best regards
Stefan

managed to bridge it back - can be closed


Doc content for 0.1.0

Tracking bug for adding docs for the 0.1.0 release.

I listed a few suggestions below. I'd be happy to assist.
Whatever direction you decide to go, I hope you'll at least permit me to submit a small PR against the README ... stomp around with my big dinosaur feet a bit and fix it up! :smile: (The Wiki FAQ could use a light pass as well. I can send you a corrected text file.)
Description Recommendation
Consider changing the repo description to ...

Blazor is an experimental .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.

Hosting Recommendation
@danroth27, you mentioned using the repo Wiki. I suggest using a separate repo and GH Pages so that PRs are possible. After all, I can't help if I can't help. :smile: ... nor can anyone else.
"Steal" the official docs/DocFX theme so that it brands with .NET products/docs. I'm not talking about building docs ... I'm just referring to the layout and style of the static content. I can help (or lead) on setting this up if you like.
Content Recommendations
Landing page content
Sidebar: TOC

Define and describe Blazor (Ref: README)
Experimental note
Why use Blazor? (benefits and features; link to FAQ)
List work-in-progress (link issues if possible)
List upcoming features (link issues if possible)
Seek to enlist the aid of the community
Next steps: Link to Introduction, FAQ, and Get started

TOC
Use official TOC structure to simplify transitioning to the official docs later if Blazor becomes a real thing :crossed_fingers:. For example, use folders with an index pages for area expansions, _static asset folders, sample sample folders, etc. Follow the official style and grammar guidelines throughout. This will vastly simplify things later. Besides, u want this to :guitar: ROCK! :guitar:, right? :+1:

Introduction (Ref: Steve's post).
FAQ (Ref: Wiki FAQ)
Get started (Ref: README): Prereqs, Build, Run tests, Run end-to-end tests, Run all tests, Build VS tooling, Use VS tooling
Tutorials

Build a Blazor app with Visual Studio
Build a Blazor app with Visual Studio Code (possible today?)
Build a client-server Blazor solution with Visual Studio
Build client-server Blazor projects with Visual Studio Code (possible today?)

Fundamentals

TBD: Subjects such as configuration, app startup, Razor concepts, functions, routing, app state, logging, error handling, etc.

Test and debug
Data access
Security
Performance
Host and deploy

Host on the Azure CDN
Host on a file server
Host on Azure App Service or on an IIS/Linux server

Hosting app configuration
Link to the Servers, Hosting, and Host and deploy topics in ASP.NET Core docs

Directory structure (of Blazor assets)

Common errors reference
Release notes
Contribute

@guardrex FYI I started a small docs project for Blazor at https://learn-blazor.com/ (work in progress!). It should help people as long as no official documentation is available. Later, I will probably use some of the content in trainings and workshops that I will do. Feel free to reuse content and/or contribute.
Greetings,
Rainer.

@rstropek Great job! I fleshed out the Fundamentals list with some of your content areas.
Was your intention to maintain a parallel doc set, or were you interested in moving that content into topics in the doc set that they might establish?
Note that I don't currently have anything to do with this project. I'm a contractor working on the ASP.NET Core docs team. However, I would like to work on this doc set in my spare time. At this point, I'm just offering my services to @danroth27, @SteveSandersonMS, and the gang.

@rstropek
Awesome site and great examples. I think this will definitely help for people who want to get started with Blazor.

We've decided to go ahead and put the Blazor preview documentation on docs.microsoft.com with the ASP.NET Core docs under the client-side development section. Moving this issue to the https://github.com/aspnet/docs repo.
The Blazor node and pages should clearly indicate that these are preview docs for an experimental framework.
@guardrex If you want to go ahead and start working on this that would be great!

This issue was moved to aspnet/Docs#5678

Nice!!!

Great work on that website @rstropek !!


Update angular-moment.js

updated changeLocale method in amMoment service so that it can accept Calendar strings customizations
http://momentjs.com/docs/#/customization/calendar/

Coverage decreased (-0.62%) when pulling 1ea0c77bc84c9c35409a09c3998707a9935d9f72 on vosi:patch-1 into 603410ef0ab70f085d1d662a8959ef46e557c888 on urish:master.

Coverage increased (+0.03%) when pulling d80936c8154c6dd403fa94ddf784736031b7decf on vosi:patch-1 into 603410ef0ab70f085d1d662a8959ef46e557c888 on urish:master.

Thanks!


Link to HTML/Image not rendering properly

What happened?
Hi, first of all, great job with the library!
Coming back to the issue at hand, the links to HTML outputs (DataFrames) and Images do not work.
I have tried the default MacOS terminal, iterm2, and the terminal integrated into VS Code.
All of them look like the sample provided in the output field.
It happens with all the Notebooks I have (also saved using Jupyter Notebook and not VS Code).
nbpreview version
nbpreview 0.8.1
Output
8;id=410413;file:///var/folders/jg/42cx8xxn6_s1kcdc594gmf_w0000gn/T/tmprg7rbhah.html🌐 Click to view HTML8;;
Notebook
No response
OS
macos
Terminal
terminal/vs code terminal
Python version
Python 3.8.10

Hey @erykml, thanks for the report!
To be clear I expect hyperlinks to only work on supported terminals. To my knowledge, the default macOS terminal and integrated VSCode temrinal do not support hyperlinks. But iTerm2 >3.1 absolutely should (it's what I use).
Regardless of what terminal you use, I am surprised that you are getting that output though. It looks like nbpreview is actually doing what I want it to do, you can see that type of pattern as the expected output in the unit tests. But, I expected your terminal to format it nicely for you. For example, this is what it looks like on my machine when I try to render a link using macOS's default terminal. There is no clickable hyperlink, but I don't get the long path text you do.

One quick way to check this.
% python -m venv .venv
% source .venv/bin/activate
% python -m pip install rich
% python -m rich.markdown --hyperlinks <(echo '[Click me](https://github.com/paw-lu/nbpreview/issues/506)')

Temporary fix
This won't fix the hyperlink problem at all, but to make it less of an eyesore for now you can pass --no-hyperlinks to have nbpreview print out the entire path name, which you can click on in some terminals like VSCode, or --no-files to keep nbpreview to disable the feature all together. Both of these can be configured more permenantly by setting their respective enrivonmental variables NBPREVIEW_HYPERLINKS=0 or NBPREVIEW_NO_FILES=1.

Hi @paw-lu!
Thanks for the very fast answer! To answer your questions in order:

I am using iterm2 3.4.15 and rich-10.16.2
I have the built-in powerglyphs enabled (tried disabling, but the issue is still there)
when I execute the code you provided, I do have a nicely formatted and clickable link

Hopefully, this will help with narrowing down the issue! And thanks for the temporary fix :)

Thanks @erykml for helping me out with debugging!
New theory is that it's your pager. Are you using a custom pager (ie not less) or special commands?
Verify
To veriy that this is a pager issue. We can prevent nbpreview by writing to your pager with --no-paging.
% nbpreview --no-paging notebook.ipynb

If the issue has to do with your pager, then you should get working hyperlinks.
Debug
What do you have set for PAGER or other environmental variables that affect paging (like LESS).
% echo $PAGER

% echo $LESS

New fixes
Disabling paging
Like we mentioned above, you can use the --no-paging to diable nbpreview from outputting to your pager. Or set NBPREVIEW_PAGING=0 for a more permanent config.
Set a new pager
Set a pager that can interpret the escape codes given. Does less -r work for you?
% PAGER='less -r' nbpreview --paging notebook.ipynb

Hi @paw-lu,
No worries, happy to help!
Let me answer in order.

Using the --no-paging flag works -> the links are clickable and nicely formatted + there is no looping behavior.
after running the two commands, I get less and -R respectively.
Running PAGER='less -r' nbpreview --paging notebook.ipynb works as well.

So based on those, seems like the pager is indeed at fault. Thanks for helping me out with this issue!

So based on those, seems like the pager is indeed at fault.

Eh, the issue is the pager, but I didn't expect you to have such a standard setup. I suspeceted you might be using some exotic pager, but your setup is what 98% of users will have. It's identical to what I have actually. I was hoping nbpreview would just work on setups like this.
Regardless, to be explict—for you and future users—you can fix this problem permentantly by setting PAGER in your startupfiles (.bashrc, .zshrc, .zshenv, .bash_profile, etc).
export PAGER='less -r'

This will also help with other clis as well.
But this is a pretty frustrating first-impression for a standard setup. Let's keep this open for now to see if we can measure how common this is.
Wonder if you have an older version of less? Kinda grasping at straws.


SSP crashes after I select a template

App Version: 1.0.15
Operating System: win32 10.0.22621
Error: Cannot read properties of undefined (reading 'username')
Stack: TypeError: Cannot read properties of undefined (reading 'username')
at de.renderTemplateSelection (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:1348747)
at de.render (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:1366760)
at Ps (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:178154)
at Is (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:177952)
at kl (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:221287)
at xd (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:209490)
at hd (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:209418)
at gd (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:209281)
at id (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:206088)
at dd (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:206477)
{"componentStack":"
at de (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:1342833)
at W (file:///C:/Users/david/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:1313827)"}

Same problem here

Same problem
App Version: 1.0.15
Operating System: win32 10.0.22621
Error: Cannot read properties of undefined (reading 'username')
Stack: TypeError: Cannot read properties of undefined (reading 'username')
at de.renderTemplateSelection (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:1348747)
at de.render (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:1366760)
at Ps (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:178154)
at Is (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:177952)
at kl (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:221287)
at xd (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:209490)
at hd (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:209418)
at gd (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:209281)
at id (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:206088)
at dd (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:206477)
{"componentStack":"
at de (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:1342833)
at W (file:///C:/Users/arzoc/AppData/Local/ssp/app-1.0.15/resources/app/.webpack/renderer/main_window/index.js:2:1313827)"}

Ty for reporting this . This is fixed in https://github.com/s-a/sonic-sound-picture/releases/tag/1.0.16 now


Bad behavior with limited internet connection

Issue Type: Bug
When starting vscode with limited internet connection (for instance with an active VPN connection to a company network, which limits access to certain hosts) vscode does not initialize fully (probably the update queries hang). This is especially a problem when launching a extension debug session. In this case the extension is never fully initialized and an error appears after 10 seconds. Additionally, after closing the debug instance of vscode the debug session is not closed and I have to manually stop it.
 (F1 > Developer: Restart With Extensions Disabled or code --disable-extensions)

Unfortunately, this is hard debug, because vscode doesn't do all the checks every time it starts up. Currently I see no issue, but I have seen this problem quite a few times before. Is it possible to force vscode to launch as if it wasn't launched for a while, so that it does all the checks in that case?
Side note: there is no F1 > Developer: Restart With Extensions, the closest that I could find is: Reload Window with Extensions Disabled, which only affects a single window.

This sounds like an extension might get hung up during startup. What is the error message you get after 10s?

Hmm, you are pretty quick with closing issues :-/. I mentioned that this is tricky to reproduce, since this check is done at will by vscode. I cannot trigger it manually. So I have to wait until this comes up again to tell you what you want to know.
Also, I asked you to give me feedback:

Is it possible to force vscode to launch as if it wasn't launched for a while, so that it does all the checks in that case?

which you completely ignored. Extensions don't play the main role here, for sure, because it doesn't happen all the time, but only when vscode does something in the background (indicated by that wait icon overlay on the Manage icon).

There is no way to tell it to do all checks. You could try with a new user data dir, because then it does not have any previous data: code --user-data-dir=<path-to-new-folder>.

Thanks to reconsider the closing decision. Unfortunately your instruction didn't help to verify the problem. No attempt was made to check for updates or similar. The IDE was immediately ready for work.
I guess if there's nothing else how we can force vscode to behave like it does when updates are checked then we have no means to verify the issue. We will have to wait until it happens next time (which can be weeks from now). So I leave it to you to decide to close this issue, in which case I will open a new one, once I have more information, or to wait until this happens in this issue at hand.

I have some news now, as today it happened again. First, the error message I see on the extension host is pretty well known:

Extension host did not start in 10 seconds, it might be stopped on the first line and needs a debugger to continue.

And I get an error in the debug console, when I waiting a while (the extension host was closed automatically):

Error: connect ENOENT /var/folders/03/gj5f1gl92w11zc3l2c526dnm0000gn/T/vscode-ipc-43472bb2-2556-488c-821b-298afd286918.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1113:14)

Then I tried again and reloaded the window with extensions disabled. This made it indeed work, but the funny thing is: extensions are not disabled, at least not the one I'm debugging. This time I also recreated the issue that the extension debugger hung. After some seconds it stopped here:

and I got:
NodeError: Channel closed
    at process.target.send (internal/child_process.js:628:16)
    at n (/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js:5:802)
    at Console.true.process.env.VERBOSE_LOGGING.console.log (/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js:5:894)
    at i.startExtensionHostProcess.catch.e (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:786:48)
    at process._tickCallback (internal/process/next_tick.js:68:7)
Emitted 'error' event at:
    at target.send.process.nextTick (internal/child_process.js:632:35)
    at process._tickCallback (internal/process/next_tick.js:61:11)

The next test was to disable all my extensions, restart vscode and restart the extension debugging session. However, the same problem occured. The only extension that was active in this moment was the one I debugged (even though it said a reload would be required, which was a bit confusing). Also here: when I reloaded the window with extensions disabled, things started to work (well, in a way). My extension still was shown as requiring reload, though. And it was still active.
The functionality of the extension was available, but while I continued to write this comment the extension host was again auto closed and the debugger hung. I killed the session and restarted extension debugging, which now shows odd behavior. It opens an empty window and I have to reload the previous folder I used to test my extension. But even if it looked as if things would work, after about 90 seconds I got the same events.js error as mentioned above. I didn't do anything, but wrote on this comment here. Seems in the background vscode still was on a timeout, which then kicked in.
Hope this helps to debug this issue further for you.

Does this only occur when you are debugging your extension?

@mike-lischke I am totally lost what your issue is. Can you explain to me in a short sentence, possibly with a screen cast or screen shots?
Here is what I think you see:

you have a slow internet connection (that should not play a role for VSCode)
you open VSCode
after 10s you see a notification that the extension host did not start

Is that it?

My understanding is that in-between 2 and 3 of @bpasero's steps you launch an extension in debug mode and that its extension host doesn't start in time

Does this only occur when you are debugging your extension?

I believe this also happens if I'm not debugging. Though, it's trickier to notice, since then you don't get any error message.

@bpasero I have pretty exactly described what happened and for me it's pretty clear what the issue is: vscode hangs and doesn't behave well. To me it looks as if a connection is blocked which vscode is not ready to handle well. I don't know if it is something caused by my extension (vscode-antlr4), as it loads remote web content (3D.js) but only if a web view is openened, not earlier. Or if it is purely a vscode issue. In any case, when I close the VPN, things return immediately to normal and stay so for a while.
Unfortunately, the behavior of vscode seem to change from time to time. Today I recorded a screen cast, however the new experience I have with this issue is different than before (in some aspects), but the overall issue is still there. First, here's a video where the extension host auto closed after a minute: http://www.soft-gems.net/files/vscode1.mov
After that I recorded a short one where I closed the extension host manually, to try to pause the debugging session (which failed, however): http://www.soft-gems.net/files/vscode2.mov

These videos are super helpful to understand the impact better, thanks.
However, my expertise in the extension host does not go as far to be helpful. I am not even sure why _tryExtHostHandshake would take > 10s and under which condition that could be. Leaving up to Alex, sorry.

Thanks @mike-lischke
I think this error message is revealing:
Error: connect ENOENT /var/folders/03/gj5f1gl92w11zc3l2c526dnm0000gn/T/vscode-ipc-43472bb2-2556-488c-821b-298afd286918.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1113:14)

The extension host is a separate process and the extension host communicates back to the renderer process via a named pipe. Before launching the extension host process, the renderer process begins listening on a named pipe, which looks like ${TEMP}/vscode-ipc-${UUID}.sock. The error message shows up in the debug console, so I think it is a message coming in from the broken extension host process. It appears that the broken extension host process cannot connect to the named pipe on which the renderer process is listening.
@mike-lischke Since you can trivially reproduce when enabling the VPN software and not when disabling it, my best guess is that your VPN software is intercepting all connect() system calls and, willingly or unwillingly, intercepts and blocks connect() system calls even to named pipes. Unfortunately, there is nothing we can do on our side if the two processes cannot talk to eachother and we correctly show an error box saying that the extension host did not start... well it did start but it did not talk back to the renderer process to let it know that it started...
Given what we know so far, I don't see any reasonable code change to do in VS Code except perhaps to do a dry-run connection from the renderer process to itself to test that connect() calls work correctly... But IMHO that is a bit overreacting as this is the first time we have gotten such an issue.
@mike-lischke Is it possible for you to look into the VPN software and check if it messes with named pipes? I would expect a lot of other software on your machine to have issues with that...

Thanks @alexandrudima for your explanation. Yes, from the anamnesis it's clear it must have to do with the VPN software (Cisco AnyConnect Mobility Client). The point that confuses me is that sometimes it works ok. Once I started the debug session without VPN in place, everything works ok for a while. Only when I didn't debug an extension for a couple of days and then do it again with the VPN being active the described behavior shows up.
That seems to indicated that vscode can well cope with this situation and only sometimes (under some other condition) things start to act strangely.
Maybe one day you feel like digging deeper into this (or a similar) issue, but for now I think it's better to close this one here.
Thanks anyway.


Reset website doesn't work

Describe the Bug
I go to settings > edit > data > reset website, enter RESET, submit, it says saved... data is not reset.
I tried clearing Chrome cache.
Database
Umami Cloud
Relevant log output
No response
Which browser are you using? (if relevant)
Chrome
How are you deploying your application? (if relevant)
No response

Sorry for the late response. Thanks for reporting, we have a fix for this that will go out next cloud release.

Fixed in v2.9.0.


[chore] Blog post announcing container generator GA on SLSA blog

The blog post went out today! https://slsa.dev/blog/2023/02/slsa-github-workflows-container-ga 🚀


Add initial Dockerfile

@gadinaor please review

@gliptak can you please share some context on the purpose or use case for this Docker file  ?

@gadinaor many tools (command-line) tools choose to have a Dockerfile or publish to Dockerhub allowing users to run the tool without local build environment setup. Below is example run:
➜ docker build --tag rbac-tool:latest .
Sending build context to Docker daemon  718.3kB
Step 1/11 : FROM golang:1.15-alpine as builder
 ---> 1de1afaeaa9a
Step 2/11 : RUN apk --no-cache add git make gcc musl-dev zip
 ---> Using cache
 ---> e562a0617e0b
Step 3/11 : WORKDIR /go/src/github.com/alcideio/rbac-tool/
 ---> Using cache
 ---> 2a1cfdcce020
Step 4/11 : ADD . /go/src/github.com/alcideio/rbac-tool
 ---> Using cache
 ---> 2873fb2e9bec
Step 5/11 : RUN make build
 ---> Using cache
 ---> de38e8ad3e24
Step 6/11 : FROM alpine:3.12 as prod
 ---> d6e46aa2470d
Step 7/11 : LABEL maintainer=alcideio
 ---> Using cache
 ---> 03164607d958
Step 8/11 : RUN apk add --no-cache ca-certificates
 ---> Using cache
 ---> 65a2f1a1edd7
Step 9/11 : COPY --from=builder /go/src/github.com/alcideio/rbac-tool/bin/rbac-tool /usr/local/bin
 ---> Using cache
 ---> e28f63a6db1d
Step 10/11 : ENTRYPOINT ["rbac-tool"]
 ---> Using cache
 ---> 31b620945d31
Step 11/11 : CMD ["help"]
 ---> Using cache
 ---> 651062f34c6c
Successfully built 651062f34c6c
Successfully tagged rbac-tool:latest
➜ docker run --rm rbac-tool:latest
rbac-tool

Usage:
  rbac-tool [command]

Available Commands:
  auditgen        Generate RBAC policy from Kubernetes audit events
  bash-completion Generate bash completion. source < (advisor bash-completion)
  generate        Generate Role or ClusterRole and reduce the use of wildcards
  help            Help about any command
  lookup          RBAC Lookup by subject (user/group/serviceaccount) name
  policy-rules    RBAC List Policy Rules For subject (user/group/serviceaccount) name
  version         Print rbac-tool version
  visualize       A RBAC visualizer

Flags:
  -h, --help      help for rbac-tool
  -v, --v Level   number for the log level verbosity

Use "rbac-tool [command] --help" for more information about a command.

@gliptak thanks !
This repo leverage goreleaser as the binary build and release.
It does have the ability to release docker images - so it would be best for us to make this enhancement using goreleaser.

@gadinaor as per the goreleaser documentation the first step is to create a Dockerfile
https://goreleaser.com/customization/docker/#how-it-works

That's correct - however the docker file doesn't need to take care of the rbac-tool binary build.
See example here: https://github.com/alcideio/iskan


Better Name?

collection-binder

How about "Bubbles"? If you think about it there are similarities with collections and data binding.

Bubbles are like views, there are plenty of them floating around.
Some bubbles disappear and the new bubbles come up just like the collection views.
Bubbles show the world around them, similar to data bounded views.
Bubbles rise up and disappear, similar to scrolled collection views.

So, what do you think? :--)


Observable reactive state being read outside a reactive context

I have simple component which is observer and have observable properties.
class SomeForm extends React.Component {
  someField = 'someValue';
  handleChange(e) {
    this[e.target.name] = e.target.value;
  }

render() {
  return (
  ...
  <Form.Control type="text" name="someField" value={this.someField} onChange={this.handleChange}/>
  ...
  )}
}
decorate(SomeForm, {
  someField: observable,
  handleChange: action.bound,
})
export default withRouter(observer(SomeForm));

Just trying to use mobx instead of setState in a hope it will make things consistent and simple. Getting tons of Observable reactive state being read outside a reactive context if observableRequiresReaction: true is set. I am guessing I got these errors because I am using  Form.Control which is indeed not an observer because it's react-bootstrap component. I have added:
<Observer render={() => <Form.Control ... value={this.someField}/>} />

to get rid of warnings. I am asking whether it's so called "idiomatic way" or I am missing something?

The <Observer> wrapper should not be needed.
Are there any mobx.configure calls in your code base?

I set as follows in App.js:
configure({
    enforceActions: 'observed',
    computedRequiresReaction: true,
    observableRequiresReaction: true,
    reactionRequiresObservable: true,
});

ok, so far it seems your setup is correct and this issue is indeed looks like a duplicate of #806. For now I recommend to disable observableRequiresReact, as it won't work together with react class components until that one is resolved.

Could you shed some light on actions also? If these directives are not mandatory, and it works without defining function as action, what a point of doing so?

see the actions documentation. Actions optimize batching and clarify the intend of the method.

@sammy007 that should've be solved on the latest release,
Please check and update/close the issue

Solved.

@mweststrate, @Bnaya
With enforceActions: 'always':
class MyStore {
    field = false;

    constructor() {
        if (...) {
            this.field = true;
        }
    }
}

Uncaught Error: [mobx] Since strict-mode is enabled, changing observed observable values outside actions is not allowed. Please wrap the code in an `action` if this change is intended. Tried to modify<EMAIL_ADDRESS>
Not sure I really should mark constructor as action though.

@sammy007 I think you are sort of contradicting yourself. If you want to enforce actions, then you should really use actions always. You cannot expect it would work selectively :)
class MyStore {
    field = false;

    constructor() {
        if (...) {
            this.initField()
        }
    }

    @action
    initField() {
      this.field = true
    }
}

Typically, the thing that create MyStore should be an action, as it is in
response to some event
On Sat, Feb 8, 2020 at 10:09 AM Daniel K<EMAIL_ADDRESS>wrote:

@sammy007 https://github.com/sammy007 I think you are sort of
contradicting yourself. If you want to enforce actions, then you should
really use actions always. You cannot expect it would work selectively :)
class MyStore {
field = false;
constructor() {
    if (...) {
        this.initField()
    }
}

@action
initField() {
  this.field = true
}

}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/828?email_source=notifications&email_token=AAN4NBFTQ6HAETZ6PRDAGHDRB2AGHA5CNFSM4KQZWXAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFONAQ#issuecomment-583722626,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBB5V4TBZVAZAHQAFH3RB2AGHANCNFSM4KQZWXAA
.

It's really non logical to expect that. It's a constructor, mobx must treat is as action without any directive. The creation is the same js source file.
export default React.createContext(new MyStore());

that's out of the scope of that issue, you may open FRC issue
mobx,or any other js code has no way to know if he is called inside a "constructor" or just a "function" somewhere in his callstack

Do consider app state initialization logic just another action / event.
Anyway, this behavior is known, working as intended and documented so closing this issue.
If it annoys you use the strict "observed" setting instead, which is also the recommended one for this reason. https://mobx.js.org/refguide/api.html#enforceactions


Access SAP Mobile Services

Tutorials: https://developers.sap.com/tutorials/fiori-ios-hcpms-setup.html
By using the trial account, it is crucial to select 'Singapore' (Azure) as your region/Provider.
Failure to choose 'Singapore' may result in authentication issues when attempting to log in to the Mobile Services Dashboard Trial (Step 2.5).
Any other region (e.g. 'US', AWS) could lead to difficulties in accessing the trial services.
Always ensure 'Singapore' (Azure) is specified to guarantee a seamless authentification.

@kelghali What issue did you encounter when choosing US region? I have a running trial in US10, not seeing any authentication related challenges.

No response from user. Assuming issue is no longer exist. Closing this.


Horizontal spacing

Hello
When using this, you would expect the View Controllers/pages to not overlap. They do, however. I don't know how to fix it.
To reproduce, just use a black background on page 1, white on page 2. Page 2 will overlap on page 1 (8-16 px approx). It becomes less when navigating to page 2 and back, for some reason. Is there a way to prevent this? An option to increase horizontal spacing?

Turns out it was a child of one the page that was the root of this issue. Never mind, sorry.


Minute level partitions

As per your comment i have updated the code, please review and let me know

Accidentally deleted the last PR. Sorry for this

Thanks for the change.

Thanks Henry...


projects option is not respected when only one project match

Do you want to request a feature or report a bug?
BUG
What is the current behavior?
When we use the projects option from the configuration file with only one project match Jest will bypass the project configuration and resolve all the test files from the root. The issue only happen with configuration file, when the option is provided to the CLI there is no issue. Here you can find an example.
What is the expected behavior?
Respect the projects option provided from the configuration file even with a single project.
Relevant files:
The issue seems to come from the jest-cli package. The projects option is not respected because this condition (see below) is not executed when only one package match.
https://github.com/facebook/jest/blob/1a487c1803124c594bdd86ee24b5949025660bc3/packages/jest-cli/src/cli/index.js#L248-L276

With<EMAIL_ADDRESS>the issue is still present.  That snippet he linked is still in master, too.


Allow large messages

We're storing a list of all changed model fields in the message field, and when saving a very large form, 512 characters is not enough to keep the list of all changed fields.

Makes sense. Just merged. I'll release a new version shortly.


Keep track of failures during negotiation for debugging

When performing TLS fallback, add previous exceptions to later ones as suppressed exceptions to help when debugging negotiation issues.
Results in output like this:
SSLv3-only server, SSLv3 disabled:
Caused by: javax.net.ssl.SSLHandshakeException: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xb81a4178: Failure in SSL library, usually a protocol error
error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol (external/openssl/ssl/s23_clnt.c:714 0xb089cdf4:0x00000000)
	at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:448)
	at com.squareup.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103)
	at com.squareup.okhttp.Connection.connect(Connection.java:143)
	at com.squareup.okhttp.Connection.connectAndSetOwner(Connection.java:185)
	at com.squareup.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128)
	at com.squareup.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:341)
	at com.squareup.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:330)
	at com.squareup.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:248)
	at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:433)
	at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:384)
	at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:231)
	at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)
	at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)
	at TryConnect.main(TryConnect.java:19)
	... 7 more
	Suppressed: javax.net.ssl.SSLHandshakeException: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xb81a4178: Failure in SSL library, usually a protocol error
error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol (external/openssl/ssl/s23_clnt.c:714 0xb089cdf4:0x00000000)
		... 21 more
	Caused by: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xb81a4178: Failure in SSL library, usually a protocol error
error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol (external/openssl/ssl/s23_clnt.c:714 0xb089cdf4:0x00000000)
		at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
		at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:405)
		... 20 more
Caused by: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xb81a4178: Failure in SSL library, usually a protocol error
error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol (external/openssl/ssl/s23_clnt.c:714 0xb089cdf4:0x00000000)
	at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
	at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:405)
	... 20 more

LGTM but your tests are failing

I threw in some debugging. Right now I have no idea why the connection would be failing with "connection refused". Weird. Tried with the same version of the JDK as on the CI, and the URL looks reasonable. It's almost like the server hasn't come up, but I can't explain why the new test would be special.
I'll look some more on Tuesday.
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at com.squareup.okhttp.internal.Platform.connectSocket(Platform.java:107)
at com.squareup.okhttp.internal.http.SocketConnector.connectRawSocket(SocketConnector.java:160)
at com.squareup.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:79)
at com.squareup.okhttp.Connection.connect(Connection.java:143)
at com.squareup.okhttp.Connection.connectAndSetOwner(Connection.java:185)
at com.squareup.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128)
at com.squareup.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:341)
at com.squareup.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:330)
at com.squareup.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:248)
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:433)
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:384)
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:497)
at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getResponseCode(DelegatingHttpsURLConnection.java:105)
at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:25)
at com.squareup.okhttp.internal.http.URLConnectionTest.connectViaHttpsWithSSLFallbackFailuresRecorded(URLConnectionTest.java:629)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54)
at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
URL: https://localhost:37981/foo

The issue, as it was on a prior change that also puzzled me, is that there are multiple routes to localhost on the CI box because it has an IPv4 and and IPv6 address, both mapped to "localhost". The MockWebServer is listening on the IPv4 address only.
With the test I added, both attempts to negotiate with the IPv4 address fails, so it moved to the IPv6 address, and that connection is refused. When that exception is thrown we only see the "connection refused" error.
I have "fixed" by using the SingleInetAddressNetwork.
It shows an important limitation of my change: we do not retain exception information across routes, so if there are multiple routes and a later route fails for a different reason the first failures are "lost".
A follow up change could be made to retain prior RouteExceptions in HttpURLConnectionImpl (and Call) and add them as yet more suppressed exceptions to the IOException that is ultimately thrown (if any).
While that could be useful, that might be better solved with logging (or interceptors in other APIs?) instead. I don't know your policy about logging. I've always assumed that OkHttp doesn't log debug information deliberately: on several occasions I've also thought it would be useful to log the IP address being attempted (e.g. in this case the presence of the IPv6 address might have hinted at the problem). I appreciate this probably has privacy concerns, though.
Let me know about retaining RouteException for suppression: I'd happily add this if you agree in principle. It'll all help with debugging and hopefully reduce my workload as result.

LGTM
I'm relatively reluctant to do any logging. With our new interceptors, it's straightforward to add whatever logging you want, though that won't work for the HttpURLConnection frontend.

Merging proactively to get this cool stuff into the codebase. If you wanna add the fail() call, please send another PR.


Fix hoptoad:deploy for custom port.

Thank you! Integrated into the new repo at: https://github.com/airbrake/airbrake


Aql functions

Added a new namespace to handle user managed custom functions. These can be found under the _api/aqlfunctions end-point.

Hi Mike, thanks for the pull request.
What was your reason to create a new namespace for the aql user functions? I'd rather put them into the already existing query namespace (which is already combining the cursor and the explain endpoints) because I would like to avoid bloating up Clarango with too many namespaces. Do you see any reason against doing that?
Sidenote: I'm actually thinking of also merging the new gharial namespace with the existing graph or just deleting graph and replacing it with gharial for the next version of Clarango, since the new version will not be backwards compatible anyway.

Hiya,
My main reason (apart from the obvious one of modularity) was to match up somewhat with the end-points as they are shown in the ArangoDB API docs. If you access the API (Tools -> API) from the web console it's easy enough to see that they consider them distinct enough (rightly or wrongly) to have distinct end-points and my reasoning was to have the namespaces match those.
I'm not especially invested one way or the other so I don't mind if this ultimately gets merged somewhere else, but it was a feature that I noticed was missing so I thought I'd push an update.


Implement fuse filesystem mount

It would be nice to be able to mount a continuity manifest via fuse via command:
continuity mount --fuse <mount> <manifest> <root>
This would only serve files identified by the manifest and only if their hash matched. We use --fuse to allow other kinds of mount implementations (imagine http, tar, etc.). Such a command should take the same options required to map uids, links, etc (not defined yet).

This should enable records for special files too:

block/char devices
unix sockets
pipes (FIFOs)
etc.

Your FUSE filesystem need not implement them, only report that they exist via dir entries and node attrs, the kernel will handle dispatching device requests to the proper driver (though major/minor mappings will likely be different between systems) and the kernel will also handle things like sockets and pipes. Gotta use the dev mount option though.
Discussed earlier IRL; Wasn't sure if I should open another issue since it's related to this one.

@jlhawn This should probably be another issue. The support for devs and sockets is shaky at this point.


Popup is misplaced when setting zoomAnimation to false in PopupOption

Hello,
Here is an issue that can be reproduced in master and RC1. Add a marker, bind a popup with zoomAnimation option as false and zoom in or out. The popup is misplaced:
https://playground-leaflet.rhcloud.com/bemi/1/edit?html,output

If both map and marker is zoomAnimation: false, the bug is not present.
So the problem might actually be that how can a marker be non-zoom animated while the map is? Maybe we should just override one with the other?

This is what seems to happen in beta1: if map is zoom animated then the popup is zoom animated as well, no matter what option is passed.

The test could be changed to a test on the map's option in https://github.com/Leaflet/Leaflet/blob/master/src/layer/Popup.js#L116 but then we might as well remove the zoomAnimation option from the PopupOption code (and docs). Which means that users with Flash content in popups would need to disable animations on the whole map

Found the original issue in leaflet 0.4 that introduced the zoomAnimation on PopupOption:
https://github.com/Leaflet/Leaflet/issues/999
Seems like a bunch of flash-browser related issues

Just tried reproducing the issue with flash content inside a popup and zoomAnimation true, seems to work alright (Chrome / IE on Windows):
https://playground-leaflet.rhcloud.com/tani/edit?html,output
Maybe the original issue is now outdated and browsers fixed it?

Hehe, Flash + zoomAnimation disabled on marker but zoomAnimation enabled on map, I'd call this an edge case of an edge case. Meanwhile Flash is kind of dead, the linked iframe example is Flash-less as well, so I wouldn't worry about it.
Personally, I'd recommend removing zoomAnimation from marker options, as it should be handled on a map level.

@fnicollet Your "flash content" is actually a HTML5 <video> tag, so that's why modern browsers don't display the bug.
I do agree that flash is pretty much dead nowadays.
I've made a small change to always reposition popups (#4685), but it's failing a test. I'll debug, then we can push it to rc2 and let people open a bug if flash or whatever fails ever again.

@IvanSanchez yup, took the examples from the original issue, 3 years ago when Youtube was still flash-only, my bad :)
Why not remove the property altogether? After your commit, it is only used in "true" cases, so no point keeping it?

@fnicollet Yeah, removing it altogether might be a better idea. Maybe you can send a PR over the weekend?

will try, yes
On Fri, Jul 1, 2016 at 5:00 PM, Iván Sánchez Ortega <
<EMAIL_ADDRESS>wrote:

@fnicollet https://github.com/fnicollet Yeah, removing it altogether
might be a better idea. Maybe you can send a PR over the weekend?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Leaflet/Leaflet/issues/4685#issuecomment-229969438,
or mute the thread
https://github.com/notifications/unsubscribe/ABLtoXCbRqm0w4EjQ_RNv201yXDyTPaBks5qRSt3gaJpZM4JAmdK
.

--
Fabien Nicollet
Tel : +33 (0)6 60 54 72 20

Seems like a minor issue so moving out ot 1.0-rc2 milestone.

Added the PR that removes the option and the checks in Popup.js

A test is failing: https://travis-ci.org/Leaflet/Leaflet/builds/141660040
But I would say that it seems more related to this commit which is already in master: https://github.com/Leaflet/Leaflet/commit/bddfb1168f5ea859181857b5764ba1f16100ddd2


[DO NOT MERGE] Managed instance updates plus examples

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Can one of the admins verify this patch?

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5899
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5899/commits/bc8da6dd3e0856e9b8e8af11c6298afc663ffd6f

Thanks for this PR!

Thanks for this PR!

Np :) Thanks for reviewing @jaredmoo and @petrajkogit !

@nschonni , not sure what's going on with the build automation for azure-sdk-for-net.
is this a transient build err?
19:34:24          StartInfo: '/c autorest.cmd https://raw.githubusercontent.com/johnpaulkee/azure-rest-api-specs/f75801138eba6842afbd124547f47aa66e4383a1/specification/sql/resource-manager/readme.md --csharp --version=2.0.4283 --reflect-api-versions --csharp.output-folder=C:\jenkins\workspace\DotNetSwaggerToSdkCI\tmp2C5E\src\SDKs\SqlManagement\Management.Sql\Generated'
19:44:24      1>c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error : InvalidOperationException: Process must exit before requested information can be determined.
19:44:24 c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error :    at System.Diagnostics.Process.EnsureState(State state)
19:44:24 c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error :    at System.Diagnostics.Process.get_ExitCode()
19:44:24 c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error :    at MS.Az.SwaggerToSdk.Common.ExecProcess.ShellExec.ExecuteCommand(String args, String workingDir) in F:\tf\AzNetSdkTools\src\SwaggerToSdk\Common\SToS.Common\ExecProcess\ShellExec.cs:line 147
19:44:24 c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error :
19:44:25          StartInfo: '/target:library /out:C:\Users\FXSign\AppData\Local\Temp\FSUtil\tmpC7D3\SqlManagement-SdkInfo.dll C:\jenkins\workspace\DotNetSwaggerToSdkCI\tmp2C5E\src\SDKs\SqlManagement\Management.Sql\Generated\SdkInfo_SqlManagementClient.cs'
19:44:26          Microsoft (R) Visual C# Compiler version <IP_ADDRESS> (b9fb1610)
19:44:26          Copyright (C) Microsoft Corporation. All rights reserved.

@nschonni , not sure what's going on with the build automation for azure-sdk-for-net.
is this a transient build err?
19:34:24          StartInfo: '/c autorest.cmd https://raw.githubusercontent.com/johnpaulkee/azure-rest-api-specs/f75801138eba6842afbd124547f47aa66e4383a1/specification/sql/resource-manager/readme.md --csharp --version=2.0.4283 --reflect-api-versions --csharp.output-folder=C:\jenkins\workspace\DotNetSwaggerToSdkCI\tmp2C5E\src\SDKs\SqlManagement\Management.Sql\Generated'
19:44:24      1>c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error : InvalidOperationException: Process must exit before requested information can be determined.
19:44:24 c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error :    at System.Diagnostics.Process.EnsureState(State state)
19:44:24 c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error :    at System.Diagnostics.Process.get_ExitCode()
19:44:24 c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error :    at MS.Az.SwaggerToSdk.Common.ExecProcess.ShellExec.ExecuteCommand(String args, String workingDir) in F:\tf\AzNetSdkTools\src\SwaggerToSdk\Common\SToS.Common\ExecProcess\ShellExec.cs:line 147
19:44:24 c:\jenkins\workspace\DotNetSwaggerToSdkCI\scripts\stostools\SToS.proj(17,9): error :
19:44:25          StartInfo: '/target:library /out:C:\Users\FXSign\AppData\Local\Temp\FSUtil\tmpC7D3\SqlManagement-SdkInfo.dll C:\jenkins\workspace\DotNetSwaggerToSdkCI\tmp2C5E\src\SDKs\SqlManagement\Management.Sql\Generated\SdkInfo_SqlManagementClient.cs'
19:44:26          Microsoft (R) Visual C# Compiler version <IP_ADDRESS> (b9fb1610)
19:44:26          Copyright (C) Microsoft Corporation. All rights reserved.

This failure looks transient. I'll ping .NET generator owners.

@shahabhijeet, Could you take a look at .NET failures?

Let me know if the azure-sdk-for-net issue is a problem to fix before merge. We're ready on our end if it isn't a problem.
Also, I just retried build and we're getting the same err.

@johnpaulkee @kpajdzik Please disregard the .NET failure here, we have some OOM exceptions when compiling SQL SDK given its size. Please feel free to approve and merge


[Feature Request] Integrate CodeBuild local agent

Description:
What about integrating the new CodeBuild local agent into sam-local?
It could make it easier for a serverless developer to test/debug a buildspec file locally.
Since sam-local already requires Docker, it could also make it a bit more transparent so that you don't need to be a "Docker expert" at all.
Suggested behaviour:
sam build --image ruby:2.3.1

The command should take care of the following steps:
# build docker image
docker build -t aws/codebuild/ruby:2.3.1 .
# pull agent image
docker pull amazon/aws-codebuild-local:latest --disable-content-trust=false
# run buildspec
docker run -it -v /var/run/docker.sock:/var/run/docker.sock -e "IMAGE_NAME=aws/codebuild/ruby:2.3.1" -e "ARTIFACTS=/home/ec2-user/environment/artifacts" -e "SOURCE=/home/ec2-user/environment/sample-web-app" amazon/aws-codebuild-local

(more detailed instructions here)

This is a good idea! I will keep the issue open here to gather feedback.