jinja2.exceptions.TemplateSyntaxError: expected token 'end of statement block', got '+'

vitex@NAX008380:~/Projects/Custom/Packaging$ cookiecutter gh:notsatan/go-template
project_name [go-template]: KbHostnames2Networks
project_description [Kbhostnames2Networks is a Go application created using https://github.com/notsatan/go-template]:
go_module_path [github.com/notsatan/go-template]: git.xx.cz/users/xxxx/repos/hostnames2networks
license_owner [notsatan]: XX a.s.
base_branch [master]:
contact_email []<EMAIL_ADDRESS>github_specific_features [y]: n
use_codecov [y]: n
use_precommit [y]: n
Select go_version:
1 - 1.17
2 - 1.16
3 - 1.18
Choose from 1, 2, 3 [1]: 2
Select license:
1 - MIT
2 - BSD-3
3 - GNU GPL v3.0
4 - Apache Software License 2.0
Choose from 1, 2, 3, 4 [1]: 1
Traceback (most recent call last):
  File "/home/vitex/.local/bin/cookiecutter", line 8, in <module>
    sys.exit(main())
  File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/vitex/.local/lib/python3.8/site-packages/cookiecutter/cli.py", line 140, in main
    cookiecutter(
  File "/home/vitex/.local/lib/python3.8/site-packages/cookiecutter/main.py", line 101, in cookiecutter
    result = generate_files(
  File "/home/vitex/.local/lib/python3.8/site-packages/cookiecutter/generate.py", line 352, in generate_files
    generate_file(
  File "/home/vitex/.local/lib/python3.8/site-packages/cookiecutter/generate.py", line 169, in generate_file
    tmpl = env.get_template(infile_fwd_slashes)
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 830, in get_template
    return self._load_template(name, self.make_globals(globals))
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 804, in _load_template
    template = self.loader.load(self, name, globals)
  File "/usr/lib/python3/dist-packages/jinja2/loaders.py", line 125, in load
    code = environment.compile(source, name, filename)
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 591, in compile
    self.handle_exception(exc_info, source_hint=source_hint)
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise
    raise value.with_traceback(tb)
  File "./Makefile", line 47, in <module>
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 497, in _parse
    return Parser(self, source, name, encode_filename(filename)).parse()
  File "/usr/lib/python3/dist-packages/jinja2/parser.py", line 901, in parse
    result = nodes.Template(self.subparse(), lineno=1)
  File "/usr/lib/python3/dist-packages/jinja2/parser.py", line 888, in subparse
    self.stream.expect('block_end')
  File "/usr/lib/python3/dist-packages/jinja2/lexer.py", line 386, in expect
    raise TemplateSyntaxError("expected token %r, got %r" %
jinja2.exceptions.TemplateSyntaxError: expected token 'end of statement block', got '+'
  File "./Makefile", line 47
    {%- endif +%}

Hi Vitexus, I tried to create a project using go-template with the same parameters as you specified, and everything went as expected with no crashes.
$ cookiecutter --version
Cookiecutter 2.1.1 from /home/notsatan/.local/lib/python3.10/site-packages (Python 3.10.4 (main, Mar 23 2022, 23:05:40) [GCC 11.2.0])
$
$ cookiecutter gh:notsatan/go-template
project_name [go-template]: KbHostnames2Networks
project_description [Kbhostnames2Networks is a Go application created using https://github.com/notsatan/go-template]:
go_module_path [github.com/notsatan/go-template]: git.xx.cz/users/xxxx/repos/hostnames2networks
license_owner [notsatan]: XX a.s.
base_branch [master]:
contact_email []<EMAIL_ADDRESS>github_specific_features [y]: n
use_codecov [y]: n
use_precommit [y]: n
Select go_version:
1 - 1.17
2 - 1.16
3 - 1.18
Choose from 1, 2, 3 [1]: 2
Select license:
1 - MIT
2 - BSD-3
3 - GNU GPL v3.0
4 - Apache Software License 2.0
Choose from 1, 2, 3, 4 [1]: 1

====================================================================================

Your project `KbHostnames2Networks` is ready!

It is suggested to go through the generated `README` for detailed instructions on
how to use the tools that come with `go-template`! The following is a *brief*
overview of steps to push code to remote.

1) Move to project directory, and initialize a git repository:
    $ cd KbHostnames2Networks && git init

2) Run codestyle:
    $ make codestyle

3) Run linters and codestyle checkers
    $ make lint

4) Run the complete test-suite:
    $ make test

7) Upload initial code to git:
    $ git add -a
    $ git commit -m "Initial commit!"
    $ git remote add origin https://git.xx.cz/users/xxxx/repos/hostnames2networks.git
    $ git push -u origin --all

If you have any suggestions, or encounter any issue, please raise an issue;
    https://github.com/notsatan/go-template

Which version of Cookiecutter were you using when you ran into this error? Can you re-try this with the latest version of Cookiecutter? My guess is that you're using an outdated version of Cookiecutter that did not support the + token in the template syntax, in this case, simply updating Cookiecutter should fix your issue!
$ pip install --upgrade cookiecutter

P.S. You can use a virtual environment to install (a localized) version of Cookiecutter that is up-to-date in case you can't (or don't want to) modify the central installation.

Hey @Vitexus, any updates on this so far?

Closing this issue, feel free to revert back if the issue still persists!

işe yaramadı bende

It didn't work for me

Thanks, Google Translate. Now @arsto27 I'm happy to reopen this issue (or you can raise a new one and link it to this one), as long as:

