primordic/IssueDupesLite huggingface dataset:
Repository: palantir/tslint

Issue #656: Formatter processed on a per file basis
Created: 2015-09-13T11:15:09Z
As far as I understand, rules are run on a per file basis. This means that formatter is called once for each file.
This is a problem if for example we want to output checkstyle file, since the xml and checkstyle tag must be added by other means.
Else, we would get output such as
<?xml version="1.0" encoding="utf-8"?>
<checkstyle version="4.3">
  <file name="file1.ts">
    <error line="1" "column="1" "severity="error" "blah" />
    <error line="2" "column="1" "severity="error" "bluh" />
  </file>
</checkstyle>
<checkstyle version="4.3">
  <file name="file2.ts">
    <error line="1" "column="1" "severity="error" "blah" />
    <error line="2" "column="1" "severity="error" "bluh" />
  </file>
</checkstyle>
which is incorrect

Duplicate issue #1492: PMD formatter spamming the same file name
Created: 2016-08-18T04:38:53Z
Bug Report

TSLint version: v3.14.0
TypeScript version: v1.8.10
Running TSLint via: CLI

When one file reports more than one error:
Actual behavior
<file name="app/player/service.ts"><violation begincolumn="1" beginline="1" priority="1" rule="File missing JSDoc comment at the top-level: app/player/service.ts"> </violation></file><file name="app/player/service.ts"><violation begincolumn="1" beginline="4" priority="1" rule="Imported module is being loaded from a relative path. Please use an absolute path: import { GenericService } from &#39;../base/service&#39;;"> </violation></file>
Expected behavior
<file name="app/player/service.ts"><violation begincolumn="1" beginline="1" priority="1" rule="File missing JSDoc comment at the top-level: app/player/service.ts"> </violation><violation begincolumn="1" beginline="4" priority="1" rule="Imported module is being loaded from a relative path. Please use an absolute path: import { GenericService } from &#39;../base/service&#39;;"> </violation></file>

Closing comment (2016-08-20T16:13:00Z): Duplicate of #656
Repository: palantir/tslint

Issue #522: Excludes for variable-name
Created: 2015-07-22T23:07:42Z
I have a variable in my app that comes from a third party and needs to be named a certain way. Would it be possible to add the ability to exclude a certain variable name? Like,
"variable-name": [true,
    "TheVarName",
],
Or something like that?

Duplicate issue #1328: Add ??? flag to variable-name rule
Created: 2016-06-22T17:11:56Z
Bug Report

TSLint version: 3.10.2
TypeScript version: 1.9.0-dev.20160614-1.0
Running TSLint via: VSCode

TypeScript code being linted
export interface Foo {

}

// [tslint] variable name must be in camelcase or uppercase
export const Foo = { 
  someFunction() {}
}
Is there a better construct without hitting this warning or getting into class + static method?
how can I disable this rule only for this use case (maybe adding a bypass-overload flag)?

Closing comment (2018-11-03T18:48:24Z): Duplicate of #522
Repository: palantir/tslint

Issue #4411: [API] support a version of lint fix which has no side effects
Created: 2018-12-25T14:54:38Z
Feature request
Is your feature request that we implement a new rule?
No
Is your feature request related to a problem? Please describe.
see https://github.com/azz/prettier-tslint/blob/2edde01bca93787ca287c1c7669a5bc18e2637b4/src/run-tslint.js#L15-L19
Describe the solution you'd like
I want to an API that tslint could  return code string after fix and linter result.
const ret = linter.lintFix(inputCode,...otherArgs)

console.log(ret.code) //  the code string after fix
console.log(ret.lintResult) // the lint result before fix
console.log(ret.lintFixedResult) // the lint result after fix

// The API name proposed by me should be polished, maybe.
Describe alternatives you've considered
None
Additional context
see https://github.com/azz/prettier-tslint/blob/2edde01bca93787ca287c1c7669a5bc18e2637b4/src/run-prettier.js#L14

Duplicate issue #4434: Add option to `lint` method that skips file-writing
Created: 2019-01-03T18:30:46Z
Feature request
Is your feature request related to a problem? Please describe.
The prettier-tslint package provides a format function that is supposed to apply TSLint fixes to source code without any file-writing. Currently, this cannot be achieved with TSLint's API.
Related issue: azz/prettier-tslint#26
Describe the solution you'd like
Add an option to the Linter#lint method that skips any file-writing.
Describe alternatives you've considered
I first looked into implementing this by looking at TSLint's source code, but a lot of the necessary functionality is contained in private methods.

Closing comment (2019-01-03T18:39:51Z): Hi @aleclarson, agreed! This looks like a duplicate of #4411.
Repository: palantir/tslint

Issue #684: Imports that are exported are described as unused
Created: 2015-09-24T18:09:02Z
Given:
import * as myLib from 'myLib';

export { myLib };
tslint gives the following error:
app.ts[1, 13]: unused variable: 'myLib'

This is a legitimate way to import / export because it allows a component to be exported instead of flattening the hierarchy with a re-export (export * from 'myLib') or exporting the contents of myLib (export { myLibChild1, myLibChild2 as appChild } from 'myLib';)

Duplicate issue #897: es6 module and unused variable
Created: 2015-12-28T07:54:17Z
import a from "module";

export { a };
Error: file.ts[1, 8]: unused variable: 'a'.
Next example is OK:
import { a } from "module";

export { a };
tslint 3.2.1
tsc 1.7.5

Closing comment (2015-12-28T18:16:20Z): Thanks for the report @vasa-c! This is a duplicate of #684, so I'm going to close this issue, but I've copied your comment over to that thread so it can be easily referenced.
Repository: palantir/tslint

Issue #684: Imports that are exported are described as unused
Created: 2015-09-24T18:09:02Z
Given:
import * as myLib from 'myLib';

export { myLib };
tslint gives the following error:
app.ts[1, 13]: unused variable: 'myLib'

This is a legitimate way to import / export because it allows a component to be exported instead of flattening the hierarchy with a re-export (export * from 'myLib') or exporting the contents of myLib (export { myLibChild1, myLibChild2 as appChild } from 'myLib';)

