Depreciated dependencies warnings

Running Ubuntu 17.10, installed NVM & set it to 'stable' which provides node v9.5.0 (npm v5.6.0).
I got the following warnings upon npm install:
npm install
npm WARN deprecated<EMAIL_ADDRESS>...psst! Your project can stop working at any moment because its dependencies can change. Prevent this by migrating to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>Use the built-in module in node 9.0.0 or newer instead
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>Deprecated, use jstransformer
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd %s %s (wd=%s<EMAIL_ADDRESS>bower install /root/open-explorer-hertz.network

Could be worth updating these packages? https://github.com/oxarbitrage/open-explorer/blob/master/package.json
Cheers 👍

Most of the packages in there can probably be updated to newer versions. However it need to be tested one by one and make sure everything remains working. I know for example the explorer fails with bootstrap 4(last version - dependency from bower, not from node) so it is using bootstrap 3.

Regarding:
npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd %s %s (wd=%s<EMAIL_ADDRESS>bower install /root/open-explorer-hertz.network
https://github.com/npm/npm/issues/3497#issuecomment-23966536 Turns out this warning is because I'm running this as root instead of as a secondary user.
Workarounds:

Use a non-root user.
Disregard concerns & use npm install --unsafe-perm

if the postinstall works the bower install is not needed. to run bower as root use bower install --allow-root

Using a non-root user solved the post install problem.

All dependencies are in the last version, this is an old one. closing.


[FEATURE] Adds the 'extras' and other nested properties to BadRequestErrorResponse

Priority
Normal
Description
This adds additional Decodable fields to the BadRequestErrorResponse object. Since the documentation provides an extras key, we can use that to suppliment error handling requests. See the Stellar REST API documentation page here.
When it is passed through along with a HorizonErrorResponse, it's useful to be able to inspect the result codes in the client application so that you can present meaningful error data. For a usage example, see the error handling scenarios of https://github.com/Block-Equity/stellar-ios-wallet/pull/257.
Screenshots
N/A

Hi @ndizazzo thank you for adding the properties


Tracing configuration example YAML switched between Kubernetes and Universal

Something has gone wrong on the tracing example https://kuma.io/docs/1.2.3/policies/traffic-trace/#add-jaeger-backend. Note that the Universal tab contains both Kubernetes and Universal YAML blocks

Thanks for catching, @jpeach -- I'll push a fix today (August 4 UTC-4 to be precise)


.NET Standard 2.0 is final

Summary
.NET Standard 2.0 is final.
You can now start producing .NET Standard 2.0 libraries and NuGet packages. Please use the latest .NET Core 2.0 Preview 2 as it contains many improvements that were necessary to provide a good experience.
Details

Bigger API Surface: We have more than doubled the set of available APIs from 13k in .NET Standard 1.6 to 32k in .NET Standard 2.0. Most of the added APIs are .NET Framework APIs. These additions make it much easier to port existing code to .NET Standard, and, by extension, to any .NET implementation of .NET Standard, such as .NET Core 2.0 and the upcoming version of UWP.

.NET Framework compatibility mode: The vast majority of NuGet packages are currently still targeting .NET Framework. Many projects are currently blocked from moving to .NET Standard because not all their dependencies are targeting .NET Standard yet. That's why we added a compatibility mode that allows .NET Standard projects to depend on .NET Framework libraries as if they were compiled for .NET Standard. Of course, this may not work in all cases (for instance, if the .NET Framework binaries uses WPF), but we found that 70% of all NuGet packages on nuget.org are API compatible with .NET Standard 2.0, so in practice it unblocks many projects.

Broad platform support. .NET Standard 2.0 is supported on the following platforms:

.NET Framework 4.6.1
.NET Core 2.0
Mono 5.4
Xamarin.iOS 10.14
Xamarin.Mac 3.8
Xamarin.Android 7.5
UWP is work in progress and will ship later this year.

Tooling Prerequisites
In general, make sure you run the latest version of the tooling:

.NET Core SDK. You always need to install .NET Core 2.0 Preview 2. This also includes the CLI (dotnet) for building packages, so if you only want to use the CLI, you can stop here.
Visual Studio. If you want to use Visual Studio for authoring .NET Standard 2.0 libraries, you also need to install Visual Studio 2017 15.3. Make sure to use 15.3 and not an earlier version, as this release addressed a couple of key issues to provide a good experience. If you only need to consume .NET Standard 2.0 libraries, you can do that even in Visual Studio 2015 but you'll need NuGet client 3.6 or higher (download from Nuget.org/downloads)
Visual Studio for Mac. The latest version of Visual Studio for Mac supports building .NET Standard 2.0 libraries.
Rider. The latest version also has support for .NET Standard 2.0.

Learn more by reading the .NET Standard FAQ.
Discussion
For discussion, see https://github.com/dotnet/standard/issues/439.

I'm closing this as the announcement has now been publicly communicated in our blog. Of course, this doesn't mean the discussion is over. Keep the questions coming.

Reopening according to process.


_CoqProject support is poor

Support:

-arg "opt" -- send opt to coqtop
-R x y (already supported)
-I x (already supported)
-Q x y (already supported)

Filter out:

files: *.ml, *.mli, *.ml4... ALL FILES (everything tat doesn't start with a dash)
-extra x y z - x y z may be quoted
-extra-phony x y z - x y z may be quoted
VARIABLE = VALUE - value can be quoted
-byte
-opt
-install opt
-f file
-o file
-h
--help

published in 0.2.3


🐛 Only bind the agent role for the addon group

Summary
Related issue(s)
Fixes #

/hold

/unhold

/cc @qiujian16

/cherrypick release-0.15


DynamoDB Lambda Triggers luck policies for AWS SDK

I've followed the doc to created a "DynamoDB Lambda Triggers".
https://docs.amplify.aws/cli/usage/lambda-triggers#dynamodb-lambda-triggers
But the policy lucks actions for using AWS SDK for DynamoDB like these:
"dynamodb:GetItem",
"dynamodb:Query",
"dynamodb:Scan",
"dynamodb:PutItem",
"dynamodb:UpdateItem",
"dynamodb:DeleteItem"

I don't want to use AppSync to update or delete my DynamoDB items from the Lambda function, I'd rather like to use the SDK directly, because of the @auth directive just doesn't allow you do so such actions.

@yaquawa Adding a Lambda function trigger on a DynamoDB table will run the lambda on an action taken on the dynamodb. This question flow does not grant access to the table. You can add the dynamodb table as a resource to access when running amplify function update.
Could you explain your usecase a bit here? Are you looking at using a lambda function as opposed to a VTL Resolver in AppSync? If so you could look into the @function directive to do something like this.

@SwaySway My usecase is do aggregation calculations. for example,
type Post {
    id: ID!
    commentsCount: Int
}

type Comment {
    id: ID!
    postID: ID!
}

so whenever a new Comment was inserted/removed, increment/decrement the corresponding psot's commentsCount field.

The missing step here would be to additionally allow access to the api so it can submit the query operation as well.
Example
➜  bookstore git:(rev) ✗ a add function
? Select which capability you want to add: Lambda function (serverless function)
? Provide an AWS Lambda function name: bookstoreXXX
? Choose the runtime that you want to use: NodeJS
? Choose the function template that you want to use: Lambda trigger
? What event source do you want to associate with Lambda trigger? Amazon DynamoDB Stream
? Choose a DynamoDB event source option Use API category graphql @model backed DynamoDB table(s) in the current Amplify project
Selected resource bookstore
? Choose the graphql @model(s) Entity

Available advanced settings:
- Resource access permissions
- Scheduled recurring invocation
- Lambda layers configuration

? Do you want to configure advanced settings? Yes
? Do you want to access other resources in this project from your Lambda function? Yes
? Select the categories you want this function to have access to. api
? Select the operations you want to permit on bookstore Mutation

Additionally using this similar thread https://github.com/aws-amplify/amplify-cli/issues/3681 you can also increment the count on a field on the Comment model itself and query that field, using a field resolver in Post.
Closing this issue as it's more of a discussion for that we do recommend our discord server: https://discord.gg/jWVbPfC
Should you have any issues related to function permissions please comment below.


fix #19220: polish arity error message

Fix #19220 .
Only overloaded call without spread arguments has new error message. I also change the wording so the message seems more concise than that proposed in #19220. It's up to @DanielRosenwasser.
For single non-overloaded call, the original error message is better than the new one because it provides the range of acceptable argument number.
I cannot find a proper description for spread argument call. The message No overload accepts {0} arguments requires accurate argument number which isn't available in spread argument. So current error message is better IMHO.
Finally, range of argument number in overload function call isn't provided. Showing that range is too complex to preserve a sensible error message.
Thanks for your review in advance!

I would argue that this is (1) rare (2) not that bad of an error message, and that this fix adds more complexity than it's worth. The bad error makes the compiler look silly, but it's not that confusing because it's so obviously incorrect. A quick look at the overload definitions will show which overloads exist -- and that quick look was always needed until recently. The pathological case is something like "1-5 arguments expected, but got 3." where only 1 and 5 parameter-overloads are defined, but nothing in between. But I expect this case to be vanishingly rare. The normal case just requires the user to change from 2 to 1 or 3.
Even if we do decide that "1-3 arguments expected, but got 2." needs to be fixed, the fixed error should not replace errors like "1-2 arguments expected, but got 3" or "... but got 0". These errors are just as correct, are more compact, and convey more information.

Fair argument. Should I close this pull request?

No, I had a long discussion with @mhegazy and we decided that reporting ranges that include overloads is not that useful. Here's what I'd like to see:

Convert the new error to an elaboration (using chainDiagnosticMessages) with the wording "Got 3 arguments, but no overload matched." then "The closest overload requires ${n} parameters."
Recursively call the existing code on a single overload. The overload should be the one with the minimum number of parameters that is greater than the number of arguments, if there is one. Otherwise it should be the overload with the greatest number of parameters. I'm not sure what to do about spread calls.
Modify the existing code to operate on a single signature. It should generate strings of the form "n" or "n-m"; the caller may still need to figure out whether to use an "at least" or "a minimum of" message based on the presence of rest/spread.
Apply this change to type arguments as well, simplifying as needed since there is no rest/spread (YET :woman_astronaut:).

Examples:

f: { (a,b,c); (a,b,c,d,e) } called with f(1,2): "The closest overload requires 3 parameters".
f: { (a,b,c?); (a,b,c,d,e) } called with f(1,2,3,4): "The closest overload requires 5 parameters".
f: { (a,b,c?); (a,b,c,d,e) } called with f(1): "The closest overload requires 1-2 parameters".
f: { (a,b,c); (a,b,c,d) } called with f(1,2,3,4,5): "The closest overload requires 4 parameters".
f: { (a,b,...c); (a,b,c,d) } called with f(1): "The closest overload requires at least 2 parameters".

Note that @mhegazy and I discussed applying this technique to both overloads and optional/rest parameters. That is, give an elaboration for optional parameters as well: "Got 1 arguments, but no signature matched. \n At least 2 parameters are required." This would change error reporting considerably, so I'd have to see it decide if it's a good idea. And it's significantly more complicated to implement, so I think it would be better to try the above technique instead.
In the meantime, I will:

For the existing error messages, flip the wording so that it reads "Got 3 arguments, but expected 2." @mhegazy suggested this to make the reading order more logical.
Apply the existing error messages to extends clause checking as well; I forgot to do this when adding them, so they use an even older message.

Sorry for the late reply. But I'm afraid I am and will be quite busy these day. So I won't have time to refine this pull request.
So let me close this and leave it for other contributors who are interested. Thank you!

No problem; I have 2 other arity fixes that I need to work on, so I will start from this code when I do.
Here's the summary for cross-referencing purposes:

Flip error messages and mention the erroneous function. "${functionName} got 2 arguments, but expected 3-4". #19374
Disallow spreads in calls that already have enough arguments: f(1, ...rest) where f = n => n + 1 #19900


<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed

I'm submitting a ...  (check one with "x")
[X ] bug report => check the FAQ and search github for a similar issue or PR before submitting
[ ] support request => check the FAQ and search github for a similar issue before submitting
[ ] feature request

Current behavior
<EMAIL_ADDRESS>requires a peer of  angular @angular/core@ ^2.0.0 but none was installed
Expected/desired behavior
Make<EMAIL_ADDRESS> require peers of   angular versions 4.X.X
Reproduction of the problem
If the current behavior is a bug or you can illustrate your feature request better with an example, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar. You can use this template as a starting point: http://plnkr.co/edit/tpl:01UjWY3TKfP6pgwXKuEa
What is the expected behavior?
<EMAIL_ADDRESS> should require peers of   angular versions 4.XX
What is the motivation / use case for changing the behavior?
Would still like t use this library after migrating to angular 4.X.X
Please tell us about your environment:

ngx-translate version: 5.0.0

Angular version: 4.3.2

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

+1 for this, we are trying to incorporate shrinkwrap into our build process and this error is preventing us.

@rbarkhouse .For now, I have  to resorted to using @ngx-translate/core which works well with angular versions 4.X,X . My imports have been changed to
import { TranslateModule, TranslateLoader } from '@ngx-translate/core';
from
import {TranslateModule, TranslateStaticLoader, TranslateLoader } from 'ng2-translate';
Hope this will help you.


using BEGIN TRANSACTION; in migration cause migration failed.

Which version and edition of Flyway are you using?
Flyway 5.2.1 (with Spring)
If this is not the latest version, can you reproduce the issue with the latest one as well?
this is the latest version in maven central.
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java API? I'm using Spring boot and it seems that Spring boot handles migration for me.
Which database are you using (type & version)?
SQLite JDBC 3.25.2
Which operating system are you using?
Windows 10
What did you do?
Execute the following migration:
PRAGMA foreign_keys=OFF;

BEGIN TRANSACTION;

CREATE TABLE new_category(
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    name TEXT NOT NULL,
    UNIQUE(name) ON CONFLICT IGNORE
    ord INTEGER
);

INSERT INTO new_category SELECT id, name, ord FROM category;

DROP TABLE category;

ALTER TABLE new_category RENAME TO category;

CREATE INDEX category_name_index ON category(name);

PRAGMA foreign_key_check;

COMMIT;

PRAGMA foreign_keys=on;

What did you expect to see?
According to flyway documentation

If Flyway detects that a specific statement cannot be run within a transaction due to technical limitations of your database, it won’t run that migration within a transaction. Instead it will be marked as non-transactional.

So I expect flyway mark this migration as non-transactional
What did you see instead?
It still wrap this migration in a transaction.
SQL State  : null
Error Code : 1
Message    : [SQLITE_ERROR] SQL error or missing database (cannot start a transaction within a transaction)
Location   : db/migration/V14__RemoveHighlightColumnInCategoryTable.sql (...\out\production\resources\db\migration\V14__RemoveHighlightColumnInCategoryTable.sql)
Line       : 3
Statement  : BEGIN TRANSACTION

This isn't trivial to solve as SQLite only supports a single transaction, via a single connection. Marking the migration as non-transactional isn't enough as it still poses issues with our schema history table management.
The workaround is easy: don't begin or commit transaction within a migration. Flyway already wraps every migration in a transaction for you.
Documented as a limitation.

Sorry for my late reply.
Currently I'm using Java Migration to workaround this, by create a subclass of BaseJavaMigration and override canExecuteInTransaction to return false.
Will this cause any problem? Like flyway's schema history table's management you metioned?
BTW I think execute something outside transaction is important, like the migration I wrote on original post, PRAGMA foreign_keys=OFF;  must be executed outside a transaction. And this is a very common usage to recreate some tables to modify some table scheme.
https://www.sqlite.org/lang_altertable.html

Your workaround should be fine for now. It could make sense for Flyway to automatically mark a migration containing PRAGMA foreign_keys= as non-transactional (even the statement can be run within a transaction, but then it is treated as a no-op which certainly isn't the desired behavior)

Fixed. Migration containing PRAGMA foreign_keys= are now automatically marked as non-transactional.


Incompatible with Dropz

The sapling autoplanting feature doesn't seem to play nicely with whatever mixins Dropz uses in the class it attempts to inject at
log.txt

This is entirely on their end, as they replace the entire ItemEntity#tick method. I could add a hacky workaround, but the correct fix for this would be for them to not replace that entire method.

This is entirely on their end, as they replace the entire ItemEntity#tick method. I could add a hacky workaround, but the correct fix for this would be for them to not replace that entire method.

Fair enough

Fair enough


EvenHubs perf tests fail to build

Repro:
dotnet build .\eng\service.proj
D:\github\azure\net\sdk\eventhub\Azure.Messaging.EventHubs.Processor\perf\Program.cs(22,43): error CS1061: 'EventHubsTestEnvironment' does not contain a definition for 'ShouldRemoveNamespaceAfterTestRunCompletion' and no accessible extension method 'ShouldRemoveNamespaceAfterTestRunCompletion' accepting a first argument of type 'EventHubsTestEnvironment' could be found (are you missing a using directive or an assembly reference?) [D:\github\azure\net\sdk\eventhub\Azure.Messaging.EventHubs.Processor\perf\Azure.Messaging.EventHubs.Processor.Perf.csproj]
D:\github\azure\net\sdk\eventhub\Azure.Messaging.EventHubs.Processor\perf\Program.cs(22,43): error CS1061: 'EventHubsTestEnvironment' does not contain a definition for 'ShouldRemoveNamespaceAfterTestRunCompletion' and no accessible extension method 'ShouldRemoveNamespaceAfterTestRunCompletion' accepting a first argument of type 'EventHubsTestEnvironment' could be found (are you missing a using directive or an assembly reference?) [D:\github\azure\net\sdk\eventhub\Azure.Messaging.EventHubs.Processor\perf\Azure.Messaging.EventHubs.Processor.Perf.csproj]
D:\github\azure\net\sdk\eventhub\Azure.Messaging.EventHubs.Processor\perf\Program.cs(22,43): error CS1061: 'EventHubsTestEnvironment' does not contain a definition for 'ShouldRemoveNamespaceAfterTestRunCompletion' and no accessible extension method 'ShouldRemoveNamespaceAfterTestRunCompletion' accepting a first argument of type 'EventHubsTestEnvironment' could be found (are you missing a using directive or an assembly reference?) [D:\github\azure\net\sdk\eventhub\Azure.Messaging.EventHubs.Processor\perf\Azure.Messaging.EventHubs.Processor.Perf.csproj]

We should also fix our CI pipelines to build perf projects.

Apologies; my understanding was that this work was already completed.   I'll get this patched today.

Please ensure that you're rebased to the latest in main.   The offending lines were fixed as part of commit 0af83e4e121a5aba44f3a2c14a3eb8478f9ce661#diff-423150fb657a5db4380672600162b9c0017a0da5717c8f056e32df9eb70f5f25 in early November.

I see what happened.   A new project was added for the Processor performance tests, which wasn't added to the Event Hubs solution, so it was missed when updating the test environment.     Fixed by #26238.


improve doc on data request form

Continued your work @smk0033 ! 😃 Mostly adding screens, that take in account these changes https://github.com/MAAP-Project/Community/pull/810.
Note : this PR will go to your branch

Thanks Emile, the updates look great!


./configure ends with: error: cannot find Lua libs

On Ubuntu 14.04, cloned the git repo, made sure libharfbuzz, libfreetype6, fontconfig, lua-lpeg-dev, lua-expat-dev, lua-filesystem wera all installed. Bootstrap ran fine, libtoolize gave a number of warnings:
libtoolize: `build-aux/ltmain.sh' is newer: use `--force' to overwrite
libtoolize: `m4/libtool.m4' is newer: use `--force' to overwrite
libtoolize: `m4/ltoptions.m4' is newer: use `--force' to overwrite
libtoolize: `m4/ltversion.m4' is newer: use `--force' to overwrite
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.

./configure ended in: configure: error: cannot find Lua libs
Very interested in trying out Sile, looking forward to some pointers..!

After reading https://github.com/simoncozens/sile/pull/275 I got this idea:
ln -s /usr/lib/x86_64-linux-gnu/liblua5.2.so /usr/lib/x86_64-linux-gnu/liblua.so
Now ./configure && echo OK end OK, but
sudo make install has justenoughharfbuzz_la-justenoughharfbuzz.lo not finding lua.h
I thought this would solve it, but it didn't:
mkdir /usr/include/lua
ln -s /usr/include/lua5.2/lua.h /usr/include/lua/

I'm a little confused by these errors, I'm note sure those libtoolize warnings have anything to do with your real problem as returned in the final exit code. Are there any lines in the output specific to lua libraries?

Also, do you know if Ubuntu has some sort of wrapper or environment hacking going on that allows you to toggle the default lua interpreter version?

It would be nice if autoconf would take setups into account that have lua5.1 and lua5.2 but not plain lua.
Unfortunately, I don't yet know much about lua...

Funny... When I do lua -v it answers Lua 5.1.5 -- I had assumed it would default to 5.2

You said you installed lua-lpeg-dev, lua-expat-dev, and lua-filesystem, but were those packages for your system default of lua of version 5.1?

Try this:
./configure LUA=which lua LUA_INCLUDE=-I/usr/local/include/lua5.2/ LUA_LIB=-llua.5.2

Well... After trying the different permutations for:
./configure LUA=$(which lua) LUA_INCLUDE=-I/usr/local/include/lua5.?/ LUA_LIB=-llua5.?
I found lua5.2 wasn't installed itself... After that both the 1/2 and the 2/2 variety came through configure OK.
But after both cases, when I do `sudo make install` it ends here:
libtool: compile:  gcc -DPACKAGE_NAME=\"SILE\" -DPACKAGE_TARNAME=\"sile\" -DPACKAGE_VERSION=\"0.9.3\" "-DPACKAGE_STRING=\"SILE 0.9.3\""<EMAIL_ADDRESS>-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LUA_H=1 -DHAVE_LUALIB_H=1 -DHAVE_LAUXLIB_H=1 -DHAVE_LUACONF_H=1 -DLIBTHAI=1 -DICU=1 -DSILE_PATH=\"/usr/local/share/sile\" -DSILE_LIB_PATH=\"/usr/local/lib/sile\" -I. -I/usr/include/freetype2 -I/usr/include/lua5.2/ -I/usr/include/harfbuzz -g -O2 -MT fontmetrics_la-fontmetrics.lo -MD -MP -MF .deps/fontmetrics_la-fontmetrics.Tpo -c fontmetrics.c  -fPIC -DPIC -o .libs/fontmetrics_la-fontmetrics.o
fontmetrics.c:3:23: error: missing binary operator before token "("
 #if HB_VERSION_ATLEAST(1,1,3)
                       ^
make[1]: *** [fontmetrics_la-fontmetrics.lo] Error 1
make[1]: Leaving directory `/home/pp/git/sile/src'
make: *** [install-recursive] Error 1

I guess people on Ubuntu is sort of an edge case for you guys. It would be nice if Sile would just be in the repos. Or even on a PPA.

@pepa65 Ubuntu is not an edge case, the release process just hasn't been through very many iterations. I've gotten packaging working on the Linux distro I use,  and poked at a couple others. However there has only been one release since I got involved and we still need to work out a lot of things about the  whole release cycle and packaging. Having an Ubuntu PPA or at least a deb package seems like a reasonable thing. Along these lines I'd like to see a few more point releases (even if they are much smaller steps than the last few) so that we can have the release process worked out before tagging it 1.0.0. Ease of getting up and running is going to be nearly as important as how the typesetter works in encouraging adoption.

That sounds very reasonable. Glad to hear Ubuntu's not an edge case, because it's the main OS (in its variations) I use. Are you on Arch?

Yes, Arch Linux here. There are currently sile and sile-git packages in the AUR.
I also setup a Homebrew package for Mac, but there are outstanding issues with Lua there too (#143).

We use Travis to test SILE on every commit, and Travis uses Ubuntu, so we have to and we do support Ubuntu! However Travis is on Ubuntu 12.02 - maybe something is different in Trusty. I'd like to get Travis doing integration checks on its beta environment too, which runs 14.04.
In particular it looks like something is going weird evaluating the Harfbuzz version check macro.  (Ping @behdad)
Which version of Harfbuzz is being installed?

dpkg -l |grep harfbuzz
ii libharfbuzz-dev 0.9.27-1ubuntu1 amd64 Development files for OpenType text shaping engine
ii libharfbuzz-gobject0:amd64 0.9.27-1ubuntu1 amd64 OpenType text shaping engine ICU backend (GObject library)
ii libharfbuzz-icu0:amd64 0.9.27-1ubuntu1 amd64 OpenType text shaping engine ICU backend
ii libharfbuzz0b:amd64 0.9.27-1ubuntu1 amd64 OpenType text shaping engine (shared library)
ii libharfbuzz0b:i386 0.9.27-1ubuntu1 i386 OpenType text shaping engine (shared library)

Bah, before 0.9.30, the macro used to be called HB_VERSION_CHECK:
commit 2b051c6057920c564c13c5d6a3e6dca93446fa12
Author: Behdad Esfahbod<EMAIL_ADDRESS>Date:   Fri Jun 20 14:09:57 2014 -0400

  Rename HB_VERSION_CHECK and hb_version_check to "atleast"

  HB_VERSION_CHECK's comparison was originally written wrongly
  by mistake.  When API tests were written, they were also written
  wrongly to pass given the wrong implementation... Sigh.

  Given the purpose of this API, there's no point in fixing it
  without renaming it.  As such, rename.

  API changes:

    HB_VERSION_CHECK -> HB_VERSION_ATLEAST
    hb_version_check -> hb_version_atleast

Oh boy. How do we work around this one?

Do this:
#ifndef HB_VERSION_ATLEAST
#define HB_VERSION_ATLEAST(major,minor,micro) \
        ((major)*10000+(minor)*100+(micro) <= \
         HB_VERSION_MAJOR*10000+HB_VERSION_MINOR*100+HB_VERSION_MICRO)
#endif

and use that one instead of HB_VERSION_CHECK().

In my local tree, the only occurrence of HB_VERSION is in src/fontmetrics.c:
#if HB_VERSION_ATLEAST(1,1,3)
There is no HB_VERSION_CHECK here...

Yeah, I was using HB_VERSION_ATLEAST but that wasn't available for older HB versions. Now I've added the definition for  HB_VERSION_ATLEAST if it's not provided, into fontmetrics.c, so please update and try a build again.

OK, pulled, built and installed. On run:
This is SILE 0.9.4-unreleased

! libtexpdf backend not available! at nil
/usr/bin/lua: core/utilities.lua:18: attempt to index field 'outputter' (a nil value)
stack traceback:
	core/utilities.lua:18: in function 'error'
	core/sile.lua:46: in function 'init'
	/usr/local/bin/sile:11: in main chunk
	[C]: in ?

So the libtexpdf backend built, but couldn't be loaded. Could you do:
 % sile
This is SILE 0.9.4-unreleased
> require("justenoughlibtexpdf")

and tell me what the error is?

I don't understand the instructions. Where do I put the require("justenoughlibtexpdf")? Note that after running sile on the commandline, it dumps.

Ah, of course; it wouldn't get as far as the REPL. OK, I'm going to look at this in a few days when I can play with a Trusty image myself. Sorry about this - this really is the kind of environment where it should just work, which makes it doubly confusing when it doesn't.

Great, thanks for working on this.

@pepa65 did you end up installing a lua dev package (e.g. liblua5.1-0-dev)? This is what I had to do to get SILE to build on Debian.
@simoncozens what is the reason for compiling Lua on Travis instead of using Ubuntu's lua packages?

Until recently Travis only supported Ubuntu Precise, which doesn't have any lua packages.

Sorry, I've migrated (am migrating) to 16.04, haven't gotten around to trying anything with Sile. Anybody tried this yet?

@pepa65 I have SILE 0.9.3 working on Debian. In addition to the lua dev package, I had to manually run sudo ldconfig to allow it to find libtexpdf.so.0 when run outside of the checked out source.

Yeah, I bet you ldconfig is the answer. It only works on Travis because we set LD_... environment paths manually.

In case it's useful, I put up a rough packaging at https://launchpad.net/~olivier-berten/+archive/ubuntu/sile
As I'm definitely no packaging expert, feel free to give me improvement advices ;-)

Thank you Olivier. I installed sile after adding your PPA, and it pulled in lua5.2, but did nothing on the harfbuzz front. What is the purpose of the harfbuzz package in your PPA? (I can't even find it when I do apt search harfbuzz...)
Also, isn't it good to include the lua classes in git/tests as well?

Repositor

In case it's useful, I put up a rough packaging at https://launchpad.net/~olivier-berten/+archive/ubuntu/sile
As I'm definitely no packaging expert, feel free to give me improvement advices ;-)

Repository is unreachable

When executing sudo add-apt-repository ppa:olivier-berten/sile it ends with:
E: The repository 'http://ppa.launchpad.net/olivier-berten/sile/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

It is a great pity that such a promising project is proving so hard to install...


Reintroduce Institution Status on Account Registration

As mentioned on https://github.com/cfpb/hmda-platform-auth/pull/31#pullrequestreview-11079721, the institution status indicators didn't make it as part of the FFIEC rebranding of Keycloak.  Let's figure out a  way to bring those back.
For reference, here's the diff:
Old (generic Keycloak theme)

New (FFIEC branded)

This is no longer applicable now that we're searching based on email domain instead of institution name.


Organization access"

Extension version:
VSCode Version:
OS:

Steps to Reproduce:

Closing in favor of https://github.com/microsoft/vscode-pull-request-github/issues/2150


Is it possible to merge any examples of AirSync? (IDFGH-4940)

@xuhongv ESP32 support WeChat airsync. We will merge the airsync example into latest IDF.
Originally posted by @Weijian-Espressif in https://github.com/espressif/esp-idf/issues/4055#issuecomment-532204720

Thanks

Not a Bluetooth developer here, just commenting on the airsync issue from my perspective.
Tencent hasn't released airsync code under a license compatible with Apache 2.0 license used by ESP-IDF, and that prevents the code from being merged.
That being said, it doesn't prevent the code from being released as a standalone component under a different license, similar to WolfSSL.


Feat/initial-pipeline-setup

installing or update of trivy operator
installing or update of trivy defectdojo reporter
missconfig scan only for container scanner
documentation draft

What's the status here?


Node sphere

Node name: sphere
Node ID: cdb2938ad8ae1dc1

rejected:B1
It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Logs are missing
We’ve thus marked B1 as rejected, however if this is a mistake, please upload the log summary and we can re-review.

rejected:B4
reason:account address not submitted, cannot verify on-chain AddBaker transaction

rejected:B4
reason:account address not submitted, cannot verify on-chain AddBaker transaction


Linptech Doorbell G04

Device model / 设备型号
linp.doorbell.g04
Component version / 插件版本
1.0.5
HA core version / HA版本
2024.12.2
Integrated mode / 集成方式
Automatic (自动模式)
The problem / 问题详情
Volume not displayed correctly
Not able to turn off the doorbell speaker
No notification of ringing in home assistant

Entity attributes / 实体属性
media_player.linp_g04_6fea_doorbell
switch.linp_g04_6fea_switch_status

Home Assistant Logs / 系统日志
No response

Hello!
It's posible to do the same for:
https://home.miot-spec.com/s/linp.doorbell.g03
Thanks!

@fangathome Is it fixed now?


How to get all keys without order by?

Team,
Is there anyway to read all the key/values in the same way we perform this query in any database but without using ascend or descend because sorting unnecessary makes a performance hit
select * from table
Does blunt db supports such behavior?

BuntDB does not have tables. It's a database with single set of key/value items ordered by the key of each item.
The Ascend does not perform ordering, because the data is already ordered. It just scans each item, one after another.
It's fast.
Under the hood, BuntDB uses a B-tree for storing data, and scanning a B-tree data is probably the fastest scan you can get from any type of tree-based data structure.


url shorter

with this small script you can make any link shorter!

Provide a README on how to use this project and move it to your_projects directory


Add Doks theme

The preview build failed for some reason that looks like my fault. I will look into it later. But the theme looks great, I didn't know about it.

@h-enk could you please rebase against the main branch? The checks fail because another theme deleted a release tag that would be used in that specific version to build the preview. This issue should have been fixed in https://github.com/gohugoio/hugoThemesSiteBuilder/commit/ca3f9f392ab8a5582fa3c502b254463949321e89.

@digitalcraftsman no, this fails for another reason. Could you pause the merging of the PRs for the day? I need to fix something in Hugo etc.

Sure, I'll stop merging themes for now. I thought the issue has been resolved since you've merged #10 and #11 without problems.

@digitalcraftsman it's resolved now, but I suspect that many of these themes (including this one) is already in the main branch.

Thanks!


Timer structure

[Note] I think that it more convenient to use same syntax everywhere. Im talking about '{'. I noticed that you moving them to new lines, I suppose we can talk about this next time with other team members.


NETOBSERV-313 Topology: automatically fit view

Automatically fit view when filters / options are updated

It doesn't seem to work properly on my local machine (see attached video).
When I show the topology, it starts with fit view, then if I reset the view, I cannot fit it anymore since the button only allows me to reset the view.
https://user-images.githubusercontent.com/939550/165917776-8f3a2120-5794-4862-8ce1-c519bc947609.mp4
.

It doesn't seem to work properly on my local machine (see attached video).

This is the expected behavior but probably not good UX here. Sorry !
The view fit by itself at first start + each time you change a filter or an option.
Maybe the reset view button doesn't make sense anymore since it reset position to 'center' and scale to 'default' (but it's not equal to the first view you see anymore).
If you press the fit to screen button on the left you will fit all items in view to your screen (position + scale).
I suggest to delete the reset button and only keep the fit one.

Yeah I just realized i was clicking the wrong button 😅


Upgrade Fuzzit client to 2.4.61

Upgrades Fuzzit client to the latest 2.4.61. Update to the Fuzzit integration #254.
There's a successful build here:
https://travis-ci.org/bookmoons/ffjson/builds/591427357
Corrected instructions to handle credentials. This should solve the build issue with the last patch:

In Fuzzit use the dropdown to switch to the ffjson org.
In settings grab an API key.
In repo settings in Travis paste it to envvar FUZZIT_API_KEY.

This build failure seems to be a network error connecting to GitHub. Maybe Travis is having network issues:
fatal: unable to access 'https://github.com/golang/lint/': Failed to connect to github.com port 443: Connection timed out

I had a similar failure but it disappeared when I ran the build again.

I see that got the build running. Thanks a lot for merging.


BufferKind::U64

Is the lack of BufferKind::U64 just caused my unimplementation or is it an ODBC limitation?

There is an SQL_C_UBIGINT variant. So these bindings could support a 64Bit unsigned buffer. See: https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/c-data-types.
However, most databases do not support unsigned 64Bit integers. The SQL standard also knows only signed integers. Some databases (looking at you Oracle) do not even support signed 64Bit integers.
If you have a usecase for this, we can implement this. If your application wants to be compatible with a wide range of databases I would advice against using it though.
Best, Markus

Thanks! Just going to be unsafe and convert to u64 (and hope for the best...) for now.
Closing. Anyone can feel free to reopen if desired.


⚠ Bofrost.es has degraded performance

In 10de14e, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1273 ms

Resolved: Bofrost.es performance has improved in 76234c5 after 6 minutes.


User does not land on Zeppelin UI Login page after clicking logout button when Zeppelin is running behind proxy server.

What is this PR for?
The user is no more on Zeppelin UI Login page after clicking logout button or links where user doesn't have access to when Zeppelin is running behind a proxy server like Nginx.
What type of PR is it?
[Bug Fix]
What is the Jira issue?

ZEPPELIN-2601

How should this be tested?
Set up any reverse proxy server like Nginx, exmaple config below;
location /abc/def/zeppelin/ {
        proxy_pass http://localhost:8080/;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
}

And now from browser navigate to this URL, and click on any like for which user doesn't have access to. In my example user1 did not have access to any of /api/interpreter/** /api/configurations/** and /api/credential/**
Screenshots (if appropriate)
Before:

After:

Questions:

Does the licenses files need update?
Is there breaking changes for older versions?
Does this needs documentation?

CI green, ready for review.

Tested locally and works as described. LGTM except for a comment.

Merging this if no more discussion.


cs47l63: Fix uninitialized return value

Return CS47L63_STATUS_OK instead of ret

@cirrus-jasonm Is this ok to merge? We see warnings on compile because of this

@cirrus-jasonm can this get merged? It is causing some troubles with our build systems.


Feature: History/Undo/Redo

https://github.com/intendednull/yewdux/issues/53#issue-1709773761
This change adds a yewdux-utils crate with a listener that tracks the history of a state and enables undo/redo.
It works very nicely  - try running new history example.
There's a couple of issues with it that I would like some feedback on.
Firstly, it should be able to initialize it by just injecting the listener using the attribute macro like this:
#[derive(Debug, Default, Clone, PartialEq, Eq)]
#[store(listener(HistoryListener<State>)]
struct State {
    count: u32,
}

but the person who implemented that attribute macro (it was me!) decided to use PathList which apparently doesn't support generic types. I've asked on the Darling repo but I'm pretty sure there's no way to make that work.
So you have to initialize it the old way
impl Store for State {
    fn new() -> Self {
        init_listener(HistoryListener::<State>::default());
        Self::default()
    }

    fn should_notify(&self, old: &Self) -> bool {
        self != old
    }
}

The other thing is that the undo tracking currently tracks a potentially infinite number of states which could lead to running out of memory quite quickly if you don't clear it periodically. I think it might be better to let you set a limit on the number of states.

Looks great! Thank you for your contribution


ADDED : The Cybersecurity

Hey @anandmohan23 !
First of all sorry for the delay, I was busy with some of my other projects. Congrats on submitting your pull request and thank you for taking out the time to contribute in this project.
Your PR has been merged and the changes will be reflected on the website in a few minutes,.
Do leave a star, if you liked the repo ;)
Happy hacking ! 🎊

hey,
happy Hacktoberfest


Update Composer dependencies (2020-12-21-00-08)

Visual regression test passed!
View the visual regression test report


Alignment of the Home Page

The home page looks good being left aligned but the left margin should be corrected.

Yes. Thanks for raising this @itisrizu .

I'll fix this, @codewithvoid can you assign this to me.

Thanks @PriteshKiri . Fixed in #113.


util/mknum.pl should not add duplicate entries

When the same function happens to be declared in more than one public header
make ordinals should not add them multiple times to, e.g., util/libcrypto.num but give an error.

When the function was already in the list and a further declaration for it shows up in a public header a duplicate is added to the list even silently.

@DDvO do you have an example of this occurring currently?

I've just tried it out: after adding a duplicate declaration, a suitable error is thrown.
So this bug has been fixed meanwhile.


Menu for Point "Split Here"

I really need this menu, since it's now so confusing and hard to just split tracks..

I have updated the scissors tool. In addition to clicking anywhere on the trace to split it there, I have added "split markers" at relevant locations (more or less of them are shown depending on the zoom level).

I have updated the scissors tool. In addition to clicking anywhere on the trace to split it there, I have added "split markers" at relevant locations (more or less of them are shown depending on the zoom level).

I’m not sure when it will be available but still not seeing this.

It's online since the last build.

It's online since the last build.

Have no idea what do you mean.. I'm expecting to see the menu as indicated in first post, like to just split in point.
For now I just see a remove point menu.

You need to use the "scissors" tool...

You need to use the "scissors" tool...

I tried - clicked.. and nothing happening. I like more old way with right click menu like.


PyCharm crashes due to an Out of Memory Error when plugin is enabled

Describe the bug
Whenever I open a project in PyCharm with the plugin enabled, it will freeze after about 30 seconds, then it will crash some time later.
To Reproduce
Steps to reproduce the behavior:

Open a project in PyCharm
Wait about 30 seconds

Note: I can't reproduce this on all of my projects, only some of them. For the projects that do cause this behavior though, it does it reliably.
Edit: I can reproduce with structlog. I needed to play a bit with the IDE to trigger the issue though, for example going in the interpreter settings.
Expected behavior
No freeze
Screenshots
N/A
Environments (please complete the following information):

IDE: PyCharm Professional 2023.2.1
OS: Arch Linux
Ruff Version: 0.0.291
Plugin version: 0.0.21

Additional context
See crash log
java_error_in_pycharm_53357.log.gz

@mathieu-lemay
Thank you for creating the issue.
I tried to reproduce what you have indicated but could not reproduce it in my environment.
If the problem occurs with 0.0.21 and not with 0.0.20, I can identify the PR in question and will try to fix the code that seems to have the problem.

@koxudaxi Well I started PyCharm with the plugin version 0.0.21, and sure enough, it froze. I then downgraded the plugin to 0.0.20 to check and the issue disappeared.
Now the weird thing, I re-updated to 0.0.21 and no matter what project I open, I can not reproduce the issue anymore. I did tick the Use ruff-lsp option while I was on 0.0.20 so I though maybe it was that, but now even if I disable that option, I can't reproduce. Not sure what to make of that. I am still pretty certain I started having the issue after upgrading to 0.0.21 though.
I have another computer with the same issue, I'll try tomorrow if I can make the issue stop with the ruff-lsp option.

@mathieu-lemay
Thank you for additional information.
In 0.0.21, the version of ruff is now retrieved to check if the format command is supported.
I am currently calling ruff --verison to get the version, but I think this is the cause of the hang. (e.g. being called infinitely in certain situations)
If the version is not cached, ruff --version is called when ruff is called.
I wanted to use the version of ruff installed in the project's virtual env, because it is easy to get the version of ruff.
However, the global ruff is not directly managed by the PyCharm project, so it is necessary to call ruff --version.
However, I don't think global ruff is changed frequently, so it may be enough to call ruff --version at project startup or at the time of global executable change.

Hi,
I have the exact same issue, like every 30-60 seconds I get that error. I have Ruff 0.0.21, Pycharm professional 2023.2.1 and my OS is arch linux.
here is the log:
java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
	at java.base/java.lang.Thread.start0(Native Method)
	at java.base/java.lang.Thread.start(Thread.java:802)
	at java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:945)
	at java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1364)
	at java.base/java.lang.ProcessHandleImpl.completion(ProcessHandleImpl.java:144)
	at java.base/java.lang.ProcessImpl.initStreams(ProcessImpl.java:363)
	at java.base/java.lang.ProcessImpl.lambda$new$0(ProcessImpl.java:326)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:325)
	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
	at com.intellij.execution.configurations.GeneralCommandLine.startProcess(GeneralCommandLine.java:432)
	at com.intellij.execution.configurations.GeneralCommandLine.createProcess(GeneralCommandLine.java:346)
	at com.intellij.execution.process.OSProcessHandler.startProcess(OSProcessHandler.java:84)
	at com.intellij.execution.process.OSProcessHandler.<init>(OSProcessHandler.java:44)
	at com.intellij.execution.process.CapturingProcessHandler.<init>(CapturingProcessHandler.java:20)
	at com.koxudaxi.ruff.RuffKt.runCommand(Ruff.kt:199)
	at com.koxudaxi.ruff.RuffKt.runCommand(Ruff.kt:178)
	at com.koxudaxi.ruff.RuffKt.runRuff(Ruff.kt:289)
	at com.koxudaxi.ruff.RuffKt.runRuff(Ruff.kt:246)
	at com.koxudaxi.ruff.RuffCacheService$getVersion$$inlined$executeOnPooledThread$default$1.call(Ruff.kt:438)
	at com.intellij.openapi.application.impl.ApplicationImpl$3.call(ApplicationImpl.java:303)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
	at java.base/java.lang.Thread.run(Thread.java:833)

@koxudaxi I agree that checking only once at project startup should be sufficient. Even if someone opens a project while they have an older version of ruff without format support, then update the global ruff executable while the project is open, the worst that would happen is that the plugin wouldn't know about it until next project open. I could see a slight issue if a user downgrades ruff, but that is quite an edge case.
In the meantime, I think I figured out why I couldn't reproduce the issue anymore yesterday. Explicitly setting globalRuffExecutablePath seems to make the problem go away. I deleted the ruff.xml file from my project and sure enough, it crashed within a few minutes. Put the file back in the project, problem went away.
@PasVegan Maybe this could work for you too. Create a ruff.xml file in the .idea folder of your project with this:
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
  <component name="RuffConfigService">
    <option name="globalRuffExecutablePath" value="/usr/bin/ruff" />
  </component>
</project>

I also had this issue recently (on v. 0.0.21)
When I enabled the plugin - I was working in project_A; when I opened project_B PyCharm came to a grinding halt and I couldn't figure out why.
I would force close it and reopen the previous project and it would work fine.
Then I disabled the plugin and opened project_B and had no issues. Then I re-enabled the plugin while working in project_B and have had zero issues.
I think it has something to do with opening a new project that has never used the plugin before with the plugin enabled or something along those lines.
However I checked the box to use my global installation of ruff as well. But after disable / open project_B / enable the plugin while working in that project?
I haven't seen any issues in any other projects.
My guess would be something with the original setting/initializing of the plugin somewhere?

Thank you all for your comments.
They are accommodating.
I have temporarily stopped publishing the plugin because 0.0.21 has only an experimental feature added, which was too problematic.
I want to release a fixed version tomorrow or next tomorrow, but after that JetBrains will need to approve on the JetBrains side, so there maybe a low probability that it will be released this week.

The following policies are used to create this PR.
https://github.com/koxudaxi/ruff-pycharm-plugin/pull/272

Run ruff --version asynchronously
Run ruff --version only in the following three patterns

When the package list is updated
When you save changes in the configuration screen
At project initialization (if version is undetected)

Thank you for waiting for the fixed version.
I have released a fixed version.
However, it takes 1-2 business days for JetBrains to review it, so if you want to use the fixed version right now, please download the zip from the release page and install it manually.
If you have any feedback, please feel free to write any comments!
Fixed version: https://github.com/koxudaxi/ruff-pycharm-plugin/releases/tag/v0.0.22
How to install: https://koxudaxi.github.io/ruff-pycharm-plugin/install/#complied-binary

@koxudaxi I'm giving it a try, so far so good.
BTW, I just realized you also developed the Poetry plugin and the Pydantic plugin. Damn, keep up the good work!

@mathieu-lemay
The version has been published in the market.
We can close the issue.
Thank you very much!!

@mathieu-lemay
Thank you for sponsoring me!!
The support of people like you is very encouraging for my activities :smile:


feat: test deploy preview subdomain

Succesfully deployed on: https://ci/test-deploy-preview-subdomain.paybutton.io

New version of this PR deployed on: https://${env.BRANCH_NAME////-}.paybutton.io

New version of this PR deployed on: https://refs-pull/25/merge.paybutton.io

New version of this PR deployed on: https://ci-test-deploy-preview-subdomain.paybutton.io

New version of this PR deployed on: https://ci-test-deploy-preview-subdomain.paybutton.io


[SPARK-27000][PYTHON] Upgrades cloudpickle to v0.8.0

What changes were proposed in this pull request?
After upgrading cloudpickle to 0.6.1 at https://github.com/apache/spark/pull/20691, one regression was found. Cloudpickle had a critical https://github.com/cloudpipe/cloudpickle/pull/240 for that.
Basically, it currently looks existing globals would override globals shipped in a function's, meaning:
Before:
>>> def hey():
...     return "Hi"
...
>>> spark.range(1).rdd.map(lambda _: hey()).collect()
['Hi']
>>> def hey():
...     return "Yeah"
...
>>> spark.range(1).rdd.map(lambda _: hey()).collect()
['Hi']

After:
>>> def hey():
...     return "Hi"
...
>>> spark.range(1).rdd.map(lambda _: hey()).collect()
['Hi']
>>>
>>> def hey():
...     return "Yeah"
...
>>> spark.range(1).rdd.map(lambda _: hey()).collect()
['Yeah']

Therefore, this PR upgrades cloudpickle to 0.8.0.
Note that cloudpickle's release cycle is quite short.
Between 0.6.1 and 0.7.0, it contains minor bug fixes. I don't see notable changes to double check and/or avoid.
There is virtually only this fix between 0.7.0 and 0.8.1 - other fixes are about testing.
How was this patch tested?
Manually tested, tests were added. Verified unit tests were added in cloudpickle.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8316/
Test PASSed.

Test build #102811 has started for PR 23904 at commit 746051e.

cc @gatorsmile, @BryanCutler, @srowen, @viirya, @inpefess

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8317/
Test PASSed.

Test build #102812 has started for PR 23904 at commit 3e0afd1.

Test build #102812 has finished for PR 23904 at commit 3e0afd1.

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

Merged build finished. Test PASSed.

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

Test build #102811 has finished for PR 23904 at commit 746051e.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8323/
Test PASSed.

Test build #102818 has started for PR 23904 at commit 3e0afd1.

Test build #102818 has finished for PR 23904 at commit 3e0afd1.

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

Merged build finished. Test PASSed.

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

Let me get this in. The pickle protocol change at #20691 was closely reviewed and I think it's still important change to keep than revert for now.


etcd namer

We have the ability to do this (we have an etcd client), but we don't have any authoritative service registry scheme for etcd. We should open tickets for each of these schemes, if they exist.


Suggestion: Use prepublishOnly instead of prepare for running build script?

As per the npm docs, prepare runs both after install and before npm publish. I personally can't think of any situations I'd want to build the module after each install, but if that's intentional then that's cool, it's not much effort when generating a new project to change. However, if this is not the intended behavior then it would be nice to have the default be to use the prepublishOnly npm script instead to only run builds before npm publish, and not after installs.

You are right. Thanks for bringing my attention to it. It's a leftover from earlier NPM versions. I'll make the change and publish a new version sometime in the next week.


Call 'fastlane' fail when in bash scrip

I'm working with AppleScript, it's calling my bash script:

And here is my bash script:

But I got error:

In fast, everything is working well if I call fastlane directly from Mac Terminal.

@fastlane-bot
Thanks so much man, I updated my question.

Seems like Apple script doesn't access your shell environment. You can try the following

Run this in the terminal manually which fastlane
Copy the full path and use that in your Apple script

Try this:
#!/bin/bash --login
[[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm"

#Debug checks...
rvm list
fastlane --version
[... rest of the original script]

Depending on how your shell is setup, this may do the trick.
if that fails too try to use bash --login to invoke your shell script from AppleScript.

@KrauseFx @Panajev
Yes, it works, I did it like this:
#fastlane env
export PATH="/Users/XXX/.rbenv/versions/2.4.3/bin:$PATH"
Thanks so much, man.

Awesome 👍


[SCHEMA] bep012 functional derivatives

My attempt at schematizing bep012. New in this PR, regex based column names.

Can't figure out the yamllint error. That line looks a lot like other checks with includes statements


Fixed #634 - Formatting on admonitions looked off.

Before:

After:

Coverage remained the same at 100.0% when pulling b78d1618f932b29baba8b4d403cc563b261a8fc0 on jgeewax:634-admonition-formatting into f73ad7e8fc877e14e2f9c0b4ec42430f2396f770 on GoogleCloudPlatform:master.

LGTM

@jgeewax I'm going to merge this for you. Typically @tseaver and I merge our own PRs in case we need to handle rebases or other, but I'm not sure what your expectation is.

Whatever works :)


Bubble Sort in C

An issue was raised, for uploading sorting algorithms. Here is Bubble Sort in C.

unnecessary time is taken


gen_odd

probably a bad solution for #9

this doesn't make sense with cudnn anymore. this will probably just be an annoying issue - or we should do the same with tensors


Upper bound Memento to 1.2 for CloudWatchLogs

I'm not sure if I'm doing this right, but my understanding is that retroactively upperbound dependencies for a package requires manually editing the Compat.toml?

Memento made a breaking release without bumping major version or what happened here? Wouldn't it be better to revoke the faulty version of Memento then?

More that CloudWatchLogs.jl made a faulty assumption about the timezone of an internal datetime field. This was never getting hit because we previously defaulted to an explicit ZonedDateTime. Memento is changing the default behaviour to add timezone information later in the pipeline and assume all datetimes are localzone.
https://github.com/invenia/CloudWatchLogs.jl/blob/master/src/event.jl#L10

Does the above response make sense or do you recommend just updating CWL.jl and maybe backporting the fix to previous releases?


Forza Horizon 5 DLSSTweaks is not working

nvgx.dll
XInput1_3.dll
XInput1_4.dll
XInput9_1_0.dll
dxgi.dll
XAPOFX1_5.dll
X3DAudio1_7.dll
winmm.dll
What filename should i use to get dlsstweaks work?

Hello i have also tried every method to get it working. and have found nothing :(


[GH-898] Add callRateThreshold too since it's mandatory now.

Purpose

https://broadinstitute.atlassian.net/browse/GH-898

Changes

Add callRateThreshold too since it's mandatory now.

Review Instructions

I want to learn from @tbl3rd about how to test this

Can you add this key to the test message that the end-to-end test uses? https://github.com/broadinstitute/push-to-cloud-service/blob/master/test/data/plumbing-test-jms-dev.edn#L8

Can you add this key to the test message that the end-to-end test uses? https://github.com/broadinstitute/push-to-cloud-service/blob/master/test/data/plumbing-test-jms-dev.edn#L8

I think that key is already in that message! :callRateThreshold


New DEV branch file selection from front end to delete from graph not working for a file stuck in processing state

New DEV branch file selection from front end to delete from graph not working for a file stuck in processing state. The file is not actually undergoing processing and seems orphaned

Hi @swanandbagve if you process any large files parallel if you try to upload or process any small files it is too much time we already working on that until please clear the DB and play with small files.

Now uploading and processing for files is working in parallel in latest release of app.


added build and stop docker-compose scripts

Thanks for the notes Dmitry, after playing with it, I see that it definitely makes sense to keep dev.sh and production.sh separate. I am a bash noob, so the concept of exporting the variables for use in other scripts took a bit to sink in. Let me know your thoughts on how it is now.
Thanks :-)

Yep I have tested locally, should I test with running the "Environment=production" portion locally? I figure that would only work on the server?
Sent from my iPhone

On Nov 13, 2016, at 1:50 PM, Dmitry Pashkevich<EMAIL_ADDRESS>wrote:
@dpashkevich approved this pull request.
Looks good! Have you tested this locally?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

You can kind of test the environment set up as well, if you locally change WEB_PORT to 8090 in production.sh. Also, obviously you'll get passwords in your config files that don't match your local credentials, so the wiki and wordpress won't be able to connect to your database, but at least you'll be able to verify that the containers run correctly

Thanks for working on this task btw, I like how modular the solution ended up being

I approved the PR, feel free to merge if you think it's ready to go

Thanks, I appreciate your notes :-) I have been trying to think as
modularly as possible since starting to play with Node, this little task
has helped for sure! I will test the production script locally, per your
suggestion above, as long as there aren't issues with it, I will merge.
Remind me again though, are we doing a merge and squash? Or just merging in
with all the commits as they appear on the scripts branch?
On Sun, Nov 13, 2016 at 2:13 PM, Dmitry Pashkevich<EMAIL_ADDRESS>
wrote:

I approved the PR, feel free to merge if you think it's ready to go
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/oc4d/main/pull/13#issuecomment-260213302, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALit42KiWT5L0PPhX4KnLZyKjydA0eNGks5q931xgaJpZM4KkcG0
.

I think doing a plain merge is totally fine in most cases. I would only
ammend commits or do a rebase if I either completely pivot from my original
solution and don't want to keep the old one in history, or if I forgot to
include a few small changes and I really want to add them to an existing
commit so that there's not a "broken" commit in the history.
On Sun, Nov 13, 2016 at 2:27 PM ranyehushua<EMAIL_ADDRESS>wrote:

Thanks, I appreciate your notes :-) I have been trying to think as
modularly as possible since starting to play with Node, this little task
has helped for sure! I will test the production script locally, per your
suggestion above, as long as there aren't issues with it, I will merge.
Remind me again though, are we doing a merge and squash? Or just merging in
with all the commits as they appear on the scripts branch?
On Sun, Nov 13, 2016 at 2:13 PM, Dmitry Pashkevich <
<EMAIL_ADDRESS>
wrote:

I approved the PR, feel free to merge if you think it's ready to go
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/oc4d/main/pull/13#issuecomment-260213302, or mute
the thread
<
https://github.com/notifications/unsubscribe-auth/ALit42KiWT5L0PPhX4KnLZyKjydA0eNGks5q931xgaJpZM4KkcG0
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/oc4d/main/pull/13#issuecomment-260214131, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABGqbeYXZekcW4V7dIq0_CU_Hi43NpTMks5q94CygaJpZM4KkcG0
.

--
Dmitry Pashkevich

Yea, the only issue I am seeing in production is that my local machine does
not have the proper access rights to read the 'secret' repo, but otherwsie
it seems to be working!
On Sun, Nov 13, 2016 at 2:27 PM, ran yehushua<EMAIL_ADDRESS>wrote:

Thanks, I appreciate your notes :-) I have been trying to think as
modularly as possible since starting to play with Node, this little task
has helped for sure! I will test the production script locally, per your
suggestion above, as long as there aren't issues with it, I will merge.
Remind me again though, are we doing a merge and squash? Or just merging
in with all the commits as they appear on the scripts branch?
On Sun, Nov 13, 2016 at 2:13 PM, Dmitry Pashkevich <
<EMAIL_ADDRESS>wrote:

I approved the PR, feel free to merge if you think it's ready to go
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/oc4d/main/pull/13#issuecomment-260213302, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALit42KiWT5L0PPhX4KnLZyKjydA0eNGks5q931xgaJpZM4KkcG0
.

Great! Let's ship it :)


JToken.Remove error when trying to remove a JProperty

The answer on SO about the error thrown in this case is helpful to understand why the error happens in the first place. http://stackoverflow.com/a/21899609/6378458
But couldn't JToken.Remove check for the potential of this error being thrown itself and in that case do the .Parent.Remove() way itself internally?
After reading the answer a few times I've understood why it works with .Parent.Remove() and why not without, but given the description of JToken.Remove(), mainly the part about it removing the element from it's parent, does .Parent.Remove() at first sound as if you'd be now about to remove the element you wanted to remove something from too.

The problem with making it remove the property is someone will call .Remove and then expect the .Parent property to be null, but it won't, the parent JProperty's .Parent will be null.


Laradumps response on ds, of any type is not working after update

Let me know if I can contribute in any way to resolve this
this is after I updated Laradumps. Before it was working fine.
The version I actually installed and using now, is 1.7.2

Hello!, I believe this could be a bug in the Laradumps app due to differing versions they support. Please update your composer package to version greater than v2
https://laradumps.dev/get-started/upgrade-guide.html


  Is that OK or should that situation also be handled?

Decided to take a better approach @ this.


Device information service is override by the MAC's data on Yosemite

I updated my mac mini to yosemite and recognised that instead of the device information service I configure with bleno, I see the mac's data (e.g. manfufacturer name string characteristics has the value 'Apple inc.' instead of "abc ltd" set by me).

@kapusil OS X 10.10 has some built-in services/characteristic for device information etc. now, which you cannot override.
I could make changes to bleno to report a failure when you try to use them.

@sandeepmistry
Thanks for the feedback. I think the error message is a good idea if there is no way to overwrite them.

@kapusil no problem. Commit https://github.com/sandeepmistry/bleno/commit/f64c805ee13aeec955e2c418e21f593615bf1c54 will report errors for UUID's which are not allowed.


[FEATURE] Add option to end pagetrees by doktype

This new option will end a pagetree per default when a backend user section or recycler is found. This patch also fixes some inconsistencies with the dependency version.
Also the page tree recursion will be skipped for a page with "Stop Page Tree" checked.

FYI: https://projekte.in2code.de/issues/26973


Fix screenshot tests

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 68.88%. Comparing base (22b0614) to head (6a0b175).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main       #8      +/-   ##
============================================
+ Coverage     60.74%   68.88%   +8.14%
============================================
  Files            59       59
  Lines           810      810
  Branches        140      140
============================================
+ Hits            492      558      +66
+ Misses          232      158      -74
- Partials         86       94       +8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Cassette should run the Exclude match against directories in addition to files

I need to research this a bit more, but as I understand the current process, Cassette will run the Exclude match in an IFileSearch only against files it finds within directories. I documented this in my original blog post (where the ~/Public/scripts/pages directory is still considered a bundle albeit empty) about advanced Cassette usage.
The issue that we're running into is that we nest assets under a public folder, so when we bundle PerSubDirectory, some directories will not contain any assets thus causing Cassette to throw a "silent" exception. I'm reporting this second-hand, which is why I want to look into it. Apparently this means we are getting exception emails on every request but Cassette still works fine and assets are bundled fine.
I believe the solution would be when Cassette starts to read in the directory name, it runs the Exclude against it. So a Regex of \\images will match and tell Cassette to ignore the folder contents thus preventing any exceptions. I think this might also help performance (avoiding throwing exceptions).

So in the v1.1 branch, this block of code in Cassette.Configuration.BundleCollectionExtensions (under AddPerSubDirectory):
var directories = parentDirectory.GetDirectories().Where(IsNotHidden);
foreach (var directory in directories)
{
    Trace.Source.TraceInformation(string.Format("Creating {0} for {1}", typeof(T).Name, directory.FullPath));
    var descriptorFile = TryGetDescriptorFile(directory);
    var descriptor = descriptorFile.Exists
        ? new BundleDescriptorReader(descriptorFile).Read()
        : new BundleDescriptor { AssetFilenames = { "*" } };
    var allFiles = fileSearch.FindFiles(directory);
    var bundle = bundleFactory.CreateBundle(directory.FullPath, allFiles, descriptor);
    if (customizeBundle != null) customizeBundle(bundle);
    TraceAssetFilePaths(bundle);
    bundleCollection.Add(bundle);
}

Am I wrong or is there no check inside the loop to see if allFiles truly found any files? Shouldn't there be a check similar to the block above?
var directories = parentDirectory.GetDirectories().Where(IsNotHidden);
foreach (var directory in directories)
{
    Trace.Source.TraceInformation(string.Format("Creating {0} for {1}", typeof(T).Name, directory.FullPath));

    var allFiles = fileSearch.FindFiles(directory);

    if (allFiles.Any()) {
      var descriptorFile = TryGetDescriptorFile(directory);
      var descriptor = descriptorFile.Exists
          ? new BundleDescriptorReader(descriptorFile).Read()
          : new BundleDescriptor { AssetFilenames = { "*" } };

      var bundle = bundleFactory.CreateBundle(directory.FullPath, allFiles, descriptor);
      if (customizeBundle != null) customizeBundle(bundle);
      TraceAssetFilePaths(bundle);
      bundleCollection.Add(bundle);
    }
}


Clean documentation

Overall, is there a rationale is writing comments in a single line
"""This is a comment"""

versus splitting them in multiple lines?
"""
This is a comment
"""


Create a new instance of Auth0 to use different login environment

Checklist

[X] I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved
Our system has different Auth0 tenants for different environments: QA, Stage, Production
We would like to re-initialize our auth0 client when the user selects a different environment.
We currently do this, but discovered that Auth0 retains some settings from the first environment.
Example:

start app
select QA environment
logout
select Production environment
login

This all works until the access token expires. The call to renew the token goes to the QA environment instead of Production.
There must be a singleton or something inside auth0 that does not get cleaned up when we re-initialize the environment.
Describe the ideal solution
Auth0 client should be able to fully dispose and allow the app to create a new instance.
Alternatives and current workarounds
No response
Additional context
No response

Update: We're planning to fix this as a part of the next major version that we're actively working on. The release is tentatively planned for mid Jan.


Logging and misc cleanup

Cleaned up a couple of logging issues that have come up over the last few days in Slack. Also noticed an unnecessary use of meta.Accessor while doing so, so removed it.

LGTM. Did you want to squash before merge, @skriss?

nah


Cache inflight requests for FindLastestAuthorizationModelId

Description

References

Review Checklist

[ ] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[ ] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

No, we didn’t have it before.
The reason this works is due to this line:
https://github.com/openfga/openfga/blob/5e8814be8e74b9e25693d73b273b20b699b42c55/pkg/storage/caching/caching.go#L18
So the struct inherits all the methods of the OpenFGAStorage it receives and any that gets declared simply becomes an override. Basically how you do inheritance in Go.

The cache is only during the duration of the first inflight request.

What does this mean? cachedOpenFGADatastore is shared across all requests

Only concurrent calls to this method are cached together. And it will last for the duration of the first call. Not the whole lifecycle of the request. So if the FindLastestModelID takes 5ms, that's how long the cache will last even tho the request might take a total of 35ms.
Picture this scenario:
R1 -> FindLastestModelID -> Calls Datastore and creates cache
R2 -> FindLastestModelID -> Will share the response with R1
R3 -> ... some delay -> FindLastestModelID -> Calls Datastore and creates new cache
R4 -> ... some delay -> FindLastestModelID -> Will share the response with R2


unix: mch_can_exe: return FALSE with empty PATH

Without this executable("foobar") is 1 after let $PATH="".
https://github.com/vim/vim/pull/3282 would change/fix this already, but
I think an empty $PATH should not be considered to be "not implemented".
This is not a real use case, but I am using this in tests.

Codecov Report

Merging #3283 into master will decrease coverage by 0.03%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master    #3283      +/-   ##
==========================================
- Coverage   76.57%   76.54%   -0.04%
==========================================
  Files          93       93
  Lines      136871   136872       +1
==========================================
- Hits       104815   104774      -41
- Misses      32056    32098      +42

Impacted Files
Coverage Δ

src/os_unix.c
57.41% <66.66%> (-0.01%)
:arrow_down:

src/gui_beval.c
55.02% <0%> (-6.56%)
:arrow_down:

src/window.c
81.87% <0%> (-0.55%)
:arrow_down:

src/gui_gtk_x11.c
48.03% <0%> (-0.25%)
:arrow_down:

src/message.c
74.64% <0%> (-0.25%)
:arrow_down:

src/term.c
59.72% <0%> (-0.21%)
:arrow_down:

src/ex_cmds2.c
82.63% <0%> (-0.1%)
:arrow_down:

src/screen.c
76.71% <0%> (-0.05%)
:arrow_down:

src/if_py_both.h
76.57% <0%> (-0.01%)
:arrow_down:

src/channel.c
83.11% <0%> (+0.03%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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


exploitdb: 2021-11-06 -> 2021-11-09

Motivation for this change
Update to latest upstream release 2021-11-09
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 145367 run on x86_64-linux 1

1 package built:

exploitdb

Change looks good to me
[nix-shell:~/.cache/nixpkgs-review/pr-145367]$ ./results/exploitdb/bin/searchsploit zlog 1.2.15
[i] Found (#1): /nix/store/aq62zilhvzci79s27r1f9ihg6zi8736x-exploitdb-2021-11-09/share/exploitdb/files_exploits.csv
[i] To remove this message, please edit "/nix/store/aq62zilhvzci79s27r1f9ihg6zi8736x-exploitdb-2021-11-09/share/exploitdb/.searchsploit_rc" for "files_exploits.csv" (package_array: exploitdb)

[i] Found (#1): /nix/store/aq62zilhvzci79s27r1f9ihg6zi8736x-exploitdb-2021-11-09/share/exploitdb/files_shellcodes.csv
[i] To remove this message, please edit "/nix/store/aq62zilhvzci79s27r1f9ihg6zi8736x-exploitdb-2021-11-09/share/exploitdb/.searchsploit_rc" for "files_shellcodes.csv" (package_array: exploitdb)

------------------------------------------------------------------------------------------------------------------------------------------------------------ ---------------------------------
 Exploit Title                                                                                |  Path
------------------------------------------------------------------------------------------------------------------------------------------------------------ ---------------------------------
zlog 1.2.15 - Buffer Overflow                                                                                | multiple/local/50504.c
------------------------------------------------------------------------------------------------------------------------------------------------------------ ---------------------------------
Shellcodes: No Results

Result of nixpkgs-review pr 145367 run on x86_64-linux 1

1 package built:

exploitdb


fix: labels for profiles

Fixes Issue
Labels added for profiles, tests, storybook using Action https://github.com/marketplace/actions/label-manager-for-prs-and-issues-based-on-configurable-conditions

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

I made a change to my profile and the level got added...


Fix several spec bugs

This PR fixes several bugs:

The text in g7:HEAD-PLAC-FORM was incorrectly linking to g7:FORM instead of g7:PLAC-FORM
Incorrect media type as reported by @fisharebest in https://github.com/FamilySearch/GEDCOM.io/pull/36
Grammatical nit

for me ok.
Albert


Add License

Coverage remained the same at 95.367% when pulling 547768f7bf84b1d5a16dafcd651196977234c560 on add-license-1 into 9a7ef994ff21d333d8b8455f092923800200c446 on develop.

Coverage remained the same at 95.367% when pulling 547768f7bf84b1d5a16dafcd651196977234c560 on add-license-1 into 9a7ef994ff21d333d8b8455f092923800200c446 on develop.


[Draft] Support stride and distance parameters

Add support for strides and distance parameters. The kernels were changed to copy from and to global memory with strides and distance, the local and private memory access patterns are unaffected.
I introduced a layout enum to differentiate configurations with default layout (PACKED), "transposed" layout (TRANSPOSED) and arbitrary strides and distance (UNPACKED). This should not be needed anymore as a template in the kernels though.
Added some convenient helper methods in the descriptor. We may consider moving them to the detail namespace if we're not sure we want to maintain them for users.
Changed the tests to more easily control which tests should be duplicated for different layouts and directions.
Changed the test reference python script to allow to copy all the test suites (with duplicates).
Checklist
Tick if relevant:

[x] New files have a copyright
[x] New headers have an include guards
[x] API is documented with Doxygen
[x] New functionalities are tested
[ ] Tests pass locally
[ ] Files are clang-formatted

Outdated


Update auth, dynamodb, s3, sqs to 2.17.109

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

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

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

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

Superseded by #804.


fix sorting by translated data

fix sorting by translated data so that where clause is inside the join

thanks!


runner + u22 installer updates

3 files were modified to result in a successful build on ubuntu22 with the gitlab runner:

syntax error fix in the runner file
install paths consistency between moab, double-down, dagmc and openmc
dagmc hotfix for the core-count

Thanks a lot for the edits @bvhoof. I've been making more or less the  edits on my part (on a branch) so I'll merge those afterwards. One small comment - the ccores error is caused by some runners not having a CPU-field in the /proc/cpuinfo. Obvioously ccores should not fail on this being the case.


Add Game: Hidden Maze Escape

Author name
Author: Rylan Berry

About your game
What is your game about?
This game is the final game in my hidden maze trilogy, this game uses the same starting maps as the original, but you can see the walls, but if you complete those five only, you'll get the first ending. For the second ending, you have to find the secret in each map and complete each of their puzzles, then you get the second ending.
The puzzles are hidden in each maze (putting a new meaning to "hidden maze" unlike the original two) you'll have to find them then you'll be taken to the puzzle room.
The puzzles work as follows: Cover all the targets with blocks, then you're done, do the puzzle for each maze then you get the second ending.

How do you play your game?
WASD: Moving up, left, down, and right, respectively.
J: Restarts the entire game.

Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Thanks for viewing my PR!

Hopefully, the previous commits from this fork don't mess with the main branch, but I'm still new to GitHub so be wary.

Hey! no worries about previous commits!! But how exactly the hidden mazes are unlocked?

hii :) i have played the game and searched for the hidden mazes, you have to go places, where you shouldn't normally go to finish the game...
btw @Dark-Sniper101, i like this game!


Add OOV vector imputation to TokenEmbedding

Description
Adds OOV vector imputation to TokenEmbedding.
Based on the changes in https://github.com/dmlc/gluon-nlp/pull/159 . Will be rebased later to include only the changes after https://github.com/dmlc/gluon-nlp/pull/159. All changes for this PR are in the last commit.
Checklist
Essentials

[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[X] Adds OOV vector imputation to TokenEmbedding

Job PR-160/14 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-160/14/index.html


Maintenance fixes to prepare release 0.0.4

Renamed the templates directory from Tempates to StackGenTemplates, to reduce the possibility of name clashes
Update readme with new installtion method
Enable the --version option from SwiftCLI

Codecov Report

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

@@           Coverage Diff           @@
##           master       #6   +/-   ##
=======================================
  Coverage   80.56%   80.56%
=======================================
  Files          35       35
  Lines         808      808
=======================================
  Hits          651      651
  Misses        157      157

Impacted Files
Coverage Δ

...es/StackGenKit/Entities/BundledTemplateGroup.swift
100.00% <ø> (ø)

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 62704dd...0a52bb2. Read the comment docs.


Queue Page

Adds a queue page!

@acrantel I'm having some troubles with styling/controlling my AsyncSelectMenu component... think you could take a look and see if I'm missing anything obvious?

Input box inside select is outlined
Placeholder doesn't show up
Can't figure out how to close the menu when you either click away or select an option

Also my commit history is scuffed... do i need to rebase?

TODO: remove uls from BattlecodeTableBottomElement.tsx 😆

Current bugs:

[ ] Placeholder never shows up
[ ] Input element is outlined
[ ] entering empty string (manually clearing) doesn't register as non-input
[ ] selecting option doesn't close dropdown menu
[ ]

Note: this blocks tournaments-page and scrimmaging-page

TODO: fix tooltip for failed matches in the queue table! (this is for my own reference)


Dead loop occured when doing perf

The pictures above are generated by pstack and gdb.   The async_profiler is maximizing CPU usage and does not exit.  It seems that there is a spin lock which is not got released, leading to such dead loop issue.

What profiler version are you running?
Can you show stack traces of other threads?

What profiler version are you running? Can you show stack traces of other threads?

version is Async-profiler 2.7 built on Nov 25 2022.   The primary scene has already been lost. So I'm sorry that I cannot provide more informations except the exsisting one.

There were many fixes since version 2.7. Please try an up-to-date version of the profiler.
2.7 is no longer supported.

I'm closing the bug assuming it has been already fixed. Feel free to reopen if you encounter this again with a recent version.


(SPIKE) DeploymentHealthMessage

Aggregated under https://github.com/graphops/subgraph-radio/issues/7


WMF 5.1 breaking puppetlabs-dsc v1.1.0?

Hi guys,
Sad to report that when I'm evaluating Windows Server 2016 which ships with WMF 5.1 my Puppet agent run seems to hang indefinently. I've done some further testing and reproduced the behaviour on Server 2012 R2 when installing the WMF 5.1 preview. BUT when using Windows Server 2016 CTP5 I had no problem of this sort, but as I vaguely remember that also had a build of WMF 5.1 in it.
So what I am doing in my manifest is this:
dsc_environment {'RubyPath':
dsc_name   => 'PATH',
dsc_value  => 'C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin',
dsc_path   => true,
dsc_ensure => 'present',
}
I've attached the verbose+debug output that seems relevant. I've also seen the behaviour using a dsc_windowsfeature resource. The above is from our production environment running on ~100 Server 2008R2 -> 2012R2. If not broken of with a ctrl+c it will wait indefinetly. And repeat the: Debug: Waited 50 milliseconds... until the end of time.
Puppet_Dsc_verboseoutput.txt

Hi @freni59, this is a known issue in the underlying code we use to control the PowerShell process. We've been working on a different approach in MODULES-3690 which will resolve this issue. We hope to have the fix out really soon.

@jpogran great to hear, thought you were allready on the case :-)

I'm trying to apply a dsc file resource using puppetlabs-powershell#stable and puppetlabs-dsc#master, and still encounter issues a similar issue: https://gist.github.com/MikaelSmith/4eb55e2672f48f58ad74e5f064b9ff67.
Is the solution for MODULES-3690 being tested with dsc?

@MikaelSmith eventually yes.

Version 1.2.0 of the module has shipped containing this fix.  Closing this issue as a result.

I would like to reopen this issue - with:
puppetlabs-dsc (v1.2.0)
puppetlabs-powershell (v2.1.0)
tested on WIndows 10 Pro, version 1607, Powershell as enclosed:
Name                           Value

PSVersion                      5.1.14393.0
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.0
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
issues pointed out by @MikaelSmith are still present. So at least on Windows 10 Pro Anniversary Edition I am unable to run Powershell DSC.
Debug: 2016-11-19 07:43:23 +0100 C:\Windows\system32\WindowsPowershell\v1.0\powershell.exe -NoProfile -NonInteractive -NoLogo -ExecutionPolicy Bypass -Command - is running as pid: 5392
Debug: Waited 50 milliseconds...
Debug: Waited 50 milliseconds...
Debug: Waited 50 milliseconds...
Debug: Waited 50 milliseconds...
Debug: Waited 50 milliseconds...
Debug: 2016-11-19 07:43:23 +0100 STDOUT> At line:1 char:32

Debug: 2016-11-19 07:43:23 +0100 STDOUT> +         if ($runspace -eq $null)

Debug: 2016-11-19 07:43:23 +0100 STDOUT> +                                ~

Debug: 2016-11-19 07:43:23 +0100 STDOUT> Missing statement block after if ( condition ).

Debug: 2016-11-19 07:43:23 +0100 STDOUT>     + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException

Debug: 2016-11-19 07:43:23 +0100 STDOUT>     + FullyQualifiedErrorId : MissingStatementBlock

Debug: 2016-11-19 07:43:23 +0100 STDOUT>

Debug: 2016-11-19 07:43:23 +0100 STDOUT>

Debug: 2016-11-19 07:43:23 +0100 STDOUT>

Debug: 2016-11-19 07:43:23 +0100 STDOUT>           $runspace = [RunspaceFactory]::CreateRunspace()

Debug: 2016-11-19 07:43:23 +0100 STDOUT>

Debug: 2016-11-19 07:43:23 +0100 STDOUT>           $runspace.Open()

Debug: 2016-11-19 07:43:23 +0100 STDOUT>


Disabling VSync causes memory leak

Godot version
4.0.3 stable (applies to 4.0.1 stable, and 4.0.2 stable as well)
System information
Windows 7, AMD Athlon X4 860 Quad Core Processor, AMD Radeon R7 250 Series
Issue description
Disabling VSync in the Project Settings (as well as in GDScript) sometimes causes a ~60-80 kB/second memory leak, as observed in the Windows Task Manager. The leak happens after running the application for about 10 seconds, after which the memory leak will endlessly pile on, without it being noticed in any of the Godot monitors.
This happens with the Forward+ renderer, the others don't seem to have this issue.
Steps to reproduce
-Run the Windows Task Manager,
-Make sure that the project uses the Forward+ renderer
-Disable VSync in the Project Settings (or GDScript with the DisplayServer.window_set_vsync_mode(DisplayServer.VSYNC_DISABLED); line.)
-Run the your application by clicking the Run Project button,
-Wait for about 10-15 seconds, after which the leak will begin
Minimal reproduction project
Any project will do, simply add a new Node2D, and run the project.

Shouldn't it be something other than DisplayServer.VSYNC_DISABLED

My bad, I typed Enable instead of Disabled.

Cannot confirm on latest version

Do you have any idea why this might happen? It's a pretty big issue for me:

This scene is just a Node2D. Maybe it has something to do with drivers?

Updating your drivers is always a good idea to eliminate problems, this could be a Win7 specific issue, as I am on Win11 and unable to replicate this issue

The fact that disabling V-Sync causes a memory leak is more that uncapping the framerate causes the engine to render far more frames, making memory leak much faster. You can confirm this by leaving V-Sync disabled but setting Max FPS advanced project setting to 60.

Yes, I have noticed that while I was doing some more testing on this issue. I updated my drivers, though it still didn't fix the issue, and the memory leak, although slower when the FPS is capped, is still there, and will eventually eat up memory completely. I didn't bother much with it after this, I simply enabled VSync and left it at that. Since the issue cannot be replicated on later Windows versions, this might be a Win7 limitation with Godot.

Vulkan on Windows 7 tends to have various issues not found on more recent Windows versions. Given you're also on an old GPU (these GPUs only have partial Direct3D 12 support for instance), it's best to stick to the Compatibility rendering method there.

Yeah, I understand, thank you informing me. 👍


update prereqs redirects

Given there are a probably a lot of sites that point to the old articles, I was thinking that it would be better to redirect them to the proper zone. @Thraka what do you think?

Great idea!


Replace The Ruby Racer with Mini Racer (updated)

Hi! This is just the branch we're using at the bundler documentation repository: https://github.com/rubygems/bundler-site, to get this repository working against a newer stack of dependencies.
This is just #36 with one commit on top to allow newer versions of mini_racer.
@matiasgarciaisaia I wonder whether there's any chance of getting some movement here? Thank you! ❤

@manastech Anyone can take a look at this? 🙏

I'm not too optimistic here :( I even sent a private email to @manastech but I got no reply. We should consider other options.

Giving up.


Actor Healthz unauthorized when using Require Authorization on MapActorsHandlers

As per documentation we are requiring all incoming requests to Dapr endpoints to have an "Api Key" in the dapr-api-token header. In the case of Actors when using MapActorsHandlers and chaining RequireAuthorization the Healthz endpoint will now require authorization. However the Daprd runtime excludes the dapr-api-token header when requesting /healthz see file here
Expected Behavior
Expect the Healthz check to ignore authorization being applied to the IEndpointConventionBuilder when calling MapActorsHandlers.RequireAuthorization or allow the location of the Actor Healthz middleware to be specified at any point within the WebApplication. ie before adding UseAuthentication and UseAuthorization.
Actual Behavior
Healthz should return a Ok status code without authorization as this is the expectation of the Daprd runtime.
Steps to Reproduce the Problem

Setup WebApplication to use Api Token authentication
Add Dapr Authorization Policy to enable api token authentication

app.UseAuthentication();
app.UseAuthorization();

app.MapActorsHandlers()
    .RequireAuthorization("Dapr");

Make GET request to /Healthz endpoint
Observe 401 response

Release Note
RELEASE NOTE: FIX Actors Healthz are now always AllowAnonymous.

/assign