text:
Next generation XML

In the current XML approach there are some issues see #176 #175, plus field names are not correct, would also like to provide just one method for adding data to an XML file.
Issues with current implementation:

Top level names are not always correct
Not possible to handle namespaces
Multiple methods

Suggested approach
See https://github.com/larshp/abapGit-NextGen-XML
2 classes, lcl_xml_input and lcl_xml_output, which both provide just a few methods to the serializers.
Breaking everything
With commit https://github.com/larshp/abapGit/commit/93c8a7a0aebe8c72199e55c1696c6508743f3ade an error message will be shown if the XML version does not match the implementation. The user will be directed to https://github.com/larshp/abapGit/wiki/XML-Mismatch which will describe how to handle the situation.

An unforeseen improvement: values are externally formatted in the XML, eg timestamp is 22:10:10 instead of 221010 in the old approach

There should be some more externally formatted data types. If I recall correctly, language is also transformed into ISO-format.

Okay, everything seems to be working now, see branch
https://github.com/larshp/abapGit/tree/next-gen-xml
a corresponding branch
https://github.com/larshp/abapGit-Unit-Test/tree/next-gen-xml
can be used for unit testing, and checking out the new format
I think the serializer origin and serializer version should be implemented before merging to master. No PRs or changes to master until this branch has been merged please.
Format
discussed in https://github.com/larshp/abapGit/issues/187
though I dont like my previous suggestion to misuse the MINOR version for serializer versions, I think adding another version attribute is better, eg. something like
<abapGit version="v1.0.0" serializer="ZCL_SOMETHING_SERIALIZER" serializer_version="v1.0.0">
Providing version
Add a method GET_VERSION in LIF_OBJECT which returns a string as version. Formatted as semver.org versions, default everything in zabapgit will start with "v1.0.0"
Accessing/adding/checking attributes in XML files
I'm not sure how this can be handled the best way, will update this thread with ideas

Scribblings
in LIF_OBJECT, add method GET_METADATA
return structure with 2 string fields, serializer class name and serializer version
in lcl_objects_files add reference to lif_object as constructor parameter
method add_xml pass the needed information to the xml render method
method read_xml can similariy pass the information to check version
in LIF_OBJECT method DESERIALIZE
new mandatory importing parameter lcl_xml_input
this will allow for parsing the xml and checking the serializer version before it is passed to the serializer, in LCL_OBJECTS plus a lot of "lo_xml = mo_files->read_xml( )." can be omitted in the serializers
change method SERIALIZE to return a XML object? to make serialize and deserialize symmetric

and thats about it
note that it is possible to have both the old and new abapgit installed in a single system, eg ZABAPGIT and ZABAPGIT_OLD
still todo:

[ ] more testing
[ ] fix plugin bridge, I'm pretty sure I broke some of it but havent tested yet

before pushing to master:

[ ] create git tag, so it is easy to fetch the old abapgit

looks nice, though I still don't like the create object lcl_xml...
I can take care of the plugins.

create object lcl_xml..: which part, can you point to code line? perhaps we can do something else

I just don't like to have each implementation instantiate it (from an architectural perspective).
E. g. unit testing would be easier if an instance of a factory for xml containers was injected into the serialize/deserialize

yes, something like:
https://github.com/larshp/abapGit/commit/bfca54b92bb9e6511b649bd9a9dee17a93aadd42
https://github.com/larshp/abapGit/commit/c77150739c510235c4acbfe551c5597dbeca3e0e
the xml object was added to both serialize and deserialize, so the interface is now:
``
INTERFACE lif_object.
METHODS:
serialize
IMPORTING io_xml TYPE REF TO lcl_xml_output
RAISING   lcx_exception,
deserialize
IMPORTING iv_package TYPE devclass
io_xml     TYPE REF TO lcl_xml_input
RAISING   lcx_exception,
``

yup, looks nicer. Sorry, had a look at it earlier.
Though this assumes that there will be exactly one xml-file per plugin. But I guess that this is fair enough.
A bit tricky to encapsulate this nicely for the plugins though without having a typed interface though...

plugins: creating global classes for input and output, eg. ZCL_ABAPGIT_XML_INPUT will most likely work, but it is hard work
the old approach still works for adding multiple XML files, currently only FUGR adds multiple XML files, but I plan changing this so there is only one(task "FUGR serializer cleanup" in above checklist)

anyway, multiple XMLs can easily be merged into one DOM tree, thus I said the assumption was fair
Give me some days to wrap that properly.

DOM tree: yes, I agree

I've fixed all the stuff on my todo list for next gen XML.
@mrsimpson is the plugins working okay? Anything else you'd like to add?
There are a lot of other things on the big todo list, but nothing IMHO that cannot be done after the PR is merged into master.

Looks fine to me. Plugins are adapted. I'd like to see it merged soon. Might implement some of the other issues this evening, seems as if I've got some time then.

Been sick and busy at work. Will look into doing the merge as soon as possible(perhaps today or tomorrow)

authors: larshp mrsimpson


text:
#2724 added message after commit

A popup_to_inform is used to show to user that the commit is successful.

Seems a bit intrusive to me. A simple MESSAGE ... TYPE 'S' might be better? Not sure.

Yea, would like not to do extra button clicks

I changed the popup to a message

Thanks for contributing! This will resolve #2724.

see comment by FreHu above

fixed the issue.

test

@Hir0ki looks like you have deleted the source branch? Hence I cannot merge the changes

Oh sry, I didn't knew that you would be able to merge the change.
I will create a new pull request.

source: gharchive/pull-request

authors: FreHu Hir0ki flaiker larshp

repo: larshp/abapGit

license: mit

license_type: permissive

license_source: bigquery


text:
Update cloudwatch, dynamodb, kinesis, s3, sns, ... to 2.17.159

Updates

software.amazon.awssdk:cloudwatch
software.amazon.awssdk:dynamodb
software.amazon.awssdk:kinesis
software.amazon.awssdk:s3
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:sts

from 2.17.143 to 2.17.159.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #852.

license: MIT

license_source: github-api


text:
Consider removing sbt-release-early

sbt-release-early keeps failing in closing the repository or releasing it (a sample error below). We could consider replacing it with sbt-release that's pretty reliable until something better is available.
[info] Nexus repository URL: https://oss.sonatype.org/service/local
[info] sonatypeProfileName = io.laserdisc
[info] Reading staging repository profiles...
[error] Multiple repositories are found:
[error] [iolaserdisc-1086] status:open, profile:io.laserdisc(4c27934a30ac28) description: Implicitly created (auto staging).
[error] [iolaserdisc-1087] status:open, profile:io.laserdisc(4c27934a30ac28) description: Implicitly created (auto staging).
[error] Specify one of the repository ids in the command line
[error] java.lang.IllegalStateException: Found multiple staging repositories
[error] 	at xerial.sbt.Sonatype$NexusRESTService.$anonfun$findTargetRepository$8(Sonatype.scala:479)
[error] 	at scala.Option.getOrElse(Option.scala:121)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.findTargetRepository(Sonatype.scala:476)
[error] 	at xerial.sbt.Sonatype$SonatypeCommand$.$anonfun$sonatypeRelease$1(Sonatype.scala:202)
[error] 	at sbt.Command$.$anonfun$applyEffect$4(Command.scala:134)
[error] 	at sbt.Command$.$anonfun$applyEffect$2(Command.scala:130)
[error] 	at ch.epfl.scala.sbt.release.Helper.runCommand$1(ReleaseEarlyPlugin.scala:524)
[error] 	at ch.epfl.scala.sbt.release.Helper.$anonfun$runCommandAndRemaining$1(ReleaseEarlyPlugin.scala:533)
[error] 	at ch.epfl.scala.sbt.release.ReleaseEarly$Defaults$.$anonfun$sonatypeRelease$1(ReleaseEarlyPlugin.scala:267)
[error] 	at ch.epfl.scala.sbt.release.ReleaseEarly$Defaults$.$anonfun$sonatypeRelease$1$adapted(ReleaseEarlyPlugin.scala:259)
[error] 	at scala.Function1.$anonfun$compose$1(Function1.scala:44)
[error] 	at sbt.internal.util.$tilde$greater.$anonfun$$u2219$1(TypeFunctions.scala:39)
[error] 	at sbt.std.Transform$$anon$4.work(System.scala:66)
[error] 	at sbt.Execute.$anonfun$submit$2(Execute.scala:263)
[error] 	at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:16)
[error] 	at sbt.Execute.work(Execute.scala:272)
[error] 	at sbt.Execute.$anonfun$submit$1(Execute.scala:263)
[error] 	at sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:174)
[error] 	at sbt.CompletionService$$anon$2.call(CompletionService.scala:37)
[error] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[error] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[error] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[error] 	at java.lang.Thread.run(Thread.java:748)
[error] java.lang.IllegalStateException: Found multiple staging repositories
[error] 	at xerial.sbt.Sonatype$NexusRESTService.$anonfun$findTargetRepository$8(Sonatype.scala:479)
[error] 	at scala.Option.getOrElse(Option.scala:121)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.findTargetRepository(Sonatype.scala:476)
[error] 	at xerial.sbt.Sonatype$SonatypeCommand$.$anonfun$sonatypeRelease$1(Sonatype.scala:202)
[error] 	at sbt.Command$.$anonfun$applyEffect$4(Command.scala:134)
[error] 	at sbt.Command$.$anonfun$applyEffect$2(Command.scala:130)
[error] 	at ch.epfl.scala.sbt.release.Helper.runCommand$1(ReleaseEarlyPlugin.scala:524)
[error] 	at ch.epfl.scala.sbt.release.Helper.$anonfun$runCommandAndRemaining$1(ReleaseEarlyPlugin.scala:533)
[error] 	at ch.epfl.scala.sbt.release.ReleaseEarly$Defaults$.$anonfun$sonatypeRelease$1(ReleaseEarlyPlugin.scala:267)
[error] 	at ch.epfl.scala.sbt.release.ReleaseEarly$Defaults$.$anonfun$sonatypeRelease$1$adapted(ReleaseEarlyPlugin.scala:259)
[error] 	at scala.Function1.$anonfun$compose$1(Function1.scala:44)
[error] 	at sbt.internal.util.$tilde$greater.$anonfun$$u2219$1(TypeFunctions.scala:39)
[error] 	at sbt.std.Transform$$anon$4.work(System.scala:66)
[error] 	at sbt.Execute.$anonfun$submit$2(Execute.scala:263)
[error] 	at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:16)
[error] 	at sbt.Execute.work(Execute.scala:272)
[error] 	at sbt.Execute.$anonfun$submit$1(Execute.scala:263)
[error] 	at sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:174)
[error] 	at sbt.CompletionService$$anon$2.call(CompletionService.scala:37)
[error] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[error] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[error] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[error] 	at java.lang.Thread.run(Thread.java:748)
[error] java.lang.IllegalStateException: Found multiple staging repositories
[error] 	at xerial.sbt.Sonatype$NexusRESTService.$anonfun$findTargetRepository$8(Sonatype.scala:479)
[error] 	at scala.Option.getOrElse(Option.scala:121)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.findTargetRepository(Sonatype.scala:476)
[error] 	at xerial.sbt.Sonatype$SonatypeCommand$.$anonfun$sonatypeRelease$1(Sonatype.scala:202)
[error] 	at sbt.Command$.$anonfun$applyEffect$4(Command.scala:134)
[error] 	at sbt.Command$.$anonfun$applyEffect$2(Command.scala:130)
[error] 	at ch.epfl.scala.sbt.release.Helper.runCommand$1(ReleaseEarlyPlugin.scala:524)
[error] 	at ch.epfl.scala.sbt.release.Helper.$anonfun$runCommandAndRemaining$1(ReleaseEarlyPlugin.scala:533)
[error] 	at ch.epfl.scala.sbt.release.ReleaseEarly$Defaults$.$anonfun$sonatypeRelease$1(ReleaseEarlyPlugin.scala:267)
[error] 	at ch.epfl.scala.sbt.release.ReleaseEarly$Defaults$.$anonfun$sonatypeRelease$1$adapted(ReleaseEarlyPlugin.scala:259)
[error] 	at scala.Function1.$anonfun$compose$1(Function1.scala:44)
[error] 	at sbt.internal.util.$tilde$greater.$anonfun$$u2219$1(TypeFunctions.scala:39)
[error] 	at sbt.std.Transform$$anon$4.work(System.scala:66)
[error] 	at sbt.Execute.$anonfun$submit$2(Execute.scala:263)
[error] 	at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:16)
[error] 	at sbt.Execute.work(Execute.scala:272)
[error] 	at sbt.Execute.$anonfun$submit$1(Execute.scala:263)
[error] 	at sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:174)
[error] 	at sbt.CompletionService$$anon$2.call(CompletionService.scala:37)
[error] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[error] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[error] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[error] 	at java.lang.Thread.run(Thread.java:748)
[error] (core / releaseEarlyPublish) java.lang.IllegalStateException: Found multiple staging repositories
[error] (coreJS / releaseEarlyPublish) java.lang.IllegalStateException: Found multiple staging repositories
[error] (fs2 / releaseEarlyPublish) java.lang.IllegalStateException: Found multiple staging repositories
[error] Total time: 779 s, completed Jul 19, 2018 4:17:40 PM