Duplicate issue #818: `unused variable` error while accessing imports in `export` statement
Created: 2015-11-24T10:17:40Z
Hi,
I am getting following error when linting this code:
Code:
import A from './a;
import B from './b';

export { A, B };
Errors:
[1, 8]: unused variable: 'A'
[2, 8]: unused variable: 'B'

Using tslint v3.0.0.
O.

Closing comment (2015-12-18T16:14:46Z): Hi @zdychacek, thanks for the report. This is a duplicate of #684, so I'm going to close this issue. This is something that should be solved though!
Repository: palantir/tslint

Issue #785: switch-case-fall-through check failed on blocked case clauses
Created: 2015-11-07T15:27:17Z
switch (0) {
  case 0: {
    break;
  }
  default:
}

Duplicate issue #898: Switch Statement + Curley Braces: Expected Break before Case
Created: 2015-12-31T13:39:48Z
The below is very valid Javascript and TypeScript however TSLint still throws the error :(
Is there something wrong with my syntax or maybe some workaround for this?

Closing comment (2016-01-04T04:46:13Z): Thanks for the report @Think7! This is a duplicate of #785, so I'm going to close this. I noted that you would like this fixed over in that issue.
Repository: palantir/tslint

Issue #1810: trailing-comma rule should be smarter about interfaces
Created: 2016-12-01T16:01:26Z
Interfaces can be written with semicolon delimiters, comma delimiters, or no delimiter at all.
Currently, TSLint will require the following trailing comma if you don't use any delimiter, and this is awkward:
interface Post {
  title: string
  age: number,
}
Proposal: enhance the rule logic to only require the trailing comma if the other fields have trailing commas.
reported by @schickling and @Zjaaspoer in #960

Duplicate issue #2285: trailing-comma false positive
Created: 2017-03-02T11:00:25Z
Bug Report

TSLint version: 4.5.0
TypeScript version: 2.2.1
Running TSLint via: (pick one) CLI, VSCode

TypeScript code being linted
interface A {
    b: {
        c: string // ok
        d: string // [tslint] Missing trailing comma (trailing-comma)
    }
    e: string // ok
}
with tslint.json configuration:
{
    "rules": {
        "trailing-comma": [
            true,
            {
                "multiline": "always",
                "singleline": "never"
            }
        ]
    }
}
Actual behavior
Requires comma at last nested type member
Expected behavior
Should not

Closing comment (2018-11-03T20:09:35Z): duplicate of #1810

In that case, closing.
Repository: pallets-eco/flask-admin

Issue #1000: security risk: need html.escape
Created: 2015-08-20T05:39:29Z
When database fields contain html, at the moment the raw html is output in the list [edit: in the case of editable fields]. For instance, <h1>hello</h1> will be rendered in the browser as a heading (unlike how it is rendered in this sentence).

In my view, this is not a desired behavior and a security risk: think of raw JS stored in the database and rendered, raw, in the browser.
It seems to me that the output of any database field should go through html.escape before hitting the browser.
As a temporary fix, you can bypass this problem with column_formatters, but there is a related issue that I will post separately.
Edit: about the free cruise grand prize... Please let me know how to collect my prize for posting issues #1000 and #1001!
Congratulations for making it this far, and huge thanks for the mammoth effort to everyone involved.

Duplicate issue #690: Admin list view XSS
Created: 2014-11-11T16:26:39Z
Edit any model (for example User), put in email field something like: <body onload=alert('xss')>@mailinator.com. After returning to list view you'll see alert with "xss" string. I.e. Flask-Admin does not escapes content.

Closing comment (2015-08-20T07:02:41Z): @nosuchip was this related to #1000? Were you using column_editable_list?
Repository: pallets-eco/flask-admin

Issue #1043: validation disabled fields sqla
Created: 2015-09-04T12:10:51Z
Hi.
SQLA.
Just Assume ModelView used just for edit.
form_widget_args = {
'code': {'disabled': True},
'created_at': {'disabled': True}
}
code is Unique value.
During editing POST event I receive validation error.

Define field as disabled doesn't prevent from add validators into field attrs.
I should replace all validators in disabled fields

Duplicate issue #1713: Read Only field
Created: 2018-09-27T19:31:31Z
repost from #1251 (comment), but setting disabled to True causes the field on the model to be blanked out on save.

Closing comment (2018-09-28T01:13:19Z): Looks like a duplicate of: #1043
Repository: pallets-eco/flask-admin

Issue #1837: Can't configure custom url path for flask admin installation
Created: 2019-03-29T05:01:36Z
Hi,
I have flask admin app running under my domain http://10.8.10.22:8080/identity/ which is routed by Traefik.
here is my configuration for the app
admin = admin.Admin(app,'Admin',url="/identity/admin")
when i access http://10.8.10.22:8080/identity/admin i get 404. But it's accessible under http://10.8.10.22:8080/identity/identity/admin/ but with broken static file links.
I tried different combinations of url and  static_url_path , nothing seems to be working properly.
Can you help me resolve this ?

Duplicate issue #1842: Flask-Admin behind Nginx 
Created: 2019-04-08T17:36:13Z
Hello,
I have two flask apps running behind nginx. One flask app is running on port 5000 and the other (api) is running on 5001. I have two location blocks in nginx.conf. The api-app is served on server_name/api.
I can access Flask-Admin on "server_name/api/admin" but the problem is that Flask-Admin looks for static files at "server_name/admin/static", but they are available at "server_name/api/admin/static".
Is there a simple way to prefix the static_url_path with "api"?

Closing comment (2019-04-08T19:39:24Z): I see now that my issue is much the same as #1837
Repository: pallets-eco/flask-admin

Issue #1694: Add section to docs describing all available config parameters
Created: 2018-08-28T15:11:44Z
Will be great to have all flask-admin configuration parameters described in the doc, like the FLASK_ADMIN_FLUID_LAYOUT

Duplicate issue #2246: Document available configuration
Created: 2022-04-06T05:56:44Z
The available configuration keys are not listed or linked anywhere in the docs. The only way to tell seems to be to dig through the sources.

Closing comment (2022-04-06T06:01:08Z): Closing as duplicate of #1694
Repository: pallets-eco/flask-admin

Issue #369: Suggestion: change save massage
Created: 2013-11-12T21:10:29Z
Small change suggestion:
On save the message "Model was successfully saved" is flashed.
I suggest to change this line to "Record was successfully saved" or something like this.
the same for delete, update messages..
"Model" stands for a data model for the table/document not the record instance.
What do you think?

Duplicate issue #381: Nitpicking: Deletion should say "Document was deleted" vs "Model was deleted"
Created: 2013-11-20T22:12:33Z
Just to reduce any possible freakouts when performing late-night actions, I think the flashed message upon deletion of a row in the list-view should be changed to "Document was successfully deleted" instead of "Model was successfully deleted" when a row is deleted.
Not sure it's important to anyone else though.

Closing comment (2013-11-20T22:13:26Z): Duplicate of #369 - deciding how proceed there.
Repository: pallets-eco/flask-admin

Issue #2413: Error launching the examples using Python 3.12
Created: 2024-02-21T15:07:23Z
I followed the instructions for cloning the repo and running the examples in my local environment. I'm using the latest stable python (3.12). I'm getting this error when attempting to launch run_server.py in examples:
ImportError: cannot import name '_request_ctx_stack' from 'flask' (/Users/project/dev/flask-admin/venv/lib/python3.12/site-packages/flask/__init__.py)
What do I need to do differently? I'm sensing that I need to be on Python 2, based on some of what I'm reading but the requirements aren't clear. I saw somewhere that Python 3.6 or higher is being worked on? Please be clear in your docs about minimum requirements, if this is the problem.

Duplicate issue #2418:  aioflask with Flask>=3.0
Created: 2024-03-06T13:50:16Z
from flask import _request_ctx_stack

ImportError: cannot import name '_request_ctx_stack' from 'flask'
Tried fixing with miguelgrinberg/aioflask#10

Closing comment (2024-07-06T07:19:51Z): Closing as a duplicate of #2413. I think there's probably some overlap here, but if you mean something slightly different please do open another issue with some additional information.
Repository: pallets-eco/flask-admin

Issue #2423: Can't use multiple `Admin` instances with different Bootstrap themes (`FLASK_ADMIN_SWATCH`)
Created: 2024-04-03T17:22:10Z
❓  How can we use different Bootstrap themes through multiple Admin instances?
👨‍💻  This is how I tried to do it:
...
app.config['FLASK_ADMIN_SWATCH'] = 'cerulean'
admin1 = Admin(app, endpoint='admin1')
app.config['FLASK_ADMIN_SWATCH'] = 'cosmo'
admin2 = Admin(app, endpoint='admin2')
...
❌  But this does NOT work, I wrote this to clarify what I want to do with my issue.
Thanks!

Duplicate issue #895: Cannot create separate instances of Admin with different template mode
Created: 2015-06-09T06:44:05Z
Setting different template modes does not work with multiple instances like one would expect:
    admin1 = admin.Admin(app, url='/admin1')
    admin1.add_view(FirstView())

    # Create second administrative interface under /admin2
    admin2 = admin.Admin(app, url='/admin2', endpoint='admin2', template_mode='bootstrap3')
    admin2.add_view(SecondView())

The outcome is that, admin2 is still using bootstrap2.

Closing comment (2024-07-25T10:18:34Z): Related to #2423
Repository: pallets-eco/flask-admin

Issue #1405: inline_models don't work for one-to-many
Created: 2016-12-14T16:47:06Z
I've not been able to make inline_models forms for one-to-many, and I think it's linked to this line: https://github.com/flask-admin/flask-admin/blob/master/flask_admin/contrib/sqla/form.py#L561
class Company(Model):
    id = db.Column(db.Integer, primary_key=True)
    address_id = db.Column(db.Integer, db.ForeignKey('address.id'))
    address = db.relationship('Address', backref='companies')

class Address(Model):
    id = db.Column(db.Integer, primary_key=True)

class CompanyModelView(ModelView):
    inline_models = (Address, )

That gives me the following exception: Exception: Cannot find reverse relation for model <class 'app.models.address.Address'>
Wondering if I'm missing something, or if this is per design ? It seems possible to change the key resolution method there to support the one-to-many.

Duplicate issue #1717: Support for ONETOMANY for inline models
Created: 2018-10-03T19:08:48Z
I have two models: Employee and Invitation. An Employee my have many invitations. That being said I would like to simultaneously create a new Invitation as well as an associated Employee. I cannot do that since the logic is limited to MANYTOONE relationships:
        for prop in target_mapper.iterate_properties:
            if hasattr(prop, 'direction') and prop.direction.name in ('MANYTOONE', 'MANYTOMANY'):
                if issubclass(model, prop.mapper.class_):
                    reverse_prop = prop
                    break

Closing comment (2018-10-31T11:10:39Z): duplicate of #1405
Repository: pallets-eco/flask-admin

Issue #467: form_ajax_refs in mongoengine
Created: 2014-02-13T09:40:28Z
I have some reference fields inside a list of embedded documents that I would like to fill with options ... but when I try and specify them it throws this error:
File "/home/aparashar/codefreak/project-awesomeness/env-awesomeness/lib/python2.7/site-packages/flask_admin/model/widgets.py", line 63, in __call__
    data = field.loader.format(field.data)
AttributeError: 'StringField' object has no attribute 'format'

Are form_ajax_refs not supported in mongoengine / embedded documents?
class CategoryMapView(ModelView):
    form_subdocuments = {
        'spec_map': {
            'form_subdocuments': {
                None: {
                    'form_columns': ('r42spec', 'ebayspec'),
                    'form_ajax_refs':{
                        'r42spec':(udaybabu.models.R42Specification.specname)    
                    }
                }
            }

        }
    }

Is it possible to make custom ajax loaders for mongoengine? Could you point me to some docs which explain the process.
Thanks.

Duplicate issue #468: form_ajax_refs in mongoengine
Created: 2014-02-13T09:41:07Z
I have some reference fields inside a list of embedded documents that I would like to fill with options ... but when I try and specify them it throws this error:
File "/home/aparashar/codefreak/project-awesomeness/env-awesomeness/lib/python2.7/site-packages/flask_admin/model/widgets.py", line 63, in __call__
    data = field.loader.format(field.data)
AttributeError: 'StringField' object has no attribute 'format'

Are form_ajax_refs not supported in mongoengine / embedded documents?
class CategoryMapView(ModelView):
    form_subdocuments = {
        'spec_map': {
            'form_subdocuments': {
                None: {
                    'form_columns': ('r42spec', 'ebayspec'),
                    'form_ajax_refs':{
                        'r42spec':(udaybabu.models.R42Specification.specname)    
                    }
                }
            }

        }
    }

Is it possible to make custom ajax loaders for mongoengine? Could you point me to some docs which explain the process.
Thanks.

Closing comment (2014-02-13T09:43:33Z): duplicate of #467 please remove.
Repository: pallets-eco/flask-admin

Issue #286: 1.0.6 (currenetly on PyPI) fails on Python 3
Created: 2013-08-16T15:44:12Z
Hello!
I know there are a few isses like this, but it would be great if you could push the latest to PyPI! (After all, installed from github works.)
Thanks

Duplicate issue #336: Please update PyPi
Created: 2013-10-15T21:43:48Z
PyPi has codes back to 13/05. It'd be nice to update it as theres  bugfixes on the git already.

Closing comment (2013-10-15T22:04:24Z): Yeah, duplicate of #286. Release is planned for tomorrow - finishing documentation.
Repository: pantsbuild/pants

Issue #484: pants should not say success if the target doesn't exist
Created: 2014-08-14T23:39:02Z
I often fat-finger my targets, eg ./pants goal test some/typo/target:: and unfortunately pants "lies" to me and says "SUCCESS" even though there is no directory or target with that name.
For example, given the pants repo itself:
[tw-172-25-142-92 pants (master)]$ ./pants goal test some/typo/target::

16:38:16 00:00 [main]
               (To run a reporting server: ./pants goal server)
16:38:16 00:00   [bootstrap]
16:38:16 00:00   [setup]
16:38:16 00:00     [parse]
               Executing goals in phases: bootstrap -> imports -> gen -> check-exclusives -> resolve -> compile -> resources -> test
16:38:16 00:00   [bootstrap]
16:38:16 00:00     [bootstrap-jvm-tools]
16:38:16 00:00   [imports]
16:38:16 00:00     [ivy-imports]
16:38:16 00:00   [gen]
16:38:16 00:00     [thrift]
16:38:16 00:00     [scrooge]
16:38:16 00:00     [protoc]
16:38:16 00:00     [antlr]
16:38:16 00:00     [ragel]
16:38:16 00:00     [jaxb]
16:38:16 00:00     [aapt]
16:38:16 00:00   [check-exclusives]
16:38:16 00:00     [check-exclusives]
16:38:16 00:00   [resolve]
16:38:16 00:00     [ivy]
16:38:16 00:00   [compile]
16:38:16 00:00     [jvm]
16:38:16 00:00       [jvm-compilers]
16:38:16 00:00   [resources]
16:38:16 00:00     [prepare]
16:38:16 00:00   [test]
16:38:16 00:00     [pytest]
16:38:16 00:00     [junit]
16:38:16 00:00     [specs]
               SUCCESS
[tw-172-25-142-92 pants (master)]$

Duplicate issue #491: `not/a/dir::` resolves to no targets on the CLI
Created: 2014-08-17T22:47:37Z
This is as opposed to not/a/dir: which gives:
$ PANTS_DEV=1 ./pants goal test examples/tests/jade:
*** Running pants in dev mode from /home/jsirois/dev/3rdparty/pants/src/python/pants/bin/pants_exe.py ***

Exception message: BUILD file does not exist at: /home/jsirois/dev/3rdparty/pants/examples/tests/jade

Closing comment (2014-08-17T22:48:42Z): Duplicate of #484
Repository: pantsbuild/pants

Issue #13745: Java import of inner enum not inferred
Created: 2021-11-30T05:59:43Z
An import of an inner-enum from/to Java within the same package is not inferred.
import akka.http.shaded.com.twitter.hpack.HpackUtil.IndexType;
final class HpackUtil {
  ...
  enum IndexType {
    ...
  }
}
The import is extracted, but the declared type is not exposed.

Duplicate issue #13750: Scala import of Java method not inferred
Created: 2021-11-30T18:32:08Z
A Scala import like:
import akka.http.javadsl.common.RegexConverters.toScala
...for a Java method, will not be inferred.
This is likely because we don't expose all symbols from Java code currently: only types.

Closing comment (2021-11-30T23:09:16Z): This is related to #13745, in that we don't extract symbols from Java currently, only types.
Repository: pantsbuild/pants

Issue #18661: "Failed to create hardlink" due to "No such file or directory" in `2.17.0.dev`
Created: 2023-04-03T16:52:34Z
Even after #18600, there appear to be periodic "No such file or directory" errors (likely caused by #18153), similar to this one: https://github.com/pantsbuild/pants/actions/runs/4585391355/jobs/8097532089?pr=18652
AFAICT, we have only seen this on 2.17.0.dev/main, and not in 2.16.x.

Duplicate issue #18731: Intermittent (but frequent) "Failed to create hardlink" in `pantsbuild/pants` CI
Created: 2023-04-13T13:03:59Z
Describe the bug
I've had multiple pantsbuild/pants CI jobs fail with an error like:
native_engine.IntrinsicError: Failed to create hardlink to /home/runner/.cache/pants/lmdb_store/immutable/files/14/14e3ea94b57166cb1e7e429dcf13c3861ef3ba3dd773af3a52aa4dab2da10376 at /tmp/pants-sandbox-OiB1fX/src/python/pants/engine/internals/native_engine.so: No such file or directory (os error 2)

Pants version
PRs off of main branch in pantsbuild/pants
OS
Linux

Closing comment (2023-04-13T16:00:39Z): Dupe of #18661: sorry for the trouble! I've fixed the title over there. cc @thejcannon
Repository: pantsbuild/pants

Issue #3798: List in new engine with no args breaks
Created: 2016-08-18T00:14:10Z
Exception caught: (<type 'exceptions.AttributeError'>)
  File "/.../pants/src/python/pants/bin/pants_exe.py", line 50, in <module>
    main()
  File "/.../pants/src/python/pants/bin/pants_exe.py", line 44, in main
    PantsRunner(exiter).run()
  File "/.../pants/src/python/pants/bin/pants_runner.py", line 57, in run
    options_bootstrapper=options_bootstrapper)
  File "/.../pants/src/python/pants/bin/pants_runner.py", line 46, in _run
    return LocalPantsRunner(exiter, args, env, options_bootstrapper=options_bootstrapper).run()
  File "/.../pants/src/python/pants/bin/local_pants_runner.py", line 53, in run
    self._maybe_profiled(self._run)
  File "/.../pants/src/python/pants/bin/local_pants_runner.py", line 50, in _maybe_profiled
    runner()
  File "/.../pants/src/python/pants/bin/local_pants_runner.py", line 95, in _run
    result = goal_runner.run()
  File "/.../pants/src/python/pants/bin/goal_runner.py", line 243, in run
    result = self._execute_engine()
  File "/.../pants/src/python/pants/bin/goal_runner.py", line 232, in _execute_engine
    result = engine.execute(self._context, self._goals)
  File "/.../pants/src/python/pants/engine/legacy_engine.py", line 26, in execute
    self.attempt(context, goals)
  File "/.../pants/src/python/pants/engine/round_engine.py", line 224, in attempt
    goal_executor.attempt(explain)
  File "/.../pants/src/python/pants/engine/round_engine.py", line 47, in attempt
    task.execute()
  File "/.../pants/src/python/pants/task/console_task.py", line 57, in execute
    for value in self.console_output(targets):
  File "/.../pants/src/python/pants/backend/graph_info/tasks/listtargets.py", line 72, in console_output
    for target in self._targets():
  File "/.../pants/src/python/pants/backend/graph_info/tasks/listtargets.py", line 82, in _targets
    return self.context.scan().targets(predicate=lambda target: not target.is_synthetic)
  File "/.../pants/src/python/pants/goal/context.py", line 355, in scan
    build_graph.inject_address_closure(address)
  File "/.../pants/src/python/pants/build_graph/mutable_build_graph.py", line 60, in inject_address_closure
    dep_addresses = list(mapper.specs_to_addresses(target_addressable.dependency_specs,

Exception message: 'LegacyAddressMapper' object has no attribute 'specs_to_addresses'

Duplicate issue #3809: ./pants dependees ... is not working with v2 engine
Created: 2016-08-25T19:35:20Z

Closing comment (2016-08-25T19:36:46Z): This issue is reported in #3798
Repository: pantsbuild/pants

Issue #18288: Add support for ReStructured text and related Python documentation tools 
Created: 2023-02-17T20:07:59Z

Duplicate issue #18456: Python documentation tool support: ReStructured Text language/Sphinx/Etc
Created: 2023-03-09T17:21:54Z
Pants is currently of limited utility for users who want to publish Python code documentation using standard Python tools, such as Sphinx, and ReadTheDocs.
This ticket is a placeholder for scoping out support for:

ReST language support
Building docs with Sphinx under Pants
Publishing to ReadTheDocs.org/.com
Migrating the Pants documentation to ReadTheDocs, by Sphinx or some other tool

Closing comment (2023-03-13T20:53:29Z): Duplicate of #18288, but this one has more details. So, I'm closing that one.
Repository: pantsbuild/pants

Issue #15069: `isort` behavior depends on which files are available in the sandbox
Created: 2022-04-08T08:13:35Z
Describe the bug
When running isort on a single source file, the result is not always consistent compared to when running on all sources.
Pants version
2.11.0rc1, 2.12.0.dev1
OS
Mac
Additional info
Test case demonstrating this issue in #15002
It seems there are cases even in fmt that requires transitive deps to be present, not only for check.
See related comment: #14186 (comment)
I've run across this a couple of times now at work, where I have a pre-commit hook that runs on a subset of files (exactly the subset of changed files only), and fails, where as when I run by hand I usually use globs like a hammer and includes a whole lot more, which exposes this issue, due to isort not being stable for the two ways it is being invoked.

Duplicate issue #15069: `isort` behavior depends on which files are available in the sandbox
Created: 2022-04-08T08:13:35Z
Describe the bug
When running isort on a single source file, the result is not always consistent compared to when running on all sources.
Pants version
2.11.0rc1, 2.12.0.dev1
OS
Mac
Additional info
Test case demonstrating this issue in #15002
It seems there are cases even in fmt that requires transitive deps to be present, not only for check.
See related comment: #14186 (comment)
I've run across this a couple of times now at work, where I have a pre-commit hook that runs on a subset of files (exactly the subset of changed files only), and fails, where as when I run by hand I usually use globs like a hammer and includes a whole lot more, which exposes this issue, due to isort not being stable for the two ways it is being invoked.

Closing comment (2024-08-14T20:08:25Z): Hi, what's the status of this issue?  Did #19796 fix this, as the description there implies?

This change also fixes #17403 (which really is a duplicate of #15069 manifest in new and exciting ways) by de-duplicating the fix-specific batching strategy. It didn't sit right to me that in the reproduction repo we did 1 batches of 2 files for fix, but 1 batch of 4 files for lint.
Repository: pantsbuild/pants

Issue #13525: JVM: Dependency inference for dereference chains where types aren't specified
Created: 2021-11-08T16:05:58Z
This small class exists in NullInjectedIntoNoNullableTest.java in the Guice repo:
  static class FromProviderModule extends AbstractModule {
    @Override
    protected void configure() {
      bind(String.class).annotatedWith(Bar.class).toProvider(() -> null);
    }
  }

In this example, toProvider produces a Provider, which is not a dependency here, so compilation fails when an explicit dependency is not offered.

Duplicate issue #13527: JVM: (PLACEHOLDER) dependency inference with generic second-degree dependency
Created: 2021-11-08T17:22:51Z
Attempting to build guice's core/test/com/google/inject/errors leads to an error where Matcher is not provided to the compiler.

Closing comment (2021-11-08T18:29:19Z): Is this related to #13525?
Repository: pantsbuild/pants

Issue #13589: Add a `urls` field to `files` and `resources` targets
Created: 2021-11-11T19:47:19Z
Is your feature request related to a problem? Please describe.
In order to fetch a URL as part of a build, you would currently need to use an experimental_shell_command. But without additionally encoding a shasum check, this is a potential hermeticity problem in your build (as well as being more verbose than necessary).
Describe the solution you'd like
Native support for fetching URLs as inputs to a build. In order to allow marking the files as either loose files, or application-level resources (more info on the distinction), this should probably be implemented as a urls argument/field on resources and files targets.
Describe alternatives you've considered
Using experimental_shell_command and a shasum check.

Duplicate issue #13596: Add support for a `url` argument on `jvm_artifact`
Created: 2021-11-12T19:13:27Z
Pants v1 supported a url argument for the jar object, generally used for fetching local files. It is supported by coursier.
Find in page on https://v1.pantsbuild.org/build_dictionary.html for "A pre-built Maven repository dependency." for more details.

Closing comment (2021-12-01T22:24:37Z): So this would not need to include the SHA 256 and number bytes then, right? Coursier handles it, rather than our DownloadFile intrinsic. In that sense, this is not related to #13589.
Repository: parse-community/Parse-SDK-JS

Issue #2012: Expand TypeScript support
Created: 2023-09-01T00:59:28Z
New Feature / Enhancement Checklist


 I am not disclosing a vulnerability.
 I am not just asking a question.
 I have searched through existing issues.

Current Limitation
TypeScript support has been added with #1950. The next step is to expand it to more files.
Feature / Enhancement Description
Contributing

Change file extension to .ts
Remove @flow from file if it exists
Add file to ./tsconfig.json
npm run build:types
Fix types
Add / enable tests  in types/test.ts
npm run test:types
Compare types to @types/parse

Progress (1/62)

 Analytics.js
 AnonymousUtils.js
 Cloud.js
 CloudCode.js
 CoreManager.js
 CryptoController.js
 EventEmitter.js
 EventuallyQueue.js
 FacebookUtils.js
 IndexedDBStorageController.js
 InstallationController.js
 LiveQueryClient.js
 LiveQuerySubscription.js
 LocalDatastore.js
 LocalDatastoreController.js
 LocalDatastoreController.react-native.js
 LocalDatastoreUtils.js
 ObjectStateMutations.js
 OfflineQuery.js
 Parse.js
 ParseACL.js
 ParseCLP.js
 ParseConfig.js
 ParseError.js
 ParseFile.js
 ParseGeoPoint.js
 ParseHooks.js
 ParseInstallation.js
 ParseLiveQuery.js
 ParseObject.js
 ParseOp.js
 ParsePolygon.js
 ParseQuery.js
 ParseRelation.js
 ParseRole.js
 ParseSchema.js
 ParseSession.ts
 ParseUser.js
 Push.js
 RESTController.js
 SingleInstanceStateController.js
 Socket.weapp.js
 Storage.js
 StorageController.browser.js
 StorageController.default.js
 StorageController.react-native.js
 StorageController.weapp.js
 TaskQueue.js
 UniqueInstanceStateController.js
 Xhr.weapp.js
 arrayContainsObject.js
 canBeSerialized.js
 decode.js
 encode.js
 equals.js
 escape.js
 isRevocableSession.js
 parseDate.js
 promiseUtils.js
 unique.js
 unsavedChildren.js
 uuid.js
 WebSocketController

Duplicate issue #2255: `Parse.User.loginAs` method not available
Created: 2024-07-30T07:43:25Z
New Issue Checklist


 I am not disclosing a vulnerability.
 I am not just asking a question.
 I have searched through existing issues.
 I can reproduce the issue with the latest versions of Parse Server and the Parse JS SDK. 

Issue Description
"I tried to log in a user directly using the Parse.User.loginAs method in the Parse JS SDK, but it is not available. However, this feature was merged from version 4.2.0 as shown in this issue: Parse JS SDK Issue #1875."
Actual Outcome
Not able to import from Parse JS SDK
Expected Outcome
It must be available in the Parse JS SDK version 5.3.0, and users can log in with the master key using this method.
Server

Parse Server version: 7.1.0
Operating system: windows
Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local

Database

System (MongoDB or Postgres): mongodb
Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): local

Client

Parse JS SDK version: 5.3.0

Closing comment (2024-08-07T16:30:01Z): Closing as duplicate of #2012.
Repository: parse-community/Parse-SDK-JS

Issue #918: Parse.Query.toJSON() not working for aggregate query
Created: 2019-09-09T23:46:14Z
Issue Description
Parse.Query.toJSON() returns an empty query when the query is an aggregate query.
Steps to reproduce
const query = new Parse.Query("MyCollection");
const pipeline = {
    "match":{"language":{"$in":[null,"en"]}},
};
const results = await query.aggregate(pipeline);
const queryJson = query.toJSON(); // returns `{where: {}}`

Expected Results
query.toJSON() should return the aggregate query.
Actual Outcome
query.toJSON() returns {where: {}}.
Environment Setup


Server

parse-server version (Be specific! Don't say 'latest'.) : 3.8.0
Operating System:     -
Hardware:             -
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): -



JS SDK

JS SDK version: 2.7.0
Application? (Browser, Node, React-Native, etc): -



Logs/Trace

Duplicate issue #2464: `Parse.Query.readPreference` condition is missing in output of `Parse.Query.toJSON`
Created: 2025-02-22T00:06:43Z
New Issue Checklist

Report security issues confidentially.
Any contribution is under this license.
Before posting search existing issues.

Issue Description
The Parse.Query.readPreference condition is missing in the output of Parse.Query.toJSON().
Steps to reproduce
const q = new Parse.Query('Test');
q.readPreference('NEAREST');
const json = q.toJSON();

Actual Outcome
The returned JSON does not contain the read preference, but it does contain other conditions like Parse.Query.limit, etc.
Expected Outcome

Parse.Query.toJSON() should contain the read preference condition.
Parse.Query.fromJSON() should correctly parse the read preference condition.

Environment

Server

Parse JS SDK version: 6.0.0-alpha.2

Closing comment (2025-02-22T00:09:28Z): This is a JS SDK issue similar to #918
Repository: parse-community/Parse-SDK-JS

Issue #916: Uncaught TypeError: Cannot read property 'iterator' of undefined
Created: 2019-09-08T14:51:33Z
parse.weapp.js  2.7.1    (parse.weapp.min.js)
Such a problem has arisen.
unavailable
I don't know if it's just me.
Uncaught TypeError: Cannot read property 'iterator' of undefined
    at module.exports (parse.weapp.js:22990)
    at Object.256.../internals/has (parse.weapp.js:22082)
    at o (parse.weapp.js:7)
    at parse.weapp.js:7
    at Object.219.../internals/create-property-descriptor (parse.weapp.js:21330)
    at o (parse.weapp.js:7)
    at parse.weapp.js:7
    at Object.222.../internals/create-iterator-constructor (parse.weapp.js:21371)
    at o (parse.weapp.js:7)
    at parse.weapp.js:7

Duplicate issue #1127: Wechat Mini Program
Created: 2020-03-27T08:05:05Z
I use the uniapp multi platform of dcloud company to refer to the SDK of Wechat Mini Program and report the following error. What's the situation?
Version 2.11 is used, but the previous version 2.6 does not have this problem
code:
`import Parse from 'parse/weapp';
Parse.initialize('11a1c4d776cf0c86584afa2f16d79719', 'ff228d062059fbf3f38bc1c383bc7584');
error:
  #VM92 WAService.js:1 Uncaught TypeError: Function(...) is not a function
at Object.129 (vendor.js:13)
at o (vendor.js:13)
at vendor.js:13
at Object.130.regenerator-runtime (vendor.js:13)
at o (vendor.js:13)
at vendor.js:13
at Object.24../CoreManager (vendor.js:13)
at o (vendor.js:13)
at vendor.js:13
at Object.29../ParseACL (vendor.js:13)`
user Wechat development tools ,
error:
VM365:1 thirdScriptError Cannot convert undefined or null to object TypeError: Cannot convert undefined or null to object at hasOwnProperty (<anonymous>) at t.exports (http://127.0.0.1:32511/appservice/utils/weapp.js:4851:18) at Object.t.exports [as f] (http://127.0.0.1:32511/appservice/utils/weapp.js:5490:33) at t.exports (http://127.0.0.1:32511/appservice/utils/weapp.js:4731:75) at Object.365.../internals/define-well-known-symbol (http://127.0.0.1:32511/appservice/utils/weapp.js:6108:49) at u (http://127.0.0.1:32511/appservice/utils/weapp.js:28:49) at http://127.0.0.1:32511/appservice/utils/weapp.js:29:18 at Object.181.../../internals/wrapped-well-known-symbol (http://127.0.0.1:32511/appservice/utils/weapp.js:4224:7) at u (http://127.0.0.1:32511/appservice/utils/weapp.js:28:49) at http://127.0.0.1:32511/appservice/utils/weapp.js:29:18

Closing comment (2020-04-17T15:44:02Z): Duplicate #916 . Check out that thread. Feel free to debug this and find a solution. Unfortunately we can test Wechat Mini Programs.
You might might have to stay 2.6.0.

Waiting for repair

用在微信那种别扭的平台上还是最好用一个APIG来处理一下最好。
直接用SDK会有不少的问题，因为你不能将WXS和标准JS混为一谈。<[这里有介绍](https://developers.weixin.qq.com/miniprogram/dev/framework/view/wxs/)>
Repository: parse-community/Parse-SDK-JS

Issue #32: query.include is not including what it should
Created: 2015-09-30T12:42:39Z
After I changed the Parse version to 1.6.4, query.include stopped working and it is not including the data from the pointer. There was no changes to my code, only the Parse version. When I revert Parse version back to 1.6.2 query.include is works fine again, but I can't use 1.6.2 because of the Relations bug that was fixed on 1.6.4.

Duplicate issue #50: Bug on Parse.Query, trying to include keys but the server doesn't fetch the information
Created: 2015-10-13T17:56:53Z
Hello. I'm mostly Android and iOS developer. I've always created my own backend for Android or iOS, so when I had some tables with pointers and I needed the information, I used to do my query including keys by include(String string) or the iOS version: [PFObject includeKey:NSString* key] and I get my pointers fetched.
Now I'm trying to do another project, which envolves the Javascript SDK on CloudCode and the pointers were not being fetched at the end... for more details, please see my question on StackOverflow: http://stackoverflow.com/questions/33059768/parse-com-javascript-sdk-using-include-but-not-working?noredirect=1#comment54030428_33059768
Changing the file /path/to/parse_project/.parse.project (hidden), I changed the "jssdk" : "latest" for "jssdk" : "1.4.2" so basically I downgraded my version, and it works perfectly now.
So I think it's a bug in the Javascript SDK.

Closing comment (2015-10-13T18:57:36Z): Duplicate of #32
Repository: parse-community/Parse-SDK-JS

Issue #530: support WeChat small program
Created: 2017-12-07T11:09:25Z
hi~when can you support WeChat small program?
please😭

Duplicate issue #793: Want to support Wechat applet
Created: 2019-04-13T03:51:09Z
Want to support Wechat applet !!!
doc https://developers.weixin.qq.com/miniprogram/en/dev/index.html?t=19041222

Closing comment (2019-04-13T14:23:18Z): Duplicate #530
Have you read the guide Supported 3rd Party Authentication? If it is unclear please let us know.
const user = await new Parse.User()._linkWith('wechat', {
  authData: {
    id: '',
    access_token: '' // get your own access token
  }
});
Repository: parse-community/Parse-SDK-JS

Issue #528: Typescript definitions @types/parse need to be kept up to date
Created: 2017-12-05T04:28:49Z
I submitted a pull to add Parse.liveQueryServerUrl to DefinitelyTyped repo, but it would be nice if that was part of the deployment workflow

Duplicate issue #745: @type/parse mismatch
Created: 2019-03-05T23:41:41Z
Using parse@2.1.1.
Trying to use Parse.enableLocalDatastore(), but there is no definition for enableLocalDatastore.
When I look at the package.json from Library/Caches/typescript/3.3/node_modules/@types/parse, I see "_from": "@types/parse@2.1.1".
The index.d.ts file has Type definitions for parse 2.1.0 in the comments. No sign of enableLocalDatastore.
Should that definition be included in index.d.ts file?

Closing comment (2019-03-15T17:13:26Z): Duplicate: #528
Repository: parse-community/Parse-SDK-JS

Issue #372: Objects from live queries are not the correct subclass
Created: 2016-11-04T10:09:19Z
When using LiveQueries I expect the objects I get from when running find or each on the query and the object that the live queries events produces to be of the same class.
But when doing
const MyExtendedClass = Parse.Object.extend('InAppNotification', {
  getType() {
    return 'myType';
  },
}, {});
const query = new ParseQuery(MyExtendedClass);

query.each((object) => {
  // object here is ParseObjectSubclass
  // and I can use object.getType()
});

query.subscribe().on('enter', (object) => {
  // object here is ParseObject
  // and I can't use object.getType()
});
I fiddled around with it a bit and changed so that the default switch statement at https://github.com/ParsePlatform/Parse-SDK-JS/blob/master/src/LiveQueryClient.js#L390
used ParseObject.fromJSON instead like it's done in ParseQuery on https://github.com/ParsePlatform/Parse-SDK-JS/blob/master/src/ParseQuery.js#L288
and it seemed to work as I expected.
I'm not familiar enough with the parse code to know that I'm right, it might be some great reason why you can't use fromJSON at that point that I'm missing or could that be a viable solution?
I'm using Parse 1.9.1

Duplicate issue #340: LiveQueries not returning subclass of ParseObject 
Created: 2016-08-30T15:15:17Z
Hi,
I'm pretty sure this is an issue:
I have extended ParseObject (doing all it takes including registersubclass etc..)
When I do a regular query I get the proper subclass of ParseObject.
However, when I get a LiveQuery update for one of these object I get it as a ParseObject, while inside it DOES hold the subclasses of ParseObject:
(res is the result from the server, notice "to" field, which is a DbLocation object (my subclass for ParseServer)

Closing comment (2016-11-29T10:50:52Z): duplicate of #372
Repository: patroni/patroni

Issue #1977: cannot execute SQL commands in WAL sender for physical replication
Created: 2021-06-22T06:42:01Z
Can you help with this errors:
cannot execute SQL commands in WAL sender for physical replication - LEADER
Follower:
ERROR: Exception when working with master via replication connection
patroni[492]: Traceback (most recent call last):
patroni[492]:   File "/usr/local/lib/python3.7/dist-packages/patroni/postgresql/rewind.py", line 188, in check_timeline_and_Jun patroni[492]:     cur.execute('IDENTIFY_SYSTEM')
patroni[492]: psycopg2.errors.InternalError: cannot execute SQL commands in WAL sender for physical replication
patroni[492]: 2021-06-22 02:41:01,273 INFO: no action.  i am a secondary and i am following a leader

Duplicate issue #1980: "syntax error" with psycopg2 2.9.1
Created: 2021-06-23T05:40:32Z
If I update psycopg2 to version 2.9.1, Patroni and Postgres logs are filled with errors:
2021-06-23 08:17:04,060 ERROR: Can not fetch local timeline and lsn from replication connection
Traceback (most recent call last):
File "/opt/pipx/venvs/patroni/lib64/python3.6/site-packages/patroni/postgresql/__init__.py", line 738, in get_replica_timeline
psycopg2.errors.SyntaxError: syntax error

2021-06-23 08:17:03,649 ERROR: Exception when working with master via replication connection
Traceback (most recent call last):
File "/opt/pipx/venvs/patroni/lib64/python3.6/site-packages/patroni/postgresql/rewind.py", line 188, in _check_timeline_and_lsn
psycopg2.errors.SyntaxError: syntax error

Same for psycopg2-binary. I have not found version requirements, so just installed latest available.
Environment

Patroni version: 2.0.2 and 2.0.1
PostgreSQL version: 9.6
DCS (and its version): Consul 1.10.0

PostgreSQL logs
repluser@[unknown] ERROR:  syntax error

psycopg2 v2.8.6 solves the issue. I have not tested v2.9.

Closing comment (2021-06-23T05:41:46Z): Duplicate of #1977, #1969, and #1979
Repository: patroni/patroni

Issue #1388: API endpoints related to standby leader return wrong codes
Created: 2020-02-11T07:40:26Z
The REST API endpoints that indicate that a node should be able to accept read-write transactions (e.g. /read-write, /master, etc.) return 200 for a standby leader, which is in fact read-only.  These should return 503.
The REST API endpoint /standby-leader returns 200 for a master node which is not a standby leader.  This should return 503.
Tested with Patroni 1.6.1.

Duplicate issue #1646: Patroni 1.6.5 GET /standby-leader return wrong status_code for non standby cluster
Created: 2020-08-11T18:58:45Z
GET /standby-leader: returns HTTP status code 200 only when the Patroni node is running as the leader in a standby cluster.

This endpoint returns 200 for non standby Primary, as per description 200 is only when the Patroni node is running as the leader in a standby cluster.

Closing comment (2020-08-11T19:11:06Z): duplicate of #1388
Fixed in #1553