Fo transformations

Should the .fo transformations be ported from xslt 1.0 to this, or is this xslt set intentionally purely focused on HTML output?

That is a question that I wrestle with regularly. I'm inclined to say that the way forward is through an XML to HTML transformation (not the same transformation as for web pages, but still HTML with extra classes and such) and then print formatting via CSS. Given that development of FO has stopped, that seems like the right approach.
On the other hand, FOP is good enough for a lot of folks and there doesn't seem to be a similarly featured open source CSS print formatter. Which surprises me a little bit.
If lack of print output is holding you back from adopting these stylesheets, I guess I want to know that. Particularly if you're relying on FOP. Getting some kind of print output is on my todo list, but it's currently somewhere below "finish XML Calabash 3.x". ☹

Sorry for the delay in responding.
My requirement is a CLI asciidoc->PDF workflow; I am attempting to make it a workflow that requires minimal installation, consistency across platforms, and some complex formatting of the PDF output (i.e., number every fifth line and print some sections in a two column layout). I have examined the existing asciidoc-to-pdf tools and have determined that an asciidoc->docbook->fo->PDF process run using maven is my current best shot at minimal install (user needs to install a JDK and a recent maven and the workflow takes care of everything else) while ensuring consistency (maven downloads the same JAR versions for every user) and allowing complex outputs (using fop within maven).

Just some comments/views from my side.
Me and my company are also interested in a FO transformation for several reasons:

FOP is getting better from release to release. In former times it was very limited, but now it's quite good. Perhaps for Arabic or other languages it still needs some work, but it's a good alternative for XEP (and it's open source).
We still have a XSLT 1.0 code base for FO. If possible, we would like to gradually move to the new stylesheets if they would be available.
In most cases, the combination of the XSLT 1.0 stylesheets and FOP works quite well. Of course, there are always some things that can be improved. Moving to a new set of tools with HTML+CSS comes usually with different problems and challenges. Some can be solved or mitigated, but I expect some would cannot be solved.

Maybe some pro points why it would be beneficial to have a native XSLT 3.0 implementation of the FO stylesheets:

See above about how FOP improved over time.
Makes it more feature parity with the DocBook XSLT 1.0 stylesheets
Although the XSL-FO spec isn't developed further, for most (technical) documentation it doesn't matter IMHO. It's completely sufficient. As DocBook deals mostly with technical documentation, these types don't tend to have fancy layouts. XSL-FO 1.1 is fully capable of doing this.
Just have another option to support a printed output, not only with HTML+CSS.
We don't have open source CSS print formatters, but we do have FOP.  As long as there are no open source alternative, it would be a good solution to have a FO workflow.
Although some browsers support HTML+CSS as PDF in a headless mode, as far as I can see it's subpar in contrast to FO.
Maybe as an interims solution, we could use the XSLT 1.0 stylesheets with Saxon 10/11? Over time, we could gradually move to XSLT 3.0

On the contrary, we should also consider the cons:

For people who write customization layers, it's probably easier to just have one layer and do all the output for HTML and PDF with HTML+CSS. No need to maintain two different customization layers.
Maybe a headless browser output of the HTML+CSS rendering is just "good enough"?
If we start to implement the FO stylesheets, they need to be maintained to some degree.

I think that If we start to implement the FO stylesheets, they need to be maintained to full degree. Either you do it completely or not at all. Halfheartedly is not an option. This means: double the effort , unless you find a more intelligent solution. There are some options, they all need volunteers:

development of XSLT 3 FO stylesheets, independent but carefully aligned to the xslTNG HTML+CSS Styleheets. IMHO not realistic.
development of an open source paged Media processor. IMHO also not realistic.
development of some sophisticated mechanism to generate FO and HTML+CSS Stylesheets from some higher-level intermediate language. Interesting, but also not realistic. You would need a language with enough expressive power to generate XSLT 3 Stylesheets, what language would that be?
development of an open source engine that takes HTML+CSS as input and generates XSL-FO. Maybe this is what the guys from the Oxygen Company (SyncroSoft) are doing with the Oxygen Chemistry product? I tried to generate PDF from xslTNG output within the Oxygen Suite with PDF Chemistry, but without success. Maybe it was just a minor issue? I cant tell since its not open source.

I would think that the last option is the only realistic one, but @tomschr , this would not help the people that still have an old XSLT 1 codebase, would it? Also, you have to deal with CSS combined with XML / (X)HTML as the base for the translation to FO. You can find this technique under the Name CSSa  (meaning CSS as Attributes in XML) as part of the transpect open source framework. So maybe there remains only one option like this:

Development of an xslTNG post processing step which produces (X)HTML with CSSa, based on the existing CSS for xslTNG;
Development of an translation engine which takes HTML+CSSa as input and generates XSL-FO for FOP.

Should be possible as an open source project based on transpect (maybe upgraded with a brand new Calabash processor for XProc 3?) I have absolutly no idea how much effort it would take.
Greetings, Frank

Thanks @frank-steimke for your interesting perspective! You made some good points.
Well, developing an open source engine or developing XSL-FO stylesheets need both efforts and time. The question is which one would be more useful.
I would like to bring two other ideas which could mitigate the pain. Not sure if it's completely insane or it has some benefits.

Why not use the existing XSL-FO 1.0 base stylesheets and transform it to get FO stylesheets that are more compatible with XSLT 3.0?
Presumably it is not a complete replacement for manually written XSLT 3.0 stylesheets. Certainly there are some issues (extension functions, no test suite etc.). If all issues could be solved, we would at least have stylesheets that could be used by Saxon >10.

In regards to an open source engine that takes HTML+CSS and generates PDF, there are some possible solutions:

Using Google Chrome's Headless Mode
You can run Google's Chrom from the commandline.
$ chrome --headless --print-to-pdf="output.pdf" URL

Using wkhtmltopdf
An open-source command-line tool which uses the WebKit rendering engine.
$ wkhtmltopdf --page-size A4 URL output.pdf

Using chromehtml2pdf
A JavaScript command-line tool that uses Chrome's headless mode.
$ chromehtml2pdf --out=file.pdf --landscape=1 URL

I haven't tested all of them (only wkhtmltopdf a bit). Maybe it helps.

I think we are talking about different scenarios for using DocBook stylesheets. I am sure that in the future there will be more ways to transform HTML+CSS to PDF. But I don't think they will be suitable to produce large and long-lasting documents in high quality. To give a few examples:

Hyphenation with custom additions and exceptions for specific terms;
Support for double-sided printing, where chapters always start on odd pages;
Floating graphics while respecting typographic criteria;
Accessibility and tagged PDF
Flexible Design of title pages with company logos
Systematic handling of external media such as images (relative vs. absolute URL)

The big advantage of DocBook 1.x stylesheets is that they are very mature and implement all the above requirements (and many more). And the biggest advantage: an acitve community, which feels responsible for the stylesheets, and patiently handles any kind of questions.
xslTNG together with paged media CSS will provide at least the same features. The open question is whether an open-source solution is conceivable that provides this performance even if FO is generated instead of (or in a second step from) HTML+CSS.
"Why not use the existing XSL-FO 1.0 base stylesheets and transform it to get FO stylesheets that are more compatible with XSLT 3.0?"
Well, you can use the XSLT 1.0 Stylesheets with the latest saxon Version. I did, and the only change that was absolute necessesary was a patch regarding an ancient node-set()- function. So it is of course possible to take that as the baseline for further development in the XSLT 3 direction.
But in doing so you would open a new line of XSL Stylesheets for docbook,, which would be in competition to the xslTNG line. This is not what i would like to support. My goal would be to support xslTNG as much as i can, and maybe contribute with documents (migration guide, best practice) or maybe an add-on for a translation of (HTML+CSS) to XSL-FO.
But before doing so, one shoud be convinced that there is a real need. Maybe evereyone who really needs high-quality Output with the features namend above already has a licence of a commercial prodict like Prince oder Antenna House and is totally fine with HTML paged media.
Cheers,
Frank

I think we are talking about different scenarios for using DocBook stylesheets.

Perhaps. :wink:

I am sure that in the future there will be more ways to transform HTML+CSS to PDF.

I hope so, really.

But I don't think they will be suitable to produce large and long-lasting documents in high quality.

I'm aware that the ideas that I've suggested is probably not a solution for high-quality docs. But for some it would be enough to get at least a "decent" PDF. What's really possible needs to be tested.

xslTNG together with paged media CSS will provide at least the same features. The open question is whether an open-source solution is conceivable that provides this performance even if FO is generated instead of (or in a second step from) HTML+CSS.

And this is the crucial point. It's all nice and dandy, but with the lack of an open-source solution I fear this is difficult. I don't know about an open source implementation.
Who will use it when you have to pay for a license? Wouldn't that divide the community?

But in doing so you would open a new line of XSL Stylesheets for docbook, which would be in competition to the xslTNG line.

Is it? And so does DocBook and the stylesheets compete with other documentation formats (ASCIIDoc, Sphinx, Markdown to name the most well-known). I don't see it as something bad. :slightly_smiling_face:
I see it more as offering an alternative. If HTML+CSS paged media cannot or don't want to be used, xou can also view it as an intermediate step to see if XSL-FO is really needed these days. If you can get some feedback or statistics then there is probably some need for it. If not, not much harm development time was wasted.

Maybe evereyone who really needs high-quality Output with the features namend above already has a licence of a commercial prodict like Prince oder Antenna House and is totally fine with HTML paged media.

This is a far-fetched assumption. :wink: Many open source projects would like to get also high-quality output. In former times it was possible with XSL-FO and it did the job well. FOP is now quite stable.
The formatting landscape today is different when XSL-FO was created and when the 1.0 stylesheets were implemented. Now we have not only DocBook, but different formats all competing with each other.
If projects cannot jump on the HTML+CSS page-media wagon, they will either use the limited option (as I showed) or they switch to something else.

i do not intend to promote commercial products, quite the contrary. And yet the question remains, how much interest is there in a solution for high-quality FO for docbook?
If most users are satisfied with free, but not so high quality solutions, there are already products. You have pointed that out.
If the others who need high quality already have or are willing to buy commercial products for HTML CSS, they have no need for an additional FO solution.
My only point is that a vibrant community needs to come about,. Right now there are exactly two people participating in the discussion about FO for xslTNG.  Add the original poster and there are three of us. That's too few in any case.
Maybe the antenna house company knows more. Their product support FO as well as HTML+CSS. They should know their customers needs.

And yet the question remains, how much interest is there in a solution for high-quality FO for docbook?
If most users are satisfied with free, but not so high quality solutions, there are already products. You have pointed that out.

True.

Right now there are exactly two people participating in the discussion about FO for xslTNG. Add the original poster and there are three of us. That's too few in any case.

Well, to some degree that's true, but I'm not completely sure if a hidden issue in a GitHub repo that not many know or aware of it is a good measurement. Perhaps not many have it on their radar or think it's production ready.
It would probably be more efficient and reach many more users if we asked on the docbook-apps mailing list and see what the response is.

I found print-css.rocks. Various tools are presented and tested there, commercial as well as open source. This led me to weasyprint. Results are promising, see attached file
xnachweis-w.pdf
There is an issue with references to page numbers which results in 0 (zero) in the table of content, see issue #497. But i think it's an issue of CSS from xslTNG, not the rendering engine.
Maybe weasyprint is the open source rendering engine we were looking for?


Add implementation of Longest Common Subsequence (LCS) algorithm in Python

📥 Pull Request
Description
Added documentation for longest common subsequence using dynamic programming
Fixes #117
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Please add hacktoberfest and gssoc-ext label


Unmute nested sort related ITs

Description
Unmuting nested sort related tests for concurrent segment search. It's not super obvious why but both these tests and the underlying race condition itself was addressed by #11249.
The race condition comes from when SortBuilder::buildSort is called simultaneously by multiple threads which results in the LinkedListed in NestedScope being accessed concurrently leading to the stack traces found in #11187 & #11258.
In #11249 this was changed here to instead pass in the same SortAndFormats from the search context instead of rebuilding it on each thread. This means that we won't run into this same race condition anymore for nested sorts and I also verified that SortBuilder::buildSort is not called in a multi-threaded fashion from anywhere else.
Thus since the underlying problem has been addressed, unmuting these tests.
Related Issues
Resolves #11187
Resolves #11258
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@reta @sohami this PR is just unmuting some tests but please let me know if you would like to discuss anything else related to the original issues. Thanks!

https://build.ci.opensearch.org/job/gradle-check/30538/

https://github.com/opensearch-project/OpenSearch/issues/2775

There's a PR open already for this issue

@reta @sohami this PR is just unmuting some tests but please let me know if you would like to discuss anything else related to the original issues. Thanks!

I guess you can update the Description as root cause is now known.
It's not super obvious why but both these tests and the underlying race condition itself was addressed by https://github.com/opensearch-project/OpenSearch/pull/11249.


Formly and dynamic forms

Reactive forms is really great package.
Thanks to author.
This package is inspired by Angular reactive forms, very similiar.
It would be even better if there would be another package that would wrap reactive forms package and fields to formly package as angular formly.
Formly is great for dynamic forms from server or json and on my opinion it would be high compatible with reactive forms package.

Hi @mitjaj76,
Thanks for your kind words and for using Reactive Forms. Definitely Formly Angular is a great library. I will be very pleased if someone else implements a library like Formly Angular for Flutter based on Flutter Reactive Forms, that would by great. I still need to add some pending features to Reactive Forms and I would like to implement some extra widgets (this is another plugin with some extra widgets based on Flutter Reactive Forms).

I will close the issue for now, don't hesitate to reopen or open a new one for some issue.


Use publishing-api lookup endpoint

This PR makes the content-tagger use the publishing-api for everything. This is better because the publishing-api is synchronous and we'll have less dependencies.
https://trello.com/b/Kg3JL5Cd

Nice :+1:


system.properties in filesystem root

Using the unifi::setting define results in a system.properties in the filesystem root as $data_directory does not exist in the unifi class (resulting in the file path "/system.properties").

Good catch! I've pushed commit 866abca on the master branch that should fix it.
Can you try out that change and let me know how it goes?

I haven't tested it yet, but as far as I know, you have to move $data_dir in the unifi class to the class parameters.

Good point. I've made them into parameters to Class[unifi]. I've also noticed that the Unifi Controller package now stores most of it's data, logs, and runtime information under subdirectories of /var, so I've updated the module to take the new paths into account. (f1f872f7)
I've also added a require parameter to the Unifi::Setting defined type so that Puppet applies them after Package[unifi] is installed. (d51b97fb)

I've just tested the fix. It works. Thanks! :-)


Do not retry when timeout is hit

this PR adds a safeguard for retrying after the timeout is hit as reported on #1080 .
This prevents:

a query that took 60seconds on one node to be retried on a second node.
a query that timed out after 30seconds on 2 nodes to be retried a third time.

By default this listens to SetTimeout() which itself defaults to 60 seconds. The max retry timeout can be configured separately by calling SetMaxRetryTimeout().
The MaxRetryException message itself clearly reflects when its thrown because we exceeded the MaxRetryTimeout.

I want confirm behavior of SetTimeout() from pre 1.3 version to 1.3 version. Say we have the following code in Nest Api 1.0
var timeoutInMillis = 100;
var maxRetries = 3;
var config= new ConnectionSettings(pool);
config.SetTimeout(timeoutInMillis);
config.MaximumRetries(maxRetries);
Now imagine the scenario where request times out on the first node in 100 milliseconds, the request will repeat for 3 more times with each timeout being 100 milliseconds, when the same code is migrated to Nest 1.3.1 with the above fix, the request will only be tried for 100 milliseconds and will not be retried as by default MaxRetryTimeout will be equal to Timeout, hence this becomes a breaking change.
I wonder if the default value of MaxRetryTimeout could have been maxRetries * timeoutInMillis


Multiple route handlers

I was wondering if restana (or find-my-way, or other) could provide multiple callback functions to handle a request, like route handlers in express. This is the main impact that I have for migrating to restana. restana is great, well thought, thanks.

Hi @kaesar, I was wondering if route level middlewares is a feature that satisfies your requirements:
Can you please have a look at: https://github.com/jkyberneees/ana#route-level-middlewares
Here you actually can "provide multiple callback functions" to handle your request.
Thanks

Yeah, it could be. Just that for migrating is for routes in a simpler style, something like: app.get('/cool', fn1, fn2, fn3). I unknown the impact for restana, so I leave it to your discretion if you find it interesting to facilitate a migration from express.

Hi @kaesar , JFYI: https://github.com/jkyberneees/ana/pull/20
Landing in 2.8.0 ;)
Regards

