Building of the image still need do download packages in its last stage

Since we refactor the management of the docker image, we have drastically reduce the size of the image to download.
For reminding, this is the command run to pre-install all the dependencies :
BASIC_DEP = All the dependencies

RUN apt-get update &&
    apt-get -qq -y install python3 python3-dev python3-pip python3-setuptools default-libmysqlclient-dev apt-file apt-utils &&
    apt-get install -qq -y --no-install-recommends --download-only  <BASIC_DEP>
RUN echo <BASIC_DEP> > /dependencies.txt

And the command to finally install them :
RUN apt-get install -qq -y --no-install-recommends $(cat /dependencies.txt)

But this method doesn't fully install the dependencies : it only download the selected packages and will download the missing dependencies when running the last command.
This behaviour not only add approximately 87 other MB to download, but it also break the image when it's needed packages isn't available anymore. This cause the current prod image to be outdated and to don't work anymore.
So we need to fix it asap.

I'm thinking about running a python script at the end of the building of basetuxml.
This script will do the follow :

run in a subprocess apt-get install -s -y --no-install-recommends $(cat /dependencies.txt)
retrieve all the additional package to install and add them to /dependencies.txt
remove the script from the image

The preceding solution reduce the number of downloaded data from 87 MB to 13 MB.

Git removed from the dependencies (we don't use git, so why do we install it?).
Fetched 8839 kB in 9s (929 kB/s)
So we need to investigate about why flex, iptables, bc, bison, btrfs-progs, dialog, gcc-6-plugin-dev, initramfs-tools, jfsutils, libcrypto++6, lzop, mcelog, moreutils, nfs-kernel-server, ppp, qemu-system, qemu-utils, qemu, reiserfsprogs, squashfs-tools, xfsprogs, grub-legacy, libdb5.3-dev, liblz4-tool, pcmciautils and quotatool aren't downloaded before.

https://unix.stackexchange.com/questions/408346/how-to-download-package-not-install-it-with-apt-get-command Could help to explore.


[1509] bug revert audited gem

Context

Changes proposed in this pull request

Guidance to review

Link to Trello card
Trello card
Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated added to the Azure KeyVault

 Revert audit library due to parallel problems


Meterings stopped rendering when opening a node graph file

Describe the bug:
When a node graph save (.ang file) is opened while the program is running, all the meterings on the playback panel on the bottom will stop rendering and stay blank.

Except, it is still working normal if I open the vectorscope and spectrum. Also, the decibel meter on the node graph is not affected

Additionally, this is what seems to happen everytime I open a node graph (not all the time):

Amethyst Details (required):
Version 1.9.14   (Windows 11)
To Reproduce (optional)
Steps to reproduce the behavior:

Open the program
Play any audio on the queue
Go to the node graph tab, open any node graph file (.ang files that you previouisly saved)
All meterings (minimized on the player panel at the bottom) will go blank despite the audio still playing, except for the decibel meter shown on any nodes

Unable to reproduce on same version on arch linux
Deprecation and MediaImage (#22) warnings are unrelated


[scheduler] Prevent frequent updates for unassigned shoots

How to categorize this PR?

/area robustness
/kind enhancement
What this PR does / why we need it:
This PR contributes the following improvements to the scheduler:

Sort error message of non-eligible seed candidates to prevent status flapping.
The scheduler not to be triggered on shoot status updates. This circumvented the reconciliation backoff in the past.

Special notes for your reviewer:
/cc @ScheererJ thanks for reporting
Release note:

The `gardener-scheduler` was improved to consider reconciliation backoffs. In the past, unassigned shoots were affected by frequent scheduler reconciliations and status updates which potentially strained the scheduler and etcd.

/retest-required


tools/bbbsupervisor: Implement basic prometheusFollower (without 3rd party deps)

Like logFollower, a prometheusFollower has a basic follow()
method, and when called to follow, periodically queries a Prometheus
server for a particular expression.
This PR has no 3rd party dependencies.

Great pull-request, works like a charm. I'd apprechiate a quick review from @benma (he had some minor nits when looking over it yesterday).
tACK https://github.com/digitalbitbox/bitbox-base/pull/92/commits/8185a9ee8d36dbbe11d4bede2dfbe82c803cf559

Thanks both for your reviews! I addressed most of the nits (and replied to all) and force-pushed to be8d0cad2179a4f8c514eaec7b478fdb3adbcdb4. I'll plan to merge if CI passes, but let me know even post-merge if there's anything you disagree with in be8d0cad2179a4f8c514eaec7b478fdb3adbcdb4, and I can send follow-up PRs.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test

Docs Build status updates of commit 1a0e9d4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-25-07-17-03 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-25-07-17-03

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Use JDK 23 for builds

Need to enable -proc:full on JDK 23. Looks like they've backported it to the latest JDK releases of Java 17 and Java 11 but not others so may have to use a custom Maven profile for this.


Missing Thumbnails On Convert-a-Card Projects

Missing pics here for the Urdu and Chinese Projects. https://www.libcrowds.com/collection/convertacard/contribute/

Thanks, and any suggestions for nice images would be very welcome! Because I know you're good at finding those (or I can't be bothered...yeah, the first one) :stuck_out_tongue_winking_eye:

We also need one for the Indonesian projects - even though they're complete people might want to go back and have a look.
Of course we can also pass this soft of thing on to our curators to help give them another element of input/ownership.

Will deal with this here https://github.com/LibCrowds/vue-pybossa-frontend/issues/295


Gradient dialect removes qnode attribute from quantum functions when creating helper functions.

Expected behavior: The attribute remains through the lowering of gradient and quantum dialect up until LLVM-IR (in which case we might wish to annotate it with some metadata).

Actual behavior: The gradient transforms generates helper functions which will strip the qnode attribute from qnodes. E.g.,

  func.func private @f(%arg0: tensor<f64>) -> tensor<f64> attributes {diff_method = "parameter-shift", llvm.linkage = #llvm.linkage<internal>, qnode} {
  }

Changes to:
  func.func private @f.quantum(%arg0: memref<f64>, %arg1: memref<?xf64>) -> memref<f64> attributes {gradient.qgrad = @f.qgrad, passthrough = ["noinline"]} {
}

This causes async to not be triggered since async looks for the qnode attribute.

Reproduces how often: Always

Copying description from the duplicate issue:

Some MLIR transforms, like the parameter shift pass, predate the introduction of the qnode attribute on MLIR functions with quantum code. The use of the attribute has also been extended, for example to determine asynchronous execution scopes.
In order to support the asynchronous execution of shifted circuits, the parameter-shift transform should propagate the qnode attribute from the original function it acts upon to the shifted function calls which each represent an independent quantum execution.
Note I don't think the current implementation would be able to benefit much from asynchronous execution, except perhaps for two evaluations at a time, because the shifted circuits are not generated in a batched but a procedural fashion. See the following snippet, where the results a quantum call a used pretty much immediately:
https://github.com/PennyLaneAI/catalyst/blob/b94be65521c726eb231dc9a42f00645757bd804b/mlir/lib/Gradient/Transforms/GradMethods/PS_QuantumGradient.cpp#L78-L91


Have a way to leave out the full_name for the Proto Encoder

Is your feature request related to a problem? Please describe.
Currently the full_name is always needed in the proto raw encoded. This is additional hassle and prone to errors, also it's causing a little additional overhead.
Describe the solution you'd like
There should be an encode without the full_name, but that can only be used id the message use is the first message defined. Using references this is very much possible, and also how I figured out this might be the default use.
Possibly we could throw an error if the method without the full name is used, but the resolved proto file does contain multiple messages.
Describe alternatives you've considered
Just using it with the name, but it's an hassle when the proto file only contains one message.
Additional context
As you can see in https://github.com/gklijs/ksqlDB-GraphQL-poc/blob/3670101fd36f2223dfed094601f525bb48a09b5b/rust-data-creator/src/kafka_producer.rs#L17 it's quite some hassle.

I could easily fix this, but would like to know how useful it's to others.


Doesn't work on OS X

The Chains: New Document command doesn't show up in the Command Palette.

I've just pushed out a fix, make sure you're on Chains v1.1.0.
Please report back whether it works for you

It works now.
This is going to be very useful.
Thank you.

No worries :)


Bug when deleting feature

For the features that use the BasicPageDetail component close detail page when feature deleted.

Fixed with 5835a26ec1c080c7e6bd92986419e0a38992ff98


