AMQP-630: Migrate to Log4J2, Part II

JIRA: https://jira.spring.io/browse/AMQP-630
The previous fix wasn't full: we still need to adjust logger configs for Log4J2

Rebased, merged as 6d1d59277b0e89b8c332fceee815eb4e2ac34367


JAVA-2304: Avoid direct calls to ByteBuffer.array()

Requires https://github.com/datastax/native-protocol/pull/27.

👍
I released native-protocol 1.4.5.


Modify isovar usage from >=3 to >=2 spanning reads

Per https://github.com/hammerlab/cohorts/pull/177#discussion_r96321375

Or, at least, consider this modification


rootston move/resize/rotate with touch

We should implement these touch features in rootston.
This is complicated by the fact that cursor.c assumes a single moveresize "mode" for the cursor when now there can be at least two.
Other features that go along with this:

Use two fingers to move/resize/rotate the view
title bar move for multiple touch points at the same time

@acrisci Can close as rootston is archived?


badges & licence

badges on Readme
licence  MIT -> APACHE 2.0

Codecov Report

Merging #8 (10efdd3) into main (957d213) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #8   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines           80        80
  Branches         7         7
=========================================
  Hits            80        80

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

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

Continue to review full report at Codecov.

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


Contacts not merged when they should have been

I ended up with two "Simon Murtha-Smith"s. Simon saw it!
/Me/contacts/update fixed it.

I don't imagine I'll figure this out right away, so if anyone else sees this sort of thing happen, send me a message with the two (or more!) unmerged objects - that will help!


Fixed a typo in event-hubs-programming-guide.md

Corrected a typo in the "Send events to an event hub" "synchronously" should be "asynchronously"

@tareksharbak : Thanks for your contribution! The author, @ShubhaVijayasarathy, has been notified to review your proposed change.


compatibility with jupyter-sphinx

I would like to use this on rst files that are used in combination with https://github.com/jupyter/jupyter-sphinx.
Here the code blocks are formatted like:
.. jupyter-execute::
    :hide-code:

    code_here

# or

.. jupyter-execute::

    code_here

Specifically, I would like to use it for the Adaptive documentation (repo).
I've made an attempt myself, but I can't match @asottile's regex wizardry 😉

I believe (?) it would be extending this line to also match jupyter-execute: https://github.com/asottile/blacken-docs/blob/109732aa39a1cafd631e5015b395fac02eb16ee0/blacken_docs.py#L25

That is exactly what I tried, but it didn't do the trick.

can you show your patch? maybe I can help :)

https://github.com/basnijholt/blacken-docs/commit/6460931f4eabce5cfe3f83141897fde84e1e0279
Thanks for the help!

ah I think you need
    rf'^(?P<indent> *)\.\. (jupyter-execute::|(code|code-block|sourcecode|ipython):: {PY_LANGS})\n'

@basnijholt were you going to submit a PR?

Will you accept it if I make this change?

yeah I was hoping you'd send a patch :)

I've just opened #37! 👍


Web accessibility reader error

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior

Pager component failes Chrome WAVE (Web accessibility evaluation).
Expected behavior

The Pager ellements would pass the readability of reader devices for the disabled.
Reproduction of the problem

What is the motivation / use case for changing the behavior?

Make it more accessible to diabled users
Please tell us about your environment:

Table version: 0.7.x

Angular version: 2.0.x

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]
All

By adding an "Aria-label" to the  tag of the pager.component.ts would fix the reader issues.
Example:

      {{pg.text}}

dupe of https://github.com/swimlane/ngx-datatable/issues/257


Options to set session ID and timers via CLI #52

Also fixes a session ID bug where the variable was never random
Introduces the following flags: rtr.sessionid. rtr.refresh, rtr.retry and rtr.expire

Resolves issue #52

Added timers to PDU EOD String() function:
$ go run rtrdump.go  -loglevel debug
INFO[0000] Connecting with plain to <IP_ADDRESS>:8282
DEBU[0000] Received: PDU Cache Response v1 (session: 19379)
DEBU[0000] Received: PDU IPv4 Prefix v1 <IP_ADDRESS>/22(->/22), origin: AS65001, flags: 1
DEBU[0000] Received: PDU End of Data v1 (session: 19379): serial: 1, refresh: 3600, retry: 600, expire: 7200


[Closed] DBeaver not showing SQL Server tables

I just downloaded and installed DBeaver 5.3.0 in my Ubuntu 16.04 desktop. I created a new table in my SQL Server 2017 database, but DBeaver's database navigator is now displaying any SQL Server tables.

But in Azure Data Studio, I can see the table I just created is there.

I figured all the tables are stored under [Schemas] -> [A Particular Schema] -> [Tables] -> [A Particular Table]. It's a different user experience compared to SSMS's.
No issue, and this issue was closed.

Yep. We can make this configurable (and show tables as a plain list just like in SSMS) - if there will be enough votes.
However I personally prefer to group tables by schemas.

Yep. We can make this configurable (and show tables as a plain list just like in SSMS) - if there will be enough votes.
However I personally prefer to group tables by schemas.

Where could we start a voting activity? For SQL Sｅｒｖｅｒ developers, the current configuration to group tables by schemas is not a sincere user experience.

@melhzy Just create a new ticket with such request.


update fetcher to allow non-zero exit code from diff

When we generate diffs from the previous generated code to the new generated code, we should allow the command to return an exit code of 1. Diff will return 1 when there are diffs, 0 when there are no diffs, and anything else if there are other errors.

This will fix the error seen here: https://github.com/bufbuild/plugins/actions/runs/3493014724/jobs/5847372558

Are we just logging the diffs for informational purposes, then?


STORM-3244 allow logviewer to use independent filter settings from ui

@revans2 - added fallback to ui filter.


[SYSTEMML-1974] Implement Optim test functions (multiple local minima, part 1)

Hi, once we implement the optimization script, we would like to test those.
So, this one introduces some multiple local minima functions, as a first iteration for easier review. This library will help us hard test our optimization scripts, nn etc. for the function approximation.
please share feedback on

naming convention of the functions. - @deroneriksson
review for the syntax, loops. - @mboehm7 @niketanpansare

It is difficult to stare at the script and see how it fits into SystemML especially because the feature you are working on is rather complicated. Can you please batch your PR such that every PR has a test or a demo that a non-domain expert can try to understand the utility as well as correctness of the script/feature you want to merge ?

Hi @niketanpansare , please find this link. Here, I am implementing this type of functions.

For example, we have a neural network or an optimization algorithm. So,

we take one function (say  Styblinski-Tang function), (first fig. from left )
we give input & output values of this function to the network(2 & 3 fig. from left are the networks trained on regular batching & sobolev kind of training after 20 trains), to see how well our function is being approximated (here, sobolev network approximated styblinski-Tang to a reasonable accuracy).
These functions are necessary to check all the nuts & bolts of the network are sound enough.

@dusenberrymw - please correct me if I am wrong with the above comment.
As these are the normal functions, may be the one way to test these will be running the script, and then make plot some how, and then see whether the function is correct. Please advice on how to test this.

You can consider running following Python code to get y and x:

from systemml import MLContext, dml, dmlFromResource, dmlFromFile, dmlFromUrl
ml = MLContext(spark)
s = """
source("many_local_minima.dml") as fn;
a = 20.0; b = 0.2; c = 2 * 3.1415
d = ??
x = rand(rows=1, cols=d)
y = fn::Ackley(x, a, b, c)
"""
helloScript = dml('source("many_local_minima.dml") as fn; y= fn::Ackley()').output('x', 'y')
res = ml.execute(helloScript)
xMat, yMAt = res.get('x', 'y')
x = xMat.toNumpy()
y = yMat.toNumpy()

Then you can plot them using the code mentioned in https://matplotlib.org/examples/mplot3d/subplot3d_demo.html

Paste the generated plots in the PR (and may be with expected plots) to show that the functions are working correctly :)

Can anyone help me understand, why all the above commits are added, I believe I have rebased my branch before committing & everything is fine yesterday.!

@j143 It looks like there was a forced update to the master branch last night that wiped out the half of month worth of commits, which are now showing up in this PR.  Don't worry about it, as soon as the master branch is fixed, this PR will look fine again.

Hi, I ran the above script. But, till
>> xMat
Matrix
>>yMat
2.790
>>X = xMat.toNumpy()
Attribute Error: 'matrix' object has no attribute 'toNumpy'
>>y = xMat.toNumpy()
Attribute Error: 'float' object has no attribute 'toNumpy'

And in the Matplotlib, here
X = np.arange(-5, 5, 0.25)
Y = np.arange(-5, 5, 0.25)
X, Y = np.meshgrid(X, Y)
R = np.sqrt(X**2 + Y**2)
Z = np.sin(R)
surf = ax.plot_surface(X, Y, Z, rstride=1, cstride=1, cmap=cm.coolwarm,
                       linewidth=0, antialiased=False)
ax.set_zlim(-1.01, 1.01)
fig.colorbar(surf, shrink=0.5, aspect=10)

how to arrange X, Y values. as for x = rand(rows=1, cols=d), first column will form X & the second column Y as input. And along the z-axis value of y = fn::Ackley(X, a, b, c)
If possible can you run the script for Ackley, to check that it works for me too. cc @niketanpansare

ping for help. - @niketanpansare. Please find the above comment.

Can you please try X = xMat.toNumPy() ?

Hi, how can I output the a y matrix, to a csv file and where that file will be saved. Thanks.
windows OS
only spark-submit works


Run packages, hosts, dns, then firewall

This ensures any packages necessary for updating DNS are available. It also puts hosts before DNS, in case it requires a configured local /etc/hosts hostname, and puts both before firewall, which could be a consumer of either sets of hostnames.

👍 lgtm


ImportError: No module named misopy

thanks for sharing your scripts. however, when I use the extract_intron_gff3_from_gff3.py to extract intron gff3 file, the script came an error ''ImportError: No module named misopy"

Could you try pip install misopy before running the script? For more detail take a look at the documentation.

thank you very much and I appologized for my late replies. well, I have installed the misopy. But the new problem is "Possible precedence issue with control flow operator at /usr/share/perl5/Bio/DB/IndexedBase.pm line 791". This is happend  when I using Bio::DB::Fasta. I installed the bioperl by using "apt-get install bioperl".  Any suggestions? many thanks.

