text:
Use version tag instead of SHA pseudo-version for dotnet docs

Currently, the site imports the dotnet docs hugo module by pseudo-version. The pseudo-version just points to the latest commit on the main branch of paketo-buildpacks/dotnet-core. It would be a better release process to specify a version like v0.1.6. This way, the automation that updates the Hugo modules will look for new tags, rather than new commits on main. This way, documentation and features can be released in versions at the same time.

Blocked until a version (v0.1.6) of paketo-buildpacks/dotnet-core is released that includes the docs/ directory.

repo: paketo-buildpacks/paketo-website


text:
Print warning when selected runtime version is/will be going EOS

Similar to the work done in the Node.js and Go Buildpacks, we should start printing deprecation messages in all PHP buildpacks that let users select a runtime version when a dependency is/will be EOS.

This will require changes to buildpacks in the PHP language family that install dependencies:

[ ] PHP dist - Already resolved because the buildpack uses the packit.scribe.LogEmitter, which supports this automatically)
[ ] PHP composer – Blocked pending a rewrite of the composer buildpack to use packit. Once it's rewritten, it can use the packit.scribe.LogEmitter and get this functionality for free.
[ ] HTTPD – Resolved since this buildpack uses the packit.scribe.LogEmitter
[ ] NGINX – Resolved since this buildpack uses the packit.scribe.LogEmitter

@paketo-buildpacks/php-maintainers is this still an issue now that the PHP rewrite has been completed?

Yes! The new Composer CNB uses the packit.scribe.LogEmitter and leverages SelectedDependency which should solve this issue.

source: gharchive/issue

authors: fg-j kvedurmu sophiewigmore

repo: paketo-buildpacks/php

license_type: permissive

license_source: github-api


text:
Upgrade Maven to 3.6.3

Maven 3.6.2 was removed from the downloads website.

@yifeih @lwwmanning

source: gharchive/pull-request

repo: palantir/spark


text:
Add new max-import-line-length rule

It would be nice to have a larger line length limit for import rules. Depending on the project, the default max-line-length limit sometimes isn't enough.
Here's an example:
import { OrganizationErpConnectionSyncStatusComponent } from 'app/MYORG-modules/admin/pages/organizations/components/organization-erp-connection-sync-status/organization-erp-connection-sync-status.component';

Thank you!

I think this is best implemented as a new option to exempt max-line-length from checking import statements, similar to https://github.com/palantir/tslint/issues/2693. Specifying multiple max line lengths based on syntax would get overly complex.

based on above, this is a duplicate of https://github.com/palantir/tslint/issues/1872

authors: SchnWalter adidahiya

repo: palantir/tslint


text:
Better tslint.json Search Behavior

The current algorithm searches for the tslint.json file in parent directories of the current file being linted. It would be much more predictable if the search was instead from the current working directory.

I suggest we try and match whatever TypeScript (with tsconfig.json) and typescript-formatter (it searches for multiple files) do for consistency's sake.

I believe typescript-formatter uses the cwd as well.
As an example, let's say you ran this:
cd A/B
tslint ../C/someFile.ts  ../D/someFile.ts

and say there's a tslint.json file in A, B, and C. Which one would you expect to get used?

@JKillian - these are the rules that I had in mind:
https://github.com/vvakame/typescript-formatter#read-settings-rules

@myitcv Didn't see that, thanks. That sounds to me that it works more similarly to how things are happening now - search locations are based off of the location of the individual files, not the cwd when the command is run. Wonder how TS does things?

See here, specifically first couple of paragraphs

@myitcv Thanks, the TS algorithm is very similar to how I thought TSLint would do things. The advantage with the current algorithm is that theoretically you could have different configurations for different files, but I'm guessing people don't really use that "feature".

I'm guessing people don't really use that "feature".

For me it's actually the other way around.
Since a tslint.json can extend another one, it is very convenient to loosen or tighten the rules for certain directories.
And now that you can specify "exclude" in tslint.json to ignore files by matching patterns, this might be used like the .tslintignore file from another feature request.

By now, this is out of scope for the repository. See #4534. 😞

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋

authors: JKillian JoshuaKGoldberg ajafff myitcv


text:
allow functions as first argument to Object.assign

PR checklist

[x] Addresses an existing issue: #3055
[x] New feature, bugfix, or enhancement

[x] Includes tests

[x] Documentation update

Overview of change:
Permits functions as first argument to Object.assign
Is there anything you'd like reviewers to focus on?

