python3Packages.recoll: init

Also move some stuff to recoll's nativeBuildInputs.

Motivation for this change
fixes https://github.com/NixOS/nixpkgs/issues/118514
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@fabianhjr @karthikiyengar Do you want to be added to recoll's maintainers?

Thanks for such a quick PR. Python isn't my primary language and the implementation details are a bit unclear to me, but sure, I can sign up and figure things out along the way :-)
I tested it out with a shell.nix and it seems to work fine.
let
  pkgs = import <nixpkgs> {};
in pkgs.mkShell {
  buildInputs = [
    pkgs.python3
    (pkgs.libsForQt5.callPackage ./pkgs/applications/search/recoll {})
  ];
}

@karthikiyengar I would recommend you put
with import ./. { };

(python3.withPackages (ps: with ps; [ recoll ])).env

in your shell.nix. It's important that recoll uses the same version of Python as the one the executable called python refers to.


update pipeline service deploy file

PR https://github.com/redhat-appstudio/infra-deployments/pull/2803 has been merged but the change in openshift-pipelines/pipeline-service/pull#867 has not been added yet. So automatic deploy file configuration is not done.

/assign @Roming22

Bot pr handles the deploy file update for staging https://github.com/redhat-appstudio/infra-deployments/pull/2931 . So I will be updating it only for production.

closing this as part of pr https://github.com/redhat-appstudio/infra-deployments/pull/2957


self is not defined NextJS app

Hi there, this error happens when we try to init the library on a NextJS app using React Native Web on the _app.tsx entry point.
We tried transpiling the modules using the next.config.js but it didn't work either.
import { Bugfender } from '@bugfender/rn-bugfender';

Bugfender.init({
appKey: 'MY_APP_KEY'
})

Or
import { Bugfender } from '@bugfender/sdk';

Bugfender.init({
appKey: 'MY_APP_KEY'
})

Transpiling the packages in the next.config.js.

Without transpiling the '@bugfender/rn-bugfender' module.

Using a react app using webpack it works fine, apparently, something is happening with the NextJS config.

Hi @juanjlunar, Bugfender is for front-end applications, so you can't run it on a Node.js server.

I managed to make it work just fine using NextJS, but I think you should add the support for NextJS, this is a frontend app.

What kind of support is missing? How did you make it work?


[SPARK-10125][Streaming]Fix a potential deadlock in JobGenerator.stop

Because lazy val uses this lock, if JobGenerator.stop and JobGenerator.doCheckpoint (JobGenerator.shouldCheckpoint has not yet been initialized) run at the same time, it may hang.
Here are the stack traces for the deadlock:
"pool-1-thread-1-ScalaTest-running-StreamingListenerSuite" #11 prio=5 os_prio=31 tid=0x00007fd35d094800 nid=0x5703 in Object.wait() [0x000000012ecaf000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        at java.lang.Thread.join(Thread.java:1245)
        - locked <0x00000007b5d8d7f8> (a org.apache.spark.util.EventLoop$$anon$1)
        at java.lang.Thread.join(Thread.java:1319)
        at org.apache.spark.util.EventLoop.stop(EventLoop.scala:81)
        at org.apache.spark.streaming.scheduler.JobGenerator.stop(JobGenerator.scala:155)
        - locked <0x00000007b5d8cea0> (a org.apache.spark.streaming.scheduler.JobGenerator)
        at org.apache.spark.streaming.scheduler.JobScheduler.stop(JobScheduler.scala:95)
        - locked <0x00000007b5d8ced8> (a org.apache.spark.streaming.scheduler.JobScheduler)
        at org.apache.spark.streaming.StreamingContext.stop(StreamingContext.scala:687)

"JobGenerator" #67 daemon prio=5 os_prio=31 tid=0x00007fd35c3b9800 nid=0x9f03 waiting for monitor entry [0x0000000139e4a000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at org.apache.spark.streaming.scheduler.JobGenerator.shouldCheckpoint$lzycompute(JobGenerator.scala:63)
        - waiting to lock <0x00000007b5d8cea0> (a org.apache.spark.streaming.scheduler.JobGenerator)
        at org.apache.spark.streaming.scheduler.JobGenerator.shouldCheckpoint(JobGenerator.scala:63)
        at org.apache.spark.streaming.scheduler.JobGenerator.doCheckpoint(JobGenerator.scala:290)
        at org.apache.spark.streaming.scheduler.JobGenerator.org$apache$spark$streaming$scheduler$JobGenerator$$processEvent(JobGenerator.scala:182)
        at org.apache.spark.streaming.scheduler.JobGenerator$$anon$1.onReceive(JobGenerator.scala:83)
        at org.apache.spark.streaming.scheduler.JobGenerator$$anon$1.onReceive(JobGenerator.scala:82)
        at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)

I can use this patch to produce this deadlock: https://github.com/zsxwing/spark/commit/8a88f28d1331003a65fabef48ae3d22a7c21f05f
And a timeout build in Jenkins due to this deadlock: https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1654/
This PR initializes checkpointWriter before eventLoop uses it to avoid this deadlock.

Merged build triggered.

Merged build started.

LGTM! Will merge when tests pass.

Test build #41296 has started for   PR 8326 at commit 7a3799b.

Test build #41296 has finished for   PR 8326 at commit 7a3799b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41296/
Test PASSed.

Merged build finished. Test PASSed.

Merging this to master and 1.5. Thanks!


Number is saved twice as high to database

Couldn't find anything about this odd issue so maybe someone here can shed light on it.
I'm running this query:
      INSERT INTO List (
        id,
        type,
        title,
        path,
        isFolder,
        trackCount,
        ordering,
        isExplicitlyExported
      )

      VALUES (
        5,
        1,
        "test",
        "test;",
        0,
        4,
        1,
        1
      )

And everything saves correctly except trackCount, it always saves 8 instead of 4  when I run this query from Nodejs. That goes for all rows that I'm saving, every value is double the actual input. Always only that field.
When I run the query with the SQLite Browser, the expected 4 is saved.
This is the table definition:
CREATE TABLE List ( [id] INTEGER, [type] INTEGER, [title] TEXT, [path] TEXT, [isFolder] NUMERIC, [trackCount] INTEGER, [ordering] INTEGER, [isExplicitlyExported] NUMERIC DEFAULT 1, PRIMARY KEY ( [id], [type] ) )

I can upload the database I'm using for this if that helps.

I've tested it with the latest sqlite3 package and it has the same issue

With an UPDATE statement the value isn't doubled but row the number is always 18 lower than the value I'm entering. If I enter 0 then it ends up as -18. If I enter 1 then it ends up as -17.
With an INSERT statement, the value is doubled.


Improve redirect treatment for clients in Quickstart.UI

I suppose the idea here is covered by #3407, but this is more focused and constrained to just the Quickstart UI.
I'm wondering about the special treatment of PKCE clients in the QuickStart UI with regard to redirecting back to the client (e.g. [1]). This special redirection treatment assumes that every PKCE client is a native client. But I think this assumption is becoming less and less true. In newer AspNet Core versions, using PKCE is a matter of setting a couple of configuration properties and adding it to older AspNet Core is not much work either [2]. It's also possible with Katana 4.1 [3]. Also, we apparently need just two grants and one of them includes PKCE and covers all kinds of apps [4] ;)
So, I wonder if there is a better differentiator than whether RequirePkce is true. Would it make sense to base the decision on what the redirect uri is? If the scheme of the redirect uri is http or https, we do a regular http redirect. Otherwise, we show the intermediate screen. The assumption then is that a native client uses Private-use URI Scheme Redirection [5].
[1] https://github.com/IdentityServer/IdentityServer4.Quickstart.UI/blob/6f187aa50f31690e44c838885b8f816c96fc417f/Quickstart/Account/AccountController.cs#L93
[2] https://www.scottbrady91.com/OpenID-Connect/ASPNET-Core-using-Proof-Key-for-Code-Exchange-PKCE
[3] https://www.scottbrady91.com/ASPNET/Refreshing-your-Legacy-ASPNET-IdentityServer-Client-Applications
[4] https://leastprivilege.com/2019/09/09/two-is-the-magic-number/
[5] https://tools.ietf.org/id/draft-ietf-oauth-native-apps-12.html#rfc.section.7.1

We improved this, so closing.


Adds open property for retrieve faces to ConcavePolygonShape