thank you very much and I appologized for my late replies. well, I have installed the misopy. But the new problem is "Possible precedence issue with control flow operator at /usr/share/perl5/Bio/DB/IndexedBase.pm line 791". This is happend when I using Bio::DB::Fasta. I installed the bioperl by using "apt-get install bioperl". Any suggestions? many thanks.

In this case, you need to install Bio::DB. However, if you use extract_intron_gff3_from_gff3.py Python script, you do not need Perl modules to be installed.


Subdomain character limit too low

The current character limit prohibits me from using anything more than my computer's name (e.g. brandon-macbook-pro) as a subdomain. I'd like it to be my computer's full hostname plus my project and company name (i.e. brandon-macbook-pro.local.api.acme). The domain names specification permits subdomains 63 characters in length or less. It would be awesome if we could get the limit changed from 20 to 63.

PR welcome for review :)

This issue is already merged... Issue should be closed


fix(error): fix #706, handleError when onHasTask throw error

fix #706,
when zoneSpec's onHasTask throw error, should call handleError to let zoneSpec has chance to process the error.

Hey, when is this patch going to be published?


[Bug] radixcache stack_overflow

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.
[x] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
[x] 4. If the issue you raised is not a bug but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.
[X] 5. Please use English, otherwise it will be closed.

Describe the bug
A bug happens in 3 hours whe running pressure test on a A800*4 with Qwen2-72B.
Error Trace ：
Location:
/sglang/python/sglang/srt/mem_cache/radix_cache.py
-- class RadixCache
     -- def _collect_leaves
        -- def dfs_

Error:
Too many times recursion causes stack overflow.
Python Stack Overflow

Reproduction
We run a pressure test, query  service with different messages by about 3 hours
Model: Qwen2-72B.


[DR14Q] Extend the model: 911-1300 A

Issue:
Some spectra in DR14Q don't have Lya peak inside the modelling window (911-1216),
this induces the model fitting a very large DLA on the red-end of the spectrum.
We had the issue before on fitting blue-end edges. This is the red-end version of it.
We did not notice this before due to DR12Q did not have many spectra not having Lya peak within the modelling window (911-1216 A).
Solution:
Extend the modelling window from 911-1216 to 911-1300.
This would include the Lya peak even the peak shifted a bit redward. Expect to regularise big DLAs on the red-ends.

Some examples:

The extended model (911 - 1216)

This has been merged to gp_dla_detection_dr16q. So close it.


[5.5][ownership] Teach the load_borrow verifier that value_metatype of an address isn't a write.

Just a case where the verifier was too sensitive. The only places that we use
this in terms of optimization would just not optimize in this case, so no
miscompiles are possible. That being said, we should ensure that SILGen doesn't
hit a verifier error after it emits code.
rdar://78698170 [SR-14680]
(cherry picked from commit ba639047a29003b2f84e860ff141eee90301fb1d)

CCC
Explanation: This is a small case where we did not update the verifier to know about a specific instruction. I updated the verifier to know about the instruction and classify it as not invalidating memory.
Scope: Without this change, when we build on Linux (where we have asserts enabled), we will get a crash and on Darwin where we do not build with asserts if we use -sil-verify-all (which enables some asserts) we may get false positives. There is no risk from the non-verifier code that uses this code path since we just return false that we can not optimize (instead of abort like we do in the verifier).
SR Issue: rdar://78698170 [SR-14680]
Risk: None. Teaches the verifier that a specific test case is safe by marking an instruction as not invalidating memory.
Testing: Added a test to test/SIL/ownership-verifier that makes sure the IR can accept this instruction from now on.
Reviewer: @atrick @meg-gupta

@swift-ci test

@swift-ci nominate


BSC bridge loading issue

Page keeps loading after clicking withdraw
See https://github.com/threefoldtech/tf_support/issues/408

User should select the correct network in metamask: BSC mainnet

@khaledyoussef24 please try it out and if it works, please close the issue

Can we asume the user has fixed this for himself? It's clearly a misconfiguration of his wallet whilst interacting with the bridge app.


Fix issues around metrics with unit rates

Description
Unit rate display in metrics has some issues. This PR:

Adds space between per and unit, e.g. per second
Doesn't pluralize rate unit
Adds tests

After:

Fixes https://github.com/dotnet/aspire/issues/5496
Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[x] Yes
[ ] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

Microsoft Reviewers: Open in CodeFlow

Will this also address the Y axis, will bytes per second show up as, for example 500MB/s? If that's what's suitable for the range/domain.

Will this also address the Y axis, will bytes per second show up as, for example 500MB/s? If that's what's suitable for the range/domain.

Do you mean the tooltip? The unit in the tooltip is the same as the graph legend:

@JamesNK I was hoping for something like this

We wouldn't do that because the unit can be long. If we changed the graph to have the unit on the axis it would be displayed vertically.
For example, https://plotly.com/javascript/line-charts/#graph-and-axes-titles


Feature:[actions/configure/] Unclear view type choose in - we need tip

Here we need tip - what view type is needed.

implemented in #582


Fix for flaky tests checking resource age

What does this PR do?
Fixes flaky tests, which check for resource age in the command output.
Expected age of resources is usually 0s, but the actual age is sometimes 1s.
What is the effect of this change to users?
No impact on the users
What does it look like?
No visible changes
Any background context you can provide?
Possible cause of the flakiness:
Output of some kubectl-gs command contains age of resources included in the output.
Therefore the tests need to check for resource age to verify that the output is correct.
The tests always work with a pre-defined set of input data - usually one or more resources of a specific kind.
Each resource in the input data contains creation date, which is used to calculate the age of the resource.
Some resources have a specific date and time of creation, others use the current timestamp.
Creation date in the input resources is configured as string in a specific format (2006-01-02T15:04:05Z).
The date string is parsed to Time object when the input resources are created from the configuration.
In case the current timestamp is used as creation date, it is formatted to string first and parsed back to Time object when used in resource creation.
This reduces accuracy of the age calculation, because dates parsed from the above format are only accurate to the nearest second.
Therefore in some cases the age may be incorrectly calculated as 1s instead of 0s, even though the input resources are returned in an output almost immediately after they are created.
The following sequence can be considered as an example:
2022-10-20T16:45:27.998 --> Start the test, create a resource with creation time set to the current timestamp
2022-10-20T16:45:27.999 --> Format the current timestamp to string (2022-10-20T16:45:27.999 --> "2022-10-20T16:45:27Z") and use it to create an input resource
2022-10-20T16:45:27.999 --> Input resource creation: parse the string creation time to Time object ("2022-10-20T16:45:27Z" --> 2022-10-20T16:45:27.000) and create the resource
2022-10-20T16:45:28.001 --> Run kubectl-gs command and return output with the resource
2022-10-20T16:45:28.001 --> Calculate the resource age: 2022-10-20T16:45:28.001 - 2022-10-20T16:45:27.000 = 1.001s

Should this change be mentioned in the release notes?

[x] CHANGELOG.md has been updated

Neat!


Fix to Div-Vor calculation - and consequences

This PR is a follow up to a bug found when comparing tropopause pressure GEOVALS between GSI and JEDI.
This has been reported among the SWELL geovals to be looked into:
https://github.com/GEOS-ESM/swell/issues/241
and it got to become an involved discussion w/ NCEP (Emily) helping out to look at this in  their system - (closed PR https://github.com/JCSDA-internal/fv3-jedi/pull/1208)
The initial discrepancies in tropprs GEOVALS looked like this:

Although at first the thought was that JEDI had a troubled code somewhere, the problem has been found to be related to how GMAO's interface to GSI calculates Vorticity and Divergence.
With a revised calculation of DIVO in GMAO's GSI, the geoval comparison now looks like this:

This was bound to happen at some point, i.e., all the GSI vs JEDI comparison would reveal an error in GSI - again, this is an error specific to GMAO's interface to GSI and not a bug in GSI per se.
The question is then how's this impact GSI's increments? Before answering this question it is good to know what role TROPPRS plays in GSI. This is how TROPPRS is used in GSI:

in the CRTM_INTERFACE treatment of IR radiance observations.
in the massaged saturation specific mixing ratio when derivatives are requested and Q and T are forced-decoupled. This plays a role in the rescaled analysis variable for humidity.
in the quality control of satellite wind observations - this controlled by a flag (qc_satwid) that is set to false in the GMAO's settings of GSI - actually, this flag (and it false settings) has been introduced by GMAO exactly because the results of applying this QC had been shown to be detrimental to GMAO's cycle - today, the speculation is that this was found to be so exactly because of the buggy DIVO.
And a much more key place where DIVO is used is in the flow-dependent feature of the background error variances in GSI.

Although the geoval comparisons above give an idea for how TROPPRS differ, here I show the actual full field difference between buggy (middle) fixed (top) and difference (bot):

As pointed out above, this difference in trop-prs is due to an error in the Div/Vor calculation. Here is a difference of the vorticity fields  (x 1e3) at about 200 mb.

And just to rule out any speculations of the vor-div in the original GMAO interface being flipped upside down of something, here is a figure of vorticity at 1 mb: top: fix, middle: original; bot: diff.

And just for completion, at a level like 400 mb, this is the difference in the divergence calculation:

With the fix introduced here, the question then becomes: what's the impact on the analysis increments?  The answer depends on the field examined. For example, the temperature and humidity fields don't seem to change much.  The increments below are all from 3DFGAT.
Here is a T-increment at 200 mb:

And here is Q at 850 mb:

All panels above are difference with a the present (before fix) configuration of GMAO's GSI. The bottom panels exploit the Q_CSATWIND option that performs quality control on the satellite wind observations based on tropopause pressure.
What the two figs above show is that the fix amounts to minimal impact on T and Q.
Unfortunately, this is not the case for the the wind. Here is a figure, simulation to those above, but for U wind at 400 mb:

Whether the qc-satwind knob is used to quality control satellite wind observations or not, the impact of the fix on the winds is substantial. The consequence of this to a cycling experiment will have to be evaluated carefully.
Just for reference, I will also show here the difference in the initial Jo tables from a run using the present GMAO GSI code (before fix; left) and one using the DIVO fix discussed here:
Initial-Jo

Final-Jo

A substantially higher amount of radiance observations (IR) are tossed with the fix-divo calculation. The consequence of such seem to impact the winds more than anything else ...
The difference in the wind must be a consequence of the flow-dependent B errors... A test is has been produced, here is a figure:

The fig above shows again  U wind at 400 mb as shown above, expect that the bottom panel deals with the no-Flow-Dependency option, that is, two cases: a default 3DFGAT was run w/o flow-dep the same case was run again, but now using the div-vor fix discussed here; the difference is what's shown.  In order words, without the flow-dependence feature, the bug in the calculation of div-vor is negligible. Unfortunately, we do make use of the flow-dependence feature and the div-vor calculation has a substantial, non-trivial impact in the wind increments.
Now, all the tests above were done in a 3DFGAT configuration - sort of similar to GEOS-IT. In hybrid 4DEnVar, as in our x-experiments or FP, the impact of the bug in the increments should be smaller, at least in the core atmosphere, since we only give 50% of weight to the climatological covariance term.
I will do some testing in Hyb-4DEnVar ... but this PR should not wait for those tests to go in.

@rtodling The changes look good to me. Thank you very much such a detailed analysis!


Does this work for expand collapse? How do I make this as gallery with expand collapse?

Does this work for expand collapse? How do I make this as gallery with expand collapse?

I couldn't figure out what "this" was, but if "this" refers to the list of samples, you can see the list of samples with images at the following link. Filter by "Microsoft Lists" to see a sample of List Formatting.
https://adoption.microsoft.com/en-us/sample-solution-gallery/
*If my answer is wrong, please create a new issue.


Fix Error: cannot use attributeBindings on a tag-less component

Modify touch-action mixin to smartly add attributeBindings to prevent
assertion error from being thrown in ember beta/canary.
Error is thrown when using 2.8.0-beta.3+cf714821 and 2.9.0-master+3f4ba8d4

This addresses #19


typo(app): I misspelled packages

Is this still waiting to be merged or should I close it?

tbh this commit just makes the other commit make sense so sure?


Use ES6 standards

I wanted to learn how to install and use eslint with the airbnb standard so I created my own implementation. I managed to set up an npm script and set the standard in PhpStorm.

Based on https://github.com/juampynr/elasticsearch-nodejs/pull/1


System.IO.IOException: The handle is invalid.

within 2106 TP3
docker run "microsoft/iis"
ops, something went wrong.  Please report this bug with the details below.
Report on GitHub: https://github.com/lzybkr/PSReadLine/issues/new
Last 0 Keys:
Last 0 Keys:
Exception:
System.IO.IOException: The handle is invalid.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.Console.GetBufferInfo(Boolean throwOnNoConsole, Boolean& succeeded)
at Microsoft.PowerShell.PSConsoleReadLine.Initialize(Runspace runspace, EngineIntrinsics engineIntrinsics)
at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics)