CHANGELOG.md entry:

[bugfix] prefer-object-spread Permit functions as first argument to Object.assign

Thanks for your interest in palantir/tslint, @davidgoli! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

Thanks @davidgoli

only works for anonymous functions ?
Doesn't complain here :
export default Object.assign((args) => {
  cons.log(args);
}, log);

But does complain here :
const jos = (args) => {
  cons.log(args);
};

export default Object.assign(jos, log);

Is this a bug or by design ?

authors: ajafff davidgoli palantirtech wesleymostien


text:
improvement: allow custom config loaders

Before this PR

Configs were always loaded from hard coded file paths
After this PR

Added a new optional entry point that allows providing custom config loading functions (not necessarily even loaded from files).
==COMMIT_MSG==
allow custom config loaders
==COMMIT_MSG==
Possible downsides?

This can't be used with the provided main macro, should we add some sort of new macro or just assume anyone doing this type of configuration knows what they are doing and doesn't need it?

Needs a rebase but LGTM

@sfackler should be good to go though it looks like I invalidated the approval by force-pushing the rebase 😬

authors: afloren-palantir sfackler

repo: palantir/witchcraft-rust-server


text:
fix: add missing icons for registered services

Related Issues

Related to #144

Proposed Changes:

Add missing icons for registered services:

Testing:

n/a
Extra Notes (optional):

n/a
Checklist

[x] Related issues and proposed changes are filled
[x] Tests are defining the correct and expected behavior
[x] Code is well-documented via docstrings

Pull Request Test Coverage Report for Build 7942668271
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.873%

Totals

Change from base Build 7942635692:
0.0%

Covered Lines:
651

Relevant Lines:
697

💛  - Coveralls

authors: coveralls palazzem

repo: palazzem/ha-econnect-alarm


text:
Using pal schema with uppercase snake case tables and columns

I'm trying out Prisma+pal with a database where all tables and columns are written in uppercase snake case e.g. the AVAILABLE_PRODUCT table has a PRODUCT_ID column and so on.
model AVAILABLE_PRODUCT {
  PRODUCT_ID              Int            @id @default(autoincrement())
}

Running pal schema camel-case produces a schema.prisma file where all tables and columns are still uppercased, but with no underscore e.g.
model AVAILABLEPRODUCT {
  PRODUCTID              Int            @id @default(autoincrement())
}

I guess pal assumes that tables and columns are written in lowercase snake case, and just removes underscores and uppercases initials.
Any suggestions on how to get out of this situation? I Thought of replacing lowercase characters with uppercase before running pal schema camel-case (e.g. through a Sublime RegEx) but that would mess up types e.g. Int, which are already in the correct notation.
Thanks in advance.

I dug up a bit more. https://github.com/paljs/prisma-tools/blob/17d8c67f0da89c6c3303f269e4a010fc8135f072/packages/schema/src/camelCase.ts#L74
Using camelCase from lodash here instead of doing the work yourself would probably be enough
Welcome to Node.js v16.9.0.
Type ".help" for more information.
> const lodash = require('lodash')
undefined
> lodash.camelCase("MY_TABLE")
'myTable'

hey, @BudWhiteStudying,
I think all that I need to do is add one word
https://github.com/paljs/prisma-tools/blob/17d8c67f0da89c6c3303f269e4a010fc8135f072/packages/schema/src/camelCase.ts#L80

also when I am working I love to do all my work without external packages if this is a small work.

Ah sure, I think that would work too. I typically try to avoid reinventing the wheel by relying on external packages when they're well established, but I completely understand your point.

Please try v4.0.2

Doesn't seem to work, although I don't understand why. I did everything from scratch with a clean schema.prisma file.
npx prisma db pull
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
[...]
Introspecting based on datasource defined in prisma/schema.prisma …

✔ Introspected 8 models and wrote them into prisma/schema.prisma in 2.68s

This again generates a model like
model AVAILABLE_PRODUCT {
  PRODUCT_ID              Int            @id @default(autoincrement())
}

then I ran
npx @paljs/cli@4.0.2 schema camel-case
Prisma Schema loaded from prisma/schema.prisma
✔ Your schema converted successfully

and the result is still
model AVAILABLEPRODUCT {
  PRODUCTID              Int            @id @default(autoincrement())
}

it must give you
model AvailableProduct {
  PRODUCTId              Int            @id @default(autoincrement())
}