I found its lack of this property, so get_faces/set_faces looks improperly. "data" is not open for the editor. I leave it untouched cuz I think it may break the existed projects if I've removes it.

This will cause shape data to be saved twice, once as data and once as faces, no?
You should either give the new "faces" property PROPERTY_USAGE_EDITOR | NETWORK (default without storage), or make the old data property have just INTERNAL (alternatively, move it to a set() method)

Ok, I've changed it to Network. Don't know if it is the right fix.

It's weird to have two properties for the same methods, with different usage flags which basically amount to it being a "normal" bound property.
Maybe data should simply be exposed as a normal property?

Eh.. it should but for 4.0 (probably) it should be renamed to "faces"

I think it should be closed for now..


Create the file README.md

Replace the strings

PACKAGE with dust,
VERSION with 0.5.4, and
LINK with https://github.com/bootandy/dust

in the document below
https://gist.github.com/icaoberg/f9b78eef05c962445566dcc59d452b7d
and save this to a file named README.md.

README.md created


nixos/redmine: Allow importing repositories at startup

Depending on the size of the repository, the import process might take some time or might even timeout if it's done over the webserver. By enabling this option, the timeout of the systemd unit is disabled in order to not interrupt the import process and thus it's recommended to enable this option only for the initial import and to disable it afterwards.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@GrahamcOfBorg test redmine

it's recommended to enable this option only for the initial import and to disable it afterwards.

oof...

@megheaiulian look good to you?

it's recommended to enable this option only for the initial import and to disable it afterwards.

oof...

Yeah, that's because of the infinite timeout of the systemd unit. It shouldn't be configured to "infinity" forever. I agree it's a bit of a hack.
Hmm.. What I have just on my mind is a little script, that gets added to the path and basically does the same as the pre-start script. So we could just always add it and remove the option. That allows the user to start an import whenever they want and not just at startup. Though, I don't know if an important can be done that way while Redmine is running, but it's still a bit better I think.
Why do you think?

that would still be subject to the timeout limits
i am not sure but would moving the prestart stuff into it's own (oneshot) service be a good idea at this point?

that would still be subject to the timeout limits

The timeout is coming from systemd. If the import stuff is separated into it's own script, say redmine-import-repos, that the user needs to run from the shell, then there are no timeouts. Then users also can decide if they want a systemd service for that on their own.

i am not sure but would moving the prestart stuff into it's own (oneshot) service be a good idea at this point?

I think that wouldn't make much difference. The part causing the timeout is just moved to a different service, but it still needs to be configured as infinite.

that would still be subject to the timeout limits

The timeout is coming from systemd. If the import stuff is separated into it's own script, say redmine-import-repos, that the user needs to run from the shell, then there are no timeouts. Then users also can decide if they want a systemd service for that on their own.

I will play around with that in the next days and see if I can run it while Redmine is running. So one could use a systemd timer or cronjob which pulls latest changes into the repos and starts another import. Otherwise, Redmine pulls latest changes by opening the "Repository" tab and in my tests, when I had to do a full import, that killed the Redmine instance. So an automatic background import would be cool.


Doesn't work with very simple usecase

Hi,
With following:
<canvas class="my-canvas"></canvas>

<script src="anime.js"></script>
<script src="pieces.js"></script>
<script>
	var options = {
		canvas: '.my-canvas',
		text: 'Hello World',
		piecesWidth: 10,
		angle: 35
	};
	var myPieces = new Pieces(options);
	myPieces.showPieces();
</script>

I got this:

I'm using latest version of anime.js and pieces.js, btw I'm using Firefox, latest version.

It works as expected...
Please active the debug option and you can see what is happening:
https://jsfiddle.net/zetqsnku/3
Then, setting a bigger width for the canvas in CSS, and using the extraSpacing option will fix the issue:
https://jsfiddle.net/zetqsnku/7/

Actually you know the secrets of your code, so for you works as expected.
This peace of info not exist in docs, so maybe you should try to update the document.
Also the library should smart enough to run without any issue with provided options. anyway thanks for helping here.


Add Create an NFT Collection using LSP8 tutorial

Why is this not put in the Setup section of this doc?

Could you please put all the install in the setup part?


Update BATS

Description
Update the BATS submodules to the latest tags.

bats-core: v1.5.0

Motivation and Context
Just trying to get Bash It working in modern environments! If you don't know my motivation by now, I dunno what to tell you 😉
How Has This Been Tested?
Types of changes

[x] Breaking change (BATS is getting stricter and stricter!)

Checklist:

[x] My code follows the code style of this project.
[x] If my change requires a change to the documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
[x] I have added tests to cover my changes, and all the new and existing tests pass.

I'd actually like to update to master as they have significantly improved the environment in which the tests run, even without running the tests in full strict mode, but I figured that they do have regular ongoing release tags so we should probably stick to those. But I'll PR as soon as they tag the next release!


Added Vue-Meteor-Data

Can you move it to the end of the list instead, just to be fair the order is first-come-first-serve.

Sure. I mistakenly assumed the lists were sorted by most recent.


[BUG] AKV10032 when accessing key vault cross-tenant

Describe the bug
Receiving an authentication error when accessing cross-tenant Keyvault using ClientSecretCredential.
This works using legacy Microsoft.Azure.KeyVault package.
Additionally, workarounds mentioned here: https://github.com/Azure/azure-sdk-for-net/issues/11559 do not seem to work.
Expected behavior
Should be able to access key vault in another tenant when the service principal has been assigned the sufficient permissions.
Actual behavior (include Exception or Stack Trace)