You actually describe your problem, and hopefully include an error log that I can use to debug the issue
You stick to English (I don't know Turkish, and Google Translate often fails for technical translations)


Page 3 | LeoHe's Space

https://hefuduo.github.io/page/3/
声明不息，学习不止

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook


Allow using Nt* versions of Zw* APIs

Is your feature request related to a problem? Please describe.
Many Nt* APIs are only documented under their Zw* variant. The docs clearly state that you should use the Nt* variant in user mode:
For example:

If the call to this function occurs in user mode, you should use the name "NtQueryKey" instead of "ZwQueryKey".

Describe the solution you'd like
For any Nt* API request that doesn't already have metadata associated with it, look for a matching Zw* API and use that definition with the Nt* prefix.

While the proposal here is possible, that sounds like something every projection would need to do. That suggests that perhaps the metadata should include the Nt variants instead of (or in addition to?) the Zw variants.
@mikebattista What do you think?

@riverar any thoughts on this?

We currently have the Zw variants in the WDK metadata. We can scan the same headers and pull in the Nt variants easy enough but we'll need to carefully resolve the type definition overlap. (For example, we will probably need to pull OBJECT_ATTRIBUTES (and its 32/64 variants, flags enum, etc.) up from Windows.Wdk.Foundation into Windows.Win32.Foundation.)

Thanks, @riverar. I'll move this to the win32metadata repo for further discussion.


Don't permit port in proxy IP option

Fixes: #809
Previously it was possible through the GUI to enter an IP address:port into the "Proxy IP" configuration box. After the node was restarted the errant setting would prevent the node starting back up until manually removed from settings.json.
Prevent this with a simple check for ":" in the string. This is acceptable here in the GUI setting because we already fail on a hostname such as "http://x.x.x.x", so it won't cause false positives.

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews
See the guideline for information on the review process.
A summary of reviews will appear here.

I'd suggest to use a regex validator for the IP address, it's much simpler I think and the user won't be allow to enter any other symbols or chars (typo?) that aren't digits (plus user can't type more than 3 subnets separated by dots where currently you could and any symbols)

I'm not convinced that a large regex is "simpler" than checking if a ":" is in the string?
Thanks for the other suggestions, but I don't feel that interested in picking them here with the QML work going on, and them not being much of an issue IMO. In contrast this fix prevents a bug whereby an incorrect setting can stop the node starting up.
The only potential issue I saw with my own solution was that it would outright prevent setting the tor proxy IP to an IPv6 address, however from my (quick) research, it didn't seem that this was actually something anyone did (and it might not even be possible/practical to do). If I'm wrong on this, I'll be happy to update the solution further, but from what I can see even setting Tor ORPort to IPV6 is barely supported, and ControlPort is limited to an IPv4 address:port...

I'm not convinced that a large regex is "simpler" than checking if a ":" is in the string?

The large one was for the port number, the one I referred as "simpler" was for the IP address: QRegularExpression ipRegex("^([0-9]{1,3}\\.){3}[0-9]{1,3}$");. What I meant is that we know in advance that the ":" would be invalid so we could restrict the user to even enter it. As current we could see this (not only ":"):

The regex would keep it cleaner, more user friendly and we don't have to do an extra validation, but I'll stop trying to convince you :smile: (btw, also we'd need to set the max length to 15/ follow up).

I don't feel that interested in picking them here with the QML work going on, and them not being much of an issue IMO.

QML is far for being at the stage where QT currently is, improving user experience could also be useful for both projects feedback.

In contrast this fix prevents a bug whereby an incorrect setting can stop the node starting up.

I agree and there's a workaround already which is just removing the IP line from the file.

The only potential issue I saw with my own solution was that it would outright prevent setting the tor proxy IP to an IPv6 address, however from my (quick) research, it didn't seem that this was actually something anyone did (and it might not even be possible/practical to do). If I'm wrong on this, I'll be happy to update the solution further, but from what I can see even setting Tor ORPort to IPV6 is barely supported, and ControlPort is limited to an IPv4 address:port...

Is it even possible to enable those checkboxes?

@jarolrod Isn't that a bug independent from the validation one?

Backported in https://github.com/bitcoin/bitcoin/pull/30092.


Missing Entry: Main

Trying to figure out why I can't seem to have a working build. VS community 2019.

As you can see from the pic, it successfully builds. I even delete the dlls and rebuild and build works fine.
But then it says Missing entry: main.

Try reinstalling the Nuget package, "Unmanaged Exports"

Do you have the same issue with the x64 version?

So first I tried x64 and it does the same thing. Then I tried to reinstall:

Then:

Now it fails all together:
1>------ Build started: Project: PowerShdll, Configuration: Release x64 ------
1>  PowerShdll -> C:\Users\cdavis\Desktop\PowerShdll-master\PowerShdll-master\dll\bin\x64\Release\PowerShdll.dll
1>C:\Users\cdavis\Desktop\PowerShdll-master\PowerShdll-master\packages\UnmanagedExports.1.2.7\tools\RGiesecke.DllExport.targets(58,3): error MSB4062: The "RGiesecke.DllExport.MSBuild.DllExportAppDomainIsolatedTask" task could not be loaded from the assembly C:\Users\cdavis\Desktop\PowerShdll-master\PowerShdll-master\packages\UnmanagedExports.1.2.7\tools\RGiesecke.DllExport.MSBuild.dll. Could not load file or assembly 'Microsoft.Build.Utilities, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Oh, do I need to have .NET 3.5 installed?

Oh yea that's what it was! Just had to install  .NET 3.5.
I'm on Server 2019 so I had to DISM /Online /Enable-Feature /FeatureName:NetFx3 /All


Codicon color tokens should be area scoped

https://github.com/microsoft/vscode/issues/89328 and related to https://github.com/microsoft/vscode/pull/89121
This looks kind of odd in the command palette imo. We may want to revisit codicon coloring, I think generally we should default to uncolored.

Personally I also think emojis in the command palette are quite ugly 😛

I think this is even more important for usages outside the command palette:

Here I was thinking about using the step icons for push/pull in the GitLens view -- but with the color they look bad.

Here's another example:

Updated the issue to make it so that all color tokens be scoped to their areas. Also happening for symbol icons used in the activity bar:

cc @sbatten

In response to https://github.com/microsoft/vscode/commit/d78f3419cca25c2c15b126365b0e836b9ef4b76b. I think e.g. the Go To Symbol (ctrl+shift+o) quick pick for example should keep the symbol icons colored like it does in the outline view. It makes distinguishing between symbols way harder when everything is the same color.

@vainamov thanks for bringing that up. This makes it really challenging to scope icon colors in the quick pick because of the various uses where some quick picks use it and others don't. I'll revert that commit and will need to revisit the strategy for this.

I think the guidance is for icons with color to adjust to their respective areas. For example, icons in the activity bar and status bar always should be a single color, while icons in the tree view + quick pick would persist their color. The primary icons that have color are Debug + Symbol icons, so it's a very limited scope already. These icons are intended to be used with color and in the cases that an extension does not want color should be recommended to use an alternate color via
this.iconPath = new vscode.ThemeIcon('rocket', new vscode.ThemeColor('foreground'));


Add details for error messages in validate_pipeline_descriptor_sets

Add details for format and image_view_type checks in RecordingCommandBuffer::validate_pipeline_descriptor_sets to make debugging easier.

Thanks, I agree that this helps. Maybe the messages would be clearer still if the message said "pipeline requires {}, but image view type is {}"? Then there's no doubt on what pieces are referred to.


Add socket.io with multiple cluster's support

For activate socket.io compatibility in production mode, or with multiple clusters, set clusterSticky to true in your config file.

Hi @bertho-zero ,
I had applied your solution but I got an error
"Assertion failed: ((consumed_) == (false)), function Consume, file ../src/stream_base.h, line 203."
Then workers went die.
Did you get the same issue?

@haduythuan people have similar issues here, might want to subscribe for a fix:
https://github.com/nodejs/node/issues/3072

This fix worked for me, thanks!

@bertho-zero hii friend, nice work but u must add count of cpu - 1 in sticky options cause in this way it is running extra cluster, cause as u run gulp it runs mean.serve that runs sticky all cpu cores so it is result with x cores + 1 so easy way to fix this i suggest to use sticky options
in ExpressEngine.js
let cpuCount = require('os').cpus().length,
stickyOptions = {
        num: cpuCount - 1
};

and replace both lines of sticky with
sticky(stickyOptions, http*

but this is type of cosmetic fix for this problem cause here are 1master cluster + cpu.count - 1
i will look for real solution

@bertho-zero are you able to integrate these changes from @emps? If not I will re-roll this PR as it was essentially to get our app working in production on heroku
To take advantage of our already used CPU_COUNT env var, I'd do:
let cpuCount = process.env.CPU_COUNT || require('os').cpus().length,
stickyOptions = {
        num: cpuCount - 1
};

Thanks @bertho-zero and @emps this has landed in 0.6.X / master


[SPARK-48107][PYTHON] Exclude tests from Python distribution

What changes were proposed in this pull request?
Change the Python manifest so that tests are excluded from the packages that are built for distribution.
Why are the changes needed?
Tests were unintentionally included in the distributions as part of #44920. See this comment.
Does this PR introduce any user-facing change?
No, since #44920 hasn't been released to any users yet.
How was this patch tested?
I built Python packages and inspected SOURCES.txt to confirm that tests were excluded:
cd python
rm -rf pyspark.egg-info || echo "No existing egg info file, skipping deletion"
python3 packaging/classic/setup.py sdist
python3 packaging/connect/setup.py sdist
find dist -name '*.tar.gz' | xargs -I _ tar xf _ --directory=dist
cd ..
open python/dist
find python/dist -name SOURCES.txt | xargs code

Was this patch authored or co-authored using generative AI tooling?
No.

Merged to master.

:-)

:)


Introduce new annotation, as an alternative to directModelSubstitute

I have a feature request / suggestion.
I have a number of objects which represent IDs, for example
public class FooId {
    private final int id;
    @JsonCreator public FooId(int id) { this.id = id; }
    @JsonValue public int getId() { return id; }
}

If I have a DTO, for example:
public class MyDto {
    public FooId theFoo;
}

When the MyDto gets serialized by Jackson, the element fooId is the integer value, so that works fine.
When I am using Springfox 2.7.0, I have to use the following line to allow Swagger to produce the right Swagger JSON.
.directModelSubstitute(FooId.class, Integer.class)

So far so good. But I have something like 20+ IDs, and thus a huge list of directModelSubstitute calls.
Although this is OK, I feel that a colleague might create a new ID object, and not know that they have to add the line to the Docket. I feel it would be more self-contained, if on the ID object I was able to write:
@ApiDirectModelSubstitute(Integer.class)
class FooId { .... }

Alternatively, Springfox could see that the class FooId has a @JsonValue returning an int, which would need no annotation or directModelSubstitute call, which I believe is in line with the philosophy of Springfox of reading as much information from the code, without additional configuration, as possible.
I understand there is still the need for the directModelSubstitute method, as sometimes one wishes to document classes such as java.time.Instant which are not under our control. So I propose this annotation as an additional way to specify that.

This is a great idea. Easily doable using the currently provided extensibility mechanisms.


CII Gold: dynamic analysis

Task
Goal
Conduct a dynamic analysis.
Description
As documented in CII Best Practices: Gold > Analysis: Dynamic code analysis > Dynamic analysis:

The project MUST apply at least one dynamic analysis tool to any proposed major production release of the software produced by the project before its release.

Success Criteria
The security document is updated with any findings and issues are opened for any security vulnerabilities identified.

RSpec performs dynamic analysis with 99% coverage using valid inputs and invalid keys.
Fuzzing is unnecessary since the library merely forwards requests to the Google Maps API and wraps the results in a Ruby object. Testing it with unexpected data would be equivalent to testing the API.
Dependabot automatically opens patches for known vulnerabilities.
CodeQL automatically opens security issues.


mjs is real life

https://nodejs.org/api/esm.html , first paragraph
Just thinking it might be easier to add .mjs to the list of executable files now, instead of raging about it later

@jeremy-coleman I will make sure to include it to v4 which is being cooked ATM

Closed due to inactivity.


Make Repository#execute private

Ditto.

@peterberkenbosch Can you please take care of it? Thank you very much.

@jodosha is this task as simple as moving this method into the private portion of Repository?

@mjbellantoni yes

I've taken a shot at this in pull #193.

Implemented by #193


Qa 0.27

What this PR does / why we need it: fixes after the QA
Unresolved issues:

there are dropped packets going to ingress-controller (both sc and wc) pods that I didn't manage to identify. Didn't notice any obvious issues caused by this.

that NP issue for ingress controller doesn't seem to be an issue on safespring, this is how it looks in my cluster


Attempt to fix brokenness with nbclassic override.

Please wait to see if passes before merging on this one, Brian :-)

This might not be you:

Per the logs, looks like we might need pip install notebook

https://github.com/ipython-contrib/jupyter_contrib_nbextensions/issues/1647
https://github.com/Jupyter-contrib/jupyter_nbextensions_configurator/issues/165
These were ported over from a legacy image.  At some point might be worth seeing what is still needed here.

I'm not sure how they're missing notebook being installed. It's possible they're looking in an old path.

Pretty much.  Instead of "notebook", it needs to look to server now: https://github.com/Jupyter-contrib/jupyter_nbextensions_configurator/pull/166/files


Help with custom log format with tabs

Hi, I have a custom log that separates data by tab (TSV log format).
Log is a DNS query.
This is a snipped of the log
[2020-05-27 14:47:47]	<IP_ADDRESS>	badexample.com	A	FORWARD	24ms	<IP_ADDRESS>:53
This is my goaccess.conf
time-format %H:%M:%S
date-format %Y-%m-%d
log-format [%d %t] %h %v %U %^ %^ %^ %^
It works fine when I manually change tab to space, but can't figure out how to get the tab read by goaccess so interprets the log file.
This is what I keep getting when trying to run goaccess
Parsed 1 lines producing the following errors:
Token for '%h' specifier is NULL.
Format Errors - Verify your log/date/time format
Thanks in advance

You can always use \t as delimiter. e.g.,
log-format [%d %t]\t%h\t%v\t%U\t%^

log-format [%d %t]\t%h\t%v\t%U\t%^

so simple yet so far :|
bloody legend mate, cheers


Add namespaces to JVM metric attributes?

Replaces https://github.com/open-telemetry/opentelemetry-specification/issues/3417
There are (currently) three proposals being discussed for metric attribute namespaces in #51.
This purpose of this issue is to try to arrive at consensus for future JVM metric attribute renames based on each of these three proposals.
Today:

process.runtime.jvm.memory.*

type
pool

process.runtime.jvm.gc.duration

gc
action

process.runtime.jvm.threads.count

daemon

process.runtime.jvm.buffer

pool

Option A: No namespaces required
Possibly no change.
Maybe gc -> name to align with Option C.
Option B: Explicit namespaces required
PR already exists for this: https://github.com/open-telemetry/semantic-conventions/pull/20

process.runtime.jvm.memory.*

type -> memory.type
pool -> memory.pool.name

process.runtime.jvm.gc.duration

gc -> gc.name
action -> gc.action

process.runtime.jvm.threads.count

daemon -> thread.daemon

process.runtime.jvm.buffer

pool -> buffer.pool.name

Option C: Namespace inherited from metric namespace

process.runtime.jvm.memory.*

type (implicitly process.runtime.jvm.memory.type)
pool (implicitly process.runtime.jvm.memory.pool)

process.runtime.jvm.gc.duration

gc -> name (implicitly process.runtime.jvm.gc.name)
action (implicitly process.runtime.jvm.gc.action)

process.runtime.jvm.threads.count

daemon (implicitly process.runtime.jvm.threads.daemon)

process.runtime.jvm.buffer

pool (implicitly process.runtime.jvm.buffer.pool)

This TC vote has concluded and we should be able to proceed with resolving this issue.
I'm in favor of option c because I view it as the least risky. There's no opportunity for future conventions to disagree with the semantics we define for general memory.type / memory.pool.name / gc.name / gc.action, since all attribute names will be clearly scoped to JVM. If general semantic conventions emerge that match JVM semantics, we can adopt those and change the name of the attributes via telemetry schemas.

I need to clarify my previous comment. I prefer the names of option c, but with fully qualified names rather than relying on any inheritance from the metric name's namespace:

process.runtime.jvm.memory.*

process.runtime.jvm.memory.type
process.runtime.jvm.memory.pool

process.runtime.jvm.gc.duration

process.runtime.jvm.gc.name
process.runtime.jvm.gc.action

process.runtime.jvm.threads.count

process.runtime.jvm.threads.daemon

process.runtime.jvm.buffer

process.runtime.jvm.buffer.pool

I also like option b, but don't want to get blocked on a discussion on whether the java memory, gc, thread, and buffer concepts are language agnostic.


“Widely available” date isn’t useful for old features

Example: <button>
https://web-platform-dx.github.io/web-features-explorer/features/button/
It says “Widely available since 2018-01-29”. The reason for such a late date is “Edge 12 Released on 2015-07-29” (30 months before).
That 2018 date isn’t useful, and it might even confuse some developers and make them think that <button> is a newer feature than it is. <button> has been widely available for a very long time, and the launch of Edge in 2015 doesn’t change anything about that.
Maybe “widely available” should only include a date in cases when a modern browser didn’t support a feature at some point. In all other cases, it could just say ”Widely available for a long time”.
In the case of <button>, all the browser versions listed on the page are the initial versions of these browsers. In other words, all the listed browsers supported <button> from the beginning. Therefore, <button> has been ”widely available for a long time”.

Thanks @simevidas. I agree that the date doesn't help here, and can sometimes be confusing.
I'll remove it for now. We can figure out later if adding it in certain cases is useful.


Raise errors for inputs that would cause blank outputs; handle length in CLI for variable length digest algorithms

Addresses #14 and #17

@zoeduan I made some significant changes to test_hasher.py to have parameterize over all test checksums provided in checksums with pytest.mark.parametrize. It does this for default length settings as well as both with and without a length used for BLAKEs. I think this is a helpful reduction of repetition.
@egrace479 I made it so that if an algorithm is not available on the system, it continues through the loop, skipping the subtest. There's also a test to make sure that if non-guaranteed algs are unavailable, just those that are available are tested.

Note that I tested possible failure modes of the testing approach locally by artificially perturbing available and guaranteed sets, e.g.:
def is_algorithm_available(algorithm):
    return algorithm in hashlib.algorithms_guaranteed # Only say that an algorithm is available if it's in the guaranteed set

Or by removing or writing an error for one or more entries in checksums causes tests to fail in the correct places.


Feature request: per-world scoreboards

Any plans to support different scoreboards in selected worlds? Similar to SimpleScore or LightBoard, but with the full functionality offered by ScoreboardStats?

@games647: Any thoughts on this? Possibility of inclusion in a release?

Closed due to dev abandonment.


Adding more fields to filing endpoint

Short description outlining key changes/additions
Adding more fields to filing endpoint
JIRA Ticket Number
Type of change

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[ ] I have added unit tests for new code that I have added
[ ] I have added/updated functional tests where appropriate
[ ] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found


Credential and Environment removed from CB, fetched from Env service

@bergerdenes the Environment related APIs will be deleted from the core's API, so it has been leaved in the code temporarily.

Can one of the admins verify this patch?

Refer to this link for build results (access rights to CI server needed):
ci-cloudbreak.eng.hortonworks.com/job/cloudbreak-pull-request-builder-v2/7/


wip: rewrite catalog store logic

https://github.com/rancher/types/pull/337

https://github.com/rancher/rancher/issues/12295

https://github.com/rancher/rancher/issues/12347


GraphQL support

🚀 Feature request
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Description
GraphQL support in Angular CLI is extremely limited or rather non existent. The big trouble for anyone trying to use Angular and GraphQL is that there is no way of pre-compile GraphQL documents. This way we end up with an extremely oversized bundles and increased script initialization.
There are solutions out there that compile GraphQL document into an AST:

graphql-tag/loader
babel-plugin-graphql-tag
ts-transform-graphql-tag
rollup-plugin-graphql

None of the solutions listed above can be used effectively if we intend to develop library containing GraphQL.
With application alone we could theoretically make it work with graphql-tag/loader. Adding library into the mix will simply not work, as ng-packagr is completely closed to any custom Rollup loaders.
Similar ng-packagr issue: https://github.com/ng-packagr/ng-packagr/issues/1619
Disclamer: I know the main issue is in ng-packagr, but I wanted to see what is the overall Angular CLI take on this, since Angular CLI is "blocked" by it indirectly.
Describe the solution you'd like
If the GraphQL is big enough in Angular it could become first class citizen.
If not (probably not), we would need some convenient way of adding loaders for both applications and libraries, as covering applications alone is only half of the story.
I know ng-packagr is a complete separate project, but that is exactly the problem here. While Angular CLI is getting more open with public APIs, ng-packagr is as closed as ever.
Describe alternatives you've considered
The only alternative I can think of is a fork of ng-packagr and a custom Angular CLI packagr builder to handle this not so special case. Either that or a complete abandonment of Angular CLI.

Hi @klemenoslaj,
Thanks for this feature request. I have discussed this with our DevRel and we agreed that adding GraphQL as a first class citizen is not in scope of the Angular CLI, as we are not opinionated about the data layer.
From an application point of view, you can use 3rd party builders to extend the CLI, such as ngx-build-plus or angular-builders.
For libraries, this is a bit more complex, because of the different module formats and only 2 of the 3 formats are being bundled using Rollup. Thus, adding any transformation at the Rollup stage is too late. Such transformations needs to happen at a TypeScript compiler level, which most likely can be achieved using the ng-packagr extension ng-cli-packagr-tasks.

Hi @klemenoslaj,
Thanks for this feature request. I have discussed this with our DevRel and we agreed that adding GraphQL as a first class citizen is not in scope of the Angular CLI, as we are not opinionated about the data layer.
From an application point of view, you can use 3rd party builders to extend the CLI, such as ngx-build-plus or angular-builders.
For libraries, this is a bit more complex, because of the different module formats and only 2 of the 3 formats are being bundled using Rollup. Thus, adding any transformation at the Rollup stage is too late. Such transformations needs to happen at a TypeScript compiler level, which most likely can be achieved using the ng-packagr extension ng-cli-packagr-tasks.

Hi @alan-agius4,
Thanks for the fast response.

as we are not opinionated about the data layer
That is 100% fine, and expected. The problem is, if people are getting blocked of using the technology of their choice, which is happening here.

I did not know of packagr-tasks, will have a look. I am not aware of any existing TS compiler transformer (they only work on bundler level), nor am I sure if it is even possible to achieve this.
Wouldn't this be problematic due to: https://github.com/microsoft/TypeScript/issues/14419?

That is 100% fine, and expected. The problem is, if people are getting blocked of using the technology of their choice, which is happening here. Should the issue not remain opened due to that fact alone?

I don't think this is blocking, both Angular CLI and ng-packagr are extensible and you do have the possibility to extend both build system to some extend. That being said, it's important to mentioned that while extending the build system is possible, this is something which the Angular tooling team doesn't support.
While ng-packagr is not as easily extensible as the Angular CLI, this is more of an ng-packagr issue rather than the Angular CLI. I suggest you raise this problem in their issue tracker. That said, as mentioned previously there are packages like ng-cli-packagr-tasks which provided a cleaner extensibility to ng-packagr.

Yes, that's what I was referring to in the issue to being nicely extendable. However majority of our code is in libraries, so that doesn't help.

As mentioned this can possible be achieved using ng-cli-packagr-tasks, by adding a custom TS transformer or changing the NGC compilation factory. https://www.npmjs.com/package/ts-transform-graphql-tag is an example of a TS transformer for GraphQL.

Wouldn't this be problematic due to: microsoft/TypeScript#14419?
No, because transformers are already part of TS public API. So you can add a custom TS transformer.

That being said, it's important to mentioned that while extending the build system is possible, this is something which the Angular tooling team doesn't support.

Well this is exactly my point. The CLI is not opinionated but it doesn't provide a support for making your own opinionated decisions around tooling.
Like in the case of GraphQL, one has to go seriously out of his way to get it done and even then, there is this "Angular tooling team doesn't support" that worries me.
As far as I am concerned, this is indeed blocking. The statement is contradicting itself - not blocked, but unsupported.
Usage of unsupported APIs is not a way to go.

While ng-packagr is not as easily extensible as the Angular CLI, this is more of an ng-packagr issue rather than the Angular CLI

Yes, aware of that :+1: Anyway, wanted to address this from the perspective of CLI, since ng-packagr is being used.


Add 'external' className to Universal link component for external link.

Hey Flameing, Can you elaborate on your issue

@ThisisMS11 This was already done in https://github.com/plone/volto/pull/5110 and https://github.com/plone/volto/pull/5188


Make it obvious that the d3-financial-components package is old

The information here should clearly sign-post d3fc:
https://www.npmjs.com/package/d3-financial-components

I'm pretty sure you get a deprecation notice when you install it (or at
least I set that up for a project which I think was this one)
On Mon, 26 Oct 2015 09:33 Colin Eberhardt<EMAIL_ADDRESS>wrote:

The information here should clearly sign-post d3fc:
https://www.npmjs.com/package/d3-financial-components
—
Reply to this email directly or view it on GitHub
https://github.com/ScottLogic/d3fc/issues/679.

Yes, pretty sure I've seen that. I was planning on adding a notice to the README for the project.

Assuming this is no longer a problem.


Fix light theme on xiaomi devices

I didnt test it yet
https://www.reddit.com/r/androiddev/comments/r5e99c/how_do_you_handle_forced_dark_mode_and_apps_not/

Thank you for the PR!
I tested on a POCO F3 with MIUI 14, forcing the dark modein MIUI results in the app using the dark theme set in the app, so I didn't see any issues compared to the normal dark theme. I will close the PR, but it can re-opened if issues are found with MIUI and the dark mode


Enable array typecast in tsv extractor

Currently users can only use array_to_string to process arrays. However PSQL array output format is parsable. We can provide the functionality in ddlib.
Reference:
https://github.com/psycopg/psycopg2/blob/master/psycopg/typecast_array.c#L60

Superseded by #236


Creates release notes.

Release notes.

Codecov Report

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

@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   46.25%
=========================================
  Files             ?       69
  Lines             ?     6058
  Branches          ?        0
=========================================
  Hits              ?     2802
  Misses            ?     3001
  Partials          ?      255