Duplicate of #158.


Introduce new installation probe service

This is mostly a refactoring of the existing probe service.
It was moved down into jvm-services and refactored to better fit our current needs.
It exposes a more capable vendor solution that can later on be used for vendor matching in toolchains.
Next steps:

replace the probe service in other places as well
replace other abstractions with JvmInstallationMetadata

This is the first part for #14030

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.


Getting an error with v1.3.0

busboy_1.default is not a constructor","stack":"TypeError: busboy_1.default is not a constructor\n    at parseMultipartForm
import busboy from 'busboy';

const bb = new busboy({ headers: req.headers });

See https://github.com/mscdex/busboy/issues/266

@mscdex if no more ‘ constructor’. I used without ‘new’ then?

The busboy readme is up-to-date, which shows you how to use the module.
I do not use typescript and do not maintain busboy type definitions, so I cannot help you with that.

Here is a definition file that works with the latest busbuy:
declare module 'busboy' {
  import { Writable, Readable } from 'stream';
  import { IncomingHttpHeaders } from 'http';

  interface BusboyConfig {
    /**
     * These are the HTTP headers of the incoming request, which are used by individual parsers.
     */
    headers: IncomingHttpHeaders;
    /**
     * `highWaterMark` to use for this Busboy instance.
     * @default WritableStream default.
     */
    highWaterMark?: number | undefined;
    /**
     * highWaterMark to use for file streams.
     * @default ReadableStream default.
     */
    fileHwm?: number | undefined;
    /**
     * Default character set to use when one isn't defined.
     * @default 'utf8'
     */
    defCharset?: string | undefined;
    /**
     * If paths in the multipart 'filename' field shall be preserved.
     * @default false
     */
    preservePath?: boolean | undefined;
    /**
     * Various limits on incoming data.
     */
    limits?:
      | {
          /**
           * Max field name size (in bytes)
           * @default 100 bytes
           */
          fieldNameSize?: number | undefined;
          /**
           * Max field value size (in bytes)
           * @default 1MB
           */
          fieldSize?: number | undefined;
          /**
           * Max number of non-file fields
           * @default Infinity
           */
          fields?: number | undefined;
          /**
           * For multipart forms, the max file size (in bytes)
           * @default Infinity
           */
          fileSize?: number | undefined;
          /**
           * For multipart forms, the max number of file fields
           * @default Infinity
           */
          files?: number | undefined;
          /**
           * For multipart forms, the max number of parts (fields + files)
           * @default Infinity
           */
          parts?: number | undefined;
          /**
           * For multipart forms, the max number of header key=>value pairs to parse
           * @default 2000 (same as node's http)
           */
          headerPairs?: number | undefined;
        }
      | undefined;
  }

  interface Busboy extends Writable {
    addListener<Event extends keyof BusboyEvents>(
      event: Event,
      listener: BusboyEvents[Event],
    ): this;
    addListener(event: string | symbol, listener: (...args: unknown[]) => void): this;

    on<Event extends keyof BusboyEvents>(event: Event, listener: BusboyEvents[Event]): this;
    on(event: string | symbol, listener: (...args: unknown[]) => void): this;

    once<Event extends keyof BusboyEvents>(event: Event, listener: BusboyEvents[Event]): this;
    once(event: string | symbol, listener: (...args: unknown[]) => void): this;

    removeListener<Event extends keyof BusboyEvents>(
      event: Event,
      listener: BusboyEvents[Event],
    ): this;
    removeListener(event: string | symbol, listener: (...args: unknown[]) => void): this;

    off<Event extends keyof BusboyEvents>(event: Event, listener: BusboyEvents[Event]): this;
    off(event: string | symbol, listener: (...args: unknown[]) => void): this;

    prependListener<Event extends keyof BusboyEvents>(
      event: Event,
      listener: BusboyEvents[Event],
    ): this;
    prependListener(event: string | symbol, listener: (...args: unknown[]) => void): this;

    prependOnceListener<Event extends keyof BusboyEvents>(
      event: Event,
      listener: BusboyEvents[Event],
    ): this;
    prependOnceListener(event: string | symbol, listener: (...args: unknown[]) => void): this;
  }

  interface BusboyEvents {
    /**
     * Emitted for each new file form field found.
     *
     * * Note: if you listen for this event, you should always handle the `stream` no matter if you care about the
     * file contents or not (e.g. you can simply just do `stream.resume();` if you want to discard the contents),
     * otherwise the 'finish' event will never fire on the Busboy instance. However, if you don't care about **any**
     * incoming files, you can simply not listen for the 'file' event at all and any/all files will be automatically
     * and safely discarded (these discarded files do still count towards `files` and `parts` limits).
     * * If a configured file size limit was reached, `stream` will both have a boolean property `truncated`
     * (best checked at the end of the stream) and emit a 'limit' event to notify you when this happens.
     *
     * @param listener.transferEncoding Contains the 'Content-Transfer-Encoding' value for the file stream.
     * @param listener.mimeType Contains the 'Content-Type' value for the file stream.
     */
    file: (
      name: string,
      stream: Readable,
      info: {
        filename: string;
        encoding: string;
        mimeType: string;
      },
    ) => void;
    /**
     * Emitted for each new non-file field found.
     */
    field: (
      name: string,
      value: string,
      info: {
        nameTruncated: boolean;
        valueTruncated: boolean;
        encoding: string;
        mimeType: string;
      },
    ) => void;
    closed: () => void;
    /**
     * Emitted when specified `parts` limit has been reached. No more 'file' or 'field' events will be emitted.
     */
    partsLimit: () => void;
    /**
     *  Emitted when specified `files` limit has been reached. No more 'file' events will be emitted.
     */
    filesLimit: () => void;
    /**
     * Emitted when specified `fields` limit has been reached. No more 'field' events will be emitted.
     */
    fieldsLimit: () => void;
    error: (error: unknown) => void;
  }

  function busboy(options: BusboyConfig): Busboy;

  export default busboy;
}


Composition events

Motivation
Add support for Composition events.
Changes

onCompositionStart, onCompositionUpdate, and onCompositionEnd event handlers.
Synthetic event type
Simulate test utils

Note: w3 spec events are compositionstart, compositionupdate, and compositionend (all lower-case), but react.js uses camel case for event names
Please Review @greglittlefield-wf @kealjones-wk @aaronlademann-wf @sydneyjodon-wk @joebingham-wk

Turns out this doesn't solve my immediate issue since I'd be adding the listeners on dynamically added elements, not react elements. BUT I do think this is still a good change to have since react.js supports these listeners even though dart2js does not.


Logging approach creates redundant events on each exception

Hello. I use this library in one of my projects. I have noticed that across the library codebase on each exception 2 logging records are created. This approach complicates integrations with errors monitoring solutions, for example Sentry. An event will be created on each logging record. For example, a record with message "unexpected error" (created here) doesn't provide any valuable information for the investigation. Also, logging.Logger.exception() method is not supposed to be used like that. It will get the Exception object implicitly and log the traceback by default. So, we only need to provide some meaningful message as an argument for this method.
I suggest to refactor all places with such an approach to create only one logging record. For example, in this place it will be like this:
current_app.logger.exception('unexpected error')

Hi @Kaveshnikov,

I suggest to refactor all places with such an approach to create only one logging record. For example, in this place it will be like this:
 current_app.logger.exception('unexpected error')

The excellent suggestion, I will accept that.
A new medium release will be launched.
Thank you.

Some examples to further information:
>>> try:
...     1/0
... except ZeroDivisionError as e:
...     logging.exception('xxx')
...
...
ERROR:root:xxx
Traceback (most recent call last):
  File "<bpython-input-9>", line 2, in <module>
    1/0
ZeroDivisionError: division by zero

>>> try:
...     1/0
... except ZeroDivisionError as e:
...     logging.error('xxx')
...
...
ERROR:root:xxx