This should be related to the way sbt-sonatype handles repositories https://github.com/xerial/sbt-sonatype/issues/49
I’m all for replacing it but I wonder if the problem is not on having the scalaVersion matrix in travis

I wonder if you should use mill 😆
It does actually have some interesting selling points (as pointed out in the linked discussion).

For the last couple of releases I set the max concurrent jobs to 1 on Travis and they went fine. This proves the problem is the releases being executed in parallel as @sirocchj suggests. The drawback of the workaround, though, is that now a full release takes double the time (around 50 minutes at the moment).

@barambani should we https://github.com/olafurpg/sbt-ci-release ?

it's worth a try. I can pick this up as soon as I have fixed the client.

I went a bit ahead (given the joy of using sbt-ci-release on Eisner) and I've created a fresh GPG key for this, I pushed it to a keyserver and have already added all Travis env variables (w/o removing anything still needed by sbt-release-early)..
To get this completed, sbt-ci-release needs now still:

some work on build.sbt and project/plugins.sbt as per https://github.com/olafurpg/sbt-ci-release#sbt
some .travis.yml TLC as per https://github.com/olafurpg/sbt-ci-release#travisyml (see example here

With the above (ideally making sure last stage does not recompile...) I think we're probably good to go w.r.t. this

source: gharchive/issue

authors: barambani fiadliel sirocchj

repo: laserdisc-io/laserdisc


text:
\current@color is independent of the target color model

Or in other words: Should \selectcolormodel update \current@color and \default@color?
For example, with pdftex and pdf mode on, \current@color is initialized to gray scale black 0 g 0 G, and \default@color is let to \current@color at beginning of document. Then a user writing \usepackage[cmyk]{xcolor} may expect that every color in the resulting pdf is represented in cmyk.
But since \normalcolor, which does \let\current@color\default@color then pushes \current@color to color stack, is used by latex2e kernel in several places, 0 g 0 G will be found multiple times in pdf. Also to machine, \normalcolor text will be different to \color{.} text.
\documentclass{article}
\usepackage{xcolor}
\def\showCurrentColor{%
  \setbox0=\hbox{{\normalcolor n}\textcolor{.}{N}}\showbox0 }
\showboxdepth=100
\showboxbreadth=100

\begin{document}
% \selectcolormodel{natural} % default color model
\showCurrentColor

\selectcolormodel{rgb}
\showCurrentColor

\selectcolormodel{cmyk}
\showCurrentColor
\end{document}

The \showbox part of {\normalcolor n} is independent of the target color model,
.\pdfcolorstack 0 push {0 g 0 G}
.\OT1/cmr/m/n/10 n
.\pdfcolorstack 0 pop

while the part of \textcolor{.}{N} is dependent of the target color model.
% color model = natural
.\pdfcolorstack 0 push {0 g 0 G}
.\OT1/cmr/m/n/10 N
.\pdfcolorstack 0 pop
% color model = rgb
.\pdfcolorstack 0 push {0 0 0 rg 0 0 0 RG}
.\OT1/cmr/m/n/10 N
.\pdfcolorstack 0 pop
% color model = cmyk
.\pdfcolorstack 0 push {0 0 0 1 k 0 0 0 1 K}
.\OT1/cmr/m/n/10 N
.\pdfcolorstack 0 pop

I'm not sure if I would dare to change that. It would affect every document which sets a color model and I don't want to get angry comments that I just broke various test suites for something that seems not to harm anyone. Imho if someone wants to change \normalcolor is should be done explicitly.

It would affect every document which sets a color model and I don't want to get angry comments that I just broke various test suites for something that seems not to harm anyone.

Perhaps through a new package option?
I admit the gains from this feature are small. Even xcolor supports this, other packages may still use a hard-coded default color, for example tikz. And as a last resort, one can always use ghostscript to convert all colors in a PDF to a specific model.

I'm not aware of any standard or use case that would force to drop the gray model, even if a document wants to force cmyk or uses spotcolors. So unless some concrete example comes up I don't see a gain here.

authors: muzimuzhi u-fischer


text:
Shutdown

This implements the shutdown functionality which was the last thing missing on the client side in order to handle async client communication.
This makes it even more obvious that a lot of code is duplicated and should be deduplicated, but in order to do any of that, some more extensive should first be added.
In order to do that, I have switched to a more feature full test framework (catch2). For now that is mostly to try and focus on actually writing tests even if most of the functionality I use could most likely be written specifically for this library which seems to be what many other boost libraries seems to do.

@djarek Thanks a lot for your comments.
I hope it makes sense that I postpone looking into any of them for now, that doesn't mean that I don't appreciate your effort.

repo: laudrup/boost-windows-sspi


text:
[server] Is it possible to use a Windows Certificate Store certificate on a server?

I have a few questions when trying to evaluate if we can use this library for our http server (written in Boost.Beast):

When creating a context for server usage, a certificate is required as well as private key. Unlike OpenSSL Windows has the concept of a certificate with an associated private key that must be available to the process or user running the server process. Such a certificate can be used using context::use_certificate().

We have our certificates in Windows Certificate Store (Personal). I was hoping to use this certificate directly in the store without having to export it / the private key. Is that possible?
The server example does not get the certificate or the private key from the windows certificate store, it seems. Is this possible?
Is it possible for me to retrieve the CERT_CONTEXT* from Windows Certificate Store (using the CryptoAPI perhaps?) directly, and then use it with context::use_certificate without having to separately import a private key (after all, it is stored in the Windows Certificate Store on the system)?

Lots of questions... :) I'm missing a server example using the Windows Certificate Store...

Hi @meastp
Thank you for your interest in this library.
I don't think it is possible to use a Windows Certificate Store with the current implementation but it sounds like it should definitely be something that ought to be possible.
To be honest I don't know much about how Windows handles certificates apart from the work I've done with this library,, so since this is something that has to be implemented I would very much appreciate you input on which kind of interface you would like for this.
If you have an idea of how you would like the interface to look we can discuss that and hopefully I'll have some time to implement it at some point. Otherwise, pull requests are of course very welcome if you want to try and implement it yourself.

@laudrup I see. I'm just a user, unfortunately with no expertise on tls or CryptoAPI, so I can't really help much.
The ideal interface would be to be able to point to a certificate in the Windows Certificate Store by using it's thumbprint (it's the usual and a sound way to pick a specific certificate on windows, at least). If this could be a certificate with a non-exportable private key, it would be the most secure (but requiring an exportable private key is also ok).

Hi again @meastp,
This library is very much modeled after how the existing asio::ssl implementation which uses OpenSSL works so that's why I initially implemented it this way.
I don't use Windows myself but most often things are quite a bit different/complicated on that platform so any user input is very much appreciated.
I've looked a bit into it and it seems like the certificate could be provided by adding an overload to the use_certificate function that takes an additional HCERTSTORE parameter to the store containing the certificate.
I think that ought to work if you call such a function with the handle to the "Personal Certificate Store" in addition to the CERT_CONTEXT pointer for the certificate to use from that store. Hopefully that should work even with a non-exportable private key. It should also be fairly simple for me to add a test for that functionality.
I don't think using a thumbprint is the correct approach here. A thumbprint is most often used for validating whether a certficiate/key matches the expected one. Of course on Windows things are quite often different from the norm though.
What do you think about adding such a function the the context class?

@meastp That's exactly what I'm suggesting. Good to hear you like that interface. Of course the most important aspect of designing APIs is that they are easy for the users to use correctly.
I'm working on implementing that and will update this issue once I have something working (or not).

@meastp
I've looked more into this and it seems like I've been a bit confused. As far as I can tell there's no need to add another member function to the context. If you have a CERT_CONTEXT which has an associated private key you should be able to simply use the code as it is.
I'm looking into extending the tests to verify that and the documentation should definitely be updated to make it more clear that this is the case.
I'm also looking into whether it's possible to verify that the CERT_CONTEXT has a usable private key associated and make the function fail if not. Currently the handshake will simply timeout if the certificate doesn't have a private key associated which is not very intuitive.
But please do feel free to use the code as it now and please do let me know if you experience any issues.

That's great news - and I think, like you, that a documentation update is really needed ;)

which has an associated private key
Have you been able to confirm if the (associated) private key has to be exportable?

@meastp
I've added some code for ensuring that a private key is referenced when setting the certificate using use_certificate. It will now fail if the certificate doesn't reference a private key or the private key doesn't match the public key used in the certificate.
I've also added some tests for ensuring that as well as for using a certificate created by CertCreateSelfSignCertificate which I think should create a certificate similar to the one you're trying to use. I'm fairly certain this also works with a non-exportable private key.
Additionally I've tried to clarify the documentation for use_certificate a bit. Do you think you could have a look at that here and see if that makes things clearer?
Of course feel free to have a look at the branch in general and let me know what you think.
Thanks.

@laudrup Great work, thank you! :) I'm on parental leave, will get back to this when I return to work (easter, next year) :)

authors: laudrup meastp

repo: laudrup/boost-wintls


text:
dot-env dependency | password and email in json

I intend to remove this dependency. Let's work it out in favor of...config files?
Also, it seems the code doesn't use dot-env now =_=
But it's still being called. My mistake.
The password and a few other info/path(s) are better off in a single config file. Rather than a json. No particular reason for why, I just prefer .cfg now.
tl:dr; Clean the code

vide fea295b20be738ad06428732a027d8824e53ee88 dot-env is not needed at all
Also, having a single main config file is probably a better choice for this project.
Next step is to make the read from the .cfg

db70784303ed1597efdf0dbb9812c237c91024ee
Done

repo: laughingclouds/Scrapia-World


text:
Cooperation Task - 4

In each game room, we'd like to underline the words "neutral" or "unpleasant" (depending on the room type) and make the whole text line larger please

underlited and increase size. can you check?, if good, feel free to close this issue.

authors: LavalleyCA toujames


text:
fetch is not defined