and this is wrong and I released another version that has a fix  v4.0.3
model AvailableProduct {
  productId Int @id @default(autoincrement()) @map("PRODUCT_ID")

  @@map("AVAILABLE_PRODUCT")
}

Now it works as intended, except for names without underscores i.e. the ID column isn't converted to id, the USER table isn't converted to User.

because we search for words have _

authors: AhmedElywa BudWhiteStudying

repo: paljs/prisma-tools

license: MIT


text:
Migrate to pyproject.toml

Modern python packaging uses pyproject.toml. Historically we had our deps in setup.py due to GitHub's dependency graph, but they've since added support for parsing deps out of pyproject.toml.
Also, this allows us to start specifying the Sphinx theme as a docs extra... this is much more idiomatic than bundling it as a git submodule.
Fix https://github.com/pallets-eco/flask-debugtoolbar/issues/191

Closing, this should be done at some point, but it's a larger task that I don't have appetite for right now, and by the time I do, I suspect the tooling will have continued to change a bit more (for example the build backends will have stabilized a bit more).
Also this PR in its current state included commits from some other unrelated PRs about fixing RTD, and I was able to figure out a way to do that leveraging our existing setup.py file... so this isn't a blocker like I originally thought.

repo: pallets-eco/flask-debugtoolbar


text:
Suggest renaming option from name to --name

Usually when I get this error message, it's because I wrote @click.option('foo') when I meant @click.option('--foo'). So this PR updates the error message to suggest the user fix that.

Reworded the message a bit, updated test, added changelog.

authors: davidism jtrakk

repo: pallets/click

license_source: bigquery


text:
from flask import current_app appears to have side effects

I have been trying to document my project with sphinx, but it seems that when sphinx reads a file that contains import current_app it breaks with the following message:
[$]>>> make html
sphinx-build -b html -d build/doctrees  -W -v source build/html
Running Sphinx v1.4.5
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 5 source files that are out of date
updating environment: 5 added, 0 changed, 0 removed
reading sources... [ 20%] index
reading sources... [ 40%] modules
reading sources... [ 60%] quizApp
Traceback (most recent call last):
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/ext/viewcode.py", line 28, in _get_full_modname
    return get_full_modname(modname, attribute)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/util/__init__.py", line 300, in get_full_modname
    __import__(modname)
TypeError: __import__() argument 1 must be string, not None
viewcode can't import None, failed with error "__import__() argument 1 must be string, not None"
Traceback (most recent call last):
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/ext/viewcode.py", line 28, in _get_full_modname
    return get_full_modname(modname, attribute)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/util/__init__.py", line 300, in get_full_modname
    __import__(modname)
TypeError: __import__() argument 1 must be string, not None
viewcode can't import None, failed with error "__import__() argument 1 must be string, not None"
Didn't find ParticipantExperiment.activities in quizApp.models
Didn't find Question.explantion in quizApp.models
Didn't find User.name in quizApp.models
Didn't find User.authenticated in quizApp.models
reading sources... [ 80%] quizApp.forms
reading sources... [100%] quizApp.views

Traceback (most recent call last):
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/cmdline.py", line 244, in main
    app.build(opts.force_all, filenames)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/application.py", line 297, in build
    self.builder.build_update()
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/builders/__init__.py", line 251, in build_update
    'out of date' % len(to_build))
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/builders/__init__.py", line 265, in build
    self.doctreedir, self.app))
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/environment.py", line 569, in update
    self._read_serial(docnames, app)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/environment.py", line 589, in _read_serial
    self.read_doc(docname, app)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/environment.py", line 742, in read_doc
    pub.publish()
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/core.py", line 217, in publish
    self.settings)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/io.py", line 49, in read
    self.parse()
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/readers/__init__.py", line 78, in parse
    self.parser.parse(self.input, document)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/__init__.py", line 172, in parse
    self.statemachine.run(inputlines, document, inliner=self.inliner)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 170, in run
    input_source=document['source'])
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
    return method(match, context, next_state)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2726, in underline
    self.section(title, source, style, lineno - 1, messages)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 327, in section
    self.new_subsection(title, lineno, messages)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection
    node=section_node, match_titles=True)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
    node=node, match_titles=match_titles)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
    return method(match, context, next_state)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2726, in underline
    self.section(title, source, style, lineno - 1, messages)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 327, in section
    self.new_subsection(title, lineno, messages)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection
    node=section_node, match_titles=True)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
    node=node, match_titles=match_titles)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
    return method(match, context, next_state)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2299, in explicit_markup
    nodelist, blank_finish = self.explicit_construct(match)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2311, in explicit_construct
    return method(self, expmatch)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2054, in directive
    directive_class, match, type_name, option_presets)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2103, in run_directive
    result = directive_instance.run()
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/ext/autodoc.py", line 1613, in run
    documenter.generate(more_content=self.content)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/ext/autodoc.py", line 963, in generate
    self.document_members(all_members)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/ext/autodoc.py", line 855, in document_members
    if cls.can_document_member(member, mname, isattr, self)]
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/ext/autodoc.py", line 1458, in can_document_member
    isdatadesc = isdescriptor(member) and not \
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/util/inspect.py", line 101, in isdescriptor
    if hasattr(safe_getattr(x, item, None), '__call__'):
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/sphinx/util/inspect.py", line 113, in safe_getattr
    if name in obj.__dict__:
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/werkzeug/local.py", line 343, in __getattr__
    return getattr(self._get_current_object(), name)
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/werkzeug/local.py", line 302, in _get_current_object
    return self.__local()
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/flask/globals.py", line 37, in _lookup_req_object
    raise RuntimeError(_request_ctx_err_msg)