That's great. Thanks a lot.


Install

Congratulations for the idea, I'm interested to command meross devices from OpenHub.
Can you explain how to install it in openhub?
I used:
git clone https://github.com/atzbert/meross-java.git
Then enter in meross-java dir but can't execute:
mvn clean install
Thanks

Hello, I'm quite new at this but I'm very interested in this package too.
This is how I built it:
git clone https://github.com/atzbert/meross-java.git
apt-get install maven
Then I went to the cloned directory (in my case /home/openhabian/meross/meross-java) and
mvn clean install

this is not an openhab binding, just a library to talk to meross from java


transfering an infographicto raw.density

Hi, I'm a newbie and wondered if anyone could tell me how to add a graphic from the library.....Cheers

Duplicate of #2197.  These GitHub issues are for bug reports and feature requests only.  Please use StackOverflow or the d3-js group for help.


Very slow upload of point data

I have been working on uploading some point data to Mapbox.
For some reason the second time I upload the data it is very slow. It uses 100% of the CPU but only managed 1-4 tiles/sec. The progress counter stays stuck at 0.1%.
The first time I upload the data it only takes 1 minute to upload.

I have the same problem but on OS X. It seems to be stuck at 0.1 %.


net: coap_client: Various fixes

This is quite long chain of fixes that I noticed when I started to fix just some simple error cases.
See individual commits for explanations.

I'll start working on rebase as the https://github.com/zephyrproject-rtos/zephyr/pull/80303 actually addressed the same issue than one of my changes, but did it differently.
I'll refactor this a bit..

Updated the description to covers the intention of this PR.


Google Services Plugin

File google-services.json is missing. The Google Services Plugin cannot function without it.
Searched Location:

You're meant to generate this file yourself - please go through the documentation referenced in the readme file.


Add notice on updating Gloworm image when using LL

Closes #130

All this being said, same as was poked at on discord - doing per-hardware repos which smush the custom .iso's and config files and latest .jar's together I think would resolve users of this step.


Can not launch server with latest Aviar patch

Issue description
Server throws various errors when launching with latest Aviar version and fails to boot, client launches fine.
Steps to reproduce

Add latest Aviar version to server mods list along with dependencies.
Launch server

Minecraft version
1.19.2 (Latest)
Forge version
43.3.0
Cosmere version
.78
Other relevant versions
https://discord.com/channels/828383636465123328/837596260168237056/1176609295958278164
Using the version linked here
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
https://mclo.gs/U3n5wv3
https://mclo.gs/Sb1fW55

found the problem, thank you, working on a fix.

I have confirmed fix in a local server, outside my dev environment this time. New builds processing on curseforge now, keep an eye out for build 79.


Replace grammar by antlr/grammars-v4's