Hello.
I am getting "fetch is not defined" on the following line:
const metadata = await urlMetadata(https://adnan-tech.com)
Any help is highly appreciated.

You're either in a Node or browser environment that doesn't have javascript fetch available.
Try upgrading your environment, or you can use an earlier version of this package (version 2.5.0).

Owner

Thanks. Exactly. I was using Node version 14. I updated my Node version to 20. Now it works fine. Hope it helps someone.

One more reason I found is that there are some websites like facebook.com, and twitter.com, where fetch() or request() modules don't work. However, it worked on other sites.

Many of the big sites explicitly block scrapers like this intentionally.

Many of the big sites explicitly block scrapers like this intentionally.

Got it.

repo: laurengarcia/url-metadata


text:
Wrong date

Hi,
Date of the consumption data is wrong : index retrieved from toutsurmoneau.fr is day-1 data not d-day as displayed in Home Assistant.
Please, let me know if it is not clear or i misunderstand something.
Thank's

Interestingly I even have the case where the data provides volumes reading at 6am and then at 10pm for the same day. I don't know which day this data belongs to.

Hi,
Any news about this topic ?
I have also 1day shifted.
Regards

Hello Laurent.
I'm not a developer (and, unable to program this)
On the site so-eau.toutsurmoneau.fr, I can retrieve my entire history in csv.
I wonder if it wouldn't be simpler to retrieve the csv through your client each day, and use an integration like https://community.home-assistant.io/t/custom-integration-to-import-long- term-statistics-from-a-file-like-csv-or-tsv  to import it?
it should solve the date shift issues?


text:
Removing init.py from lava/lib to avoid module clash across lava libraries

Removing init.py from lava/lib to avoid module clash across lava libraries and let namespace search take care of it.

Was there an issue with the release @bamsumit ? Should we rerelease, @bamsumit , @mgkwill ?

Yeah. Basically one cannot make lava-dl and lava-optimization work together. Depending on their order in the PYTHONPATH, the user can import the first library only.

@mathisrichter tagging you for lava-dnf

authors: awintel bamsumit

repo: lava-nc/lava-optimization


text:
Unit Tests for AnimatedSprite

Unit Test everything testable in this class.
Cover all edge cases.

Worked on as part of i13

Not a lot of commenting in the test file. We may want more for our test files. Thoughts?

Thoughts on the test suites?

Oh god. I think that either each test needs a comment or two, or potentially, a short comment for each BOOST_CHECK. I'm more leaning for the second of the two, but to be fair, both could be helpful.

I think they're fine. If you like, you could add a a couple subsuites still. Maybe one for testing different constructors or initialization, one for testing the steps, one for setting values.

I agree with michael

How about now?

finished as part of #13

authors: bauerbp gyurgyma lavinrp

repo: lavinrp/GameBackbone


text:
学到了，谢谢！

感谢

您好！您的邮件我已收到，我将尽快给您回复，谢谢！祝：身体健康，工作顺利！


text:
Integration Testing for "chore(datastore): explicit owner integ tests refactoring"

Issue #, if available:
Integration testing for https://github.com/aws-amplify/amplify-ios/pull/1510
Description of changes:
Check points: (check or cross out if not relevant)

[ ] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

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

:exclamation: Current head d70518f differs from pull request most recent head 874ab13. Consider uploading reports for the commit 874ab13 to get more accurate results

@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage        ?   58.42%
=======================================
  Files           ?      617
  Lines           ?    18658
  Branches        ?        0
=======================================
  Hits            ?    10901
  Misses          ?     7757
  Partials        ?        0

Flag
Coverage Δ

AWSPluginsCore
73.10% <0.00%> (?)

Amplify
45.93% <0.00%> (?)

Analytics_plugin_unit_test
71.76% <0.00%> (?)

Auth_plugin_unit_test
78.96% <0.00%> (?)

DataStore_plugin_unit_test
75.70% <0.00%> (?)

Predictions_plugin_unit_test
26.81% <0.00%> (?)

Storage_plugin_unit_test
58.06% <0.00%> (?)

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

Continue to review full report at Codecov.

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

authors: codecov-commenter lawmicha

repo: lawmicha/amplify-ios


text:
Add scripts

upload script to generate missing directory indexes

Also includes a few fixes I was trying to troubleshoot theme generation issues


text:
[Extensibility] Move from "SaaS" to "Provider" or "RemoteProvider"

Let's switch from SaaS to Provider or RemoteProvider
Originally posted by @leecalcote in https://github.com/layer5io/meshery/pull/2145#discussion_r549476993

Related to #2141


text:
fix: 修复table edit时数据值为0 输入框显示的值不正确

问题描述
表格开启单元格编辑时，需要展示数据单位，故cols字段使用templet属性自定义单元格。当数据值为0时，点击单元格编辑时会将单位文案也带入输入框。阅读源码后发现是因为把数据存在了html标签的content属性上，通过JQuery.data方法去获取content属性的值得到的是数字0，所以input[0].value读的值是elemCell.text()整个文本的值，换成JQuery.attr("data-content")获取的是字符串0就没有问题了
问题复现线上地址
https://codepen.io/wuxunjiee/pen/MWvYVMz

这个问题已经在后续版本修复了， 抱歉 pr 未及时处理

authors: sentsim wuxunjiee

repo: layui/layui


text:
rustc nightly

Hi,
First off, thank you for a great crate. Would it be possible to change it a bit so it does not require nightly rustc ?
Best regards
Kim

I am afraid it's not possible for now. Because I use concat_idents to generate codes that require nightly, otherwise I need a custom code generation mechanism which I don't have time for now.

oki thank you :)

You can use version 0.5.0 which support stable now

authors: desdic lazytiger

repo: lazytiger/ipset


text:
Fix/ Incident Handling

OP-1977 | OP-1978 | OP-1979 | OP-1980 | OP-1981