Status: 401 (Unauthorized)
Content:
{"error":{"code":"Unauthorized","message":"AKV10032: Invalid issuer. Expected one....

To Reproduce
CertificateClient = new CertificateClient(new Uri(KeyVaultUrl), new ClientSecretCredential(TenantId, AppId, ClientSecret));
Where TenantId is different from the Tenant that owns the Key Vault
Environment:

Name and version of the Library package used: Azure.Security.KeyVault.Certificates 4.1.0
Hosting platform or OS and .NET runtime version: .NET Framework 4.7.2/Windows 10
IDE and version : Visual Studio 16.8.4

Thank you for your feedback.  Tagging and routing to the team best able to assist.

Any update on this particular issue?
I'm actively trying to coordinate a large migration of resources between two tenants after an acquisition.
We'd like to be able to move/re-create our applications independently from the KeyVault to minimize downtime during the migration, but it seems we can't proceed this way until this bug is resolved.

This has been enabled in Azure.Identity but needs to be enabled in Key Vault, built upon that work:

https://github.com/Azure/azure-sdk-for-net/pull/21378/files#diff-e6cdf954943d7cfe61416c460ce4b0b034d1f3821e334b4c78a3ad27a94f3961R84
https://github.com/Azure/azure-sdk-for-net/blob/e26ff0247ed6a9a08d29081ef3ccaf00bf01c68f/sdk/keyvault/Azure.Security.KeyVault.Secrets/tests/SessionRecords/SecretClientLiveTests/BackupSecret.json#L27


Couldnt understand the code in chapter-2 while separating test set

Hi Mr.Aurélien Géron,
In your book while separating the test set you have written.
def test_set_check(identifier, test_ratio, hash):
return hash(np.int64(identifier)).digest()[-1] < 256 * test_ratio
def split_train_test_by_id(data, test_ratio, id_column, hash=hashlib.md5):
ids = data[id_column]
in_test_set = ids.apply(lambda id_: test_set_check(id_, test_ratio, hash))
return data.loc[~in_test_set], data.loc[in_test_set]
Can you help me to understand how hash helps in separating the test set and avoid the problems mentioned before. In the second book you have used crc32 and the code is as following:
from zlib import crc32
def test_set_check(identifier, test_ratio):
return crc32(np.int64(identifier)) & 0xffffffff < test_ratio * 2**32
How does this equals to the above code?

He covered it pretty extensively here : https://github.com/ageron/handson-ml/issues/71


Revert "[INFINITY-1778] Insulate sdk_install from failures (#1130)"

This reverts commit f0a159709fcd9469e06b8c55d17e220871503b53.

Sadly, the dance of "what exceptions are good vs bad" is just a PITA.

retest this please

The problem with the last run was specific to helloworld which we know has unsolved problems with startup that come and go.  essentially IMO the last run was "clean", and this is good to merge.


Able to define invalid XMLs with multiple possible root nodes

Description:
$Subject
Steps to reproduce:
Run the below sample.
import ballerina/io;

public function main() {
    xml x = xml `<name>Alex</name><age>30</age>`;
    io:println(x);
}

Output:
<name>Alex</name><age>30</age>

However, this is not a valid XML since there can be multiple possible root nodes.
Affected Versions:
SLBeta3
OS, DB, other environment details and versions:
MacOS

The xml type in Ballerina represents all XML values where
An xml value is a sequence representing parsed XML, such as occurs in the content of an XML element.

See https://ballerina.io/spec/lang/master/#XML
An XML value can be a singleton of element, processing instruction, comment, and text or a sequence of multiple items. It is not required to be a valid XML document.


virtual audio device not shown on macos (sometimes)

https://discord.com/channels/1255148501793243136/1255148503081156642/1277916241960501328

fixed


Pipeline list page show pipelines of other projects

Rancher versions: mater 2_27
Steps to Reproduce:

Add a pipeline to project A
Add a pipeline to project B
Go to project A's pipeline list page

Results:
Can see pipelines of project B on the page.

Version - 2.0 master 2/27
Verified fixed


Disable unserializer

Hi,
We are using Yii framework and it has a certain peculiarity of saving url rules classes in the cache.
Like this:
   'value' => CUrlRule::__set_state(array(
       'urlSuffix' => NULL,
       'caseSensitive' => NULL,
       'defaultParams' => array(),
       'matchValue' => NULL,
       'verb' => NULL,
       'parsingOnly' => false,
       'route' => 'site/robots',
       'references' => array(),
       'routePattern' => NULL,
       'pattern' => '/^robots\\.txt\\/$/u',
       'template' => 'robots.txt',
       'params' =>array (),
       'append' => false,
       'hasHostInfo' => false,
       '_e' => NULL,
       '_m' => NULL,
    )),
  )

Now the problem is that we have implemented a function to flush all the cache values like this:
$return = $aerospike->scan($namespace, $set, function ($record) use ($aerospike) {
    echo "\n" . $record['bins']['key'] . ' [' . var_export($record['bins']['data'], true) . ']';
    $aerospike->remove($record['key']);
});

And the scan function deserializes the object saved in the cache.
When it deserializes, PHP tries to instantiate it.
If the object does not exists, it fails, because it can't find it.
How can we disable the deserialization, or better yet, how can we improve this flush values method?
Thanks so much!

Well, we solved. Basically Yii 1 hash "private classes":
http://www.yiiframework.com/forum/index.php/topic/64-yiibaseimport-support-for-multiple-classes-in-one-file/
What we have done is create our own CUrlRule and implement the same methods in a separate file to be accesible from the outside.
Not the best solution, but it works.


Catch render() call, to allow overriding.

Description
This PR changes a call in admin.py from being a direct call to django.shortcuts.render to being an indirect call, thereby allowing for the method to be overridden.
Related Issue
N/A
Motivation and Context
The problem being solved is flexibility with regards to overriding the default behavior of the admin view + form. Currently the only configuration points, are:

Providing additional context and overriding templates, or
Overriding get_form / get_formset, or
Overriding field defitinitions.

Adding the ability to override this one point, makes you able to change almost everything.
As the entire context is available, and one can simply provide any other required variables in the context, and clean them up again in the overridden render method.
The problem this solved for me, was the capability to change the generated form, not the form-class.
How Has This Been Tested?
Not a lot of tests were needed, it's a simple indirection, but I have used it to change the generated form.
Screenshots (if appropriate):
N/A
Types of changes

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

The change could potentially be changing for some users, assuming they have a method named indirect_render already.
Checklist:

[ ] I have run the make format command to format my code
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have added my name and/or github handle to AUTHORS.rst
[ ] I have added my change to CHANGES.rst
[ ] All new and existing tests passed.

i suggest self.render_history_view instead of self.indirect_render

I have no argument against that, I think that is very reasonable. - My main discussion point would however be, if more configuration points should be added, perhaps similar to the way Django views have a plethora of them.

@Skeen I wouldn't worry about similar configuration points for now (unless you need any others), but I agree with @erikvw on naming. Want to make that change, and we'll merge? Thanks!

@rossmechanic I renamed the function according to @erikvw's suggestion.

Codecov Report

Merging #530 into master will increase coverage by 0.07%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #530      +/-   ##
==========================================
+ Coverage   97.71%   97.79%   +0.07%
==========================================
  Files          17       17
  Lines         830      860      +30
  Branches      114      120       +6
==========================================
+ Hits          811      841      +30
  Misses          8        8
  Partials       11       11

Impacted Files
Coverage Δ

simple_history/admin.py
98.11% <100%> (+0.07%)
:arrow_up:

simple_history/exceptions.py
100% <0%> (ø)
:arrow_up:

...ory/management/commands/clean_duplicate_history.py
100% <0%> (ø)
:arrow_up:

simple_history/utils.py
100% <0%> (ø)
:arrow_up:

simple_history/models.py
99.03% <0%> (+0.07%)
:arrow_up:

Continue to review full report at Codecov.

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

I believe this is an issue on my end, but I seem unable to reproduce the results on travis, running:
flake8 simple_history

Produced:
$ flake8 simple_history
simple_history/admin.py:96:89: E501 line too long (103 > 88 characters)
simple_history/admin.py:202:1: W293 blank line contains whitespace
The command "flake8 simple_history" exited with 1.

On travis, however locally it produces:

Click to unfold (long)
simple_history/admin.py:1:1: D100 Missing docstring in public module
...

simple_history/admin.py:1:1: D100 Missing docstring in public module
simple_history/admin.py:23:1: D101 Missing docstring in public class
simple_history/admin.py:27:1: D401 First line should be in imperative mood
simple_history/admin.py:98:1: D102 Missing docstring in public method
simple_history/admin.py:115:1: D102 Missing docstring in public method
simple_history/admin.py:206:1: D400 First line should end with a period
simple_history/models.py:1:1: D100 Missing docstring in public module
simple_history/models.py:60:1: D101 Missing docstring in public class
simple_history/models.py:63:1: D102 Missing docstring in public method
simple_history/models.py:107:1: D102 Missing docstring in public method
simple_history/models.py:121:1: D102 Missing docstring in public method
simple_history/models.py:122:1: D400 First line should end with a period
simple_history/models.py:137:1: D102 Missing docstring in public method
simple_history/models.py:167:1: D401 First line should be in imperative mood
simple_history/models.py:167:1: D200 One-line docstring should fit on one line with quotes
simple_history/models.py:205:1: D102 Missing docstring in public method
simple_history/models.py:212:1: D401 First line should be in imperative mood
simple_history/models.py:212:1: D400 First line should end with a period
simple_history/models.py:212:1: D205 1 blank line required between summary line and description
simple_history/models.py:318:1: D202 No blank lines allowed after function docstring
simple_history/models.py:318:1: D400 First line should end with a period
simple_history/models.py:347:1: D200 One-line docstring should fit on one line with quotes
simple_history/models.py:358:1: D200 One-line docstring should fit on one line with quotes
simple_history/models.py:394:1: D401 First line should be in imperative mood
simple_history/models.py:394:1: D400 First line should end with a period
simple_history/models.py:394:1: D205 1 blank line required between summary line and description
simple_history/models.py:412:1: D102 Missing docstring in public method
simple_history/models.py:418:1: D102 Missing docstring in public method
simple_history/models.py:425:1: D102 Missing docstring in public method
simple_history/models.py:480:1: D400 First line should end with a period
simple_history/models.py:503:1: D101 Missing docstring in public class
simple_history/models.py:504:1: D102 Missing docstring in public method
simple_history/models.py:508:1: D105 Missing docstring in magic method
simple_history/models.py:513:1: D101 Missing docstring in public class
simple_history/models.py:514:1: D102 Missing docstring in public method
simple_history/models.py:537:1: D101 Missing docstring in public class
simple_history/models.py:538:1: D102 Missing docstring in public method
simple_history/models.py:544:1: D101 Missing docstring in public class
simple_history/models.py:545:1: D102 Missing docstring in public method
simple_history/middleware.py:1:1: D100 Missing docstring in public module
simple_history/middleware.py:14:1: D102 Missing docstring in public method
simple_history/middleware.py:17:1: D102 Missing docstring in public method
simple_history/exceptions.py:1:1: D200 One-line docstring should fit on one line with quotes
simple_history/exceptions.py:6:1: D400 First line should end with a period
simple_history/manager.py:1:1: D100 Missing docstring in public module
simple_history/manager.py:7:1: D101 Missing docstring in public class
simple_history/manager.py:8:1: D102 Missing docstring in public method
simple_history/manager.py:11:1: D105 Missing docstring in magic method
simple_history/manager.py:17:1: D101 Missing docstring in public class
simple_history/manager.py:18:1: D102 Missing docstring in public method
simple_history/manager.py:23:1: D102 Missing docstring in public method
simple_history/manager.py:26:1: D102 Missing docstring in public method
simple_history/manager.py:37:1: D401 First line should be in imperative mood
simple_history/manager.py:37:1: D200 One-line docstring should fit on one line with quotes
simple_history/manager.py:101:1: D202 No blank lines allowed after function docstring
simple_history/manager.py:101:1: D400 First line should end with a period
simple_history/signals.py:1:1: D100 Missing docstring in public module
simple_history/utils.py:1:1: D100 Missing docstring in public module
simple_history/utils.py:6:1: D103 Missing docstring in public function
simple_history/utils.py:38:1: D202 No blank lines allowed after function docstring
simple_history/utils.py:38:1: D400 First line should end with a period
simple_history/utils.py:38:1: D205 1 blank line required between summary line and description
simple_history/tests/view.py:1:1: D100 Missing docstring in public module
simple_history/tests/view.py:17:1: D101 Missing docstring in public class
simple_history/tests/view.py:22:1: D101 Missing docstring in public class
simple_history/tests/view.py:27:1: D101 Missing docstring in public class
simple_history/tests/view.py:32:1: D101 Missing docstring in public class
simple_history/tests/view.py:37:1: D101 Missing docstring in public class
simple_history/tests/view.py:42:1: D101 Missing docstring in public class
simple_history/tests/view.py:47:1: D101 Missing docstring in public class
simple_history/tests/view.py:52:1: D101 Missing docstring in public class
simple_history/tests/admin.py:1:1: D100 Missing docstring in public module
simple_history/tests/admin.py:20:1: D101 Missing docstring in public class
simple_history/tests/admin.py:21:1: D102 Missing docstring in public method
simple_history/tests/admin.py:25:1: D101 Missing docstring in public class
simple_history/tests/admin.py:29:1: D101 Missing docstring in public class
simple_history/tests/admin.py:30:1: D102 Missing docstring in public method
simple_history/tests/models.py:1:1: D100 Missing docstring in public module
simple_history/tests/models.py:17:1: D101 Missing docstring in public class
simple_history/tests/models.py:23:1: D102 Missing docstring in public method
simple_history/tests/models.py:27:1: D101 Missing docstring in public class
simple_history/tests/models.py:34:1: D101 Missing docstring in public class
simple_history/tests/models.py:42:1: D101 Missing docstring in public class
simple_history/tests/models.py:45:1: D101 Missing docstring in public class
simple_history/tests/models.py:49:1: D101 Missing docstring in public class
simple_history/tests/models.py:55:1: D102 Missing docstring in public method
simple_history/tests/models.py:59:1: D101 Missing docstring in public class
simple_history/tests/models.py:60:1: D102 Missing docstring in public method
simple_history/tests/models.py:64:1: D102 Missing docstring in public method
simple_history/tests/models.py:67:1: D102 Missing docstring in public method
simple_history/tests/models.py:74:1: D101 Missing docstring in public class
simple_history/tests/models.py:79:1: D101 Missing docstring in public class
simple_history/tests/models.py:95:1: D101 Missing docstring in public class
simple_history/tests/models.py:107:1: D101 Missing docstring in public class
simple_history/tests/models.py:116:1: D101 Missing docstring in public class
simple_history/tests/models.py:120:1: D105 Missing docstring in magic method
simple_history/tests/models.py:124:1: D101 Missing docstring in public class
simple_history/tests/models.py:125:1: D102 Missing docstring in public method
simple_history/tests/models.py:143:1: D101 Missing docstring in public class
simple_history/tests/models.py:147:1: D101 Missing docstring in public class
simple_history/tests/models.py:153:1: D101 Missing docstring in public class
simple_history/tests/models.py:158:1: D102 Missing docstring in public method
simple_history/tests/models.py:165:1: D101 Missing docstring in public class
simple_history/tests/models.py:171:1: D101 Missing docstring in public class
simple_history/tests/models.py:182:1: D101 Missing docstring in public class
simple_history/tests/models.py:190:1: D101 Missing docstring in public class
simple_history/tests/models.py:194:1: D101 Missing docstring in public class
simple_history/tests/models.py:198:1: D101 Missing docstring in public class
simple_history/tests/models.py:203:1: D101 Missing docstring in public class
simple_history/tests/models.py:208:1: D101 Missing docstring in public class
simple_history/tests/models.py:212:1: D101 Missing docstring in public class
simple_history/tests/models.py:216:1: D101 Missing docstring in public class
simple_history/tests/models.py:220:1: D101 Missing docstring in public class
simple_history/tests/models.py:224:1: D101 Missing docstring in public class
simple_history/tests/models.py:228:1: D101 Missing docstring in public class
simple_history/tests/models.py:232:1: D101 Missing docstring in public class
simple_history/tests/models.py:236:1: D101 Missing docstring in public class
simple_history/tests/models.py:237:1: D101 Missing docstring in public class
simple_history/tests/models.py:241:1: D101 Missing docstring in public class
simple_history/tests/models.py:245:1: D101 Missing docstring in public class
simple_history/tests/models.py:252:1: D101 Missing docstring in public class
simple_history/tests/models.py:256:1: D101 Missing docstring in public class
simple_history/tests/models.py:264:1: D101 Missing docstring in public class
simple_history/tests/models.py:268:1: D101 Missing docstring in public class
simple_history/tests/models.py:272:1: D101 Missing docstring in public class
simple_history/tests/models.py:283:1: D101 Missing docstring in public class
simple_history/tests/models.py:287:1: D101 Missing docstring in public class
simple_history/tests/models.py:291:1: D101 Missing docstring in public class
simple_history/tests/models.py:303:1: D101 Missing docstring in public class
simple_history/tests/models.py:308:1: D101 Missing docstring in public class
simple_history/tests/models.py:312:1: D101 Missing docstring in public class
simple_history/tests/models.py:317:1: D101 Missing docstring in public class
simple_history/tests/models.py:321:1: D101 Missing docstring in public class
simple_history/tests/models.py:325:1: D101 Missing docstring in public class
simple_history/tests/models.py:330:1: D101 Missing docstring in public class
simple_history/tests/models.py:334:1: D101 Missing docstring in public class
simple_history/tests/models.py:339:1: D101 Missing docstring in public class
simple_history/tests/models.py:346:1: D101 Missing docstring in public class
simple_history/tests/models.py:352:1: D101 Missing docstring in public class
simple_history/tests/models.py:360:1: D101 Missing docstring in public class
simple_history/tests/models.py:372:1: D101 Missing docstring in public class
simple_history/tests/models.py:375:1: D101 Missing docstring in public class
simple_history/tests/models.py:379:1: D101 Missing docstring in public class
simple_history/tests/models.py:382:1: D101 Missing docstring in public class
simple_history/tests/models.py:386:1: D101 Missing docstring in public class
simple_history/tests/models.py:387:1: D101 Missing docstring in public class
simple_history/tests/models.py:391:1: D101 Missing docstring in public class
simple_history/tests/models.py:395:1: D101 Missing docstring in public class
simple_history/tests/models.py:399:1: D101 Missing docstring in public class
simple_history/tests/models.py:402:1: D101 Missing docstring in public class
simple_history/tests/models.py:406:1: D101 Missing docstring in public class
simple_history/tests/models.py:409:1: D101 Missing docstring in public class
simple_history/tests/models.py:413:1: D101 Missing docstring in public class
simple_history/tests/models.py:417:1: D101 Missing docstring in public class
simple_history/tests/models.py:421:1: D101 Missing docstring in public class
simple_history/tests/models.py:425:1: D101 Missing docstring in public class
simple_history/tests/models.py:429:1: D101 Missing docstring in public class
simple_history/tests/models.py:433:1: D101 Missing docstring in public class
simple_history/tests/models.py:437:1: D101 Missing docstring in public class
simple_history/tests/models.py:441:1: D101 Missing docstring in public class
simple_history/tests/models.py:445:1: D101 Missing docstring in public class
simple_history/tests/models.py:452:1: D101 Missing docstring in public class
simple_history/tests/models.py:463:1: D103 Missing docstring in public function
simple_history/tests/models.py:470:1: D101 Missing docstring in public class
simple_history/tests/models.py:483:1: D103 Missing docstring in public function
simple_history/tests/models.py:490:1: D101 Missing docstring in public class
simple_history/tests/models.py:493:1: D102 Missing docstring in public method
simple_history/tests/models.py:504:1: D101 Missing docstring in public class
simple_history/tests/models.py:509:1: D101 Missing docstring in public class
simple_history/tests/models.py:520:1: D101 Missing docstring in public class
simple_history/tests/models.py:533:1: D101 Missing docstring in public class
simple_history/tests/models.py:542:1: D101 Missing docstring in public class
simple_history/tests/models.py:547:1: D101 Missing docstring in public class
simple_history/tests/models.py:552:1: D101 Missing docstring in public class
simple_history/tests/models.py:557:1: D101 Missing docstring in public class
simple_history/tests/models.py:562:1: D101 Missing docstring in public class
simple_history/tests/urls.py:1:1: D100 Missing docstring in public module
simple_history/tests/other_admin.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_admin.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_admin.py:35:1: D103 Missing docstring in public function
simple_history/tests/tests/test_admin.py:52:1: D101 Missing docstring in public class
simple_history/tests/tests/test_admin.py:53:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:56:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:62:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:70:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:88:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:109:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:127:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:137:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:142:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:147:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:156:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:199:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:217:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:225:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_admin.py:234:1: D400 First line should end with a period
simple_history/tests/tests/test_admin.py:240:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:250:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:265:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:271:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:288:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:311:1: D400 First line should end with a period
simple_history/tests/tests/test_admin.py:326:1: D400 First line should end with a period
simple_history/tests/tests/test_admin.py:341:1: D209 Multi-line docstring closing quotes should be on a separate line
simple_history/tests/tests/test_admin.py:341:1: D400 First line should end with a period
simple_history/tests/tests/test_admin.py:341:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_admin.py:353:1: D400 First line should end with a period
simple_history/tests/tests/test_admin.py:363:1: D400 First line should end with a period
simple_history/tests/tests/test_admin.py:363:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_admin.py:386:1: D400 First line should end with a period
simple_history/tests/tests/test_admin.py:386:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_admin.py:413:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:432:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:483:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:536:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:589:1: D102 Missing docstring in public method
simple_history/tests/tests/test_admin.py:644:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_utils.py:11:1: D101 Missing docstring in public class
simple_history/tests/tests/test_utils.py:12:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:21:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:27:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:31:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:40:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:44:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:50:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:60:1: D101 Missing docstring in public class
simple_history/tests/tests/test_utils.py:61:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:74:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:81:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:90:1: D102 Missing docstring in public method
simple_history/tests/tests/test_utils.py:102:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_commands.py:14:1: D103 Missing docstring in public function
simple_history/tests/tests/test_commands.py:25:1: D101 Missing docstring in public class
simple_history/tests/tests/test_commands.py:29:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:34:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:52:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:60:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:72:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:83:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:97:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:108:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:119:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:125:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:144:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:159:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:169:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:185:1: D101 Missing docstring in public class
simple_history/tests/tests/test_commands.py:189:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:194:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:212:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:220:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:253:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:274:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:300:1: D102 Missing docstring in public method
simple_history/tests/tests/test_commands.py:327:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_models.py:92:1: D103 Missing docstring in public function
simple_history/tests/tests/test_models.py:98:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:99:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:102:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:110:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:126:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:157:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:186:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:215:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:227:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:255:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:261:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:270:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:288:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:298:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:306:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:332:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:344:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:355:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:363:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:375:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:388:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:399:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:410:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:418:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:429:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:436:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:441:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:455:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:469:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:484:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:499:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:505:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:511:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:517:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:530:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:545:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:560:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:572:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:580:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:589:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:590:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:594:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:598:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:614:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:619:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:625:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:634:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:651:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:656:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:662:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:672:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:673:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:684:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:695:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:707:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:721:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:722:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:725:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:736:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:745:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:770:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:812:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:813:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:824:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:828:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:832:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:841:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:859:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:869:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:885:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:893:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:898:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:903:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:908:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:961:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:969:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:973:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1023:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1035:1: D400 First line should end with a period
simple_history/tests/tests/test_models.py:1038:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1043:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1050:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1056:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1062:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1069:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1070:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1078:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1084:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1092:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1094:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1097:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1100:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1106:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1107:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1118:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1119:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1126:1: D200 One-line docstring should fit on one line with quotes
simple_history/tests/tests/test_models.py:1132:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1137:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1142:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1147:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1156:1: D103 Missing docstring in public function
simple_history/tests/tests/test_models.py:1161:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1162:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1169:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1176:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1185:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1194:1: D103 Missing docstring in public function
simple_history/tests/tests/test_models.py:1200:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1201:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1208:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1215:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1227:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1228:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1248:1: D400 First line should end with a period
simple_history/tests/tests/test_models.py:1248:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_models.py:1256:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1260:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1267:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1272:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1280:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1285:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1293:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1306:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1319:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1335:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1336:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1340:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1345:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1352:1: D101 Missing docstring in public class
simple_history/tests/tests/test_models.py:1353:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1361:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1371:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1381:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1389:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1397:1: D102 Missing docstring in public method
simple_history/tests/tests/test_models.py:1403:1: D102 Missing docstring in public method
simple_history/tests/tests/test_signals.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_signals.py:17:1: D101 Missing docstring in public class
simple_history/tests/tests/test_signals.py:18:1: D102 Missing docstring in public method
simple_history/tests/tests/test_signals.py:24:1: D102 Missing docstring in public method
simple_history/tests/tests/test_signals.py:41:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_manager.py:14:1: D101 Missing docstring in public class
simple_history/tests/tests/test_manager.py:17:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:35:1: D400 First line should end with a period
simple_history/tests/tests/test_manager.py:35:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_manager.py:43:1: D400 First line should end with a period
simple_history/tests/tests/test_manager.py:43:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_manager.py:51:1: D400 First line should end with a period
simple_history/tests/tests/test_manager.py:51:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_manager.py:60:1: D400 First line should end with a period
simple_history/tests/tests/test_manager.py:60:1: D205 1 blank line required between summary line and description
simple_history/tests/tests/test_manager.py:69:1: D101 Missing docstring in public class
simple_history/tests/tests/test_manager.py:70:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:80:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:87:1: D101 Missing docstring in public class
simple_history/tests/tests/test_manager.py:88:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:96:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:112:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:127:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:138:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:147:1: D102 Missing docstring in public method
simple_history/tests/tests/test_manager.py:156:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_middleware.py:16:1: D101 Missing docstring in public class
simple_history/tests/tests/test_middleware.py:17:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:22:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:35:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:45:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:63:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:78:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:110:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:125:1: D102 Missing docstring in public method
simple_history/tests/tests/test_middleware.py:137:1: D102 Missing docstring in public method
simple_history/tests/tests/test_templatetags.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/test_templatetags.py:6:1: D101 Missing docstring in public class
simple_history/tests/tests/test_templatetags.py:10:1: D101 Missing docstring in public class
simple_history/tests/tests/test_templatetags.py:11:1: D102 Missing docstring in public method
simple_history/tests/tests/test_templatetags.py:14:1: D102 Missing docstring in public method
simple_history/tests/tests/utils.py:1:1: D100 Missing docstring in public module
simple_history/tests/tests/utils.py:16:1: D101 Missing docstring in public class
simple_history/tests/tests/utils.py:17:1: D102 Missing docstring in public method
simple_history/tests/tests/utils.py:22:1: D102 Missing docstring in public method
simple_history/tests/tests/utils.py:27:1: D102 Missing docstring in public method
simple_history/tests/tests/utils.py:32:1: D102 Missing docstring in public method
simple_history/tests/external/models.py:1:1: D100 Missing docstring in public module
simple_history/tests/external/models.py:10:1: D101 Missing docstring in public class
simple_history/tests/external/models.py:13:1: D101 Missing docstring in public class
simple_history/tests/external/models.py:17:1: D101 Missing docstring in public class
simple_history/tests/external/models.py:22:1: D101 Missing docstring in public class
simple_history/tests/external/models.py:29:1: D101 Missing docstring in public class
simple_history/tests/external/models.py:34:1: D400 First line should end with a period
simple_history/tests/custom_user/admin.py:1:1: D100 Missing docstring in public module
simple_history/tests/custom_user/models.py:1:1: D100 Missing docstring in public module
simple_history/tests/custom_user/models.py:6:1: D101 Missing docstring in public class
simple_history/management/commands/populate_history.py:1:1: D100 Missing docstring in public module
simple_history/management/commands/populate_history.py:11:1: D101 Missing docstring in public class
simple_history/management/commands/populate_history.py:27:1: D102 Missing docstring in public method
simple_history/management/commands/populate_history.py:47:1: D102 Missing docstring in public method
simple_history/management/commands/populate_history.py:113:1: D202 No blank lines allowed after function docstring
simple_history/management/commands/clean_duplicate_history.py:1:1: D100 Missing docstring in public module
simple_history/management/commands/clean_duplicate_history.py:9:1: D101 Missing docstring in public class
simple_history/management/commands/clean_duplicate_history.py:18:1: D102 Missing docstring in public method
simple_history/management/commands/clean_duplicate_history.py:35:1: D102 Missing docstring in public method
simple_history/management/commands/clean_duplicate_history.py:100:1: D102 Missing docstring in public method
simple_history/templatetags/simple_history_compat.py:1:1: D100 Missing docstring in public module
simple_history/templatetags/simple_history_admin_list.py:1:1: D100 Missing docstring in public module
simple_history/templatetags/simple_history_admin_list.py:7:1: D103 Missing docstring in public function
simple_history/templatetags/getattributes.py:1:1: D100 Missing docstring in public module
simple_history/templatetags/getattributes.py:6:1: D401 First line should be in imperative mood
simple_history/templatetags/getattributes.py:6:1: D202 No blank lines allowed after function docstring
simple_history/templatetags/getattributes.py:6:1: D400 First line should end with a period
simple_history/registry_tests/models.py:1:1: D100 Missing docstring in public module
simple_history/registry_tests/tests.py:1:1: D100 Missing docstring in public module
simple_history/registry_tests/tests.py:41:1: D101 Missing docstring in public class
simple_history/registry_tests/tests.py:42:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:48:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:58:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:62:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:72:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:80:1: D101 Missing docstring in public class
simple_history/registry_tests/tests.py:81:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:85:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:90:1: D101 Missing docstring in public class
simple_history/registry_tests/tests.py:91:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:97:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:104:1: D101 Missing docstring in public class
simple_history/registry_tests/tests.py:105:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:122:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:140:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:148:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:164:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:180:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:196:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:201:1: D210 No whitespaces allowed surrounding docstring text
simple_history/registry_tests/tests.py:201:1: D400 First line should end with a period
simple_history/registry_tests/tests.py:204:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:209:1: D101 Missing docstring in public class
simple_history/registry_tests/tests.py:210:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:215:1: D102 Missing docstring in public method
simple_history/registry_tests/tests.py:221:1: D210 No whitespaces allowed surrounding docstring text
simple_history/registry_tests/tests.py:221:1: D400 First line should end with a period
simple_history/registry_tests/tests.py:224:1: D102 Missing docstring in public method
simple_history/registry_tests/migration_test_app/models.py:1:1: D100 Missing docstring in public module
simple_history/registry_tests/migration_test_app/models.py:5:1: D101 Missing docstring in public class
simple_history/registry_tests/migration_test_app/models.py:9:1: D101 Missing docstring in public class
simple_history/registry_tests/migration_test_app/models.py:13:1: D101 Missing docstring in public class
simple_history/registry_tests/migration_test_app/models.py:18:1: D101 Missing docstring in public class
simple_history/registry_tests/migration_test_app/models.py:19:1: D102 Missing docstring in public method
simple_history/registry_tests/migration_test_app/models.py:23:1: D102 Missing docstring in public method
simple_history/registry_tests/migration_test_app/models.py:26:1: D102 Missing docstring in public method
simple_history/registry_tests/migration_test_app/models.py:33:1: D101 Missing docstring in public class

Weird... @Skeen. Not sure why you see that. I don't see any flake errors locally. Maybe a config isn't being pointed to correctly?

@Skeen see the flake8 errors

@Skeen if you fix the flake8 errors i can merge this


System locks up when using limit with fzf

Hi 👋🏾 thanks for your work on this, it's really impressive.
I've just been trying to tweak the grep functionality to have some fuzzy behaviour/see how it works and just had my system hang had to kill the nvim process using the following config.

    use {
      "camspiers/snap",
      rocks = {"fzy"},
      config = function()
        local snap = require("snap")
        local limit = snap.get("consumer.limit")
        local fzf = snap.get("consumer.fzf")
        snap.register.map(
          {"n"},
          {"<leader>fs"},
          function()
            snap.run {
              prompt = "Grep",
              producer = fzf(
                limit(10000, snap.get("producer.ripgrep.vimgrep")) -- <-- this seems like the issue
              ),
              select = snap.get("select.vimgrep").select,
              multiselect = snap.get("select.vimgrep").multiselect,
              views = {snap.get("preview.vimgrep")}
            }
          end
        )
      end
    }

I might be using things incorrectly since I don't see an example of using the limit as well as the fzf consumer, was just trying to see how they can be used together.

I will have to look into this further, thanks for the report, but the first note is that it doesn't make sense to use the ripgrep.vimgrep producer with the fzf or fzy consumer added. vimgrep is already filtering because it's grepping text, and as such further filtering the input via fzf or fzy is probably not going to give you what you want. I suggest removing the fzf consumer in this case and instead just use ripgrep.vimgrep. If you need to use regular expressions etc in ripgrep you can. Closing for now, but reopen if this didn't address the issue as thing locking up is not what I want :D

@camspiers thanks for clearing things up. I realised my mistake but raised it anyway because the side effect of making this mistake is quite dramatic. Regarding ripgrep.vimgrep what I was initially trying to do was replicate, fzf.vim's Rg function which allows you to fuzzy find a string across a project. using the ripgrep.vimgrep produce doesn't quite do the same thing since the results from rg aren't can't then be filtered using fzf?
I could very easily be missing something conceptually. Is there a way to fuzzy find a string in the cwd?

I guess I don't quite understand the feature request, the syntaxes for ripgrep and fzf syntax are different, so it doesn't make sure to me that the same input prompt would drive both the ripgrep query and the fzf fuzzy filtering. I think the right approach conceptually here is to have two input fields, one for the ripgrep query and one for the fzf filtering. But I need to think through the sense of that, the same idea came up in the following reddit thread too, so I guess it is a common desire.
https://www.reddit.com/r/neovim/comments/nvl2fy/snap_a_nonblocking_finder_system_for_neovim_05/h1bqqll/?utm_source=reddit&utm_medium=web2x&context=3

Maybe the concept is like a secondary consumer, if the secondary consumer is provided the a secondary input appears, if the secondary input has content, then the secondary consumer will be be passed the primary producer as an input and take over the results buffer so you can filter further. Unsure.

https://github.com/camspiers/snap/commit/dd9e742b9c095a8a615c26b949b7aab00bb87359
I think you will like this feature.
You can now run:
  (snap.register.map
    [:n]
    [:<Leader>ff]
    (fn []
      (snap.run {:prompt :Grep
                 :producer (limit 50000 producer-vimgrep)
                 :next {:consumer fzf :config {:prompt :FZF}}
                 :select select-vimgrep.select
                 :multiselect select-vimgrep.multiselect
                 :views [preview-vimgrep]})))

And you can change arbitrary config for the next consumer. Then next consumer get provided the current results list from the results view.
This supports any kind of chaining you want.
To activate the the next consumer/config just hit  for any results view you have (provided you have configured next).

@camspiers just tried it out but can't quite get it working but need to probably spend a bit more time with it.
I've configured it as
    use {
      "camspiers/snap",
      rocks = {"fzy"},
      -- branch = "fixes/lsp-preview",
      config = function()
        local snap = require("snap")
        local limit = snap.get("consumer.limit")
        local vimgrep = snap.get("select.vimgrep")
        local fzf = snap.get("consumer.fzf")
        print("fzf: " .. vim.inspect(fzf))
        snap.register.map(
          {"n"},
          {"<leader>fs"},
          function()
            snap.run {
              prompt = "Grep",
              producer = limit(10000, snap.get("producer.ripgrep.vimgrep")),
              ["next"] = {fzf({config = {prompt = "FZF"}})},
              select = vimgrep.select,
              multiselect = vimgrep.multiselect,
              views = {snap.get("preview.vimgrep")}
            }
          end
        )
      end
    }

The FZF thing I was talking about is
function! RipgrepFzf(query, fullscreen)
  let command_fmt = 'rg --column --line-number --no-heading --color=always --smart-case -- %s || true'
  let initial_command = printf(command_fmt, shellescape(a:query))
  let reload_command = printf(command_fmt, '{q}')
  let spec = {'options': ['--phony', '--query', a:query, '--bind', 'change:reload:'.reload_command]}
  call fzf#vim#grep(initial_command, 1, fzf#vim#with_preview(spec), a:fullscreen)
endfunction

command! -nargs=* -bang RG call RipgrepFzf(<q-args>, <bang>0)

from here
I don't know about needing multiple inputs or anything or if this implementation requires that somehow. I'll be honest and say I never dug into how fzf was using ripgrep to do the grepping if things were being piped together etc.#5
I'll spend a bit more time with it once I get a chance

Tbh I hadn't really meant this as a feature request although it's definitely nice to have. If you get the chance I think it's worth trying fzf.vim's Rg command to see how the flow works. No pressure to implement this straight away since this isn't really what I was driving at.
Using :Rg from fzf, there is no visible secondary input or further user input required. Say I'm looking for fill_line in my repo and I typed flne after hitting Rg that would just immediately surface the function as part of the result.

next should be:
{consumer = fzf, config = {prompt = "FZF>"}}


steem-js cannot be imported into typescript project but can with js project...

Expected behavior
'npm install steem --save' should result in being able to use it from both typescript or javascript.
Actual behavior
'npm install steem --save' doesn't even work.
'npm install https://github.com/steemit/steem-js -g --save' seems to work though until you actually run 'npm dev start' when it cannot find the steem object in SteemUserButton.js, however it can when it uses generic React without Typescript.
How to reproduce
Create a typescript skeleton add steem-js via npm as above and then add to App.tsx the following line:
import 'steem';
Then run 'npm start dev'.  It fails with "Module not found: Can't resolve 'steem' in 'D:\Source\steemfiles-ts-react\src".

I am using Brave and the github version "https://github.com/steemit/steem-js".

Windows 10

The npm package is called steem. Not steem-js


What about cron-like tasks definition?

We are using taskman for support tasks on top of workers.
I don't feel safe with some kind of manual triggering for cron-like tasks from within our offices.
Had you ever think about placing some kind of mechanism for this kind of jobs?

@cusspvz I am sorry but I don't understand, taskman is designed to run a worker in background. Tasks are taken as soon as a new task is published.

@neoziro thanks for your answer! :)
taskman does its job flawless, by executing pontual tasks. My question is: Have you ever think to support schedule tasks on taskman?