>>> try:
...     1/0
... except ZeroDivisionError:
...     logging.exception('xxx')
...
...
ERROR:root:xxx
Traceback (most recent call last):
  File "<bpython-input-23>", line 2, in <module>
    1/0
ZeroDivisionError: division by zero

>>> try:
...     1/0
... except:
...     import logging
...     logging.exception('xxx')
...
...
ERROR:root:xxx
Traceback (most recent call last):
  File "<bpython-input-30>", line 2, in <module>
    1/0
ZeroDivisionError: division by zero


Ranger docker image failing

See https://jenkins.odpi.org/view/egeria-docker/job/egeria-ranger-maven-docker-stage-master/71/console
13:38:26 [INFO] Scanning for projects...
13:38:26 [ERROR] [ERROR] Some problems were encountered while processing the POMs:
13:38:26 [FATAL] Non-readable POM /w/workspace/egeria-ranger-maven-docker-stage-master/open-metadata-resources/open-metadata-deployment/docker/ranger: /w/workspace/egeria-ranger-maven-docker-stage-master/open-metadata-resources/open-metadata-deployment/docker/ranger (No such file or directory) @
13:38:26  @
13:38:26 [ERROR] The build could not read 1 project -> [Help 1]
13:38:26 org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
13:38:26 [FATAL] Non-readable POM /w/workspace/egeria-ranger-maven-docker-stage-master/open-metadata-resources/open-metadata-deployment/docker/ranger: /w/workspace/egeria-ranger-maven-docker-stage-master/open-metadata-resources/open-metadata-deployment/docker/ranger (No such file or directory) @
13:38:26
13:38:26     at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:383)
13:38:26     at org.apache.maven.graph.DefaultGraphBuilder.collectProjects (DefaultGraphBuilder.java:414)
13:38:26     at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor (DefaultGraphBuilder.java:405)
13:38:26     at org.apache.maven.graph.DefaultGraphBuilder.build (DefaultGraphBuilder.java:82)
13:38:26     at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507)
13:38:26     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219)
13:38:26     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
13:38:26     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
13:38:26     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
13:38:26     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
13:38:27     at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
13:38:27     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
13:38:27     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
13:38:27     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
13:38:27     at java.lang.reflect.Method.invoke (Method.java:498)
13:38:27     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
13:38:27     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
13:38:27     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
13:38:27     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
13:38:27 [ERROR]
13:38:27 [ERROR]   The project  (/w/workspace/egeria-ranger-maven-docker-stage-master/open-metadata-resources/open-metadata-deployment/docker/ranger) has 1 error
13:38:27 [ERROR]     Non-readable POM /w/workspace/egeria-ranger-maven-docker-stage-master/open-metadata-resources/open-metadata-deployment/docker/ranger: /w/workspace/egeria-ranger-maven-docker-stage-master/open-metadata-resources/open-metadata-deployment/docker/ranger (No such file or directory)
13:38:27 java.io.FileNotFoundException: /w/workspace/egeria-ranger-maven-docker-stage-master/open-metadata-resources/open-metadata-deployment/docker/ranger (No such file or directory)
13:38:27     at java.io.FileInputStream.open0 (Native Method)

Looks like a bad pom

The Docker images have been re-organised a bit to split up the build-time vs. the run-time...  I had assumed that the changes would be picked up automatically, but seems like there's something hard-coded in our Jenkins pipeline regarding old paths (?)

Build images for Apache projects are now under /open-metadata-resources/open-metadata-deployment/docker/build-images/apache/... while the runtime images are retained at the "top-level" (/open-metadata-resources/open-metadata-deployment/docker/...)
The intention is:

more clearly separate rare builds (.../build-images/...) from the runtime

against which we should be able to put more restrictive controls on triggering Docker image builds and pushes (ie. only when the Dockerfile under .../build-images/... changes do those images need to be re-built)
which also means these more clearly build once, but may be used as the source for multiple runtime images (eg. if we need other Ranger images than just the admin, with some other subset of build artefacts)
also allows cached images to be used for these build images, since they're the long-running ones that will rarely change this should significantly enhance build times (eg. via Maven) after the initial build

the runtime images should now be pulling their build image starting points directly from Docker Hub (by default, though repo is parameterised to allow local builds if people want to venture that way)
the ordering of the modules in the upper-level pom should ensure that the build images build before any runtime images (if driving the build purely from Maven)

Yes, understand.. But noticed the builds were failing. I'm currently testing them and found the failure. I'll fix the egeria one first, then look at the others.

Give me a shout if you want more explanation on the changes / where things are now 😄

Ok now ranger.. the reason for this failure is that there is no pom ... in the directory the build process is using ... because the directory is renamed.
The current process isn't ideal - as you said, a full maven build is fine as things are done in the right order, with the right references. The resource requirements being two high resulted in independent jenkins jobs being setup -- and one of those needs updating to address the directory change.
The atlas issue was down to (I think) the base image not being rebuilt at all - another challenge with the split.
However there are potential changes coming in the build pipeline infrastructure so I'm going to fix these up manually, raise an issue/PR for THIS ranger build... then we can look at moving forward when any new CI/CD infra evolves.

fixed (by manually forcing a build of the base ranger image)


feat(CategoryTheory): proof producing coherence tactic 3: main

[ ] depends on: #16567
[ ] depends on: #16578

This PR moved to #16852.


Fix a broken link

Was reading through the docs and found a broken link - here's a PR to fix it.

Thanks!


[hal] remove unused lifetimes

Fixes #issue
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[x] tested examples with the following backends: metal
[ ] rustfmt run on changed code

bors retry


Websites that needs windows authentication fails to load

Hello,
The websites that  needs the windows authentication over http is failing to load the pages while using the proxy.Chrome shows the message as This webpage is not available, ERR_CONTENT_LENGTH_MISMATCH. Please help me to solve the issue

Hi venkat,
I have successfully used chrome in my office computer to access intranet sites that uses windows authentication when proxy was running on my local machine. You may have to configure chrome. Search online for info on windows authentication on Chrome.
However, theoretically you cannot use windows authentication when proxy is running on a remote machine, because there is a double hop issue when windows uses kerberos authentication. You can get away with it by allowing delegation on the proxy server, and then modify the code to pass client credentials to server on behalf of client.   At this moment I am not working in to it, but may update in future.

Thanks For the Quick Response, The issue is not limited to Chrome but happens in IE and Firefox also. In my case there were couple of websites that were hosted on Amazon over http uses the windows authentication and failing to show Authentication popup. Please try this website which is configured for Windows Authentication. http://bestdeals9.com/

Also i have noticed few Websites that enables chat sessions is having problem with communicating. Here is one of the example i noticed that works good without proxy but errors out with proxy.
http://makemytrip.custhelp.com/app/chat/chat_landing_chat_us/mobile/6145671627/skill/1308/ptype/http:$$us.makemytrip.com$homepage/qtype/2441/first_name/Test1/last_name/Test2/email/Test2%40gmail.com
This url errors out as " There was a problem connecting to the Chat Server" when using with Chrome and Firefox, but works good in IE8.

Another Issue is While on Post action Some sites Errors out with 417 - Expectation Failed error. this is noticed in Slickdeals.net, Not sure if its Site Specific? Any help to fix this issue is appreciated. Thanks

I noted the "windows authentication" issue you mentioned, though it is not windows authentication but basic authentication. I will fix it soon.
Regarding other issues, I am using chrome and I was able to browse through the chat link you send without any issue. Also can you give a sample link for 417-expectation failed?

http://slickdeals.net/forums/newreply.php?v=1&do=postreply&t=7862265
Here is the link. Error occurred when i tried to reply to the post.
Also This piece of code takes really long time to execute few requests making the browsing experience really slow. Can this be fine tuned? Thanks
while (!String.IsNullOrEmpty(tmpLine = clientStreamReader.ReadLine()))
{
requestLines.Add(tmpLine);
}

I am not an expert in this. However I hope my recent commit would fix the authentication issue. Regarding slow reading, I believe its more related to IO wait than code. I checked on the link for "417 - Expectation Failed error". Couldn't reproduce it.

Thanks for Providing the fix, For Slow Reading i tried to rewriting the logic however i ended up having more issues in POST, But works faster for GET. Here is the code i modified, sorry for my bad code.
            byte[] bytes = new byte[client.receivebuffersize];
            netstream.read(bytes, 0, (int)client.receivebuffersize);
            string returndata = encoding.ascii.getstring(bytes);
            requestlines = returndata.replace("\r", "").replace("\0", "").split('\n').tolist();
            requestlines = requestlines.Where(s => !string.IsNullOrWhiteSpace(s)).Distinct().ToList();

Regarding "417 - Expectation Failed error", i still could able to reproduce the error on all 3 browsers. None of the Post events including login are successful in this site(Slickdeals.net) with the proxy.

Also I noticed webReq.Headers.Add(header[0], header[1]); will throw out of range exception exception if the header length is 1, Probably this needs to be modified to if (header.Length > 1). Please ignore if this is not making any sense, Thanks
default:
if (header.Length > 0)
webReq.Headers.Add(header[0], header[1]);
else
webReq.Headers.Add(header[0], "");
                        break;

Can you clone this project and perhaps create a branch and then commit your changes using github client. I could look at it and pull in your changes to the main branch. Thanks for your suggestions. But I don't have much time nowadays to contribute. This was a learning project for me. So perhaps you could also learn by researching. One good tool you can use would be fiddler proxy. Using fiddler you can compare the reasons for error by looking the response headers fiddler returns and then the headers this proxy returns (use chrome development tools on chrome browser). Just FYI.

I am still trying to understand the code, I will try to commit the changes if any after some testing. even i am using this project for learning purpose,
Again Any issues i will continue to post here and if can spend some time to answer that will be great. Thanks for your time.

Hi,
The Authentication issue still exists, The authentication for the site which i was trying is NTLM authentication and the fix add the headers for basic Authentication. Also even after entering the credentials and authentication is successful, Authentication popup will be prompted again for another request. This happens for every request of the page. Any idea how this can be fixed?

I reverted my change since its breaking other requests. I am not sure.
NTLM authentication is possible on internet? I always thought its used only in intranet sites.
The Httpwebrequest class handles all the heavy lifting for authentication in background. The only case it cannot handle without user input is basic authentication. Since it would need a username and password.

I have noticed lots of sites with NTLM Authentication on internet. Are you planning to fix this any time soon? if not probably i will try to fix it when i get a chance. Is there any other requests this change is breaking?