Manager does not retry for failed nodes (token:// discovery)

version: 0.4.0
When Swarm manager starts (using discovery token://), if the node in the list is down, the manager flags it as dead indefinitely and does not pick it up again when the node comes afterwards.
This also happens after the Swarm manager was started. Once a node dies, the engine logs Removed engine %s and even though engine comes up afterwards, in the --debug logs the only Updated engine state belongs to the node that never failed.
Some logs... Around 05:36:20 I took node alp down and brought up 2 minutes later. But it never showed up in the logs nor in the /info... But when I started another manager container that targets the same token://, it was able to pick up the node died earlier.
Hence, the manager is most definitely not retrying for failed nodes. It should be more tolerant to faults.
time="2015-09-01T05:36:15Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:36:16Z" level=info msg="Registered Engine hellodocker at hellodocker.REDACTED:xxxx"
time="2015-09-01T05:36:16Z" level=debug msg="Updated engine state" id="2MJA:DPJM:6ACB:GUN2:G4VK:GZRT:NNMS:JUYJ:IEYB:A5AP:HAMX:XCDA" name=alp
time="2015-09-01T05:36:16Z" level=info msg="Registered Engine alp at alp.co:xxxx"
time="2015-09-01T05:36:34Z" level=info msg="Removed Engine alp"
time="2015-09-01T05:36:46Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:37:16Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:37:46Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:38:16Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:38:46Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:39:16Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:39:47Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:40:17Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker
time="2015-09-01T05:40:47Z" level=debug msg="Updated engine state" id="VJEO:U3TS:HJ7T:IKNS:JHJP:YTOW:UVLP:NUMC:RSA7:U42X:OMNC:QCYW" name=hellodocker

cc: @garimakhulbe

I can confirm the behavior, though I don't see the "removed engine" message.
I could make an argument that this would self correct in most instances. However it would be better off to not have any timing dependent problems.

@MHBauer maybe you need to start with --debug (actually it's an info log, but I'm not sure)...
and no it doesn't self-correct (unless container/VM restarts), that's what this issue is about.

It self corrects if the node stops advertising long enough for it to be removed from the list, and then re-added afterwards.
Here's my version info:
root@node-1:~# docker -H <IP_ADDRESS>:3375 version
Client:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:35:49 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      swarm/0.4.0
 API version:  1.16
 Go version:   go1.4.2
 Git commit:   d647d82
 Built:
 OS/Arch:      linux/amd64

When the engines are bulk added in https://github.com/docker/swarm/blob/master/cluster/swarm/cluster.go#L253 addEngine() fails and returns an error, which is silently discarded. Thus the code never gets to the refresh loop that periodically checks on the state of a node.
It never gets re-added until it disappears and is readded through the join registration being killed and restarted.
I am not really sure how to fix it, but that is the root cause.

:+1: thanks for the investigation @MHBauer.

I think this is the same as issue #1044. We don't try to do an initial connect to an engine more than once.

eh that seems stalled.

We have to redesign the node registration system.
Right now, as you mentioned, if the initial registration fails then it gives up. That's for multiple somewhat valid reasons.
It just assumed that whenever we detect a new node, a join was just issued therefore the node has just been started therefore it should be reachable. If not, then it was probably because of a join misconfiguration.
Adding a misconfiguring node to the cluster would have caused issues and that's why it's the way it is.
Things changed however, and it should probably work like this instead:

Whenever we find an engine in discovery, we ALWAYS add it
The codebase just have to deal with the fact that we might have invalid engines in the cluster
Engine will retry to connect to it using the delayer (random interval)
docker info would report non-connected nodes as well, along with the last error message. This way, you would actually see in docker info why we couldn't reach an unresolvable address for instance

@aluzzardi ^ this SGTM, I think for point 4, as long as we list healthy / non-healthy engines separately in the output, it can be a very clean solution to the problem.

Issue now tracked by the node management proposal (#1486)


[bug report] element UI CDN cannot use the website dependency report rate exceeded

Element UI version
2.13.0
OS/Browsers version
windows7
Vue version
3.0.0-alpha.0
Reproduction Link
https://jsfiddle.net/mmx38qxw/
Steps to reproduce
element-ui CDN无法使用 网站依赖报Rate exceeded. https://unpkg.com/element-ui/
What is Expected?
css和js 依赖正常加载
What is actually happening?
无法加载导致页面数据无法加载

me too

Hope to resume normal use of CDN as soon as possible

me too

Mee too

mee too

me too.

me too

It's not an Element issue, the CDN UNPKG.com is down maybe changed CDN or just download the files and serve them by yourself

what's the new CDN link

You can add an element discussion group to reflect the problem and see if they have any channels to contact the insiders

It's not an Element issue, the CDN UNPKG.com is down maybe changed CDN or just download the files and serve them by yourself

Where I can download those files~ I can not find any links from https://element.eleme.io

You can try to use NPM to download. Maybe you can download and use it

https://cdnjs.com/libraries/element-ui
you welcome

@calinsinea any alternative for index.css?


Add module Mail when loading AddressListsParser in AddressList

We have had issues with this class, it looks like randomly it is not loading fine the class AddressListsParser from AddressList. These classes are being loaded with autoload so it seems that they are not being loaded fine if the Mail module is not added, like in the other element classes when using the parsers.
This is the error raised:
Message: uninitialized constant Mail::Parsers::AddressListsParser
Backtrace: /data/filer/current/vendor/bundle/ruby/1.9.1/gems/rake-<IP_ADDRESS>/lib/rake/ext/module.rb:36:in `const_missing'
/bundle/ruby/1.9.1/gems/mail-2.6.3/lib/mail/elements/address_list.rb:22:in `initialize'
/bundle/ruby/1.9.1/gems/mail-2.6.3/lib/mail/fields/common/common_address.rb:9:in `new'
/bundle/ruby/1.9.1/gems/mail-2.6.3/lib/mail/fields/common/common_address.rb:9:in `parse'

I do not know a way to test this as this is happening totally random for us.

@jeremy @grosser I can't see any downsides to this.  You?

weird bug ... most likely something else defining parsers or so ... but no harm done ... :+1:

Have the same issue

Any new on this?? We keep having this error sometimes.

Any news on this?
I just encountered this same error. It seems to occur randomly (but deterministically, always for the same addresses).
My traceback:
/var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/elements/address_list.rb:22:in `initialize': uninitialized constant Mail::Parsers::AddressListsParser (NameError)
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/common/common_address.rb:9:in `new'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/common/common_address.rb:9:in `parse'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/common/common_address.rb:96:in `value='
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/structured_field.rb:29:in `initialize'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/from_field.rb:41:in `initialize'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:239:in `new'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:239:in `new_field'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:228:in `create_field'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:141:in `field'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:189:in `method_missing'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:1196:in `default'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:647:in `from'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:1278:in `from_addrs'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:1059:in `smtp_envelope_from'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/check_delivery_params.rb:4:in `check_delivery_params'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/network/delivery_methods/smtp.rb:98:in `deliver!'
	from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:252:in `deliver!'
	from /home/william/scripts/sms:74:in `block (2 levels) in <main>'

Anything we can test deterministically
B mobile phone

On Jan 18, 2016, at 4:45 PM, William Woodruff<EMAIL_ADDRESS>wrote:
Any news on this?
I just encountered this same error. It seems to occur randomly (but deterministically, always for the same addresses).
My traceback:
/var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/elements/address_list.rb:22:in initialize': uninitialized constant Mail::Parsers::AddressListsParser (NameError)     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/common/common_address.rb:9:in new'
from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/common/common_address.rb:9:in parse'     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/common/common_address.rb:96:in value='
from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/structured_field.rb:29:in initialize'     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/fields/from_field.rb:41:in initialize'
from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:239:in new'     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:239:in new_field'
from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:228:in create_field'     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:141:in field'
from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/field.rb:189:in method_missing'     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:1196:in default'
from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:647:in from'     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:1278:in from_addrs'
from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:1059:in smtp_envelope_from'     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/check_delivery_params.rb:4:in check_delivery_params'
from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/network/delivery_methods/smtp.rb:98:in deliver!'     from /var/lib/gems/2.2.0/gems/mail-2.6.3/lib/mail/message.rb:252:in deliver!'
from /home/william/scripts/sms:74:in `block (2 levels) in '
—
Reply to this email directly or view it on GitHub.

Actually, it looks like I was wrong - it's not deterministic. I got the same error about 6 times in a row, but I'm no longer getting it regularly for unchanged input.
If you want, you can run my code (I don't know how much help it will be):
https://github.com/woodruffw/snippets/blob/master/sms/sms.rb
https://github.com/woodruffw/snippets/blob/master/sms/smsrc
It takes a phone number to send an SMS message via an SMTP gateway.
Regardless of whether the phone number is real, the script itself should never fail - all it does is send a batch of emails (that may bounce, but that doesn't concern it).

Oh, threads...

Everyone who's commented here: does this pr fix your issue?

@salrepe can you rebase this? Thanks

I doubt this PR fixes anything ... the autoloading logic should still behave the same / it currently tries the Mail namespace too ... so maybe the 'fixed' behavior was just randomly fixed ?

Oh, threads...

Could this be a threading issue? I'd be pretty scared if individual instances could affect each other like this...

Autoload is threadafe in recent rubies. Was just my reaction to thinking of a deterministic test with threads.
The client could call Mail.eager_autoload! (Note, I'm writing from my phone)
@grosser want commit?

if want commit means 'should we merge this' then I'd say only if someone can confirm that solves the issue ... ideally a failing testcase would be great.

The client could call Mail.eager_autoload!

Thanks, Mail.eager_autoload! appears to have "solved" the problem in my case (at least, I haven't seen any more crashes).

If you can reproduce then a real fix or even failing test case would be
even better :D
On Mon, Jan 18, 2016 at 6:15 PM, William Woodruff<EMAIL_ADDRESS>wrote:

The client could call Mail.eager_autoload!
Thanks, Mail.eager_autoload! appears to have "solved" the problem in my
case (at least, I haven't seen any more crashes).
—
Reply to this email directly or view it on GitHub
https://github.com/mikel/mail/pull/867#issuecomment-172710456.

(assuming it's not a ruby autoload issue but us doing something weird ...
the error is on ruby 2.x ?)
On Mon, Jan 18, 2016 at 6:17 PM, Michael Grosser<EMAIL_ADDRESS>wrote:

If you can reproduce then a real fix or even failing test case would be
even better :D
On Mon, Jan 18, 2016 at 6:15 PM, William Woodruff <
<EMAIL_ADDRESS>wrote:

The client could call Mail.eager_autoload!
Thanks, Mail.eager_autoload! appears to have "solved" the problem in my
case (at least, I haven't seen any more crashes).
—
Reply to this email directly or view it on GitHub
https://github.com/mikel/mail/pull/867#issuecomment-172710456.

I experienced the error on 2.2.4p230, so I doubt it's an autoload issue.
I haven't peeked at the library's internals yet, but I'll do so right now and see if I can find the fault :smile:

Obviated by #1030, uses an explicit require for the address lists parser rather than autoload.

Backported to 2-6-stable as a code style change @ 06d1d7bbcd96de342a4a8a91bc903c1dc86354d5

Hello
I am having a similar issue on rspec-rails CI and JRuby. It happens on Ubuntu but I was never able to reproduce on my mac.
uninitialized constant Mail::AddressList::Address
CI failure: https://github.com/rspec/rspec-rails/runs/1408883200?check_suite_focus=true
    describe 'clears ActionMailer::Base::Deliveries after each example' do
      let(:mailer) do
        Class.new(ActionMailer::Base) do
          default from<EMAIL_ADDRESS>
          def welcome(to:)
            mail(to: to, subject: 'subject', body: render(inline: "Hello", layout: false))
          end
        end
      end

      before do
        ActionMailer::Base.delivery_method = :test
      end

      it 'only has deliveries from this test (e.g. from email@example.com)' do
        mailer.welcome(to: 'email@example.com').deliver_now

        expect(ActionMailer::Base.deliveries.map(&:to).flatten.sort).to<EMAIL_ADDRESS>      end

      it 'only has deliveries from this test (e.g. from email_2@example.com)' do
        mailer.welcome(to: 'email_2@example.com').deliver_now

        expect(ActionMailer::Base.deliveries.map(&:to).flatten.sort).to<EMAIL_ADDRESS>      end
    end

  1) Configuration clears ActionMailer::Base::Deliveries after each example only has deliveries from this test (e.g. from<EMAIL_ADDRESS>     Failure/Error: mailer.welcome(to: 'email@example.com').deliver_now

     NameError:
       uninitialized constant Mail::AddressList::Address
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/elements/address_list.rb:26:in `block in initialize'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/elements/address_list.rb:26:in `map'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/elements/address_list.rb:26:in `initialize'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/fields/common/common_address.rb:9:in `new'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/fields/common/common_address.rb:9:in `parse'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/fields/common/common_address.rb:103:in `value='
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/fields/structured_field.rb:30:in `initialize'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/fields/from_field.rb:42:in `initialize'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/field.rb:277:in `new'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/field.rb:277:in `new_field'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/field.rb:266:in `create_field'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/field.rb:187:in `field'
     # /home/runner/.rubies/jruby-head/lib/ruby/gems/shared/gems/mail-2.7.1/lib/mail/field.rb:239:in `method_missing'

I tried few proposals made here without any changes in the CI result.


Build avr32-gcc from source

@lis-epfl/mavric-lis
It is possible to build avr32-gcc from source (also for MAC OS)
I had issue with an update of glibc on my machine, the pre-compiled avr32-gcc was not working anymore.
I found the solution with this repository:
https://github.com/denravonska/avr32-toolchain
Happy to hear if someone can have it work on MAC OS :-)

Building from source works on MAC OS (tested on 10.10.4) thanks to the avr32-toolchain. :+1:

I was also able to make it work on Mac os! :)

awesome Julien, thanks for sharing! Finally I can use CodeLite natively
on the Mac :)
reminds me that I should release my mavlink-native bootloader some time
soon... works nicely now.
On 17/09/15 10:59 AM, Julien Lecoeur wrote:

@lis-epfl/mavric-lis https://github.com/orgs/lis-epfl/teams/mavric-lis
It is possible to build avr32-gcc from source (also for MAC OS)
I had issue with an update of glibc on my machine, the pre-compiled
avr32-gcc was not working anymore.
I found the solution with this repository:
https://github.com/lis-epfl/MAVRIC/wiki/First-Steps-Setup-on-Linux
Happy to hear if someone can have it work on MAC OS :-)
—
Reply to this email directly or view it on GitHub
https://github.com/lis-epfl/MAVRIC_Library/issues/115.

Indeed that would be great @fschill !
We often break USB connectors while flashing, a mavlink bootloader would be very handy!

Hi Felix,
As discussed lat week, I can have a look and try to integrate within our
current MAVRIC code your stuff.
Thus, could you push mavlink-native bootloader somewhere please ?
It would be so nice to have it already :-) !!
Thanks !!
Grégoire Heitz
Support Engineer LIS Laboratory
2015-09-23 14:23 GMT+02:00 Julien Lecoeur<EMAIL_ADDRESS>
Indeed that would be great @fschill https://github.com/fschill !
We often break USB connectors while flashing, a mavlink bootloader would
be very handy!
—
Reply to this email directly or view it on GitHub
https://github.com/lis-epfl/MAVRIC_Library/issues/115#issuecomment-142583485
.

Hi,
I was away the last few days. Anyway, the bootloader is now on github, with the boardsupport for the MAVRIC autopilot (we have several folders instead of just src/mavric, one for each hardware - the rest is identical). I copied the Library (just the necessary files), but usually this would be a submodule.
https://github.com/fschill/MavBoot
You should be able to compile it with CodeLite or AVRStudio (optimized profile to fit into 8kb). With UART it should be around 7500 bytes.
There is also the XML file for the additional MAVLINK message definitions:
https://github.com/fschill/MavBoot/blob/master/dbgextensions.xml
The comments there should give a rough idea how it works. I still have to post the "other side" for sending images - it's essentially an extension to mavue, written in python.
The bootloader will always activate at reset, send a mavlink message to say hello and wait for approximately 1 second for a reply. If no reply it launches the main program. The PC side, when active, will reply and switch the bootloader to boot mode where it will remain until the "start application" command is sent.
The upload process consists of sending a number of binary blocks (32 bytes) until a full page has been transferred. Each message is acknowledged by the bootloader with a CRC of what it received. Once the full page has been transferred and acknowledged, the "write to flash" command is sent. The bootloader writes the page, and replies with an ACK containing the CRC of what is now in the flash.
It is therefore all quite robust against dropouts, as the uploader can re-transmit blocks without ACK, and verify the pages directly after writing each page. I've successfully flashed through XBee, and also while forwarding from UART to an internal CAN-bus and back (it's a bit slower but works fine).
To speed up reflashing, multiple blocks can be sent in a burst while waiting for all the ACKs to come back. Also, I implemented an additional check before sending a page, where the uploader requests the CRC of the current flash page, and only sends the page if the CRC differs. This makes a huge difference if you only change a constant, as nothing will shift, and it's also a neat "Verify" feature (if the code is already uploaded, a re-upload is just a verify which takes 3-4 seconds). If code changes more significantly, the addresses will shift and the speedup is a lot less, but on average it's still a bit faster. If an upload fails, a re-upload will also resume where it failed.
More later... :) updated Mavue will follow soon...
Felix

Hi again,
just pushed my current version of Mavue to github: https://github.com/fschill/mavue
This has a Bootloader button that allows you to load a .hex file and flash it to the microcontroller via bootloader.
First you have to compile and flash the bootloader to the mavric board. Start mavue with appropriate options, e.g.:
python mavue.py --device=/dev/ttyUSB0 --baudrate=115200
-click on "Bootloader"

reset the mavric board - the Mavlink SYSID and COMP ID should now appear in the list of the new window
select a flash file
click "Write Flash"
It should now upload the file, and show a progress bar. Additional information (errors) are currently shown on the terminal output - check if there are errors. Ignore if there is a checksum error on the last flash page - this is normal as the page is not complete.
If you click "write flash" again it should be very quick (3 seconds) as it will only do a fast verify if the code is identical.

cheers,
Felix

..just noticed that this issue was closed - briefly re-opened to guide your attention to my last two posts with the bootloader and new version of mavue :)

Hi Felix,
Thanks for the two repositories!
I am currently working on this and I would like to know whether there is a size limit on the binary we can send to the microcontroller?
When I try to send it, I have mavue returning an error:

Do you have any clue?

In addition, on Linux, I have the following error if I choose any usb serial
Traceback (most recent call last):
  File "mavue.py", line 89, in update
    msg_key, msg=self.mavlinkReceiver.wait_message()
  File "/home/lis/Documents/myCopter/mavue/mavlink_receiver.py", line 141, in wait_message
    msg = self.master.recv_msg()
  File "/home/lis/Documents/myCopter/mavue/./pymavlink/mavutil.py", line 302, in recv_msg
    s = self.recv(n)
  File "/home/lis/Documents/myCopter/mavue/./pymavlink/mavutil.py", line 758, in recv
    ret = self.port.read(n)
  File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 460, in read
    raise SerialException('device reports readiness to read but returned no data (device disconnected?)')
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected?)

did you ever have such issue as well?

Hi Nicolas,
I never had this error - seems to be happening within the intelhex
library that is included in the project. There isn't really a size limit
for the .hex files - the error rather seems to indicate a 32bit/64bit
issue or something like that (int size different).
Which OS does this error occur on? Is it 32bit or 64bit? I have mostly
tested it on 14.04 64bit without issues.
On 13/10/15 16:58, ndousse wrote:

Hi Felix,
Thanks for the two repositories!
I am currently working on this and I would like to know whether there is
a size limit on the binary we can send to the microcontroller?
When I try to send it, I have mavue returning an error:
python_error
https://cloud.githubusercontent.com/assets/6390059/10458549/98644698-71cb-11e5-9213-3494c522a42a.png
Do you have any clue?
—
Reply to this email directly or view it on GitHub
https://github.com/lis-epfl/MAVRIC_Library/issues/115#issuecomment-147741335.

This is also not an error I have seen. Sometimes if the power supply is
flaky the FTDI chip crashes - then something like this could happen. Or
maybe you have the serial port opened somewhere else?
On 13/10/15 17:26, ndousse wrote:

In addition, on Linux, I have the following error if I choose any usb serial
|Traceback (most recent call last): File "mavue.py", line 89, in update
msg_key, msg=self.mavlinkReceiver.wait_message() File
"/home/lis/Documents/myCopter/mavue/mavlink_receiver.py", line 141, in
wait_message msg = self.master.recv_msg() File
"/home/lis/Documents/myCopter/mavue/./pymavlink/mavutil.py", line 302,
in recv_msg s = self.recv(n) File
"/home/lis/Documents/myCopter/mavue/./pymavlink/mavutil.py", line 758,
in recv ret = self.port.read(n) File
"/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 460, in
read raise SerialException('device reports readiness to read but
returned no data (device disconnected?)')
serial.serialutil.SerialException: device reports readiness to read but
returned no data (device disconnected?) |
did you ever have such issue as well?
—
Reply to this email directly or view it on GitHub
https://github.com/lis-epfl/MAVRIC_Library/issues/115#issuecomment-147749755.

Hi Felix,
The first error related to intelhex is occuring on Windows 7 64bit
The second error is occuring in ubuntu 14.04 64bit.
I also tried mavue with the XBee and the standard LEQuad code and I got the same error. I received messages (e.g. heartbeat) for 3-5 seconds max and then the connexion is lost...
I flashed the bootloader via the JTAG interface on Atmel Studio. I connected the board via the debug board and the 10 pin cable. I also tried to bootload via XBee but got the same issues.
Do I have by chance to recompile pymavlink?
I use Python 2.7.6

Ok - I never tested the bootloader part in windows I think. All the rest
(plotting, etc.) is working fine for me on all OSes. I did test again
the bootloader on Linux and MacOS - both worked fine for me without any
issues.
Regarding the serial connection - I think this must be related to either
the FTDI driver, or the python serial package. Do you have any issues
using the same hardware and Linux in e.g. qgroundcontrol? The only time
I have problems with serial is if the board is powered through USB and
draws too much power so that the USB port cuts off - this leaves the
FTDI driver in a bad state and I have to unplug and replug, and start
mavue again.
However if you have the same issue over XBee I assume the board is
powered separately. The XBee adapter is also FTDI, so maybe you have a
different driver than me?
pymavlink doesn't really have compiled parts, it's all pure python as
far as I know. The only exception is that it dynamically generates the
dialect code based on the XML message definitions if they don't already
exist - but the errors related to that if something goes wrong don't
have anything to do with the serial connection.
As I can't reproduce this error on any of my machines (2 Linux desktops
and MacOS) I don't really know how to proceed. Maybe try on a different
Linux machine to see if it's the OS or something else?
On 14/10/15 11:00, ndousse wrote:

Hi Felix,
The first error related to intelhex is occuring on Windows 7 64bit
The second error is occuring in ubuntu 14.04 64bit.
I also tried mavue with the XBee and the standard LEQuad code and I got
the same error. I received messages (e.g. heartbeat) for 3-5 seconds max
and then the connexion is lost...
I flashed the bootloader via the JTAG interface on Atmel Studio. I
connected the board via the debug board and the 10 pin cable. I also
tried to bootload via XBee but got the same issues.
Do I have by chance to recompile pymavlink?
I use Python 2.7.6
—
Reply to this email directly or view it on GitHub
https://github.com/lis-epfl/MAVRIC_Library/issues/115#issuecomment-147982995.

FYI, on my current machine I have the following versions (from 14.04 repos):
python             2.7.5-5
python-serial   2.6.1build1
python-qt4       4.10
To see the bootloader messages, you can also try to specify the dialect
with cmd-line option:
--dialect=dbgextensions
If the file is missing it should generate it - the bootloader needs it I
think. For our project we included the dbgextensions messages into our
normal message set.
On 14/10/15 11:00, ndousse wrote:

Hi Felix,
The first error related to intelhex is occuring on Windows 7 64bit
The second error is occuring in ubuntu 14.04 64bit.
I also tried mavue with the XBee and the standard LEQuad code and I
got the same error. I received messages (e.g. heartbeat) for 3-5
seconds max and then the connexion is lost...
I flashed the bootloader via the JTAG interface on Atmel Studio. I
connected the board via the debug board and the 10 pin cable. I also
tried to bootload via XBee but got the same issues.
Do I have by chance to recompile pymavlink?
I use Python 2.7.6
—
Reply to this email directly or view it on GitHub
https://github.com/lis-epfl/MAVRIC_Library/issues/115#issuecomment-147982995.

Hi !
Thanks for sharing Felix.
Mavue works for me, but only with the baudrate at 57600:
python2 mavue.py --device /dev/ttyUSB0 --baudrate 57600 --dialect=common

Here are the versions on my machine:
python2 2.7.10
python2-pyserial 2.7.5
python2-pyqt4 4.11.4-2
I haven't tried the bootloader.

good to know, thanks for the feedback.
I've used baudrates 57600, 115200, 256000 and 512000 successfully - but
it of course also depends on the settings and capabilities of the
microcontroller. Maybe there's too much clock error at higher baudrates.
If not specified mavue uses 115200 as this is the default on all my
projects - this can be changed in mavlink_receiver.py line 29.
When you compile the bootloader it makes sense to set the UART to the
same baudrate you're going to be using in your project
(mavric/boardsupport.h, currently it is at 115200). Otherwise there will
be problems when switching between bootloader and application, as mavue
currently doesn't change baudrate at runtime.
On 10/14/2015 01:46 PM, Julien Lecoeur wrote:

Hi !
Thanks for sharing Felix.
Mavue works for me, but only with the baudrate at 57600:
|python2 mavue.py --device /dev/ttyUSB0 --baudrate 57600 --dialect=common |
Here are the versions on my machine:
python2 2.7.10
python2-pyserial 2.7.5
python2-pyqt4 4.11.4-2
I haven't tried the bootloader.
—
Reply to this email directly or view it on GitHub
https://github.com/lis-epfl/MAVRIC_Library/issues/115#issuecomment-148025974.

I close this because the compilation of avr32-gcc works, and let the discussion continue in #144


Slack Workspace

I created a Slack workspace for additional discussions and help with collaboration. Use this link to join:
https://join.slack.com/t/opensprinkler-ints/shared_invite/zt-exuhv4f5-SQbp7ACyLiSYaPXinkFG1Q

Just closing this so its not on the open list now that I have it pinned


deprecated in PyPDF2 3.0.1

With the newest release of PyPDF2 3.0.1, many of the imports and built in functions used were deprecated or modified in their usage. I rewrote the merger and splitter scripts to account for the changes, while maintaining the same functionality. I added a final step to the README file to ensure that users verify that they're using the newest version (3.0.1). Official docs/updates can be referenced here: https://pypi.org/project/PyPDF2/3.0.1/

Made additional changes to clean up the README file and fix some spelling/formatting


Handled exceptions in python files

Description
This update introduces exception handling for the concurrent execution of the FastAPI and Flask applications. The changes ensure that if either application fails to start, an error message is logged, helping to diagnose issues during startup. The motivation for this enhancement is to improve the reliability and maintainability of the application by providing clear logging of errors.
**Fixes #96
Type of change

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

How Has This Been Tested?
The following tests were conducted to verify the changes:

Both the FastAPI and Flask applications were started simultaneously using the updated script.

The applications were intentionally made to throw exceptions (e.g., by pointing to incorrect configurations) to verify that the error logging works correctly.

No other tests were run since this change pertains primarily to startup error handling.

[x] Test A: Verified that both applications start without issues under normal conditions.

[x] Test B: Confirmed that errors are logged when one of the applications fails to start.

Checklist:

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

Once check and tell me if I have to do something

Can you update me

Hi @Sai-ganesh-0004 ,
Thank you for the efforts - we will review and get back

any updates

@devansh-shah-11 any updates?

any updates @devansh-shah-11

@Sai-ganesh-0004 could you please solve this errors in tests.