RuntimeError: Working outside of request context.

This typically means that you attempted to use functionality that needed
an active HTTP request.  Consult the documentation on testing for
information about how to avoid this problem.

Exception occurred:
  File "/home/alyosha/.virtualenvs/quizApp-new/lib/python2.7/site-packages/flask/globals.py", line 37, in _lookup_req_object
    raise RuntimeError(_request_ctx_err_msg)
RuntimeError: Working outside of request context.

This typically means that you attempted to use functionality that needed
an active HTTP request.  Consult the documentation on testing for
information about how to avoid this problem.
The full traceback has been saved in /tmp/sphinx-err-iI83eY.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
make: *** [Makefile:53: html] Error 1

It looks like something weird is going on at import time with current_app. I'm not 100% sure if this is a sphinx error or flask error, but I'm leaning towards flask.
I made the following example to reproduce it.
https://github.com/PlasmaSheep/sphinx-error
Instructions for running it are in the README.md file.

at first glacne it looks like it dies at inspecting current_app, what happens if you tell sphinx to ignore the current_app member of that module?

It doesn't seem that there is a way to ignore an import in sphinx, see this question:
https://stackoverflow.com/questions/15889621/sphinx-how-to-exclude-imports-in-automodule

After some testing, it seems that this is a sphinx bug. In fact, this has been fixed in git, but not yet pushed to pypi (to be exact, sphinx 1.4.5 has the bug). I'm going to mark this closed.

@PlasmaSheep: Could you point me to the Sphinx git commit that fixed this problem? Thank you!

@MartinBorg Funny I just came across this issue today. If you still really need this working my solution was to just install the latest dev-version of sphinx via pip
pip install git+https://github.com/sphinx-doc/sphinx@stable

its occure due to : If you put statement out side of a function/methode
example:
class User_Register(Resource):
request_data = request.get_json()
print(request_data)

Obviously what you are trying to do makes no sense and isn't possible. You are defining a class and trying to assign the result of request.get_json() to a class attribute at class definition time. There is no request at that point...

authors: Karanjkarnilesh MartinBorg PlasmaSheep RonnyPfannschmidt ThiefMaster ZacBlanco abendebury

repo: pallets/flask


text:
Recommended link update for "Make the Project Installable" docs

The link to the "official packaging guide" in the "Make the Project Installable" tutorial section makes little reference to setup.py and no reference to the MANIFEST.in file.
I recommend updating the link from the "Packing Python Projects" tutorial to the "Packaging and distributing projects" guide which details usage of setup.py and the MANIFEST.in file.
I'd be happy to make a PR to update if this change is welcome.

I'd be fine with including links to both, something like "Follow this to get started, and there's more details here." Ultimately, this whole section should probably be replaced with modern project config/management tools like Flit/PDM/Poetry, but that's for me to do later.

authors: davidism nkabrown


text:
Tags following urls are being improperly escaped

See how in the code snippet below the closing anchor tag following a url is being escaped (</a> instead of ) when it should not be (Example 1). If a space is added before the closing tag (Example 2), or the https:// is dropped from the url (Example 3) the closing tag behaves as expected.
It is possible this behavior is intentional but I do not understand why.
from jinja2 import Template