Motivation
Microsoft has never published a full open specification for T-SQL, so each grammar "replication" of Transact-SQL (TSQL) is incomplete. The project's current grammar is (mainly) based on https://github.com/antlr/codebuff/blob/master/grammars/org/antlr/codebuff/tsql.g4, which was last updated in 2016.
Consequently, in my projects, I encountered several (elements of) SQL statements that pytsql was or is currently incapable of parsing - i.e., it's not possible to execute them with pytsql.
Examples are PR #51, #59, or, more recently, I tried to parse DATETIME2 and STRING_AGG() without luck.
In the past, we always manually adjusted our .g4 grammar - e.g., PR #33. However, this solves the problem, namely that the grammar has (apparent) gaps, only fragmentarily. Also, manual changes to the grammar generally make the package harder to maintain and may need to be more focused on the actual focus of the package.
Fortunately, however, a relatively actively maintained grammar with significantly greater functionality exists: https://github.com/antlr/grammars-v4/tree/master/sql/tsql (*). It is even an evolution of our 2016 version. I propose to base our grammar on it instead.
I would even propose moving all future grammar extensions completely to this external repository to keep our package as light as possible.
👍 Pros:

Grammar (*) ships much more valid syntax
👉 pytsql get's "leaner" & can focus less on grammar definition
👉  In effect, more TSQL statements get parseable

👎 Cons:

Grammar (*) has more false positives. That is, sometimes invalid statements are still parsed successfully

example (1): USEE master does not raise an issue
example (2): in rare cases \N GO is not recognised correctly; see https://github.com/antlr/grammars-v4/issues/3275 - adding ';' solves it for isolate_top_level_statements=False
however, despite pytsql "executing" these statements, sqlcmd in the end still handles them correctly...
... so it may boils down to which tools should generate the error message (?)

Changes
Replace tsql.g4 by https://github.com/antlr/grammars-v4/tree/master/sql/tsql (*).

Modify grammar (*) slightly:

certain rule element labels are protected within C++
👉 rename label <x> to <x>_label (similar to PR #28)

Generate new targets
Adjust tsql.py
Adjust tests:

+1: some minor flaws in current test queries were not flagged with our current grammar
-1: remove some tests that flagged wrong TSQL statements

Adjust documentation

Example of a false positive parsing of grammar (*):

For faster feedback this should also has Windows unit tests ;)


Initial implementation of class generation (Draft)

Added type annotations to most of the project
Implemented a source-generated serialization system for object.properties via fmodel
Added some convenience functions and manually implemented the missing UE/TU primitives: Guid, Rotator, Plane, Vector2D, LienarColor, Color, Colorable, Transform

Future work:

Apply this approach to object.item and object.item['properties']

Source generation is probably not needed as I suspect the properties for those are always the same

Manually add property definitions for properties that fmodel cannot see
Implement arrays
Test vigorously

Here's the error from the Read The Docs build:
ERROR: Cannot install -r docs/requirements.txt (line 2), -r docs/requirements.txt (line 3) and sphinx==7.1.2 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested sphinx==7.1.2
    sphinx-rtd-theme 1.3.0rc1 depends on sphinx<8 and >=1.6
    sphinx-autodoc-typehints 2.1.0 depends on sphinx>=7.3.5

Oh wait, I think that build failure is from me. Wacky I didn't catch it previously

Read The Docs failure is fixed in 887045f


[Lite] To disable Web Bluetooth

Disabled size = 20K

@heke123 @halton

@PeterWangIntel , Only one comment:
There are many files in /device directory, and they are compiled. Just make sure they are not linked into the libxwalkcore.so.

@heke123
thx for reminding. patch has been updated.

LGTM


Cultures not working in Vue which looks like dynamic routing issue

Version
2.5.9
Reproduction link
https://github.com/hmuhdkamran/Cms
Live Website Working at
sqanetcore.thetowertech.com
Steps to reproduce
Just open the website and open chrome console window it will start showing error.
What is expected?
It should run properly and start working as it is working in development server.
What is actually happening?
I am making a website on Vue using aspnetcore 2.0 which i am using development there is no bug no issues it is working perfectly fine when I am rolling it out to production it is giving me error
http://<IP_ADDRESS>/api/culture/SupportedCultures 500 (Internal Server Error)
<IP_ADDRESS>/:1 Uncaught (in promise)
{messageTypeId: "Error", text: "Request failed with status code 500", title: "Code:undefined. Error"}
messageTypeId
:
"Error"
text
:
"Request failed with status code 500"
title
:
"Code:undefined. Error"
proto
:
Object

I am facing the same problem

Sorry but a full project is not a valid repro, it has to be boiled down to the minimal

Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂

@posva
I just uploaded code because you cannot do routing. the basic issue is not in the code as it is perfectly working Okay on development machine as soon as it is made production it stops working,


could you tell me how the 4step alternating training take place

hello,I read the fasterrcnn paper and your code for several days .the paper said  they used  a 4step alternating training .
first fine-tuned end-to-end for the region proposal task,then train a separate detection network by Fast R-CNN using the proposals generated by the step-1 RPN,In the third step, use the detector network to initialize RPN training and  fix the shared convolutional layers and only fine-tune the layers unique to RPN. Now the two networks
share convolutional layers. Finally, keeping the shared
convolutional layers fixed,  fine-tune the unique
layers of Fast R-CNN.
but from your code ,I see three networks:rpn,fast-cnn detection, and model-all, can you tell me how the above four steps is used in your codes?
thanks so much!

+1

I also found that the RPN and fast-rcnn are not share the convolutional layers in  yhenon's code ,it's a doubtful place. Besides, the region proposals  used for training fast-rcnn are not best because the rpn is not finishing training.


Machines are in a broken state when creation fails

Consider this example:
$ machine ls
NAME   ACTIVE   DRIVER   STATE   URL

$ machine create -d amazonec2 --amazonec2-access-key foo --amazonec2-secret-key bar --amazonec2-subnet-id quux spam
INFO[0000] Launching instance...
FATA[0000] Problem with AWS API call: Non-200 API response: code=401 message=AWS was not able to validate the provided access credentials

$ machine ls
ERRO[0000] error getting state for host spam: Problem with AWS API call: Non-200 API response: code=401 message=AWS was not able to validate the provided access credentials

ERRO[0000] error getting URL for host spam: Problem with AWS API call: Non-200 API response: code=401 message=AWS was not able to validate the provided access credentials

NAME   ACTIVE   DRIVER      STATE   URL
spam            amazonec2   Error

$ machine rm spam
ERRO[0000] Error removing machine spam: unabme to terminate instance: unknown instance
FATA[0000] There was an error removing a machine. To force remove it, pass the -f option. Warning: this might leave it running on the provider.

$ machine ls
ERRO[0000] error getting state for host spam: Problem with AWS API call: Non-200 API response: code=401 message=AWS was not able to validate the provided access credentials

ERRO[0000] error getting URL for host spam: Problem with AWS API call: Non-200 API response: code=401 message=AWS was not able to validate the provided access credentials

NAME   ACTIVE   DRIVER      STATE   URL
spam            amazonec2   Error

$ machine rm -f spam
ERRO[0000] Error removing host, force removing anyway: unabme to terminate instance: unknown instance

$ machine ls
NAME   ACTIVE   DRIVER   STATE   URL

User should not have to machine rm -f at all.  If there is any error with machine create, machine should clean up the failed host create.

What if we do the following:
If DEBUG is enabled, we do not automatically cleanup the reference nor attempt to remove the provisioned instance.
If not, we show the error and then remove the reference and attempt to remove the possibly provisioned instance.  We also show a warning that states all resources may not have been removed.
Thoughts?

If a machine might have been created, we definitely want to keep around the local reference. Otherwise the user might not know they have created an instance and they'll be charged money for it.
Perhaps along with an error, we explain that your machine might be in a broken state, and give you instructions on how to remove it.

@bfirsh ok makes sense
So perhaps this:  if DEBUG, things basically perform as they do today and leave it in whatever state along with a message stating something went wrong and general instructions for cleanup.
By default, it would report and error and attempt to do the remove / cleanup but still report the instructions "just in case".
Thoughts?
/cc @nathanleclaire @sthulb

My thinking is, "normal" mode should clean up, if we're in a state we know we can clean up from.
Debug mode should act as we do now, leave things in place with a note telling people the resources are there still.

@sthulb cool -- thanks

@bfirsh @nathanleclaire @sthulb could you take a look at #234 and see if it makes sense?  Thanks!

Closing as #234 is merged.

Re-opening.  If you happen to try to create a machine with the same name as an existing machine, this will remove the old one.

Yes.  As mentioned in IRC but I actually have changed my mind on the PR that was submitted to address this due to discussion with @bfirsh and @SvenDowideit.  Auto-remove seems to be causing too many problems, I was wrong.  If you CTRL+C in the middle of a create, for instance, the reference will not get cleaned up.
I think leaving the machines around in an error state is fine.  However, I don't really like the extra "ERROR" logs that pop up when you run machine ls or something if the state of the machine is Error.

Ok thx.  I agree with the extra logging.  I would like to clean up logging
in general as each driver seems to do its own thing.
On Mon, Jan 19, 2015 at 2:45 PM, Nathan LeClaire<EMAIL_ADDRESS>wrote:

Yes. As mentioned in IRC but I actually have changed my mind on the PR
that was submitted to address this due to discussion with @bfirsh
https://github.com/bfirsh and @SvenDowideit
https://github.com/SvenDowideit. Auto-remove seems to be causing too
many problems, I was wrong. If you CTRL+C in the middle of a create, for
instance, the reference will not get cleaned up.
I think leaving the machines around in an error state is fine. However, I
don't really like the extra "ERROR" logs that pop up when you run machine
ls or something if the state of the machine is Error.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/issues/119#issuecomment-70549580.

I think I will close this as we've reverted the auto-cleanup and fixed some of the logging.  We are looking to standardize the way we handle common tasks (create, remove, etc) and I think the error reporting can be a part of this.  We can use #392 to track that.