Continue to review full report at Codecov.

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


Float field on Visual Shader editor bug

Godot version: 3.3.2 | From Steam release
OS/device including version:

Test on :

Windows 10, GeForce 1080 i7-3770k@ 3.5Ghz
Windows 10, Intel(R) Iris(R) Plus Graphics, Intel Core i7-1065G7@ 1.3Ghz
Linux Manjaro -- Intel® Core™ i7-4790K CPU @ 4.00GHz × 8 -- GeForce GTX 1070/PCIe/SSE2

Issue description:
Hello,
with the visualshader editor, if you try to slide a value with your cursor, godot move your cursor on your screen center. Try with an empty scene and a new shader.
Gif Explain:

Steps to reproduce:
Add a scalar constant with the VisualShader editor, and try to slide the value.
Minimal reproduction project:
A simple project with a basic material.
Test.zip

Related to https://github.com/godotengine/godot/issues/47608.

Couldn't reproduce this on the latest version, everything was working as expected. This was probably fixed, but the fix needs to be backported to 3.3. What do you think?

Working for me on the master as well.

Hi,
i'm compile any branches and my result :

[x] Master branch, it's work with the Float node (this node a rename ?)
[ ] 3.x branch, feature broken
[ ] 3.3 branch, feature broken

I'll try to identify what's solved it and see if I can backport the fix to 3.3 and 3.x branches.