You are always welcome to do fixes. I don't have time to contribute like I said earlier. Sorry.

I looked at this issue again. I tested a website that uses basic authentication. Worked fine without any issue.
In the website you gave if you can give me  a sample login I can test it. Otherwise I am going to close this issue.


Make resolve work with node v0.6.10

Test is broken with node v0.6.10
$ make test
[0:00:00 0 0/1 0.0% node test/integration/test-basics.js]
node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
AssertionError: "h" === "/home/dev/workspace/node-require-like/test/fixture/foo.js"
at testResolve (/home/dev/workspace/node-require-like/test/integration/test-basics.js:27:10)
at Object. (/home/dev/workspace/node-require-like/test/integration/test-basics.js:28:2)
at Module._compile (module.js:441:26)
at Object..js (module.js:459:10)
at Module.load (module.js:348:31)
at Function._load (module.js:308:12)
at Array.0 (module.js:479:10)
at EventEmitter._tickCallback (node.js:192:40)
[0:00:00 1 0/1 100.0% node test/integration/test-basics.js]
make: *** [test] Error 1
This problem is caused by this commit https://github.com/joyent/node/commit/840229a8251955d2b791928875f36d35127dcad0#lib/module.js (as pointed by itay on https://github.com/felixge/node-sandboxed-module/issues/5) where Module._resolveFilename no longer returns an array.
I've tested this patch against node v0.4.7, v0.6.9, and v0.6.10 .

Wow - I can't believe I was right :)
Way to go @cliffano!

Thanks for the patch. Sorry for the delay, I was swamped. Released as v0.1.2.
And yes, I generally prefer Array.isArray, but whatever : ).

Thanks Felix.


PHP @method misuse

PHP docblocks for methods always contain an @method tag: this is a misuse of this tag, according to https://docs.phpdoc.org/references/phpdoc/tags/method.html

@method tags MUST NOT be used in a PHPDoc that is not associated with a class or interface.

Or maybe this package is for another phpdoc generator?
Could it be removed from template?
Or is there a way to customize the templates?

The @method shouldn't be there. I can't reproduce this. Could it be that you added @method in the extra_tags configuration?

@Arcesilas I had the same question and when I looked into the source for the DocsParser.prototype.format_function function definition, I noticed that there's this code at line 140:
    if (this.editor_settings.auto_add_method_tag) {
        out.push('@method '+ escape(name));
    }

I checked my Docblockr package settings in Atom and sure enough the tick box was checked. Unchecking this solved my issue. Not sure if it'll be the same for you, but might also explain why @MoritzKn  couldn't reproduce this behaviour.


chore: add nativeID to image.md

Add nativeID prop to Image component, missing from the docs.

Hi @nelsonprsousa, a you can see in the code nativeID is not a Image component prop, it's inherited from the View component:

https://github.com/facebook/react-native/blob/master/Libraries/Image/ImageProps.js
https://github.com/facebook/react-native/blob/master/Libraries/Components/View/ViewPropTypes.js#L457-L464

To avoid the large amount of code duplicates we usually placing the inherited props section with the link to the component at the top of the Props list, as seen in here:

https://reactnative.dev/docs/scrollview#props

This part is definitely missing for the Image component right now. If you can, please update the PR code accordingly to the pattern mentioned above. Additionally if you want to see the changes in for example 0.64 docs, you will need to update also the versioned file under website/versioned_docs.

Hi @Simek ,
Just to be sure, you want me to remove the nativeID prop from Image and add this section to the Image.md just like the scrollview:

Right?

Yes, that's what I'm asking for! 🙂

Yes, that's what I'm asking for! 🙂

Done. Can you please re-check? 🙏
Also, your opinion on this is also appreciated. Do you think I should change something here? It is related to this change.

Also, your opinion on this is also appreciated. Do you think I should change something here? It is related to this change.

I think that all inherited props should be defined similar to the RN codebase, so the component props should be extended by parent props, like for example here:

https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react-native/index.d.ts#L488

Since the DT file is quite large the links to the specific line don't work that good, there is the code I'm talking about:
export interface PressableProps extends AccessibilityProps, Omit<ViewProps, 'style' | 'hitSlop'>

Like in the example above, Image component props should be extended by View props omitting the style. This props diff also can be seen in the Flow annotation in the RN code:

https://github.com/facebook/react-native/blob/master/Libraries/Image/ImageProps.js#L59


progressreader should not write to output on Close()

Since there's a well defined completion point for the whole operation  at Read(), anything that needs to be written could be written from there, right?. I ran into problems when using a progressreader that remained open for a certain interval of time during which other parts of the code wrote to the same output used by the progressreader, then on Close() there would be an out of place output with the full progress line from the progressreader when it was closed by a defer.
Removing the call to config.Out.Write() from Close() fixes the problem and does not seem to cause any issues with the other users of progressreader (e.g. docker push / pull).
Is there some special case for which that output was included originally?

Hi!
If you are reporting a new issue, PLEASE make sure that does not have any duplicates already open.
We would like to take this time to remind you of the information we need to debug the problem you are seeing. This is an automated response so if this ticket is not about a bug, do not fret.
If you fail to provide this information within 7 days, we will close this because we cannot debug your issue. We can reopen whenever the information is provided.
Thank you.
Please see:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
Description of problem:

`docker version`:

`docker info`:

`uname -a`:

Environment details (AWS, VirtualBox, physical, etc.):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Additional info:

#ENEEDMOREINFO

@moysesb moving the final print to the Read() makes sense to me.  But, would we need to call FormatProgress() one last time to ensure that it showed things at 100% (still within Read())?  Also, if someone does call Close() prematurely, I'm not sure we'd want to lose that final Write so what if the Close() only printed a final status IFF it wasn't already done within Read() ?


Running multiple rootless containers in parallel with toolbox-like UID mapping results in "conmon.pid: permission denied"

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Running Fedora Silverblue 30 with Podman 1.3.1, i can't run multiple containers with toolbox-like UID mapping in parallel. First i tought this is #2935 or #2673 but i no longer think so. I ran podman system migrate, and eventually i ran also rm -rf .local/share/containers, so the containers (and images too) were created on the most recent Podman, but none of that helped. This worked fine before -- i'm not sure which version of Podman i was using previously but i think it was 1.2.
FYI @debarshiray, i guess this must be affecting toolbox on Silverblue 30.
 twice.
spawn_container
sleep 5
spawn_container

Describe the results you received:
Run ./test.sh for the first time, it prints "Hi from container." just once. On a subsequent run it prints "Hi from container." just once, but it's then also followed by error conmon.pid: permission denied. Full output and full error message below:
$ ./test.sh
Trying to pull registry.fedoraproject.org/fedora:30...Getting image source signatures
Copying blob 149da9c683f1 [==>-----------------------------------] 7.8MiB / 93.2MiB

Copying blob 149da9c683f1 [==========>---------------------------] 27.4MiB / 93.2MiB
Copying blob 149da9c683f1 [=============>------------------------] 34.9MiB / 93.2MiB
Copying blob 149da9c683f1 [======================>---------------] 55.5MiB / 93.2MiB
Copying blob 149da9c683f1 [======================>---------------] 57.0MiB / 93.2MiB
Writing manifest to image destination
Copying blob 149da9c683f1 [==============================>-------] 77.2MiB / 93.2MiB
Copying blob 149da9c683f1 done
Copying config edc5d31c98 done
Writing manifest to image destination
Storing signatures
Hi from container.

$ ./test.sh
Hi from container.
$ ERRO[0000] open /var/home/jistr/.local/share/containers/storage/overlay-containers/8747fdf01fe9686eadc4e03d57f5946c5904bc67bf0c63906d9df373550e61a7/userdata/conmon.pid: permission denied

Describe the results you expected:
The test.sh script should print "Hi from container." twice.
Output of podman version:
Version:            1.3.1
RemoteAPI Version:  1
Go Version:         go1.12.2
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.12.2
  podman version: 1.3.1
host:
  BuildahVersion: 1.8.2
  Conmon:
    package: podman-1.3.1-1.git7210727.fc30.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 1.12.0-dev, commit: c9a4c48d1bff85033b7fc9b62d25961dd5048689'
  Distribution:
    distribution: fedora
    version: "30"
  MemFree:<PHONE_NUMBER>2
  MemTotal:<PHONE_NUMBER>6
  OCIRuntime:
    package: runc-1.0.0-92.dev.gitc1b8c57.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc7+dev
      commit: d38f8a2d00ff444e52d16ab1ea5bbe5c1cb471e8
      spec: 1.0.1-dev
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 4
  hostname: split
  kernel: 5.0.16-300.fc30.x86_64
  os: linux
  rootless: true
  uptime: 42m 10.06s
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /home/jistr/.config/containers/storage.conf
  ContainerStore:
    number: 0
  GraphDriverName: overlay
  GraphOptions:
  - overlay.mount_program=/usr/bin/fuse-overlayfs
  GraphRoot: /var/home/jistr/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 1
  RunRoot: /tmp/1000
  VolumePath: /var/home/jistr/.local/share/containers/storage/volumes

Additional environment details (AWS, VirtualBox, physical, etc.):
Physical host, Fedora Silverblue 30.

So you ran system migrate and you're still seeing a permission denied on the Conmon pidfile?
@giuseppe PTAL