I've managed to remove it by removing the right folder from here ~/.docker/machine/machines/
Origin: https://www.digitalocean.com/community/questions/can-t-remove-a-docker-machine
Sorry for commenting on an old thread but I googled it and thought it might help others.
A thought: maybe the rm -f should be able to remove even if there's no connection.

A thought: maybe the rm -f should be able to remove even if there's no connection.

Especially if the error is that the instance doesn't exist (anymore) 😅


Validate data type and item nesting within answers for repeated answers while prefilling UI with a Questionnaire response

We need to validate the Questionnaire Response structure with that of the Questionnaire before prefilling the UI. This is to make sure that this particular questionnaire response has been generated by answering the current questionnaire.
Currently we only validate nesting of item within group and the linkId.
We will also have to add checks to make sure:

The data type of the questionnaire-item and questionnaireResponse-item match
Item nesting within answers #274

This is an improvement related to #244

Can i work on this if available

@kartikeysaran can you briefly describe what's needed to be done and your plan here? thanks!


[FancyZones] Cleanup

Summary of the Pull Request
What is this about:
Some cleanup I think would be beneficial.
What is include in the PR:

Rename zoneUuid -> zoneLayoutUuid: The variable holds the UUID of the layout (not of a zone).
Rename m_activeZoneSet -> m_zoneSet: There is only one zone set used by a work area.
Refer to the current move/size action as active
Complete renaming ZoneWindow to WorkArea: Fix leftovers from "[FancyZones] Rename ZoneWindow -> WorkArea (#12223)"
Move adjustment of RECT to utils.cpp: By doing so, also fix a bug where a non-WS_SIZEBOX window (a window that should not be resized) was resized (and not properly resized) if it was zoned into more than one zone.
Remove obsolete code: The field m_windows is unused, and may be removed.
Remove obsolete code: The field m_zoneSets is unused, and may be removed.

How does someone test / validate:
Quality Checklist

[ ] Linked issue: #xxx
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

I think it also worth thinking about:

Removing the COM interfaces (IFACEMETHOD_, etc.) and just use the classes themselves
Renaming ZoneSet -> ZoneLayout
Remove m_windowIndexSet (it is not thoroughly maintained, and, actually, is a copy or the zone set stamps)
Create a class to encapsulate ZoneIndexSet, including limiting the amount of zones to 64 (which now plays a part only in zone set stamps)

Hi @FLOAT4 ,
Thanks for opening the PR.
It seems there are some conflicts here.
Another old PR that just got in seems to have caused them: https://github.com/microsoft/PowerToys/commit/3a6dd45741c16b97c6e92758367bcfbcc0b3e261
Could you please fix the conflicts before we get this into review?

Rebased.

@stefansjfw What is missing in the zoneWindow -> workArea renaming?
Are you referring to ZoneWindowDrawing? If so, what should the name be? I think WorkAreaDrawing isn’t clear enough. How about ZonesDrawing?

I reverted the deletion. Anything else?

@stefansjfw What is missing in the zoneWindow -> workArea renaming?
Are you referring to ZoneWindowDrawing? If so, what should the name be? I think WorkAreaDrawing isn’t clear enough. How about ZonesDrawing?

ZonesDrawing sounds clear. Let's leave this to separate PR.

OK. I do not have write access, so please merge when possible.

Great! Please merge when possible (I do not have write access).


Call to undefined function App\Http\Controllers\Admin\activity()

Hello,
I have followed the steps in

https://docs.spatie.be/laravel-activitylog/v3/installation-and-setup/

and everything working fine on local host...and now i pushed the code to live server and just run
php artisan migrate

and it creates the table and everything looks fine in command line.
But while i run the site it shows the error.

Call to undefined function App\Http\Controllers\Admin\activity()

Hey,
just to be sure: have you run composer update/install and composer dump-autoload on your production server?
The function is part of the package and the file is loaded via composer autoloading.
So as long as the package is installed via composer everything should be fine.
Nearly all times this comes down to a failed composer step during deployment.

@Gummibeer Thank you.

The function is part of the package and the file is loaded via composer autoloading.
So as long as the package is installed via composer everything should be fine.
Nearly all times this comes down to a failed composer step during deployment

anyone can help me in this error??
Call to undefined function App\Http\Controllers\Admin\unique()

Hey,
just to be sure: have you run composer update/install and composer dump-autoload on your production server?
The function is part of the package and the file is loaded via composer autoloading.
So as long as the package is installed via composer everything should be fine.
Nearly all times this comes down to a failed composer step during deployment.

https://github.com/spatie/laravel-activitylog/issues/718#issuecomment-618237178


[docs] Fix md files to use styleOverrides instead of overrides

[x] I have followed (at least) the PR section of the contributing guide.

Fix #22476

@discodanne It's a great first pull request on Material-UI 👌🏻. Thank you for working on it!


Broken SslEngine [set|get]EnabledCipherSuites behavior

Expected behavior
The resultant SslEngine instances would obey the contract set forth in the Java docs here.
Actual behavior
When we set the supported ciphers to a single v1.2 suite we see that TLSv1.3 ciphers are present in the supported ciphers. Specifically, we see supported ciphers such as
"TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256", "TLS_AES_128_GCM_SHA256", "TLS_AES_256_GCM_SHA384", "TLS_CHACHA20_POLY1305_SHA256"

Minimal yet complete reproducer code (or URL to code)
Repro here: https://github.com/bryce-anderson/netty/commit/09fc8d1eef9e77b603fb081db848a1cafcc23102
Netty version
4.1 (as of Jan 2, SHA 0dc246eb1297963)
JVM version (e.g. java -version)
Java 8
OS version (e.g. uname -a)
OSX

I guess that comes from the fact that BoringSSL has no notion to explict disable TLS1.3 ciphers and only either allow to enable it or disable TLS1.3 all together. Let me have a look tho

I guess that comes from the fact that BoringSSL has no notion to explict disable TLS1.3 ciphers and only either allow to enable it or disable TLS1.3 all together. Let me have a look tho

@bryce-anderson thanks for the test... I think I have a fix... Will open a PR soonish

@bryce-anderson thanks for the test... I think I have a fix... Will open a PR soonish

@bryce-anderson PTAL https://github.com/netty/netty/pull/10919

@bryce-anderson PTAL https://github.com/netty/netty/pull/10919


Fix commit expand button to not go to commit link

Currently when clicking expand button in commit message it will expand and trigger also commit link click that will lead to opening commit diff page.
See https://try.gitea.io/jueti/learn-regex

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f694bb4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #8745   +/-   ##
=========================================
  Coverage          ?   41.36%
=========================================
  Files             ?      538
  Lines             ?    69317
  Branches          ?        0
=========================================
  Hits              ?    28675
  Misses            ?    36948
  Partials          ?     3694

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 f694bb4...bd3ebee. Read the comment docs.

Noticed this too. A better fix be to not wrap the expander button and expanded content in the <a> tag so that the link hover highlight does not include that expanded content.

@silverwind fixed that also :)

@lafriks @silverwind it's actually not wrapped with . there is a bug something else.
when you look at source code  last a tag does not closing

@jaqra I already fixed that in latest commit :)

Functionality-wise, this is LGTM.

@lafriks Please send back port to v1.10


Train and evaluate with custom dataset

Hi, I wanna ask if there are any code versions which is available for training or testing on a custom dataset. It seems that the current code doesn't support this and the format of data is not stated.
It would be really helpful if you can give the code for converting to your data format, or a note on how to organize the data files to run the code. Thank you in advance!