=========================== short test summary info ============================
ERROR testing/test_database.py
ERROR testing/test_face_cycle.py - RecursionError: maximum recursion depth exceeded in comparison
ERROR testing/test_face_endpoints.py - RecursionError: maximum recursion depth exceeded in comparison
!!!!!!!!!!!!!!!!!!! Interrupted: 3 errors during collection !!!!!!!!!!!!!!!!!!!!
============================== 3 errors in 9.38s ===============================```

@Devasy23 upgrade this to level3, this deserves to be level3 due to extensive work that has to be done...!

@SparshKhanna0001 i understand your concern but it is already decided by mentors that it is level 2 but it all errors are solved then maybe we can give level 3.
@Sai-ganesh-0004 please complete the necessary


a11y: fix aria-label content

Description
Aria label should start from visible content. This PR fixes the occurrence pointed out in the linked bug.
Task Item

VSTS 70094

Screenshots
#minor

Coverage remained the same at 55.883% when pulling feff98746244295a53a30ec5aeac78cffeece62b on OEvgeny:a11y/profile-aria into f5b059af5047d8b7c9498adf3195339b6c0fe582 on microsoft:main.


[1.21.1] Crash on dedicated server caused by classloading of client-only class when fabric mod registers a custom fluid.

FluidHandlerCompat.initFabricFluidTypes() calls into ForgifiedFabricAPI's FluidRenderHandlerRegistry, whose implementation loads WaterRenderHandler, which has a field of type TextureAtlasSprite[]. Since TextureAtlasSprite is a client-only class, this crashes on dedicated servers. This issue was reported to me here with this stack trace.
If it's relevant, my fluid registration code can be found here.

Same here on 1.21.1
We are currently on the Modfest event, coding a simple Mod on Fabric to use on NeoForge.
Our mod, FBombs, makes use of a basic fluid. This specifically seemed to let dedicated server environments not boot anymore since its trying to access client only sided code.
FBombs (Fabric 1.21.1):
fluid class | fluid registration class
In Fabric launches and renders fluid just fine, even on dedicated server environments
Server latest log with the crash:
latest.log
Installed are:

connector-2.0.0-beta.3+1.21.1-full
fbombs-1.2.0+1.21
forgified-fabric-api-0.104.0+2.0.18+1.21.1

Also if im reading the logs right, it has the same issue with...

net/minecraft/client/gui/screens/Screen
net/minecraft/client/RecipeBookCategories
net/minecraft/client/renderer/ItemBlockRenderTypes

... where it's attempting to load those classes on the dedicated Server environment. For us, the error only appeared starting with the new implementation of the basic fluid, tho.

Fixed in 2.0.0-beta.4+1.21.1


Making the same WebRequest twice fails in the same lifetime of console app

The problem is that the code below succeeds if you run it once but fails if you run it twice during the same lifetime of a program.
var request = (HttpWebRequest)WebRequest.Create("https://google.com");
var response = (HttpWebResponse)await request.GetResponseAsync();

I have .NET Core 3.0 and SDK Version 3.0.100.
Reproduce:

dotnet new console -n test-ssl cd test-ssl.
Open Program.cs.
Replace content with:

using System;
using System.IO;
using System.Net;
using System.Threading.Tasks;

namespace test_ssl
{
    class Program
    {
        static async Task Main(string[] args)
        {
            await CallGoogle();
            await CallGoogle();
        }

        private static async Task CallGoogle()
        {
            var request = (HttpWebRequest)WebRequest.Create("https://google.com");
            var response = (HttpWebResponse)await request.GetResponseAsync();
            var jsonResponse = new StreamReader(response.GetResponseStream()).ReadToEnd();
            Console.WriteLine(jsonResponse);
        }
    }
}

dotnet run.

This will crash with the exception:
Unhandled exception. System.Net.WebException: The SSL connection could not be established, see inner exception. The handshake failed due to an unexpected packet format.
 ---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
 ---> System.IO.IOException: The handshake failed due to an unexpected packet format.
   at System.Net.Security.SslStream.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslStream.PartialFrameCallback(AsyncProtocolRequest asyncRequest)
--- End of stack trace from previous location where exception was thrown ---
   at System.Net.Security.SslStream.ThrowIfExceptional()
   at System.Net.Security.SslStream.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Net.Security.SslStream.EndProcessAuthentication(IAsyncResult result)
   at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult)
   at System.Net.Security.SslStream.<>c.<AuthenticateAsClientAsync>b__65_1(IAsyncResult iar)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean allowHttp2, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
   at System.Net.HttpWebRequest.SendRequest()
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.WebRequest.<>c.<GetResponseAsync>b__68_2(IAsyncResult iar)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
   at test_ssl.Program.CallGoogle() in C:\Users\me\source\Workspaces\tests\test-ssl\Program.cs:line 19
   at test_ssl.Program.Main(String[] args) in C:\Users\me\source\Workspaces\tests\test-ssl\Program.cs:line 13
   at test_ssl.Program.<Main>(String[] args)

Why would it fail the second time?
Created this on StackOverflow originally but noticed after more debugging that it seems to be related to .NET Core 3 since I can't repro with .NET Framework 4.8. But please read the original issue on Stack Overflow also: https://stackoverflow.com/questions/58937402/webrequest-fails-the-second-time-due-to-ssl-handshake-exception

Could this be https://github.com/dotnet/corefx/issues/41673? Very similar issue--hitting this exception on the second (and fourth) request. In that case there was a firewall in the way that was doing (bad) TLS inspection.

I would've transferred the issue to the corefx repo, but I don't think we can do that right now due to the state of the repo, so let's keep the issue here for now.
@scalablecory does this issue sound familiar to you?

I don't think it's a firewall problem for me since I was able to run:
docker run --rm -it mcr.microsoft.com/dotnet/core/sdk:3.0
dotnet new console -n test-ssl
cd test-ssl
// Replace content of Program.cs again.
dotnet run
// Everything works.

That leads me to belive it's my PC that has some strange settings since in the end the docker container has to go through the same firewall as my PC is going through.

It might have something to do with this Powershell script for configuring some TLS things, but I really don't know. It's has been run on my work PC.
https://www.hass.de/content/setup-microsoft-windows-or-iis-ssl-perfect-forward-secrecy-and-tls-12

Ok the runtime repo is in a better state. I'll transfer it there so the Networking team can take a better look.


Call for project ownership

Hello all,
It probably hasn’t gone unnoticed that this repository hasn’t seen much activity in the last 6+ months, which is due to the fact that we simply don’t have the capacity to maintain and extend it at this point.
We appreciate that the project might still be used (although we recommend people to use aws/aws-node-termination-handler instead) and thus we are looking for people that want to take over the project, both in terms of ownership (i.e. transferring the repository to a new home) and maintainership (i.e. triaging issues, reviewing pull requests, adding new features, etc).
In the case that no such event occurs we plan on archiving the repository in a week from now, on 2020-11-16 (i.e. it will still be here on GitHub but read-only).

We decided to not archive the repository so that we can leave this issue up for comments, for an undetermined period of time.


docs: clarify iOS return values of getSystemName

Description
This commit will clarify in the README that both "iOS" and "iPhone OS" are possible return values from calling getSystemName when running on an iOS device. "iOS" being reported on most iOS 10+ devices and "iPhone OS" reported on iOS 9 and less and some iOS 10 devices.
Fixed issue #410

Thank you so much @kfoxb and sorry for the delays :D


refactor: remove loading and eds-dependencies from dm-core components

Why
We want dm-core to be free of all styling and dependencies to EDS.
We want loading to be mostly handled by plugin, and for the most part, getting the uiRecipe, attribute and calling ViewCreator/EntityView is too quick for the loading state to have any effect other than "blinking"
Task

[ ] Remove loading UI in EntityView and ViewCreator
[ ] Try to remove dependencies to EDS in dm-core components

done


Minor fix in migrating guide

Thanks @gimenete even I'm still getting used to the new schema
Let me know if you have any feedback about the new 1.0 release

Thanks @G4brym
I'm migrating my project and I love the improvements. Great job! I'll let you know if I have more feedback.


Spawning machines on entry action doesn't work (4.7.0-rc5)

Description
I've been playing around with the next release of xstate and the new features are looking great. One issue I've noticed is spawning machines on an entry action doesn't seem to be working.
Expected Result
Spawning a machine in an assign action should create a machine and save it as a ref in context.
Actual Result
Xstate gives a warning about spawning new machines outside of an assign and doesn't spawn the machine.
Reproduction
https://codesandbox.io/s/hopeful-franklin-8z0t6
Additional context
Create with 4.7.0-rc5

@allforabit I've noticed this issue but I think it's slightly different from what you've described.
Spawning a machine does seem to work properly, I think what you're seeing is some react-specific issues relating to the ref prop on a function component. If you change the prop name to anything else (ex. machineRef) things work properly - however the warning remains.
Here's your codesandbox updated to use machineRef instead of ref as a prop - https://codesandbox.io/s/wandering-dust-7i6tx
So from what I'm seeing it seems like the warning shouldn't be there at all - the Todo works properly and can send messages to the parent.

@allforabit thanks for the repro case for the unnecessary warning being logged to the console. I've prepared a fix for this https://github.com/davidkpiano/xstate/pull/758


[TASK] Update base image version to 15.6 for v1.6.4

What's the task? Please describe

Describe the sub-tasks

Update the base image version of Longhorn components to 15.6, if they are not already using this version.

Additional context

https://github.com/longhorn/longhorn/issues/9898#issuecomment-2561670008

Test result (coretest): https://ci.longhorn.io/job/private/job/longhorn-tests-regression/7980/

All PRs merged. This issue only updated the base image version with no changes to code logic. Any potential failures should surface during regression testing, so no additional QA effort is required. Closing the issue.
cc @longhorn/qa


Javascript version of the Library

I am opening this issue to see if anyone is interested in contributing.
As XGBoost have minimum dependecy, it is possible to use amalgamation and emscripten to build a javascript version of the library. See https://github.com/dmlc/mxnet.js as an example for our deep learning project.
This could be fun for some usecases, to run XGBoost on the browser and provide some cool demos

@tqchen I can try to participate in it

sounds good, @Jabher Let me know if you need any help on this, mxnet.js could be a good starting point

Cool, thanks!

@tqchen I personally think that implementing predict is more important than implementing train in this case.  I can only think of toy examples where a train javascript function would be helpful, such as web ML demos.  However, there are a lot of cases where computing xgboost predictions clientside on a pre-built xgboost model would be very practical for a variety of applications.  I've had to do this for clients before using other ML models.  A typical workflow might be:

train locally on a research machine using an existing xgboost API (Scala, R, python..).
export tree as json object with xgb.dump.
read in json model into javascript environment and generate predictions.

The advantage of just implementing the predict functionality is that it can be done with VinallaJS.  I could also develop the predict functionality quite quickly, whereas a complete javascript API for XGBoost would be a larger-scale undertaking.  What do you think?  Happy to contribute a PR for this.

@AndrewHannigan FYI there is a project to build compiler of boosting model (transform the model in if else instructions in C++ then compile it). It will be released soon. What you are speaking may be part of this project.
More info here : https://github.com/dmlc/xgboost/issues/2551

@pommedeterresautee sounds very intriguing, but why take C++ source code as input for the compiler?  Wouldn't JSON be easier to parse, more portable, widely supported by other languages, etc.?  Seems to me the forest should be represented as data, not code.

performance !!

Oh I see, so this just going to produce a binary executable.  Sounds cool!  There might be pieces of the pipeline before the ifelse generation step that would overlap with this project.

@hcho3 may give you more info.
The parsing of the model and the internal representation may be useful for both projects, plus tree-lite manages also models from lightgbm...

@AndrewHannigan treelite is currently in public beta. I am adding more documentation before an official release. The idea here is to produce a binary executable for optimized prediction. Right now, treelite produces C program internally to be fed into a C compiler (e.g. gcc), but we can certainly produce a JS program instead.

Has there been any progress on this?

Hello @tqchen,
I have a version on JS working (using WebAssembly) so it's able to run on the browser, also I'm able to load models saved on other programming languages (using th e C API)
mljs/xgboost
tell me if you are interested to include it here.

nice, if you are interested in porting back the js binding, we can put it under xgboost/web
We cannot host the emscriptened js file directly in the repo(as it can be big), but we can host the build flow and put emcc generated file in a separate repo.

cc @hcho3

For most of the C++ change, we can use EMSCRIPTEN to detect if the current project is compiled with emcc

@tqchen I'd suppose we need to update both Makefile and CMakeLists.txt to accommodate the JS build?


Crashes

When I try to add RTSP source to graphedt.exe then it crashes. I tried to create instance of source through Activator in Visual Studio and it crashes with stack overflow exception. My goal is to use RTSP source with a custom source filter.

I tried to add all files from output folder to same folder with graphedt.exe but still no luck.

@gpeipman did you see the final comment in #1 ?
Also  how are  you loading the filter in GraphEdit? It's been a while but I believe I used the Render URL option from the File menu in graphedit when testing.
Unfortunately, I stopped working on this filter a long time ago and switched to a 3rd party commercial filter that is much more feature rich. I can't even build this project right now due to my environment being setup for some other work.
Let me know if you want a pointer to the 3rd party filter_ it's pretty good and includes enough hooks so you could probably use it with your custom filter.

When opening from menu then URL is opened by some LAV filter instead. What 3rd party you are using currently?

I've been using the DataStead Filter. http://www.datastead.com/products/rtsprtmpsrc.html


Create abstraction layer for blockchain index

Description
Create abstraction layer for blockchain index based on the experimental PouchDB implementation.
Consider the following backends that might be used in the future:

Redis
RediSearch
PostgreSQL
SQlite
MongoDB

Motivation

Need to know the technical limitations of storing blockchain data index

Acceptance Criteria

Comments in the issue with results
Draft implementation for Redis

Reason to not proceed with Redis secondary index:

Secondary index uses a score to create index. Refer ZADD method.

We intended to directly use the prospective indexed attributes as the score. Hence, indexing non-numeric data such as address, publicKey, username, ip etc. though feasible is a cumbersome process. It would introduce unnecessary computational overhead for (de-)encoding.


Links with relative path towards other .md files open github instead of the page itself

What happened:
Links with relative path towards other .md files open github instead of the page itself
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):

https://gardener.cloud/docs/concepts/core-components/api-server/ page, towards the end has 'Please see this separate documentation file.'  The link is defined as '../usage/openidconnect-presets.md' and resolved as https://github.com/gardener/gardener/blob/master/docs/usage/openidconnect-presets.md which is not correct
https://gardener.cloud/docs/guides/applications/access_pod_from_local/ page has a link 'Access my service' defined as '../service-access/', resolved to https://github.com/gardener/documentation/tree/master/website/documentation/guides/applications/service-access
https://gardener.cloud/blog/2021-01/00/machine-controller-manager/ -> all links to other pages within the site are broken
...

Anything else we need to know:
How to categorize this issue?

/kind bug
/priority critical

As discussed, for the 1st example the link is not resolved correctly, because the targeted page is not part of the site (it's not part of the manifest), so the page is treated as external. The solution will be to include openidconnect-presets.md in the manifest

For the other examples - Docforge would parse the url correctly if the url was pointing to a concrete .md file.
We shall add support for urls which end in / (thus pointing logically to the _index.md file in the directory)


Reduce build time

After adding X-Chair, we saw our build times go from 5-7 to 22 minutes or altogether fail. I believe this has to do with gatsby-source-filesystem to compile chair images instead of using our CMS. I found a few issues coming to this conclusion but nothing conclusive or exact. This PR is testing that theory by moving all color/fabric media to our cms.

PR builds in 6:25 minutes 🎉


[1082] eo slow

Resolves #1082 by simply removing the offending view

closing and restarting in a new branch due to too many merge conflicts


Duplicated issues in tree

Using the extension at version v0.63.2023042709
I'm using the following settings:
	"githubIssues.queries": [
		{
			"label": "April 2023",
			"query": "assignee:${user} state:open milestone:\"April 2023\""
		},
		{
			"label": "My Issues",
			"query": "default"
		},
		{
			"label": "Created Issues",
			"query": "author:${user} state:open repo:${owner}/${repository} sort:updated-desc"
		}
	],

In the tree, I am seeing that the issues are shown twice:

Version: 1.78.0-insider
Commit: d6290ef6582acecbf3bca1558111f2ee64375801
Date: 2023-04-27T05:38:42.326Z
Electron: 22.4.8
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.4.0
Sandboxed: No

Can you share the output of git remote -v for the folder you had open?


[WIP] move deletes calculation into save_inventory_multi

all the code that determines the deletes (and refreshes) is copied across a number of entries.

This is a great refactoring...makes it a lot clearer.

There are changes based upon the nil check stuff we did.
Wanted to rebase this - to see what is left for us to possible tease out of here and incorporate into the main branch.

most of the useful changes from this PR have been pulled out.
I introduced save_inventory_assoc to handle most of these cases anyway.


Text field error message example

add the assisted text message "Error message" when the "error state is selected"

ok for this update, but there is a vocalisation to add  #359


Java - Waitskill added

Motivation and Context

Description

Based on the wait_skill.py
I implemented the WaitSkill by using Mono of Project Reactor.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[ ] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Does this test block for the full time? Can we use https://projectreactor.io/docs/core/release/reference/#_manipulating_time to avoid long running tests?


question: What's the purpose of useLifecycleObserver option?

Basically title, the default value is false, when would/should I set it to true? I want to track application lifecycle events so I'm setting trackApplicationLifecycleEvents to true but I don't know what's the significance of useLifecycleObserver. The documentation just says enables the use of LifecycleObserver to track Application lifecycle events but it doesn't explain what I should consider when enabling this flag

Hi, thanks but that doesn't really answer my question - what would be my use case for using one or the other? As a library consumer I still don't know if I should change the default or not. If both options work the same, why have it configurable in the first place?

if you already use lifecycle observer in your app, you can set useLifecycleObserver = true, but you don't have to. this flag is designed for the apps that did not implement lifecycle observer.


Hint boxes improvements

Made the hint boxes more intuitive via modifying the default syntax, with 6 available boxes.

Went through the wiki to assign an appropriate boxes to the current ones.

Two general observations I want to mention, but these are not showstoppers:

When the boxes contain footnotes, these footnotes are rendered within the box. I guess that is the way the template works? Just seems to unnecessarily bloat the box. See e.g. the SameSite Cookies page
The "Important" box is in yellow (red being occupied by warning). I think this draws less attention than it maybe should? An option could be to use a lighter shade of red for "Important"?

Thanks for suggestions @goedi02.

When the boxes contain footnotes, these footnotes are rendered within the box. I guess that is the way the template works? Just seems to unnecessarily bloat the box. See e.g. the SameSite Cookies page

I was fighting with it a few days ago, and because hints are rendered in different context, hint boxes do not work. Maybe in the future we can try to integrate it to the main document but for now there seem to be no easy way to do it.

The "Important" box is in yellow (red being occupied by warning). I think this draws less attention than it maybe should? An option could be to use a lighter shade of red for "Important"?

I changed the color palette again:

Let me know if shades are better now.

I was fighting with it a few days ago, and because hints are rendered in different context, footnotes do not work. Maybe in the future we can try to integrate it to the main document but for now there seem to be no easy way to do it.

Thanks for the background info. Agree, let's leave as-is, no need to invest extra time into this now.

The "Important" box is in yellow (red being occupied by warning). I think this draws less attention than it maybe should? An option could be to use a lighter shade of red for "Important"?

I changed the color palette again:

The new colors looks great! Just to clarify my preceding comment: I think it would be preferable to use red for both "Important" and "Warning". "Warning" could use a darker shade of red to make it easy to distinguish it from "Important". This is probably the only color convention in doc, that red is used for stuff you really should not miss ;-). If this is an easy fix, it could be worth doing, otherwise feel free to ignore.


Fix selection moving bug

Fixes https://github.com/BitPhinix/slate-yjs/issues/226
When applying remote yjs events to a Slate document, slate-yjs uses the Transforms slate module with calls like Transforms.insertText, Transforms.setNodes, etc. These methods update the local user's selection state after doing the transformation. This is not what we want when applying remote operations; the transformations should not affect the local user's selection state.
This PR ignores "set_selection" operations while Yjs events are being applied to a Slate editor. As seen in the video linked in the comments below, this will preserve the intended selection location of the local user, even as changes happen on the same line or other lines from a remote user.

I'm not sure that not changing the selection is what everyone would expect. Given the following scenario, where user 1 is remote and user 2 is us:
A(selection of user 1)BC(selection of user 2)
If user 1 adds the character D, for example, i would expect the following result:
AD(selection of user 1)BC(selection of user 2)
IOW, the selection of user 2 was moved a character forward. That being said, when we used slate-collaborative (automerge) we did so without using Transforms, so not sure if something can go wrong by changing the selection or is it a preference?

Hi @nemanja-tosic , I've updated this PR's approach so I need to update my description above. It works exactly as you expect, see this video:
https://user-images.githubusercontent.com/5554373/119815720-d6fc0580-beb9-11eb-8413-4a6ddb78fee0.mov
The new approach is that while applying the remote Yjs operations, we disable all "set_selection" operations. This prevents the local user's selection being affected by the selection changes that are part of slate's Transforms calls. However, the underlying local user's selection will still remain in their intended location, as you can see in the attached video.

For reference, here is the buggy behavior we see with the existing slate-yjs lib. Deleting a character on another line moves the remote user's cursor to that line:
https://user-images.githubusercontent.com/5554373/119816676-fd6e7080-beba-11eb-8a3e-e1bede9fc4fe.mov
And here is the same scenario with this PR applied. Deleting a character on another line has no effect on the remote user's cursor:
https://user-images.githubusercontent.com/5554373/119816767-19721200-bebb-11eb-83c2-2f04e84cbb6b.mov

Hi there,
thanks so much for this PR 🙏 . While ignoring set selection commands is definitely the cleaner approach of the 2 mentioned above I think directly targeting the insert text operation might be the better way to go here to avoid potential unwanted side-effects. Something like creating a range ref for the selection with a backward affinity before inserting text and then selecting it afterward.
I haven't tested this yet though but I think it should work.

@skokenes thanks for the video, i was not seeing the behavior as i had the wrong setup.

Well, if it helps anyone, in the end we overrode editor.apply with something like:
const { apply } = editor;

apply: op => {
  // fixes: https://github.com/BitPhinix/slate-yjs/pull/234
  if (YjsEditor.isRemote(editor) && op.type === 'set_selection') {
    return;
  }

  apply(op);
}

If it's a good enough fix for the package as well i can whip up a PR.
So if a set_selection does come in during asRemote, it gets ignored.

I'm not sure that creating range refs and reapplying is a good idea as there may be issues with reapplication of a selection after a doc's structure changes. Or it might conflict with another selection change a user makes simultaneously by clicking somewhere in the editor.
I think the most bulletproof solution is to somehow rip the select transformations out of the calls you are using like Transforms.insertText so that any other select ops generated by slate work fine, but I am not sure how to go about doing that without duplicating the existing implementation of Transforms.insertText, which would then lose future updates to that module.
Any thoughts?

It's stopping the operation from going into slate, it's not re-application but rather filtering what we apply. Or am i missing something?

@nemanja-tosic I was talking about @BitPhinix 's suggested alternative. If you look at my PR its more or less doing exactly what your solution already does.
BUT, with the solution that you/I have suggested with overriding editor.apply, I have already seen issues with multiplayer cursors where one user's selection responds funkily to changes while another user is making changes. Still working on reproducing it, will report back when I have steps

Yes, it does, this is just higher up so it was easier to patch from the outside.

This is the part of the Transforms.insertText that is causing the original bug I believe: https://github.com/ianstormtaylor/slate/blob/main/packages/slate/src/transforms/text.ts#L479
And of course other Transform calls probably have this problem as well, such as insertNodes

@BitPhinix Is there a reason to use Transforms.insertText as opposed to just generating a text input operation like so?
editor.apply({ type: 'insert_text', path, offset, text })
Seems like Transforms.insertText has a lot of extra code mostly related to getting the location to insert from a user's selection, which we don't need...

I'm not sure that creating range refs and reapplying is a good idea as there may be issues with reapplication of a selection after a doc's structure changes. Or it might conflict with another selection change a user makes simultaneously by clicking somewhere in the editor.

That's the "beauty" of js, the user actually can't make a selection while this is happening since the thread is busy running the handler, but blocking set selection calls works as well. Just blindly re-applying without refs (like in the first comment) however will lead to editor crashes if e.g. the text node that has previously selected got deleted. Both of these approaches could however potentially cause conflicts with other plugins.
Another solution would be to translate the yjs changes directly into editor operations (like in the first version) and just apply them directly to the editor. That however would require a bigger rewrite of the entire yjs change apply side but would fix https://github.com/BitPhinix/slate-yjs/issues/202

@BitPhinix Is there a reason to use Transforms.insertText as opposed to just generating a text input operation like so?
editor.apply({ type: 'insert_text', path, offset, text })
Seems like Transforms.insertText has a lot of extra code mostly related to getting the location to insert from a user's selection, which we don't need...

The 1.0 of slate-yjs actually did it this way, but you can't get all the information to generate undoable slate operations from the yjs events. You could however also consult the current editor state to get all the info you need for complete operations. I've simply used Transforms in 2.0 since they were more convenient, but I'm open to changing it back.

BUT, with the solution that you/I have suggested with overriding editor.apply, I have already seen issues with multiplayer cursors where one user's selection responds funkily to changes while another user is making changes. Still working on reproducing it, will report back when I have steps

I rechecked this and this issue exists even without any changes to slate-yjs, so it looks like a separate item. I will open an issue on it.
I am using @nemanja-tosic 's solution for now for overriding apply during remote ops to ignore selections

I've created a PR with the event to slate op conversion approach. https://github.com/BitPhinix/slate-yjs/pull/238 which should fix this issue.
Could you please test it with your editor implementations and see if it fixes the issue for you and/or causes any other unwanted side effects?


Reduce padding on body text/headings?

I think that we should try to improve the look and readability of our docs-site pages. Looking at some other modern documentation examples, they seem to have significantly less spacing around the body of text and it feels easier to read IMO. In general, try to reduce padding on sides/top/bottom of headings/paragraphs.
Any other opinions on this?

Our current doc - https://zowe.github.io/docs-site/latest/user-guide/cli-usingcli.html#display-zowe-cli-help
Microsoft doc - https://docs.microsoft.com/en-us/outlook/add-ins/addin-tutorial
Amazon doc - https://docs.aws.amazon.com/opsworks/latest/userguide/opscm-maintenance.html
Vuepress doc - https://vuepress.vuejs.org/guide/#how-it-works

+1 with Brandon's @BrandonJenkins14 proposal about reducing padding to improve readability. When you look at release notes, this problem is more obvious: https://zowe.github.io/docs-site/latest/getting-started/summaryofchanges.html#version-0-9-4-november-2018.
@jackjia-ibm Hi Jack, we need your technical support here. This is a UI issue which I think we might need to adjust the page CSS file (if there is one) to reduce the padding around h1, h2, h3 and h4 headers. Can you help take a look? Thanks!

@nannanli, will check and create a PR for this improvement.

@BrandonJenkins14 I agree we should keep all 3 changes. Thanks Jack for the quick and great work!

Thanks!
@BrandonJenkins14 I can think of 2 ways to fix the nav elements. One is reducing the links to maybe 4-5, or change some text links to image, like Amazon docs.
Another way is adding an intermediate hiding logic to hide the unimportant links, like Microsoft docs will hide "Programs" dropdown with certain browser width.
Which way do you think is better?

I think using logo thumbnails is a very good option for the Github and Zowe.org links.
I'd suggest hiding the "Contributing" tab very early in the width reduction too.
Alternatively, we could offer links to GitHub, Slack, Zowe.org, and anything else in a pager footer, see the bottom of this angular.io doc for an example - https://angular.io/      But it's nice to have them at the top right if possible.

If we go with thumbnails, the thumbnails should have alt text....

I made 2 changes:

converted zowe.org and github links to icons,
"Contributing" link will be hide earlier than others.

Please see if this looks ok, or I can revert back. We now changed from 1090px browser with to 860px to fully hide the nav links.

This should have been fixed by https://github.com/zowe/docs-site/pull/284 and https://github.com/zowe/docs-site/pull/293.


SFTP: can't edit a file with a French letter inside

Describe the bug
SFTP : we can't edit a PHP file which contains French letters. For example, if there is an "é" in the HTML code, when you click on "edit file", a blank page appears.
Informations

Device : Iphone SE
OS : 14.6
WebSSH Pro version : 14.18.1

Screenshots
To Reproduce
Steps to reproduce the behavior:

Go to SFTP
log in to a server
edit a PHP file with an "é" in the code for example (any French letters) - ending in .php (maybe in other types)
a blank page appears, no content, no icon to save, can't edit the file

It's not related with diacritics :

I'm searching the root cause...

Related to file encoding and BOM.
I'm fixing it.

Hello @vc02  👋
I have fixed it : please install WebSSH Beta from TestFlight app : https://testflight.apple.com/join/QSrBK59z
☀ Have a nice day

Super ! Merciiii 👍

Avec plaisir 😉


[backport] add cupyx.scipy.sparse.diags

Backport of #1840

[automatic post] Jenkins, test this please.

Jenkins, test this please.

Jenkins CI test (for commit 3f426c26dd6532b948f1d8e66279b183a900bb9f, target branch v5) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

LGTM!


Terminal will auto repeat my last input

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Microsoft Windows [Version 10.0.18363.535]
Windows Terminal version (if applicable):
Version: 0.7.3451.0

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

when I input something within the terminal, no matter it is command line or coding with VIM editor in WSL, it will all occur this problem.
For example, I want to key down "cat -n 10 myfilename" in the wsl command line, sometimes when I finished key down the letter "n", I want to continue to write "a", but at this time, The terminal will auto repeating the letter "n" for many many times. I was not able to do anything unless just press the X button to close that window.
I have recorded a video to show this problem

But this will not occur in the system's cmd which opens with "win+r" then write down "cmd" or PowerShell and so on. Only occur in terminal

The system version which I use is:

I cannot search for anything with this problem. Appreciate to get some help

This seems like #3706, but your example indicates that it happens for normal input?

This seems like #3706, but your example indicates that it happens for normal input?

Yes, absolutely normal. I see that issue #3706 was caused by the Chinese character. Or it may occur by the Chinese input software? I am using the Microsoft Wubi from the system. But this problem occurred when I was in English input status.

I started seeing this to on the latest nightlies.
See screenshot. This appears to be a display issue as the commands execute successfully.

I'm experiencing the same as @onovotny
Building from current master (d711d731d7d00259b2e0fe5847928c9f1c1121ed) results in this behaviour.
I reverted to 4daf1d7f9c36eb2129c277e89255d44670db0537 (just because it was the last usable version I built) and don't have this, so the issue may be within that commit range.

Yeah, this is #4107 (PR #4113)

@xjr7670 Are there any other interesting things about your machine that might help us figure this one out? Nobody here's got any idea.
Just FYI - #4107 is a new regression after 0.7, so it is not the cause of this issue.

@xjr7670 Are there any other interesting things about your machine that might help us figure this one out? Nobody here's got any idea.
Just FYI - #4107 is a new regression after 0.7, so it is not the cause of this issue.

In addition to the input software, there is a software called DLP. Which is used to monitoring every computer's internet I/O traffic inside our company to prevent information leakage.
After installed DLP, it will auto output some error info to the shell window, especially within the powershell

I can offer something about DLP if you need it. For example the log file or something else.

We have made some changes to the input stack recently. Is this still happening?

It has not reappeared recently, it should have been repaired

Thank you!


Feature request - add properties of link in table.

Say I have a schema as following:
type Bom{
title: str;
components: Component {relationship:str;};
...
}
type Component {
some properties ...
}
But I don't find @relationship anywhere, neither Bom UI nor Component UI. I think these properties should be show in the table of Component as @relationship;

Duplicates #11


Problem running "create.user.sh" on master

The script "create.user.sh" won't run on master. After tagging RC2, I was able to run it successfully.

Hello @BrenoFortunato, sorry for the huge delay on replying your issue.
As of now (as tracked by dojot-nightly/docker-compose@ and the current tip of dojot/docker-compose on master, a user is no longer required to run either create.user.sh or kong.config.sh to perform the initial system configuration bootstrapping.
Unfortunately, I also see that documentation is not up to date in that regard.
That said, I'll change this issue to track that documentation update, ok?

Documentation was updated to omit deprecated steps.


Export R_PROFILE during the configure step, rather than export

export is run after configure, and R_PROFILE needs to be set for
setup_bioc.
It looks to me like the export stage is always run after configure, which is why the repos were not being set https://github.com/travis-ci/travis-build/blob/4f580b238530108cdd08719c326cd571d4e7b99f/lib/travis/build/stages.rb#L15-L19
An example error this should fix is https://travis-ci.org/ropenscilabs/available/jobs/452418452#L913-L916
cc @LiNk-NY

Thanks @BanzaiMan ! :tada:


If loop = true is set then events such as onSlideChangeStart and onTransitionEnd etc are fired automatically on page load

Hi!
If loop = true is set, then events such as onSlideChangeStart and onTransitionEnd etc are fired after the page loads without any user interaction. If I set loop = false then these events don't fire.
Is this a correct/normal behavior?
I would prefer them not to fire btw.
Thank you.

You can disable runCallbacksOnInit parameter to disable it

Can't believe I missed that in the API docs, thank you so much for your help Vladimir. Swiper is great :)

I have configured runCallbacksOnInit: false but loop: true and events fire anyway 👎


looking for networking doc

System Information
HP Bare Metal Server
Linux distribution
NAME=Fedora
VERSION="29 (Server Edition)"
Terraform version
Terraform v0.12.26

provider.libvirt (unversioned)
provider.template v2.1.2

Description of Issue/Question
I would like to give some kvm guests direct network access.
manual configuration of a vm guest works and creates the following (eno1 is main interface):
<interface type='direct'>
<mac address='52:54:00:f0:8a:3a'/>
<source dev='eno1' mode='bridge'/>
<target dev='macvtap1'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</interface>

65536: macvtap1@eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 500
    link/ether 52:54:00:f0:8a:3a brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5054:ff:fef0:8a3a/64 scope link

Setup
Installed docker and libvirt on the Host
virbr0 network is internal kvm network
virbr1 network created using terraform for guest only communication
brctl show
bridge name     bridge id               STP enabled     interfaces
br-5d6f55713f15         8000.0242c54f5707       no              vethdd6e16a
                                                        vethe25819d
                                                        vethf860f75
docker0         8000.02420d129272       no              veth425a6a9
virbr0          8000.525400bb5f23       yes             virbr0-nic
                                                        vnet1
virbr1          8000.525400821abe       yes             virbr1-nic
                                                        vnet0
                                                        vnet2
                                                        vnet3
                                                        vnet4
                                                        vnet5
                                                        vnet6
                                                        vnet7
                                                        vnet8

Question: how can I create a network config using terraform that uses direct host access (without creating a bridge on the host)?

Additional information:
selinux and firewall disabled

https://github.com/dmacvicar/terraform-provider-libvirt/blob/master/website/docs/r/network.markdown

Hi,
thx for the link - I already found that page, but as I understand this requires the configuration of a bridge on the host system, then linking the bridge to the vm using the bridge name: "The bridge network attribute is mandatory in this case"
yes, an example would be great!

hi  @MalloZup!
any chance to get some docs for this?
thx and br

Hi @muj85
some upstream libvirt documentation: https://wiki.libvirt.org/VirtualNetworking.html
What exactly do you mean by 'direct host access'?

Hi @scabala,
I solved it using bridge setup with script during kvm host boot process, later moved to systemd network config, works for me.
thank you!


pivccu on raspberry pi 1?

Hello,
Is there a concrete reason why RPI 1 is not supported?
Thank you very much in advance!

The CCU firmware is compiled for ARMv7 while RPI 1 is ARMv6.

Thank you!
Sad story :(


Description link goes to an image

The repo description links to https://www.visualstudio.com/features/azure-tools-vs, which redirects to https://www.visualstudio.com/wp-content/uploads/2016/06/azure.png.
It doesn't make any sense so I assume there was a copy/paste error somewhere.

this has been fixed.

You're welcome.


fix: changes Catalog Source API version to v1alpha1

Signed-off-by: Jennifer Power<EMAIL_ADDRESS>Description
This PR fixes the API version on the generated Catalog Sources when processing operator catalogs.
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?

[X] Manual testing

Checklist:

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

/lgtm


Support SSL connection in LDAP integration

What happened?
Reported on Discord: ldap:// part is hardcoded
Reposilite version
3.x
Relevant log output
No response

I reported the issue.
https://github.com/dzikoysk/reposilite/blob/d286125abc9aac7fa7a21ca419767d84454cae80/reposilite-backend/src/main/kotlin/com/reposilite/auth/LdapAuthenticator.kt#L104 - There is the Hardcoded ldap://-String. It should be either not a fixed prefix at all, or a switch between ldap or ldaps.
I will provide documentation on how to inject a certificate for usage with ldaps (or other internal connections) for the documentation.


Recognize comments by default.

Fixes #3385
PR against #3432

Ok cool, it's works for me.
/cc @robbyrussell

Can you quickly rebase this for me?

@robbyrussell Done.

:+1:
@robbyrussell please pull in this easy merge.

@robbyrussell please merge this. I accidentally ran into this error today when I pasted some snippet with comment and zsh threw an error at me. Was expecting this to be already merged.

This will be merged in #3809.


THE screen is always black when running on the MIPS 64EL

How can I solve this problem? Do I need to modify the SKIA source code and recompile it

Provide more info about your environment.

Linux distro?
X11, XWayland, fbdev, libdrm?
With or without GPU acceleration

development environment
1.The Linux distribution  is Ubuntu
2.display library is X11
3.machine has GPU acceleration

This is what the interface looks like after the project is run

@Aaronlog Verbose logs can be useful
   .LogToTrace(LogEventLevel.Verbose)

Try adding
.With(new X11PlatformOptions
{
    UseGpu = false
});

to your app builder.

@kekekeks When useGPU is set to false, the entire window is not visible, but the taskbar is

@maxkatz6 After adding this LogToTrace(logeventlevel.verbose) attribute, I did not see the related log file in the whole project directory. Could you please tell me how to use this log in detail? Thank you very much

@Aaronlog Trace logging writes messages to the Trace output.
If you need file logging, you need to implement your Sink with ILogSink and set you instance to Logger.Sink.

@maxkatz6 Hello, logging has been added, but after the project has run, there are no error messages in the log file.It is still not known what caused the Windows to appear black.By the way, do you have a MIPS running environment?

@Aaronlog I don't have anything suitable for development.

I don't think SkiaSharp has a MIPS build

@maxkatz6
The problem of black screen has been solved. The previous version of SkiaSharp is 1.68.0, but now we want to release it with the version of Avalonia0.10. SkiaSharp 2.80.2 has been compiled, but I don't know how to compile libharfbuzzsharp

That's the same as the libSkiaSharp bits. Just modify the build script. Both native parts work with gn.


[Translate] Translate the documentation - Configuration

Translate the configuration part.
Repo: https://github.com/hiproxy/documentation
Branch: master
Directory: https://github.com/hiproxy/documentation/tree/master/source/configuration

jamesfancy is translating this part.
:-)

Finished. Thanks jamesfancy


Origin of vfile message when using remark plugin

I'm using a custom remarkPlugin that adds some message to a vfile under certain condition (broken link) :
const mdxFile = (route: string) => {
  // returns true or false depending on whether route is valid or not
  ...
}

const attacher = () => {
  return transformer

  function transformer(tree, file) {
    visit(tree, { type: "link" }, (node: Node) => {
      const lnode = node as LinkNode
      const route: string = lnode.url
      if (!/^http/.test(route) && !mdxFile(route)) {
        file.message(`${route} is not a valid link`)
        const title = lnode.title || ""
        lnode.title = `[BROKEN LINK]${title}`
      }
    })
  }
}

I'm later on using it like so :
const rawContent = fs.readFileSync(filePath).toString()
  const { code, frontmatter } = await bundleMDX(rawContent, {
    xdmOptions(options) {
      options.remarkPlugins = [...(options.remarkPlugins ?? []), brokenLinks]
      return options
    },
  })

It's kinda working but the output is not as helpful as I'd like as I'm loosing track of the original filePath  :
> __mdx_bundler_fake_dir__/_mdx_bundler_entry_point.mdx:0:0: warning: [plugin: esbuild-xdm] /fr/recherche/equipes/sen/collisions-d-ions-lourds-et-equation-d-etat-de-la-matiere-nucleaire-2 is not a valid link
    0 │ ---
      ╵ ^

Is there a way to get the part before the warning (__mdx_bundler_fake_dir__/_mdx_bundler_entry_point.mdx:0:0 be the filePath ?
Using the cwd bundleMDX param I was able to change the __mdx_bundler_fake_dir__ part, but have no clue on how to deal with the other part (_mdx_bundler_entry_point.mdx:0:0).
Sorry if that's obvious.

mdx-bundler version: 4.0.0
node version: 14.15.3
npm version: 6.14.9

_mdx_bundler_entry_point.mdx is the fake file we create in memory to hold the mdx source passed as the first option to bundleMDX.
You could replace the entry point in esbuild with the file on disk and it should give you the real path in errors.
const { code, frontmatter } = await bundleMDX('', {
  esbuildOptions(options) {
    options.entryPoints = [filePath]
    return options
  },
  xdmOptions(options) {
    options.remarkPlugins = [...(options.remarkPlugins ?? []), brokenLinks]
    return options
  },
})

This would then ignore the now empty in memory entry point and read your file straight from disk. Added bonus, you wont have to read the file contents in yourself either as esbuild will do it for you.

@aphecetche 4.1.0 has tests for this now and supports replacing the entry point properly now.

@Arcath thanks a lot. Have been diverted from this for a while, will test as soon as I can.

Actually works perfectly. Thanks !