# Example 1:
t = Template('https://www.google.com')
print(t.render())
# Output: https://www.google.com</a>
# Expected: https://www.google.com;

# Example 2: Adding a space after the url. This works as expected.
t = Template('https://www.google.com ')
print(t.render())
# https://www.google.com

# Example 3: Dropping the https://. This works as expected as well.
t = Template('www.google.com')
print(t.render())
# www.google.com

Environment:

Python version: 3.8.6
Jinja version: 2.11.2

I can't reproduce this issue, all the examples given work as expected. Autoescaping is not enabled by default, and even if it was it is not applied to static template data. There is something else going on with your code, not with Jinja.

Looks like this is only happening in my Jupyter notebook. If I run the same code in a python shell with the same virtual environment as my notebook, it runs as expected. Very odd.

authors: davidism kdumovic

repo: pallets/jinja


text:
Feature request: Output file selection

Expected Behavior
I want to produce multiple output files from jinja templates, and i would like to have control
over what is produced within the jinja template itself, not in my python code.
So i propose to add a new keywords (pair) like
{% output to "filename.txt" %} ... {% end output %}
which will switch the output to go into the specified filename within the given block.
Since the output file can be nesting (via macros / templates), it should be
implemented as a stack of output files (with the current output to string as the lowest element)
where the top most output file is the active one:
 ... goes to string output
{% output to "file1txt" %}
 ... goes to file1.txt
   {% output to "file2.txt" %}
 ... goes to file2.txt
   {% end output %}
 ... goes to file1.txt
{% end output %}
 ... goes to string output

With that option i can render my toplevel template:
                out = type_tmpl.render(type=type,
                                       name=type_name,
                                       schema=self._xsd,
                                       root_elem = self._xsd.elements[self._root_elem_name]
                                       )
                type_file.write(out)

and have that template create my output file set:

{% macro render_child(obj) %}
...
{% endmacro %}