Hi!
We appreciate your interest in our work. We added a section for custom datasets in the readme (https://github.com/aleflabo/MoCoDAD/blob/main/README.md#custom-datasets-preparation).
You can find the structure of the HR-UBnormal dataset here: https://drive.google.com/drive/u/1/folders/1h-dBNkAZdmgtlRd-TB8ScyHLshogTrLb


Building wheel for go-vncdriver (setup.py) ... error +. Setup: MacOS Mojave + Python 3.5

I have this message when I try to install Universe or vncdriver.
¿Someone can help me plz?
Building wheel for go-vncdriver (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /Users/dennis/virtualenvs/relearning/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py'"'"'; file='"'"'/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-wheel-tga4kfq9
cwd: /private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/
Complete output (55 lines):
running bdist_wheel
running build
Running new build
Env info:
export GO15VENDOREXPERIMENT='1'
export CGO_CFLAGS='-I/Users/dennis/virtualenvs/relearning/lib/python3.5/site-packages/numpy/core/include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m'
export CGO_LDFLAGS='/usr/local/opt/jpeg-turbo/lib/libjpeg.dylib -undefined dynamic_lookup'
export GOPATH='/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/.build'
Running build with OpenGL rendering.
Building with OpenGL: GOPATH=/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/.build go build -buildmode=c-shared -o go_vncdriver.so github.com/openai/go-vncdriver. (Set GO_VNCDRIVER_NOGL to build without OpenGL.)
no required module provides package github.com/openai/go-vncdriver: working directory is not part of a module
Note: could not build with OpenGL rendering (cf https://github.com/openai/go-vncdriver). This is expected on most servers. Going to try building without OpenGL.
Building without OpenGL: GOPATH=/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/.build go build -tags no_gl -buildmode=c-shared -o go_vncdriver.so github.com/openai/go-vncdriver
no required module provides package github.com/openai/go-vncdriver: working directory is not part of a module
Could not build go_vncdriver:
Build failed. HINT:

Ensure you have your Python development headers installed. (On Ubuntu,
this is just 'sudo apt-get install python-dev'.

Traceback (most recent call last):
File "", line 1, in
File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py", line 75, in
install_requires=['numpy'],
File "/Users/dennis/virtualenvs/relearning/lib/python3.5/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/core.py", line 148, in setup
dist.run_commands()
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/Users/dennis/virtualenvs/relearning/lib/python3.5/site-packages/wheel/bdist_wheel.py", line 299, in run
self.run_command('build')
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py", line 23, in run
self.build()
File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py", line 61, in build
build.build()
File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/build.py", line 114, in build
build_no_gl()
File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/build.py", line 95, in build_no_gl
''')
build.BuildException:
Build failed. HINT:

Ensure you have your Python development headers installed. (On Ubuntu,
this is just 'sudo apt-get install python-dev'.

ERROR: Failed building wheel for go-vncdriver
Running setup.py clean for go-vncdriver
Building wheel for gym (setup.py) ... done
Created wheel for gym: filename=gym-0.7.4-py3-none-any.whl size=204692 sha256=cae48942ac7de8ed26c1fae04761ee51e0c08534dfb302d310340232ea13f79a
Stored in directory: /Users/dennis/Library/Caches/pip/wheels/c5/26/38/1e640c85a7db5871613e0d569c4297fff415d595a144671944
Successfully built gym
Failed to build go-vncdriver
Installing collected packages: gym, go-vncdriver, fastzbarlight, docker-py, autobahn, universe
Attempting uninstall: gym
Found existing installation: gym 0.17.3
Uninstalling gym-0.17.3:
Successfully uninstalled gym-0.17.3
Running setup.py install for go-vncdriver ... error
ERROR: Command errored out with exit status 1:
command: /Users/dennis/virtualenvs/relearning/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py'"'"'; file='"'"'/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-record-eu0nyupl/install-record.txt --single-version-externally-managed --compile --install-headers /Users/dennis/virtualenvs/relearning/include/site/python3.5/go-vncdriver
cwd: /private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/
Complete output (57 lines):
running install
running build
Running new build
Env info:
export GOPATH='/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/.build'
export CGO_LDFLAGS='/usr/local/opt/jpeg-turbo/lib/libjpeg.dylib -undefined dynamic_lookup'
export CGO_CFLAGS='-I/Users/dennis/virtualenvs/relearning/lib/python3.5/site-packages/numpy/core/include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m'
export GO15VENDOREXPERIMENT='1'

Running build with OpenGL rendering.
Building with OpenGL: GOPATH=/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/.build go build -buildmode=c-shared -o go_vncdriver.so github.com/openai/go-vncdriver. (Set GO_VNCDRIVER_NOGL to build without OpenGL.)
no required module provides package github.com/openai/go-vncdriver: working directory is not part of a module

Note: could not build with OpenGL rendering (cf https://github.com/openai/go-vncdriver). This is expected on most servers. Going to try building without OpenGL.
Building without OpenGL: GOPATH=/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/.build go build -tags no_gl -buildmode=c-shared -o go_vncdriver.so github.com/openai/go-vncdriver
no required module provides package github.com/openai/go-vncdriver: working directory is not part of a module
Could not build go_vncdriver:
Build failed. HINT:

- Ensure you have your Python development headers installed. (On Ubuntu,
  this is just 'sudo apt-get install python-dev'.

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py", line 75, in <module>
    install_requires=['numpy'],
  File "/Users/dennis/virtualenvs/relearning/lib/python3.5/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/Users/dennis/virtualenvs/relearning/lib/python3.5/site-packages/setuptools/command/install.py", line 61, in run
    return orig.install.run(self)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/command/install.py", line 539, in run
    self.run_command('build')
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py", line 23, in run
    self.build()
  File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py", line 61, in build
    build.build()
  File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/build.py", line 114, in build
    build_no_gl()
  File "/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/build.py", line 95, in build_no_gl
    ''')
build.BuildException:
Build failed. HINT:

- Ensure you have your Python development headers installed. (On Ubuntu,
  this is just 'sudo apt-get install python-dev'.

----------------------------------------

ERROR: Command errored out with exit status 1: /Users/dennis/virtualenvs/relearning/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py'"'"'; file='"'"'/private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-install-dks8lxlo/go-vncdriver_2d414f74052047c998a5e5a51a457ed5/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /private/var/folders/cw/264vdnpj2qv5jvm2clnnx7dm0000gn/T/pip-record-eu0nyupl/install-record.txt --single-version-externally-managed --compile --install-headers /Users/dennis/virtualenvs/relearning/include/site/python3.5/go-vncdriver Check the logs for full command output.

Have you solved it yet?


Investigate root cause of overwritten MCap polyfill on Safari

In #3530, the MCap polyfill is being overwritten on Safari.  It's not clear what is causing this.  @joeyparrish could not reproduce the issue, but @theodab could.
PR #3668 gave us a workaround, but we still haven't addressed the root cause.  It would be preferable to find the root cause of the issue, revert the PR, and merge a fix that addresses the root cause.

I'm able to reproduce the original issue on Safari 15.1.  Previously, I was unable to reproduce it in Safari 14.1.

The issue is timing-related.  With breakpoints enabled in the polyfill installation, the problem vanishes.

Delaying the polyfill by 5 seconds seems to work around the issue.  With that, content shared with us privately via #3530 gets past the original 6010 error (and instead fails a license request).

I was trying to determine if/when/how the property for decodingInfo was being overwritten, and I may have stumbled onto a good clue.
I first changed the polyfill to:

Set decodingInfo
Use Object.defineProperty to make the property non-writeable
Check 5 seconds later if the value was still what I set it to

After 5 seconds, the value had been reset every time (presumably by the platform).  But I couldn't be sure if it was decodingInfo or the mediaCapabilities parent of decodingInfo which was being reset.
So then I changed the polyfill to:

Set decodingInfo
Make a local copy of the value of mediaCapabilities
Use Object.defineProperty as before
Check both the values of decodingInfo and mediaCapabilities after 5 seconds

And magically... both were the same now!  And consistently when reloading the page to try again.
So here's my theory.  It may be that navigator.mediaCapabilities is a getter which returns a new MediaCapabilities object on-demand, which is later garbage-collected when not referenced.  Creating a local copy that is used later in a closure seems to keep our modifications in the polyfill from being undone.
I'll experiment with this more and see if this could be a viable fix.


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210716093808543 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210716093808543 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 42.75%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
26253

Relevant Lines:
55746

💛  - Coveralls


[New chain]: Haqq network testnet

ChainId
54211
Chainlist
https://chainlist.org/chain/54211
Contract deployed

[X] I confirm that the contracts are deployed

Version of contracts deployed
v1.3.0
Relevant information
Explorer: https://explorer.testedge2.haqq.network/
Docs: https://docs.haqq.network/
https://islamiccoin.net/

Is there any faucet which I can use to get some ISLM coins and do some transactions?

Is there any faucet which I can use to get some ISLM coins and do some transactions?

https://testedge2.haqq.network/


[INLONG-2193] optimize inlong manager structure

Title Name: [INLONG-XYZ][component] Title of the pull request
where XYZ should be replaced by the actual issue number.
Fixes #2193
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@healchow PTAL

Codecov Report

Merging #2195 (a5b98e1) into master (e60f461) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2195   +/-   ##
=========================================
  Coverage     12.58%   12.59%
- Complexity     1207     1208    +1
=========================================
  Files           417      417
  Lines         35735    35735
  Branches       5590     5590
=========================================
+ Hits           4498     4500    +2
+ Misses        30435    30433    -2
  Partials        802      802

Impacted Files
Coverage Δ

.../producer/qltystats/DefaultBrokerRcvQltyStats.java
45.31% <0.00%> (-0.40%)
:arrow_down:

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
34.51% <0.00%> (+0.44%)
:arrow_up:

.../inlong/tubemq/corebase/policies/FlowCtrlItem.java
40.00% <0.00%> (+1.11%)
: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 e60f461...a5b98e1. Read the comment docs.


Update devInternalSettings

Summary:
The ReactAndroidCodeTransformer did not make the necessary modifications during the RN upgrade.

@Kudo I've fixed it and added it to my android PR for the expo go migration. JavaParser is not really suitable for modifying kotlin code and RN will continue migrating classes to it so we so we should look for better solutions for doing this.

@Kudo I've fixed it and added it to my android PR for the expo go migration. JavaParser is not really suitable for modifying kotlin code and RN will continue migrating classes to it so we so we should look for better solutions for doing this.

makes sense. in this case, maybe we can edit in-place and drop the ReactAndroidCodeTransformer. let's discuss this in sdk sync.


Agent start up speed

Agent start up speed
Hetzner
An agent from Hetzner takes ~1 minute to start:
 Network root_default  Creating
 Network root_default  Created
 Container root-woodpecker-agent-1  Creating
 Container root-woodpecker-agent-1  Created
 Container root-woodpecker-agent-1  Starting
 Container root-woodpecker-agent-1  Started
 The system is finally up, after 44.14 seconds

And whats the issue?

Nothing for now. Just wanted to document the different speeds of the providers, but didn't wanted to push a file


Add argument expectation matcher support

Support argument expectation matchers and not just literal values. Matchers like kind_of, no_args, any_args, and regexes.

I found myself needing this too.
FWIW, this works with the anything matcher as well. I added a spec to @cgriego's branch to verify it: 45b9273b99eb70d30c8c5f397b48bc9058fc3e7a.

I've merged the spec from @therealadam into my pull request.


[REFACTOR] Example with the new version

Hey there,
I noticed some of examples wasn't working for the new version so i wanted to help by correcting them.
But i couldn't figure out how to fix the middleware example, the Transform trait seems not available anymore and im not sure what is the replacement.
As well as the websocket examples the on_shutdown callback seems not existing and it make the heartbeat stop because the variable drop if we just remote it.
Thank for your work and time.

Transform is renamed to Middleware.

regarding "on_shutdown". I changed FnService in new version of ntex-service, now it does not provide shutdown handler. But it is possible to create special service, something like FnShotdown, that would provide same functionality

Hey based on your commentary i update the websocket example to use the Service Trait.
What do you think of the implementation ?
If you like it i can update websocket-chat and websocket-tcp-chat using the same way

I think we can move FnShutdown type to ntex-service crate. I've been thinking about something like FnShutdown<S, F: FnOnce>

Sure as you wish, i'll try to do it and make a pull request during the day!

So i updated example to your latest version 6.0.2 that include fn_shutdown and refactored the websocket example to use it.
I also corrected the middleware example but i coudn't make compile the file read_response_body.rs kind of lifetime problem that i coudn't figure out how to solve it..

here is code:

impl<S, Err> Service<WebRequest<Err>> for LoggingMiddleware<S>
where
    S: Service<WebRequest<Err>, Response = WebResponse, Error = Error>,
    Err: 'static,
{
    type Response = WebResponse;
    type Error = Error;
    type Future<'f> = BoxFuture<'f, Result<WebResponse, Error>> where Self: 'f;

    ntex::forward_poll_ready!(service);

    fn call(&self, req: WebRequest<Err>) -> Self::Future<'_> {
        Box::pin(async move {
            self.service.call(req).await.map(|res| {
                res.map_body(move |_, body| {
                    Body::from_message(BodyLogger {
                        body,
                        body_accum: BytesMut::new(),
                    })
                    .into()
                })
            })
        })
    }
}

Thx i updated the middleware example.
I used :
Err: ErrorRender

instead of
Err: 'static

Maybe you don't want that ?

@leon3s can you look at websoket-tcp-chat example error?
WS client drop connection immediately.
on this PR
$ git log -n 1
commit 2354c61ebf630e05903fea4c50e90e6e1e47fa67 (HEAD -> fix-websocket-and-server-sent-events, origin/fix-websocket-and-server-sent-events)
Author: leon3s<EMAIL_ADDRESS>Date:   Wed Jan 25 13:53:29 2023 +0100

    [REFACTOR] Rustfmt

Server output
RUST_LOG=trace cargo run --bin websocket-tcp-chat-server
    Finished dev [unoptimized + debuginfo] target(s) in 0.12s
     Running `/home/user/tmp/fork-examples/target/debug/websocket-tcp-chat-server`
Started chat server
[2023-02-06T07:21:42Z INFO  ntex::server::builder] Starting 12 workers
[2023-02-06T07:21:42Z INFO  ntex::server::builder] Starting "tcp" service on <IP_ADDRESS>:12345
[2023-02-06T07:21:42Z INFO  ntex::server::builder] Starting "websockets" service on <IP_ADDRESS>:8080
[2023-02-06T07:21:42Z INFO  ntex::server::accept] Starting socket listener on <IP_ADDRESS>:12345
[2023-02-06T07:21:42Z INFO  ntex::server::accept] Starting socket listener on <IP_ADDRESS>:8080
Someone joined

Client output
RUST_LOG=trace cargo run --bin websocket-tcp-chat-client
    Finished dev [unoptimized + debuginfo] target(s) in 0.12s
     Running `/home/user/job/tmp/fork-examples/target/debug/websocket-tcp-chat-client`
[2023-02-06T07:21:48Z TRACE ntex::ws::client] Open ws connection to http://<IP_ADDRESS>:8080/ws/ addr: None
[2023-02-06T07:21:48Z TRACE ntex_connect::service] TCP connector - connecting to "<IP_ADDRESS>" port:8080
[2023-02-06T07:21:48Z TRACE ntex_connect::service] TCP connector - successfully connected to connecting to "<IP_ADDRESS>" - Some(<IP_ADDRESS>:8080)
[2023-02-06T07:21:48Z TRACE ntex::ws::client] Sending ws handshake http message
[2023-02-06T07:21:48Z TRACE ntex::ws::client] Waiting for ws handshake response
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Disconnected(None)', websocket-tcp-chat/src/client-ws.rs:21:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Panic in Arbiter thread.

Hey @estin I mostly tested the websocket example.
The problem seems to came from how the ID is retrieve, the unbounded channel is already disconnected when to send the ID in this function:
websocket-tcp-chat/src/server.rs:108
rt::spawn(async move {
    println!("Send id back: {id}");
    let _res = sender.send(ClientMessage::Id(id)).await;
    println!("{_res:#?}");
});

Im not sure why i tried couple thing to fix it but i don't really have time right now i'll investigate further later.
If you remove the function that send the connect event and wait the id it work fine.
websocket-tcp-chat/src/web.rs:70

@leon3s thanks!
This is result of my research about client disconnect over http upgrade request

bug related to h1/Dispatcher and upgrade request logic
if comment line on commit https://github.com/ntex-rs/ntex/commit/7da66512ee8a55b4cb1c7818e3b027c610662e29#diff-5a96ae4150630a4e13848b56c1cf5f8c6660d254766b91e5ddb050bc2c47aeffR220  all works fine

Dispatcher stops when io has flags IO_STOPPED | IO_STOPPING | IO_STOPPING_FILTERS | DSP_STOP
On upgrade request called self.io.take() ->  io.take()  create new io with this flags IO_STOPPED | IO_STOPPING | IO_STOPPING_FILTERS | DSP_STOP
There two ways to make this example works

don't wait client id from unbound channel https://github.com/ntex-rs/examples/pull/13#issuecomment-1418881511
comment line *this.st = State::Stop;

Don't understand how they related.

I will check later this week


Enabled go mod vendor

closes #10

Pull Request Test Coverage Report for Build 274682989

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.299%

Totals

Change from base Build 274663791:
0.0%

Covered Lines:
126

Relevant Lines:
291

💛  - Coveralls


Request for ARCH

Hi,
Can you please create a git-watcher AUR for "v0.5.2" ?, if not, do you mind if I'll do it ?
Thanks :)

No help at all :(

Sorry, I saw that there were no changes to the project for some time and I thought you abandoned it, if this is still active I'll create the new AUR packages :)

Yes, next week I'll start working on this again. New build with recent version of nw.js coming soon.


Support Android file upload

There are already a lot of forks of the official webview to support that feature, there is no reason not to add it to that repo.
Let review all of them and we can discuss about implementation here.

One reference is react-native-webview-android: https://github.com/lucasferreira/react-native-webview-android#note-about-html-file-input-files-upload

@Titozzz do you have any good development workflow on how to use react-native-webview package in an example RN project, but from an external folder?

:tada: This issue has been resolved in version 2.10.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


DS defined with LikeDS has spurious End_DS added

For example:
     d source          ds                  likeds(QtqCode_t)
     d                                     inz(*likeds)
     d target          ds                  likeds(QtqCode_t)
     d                                     inz(*likeds)
     d toEBC           ds                  likeds(iconv_t)

Incorrectly converts to:
       Dcl-DS source  likeds(QtqCode_t) inz(*likeds);
        End-DS;
       Dcl-DS target  likeds(QtqCode_t) inz(*likeds);
        End-DS;
       Dcl-DS toEBC  likeds(iconv_t);
        End-DS;

Note: If a single DS of the orininal is highlighted and convereted it works correctly. Only when the whole group is converted does it get it wrong.

Sorry for my multiple commits related to this issue.  I kept thinking I was doing something wrong in my commit message as the issues were linked, but not closed.  I think linking to an issue will auto-close only if you are the creator of the issue.  So, the pull request #79 from the BrianGodsend/vscode-rpgfree fork does fix this issue.


update cross_region_location variable description in the cross regional bucket DA

Remove "If specified, set the value of region and single_site_location to null." from here -> https://github.com/terraform-ibm-modules/terraform-ibm-cos/blob/3cec7c56215fbe6892791e9e31ed6a47bb5e4244/solutions/secure-cross-regional-bucket/variables.tf#L78
These vars are not in this DA

Complete in #675 version 8.8.5


Add recipe for Electron

Write guide on how to debug both Electron processes via composites
launch.json
{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Electron: Main",
            "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron",
            "runtimeArgs": [
                "--remote-debugging-port=9222",
                "."
            ],
            "windows": {
                "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron.cmd"
            }
        },
        {
            "name": "Electron: Renderer",
            "type": "chrome",
            "request": "attach",
            "port": 9222
        }
    ],
    "compounds": [
        {
            "name": "Electron: All",
            "configurations": [
                "Electron: Main",
                "Electron: Renderer"
            ]
        }
    ]
}

@auchenberg yes, a Electron recipe is really needed...
And with VS Code 1.14 it is getting simpler. The Windows specific runtimeExecutable should no longer be needed.

Found an old electron demo app https://github.com/auchenberg/electron-quick-start-vscode

Hi guys, I am new to VS Code, as well as remote debugging with Chrome in general, so I have a basic question:
I have an internal Electron app that I would like to use the VS Code debugger on. I pasted in the above into my VS Code launch.json file. I then hit F5 to run and everything seems to launch ok, but I don't know what to do next, like what URL to go in Chrome based on this output:
Debugging with inspector protocol because a runtime executable is set.
/Users/rishi/Projects/albert/albert-support-desktop/node_modules/.bin/electron --inspect=45437 --debug-brk --remote-debugging-port=9222 .
Debugger listening on port 45437.
Warning: This is an experimental feature and could change at any time.

I tried poking around on chrome://inspect/ but don't see anything on the various tabs that seems relavent. I feel like I am missing something pretty basic here.
Here is a screenshot of of my VS Code:

@rkpatel33 Your setup looks correct, and it looks like your Electron app has a few script errors, which are displayed in the debug console.
You don't need Chrome DevTools or chrome://inspect but you should be able to go to your Electron JavaScript files and set breakpoints from within VS Code.

Thanks for the reply. So the breakpoints are working now, and I am also able to see a list of all the processes running in chrome://inspect. Both of these things weren't happening (I think) before. So I seem to be all good!

Bug found for our composite configuration: https://github.com/Microsoft/vscode-chrome-debug/issues/501


Build error on Flatpak with the FreeDesktop 21.08 runtime: size_t has not been declared

SHADERed version: 1.5.4 (could be reproduced with 1.4.3 too)
While trying to update the Flatpak to use the latest FreeDesktop SDK version, I'm getting the following build error:
/run/build/shadered/libs/ShaderExpressionParser/Tokenizer.h:50:39: error: ‘size_t’ has not been declared
   50 |         Tokenizer(const char* buffer, size_t bufLength);
      |                                       ^~~~~~

This is not an issue with the older FreeDesktop 20.08 runtime because it uses an older GCC version. See this comment for the reason: https://github.com/flathub/org.shadered.SHADERed/pull/15#issuecomment-920460902

Thanks for reporting, it should be fixed. I don't think size_t was needed there anyway.


References

Hi, thanks for making this theme, it looks really nice :+1:
The changes in this PR allow users to add references to their CVs. It reuses the icons from the contact element, but given the background colours of the two areas may be different, I've added more descriptive configs in config.toml, which can be used to change just parts of the page.
Here's a picture of the example site with the added references:

Happy to receive any feedback, and thanks again!

Looks good to me :+1:


Fatal Error: Uncaught Exception with message: [ssl:hostname:6380] in AbstractConnection.php

I'm running my PHP app on an Azure Web App with Predis connecting to an Azure Redis Cache, under their SSL enabled 6380 port. I'm using the fork of this library that supports SSL.
My app consists of two parts, a client-side JS that sends AJAX requests to the PHP app for the HTML of the app (and in mosts cases, the App performs an API call before spitting out relevant HTML).
I'm using the Predis Session Handler, and also storing a variety of other non-user specific data. This is what my code looks like: -
$redis = new Predis\Client($settings);

try {
    $redis->connect();
} catch (Predis\Connection\ConnectionException $exception) {
    new error("Redis.Connect()", array($redis, $exception));
    while (true) {
        usleep(200000);
        try {
            $redis->connect();
            break;
        }
        catch (Predis\Connection\ConnectionException $exception) {}
    }
}

$sessHandler = new Predis\Session\Handler($redis);
session_set_save_handler($sessHandler);
session_id($sessId);
session_start();

In order to prevent the exception I'm getting from happening, I set up a while loop to run indefinitely to try and connect to Redis (assuming 99.99% availability of the Azure Redis Cache). If it fails, it will generate an entity in Azure Tables logging the fail.
It's generating tons of errors, it seems to fail to connect to Redis pretty much all the time, even though the Redis server itself has low load, with few clients connected. It always eventually connects, but with the while loop it ends up hemorrhaging performance.
Is there some way to address this issue? At other times, I get an error that that host/socket/port is in use and another connection can't be opened. Any ideas?

The more common error that I seem to be getting is this: -
Fatal error: Uncaught exception 'Predis\Connection\ConnectionException' with message 'Only one usage of each socket address (protocol/network address/port) is normally permitted.
How do I fix this?

@justin-frenzel the SSL feature is not battle tested and honestly I've never even tried using it on Windows systems yet. That said, on Windows the "Only one usage of each socket address (protocol/network address/port) is normally permitted" error usually suggests that the OS has no more available ports so it cannot reserve new ones for creating new connections (e.g. too many connections in TIME_WAIT state). See also https://msdn.microsoft.com/en-us/library/aa560610(v=bts.20).aspx for a description of the problem.
I'm not able to replicate the issue right now but if you are using PHP >= 5.4.0 you can modify the Predis\Connection\StreamConnection class by adding here the following lines:
$socket = socket_import_stream($resource);
socket_set_option($socket, SOL_TCP, SO_REUSEADDR, 1);

See if anything changes and please report back.
Thanks

I'm closing this issue due to the lack of feedback and the inability to reproduce it, but feel free to add more details if they can help tracing the source of the problem.

We were having the same problem with the connections to Redis and we saw this issue. In spite of being closed, I would like to comment out that this can be solved in Laravel (afaik from 5.2 to 5.4 and predis 1.1) adding the option 'persistent' => true, to the Redis connection in the file config/database.php:
'redis' => [
        'cluster' => false,
        'default' => [
            'host'     => env('CACHE_HOST', '<IP_ADDRESS>'),
            'port'     => env('CACHE_PORT', 6379),
            'password' => env('CACHE_PASSWORD', ''),
            'database' => 0,
            'persistent' => true, // This option
        ],
    ],


Operator hangs on Reconciler error

Bug Report

What did you do?
Created a secret with a wrongly formatted .dockerconfigjson. This results in:
fatal: [localhost]: FAILED! => {"changed": false, "error": 400, "msg": "Failed to create object: b'{\"kind\":\"Status\",\"apiVersion\":\"v1\",\"metadata\":{},\"status\":\"Failure\",\"message\":\"Secret in version \\\\\"v1\\\\\" cannot be handled as a Secret: v1.Secret.ObjectMeta: v1.ObjectMeta.TypeMeta: Kind: Data: decode base64: illegal base64 data at input byte 0, error found in #10 byte of ...|son\\\\\":\\\\\"secret\\\\\"},\\\\\"kind\\\\\":\\\\\"|..., bigger context ...|apiVersion\\\\\":\\\\\"v1\\\\\",\\\\\"data\\\\\":{\\\\\".dockerconfigjson\\\\\":\\\\\"secret\\\\\"},\\\\\"kind\\\\\":\\\\\"Secret\\\\\",\\\\\"metadata\\\\\":{\\\\\"labels\\\\\":{\\\\\"myapi.s|...\",\"reason\":\"BadRequest\",\"code\":400}\\n'", "reason": "Bad Request", "status": 400}

The operator stop reconciling the other resources in the cluster and only shows:
{"level":"error","ts":1608116082.7651885,"logger":"controller","msg":"Reconciler error",
"controller":"myresource-controller","name":"team132","namespace":"operator","error":"event runner on failed","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error
\t/home/travis/gopath/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
\t/home/travis/gopath/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:246
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
\t/home/travis/gopath/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:218
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
\t/home/travis/gopath/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:197
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1
\t/home/travis/gopath/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:155
k8s.io/apimachinery/pkg/util/wait.BackoffUntil
\t/home/travis/gopath/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:156
k8s.io/apimachinery/pkg/util/wait.JitterUntil
\t/home/travis/gopath/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:133
k8s.io/apimachinery/pkg/util/wait.Until
\t/home/travis/gopath/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:90"}

Starting it new, allows for some reconciliations before it crashes again.
What did you expect to see?
Since the content in the resources can be configured by users, I would have hoped that the operator keeps on reconciling.
What did you see instead? Under which circumstances?
See above.
Environment
Operator type:

/language ansible

Kubernetes cluster type:
Vanilla K8s cluster
$ operator-sdk version

On my workstation:
operator-sdk version: "v1.1.0", commit: "9d27e224efac78fcc9354ece4e43a50eb30ea968", kubernetes version: "v1.18.2", go version: "go1.15.2 darwin/amd64", GOOS: "darwin", GOARCH: "amd64"
Deployed is version 1.2.0
$ kubectl version

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T23:35:15Z", GoVersion:"go1.14.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.4", GitCommit:"d360454c9bcd1634cf4cc52d1867af5491dc9c5f", GitTreeState:"clean", BuildDate:"2020-11-11T13:09:17Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Possible Solution

Additional context

Closing the issue as it seems resolved when reconcilePeriod is defined.


Brand new type of component store injection

Hey all. I want to suggest you new, good from typescript view store-to-component injection mechanism.
This is working example:
class Store {
  @observable items: string[];
}
class RootComponent extends React.Component<void, void> {
  @inject
  private store: Store;

  render() {
    return
{this.store.items.map(i =>
{i}
}
;
  }
}

ReactDOM.render(
  <StoresProvider><RootComponent /></StoresProvider>
)

Implementation details
Thanks to typescript emitDecoratorMetadata feature, information about type of RootComponent.store available at runtime. So, @inject decorator can define getter at that field, which gather Store instance from context. Context provided by StoresProvider component, which manage instances of requested stores too.
For javascript it is possible to pass store class to inject decorator: @inject(Store)
What do you think about it? Is it fittable to this package, ot mobx-react, or maybe separated package?

@Strate I think it looks cool! I would only consider the decorator version, for non-typed environments without decorators the old syntax is fine I think.

I've been experimenting with something very similar to this:
import React from 'react';

export const injectable = (target: Function) => {
    if (!('contextTypes' in target)) {
        target['contextTypes'] = {};
    }
    const contextTypes = target['contextTypes'];
    if (!('mobxStores' in contextTypes)) {
        contextTypes['mobxStores'] = React.PropTypes.object;
    }
};

export const inject = (name: string) => {
    return (target: Object, propertyKey: string | symbol) => {
        Object.defineProperty(target, propertyKey, {
            get: function(this: React.Component<any, any>) {
                return this.context['mobxStores'][name];
            },
            enumerable: false,
            configurable: false
        });
    };
};

Basically put @injectable on your component, then @inject on a field:
@injectable
public class TestComponent extends React.Component<any, void> {
    @inject('color') private _color: string; // === "red"
}

// ...

<Provider color='red'>
    <TestComponent />
</Provider

I'm sure it could be streamlined (the @injectable decorator feels superfluous), but it works. I'm curious to know what the pros and cons are that I can't see? Injecting context into props has always felt weird with mobx-react - I know Redux does it, but MobX has it's own way of handling changing data that aren't reliant on React's idea of changing props.

@jamiewinder almost same technique used in my project, With exception of @injectable - operations from it performed on first @inject

@Strate - I tried that and it didn't seem to work. I think I'll give that another go, thanks for the tip. I really like the sound of the benefits of your version (type matching). Any chance you can share the code?

Here's an updated version:
import React from 'react';

const MOBXSTORES = 'mobxStores';

function ensureContext(target: Function) {
    if (!('contextTypes' in target)) {
        target['contextTypes'] = {};
    }
    const contextTypes = target['contextTypes'];
    if (!(MOBXSTORES in contextTypes)) {
        contextTypes[MOBXSTORES] = React.PropTypes.object;
    }
}

export function provide(name: string) {
    return (target: Object, propertyKey: string | symbol) => {
        ensureContext(target.constructor);
        Object.defineProperty(target, propertyKey, {
            get: function(this: React.Component<any, any>) {
                return this.context[MOBXSTORES][name];
            },
            enumerable: false,
            configurable: false
        });
    };
}

Renamed inject to provide is it seems better suited (and doesn't clash with the existing class decorator). Also does the contextTypes changes automatically as @Strate suggested.
I think it'd be great to have something like this in the library. The above follows the same patterns that <Provider> and @inject already do so shouldn't be a big deviation in that regard. PR?

I don't think that provide is good over inject - because this is exactly the same behaviour, but applied to property, not a class.
Yet another note: it would be great to allow inject by class:
class Component {
  @inject
  private store: Store
}

and thiw how it could be done in non-typescript:
class Component {
  @inject(Store)
  private store
}

Maybe this could be done in separate package? For example mobx-inject or mobx-dic, with extra ability to handle dependency injection stuff in stores and etc

it would be great to have the stateless component support, one thing I'm still missing from this is to be able to inject a class and get that instantiated like the example above. ^^  class Component {   @inject   private store: Store } this would be similar to what angular2 does.  For now I have to instantiate the class in the injector like this: export const FacebookAuth = inject(   stores => ({     sessionStore: new stores.SessionStore()   }) )(({sessionStore}) => {   return (<Image style={styles.bg} source={require('./facebook-auth-bg.png')}>     <View style={styles.contentWrap}> thoughts?

@Strate / @jamiewinder sorry, somehow got out of sync with this thread, but I think the @inject looks great, especially with the `@injectable. Would any of you feel for creating a PR including tests? Thanks!

@mweststrate right now my buddy works on separate package to achieve same behaviour. Ping @mass3ff3ct

Hi, here's my implementation https://github.com/mass3ff3ct/mobx-react-inject
Strictly do not judge, was created to meet specific needs ))

I don't think I'm well placed to champion this anymore, as I've found myself 'converted' to the props-way of doing it (convenient for testing things in isolation). It might still be nice for certain situations though.

closing issue, I think a separate package is nice. I like the approach (will probably start using it myself), but I thik it is good that the standard package provides one way of doing it. Will make sure it is mentioned in the awesome list though.


[DO NOT MERGE] Backport some fixes from master to ozone-1.4

What changes were proposed in this pull request?
Backport the following fixes from master to ozone-1.4 for 1.4.1:
HDDS-9962. Intermittent timeout in TestBlockDeletion.testBlockDeletion (#5886) - (to fix the problem described in https://issues.apache.org/jira/browse/HDDS-10799)
How was this patch tested?
https://github.com/vtutrinov/ozone/actions/runs/8967491544

/pending DO NOT MERGE

Thanks @vtutrinov for working on the backport. LGTM +1.

Thanks @vtutrinov for backporting this, @xichen01 for the review.


logaddexp and logsumexp do not handle -inf correctly, don't match numpy/scipy

logaddexp(-inf, -inf) should be -inf, is nan in jax implementations.
numpy.logaddexp(np.NINF, np.NINF) => -inf
jax.numpy.logaddexp(np.NINF, np.NINF) => nan
Same issue for special.logsumexp

I'm seeing -inf for logaddexp but NaN for logsumexp. Can you share the exact code that gives you NaN with jax.numpy.logaddexp?

The jax.numpy.logaddexp behavior is really weird, I only see it when running on an array with more than one item:
import jax.numpy as np
np.logaddexp(np.NINF, np.NINF) -> -inf
np.logaddexp(np.array([np.NINF]), np.array([np.NINF])) -> [-inf]
np.logaddexp(np.array([np.NINF, -1.0]), np.array([np.NINF, -1.0])) -> [nan, -0.30685282]

I think the last behavior is because of XLA mishandling exp for NaN inputs on CPU:
In [7]: lax.exp(np.nan)
Out[7]: DeviceArray(0., dtype=float32)

In [8]: lax.exp(np.array([np.nan, 0.]))
Out[8]: DeviceArray([inf,  1.], dtype=float32)

I filed a bug with the XLA folks.

Er, why is lax.exp(np.nan) = 0 in the first case? Shouldn't it just be nan?
In both the numpy/scipy functions, there is a special case to handle logsum of two -infs that the jax implementations don't do:
logsumexp:
https://github.com/scipy/scipy/blob/0781734e45886567f84d9fc0caa56476a32d82bb/scip
y/special/_logsumexp.py#L104
logaddexp: https://github.com/numpy/numpy/blob/31ffdecf07d18ed4dbb66b171cb0f998d4b190fa/numpy/core/src/npymath/npy_math_internal.h.src#L587
The logaddexp numpy thing would give weird results for autodiff.

It should be nan in both cases. Both are bugs, but exhibiting slightly differently in the scalar and vector cases.


Define additional IPPROTO_* constants.

Define additional IPPROTO_* constants, e.g. for DCCP and SCTP. These constants are standard across all system types -- the values are those assigned to the protocol by the IANA:
https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml

Thanks! Looks like CI is failing though?

Yeah -- I'll fix it. These constants are the same across all platforms so I thought it might be fine to just put them all in the base module. libc-test is strict and only allowing the constants defined on each particular platform though, so I'll need to go back and move some of the constants into the platform-specific modules instead. (Will do that when I have a minute then update the PR.)

I've updated the PR, and the build succeeds on my machine and passes most of the travis CI builds now. However, a few of the travis builds are still failing with the latest code and I don't see why that's the case. A couple of them appear to be failing in the C compiler tests with a constant redefinition error, any ideas why that's happening?

Some of these constants may not be defined on OSX?

Yes -- there were a few constants that'd been removed from the OSX / Darwin headers when they were ported over from FreeBSD, and I'd left them in there by accident. There were also a couple of other places where I'd added a duplicate IPPROTO_RAW constant in. I've fixed these and updated the PR.
One small note -- I had to disable (comment out) the IPPROTO_L2TP constant for NetBSD. It's defined in the latest NetBSD source, but it looks as though the docker image used by the CI tests is using an older version of NetBSD which doesn't have that constant defined. The constant was added here:
https://github.com/NetBSD/src/commit/7c6df79fc2d2c616a886db2f5e64951d33d313ef#diff-dab66d274da3dd4ba168b2ba7f3b4374R108

@bors: r+
Ok, thanks!

:pushpin: Commit e8dd192 has been approved by alexcrichton

:hourglass: Testing commit e8dd192440e2ced9603d52b02dd2f7f1d6d37c5b with merge ba1d2f1f6ab383c12ba344c4b41036b1c22ecd7d...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing ba1d2f1f6ab383c12ba344c4b41036b1c22ecd7d to master...


Rust: add option for path to wit-bindgen runtime.

This PR adds an optional path to the wit-bindgen runtime to use for Rust code generation.
This will allow a different crate from wit-bindgen to generate bindings while also re-exporting wit-bindgen::rt at a known path for the generated code to use.

I've added a runtime_path option to the generate! macro so we can set it via a test, which I've also added.

@alexcrichton thoughts on doing a release that might include this change?
This will enable cargo-component to migrate to using a wit-bindgen::generate!-style macro ahead of the resource changes and we've also rev'd the wasm-tools dependencies in main, which would be nice to have for downstream crates to sync on.
I realize that we'll want a release in the (near?) future to support resources, but an interim release would definitely help me out.

Sounds good to me! I'll send a version bump to this repo which will be good to pull in the wasm-tools update regardless.

Posted a bump at https://github.com/bytecodealliance/wit-bindgen/pull/620


Improve frontend design

We are already creating a new frontend design. Let's implement it to project.
Mockups
#31
And related issue with this issue #39, #41

https://www.figma.com/file/8zYkdrtzVFm5CJ3rRqLUZs/Untitled?type=design&node-id=0%3A1&mode=design&t=R6r8J4Y1voApq4Zt-1

@aykutkantas & @dbaslan you should decide which components will be done by who.
As I know Aykut created mock ups for this issue. #31
Let's break down components
Main component groups are below

[ ] homepage
[ ] landing
[ ] profile
[ ] search
[ ] story
[ ] header

Also related with #63

@aykutkantas & @dbaslan you should decide which components will be done by who. As I know Aykut created mock ups for this issue. #31
Let's break down components Main component groups are below

[ ]  homepage
[ ]  landing
[ ]  profile
[ ]  search
[ ]  story
[ ]  header

Hi guys,
Is there a final decision about "which components will be done by who"?
If so, let's indicate here and let's close this issue.
If not, let's transfer this content into Discussions and again let's close this issue.
Thanks in advance.

@dbaslan

@sadikkuzu @dbaslan @oguzsenna I have made landing and also I am planning to make homepage and profile.

I will be handling the memory creation screen, memory viewing screen and the search screen. @oguzsenna will be handling the timeline, activity stream and the header. We might need to collaborate on search and timeline but we'll see. Closing issue and opening new issues for individual tasks.


Change-Type: major|minor|patch
Connects-To: #
HQ:
See:
Depends-On:

Contributor checklist

[ ] Build output been rebuilt and tested
[ ] Introduces security considerations
[ ] Tests are included
[ ] Documentation is added or changed
[ ] Affects the development, build or deployment processes of the component

Reviewer Guidelines

When submitting a review, please pick:

'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

This looks to be a test PR, closing now


Implement DOM overlays for expressing conventions + build files in the terms of a DOM

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

Sorry some internal error occurs, please contact the administrator @gradle/bt-developer-productivity

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build