(That error is actually exactly what system migrate was supposed to solve, so I'm very curious here)

@mheon One more thing to highlight which might be easy to miss in the logs. The error message in #2935 was with the old conmon.pid location in /run/user/1000, but the error message here is with the new location in ~/.local/share/containers. As i wrote, i eventually completely dropped the data directory, so this issue is not about migration of content from older Podman. In my later attempts, all the content was created from scratch on Podman 1.3.1, still producing the same error.

we managed to break it again when we dropped the intermediate namespace.
I am going to work on a fix for toolbox.  This should not happen anymore in future as we have a pause process, but let's have a workaround for now to not have another breaking change for existing running containers

@jistr could try out the PR I've just opened?

@giuseppe Thanks for such a quick fix. I will do my best to try when i get home (i'm not hitting this bug at work). I'm not a Go dev (go Rust! :D ) and my dev workflow on my home machine is a bit troublesome right now because of this very bug, so i can't promise results with certainty, but i'll try :).

I reported a similar issue in Toolbox1, someone pointed this issue there (this issue may related to my original issue).
For that issue, I ran system migrate many times, I still can see permission denied if I try to enter Toolbox.
And in the new Toolbox version, if I enter Toolbox, I would see this outpout:

~> podman system migrate
container_linux.go:388: signaling init process caused "operation not permitted"
ERRO[0000] Error removing store for partially-created runtime: A layer is mounted: layer is in use by a container
Error: error migrating containers: cannot stop container a33655212b94c4b5eb9b59feec317f89dbc9771d2e0a3c51b573cccce4b1f68d: operation not permitted

Thanks for sorting this out, @jistr and @giuseppe !

@debarshiray from the next 1.4 release rootless containers are out of tech preview and there won't be more breaking changes.
@debarshiray could you help us to figure out the toolbox use cases so that we have proper tests for it?
I am going to work on something like --userns=keep-uid ASAP, so that we won't need the magic shell code for creating the nested user namespace

I tested latest-at-the-time commit 6bca80bdfebf9d390ce1a9786ae6101c87f1322d and it does fix the issue for me. Thanks @giuseppe! Let me know if you want me to retest again with later/final version.
Also +1 on the idea of --userns=keep-uid :).


fix: pass border color to ColumnAdjuster

Passes the border color from the styleService to ColumnAdjuster. I noticed while testing that the default border color can be semi-transparent. That means that the the border color and column adjuster color will stack, and it doesn't look great. Pretty hard to see since we are talking about 1 px on each side, but not nice that the default case looks bad. I have an idea of how to fix this, but wont do it in this PR

:tada: This PR is included in version 2.5.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


question: minimizing consumption buffering

Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Sarama Version: 1.16.0
Kafka Version: <IP_ADDRESS>
Go Version: 1.10
Configuration
What configuration values are you using for Sarama and Kafka?
Defaults
Logs
When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set sarama.Logger to a log.Logger to capture Sarama debug
output.
Problem Description
A question regarding sarama buffering. Say I want to read messages between 2 offsets. I want to minimize the consumption of resources as much as possible; as little buffering of unwanted messages as possible. Any guidelines how best to make this happen with the kafka configuration; channel buffer size, max wait time, max processing time, etc?

Since you have explicit topic/partition/offsets in mind in this case, to truly minimize the consumption of resources you can create a Broker directly and construct the FetchRequests yourself. That gives you final control and introduces effectively no buffering in the system.
If you want to use the Consumer still I would suggest the following config tweaks (see the docs for more details on each key):

reduce Net.MaxOpenRequests
disable Metadata.RefreshFrequency
strictly limit Consumer.Fetch.Max and Consumer.Fetch.Default
strictly limit ChannelBufferSize

Consumer.MaxWaitTime isn't really relevant unless you're reading "live" topics - since it sounds like you're reading existing static data it makes no difference. Consumer.MaxProcessingTime is only really relevant if you're trying to read multiple topics at once to avoid contention. I suppose the way to make it most irrelevant would be to set it to a huge value (minutes or hours).
Hope this helps!

perfect. thank you!


[RPMP][bug] Config folder is not generated in built artifact.

The default config files should be part of built artifact of RPMP.
It will cause the binary launch failure if the launching is happening just in the bin folder.

See PR #107


Wrong message context while extract localizer string in Razor pages

While extract po using command:
extractpo ..\WebApplication1\WebApplication1 .\Output
The output of po file wrong msgctxt for Razor page Index
instead of msgctxt is WebApplication1.Pages.Index. it output msgctxt Pages.Index.
see attached project
WebApplication1.zip

Are you using the latest bits? If Yes we need to fix it before release 1.0.0

@rjpowers10 did you come across this issue with the latest bits?

There was unexpected but, I will fix it soon

Fixed in https://github.com/OrchardCoreContrib/OrchardCoreContrib.PoExtractor/commit/441dffb51f77fc7b9520e82a1aa8c03860e50bd6


Refs 105: Add pr_checks and build_deploy

Add a docker-login make target, for use in build_deploy.sh
build_deploy.sh will be used by appsre pipelines to push commits to
quay/redhat.io. The GH action building to quay can be removed (once
appinterface updates are accepted and repo created).
pr_checks leverages bonfire for PR image building, deployment, and test execution. appinterface pipeline definitions will execute this script against PRs.

https://issues.redhat.com/browse/HMSCONTENT-105

⚠ This task currently requires qe-approval, but this PR does not fully resolve the task.  Please contact QE to determine appropriate testing required.

Built and pushed image for bb691bd53008b196649a3e6a70112894a2124d67

https://issues.redhat.com/browse/14712517

Built and pushed image for 20cf2ba085260631cac10e29d5296a82c1c50d7f


Add migration guide for 3.0

This is kind of motivated by the addition of crypto.pod.
Many of the deprecated mappings are listed in CHANGES so not quite sure what to do with the deprecated section yet.
Feedback and suggestions are more than welcome..

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Quick note: its location is a bit curious...

I think this needs some guidance from OTC..

Added PKCS12 related API's from https://github.com/openssl/openssl/pull/14434

I worry that the long "laundry lists" of affected functions will distract from the main thrust of the content.  Maybe we can reference a header file or two to get the lists instead of duplicating them in-band?

OTC discussion that more details should be in migration guide and CHANGES should have less information.

There are many check_docs CI failures.

There are many check_docs CI failures.

I may not quite be finished yet :)

There are many check_docs CI failures.

I may not quite be finished yet :)

Sure. BTW, looking at the nice gray Draft GitHub icon this morning
I figured this must have been triggered by placing [WIP] in the PR title. WIP: seems not to work.

There are many check_docs CI failures.

I may not quite be finished yet :)

Sure. BTW, looking at the nice gray Draft GitHub icon this morning
I figured this must have been triggered by placing [WIP] in the PR title. WIP: seems not to work.

When you create a PR it gives you the option of creating it as a draft (I think I did that since I knew this would take a while)

At the moment this is mostly stuff moved from CHANGES into a migration guide form. I think the intention is that this will replace the wiki page for 3.0 that we have at the moment:
https://wiki.openssl.org/index.php/OpenSSL_3.0
If so, then I think there's quite a lot of content on that page that could usefully be moved into the migration guide.

A large portion of it is in there already in some form..
Do you prefer the wiki sections as they are?
You already have moved sections 6 and 7 into pod files already which is one of the major parts.
Section 9 doesnt seem all that useful.

If so, then I think there's quite a lot of content on that page that could usefully be moved into the migration guide.

Also CHANGES.md currently contains various hints/lists how to replace deprecated function that could be moved to the migration guide.

Also CHANGES.md currently contains various hints/lists how to replace deprecated function that could be moved to the migration guide.

A large section of the migration guide is related to deprecated functions already.
You might have to be a bit more specific if there is something that is missing.
Please also be aware that changes.md is not exactly a small list for 3.0 :)

Ah, just noticed that your PR already moves those parts of CHANGES.md that I had in mind :+1:

A large portion of it is in there already in some form..
Do you prefer the wiki sections as they are?
You already have moved sections 6 and 7 into pod files already which is one of the major parts.
Section 9 doesnt seem all that useful.

Section 6 is mostly covered by crypto.pod, although I think a prominent reference to that page from the migration guide would be useful.
Section 7 seems covered by fips_module.pod in this PR. Again I think the migration guide should prominently reference that page.
I agree section 9 is not particularly useful.
But what about sections 1 - 5 and 8?

@mattcaswell I have moved across the sections from the wiki.. Most of the sections are the same. Hopefully this is getting closer now.

Can this be taken out of WIP now?