It might not be enough, there might be orphan persons left behind (see https://github.com/lblod/app-organization-portal/pull/208/files)
If there are persons with positions in those bestuur (and not anywhere else), you might need to either migrate them to the correct bestuur or delete them completely

authors: iurianu nbittich

repo: lblod/app-organization-portal


text:
Mismatch between keys cloudInit and userData.cloud-init in scaleway.InstanceServer

When creating an InstanceServer provided with the cloudInit key, any subsequent invocation of pulumi up will incorrectly trigger an update of this resource as the field userData.cloud-init is present in the created state, but absent in the resource description of InstanceServer.
When (by incorrectly using the API) passing the cloud-init configuration as userData: { 'cloud-init': ... }, pulumi no longer wishes to update the resource.
This might be fixed upstream, where cloud-init is passed as a key to userData. It coincides with the migration from V1 to V2 of the Scaleway API.
EDIT: just passing 'cloud-init' as a key to userData fixes the problem

We're up to date with the latest upstream now, so I believe this is resolved.

repo: lbrlabs/pulumi-scaleway


text:
make transcoding work

transcoding works for mov to mp4
publishing in progress removes all but the top card and the bottom controls rather than forcing you to scroll up to see what's going on
start to make transcoding settings card in settings
add optimize checkbox to publishing
connect to supporting code in lbry-redux (lbry)
todo:
add ffmpeg availability and "find" button
get file size and suggest / warn about estimated time
prune support to be only for video, and only for desktop

I think this looks good!

@seanyesmunt re-review requested of this

authors: jessopb kauffj seanyesmunt

repo: lbryio/lbry-desktop


text:
Homepage: show Reposts w/o dups + enable for Ody

Issue
Closes #5894 Examine re-enabling reposts on odysee homepage
Changes to ClaimTilesDiscover

Add remove_duplicates by default.
Port forceShowReposts from ClaimListsDiscover. This allows reposts to be shown regardless of the "Hide Reposts" setting, which is locked to "true" for Odysee.

My bad.  I looked at the wrong SDK PR (make reposts searchable by: stream_type, media_type, duration, fee_amount and fee_currency #3386).  During testing, I must have tested against "Following" instead of categories.


text:
Referral fixes

@lyoshenka not sure how this got so FUBAR'ed, should only be  a28df97

when I do this, which is more then I'd like to admit, I usually cherry-pick the one commit onto a new branch:
git checkout master
git pull --rebase
git checkout -b referral_fixes_2
git cherry-pick a28df97
git push

@jobevers good idea and done, thanks!

authors: jobevers kauffj


text:
关于CollapsingToolbarLayout嵌套TwinklingRefreshLayout闪屏及TwinklingRefreshLayout嵌套viewpager问题解决办法

我的xml结构是
-CoordinatorLayout
--AppBarLayout
----VideoView //隐藏
----SlidingTabLayout //不隐藏
--AppBarLayout
--TwinklingRefreshLayout
----ViewPager
--TwinklingRefreshLayout
-CoordinatorLayout
viewPager下是fragment，fragment下是recycleView
按照作者提供的CollapsingToolbarLayout嵌套TwinklingRefreshLayout方法使用时，发现触摸屏幕缓慢向上移动会出现闪屏，不管是在viewPager下的fragment外嵌套TwinklingRefreshLayout还是在viewpager外嵌套TwinklingRefreshLayout。
是该方法导致 refreshLayout.setNestedScrollingEnabled(false);
这个方法应该是让TwinklingRefreshLayout跟随着CollapsingToolbarLayout移动。当设置为false时不再闪屏，但是触摸屏幕上下拖动无法再移动，或者移动不流畅。
我解决方法是 当recyclerView滑到顶部或底部时才能使用TwinklingRefreshLayout
步骤:
1.refreshLayout.setNestedScrollingEnabled(false);设置为false，setrefresh 及setLoadmore也设置为false，setOverScroll也设置为false,此时相当于TwinklingRefreshLayout不起作用
2.判断recyclerView的滑动状态及是否滑动到底部及顶部
当recyclerView向下滑，且滑动到底部时，setLoadmore方法设置true
当recyclerView在滑动时，执行步骤1操作
当recyclerView向上滑，且滑动到顶部时，setrefresh 方法设置为true
本人小白，提出一个自己的解决方法，希望能帮到其他人，如果有更好的请告诉我。

我也遇到这个问题，还好你这边给出了解决方法，也不知道这个库什么时候可以解决这个问题。

太棒了，解决了，不过滑动还是有点别扭

我找到一个办法，可以对appBarLayout addOnOffsetChangedListener，offset为0表示到顶部了，启用refreshLayout，反之禁用。
https://www.jcodecraeer.com/a/anzhuokaifa/androidkaifa/2015/0616/3052.html
appBarLayout.addOnOffsetChangedListener(object : AppBarLayout.OnOffsetChangedListener{
override fun onOffsetChanged(barLayout: AppBarLayout?, offset: Int) {
if (offset == 0) {
list?.forEach {
(it as BaseClientPromotionLogFragment).enableRefreshLayout()
}
} else {
list?.forEach {
(it as BaseClientPromotionLogFragment).disableRefreshLayout()
}
}
}
    })

public fun disableRefreshLayout() {
refreshLayout.isNestedScrollingEnabled = false
refreshLayout.setEnableRefresh(false)
refreshLayout.setEnableOverScroll(false)
}
public fun enableRefreshLayout() {
    refreshLayout.isNestedScrollingEnabled = true
    refreshLayout.setEnableRefresh(true)
    refreshLayout.setEnableOverScroll(true)
}

authors: CarpOrange flztsj mendax92 tangjiarao

repo: lcodecorex/TwinklingRefreshLayout


text:
ElevationProfile: slope visualization not plausible for short distances

Example parameter:
?c=689932,5330260&z=16&l=atkis,f_a30f0dc0-e829-11ee-9e1d-774423e0ec98_407404b0-f688-4069-9fd8-c50d90bdcc45&t=ba&rtwp=1286848.4338603707,6123402.321062666,1286783.9501924426,6123287.630345532,1286662.1477085783,6122776.300898309&rtc=bvv-hike

Update:

With improved Backend and ElevationMS:


text:
Windows 10 Metro applications bug

Metro apps show twice and don't have any icon.

clever-dock work for win7/vista/xp 100%
not work for win10/8.1/8

I managed to fix most bugs on my PC, I should push this evening. Now I just need to find a way to get an icon for Metro apps as the usual win api calls do not work for them, and they all have explorer.exe as process filename.

I try on windows 10. But Windows bar is hidden! I can't fixed. Because the settings menu looks normal.

authors: Raafet ldom66 timemrah


text:
encoding of the '!important' rule

For a following idml2xml commit I need to know how to save the !important CSS rule in Hub.
The following image will demonstrate the need on setting cell border properties with an important rule:
Cell 1 has a solid border, tough cell 2 (below cell 1) overwrites the border-bottom property of cell 1.
Idea A
We expand all attribute value definitions to allow !important as suffix:
    css:border-top-width="0.5pt !important"
    css:border-top-color="yellow !important"

Idea B
We use separate attributes:
    css:border-top-color-important="true"
    css:border-top-width-important="true"

Leads to a lot of / inefficient attributes if there are lot of overwrites (i.e. dashed line, etc.).
Idea C
One attribute with a space separated list of the important properties:
    css:border-top-important="color width"

I would prefer idea C. Does this concept work for all CSS properties (what about single props, such as css:color)?
Any other suggestions?

I think we should go with Idea A and adapt the CSSa schema accordingly.

Con: It requires some more parsing when not using the CSS parser.
Pro: It will be parsed as expected by said CSS parser.

Actually, there is no need for the !important suffix at the moment. Resolved in idml2xml without of setting !important anywhere.
Another aspect to mention: !important is useless in HTML context, when the border-width of the cell is thinner than the neighbor as in the following example:

    1
    2

By adding !important to the second cell there will be no change of the border style between cell 1 and cell 2.

authors: gimsieke pglatza

repo: le-tex/CSSa


text:
testかく

ちゃんとしたやつ

done


text:
🛑 Meraki API Org Show is down

In 0243ea1, Meraki API Org Show (https://api.meraki.com/api/v1/organizations/43483) was down:

HTTP code: 502
Response time: 1438 ms

Resolved: Meraki API Org Show is back up in c525dd3.

repo: leafle/mki-api-upptime


text:
refactor(ModelTheory): Remove FirstOrder.Language.mk₂ and related constructors

Removes FirstOrder.Language.mk₂ and related constructors, and lemmas about them
Redefines FirstOrder.Language.constantsOn to not use FirstOrder.Language.mk₂

[x] depends on: #16323
[x] depends on: #16338
[x] depends on: #16367

Looks like it didn't work
maintainer merge

Could you please extend the PR commit message a bit with some motivation. And please record the list of deleted names in the commit message. The bot posted a rough approximation here: https://github.com/leanprover-community/mathlib4/pull/16369#issuecomment-2322983730

Thanks :tada:
bors merge

authors: YaelDillies awainverse jcommelin


text:
feat: fun n : ℕ ↦ n ^ n is monotone

From GrowthInGroups (LeanCamCombi)

bors merge


text:
refactor: Data/Bitvec change definition of ofInt to the ring homomorphism

After discussion with colleagues, we agreed that this was probably the more usual definition of ofInt. I kept the old sign-preserving version as ofIntSign.

Sorry this has been sitting here unreviewed. I can't really tell why this change is being made. Perhaps you could incorporate more of that discussion into comments?
(But please, other reviewers, don't let my ignorance get in the way if you're inclined to merge.)

Thank you @semorrison. As part of our effort to model compiler IRs as they arise in LLVM and MLIR, @bollu, @goens, and @ChrisHughes24 started to model bit-vector arithmetic. Aiming to contribute to the lean community where sensible, we want to explore in which way our requirements are compatible with mathlib. Truncating to the least significant bits (instead of preserving the sign but) is what programming languages typically do and also matches our own modeling efforts for LLVM/MLIR as well as the lean-smt people. We once again discussed this internally and feel this is a genuine correction to mathlib and the old code just required this correction.
Some CS details: in our work we obtained peephole rewrite test cases from the Alive project that are generic over the bitwidth and contain constants such as 1. Even though the value 1 is a common constant in many test cases, it is not in the set of values represented by a 1-bit vector when interpreted as 2's complement, which is just {0, -1}. Hence, we need to convert the bitwidth-generic value 1 into a 1-bit value. The new implementation that this PR introduces coincides with the conversion LLVM/MLIR chose for the very reason that it is more convenient for mathematicians, as it increases consistency across different bitwidths.

The new definition is definitely more sensible than the old one.
bors r+

Thank you @digama0


text:
feat(UniqueProds): subsingleton and MulOpposite lemmas

Basic support for subsingleton and MulOpposites.  Helps #6723.

Eric, your comments are great!  However, I just left my computer for about half an hour: I'll produce a further PR incorporating them, since in the meanwhile bors is merging!

Eric, given that there were conflicts, I went ahead and incorporated your suggestions in this PR.  The conflicts are with #6677.  I tried implementing the change just in this file from that PR, but I think that it needs some of the earlier stuff too.
One of the two PRs should go first, and I do not really have a preference of which one it is!


text:
feat(LinearAlgebra/Matrix/Trace): add Matrix.trace_diagonal

The statement that the trace of a diagonal matrix is the sum of the diagonal elements.
Zulip discussion

Is this ready for review?

Ah, yes, I simply forgot to tag it!

bors r+

authors: ADedecker adomani


text:
LSP-based infoview

This PR splits the infoview into a separate NPM package independent of VSCode, and based on a more general editor<->infoview API based on LSP. Changes include:

The new infoview API tries to provide more general functionality, basing most of it on LSP requests and the ability to listen in on incoming/outgoing LSP notifications from within the infoview. This is intended to allow using custom requests from widget code.

This is not as nice to implement on the VSCode extension side as one might like. See here for why. This may be fixable in upstream vscode-jsonrpc.
I expect the new API to be more easily implementable in any other text editor capable of displaying a webpage.

Fixes in various edge cases. For example, we now delete pins when the corresponding file is closed as the server cannot produce goal states for them any more.
We handle more stuff in the infoview. For example, pins are synced there without going through the extension by subscribing to textDocument/didChange.
Outsourced tachyons CSS and codicons to NPM packages. I took the artistic liberty of changing the codicon for copy-to-comment to "quote" (see it here) as I couldn't find the current one (and maybe "quote" is a little clearer?).
Some refactoring, primarily on info.tsx. UI code is difficult, but I tried to separate the concerns of pausing and fetching goals into different and maybe reusable components.
The repository is now organised into a "monorepo" containing two packages. We use Lerna to manage them.
Probably other things I forgot.

I apologise for making the development a bit hard to follow. I made commits to a separate repo before copying the files here. They can be browsed.
There are quite a lot of changes, and while I tried testing all functionality I expect there to be some breakage. Still to be fixed:

[x] Re-send diagnostics to infoview on startup
[x] Implement "copy-to-comment" (now a general "make text edit" API)

I've tried it out a bit now.  Some comments:

The LICENSE file should go back into the root directory.
The release.sh script should also go back into the root directory, and run npm run build after npm i.  (Ideally, there'd be a github action which uploads the release when a tag is pushed, but we can do that another time.)
There's quite a bit of flickering when you move the cursor through a file (it switches between "No info found." and something else).  This might be related to https://leanprover.zulipchat.com/#narrow/stream/147302-lean4-dev/topic/Auto.20completion/near/233509746 and eafe2e1980467d3851f175754ffb56c27d4c332b
I'm not sure what I think about the grayed-out identifiers.  Graying out the hypothesis name foo✝ in foo✝ : Nat is a positive change in my eyes (since you can easily spot the accessible hypotheses).  But graying them out in the rest of the term looks very distracting (since it's the only highlighting so it sticks out like a sore thumb).
The pinned info shows Loading... for a short time every time you type something.
Copy-to-comment produces an extra newline.
vscode now uses 230% CPU (with 4 processes)

* But graying them out in the rest of the term looks very distracting (since it's the only highlighting so it sticks out like a sore thumb).

In Emacs I quickly got used to it, and I believe @leodemoura liked them as well. I haven't seen this PR in action yet though, it might be a case of color schemes. Here is what it looks like in Emacs for me currently:

* But graying them out in the rest of the term looks very distracting (since it's the only highlighting so it sticks out like a sore thumb).

In Emacs I quickly got used to it, and I believe @leodemoura liked them as well. I haven't seen this PR in action yet though, it might be a case of color schemes. Here is what it looks like in Emacs for me currently:

I get something very similar on my machine, and yes I like it too :)

It's a much lighter gray here:

With #777 as the gray color for the light theme it looks better for me.

The LICENSE file should go back into the root directory.
vscode now uses 230% CPU (with 4 processes)

fixed

The release.sh script should also go back into the root directory, and run npm run build after npm i. (Ideally, there'd be a github action which uploads the release when a tag is pushed, but we can do that another time.)

I made an attempt at how this should work but cannot test it without the PAT, so feel free to change things. Note the slightly weird --scope=lean4 because the extension package is named lean4. Ideally we'd rename it to something like @lean4/vscode-extension but not necessary if it would cause trouble with the extension marketplace.

Copy-to-comment produces an extra newline

This is also the current behaviour, but I removed the newline.

There's quite a bit of flickering when you move the cursor through a file

The pinned info shows Loading... for a short time every time you type something.

I removed the Loading... indicator, I think it is nicer this way. In particular we still get a gold font on the status line when things are loading so no information is lost.

Copy-to-comment produces an extra newline

This is also the current behaviour, but I removed the newline.

Oops, I didn't notice that.  You're right of course.

There's quite a bit of flickering when you move the cursor through a file

The pinned info shows Loading... for a short time every time you type something.

I removed the Loading... indicator, I think it is nicer this way. In particular we still get a gold font on the status line when things are loading so no information is lost.

I think that was a different bug.  I mean the following:
#eval 1 + Nat.zero

Put the cursor on Nat, and pin the info.
Insert spaces before 1.

Every space increases the position of the pin by two!
On every keystroke, the expected type briefly disappears.

After some spaces, the pin is beyond the end of the line.

I fixed the type disappearing. As for the double-move, I also observed that before but can't anymore. I will wishfully think it disappeared along with one of the recent changes, but let me know if it's still buggy. Also the pin movement is still incorrect if you insert a newline before 1 and then immediately remove it, but that also seems broken in the current code so is no regression.

I still get the double-moves.

Fixed now, hopefully. This was only observable on development builds because it was (intentionally, to catch this kind of bug) triggered by React.StrictMode.

@gebner I've been test-driving this since the PR and it seems to work fine. I think it's good to go. Though I probably wouldn't release a new version until there are actually new features (WIP) using the LSP API.

Great!  I'll make a release so that we get some free testing!

authors: Kha Vtec234 gebner leodemoura


text:
[Feature request] support lean4

It looks like elan does not support updating Lean 4 toolchains:
$ elan -V
elan 1.0.0 (bc778de59 2021-04-17)
$ elan toolchain list
leanprover-lean4-nightly (default)
$ elan update
info: no updatable toolchains installed
info: checking for self-updates

It would be nice to have it work.

It looks like this is a pretty fundamental limitation with @khoek's changes for supporting arbitrary repositories - not sure if he's interested in taking another look :)

Ok, I gave a quick workaround a try after all. Please see the changelog of the linked commit and complain if I've broken anything.

authors: Kha fghzxm

repo: leanprover/elan


text:
compiler core-dumping (when defining structures?)

The following give me a core dump with message src/tcmalloc.cc:277] Attempt to free invalid pointer 0x7fffd7100118 . I run lean without memory restrictions... Can anyone reproduce this?
import types.sigma types.prod
import algebra.binary algebra.group
open eq eq.ops

namespace path_algebra

variable {A : Type}

structure distrib [class] (A : Type) extends has_mul A, has_add A :=
(left_distrib : ∀a b c, mul a (add b c) = add (mul a b) (mul a c))
(right_distrib : ∀a b c, mul (add a b) c = add (mul a c) (mul b c))

structure mul_zero_class [class] (A : Type) extends has_mul A, has_zero A :=
(zero_mul : Πa, mul zero a = zero)
(mul_zero : Πa, mul a zero = zero)

structure zero_ne_one_class [class] (A : Type) extends has_zero A, has_one A :=
(zero_ne_one : zero ≠ one)

structure semiring [class] (A : Type) extends add_comm_monoid A, monoid A,
  distrib A, mul_zero_class A, zero_ne_one_class A

end path_algebra

I get this same behavior:
-- mode: compilation; default-directory: "~/Dropbox/Projects/Lean/" --
Compilation started at Tue Jan 6 13:47:14 ~/projects/lean/bin/lean
-Dpp.width=80 /home/avigad/Dropbox/Projects/Lean/test.hlean *** Error in
`/home/avigad/projects/lean/bin/lean': free(): invalid next size (fast):
0xbfe52e18 *** Compilation aborted (core dumped) at Tue Jan 6 13:47:14
On Tue, Jan 6, 2015 at 12:18 AM, Jakob von Raumer notifications@github.com
wrote:

The following give me a core dump with message src/tcmalloc.cc:277]
Attempt to free invalid pointer 0x7fffd7100118. I run lean without memory
restrictions... Can anyone reproduce this?
import types.sigma types.prod
import algebra.binary algebra.group
open eq eq.ops
namespace path_algebra
variable {A : Type}
structure distrib [class] (A : Type) extends has_mul A, has_add A :=
(left_distrib : ∀a b c, mul a (add b c) = add (mul a b) (mul a c))
(right_distrib : ∀a b c, mul (add a b) c = add (mul a c) (mul b c))
structure mul_zero_class [class] (A : Type) extends has_mul A, has_zero A :=
(zero_mul : Πa, mul zero a = zero)
(mul_zero : Πa, mul a zero = zero)
structure zero_ne_one_class [class] (A : Type) extends has_zero A, has_one A :=
(zero_ne_one : zero ≠ one)
structure semiring [class] (A : Type) extends add_comm_monoid A, monoid A,
distrib A, mul_zero_class A, zero_ne_one_class A
end path_algebra
—
Reply to this email directly or view it on GitHub
https://github.com/leanprover/lean/issues/385.

authors: avigad javra

repo: leanprover/lean


text:
Simp fails to apply certain lemma

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Checked that your issue isn't already filed.
Reduced the issue to a self-contained, reproducible test case.

Description
simp generalizes class instance parameters used in the simp lemma to metavariables, but then a default instance of the class is synthesized there before it is tried to match the target expression.
Thus, the matching fails and the simp lemma cannot be applied.
I'm not sure why it works for one case below but not for the other case.
Steps to Reproduce
I made a Monoid class:
abbrev Zero α := OfNat α (natLit! 0)

class Monoid (α : Type u) [Zero α] extends Add α where
  zero_add (a : α) : 0 + a = a
  add_zero (a : α) : a + 0 = a

attribute [simp] Monoid.zero_add Monoid.add_zero

Then, something strange happens. simp can use zero_add but not add_zero despite their similar types:
variable {α : Type u} [Zero α] [Monoid α]

-- works
example (a : α) : 0 + a = a := by simp

-- fails
example (a : α) : a + 0 = a := by simp

Here is the relevant part of the trace:
[Meta.isDefEq]
  [Meta.isDefEq.step] @HAdd.hAdd ?m.967 ?m.967 ?m.967 (@instHAdd ?m.967 (@Monoid.toAdd ?m.967 ?m.968 ?m.969)) ?m.970
    (@OfNat.ofNat ?m.967 0
      ?m.968) =?= @HAdd.hAdd α α α (@instHAdd α (@Monoid.toAdd α inst✝¹ inst✝)) a (@OfNat.ofNat α 0 inst✝¹)
  [Meta.whnf] @HAdd.hAdd ?m.967 ?m.967 ?m.967 (@instHAdd ?m.967 (@Monoid.toAdd ?m.967 ?m.968 ?m.969)) ?m.970
      (@OfNat.ofNat ?m.967 0 ?m.968)
    [Meta.whnf] @HAdd.hAdd
    [Meta.whnf] @HAdd.hAdd α α α (@instHAdd α (@Monoid.toAdd α inst✝¹ inst✝)) a (@OfNat.ofNat α 0 inst✝¹)
    [Meta.whnf] @HAdd.hAdd
    [Meta.isDefEq.step] ?m.967 =?= Nat
    [Meta.isDefEq] ?m.967 [assignable] =?= Nat [nonassignable]
      [Meta.isDefEq.assign]
        [Meta.isDefEq.assign] ?m.967 := Nat
        [Meta.isDefEq.assign.beforeMkLambda] ?m.967 [] := Nat
        [Meta.isDefEq.assign.checkTypes]
          [Meta.isDefEq.step] Type ?u.966 =?= Type
          [Meta.isLevelDefEq.step] ?u.966 =?= 0
          [Meta.isDefEq.assign.final] ?m.967 := Nat
    [Meta.isDefEq.step] ?m.970 =?= a
    [Meta.isDefEq] ?m.970 [assignable] =?= a [nonassignable]
      [Meta.isDefEq.assign]
        [Meta.isDefEq.assign] ?m.970 := a
        [Meta.isDefEq.assign.beforeMkLambda] ?m.970 [] := a
        [Meta.isDefEq.assign.checkTypes]
          [Meta.isDefEq.step] Nat =?= α
          [Meta.whnf] Nat
            [Meta.isDefEq.step] Nat =?= α
            [Meta.whnf] Nat
              [Meta.isDefEq.hint] Nat =?= α
              [Meta.whnf] Nat
              [Meta.isDefEq.hint] α =?= Nat
          [Meta.isDefEq.assign.typeMismatch] ?m.970 : Nat := a : α
  [Meta.isDefEq] @HAdd.hAdd ?m.967 ?m.967 ?m.967 (@instHAdd ?m.967 (@Monoid.toAdd ?m.967 ?m.968 ?m.969)) ?m.970
    (@OfNat.ofNat ?m.967 0
      ?m.968) =?= @HAdd.hAdd α α α (@instHAdd α (@Monoid.toAdd α inst✝¹ inst✝)) a (@OfNat.ofNat α 0 inst✝¹) ... failure
[Meta.Tactic.simp.unify] Monoid.add_zero:1000, failed to unify @HAdd.hAdd ?m.967 ?m.967 ?m.967
  (@instHAdd ?m.967 (@Monoid.toAdd ?m.967 ?m.968 ?m.969)) ?m.970
  (@OfNat.ofNat ?m.967 0
    ?m.968) with @HAdd.hAdd α α α (@instHAdd α (@Monoid.toAdd α inst✝¹ inst✝)) a (@OfNat.ofNat α 0 inst✝¹)

Somehow Nat is assigned to a metavar out of thin air.
Perhaps it is from the @[defaultInstance] here: https://github.com/leanprover/lean4/blob/5d4cb58f786ae9e7142e578e29fc9e4c9b651403/src/Init/Prelude.lean#L349-L351
I tried to reduce the test case above, but I found several things are essentials to reproduce this issue:

It works if rw is used:

-- works
example (a : α) : a + 0 = a := by rw [Monoid.add_zero]

It works if OfNat is replaced with a class and number literal is not used:

class Zero (α : Type u) := zero : α

add_zero (a : α) : a + Zero.zero = a

It works if Add is replaced with a custom class:

class Op (α : Type u) := op : α → α → α

It works if I specify the type manually:

-- works
example (a : α) : a + 0 = a := by simp [Monoid.add_zero (α := α)]

Expected behavior: Monoid.add_zero is applied by simp.
Actual behavior: simp fails to use the lemma.
Reproduces how often: Always.
Versions
Lean (version 4.0.0, Release) current master.

My result of investigation was completely wrong :|

My result of investigation was completely wrong :|

It helped.

authors: leodemoura pcpthm


text:
fix: watch out for heartbeat wraparound

Fix for possible heartbeat wrap-around in very long running processes (e.g LSP perhaps?)  See discussion: https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/heartbeats.2C.20GMP.20vs.20no.20GMP

There is no wrap-around issue being reported in the linked thread.

g_heap is thread local. There is no issue here. I am closing the PR

authors: leodemoura lovettchris


text:
Setup script for Chill

Features

Asks user for the inputs required by chill.
Modifies chill.yml as per the inputs.
Uses pm2 to start the processes.
Displays the addresses where the processes are run.

Limitations

Doesn't add an nginx configuration. User will have to manually point to the addresses displayed.
node/yarn/pm2/git have to be pre-installed for the script to proceed with the installation. (The script however does check if these are pre-installed or not)

Screenshots

:100:

Codecov Report

Merging #55 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   80.59%   80.59%
=======================================
  Files          19       19
  Lines         943      943
  Branches      135      135
=======================================
  Hits          760      760
  Misses        183      183

Continue to review full report at Codecov.

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

@kabirbaidhya @romitamgai Someone with Linux should try doing this and then we can merge it.

Also the script creates chill inside chill #chill-ception.
/codehome/leapfrog/chill-project/chill/scripts/chill, /codehome/leapfrog/chill-project/chill/scripts/chill/chill.yml
@leapfrogtechnology/chill-team

@manisacharya You can look at this script and update it. We need a sh file to setup all of chill. This should be like a one click install but from the terminal.
Good opportunity to learn a bit of bash. 😛

@mesaugat I was looking into this. First I had to move chill.yml outside the monitor folder. Now, I will work on this.

authors: codecov-io manisacharya mesaugat pratishshr romitamgai

repo: leapfrogtechnology/chill


text:
Uncaught TypeError: Cannot read property 'log' of undefined

[Enter steps to reproduce below:]

Lose internet.
Get internet back.
Obsessively hit the reconnect button.

Atom Version: 2.0.0-beta3
Electron Version: 0.37.8
System: Mac OS X 10.11.1
Thrown From: learn-ide package, v2.0.0-beta3
Stack Trace
Uncaught TypeError: Cannot read property 'log' of undefined
At /Users/jonas/Downloads/Learn IDE Beta.app/Contents/Resources/app.asar/node_modules/node-ipc/dao/client.js:127

TypeError: Cannot read property 'log' of undefined
    at Socket.<anonymous> (/Users/jonas/Downloads/Learn IDE Beta.app/Contents/Resources/app.asar/node_modules/node-ipc/dao/client.js:127:19)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at onwriteError (_stream_writable.js:313:10)
    at onwrite (_stream_writable.js:331:5)
    at WritableState.onwrite (_stream_writable.js:89:5)
    at fireErrorCallbacks (net.js:450:13)
    at Socket._destroy (net.js:459:5)
    at Socket._writeGeneric (net.js:648:10)
    at Socket._write (net.js:700:8)
    at doWrite (_stream_writable.js:301:12)
    at writeOrBuffer (_stream_writable.js:287:5)
    at Socket.Writable.write (_stream_writable.js:215:11)
    at Socket.write (net.js:626:40)
    at Client.emit (/Users/jonas/Downloads/Learn IDE Beta.app/Contents/Resources/app.asar/node_modules/node-ipc/dao/client.js:45:21)
    at SingleSocket.close (/Users/jonas/Downloads/Learn IDE Beta.app/Contents/Resources/app.asar/node_modules/single-socket/lib/single-socket.js:67:19)
    at Terminal.module.exports.Terminal.reset (/Users/jonas/Downloads/Learn IDE Beta.app/Contents/Resources/app.asar/node_modules/learn-ide/lib/terminal.js:66:19)
    at HTMLDivElement.<anonymous> (/Users/jonas/Downloads/Learn IDE Beta.app/Contents/Resources/app.asar/node_modules/learn-ide/lib/views/status.js:69:33)

Commands
     -5:41.6.0 editor:newline (atom-text-editor.editor.is-focused)
  8x -5:20.1.0 learn-ide:save (atom-text-editor.editor.is-focused)
  4x -3:37.8.0 editor:newline (atom-text-editor.editor.is-focused)
     -3:36.2.0 learn-ide:save (atom-text-editor.editor.is-focused)
     -3:35.1.0 editor:newline (atom-text-editor.editor.is-focused)
  2x -3:34.9.0 learn-ide:save (atom-text-editor.editor.is-focused)
     -3:32 fuzzy-finder:toggle-file-finder (atom-text-editor.editor.is-focused)
     -3:30.9.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -3:30.9.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -3:30.4.0 tree-view:add-file (atom-text-editor.editor.is-focused)
  2x -3:25.3.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -3:24.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  2x -2:03.8.0 core:close (atom-text-editor.editor.is-focused)
  2x -1:55.7.0 editor:newline (atom-text-editor.editor.is-focused)
     -1:53.6.0 core:close (atom-text-editor.editor.is-focused)
     -0:50.8.0 learn-ide:save (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "integrated-learn-environment",
      "integrated-learn-environment",
      "integrated-learn-environment"
    ]
  },
  "learn-ide": {
    "oauthToken": "8def7bfa10b497267c50ee8791a2950bf90e65aadd6b3a59fd82656d9eedb1ea",
    "vmPort": 3007
  }
}

Installed Packages
# User
integrated-learn-environment, v1.9.0 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (active)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (active)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2-hotfix1 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
update-package-dependencies, v0.10.0 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)
learn-ide, v2.0.0-beta3 (active)
learn-ide-tree, v1.0.6 (active)

# Dev
No dev packages

@joshrowley I was seeing this as well earlier today

maybe, i'll look into it, thanks for the detailed report @adamjonas

tada

authors: adamjonas drewprice joshrowley

repo: learn-co/learn-ide


text:
investigate distribution via play store

From both a technical and user experience point of view, let's investigate the process for and implications of having Kolibri on Google Play.

There is also F-Droid, which might be an better option for initial broader deployment.

Already in place (but still pre-release).

authors: indirectlylit jamalex poVoq


text:
Older <4.4 Android Compatibility

Notes:

https://github.com/kivy/python-for-android/pull/903

The issue appears to be with loading sqlite3 https://github.com/kivy/python-for-android/issues/925

Based on barriers around target API versions and Play Store requirements, I don't think we're pushing for versions older than this now.

authors: DXCanas christianmemije jamalex


text:
Integrate monit for service monitoring & health checks

Feature request
It would be nice to integrate dokku-monit to ledokku. This would make possible checking for service health and service status from the UI. If a service is down, one could restart it using the already implemented restart button.
Also there should be possible to configure monit project wise through a plugins tab in the dedicated app menu.
Let me know what you think! :rocket:

@SaizFerri Hey and thanks for opening the issue! Looks interesting.
Do you have any ideas how and where it should be placed in the UI?
Would you be interested in implementing this yourself?

@Akirtovskis There could be another tab besides settings called plugins (when an app has been selected, not the global one). Under this tab there could be a left pane with a list of installed plugins such as letsencrypt or monit (like in settings with port management, domains and so on...). When a user clicks on a plugin we show all the functionality for that plugin. For example for monit we could show a toggle button for enabling it and all the env variables. Besides that at the top, the health check & system status. We could also show the health check at the dashboard, besides the docker logo on every app (if monit is enabled).
I could try to implement it myself and make a PR :ok_hand:

Sounds great! Let us know if you need any help, we are happy to give feedback or guide you around the unclear parts.

@Akirtovskis Thanks! Do you have some kind of discord or something where I can ask? I'm having trouble getting the client app to work locally.

@SaizFerri There you go : https://discord.gg/MmwtW5Ys

authors: Akirtovskis SaizFerri

repo: ledokku/ledokku


text:
images are not showing in android.

I am only getting this screen in android

+1

+1

+1

authors: edencakir nguyendinhmanh58 tavriaforever waleedarshad-vf

repo: leecade/react-native-swiper


text:
ibgen-rs

IBGEN - Instituto Brasileiro de Gestão de Negócios - Porto Alegre/RS

Do you mean ibgen.com.br domain?

repo: leereilly/swot


text:
Error train with my data

InvalidArgumentError (see above for traceback): Restoring from checkpoint failed. This is most likely due to a mismatch between the current graph and the graph from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:
Assign requires shapes of both tensors to match. lhs shape= [4096,539] rhs shape= [4096,1470]
[[node save/Assign_53 (defined at train.py:35) ]]

The VOC dataset is 20 classes, your date must be 1 class?? So you don't restore the last layer weights.

The VOC dataset is 20 classes, your date must be 1 class?? So you don't restore the last layer weights.

what sould i do??

You shouldn't restore the last layer weights.

with your suggest, i dont have problem until training. but when im testing with my data, there are no box in img... any suggest??

When you stop train, how much is the loss??

1000 iteration and i have loss 10 dude..
i only have 80 image, is it ok??

authors: leeyoshinari miscla


text:
style: :pencil2: fixed typos

fixed typos

Excelente trabajo justo este tipo de detalles hacen un software  profesional. Estamos empezando con la documentación sería bueno tú aporte

repo: leifermendez/bot-whatsapp


text:
[Suggestion] User friendly ban command

!ban - When a user doesn't specify a duration, automatically make the duration permanent.
!ban Player1 too cool for the game > auto assumes duration 0 and completes successfully.
!banip - When a user doesn't specify CIDR for an IP address, automatically make the CIDR /32.
!banip 192.168.23.19 the coffee is too hot > auto assumes 192.168.23.19/32.

I think the slash commands largely makes this not matter as much anymore. ReOpen if you disagree

Makes sense to me 👍

authors: JONTTM leighmacdonald

repo: leighmacdonald/gbans


text:
Using 'attach' mode doesn't support colors

I am using 'add flutter to native project', when using attach mode, VSCode's console doesn't show any colors.

Please review and/or search the other issues when creating an issue. See #1 and #2.
tl;dr: colors are not supported in IDE consoles. These consoles do not support ANSI escapes.

repo: leisim/logger


text:
Remove call to deprecated RCTImageLoader method

The deprecated loadImageWithTag method has been removed in v0.32.0-rc.0.

Reference: https://github.com/facebook/react-native/commit/7e5de707be0d0bdfe90f908b1fc7d6de08050613

With 0.32 stable being released, is this to be merged soon ?

@rdougan your fix cause new error: unknown type name 'RCTImageLoaderCancellationBlock'

@jernejrus what version of RN? I'm testing with the latest 0.32 stable and it appears to be working fine. RCTImageLoaderCancellationBlock still exists in RCTImageLoader.h header:
https://github.com/facebook/react-native/blob/master/Libraries/Image/RCTImageLoader.h

Sorry, it was my mistake. I did not only remove the call of the function but also the import of RCTImageLoader.h. The fix is OK!

This was fixed by https://github.com/lelandrichardson/react-native-maps/pull/389.  We just need to publish a new version. I'll be publishing 8.0 today.

I just released 0.8.0, which fixes this issue.

Thanks!

Hi, I can't find which function we should call instead of loadImageWithTag.  I assume that if it is deprecated, there is another function that performs a superset of loadImageWithTag, but it is not in the release notes for 0.32.  I think an answer here will also help others running into this problem in various npm libraries (like react-native-image-rotate.)  Cheers, Chris

I am getting error while building the project
/Users/mahesh/MaheshApps/myproject/node_modules/react-native-maps/ios/AirMaps/AIRMapMarker.m:212:58: No visible @interface for 'RCTImageLoader' declares the selector 'loadImageWithURLRequest:size:scale:clipped:resizeMode:progressBlock:completionBlock:'

React-native :- V0.35
React :- V15.3.2
React-native-maps :- V0.10.1

authors: Exilz cfogelklou jernejrus maheshiv rdougan spikebrehm

repo: lelandrichardson/react-native-maps


text:
Do not require react-addons-perf

This removes react-addons-perf which seems to be unavailable in 15.1, although someone who actually uses this should probably weigh in as it may have simply moved locations.
The specific observed error prompting this change was: Error: Cannot find module 'react/lib/ReactDefaultPerf'

I'm not sure this is a valid solution. I've never had this problem before. We are requiring the library properly to the latest version. Could you update to the latest version and try again. Make sure you install the dependancies properly

I have the same issue after react 15.1 upgrade

@evollu Are you having this issue using the latest version of react-native-mock (0.2.3), or an older version. You must be using the latest version

I tried 0.2.2 yesterday. I will try 2.3 today

0.2.3 is working for me

@rt2zz Can you retry with version 0.2.3, and close if problem solved.

:+1:

authors: RealOrangeOne evollu rt2zz

repo: lelandrichardson/react-native-mock


text:
失联啦？

我不用微信了，你只能给我打电话

我不用微信了，你只能给我打电话


text:
Pantograph Error Cases Report

Environment setup
header = """
set_option maxHeartbeats 0
open BigOperators Real Nat Topology Rat
"""
project_path = "<repo>/experiments/minif2f/MiniF2F"
server = Server(imports=['Aesop', 'Mathlib'], project_path=project_path)

Error cases

[ ] JSONDecodeError for parsing brackets
theorem amc12_2000_p15 (f : ℂ → ℂ) (h₀ : ∀ x, f (x / 3) = x ^ 2 + x + 1)
    (h₁ : Fintype (f ⁻¹' {7})) : (∑ y in (f ⁻¹' {7}).toFinset, y / 3) = -1 / 9

[ ] JSONDecodeError for mathd_numbertheory_552
theorem mathd_numbertheory_552
  (f g h : ℕ+ → ℕ)
  (h₀ : ∀ x, f x = 12 * x + 7)
  (h₁ : ∀ x, g x = 5 * x + 2)
  (h₂ : ∀ x, h x = Nat.gcd (f x) (g x))
  (h₃ : Fintype (Set.range h)) :
  (∑ k in (Set.range h).toFinset, k) = 12

A minimized Case
theorem mathd_numbertheory_552_min (h : ℕ → ℕ) (h₃ : Fintype (Set.range h)) : true

[ ] Unsolved goals
theorem sample (p q r x : ℂ)
      (h₀ : (x - p) _(x - q) = (r - p)_ (r - q))
   : (x - r) _x = (x - r)_ (p + q - r)

The remaining goal state:
p : ℂ
q : ℂ
r : ℂ
x : ℂ
h₀ : (x - p) _(x - q) = (r - p)_ (r - q)
⊢ ℂ

Lean Server Result
The Lean server response can be check here

As for the JSONDecodeError in mathd_numbertheory_552 (and the corrsponding MWE), could you please try the following fix?
https://github.com/lenianiva/PyPantograph/blob/f4cc21cc963a9f410b0aec05052d6b4975861321/pantograph/server.py#L177

Can you explain what is supposed to happen in case 2?
The first one is probably a Python problem

The first one is probably a Python problem

Sorry for the words "parsing brackets"—that wasn't accurate. The issue isn't with the {} but with the () in the last condition:
(∑ y in (f ⁻¹' {7}).toFinset, y / 3)
The same applies to the second one as well. Note that this all works fine in the LSP. You can try the following code:
import Mathlib
import Aesop

theorem mathd_numbertheory_552
  (f g h : ℕ+ → ℕ)
  (h₀ : ∀ x, f x = 12 * x + 7)
  (h₁ : ∀ x, g x = 5 * x + 2)
  (h₂ : ∀ x, h x = Nat.gcd (f x) (g x))
  (h₃ : Fintype (Set.range h)) :
  (∑ k in (Set.range h).toFinset, k) = 12 := sorry

theorem amc12_2000_p15 (f : ℂ → ℂ) (h₀ : ∀ x, f (x / 3) = x ^ 2 + x + 1)
    (h₁ : Fintype (f ⁻¹' {7})) : (∑ y in (f ⁻¹' {7}).toFinset, y / 3) = -1 / 9 := sorry

The error is raised by the server, not by json-loading. You can reproduce the error by:

Understood. This does seem rather strange as I've come across several similar issues that were due to json errors and were resolved by setting ensure_ascii=False.
I was able to successfully reproduce the error you mentioned. Below is a more detailed error backtrace:
PANIC at _private.Pantograph.Frontend.MetaTranslate.0.Pantograph.Frontend.MetaTranslate.translateExpr Pantograph.Frontend.MetaTranslate:71:6: assertion violation: ( __do_lift._@.Pantograph.Frontend.MetaTranslate._hyg.610.0 ).contains fvarId'

backtrace:
/path/to/pantograph/pantograph-repl(lean_panic_fn+0x70) [0xaaaad8c6b250]
/path/to/pantograph/pantograph-repl(l_panic___at___private_Pantograph_Frontend_MetaTranslate_0__Pantograph_Frontend_MetaTranslate_translateExpr___spec__1+0x44) [0xaaaad53c26c4]
/path/to/pantograph/pantograph-repl(lean_apply_7+0x460) [0xaaaad8c7a890]
/path/to/pantograph/pantograph-repl(lean_apply_8+0x2fc) [0xaaaad8c7b140]
/path/to/pantograph/pantograph-repl(l_ReaderT_bind___at___private_Pantograph_Frontend_MetaTranslate_0__Pantograph_Frontend_MetaTranslate_translateExpr___spec__8___rarg+0x114) [0xaaaad53c6ba8]
/path/to/pantograph/pantograph-repl(lean_apply_8+0x45c) [0xaaaad8c7b2a0]
/path/to/pantograph/pantograph-repl(l_Lean_Core_withIncRecDepth___at___private_Pantograph_Frontend_MetaTranslate_0__Pantograph_Frontend_MetaTranslate_translateExpr___spec__9+0x464) [0xaaaad53c7534]
/path/to/pantograph/pantograph-repl(l_Lean_Core_transform_visit___at___private_Pantograph_Frontend_MetaTranslate_0__Pantograph_Frontend_MetaTranslate_translateExpr___spec__4+0xa58) [0xaaaad53c40b4]
/path/to/pantograph/pantograph-repl(l_Lean_Core_transform___at___private_Pantograph_Frontend_MetaTranslate_0__Pantograph_Frontend_MetaTranslate_translateExpr___spec__3+0xfc) [0xaaaad53cee5c]
/path/to/pantograph/pantograph-repl(l___private_Pantograph_Frontend_MetaTranslate_0__Pantograph_Frontend_MetaTranslate_translateExpr+0x1dc) [0xaaaad53d1abc]
/path/to/pantograph/pantograph-repl(l_Pantograph_Frontend_MetaTranslate_translateLocalInstance+0x184) [0xaaaad53d26ec]
/path/to/pantograph/pantograph-repl(l_Array_mapMUnsafe_map___at_Pantograph_Frontend_MetaTranslate_translateMVarId___spec__1+0x19c) [0xaaaad53d20b8]
/path/to/pantograph/pantograph-repl(l_Pantograph_Frontend_MetaTranslate_translateMVarId___lambda__3+0x534) [0xaaaad53d6cd4]
/path/to/pantograph/pantograph-repl(lean_apply_8+0x45c) [0xaaaad8c7b2a0]
/path/to/pantograph/pantograph-repl(lean_apply_5+0x444) [0xaaaad8c79338]
/path/to/pantograph/pantograph-repl(l_Lean_Meta_withLCtx___at_Pantograph_Frontend_MetaTranslate_translateMVarId___spec__6___rarg+0x64) [0xaaaad53d4a2c]
/path/to/pantograph/pantograph-repl(l_Pantograph_Frontend_MetaTranslate_translateMVarId___lambda__4+0x19c) [0xaaaad53d78fc]
/path/to/pantograph/pantograph-repl(l_Pantograph_Frontend_MetaTranslate_translateMVarId+0x564) [0xaaaad53d15f4]
/path/to/pantograph/pantograph-repl(l_List_mapM_loop___at_Pantograph_Frontend_MetaTranslate_translateMVarFromTacticInfoBefore___spec__1+0x274) [0xaaaad53dec94]
/path/to/pantograph/pantograph-repl(l_List_mapM_loop___at_Pantograph_Frontend_sorrysToGoalState___spec__3+0x254) [0xaaaad53f1678]
/path/to/pantograph/pantograph-repl(pantograph_frontend_sorrys_to_goal_state_m+0x1b0) [0xaaaad53f2cb0]
/path/to/pantograph/pantograph-repl(lean_apply_5+0x3ac) [0xaaaad8c792a0]
/path/to/pantograph/pantograph-repl(l_Pantograph_Repl_runMetaInMainM___rarg+0x88) [0xaaaad5407528]
/path/to/pantograph/pantograph-repl(l_Pantograph_Repl_runMetaInMainM___rarg___boxed+0x14) [0xaaaad5407c3c]
/path/to/pantograph/pantograph-repl(lean_apply_5+0x3ac) [0xaaaad8c792a0]
/path/to/pantograph/pantograph-repl(l_ReaderT_bind___at_Pantograph_Repl_execute_frontend__process___spec__2___rarg+0x98) [0xaaaad5446a4c]
/path/to/pantograph/pantograph-repl(lean_apply_5+0x3d0) [0xaaaad8c792c4]
/path/to/pantograph/pantograph-repl(l_Lean_withEnv___at_Pantograph_Repl_execute_frontend__process___spec__3+0x1e0) [0xaaaad5446f54]
/path/to/pantograph/pantograph-repl(l_List_mapM_loop___at_Pantograph_Repl_execute_frontend__process___spec__5+0x778) [0xaaaad544923c]
/path/to/pantograph/pantograph-repl(l_Pantograph_Repl_execute_frontend__process___lambda__5+0x510) [0xaaaad544ac04]
/path/to/pantograph/pantograph-repl(l_Pantograph_Repl_execute_frontend__process___lambda__7+0x230) [0xaaaad544be84]
/path/to/pantograph/pantograph-repl(l_Pantograph_Repl_execute_frontend__process+0x180) [0xaaaad544c124]
/path/to/pantograph/pantograph-repl(l_Pantograph_Repl_execute+0x333c) [0xaaaad54507c8]
/path/to/pantograph/pantograph-repl(l_loop___lambda__2+0x264) [0xaaaad53123fc]
/path/to/pantograph/pantograph-repl(l_loop+0x41c) [0xaaaad53117a0]
/path/to/pantograph/pantograph-repl(l_loop___lambda__1___boxed+0x28) [0xaaaad5313758]
/path/to/pantograph/pantograph-repl(lean_apply_6+0x1f8) [0xaaaad8c79bc0]
/path/to/pantograph/pantograph-repl(l_loop+0x41c) [0xaaaad53117a0]
/path/to/pantograph/pantograph-repl(l_main___lambda__1+0xb4) [0xaaaad5313f60]
/path/to/pantograph/pantograph-repl(l_main___lambda__2+0x554) [0xaaaad5314c6c]
/path/to/pantograph/pantograph-repl(+0xfa61e4) [0xaaaad53161e4]
/usr/lib64/libc.so.6(+0x2b040) [0xffffb93cd040]
/usr/lib64/libc.so.6(__libc_start_main+0x94) [0xffffb93cd118]
/path/to/pantograph/pantograph-repl(_start+0x30) [0xaaaad53104b0]

As the error message suggests, commenting out this line can address the aforementioned JSONDecodeErrors. (However, Unsolved goals remains unsolved):
https://github.com/lenianiva/Pantograph/blob/3744cfaa9608cd43e00078283339662b3720949b/Pantograph/Frontend/MetaTranslate.lean#L71C1-L71C43
I'm still not certain why this assertion fails. Perhaps @lenianiva could conduct a more in-depth inspection.

authors: Purewhite2019 RexWzh lenianiva

repo: lenianiva/PyPantograph


text:
fix: fix a compilation bug when inherit from another module

Description of the changes
Fix a bug introduced by the 2.7 patch
Checklist

[x] I didn't over-scope my PR
[x] My PR title matches the commit convention
[x] I did not include breaking changes
[x] I made my own code-review before requesting one

I included unit tests that cover my changes

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

I added/updated the documentation about my changes

[ ] 📜 README.md
[ ] 📕 docs/*.md
[ ] 📓 docs.lenra.io
[x] 🙅 no documentation needed

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

authors: Nesqwik shiipou

repo: lenra-io/lenra-common


text:
access controls should be hidden when inaccessible

Describe the bug
If the user does not have permission to get/list service accounts, roles, and/or role bindings, these buttons are still showing up under "Access Control". If you click on them, it says "Failed to load items."
To Reproduce
Steps to reproduce the behavior:

Set up a user with limited permissions with no access to service accounts, roles, or role bindings.
Authenticate as that user and open up the cluster in Lens.
Open up "Access Controls" on the lefthand side and click on "Service Accounts", "Role Bindings", or "Roles".

Expected behavior
These buttons should be hidden if the user doesn't have permission, just like other resources are hidden. If nothing under "Access Controls" is accessible then the whole thing should be hidden.
Screenshots

Environment (please complete the following information):

Lens Version: 4.2.2
OS: macos 10.15.7
Installation method (e.g. snap or AppImage in Linux): n/a

Fixed by #2258

repo: lensapp/lens


text:
Kubectl binary is downloaded when opening cluster dashboard

Describe the bug
When opening a cluster dashboard first time, Lens will download kubectl binary matching to the cluster version. However, afaik the dashboard itself does not require kubectl binary. When opening the terminal, installing features or applying resources kubectl binary is needed and Lens will already download it on demand. So it seems that downloading kubectl binary is not necessary when opening the cluster dashboard.

I think it should be downloaded right after dashboard is opened. But instead of blocking everything it should be spawned to background.

authors: jakolehm nevalla


text:
Upgrade to typedoc@0.20.X

Signed-off-by: Sebastian Malton sebastian@malton.name
closes https://github.com/lensapp/lens/pull/2518
blocked by https://github.com/TypeStrong/typedoc/issues/1589

https://user-images.githubusercontent.com/8225332/120702364-fd094300-c481-11eb-9e5f-1d25e88ebe2c.mov


text:
Support using Eviction API where applicable

close #5602

Also reminder that enhancements should never go into patch releeases

In light of https://kubernetes.io/docs/concepts/scheduling-eviction/api-eviction/#troubleshooting-stuck-evictions we might want to support a "force delete" option in the Lens UI, which directly invokes the delete() method instead of evict(). Could be for another PR...

How exactly you think we should implement it? Keep separated menu items "Delete" and "Evict" for the Pods menu?

How exactly you think we should implement it? Keep separated menu items "Delete" and "Evict" for the Pods menu?

Maybe we could somehow detect that a pod is being evicted and then show a Force Delete action in the menu.

I thought of separate menu items. "Delete" (or "Evict") and "Force Delete" (or "Kill"). Also, there could be a "Force" checkbox on the delete dialog.

authors: Nokel81 ixrock jim-docker


text:
Use Inno for creation of standalone .exe

Hie, @leoafarias  this is a continuation of issue raised here #1
I have been experimenting with flutter desktop for sometime and creating a single .exe has been a pain. Luckily i found a free installer inno setup as mentioned in flutter docs .
The advantage of this is that, it creates a bundled .exe file which can be shared as a single file, it comes with a graphical wizard to setup and also a script that you then run and it compiles to create your .exe
I have downloaded the sidekick and used inno setup to create a standalone .exe
Here is an example script i used to generate the .exe file (auto generated by Inno setup script wizard) available as gist here
The example executable file created,

The main issue I see with Inno is the fact that it has to be done manually, and there is no "easy" way to create the installer using Github Actions

@DonnC would like to help to implement this as part of our creation workflow, also what is the main benefits of Inno vs Msix, and also their certificate signing

The app is now on the MS Store
https://www.microsoft.com/store/productId/9NZ54K8CW0WG
and has  a signed installer: https://github.com/leoafarias/sidekick/releases/download/0.2.0/windows-signed-0.2.0.Msix
I see no need for alternative install methods at this time

authors: DonnC aguilaair leoafarias

repo: leoafarias/sidekick


text:
clean + fix coveralls

clean + fix coveralls
Describe your change:
Make sure it is clean before testing + coveralls only at the end of unit test
Checklist - Check boxes in the PR UI, not by editing the text
Pull Request

[x] PR description is meaningful.
[x] There are no more than a few commits to merge.
[x] There are no more than a few lines of code to review.

Code style

[x] Maximum line length does not require scrolling in Github
[x] FMT and ScalaStyle and ScalaFix are good

Testing

[x] Unit tests for the added/modified code
[x] Overall unit test coverage good
[x] Unit tests are passing

Dependencies

[ ] The plugin is added to itself
[ ] The latest version is added to itself
[x] New dependencies do not have vulnerabilities

Security

[x] There is no known vulnerability being added to this project
[ ] Everything on this list is checked

Coverage remained the same at 69.841% when pulling aca623dbb71342ab5377c51bb9e754bc2eab7747 on lbenkel/publish into 6a79aa66528f26f4e9cdbf39f2c3eb8ff828e438 on master.

authors: coveralls leobenkel


text:
缩放如何保持item间距一样

滑动缩放时怎样设置所有item间距一样，不做改动的话中间的间距是最小的

现在间距就是一样的，中间小是因为中间的放大了，你想要的那种就要动态改变间距了，目前这个库底层不支持这种操作

我做了一个处理，能保证在Item 为 5个之内 能保证一样。参考这个回答

authors: leochuan yangwhat zhangchaojiong

repo: leochuan/ViewPagerLayoutManager


text:
希望添加搜索框选择删除某条记录的功能

当前版本中搜索框记录有一次全部清除历史记录的按钮，希望能添加一个单独删除某条记录的按钮，像百度首页搜索框的记录删除功能一样即可。
搜索框记录在一定程度上会充当收藏夹/常用搜索的功能，因为一些一次性搜索记录挤占掉常用搜索记录的位置有些不妥，而且重复搜索历史记录中的关键词，记录的顺序并不会更新保持置顶，这种不是因为时间权重而是综合新出现于时间权重的排序方式会让记录被没有出现过的关键词挤占掉位置。

这个功能比较简单，有空加一下，请期待

Done.
https://github.com/leon-kfd/Dashboard/commit/25b1384b765f6ef335626d01e89183a30d606171

Check. 感谢开发者！

authors: Lyrikp leon-kfd

repo: leon-kfd/Dashboard


text:
v1

大概架構:
外層(展覽/活動) 用Tabs做,
Tabs 的 child才是 eventList
eventsData.map((event)=>(Card))
Card 裡面還有 EventImg 的 component
可以直接在router import
細節顏色還沒調

衝突的部分, 把 sample code 刪掉即可


text:
Toggle icon to disable/enable  extension

It would be a nice feature like others to have the icon clickable and toggle extension to disable and enable.

We could repurpose the "Connected to Discord" text for this

repo: leonardssh/vscord


text:
yahm-ui develop branch abbruch

habe gerade yahm geupdatet und jetzt kommt wenn ich die yahm-ui aufrufen will dieser fehler.
/opt/YAHM/share/include.sh: Zeile 48: -is: Kommando nicht gefunden.
es liegt daran das in der include.sh nicht die variable LSB_RELEASE gesetzt wird.
ein
LSB_RELEASE="/usr/bin/lsb_release"
in der zeile hilft dann.
mfg
sven
scholz

gleiches Problem:

gefixt

zur Info:
Falls jemand die Datei angepasst hat muss er jetzt folgendes machen, sonst meckert das update die angepasste Datei an:
git reset --hard git pull

repo: leonsio/YAHM


text:
[BUG] Error in CG implementation

https://github.com/leopard-ai/betty/blob/39457e1800e3dd3c8b50c30bc6b7bd9ef4a96148/betty/hypergradient/cg.py#L53
I think p_new should be calculated based on r_new instead of r here. In the Wikipedia version (https://en.wikipedia.org/wiki/Conjugate_gradient_method) the corresponding formula is $p_{k+1} = r_{k+1} + \beta_k p_k$ with $r_{k+1}$ corresponding to r_new.

Hello @HuyD24,
Thanks for your interest and pointing out the error in my code. I think you are right, and thus I fixed the code to use r_new instead of r. When I ran several benchmarks with both r and r_new, I didn't experience any noticeable performance differences, and hope your experiments also didn't get affected by this bug. Let me know if you have other concerns.
Best,
Sang

Closing the issue as the bug is fixed.

repo: leopard-ai/betty


text:
fix: extract dyn_bindings impl into DynBindings trait

solves #2618

Thanks. Could you please run cargo fmt and update the PR?

authors: Upbolt gbj

repo: leptos-rs/leptos


text:
Dev

PR con aggiunta di moduli e subworkflow.
Inoltre abbiamo aggiunto la cartella bin dove depositerò gli script locali della pipeline per ovviare al precedente problema:
ovvero il problema di identificazione del path in container docker e singularity corrispettivo al path in locale.
Ho aggiunto il prettier ma ho effettuato una modifica all'editorconfig per ovviare ad un altro errore che occorreva durante il commit.

Reminder
Remove the TODOs and check the meta.yml of each module to see if they are correct.
For now, ignore the logo issue (files_unchanged), which seems to be a general problem. Remember to check it in the future.

repo: lescailab/nanorepertoire


text:
Adds a random cat image command

Haven't been able to test the code with your bot setup, but the random cat image code itself has been tested on my own setup and works.

Veldig gøy å se noen bidra allerede! Skal merge denne ASAP.

Innså at jeg gjorde en force-push når jeg rebaset master på branchen for Python, så din branch ble out-of-sync. Jeg cherry-picket og pushet til Python nå, sorry det ble litt rot. Anbefaler å resette din lokale python-branch slik at den blir synket. Du ser committene 677a2c6feb573d3b1105bc69dbd926313f0a72e6 og 5ef5b6409540a2c578248479b1a459b37b36acc3 i branchen nå :)

repo: lesesalen/lesebot


text:
(nice to have) _sendRequest as public for custom requests.

Just as support for add_filter('xmlrpc_methods',array($foo,"bar"));

I'll update the library to support custom XML-RPC methods in next day.

Greate. Thx.

authors: OskHa letrunghieu

repo: letrunghieu/wordpress-xmlrpc-client


text:
Add e2e test cases

Proposed changes
This PR adds e2e test cases.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[X] I have signed the CLA
[X] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

Coverage remained the same at 100.0% when pulling 5c2380052a96f013a981922867a39f4e05139d9b on fisuda:feature/e2e_test into 40aa95e66f00fec250b94841ad7704cde1c5f8b4 on lets-fiware:main.

authors: coveralls fisuda

repo: lets-fiware/ngsi-go


text:
YouTube Shorts - not blocked in List view of subscriptions

What filter does this issue target?
https://letsblock.it/filters/youtube-shorts
What changes should be made?

Did you write a uBlock filter solving this?
www.youtube.com##ytd-browse ytd-item-section-renderer:has(span.ytd-thumbnail-overlay-time-status-renderer[aria-label="Shorts"])
Additional notes
No response

Thanks @kiriya-aoi. That was also discussed on reddit for the upcoming lives filter.
I'm updating all the relevant filters in https://github.com/letsblockit/letsblockit/pull/200

This filter breaks the grid view when videos are grouped by date, so I have reverted it while I look for a fix.

Ah, it actually deletes the subscription view chooser (pictured) too, if a short is first in the list.

If I limit the scope, I can eliminate the videos themselves in list view (but not the title of the channel that released the short).
www.youtube.com##ytd-browse ytd-expanded-shelf-contents-renderer:has(span.ytd-thumbnail-overlay-time-status-renderer[aria-label="Shorts"])
Which gives this result for shorts in list view:

It doesn't affect the behavior in grid view, but it's also not good enough to really recommend.

My concern was also that if a channel posted two videos consecutively they would be groupped in the same ytd-item-section-renderer, meaning one short would hide the "full video" posted alongside it. On my account, it does not seem to be the case, each video has their own section:

That might change in the future, in which case we'll need to rollback our change, but for now we are safe with hiding the full ytd-item-section-renderer, we just need to find a way to differentiate between grid and list view. Unfortunately, the toplevel elements have no semantic difference, but the ytd-thumbnail item does have different classes. We should be able to get away with rules in the following form
www.youtube.com##ytd-browse PARENT_TO_FIND span.ytd-thumbnail-overlay-time-status-renderer[aria-label="Shorts"]:upward(ytd-grid-video-renderer)
www.youtube.com##ytd-browse PARENT_TO_FIND span.ytd-thumbnail-overlay-time-status-renderer[aria-label="Shorts"]:upward(ytd-item-section-renderer)

Let's go with the following rules:
! For list view
www.youtube.com##ytd-browse ytd-video-renderer span.ytd-thumbnail-overlay-time-status-renderer[aria-label="Shorts"]:upward(ytd-item-section-renderer)
! For grid view
www.youtube.com##ytd-browse ytd-grid-video-renderer span.ytd-thumbnail-overlay-time-status-renderer[aria-label="Shorts"]:upward(ytd-grid-video-renderer)
I'll prepare a PR to update the shorts filter, and work on the other filters if nothing breaks.

Heya @kiriya-aoi I merged #203 that should improve the situation without regression on the grid list.
Please try refreshing your list and tell me whether it works for for you!

It does appear to work in all of my usage. No noticeable side-effects, aside from the one I mentioned in the first line of https://github.com/letsblockit/letsblockit/issues/198#issuecomment-1166394554.

Thanks for your response @kiriya-aoi.
I think this is an acceptable tradeoff. An alternative would be to enforce never hiding the first row, but that would probably be more confusing.

authors: kiriya-aoi xvello

repo: letsblockit/letsblockit


text:
added triggers, to appease the war

I know how terribly the friendly, and totally not a biased circle jerk, discussion is going. This should clear a few issues up, for anyone scared of using DICSS.

What about some methods for establishing consent before exposing an API? I don't, some kind of verification and guidance layer. Done very tastefully, of course.

Oh no, that completely skipped over my privileged mind. Maybe someone can submit a pull request establishing consent rules, to let me know how much of a shitlord I really am?

Good trolling, but adding "trigger warnings" only makes the opposition more legitimate.
A joke doesn't need to apologize for itself, nor does it give warnings in advance.

authors: 0xdeafcafe Zaskoda letsgetrandy

repo: letsgetrandy/DICSS