@cusspvz ah OK, no I do not plan to add this support to taskman, sorry.

Thanks anyway!!
Also thanks for providing taskman as open-source, you did a great job!! :)


[Bug]:  AppException: non-zero custom status code considered fatal, link to server logs: null

What happened?
Hello !
I tried to run my app on old android devices, a samung tablet running on Android 7.0 but I was unable to connect.
I then tried to reproduce on the android emulator (api level 24, android 7.0 nougat) and it still didn't work.
I only got the error mentioned on the bug title.
I tried with an older version of realm (0.3.1) and got nearly the same error : RealmException: non-zero custom status code considered fatal. (Not sure for error text on 0.3.1, but it should be that)
My app is still in development, but it currently work well on Tiramisu (api level 33) on emulator and on my samsung phone (android 12.0)
I didn't manage to find if you only support specific android version, so I created a bug here.
Repro steps
https://github.com/geosebas/flutter_realm_auth
Just add your realm app id on main.dart, run and try to login (on my app, I already have an user so didn't try to register on this repo)
Version
0.7.0rc
What Realm SDK flavor are you using?
MongoDB Atlas (i.e. Sync, auth, functions)
What type of application is this?
Flutter Application
Client OS and version
Android 7.0
Code snippets
No response
Stacktrace of the exception/crash you're getting
No response
Relevant log output
No response

Hi @geosebas,
This error is usually returned if your device has no connection to Atlas services.
Are you sure you have an internet connection on the devices you are testing with?

Hi @desistefanova,
That's one of the first I checked but I'm connected to internet on the device and the permissions have been added to android manifest so it should be ok.
The only thing that seems to have changed is the android version, otherwise it's the same code, same permissions.

The issue may be related to the fact older android versions don't trust the LetsEncrypt certificate being used on cloud. If that's the case, you may need to provide a custom http client when constructing the AppConfiguration and configure it to trust the certificate used on Cloud.

Hi @nirinchev,
Thanks it's resolved now !
With this clue I found this : https://stackoverflow.com/questions/69511057/flutter-on-android-7-certificate-verify-failed-with-letsencrypt-ssl-cert-after-s
IMHO, it should either be added in your documentation or directly implemented in your code. Or at least provide a better explanation when throwing the error.
Again, thanks a lot !

Glad we were able to help. Closing this now.


[Tabs] Height defined by the tallest tab

Bug, feature request, or proposal:
A way to tell MatTabGroup that its height should be set to the height of the tab with the greatest height value.
What is the expected behavior?
Having a way (maybe an @Input property) to tell MatTabGroup to set its height to be the same as the MatTab with the greatest height.
What is the current behavior?
Without this feature, the container of MatTabGroup can potencially change size when you switch tabs. In some situations it's not a desirable behavior:

What is the use-case or motivation for changing an existing behavior?
Better UX

Is there any benefit to having this as an API vs. setting an explicit height for the tab group?

Is there any benefit to having this as an API vs. setting an explicit height for the tab group?

Well, I'm having some second thoughts... suposing we have, for example, like the gif I pasted above, a table that can grow inside a tab.

If you set an explicit height, you won't let the tab grow with its contents and will see the scrolling bars when needed.
If you do not set its height and let it grow with its content, you will push down any content below the MatTabGroup. And this content would move up and down when you switch among different height tabs.
If we have the requested feature, we would avoid this "jumping behavior" of the content bellow MatTabGroup. But it should be optional:

The UX would be terrible if the user switched to a shorter tab and didn't see the content below MatTabGroup because a longer content tab would have pushed it far below the screen (but it seems to me that is not a good idea to put things below a MatTabGroup that can grow indefinitelly)
But it makes sense with components like a dialog, which have an action row that will always be in the visible area of the screen and you want to allow the dialog's height to grow to the screen size in different display sizes. Maybe I could use a worst-case design and define a height to fit the smallest desktops screen size to avoid problems in this case, not sure if it would be better or worse than what I did.

Ok... It appears this is not broad-use feature. It looks like to be a problem just with small dialogs when is not so difficult to forseen a height for the MatTabGroup. Right now I'm not sure it's worth the effort to modify the API. It's a nice-to-have feature, not something that is killing designs.

@julianobrasil does dynamicHeight help here, at least visually? It should add an animation when the height changes.
Also I think you could accomplish this all with css such that the dialog never grows more than 100vh and anything more requires scrolling in the tab body or dialog body.
I do like the idea of defining the body to the size of the largest tab body, but it wouldn't play great with lazy tabs and, as you mentioned, doesn't offer a great solution for tab bodies that have dynamic content, like tables.

@willshowell, I had tried dynamicHeight, but it didn't make it much better.
As it is a very simple case, I used a fixed height (320px). It satisfactory solved the problem (but I'll also try out a complete layout change in this case - maybe the main problem is not the lack of this feature, but a bad layout).

it wouldn't play great with lazy

Yeah, in cases like that the actual height would have to be recalculated every time any change took place in a tab body.

Closing since it addresses a fairly small edge case and we'd prefer to keep the API as is


Example in readme does not work

Here's my file file.py:
import math

def foo(x):
    return math.sin(x) + math.cos(x)

Here I run the code from README.md:
Python 3.6.4 (default, Apr 22 2019, 17:19:59)
[GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-9<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import list_imports
>>> imports = list_imports.get(open("file.py").read())
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/peter/.pyenv/versions/3.6.4/lib/python3.6/site-packages/list_imports/__init__.py", line 8, in get
    code = open(path).read()
FileNotFoundError: [Errno 2] No such file or directory: 'import math\n\n\ndef foo(x):\n    return math.sin(x) + math.cos(x)\n'

thx. fixed


angular-input-masks-standalone doesnt work with requirejs

Added angular-input-masks-standalone in requirejs config.
gives the following error on load:
angular-input-masks-standalone.js:3969 Uncaught TypeError: StringMask is not a constructor
angular: 1.3.13
angular-input-masks: 2.0.0

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/32283530-angular-input-masks-standalone-doesnt-work-with-requirejs?utm_campaign=plugin&utm_content=tracker%2F1022469&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1022469&utm_medium=issues&utm_source=github).

same here 2.2.0

this works:
require.config({
	paths: {
		'angular': 'js/libs/angular/angular.min',
		'moment': 'js/libs/moment/moment.min',
		'string-mask': 'js/libs/string-mask/string-mask',
		'br-validations': 'js/libs/br-validations/br-validations',
		'angular-input-masks': 'js/libs/angular-input-masks/angular-input-masks',
	},
	shim: {
		'angular-input-masks': ['angular', 'string-mask', 'moment', 'br-validations'],
		'angular': {exports: 'angular'}
	},
	baseUrl: '/static'
});

require(['modules/app'], function(app) {
	app.init();
});

But we actually need to do this imports in a different way inside the npm module.
Seems like requireJS is not doing his job there

as a final note: don't use angular-input-masks on a requirejs based application.

There is a workaround that did the trick for me, i imagine it could help someone...
/** Workaround to make angular-input-mask work with requirejs  */
var _require = require;

require.config({
    waitSeconds: 15,

    baseUrl: "",

    paths: {
        'angular-input-masks': 'assets/libs/angular-input-masks/angular-input-masks',
        'string-mask': 'assets/libs/string-mask/string-mask',
        'br-validations': 'assets/libs/br-validations/br-validations',
        'moment': 'assets/libs/moment/moment'
    },
    shim: {
        "angular": {
            exports: "angular"
        },
        'angular-input-masks': {
            deps: ['angular', 'string-mask', 'moment', 'br-validations'],
            init: function () {
                require = _require;
            }
        }
    },

    deps: ['app']
});

The two main points beeing:
• Instantiate a new require variable and create the init function inside 'angular-input-masks' shim, like shown above.
• You should import the angular-input-masks.js and NOT the standalone version.

On the latest version this workaround does not work anymore.


Update list of faults

Update HCE vs LitmusChaos fault list

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66fa294020084cff61dad665--harness-developer.netlify.app


Agonite player armour animation

Task description
A new metal armour type is to be added in an upcoming update: Agonite.
Made of a red metal, higher tier than iron, lower than dungium.
It will be a variant of the basic iron armour, but with the armour restyled to a more red colour, and with larger horns on the helmet than the warrior, and the armour covers more of the body.
This is largely a lot of the same work for the berserker task: https://github.com/Arcanorum/dungeonz/issues/65
Can just do this one and lay it over the base human character animation to create the berserker.
You will probably want the base human sprites to use as a guide for what it would look like when equipped by a player, as clothing items are just sprites layered over the top of the player sprite, matching the frame of the player animation.
References/notes
Iron armour sprites: https://github.com/Arcanorum/dungeonz/tree/master/client/src/assets/images/entities/clothes/iron armour
Human base sprites: https://github.com/Arcanorum/dungeonz/tree/master/client/src/assets/images/entities/characters/human base
Acceptance criteria
Visual

A set of clothing sprites for a red armour.
3 animation frames for each direction (up, down, left, right (left but flipped)), to be played in the basic humanoid animation pattern used by other entities: 1 (standing), 2 (right step), 1 (standing), 3 (left step), repeating.
Uses the DawnBringer 32 colour palette used by the rest of the sprites.
Expected files:
agonite-armour-up-1.png
agonite-armour-up-2.png
agonite-armour-up-3.png
agonite-armour-down-1.png
agonite-armour-down-2.png
agonite-armour-down-3.png
agonite-armour-left-1.png
agonite-armour-left-2.png
agonite-armour-left-3.png
agonite-armour-right-1.png
agonite-armour-right-2.png
agonite-armour-right-3.png

Code

Add agonite armour config to the server item values config list.
https://github.com/Arcanorum/dungeonz/blob/master/server/src/configs/Items.yml
Add a client config to the list of clothes that can be equipped for the new clothing set.
https://github.com/Arcanorum/dungeonz/blob/master/client/src/game/entities/characters/Clothes.js#L56

Done. Added to update 10.


[GPT-88] feat: update footnotes styling

Also, can I check if the code was adapted from anywhere?

I can't seem to remove the brackets. Code for footnote counter is from ChatGPT, code for style adapted from the wordpress website.


Add mozangle

This change is

@bors-servo r+

:pushpin: Commit de5a596 has been approved by jdm

:hourglass: Testing commit de5a5967f42c1cd8f5f2d2966740ad49cda359ed with merge 53930303ad9967535d455a58e77a87bb23cb0bf3...

:broken_heart: Test failed - status-travis

          ID: python3
    Function: pkg.installed
      Result: False
     Comment: An error was encountered while installing package(s): stdout:
              stderr: Error: python 2.7.12_1 is already installed
              To upgrade to 3.6.4_3, run `brew upgrade python`
              retcode: 1

          ID: sccache
    Function: file.managed
        Name: /usr/local/bin/sccache
      Result: False
     Comment: Failed to cache https://servo-deps.s3.amazonaws.com/sccache/2018-01-09-sccache-x86_64-apple-darwin: Error: [Errno 8] nodename nor servname provided, or not known reading https://servo-deps.s3.amazonaws.com/sccache/2018-01-09-sccache-x86_64-apple-darwin

@bors-servo retry
?

:hourglass: Testing commit de5a5967f42c1cd8f5f2d2966740ad49cda359ed with merge 94e5ca7888acf45969fa19593fc320ecd9072661...

@bors-servo retry
https://github.com/servo/saltfs/pull/807 has landed

:hourglass: Testing commit de5a5967f42c1cd8f5f2d2966740ad49cda359ed with merge 815864c8f8e9e1bf162d2e99edb95b29773713c4...

:sunny: Test successful - status-travis
Approved by: jdm
Pushing 815864c8f8e9e1bf162d2e99edb95b29773713c4 to master...


Style issue in "Create External Account" modal

Environment
Host

item
version

GROWI
3.7.4

node.js
12.16.2

npm
6.14.4

How to reproduce? (再現手順)

Go to /me
Open "External Accounts" tab.
Click "Add".

What happens? (症状)

Styling issue in modal.

What is the expected result? (期待される動作)

Fix layout style.

Thank you for reporting the issue.
This Styling issue is occurring on some layouts, island, christmas, and antarctic.
Please wait a moment for investigate and fix.


osx build fix

osx build fixed. But why this hangs even though all the tests pass? What are these duplicates which do not progress?

I removed that pull_request trigger as it did not help. Do these "posix-conan-test" etc. without "Test " name come from somewhere else than test.yml? I'm stuck here.

Ah ok, it is this: "Please remove the invalid/outdated status check in the protected branch setting of the repository settings"

Thanks for fixing this


Add new type ComponentId

This is a WIP and the current work is 90% done by ChatGPT.
I am currently busy with a few other things, so anyone can take over this PR and finish it.
Otherwise I'll get back to it when my important stuff is done.

I'll try this in the new microgrid API client.


Update README.md

Fixed a typo and also removed note about SPM not working, as it now successfully works! :)

Current coverage is 100.00%

Merging #55 into master will not affect coverage as of 8ef33ca

@@            master     #55   diff @@
======================================
  Files            4       4
  Stmts          241     241
  Branches         0       0
  Methods          0       0
======================================
  Hit            241     241
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 8ef33ca

Powered by Codecov. Updated on successful CI builds.


[enhancement]: Add the option to restart/redo the task in the queue panel

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
Adding an extra button to the task queue to redo, or add the job back into the queue as a live task. Currently there is only the option of cancel the job or the batch.

Alternatives
No response
Additional Content
No response

I think this would only be useful is when the system is low on VRAM due to other applications using it up, which sounds like a fairly rare edge case. I'm not going to close this as not-planned, but it's pretty low priority.


repo.update is missing

It seems that repo.update is currently missing, requiring a repo.remove POST followed by a repo.write POST instead of the single repo.update PUT operation. ref: http://developer.github.com/v3/repos/contents/#update-a-file

@Pomax Sounds like you've got it. Prioritising this for next release.

Bumping to 0.10.8, we really need to release 0.10.7.