Tried to reproduce this today on 3.x, and I got the expected behavior. Going back to 3.3 to see if it's still there.

Float node (this node as rename ?)

It is.

Haven't figured it out, it seems like the culprit is lower level than I originally thought


deprecated p4 method which sets the user name to 'rolem'

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.


Tools: add PHPUnit Polyfills

name: 🎉 New Feature
about: Add a new feature
labels: enhancement
A Pull Request should be associated with a Discussion.
Fixes #502
Description
This PR adds support for the PHPUnit Polyfills tool via the tools input to setup-php.
I have added a test to the linux test and a second test with a specific version to the darwin test.

In case this PR introduced TypeScript/JavaScript code changes:

[x] I have written test cases for the changes in this pull request
[x] I have run npm run format before the commit.
[x] I have run npm run lint before the commit.
[x] I have run npm run release before the commit.
[x] npm test returns with no unit test errors and all code covered.

Note: running these scripts, automatically added two unrelated changes to the PR, which I have manually removed (had to disable the pre-commit hook to do so). The changes were to package-lock.json and to dist/index.js. Not sure what's going on there.

In case this PR edits any scripts:

[ ] I have checked the edited scripts for syntax.
[ ] I have tested the changes in an integration test (If yes, provide workflow YAML and link).

Yikes! Sorry about that, not sure how that got in there as I have a git global ignore set up for those type of files... Either way, should be fixed now.