{% for child in root_elem.elem_childs recursive %}
{% output to child | uniqe_filename("dita) %}
  {% render_child(child) %}
{% end output %}

Your Environment

Python version: python 3.5
Jinja version: 2.10

It's an interesting idea, but not one that I think belongs in Jinja core. Perhaps you could do this with an extension, but I personally would do this in Python.

The second part of your request, outpouring blocks to variables with filters, is already handled by set blocks


text:
layout.html v0.14.1 license

Hi,
Can you please specify which BSD applies on the file https://github.com/pallets/werkzeug/blob/0.14.1/examples/cupoftee/templates/layout.html ?
Is it the one from the LICENSE file or another ? Cause there is no version specified in the above file and from what I've noticed, there are other files, like https://github.com/pallets/werkzeug/blob/0.14.1/docs/werkzeugext.py which have an older bsd license.
Thank you

The same license as the rest of the project: BSD 3-Clause.

authors: Silviu-Caprar davidism

repo: pallets/werkzeug


text:
Script is Stopped Working

Yup.. Updated the readme

Duplicate of #45

authors: pallupz sudhir-trigyn

repo: pallupz/covid-vaccine-booking


text:
Implement globalfee module

Background
Describe the problem that we are trying to solve with this feature.
If a path to a solution is known, feel free to write it down, but have an open mind
Implement a globalfee module for Paloma https://github.com/confio/tgrade/tree/main/x/globalfee
Also see the Gaia implementation: https://github.com/cosmos/gaia/tree/main/x/globalfee
Gaia docs: https://hub.cosmos.network/main/modules/globalfee.html
Done when

[ ]  Global Fee module implemented
[ ]  Release paloma v0.11.6 with new branch with fee
[ ]  Chain halt upgrade on fee release
[ ]  Add proposal for fee on testnet

Discussed that this is not needed

repo: palomachain/paloma


text:
Restore procedure suggestions?

Hi,
fortunately, I had no need for full website restore... yet :D What would be the best procedure to perform a restore?
Regard,
Darjan

Hi, the plugin does not have a restore option. You have to replace the files/database you want to restore manually.

authors: panakour zlobec

repo: panakour/oc-backup-plugin


text:
Latest not resolving to latest

I'm noticing that the latest tag on dockerhub does not resolve to the latest image. Is this automated or do I need to do something to make this work? Please let me know. Thank you very much for all your help Pangeo!!

I'm seeing this: https://github.com/pangeo-data/pangeo-docker-images/issues/80#issuecomment-642325818. Is this still how things work? I can manually push a tag if that's the right way to go. Thanks!

I'll use the master tag. Thanks.

repo: pangeo-data/pangeo-docker-images


text:
Update status badges and colors

Fixes #127

Before

After

Cc @jbusecke

Very cool! Thanks @andersy005!

I'm going to merge this as is so i can focus on other outstanding tasks. Happy to address any additional feedback in a separate PR.


text:
109 - Turn on 'treat warnings as errors' flag for every target.

fixes #109

Current coverage is 97.40% (diff: 100%)

Merging #112 into master will increase coverage by 0.28%

@@             master       #112   diff @@
==========================================
  Files            27         27
  Lines          1039       1039
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1009       1012     +3
+ Misses           30         27     -3
  Partials          0          0

Powered by Codecov. Last update 91bde39...9a3be1a

authors: codecov-io pantuspavel

repo: pantuspavel/PPEventRegistryAPI

license: mit


text:
A small Readme Update

Hello, first thanks for the great repo and for the hard work you put in to make it easier on us 👍 ,
can you update the readme to put what versions this appintro works on like 5+ or 4+ or ? i have an application that works on android 4+ does this intro works on it ? thank you!

Let me give you a quick tip that will not only help you figure this out for this library but for many others so that you'll know what is compatible or not.
Don't take this as an insult or anything, just want to educate other developers with what I know.
When taking a look at an application, or a library in this case, look for the build.gradle file included in the app (in case of an application) or in the library directory (in case of a library) -- in AppIntro, this would be here.
Checking out the contents of this file, we see the following:
apply plugin: 'com.android.library'
apply plugin: 'maven'
apply plugin: 'signing'
apply from: 'maven-push.gradle'

android {
    compileSdkVersion 25
    buildToolsVersion "25.0.1"

    defaultConfig {
        minSdkVersion 11
        targetSdkVersion 25
        versionCode 13
        versionName "4.1.0"

        consumerProguardFiles 'consumer-proguard-rules.pro'
        vectorDrawables.useSupportLibrary = true
    }
}

dependencies {
    compile 'com.android.support:appcompat-v7:25.0.1'
    compile 'com.android.support:support-annotations:25.0.1'
}

What we care about, in the android block, are the following:
compileSdkVersion, buildToolsVersion, minSdkVersion and targetSdkVersion.

compileSdkVersion: You'll need to have this SDK version installed in order to include the library.
buildToolsVersion: These are the tools -- you'll want this as well.
minSdkVersion: This is the lowest SDK version in which the library has been tested to compile on without loosing too many features -- you can cross reference that here to figure out the Android version.
targetSdkVersion: While the library will work with the minimum SDK level above, you really want to be on the latest SDK level if possible -- this is the SDK level that the library itself is targeting; you want to have this installed.

What do you think? The above should answer your question fairly well.

Hello Avluis thank you for the helpful answer, and for the great educational information it contains 👍yeah i got the answer ! thank you again!

authors: avluis ziadkiwan

repo: paolorotolo/AppIntro


text:
Move to alloy types

move to alloy types with upcoming alloy 0.4 release
https://github.com/alloy-rs/core

@mattsse https://github.com/paradigmxyz/mev-share-rs/pull/46

authors: DaniPopes mattsse

repo: paradigmxyz/mev-share-rs


text:
Add open db transaction graph in grafana dashboard

With https://github.com/paradigmxyz/reth/pull/12273 we now have individual metrics for opened and closed transactions, including on the grafana dashboard. These metrics are both cumulative. We do however want a third line on the panel, for open - closed. This should accurately represent currently open read transactions, for example.

hey! could i take this one?

Let me try this one!

repo: paradigmxyz/reth


text:
Weird params inside send_transaction function

I try to run this method (my comment referenced below) and when it comes into method self.estimate_gas_at,  the underlying ensure_fees function return error Err(EthApiError::ConflictingFeeFieldsInRequest). I debugged and found that there is no case that all of three gas_price,  max_fee_per_gas and   max_priority_fee_per_gas is Some(...). Could anyone please help me with this point ?
And if I were wrong at some point, could anyone send me the correct parameters to pass into the send_transaction function to execute successfully? Thank you so much for the help.
Originally posted by @huongcodelight in https://github.com/paradigmxyz/reth/pull/1976#discussion_r1399010050

what price should be picked when conflicting fields are set?
send_transaction isn't really implemented because only useful for dev purposes.
there are no signers included so this is essentially a noop by default

what price should be picked when conflicting fields are set?
send_transaction isn't really implemented because only useful for dev purposes.
there are no signers included so this is essentially a noop by default

Thank you for your quick response 🙏  I use Postman to call rpc eth_sendTransaction and find this issue. Are there some relevant ways to send transactions if the way above isn't really implemented?

if you want to send real transaction to the network you should always use the send_rawTransaction endpoint that only accepts signed transactions.
if you need a node for local testing purposes, you can use anvil for example

this has been fixed via #6671

authors: huongcodelight mattsse


text:
refactor: cleanup Providererror

remove unused variants
unify variants
consistent naming: NotFound suffix

🤖 Generated by Copilot at 38beda3
This pull request refactors the ProviderError enum and the code that uses it in various modules of the reth crate. The main purpose is to improve the error handling, consistency, and flexibility of the provider interface and its implementations. The pull request also introduces a new parameter type BlockHashOrNumber that can represent either a block hash or a block number and allows the provider to handle different kinds of block identifiers. The pull request updates the code and tests in the interfaces, stages, storage, and consensus modules to use the new error and parameter types.

Codecov Report

Merging #2710 (1a9333a) into main (ca6724f) will increase coverage by 0.02%.
The diff coverage is 43.90%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main    #2710      +/-   ##
==========================================
+ Coverage   71.31%   71.33%   +0.02%
==========================================
  Files         503      503
  Lines       65068    65070       +2
==========================================
+ Hits        46400    46415      +15
+ Misses      18668    18655      -13

Flag
Coverage Δ

integration-tests
17.60% <0.00%> (+<0.01%)
:arrow_up:

unit-tests
66.27% <43.90%> (+0.02%)
:arrow_up:

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

Impacted Files
Coverage Δ

crates/consensus/beacon/src/engine/mod.rs
86.65% <0.00%> (ø)

crates/interfaces/src/provider.rs
0.00% <ø> (ø)

crates/storage/provider/src/providers/mod.rs
13.81% <0.00%> (ø)

...tes/storage/provider/src/providers/state/latest.rs
29.50% <0.00%> (ø)

crates/storage/provider/src/traits/state.rs
19.29% <0.00%> (ø)

crates/storage/provider/src/providers/database.rs
35.87% <5.88%> (-0.28%)
:arrow_down:

crates/storage/provider/src/transaction.rs
89.89% <83.33%> (+<0.01%)
:arrow_up:

crates/stages/src/pipeline/mod.rs
88.77% <100.00%> (ø)

crates/stages/src/stages/finish.rs
89.65% <100.00%> (-0.35%)
:arrow_down:

crates/stages/src/stages/headers.rs
93.98% <100.00%> (ø)

... and 3 more

... and 4 files with indirect coverage changes

authors: codecov-commenter mattsse


text:
feat(payload): make the actual payload build function generic

Should solve #4145.

@onbjerg Tell me if this is better now :)


text:
feat: implement conversion of optimism deposit tx from alloy to reth

The alloy_compat feature in reth/primitives contains conversion functions from Alloy types to Reth types. When converting transactions, the Optimism deposit tx type is currently unimplemented. This PR contains an implementation.
Questions:

How do you all like to handle tests for functions like this? I've tested manually in another crate, but to add a test directly to the alloy_compat.rs file would require importing a lot of machinery. Is there a better way to handle it?

The errors for this function are imported from Alloy, and the enum currently doesn't contain some errors I need. I've stubbed it out with inaccurate errors. I assume best process to submit PR to Alloy to add those errors, then update them here before merging?

@mattsse I think this should be good to go, pending the Alloy errors (which we're discussing here: https://github.com/alloy-rs/alloy/pull/875).
Thank you for your help with this. Please let me know if you have any other feedback — otherwise will ping you when errors are updated for final approval.

@mattsse Alloy error update was merged (https://github.com/alloy-rs/alloy/pull/875/) so updated this accordingly. It's ready to go but will need an Alloy version bump before it works.
Is best practice just to let it wait until that time, or is there another way to handle it?


text:
Fix compiler warnings and add CODEOWNERS

Replace var to <type>, because the former is deprecated.
Add CODEOWNERS

The buildkite failure looks indeed like it is the case -- Badge::meta is not properly deleted so this might be a low-priority security issue.

@sorpaas Looks like (at least at the moment) we're not relying on any meta values anywhere in the code.
This means the in case of "mapping hijacking" (creating the new badge with the same id) the meta from the old record will be inherited by the new one.
This might lead to the "read meta after deletion" bug — but is not a security concern, as long as:

We only add badges to the array with push, thus effectively never reusing the same id twice.
(a little bit more far-fetched) We don't rely on anything in those meta fields in the code, so it's not a subject for "mapping hijacking", when one legitimate cell owner sets the mapping, and then after the deletion of the record the next user is inheriting all the mappings somehow, adding them extended permissions or whatnot.

Still, maybe the "safe-deletion" (with a boolean flag deleted on the record) will be a safer alternative to the delete we have now? Like @andresilva did for SimpleOperations.sol.

Tried a version using the safe deletion method:

Changed all current if return modifier to use require. This is both more clearer for the source code and contract user -- we're already throwing errors for out of bound indexes.
Added deleted flag in Badge, and change badgeCount to be a variable to store the actual count.

I'll write a test spec for this.

authors: andresilva kirushik sorpaas

repo: parity-contracts/badge-registry


text:
frontend raise i.toJSON is not a function error

Hi guys,
I searched all over with no luck. Hope someone could shine some light on below issue.
I tried to deploy contract https://github.com/ww8912188/ink-contracts/tree/main/voting on https://paritytech.github.io/canvas-ui/#/upload.
It works smoothly for the upload process but deploy, it raise below error:

Can someone take a look at this issue? This contract works last week to my memory.
I also tried to install canvas-ui on locally with the newest release version v0.44.1. But it seems the UI looks totally different
from the one of https://paritytech.github.io/canvas-ui/#/upload, so I cannot debug my code.
Regards,
Nan

I tried to deploy it on https://polkadot.js.org/apps/#/contracts, and it seems it works smoothly.

Please try again, I believe this should be fixed now after new PR

I've tried it and it works smoothly now. Thanks kwingram25, really appreciate. Wish canvas-ui better and better. Close this issue.

repo: paritytech/canvas-ui


text:
wasm-builder stalls build

While working (mostly cargo check) on polkadot I've stumbled on a problem where the kusama-runtime (only it) build hangs. According to cargo build -vv kusama-runtime starts building in the very start and the waits for the lock on build directory.
Here is the excerpt
[kusama-runtime 0.8.25]     Blocking waiting for file lock on package cache
[rococo-v1-runtime 0.8.25]     Blocking waiting for file lock on package cache
[polkadot-test-runtime 0.8.25]     Blocking waiting for file lock on package cache
[polkadot-runtime 0.8.25]     Blocking waiting for file lock on package cache
[westend-runtime 0.8.25]     Blocking waiting for file lock on package cache
[kusama-runtime 0.8.25]     Blocking waiting for file lock on build directory

Apparently, it never actually releases this lock. Removing wbuild and wbuild-runner didn't help and has lead to inclusion failures. Removing locks across the target directory didn't help as well, but probably I missed the right one.
cargo clean saved the day, but it's really annoying to wait for the rebuild.

Is this reproducible?

just got that the second time
here is my current workflow in detail: i do cargo check --all --tests a lot (doing many changes across codebase), and when I get the first error, I ^C the build. I suspect that it is related.
Meanwhile I tried to do
find ./target -iname '.cargo-lock' -exec rm {} \;

to remove all the locks and it helps.

authors: bkchr pepyakin

repo: paritytech/substrate


text:
Update orchestrator plugin to communicate with Data-Index service

With version 0.0.8 of the backstage orchestrator plugins, we can now communicate with the platform's data-index service. This will enable to deploy and support multiple sonataflow workflows at the same time.
This issue requires a version of the operator with https://issues.redhat.com/browse/KOGITO-9888 fixed.

/lgtm

/lgtm

/lgtm

authors: dmartinol masayag pkliczewski

repo: parodos-dev/orchestrator-helm-chart


text:
Fixed bug in GammaRamp tutorial

...Which caused the lower image to be not displayed.

can you elaborate on the problem at hand? the code seems fine without your changes. (which miss the calls to glDeleteShader BTW)

Calls to glDeleteShader were the main cause of the problem, and were therefore omitted.
Since the Framework::CreateProgram function deletes all the passed shaders after the program linking, the repeated call in InitializeProgram() results in attempt of deleting already deleted shaders.
The program g_gammaProgram attempts to reuse already deleted vertexShader, which results in program linking failure, and prevents any further use of it, which eventually results in the bottom stripe not being rendered.

Since the Framework::CreateProgram function deletes all the passed shaders

missed that. thanks :+1:

repo: paroj/gltut