Can we also change the two release email text templates (dev/release-aux/openssl-announce(-pre)-release.tmp) to remove the wiki link and instead have a link to the migration guide (would fix #15186)?

Can we also change the two release email text templates (dev/release-aux/openssl-announce(-pre)-release.tmp) to remove the wiki link and instead have a link to the migration guide (would fix #15186)?

Looks like a dependancy that should be done after this PR goes in.. Duplicated your text in the issue

Taken out of draft state.

Thanks for the review matt, it is a bit time consuming to read...

Thanks Pauli, comments addressed. There were a few more items that I grouped together. The pattern I was following matched what we do in some other places for groups of =item

Addressed latest round of nits :) Thanks for looking.


Added latest missing changes from security scanning PR (#1289)

Not showing the flashy message "Unable to fetch newer tags data" for every polling.
Showing "No vulnerabilities found" on tags#show panel istead of an empty space.

Done.

Thanks 👏


IndentationError: unexpected indent

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
A cell with indented code cannot be run as it could before.  In this example the second cell cannot be run:
print ('hello')

if 1:
    print('hello again')

#%%
    print ('hello')

Versions

Spyder version: 4.1.2
Python version: 3.7.2 64b
Qt version: 5.9.6
PyQt version: 5.9.2
Operating System name/version: Win7 64b

Dependencies

# Mandatory:
atomicwrites >=1.2.0           :  1.2.1 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  0.6.1 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.2.0 (OK)
jedi =0.15.2                   :  0.15.2 (OK)
nbconvert >=4.0                :  5.3.1 (OK)
numpydoc >=0.6.0               :  0.8.0 (OK)
paramiko >=2.4.0               :  2.4.2 (OK)
parso =0.5.2                   :  0.5.2 (OK)
pexpect >=4.4.0                :  4.7.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.4.8 (OK)
pygments >=2.0                 :  2.3.1 (OK)
pylint >=0.25                  :  2.2.2 (OK)
pyls >=0.31.9;<0.32.0          :  0.31.9 (OK)
qdarkstyle >=2.8               :  2.8 (OK)
qtawesome >=0.5.7              :  0.5.7 (OK)
qtconsole >=4.6.0              :  4.6.0 (OK)
qtpy >=1.5.0                   :  1.5.2 (OK)
rtree >=0.8.3                  :  0.8.3 (OK)
sphinx >=0.6.6                 :  1.8.2 (OK)
spyder_kernels >=1.9.0;<1.10.0 :  1.9.0 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  17.1.2 (OK)

# Optional:
cython >=0.21                  :  0.29.2 (OK)
matplotlib >=2.0.0             :  3.0.2 (OK)
numpy >=1.7                    :  1.15.4 (OK)
pandas >=0.13.1                :  0.24.2 (OK)
scipy >=0.17.0                 :  1.2.1 (OK)
sympy >=0.7.3                  :  1.3 (OK)

Hi @adriesse, it seems that the snippet posted on the issue has wrong identation. That should be fixed by correcting the identation of the offending lines.

To run a cell, normally only the indentation within that cell must be correct--at least that's the way it used to work.  Anyway, I've updated the snippet so that it is correct for the whole file as well.  The second cell still does not run.

This is a duplicate of #11023, which should be fixed in spyder-kernels.
I can't reproduce the error here using the same spyder-kernels version as @adriesse

I apologize for not finding that other issue earlier, but the way I read now it is that it was fixed for .ipy files but not for .py files and nevertheless closed.  I'm afraid I don't quite understand this.

It should work on py and ipy files. I think we are only going to allow ipython magic commands in ipy eventually but code cells will still work in py files.
@impact27 Can you reproduce this one?

With the ipython PR I get:
In [1]: runcell(1, '/Users/quentinpeter/Desktop/untitled2.py')

WARNING: This is not valid Python code. If you want to use IPython magics, flexible indentation, and prompt removal, please save this file with the .ipy extension. This will be an error in a future version of Spyder.

hello

In [2]:

I can't reproduce it either. @dalthviz, can you reproduce this on Windows?

@impact27 I get that too.  Off topic but I think that warning is coming up in error. We should check if the % is in a comment.

I think that warning is coming up in error

Why? Random indentation is not correct python code. Executing:
#%%
    print ('hello')

Shouldn't work, unless this is a ipython file.

I observe the same behaviour, whether the filename ends in '.py' or '.ipy'.

Why? Random indentation is not correct python code

It also not correct in ipy files either. This behavior is actually most important in python files particularly for the code cells in the if __name__ = "__main__" section.

Why? Random indentation is not correct python code

It also not correct in ipy files either. This behavior is actually most important in python files particularly for the code cells in the if __name__ = "__main__" section.

Fair, then we can use leading_indent from IPython.core.inputtransformer2 (PY3 only) when running cells and the full TransformerManager for ipython files.

I thought this was an editor/ide feature, not art of the Python language.

Have you all decided which behavior you will provide going forward?

Hi @adriesse I think some ideas were indeed proposed by @impact27 what do you think @ccordoba12 ?
Also, checking this I wasn't able to reproduce the error (at least using Spyder 4.1.3) using Ctrl + Enter to run the cells.
This is what I'm getting with the Copy full cell contents to the console when running code cell option enabled (this option is available in the Preferences dialog > Editor > Run code):

And this is what I'm getting with the option disabled:

If you keep experiencing the issue (the raise of an IndentationError) could you try to:

Update to Spyder 4.1.3
Record a GIF for a better understanding of the way you are running the cells and how an IndentationError is being raised

Any new input (info about the error you experienced and/or perspective on how things should be working) is greatly appreciated, thanks :)

I think some ideas were indeed proposed by @impact27 what do you think @ccordoba12 ?

Let's wait to see what @adriesse says because I can't reproduce this bug either on Linux.

I'm still unclear on what your intended behavior is, and/or whether there was a conscious decision recently to change the intended behavior, so I don't whether it is a bug.  Anyway, here are some screen shots:

With "copy full cell contents":

Without "copy full cell contents":

Thanks for the screenshots @adriesse I was able to reproduce this!:

Please update ipython (that should enable you to just see a warning instead of the IndentationError):

Thanks!  The upgrade changes the error to a warning, and now if I rename the file to .ipy the warning goes away.
How will it be in the future?
As @bcolsen observed above:

It also not correct in ipy files either. This behavior is actually most important in python files particularly for the code cells in the if name = "main" section.

What is the motivation for disallowing the execution of indented code blocks?  Has it caused problems?

I think that indentation is a fundamental part of the syntax of Python and taking that into account basically mixed indentation levels are not the correct way to go (the code will not be accepted for the Python interpreter). As an example the following isn't correctly formatted Python code:

Even though currently you can run this inside Spyder (and a warning mentions what I'm saying):

Using .ipy and IPython in general provides a layer that can handle, for example, the mixed indentation since IPython has a transformation logic that not only provides the way to handle the semantic of magics but also can handle things like flexible indentation. However, at the end, the transformation logic that IPython uses translates your code into properly formatted Python (for example removing the leading indentation that isn't supported for the interpreter).
Maybe I'm missing some stuff, and please guys correct me if I'm messing up some where in the explanation, but that's why we not encourage using indented blocks if running from .py files :)

@dalthviz The only indentation flexibility that ipython has is if code has an indentation in the first line  that indentation is removed from all the other lines. This also isn't corrected in .ipy files because they don't support executing codecells we are tagging that on ourselves.
As @impact27 mentions this, is the solution:

Why? Random indentation is not correct python code

It also not correct in ipy files either. This behavior is actually most important in python files particularly for the code cells in the if __name__ = "__main__" section.

Fair, then we can use leading_indent from IPython.core.inputtransformer2 (PY3 only) when running cells and the full TransformerManager for ipython files.

We could even implement it ourselves:
https://github.com/ipython/ipython/blob/0bc26f65bc775082dc36d89edc1657be031b9e79/IPython/core/inputtransformer2.py#L34
I think that allowing codecells with arbitrary initial indent is fine. I don't think we need to be that strict about it. It will still give plenty of indentation errors:
In [4]:     print("hello")
   ...: print("hello")
hello
hello

In [5]:     print("hello")
   ...: print("hello")
   ...:         print("hello")
  File "<ipython-input-5-ed6671ba29f1>", line 3
    print("hello")
    ^
IndentationError: unexpected indent

In [6]:     print("hello")
   ...:         print("hello")
   ...:         print("hello")
  File "<ipython-input-6-e529d318b1ea>", line 2
    print("hello")
    ^
IndentationError: unexpected indent

In [7]: print("hello")
   ...:     print("hello")
   ...:     print("hello")
  File "<ipython-input-7-e529d318b1ea>", line 2
    print("hello")
    ^
IndentationError: unexpected indent

In [8]:     print("hello")
   ...:     print("hello")
   ...:     print("hello")
hello
hello
hello

In [9]:         print("hello")
   ...:     print("hello")
   ...:     print("hello")
  File "<ipython-input-9-e529d318b1ea>", line 2
    print("hello")
    ^
IndentationError: unexpected indent

I think that allowing codecells with arbitrary initial indent is fine.

I agree.

We could even implement it ourselves

@bcolsen, could you create a PR for this?

On a related note, I have the impression that Spyder is now saving my file (all changed files?) whenever I run a cell, whereas previously it only did so when running the whole file.  As with the previously discussed behavior, it is unclear whether this is by design intent or a side-effect of some other change.  I can see the logic in saving other changed files in case there are dependencies, but saving the current file doesn't seem necessary or desirable--at least to me.  I have now unchecked the editor/run_code/save_files option and I'll how that goes.

On a related note, I have the impression that Spyder is now saving my file (all changed files?) whenever I run a cell, whereas previously it only did so when running the whole file. As with the previously discussed behavior, it is unclear whether this is by design intent or a side-effect of some other change. I can see the logic in saving other changed files in case there are dependencies, but saving the current file doesn't seem necessary or desirable--at least to me. I have now unchecked the editor/run_code/save_files option and I'll how that goes.

I don't think it should do that. Could you open a new issue for this behaviour?

Fixed by https://github.com/spyder-ide/spyder-kernels/pull/243


Support overriding colors using vim.g.catppuccin_override_colors

This PR proposes a simple way to override the palette colors by setting the global variable vim.g.catppucin_override_colors.
Usage:
  vim.g.catppuccin_flavour = "mocha"
  vim.g.catppuccin_override_colors = {
    base = "#ff0000"
  }
  vim.cmd [[colorscheme catppuccin]]

Nice. thanks @3rd for submitting the PR.

Hey, @sandangel
No problem, should it throw an error or print a message if a key in the user provided palette doesn't exist?
Should I add some documentation about it?

sorry, I'm not the owner so not really can make decision. but from an engineer perspective:

should it throw an error or print a message if a key in the user provided palette doesn't exist

I think so. Basically we should give feedback when user configure something wrong. A warning message would be better in term of user experience.

Should I add some documentation about it?

Yes. To let user know about this feature and how to use it. So they won't open a new issue for this.

hi @mainrs , could you please have a review on this PR?

Hi! I am actually not familiar with nvim. I think one of the other contributors is better suited to review it.

Oh sorry. @Pocco81 @vinibispo could you help?

I've been staying out of this because I'm not maintaining this whatsoever. From a technical POV I think the changes are great, but I'd prefer to have Pocco have the last word in this, as this is his baby. :D

Sorry for the delay! I'm doing a rewrite of the plugin :)

from: https://github.com/catppuccin/nvim/pull/165/commits/62856bd8d54220f70118798df26965d03d2b20c1

feat: added color_overrides to settings

the g:catppuccin_override_colors variable was removed in favour of a
setting in the user's Catppuccin conf. This commit also added the
ability to change individual colors per palette and also apply changes
to all of them.

hi @Pocco81 , in that case can you fix the README? I think it's still referencing the old proposal from this PR.


Bad layout of blog posts

I took the new layout for blog posts (see https://github.com/OpenElements/website/issues/74) and refactored it to be dynamic.
The current PR can be found here: https://github.com/OpenElements/website/pull/70
Sadly the layout is broken since all the classes that are used in the dynamic content creation of Hugo does not fit. The current state does not have any specific layout for headlines or links for example. A concrete example can be found in the preview here: https://deploy-preview-70--open-elements.netlify.app/posts/2019-01-09-integration-docker/
This is how it looks on my machine:

The issue is fixed please check the blog branch.


Models: Fail if submodule not installed

Expected behaviour
A git clone should work out of the box or error / warn if dependencies are missing.
Actual behaviour
Git clone is installed correctly in develop mode. Module can be imported, client can be instantiated, but has the attributes client.model_1, client.model_111, ... instead of the expected client.common, client.inverter, ...
Steps to reproduce
git clone https://github.com/sunspec/pysunspec
pip install -e pysunspec

and then try an example such as https://pysunspec.readthedocs.io/en/latest/pysunspec.html#interacting-with-a-sunspec-device.
Suggested fix
Error out or warn the user / developer that the model definitions could not be found.
Notes
The README states that the clone should have --recursive for the git submodules, but that may be overlooked in development, customized or automated installations. This is to warn / fail early in case of an inconsistent and non-functioning installation.

I had a closer look and it seems that the branch
https://github.com/sunspec/pysunspec/blob/5242ea9e4c687061cc0b8de4417b1943ed8f9264/sunspec/core/device.py#L907
is not followed because model_type_get(1) does not throw any exception.


Paths for Images in Dokumentation are wrong

In this Documentation of SFTP List the Paths are wrong and wont bring you to the actual linked Images

The Path to the Images currently is:

"https://github.com/mulesoft/docs-connectors/blob/latest/sftp/1.3/modules/ROOT/pages/sftp-list-operation-1.png"

The Path to the Images should be:

"https://github.com/mulesoft/docs-connectors/blob/latest/sftp/1.3/modules/ROOT/images/sftp-list-operation-1.png"

sooo it goes to "/pages/" instead of "/images/"

Would also be cool to update the Images to show whats described.
You explain how to do this and that, then showing a image with not even half of the mentioned steps.... not really a good example.

Thank you for your valuable feedback. Use the latest version of SFTP Connector 2.1 here https://docs.mulesoft.com/sftp-connector/latest/sftp-list


TypeScript error about missing @tanstack/virtual-core unless you enable skipLibCheck

Describe the bug
I get this TypeScript error when using @tanstack/react-virtual unless I enable the "skipLibCheck" option in tsconfig:
node_modules/@tanstack/react-virtual/build/types/react-virtual/src/index.d.ts:1:62 - error TS2307: Cannot find module '@tanstack/virtual-core' or its corresponding type declarations.

1 import { PartialKeys, Virtualizer, VirtualizerOptions } from '@tanstack/virtual-core';
                                                               ~~~~~~~~~~~~~~~~~~~~~~~~

node_modules/@tanstack/react-virtual/build/types/react-virtual/src/index.d.ts:2:15 - error TS2307: Cannot find module '@tanstack/virtual-core' or its corresponding type declarations.

2 export * from '@tanstack/virtual-core';
                ~~~~~~~~~~~~~~~~~~~~~~~~

Found 2 errors in the same file, starting at: node_modules/@tanstack/react-virtual/build/types/react-virtual/src/index.d.ts:1

Your minimal, reproducible example
https://github.com/dumbmatter/tanstack-virtual-typescript
Steps to reproduce

Clone repo
npm install
npm run tsc
Observe error
Uncomment the skipLibCheck line in tsconfig.json
npm run tsc
Observe no error

Expected behavior
There should not be an error when you run TypeScript.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
Node v18.4 on Linux
tanstack-virtual version
@tanstack/react-virtual v3.0.0-beta.2
TypeScript version
v4.7.4
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Fixed in the latest release.


inconsistent results from API queries

Having a problem with hotspot rewards API calls where the rewards for a longer period doesn't equal the sum of the rewards of shorter periods within it.  For example:
The API returns rewards for 10/1 to 10/27:<PHONE_NUMBER>6
The API returns rewards for 10/27 to 10/28:  849902422
sum of these:<PHONE_NUMBER>8
but the API returns rewards for 10/01 to 10/28:<PHONE_NUMBER>0, or 78604392 greater than the sum of the individual periods.
[https://api.helium.io/v1/hotspots/1162fRqWoUGd8DUexz92d3ZsVaZre4wjXFTWEmLjK4WnXkmZMss/rewards/sum/?min_time=2020-10-01T00:00:00&max_time=2020-10-27T00:00:00]
{"data":{"sum":"33108296896","min_time":"2020-10-01T00:00:00Z","max_time":"2020-10-27T00:00:00Z"}}
[https://api.helium.io/v1/hotspots/1162fRqWoUGd8DUexz92d3ZsVaZre4wjXFTWEmLjK4WnXkmZMss/rewards/sum/?min_time=2020-10-27T00:00:00&max_time=2020-10-28T00:00:00]
{"data":{"sum":"849902422","min_time":"2020-10-27T00:00:00Z","max_time":"2020-10-28T00:00:00Z"}}
[https://api.helium.io/v1/hotspots/1162fRqWoUGd8DUexz92d3ZsVaZre4wjXFTWEmLjK4WnXkmZMss/rewards/sum/?min_time=2020-10-01T00:00:00&max_time=2020-10-28T00:00:00]
{"data":{"sum":"34036803710","min_time":"2020-10-01T00:00:00Z","max_time":"2020-10-28T00:00:00Z"}}

Nice find @foster805 and nice fix, @madninja


TreeListEnableHeaderTotals setting does not save properly

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Start processhacker with empty settings file.
See that columns have header totals
Go to options > general, enable advanced options
Under advanced options set TreeListEnableHeaderTotals to 0
Close settings
Restart processhacker as suggested
Header totals still shown

Expected behavior
A clear and concise description of what you expected to happen.
Header totals should not be shown anymore.
NOTE: If the setting is manually set to zero in the XML file, the header totals are not shown.
Screenshots
I don't think any are needed.
Desktop (please complete the following information):

OS: Windows 10
Version: 19044.1415

Additional context
Add any other context about the problem here.
Also occurs with a fresh compile-from-master.

The checkbox on the General tab overrides any manual changes in the advanced tab:

This is by design since the general tab is saved last.


Link to CNCF training courses

Add a hyperlink from https://kubernetes.io/docs/tutorials/online-training/overview/ to https://www.cncf.io/certification/training/
Also, sort the list of courses (based on sorting the entire line alphabetically).

Thanks for your PR @sftim . The link you added to CNCF training is redundant because it is the same course that is offered on edx.
Thanks for listing it in an alphabetical order.

This change as it stands isn't needed.


"Starts_With" should not be marked as inline, and write_component_static_forwarder should be.

The reason for this comes down to clang's interpretation. Starts_with is already entirely in a struct, while "write_component_static_forwarder" is not, and should be marked as such.

/azp run


determine if you can intrinsic an intrinsic

Will affect inheritance of uiobject templates.

it appears you cannot; however, testing this currently throws errors in the client; need to find a clean way to test this for wowless-addon


PIZ2-add-a-beverage-model-manager-and-service

Ticket link:
PIZ2
Description:
Implement a model, relate it with the order model or order detail model, implement a basic manager and a service for it. And show it on the page.
Screenshot/Video:

The beverage options are visible and it allows you to select multiple ones

The total price includes the beverage (doesn't include the size price)

The order detail shows the beverages (doesn't include the size price)

Beverage section

Notes:
The calculate order price test is failing :disappointed:
The order price doesn't include the size amount :warning:

LGTM! :100:


empty app/Http/routes.php file

After the composer install command, the new project is missing routes.  Do you recommend some common routes in routes.php?  Perhaps this could contain some example routes, so that the new project has something to display as a 'hello world'?

Excute the command php artisan app:install for install lms

The routes are managed directly from each module

So Apache/Nginx should not point to the public folder of  the NewProject/public/?  I see

If you must point to the public folder (NewProject / public /), it's just that LMS-laravel is a modular application, and each module sets its own routes, for more information visit https://sky.pingpong-labs.com/docs/2.1/modules, but the rest is all the same.
I'm sorry for my English.

Si debe apuntar a la carpeta pública(NewProject/public/), es solo que LMS-Laravel es una aplicacion modular, y cada modulo establece sus propias rutas, para mas informacion visita https://sky.pingpong-labs.com/docs/2.1/modules, pero el resto es todo igual
Lo siento por mi ingles

Whoops, looks like something went wrong.
2/2 ErrorException in FileViewFinder.php line 137: View [default.views.errors.form_error] not found. (View: /home/vagrant/Code/acad/themes/Default/views/auth/login.blade.php)
what's problem ?

It seems that is not the view, see if there is vistam and tell me if the problem continues


Problem with combat tracker after system update

After system update, when the combat encouter is started the initiative slots are not automatically claimed, and after "taking out" the tab with the combat tracker, it takes up the entire length of the screen (like on a screen shot).

I'm not sure what bug your describing. You seem to be describing system functionality, but you've filed the issue for a module. Can you reword and/or expand on what the issue is?

Sorry, my bad - I got the wrong repositories. It should be system one.


Using :value and @change instead v-model

What you are trying to do. A clear and concise description of what you want to happen:
I'm migrating from vue 2 to vue 3 and I've replaced bootstrap-vue with bootstrap-vue-next.
The problem I'm running into is that the data is coming through props from various components above and I'm not able to use the v-model.
In the old code (vue 2) it basically plays this role, but now this happens:
https://stackblitz.com/edit/vitejs-vite-pxa5ft?file=src%2FApp.vue
My question is, why does the  not write if in vue 2 with bootstrap-vue it works?
Here is the old code in vue 2:

Here it is now with vue 3:

Environment:

OS: [MacOS]
"dependencies": {
"bootstrap": "^5.3.3",
"bootstrap-vue-next": "^0.22.7",
"vue": "^3.4.29"
},

Because selectedText is a reactive and doesn't have a .value property

Also in the provided snippet you didn't import ref

But the chain in logic is wrong. @change will only run during the @change 's input event, naturally. But you have blocked changing of the value of the input. It's odd behavior.
You may prefer using the following code, assuming you even need the change event
<template>

    <BFormInput v-model.lazy="selectedText" @change="console.log('changed')" />

Value: {{ selectedText }}

</template>

But the chain in logic is wrong. @change will only run during the @change 's input event, naturally. But you have blocked changing of the value of the input. It's odd behavior.
You may prefer using the following code, assuming you even need the change event
<template>

    <BFormInput v-model.lazy="selectedText" @change="console.log('changed')" />

Value: {{ selectedText }}

</template>

You're right, ref is working, I'll test it in my code now, but I read in the documentation that I should use reactive instead of ref when using complex objects (which is my case)

Regardless the reactive isn't the issue.
The vue docs mention reactive but I think most people will use ref for everything
I'm surprised <input :value="selectedText" @change="changeValue($event)" /> works. Logically it doesn't make any sense on how the value is meant to change. But vue's usage of input v-models is different than that of a component v-model

The reason why it works in bootstrap-vue though is because they overwrote the native @input and @change events. This is because of how vue 2 handles v-models -- a v-model in vue 2 compiled to :value="" @input="" whereas in vue 3 its' :value="" @update:modelValue="". So, in the last few iterations I made the decision to not overwrite the natives, as anything you can get from them you can do using Vue 3 features (modelValue)

When you submit reproductions you'd always need to show what you're doing. This mov is meaningless to me

When you submit reproductions you'd always need to show what you're doing. This mov is meaningless to me

What do you need to see?