@jrfnl Thanks!

Thanks @shivammathur !

Integration test:

Yaml changes: https://github.com/jrfnl/PHPMailer/commit/342ad9bba5cccee6f581e5f1db1beda03e2c0124
Successful action run: https://github.com/jrfnl/PHPMailer/actions/runs/1255741429

FYI: I've added an FAQ section to the README for the PHPUnit Polyfills about how using it via setup-php with tools:
https://github.com/Yoast/PHPUnit-Polyfills#q-how-do-i-run-my-tests-when-the-library-is-installed-via-the-github-actions-setup-php-action-


DEBUG not enabled vscode debug in .env variables

I have this test code:

const info = require('debug')('app:info');
console.log('env NODE_ENV', process.env.NODE_ENV);
console.log('env ANOTHER_VAR', process.env.ANOTHER_VAR);
console.log('env DEBUG', process.env.DEBUG);
info('Test info debug logging');
console.log('debug status:', info.enabled);

If I run the program in vscode using the debug mode, it doesn't enable debug using the environment variables.
I have tried:

setting the env variables in the launch parameters
"env": { "NODE_ENV": "dev", "DEBUG": "app:*" },
setting the variables in the .env file and setting the launch parameters to load the .env file
"envFile": "${workspaceFolder}/.env",
.env file:

NODE_ENV=dev
DEBUG=app:info,-trace
ANOTHER_VAR=WHatNow

The output is:

env NODE_ENV dev
env ANOTHER_VAR undefined
env DEBUG app:*
// Missing line here, should contain "Test info debug logging"
debug status: true

When I run the program in a bash window using this command, it shows the info output
"Test info debug logging".
This is the full output:

[nodemon] starting node demo.js
env NODE_ENV dev
env ANOTHER_VAR WhatNow
env DEBUG app:debug,app:info
app:info Test info debug logging +0ms
debug status: true

I've tried setting info.enabled = true (as in ticket #774) - doesn't help. As you can see in the last line, it's already true. I've gone through a range of tickets, such as #696 and others, but can't find anything.
When I trace the app, in the file common.js, debug.enabled is false so the debug function simply returns.

function createDebug(namespace) {
let prevTime;
  function debug(...args) {
  	// Disabled?
  	if (!debug.enabled) {
  		return;
  	}

.....

Please assist.
Thanks
Brian

This has to do with VSCode, not debug - as you've seen with bash, debug is working fine. The conditional you mention at the bottom is to see if that instance's namespace is enabled given the environment variable, but since VSCode doesn't provide one to your program (for whatever reason) then of course debug.enabled will be false.
There's something else about your VSCode configuration that is wrong; I don't use VSCode so I can't really help, unfortunately. You might want to open an issue over on the VSCode repository.
Good luck!

@Qix- I encountered the same issue, and I can't really understand your explanation.

The conditional you mention at the bottom is to see if that instance's namespace is enabled given the environment variable, but since VSCode doesn't provide one to your program (for whatever reason) then of course debug.enabled will be false.
However, in the given example @icaptnbob provides, they called

console.log('env DEBUG', process.env.DEBUG);

and it outputs:

env DEBUG app:*
Doesn't it mean environment variable DEBUG is correctly provided?

@icaptnbob Did you find a solution later?


Clipboard copy & paste in edit messages inconsistent between app and mWeb

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login with any account in web and mobile.
On Mobile, go to any report, copy any message text, try to edit any message, paste the clipboard that you copied before.
Notice that there is a space right before the clipboard.
On Web, go to any report, copy any message text, try to edit any message, paste the clipboard that you copied before.
Notice that there isn't any space before the clipboard.

Expected Result:
Clipboard should consistent between Mobile and Web
Actual Result:
Clipboard inconsistent between Mobile and Web
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] iOS / native
[ ] iOS / Safari

Version Number: 1.2.49-0
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/210910000-ea84976e-6ca8-4494-8e75-3202d5a6179d.mp4
https://user-images.githubusercontent.com/43996225/210910015-41d00e41-1fc4-4602-8dea-28bb826fc217.MP4
Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1672937753516379
View all open jobs on GitHub

This bug does seem to happen, not 100 % sure why it happens, it might be a specific iOS thing

I did some research this is definetly and iOS thing, there must be a fix, because other Apps do not do it, but I haven't figured out yet, a possibilty is listening to a couple of events and try check if the pasted value is the same as the one in the clipboard.

@sketchydroide Seem we have similar issue here and may be it's a dupe of this issue
https://github.com/Expensify/App/issues/14164

@Gonals commented on that other issue (https://github.com/Expensify/App/issues/14164) - is this the same thing?

I don't think it is a duplicate, and also the platform for that issue is Web, whereas here it is mWeb/iOS.
@sketchydroide @lschurr do we know which behaviour is expected? Should it add the space or not?

@Gonals commented on that other issue (#14164) - is this the same thing?

I think they are different :)

Thanks for the comment @Gonals.

I don't think it is a duplicate, and also the platform for that issue is Web, whereas here it is mWeb/iOS.
@sketchydroide @lschurr do we know which behaviour is expected? Should it add the space or not?

@sketchydroide @lschurr do we know the expected behavior here?

Asked in the Slack thread for someone to confirm the expected behavior.

@sketchydroide We haven't got any response on the thread. Can you help tag some folks who might be able to help with the decision here?

It looks like Shawn and Jason commented in that thread.. the latest was..

Let’s open it up for proposals and see if someone can determine why Slack doesn’t add the space but other iOS apps do. I do agree with others, though, that I’m not sure if if this is a bug at this point. We’re venturing into New Feature territory.

Thanks for posting the update @lschurr.
Yes. Let’s see if we get good proposal that don’t require too much refactor.

I don't think we should add the space, it's weird that iOS does this automatically, and actually anoying, I get why, but there should be an option programatically to do it, while I know there are options in Safari settings that allow for this, we should still remove the space.
There are instances where this can be particularly anoying, and I see expense values as being one of them.

I think we are still waiting for proposals

I had forgoten to set this as an extrenal (I was sure I had do it 🤷🏼) should get some proposal now hopefully

not overdue, seems we still don't have any proposals

Hello, I'm Fábio from Callstack and I'm interested in taking and analysing this issue to work on a fix for it.

@fabioh8010 Feel free to post a proposal and checkout our contributing guidelines to understand the process.

@lschurr @sketchydroide context here: https://expensify.slack.com/archives/C03UK30EA1Z/p1675178800825569

@mananjadhav we're doing a little different process here in assigning @fabioh8010 before the proposal. But everything else in terms of him posting a proposal and having it approved prior to starting the work will be the exact same.

Okay noted @puneetlath. Is the slack discussion internal? Can you shed some light on the process? Can't access the link.

@mananjadhav internal so far, but @AndrewGable will be sharing an update in #contributor-plus in the near future.

@fabioh8010 Waiting for a proposal from your end. Are you still keen on working on this one?

Hi @mananjadhav, yes I'm still looking at this. Last week I only had time to investigate on 31st Jan, the following days we were in internal workshops.

Issue
This paste behaviour in iOS can be configured with the property smartInsertDeleteType described in the Apple documentation: https://developer.apple.com/documentation/uikit/uitextinputtraits/2865828-smartinsertdeletetype.
This property is defaulting to true because of the keyboard type that are being used in the application, leading to this issue described here.
It is necessary a way of disabling this property from RN side so we can control it properly. At the moment this property is not exposed to the RN's TextInput component.
Proposal
This proposal has two parts:
1) Add support for this property in the react-native library
We need to implement a new prop called smartInsertDelete to the TextInput component in iOS. This prop will be responsible for controlling the smartInsertDeleteType native property, it will be optional and will default to "default" as described in the Apple documentation.
We are going to create a PR to the react-native library itself with the new feature so they can review it.
2) Use the new prop in the application
We are going to set the new smartInsertDelete prop to false in the Composer component, thus disabling this paste behaviour and fixing the issue.
diff --git a/src/components/Composer/index.ios.js b/src/components/Composer/index.ios.js
index b31a5b462f..ed123d164d 100644
--- a/src/components/Composer/index.ios.js
+++ b/src/components/Composer/index.ios.js
@@ -106,6 +106,7 @@ class Composer extends React.Component {
                 onContentSizeChange={e => ComposerUtils.updateNumberOfLines(this.props, e)}
                 rejectResponderTermination={false}
                 textAlignVertical="center"
+                smartInsertDelete={false}
                 style={this.state.propStyles}
                 /* eslint-disable-next-line react/jsx-props-no-spreading */
                 {...propsToPass}

Great investigation @fabioh8010

That sounds like a good approach, not sure how long upstream will take to review/approve though

I think typically we would make the PR in our fork and in the upstream repo so that we can get the value of the fix immediately, but also try to get it merged upstream.

Hello, I made a good progress today in the implementation of the new prop, and I expect to create a PR to the upstream repo tomorrow.

Hi! The PR to the upstream repo is ready: https://github.com/facebook/react-native/pull/36111.
About your fork, what is the procedure for the PR?

@fabioh8010 the procedure would be to raise the same PR in our fork and tag the people assigned to this issue to review.

@puneetlath thanks for jumping in
@fabioh8010 what @puneetlath said

PR is ready! https://github.com/Expensify/react-native/pull/39

@fabioh8010 The fork PR was merged. Can you please update the App PR along with the PR template checklist?

Okay thanks for the update @mountiny

@mountiny Let's update the title to reflect that the issue is on hold?

Sorry, was ooo, updated the title

@sketchydroide, @mananjadhav, @fabioh8010, @lschurr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

Taking this one on from Andre

@mananjadhav, @fabioh8010, @lschurr, @mountiny Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@mananjadhav, @fabioh8010, @lschurr, @mountiny Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

Waiting for fix in upstream

@mananjadhav, @fabioh8010, @lschurr, @mountiny, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

@hungvu193 can you confirm this has been fixed by the rn update?

@mountiny Yep, I think it's fixed. I couldn't reproduce the issue.
https://user-images.githubusercontent.com/16502320/236364703-ab221abd-4bc4-41da-9883-cf429bd16b2a.mov

@lschurr Could you please pay @hungvu193 for reporting this bug, we missed this before. Thank you!

@mountiny There's a payout for the C+ review of the PR too.

Cool - @hungvu193 @mananjadhav can you apply for this job? https://www.upwork.com/jobs/~01090d4d204cb9362e

Thanks @lschurr, I've just applied

@lschurr applied. Thanks.

All paid!


Remove "user: root" placeholder from console connection form

Enter some container, then go to console and you will see 3 form fields: Command, Use custom command and User. User has confusing placeholder "root". This suggests that we connecting as root user.
I think, placeholder is confusing and need to be removed.

Hi @emprove ,
User root is common use by some container. That user form field will be helpful for container is not using root as standard user.

This should be a feature request to change the placeholder of that field to show more examples, not to remove it as its useful to a user to know what format they should follow when entering text in the field.

As far I know Docker is aware about which user container is running so right thing to do would be show that username/ID instead of root.


Orient 2.1.12: changing log level just for Orient libraries.

Hi folks,
I would like to change log level in tests just for OrientDB classes from INFO to WARN.
According to http://orientdb.com/docs/2.1/Logging.html changing log level can be achieved by setting this system property:
-Dlog.console.level=WARNING"
This changes log level for all libraries using java logging. Is there a way just to change OrientDB logging?

Sure, change the .properties file by replacing INFo with WARNING: http://orientdb.com/docs/last/Logging.html#configuration-file


The show memo toggle doesn't render as a checkbox

What happened?
When selecting View Option in YNAB with the "Add "Toggle Memo" Option" feature enabled, the "Show Memo Column" option renders as a small circle instead of the standard checkbox
Steps to Reproduce

Enable the Add "Toggle Memo" Option feature in settings
Navigate to any budget account
Select the view dropdown to open View Options
Note the Show Memo Column option does not render as a checkbox, but instead as a small circle (see screenshot)

What browsers are you seeing the problem on?
Chrome v130.0.6723.59
What OSs are you seeing the problem on?
Windows 11
What Toolkit Version are you running?
3.15.0
Screenshots

Setting Export
No response

Possibly related to #3045

Confirming that this issue exists in Firefox v132.0.2 with v3.15 of the extension.


CFE_ES_MAX_EID incorrect

Is your feature request related to a problem? Please describe.
Max EID incorrect:
https://github.com/nasa/cFE/blob/e80aae94e0f56b868657daba965c590766a4dc57/modules/es/fsw/inc/cfe_es_events.h#L46
https://github.com/nasa/cFE/blob/e80aae94e0f56b868657daba965c590766a4dc57/modules/es/fsw/inc/cfe_es_events.h#L1449
Describe the solution you'd like
Fix.
Describe alternatives you've considered
None
Additional context
Code review
Requester Info
Jacob Hageman - NASA/GSFC

The real fix is #1583, order EIDs and remove the fragile MAX tracking by hand.


cargo-xbuild: 0.5.7 -> 0.5.8

Motivation for this change
Update to the latest release.
https://github.com/rust-osdev/cargo-xbuild/releases/tag/v0.5.8
Things done

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

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

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

@GrahamcOfBorg build cargo-xbuild


feat(Footer): remove shop link from footer

Overview

Remove link to shop from footer

PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: DISC-817
[x] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] This PR includes testing instructions tests for the code change
[x] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories (there are unrelated flaky tests in monolith that ill figure out)

Testing Instructions
Verify that the shop link does not appear in the footer
PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal PR
Portal Env

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.191-alpha.504404.0@codecademy/gamut-labs@33.1.12-alpha.504404.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-kit@0.6.191-alpha.dd9400.0@codecademy/gamut-labs@33.1.12-alpha.dd9400.0@codecademy/gamut@50.5.4-alpha.dd9400.0@codecademy/monaco@0.6.81-alpha.dd9400.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://630cd3da94f02848ab0aa267--gamut-preview.netlify.appDeploy Logs